<?xml version="1.0" encoding="UTF-8"?>
<FEDREG xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="FRMergedXML.xsd">
    <VOL>91</VOL>
    <NO>127</NO>
    <DATE>Monday, July 6, 2026</DATE>
    <UNITNAME>Contents</UNITNAME>
    <CNTNTS>
        <AGCY>
            <EAR>
                Agency Health
                <PRTPAGE P="iii"/>
            </EAR>
            <HD>Agency for Healthcare Research and Quality</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Patient Safety Organizations:</SJ>
                <SJDENT>
                    <SJDOC>Voluntary Relinquishment for the Cassatt Patient Safety Organization, </SJDOC>
                    <PGS>41030</PGS>
                    <FRDOCBP>2026-13604</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Agriculture</EAR>
            <HD>Agriculture Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Commodity Credit Corporation</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Farm Service Agency</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Rural Utilities Service</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>40966-40967</PGS>
                    <FRDOCBP>2026-13589</FRDOCBP>
                      
                    <FRDOCBP>2026-13618</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Alcohol Tobacco Firearms</EAR>
            <HD>Alcohol, Tobacco, Firearms, and Explosives Bureau</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Licensee ``eZ Check'' Verification for Transfers; Withdrawal, </DOC>
                    <PGS>40879</PGS>
                    <FRDOCBP>2026-13585</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Fingerprint and Photograph Requirements for Firearms Applications, </DOC>
                    <PGS>40924-40944</PGS>
                    <FRDOCBP>2026-13587</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Registering National Firearms Act Firearms That Fall Out of Government Contract, </DOC>
                    <PGS>40944-40954</PGS>
                    <FRDOCBP>2026-13586</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Antitrust Division</EAR>
            <HD>Antitrust Division</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Proposed Final Judgment and Competitive Impact Statement:</SJ>
                <SJDENT>
                    <SJDOC>United States et al. v. Live Nation Entertainment, Inc., </SJDOC>
                    <PGS>41330-41408</PGS>
                    <FRDOCBP>2026-13623</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Fiscal</EAR>
            <HD>Bureau of the Fiscal Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Certificate of Identity, </SJDOC>
                    <PGS>41170</PGS>
                    <FRDOCBP>2026-13508</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Pools and Associations—Annual Letter, </SJDOC>
                    <PGS>41170-41171</PGS>
                    <FRDOCBP>2026-13507</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Special Form of Request for Payment of US Savings and Retirement Securities Where Use of a Detached Request is Authorized, </SJDOC>
                    <PGS>41171</PGS>
                    <FRDOCBP>2026-13504</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>TreasuryDirect System, </SJDOC>
                    <PGS>41169-41170</PGS>
                    <FRDOCBP>2026-13505</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Centers Disease</EAR>
            <HD>Centers for Disease Control and Prevention</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>41030-41037</PGS>
                    <FRDOCBP>2026-13558</FRDOCBP>
                      
                    <FRDOCBP>2026-13559</FRDOCBP>
                      
                    <FRDOCBP>2026-13560</FRDOCBP>
                      
                    <FRDOCBP>2026-13561</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Centers Medicare</EAR>
            <HD>Centers for Medicare &amp; Medicaid Services</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Calendar Year 2027 Home Health Prospective Payment System Rate Update; etc., </DOC>
                    <PGS>41216-41327</PGS>
                    <FRDOCBP>2026-13602</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>41039-41040</PGS>
                    <FRDOCBP>2026-13603</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Privacy Act; Matching Program, </DOC>
                    <PGS>41037-41039</PGS>
                    <FRDOCBP>2026-13572</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Coast Guard</EAR>
            <HD>Coast Guard</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Regulated Navigation Area:</SJ>
                <SJDENT>
                    <SJDOC>Hudson River, Albany, NY, </SJDOC>
                    <PGS>40892-40896</PGS>
                    <FRDOCBP>2026-13568</FRDOCBP>
                </SJDENT>
                <SJ>Safety Zone:</SJ>
                <SJDENT>
                    <SJDOC>America 250 Fireworks 2026, San Francisco, CA, </SJDOC>
                    <PGS>40889-40891</PGS>
                    <FRDOCBP>2026-13551</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Annual Events Requiring Safety Zones in the Captain of the Port Lake Michigan Zone, </SJDOC>
                    <PGS>40887</PGS>
                    <FRDOCBP>2026-13548</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Fireworks Displays in the USCG East District, Ocean City, NJ, </SJDOC>
                    <PGS>40887-40888</PGS>
                    <FRDOCBP>2026-13562</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Fireworks Displays within the USCG East District, </SJDOC>
                    <PGS>40896-40898</PGS>
                    <FRDOCBP>2026-13555</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Lake Michigan, Chicago, IL, </SJDOC>
                    <PGS>40891-40892</PGS>
                    <FRDOCBP>2026-13619</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Marine Events within the USCG East District, </SJDOC>
                    <PGS>40885-40887</PGS>
                    <FRDOCBP>2026-13556</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Savannah River, Savannah, GA, </SJDOC>
                    <PGS>40888-40889</PGS>
                    <FRDOCBP>2026-13614</FRDOCBP>
                </SJDENT>
                <SJ>Special Local Regulation:</SJ>
                <SJDENT>
                    <SJDOC>Marine Events within the Coast Guard East District, </SJDOC>
                    <PGS>40885</PGS>
                    <FRDOCBP>2026-13554</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Commerce</EAR>
            <HD>Commerce Department</HD>
            <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>Commodity Credit</EAR>
            <HD>Commodity Credit Corporation</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Organic Certification Cost Share Program, </DOC>
                    <PGS>40859-40865</PGS>
                    <FRDOCBP>2026-13571</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Defense Department</EAR>
            <HD>Defense Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Charter Amendments, Establishments, Renewals and Terminations:</SJ>
                <SJDENT>
                    <SJDOC>Board of Actuaries, </SJDOC>
                    <PGS>40989-40991</PGS>
                    <FRDOCBP>2026-13514</FRDOCBP>
                </SJDENT>
                <SJ>Hearings, Meetings, Proceedings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Wage Committee, </SJDOC>
                    <PGS>40987-40989</PGS>
                    <FRDOCBP>2026-13516</FRDOCBP>
                </SJDENT>
                <SJ>TRICARE Demonstration Project:</SJ>
                <SJDENT>
                    <SJDOC>TRICARE Ambulance Add-On Reimbursement for Pre-Hospital Blood Transfusion, </SJDOC>
                    <PGS>40985-40987</PGS>
                    <FRDOCBP>2026-13515</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Drug</EAR>
            <HD>Drug Enforcement Administration</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Schedules of Controlled Substances:</SJ>
                <SJDENT>
                    <SJDOC>Temporary Placement of 7-Hydroxymitragynine above a Specified Threshold in Schedule I, </SJDOC>
                    <PGS>40917-40924</PGS>
                    <FRDOCBP>2026-13580</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Temporary Placement of Mitragynine Pseudoindoxyl, MGM-15, and MGM-16 in Schedule I, </SJDOC>
                    <PGS>40909-40916</PGS>
                    <FRDOCBP>2026-13581</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Education Department</EAR>
            <HD>Education Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Foreign Gifts and Contracts Disclosures; Correction, </DOC>
                    <PGS>40991</PGS>
                    <FRDOCBP>2026-13605</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Energy Department</EAR>
            <HD>Energy Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Federal Energy Regulatory Commission</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Implementing Voluntary Agreements under the Defense Production Act, </DOC>
                    <PGS>40991-41002</PGS>
                    <FRDOCBP>2026-13486</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Environmental Protection</EAR>
            <HD>Environmental Protection Agency</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>National Emission Standards for Hazardous Air Pollutants:</SJ>
                <SJDENT>
                    <SJDOC>Plywood and Composite Wood Products, </SJDOC>
                    <PGS>41410-41464</PGS>
                    <FRDOCBP>2026-13550</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Pesticide Tolerance; Exemptions, Petitions, Revocations, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Receipt of Pesticide Petitions Filed for Residues of Pesticide Chemicals in or on Various Commodities—April 2026, </SJDOC>
                    <PGS>40962-40964</PGS>
                    <FRDOCBP>2026-13557</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <PRTPAGE P="iv"/>
                <HD>NOTICES</HD>
                <SJ>Guidance:</SJ>
                <SJDENT>
                    <SJDOC>Reducing Risk from Perfluorooctanoic Acid and Perfluorooctane Sulfonic Acid in Biosolids, </SJDOC>
                    <PGS>41020-41022</PGS>
                    <FRDOCBP>2026-13615</FRDOCBP>
                </SJDENT>
                <SJ>Pesticide Product Registration:</SJ>
                <SJDENT>
                    <SJDOC>Applications for New Active Ingredients (April 2026), </SJDOC>
                    <PGS>41019-41020</PGS>
                    <FRDOCBP>2026-13553</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Applications for New Uses (April 2026), </SJDOC>
                    <PGS>41018-41019</PGS>
                    <FRDOCBP>2026-13552</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Equal</EAR>
            <HD>Equal Employment Opportunity Commission</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Rescission of Guidelines on Affirmative Action Appropriate Under Title VII of the Civil Rights Act, as Amended, </DOC>
                    <PGS>40879-40885</PGS>
                    <FRDOCBP>2026-13637</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Meetings; Sunshine Act, </DOC>
                    <PGS>41022</PGS>
                    <FRDOCBP>2026-13584</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Farm Service</EAR>
            <HD>Farm Service Agency</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>General Program Administration, </SJDOC>
                    <PGS>40967-40968</PGS>
                    <FRDOCBP>2026-13606</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Aviation</EAR>
            <HD>Federal Aviation Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Airworthiness Directives:</SJ>
                <SJDENT>
                    <SJDOC>Airbus Helicopters, </SJDOC>
                    <PGS>40865-40870</PGS>
                    <FRDOCBP>2026-13538</FRDOCBP>
                      
                    <FRDOCBP>2026-13540</FRDOCBP>
                </SJDENT>
                <SJ>Restricted Area:</SJ>
                <SJDENT>
                    <SJDOC>North Carolina, </SJDOC>
                    <PGS>40870-40872</PGS>
                    <FRDOCBP>2026-13620</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Airworthiness Directives:</SJ>
                <SJDENT>
                    <SJDOC>Rolls-Royce Deutschland Ltd and Co KG Engines, </SJDOC>
                    <PGS>40900-40902</PGS>
                    <FRDOCBP>2026-13541</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Ensuring Passenger Safety by Preempting Duty and Rest Requirements, </DOC>
                    <PGS>40902-40909</PGS>
                    <FRDOCBP>2026-13546</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Communications</EAR>
            <HD>Federal Communications Commission</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Petition for Reconsideration of Action in Rulemaking Proceeding, </DOC>
                    <PGS>40964-40965</PGS>
                    <FRDOCBP>2026-13611</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>41022-41023, 41025-41028</PGS>
                    <FRDOCBP>2026-13593</FRDOCBP>
                      
                    <FRDOCBP>2026-13601</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Prohibiting Importation and Marketing of Previously Authorized Covered Communications Equipment Added to the Covered List in 2024 or Earlier, </DOC>
                    <PGS>41023-41025</PGS>
                    <FRDOCBP>2026-13518</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Deposit</EAR>
            <HD>Federal Deposit Insurance Corporation</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>41028-41029</PGS>
                    <FRDOCBP>2026-13506</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Energy</EAR>
            <HD>Federal Energy Regulatory Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Application:</SJ>
                <SJDENT>
                    <SJDOC>Dominion Energy South Carolina, Inc., </SJDOC>
                    <PGS>41015-41016</PGS>
                    <FRDOCBP>2026-13596</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Southeast Supply Header, LLC, </SJDOC>
                    <PGS>41005-41007</PGS>
                    <FRDOCBP>2026-13598</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Steel Reef Pipelines US LLC, </SJDOC>
                    <PGS>41011-41013</PGS>
                    <FRDOCBP>2026-13597</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Vinton Dome Storage Hub, LLC, </SJDOC>
                    <PGS>41016-41018</PGS>
                    <FRDOCBP>2026-13599</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Combined Filings, </DOC>
                    <PGS>41003-41005, 41010-41011, 41013-41014</PGS>
                    <FRDOCBP>2026-13563</FRDOCBP>
                      
                    <FRDOCBP>2026-13564</FRDOCBP>
                      
                    <FRDOCBP>2026-13565</FRDOCBP>
                </DOCENT>
                <SJ>Environmental Assessments; Availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Powerhouse Systems, LLC, </SJDOC>
                    <PGS>41009</PGS>
                    <FRDOCBP>2026-13594</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Public Service Co. of Colorado, </SJDOC>
                    <PGS>41005</PGS>
                    <FRDOCBP>2026-13595</FRDOCBP>
                </SJDENT>
                <SJ>Environmental Issues:</SJ>
                <SJDENT>
                    <SJDOC>Columbia Gas Transmission, LLC, Majorsville-Heard Storage Complex Abandonment Project, </SJDOC>
                    <PGS>41007-41009</PGS>
                    <FRDOCBP>2026-13600</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Records Governing Off-the-Record Communications, </DOC>
                    <PGS>41014-41015</PGS>
                    <FRDOCBP>2026-13566</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Reserve</EAR>
            <HD>Federal Reserve System</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Change in Bank Control:</SJ>
                <SJDENT>
                    <SJDOC>Acquisitions of Shares of a Bank or Bank Holding Company, </SJDOC>
                    <PGS>41029-41030</PGS>
                    <FRDOCBP>2026-13591</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Food and Drug</EAR>
            <HD>Food and Drug Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Administrative Practices and Procedures; Formal Hearings, </SJDOC>
                    <PGS>41040-41041</PGS>
                    <FRDOCBP>2026-13534</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Biologics License Applications, Procedures and Requirements, </SJDOC>
                    <PGS>41046-41049</PGS>
                    <FRDOCBP>2026-13533</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Premarket Approval of Medical Devices, </SJDOC>
                    <PGS>41042-41045</PGS>
                    <FRDOCBP>2026-13519</FRDOCBP>
                </SJDENT>
                <SJ>Drug Products not Withdrawn from Sale for Reasons of Safety or Effectiveness:</SJ>
                <SJDENT>
                    <SJDOC>Vasopressin in Sodium Chloride (vasopressin) 0.9 Percent, Injection, 50 units/50 milliliters (1 unit/ milliliters), </SJDOC>
                    <PGS>41041-41042</PGS>
                    <FRDOCBP>2026-13492</FRDOCBP>
                </SJDENT>
                <SJ>Request for Information:</SJ>
                <SJDENT>
                    <SJDOC>Expedited Investigational New Drug Pilot Program; Correction, </SJDOC>
                    <PGS>41049</PGS>
                    <FRDOCBP>2026-13592</FRDOCBP>
                </SJDENT>
                <SJ>Withdrawal of Approval of Drug Application:</SJ>
                <SJDENT>
                    <SJDOC>Endo Operations Ltd., et al., </SJDOC>
                    <PGS>41045-41046</PGS>
                    <FRDOCBP>2026-13616</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Foreign Assets</EAR>
            <HD>Foreign Assets Control Office</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Sanctions Action, </DOC>
                    <PGS>41171-41173</PGS>
                    <FRDOCBP>2026-13494</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Health and Human</EAR>
            <HD>Health and Human Services Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Agency for Healthcare Research and Quality</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Centers for Disease Control and Prevention</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Centers for Medicare &amp; Medicaid Services</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Food and Drug Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Institutes of Health</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Substance Abuse and Mental Health Services Administration</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Request for Information:</SJ>
                <SJDENT>
                    <SJDOC>Temporary Placement of 7-Hydroxymitragynine above a Specified Threshold in Schedule I, </SJDOC>
                    <PGS>41049-41050</PGS>
                    <FRDOCBP>2026-13608</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Homeland</EAR>
            <HD>Homeland Security Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Coast Guard</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>U.S. Customs and Border Protection</P>
            </SEE>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Counter-Unmanned Aircraft System Authority for State, Local, Tribal, and Territorial Law Enforcement and Correctional Agencies, </DOC>
                    <PGS>41466-41516</PGS>
                    <FRDOCBP>2026-13609</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Housing</EAR>
            <HD>Housing and Urban Development Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Privacy Act; Systems of Records, </DOC>
                    <PGS>41058</PGS>
                    <FRDOCBP>2026-13543</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Regulatory Waiver Requests Granted for the Fourth Quarter of Calendar Year 2025, </DOC>
                    <PGS>41176-41214</PGS>
                    <FRDOCBP>2026-13539</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Regulatory Waiver Requests Granted for the Third Quarter of Calendar Year 2025, </DOC>
                    <PGS>41061-41082</PGS>
                    <FRDOCBP>2026-13537</FRDOCBP>
                </DOCENT>
                <SJ>Section 8 Housing Assistance Payments Program:</SJ>
                <SJDENT>
                    <SJDOC>Fiscal Year 2026 Inflation Factors for Public Housing Agency Renewal Funding, </SJDOC>
                    <PGS>41058-41061</PGS>
                    <FRDOCBP>2026-13542</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>
                Interior
                <PRTPAGE P="v"/>
            </EAR>
            <HD>Interior Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Land Management Bureau</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Office of Natural Resources Revenue</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>International Trade Adm</EAR>
            <HD>International Trade Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Common Alloy Aluminum Sheet from Bahrain, India, and the Republic of Turkiye, </SJDOC>
                    <PGS>40977-40979</PGS>
                    <FRDOCBP>2026-13513</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Request for Duty-Free Entry of Scientific Instrument or Apparatus, </SJDOC>
                    <PGS>40981-40982</PGS>
                    <FRDOCBP>2026-13626</FRDOCBP>
                </SJDENT>
                <SJ>Antidumping or Countervailing Duty Investigations, Orders, or Reviews:</SJ>
                <SJDENT>
                    <SJDOC>Carbon and Certain Alloy Steel Wire Rod from Mexico, </SJDOC>
                    <PGS>40974-40975</PGS>
                    <FRDOCBP>2026-13567</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Certain Corrosion-Resistant Steel Products from the People's Republic of China, </SJDOC>
                    <PGS>40969-40970</PGS>
                    <FRDOCBP>2026-13607</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Common Alloy Aluminum Sheet from Bahrain, Brazil, Croatia, Egypt, Germany, India, Indonesia, Italy, Oman, Romania, Serbia, Slovenia, South Africa, Spain, Taiwan, and the Republic of Turkiye, </SJDOC>
                    <PGS>40972-40974</PGS>
                    <FRDOCBP>2026-13511</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Common Alloy Aluminum Sheet from Bahrain, India, and the Republic of Turkiye, </SJDOC>
                    <PGS>40979-40980</PGS>
                    <FRDOCBP>2026-13509</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Diamond Sawblades and Parts Thereof from the People's Republic of China, </SJDOC>
                    <PGS>40976</PGS>
                    <FRDOCBP>2026-13573</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Seamless Carbon and Alloy Steel Standard, Line, and Pressure Pipe from the Czech Republic, Republic of Korea, the Russian Federation, and Ukraine, </SJDOC>
                    <PGS>40980-40981</PGS>
                    <FRDOCBP>2026-13489</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Seamless Carbon and Alloy Steel Standard, Line, and Pressure Pipe from the Republic of Korea and the Russian Federation, </SJDOC>
                    <PGS>40982-40983</PGS>
                    <FRDOCBP>2026-13490</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Silicon Metal from Bosnia and Herzegovina, Iceland, and Malaysia, </SJDOC>
                    <PGS>40983-40984</PGS>
                    <FRDOCBP>2026-13512</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Standard Steel Welded Wire Mesh from Mexico, </SJDOC>
                    <PGS>40976-40977</PGS>
                    <FRDOCBP>2026-13510</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Steel Concrete Reinforcing Bar from Algeria, </SJDOC>
                    <PGS>40970-40972</PGS>
                    <FRDOCBP>2026-13488</FRDOCBP>
                </SJDENT>
            </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>Diamond Sawblades and Parts Thereof from China, </SJDOC>
                    <PGS>41084-41085</PGS>
                    <FRDOCBP>2026-13610</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Glyphosate from China, </SJDOC>
                    <PGS>41085-41086</PGS>
                    <FRDOCBP>2026-13517</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Justice Department</EAR>
            <HD>Justice Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Alcohol, Tobacco, Firearms, and Explosives Bureau</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Antitrust Division</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Drug Enforcement Administration</P>
            </SEE>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Counter-Unmanned Aircraft System Authority for State, Local, Tribal, and Territorial Law Enforcement and Correctional Agencies, </DOC>
                    <PGS>41466-41516</PGS>
                    <FRDOCBP>2026-13609</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Land</EAR>
            <HD>Land Management Bureau</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Plats of Survey:</SJ>
                <SJDENT>
                    <SJDOC>Minnesota, </SJDOC>
                    <PGS>41082</PGS>
                    <FRDOCBP>2026-13503</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Maritime</EAR>
            <HD>Maritime Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Use of Foreign-Built Small Passenger Vessel in United States Coastwise Trade:</SJ>
                <SJDENT>
                    <SJDOC>M/V Deuce, </SJDOC>
                    <PGS>41163-41164</PGS>
                    <FRDOCBP>2026-13502</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>M/V Meat Wagon 2, </SJDOC>
                    <PGS>41165-41166</PGS>
                    <FRDOCBP>2026-13498</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>S/V Gracie, </SJDOC>
                    <PGS>41164-41165</PGS>
                    <FRDOCBP>2026-13501</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>S/V Kingsley, </SJDOC>
                    <PGS>41166-41167</PGS>
                    <FRDOCBP>2026-13500</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>S/V Lady Susan, </SJDOC>
                    <PGS>41162-41163</PGS>
                    <FRDOCBP>2026-13499</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>S/V Nauti Dog, </SJDOC>
                    <PGS>41167-41168</PGS>
                    <FRDOCBP>2026-13497</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>NASA</EAR>
            <HD>National Aeronautics and Space Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Nondiscrimination in Federally Assisted Programs of NASA—Effectuation of Title VI of the Civil Rights Act, </DOC>
                    <PGS>40872-40879</PGS>
                    <FRDOCBP>2026-13624</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Archives</EAR>
            <HD>National Archives and Records Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Hearings, Meetings, Proceedings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>State, Local, Tribal, and Private Sector Policy Advisory Committee, </SJDOC>
                    <PGS>41086</PGS>
                    <FRDOCBP>2026-13590</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Endowment for the Arts</EAR>
            <HD>National Endowment for the Arts</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Hearings, Meetings, Proceedings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Arts Advisory Panel, </SJDOC>
                    <PGS>41086-41087</PGS>
                    <FRDOCBP>2026-13613</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Foundation</EAR>
            <HD>National Foundation on the Arts and the Humanities</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Endowment for the Arts</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>National Highway</EAR>
            <HD>National Highway Traffic Safety Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Petition for Decision of Inconsequential Noncompliance:</SJ>
                <SJDENT>
                    <SJDOC>Rivian Automotive, LLC, </SJDOC>
                    <PGS>41168-41169</PGS>
                    <FRDOCBP>2026-13544</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Institute</EAR>
            <HD>National Institutes of Health</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Generic Clearance for National Institutes of Health Citizen Science and Crowdsourcing Projects, </SJDOC>
                    <PGS>41050-41051</PGS>
                    <FRDOCBP>2026-13583</FRDOCBP>
                </SJDENT>
                <SJ>Hearings, Meetings, Proceedings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Center for Scientific Review, </SJDOC>
                    <PGS>41051-41052</PGS>
                    <FRDOCBP>2026-13612</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Oceanic</EAR>
            <HD>National Oceanic and Atmospheric Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Atlantic Highly Migratory Species:</SJ>
                <SJDENT>
                    <SJDOC>Atlantic Bluefin Tuna Fisheries; Closure of the Angling Category Southern New England Area Trophy Fishery for 2026, </SJDOC>
                    <PGS>40898-40899</PGS>
                    <FRDOCBP>2026-13630</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Wage Mariner Hiring Portal, </SJDOC>
                    <PGS>40984-40985</PGS>
                    <FRDOCBP>2026-13625</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Natural Resources</EAR>
            <HD>Office of Natural Resources Revenue</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Federal Oil and Gas Valuation, </SJDOC>
                    <PGS>41082-41084</PGS>
                    <FRDOCBP>2026-13536</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Pension Benefit</EAR>
            <HD>Pension Benefit Guaranty Corporation</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Improvements to Rules on Recoupment of Benefit Overpayments, </DOC>
                    <PGS>40954-40962</PGS>
                    <FRDOCBP>2026-13639</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Postal Regulatory</EAR>
            <HD>Postal Regulatory Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>New Postal Products, </DOC>
                    <PGS>41087</PGS>
                    <FRDOCBP>2026-13617</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>
                Presidential Documents
                <PRTPAGE P="vi"/>
            </EAR>
            <HD>Presidential Documents</HD>
            <CAT>
                <HD>ADMINISTRATIVE ORDERS</HD>
                <DOCENT>
                    <DOC>Venezuela; Presidential Determination on Assistance Consistent With the Trafficking Victims Protection Act of 2000 (Presidential Determination No. 2026-17 of June 26, 2026), </DOC>
                    <PGS>41517-41519</PGS>
                    <FRDOCBP>2026-13631</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Rural Utilities</EAR>
            <HD>Rural Utilities Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>40968-40969</PGS>
                    <FRDOCBP>2026-13622</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>41091-41092, 41113-41114</PGS>
                    <FRDOCBP>2026-13495</FRDOCBP>
                      
                    <FRDOCBP>2026-13496</FRDOCBP>
                </DOCENT>
                <SJ>Application:</SJ>
                <SJDENT>
                    <SJDOC>Blue Tractor ETF Trust, et al., </SJDOC>
                    <PGS>41102-41104</PGS>
                    <FRDOCBP>2026-13493</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Manulife Investment Management Private Markets (US) LLC; Manulife Employee Securities Co. 2025, LP, </SJDOC>
                    <PGS>41090-41091</PGS>
                    <FRDOCBP>2026-13569</FRDOCBP>
                </SJDENT>
                <SJ>Self-Regulatory Organizations; Proposed Rule Changes:</SJ>
                <SJDENT>
                    <SJDOC>BOX Exchange LLC, </SJDOC>
                    <PGS>41088-41090</PGS>
                    <FRDOCBP>2026-13524</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Financial Industry Regulatory Authority, Inc., </SJDOC>
                    <PGS>41109-41110</PGS>
                    <FRDOCBP>2026-13530</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Miami International Securities Exchange, LLC, </SJDOC>
                    <PGS>41095-41102</PGS>
                    <FRDOCBP>2026-13522</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>MIAX PEARL, LLC, </SJDOC>
                    <PGS>41114-41120</PGS>
                    <FRDOCBP>2026-13520</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>National Securities Clearing Corp., </SJDOC>
                    <PGS>41128-41138</PGS>
                    <FRDOCBP>2026-13523</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>NYSE American LLC, </SJDOC>
                    <PGS>41104-41109, 41149-41153</PGS>
                    <FRDOCBP>2026-13527</FRDOCBP>
                      
                    <FRDOCBP>2026-13532</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>NYSE Arca, Inc., </SJDOC>
                    <PGS>41110-41113, 41123-41128</PGS>
                    <FRDOCBP>2026-13528</FRDOCBP>
                      
                    <FRDOCBP>2026-13535</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>NYSE National, Inc., </SJDOC>
                    <PGS>41143-41149</PGS>
                    <FRDOCBP>2026-13529</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>NYSE Texas, Inc., </SJDOC>
                    <PGS>41121-41123, 41138-41143, 41153-41161</PGS>
                    <FRDOCBP>2026-13521</FRDOCBP>
                      
                    <FRDOCBP>2026-13525</FRDOCBP>
                      
                    <FRDOCBP>2026-13531</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Texas Stock Exchange LLC, </SJDOC>
                    <PGS>41092-41095</PGS>
                    <FRDOCBP>2026-13526</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Small Business</EAR>
            <HD>Small Business Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Disaster Declaration:</SJ>
                <SJDENT>
                    <SJDOC>New York, </SJDOC>
                    <PGS>41161</PGS>
                    <FRDOCBP>2026-13570</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>State Department</EAR>
            <HD>State Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Culturally Significant Objects Imported for Exhibition:</SJ>
                <SJDENT>
                    <SJDOC>Maverick Kings: Three Visionary Pharaohs of Egypt's Golden Age, </SJDOC>
                    <PGS>41161-41162</PGS>
                    <FRDOCBP>2026-13545</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Substance</EAR>
            <HD>Substance Abuse and Mental Health Services Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>41052-41053</PGS>
                    <FRDOCBP>2026-13621</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>Maritime Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Highway Traffic Safety Administration</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Treasury</EAR>
            <HD>Treasury Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Bureau of the Fiscal Service</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Foreign Assets Control Office</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Customs</EAR>
            <HD>U.S. Customs and Border Protection</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Commercial Gauger and Laboratory; Accreditation and Approval:</SJ>
                <SJDENT>
                    <SJDOC>NMK Resources, Inc. (Pasadena, TX), </SJDOC>
                    <PGS>41057-41058</PGS>
                    <FRDOCBP>2026-13577</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>NMK Resources, Inc. (Thorofare, NJ), </SJDOC>
                    <PGS>41056-41057</PGS>
                    <FRDOCBP>2026-13578</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>The Strawn Group (Houston, TX), </SJDOC>
                    <PGS>41053</PGS>
                    <FRDOCBP>2026-13575</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Modification and Clarification of the National Customs Automation Program Test Regarding Post-Summary Corrections, </DOC>
                    <PGS>41053-41056</PGS>
                    <FRDOCBP>2026-13574</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <PTS>
            <HD SOURCE="HED">Separate Parts In This Issue</HD>
            <HD>Part II</HD>
            <DOCENT>
                <DOC>Housing and Urban Development Department, </DOC>
                <PGS>41176-41214</PGS>
                <FRDOCBP>2026-13539</FRDOCBP>
            </DOCENT>
            <HD>Part III</HD>
            <DOCENT>
                <DOC>Health and Human Services Department, Centers for Medicare &amp; Medicaid Services, </DOC>
                <PGS>41216-41327</PGS>
                <FRDOCBP>2026-13602</FRDOCBP>
            </DOCENT>
            <HD>Part IV</HD>
            <DOCENT>
                <DOC>Justice Department, Antitrust Division, </DOC>
                <PGS>41330-41408</PGS>
                <FRDOCBP>2026-13623</FRDOCBP>
            </DOCENT>
            <HD>Part V</HD>
            <DOCENT>
                <DOC>Environmental Protection Agency, </DOC>
                <PGS>41410-41464</PGS>
                <FRDOCBP>2026-13550</FRDOCBP>
            </DOCENT>
            <HD>Part VI</HD>
            <DOCENT>
                <DOC>Homeland Security Department, </DOC>
                <PGS>41466-41516</PGS>
                <FRDOCBP>2026-13609</FRDOCBP>
            </DOCENT>
            <DOCENT>
                <DOC>Justice Department, </DOC>
                <PGS>41466-41516</PGS>
                <FRDOCBP>2026-13609</FRDOCBP>
            </DOCENT>
            <HD>Part VII</HD>
            <DOCENT>
                <DOC>Presidential Documents, </DOC>
                <PGS>41517-41519</PGS>
                <FRDOCBP>2026-13631</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>127</NO>
    <DATE>Monday, July 6, 2026</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <RULES>
        <RULE>
            <PREAMB>
                <PRTPAGE P="40859"/>
                <AGENCY TYPE="F">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBAGY>Commodity Credit Corporation</SUBAGY>
                <CFR>7 CFR Part 1417</CFR>
                <DEPDOC>[Docket ID FSA-2026-0331]</DEPDOC>
                <RIN>RIN 0560-AI85</RIN>
                <SUBJECT>Organic Certification Cost Share Program (OCCSP)</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Commodity Credit Corporation, 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>The One Big Beautiful Bill Act (OBBBA) provides funding for the Organic Certification Cost Share Program (OCCSP) for fiscal years 2025 through 2031, and, as a result, the Commodity Credit Corporation (CCC) is issuing this rule to establish OCCSP for 2025 and future program years. The rule specifies the eligibility criteria and payment calculation for OCCSP, which are consistent with how CCC has administered OCCSP in previous years by Notices of Funding Availability (NOFAs). Prior NOFAs also established the opportunity for State agencies to enter into agreements to administer OCCSP; these provisions are also included in this rule. The rule also establishes the application process and deadlines for eligible producers and handlers who apply through FSA county offices.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This rule is effective on July 6, 2026.</P>
                    <P>
                        <E T="03">Producer and Handler Applications:</E>
                         FSA county offices will accept applications for OCCSP payments from producers and handlers for the 2025 and 2026 program years until December 31, 2026. For 2027 and subsequent program years, producers and handlers may submit applications to FSA county offices from the beginning of the application period, which will be announced through a press release and on the OCCSP website (
                        <E T="03">https://www.fsa.usda.gov/resources/income-support/organic-certification-cost-share-program-occsp</E>
                        ), through December 31 following the end of the program year. That means, for example, that for the 2027 program year, producers have until December 31, 2028, to submit an application for payment under OCCSP. Producers and handlers who apply through a participating State agency should refer to the State agency for application period beginning and ending dates.
                    </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Jenae Orso; telephone: (229) 850-0194; or email: 
                        <E T="03">Jenae.Orso@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. Available Funding</FP>
                    <FP SOURCE="FP-2">III. State Agency Participation</FP>
                    <FP SOURCE="FP-2">IV. Eligible Producers and Handlers</FP>
                    <FP SOURCE="FP-2">V. Eligible Scopes</FP>
                    <FP SOURCE="FP-2">VI. Allowable and Unallowable Costs</FP>
                    <FP SOURCE="FP-2">VII. How to Apply</FP>
                    <FP SOURCE="FP1-2">A. Applying Through an FSA County Office</FP>
                    <FP SOURCE="FP1-2">B. Applying Through a Participating State Agency</FP>
                    <FP SOURCE="FP-2">VIII. Payments</FP>
                    <FP SOURCE="FP-2">IX. Regulatory Analyses</FP>
                    <FP SOURCE="FP1-2">A. Notice and Comment and Effective Date</FP>
                    <FP SOURCE="FP1-2">B. Executive Orders 12866, 13563, and 14192</FP>
                    <FP SOURCE="FP1-2">C. Environmental Review</FP>
                    <FP SOURCE="FP1-2">D. Executive Order 13175</FP>
                    <FP SOURCE="FP1-2">E. Unfunded Mandates Reform Act</FP>
                    <FP SOURCE="FP1-2">F. Paperwork Reduction Act Requirements</FP>
                    <FP SOURCE="FP1-2">G. E-Government Act Compliance</FP>
                </EXTRACT>
                <HD SOURCE="HD1">I. Background</HD>
                <P>OCCSP provides cost share assistance to producers and handlers of agricultural products for the costs of obtaining or maintaining organic certification under the National Organic Program (NOP; 7 CFR part 205). USDA's Agricultural Marketing Service (AMS) administers the NOP, which develops and enforces consistent national standards for organically produced agricultural products sold in the United States and accredits third-party organizations to certify that farms and businesses meet the national organic standards. OCCSP is a separate program, administered by FSA on behalf of CCC, that provides financial support to producers and handlers who are certified under the NOP. This financial assistance helps organic producers and handlers sustain their operations and meet the growing consumer demand for products that meet the robust standard indicated by the USDA organic label, which supports the Trump Administration's expansive efforts to Make America Healthy Again. National funding for 2025 through 2031 was authorized by Section 10606(e) of the One Big Beautiful Bill Act (OBBBA; Pub. L. 119-21), which was signed on July 4, 2025. Due to the delay in authorization of National funding for 2025, CCC will administer OCCSP for the 2025 and 2026 program years concurrently.</P>
                <P>Prior to 2017, OCCSP was administered by AMS through grants with State agencies. Beginning in 2017, administration of the program was transferred to FSA on behalf of CCC and cost share assistance has been provided through two approaches: (1) through grant agreements with State agencies that provide cost share payments to producers and handlers in their state; and (2) by issuing payments directly to producers and handlers who apply for cost share payments through an FSA county office (see 82 FR 23522, May 23, 2017; 84 FR 17997, April 29, 2019; and 89 FR 39579, May 9, 2024).</P>
                <P>This final rule specifies the OCCSP eligibility criteria and payment calculation for producers and handlers. It also establishes the application process and deadlines for eligible producers and handlers who apply through FSA county offices, and it announces the opportunity for State agencies to establish agreements through grants to administer OCCSP. This final rule is not making substantive changes to the administration of OCCSP. The provisions of this final rule, which address OCCSP administration for 2025 and subsequent program years, are consistent with administration of OCCSP in recent years, as announced in previous NOFAs.</P>
                <P>
                    The terms “producer”, “handler”, and “program year” are used throughout this rule. “Producer” and “handler” have the same meaning as used in the NOP regulations at 7 CFR 205.2. “Producer” means “a person who engages in the 
                    <PRTPAGE P="40860"/>
                    business of growing or producing food, fiber, feed, and other agricultural-based consumer products,” and “handler” means “any person that handles agricultural products, except final retailers of agricultural products that do not process agricultural products.” The program year for OCCSP is the fiscal year beginning on October 1 of the preceding calendar year and ending on September 30 (7 CFR 1417.3). For example, the 2025 program year began on October 1, 2024, and ended on September 30, 2025.
                </P>
                <P>This final rule also uses the term “scopes”, which means the four categories of USDA organic certification (crops, livestock, handling, and wild crops) and State organic program fees, as described in section V of this rule and defined in § 1417.3.</P>
                <HD SOURCE="HD1">II. Available Funding</HD>
                <P>Funding for OCCSP is provided through two authorizations. Agricultural Management Assistance (AMA) funding is authorized by 7 U.S.C. 1524(b)(4)(C)(ii), which provides that the Commodity Credit Corporation shall use not less than 10 percent of the amounts made available to carry out that subsection per fiscal year to provide organic certification cost share assistance for producers in the following 16 States: Connecticut, Delaware, Hawaii, Maryland, Massachusetts, Maine, Nevada, New Hampshire, New Jersey, New York, Pennsylvania, Rhode Island, Utah, Vermont, West Virginia, and Wyoming. AMA funds are used for only the scopes of crops, wild crops, and livestock because the authorizing law specifies that those funds will be used to provide assistance to producers (7 U.S.C. 1524(b)(1)). AMA funding that is not obligated during the fiscal year for which it is provided cannot be used for future years.</P>
                <P>National funding is authorized by 7 U.S.C. 6523(d)(1)(C), which directs the Secretary to make available $8 million in CCC funding for each of fiscal years 2022 through 2031 for OCCSP, to remain available until expended. Approximately $1,945,000 in National funding is still available from prior years that has not been expended and can be used for any future years. National funding is used to assist certified producers and handlers in all States (including States with AMA funding), U.S. territories, and the District of Columbia. National OCCSP funds are used to provide cost share for all five scopes (crops, livestock, handling, wild crops, and State organic program fees).</P>
                <P>Both National funding and AMA funding may be used for grants to State agencies and payments through FSA county offices. AMA funding cannot be used for the scopes of handling and State organic program fees; therefore, all cost share for those scopes must be paid with National funding even in AMA-eligible States. AMA-eligible States must submit separate grant applications for AMA funding and National funding to cover all eligible scopes for applicants in their State.</P>
                <HD SOURCE="HD1">III. State Agency Participation</HD>
                <P>
                    To participate in OCCSP, State agencies must complete an Application for Federal Assistance (Standard Form 424 (OMB 4040-0004; Expiration Date: 03/31/2029) and 424B (OMB 4040-0007; Expiration Date: 07/31/2028)) and enter into a grant agreement with CCC (see § 1417.4). State agencies must apply electronically via 
                    <E T="03">Grants.gov</E>
                    , the Federal grants website, at 
                    <E T="03">http://www.grants.gov.</E>
                     For information on how to use 
                    <E T="03">Grants.gov</E>
                    , please consult 
                    <E T="03">https://www.grants.gov/applicants/grant-applications/how-to-apply-for-grants.</E>
                     All grant awards will be subject to the provisions of the applicable Notice of Funding Opportunity (NOFO) and the USDA General Terms and Conditions for Federal Awards in effect at the time the grants are executed.
                </P>
                <P>
                    FSA will soon announce a 30-day application period for state agencies to apply through 
                    <E T="03">Grants.gov</E>
                     to administer OCCSP. Upon receipt of complete applications, CCC may begin reviewing the applications and may make awards prior to the deadline. Applications for grant awards received after the deadline may be considered if CCC determines the delay does not disrupt program administration.
                </P>
                <P>
                    For 2027 and future program years, this funding opportunity will be announced through a press release and on the OCCSP website and 
                    <E T="03">Grants.gov</E>
                    , without a 
                    <E T="04">Federal Register</E>
                     notice. State agencies that wish to participate should make a note of this change and monitor those locations for future announcements.
                </P>
                <HD SOURCE="HD1">IV. Eligible Producers and Handlers</HD>
                <P>To be eligible for OCCSP, a producer or handler must:</P>
                <P>• Possess USDA organic certification under the NOP:</P>
                <FP SOURCE="FP-1">○ For the 2025 program year, at any time during the 2025 program year, or</FP>
                <FP SOURCE="FP-1">○ For 2026 and subsequent program years, at the time of application;</FP>
                <P>• Have paid fees or expenses related to their initial certification or renewal of their certification from a certifying agent; and</P>
                <P>• Be located in the 50 United States, the District of Columbia, the Commonwealth of Puerto Rico, Guam, American Samoa, the U.S. Virgin Islands, and the Commonwealth of the Northern Mariana Islands.</P>
                <P>Producers and handlers with suspended, revoked, or withdrawn certifications at the time of application are ineligible for cost share reimbursement.</P>
                <HD SOURCE="HD1">V. Eligible Scopes</HD>
                <P>Five separate “scopes,” or categories of certification, are covered under OCCSP. Four of these scopes are set forth in the NOP regulations and must be individually inspected and certified: crops, livestock, wild crops, and handling. A single operation may be certified under multiple scopes, which may all be listed on the same certificate. For example, a certified organic vegetable farm that also has certified organic chickens and produces certified organic jams would be required to be certified for three scopes: crops, livestock, and handling. To receive an OCCSP payment for the scopes of crops, handling, livestock, or wild crops, the scope must be listed on the producer or handler's organic certificate.</P>
                <P>State organic program fees may be required by a State that has established a State organic program, which allows the State to oversee organic production and handling operations and assume regulatory enforcement responsibility of the USDA organic regulations for all organic farms and businesses operating within its boundaries (see 7 CFR 205.620 through 205.622). These fees are in addition to the costs of organic certification under the four scopes of USDA organic certification. These State organic program fees are eligible for OCCSP cost share reimbursement and for OCCSP purposes are considered an additional, separate scope.</P>
                <HD SOURCE="HD1">VI. Allowable and Unallowable Costs</HD>
                <P>Allowable costs for OCCSP include only the following:</P>
                <P>• Application fees and administrative fees for USDA organic certification;</P>
                <P>• Inspection fees for USDA organic certification, including travel costs and per diem for organic inspectors;</P>
                <P>• USDA organic certification costs, including fees necessary to access international markets with which AMS has equivalency agreements or arrangements;</P>
                <P>• State organic program fees;</P>
                <P>• User fees and sale assessment fees for USDA organic certification; and</P>
                <P>
                    • Postage for materials related to obtaining or renewing USDA organic certification.
                    <PRTPAGE P="40861"/>
                </P>
                <P>Any costs not listed above are considered unallowable, including, but not limited to, the following examples:</P>
                <P>• Inspections due to violations of USDA organic regulations or violations of State organic program requirements;</P>
                <P>• Costs related to non-USDA organic certifications;</P>
                <P>• Costs related to transitional certification;</P>
                <P>• Costs related to any labeling program other than USDA organic certification;</P>
                <P>• Materials, supplies, and equipment;</P>
                <P>• Late fees and expediting fees;</P>
                <P>• Membership fees; and</P>
                <P>• Consultant fees.</P>
                <P>OCCSP provides cost share for allowable costs based on the program year in which the allowable cost was paid, which may be different than the year in which the cost was incurred. For example, during the 2025 program year (October 1, 2025, through September 30, 2026), a producer paid their application fee and inspection fees. The producer also incurred a sales assessment fee during the 2025 program year but paid it on October 10, 2026. The producer would include the application fee and inspection fees on their 2025 program year application. The sales assessment fee would be included on their 2026 program year application and the producer must meet eligibility requirements for that program year to receive an OCCSP payment.</P>
                <P>If an allowable cost is incurred for more than one scope, the amount will be divided by the number of applicable scopes, and the result will be entered on the application for each applicable scope. For example, a producer received a bill with a single amount of $1,000 for an inspection that covered both crop and livestock scopes. The amount of the inspection would be divided by 2; $500 would be the cost for the crop scope and $500 would be the cost for the livestock scope on the producer's application.</P>
                <HD SOURCE="HD1">VII. How To Apply</HD>
                <P>All eligible producers and handlers can apply for OCCSP through their local FSA county offices. Producers and handlers may apply with either the State agency or an FSA county office in States where a State agency participates in OCCSP; however, applicants may not receive OCCSP payments for the same scope through both the State agency and their FSA county office. Producers and handlers are subject to the same eligibility criteria and calculation of cost share payments regardless of whether they apply through a participating State agency or an FSA county office.</P>
                <HD SOURCE="HD2">A. Applying Through an FSA County Office</HD>
                <P>To apply for OCCSP through an FSA county office, an applicant must submit the following:</P>
                <P>
                    • Form CCC-884 (OMB 0560-0289; Expiration Date: 04/30/2029), Organic Certification Cost Share Program (OCCSP) Application, available online at 
                    <E T="03">https://www.fsa.usda.gov/programs-and-services/occsp</E>
                     or at any FSA county office;
                </P>
                <P>• Proof of USDA organic certification;</P>
                <P>• Itemized invoices showing allowable certification costs paid to a third-party certifying agency or State organic program during the program year for which the application is submitted; and</P>
                <P>• Form AD-2047 (OMB 0560-0265; Expiration Date: 01/31/2027), if not previously filed with FSA.</P>
                <P>Applicants may be required to provide additional documentation, if necessary, to verify eligibility or issue a payment. FSA may contact an applicant's certifying agent to verify the information provided by an applicant.</P>
                <P>
                    Applications may be submitted in person, electronically, or by mail or FAX. FSA county offices are currently accepting OCCSP applications for the 2025 and 2026 program years. The beginning of the application period for 2027 and future program years will be announced through a press release and on the OCCSP website at 
                    <E T="03">https://www.fsa.usda.gov/resources/income-support/organic-certification-cost-share-program-occsp.</E>
                </P>
                <P>For 2026 and future program years the deadline to submit CCC-884 and other required documents is December 31 following the end of the program year. For example, the 2026 program year ends on September 30, 2026, and an applicant must apply for cost share for allowable costs paid between October 1, 2025, through September 30, 2026, by December 31, 2026. Due to the delay in the authorization of funds, the application period for the 2025 program year will run concurrently with program year 2026, and the deadline is December 31, 2026.</P>
                <P>In some instances, a producer or handler may pay allowable costs during a program year but not receive their initial organic certification until after the deadline for the program year. In those instances, an exception to the December 31 deadline applies and the producer or handler must submit all required documents to their FSA county office within 30 days after receiving their certification, subject to the availability of funding. This exception does not apply to applications submitted to participating State agencies.</P>
                <P>CCC and State agencies will stop issuing payments for a program year if available funding is expended, regardless of when an application is filed.</P>
                <HD SOURCE="HD2">B. Applying Through a Participating State Agency</HD>
                <P>
                    Participating State agencies will establish their own application process and deadlines for producers and handlers, subject to the terms of their grant agreements. State agencies should refer to the NOFO on 
                    <E T="03">Grants.gov</E>
                     for additional details on application and deadline requirements. CCC will provide a list of participating State agencies, updated as their grants are finalized, at 
                    <E T="03">https://www.fsa.usda.gov/programs-and-services/occsp.</E>
                </P>
                <HD SOURCE="HD1">VIII. Payments</HD>
                <P>OCCSP payments are equal to the lesser of the following for each scope per program year:</P>
                <P>• the applicable reimbursement percentage, not to exceed 75 percent, multiplied by a producer's or handler's allowable costs; or</P>
                <P>• the maximum payment amount, not to exceed $750 per scope.</P>
                <P>The maximum reimbursement percentage and payment amount are specified in 7 U.S.C. 6523(b). Prior to the beginning of the application period for a program year, CCC will determine the applicable percentage and maximum amount for a program year based on factors such as participation rates in prior years and changes in the number of certified organic operations. If sufficient funding is available to cover expected participation, OCCSP payments will be calculated based on the maximum percentage and payment amount. If available funding is not likely to cover all eligible applicants, CCC may announce a lower percentage and maximum amount to allow a larger number of certified organic operations to receive assistance. For the 2025 and 2026 program years, the reimbursement percentage will be 75 percent, up to a maximum of $750 per scope.</P>
                <P>The percentage and maximum payment amount will be the same regardless of whether a producer or handler applies through an FSA county office or a participating State agency. Cost share assistance will be provided to producers and handlers on a first come, first served basis, until all available funds for a program year are expended. Applications received after all funds are expended will not be paid.</P>
                <P>
                    FSA will coordinate with participating State agencies to ensure 
                    <PRTPAGE P="40862"/>
                    there are no duplicate payments. If a duplicate payment is inadvertently made, then FSA will inform the participant and require that funds be returned to CCC.
                </P>
                <HD SOURCE="HD1">IX. Regulatory Analyses</HD>
                <HD SOURCE="HD2">A. Notice and Comment and Effective Date</HD>
                <P>The Administrative Procedure Act (APA, 5 U.S.C. 553(a)(2)) provides that the notice and comment requirements and 30-day delay in the effective date provisions of that Act do not apply when the rule involves specified actions, including matters relating to loans, grants, benefits, or contracts. This rule governs payments to certified organic producers and handlers and therefore falls within the benefits exemption.</P>
                <P>
                    The Office of Information and Regulatory Affairs has found that this rule does not meet the criteria at 5 U.S.C. 804(2) of the Congressional Review Act (CRA). Moreover, 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. 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. 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,” directed 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). Further, Executive Order 13563 emphasized the importance of quantifying both the costs and benefits of reducing costs, harmonizing rules, and 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 these Executive Order requirements, the Agency has chosen this regulatory approach in order toprovide clarity with respect to program administration and enable CCC to partner with State agencies to facilitate program delivery in a manner that maximizes benefits and minimizes burdens on certified organic producers and handlers. 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) has designated this rule as “not significant” under Executive Order 12866. Accordingly, OMB has not reviewed this rule and an analysis of costs and benefits is not required under either Executive Order 12866 or Executive Order 13563.</P>
                <HD SOURCE="HD2">C. 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>There are no actions under this rule that have the potential to impact the human environment. Accordingly, the actions under this rule are covered by the FSA Categorical Exclusion specified in 7 CFR 1b.4(c)(16)(vii), financial assistance to supplement income, that applies to OCCCP.</P>
                <P>No Extraordinary Circumstances (§ 1b.3(f)) exist because this is an administrative payment program. OCCSP does not constitute a major Federal action that would significantly affect the quality of the human environment, individually or cumulatively. Therefore, CCC 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">D. 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>CCC has assessed the impact of this rule on Indian Tribes and determined that this rule does not, to our knowledge, have Tribal implications that require Tribal consultation at this time. If a Tribe requests consultation in the future, FSA will work with the Office of Tribal Relations to ensure meaningful consultation is provided.</P>
                <HD SOURCE="HD2">E. 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">F. Paperwork Reduction Act Requirements</HD>
                <P>
                    There are no changes to the information collection request for OCCSP that has been approved by the Office of Management and Budget (OMB) under the Paperwork Reduction Act. The OMB control number for the approval is 0560-0289; Expiration Date: 04/30/2029.
                    <PRTPAGE P="40863"/>
                </P>
                <HD SOURCE="HD2">G. E-Government Act Compliance</HD>
                <P>CCC 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="HD2">Federal Assistance Programs</HD>
                <P>The title and number of the Federal assistance program, as found in the Assistance Listing, to which this document applies are 10.171—Organic Certification Cost Share Program (OCCSP).</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 7 CFR Part 1417</HD>
                    <P>Agricultural commodities, Agriculture, Animals, Grant programs-agriculture, Livestock, Organically produced products, Plants, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <REGTEXT TITLE="7" PART="1417">
                    <AMDPAR>For the reasons discussed above, Commodity Credit Corporation amends 7 CFR chapter XIV by adding part 1417 to read as follows:</AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 1417—ORGANIC CERTIFICATION COST SHARE PROGRAM</HD>
                        <CONTENTS>
                            <SECHD>Sec.</SECHD>
                            <SECTNO>1417.1</SECTNO>
                            <SUBJECT>Applicability.</SUBJECT>
                            <SECTNO>1417.2</SECTNO>
                            <SUBJECT>Administration.</SUBJECT>
                            <SECTNO>1417.3</SECTNO>
                            <SUBJECT>Definitions.</SUBJECT>
                            <SECTNO>1417.4</SECTNO>
                            <SUBJECT>State agencies.</SUBJECT>
                            <SECTNO>1417.5</SECTNO>
                            <SUBJECT>Eligible producers and handlers.</SUBJECT>
                            <SECTNO>1417.6</SECTNO>
                            <SUBJECT>Eligible scopes.</SUBJECT>
                            <SECTNO>1417.7</SECTNO>
                            <SUBJECT>Allowable and unallowable costs.</SUBJECT>
                            <SECTNO>1417.8</SECTNO>
                            <SUBJECT>How to apply.</SUBJECT>
                            <SECTNO>1417.9</SECTNO>
                            <SUBJECT>Payments.</SUBJECT>
                            <SECTNO>1417.10</SECTNO>
                            <SUBJECT>General provisions.</SUBJECT>
                        </CONTENTS>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>
                                 7 U.S.C. 1524; 7 U.S.C. 6523; and 15 U.S.C 714, 
                                <E T="03">et seq.</E>
                            </P>
                        </AUTH>
                        <SECTION>
                            <SECTNO>§ 1417.1</SECTNO>
                            <SUBJECT>Applicability.</SUBJECT>
                            <P>(a) The regulations in this part specify how the Commodity Credit Corporation will administer the Organic Certification Cost Share Program (OCCSP). OCCSP provides cost share assistance to producers and handlers of agricultural products for the costs of obtaining or maintaining organic certification under the National Organic Program (7 CFR part 205).</P>
                            <P>(b) The regulations in this part are applicable to the 2025 and subsequent program years. The availability of cost share assistance through OCCSP is subject to the availability of funding.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1417.2</SECTNO>
                            <SUBJECT>Administration.</SUBJECT>
                            <P>(a) The regulations in this part will be administered under the general supervision and direction of the Executive Vice President, Commodity Credit Corporation (CCC). In the field, the regulations in this part will be administered by the Farm Service Agency (FSA) State and county committees (referred to as “State committee” and “county committee,” respectively).</P>
                            <P>(b) State executive directors, county executive directors, and State and county committees do not have authority to modify or waive any of the provisions of this part.</P>
                            <P>(c) The State committee may take any action authorized or required by this part to be taken by the county committee that has not been taken by the county committee. The State committee may also:</P>
                            <P>(1) Correct or require a county committee to correct any action taken by the county committee that is not in accordance with 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 delegation in this subpart to a State or county committee precludes 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 a State or county committee.</P>
                            <P>(e) CCC may also carry out OCCSP through grant agreements with State agencies as provided in § 1417.4.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1417.3</SECTNO>
                            <SUBJECT>Definitions.</SUBJECT>
                            <P>The definitions in this section are applicable for all purposes of administering this part. The terms defined in 7 CFR part 205 are also applicable, except where those definitions conflict with the definitions specified in this section. Where there is a conflict or a difference in definitions specified in this subpart and part 205 of this title, the regulations in this part will apply.</P>
                            <P>
                                <E T="03">AMS</E>
                                 means the USDA's Agricultural Marketing Service.
                            </P>
                            <P>
                                <E T="03">AMA funding</E>
                                 means Agricultural Management Assistance funding authorized by 7 U.S.C. 1524(b)(4)(C)(ii) to provide organic certification cost share for producers in the following states: Connecticut, Delaware, Hawaii, Maryland, Massachusetts, Maine, Nevada, New Hampshire, New Jersey, New York, Pennsylvania, Rhode Island, Utah, Vermont, West Virginia, and Wyoming.
                            </P>
                            <P>
                                <E T="03">CCC-884</E>
                                 means Form CCC-884, Organic Certification Cost Share Program (OCCSP) Application.
                            </P>
                            <P>
                                <E T="03">National funding</E>
                                 means the funding authorized by 7 U.S.C. 6523(d)(1)(C) to provide organic certification cost share for producers and handlers in all States, U.S. territories, and the District of Columbia.
                            </P>
                            <P>
                                <E T="03">Program year</E>
                                 means the fiscal year beginning on October 1 of the preceding calendar year and ending on September 30.
                            </P>
                            <P>
                                <E T="03">State agency</E>
                                 means the agency, commission, or department responsible for agriculture under its jurisdiction in each of the 50 States, the District of Columbia, the Commonwealth of Puerto Rico, the United States Virgin Islands, Guam, American Samoa, and the Commonwealth of the Northern Marina Islands.
                            </P>
                            <P>
                                <E T="03">Scope</E>
                                 means the category of certification (that is, crops, livestock, wild crops, handling, or State organic program fees).
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1417.4</SECTNO>
                            <SUBJECT>State agencies.</SUBJECT>
                            <P>(a) To administer OCCSP, a State agency must apply for and receive a grant award to administer OCCSP. All grant awards will be subject to the provisions of the applicable Notice of Funding Opportunity and the USDA General Terms and Conditions for Federal Awards in effect at the time the grants are executed.</P>
                            <P>
                                (b) To apply to administer OCCSP, a State agency must submit an Application for Federal Assistance (Standard Form 424 and 424B) electronically via 
                                <E T="03">Grants.gov</E>
                                 by the announced deadline for the applicable fiscal year. CCC may consider applications received after the deadline if the delay does not disrupt program administration.
                            </P>
                            <P>(c) All State agencies may apply for a grant award of National funding. State agencies in State that are eligible for AMA funding may receive grant awards for both AMA funding and National funding but must submit a separate application for each grant award.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1417.5</SECTNO>
                            <SUBJECT>Eligible producers and handlers.</SUBJECT>
                            <P>(a) To be eligible for OCCSP, a producer or handler must:</P>
                            <P>(1) Possess a valid USDA organic certification:</P>
                            <P>(i) For the 2025 program year, at any time during the program year; or</P>
                            <P>(ii) For 2026 and subsequent program years, at the time of application;</P>
                            <P>(2) Have paid allowable expenses, as specified in § 1417.7, for initial organic certification or renewal of organic certification from a certifying agent during the applicable fiscal year; and</P>
                            <P>(3) Be located in the 50 United States, the District of Columbia, the Commonwealth of Puerto Rico, Guam, American Samoa, the U.S. Virgin Islands, or the Commonwealth of the Northern Mariana Islands.</P>
                            <P>
                                (b) Producers and handlers with suspended, revoked, or withdrawn 
                                <PRTPAGE P="40864"/>
                                certifications at the time of application are ineligible for OCCSP.
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1417.6</SECTNO>
                            <SUBJECT>Eligible scopes.</SUBJECT>
                            <P>(a) Applicants may receive OCCSP cost share for the following scopes:</P>
                            <P>(1) Crops;</P>
                            <P>(2) Handling;</P>
                            <P>(3) Livestock;</P>
                            <P>(4) Wild crops; and</P>
                            <P>(5) State organic program fees.</P>
                            <P>(b) To receive OCCSP cost share for the scopes of crops, handling, livestock, or wild crops, the scope must be listed on the producer or handler's organic certificate.</P>
                            <P>(c) National funds may be used to issue OCCSP payments for all scopes listed in paragraph (a) of this section. AMA funds may be used to issue OCCSP payments for only the scopes of crops, wild crops, and livestock.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1417.7</SECTNO>
                            <SUBJECT>Allowable and unallowable costs.</SUBJECT>
                            <P>(a) OCCSP provides cost share for allowable costs that are paid by the eligible producer or handler during a program year. Allowable costs that have not been paid at the time of application are not eligible for OCCSP.</P>
                            <P>(b) Allowable costs for OCCSP include:</P>
                            <P>(1) Application fees and administrative fees for USDA organic certification;</P>
                            <P>(2) Inspection fees for USDA organic certification, including travel costs and per diem for organic inspectors;</P>
                            <P>(3) USDA organic certification costs, including fees necessary to access international markets with which AMS has equivalency agreements or arrangements;</P>
                            <P>(4) State organic program fees;</P>
                            <P>(5) User fees and sale assessments for USDA organic certification; and</P>
                            <P>(6) Postage for materials related to obtaining or renewing USDA organic certification.</P>
                            <P>(c) Any costs not included in paragraph (a) of this section are considered unallowable, including, but not limited to:</P>
                            <P>(1) Inspections due to violations of USDA organic regulations or violations of State organic program requirements;</P>
                            <P>(2) Costs related to non-USDA organic certifications;</P>
                            <P>(3) Costs related to transitional certification;</P>
                            <P>(4) Costs related to any other labeling program;</P>
                            <P>(5) Materials, supplies, and equipment;</P>
                            <P>(6) Late fees and expediting fees;</P>
                            <P>(7) Membership fees; and</P>
                            <P>(8) Consultant fees.</P>
                            <P>(d) If a single allowable cost is incurred for more than one scope, the amount will be divided by the number of applicable scopes, and the result will be entered on the application for each applicable scope.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1417.8</SECTNO>
                            <SUBJECT>How to apply.</SUBJECT>
                            <P>(a) FSA county offices will begin accepting OCCSP applications for a program year on the date announced by CCC. Applications may be submitted in person, electronically, or by mail or FAX.</P>
                            <P>(b) To apply for OCCSP through an FSA county office, a producer or handler must submit all of the following:</P>
                            <P>(1) Form CCC-884, Organic Certification Cost Share Program (OCCSP) Application;</P>
                            <P>(2) USDA organic certificate; and</P>
                            <P>(3) Itemized invoices showing allowable certification costs paid to a third-party certifying agency or State organic program during the program year for which the application is submitted.</P>
                            <P>(c) Applicants may be required to provide additional documentation to FSA if necessary to verify eligibility or issue a payment. FSA may contact an applicant's certifying agent to verify the information provided by an applicant.</P>
                            <P>(d) The deadline to apply through an FSA county office for the 2025 program year is December 31, 2026. For 2026 and future program years, the deadline to submit CCC-884 and other required documents to an FSA county office is December 31 following the end of the program year.</P>
                            <P>(e) If a producer or handler pays allowable costs during a program year but does not receive their initial organic certification until after the OCCSP deadline for that program year, the deadline for the producer or handler to apply through an FSA county office is 30 days after receiving their organic certification, subject to the availability of funding. Applications will not be accepted by participating State agencies after December 31 following the end of the program year.</P>
                            <P>(f) Producers and handlers applying through a participating State agency must follow the application process and deadlines announced by the State agency.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1417.9</SECTNO>
                            <SUBJECT>Payments.</SUBJECT>
                            <P>(a) OCCSP payments are equal to the lesser of the following for each scope:</P>
                            <P>(1) The applicable reimbursement percentage, not to exceed 75 percent, multiplied by a producer's allowable costs; or</P>
                            <P>(2) The maximum payment amount, not to exceed $750 per scope.</P>
                            <P>(b) The applicable reimbursement percentage and maximum payment amount for a program year will be determined and announced by CCC prior to the beginning of the application period.</P>
                            <P>(c) Producers and handlers shall not receive OCCSP payments for the same scope through both a State agency and an FSA county office for the same program year.</P>
                            <P>(d) OCCSP payments shall be provided on a first come, first served basis, until all available funds are expended by CCC or the State agency. Applications received after all available funds are expended will not be paid.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1417.10</SECTNO>
                            <SUBJECT>General provisions.</SUBJECT>
                            <P>(a) All information provided to FSA for program eligibility and payment calculation purposes is subject to spot check. Participants are required to retain documentation in support of their application for 3 years after the date of approval. Participants receiving OCCSP payments or any other person who furnishes such information to the U.S. Department of Agriculture (USDA) must permit authorized representatives of USDA or the Government Accountability Office, during regular business hours, to enter the operation and to inspect, examine, and allow representatives to make copies of books, records, or other items for the purpose of confirming the accuracy of the information provided by the participant.</P>
                            <P>(b) If an OCCSP payment resulted from erroneous information provided by a participant, or any person acting on their behalf, the payment will be recalculated and the participant must refund any excess payment to FSA with interest calculated from the date of the disbursement of the payment. If FSA determines that the applicant intentionally misrepresented information included on their application, the application will be disapproved and the applicant must refund the full payment to FSA with interest from the date of disbursement.</P>
                            <P>(c) Any payment under this subpart will be made without regard to questions of title under State law and without regard to any claim or lien. The regulations governing offsets in 7 CFR part 3 apply to OCCSP payments.</P>
                            <P>
                                (d) In either applying for or participating in OCCSP, or both, the applicant is subject to laws against perjury (including, but not limited to, 18 U.S.C. 1621). If the applicant willfully makes and represents as true any verbal or written declaration, certification, statement, or verification that the applicant knows or believes not to be true, in the course of either applying for or participating in OCCSP, or both, then the applicant may be found to be guilty 
                                <PRTPAGE P="40865"/>
                                of perjury. Except as otherwise provided by law, if guilty of perjury the applicant may be fined, imprisoned for not more than 5 years, or both, regardless of whether the applicant makes such verbal or written declaration, certification, statement, or verification within or outside the United States.
                            </P>
                            <P>(e) For the purposes of the effect of a lien on eligibility for Federal programs (28 U.S.C. 3201(e)), USDA waives the restriction on receipt of funds under this subpart but only as to beneficiaries who, as a condition of the waiver, agree to apply OCCSP payments to reduce the amount of the judgment lien.</P>
                            <P>(f) In addition to any other Federal laws that apply to OCCSP, the following laws apply: 18 U.S.C. 286, 287, 371, and 1001.</P>
                            <P>(g) Sequestration will apply to the total amount of funding available for OCCSP if required by law.</P>
                        </SECTION>
                    </PART>
                </REGTEXT>
                <SIG>
                    <NAME>William Beam,</NAME>
                    <TITLE>Executive Vice President, Commodity Credit Corporation.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13571 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3411-E2-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. FAA-2026-3482; Project Identifier MCAI-2025-01288-R; Amendment 39-23390; AD 2026-13-08]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; Airbus Helicopters</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The FAA is adopting a new airworthiness directive (AD) for certain Airbus Helicopters Model H160-B helicopters. This AD was prompted by reports of missing retaining rings on the hinge pins installed on the jettisonable window systems. This AD requires inspecting for missing retaining rings on all the hinge pins installed on the jettisonable window systems and, depending on findings, installing retaining rings found missing. The FAA is issuing this AD to address the unsafe condition on these products.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This AD is effective August 10, 2026. The Director of the Federal Register approved the incorporation by reference of a certain publication listed in this AD as of August 10, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P/>
                    <P>
                        <E T="03">AD Docket:</E>
                         You may examine the AD docket at 
                        <E T="03">regulations.gov</E>
                         under Docket No. FAA-2026-3482; or in person at Docket Operations between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains this final rule, the mandatory continuing airworthiness information (MCAI), any comments received, and other information. The address for Docket Operations is U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE, Washington, DC 20590.
                    </P>
                    <P>
                        <E T="03">Material Incorporated by Reference:</E>
                    </P>
                    <P>
                        • For European Union Aviation Safety Agency (EASA) material identified in this AD, contact EASA, Konrad-Adenauer-Ufer 3, 50668 Cologne, Germany; phone: +49 221 8999 000; email: 
                        <E T="03">ADs@easa.europa.eu;</E>
                         website: 
                        <E T="03">easa.europa.eu.</E>
                         You may find this material on the EASA website at 
                        <E T="03">ad.easa.europa.eu.</E>
                    </P>
                    <P>
                        • You may view this material at the FAA, Airworthiness Products Section, Operational Safety Branch, 10101 Hillwood Parkway, Fort Worth, TX 76177. For information on the availability of this material at the FAA, call (817) 222-5110. It is also available at 
                        <E T="03">regulations.gov</E>
                         under Docket No. FAA-2026-3482.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Aryanna Sanchez, Aviation Safety Engineer, FAA, 1600 Stewart Avenue, Suite 410, Westbury, NY 11590; phone: (520) 990-9321; email: 
                        <E T="03">aryanna.t.sanchez@faa.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    The FAA issued a notice of proposed rulemaking (NPRM) to amend 14 CFR part 39 by adding an AD that would apply to certain Airbus Helicopters Model H160-B helicopters. The NPRM was published in the 
                    <E T="04">Federal Register</E>
                     on April 13, 2026 (91 FR 18790). The NPRM was prompted by EASA AD 2025-0161, dated July 29, 2025 (EASA AD 2025-0161) (also referred to as the MCAI), issued by EASA, which is the Technical Agent for the Member States of the European Union. The MCAI states that reports were received of missing retaining rings on some of the hinge pins installed on the jettisonable window systems. Subsequent investigation revealed that these missing retaining rings had not been installed in production. This condition, if not addressed, could prevent a window from jettisoning, which could affect the evacuation of occupants during an emergency.
                </P>
                <P>In the NPRM, the FAA proposed to require inspecting for missing retaining rings on all the hinge pins installed on the jettisonable window systems and, depending on findings, installing retaining rings found missing.</P>
                <P>
                    You may examine the MCAI in the AD docket at 
                    <E T="03">regulations.gov</E>
                     under Docket No. FAA-2026-3482.
                </P>
                <HD SOURCE="HD1">Discussion of Final Airworthiness Directive</HD>
                <HD SOURCE="HD1">Comments</HD>
                <P>The FAA received no comments on the NPRM or on the determination of the costs.</P>
                <HD SOURCE="HD1">Conclusion</HD>
                <P>These products have been approved by the civil aviation authority of another country and are approved for operation in the United States. Pursuant to the FAA's bilateral agreement with this State of Design Authority, that authority has notified the FAA of the unsafe condition described in the MCAI referenced above. The FAA reviewed the relevant data, considered any comments received, and determined that air safety requires adopting this AD as proposed. Accordingly, the FAA is issuing this AD to address the unsafe condition on these products. Except for minor editorial changes, this AD is adopted as proposed in the NPRM. None of the changes will increase the economic burden on any operator.</P>
                <HD SOURCE="HD1">Material Incorporated by Reference Under 1 CFR Part 51</HD>
                <P>The FAA reviewed EASA AD 2025-0161, which specifies procedures for inspecting for missing retaining rings on all the hinge pins installed on the jettisonable window systems and, if any retaining ring is found missing, installing a retaining ring at that position.</P>
                <P>
                    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">Costs of Compliance</HD>
                <P>The FAA estimates that this AD affects 12 helicopters of the U.S. registry.</P>
                <P>
                    The FAA estimates the following costs to comply with this AD.
                    <PRTPAGE P="40866"/>
                </P>
                <GPOTABLE COLS="5" OPTS="L2,nj,i1" CDEF="s50,r50,12C,12C,12C">
                    <TTITLE>Estimated Costs</TTITLE>
                    <BOXHD>
                        <CHED H="1">Action</CHED>
                        <CHED H="1">
                            Labor
                            <LI>cost</LI>
                        </CHED>
                        <CHED H="1">
                            Parts
                            <LI>cost</LI>
                        </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">Inspect for missing retaining rings</ENT>
                        <ENT>2 work-hours × $85 per hour = $170 (108 rings per helicopter)</ENT>
                        <ENT>$0</ENT>
                        <ENT>$170</ENT>
                        <ENT>$2,040</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The number of retaining rings found missing as a result of the inspection could vary from helicopter to helicopter. Installing a retaining ring costs $50 per ring and requires a minimal amount of time. The FAA has no way of determining the number of helicopters that may require installing missing retaining rings.</P>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. Subtitle VII: Aviation Programs, describes in more detail the scope of the Agency's authority.</P>
                <P>The FAA is issuing this rulemaking under the authority described in Subtitle VII, Part A, Subpart III, Section 44701: General requirements. Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action.</P>
                <HD SOURCE="HD1">Regulatory Findings</HD>
                <P>This AD will not have federalism implications under Executive Order 13132. This AD will not have a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
                <P>For the reasons discussed above, I certify that this AD:</P>
                <P>(1) Is not a “significant regulatory action” under Executive Order 12866,</P>
                <P>(2) Will not affect intrastate aviation in Alaska, and</P>
                <P>(3) Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Amendment</HD>
                <P>Accordingly, under the authority delegated to me by the Administrator, the FAA amends 14 CFR part 39 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
                </PART>
                <REGTEXT TITLE="14" PART="39">
                    <AMDPAR>1. The authority citation for part 39 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 49 U.S.C. 106(g), 40113, 44701.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 39.13</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="14" PART="39">
                    <AMDPAR>2. The FAA amends § 39.13 by adding the following new airworthiness directive:</AMDPAR>
                    <P>
                        <E T="04">2026-13-08 Airbus Helicopters:</E>
                         Amendment 39-23390; Docket No. FAA-2026-3482; Project Identifier MCAI-2025-01288-R.
                    </P>
                    <HD SOURCE="HD1">(a) Effective Date</HD>
                    <P>This airworthiness directive (AD) is effective August 10, 2026.</P>
                    <HD SOURCE="HD1">(b) Affected ADs</HD>
                    <P>None.</P>
                    <HD SOURCE="HD1">(c) Applicability</HD>
                    <P>This AD applies to Airbus Helicopters Model H160-B helicopters, certificated in any category, as identified in European Union Aviation Safety Agency AD 2025-0161, dated July 29, 2025 (EASA AD 2025-0161).</P>
                    <HD SOURCE="HD1">(d) Subject</HD>
                    <P>Joint Aircraft System Component (JASC) Code 2500, Cabin equipment/furnishings.</P>
                    <HD SOURCE="HD1">(e) Unsafe Condition</HD>
                    <P>This AD was prompted by reports of missing retaining rings on hinge pins installed on the jettisonable window systems. The FAA is issuing this AD to detect and address missing retaining rings. The unsafe condition, if not addressed, could prevent a window from jettisoning, which could affect the evacuation of occupants during an emergency.</P>
                    <HD SOURCE="HD1">(f) Compliance</HD>
                    <P>Comply with this AD within the compliance times specified, unless already done.</P>
                    <HD SOURCE="HD1">(g) Required Actions</HD>
                    <P>Except as specified in paragraphs (h) and (i) of this AD: Comply with all required actions and compliance times specified in, and in accordance with EASA AD 2025-0161.</P>
                    <HD SOURCE="HD1">(h) Exceptions to EASA AD 2025-0161</HD>
                    <P>(1) Where EASA AD 2025-0161 refers to its effective date, this AD requires using the effective date of this AD.</P>
                    <P>(2) Where EASA AD 2025-0161 defines “affected parts”, this AD requires replacing that definition with “Jettisonable window system elements identified as `Components affected' and listed by part number (P/N) and manufacturer P/N in section `Applicability' of Airbus Helicopters Alert Service Bulletin ASB H160-52-20-0002, Issue 001, dated June 25, 2025, or having a P/N or manufacturer P/N that cannot be identified”.</P>
                    <P>(3) This AD does not adopt the “Remarks” section of EASA AD 2025-0161.</P>
                    <HD SOURCE="HD1">(i) No Reporting Requirement</HD>
                    <P>Although the material referenced in EASA AD 2025-0161 specifies to submit certain information to the manufacturer, this AD does not require that action.</P>
                    <HD SOURCE="HD1">(j) Alternative Methods of Compliance (AMOCs)</HD>
                    <P>
                        (1) The Manager, International Validation Branch, FAA, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. In accordance with 14 CFR 39.19, send your request to your principal inspector or local flight standards district office, as appropriate. If sending information directly to the manager of the International Validation Branch, send it to the attention of the person identified in paragraph (k) of this AD and email to: 
                        <E T="03">AMOC@faa.gov.</E>
                    </P>
                    <P>
                        (2) Before using any approved AMOC, notify your appropriate principal inspector, or lacking a principal inspector, the manager of the local flight standards district office/certificate holding district office.
                        <PRTPAGE P="40867"/>
                    </P>
                    <HD SOURCE="HD1">(k) Additional Information</HD>
                    <P>
                        For more information about this AD, contact Aryanna Sanchez, Aviation Safety Engineer, FAA, 1600 Stewart Avenue, Suite 410, Westbury, NY 11590; phone: (520) 990-9321; email: 
                        <E T="03">aryanna.t.sanchez@faa.gov.</E>
                    </P>
                    <HD SOURCE="HD1">(l) 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) European Union Aviation Safety Agency (EASA) AD 2025-0161, dated July 29, 2025.</P>
                    <P>(ii) [Reserved]</P>
                    <P>
                        (3) For EASA material identified in this AD, contact EASA, Konrad-Adenauer-Ufer 3, 50668 Cologne, Germany; phone: +49 221 8999 000; email: 
                        <E T="03">ADs@easa.europa.eu;</E>
                         website: 
                        <E T="03">easa.europa.eu.</E>
                         You may find the EASA material on the EASA website at 
                        <E T="03">ad.easa.europa.eu.</E>
                    </P>
                    <P>(4) You may view this material at the FAA, Airworthiness Products Section, Operational Safety Branch, 10101 Hillwood Parkway, Fort Worth, TX 76177. For information on the availability of this material at the FAA, call (817) 222-5110.</P>
                    <P>
                        (5) You may view this material at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, visit 
                        <E T="03">www.archives.gov/federal-register/cfr/ibr-locations</E>
                         or email 
                        <E T="03">fr.inspection@nara.gov.</E>
                    </P>
                </REGTEXT>
                <SIG>
                    <DATED>Issued on June 25, 2026.</DATED>
                    <NAME>Christopher R. Parker,</NAME>
                    <TITLE>Acting Deputy Director, Compliance &amp; Airworthiness Division, Aircraft Certification Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13540 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. FAA-2025-2551; Project Identifier MCAI-2024-00191-R; Amendment 39-23386; AD 2026-13-04]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; Airbus Helicopters</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The FAA is adopting a new airworthiness directive (AD) for all Airbus Helicopters Model H160-B helicopters modified by Supplemental Type Certificate (STC) SR00223IB. This AD was prompted by a report that several self-locking nuts of the window jettisoning system could be loosened by hand due to a non-conformity in the cable kit. This AD requires modifying an affected window into a serviceable window. This AD also prohibits installing an affected window or an affected door on any helicopter modified with STC SR00223IB. The FAA is issuing this AD to address the unsafe condition on these products.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This AD is effective August 10, 2026. The Director of the Federal Register approved the incorporation by reference of a certain publication listed in this AD as of August 10, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P/>
                    <P>
                        <E T="03">AD Docket:</E>
                         You may examine the AD docket at 
                        <E T="03">regulations.gov</E>
                         under Docket No. FAA-2025-2551; or in person at Docket Operations between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains this final rule, the mandatory continuing airworthiness information (MCAI), any comments received, and other information. The address for Docket Operations is U.S. Department of Transportation, Docket Operations, M-91, West Building Fifth Floor, Room W58-213, 1200 New Jersey Avenue SE, Washington, DC 20590.
                    </P>
                    <P>
                        <E T="03">Material Incorporated by Reference:</E>
                    </P>
                    <P>
                        • For European Union Aviation Safety Agency (EASA) material identified in this AD, contact EASA, Konrad-Adenauer-Ufer 3, 50668 Cologne, Germany; phone: +49 221 8999 000; email: 
                        <E T="03">ADs@easa.europa.eu;</E>
                         website: 
                        <E T="03">easa.europa.eu.</E>
                         You may find the EASA material on the EASA website at 
                        <E T="03">ad.easa.europa.eu.</E>
                    </P>
                    <P>
                        • You may view this material at the FAA, Airworthiness Products Section, Operational Safety Branch, 10101 Hillwood Parkway, Fort Worth, TX 76177. For information on the availability of this material at the FAA, call (817) 222-5110. It is also available at 
                        <E T="03">regulations.gov</E>
                         under Docket No. FAA-2025-2551.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Eric Rivera, Aviation Safety Engineer, FAA, 1600 Stewart Avenue, Suite 410, Westbury, NY 11590; phone: (773) 412-9048; email: 
                        <E T="03">eric.rivera01@faa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    The FAA issued a notice of proposed rulemaking (NPRM) to amend 14 CFR part 39 by adding an AD that would apply to all Airbus Helicopters Model H160-B helicopters modified by STC SR00223IB. The NPRM was published in the 
                    <E T="04">Federal Register</E>
                     on September 22, 2025 (90 FR 45338). The NPRM was prompted by EASA AD 2024-0075, dated March 18, 2024 (EASA AD 2024-0075) (also referred to as the MCAI), issued by EASA, which is the Technical Agent for the Member States of the European Union. The MCAI states that during a maintenance operation, several self-locking nuts of the window jettisoning system could be loosened by hand. The MCAI further states that the function of these nuts is to hold the threaded axis and the associated cable tigh, as part of the passenger windows' jettisoning system mechanism. The MCAI also states that certain cable kits which are part of the window jettisoning system might not be in conformance with applicable specifications. Since FAA STC SR00223IB has the same specifications as EASA STC 10080809, it was determined that helicopters modified by FAA STC SR00223IB would have the same unsafe condition.
                </P>
                <P>In the NPRM, the FAA proposed to require modifying an affected window into a serviceable window. This AD also prohibits installing an affected window or an affected door on any helicopter modified with STC SR00223IB. The FAA is issuing this AD to prevent failure of the jettisoning function of the window. The unsafe condition, if not addressed, could result in the inability to evacuate helicopter occupants during an emergency situation.</P>
                <P>
                    You may examine the MCAI in the AD docket at 
                    <E T="03">regulations.gov</E>
                     under Docket No. FAA-2025-2551.
                </P>
                <HD SOURCE="HD1">Discussion of Final Airworthiness Directive</HD>
                <HD SOURCE="HD1">Comments</HD>
                <P>The FAA received comments from the Citizens Rulemaking Alliance. The following presents the comments received on the NPRM and the FAA's response to each comment.</P>
                <HD SOURCE="HD1">Request To Issue an NPRM or Justify Forgoing Notice and Comment or Delay Effective Date for Non-Immediate Tasks</HD>
                <P>
                    The Citizens Rulemaking Alliance requested that the FAA either retain necessary “before further flight” and short-interval inspection/mitigation requirements in the immediately adopted rule and republish any longer-term replacement, configuration changes, or recurring actions with longer compliance times as an NPRM with a 30 to 60-day comment period. 
                    <PRTPAGE P="40868"/>
                    Alternatively, the commenter suggested the FAA publish an interim final rule limited to immediate mitigations and a parallel NPRM for the longer-term actions. The commenter asserted the FAA has not adequately justified use of the good cause exemption to bypass notice and comment and the 30-day delayed effective date.
                </P>
                <P>
                    The FAA notes the comment was submitted in response to an NPRM for which the FAA provided a 45-day comment period. This final rule is effective 35 days after its publication in the 
                    <E T="04">Federal Register</E>
                    . Therefore, the FAA did not change this AD as a result of this comment.
                </P>
                <HD SOURCE="HD1">Request To Comply With the Paperwork Reduction Act (PRA)</HD>
                <P>The Citizens Rulemaking Alliance requested that the FAA revise the proposed AD to comply with the PRA if reporting is required or remove any mandatory reporting provisions or suspend enforcement until PRA requirements are satisfied. If reporting is not required, the commenter requested the FAA clarify that in the AD.</P>
                <P>The FAA notes that paragraph (i) of this AD specifies that this AD does not require reporting. If an AD were to require reporting, the preamble of the AD would include a paragraph titled “Paperwork Reduction Act” that would provide the applicable OMB control number, required PRA statements, and the estimated time to collect the required information (burden). Any costs associated with the reporting requirement would be included in the Costs of Compliance section in the preamble of the AD. Therefore, the FAA did not change this AD as a result of this comment.</P>
                <HD SOURCE="HD1">Request To Make Incorporation by Reference (IBR) Materials Reasonably Available</HD>
                <P>The Citizens Rulemaking Alliance stated that the FAA's current practices for IBR frequently fail to meet the legal and regulatory standards for reasonable availability. The commenter called on the FAA to guarantee that all IBR materials are easily and freely accessible to the public and affected parties for both commenting and compliance purposes and to confirm that the AD does not incorporate later revisions or materials that incorporate other unavailable documents.</P>
                <P>
                    The FAA clarifies that this AD incorporates by reference EASA AD 2024-0075, not the manufacturer service information referenced in that EASA AD. The FAA posted EASA AD 2024-0075 to the AD docket when the NPRM was published in the 
                    <E T="04">Federal Register</E>
                    . The material referenced in EASA AD 2024-0075 may only be posted before the final rule's publication if it is already publicly available or if there is written consent from the owner of that material. Additionally, the FAA provided notice in the NPRM that the material referenced in EASA AD 2024-0075 will be available in the AD docket after this AD is published.
                </P>
                <P>1 CFR part 51 requires that the specific version of the material to be incorporated by reference be specifically identified and formally approved for IBR by the Office of the Federal Register. Once a document is incorporated by reference with a specific date/revision, that exact version becomes the regulatory requirement. This AD does allow, but does not mandate the use of later-approved revisions of the material referenced in EASA AD 2024-0075 as acceptable for compliance with the required actions. This AD adopts the “Ref. Publications” section of EASA AD 2024-0075, which includes the current version of the referenced material as well as later approved revisions. Referring to EASA AD 2024-0075 instead of a service bulletin minimizes the need for alternative methods of compliance.</P>
                <P>Therefore, the FAA did not change this AD as a result of this comment.</P>
                <HD SOURCE="HD1">Request To Consider Impact on Small Entities</HD>
                <P>The Citizens Rulemaking Alliance requested that the FAA prepare an initial regulatory flexibility analysis that takes into account parts, labor, aircraft downtime, and specific small entity impacts. Additionally, the commenter requested that the FAA adopt less burdensome alternatives for small operators, such as explicit alternative method of compliance (AMOC) alternatives, temporary ferry flight allowances, and flexible compliance intervals.</P>
                <P>The FAA has considered the AD's impact on small entities and provides the following factual basis for its Regulatory Flexibility Act (RFA) certification.</P>
                <P>The Regulatory Flexibility Act of 1980, Public Law 96-354, 94 Stat. 1164 (5 U.S.C. 601-612), as amended by the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121, 110 Stat. 857, Mar. 29, 1996) and the Small Business Jobs Act of 2010 (Pub. L. 111-240, 124 Stat. 2504, Sept. 27, 2010), requires Federal agencies to consider the effects of the regulatory action on small business and other small entities and to minimize any significant economic impact. The term “small entities” comprises small businesses and not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000.</P>
                <P>The FAA identified one pharmaceutical preparation manufacturer and one nonscheduled air transportation operator that will be affected by this AD. Based on the Small Business Administration (SBA) size standard (displayed in the table below), both entities are large businesses.</P>
                <P/>
                <GPOTABLE COLS="3" OPTS="L2,nj,i1" CDEF="xs60,r100,r35">
                    <TTITLE>
                        Small Business Size Standards 
                        <SU>1</SU>
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">
                            NAICS 
                            <SU>2</SU>
                            <LI>code</LI>
                        </CHED>
                        <CHED H="1">Description</CHED>
                        <CHED H="1">
                            Size
                            <LI>standard</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">325412</ENT>
                        <ENT>Pharmaceutical Preparation Manufacturing</ENT>
                        <ENT>1,300 employees.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">481219</ENT>
                        <ENT>Other Nonscheduled Air Transportation</ENT>
                        <ENT>$25.0 million.</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>1</SU>
                         Sources: 
                        <E T="03">sba.gov:</E>
                         Table of Small Business Size Standards. Dun &amp; Bradstreet; D&amp;B Hoovers; Retrieved April 29, 2026; 
                        <E T="03">app.hoovers.dnb.com.</E>
                    </TNOTE>
                    <TNOTE>
                        <SU>2</SU>
                         NAICS = North American Industrial Classification System.
                    </TNOTE>
                </GPOTABLE>
                <P>If an agency determines that a rulemaking action will not result in a significant economic impact on a substantial number of small entities, the head of the agency may certify under section 605(b) of the RFA. Therefore, as provided in section 605(b) and based on the foregoing, the head of the FAA certifies that this AD will not result in a significant economic impact on a substantial number of small entities. The FAA did not change this AD as a result of this comment.</P>
                <HD SOURCE="HD1">Conclusion</HD>
                <P>
                    These products have been approved by the civil aviation authority of another 
                    <PRTPAGE P="40869"/>
                    country and are approved for operation in the United States. Pursuant to the FAA's bilateral agreement with this State of Design Authority, that authority has notified the FAA of the unsafe condition described in the MCAI referenced above. The FAA reviewed the relevant data, considered any comments received, and determined that air safety requires adopting this AD as proposed. Accordingly, the FAA is issuing this AD to address the unsafe condition on these products. Except for minor editorial changes, a correction to the revision level of Vision Systems Vendor Service Bulletin No. 02-050-015 from Revision 10 to Revision 0, a change in the Costs of Compliance section (from 11 helicopters to 10 helicopters and corresponding cost changes), and any other changes described previously, this AD is adopted as proposed in the NPRM. None of the changes will increase the economic burden on any operator.
                </P>
                <HD SOURCE="HD1">Material Incorporated by Reference Under 1 CFR Part 51</HD>
                <P>
                    The FAA reviewed EASA AD 2024-0075, which specifies procedures for replacing each affected passenger window with a serviceable window or modifying an affected window into a serviceable window, which consists of removing and installing a certain part-numbered cable kit. EASA AD 2024-0075 also prohibits installing an affected window or an affected door on any helicopter. 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">Differences Between This AD and the MCAI</HD>
                <P>The MCAI applies to Airbus Helicopters Model H160 B helicopters, all serial numbers, if modified by EASA STC 10080809 original issue or Revision 1, whereas this AD applies to Airbus Helicopters Model H160-B helicopters modified by FAA STC SR00223IB, having a date of issuance of the original airworthiness certificate or date of issuance of the original export certificate of airworthiness on or before October 3, 2024.</P>
                <HD SOURCE="HD1">Costs of Compliance</HD>
                <P>The FAA estimates that this AD affects 10 helicopters of U.S. registry. The FAA estimates the following costs to comply with this AD.</P>
                <GPOTABLE COLS="5" OPTS="L2,nj,i1" CDEF="s50,r50,12,12,12">
                    <TTITLE>Estimated Costs</TTITLE>
                    <BOXHD>
                        <CHED H="1">Action</CHED>
                        <CHED H="1">
                            Labor
                            <LI>cost</LI>
                        </CHED>
                        <CHED H="1">
                            Parts
                            <LI>cost</LI>
                        </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">Modify windows (4 per helicopter)</ENT>
                        <ENT>13 work-hours × $85 per hour = $1,105</ENT>
                        <ENT>$3,132</ENT>
                        <ENT>$4,237</ENT>
                        <ENT>$42,370</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The FAA has included all known costs in its cost estimate. According to the manufacturer, however, some of the costs of this AD may be covered under warranty, thereby reducing the cost impact on affected operators.</P>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. Subtitle VII: Aviation Programs, describes in more detail the scope of the Agency's authority.</P>
                <P>The FAA is issuing this rulemaking under the authority described in Subtitle VII, Part A, Subpart III, Section 44701: General requirements. Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action.</P>
                <HD SOURCE="HD1">Regulatory Findings</HD>
                <P>This AD will not have federalism implications under Executive Order 13132. This AD will not have a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
                <P>For the reasons discussed above, I certify that this AD:</P>
                <P>(1) Is not a “significant regulatory action” under Executive Order 12866,</P>
                <P>(2) Will not affect intrastate aviation in Alaska, and</P>
                <P>(3) Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Amendment</HD>
                <P>Accordingly, under the authority delegated to me by the Administrator, the FAA amends 14 CFR part 39 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
                </PART>
                <REGTEXT TITLE="14" PART="39">
                    <AMDPAR>1. The authority citation for part 39 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 49 U.S.C. 106(g), 40113, 44701.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 39.13</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="14" PART="39">
                    <AMDPAR>2. The FAA amends § 39.13 by adding the following new airworthiness directive:</AMDPAR>
                    <EXTRACT>
                        <FP SOURCE="FP-2">
                            <E T="04">2026-13-04 Airbus Helicopters:</E>
                             Amendment 39-23386; Docket No. FAA-2025-2551; Project Identifier MCAI-2024-00191-R.
                        </FP>
                    </EXTRACT>
                    <HD SOURCE="HD1">(a) Effective Date</HD>
                    <P>This airworthiness directive (AD) is effective August 10, 2026.</P>
                    <HD SOURCE="HD1">(b) Affected ADs</HD>
                    <P>None.</P>
                    <HD SOURCE="HD1">(c) Applicability</HD>
                    <P>This AD applies to Airbus Helicopters Model H160-B helicopters, certificated in any category, modified by Supplemental Type Certificate (STC) SR00223IB having a date of issuance of the original airworthiness certificate or date of issuance of the original export certificate of airworthiness on or before October 3, 2024.</P>
                    <HD SOURCE="HD1">(d) Subject</HD>
                    <P>Joint Aircraft System Component (JASC) Code 5630, Door windows.</P>
                    <HD SOURCE="HD1">(e) Unsafe Condition</HD>
                    <P>
                        This AD was prompted by a report that several self-locking nuts of the window jettisoning system could be loosened by hand due to a non-conformity in the cable kit. The FAA is issuing this AD to prevent failure of the jettisoning function of the window. The unsafe condition, if not addressed, could result in the inability to evacuate helicopter occupants during an emergency situation.
                        <PRTPAGE P="40870"/>
                    </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) Requirements</HD>
                    <P>Except as specified in paragraphs (h) and (i) of this AD: Comply with all required actions and compliance times specified in, and in accordance with, European Union Aviation Safety Agency AD 2024-0075, dated March 18, 2024 (EASA AD 2024-0075).</P>
                    <HD SOURCE="HD1">(h) Exceptions to EASA AD 2024-0075</HD>
                    <P>(1) Where EASA AD 2024-0075 refers to its effective date, this AD requires using the effective date of this AD.</P>
                    <P>(2) Where EASA AD 2024-0075 requires compliance in terms of flight hours, this AD requires using hours time-in-service.</P>
                    <P>(3) Where EASA AD 2024-0075 defines “affected passenger window” and refers to “a Part Number as listed in the MSB and an s/n as listed in the vendor SB”, this AD requires replacing that text with “a part number identified in Planning Information, paragraph A.1 Effectivity, and a serial number identified in the Appendix: Applicable serial number, of Vision Systems Vendor Service Bulletin No. 02-050-015, Revision 0, dated January 24, 2024, as applicable”.</P>
                    <P>(4) Where EASA AD 2024-0075 specifies “replace each affected passenger window with a serviceable window”, this AD requires replacing that text with “modify each affected passenger window into a serviceable window”.</P>
                    <P>(5) Where the material referenced in EASA AD 2024-0075 specifies “check”, this AD requires replacing that text with “inspect”.</P>
                    <P>(6) Where the material referenced in EASA AD 2024-0075 specifies “throw away”, this AD requires replacing that text with “remove from service”.</P>
                    <P>(7) Where the material referenced in EASA AD 2024-0075 specifies “respect the screwing order”, this AD requires replacing that text with “follow the screwing order”.</P>
                    <P>(8) Where the material referenced in EASA AD 2024-0075 specifies “screw the nuts”, this AD requires replacing that text with “secure the nuts into place”.</P>
                    <P>(9) Where the material referenced in EASA AD 2024-0075 specifies “fine tuning the pull-up cables in locked position (finger)”, this AD requires replacing that text with “put the pull-up cables into the locked position and make small adjustments to the nuts to ensure cable tension and prevent twisting, coiling, or crossing of cables”.</P>
                    <P>(10) This AD does not adopt the “Remarks” section of EASA AD 2024-0075.</P>
                    <HD SOURCE="HD1">(i) No Reporting Requirement</HD>
                    <P>Although the material referenced in EASA AD 2024-0075 specifies to submit certain information to the manufacturer, this AD does not require that action.</P>
                    <HD SOURCE="HD1">(j) Alternative Methods of Compliance (AMOCs)</HD>
                    <P>
                        (1) The Manager, International Validation Branch, FAA, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. In accordance with 14 CFR 39.19, send your request to your principal inspector or local Flight Standards District Office, as appropriate. If sending information directly to the manager of the International Validation Branch, send it to the attention of the person identified in paragraph (k) of this AD and email to: 
                        <E T="03">AMOC@faa.gov.</E>
                    </P>
                    <P>(2) Before using any approved AMOC, notify your appropriate principal inspector, or lacking a principal inspector, the manager of the local flight standards district office/certificate holding district office.</P>
                    <HD SOURCE="HD1">(k) Additional Information</HD>
                    <P>
                        For more information about this AD, contact Eric Rivera, Aviation Safety Engineer, FAA, 1600 Stewart Avenue, Suite 410, Westbury, NY 11590; phone: (773) 412-9048; email: 
                        <E T="03">eric.rivera01@faa.gov.</E>
                    </P>
                    <HD SOURCE="HD1">(l) 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) European Union Aviation Safety Agency (EASA) AD 2024-0075, dated March 18, 2024.</P>
                    <P>(ii) [Reserved]</P>
                    <P>
                        (3) For EASA material identified in this AD, contact EASA, Konrad-Adenauer-Ufer 3, 50668 Cologne, Germany; phone: +49 221 8999 000; email: 
                        <E T="03">ADs@easa.europa.eu;</E>
                         website: 
                        <E T="03">easa.europa.eu.</E>
                         You may find the EASA material on the EASA website at 
                        <E T="03">ad.easa.europa.eu.</E>
                    </P>
                    <P>(4) You may view this material at the FAA, Airworthiness Products Section, Operational Safety Branch, 10101 Hillwood Parkway, Fort Worth, TX 76177. For information on the availability of this material at the FAA, call (817) 222-5110.</P>
                    <P>
                        (5) You may view this material at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, visit 
                        <E T="03">www.archives.gov/federal-register/cfr/ibr-locations</E>
                         or email 
                        <E T="03">fr.inspection@nara.gov.</E>
                    </P>
                </REGTEXT>
                <SIG>
                    <DATED>Issued on June 18, 2026.</DATED>
                    <NAME>Christopher R. Parker,</NAME>
                    <TITLE>Acting Deputy Director, Compliance &amp; Airworthiness Division, Aircraft Certification Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13538 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 73</CFR>
                <DEPDOC>[Docket No. FAA-2026-7162; Airspace Docket No. 26-ASO-10]</DEPDOC>
                <RIN>RIN 2120-AA66</RIN>
                <SUBJECT>Amendment of Using Agency and Controlling Agency for Restricted Areas R-5301, R-5302A, R-5302B, and R-5302C; NC</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This action amends the using agency and controlling agency descriptions listed for restricted areas R-5301, R-5302A, R-5302B, and R-5302C, NC. This action does not change any boundaries, altitudes, times of designation, or activities conducted within the restricted areas.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective date 0901 UTC, July 9, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        A copy of this final rule and all background material may be viewed online at 
                        <E T="03">www.regulations.gov</E>
                         using the FAA Docket number. Electronic retrieval help and guidelines are available on the website. It is available 24 hours each day, 365 days each year. An electronic copy of this document may also be downloaded from 
                        <E T="03">www.federalregister.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Ashley Toth, Rules and Regulations Group, Policy Directorate, Federal Aviation Administration, 800 Independence Avenue SW, Washington, DC 20591; telephone: (202) 267-8783.</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 
                    <PRTPAGE P="40871"/>
                    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 the 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 updates the using agency and controlling agency listed for restricted areas R-5301, R-5302A, R-5302B, and R-5302C in North Carolina.
                </P>
                <HD SOURCE="HD1">Background</HD>
                <P>The U.S. Marine Corps requested that the Federal Aviation Administration amend the using agency and controlling agency descriptions for restricted areas R-5301, R-5302A, R-5302B, and R-5302C to correct minor discrepancies.</P>
                <HD SOURCE="HD1">The Rule</HD>
                <P>This action amends 14 CFR part 73 by updating the using agency and controlling agency descriptions for restricted areas R-5301, R-5302A, R-5302B, and R-5302C. The using agency for all four restricted areas is updated by removing “U.S Navy, Fleet Area Control and Surveillance Facility, Virginia Capes (FACSFAC VACAPES), Virginia Beach, VA” and replaced with “USMC, Commanding Officer, MCAS Cherry Point, NC.” The controlling agency for restricted area R-5301 is updated by removing “FAA Washington ARTCC” and replacing it with “USMC, MCAS Cherry Point CERAP”. For restricted areas R-5302A, R-5302B, and R-5302C the controlling agency is updated by removing “USMC, Marine Corps Air Station Cherry Point Approach Control” and replacing it with “USMC, MCAS Cherry Point CERAP.”</P>
                <HD SOURCE="HD1">Good Cause for Bypassing Notice and Comment</HD>
                <P>
                    Under 5 U.S.C. 553, federal agencies engaged in informal rulemaking must provide the public with a notice of proposed rulemaking and an opportunity for public participation. However, 5 U.S.C. 553(b)(B) exempts a rule from these requirements “when the agency for good cause finds (and incorporates the finding and a brief statement of reasons therefor in the rules issued) that notice and public procedure thereon are impracticable, unnecessary, or contrary to the public interest.” Courts have construed these exceptions narrowly, but have nonetheless accepted determinations of good cause that notice and comment is unnecessary in “those situations in which the administrative rule is a routine determination, insignificant in nature and impact, and inconsequential to the industry and to the public.” See 
                    <E T="03">Mack Trucks, Inc.</E>
                     v. 
                    <E T="03">EPA,</E>
                     682 F.3d 87, 94 (D.C. Cir. 2012). This action consists of administrative name changes and minor technical amendments only. It does not affect the boundaries, altitudes, time of designation, operating requirements, or activities conducted in the restricted areas. Therefore, FAA has determined that good cause exists to find that notice and public procedure under 5 U.S.C. 553(b) are unnecessary.
                </P>
                <HD SOURCE="HD1">Regulatory Notices and Analyses</HD>
                <P>The FAA has determined that this regulation only involves an established body of technical regulations for which frequent and routine amendments are necessary to keep them operationally current. It, therefore: (1) is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under DOT 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 these amendments are routine and the expected impact to operators is de minimis, the FAA certifies that this rule, when promulgated, does 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>
                    The FAA has determined that this action of making an administrative change to amend the using agency and controlling agency descriptions for restricted areas R5301, R-5302A, R-5302B, and R-5302C, NC, qualifies for categorical exclusion under the National Environmental Policy Act (42 U.S.C. 4321, 
                    <E T="03">et seq.</E>
                    ) and in accordance with FAA Order 1050.1G, 
                    <E T="03">FAA National Environmental Policy Act Implementing Procedures,</E>
                     paragraph B-2.6(d), which categorically excludes from further environmental impact review the issuance of regulatory documents (
                    <E T="03">e.g.,</E>
                     Notices of Proposed Rulemaking and issuance of Final Rules) covering administrative or procedural requirements, and paragraph B-2.5(d), which categorically excludes from further environmental impact review modification of the technical description of special use airspace (SUA) that does not alter the dimensions, altitudes, or times of designation of the airspace (such as changes in designation of the controlling or using agency, or correction of typographical errors). As such, this action is not expected to result in any potentially significant environmental impacts. In accordance with the FAA's NEPA implementation policy and procedures regarding extraordinary circumstances, the FAA has reviewed this action for factors and circumstances in which a normally categorically excluded action may have a significant environmental impact requiring further analysis. The FAA has determined that no extraordinary circumstances exist that warrant preparation of an environmental assessment or environmental impact statement.
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 73</HD>
                    <P>Airspace, Prohibited areas, Restricted areas.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Amendment</HD>
                <P>In consideration of the foregoing, the Federal Aviation Administration amends 14 CFR part 73 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 73—SPECIAL USE AIRSPACE</HD>
                </PART>
                <REGTEXT TITLE="14" PART="73">
                    <AMDPAR>1. The authority citation for 14 CFR part 73 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>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 73.53</SECTNO>
                    <SUBJECT>North Carolina (NC) [Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="14" PART="73">
                    <AMDPAR>2. Section 73.53 is amended as follows:</AMDPAR>
                    <STARS/>
                    <EXTRACT>
                        <HD SOURCE="HD1">R-5301 Harvey Point, NC [Amended]</HD>
                        <P>
                            <E T="03">Boundaries.</E>
                             Beginning at lat. 36°04′56″ N, long. 76°16′47″ W; to lat. 36°04′23″ N, long. 76°20′59″ W; to lat. 36°06′58″ N, long. 76°20′58″ W; thence clockwise via a 3 nautical mile arc centered at lat. 36°04′01″ N, long. 76°20′19″ W; to the point of beginning.
                        </P>
                        <P>
                            <E T="03">Designated altitudes.</E>
                             Surface to 14,000 feet MSL.
                        </P>
                        <P>
                            <E T="03">Time of designation.</E>
                             Continuous.
                        </P>
                        <P>
                            <E T="03">Controlling agency.</E>
                             USMC, MCAS Cherry Point CERAP.
                        </P>
                        <P>
                            <E T="03">Using agency.</E>
                             USMC, Commanding Officer, MCAS Cherry Point, NC.
                        </P>
                        <HD SOURCE="HD1">R-5302A Albemarle Sound, NC [Amended]</HD>
                        <P>
                            <E T="03">Boundaries.</E>
                             Beginning at lat. 36°01′21″ N, long. 76°14′29″ W; to lat. 36°02′19″ N, long. 76°07′14″ W; to lat. 36°00′01″ N, long. 76°07′14″ W; to lat. 36°00′01″ N, long. 76°14′29″ W; to the point of beginning.
                        </P>
                        <P>
                            <E T="03">Designated altitudes.</E>
                             Surface to 14,000 feet MSL.
                        </P>
                        <P>
                            <E T="03">Time of designation.</E>
                             By NOTAM at least 24 hours in advance.
                            <PRTPAGE P="40872"/>
                        </P>
                        <P>
                            <E T="03">Controlling agency.</E>
                             USMC, MCAS Cherry Point CERAP.
                        </P>
                        <P>
                            <E T="03">Using agency.</E>
                             USMC, Commanding Officer, MCAS Cherry Point, NC.
                        </P>
                        <HD SOURCE="HD1">R-5302B Albemarle Sound, NC [Amended]</HD>
                        <P>
                            <E T="03">Boundaries.</E>
                             Beginning at lat. 36°04′59″ N, long. 76°16′29″ W; to lat. 36°04′01″ N, long. 76°05′59″ W; to lat. 36°00′01″ N, long. 76°05′59″ W; to lat. 36°00′01″ N, long. 76°12′59″ W; to lat. 36°00′04″ N, long. 76°24′17″ W; thence clockwise via a 4 nautical mile arc centered at lat. 36°02′01″ N, long. 76°19′59″ W; to lat. 36°03′56″ N, long. 76°24′18″ W; to the point of beginning.
                        </P>
                        <P>
                            <E T="03">Designated altitudes.</E>
                             100 feet AGL to 14,000 feet MSL.
                        </P>
                        <P>
                            <E T="03">Time of designation.</E>
                             By NOTAM at least 24 hours in advance.
                        </P>
                        <P>
                            <E T="03">Controlling agency.</E>
                             USMC, MCAS Cherry Point CERAP.
                        </P>
                        <P>
                            <E T="03">Using agency.</E>
                             USMC, Commanding Officer, MCAS Cherry Point, NC.
                        </P>
                        <HD SOURCE="HD1">R-5302C Albemarle Sound, NC [Amended]</HD>
                        <P>
                            <E T="03">Boundaries.</E>
                             Beginning at lat. 36°00′01″ N, long. 76°12′59″ W; to lat. 35°58′50″ N, long. 76°16′58″ W; thence clockwise via a 4 nautical mile arc centered at lat. 36°02′01″ N, long. 76°19′59″ W; to lat. 36°00′04″ N, long. 76°24′17″ W; to the point of beginning.
                        </P>
                        <P>
                            <E T="03">Designated altitudes.</E>
                             100 feet AGL to 3,000 feet MSL.
                        </P>
                        <P>
                            <E T="03">Time of designation.</E>
                             By NOTAM at least 24 hours in advance.
                        </P>
                        <P>
                            <E T="03">Controlling agency.</E>
                             USMC, MCAS Cherry Point CERAP.
                        </P>
                        <P>
                            <E T="03">Using agency.</E>
                             USMC, Commanding Officer, MCAS Cherry Point, NC.
                        </P>
                    </EXTRACT>
                </REGTEXT>
                <STARS/>
                <SIG>
                    <DATED>Issued in Washington, DC, on July 1, 2026.</DATED>
                    <NAME>Alex W. Nelson,</NAME>
                    <TITLE>Manager, Rules and Regulations Group.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13620 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">NATIONAL AERONAUTICS AND SPACE ADMINISTRATION</AGENCY>
                <CFR>14 CFR Part 1250</CFR>
                <DEPDOC>[NASA Document Number: NASA-26-029]</DEPDOC>
                <RIN>RIN 2700-AE89</RIN>
                <SUBJECT>Nondiscrimination in Federally Assisted Programs of NASA—Effectuation of Title VI of the Civil Rights Act of 1964</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Aeronautics and Space Administration (NASA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>NASA is amending its regulation implementing Title VI of the Civil Rights Act of 1964 (Title VI) for federally assisted programs to conform more closely to the statutory text and recent revisions by the Department of Justice (DOJ). This action removes provisions establishing disparate-impact liability. The rule also clarifies that Title VI reaches employment practices under this part only where employment is a primary objective of the Federal financial assistance or where intentional discrimination is shown. These changes align NASA's regulation with Title VI and promote consistency across Federal agencies.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective date:</E>
                         July 6, 2026.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Rob Grant, Equal Opportunity Program Division, NASA Headquarters, (321) 867-9169.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Executive Summary</HD>
                <P>
                    NASA 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 intentionally discriminatory conduct, 
                    <E T="03">see</E>
                     42 U.S.C. 2000d. There are serious statutory and constitutional concerns with NASA's current Title VI regulations because the current regulations go beyond intentional discrimination by prohibiting conduct that has an unintentional disparate impact. This rule accordingly rescinds those portions of the regulations, which are in considerable tension with both the statute and the Constitution and do not sufficiently serve the public interest.
                </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 (Apr. 23, 2025). That 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.” 
                    <E T="03">Id.</E>
                     at 17537. Although NASA would take this action independent of Executive Order 14281, the Order supports this action.
                </P>
                <P>This rule makes clear to NASA's Federal-funding recipients that its Title VI regulations prohibit only intentional discrimination, and NASA thus will not pursue 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, as amended, provides: “No person in the United States shall, on the ground of race, color, or national origin, be excluded from participation in, be denied the benefits of, or be subjected to discrimination under any program or activity receiving 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. 
                    <E T="03">See Alexander</E>
                     v. 
                    <E T="03">Sandoval,</E>
                     532 U.S. 275, 280 (2001) (“[I]t is . . . beyond dispute—and no party disagrees—that [Title VI] prohibits only intentional discrimination.”). The statute does not provide any Federal department or agency with authority to prohibit conduct having an unintentional disparate impact. And despite having ample opportunities, Congress has enacted no subsequent amendments to Title VI to impose disparate-impact liability.
                </P>
                <HD SOURCE="HD2">B. Relevant Supreme Court Decisions</HD>
                <P>
                    The Supreme Court has held that Title VI, 42 U.S.C. 2000d, does not prohibit facially neutral policies that result in disparate outcomes when there is no discriminatory intent. Rather, it prohibits only intentional discrimination. In 1978, 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 the Univ. of Cal.</E>
                     v. 
                    <E T="03">Bakke,</E>
                     438 U.S. 265, 287 (1978) (Powell, J., announcing the judgment of the Court); 
                    <E T="03">id.</E>
                     at 325, 328, 352-53 (Brennan, White, Marshall, and Blackmun, JJ., concurring in part and dissenting 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>
                    ”). Shortly before 
                    <E T="03">Bakke,</E>
                     the Supreme Court held that the Equal Protection Clause prohibits only intentional discrimination and that “a law or other official act” that has a “racially disproportionate impact” alone does not violate that clause. 
                    <E T="03">Washington</E>
                     v. 
                    <E T="03">Davis,</E>
                     426 U.S. 229, 239 (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.”). Taken together, these Supreme Court cases establish that Title VI's statutory prohibition, like the Equal Protection Clause, extends only to intentional discrimination.
                </P>
                <P>
                    In 2001, the Supreme Court, in 
                    <E T="03">Alexander</E>
                     v. 
                    <E T="03">Sandoval,</E>
                     reaffirmed that settled understanding. 532 U.S. at 280 (“[I]t is . . . beyond dispute . . . that [Title VI] prohibits only intentional discrimination.”). In 
                    <E T="03">Sandoval,</E>
                     the Supreme Court held that private plaintiffs lacked a private right of action 
                    <PRTPAGE P="40873"/>
                    to enforce DOJ's then-existing “disparate-impact regulations.” 
                    <E T="03">Id.</E>
                     at 285-87. Although the Supreme Court had previously found a private cause of action to enforce Title VI's bar on intentional discrimination, 
                    <E T="03">id.</E>
                     at 279-80, that conclusion did not extend to enforcing DOJ's “disparate-impact regulations.” 
                    <E T="03">Id.</E>
                     at 285. As the Supreme Court explained, it is “clear” that “the disparate-impact regulations do not simply apply” the statutory prohibition, as the regulations “forbid conduct that [Title VI] permits,” so it is equally “clear that the private right of action to enforce [Title VI] does not include a private right to enforce these regulations.” 
                    <E T="03">Id.</E>
                     And although the Supreme Court in 
                    <E T="03">Sandoval</E>
                     “assume[d],” without deciding, that DOJ's disparate-impact regulations were valid, the Court explained that the then-current version of the regulations were in “considerable tension” with the Supreme Court's Title VI precedents. Similarly, the regulations did not “authoritatively” construe Title VI because the regulations “forbid conduct”—namely, policies that unintentionally result in a disparate impact—that Title VI “permits.” 
                    <E T="03">Id.</E>
                     at 281-82, 284-85; 
                    <E T="03">see also id.</E>
                     at 286 n.6 (“[Title VI] permits the very behavior that the regulations forbid.”).
                </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">C. 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 explains that this “principle guarantees equality of opportunity, not equal outcomes,” and “promises that people are treated as individuals, not components of a particular race or group.” 
                    <E T="03">Id.</E>
                </P>
                <P>
                    That Order also explains 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.” 
                    <E T="03">Id.</E>
                     As the Order explains, disparate-impact liability “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 disparate-impact liability's 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>
                     Accordingly, this rule revises NASA's currently existing Title VI regulations, consistent with the Order's policy and purpose.
                </P>
                <P>
                    In any event, NASA would have independently initiated steps toward making these changes regardless of Executive Order 14281. Even if Executive Order 14281 did not exist, in other words, NASA would have taken steps to adopt the policy to eliminate the use of disparate-impact liability under Title VI. The Order states, and NASA firmly agrees, that a “bedrock principle of the United States is that all citizens are treated equally under the law. 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. It encourages meritocracy and a colorblind society,” not race-, color-, or national-origin-based favoritism. 90 FR at 17537. And adherence to this principle, including in the issuance of grants, “is essential to creating opportunity, encouraging achievement, and sustaining the American Dream.” 
                    <E T="03">Id.</E>
                </P>
                <P>Imposing disparate-impact liability endangers these policy objectives. Disparate-impact liability also raises serious constitutional concerns, is in considerable tension with Title VI, creates confusion, increases the costs of compliance, and does not serve the public interest. After considering the relevant issues and factors and weighing the relevant considerations, NASA concludes that these reasons support eliminating disparate-impact liability from NASA's Title VI regulations. In any event, NASA concludes that each reason is an independent basis for eliminating disparate-impact liability from NASA's Title VI regulations.</P>
                <HD SOURCE="HD2">D. Need for Rulemaking</HD>
                <P>14 CFR 1250.103, entitled “Discrimination prohibited,” includes several provisions that go beyond Title VI and the Constitution by prohibiting conduct or activities causing unintentional disparate impact. And in some instances, these provisions may encourage or even require unlawful discrimination in the form of affirmative action. 14 CFR 1250.103-2(b) is the current regulation's general disparate-impact prohibition, which states that a “recipient . . . may not . . . utilize criteria or methods of administration which have the effect of subjecting individuals to discrimination because of their race, color, or national origin.” Beyond that general prohibition, 14 CFR 1250.103-2(a)(3) addresses a Federal-funding recipient's selection of the site or location of facilities and includes two references to “effect” that extends to conduct with an unintentional disparate impact. 14 CFR 1250.103-2(e) addresses the use of affirmative action and provides that funding recipients may (and sometimes must) use race, color, or national origin to overcome unintentional disparate “consequences.” But this provision does not expressly specify that the funding recipient must narrowly tailor such use nor that this use must serve a compelling governmental interest, as is required to satisfy strict scrutiny. 14 CFR 1250.103-3(d) addresses prohibited discriminatory employment practices and extends beyond intentional discrimination to prohibiting conduct that “tends” to have a discriminatory effect. Finally, 14 CFR 1250.103-4(f)-(g) provide two illustrative applications of disparate-impact liability.</P>
                <P>There are serious statutory and constitutional concerns with NASA's Title VI disparate-impact regulations. NASA also has serious policy concerns with its current disparate-impact regulations because they create confusion, undermine public confidence in the nation's civil rights laws and the rule of law, and produce 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. As the Supreme Court has made clear, Title VI prohibits “only intentional discrimination” and “permits” facially neutral policies that result in disparate outcomes when there is no discriminatory intent. 
                    <E T="03">Sandoval,</E>
                     532 U.S. at 280, 286 n.6. That is the “single, best meaning” of Title VI. 
                    <E T="03">
                        Loper 
                        <PRTPAGE P="40874"/>
                        Bright,
                    </E>
                     603 U.S. at 400. 
                    <E T="03">Sandoval</E>
                     calls into serious doubt the legality of NASA's “disparate-impact regulations.” 
                    <E T="03">Sandoval,</E>
                     532 U.S. at 281-82, 284-85 (noting that DOJ's then-existing regulations were in “considerable tension” with the Supreme Court's Title VI precedents); 
                    <E T="03">see also id.</E>
                     at 286 n.6 (“[Title VI] permits the very behavior that the regulations forbid.”).
                </P>
                <P>
                    Although 
                    <E T="03">Sandoval</E>
                     applied to DOJ's Title VI regulations and resolved only the question of private enforceability, subsequent cases such as 
                    <E T="03">Loper Bright</E>
                     have made clear that NASA cannot extend Title VI beyond its best meaning. 
                    <E T="03">See</E>
                     603 U.S. at 412-13 (holding that “courts must . . . ensur[e] that [an] agency acts within” its statutory authority). And even in the absence of Supreme Court precedent, NASA would have concluded that the best reading of Title VI is that it prohibits only intentional discrimination.
                </P>
                <P>
                    Title VI authorizes agencies to promulgate regulations “to effectuate” the statute's prohibition of intentional discrimination. 42 U.S.C. 2000d-1. The current prohibition of conduct having an unintentional disparate impact reaches a vastly broader scope than the statute itself. This scope is too broad to be considered a simple prophylactic measure aimed at preventing intentional discrimination. 
                    <E T="03">See Sandoval,</E>
                     532 U.S. at 286 n.6 (“[Title VI] permits the very behavior that the regulations forbid.”). Thus, the disparate-impact regulations do not “effectuate” Title VI. 42 U.S.C. 2000d-1.
                </P>
                <P>
                    There are also serious concerns about whether NASA'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 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.)). Despite the promises of the Equal Protection Clause, a funding recipient's risk of disparate-impact liability under NASA's regulations is triggered by unintentional disparate outcomes, which the 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 is coerced to proactively consider race, color, and national origin, and potentially use it to change unintended disparate outcomes.
                </P>
                <P>
                    In short, disparate-impact liability encourages and, in some cases, requires covered entities to engage in the intentional use of race and racial balancing to eliminate those disparate outcomes by treating certain racial groups differently from others—the exact conduct the Equal Protection Clause forbids. 
                    <E T="03">See id.</E>
                     The serious constitutional concerns raised by these perverse incentives further confirm that the best reading of Title VI is that it prohibits only intentional discrimination and does not authorize NASA to impose disparate-impact liability. 
                    <E T="03">See Edward J. DeBartolo Corp.</E>
                     v. 
                    <E T="03">Fla. Gulf Coast Bldg. &amp; Constr. Trades Council,</E>
                     485 U.S. 568, 575 (1988) (“[W]here an otherwise acceptable construction of a statute would raise serious constitutional problems, the Court will construe the statute to avoid such problems unless such construction is plainly contrary to the intent of Congress.” (citing 
                    <E T="03">NLRB</E>
                     v. 
                    <E T="03">Catholic Bishop of Chi.,</E>
                     440 U.S. 490, 499-501, 504 (1979))).
                </P>
                <P>
                    This encouraged or coerced use of race, color, or national origin violates the Equal Protection Clause unless it survives review under the “daunting” strict-scrutiny standard. 
                    <E T="03">SFFA,</E>
                     600 U.S. at 206; 
                    <E T="03">see also Free Speech Coal., Inc.</E>
                     v. 
                    <E T="03">Paxton,</E>
                     145 S. Ct. 2291, 2310 (2025) (“Strict scrutiny—which requires a restriction to be the least restrictive means of achieving a compelling governmental interest—is `the most demanding test known to constitutional law.'” (quoting 
                    <E T="03">City of Boerne</E>
                     v. 
                    <E T="03">Flores,</E>
                     521 U.S. 507, 534 (1997))). The use of race, color, or national origin necessitated by the disparate-impact provisions runs into serious issues with the requirement of narrow tailoring to achieve a compelling interest. 
                    <E T="03">SFFA,</E>
                     600 U.S. at 206-07.
                </P>
                <P>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 to “overcome the consequences of” unintended racial disparities. 14 CFR 1250.103-2(e). Thus, for substantially the same reasons as above, the affirmative action provision raises serious constitutional concerns.</P>
                <P>Finally, 14 CFR 1250.103-4(f)-(g) provide illustrative applications of disparate-impact liability. Because NASA is removing from its regulations the provisions establishing disparate-impact liability, the examples of disparate impact are no longer relevant.</P>
                <P>
                    As summarized above, there are serious statutory and constitutional concerns with NASA's disparate-impact regulations. But even if the regulations were legal, NASA finds that eliminating the potential constitutional concerns addressed above would independently justify the amendment 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”). And even if the regulations did not raise serious constitutional concerns, NASA finds that eliminating the costs and confusion caused by the mismatch between the statute and the disparate-impact regulations would independently justify the repeal of the regulations.
                </P>
                <HD SOURCE="HD2">2. Serious Policy Concerns</HD>
                <P>NASA also has serious policy concerns with the imposition of disparate-impact liability. Although NASA expresses its policy concerns with disparate-impact liability independent of Executive Order 14281, that Order sets forth many valid policy concerns with disparate-impact liability. As noted in section 1 of the Order,</P>
                <EXTRACT>
                    <FP>On a practical level, disparate-impact liability has hindered businesses from making hiring and other employment decisions based on merit and skill, their needs, or the needs of their customers because of the specter that such a process might lead to disparate outcomes, and thus disparate-impact lawsuits. This has made it difficult, and in some cases impossible, for employers to use bona fide job-oriented evaluations when recruiting, which prevents job seekers from being paired with jobs to which their skills are most suited—in other words, it deprives them of opportunities for success.</FP>
                </EXTRACT>
                <FP>
                    90 FR at 17537. Moreover, the legal concerns identified 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, color, and national origin. As explained above, 
                    <E T="03">Sandoval</E>
                     casts substantial doubt on the validity of the disparate-impact regulations that many Federal departments and agencies have promulgated pursuant to Title VI. 532 U.S. at 280-82.
                </FP>
                <P>
                    Additionally in practice, and as explained above, disparate-impact liability can lead covered entities to engage in racial balancing even as Title VI forbids intentional racial discrimination. This tension tends to 
                    <PRTPAGE P="40875"/>
                    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.
                </P>
                <P>
                    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. 
                    <E T="03">See, e.g., SFFA,</E>
                     600 U.S. at 216-17 (explaining that the “[racial] categories” utilized in the racial preference programs at issue were “themselves imprecise in many ways” and “the use of these opaque racial categories undermine[d], instead of promote[d], [their] goals”). This confusion undermines the law's ability to teach principles of nondiscrimination. 
                    <E T="03">See e.g.,</E>
                     14 CFR 1250.103-4(f)-(g) (providing illustrations of affirmative action in referrals and recruitment). NASA believes that these policy concerns independently justify repealing certain parts of its regulation to cure this confusion, remove the incentive for covered entities to engage in racial balancing, and maintain clarity and public confidence in the nation's civil rights laws.
                </P>
                <P>NASA has considered the view that looking at disparate effects can sometimes be useful in uncovering or deterring subtle intentional discrimination or intentional indifference to unnecessary and arbitrary barriers. But that view's alleged benefits are outweighed by the other issues and factors NASA has considered. And in any event, eliminating disparate-impact liability does not preclude the use of data on disparate outcomes to help prove intentional discrimination. This use of statistical disparity to help establish, as an evidentiary matter, liability for intentional discrimination materially differs from using it to impose liability for conduct having an unintentional disparate impact.</P>
                <P>NASA has also considered the alternative of trying to adopt a modified version of disparate-impact liability, for example, by requiring covered entities to remedy so-called unintentional discrimination through a notice-and-remedy model. Such an approach might require a recipient to develop and implement a race-neutral corrective action plan when a compliance review reveals substantial disparities in access or benefits or require targeted, race-neutral barrier-removal measures if a periodic audit reveals statistically significant disparities of key program outcomes. But any version of imposing liability for so-called unintentional discrimination is inconsistent with Title VI's original public meaning. Regardless, even a modified version of disparate-impact liability would not eliminate NASA's serious legal and policy concerns. NASA determines that any benefits from adopting alternative versions of disparate-impact liability are outweighed by NASA's legal and policy concerns. And even if possible, developing such a rule would not solve the confusion or rule-of-law concerns expressed above, nor reduce the compliance and litigation costs that covered entities face. NASA believes that the better course is to avoid the complexities, costs, and litigation associated with this alternative, even if eliminating disparate-impact liability would ultimately leave some problems unaddressed and others inadequately addressed.</P>
                <P>
                    NASA has additionally considered the potential reliance interests of funding recipients and others on the disparate-impact regulations. 
                    <E T="03">Sandoval,</E>
                     however, cast serious doubt on the continuing viability of the regulations more than 20 years ago. At least since Sandoval, NASA's enforcement of its Title VI disparate-impact regulations has been minimal. 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 NASA's Title VI disparate-impact regulations. 90 FR at 17538. NASA accordingly believes that any reliance interests should be minimal and do not outweigh NASA's legal and other policy concerns. Further, each of NASA's concerns, whether considered cumulatively or separately, outweighs any reliance interests.
                </P>
                <P>
                    NASA 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, while NASA could continue to pursue disparate-impact liability. Repealing the disparate-impact regulations would eliminate this incongruent enforcement.
                </P>
                <P>Overall, after considering the relevant issues and factors and weighing the relevant considerations, NASA finds that, regardless of the legality of NASA's disparate-impact regulations, the above summarized policy concerns, when viewed separately or cumulatively, independently justify the repeal of its disparate-impact regulations.</P>
                <HD SOURCE="HD1">III. Regulatory Amendments</HD>
                <HD SOURCE="HD2">A. Comparison of Amendments</HD>
                <P>The left column lists the DOJ's Title VI final rule conforming amendments, and the right column shows the NASA regulatory text to remove.</P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s75,r150">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Section (DOJ 28 CFR 42.104)</CHED>
                        <CHED H="1">Remove (NASA 14 CFR part 1250)</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">(b)(2)—Disparate impact “criteria or methods of administration”</ENT>
                        <ENT>1250.103-2(b)—Delete full text of paragraph: “A recipient, in determining the types of services, financial aid, or other benefits, or facilities which will be provided under any such program, or the class of individuals to whom, or the situations in which, such services, financial aid, other benefits, or facilities will be provided under any such program, or the class of individuals to be afforded an opportunity to participate in any such program, may not, directly or through contractual or other arrangements, utilize criteria or methods of administration which have the effect of subjecting individuals to discrimination because of their race, color, or national origin, or have the effect of defeating or substantially impairing accomplishment of the objectives of the program as respects individuals of a particular race, color, or national origin.”</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">(b)(3)—Facility site selection (“purpose vs. effect”)</ENT>
                        <ENT>1250.103-2(a)(3)—Delete the phrase “or effect” in both places within the section. Current text includes: “. . . may not make selections with the purpose or effect of excluding individuals from, denying them the benefits of, or subjecting them to discrimination under any program to which this regulation applies, on the grounds of race, color, or national origin; or with the purpose or effect of defeating or substantially impairing the accomplishment of the objectives of the Act or this regulation.”</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">(b)(6)—“Affirmative action”/mandatory remedial steps</ENT>
                        <ENT>1250.103-2(e)—Delete full text of paragraphs mandating affirmative steps to overcome past discrimination or requiring service to underrepresented groups.</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="40876"/>
                        <ENT I="01">(c)(2)—Employment practices (disparate impact reach)</ENT>
                        <ENT>1250.103-3(d)—Delete full text of paragraph that extends Title VI to disparate impact in programs the primary purpose of which is not employment: “Where a primary objective of the Federal financial assistance is not to provide employment, but discrimination on the grounds of race, color, or national origin in the employment practices of the recipient or other persons subject to the regulation tends, on the grounds of race, color, or national origin, to exclude individuals from participation in, to deny them benefits of, or to subject them to discrimination under any program to which this regulation applies, the provisions of paragraph (a) of this section shall apply to the employment practices of the recipient or other persons subject to the regulation, to the extent necessary to assure equality of opportunity to, and nondiscriminatory treatment of, beneficiaries.”</ENT>
                    </ROW>
                </GPOTABLE>
                <P>Additionally, NASA is making further changes. First, NASA is replacing the defined term “Applicable” with “Applicant” within section 1250.102(b). Additionally, NASA is deleting 14 CFR 1250.103-4(f)-(g) in their entirety. Finally, NASA is removing 14 CFR 1250.112.</P>
                <HD SOURCE="HD2">B. Section-By-Section Analysis</HD>
                <HD SOURCE="HD3">14 CFR 1250.102(b)</HD>
                <P>14 CFR 1250.102(b) contains a typo regarding the term “Applicant,” which this rule corrects.</P>
                <HD SOURCE="HD3">14 CFR 1250.103-2(b)</HD>
                <P>14 CFR1250.103-2(b) 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 14 CFR 1250.103-2(b)'s purpose is to prohibit unintentional disparate-impact discrimination, this rule deletes this subsection in its entirety. It thus amends the regulations to conform to Title VI and to address the considerations and determinations described in this document. The rule replaces subsection (b) with a placeholder to maintain the numbering accuracy of previous citations and other references to parts of this section.</P>
                <HD SOURCE="HD3">14 CFR 1250.103-2(a)(3)</HD>
                <P>14 CFR 1250.103-2(a)(3) addresses a Federal-funding recipient's or applicant's selection of the site or location of facilities. It provides that a funding recipient may not make selections with the “purpose or effect” of discriminating, or “with the purpose or effect of defeating or substantially impairing the accomplishment of the objectives of” Title VI or NASA's implementing regulations. The paragraph's two references to “effect” extend its scope to unintentional disparate impacts. This rule deletes both “or effect” references to conform paragraph (a)(3) more closely to Title VI and to address the legal and policy considerations and determinations described in this document.</P>
                <HD SOURCE="HD3">14 CFR 1250.103-2(e)</HD>
                <P>14 CFR 1250.103-2(e) deals with affirmative action. The second sentence—beginning with “This regulation does not prohibit the consideration of race, color, or national origin”—authorizes affirmative action even in the absence of a finding of prior discrimination in a program “to remove or over the consequences of practices or impediments of practices or impediments which have restricted the availability of, or participation in, the program or activity receiving Federal financial assistance, on the grounds of race, color, or national origin.” This provision points not to intentional discrimination, but rather to the unintentional “consequences of practices or impediments.” It consequently encourages intentional racial classifications, racial preferences, and other race-based actions without specifying the compelling governmental interest and narrow tailoring that the Equal Protection Clause demands. This section has long been unlawful under the Equal Protection Clause.</P>
                <P>
                    The third sentence of 14 CFR 1250.103-2(e) provides that “[w]here previous discriminatory practices or usage tends, on the grounds 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 any program or activity to which this regulation applies the applicant or recipient has an obligation to take reasonable action to remove or overcome the consequences of the prior discriminatory practice or usage, and to accomplish the purpose of the Act.” This provision goes beyond the Equal Protection Clause, which permits, but does not mandate, a government to take narrowly tailored action to remedy the effects of its identified past discrimination. 
                    <E T="03">See, e.g., Bakke,</E>
                     438 U.S. at 307 (Powell, J.). Moreover, even putting aside the mandatory language, this provision does not expressly require narrow tailoring to counter particular past discrimination, but rather simply “an obligation to take reasonable action to remove or overcome the consequences of the prior discriminatory practice.” This provision accordingly promotes potentially illegal race, color, and national origin discrimination. Moreover, in some instances, it may even coerce recipients to consider and use racial preferences when the recipient may not want to. This is contrary to NASA's goal of promoting and defending a culture of nondiscrimination and is destructive to the public's understanding of and faith in the nation's civil rights laws. This rule, therefore, removes paragraph (e).
                </P>
                <HD SOURCE="HD3">14 CFR 1250.103-3(d)</HD>
                <P>14 CFR 1250.103-3 addresses prohibited discriminatory employment practices. 14 CFR 1250.103-3(a) prohibits intentionally discriminatory employment practices in a program when a primary objective of the Federal financial assistance that program receives is to provide employment. 14 CFR 1250.103-3(d) extends the prohibition on discrimination to employment practices of the funding recipient even when 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 persons from participation in, to deny them the benefits of, or to subject them to discrimination under the program receiving Federal financial assistance.” This section prohibits not only intentional discrimination but also conduct that “tends” to have a discriminatory effect.</P>
                <P>
                    Moreover, NASA notes that the extension to employment practices where the Federal funding's primary objective is not to provide employment conflicts with 42 U.S.C. 2000d-3. That section 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 
                    <PRTPAGE P="40877"/>
                    employer, employment agency, or labor organization except where a primary objective of the Federal financial assistance is to provide employment.” 42 U.S.C. 2000d-3; 
                    <E T="03">see also Johnson</E>
                     v. 
                    <E T="03">Transp. Agency, Santa Clara Cnty.,</E>
                     480 U.S. 616, 627-28 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 14 CFR 1250.103-3(d) to amend the regulation so that it more closely adheres to Title VI and to address the legal and policy considerations and determinations described in this document.
                </P>
                <HD SOURCE="HD3">Section 14 CFR 1250.103-4(f)-(g)</HD>
                <P>Additionally, 14 CFR 1250.103-4(f)-(g) provide illustrative applications of disparate-impact liability. Because NASA is removing from its regulations the provisions establishing disparate-impact liability, these examples are no longer relevant.</P>
                <HD SOURCE="HD3">Section 14 CFR 1250.112</HD>
                <P>Finally, NASA is removing 14 CFR1250.112 because the provision is unnecessary to effectuate 42 U.S.C. 2000d-1. No specific statutory provision mandates or necessitates a regulation governing the internal coordination and relationships of agency officials. 42 U.S.C. 2000d-1 directs the agency to issue rules to effectuate the nondiscrimination requirements applicable to external recipients of Federal funds. Although internal coordination is a necessary component of agency operations, a formal regulation is not required to effectuate external enforcement; such matters can be handled through internal agency management directives. Removing this section ensures that NASA's Title VI regulations remain fully aligned with the agency's commitment to modernize its regulations by rescinding outdated provisions and text that lacks a statutory basis.</P>
                <HD SOURCE="HD1">IV. Severability</HD>
                <P>NASA's position is that each of the amendments described by this rule serves a vital, related, but distinct purpose. NASA 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. NASA would adopt any of the amendments independently of the invalidity of a separate amendment.</P>
                <HD SOURCE="HD1">V. Legal Authority</HD>
                <P>This rule is issued under section 602 of Title VI,42 U.S.C. 2000d-1, and the laws listed in appendix A to part 1250.</P>
                <HD SOURCE="HD1">VI. Regulatory Certifications</HD>
                <HD SOURCE="HD2">Administrative Procedure Act</HD>
                <P>NASA issues this final rule without prior public notice and comment or a delayed effective date 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).</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.” 14 CFR 1250.102(d); 
                    <E T="03">see also</E>
                     14 CFR 1250.104 (requiring funding recipient sign contractual assurance of compliance with Title VI); 
                    <E T="03">Cummings</E>
                     v. 
                    <E T="03">Premier Rehab Keller, P.L.L.C.,</E>
                     596 U.S. 212, 217-18 (2022) (observing that Congress enacted Title VI “[p]ursuant to its authority to `fix the terms on which it shall disburse federal money' ” (internal citation omitted)). 
                    <E T="03">Cf. Education Programs or Activities Receiving or Benefitting from Federal Financial Assistance,</E>
                     82 FR 46655, 46655 (Oct. 6, 2017) (invoking the section 553(a)(2) exception to amend Title IX regulations to “promote consistency in the enforcement of Title IX for [the Department of Agriculture] financial assistance recipients”); 
                    <E T="03">Preserving Community and Neighborhood Choice,</E>
                     85 FR 47899 (Aug. 7, 2020) (invoking the 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 the 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 the exception to suspend DOJ 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 for Management and Budget (OMB) under 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 NASA, all the forms of Federal financial assistance set forth under 2 CFR 200.1 that NASA administers would fall under the “public property, loans, grants, benefits, or contracts” exception. Thus, NASA issues this final rule without prior public notice and comment or a delayed effective date under 5 U.S.C. 553(a)(2).</P>
                <HD SOURCE="HD2">Executive Order 12866 and Executive Order 13563 (Regulatory Review)</HD>
                <P>
                    NASA has consulted the Office of Information and Regulatory Affairs (OIRA) pursuant to section 3(f) of Executive Order 12866, 
                    <E T="03">Regulatory Planning and Review,</E>
                     58 FR 51735, 51738 (Sep. 30, 1993). Because this rule makes conforming edits, aligns with DOJ's Title VI revisions, and imposes no new requirements, this final rule is a significant regulatory action.
                </P>
                <P>
                    This regulation has been drafted and reviewed in accordance with Executive Order 13563 section 1(b), 
                    <E T="03">Improving Regulation and Regulatory Review,</E>
                     76 FR 3821, 3821 (Jan. 18, 2011), which supplements and reaffirms the principles of Executive Order 12866. Executive Orders 12866 and 13563 direct agencies to assess all costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits. 58 FR at 51735; 76 FR at 3821. 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. 
                    <E T="03">Id.</E>
                </P>
                <P>
                    As explained in the preamble, the regulatory modifications this rule makes are necessary to conform NASA regulations to Executive Order 14281, address serious legal concerns regarding NASA's Title VI regulation based on the Supreme Court's reading of Title VI in 
                    <E T="03">Sandoval,</E>
                     harmonize the implementing regulation 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 NASA's Title VI regulations.
                    <PRTPAGE P="40878"/>
                </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, NASA issued approximately 8,202 separate awards totaling approximately $6 billion over the past 5 years. NASA does not track which of its investigations and compliance reviews involve solely allegations of disparate-impact discrimination. For enforcement actions that relate to both intentional discrimination and conduct having an unintentional disparate impact, NASA does not track and cannot reliably quantify the costs attributable to the disparate-impact portions of enforcement actions. That the existence of a disparate impact is a factor that may be considered in evaluating intentional discrimination further impedes monetizing costs and benefits. Therefore, the overall cost effect on NASA is difficult to quantify. The deregulatory action should decrease NASA's enforcement costs, however. It should also have the benefit, albeit difficult to quantify, of bringing NASA's conduct in line with the law. Similarly, NASA 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>
                    NASA recognizes that a funding recipient may receive Federal funds from sources other than NASA. This deregulatory action does not create any new obligations for funding recipients. On the contrary, by eliminating disparate-impact liability from the regulation, this 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>
                     14 CFR 1250.104. These contractual assurances impose varying requirements that each Federal funding source deems necessary. Funding recipients will continue to be held to the most stringent contractual assurance and regulation. And in any event, NASA notes that other agencies are currently amending their regulations to align with the changes made in this rule, so NASA 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, NASA 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, NASA adopt a regulation only upon a reasoned determination that its benefits justify its costs and choose a regulatory approach that maximizes net benefits. 
                    <E T="03">See</E>
                     58 FR at 51735; 76 FR at 3821.
                </P>
                <HD SOURCE="HD2">Executive Order 14192 (Unleashing Prosperity Through Deregulation)</HD>
                <P>
                    Executive Order 14192 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. 90 FR 9065, 9065 (Jan. 31, 2025). In furtherance of this requirement, section 3(c) of the Order requires that “any 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.” 
                    <E T="03">Id.</E>
                     This rule eliminates unnecessary regulation by revising NASA's current Title VI regulations, which extend prohibited conduct to include unintentional disparate impacts and thus expand the scope of those regulations to a vastly broader range of conduct than the statute prohibits. Accordingly, NASA considers this rule to be a deregulatory action under Executive Order 14192.
                </P>
                <HD SOURCE="HD2">Executive Order 14294 (Fighting Overcriminalization in Federal Regulations)</HD>
                <P>NASA has reviewed this rule under Executive Order 14294 and determined that it does not create or modify any criminal regulatory provisions; accordingly, Executive Order 14294 does not apply.</P>
                <HD SOURCE="HD2">Executive Order 13132 (Federalism)</HD>
                <P>NASA analyzed this rule under Executive Order 13132 and determined it does not have federalism implications because it does not have substantial direct effects on the States, alter the relationship between the national government and the States, or affect the distribution of power and responsibilities among levels of government. Accordingly, no federalism summary impact statement is required.</P>
                <HD SOURCE="HD2">Executive Order 12988 (Civil Justice Reform)</HD>
                <P>This final rule has been reviewed in accordance with Executive Order 12988. It meets applicable standards to minimize litigation, is written clearly, and has no retroactive effect.</P>
                <HD SOURCE="HD2">Regulatory Flexibility Act</HD>
                <P>NASA certifies that this final rule will not have a significant economic impact on a substantial number of small entities because it removes provisions and clarifies the scope of existing requirements without adding new compliance obligations.</P>
                <HD SOURCE="HD2">Unfunded Mandates Reform Act (UMRA)</HD>
                <P>This rule does not contain Federal mandates that may result in the expenditure by State, local, or Tribal governments, in the aggregate, or by the private sector, of $100 million or more in any one year; therefore, sections 202 and 205 of UMRA do not apply.</P>
                <HD SOURCE="HD2">Congressional Review Act (CRA)</HD>
                <P>NASA will submit the rule and the required reports to Congress and the Government Accountability Office pursuant to 5 U.S.C. 801. OIRA has determined that this final rule is not a “major rule” under 5 U.S.C. 804(2).</P>
                <HD SOURCE="HD2">Paperwork Reduction Act</HD>
                <P>
                    This final rule contains no new or revised information collection requirements subject to the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ).
                </P>
                <HD SOURCE="HD2">Executive Order 12250</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>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 1250</HD>
                    <P>Administrative practice and procedure, Civil rights, Equal employment opportunity, Grants programs.</P>
                </LSTSUB>
                <P>For the reasons stated in the preamble, NASA amends 14 CFR part 1250 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 1250—NONDISCRIMINATION IN FEDERALLY-ASSISTED PROGRAMS OF NASA-EFFECTUATION OF TITLE VI OF THE CIVIL RIGHTS ACT OF 1964</HD>
                </PART>
                <REGTEXT TITLE="14" PART="1250">
                    <AMDPAR>1. The authority citation for part 1250 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>Sec. 602, 78 Stat. 252, 42 U.S.C. 2000d-1; and the laws listed in appendix A to this part.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <PRTPAGE P="40879"/>
                    <SECTNO>§ 1250.102</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="14" PART="1250">
                    <AMDPAR>2. In § 1250.102(b), remove the word “Applicable” and add in its place “Applicant.”</AMDPAR>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 1250.103-2</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="14" PART="1250">
                    <AMDPAR>3. In § 1250.103-2:</AMDPAR>
                    <AMDPAR>a. In paragraph (a)(3), remove the words “or effect” wherever they appear.</AMDPAR>
                    <AMDPAR>b. Remove paragraphs (b) and (e).</AMDPAR>
                    <AMDPAR>c. Redesignate paragraphs (c) and (d) as paragraphs (b) and (c).</AMDPAR>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 1250.103-3</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="14" PART="1250">
                    <AMDPAR>4. In § 1250.103-3, remove paragraph (d).</AMDPAR>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 1250.103-4</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="14" PART="1250">
                    <AMDPAR>5. In § 1250.103-4, remove paragraphs (f) and (g).</AMDPAR>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 1250.112</SECTNO>
                    <SUBJECT>[Removed]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="14" PART="1250">
                    <AMDPAR>6. Remove § 1250.112.</AMDPAR>
                </REGTEXT>
                <SIG>
                    <NAME>Jamie Krauk,</NAME>
                    <TITLE>Director, Office of the Executive Secretariat (OES).</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13624 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7510-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Bureau of Alcohol, Tobacco, Firearms, and Explosives</SUBAGY>
                <CFR>27 CFR Part 478</CFR>
                <DEPDOC>[Docket No. ATF-2026-0009; ATF No. 2025R-32D]</DEPDOC>
                <RIN>RIN 1140-AA61</RIN>
                <SUBJECT>Licensee “eZ Check” Verification for Transfers; Withdrawing Direct Final Rule</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Alcohol, Tobacco, Firearms, and Explosives, Department of Justice.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Withdrawing direct final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Due to receiving adverse comments, the Bureau of Alcohol, Tobacco, Firearms, and Explosives (“ATF”) is withdrawing the direct final rule, “Licensee “eZ Check” Verification for Transfers,” published on May 6, 2026.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective July 6, 2026, ATF withdraws the direct final rule published at 91 FR 24357, on May 6, 2026.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Office of Regulatory Affairs, by email at 
                        <E T="03">ORA@atf.gov,</E>
                         by mail at Office of Regulatory Affairs; Enforcement Programs and Services; Bureau of Alcohol, Tobacco, Firearms, and Explosives; 99 New York Ave. NE, Washington, DC 20226, or by telephone at 202-648-7070 (this is not a toll-free number).
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    On May 6, 2026, ATF published a direct final rule in the 
                    <E T="04">Federal Register</E>
                     (91 FR 24357) entitled, “Licensee “eZ Check” Verification for Transfers.” We stated in that direct final rule that if we received significant adverse comment by June 5, 2026, the direct final rule would not take effect and we would publish a timely withdrawal in the 
                    <E T="04">Federal Register</E>
                    . Because we subsequently received adverse comment on that direct final rule, we are withdrawing the rule.
                </P>
                <P>
                    ATF may issue a notice of proposed rulemaking in a future edition of the 
                    <E T="04">Federal Register</E>
                     to initiate action to repromulgate the rule provisions that are being withdrawn today. In any such action, we would address the adverse comment we received on the direct final rule. The adverse comment is publicly available in the electronic docket for RIN 1140-AA61 at 
                    <E T="03">http://www.regulations.gov.</E>
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of subjects in 27 CFR Part 478</HD>
                    <P>Administrative practice and procedure, Arms and munitions, Exports, Freight, Imports, Intergovernmental relations, Law enforcement officers, Military personnel, Penalties, Reporting and recordkeeping requirements, Research, Seizures and forfeitures, Transportation.</P>
                </LSTSUB>
                <P>Accordingly, as of July 6, 2026, ATF withdraws the direct final rule amending 27 CFR part 478, which published at 91 FR 24357 on May 6, 2026.</P>
                <SIG>
                    <NAME>Robert Cekada,</NAME>
                    <TITLE>Director.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13585 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-FY-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">EQUAL EMPLOYMENT OPPORTUNITY COMMISSION</AGENCY>
                <CFR>29 CFR Part 1608</CFR>
                <RIN>RIN 3046-AB39</RIN>
                <SUBJECT>Rescission of Guidelines on Affirmative Action Appropriate Under Title VII of the Civil Rights Act of 1964, as Amended</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Equal Employment Opportunity Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final interpretive rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Equal Employment Opportunity Commission (“EEOC” or “Commission”) is rescinding its regulations regarding Affirmative Action Appropriate Under Title VII of the Civil Rights Act of 1964 (“Guidelines”), and removing it from the Code of Federal Regulations. The Commission is rescinding the Guidelines and removing them from the Code of Federal Regulations because the Guidelines are inconsistent with the statutory language and were not supported by Supreme Court precedent when issued; they are obsolete; they only apply to affirmative action to benefit women or minorities; and they do not take into account multiple relevant Supreme Court cases and numerous developments in the lower courts, over the past four decades since their issuance in 1979.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This final interpretive rule is effective on July 6, 2026, and applicable as of June 29, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Raymond Peeler, Associate Legal Counsel, Office of Legal Counsel at 202-821-6367 (voice), 1-800-669-6820 (TTY), 
                        <E T="03">raymond.peeler@eeoc.gov.</E>
                         Requests for copies of this final interpretive rule in alternative formats should be made to the Office of Communications and Legislative Affairs at (202) 921-3191 (voice), 1-800-669-6820 (TTY), or 1-844-234-5122 (ASL video phone).
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Rescission and Removal of the Guidelines</HD>
                <HD SOURCE="HD2">A. Background</HD>
                <P>
                    Title VII of the Civil Rights Act of 1964 prohibits “discriminat[ion]” against workers “because of [their] race, color, religion, sex, or national origin.” 42 U.S.C. 2000e-2(a)(1). In 1977, the then-Commission proposed—and in 1979 enacted—Guidelines on Affirmative Action Appropriate Under Title VII of the Civil Rights Act, As Amended. The Guidelines' stated purpose was to protect “employers, labor organizations, and other persons subject to title VII [who] have changed their employment practices and systems to improve employment opportunities for minorities and women[.]” 29 CFR 1608.1(a). Employers and other entities subject to Title VII, the then-Commission believed, lacked sufficient guidance regarding the circumstances under which, and the means through which, they could take race- and sex-conscious affirmative action. 
                    <E T="03">Id.</E>
                </P>
                <P>
                    When the Guidelines were proposed in 1977, cases questioning whether affirmative action was compatible with Title VII were winding their way through the lower courts. 
                    <E T="03">See, e.g., Weber</E>
                     v. 
                    <E T="03">Kaiser Aluminum &amp; Chem. Corp.,</E>
                     415 F. Supp. 761 (E.D. La. 1976), 
                    <E T="03">aff'd,</E>
                     563 F.2d 216 (5th Cir. 1977), 571 
                    <PRTPAGE P="40880"/>
                    F.2d 337 (5th Cir. 1978), 
                    <E T="03">cert. granted,</E>
                     439 U.S. 1045 (1978). The district court and the Fifth Circuit in 
                    <E T="03">Weber</E>
                     had already held that the challenged affirmative action program at issue, a racial quota, violated Title VII. Despite the percolating cases, the then-Commission chose to preemptively issue guidance opining that Title VII should be interpreted to permit race- and sex-conscious affirmative action, and explaining to employers when and how they purportedly could take such action permissibly without exposing themselves to liability for violating Title VII.
                </P>
                <P>In the final Guidelines, the then-Commission conceded that objections to race- and sex-conscious affirmative action were “based upon the principles of title VII.” 29 CFR 1608.1. Nevertheless, the then-Commission invoked legislative intent as a limitation on those principles. Namely, the then-Commission opined that Title VII exists “to overcome the effects of past and present employment practices which are part of a larger pattern of restriction, exclusion, discrimination, segregation and inferior treatment of minorities and women in many areas of life.” 44 FR 4422, 4422 (Jan. 19, 1979). From this, the then-Commission reasoned that one of Congress's purposes in enacting Title VII was “to improve the economic and social conditions of minorities and women by providing equality of opportunity in the work place.” 29 CFR 1608.1. To further this purported legislative intent, the then-Commission concluded that “appropriate voluntary affirmative action, or affirmative action pursuant to an administrative or judicial requirement, does not constitute unlawful discrimination in violation of [Title VII].” 44 FR at 4422.</P>
                <P>
                    In response to commentators who argued that the proposed affirmative action guidelines violated the text of Title VII—specifically, that “Title VII requires that all employment decisions be made without any consideration of race, color, religion, sex, or national origin, regardless of the circumstances”—the then-Commission concluded that such a view of Title VII “does not comport with” the then recent position taken by the Supreme Court on affirmative action in college admissions in 
                    <E T="03">Regents of the University of California</E>
                     v. 
                    <E T="03">Bakke,</E>
                     438 U.S. 265 (1978). 44 FR at 4423. And as discussed in section B.1, below, the then-Commission found additional support in two Supreme Court Title VII decisions, 
                    <E T="03">Albemarle Paper Company</E>
                     v. 
                    <E T="03">Moody,</E>
                     422 U.S. 405 (1975), and 
                    <E T="03">Griggs</E>
                     v. 
                    <E T="03">Duke Power Company,</E>
                     401 U.S. 424 (1971).
                </P>
                <P>
                    Once finalized, the Guidelines were offered to the public as the Commission's “written interpretation and opinion” pursuant to Section 713(b)(1) of Title VII. 29 CFR 1608.2.
                    <SU>1</SU>
                    <FTREF/>
                     Therefore, employers who entered into affirmative action plans or programs in good faith and in conformity with the Guidelines were afforded 713(b) protection if the underlying unlawful employment practice complained of was a result of such a plan. 
                    <E T="03">Id.</E>
                     § 1608.4. As such, pursuant to Section 713(b) of Title VII, the Guidelines provided a statutory defense to claims brought against employers and other covered entities that relied on the Guidelines in good faith and took race- or sex-conscious action in conformance with them.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Pursuant to 713(b), if an employer pleads and proves that the alleged unlawful employment practice complained of was “in good faith, in conformity with, and in reliance on any written interpretation or opinion of the Commission,” then it “shall not be subject to any liability or punishment for or on account of the [practice].” 42 U.S.C. 2000e-12(b).
                    </P>
                </FTNT>
                <P>
                    The Guidelines also set forth the elements of an affirmative action plan under the Guidelines, 29 CFR 1608.4, as well as other scenarios in which the then-Commission believed an employer lawfully could have an affirmative action plan—such as pursuant to the now-revoked Executive Order (“E.O.”) 11246, 29 CFR 1608.5; a Commission conciliation or settlement agreement, 
                    <E T="03">id.</E>
                     § 1608.6; a state or local law, 
                    <E T="03">id.</E>
                     § 1608.7; a court order, 
                    <E T="03">id.</E>
                     § 1608.8; or reliance on the directive of a government agency, 
                    <E T="03">id.</E>
                     § 1608.9—and outlined what must be shown in those circumstances in order for an employer to try to use such an affirmative action plan as a defense. For example, the Guidelines state, for 713(b)(1) to apply, specific portions of an affirmative action plan needed to be dated and in writing—noting absence of such “may make it more difficult to provide credible evidence that . . . [the alleged unlawful action] was taken pursuant to a plan or program.” 29 CFR 1608.4. Once a respondent to a charge pleads “that the challenged action was taken pursuant to and in accordance with a plan or program which was adopted or implemented in good faith, in conformity with, and in reliance upon [the] Guidelines,” and specific portions “are in writing,” then “the Commission will determine whether the assertion is true.” 29 CFR 1608.10(b). If the Commission so finds, the Commission will issue a no reasonable cause determination and “will advise the respondent that: (1) The Commission has found that the respondent is entitled to the protection of section 713(b)(1) of Title VII; and (2) That the determination is itself an additional written interpretation or opinion of the Commission pursuant to 713(b)(1).” 
                    <E T="03">Id.</E>
                     For those affirmative action plans or programs not specifically relying on the Guidelines, the Guidelines provide that if a respondent asserts as a defense to a charge of discrimination that the underlying action was taken in accordance with an affirmative action plan of the type described in the Guidelines, the Commission will determine whether that is true and whether the program conforms with the requirements of the Guidelines. 29 CFR 1608.10(a). “If the Commission so finds, the Commission shall issue a determination of no reasonable cause” and “where appropriate, will state the determination is a written opinion of the Commission under Section 713(b)(1).” 
                    <E T="03">Id.</E>
                     The respondent then may rely on the Commission's determination for future charges alleging similar facts. 
                    <E T="03">Id.</E>
                     However, “[i]f the Commission does not so find, it will proceed with the investigation in the usual manner.” 
                    <E T="03">Id.</E>
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         On October 1, 1981, the Commission issued 
                        <E T="03">CM-607 Affirmative Action,</E>
                         providing detailed guidance on the Guidelines and instructions for EEOC processing of charges in which a respondent asserts that the challenged action was based on an affirmative action plan. The Commission has issued a separate notice rescinding 
                        <E T="03">CM-607.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Reasons for Rescinding the Guidelines</HD>
                <P>As explained more fully herein, the Commission has determined that rescission of the Guidelines is necessary because they (1) are inconsistent with the plain text of Title VII and were unsupported by Supreme Court Title VII caselaw addressing affirmative action when issued; (2) are obsolete; (3) contemplate only plans which benefit minorities and women; and (4) may conflict with subsequent caselaw and the U.S. Constitution. The totality of the reasons for rescission outweighs any potential reliance interests, which themselves are minimal.</P>
                <HD SOURCE="HD3">1. The Guidelines Are Inconsistent With the Plain Text of Title VII</HD>
                <P>
                    First, the Commission is rescinding the Guidelines because they are inconsistent with the plain text of Title VII and were not supported by any Supreme Court Title VII precedent addressing affirmative action when issued.
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         As discussed in subsequent sections, the Commission has further determined that the Guidelines should be rescinded even if they were initially justified when issued.
                    </P>
                </FTNT>
                <P>
                    The Supreme Court has repeatedly stressed that “statutory interpretation must `begi[n] with,' and ultimately 
                    <PRTPAGE P="40881"/>
                    heed, what a statute actually says.” 
                    <E T="03">Groff</E>
                     v. 
                    <E T="03">DeJoy,</E>
                     600 U.S. 447, 468 (2023) (quoting 
                    <E T="03">Nat'l Ass'n of Mfrs.</E>
                     v. 
                    <E T="03">Dep't of Def.,</E>
                     583 U. S. 109, 127 (2018)); 
                    <E T="03">see also, e.g., Babb</E>
                     v. 
                    <E T="03">Wilkie,</E>
                     589 U.S. 399, 404 (2020) (holding that “the plain meaning of the statutory text shows that age need not be a but-for cause of an employment decision in order for there to be a violation of § 633a(a)” of the Age Discrimination in Employment Act). Indeed, when the then-Commission adopted the Guidelines, it acknowledged that affirmative action had “been challenged under Title VII as inconsistent with statutory language requiring that employment decisions not be based on race [or] sex . . . considerations.” 44 FR at 4422.
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         The text of Title VII states:
                    </P>
                    <P>(a) It shall be an unlawful employment practice for an employer—</P>
                    <P>(1) to fail or refuse to hire or to discharge any individual, or otherwise to discriminate against any individual with respect to his compensation, terms, conditions, or privileges of employment, because of such individuals race . . . [or] sex . . .; or (2) to limit segregate or classify his employees or applications for employment in any way which would deprive or tend to deprive any individual of employment opportunities or otherwise adversely affect his status as an employee because of such individual's race . . . [or] sex . . .</P>
                    <P>42. U.S.C. 2000e-2(a)(1)-(2). Further, Title VII states:</P>
                    <P>Nothing contained in this subchapter shall be interpreted to require any employer, employment agency, labor organization, or joint labor management committee . . . to grant preferential treatment to an individual or to any group because of the race . . . [or] sex . . . of such individual or group on account of an imbalance which may exist with respect to the total number or percentage of persons of any race . . . [or] . . . sex . . . employed by any employer . . . in comparison with the total number of percentage of persons of such race . . . [or] sex . . . in any community, State, section, or other area, or in the available work force in any community, State, section or other area.</P>
                    <P>42 U.S.C. 2000e-2(j).</P>
                </FTNT>
                <P>In adopting the Guidelines, however, the then-Commission relied heavily on its view that the purpose of Title VII was to improve the employment opportunities of minorities and women, and as a result, notwithstanding its recognition that the same protections apply to all protected groups, the then-Commission concluded that affirmative action to benefit minorities and women was nevertheless consistent with Title VII. 29 CFR 1608.1(a).</P>
                <P>
                    When the Guidelines were issued, however, there was no Supreme Court precedent supporting the then-Commission's interpretation of Title VII. To justify its atextual interpretation of Title VII, the then-Commission relied on 
                    <E T="03">Albemarle Paper Company</E>
                     v. 
                    <E T="03">Moody,</E>
                     a backpay case dealing with employment selection tests. The then-Commission reasoned that “the Supreme Court has called upon employers [in Title VII cases] `. . . to self-examine and self-evaluate their employment practices and to endeavor to eliminate, so far as possible, the last vestiges of an unfortunate and ignominious page in this country's history' ” including through voluntary affirmative action plans. 44 FR at 4423 (citing 422 U.S. 405, 418 (1975) (quoting 
                    <E T="03">United States</E>
                     v. 
                    <E T="03">N.L. Indus., Inc.,</E>
                     479 F.2d 354, 379 (8th Cir. 1973))).
                    <SU>5</SU>
                    <FTREF/>
                      
                    <E T="03">Albemarle Paper</E>
                     did not go that far. The decision, in fact, does not address voluntary affirmative action plans at all. Rather, the decision addresses the scope of relief under Title VII that a class of employees and applicants were entitled to following a determination that their employer had used an unlawfully discriminatory employment test in hiring. 422 U.S. at 408-09.
                    <SU>6</SU>
                    <FTREF/>
                     The Court's holding on these post-liability issues is not analogous to the permissibility of pre-liability race- and sex-conscious affirmative action under Title VII.
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         The full sentence including the portion of the quote eliminated by an ellipsis states, “It is the reasonably certain prospect of a 
                        <E T="03">backpay award</E>
                         that `provide(s) the spur or catalyst which causes employers and unions to self-examine and to self-evaluate their employment practices and to endeavor to eliminate, so far as possible, the last vestiges of an unfortunate and ignominious page in this country's history.' ” 422 U.S. at 418 (emphasis added).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         In promulgating the Guidelines, the Commission also relied on 
                        <E T="03">Griggs</E>
                         v. 
                        <E T="03">Duke Power Co.,</E>
                         401 U.S. 424 (1971) generally, which addresses arbitrary employment tests that have a disproportionate effect on minorities, but, as with 
                        <E T="03">Albemarle,</E>
                         does not discuss affirmative action prophylactically.
                    </P>
                </FTNT>
                <P>
                    The Commission's reliance in the Guidelines on 
                    <E T="03">Albemarle</E>
                     for sweeping authorization to look beyond Title VII's text to remedial intent was always suspect. The Supreme Court has since made clear that any employment practice that violates the plain terms of Title VII's antidiscrimination provisions is not excused because of a benign or benevolent motive. 
                    <E T="03">Ricci</E>
                     v. 
                    <E T="03">DeStefano,</E>
                     557 U.S. 557, 579 (2009) (concluding that the employer's “ultimate aim—however well intentioned or benevolent it might have seemed”—did not change the fact that it was because of race); 
                    <E T="03">cf. Int'l Union, United Auto., Aerospace &amp; Agr. Implement Workers of Am., UAW</E>
                     v. 
                    <E T="03">Johnson Controls, Inc.,</E>
                     499 U.S. 187, 199 (1991) (concluding that “the absence of a malevolent motive does not convert a facially discriminatory policy into a neutral policy”). The EEOC's statutory authority to issue rules under Title VII is limited to procedural matters. 
                    <E T="03">See</E>
                     42 U.S.C. 2000e-12(a) (“The Commission shall have authority from time to time to issue, amend, or rescind suitable procedural regulations to carry out the provisions of this subchapter.”); 
                    <E T="03">Gen. Elec. Co.</E>
                     v. 
                    <E T="03">Gilbert,</E>
                     429 U.S. 125, 141 (1976) (“Congress, in enacting Title VII, did not confer upon the EEOC authority to promulgate rules or regulations pursuant to . . . Title [VII].” (citing 
                    <E T="03">Albemarle</E>
                     v. 
                    <E T="03">Moody,</E>
                     422 U.S. at 431)). And regardless of the Commission's Title VII enforcement authority, the Guidelines may conflict with the “single, best meaning” of Title VII as reflected in binding Supreme Court precedent. 
                    <E T="03">Loper Bright Enters.</E>
                     v. 
                    <E T="03">Raimondo,</E>
                     603 U.S. 369, 400 (2024). The issuance of the Guidelines therefore may have exceeded the Commission's authority.
                </P>
                <HD SOURCE="HD3">2. The Guidelines Are Obsolete</HD>
                <P>
                    Second, the Commission is rescinding the Guidelines because they are obsolete given the caselaw that has developed since their issuance. In the 46-plus years since the Guidelines were issued, a copious amount of caselaw has developed addressing when, if ever at all, an employer may lawfully engage in voluntary affirmative action. 
                    <E T="03">See generally</E>
                     Barbara T. Lindemann et al., Employment Discrimination Law, Chapter 38 (6th ed. 2021) (providing overview of caselaw on affirmative action); 
                    <E T="03">see, e.g., Ames</E>
                     v. 
                    <E T="03">Ohio Dep't of Youth Servs.,</E>
                     605 U.S. 303 (2025); 
                    <E T="03">Students for Fair Admissions, Inc.</E>
                     v. 
                    <E T="03">President &amp; Fellows of Harvard Coll. (SFFA),</E>
                     600 U.S. 181 (2023); 
                    <E T="03">Ricci</E>
                     v. 
                    <E T="03">DeStefano,</E>
                     557 U.S. 557 (2009); 
                    <E T="03">Johnson</E>
                     v. 
                    <E T="03">Transp. Agency,</E>
                     480 U.S. 616 (1987); 
                    <E T="03">United States Steel Workers of Am. AFL-CIO-CLC</E>
                     v. 
                    <E T="03">Weber,</E>
                     433 U.S. 193 (1979); 
                    <E T="03">see also, e.g., Taxman</E>
                     v. 
                    <E T="03">Bd. of Educ.,</E>
                     91 F.3d 1547 (3d Cir. 1996). This caselaw has rendered the Guidelines obsolete. In evaluating a charge of discrimination involving an affirmative action plan, the proper inquiry is whether the charging party has been subjected to discrimination prohibited by Title VII, as determined by binding legal authority, not whether the respondent's affirmative action plan conforms to guidelines that were issued before the Supreme Court had ever addressed the permissibility of affirmative action under Title VII. Because the Guidelines “encourage” affirmative action benefiting minorities and women, their rescission is also consistent with Executive Order 14173, “Ending Illegal Discrimination and Restoring Merit-Based Opportunity” (Jan. 21, 2025), which revoked Executive Order 11246.
                </P>
                <P>
                    Even assuming, 
                    <E T="03">arguendo,</E>
                     the Guidelines were ever justified, the Supreme Court has recognized that explicitly race-based actions are inherently suspect and their use must be limited in duration and have a clear end date. 
                    <E T="03">Cf. SFFA,</E>
                     600 U.S. at 212 
                    <PRTPAGE P="40882"/>
                    (concluding that a “race conscious” college admissions program must have an “end point”); 
                    <E T="03">id.</E>
                     at 314 (Kavanaugh, J., concurring) (stating that in 
                    <E T="03">Grutter,</E>
                     the Court did not exempt college admissions from the requirement that “all governmental use of race must have a logical end point” and that this requirement “assures all citizens that the deviation from the norm of equal treatment of all racial and ethnic groups is a temporary matter” (quoting 
                    <E T="03">Grutter</E>
                     v. 
                    <E T="03">Bollinger,</E>
                     539 U.S. 306, 342 (2003))). Because more than four decades have passed since the Guidelines were adopted, their “end point” has surely been reached, if not far surpassed, and they must be rescinded.
                </P>
                <P>
                    Moreover, the historical and cultural factors that gave rise to affirmative action programs in the immediate wake of the civil rights advancements of the 1960s are simply not present in 2026. The societal context today is different. 
                    <E T="03">Cf. SFFA,</E>
                     600 U.S. at 213 (noting that twenty years earlier it had held that it expected that in twenty-five years “racial preferences [in college admissions] will no longer be necessary to further the interest approved today”). As with college admissions, in the employment context, the interests advanced when the Guidelines were adopted in 1979 that were purported to have justified race-conscious affirmative action programs, even if present then, are simply not present today. The Guidelines remain frozen in time and cannot account for the more than 60 years of progress made under Title VII towards equal employment opportunity.
                    <SU>7</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         By way of contrast, the latest Supreme Court decision addressing affirmative action under Title VII was issued almost 40 years ago in 1987. 
                        <E T="03">See Johnson</E>
                         v. 
                        <E T="03">Transp. Agency,</E>
                         480 U.S. 616 (1987). Much more recently, the Supreme Court has rejected the use of race to provide advantage in another context. 
                        <E T="03">See, e.g., SFFA,</E>
                         600 U.S. 181 (2023) (finding considerations of race in admissions at two universities violated the Fourteenth Amendment and/or Title VI of the Civil Rights Act of 1964).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">3. The Guidelines Provide a Defense for Affirmative Action Efforts on Behalf of Only Women and Minorities</HD>
                <P>
                    Third, the Guidelines facially and impermissibly endorse only those affirmative action plans aimed at remedying past discrimination against minorities or women. 
                    <E T="03">See, e.g.,</E>
                     29 CFR 1608.1(a) (stating that employers must continue to change practices to “improve employment opportunities for minorities and women” and that the Guidelines were being issued to allow “affirmative action to [be] undertaken to improve the conditions of minority and women” because the Commission did not believe that Congress intended to “immobilize or reduce the efforts of many who would otherwise take action to improve the opportunities of minority and women without litigation”); 
                    <E T="03">id.</E>
                     § 1608.1(c) (“Voluntary affirmative action to improve opportunities for minorities and women must be encouraged and protected . . . .”); 
                    <E T="03">id.</E>
                     § 1608.1(d) (“These Guidelines describe the circumstances in which persons subject to title VII may take or agree upon action to improve employment opportunities of minorities and women . . . .”). Clearly, the Guidelines were promulgated for the express purpose of protecting affirmative action only on behalf of women and minorities.
                </P>
                <P>To the extent specific provisions, such as 29 CFR 1608.3, might be read in isolation to potentially authorize affirmative action plans for persons other than women and minorities, such a reading would be incongruent with the singular rationale set forth in Section 1608.1 for the adoption of the Guidelines as protecting affirmative action plans for women and minorities. The regulatory text is explicit that at the time of the Guidelines' adoption, affirmative action was understood as supporting only women and minorities.</P>
                <P>
                    Moreover, Section 1608.5 incorporates affirmative action plans created by federal contractors pursuant to the now-revoked E.O. 11246.
                    <SU>8</SU>
                    <FTREF/>
                     Those plans are likewise limited to women and minorities. 
                    <E T="03">See</E>
                     41 CFR 60-2.10-2.17. Thus, any E.O. 11246 affirmative action plan defense contemplated by 29 CFR 1608.5 necessarily would be available only for women and minority affirmative action programs, and not those supporting any other category of individuals.
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         E.O. 11246 was revoked on January 21, 2025, by E.O. 14173, “Ending Illegal Discrimination and Restoring Merit-Based Opportunity.”
                    </P>
                </FTNT>
                <P>Notably, the Department of Labor has issued a notice of intent to rescind its regulations implementing now-revoked E.O. 11246. Those regulations are foundational to the plans endorsed in Section 1608.5 of the Guidelines and to the “self-analysis” mandated by Section 1608.4 (“The employer may utilize techniques used in order to comply with E.O. 11246, as amended, and its implementing regulations, including 41 CFR part 60-2 (known as Revised Order 4), or related orders issued by the Office of Federal Contract Compliance Programs . . . .”). The Guidelines therefore incorporate an Executive Order and regulatory scheme that no longer have any valid authorizing source of law, which further supports rescission of the Guidelines.</P>
                <P>
                    Because the Guidelines provide a defense for affirmative action efforts on behalf of only women and minorities, they result in different standards for “majority-group” individuals to prove Title VII discrimination where an employer asserts this defense. In June 2025, the Supreme Court unanimously held that the evidentiary standard for proving disparate treatment under Title VII does not depend on whether a plaintiff is a member of a “minority group” or “majority group.” 
                    <E T="03">Ames,</E>
                     605 U.S. at 310. Rather, Title VII provides the “same protections for every `individual.' ” 
                    <E T="03">Id.</E>
                     Because the Guidelines are limited to affirmative action plans to improve opportunities for minorities and women, they provide less protection to majority-group employees, which may be contrary to 
                    <E T="03">Ames</E>
                     and the text of Title VII.
                </P>
                <P>
                    In limiting protections to affirmative action plans that favor certain groups because of their race, national origin, and sex, the Guidelines also implicate constitutional equal protection guarantees. Government actions that involve race- and sex-based classifications are subject to heightened scrutiny under the Constitution. 
                    <E T="03">See United States</E>
                     v. 
                    <E T="03">Skrmetti,</E>
                     605 U.S. 495, 510 (2025) (contrasting strict scrutiny (race, alienage, national origin) and intermediate scrutiny (sex) with rational basis review). It is highly questionable whether the Commission could establish that it had constitutionally adequate reasons for the 
                    <E T="03">categorical</E>
                     exclusion of men and those in a racial majority, 
                    <E T="03">i.e.,</E>
                     Whites, at the time it issued the Guidelines, much less that the exclusion continues to be justified decades later. If an employer were able to establish that an affirmative action plan to address purported “under-representation” of men or white individuals from the workplace that met the Guidelines' requirements, it is not clear why such an affirmative action plan for men or White individuals should not be entitled to the same protections as those for minorities or women. 
                    <E T="03">Cf. SFFA,</E>
                     600 U.S. at 206 (stating, in the context of a case addressing the constitutionality of affirmative action in college admissions, that “[e]liminating racial discrimination means eliminating all of it” and that “the Equal Protection Clause applies `without regard to any differences of race, of color, or of nationality'—it is `universal in [its] application' ” (quoting 
                    <E T="03">Yick Wo</E>
                     v. 
                    <E T="03">Hopkins,</E>
                     118 U.S. 356, 369 (1886))); 
                    <E T="03">see also Frank</E>
                     v. 
                    <E T="03">Xerox Corp.,</E>
                     347 F.3d 130, 137 (5th Cir. 2003) (employer's affirmative action efforts to correct underrepresentation of Whites in 
                    <PRTPAGE P="40883"/>
                    its workforce constituted unlawful discrimination against Black employees).
                </P>
                <P>As discussed in the next section, even if the Guidelines were not limited to affirmative action benefiting women and minorities, they still would be suspect given the sea change in caselaw addressing the legality of affirmative action programs since the Guidelines were issued.</P>
                <HD SOURCE="HD3">4. The Guidelines Potentially Conflict With Subsequent Caselaw and the Constitution</HD>
                <P>
                    Fourth, aside from the limitation to minorities and women, other aspects of the Guidelines potentially conflict with subsequent caselaw and the U.S. Constitution. For example, in 
                    <E T="03">Ricci</E>
                     v. 
                    <E T="03">DeStefano,</E>
                     557 U.S. 557, 579-80 (2009), the Supreme Court faulted the district court for concluding that a city's decision to reject test scores was not discriminatory even though the city took the action solely because the higher-scoring candidates were White. Even if the city rejected the results to avoid disparate impact liability, the Court explained, its decision was nevertheless based on race. In an amicus brief filed by the United States, and joined by the then-Commission, the government argued that an employer's refusal to certify test results does not violate Title VII's disparate treatment provision when based on a reasonable belief that the test violates Title VII's disparate impact provision, and for support, the government pointed to 29 CFR 1608.4(b)(1) and (3). Brief for the United States as Amicus Curiae Supporting Vacatur and Remand, 
                    <E T="03">Ricci</E>
                     v. 
                    <E T="03">DeStefano,</E>
                     557 U.S. 557 (2009) (Nos. 07-1428, 08-328). The Supreme Court disagreed, concluding that an employer is permitted to engage in intentional discrimination only if it has a “strong basis in evidence” to believe that the action was necessary to avoid disparate-impact liability. The Guidelines do not require that an employer use a “strong basis in evidence” standard for past unlawful discrimination remedied through a race-conscious employment decision-making framework such as affirmative action. Although 29 CFR 1608.3 discusses circumstances in which an employer may appropriately engage in voluntary affirmative action, the Guidelines do not impose any particular evidentiary standard that the employer must meet in making this determination.
                    <SU>9</SU>
                    <FTREF/>
                      
                    <E T="03">Ricci</E>
                     states that in order to take actions based on race under Title VII—including those intended to remedy past discrimination—an employer must meet an exacting evidentiary standard that the Guidelines do not require. Thus, the Guidelines may be inconsistent with 
                    <E T="03">Ricci.</E>
                    <SU>10</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         Section 1608.3(a) allows affirmative action where a policy has an adverse effect where it “ `[t]end[s] to deprive' persons of equal employment opportunities.” Certainly the “tends to deprive” standard falls short of 
                        <E T="03">Ricci'</E>
                        s “strong basis in evidence” standard. And § 1608.3(b), allowing affirmative action “to correct the effects of prior discriminatory practices,” and § 1608.3(c), allowing affirmative action where there is a historically limited labor pool, contain no evidentiary standards that an employer must meet to show these circumstances exist.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         In E.O. 14281, 
                        <E T="03">Restoring Equality of Opportunity and Meritocracy</E>
                         (Apr. 23, 2025), President Donald Trump criticized disparate-impact liability and stated 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.” Because the EEOC is not required to provide a defense under section 713(b) for employers that decide to adopt voluntary affirmative action plans, the rescission of the Guidelines aligns with the Executive Order.
                    </P>
                </FTNT>
                <P>
                    The analysis in 
                    <E T="03">Ricci</E>
                     also suggests that the Guidelines may be unconstitutional. Relying heavily on 
                    <E T="03">Ricci,</E>
                     the Department of Justice (DOJ) issued an opinion on June 9, 2026, concluding that the Guidelines are unconstitutional because they endorse the use of “racial preferences” under Title VII even though “Congress has never demonstrated that `racial classifications' under Title VII are necessary to `remediat[e] specific, identified instances of past discrimination that violated the Constitution or a statute' ” and the Guidelines “encourage racial quotas, lack any definite endpoint, rely on arbitrary and undefined racial categories, and impose burdens on other racial groups” (citations omitted)). 50 Op. O.L.C. (June 9, 2026) (slip op. at 24).
                </P>
                <P>
                    The Court's 
                    <E T="03">Ricci</E>
                     decision is part of a broader sea change in Supreme Court jurisprudence rejecting purpose-driven interpretations of anti-discrimination protections in favor of textualist and colorblind approaches that treat everyone the same without exception. 
                    <E T="03">See Callais</E>
                     v. 
                    <E T="03">Louisiana,</E>
                     145 S. Ct. 1131 (2026) (Voting Rights Act case); 
                    <E T="03">Ames,</E>
                     605 U.S. 303; 
                    <E T="03">SFFA,</E>
                     600 U.S. 181 (Equal Protection Clause case); 
                    <E T="03">Parents Involved in Cmty. Schs.</E>
                     v. 
                    <E T="03">Seattle Sch. Dist. No. 1,</E>
                     551 U.S. 701 (2007) (Equal Protection Clause case). The only affirmative action case that the then-Commission relied on in adopting the Guidelines—
                    <E T="03">Bakke,</E>
                     438 U.S. 265—was effectively overruled in 
                    <E T="03">SFFA.</E>
                     To the extent there is Supreme Court caselaw that has blessed the use of affirmative action as consistent with Title VII, 
                    <E T="03">see Weber,</E>
                     443 U.S. 193; 
                    <E T="03">Johnson,</E>
                     480 U.S. 616, the Commission is not taking a position herein on whether those decisions have been effectively overruled; the Commission defers to DOJ's position regarding that question. Regardless, that question need not be addressed here because the existence of these cases does not require that the Commission promulgate or retain outdated and unhelpful guidance, including a safe harbor, on the topic of affirmative action into perpetuity.
                </P>
                <HD SOURCE="HD3">5. Any Reliance Interests in the Guidelines Are Minimal and Are Outweighed by the Reasons for Rescission</HD>
                <P>
                    Although the rescission of the Guidelines means that employers will not be able to assert a defense under section 713(b) for actions taken pursuant to an affirmative action plan after the rescission, the Commission does not believe the rescission will have a meaningful impact on how employers will implement their Title VII responsibilities. Even when affirmative action is asserted as a potential defense in a case, it does not appear that employers rely on affirmative action plans that have been formulated to meet the requirements of the Guidelines. Rather, when an affirmative action plan has been at issue, courts have almost always looked at whether the employer has violated Title VII by adopting and implementing the plan, not whether the plan is legally insulated pursuant to the Guidelines and section 713(b). 
                    <E T="03">See generally</E>
                     Barbara T. Lindemann et al., Employment Discrimination Law, Chapter 38 (6th ed. 2021) (discussing affirmative action caselaw). Decisions addressing the Guidelines are especially rare, and the Commission has not located a decision in which a court has held that an employer was protected from liability because of its reliance on the Guidelines. Regardless, because the rescission will not be retroactive, employers will still be able to assert a defense 
                    <SU>11</SU>
                    <FTREF/>
                    —assuming, 
                    <E T="03">arguendo,</E>
                     the employer can establish all prerequisites necessary to assert such a defense—under section 713(b) for actions taken before the rescission. 
                    <E T="03">See</E>
                     29 U.S.C. 2000e-12(b) (defense is available notwithstanding that “written interpretation or opinion of the Commission” is “modified or rescinded or is determined by judicial authority to be invalid or of no legal effect” after 
                    <PRTPAGE P="40884"/>
                    employer takes challenged employment decision).
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         Whether the defense is successful will hinge on numerous factors, which the Commission does not attempt to prejudge here, including whether all conditions precedent are met and whether the alleged unlawful conduct was actually taken pursuant to said plan.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">C. Conclusion</HD>
                <P>The Commission has voted to rescind the Guidelines on Affirmative Action Appropriate Under Title VII of the Civil Rights Act of 1964, as Amended. Even when first issued, the Guidelines were suspect, given their inconsistency with the statutory text and narrow application to affirmative action benefiting women and minorities. Since the issuance of the Guidelines in 1979, the Supreme Court and numerous courts have issued a vast number of cases addressing affirmative action. That caselaw has rendered the Guidelines obsolete and also potentially legally incorrect in various respects. Rescinding the Guidelines is unlikely to significantly affect employers, given the lack of evidence that today's employers adopt affirmative action plans in reliance on the Guidelines.</P>
                <HD SOURCE="HD1">II. Procedural Issues and Regulatory Review</HD>
                <HD SOURCE="HD2">A. Administrative Procedure Act</HD>
                <P>
                    The Commission issued the Guidelines in 1979 pursuant to its authority under section 713 as a “written interpretation or opinion of the Commission” that would provide a defense to potential Title VII liability for someone who “pleads and proves that the act or omission complained of was in good faith, in conformity with, and in reliance” on the Guidelines. 42 U.S.C. 2000e-12(b). Because the Commission lacks substantive rulemaking authority, 
                    <E T="03">see id.</E>
                     § 2000e-12(a) (authorizing Commission to issue “suitable procedural regulations” only), the Guidelines merely provide the Commission's non-binding interpretations of Title VII. Recognizing this limitation, the Commission characterized the Guidelines as “Interpretative Guidelines” when they were issued, though it voluntarily underwent the notice-and-comment process before promulgation of the Guidelines.
                    <SU>12</SU>
                    <FTREF/>
                     44 FR at 4422.
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         The terms “interpretative guidelines” and “interpretive guidelines” are interchangeable, as are the terms “interpretative rules” and “interpretive rules.” The latter phrasings (“interpretive . . .”) are the more common current-day phrasings. 
                        <E T="03">See Perez</E>
                         v. 
                        <E T="03">Mortg. Bankers Ass'n,</E>
                         575 U.S. 92, 96 n.1 (2015).
                    </P>
                </FTNT>
                <P>
                    Under the Administrative Procedure Act (“APA”), agencies are not required to follow the notice-and-comment process for “interpretative rules.” 5 U.S.C. 553(b) (A). In 
                    <E T="03">Perez</E>
                     v. 
                    <E T="03">Mortgage Bankers Ass'n,</E>
                     575 U.S. 92 (2015), the Supreme Court held that the Department of Labor (“DOL”) was not required to follow notice-and-comment procedures when it rescinded an interpretive rule in the form of an opinion letter that had interpreted an administrative exemption as applying to mortgage-loan officers.
                    <SU>13</SU>
                    <FTREF/>
                     The Court held that the APA exception in § 4 of the APA (5 U.S.C. 553) is “
                    <E T="03">categorical.</E>
                    ” 
                    <SU>14</SU>
                    <FTREF/>
                     575 U.S. at 100 (emphasis added). As a result, courts “lack authority `to impose upon [an] agency its own notion of which procedures are `best' or most likely to further some vague, undefined public good.' ” 
                    <E T="03">Id.</E>
                     at 102 (quoting 
                    <E T="03">Vermont Yankee Nuclear Power Corp.</E>
                     v. 
                    <E T="03">Nat. Res. Def. Council, Inc.,</E>
                     435 U.S. 519, 549 (1978)).
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         Similar to the EEOC's Affirmative Action Guidelines, the DOL opinion letter at issue in 
                        <E T="03">Perez</E>
                         provided a defense to liability for employers that had relied on the letter in good faith. Section 258 of the Portal-to-Portal Act provides: 
                    </P>
                    <P>[N]o employer shall be subject to any liability or punishment for or on account of the failure of the employer to pay minimum wages or overtime compensation under the Fair Labor Standards Act of 1938, as amended, . . . if he pleads and proves that the act or omission complained of was in good faith in conformity with and in reliance on any administrative regulation, order, ruling, approval, or interpretation, of any agency of the United States, or any administrative practice or enforcement policy of any such agency with respect to the class of employers to which he belonged. </P>
                    <P>29 U.S.C. 258.</P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         The Supreme Court stated in 
                        <E T="03">Perez:</E>
                         “[T]he D.C. Circuit correctly read § 2 [5 U.S.C. 551] of the APA to mandate that agencies use the same procedures when they amend or repeal a rule as they used to issue the rule in the first instance.” 575 U.S. at 101. This statement should not be understood to mean that an agency must use notice-and-comment procedures to rescind a document that the agency 
                        <E T="03">voluntarily</E>
                         decided to use in adopting the document. This statement relates only to the definition of “rule making” in 5 U.S.C. 551(5), which, as explained by the Court, does not “say what procedures an agency must use when it engages in rulemaking.” 
                        <E T="03">Id.</E>
                         Those required procedures are in § 4 (5 U.S.C. 553), which the Court concluded 
                        <E T="03">categorically</E>
                         exempts interpretive rules from notice-and-comments requirements. Thus, notice-and-comment procedures are not required for the rescission of interpretive rules even if those procedures were used when the rules were adopted. 
                        <E T="03">See</E>
                         Rescission of Procedures for Implementing the National Environmental Policy Act, 90 FR 29,453, 29,455 (July 3, 2025) (agency voluntarily provided notice-and-comment opportunity to respond to interim final rule: “As the Supreme Court has held, where notice-and-comment procedures are not required, prior use of them in promulgating a rule does not bind the agency to use such procedures in repealing it.” (citing 
                        <E T="03">Perez,</E>
                         575 U.S. at 101)).
                    </P>
                </FTNT>
                <P>
                    Likewise here, under both the APA and 
                    <E T="03">Perez,</E>
                     the Commission rescinds the Guidelines without notice and comment. Although the Guidelines were issued after notice and comment, the Commission has voted to approve a final rescission of the Guidelines without following the same process. When the Commission proposed the Guidelines, it followed notice-and-comment procedures because it believed “public comment would be useful,” not that it was required. 42 FR at 64,826. As discussed above, the Commission has identified multiple compelling justifications for rescinding the Guidelines, and therefore, determines that they should be rescinded expeditiously without notice and comment.
                </P>
                <HD SOURCE="HD2">B. Review Under Executive Order 14192</HD>
                <P>The Commission has examined this rescission and has determined that it is consistent with the policies and directives outlined in E.O. 14192, “Unleashing Prosperity Through Deregulation.” This rescission is expected to be an E.O. 14192 deregulatory action.</P>
                <HD SOURCE="HD2">C. Review Under Executive Order 12866 (as Amended by Executive Order 14215)</HD>
                <P>The Commission has complied with the principles in section 1(b) of E.O. 12866, as amended by E.O. 14215, Regulatory Planning and Review. This rescission is not a “significant regulatory action” under section 3(f) of the Executive Order and does not require an assessment of potential costs and benefits under section 6(a)(3) of the Executive Order.</P>
                <HD SOURCE="HD2">D. Review Under Paperwork Reduction Act</HD>
                <P>The Paperwork Reduction Act (44 U.S.C. chapter 35) (“PRA”) applies to Federal collections of information when an agency creates a new paperwork burden on regulated entities or modifies an existing burden. This rescission imposes no new information collection requirements on the public, and therefore it will create no new paperwork burdens or modifications to existing burdens that are subject to review by the Office of Management and Budget under the PRA.</P>
                <HD SOURCE="HD2">E. Unfunded Mandates Reform Act of 1995</HD>
                <P>This rescission will not result in the expenditure by State, local, or Tribal governments, in the aggregate, or by the private sector, of $100 million or more in any one year and it will not significantly or uniquely affect small governments. Therefore, no actions were deemed necessary under the provisions of the Unfunded Mandates Reform Act of 1995, 2 U.S.C. 1501, 1532(a).</P>
                <HD SOURCE="HD2">F. 29 CFR Part 1695</HD>
                <P>
                    Commission regulations at part 1695 of title 29 of the CFR provide procedures that generally apply to a “guidance document,” which is defined as “any statement of Commission policy or interpretation concerning a statute, regulation, or technical matter within its 
                    <PRTPAGE P="40885"/>
                    jurisdiction that is intended to have general applicability and future effect, but which is not intended to be binding in its own right and is not otherwise required by statute to satisfy the rulemaking procedures specified in 5 U.S.C. 553 or 5 U.S.C. 556.”
                </P>
                <P>
                    The Commission has determined that the rescission of the Guidelines does not constitute a “guidance document,” and therefore, the procedures in CFR part 1695 do not apply to the rescission. In issuing the Guidelines, the Commission “made a statement of Commission policy or interpretation concerning a statute, regulation, or technical matter.” However, in merely rescinding the Guidelines 
                    <E T="03">without replacing them with a different</E>
                     “statement of Commission policy or interpretation,” the Commission is not issuing a “guidance document.”
                </P>
                <P>
                    This understanding is confirmed by the specific requirements of part 1695, which contemplate that the procedures will apply only when the Commission affirmatively makes a “statement of Commission policy or interpretation” and not when the Commission rescinds such a statement. Other provisions refer either to the “repeal” or “rescission” of guidance, thereby distinguishing rescission of guidance from its adoption. 
                    <E T="03">See</E>
                     29 CFR 1695.7(a), (e); 29 CFR 1695.8(d); 29 CFR 1695.9.
                </P>
                <P>
                    Excluding rescissions from 29 CFR part 1695 is also consistent with Executive Order 13891, which prompted the issuance of 29 CFR part 1695. Executive Order 13891 targeted the issuance of agency documents that regulate stakeholders, including the potential misuse of guidance documents to impose binding legal requirements. 
                    <E T="03">See</E>
                     Exec. Order No. 13891, Sec. 1 (Oct. 15, 2019) (“Americans deserve an open and fair regulatory process that imposes new obligations on the public only when consistent with applicable law and after an agency follows appropriate procedures.”), 
                    <E T="03">rescinded by</E>
                     Exec. Order 13992 (Jan. 20, 2021) (
                    <E T="03">rescinded by</E>
                     Exec. Order 14148 (Jan. 20, 2025). Executive Order 13891 required agencies to adopt procedures ensuring that they do not issue documents that improperly regulate stakeholders. The exclusion of guidance rescissions from 29 CFR part 1695 is consistent with the policy of that Executive Order.
                </P>
                <HD SOURCE="HD2">G. Congressional Review Act</HD>
                <P>Out of an abundance of caution, the Commission has submitted this document for review under 5 U.S.C. 801.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 29 CFR Part 1608</HD>
                    <P>Affirmative action plans, Equal employment opportunity.</P>
                </LSTSUB>
                <PART>
                    <HD SOURCE="HED">PART 1608—[REMOVED AND RESERVED]</HD>
                </PART>
                <REGTEXT TITLE="29" PART="1608">
                    <AMDPAR>For the reasons discussed in the preamble, and under the authority of 42 U.S.C. 2000e-12(b), the Commission removes and reserves 29 CFR part 1608.</AMDPAR>
                </REGTEXT>
                <SIG>
                    <DATED>Signed this 1st day of July, 2026.</DATED>
                    <NAME>Andrea R. Lucas,</NAME>
                    <TITLE>Chair, Equal Employment Opportunity Commission.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13637 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6570-01-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <CFR>33 CFR Part 100</CFR>
                <DEPDOC>[Docket No. USCG-2026-0881]</DEPDOC>
                <SUBJECT>Special Local Regulations; Marine Events Within the Coast Guard East District</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notification of enforcement of regulation.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Coast Guard will enforce special local regulations for the 2026 Tiki Lee's Shootout on the River Airshow from July 10 to 12, 2026, to provide for the safety of life on navigable waterways during this event. Our regulation for marine events within the Coast Guard East District identifies the regulated area for this event in Sparrows Point, MD. During the enforcement periods, the operator of any vessel near the aerobatics box must comply with directions from the Patrol Commander or any Official Patrol displaying a Coast Guard ensign.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The regulations in 33 CFR 100.501 will be enforced from 4 p.m. to 7 p.m. on July 10, 2026, and from 1 p.m. to 4 p.m. on July 11, 2026, and July 12, 2026.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        If you have questions about this rule, contact MST2 Natasha M. Hand, Sector Maryland—NCR, Waterways Management Division, U.S. Coast Guard: telephone 410-576-2596, email 
                        <E T="03">MDNCRMarineEvents@uscg.mil.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Coast Guard will enforce special local regulations in 33 CFR 100.501 for the 2026 Tiki Lee's Shootout on the River Air Show regulated area from 4 p.m. to 7 p.m. on July 10, 2026, and from 1 p.m. to 4 p.m. on July 11, 2026, and July 12, 2026. This action is being taken to provide for the safety of life on navigable waterways during this 3-day event. Our regulation for marine events within the Coast Guard East District, § 100.501, specifies the location of the Aerobatics Box for the Air Show which encompasses portions of the Back River. During the enforcement periods, as reflected in § 100.501(c), if you are the operator of a vessel in the regulated area you must comply with directions from the Patrol Commander or any Official Patrol displaying a Coast Guard ensign.</P>
                <SIG>
                    <DATED>Dated: June 26, 2026.</DATED>
                    <NAME>Patrick C. Burkett,</NAME>
                    <TITLE>Captain, U.S. Coast Guard, Captain of the Port, Sector Maryland—National Capital Region.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13554 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-04-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <CFR>33 CFR Part 100</CFR>
                <DEPDOC>[Docket Number USCG-2026-0804]</DEPDOC>
                <RIN>RIN 1625-AA08</RIN>
                <SUBJECT>Special Local Regulation; Marine Events Within the USCG East District</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Temporary final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Coast Guard is establishing a temporary special local regulation (SLR) for certain waters of the Tred Avon River near Oxford, Maryland. This action is necessary to provide for the safety of life on these navigable waters near Oxford, MD during a power boat racing event on July 18, 2026. In the event of inclement weather, the event will take place on July 19, 2026. This regulation prohibits persons and vessels from entering the regulated area unless specifically authorized by the Captain of the Port Sector Maryland—National Capital Region or their designated representative.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This rule is effective from 12:30 p.m. on July 18, 2026, through 3 p.m. on July 19, 2026. It will only be subject to enforcement, however, between 12:30 p.m. and 3 p.m. on one of those two days. Weather permitting, it will be subject to enforcement, on July 18, 2026. In the event of inclement weather, it will be subject to enforcement on July 19, 2026.</P>
                </EFFDATE>
                <ADD>
                    <PRTPAGE P="40886"/>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        To view available documents go to 
                        <E T="03">https://www.regulations.gov</E>
                         and search for USCG-2026-0804.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        If you have questions about this rule, contact MST2 Natasha Hand, Sector Maryland—NCR, Waterways Management Division, U.S. Coast Guard: telephone 410-576-2596, or email 
                        <E T="03">MDNCRWaterways@uscg.mil.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Table of Abbreviations</HD>
                <EXTRACT>
                    <FP SOURCE="FP-1">CFR Code of Federal Regulations</FP>
                    <FP SOURCE="FP-1">COTP Captain of the Port</FP>
                    <FP SOURCE="FP-1">DHS Department of Homeland Security</FP>
                    <FP SOURCE="FP-1">FR Federal Register</FP>
                    <FP SOURCE="FP-1">NPRM Notice of proposed rulemaking</FP>
                    <FP SOURCE="FP-1">§ Section </FP>
                    <FP SOURCE="FP-1">SLR Special Local Regulation</FP>
                    <FP SOURCE="FP-1">U.S.C. United States Code</FP>
                </EXTRACT>
                <HD SOURCE="HD1">II. Background and Authority</HD>
                <P>The Coast Guard received a request under 33 CFR 100.15 from the Smith Island Crab Skiff Association for a Marine Event Permit to host Historic Smith Island crab skiff races. The event will be held from 1 p.m. through 2:30 p.m. on July 18, 2026, in and around Oxford, MD. The power boat race will consist of three heats with approximately 6 22-foot-long boats in each race, competing on a designated, marked course.</P>
                <P>The Captain of the Port, Sector Maryland—National Capital Region is issuing this Special Local Regulation (SLR) under the authority in 46 U.S.C. 70041. The COTP has determined that potential hazards associated with the power boat race, such as the risk of collisions, would be a safety concern for anyone intending to participate in this event and for vessels that operate within the specified waters of the Tred Avon River. The purpose of this rule is to protect event participants, non-participants, and transiting vessels before, during, and after the scheduled event.</P>
                <P>As is authorized by 5 U.S.C. 553(b)(B), the Coast Guard finds that good cause exists for not publishing a notice of proposed rulemaking (NPRM) with respect to this rule because it is impracticable to publish an NPRM, consider and respond to comments, and publish a final rule within the time if we are to establish this SLR by July 18, 2026, to protect personnel, vessels, and the marine environment. Therefore, we have do not have enough time to solicit and respond to comments.</P>
                <P>
                    For the same reasons, the Coast Guard finds that under 5 U.S.C. 553(d)(3), good cause exists for making this rule effective less than 30 days after publication in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <HD SOURCE="HD1">III. Discussion of the Rule</HD>
                <P>This rule establishes a temporary SLR which will be subject to enforcement from 12:30 p.m. through 3 p.m. on July 18, 2026. Alternatively, and in the event of inclement weather, the SLR will only be subject to enforcement from 12:30 p.m. through 3 p.m. on July 19, 2026. The SLR will cover certain waters of the Tred Avon River near Oxford, Maryland. The coordinates of these waters are provided in the rule text, at the end of this document. No vessel or person other than those that are registered with the event host as participants will be permitted to enter the regulated area without obtaining permission from the COTP or their designated representative.</P>
                <HD SOURCE="HD1">IV. Regulatory Analyses</HD>
                <P>We developed this rule after considering numerous statutes and Executive orders related to rulemaking. Below we summarize our analyses based on a number of these statutes and Executive orders.</P>
                <HD SOURCE="HD2">A. Impact on Small Entities</HD>
                <P>The regulatory flexibility analysis provisions of the Regulatory Flexibility Act of 1980, 5 U.S.C. 601-612, do not apply to rules that are not subject to notice and comment. Because the Coast Guard has, for good cause, waived the notice and comment requirement that would otherwise apply to this rulemaking, the Regulatory Flexibility Act's flexibility analysis provisions do not apply here.</P>
                <P>
                    Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121), if this rule will affect your small business, organization, or governmental jurisdiction and you have questions, contact the person listed in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section. Small businesses may send comments to the Small Business and Agriculture Regulatory Enforcement Ombudsman and the Regional Small Business Regulatory Fairness Boards by calling 1-888-REG-FAIR (1-888-734-3247). The Coast Guard will not retaliate against small entities that question or complain about this rule or any policy or action of the Coast Guard.
                </P>
                <HD SOURCE="HD2">B. Collection of Information</HD>
                <P>This rule will not call for a new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520).</P>
                <HD SOURCE="HD2">C. Federalism and Indian Tribal Governments</HD>
                <P>We have analyzed this rule under Executive Order 13132, Federalism, and have determined that it is consistent with the fundamental federalism principles and preemption requirements described in that Order.</P>
                <P>Also, this rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it does not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes.</P>
                <HD SOURCE="HD2">D. Unfunded Mandates Reform Act</HD>
                <P>As required by The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538), the Coast Guard certifies that this rule will not result in an annual expenditure of $100,000,000 or more (adjusted for inflation) by a State, local, or tribal government, in the aggregate, or by the private sector.</P>
                <HD SOURCE="HD2">E. Environment</HD>
                <P>
                    We have analyzed this rule under Department of Homeland Security Directive 023-01, Rev. 1, associated implementing instructions, and Environmental Planning COMDTINST 5090.1 (series), which guide the Coast Guard in complying with the National Environmental Policy Act of 1969 (42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ), and have determined that this action is one of a category of actions that do not individually or cumulatively have a significant effect on the human environment.
                </P>
                <P>This rule is a special local regulation. It is categorically excluded from further review under paragraph L61 of Appendix A, Table 1 of DHS Instruction Manual 023-01-001-01, Rev. 1.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 33 CFR Part 100</HD>
                    <P>Harbors, Marine safety, Navigation (water), Reporting and recordkeeping requirements, Security measures, Waterways.</P>
                </LSTSUB>
                <P>For the reasons discussed in the preamble, the Coast Guard amends 33 CFR part 100 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 100—SAFETY OF LIFE ON NAVIGABLE WATERS</HD>
                </PART>
                <REGTEXT TITLE="33" PART="100">
                    <AMDPAR>1. The authority citation for part 100 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 46 U.S.C. 70041; 33 CFR 1.05-1.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="33" PART="100">
                    <AMDPAR>2. Add § 100.T599-0804 to read as follows:</AMDPAR>
                    <SECTION>
                        <PRTPAGE P="40887"/>
                        <SECTNO>§ 100.T599-0804</SECTNO>
                        <SUBJECT>Special Local Regulation; Tred Avon River, Oxford, MD</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Location.</E>
                             This special local regulation applies to the following regulated area:
                        </P>
                        <P>
                            (1) 
                            <E T="03">Regulated area.</E>
                             All waters of the Tred Avon River, from surface to bottom, encompassed by a line connecting the following points beginning at 38°41′02.42″ N 76°10′25.71″ W, thence to 38°40′46.40″ N 76°10′25.83″ W, thence to 38°40′46.45″ N 76°10′38.03″ W, thence to 38°41′03.19″ N 76°10′37.60″ W and back to the beginning point. The race area and buffer zone are within the regulated area.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Race area.</E>
                             This area is bounded by a line commencing at position 38°41′01.56″ N 76°10′27.99″ W, thence to 38°40′47.72″ N 76°10′27.83″ W, thence to 38°40′47.62″ N 76°10′35.84″ W, thence to 38°41′01.53″ N 76°10′36.00″ W, and back to the beginning point.
                        </P>
                        <P>
                            (3) 
                            <E T="03">Buffer zone.</E>
                             The buffer zone surrounds the entire race area and is bounded by a line commencing at position 38°41′02.42″ N 76°10′25.71″ W, thence to 38°40′46.40″ N 76°10′25.83″ W, thence to 38°40′46.45″ N 76°10′38.03″ W, thence to 38°41′03.19″ N 76°10′37.60″ W and back to the beginning point.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Definitions.</E>
                             As used in this section, 
                            <E T="03">designated representative</E>
                             means a Coast Guard Patrol Commander, including a Coast Guard coxswain, petty officer, or other officer operating a Coast Guard vessel and a Federal, State, and local officer designated by or assisting the Captain of the Port Sector Maryland—National Capital Region (COTP) in the enforcement of the regulated area. 
                            <E T="03">Participant</E>
                             means all persons and vessels registered with the event sponsor as a participant in the race.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Regulations.</E>
                             (1) All non-participants are prohibited from entering, transiting through, anchoring in, or remaining within the regulated area described in paragraph (a) of this section unless authorized by the COTP or their designated representative.
                        </P>
                        <P>(2) To seek permission to enter, contact the COTP or the COTP's representative on VHF-FM channel 16 or by telephone at (410) 576-2693. Those in the regulated area must comply with all lawful orders or directions given to them by the COTP or the COTP's designated representative.</P>
                        <P>
                            (d) 
                            <E T="03">Enforcement periods.</E>
                             This section will be enforced from 12:30 p.m. through 3 p.m. on July 18, 2026. Alternatively, and in the event of inclement weather, enforcement will occur from 12:30 p.m. through 3 p.m. on July 19, 2026.
                        </P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: June 26, 2026.</DATED>
                    <NAME>Patrick C. Burkett,</NAME>
                    <TITLE>Captain, U.S. Coast Guard, Captain of the Port Maryland—National Capital Region.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13556 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-04-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <CFR>33 CFR Part 165</CFR>
                <DEPDOC>[Docket No. USCG-2026-0885]</DEPDOC>
                <SUBJECT>Safety Zones; Annual Events Requiring Safety Zones in the Captain of the Port Lake Michigan Zone</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notification of enforcement of regulation.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Coast Guard will enforce the safety zone for Super Boat Grand Prix from August 1 through August 2, 2026, to provide for the safety of life on navigable waterways during this event. Our regulation for marine events within the Great Lakes District Coast Guard identifies the regulated area for this event in Michigan City, IN. During the enforcement period listed below, entry into, transiting, or anchoring within the safety zone is prohibited unless authorized by the Captain of the Port Lake Michigan or a designated representative.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The regulation in Item 7 to Table 2 in 33 CFR 165.929 will be enforced from 9 a.m. until 5 p.m. each day from August 1, 2026 through August 2, 2026.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        If you have questions about this notification of enforcement, call or email Lieutenant Commander Jessica Anderson, Sector Lake Michigan Waterways Management Division, U.S. Coast Guard; telephone 414-747-7182, email: 
                        <E T="03">D09-SMB-SECLAKEMICHIGAN-WWM@uscg.mil.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Coast Guard will enforce the safety zone in Michigan City, IN in 33 CFR 165.929 listed in Item 7 to Table 2 for the Super Boat Grand Prix, also referred to as the RWO Great Lakes Grand Prix, from 9 a.m. to 5 p.m. on August 1 and 2, 2026. This action is being taken to provide for the safety of life on navigable waterways during this 2-day event. This safety zone consists of all water of Lake Michigan bounded by a rectangle drawn from 41°43.655′ N, 086°54.550′ W; then northeast to 41°44.808′ N, 086°51.293′ W; then northwest to 41°45.195′ N, 086°51.757′ W; then southwest to 41°44.063′ N, 086°54.873′ W; then southeast returning to the point of origin.</P>
                <P>All vessels must obtain permission from the Captain of the Port (COTP) Lake Michigan or designated on-scene representative to enter, move within, or exit this safety zone during the enforcement times listed in this notice of enforcement. Vessels and persons granted permission to enter the safety zone must obey all lawful orders or directions of the COTP Lake Michigan or designated representative. Upon being hailed by the U.S. Coast Guard by siren, radio, flashing light or other means, the operator of a vessel must proceed as directed.</P>
                <P>
                    In addition to this notification of enforcement in the 
                    <E T="04">Federal Register</E>
                    , the Coast Guard plans to provide notification of this enforcement period via the Local Notice to Mariners and marine information broadcasts. The COTP Lake Michigan may be reached by contacting the Coast Guard Sector Lake Michigan Command Center at (414) 747-7182. An on-scene designated representative may be reached via VHF-FM Channel 16.
                </P>
                <SIG>
                    <NAME>Rhianna N. Macon,</NAME>
                    <TITLE>Captain, U.S. Coast Guard, Captain of the Port Sector Lake Michigan.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13548 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-04-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <CFR>33 CFR Part 165</CFR>
                <DEPDOC>[Docket No. USCG-2026-0753]</DEPDOC>
                <SUBJECT>Safety Zones; Fireworks Displays in the USCG East District, Ocean City, NJ</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notification of enforcement of regulation.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Coast Guard will enforce a safety zone for the Ocean City “Night in Venice” Fireworks Display to provide for the safety of life on navigable waterways during this event. Our regulation for marine events within the USCG East District identifies the regulated area for this event in Ocean City, NJ. During the enforcement periods, the operator of any vessel in the regulated area must comply with directions from the Patrol Commander or any Official Patrol displaying a Coast Guard ensign.</P>
                </SUM>
                <EFFDATE>
                    <PRTPAGE P="40888"/>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The regulations in 33 CFR 165.506 for event 13 in table 1 to paragraph (h)(1) will be enforced from 9:15 p.m. until 9:30 p.m., on July 25, 2026.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        If you have questions about this notification of enforcement, call or email Petty Officer Dominick Dobridge, Waterways Management Division, Sector Delaware Bay, U.S. Coast Guard; telephone 206-815-6688, option 3, email 
                        <E T="03">SecDelBay@uscg.mil.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Coast Guard will enforce the safety zone in entry No. 13 of table 1 to paragraph (h)(1) to 33 CFR 165.506 for a fireworks display on July 25, 2026, from 9:15 p.m. to 9:30 p.m. This action is being taken to provide for the safety of life on navigable waterways during the fireworks display. The regulated area includes all waters of the Great Egg Harbor Bay within a 300-yard radius of the fireworks barge position. The approximate position for the display is latitude 39°17′24″ N, longitude 074°34′31″ W, adjacent to shoreline of Ocean City, NJ. During the enforcement period, as reflected in § 165.506(d), vessels may not enter, remain in, or transit through the safety zone unless authorized by the Captain of the Port or designated Coast Guard patrol personnel on-scene.</P>
                <P>
                    In addition to this notification of enforcement in the 
                    <E T="04">Federal Register</E>
                    , the Coast Guard plans to provide notification of this enforcement period via the Local Notice to Mariners and marine information broadcasts.
                </P>
                <SIG>
                    <NAME>Roberto Rivera,</NAME>
                    <TITLE>Captain, U.S. Coast Guard, Acting Captain of the Port, Sector Delaware Bay.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13562 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-04-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <CFR>33 CFR Part 165</CFR>
                <DEPDOC>[Docket Number USCG-2026-0805]</DEPDOC>
                <RIN>RIN 1625-AA00</RIN>
                <SUBJECT>Safety Zone; Savannah River, Savannah, GA</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Temporary final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Coast Guard is establishing a temporary safety zone for navigable waters near Elba Island Cut on the Savannah River, Savannah, GA. The safety zone is needed to protect personnel, vessels, and the marine environment from potential hazards associated with installation of submerged dredge pipelines. Entry of vessels or persons into this zone is prohibited unless specifically authorized by the Captain of the Port Savannah, or their designated representative.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This rule is effective from July 6, 2026, through July 17, 2026. For purpose of enforcement, actual notice will be used from 6 a.m. June 30, 2026, through July 6, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        To view available documents, go to 
                        <E T="03">https://www.regulations.gov</E>
                         and search for USCG-2026-0805.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        If you have questions about this rule, contact Lieutenant Anthony Harris, MSU Savannah Waterways Management Division, U.S. Coast Guard; telephone (912) 210-8714, or email 
                        <E T="03">Anthony.E.Harris@uscg.mil.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Table of Abbreviations</HD>
                <EXTRACT>
                    <FP SOURCE="FP-1">CFR Code of Federal Regulations</FP>
                    <FP SOURCE="FP-1">COTP Captain of the Port</FP>
                    <FP SOURCE="FP-1">DHS Department of Homeland Security</FP>
                    <FP SOURCE="FP-1">FR Federal Register</FP>
                    <FP SOURCE="FP-1">NPRM Notice of proposed rulemaking</FP>
                    <FP SOURCE="FP-1">§ Section </FP>
                    <FP SOURCE="FP-1">U.S.C. United States Code</FP>
                </EXTRACT>
                <HD SOURCE="HD1">II. Background and Authority</HD>
                <P>The Coast Guard received notification that Cottrell Contracting Corporation will be installing dredge pipeline within the Savannah Ship Channel at the Intracoastal Waterway confluence of the Savannah River near Elba Island Cut. Hazards from this project include but are not limited to deployment of heavy equipment which will obstruct vessel traffic, and various other activities which create underwater hazards for workers and the public. The Captain of the Port (COTP) Savannah has determined that potential hazards associated with installation of submerged pipeline are a safety concern for anyone within the work area. Therefore, the COTP is issuing this rule under the authority in 46 U.S.C. 70034, which is needed to protect personnel, vessels, and the marine environment in the navigable waters within the safety zone.</P>
                <P>Because of these potential hazards, the Coast Guard is issuing this rule without prior notice and comment. As is authorized by 5 U.S.C. 553(b)(B), the Coast Guard finds that good cause exists for not publishing a notice of proposed rulemaking (NPRM) with respect to this rule because it is impracticable. The Coast Guard received final details of this event on June 18, 2026, but we must establish this safety zone by June 30, 2026, to protect personnel, vessels, and the marine environment. Therefore, we do not have enough time to solicit and respond to comments.</P>
                <P>
                    For the same reason, the Coast Guard finds that under 5 U.S.C. 553(d)(3), good cause exists for making this rule effective less than 30 days after publication in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <HD SOURCE="HD1">III. Discussion of the Rule</HD>
                <P>This rule establishes a safety zone from 6:00 a.m. June 30, 2026, through 11:59 p.m. July 17, 2026. The day and time of enforcement will depend on the weather conditions and will be announced to the public in advance. The safety zone will cover all navigable waters in the Savannah River and Ship Channel within the following points: Point 1 at 32°04′28.6″ N 80°57′31.2″ W, thence to Point 2 at 32°04′34.1″ N 80°58′02.1″ W, thence to Point 3 at 32°03′53.0″ N 80°59′36.3″ W thence to Point 4 at 32°03′47.9″ N 80°59′33.8″ W; thence returning to Point 1. Vessels and persons will not be allowed to enter the zone during this time, unless authorized by the Captain of the Port.</P>
                <HD SOURCE="HD1">IV. Regulatory Analyses</HD>
                <P>We developed this rule after considering numerous statutes and Executive orders related to rulemaking. Below we summarize our analysis based on a number of these statutes and Executive orders.</P>
                <HD SOURCE="HD2">A. Impact on Small Entities</HD>
                <P>The regulatory flexibility analysis provisions of the Regulatory Flexibility Act of 1980, 5 U.S.C. 601-612, do not apply to rules that are not subject to notice and comment. Because the Coast Guard has, for good cause, waived the notice and comment requirement that would otherwise apply to this rulemaking, the Regulatory Flexibility Act's flexibility analysis provisions do not apply here.</P>
                <P>
                    Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121), if this rule will affect your small business, organization, or governmental jurisdiction and you have questions, contact the person listed in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section.
                </P>
                <P>
                    Small businesses may send comments to the Small Business and Agriculture Regulatory Enforcement Ombudsman and the Regional Small Business Regulatory Fairness Boards by calling 1-888-REG-FAIR (1-888-734-3247). The 
                    <PRTPAGE P="40889"/>
                    Coast Guard will not retaliate against small entities that question or complain about this rule or any policy or action of the Coast Guard.
                </P>
                <HD SOURCE="HD2">B. Collection of Information</HD>
                <P>This rule will not call for a new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520).</P>
                <HD SOURCE="HD2">C. Federalism and Indian Tribal Governments</HD>
                <P>We have analyzed this rule under Executive Order 13132, Federalism, and have determined that it is consistent with the fundamental federalism principles and preemption requirements described in that Order.</P>
                <P>Also, this rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it does not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes.</P>
                <HD SOURCE="HD2">D. Unfunded Mandates Reform Act</HD>
                <P>As required by The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538), the Coast Guard certifies that this rule will not result in an annual expenditure of $100,000,000 or more (adjusted for inflation) by a State, local, or tribal government, in the aggregate, or by the private sector.</P>
                <HD SOURCE="HD2">E. Environment</HD>
                <P>
                    We have analyzed this rule under Department of Homeland Security Directive 023-01, Rev. 1, associated implementing instructions, and Environmental Planning COMDTINST 5090.1 (series), which guide the Coast Guard in complying with the National Environmental Policy Act of 1969 (42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ), and have determined that this action is one of a category of actions that do not individually or cumulatively have a significant effect on the human environment.
                </P>
                <P>This rule is a safety zone. It is categorically excluded from further review under paragraph L60(a) of Appendix A, Table 1 of DHS Instruction Manual 023-01-001-01, Rev. 1. A Record of Environmental Consideration supporting this determination is available in the docket.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 33 CFR Part 165</HD>
                    <P>Harbors, Marine safety, Navigation (water), Reporting and recordkeeping requirements, Security measures, Waterways.</P>
                </LSTSUB>
                <P>For the reasons discussed in the preamble, the Coast Guard amends 33 CFR part 165 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 165—REGULATED NAVIGATION AREAS AND LIMITED ACCESS AREAS</HD>
                </PART>
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>1. The authority citation for part 165 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P> 46 U.S.C. 70034, 70051, 70124; 33 CFR 1.05-1, 6.04-1, 6.04-6, and 160.5; DHS Delegation No. 00170.1, Revision No. 01.4.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>2. Add § 165.T07-0805 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 165.T07-0805</SECTNO>
                        <SUBJECT>Safety Zone; Savannah River, Savannah, GA.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Location.</E>
                             The following area is a safety zone: The safety zone will cover all navigable waters in the Savannah River and Ship Channel within the following points: Point 1 at 32°04′28.6″ N 80°57′31.2″ W, thence to Point 2 at 32°04′34.1″ N 80°58′02.1″ W, thence to Point 3 at 32°03′53.0″ N 80°59′36.3″ W thence to Point 4 at 32°03′47.9″ N 80°59′33.8″ W; thence returning to Point 1. These coordinates are based on the World Geodetic System (WGS 84).
                        </P>
                        <P>
                            (b) 
                            <E T="03">Definitions.</E>
                             As used in this section, 
                            <E T="03">designated representative</E>
                             means a Coast Guard Patrol Commander, including a Coast Guard coxswain, petty officer, or other officer operating a Coast Guard vessel and a Federal, State, and local officer designated by or assisting the Captain of the Port Savannah (COTP) in the enforcement of the safety zone.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Regulations.</E>
                             (1) Under the general safety zone regulations in subpart C of this part, you may not enter the safety zone described in paragraph (a) of this section unless authorized by the COTP or the COTP's designated representative.
                        </P>
                        <P>(2) To seek permission to enter, contact the COTP or the COTP's representative on VHF-FM channel 16 or by telephone at (912) 210-8714. Those in the safety zone must comply with all lawful orders or directions given to them by the COTP or the COTP's designated representative.</P>
                        <P>
                            (d) 
                            <E T="03">Enforcement periods.</E>
                             This section will be enforced from 6 a.m. June 30, 2026, through 11:59 p.m. July 17, 2026, when dredging operations are expected to occur at the location described in paragraph (a) of this section. The Coast Guard will rely on the methods described in § 165.7 to notify the public prior to activation of any of the safety zones described in paragraph (a) of this section.
                        </P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <NAME>Dimitrios N. Wiener,</NAME>
                    <TITLE>Commander, U.S. Coast Guard, Captain of the Port Savannah.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13614 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-04-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <CFR>33 CFR Part 165</CFR>
                <DEPDOC>[Docket Number USCG-2026-0821]</DEPDOC>
                <RIN>RIN 1625-AA00</RIN>
                <SUBJECT>Safety Zone; America 250 Fireworks 2026, San Francisco, CA</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Temporary final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Coast Guard is establishing a temporary safety zone for the navigable waters in the San Francisco Bay, San Francisco, CA for July 4, 2026. The safety zone is needed to protect personnel, vessels, and the marine environment from potential hazards associated with an over water fireworks display. During the enforcement periods, entry of vessels and persons is prohibited unless specifically authorized by the Captain of the Port, Sector San Francisco, or their designated representative.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This rule is effective on July 4, 2026 from 4 a.m. until 10:30 p.m.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        To view available documents, go to 
                        <E T="03">https://www.regulations.gov</E>
                         and search for USCG-2026-0821.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        If you have questions about this rule, contact Ensign Christine Greeley, Sector San Francisco Waterways Management Division, U.S. Coast Guard; telephone (510) 612-9729, or email 
                        <E T="03">SFWaterways@uscg.mil.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Table of Abbreviations</HD>
                <EXTRACT>
                    <FP SOURCE="FP-1">CFR Code of Federal Regulations</FP>
                    <FP SOURCE="FP-1">COTP Captain of the Port</FP>
                    <FP SOURCE="FP-1">DHS Department of Homeland Security</FP>
                    <FP SOURCE="FP-1">FR Federal Register</FP>
                    <FP SOURCE="FP-1">NPRM Notice of proposed rulemaking</FP>
                    <FP SOURCE="FP-1">RFA Regulatory Flexibility Act</FP>
                    <FP SOURCE="FP-1">§ Section </FP>
                    <FP SOURCE="FP-1">U.S.C. United States Code</FP>
                </EXTRACT>
                <HD SOURCE="HD1">II. Background and Authority</HD>
                <P>
                    The Coast Guard received notification that the America 250 Fireworks 2026 displays will be occurring in various 
                    <PRTPAGE P="40890"/>
                    locations in San Francisco Bay on July 4, 2026. The Captain of the Port (COTP) San Francisco has determined that potential hazards associated with fireworks are a safety concern for anyone within a 1,200-yard radius of the fireworks displays. Therefore, the COTP is issuing this rule under the authority in 46 U.S.C. 70034, which is needed to protect personnel, vessels, and the marine environment in the navigable waters within the safety zone.
                </P>
                <P>Because of these potential hazards, the Coast Guard is issuing this rule without prior notice and comment. As is authorized by 5 U.S.C. 553(b)(B), the Coast Guard finds that good cause exists for not publishing a notice of proposed rulemaking (NPRM) with respect to this rule because it is impracticable. The Coast Guard was notified of this event on May 26, 2026, but we must establish this safety zone by July 4, 2026, to protect personnel, vessels, and the marine environment. Therefore, we do not have enough time to solicit and respond to comments.</P>
                <P>
                    For the same reason, the Coast Guard finds that under 5 U.S.C. 553(d)(3), good cause exists for making this rule effective less than 30 days after publication in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <HD SOURCE="HD1">III. Discussion of Comments and the Rule</HD>
                <P>This rule establishes a safety zone on July 4, 2026. The safety zone will cover all navigable waters in San Francisco Bay within a 1,200-yard radius of each fireworks barge and the Golden Gate Bridge during the loading of pyrotechnics, transit of the barges to the display locations, and during the fireworks display. The fireworks displays will be located at Pier 39 Barge Zone (37.814268 N, −122.41706 W), Golden Gate Barge Zone (37.817442 N,  −122.465684 W), and Golden Gate Bridge Zone (37.817667 N,  −122.478333 W). At 4:00 a.m. on July 4, 2026, the barges will commence the onload of pyrotechnics at Pier 68. At 4:00 p.m. on July 4, 2026, the barges will commence the transit, and stage at the display locations. From 4:30 p.m. until approximately 10:30 p.m. on July 4, 2026, the safety zones will encompass all navigable waters within a 1,200-foot radius of each fireworks barge, and 1,200-yards off the Golden Gate Bridge in all directions. Vessels and persons will not be allowed to enter the zone during these times, unless authorized by the COTP.</P>
                <HD SOURCE="HD1">IV. Regulatory Analyses</HD>
                <P>We developed this rule after considering numerous statutes and Executive orders related to rulemaking. Below we summarize our analyses based on a number of these statutes and Executive orders.</P>
                <HD SOURCE="HD2">A. Impact on Small Entities</HD>
                <P>The regulatory flexibility analysis provisions of the Regulatory Flexibility Act of 1980, 5 U.S.C. 601-612, do not apply to rules that are not subject to notice and comment. Because the Coast Guard has, for good cause, waived the notice and comment requirement that would otherwise apply to this rulemaking, the Regulatory Flexibility Act's flexibility analysis provisions do not apply here.</P>
                <P>
                    Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121), if this rule will affect your small business, organization, or governmental jurisdiction and you have questions, contact the person listed in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section.
                </P>
                <P>Small businesses may send comments to the Small Business and Agriculture Regulatory Enforcement Ombudsman and the Regional Small Business Regulatory Fairness Boards by calling 1-888-REG-FAIR (1-888-734-3247). The Coast Guard will not retaliate against small entities that question or complain about this rule or any policy or action of the Coast Guard.</P>
                <HD SOURCE="HD2">B. Collection of Information</HD>
                <P>This rule will not call for a new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520).</P>
                <HD SOURCE="HD2">C. Federalism and Indian Tribal Governments</HD>
                <P>We have analyzed this rule under Executive Order 13132, Federalism, and have determined that it is consistent with the fundamental federalism principles and preemption requirements described in that Order.</P>
                <P>Also, this rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it does not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes.</P>
                <HD SOURCE="HD2">D. Unfunded Mandates Reform Act</HD>
                <P>As required by The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538), the Coast Guard certifies that this rule will not result in an annual expenditure of $100,000,000 or more (adjusted for inflation) by a State, local, or tribal government, in the aggregate, or by the private sector.</P>
                <HD SOURCE="HD2">E. Environment</HD>
                <P>
                    We have analyzed this rule under Department of Homeland Security Directive 023-01, Rev. 1, associated implementing instructions, and Environmental Planning COMDTINST 5090.1 (series), which guide the Coast Guard in complying with the National Environmental Policy Act of 1969 (42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ), and have determined that this action is one of a category of actions that do not individually or cumulatively have a significant effect on the human environment.
                </P>
                <P>This rule is a safety zone. It is categorically excluded from further review under paragraph L60 (a) of Appendix A, Table 1 of DHS Instruction Manual 023-01-001-01, Rev. 1. A Record of Environmental Consideration supporting this determination is available in the docket.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 33 CFR Part 165</HD>
                    <P>Harbors, Marine safety, Navigation (water), Reporting and recordkeeping requirements, Security measures, Waterways.</P>
                </LSTSUB>
                <P>For the reasons discussed in the preamble, the Coast Guard amends 33 CFR part 165 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 165—REGULATED NAVIGATION AREAS AND LIMITED ACCESS AREAS</HD>
                </PART>
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>1. The authority citation for part 165 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 46 U.S.C. 70034, 70051, 70124; 33 CFR 1.05-1, 6.04-1, 6.04-6, and 160.5; DHS Delegation No. 00170.1, Revision No. 01.4.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>2. Add § 165.T11-246 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 165.T11-246</SECTNO>
                        <SUBJECT>Safety Zone; America 250 Fireworks 2026, San Francisco, CA.</SUBJECT>
                        <P>
                            <E T="03">(a) Location.</E>
                             The following area is a safety zone: All waters of San Francisco Bay, from surface to bottom, 1,200-yards from Pier 39 Barge Zone (37.814268 N,  −122.41706 W), Golden Gate Barge Zone (37.817442 N,  −122.465684 W), and Golden Gate Bridge Zone (37.817667 N,  −122.478333 W) in San Francisco, CA.
                        </P>
                        <P>
                            <E T="03">(b) Definitions.</E>
                             As used in this section, 
                            <E T="03">designated representative</E>
                             means a Coast Guard Patrol Commander, including a Coast Guard coxswain, petty officer, or other officer operating a Coast Guard vessel and a Federal, State, or local officer designated by or assisting the Captain of the Port (COTP) San Francisco in the enforcement of the safety zone.
                            <PRTPAGE P="40891"/>
                        </P>
                        <P>
                            (c) 
                            <E T="03">Regulations.</E>
                             (1) Under the general safety zone regulations in subpart C of this part, you may not enter the safety zone described in paragraph (a) of this section unless authorized by the COTP or the COTP's designated representative.
                        </P>
                        <P>(2) To seek permission to enter, contact the COTP or the COTP's representative on VHF-FM channel 16. Those in the safety zone must comply with all lawful orders or directions given to them by the COTP or the COTP's designated representative.</P>
                        <P>
                            <E T="03">(d) Enforcement period.</E>
                             This section will be enforced on July 4, 2026. This section will be enforced at Pier 68 from 4 a.m. until 4 p.m., around the three barges while transiting from 4 p.m. until 4:30 p.m., and at Pier 39 Barge Zone, Golden Gate Barge Zone, Golden Gate Bridge Zone from 4:30 p.m. until 10:30 p.m.
                        </P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: June 30, 2026.</DATED>
                    <NAME>Jordan M. Baldueza,</NAME>
                    <TITLE>Captain, U.S. Coast Guard, Captain of the Port Sector San Francisco.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13551 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-04-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <CFR>33 CFR Part 165</CFR>
                <DEPDOC>[Docket Number USCG-2026-0810]</DEPDOC>
                <RIN>RIN 1625-AA00</RIN>
                <SUBJECT>Safety Zone; Lake Michigan, Chicago, IL</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Temporary final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Coast Guard is establishing a temporary safety zone for certain navigable waters of Monroe Harbor and Lake Michigan. The safety zone is needed to protect personnel, vessels, and the marine environment from potential hazards created by a fireworks display and drone show. This proposed rulemaking would prohibit persons and vessels from being in the safety zone unless specifically authorized by the Captain of the Port, Sector Lake Michigan.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This rule is effective from 8:45 p.m. through 9:30 p.m. on July 10, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        To view available documents go to 
                        <E T="03">https://www.regulations.gov</E>
                         and search for USCG-2026-0810.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        If you have questions about this rule, contact LT Kyle Goetz, Marine Safety Unit Chicago, Waterways Management Division, U.S. Coast Guard; telephone 630-341-8320, or email 
                        <E T="03">D09-SMB-MSUChicago-WWM@uscg.mil.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Table of Abbreviations</HD>
                <EXTRACT>
                    <FP SOURCE="FP-1">CFR Code of Federal Regulations</FP>
                    <FP SOURCE="FP-1">COTP Captain of the Port</FP>
                    <FP SOURCE="FP-1">DHS Department of Homeland Security</FP>
                    <FP SOURCE="FP-1">FR Federal Register</FP>
                    <FP SOURCE="FP-1">NPRM Notice of proposed rulemaking</FP>
                    <FP SOURCE="FP-1">§ Section </FP>
                    <FP SOURCE="FP-1">U.S.C. United States Code</FP>
                </EXTRACT>
                <HD SOURCE="HD1">II. Background and Authority</HD>
                <P>On June 10, 2026, an organization notified the Coast Guard that they will be hosting a firework display and drone show over Monroe Harbor for an event called the Taste of Chicago, on July 10, 2026. Hazards that could be potentially involved in the display include, but are not limited to, fallout from the fireworks and drones in the water. The Captain of the Port Sector Lake Michigan (COTP) has determined that potential hazards associated with this event are a safety concern for participants and spectators involved in the show. Therefore, the COTP is issuing this rule under the authority in 46 U.S.C. 70034, which is needed to protect personnel, vessels, and the marine environment in the navigable waters within the safety zone.</P>
                <P>Because of these potential hazards, the Coast Guard is issuing this rule without prior notice and comment. As is authorized by 5 U.S.C. 553(b)(B), the Coast Guard finds that good cause exists for not publishing a notice of proposed rulemaking (NPRM) with respect to this rule because it is impracticable. The Coast Guard was notified of this event on June 10, 2026, but we must establish this safety zone by July 10, 2026, to protect personnel, vessels, and the marine environment. Therefore, we do not have enough time to solicit and respond to comments.</P>
                <P>
                    For the same reason, the Coast Guard finds that under 5 U.S.C. 553(d)(3), good cause exists for making this rule effective less than 30 days after publication in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <HD SOURCE="HD1">III. Discussion of the Rule</HD>
                <P>This rule establishes a safety zone beginning at 8:45 p.m. until 9:30 p.m. on July 10, 2026. The safety zone will cover all navigable waters of Monroe Harbor and Lake Michigan within the following points: point 1 at 41°52′42.1″ N 87°37′1.1″ W, thence to point 2 at 41°52′25.8″ N 87°37′0.1″ W, thence to point 3 at 41°52′26.1″ N 87°36′22.4″ W, thence to point 4 at 41°52′42.3″ N 87°36′21.7″ W, thence returning to point 1. The safety zone has been specifically sized to encompass the combined hazard and fall-out areas for both the land-launched drone show located near Lakefront Park and the barge-launched fireworks display located near the entrance to Monroe Harbor. This safety zone is necessary to protect personnel, vessels, and the marine environment from the potential hazards associated with these concurrent events. Vessels and persons will not be allowed to enter the zone during this time, unless authorized by the Captain of the Port.</P>
                <HD SOURCE="HD1">IV. Regulatory Analyses</HD>
                <P>We developed this rule after considering numerous statutes and Executive orders related to rulemaking. Below we summarize our analyses based on a number of these statutes and Executive orders.</P>
                <HD SOURCE="HD2">A. Impact on Small Entities</HD>
                <P>The regulatory flexibility analysis provisions of the Regulatory Flexibility Act of 1980, 5 U.S.C. 601-612, do not apply to rules that are not subject to notice and comment. Because the Coast Guard has, for good cause, waived the notice and comment requirement that would otherwise apply to this rulemaking, the Regulatory Flexibility Act's flexibility analysis provisions do not apply here.</P>
                <P>
                    Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121), if this rule will affect your small business, organization, or governmental jurisdiction and you have questions, contact the person listed in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section.
                </P>
                <P>Small businesses may send comments to the Small Business and Agriculture Regulatory Enforcement Ombudsman and the Regional Small Business Regulatory Fairness Boards by calling 1-888-REG-FAIR (1-888-734-3247). The Coast Guard will not retaliate against small entities that question or complain about this rule or any policy or action of the Coast Guard.</P>
                <HD SOURCE="HD2">B. Collection of Information</HD>
                <P>This rule will not call for a new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520).</P>
                <HD SOURCE="HD2">C. Federalism and Indian Tribal Governments</HD>
                <P>
                    We have analyzed this rule under Executive Order 13132, Federalism, and have determined that it is consistent with the fundamental federalism principles and preemption requirements described in that Order.
                    <PRTPAGE P="40892"/>
                </P>
                <P>Also, this rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it does not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes.</P>
                <HD SOURCE="HD2">D. Unfunded Mandates Reform Act</HD>
                <P>As required by The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538), the Coast Guard certifies that this rule will not result in an annual expenditure of $100,000,000 or more (adjusted for inflation) by a State, local, or tribal government, in the aggregate, or by the private sector.</P>
                <HD SOURCE="HD2">E. Environment</HD>
                <P>
                    We have analyzed this rule under Department of Homeland Security Directive 023-01, Rev. 1, associated implementing instructions, and Environmental Planning COMDTINST 5090.1 (series), which guide the Coast Guard in complying with the National Environmental Policy Act of 1969 (42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ), and have determined that this action is one of a category of actions that do not individually or cumulatively have a significant effect on the human environment.
                </P>
                <P>This rule is a safety zone. It is categorically excluded from further review under paragraph L60(a) of Appendix A, Table 1 of DHS Instruction Manual 023-01-001-01, Rev. 1. A Record of Environmental Consideration supporting this determination is available in the docket.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 33 CFR Part 165</HD>
                    <P>Harbors, Marine safety, Navigation (water), Reporting and recordkeeping requirements, Security measures, Waterways.</P>
                </LSTSUB>
                <P>For the reasons discussed in the preamble, the Coast Guard amends 33 CFR part 165 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 165—REGULATED NAVIGATION AREAS AND LIMITED ACCESS AREAS</HD>
                </PART>
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>1. The authority citation for part 165 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 46 U.S.C. 70034, 70051, 70124; 33 CFR 1.05-1, 6.04-1, 6.04-6, and 160.5; DHS Delegation No. 00170.1, Revision No. 01.4.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>2. Add § 165.T09-0810 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 165.T09-0810</SECTNO>
                        <SUBJECT>Safety Zone; Lake Michigan, Chicago, IL.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Location.</E>
                             The following area is a safety zone: all navigable waters of Monroe Harbor and Lake Michigan within the following points: point 1 at 41°52′42.1″ N 87°37′1.1″ W, thence to point 2 at 41°52′25.8″ N 87°37′0.1″ W, thence to point 3 at 41°52′26.1″ N 87°36′22.4″ W, thence to point 4 at 41°52′42.3″ N 87°36′21.7″ W, thence returning to point 1. The safety zone has been specifically sized to encompass the combined hazard and fall-out areas for both the land-launched drone show located near Lakefront Park and the barge-launched fireworks display located near the entrance to Monroe Harbor. These coordinates are based on the World Geodetic System (WGS 84).
                        </P>
                        <P>
                            (b) 
                            <E T="03">Definitions.</E>
                             As used in this section, 
                            <E T="03">designated representative</E>
                             means a Coast Guard Patrol Commander, including a Coast Guard coxswain, petty officer, or other officer operating a Coast Guard vessel and a Federal, State, and local officer designated by or assisting the Captain of the Port Sector Lake Michigan (COTP) in the enforcement of the safety zone.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Regulations.</E>
                             (1) Under the general safety zone regulations in subpart C of this part, you may not enter the safety zone described in paragraph (a) of this section unless authorized by the COTP or the COTP's designated representative.
                        </P>
                        <P>(2) To seek permission to enter, contact the COTP or the COTP's representative on VHF-FM channel 16 or by telephone at (833) 900-2247. Those in the safety zone must comply with all lawful orders or directions given to them by the COTP or the COTP's designated representative.</P>
                        <P>
                            (d) 
                            <E T="03">Enforcement period.</E>
                             This section will be enforced from 8:45 p.m. to 9:30 p.m. on July 10, 2026.
                        </P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <NAME>R.N. Macon,</NAME>
                    <TITLE>Captain, U.S. Coast Guard, Captain of the Port, Lake Michigan.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13619 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-04-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <CFR>33 CFR Part 165</CFR>
                <DEPDOC>[Docket Number USCG-2026-0633]</DEPDOC>
                <RIN>RIN 1625-AA11</RIN>
                <SUBJECT>Regulated Navigation Area; Hudson River, Albany, NY</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Temporary interim rule and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Coast Guard is establishing a temporary regulated navigation area (RNA) for navigable waters on the Hudson River near Albany, NY. This RNA prohibits entry of vessels or persons during full enforcement unless specifically authorized by the Captain of the Port, Sector New York, or their designated representative, imposes a “Slow-No Wake” speed restriction, and sets forth other limitations. This rule is necessary to protect personnel, vessels, and the marine environment from potential hazards associated with construction of the new Livingston Avenue Railroad Swing Bridge and demolition of the existing bridge.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This rule is effective from July 12, 2026, through October 31, 2029. Comments and related material must be received by the Coast Guard on or before August 5, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        To submit comments and view available documents, go to 
                        <E T="03">https://www.regulations.gov</E>
                         and search for USCG-2026-0633.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        If you have questions about this rule, contact Mr. Jeffrey Yunker, Sector New York Waterways Management Division, U.S. Coast Guard; telephone 571-607-2628, or email 
                        <E T="03">Jeffrey.M.Yunker@uscg.mil.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Table of Abbreviations</HD>
                <EXTRACT>
                    <FP SOURCE="FP-1">CFR Code of Federal Regulations</FP>
                    <FP SOURCE="FP-1">COTP Captain of the Port New York</FP>
                    <FP SOURCE="FP-1">DHS Department of Homeland Security</FP>
                    <FP SOURCE="FP-1">FR Federal Register</FP>
                    <FP SOURCE="FP-1">LAB JV Livingston Avenue Bridge Joint Venture</FP>
                    <FP SOURCE="FP-1">NPRM Notice of proposed rulemaking</FP>
                    <FP SOURCE="FP-1">RNA Regulated Navigation Area</FP>
                    <FP SOURCE="FP-1">§ Section </FP>
                    <FP SOURCE="FP-1">U.S.C. United States Code</FP>
                </EXTRACT>
                <HD SOURCE="HD1">II. Background and Authority</HD>
                <P>
                    The Coast Guard received notification that Skanska Koch LAB JV will be constructing a new Livingston Avenue Bridge and demolishing the existing bridge within the Hudson River near Albany, NY. Hazards from this project include but are not limited to deployment of heavy equipment which will obstruct vessel traffic, heavy lift operations, installation of transfer bents for new bridge spans staging prior to installation, and multiple tugboats and barges staged throughout the project with daily movements. The Northeast Coast Guard District Commander has determined that potential hazards associated with construction of a new 
                    <PRTPAGE P="40893"/>
                    bridge, and demolition of the existing bridge, are a safety concern for anyone within the work area. Therefore, the Northeast Coast Guard District Commander is issuing this rule under the authority in 46 U.S.C. 70034, which is necessary to protect personnel, vessels, and the marine environment in the navigable waters within the RNA.
                </P>
                <P>Because of these potential hazards, the Coast Guard is issuing this rule without prior notice and comment. As authorized by 5 U.S.C. 553(b)(B), the Coast Guard finds that good cause exists for not publishing a notice of proposed rulemaking (NPRM) with respect to this rule because it is impracticable. The Coast Guard was not notified of this revised project schedule and Limited Access Area request with sufficient notice prior to when the RNA is needed on July 12, 2026, to protect personnel, vessels, and the marine environment. Therefore, we do not have enough time to solicit and respond to comments.</P>
                <P>
                    Because of the potential hazards associated with the bridge construction, the Coast Guard finds that under 5 U.S.C. 553(d)(3), good cause exists for making this rule effective less than 30 days after publication in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <P>
                    Although this regulation is published as a temporary interim rule without prior notice, public comment is nevertheless desirable to ensure that the regulation is both workable and reasonable. Accordingly, persons wishing to comment may do so by submitting written comments as set out under the 
                    <E T="02">ADDRESSES</E>
                     section in this preamble. Commenters should include their names and addresses, identify the docket number for the regulation, and give reasons for their comments. If the Coast Guard determines that changes to the temporary interim rule are necessary, we will publish a temporary final rule or other appropriate document.
                </P>
                <HD SOURCE="HD1">III. Discussion of the Rule</HD>
                <P>This rule establishes an RNA from 7 a.m. on July 12, 2026, until 11:59 p.m. on October 31, 2029. The Coast Guard is creating a RNA as shown in figure 1, to include all navigable waters of the Hudson River, mile 146.2, in the vicinity of the Livingston Avenue Railroad Swing Bridge, Albany, NY, surface to bottom, shoreline to shoreline, south of a line drawn from 42°39′23.50″ N, 73°44′31.12″ W thence to 42°39′18.25″ N, 73°44′17.41″ W, approximately 600 feet north of the existing bridge, and north of a line drawn from 42°39′09.46″ N, 73°44′41.01″ W thence to 42°39′04.22″ N, 73°44′29.72″ W, approximately 1,000 feet south of the existing bridge. These coordinates are based on the World Geodetic System (WGS 84)/North American Datum 83 (NAD 83).</P>
                <HD SOURCE="HD1">Figure 1 Chartlet Showing the Boundaries of the RNA</HD>
                <GPH SPAN="3" DEEP="440">
                    <PRTPAGE P="40894"/>
                    <GID>ER06JY26.002</GID>
                </GPH>
                <P>The RNA will establish the following operating restrictions on vessels:</P>
                <P>(1) In addition to the general RNA regulations in § 165.13, the following regulations apply to the RNA described in paragraph (a) of this section.</P>
                <P>
                    (2) Nothing in this regulation relieves any vessel, owner, operator, charterer, master, or person directing the movement of a vessel, from the consequences of any neglect to comply with this part or any other applicable law or regulation (
                    <E T="03">i.e.</E>
                     the International Regulations for Prevention of Collisions at Sea, 1972 (72 COLREGS) or 33 CFR part 84—Subchapter E, Inland Navigation Rules) or of the neglect of any precaution which may be required by the ordinary practice of seamen, or by the special circumstances of the case.
                </P>
                <P>(3) Entry and movement within the RNA is subject to a “Slow-No Wake” speed limit. All vessels may not produce a wake and may not attain speeds greater than five (5) knots unless a higher minimum speed is necessary to maintain bare steerageway.</P>
                <P>(4) Any vessel transiting through the RNA must make a direct passage. No vessel may stop, fish, moor, anchor, or loiter within the RNA at any time.</P>
                <P>(5) Vessels may not pass (overtake) another vessel within the RNA.</P>
                <P>(6) Except when transiting through the navigation channel, no vessel or craft may operate within 20 feet of the bridge(s).</P>
                <P>(7) The operator of any vessel transiting in the RNA must comply with all lawful directions given to them by the COTP or the COTP's on-scene representative.</P>
                <P>(8) When a full enforcement period of the regulated area is activated, only vessels authorized by COTP may enter or remain within the RNA.</P>
                <P>Restrictions (1) through (7) will be enforced throughout the entire effective period. Restriction (8) will be enforced during limited periods (referred to as “full enforcement” periods).</P>
                <P>Full enforcement periods, which entail prohibiting all vessel entry within the regulated area, will be implemented only during hazardous construction operations involving multiple tugs and large barges maneuvering in, or near, and obstructing the navigable channel for heavy lift, construction, or demolition activities at the Livingston Avenue Railroad Swing Bridge (mile 146.2). These intermittent full closures are anticipated to occur between July 12, 2026, and October 27, 2027.</P>
                <P>
                    Currently, up to 20 full enforcement periods are planned, during which all 
                    <PRTPAGE P="40895"/>
                    vessel transits through the regulated area will be prohibited. These dates are tentative and subject to change due to weather, construction or supply chain delays, or other unforeseen circumstances. SKANSKA KOCH will provide email updates to all stakeholders as the project progresses and as the full closure dates and times are finalized based on construction progress.
                </P>
                <P>Full enforcement periods prohibiting vessels from entering the regulated area are planned during the following approximate dates:</P>
                <P>• July 2026 through December 2026, up to five full waterway closures lasting one day each to install drilled shafts, precast pile caps, and cast-in-place pier walls.</P>
                <P>• October 2026 through November 2026, no anticipated waterway closures, but work occurs within the proposed RNA to install piles and grillage for transfer bent south of existing bridge.</P>
                <P>• September 2026 through February 2027, up to six full waterway closures lasting one day each to install new lift span towers between new piers three and four.</P>
                <P>• January 2027 through February 2027, up to five full waterway closures lasting one day each, and one full waterway closure lasting two or three days to set lift span truss onto transfer bent and float truss into final position between new piers three and four.</P>
                <P>• March 2027, up to three full waterway closures lasting one day each and one full waterway closure lasting two or three days to float truss span into final position between new piers two and three.</P>
                <P>• March 2027 through September 2027, no waterway closures, but work occurs within the RNA to install mechanical equipment of lift span and erection of approach girders.</P>
                <P>• August 2027 through September 2027, one full waterway closure lasting 14 days and five full waterway closures lasting one day each to set west flanking span truss onto transfer bent and float truss into final position between new piers four and five.</P>
                <P>• October 2027 through February 2029, Navigation opening will be reduced to 84 feet for an estimated 30-day to 60-day period around October 2027 following the 14-day navigational channel closure, demolition of superstructure and substructure of the existing Livingston Avenue Bridge.</P>
                <P>
                    The dates and times of the full enforcement periods, during which all vessel transits through the regulated area will be prohibited, will be published in the Local Notice to Mariners, posted on the Coast Guard Navigation Center Maritime Safety Information Products page at 
                    <E T="03">https://www.navcen.uscg.gov/msi</E>
                    , and issued in a Broadcast Notice to Mariners via marine channel 16 (VHF-FM) as soon as practicable in response to an emergency or hazardous condition.
                </P>
                <P>This rule will remain in effect through October 31, 2029, which should accommodate the possibility of project delays due to unforeseen circumstances. If the project is completed before October 31, 2029, enforcement of the regulated navigation area will be suspended, and notice will be provided via the Local Notice to Mariners.</P>
                <P>
                    The Coast Guard Northeast District Local Notice to Mariners can be found at: 
                    <E T="03">https://www.navcen.uscg.gov/maritime-safety-information.</E>
                </P>
                <HD SOURCE="HD1">IV. Regulatory Analyses</HD>
                <P>We developed this rule after considering numerous statutes and Executive orders related to rulemaking. Below we summarize our analyses based on a number of these statutes and Executive orders.</P>
                <HD SOURCE="HD2">A. Impact on Small Entities</HD>
                <P>The regulatory flexibility analysis provisions of the Regulatory Flexibility Act of 1980, 5 U.S.C. 601-612, do not apply to rules that are not subject to notice and comment. Because the Coast Guard has, for good cause, waived the notice and comment requirement that would otherwise apply to this rulemaking, the Regulatory Flexibility Act's flexibility analysis provisions do not apply here.</P>
                <P>
                    Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121), if this rule will affect your small business, organization, or governmental jurisdiction and you have questions, contact the person listed in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section.
                </P>
                <P>Small businesses may send comments to the Small Business and Agriculture Regulatory Enforcement Ombudsman and the Regional Small Business Regulatory Fairness Boards by calling 1-888-REG-FAIR (1-888-734-3247). The Coast Guard will not retaliate against small entities that question or complain about this rule or any policy or action of the Coast Guard.</P>
                <HD SOURCE="HD2">B. Collection of Information</HD>
                <P>This rule will not call for a new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520).</P>
                <HD SOURCE="HD2">C. Federalism and Indian Tribal Governments</HD>
                <P>We have analyzed this rule under Executive Order 13132, Federalism, and have determined that it is consistent with the fundamental federalism principles and preemption requirements described in that Order.</P>
                <P>Also, this rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it does not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes.</P>
                <HD SOURCE="HD2">D. Unfunded Mandates Reform Act</HD>
                <P>As required by The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538), the Coast Guard certifies that this rule will not result in an annual expenditure of $100,000,000 or more (adjusted for inflation) by a State, local, or tribal government, in the aggregate, or by the private sector.</P>
                <HD SOURCE="HD2">E. Environment</HD>
                <P>
                    We have analyzed this rule under Department of Homeland Security Directive 023-01, Rev. 1, associated implementing instructions, and Environmental Planning COMDTINST 5090.1 (series), which guide the Coast Guard in complying with the National Environmental Policy Act of 1969 (42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ), and have determined that this action is one of a category of actions that do not individually or cumulatively have a significant effect on the human environment.
                </P>
                <P>This rule is a regulated navigation area. It is categorically excluded from further review under paragraph L60(a) of Appendix A, Table 1 of DHS Instruction Manual 023-01-001-01, Rev. 1. A Record of Environmental Consideration supporting this determination is available in the docket.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 33 CFR Part 165</HD>
                    <P>Harbors, Marine safety, Navigation (water), Reporting and recordkeeping requirements, Security measures, Waterways.</P>
                </LSTSUB>
                <P>For the reasons discussed in the preamble, the Coast Guard amends 33 CFR part 165 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 165—REGULATED NAVIGATION AREAS AND LIMITED ACCESS AREAS</HD>
                </PART>
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>1. The authority citation for part 165 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <PRTPAGE P="40896"/>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 46 U.S.C. 70034, 70051, 70124; 33 CFR 1.05-1, 6.04-1, 6.04-6, and 160.5; DHS Delegation No. 00170.1, Revision No. 01.4.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>2. Add § 165.T01-0633 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 165.T01-0633</SECTNO>
                        <SUBJECT>Regulated Navigation Area; Hudson River, Albany, NY.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Location.</E>
                             The following area is a Regulated Navigation Area (RNA): All waters of the Hudson River, mile 146.2, in the vicinity of the Livingston Avenue Railroad Swing Bridge, Albany, NY, from surface to bottom, shoreline to shoreline, south of a line drawn from 42°39′23.50″ N, 73°44′31.12″ W thence to 42°39′18.25″ N, 73°44′17.41″ W, approximately 600 feet north of the existing bridge, and north of a line drawn from 42°39′09.46″ N, 73°44′41.01″ W thence to 42°39′04.22″ N, 73°44′29.72″ W, approximately 1,000 feet south of the existing bridge. These coordinates are based on the World Geodetic System (WGS 84)/North American Datum 83 (NAD 83).
                        </P>
                        <P>
                            (b) 
                            <E T="03">Definitions.</E>
                             As used in this section, 
                            <E T="03">designated representative</E>
                             means a Coast Guard Patrol Commander, including a Coast Guard coxswain, petty officer, or other officer operating a Coast Guard vessel and a Federal, State, and local officer designated by or assisting the Northeast Coast Guard District Commander in the enforcement of the regulated area. 
                            <E T="03">Local officer</E>
                             means any officer, agent, or employee of a unit of local government authorized by law or by a local government agency to engage in or supervise the prevention, detection, investigation, or prosecution of any violation of criminal law.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Regulations.</E>
                             (1) In addition to the general RNA regulations in § 165.13, the following regulations apply to the RNA described in paragraph (a) of this section.
                        </P>
                        <P>
                            (2) Nothing in this regulation relieves any vessel, owner, operator, charterer, master, or person directing the movement of a vessel, from the consequences of any neglect to comply with this part or any other applicable law or regulation (
                            <E T="03">i.e.</E>
                             the International Regulations for Prevention of Collisions at Sea, 1972 (72 COLREGS) or 33 CFR part 84—Subchapter E, Inland Navigation Rules) or of the neglect of any precaution which may be required by the ordinary practice of seamen, or by the special circumstances of the case.
                        </P>
                        <P>(3) Entry and movement within the RNA is subject to a “Slow-No Wake” speed limit. All vessels may not produce a wake and may not attain speeds greater than five (5) knots unless a higher minimum speed is necessary to maintain bare steerageway.</P>
                        <P>(4) Any vessel transiting through the RNA must make a direct passage. No vessel may stop, fish, moor, anchor, or loiter within the RNA at any time.</P>
                        <P>(5) Vessels may not pass (overtake) another vessel within the RNA.</P>
                        <P>(6) Except when transiting through the navigation channel, no vessel or craft may operate within 20 feet of the bridge(s).</P>
                        <P>(7) The operator of any vessel transiting in the RNA must comply with all lawful directions given to them by the COTP or the COTP's on-scene representative.</P>
                        <P>(8) When a full enforcement period of the regulated area is activated, only vessel authorized by COTP may enter or remain within the RNA.</P>
                        <P>
                            (d) 
                            <E T="03">Enforcement period.</E>
                             The following enforcement periods and requirements apply to this RNA.
                        </P>
                        <P>(1) This section will be enforced from 7 a.m. on July 12, 2026, to 11:59 p.m. on October 31, 2029.</P>
                        <P>(2) The “Slow-No Wake” speed limit, and other restrictions—except for the limited full enforcement period prohibiting vessels from entering the regulated area—will be enforced throughout the entire enforcement period.</P>
                        <P>
                            (3) Full enforcement periods of the regulated area, prohibiting all vessel entry, will be enforced only during hazardous construction operations involving multiple tugs and large barges maneuvering in and obstructing the navigable channels, or near the navigable channels, for heavy lift, construction, or demolition activities. The Coast Guard will issue information on full enforcement periods through Local Notice to Mariners, the Coast Guard Navigation Center Maritime Safety Information Products page at 
                            <E T="03">https://www.navcen.uscg.gov/msi,</E>
                             and Broadcast Notice to Mariners via marine channel 16 (VHF-FM) as soon as practicable.
                        </P>
                        <P>(4) Persons or vessels seeking to deviate from the restrictions described in section (c) of this section or to enter the regulated area during a full enforcement period must request authorization from the COTP or the COTP's on-scene designated representative on VHF-16 or via phone at (718) 354-4353.</P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <NAME>Michael E. Platt,</NAME>
                    <TITLE>Rear Admiral, U.S. Coast Guard, Commander, Northeast District.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13568 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-04-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <CFR>33 CFR Part 165</CFR>
                <DEPDOC>[Docket Number USCG-2026-0803]</DEPDOC>
                <RIN>RIN 1625-AA00</RIN>
                <SUBJECT>Safety Zone; Fireworks Displays Within the USCG East District</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Temporary final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Coast Guard is establishing a temporary safety zone for certain waters of the Potomac River. This action is necessary to provide for the safety of life on these navigable waters near Fairview Beach, Virginia during a fireworks display on July 11, 2026. This regulation prohibits persons and vessels from being in the safety zone unless authorized by the Captain of the Port, Sector Maryland—National Capital Region or a designated representative.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This rule is effective from 8:15 p.m. on July 11, 2026, to 10:30 p.m. on July 12. It will only be enforced, however, from 8:15 p.m. to 10:30 p.m. on July 11 unless the fireworks display is cancelled due to inclement weather. If it is cancelled, it will only be enforced from 8:15 p.m. to 10:30 p.m. on July 12.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        To view available documents, go to 
                        <E T="03">https://www.regulations.gov</E>
                         and search for USCG-2026-0803.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        If you have questions about this rule, contact MST2 Natasha M. Hand, Sector Maryland—NCR, Waterways Management Division, U.S. Coast Guard: telephone 410-576-2596, email 
                        <E T="03">MDNCRMarineEvents@uscg.mil.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Table of Abbreviations</HD>
                <EXTRACT>
                    <FP SOURCE="FP-1">CFR Code of Federal Regulations</FP>
                    <FP SOURCE="FP-1">COTP Captain of the Port</FP>
                    <FP SOURCE="FP-1">DHS Department of Homeland Security</FP>
                    <FP SOURCE="FP-1">FR Federal Register</FP>
                    <FP SOURCE="FP-1">NPRM Notice of proposed rulemaking</FP>
                    <FP SOURCE="FP-1">§ Section </FP>
                    <FP SOURCE="FP-1">U.S.C. United States Code</FP>
                </EXTRACT>
                <HD SOURCE="HD1">II. Background and Authority</HD>
                <P>
                    The Coast Guard received notification that fireworks will be launched from a barge on the Potomac River near Fairview Beach, Virginia. The Captain of the Port (COTP) Sector Maryland—National Capital Region has determined that potential hazards associated with fireworks are a safety concern for 
                    <PRTPAGE P="40897"/>
                    anyone within 600 feet of the fireworks display.
                </P>
                <P>Therefore, the COTP is issuing this rule under the authority in 46 U.S.C. 70034, which is needed to protect personnel, vessels, and the marine environment in the navigable waters within the safety zone.</P>
                <P>Because of these potential hazards, the Coast Guard is issuing this rule without prior notice and comment. As is authorized by 5 U.S.C. 553(b)(B), the Coast Guard finds that good cause exists for not publishing a notice of proposed rulemaking (NPRM) with respect to this rule because it is impracticable. The Coast Guard was notified of this event on June 9, 2026, but we must establish this safety zone by July 11, 2026, to protect personnel, vessels, and the marine environment. Therefore, we do not have enough time to solicit and respond to comments.</P>
                <P>
                    For the same reason, the Coast Guard finds that under 5 U.S.C. 553(d)(3), good cause exists for making this rule effective less than 30 days after publication in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <HD SOURCE="HD1">III. Discussion of the Rule</HD>
                <P>Tim's II Rivershore Restaurant, of King George, Virginia, will sponsor a fireworks display launched from a barge located in the Potomac River, near Fairview Beach, Virginia, on Saturday, July 11, 2026, at approximately 9:15 p.m. If necessary, due to inclement weather, the display will be held on July 12, 2026. This rule establishes a temporary safety zone which will be enforced from 8:15 p.m. to 10:30 p.m. on July 11, 2026, or from 8:15 p.m. to 10:30 p.m. on July 12, 2026 (if the event is postponed due to inclement weather on July 11). The duration of the safety zone is intended to ensure the safety of vessels and these navigable waters before, during, and after the scheduled 9:15 p.m. to 9:30 p.m. fireworks display. This temporary safety zone will cover all navigable waters within a 600 ft radius of a barge in the Potomac River, approximately 700 ft from the shoreline at Fairview Beach, Virginia. The approximate position of the barge is latitude 38°20′00.00″ N, longitude 077°14′48.31″ W, (NAD 1983). No person or vessel will be permitted to enter the safety zone without obtaining permission from the COTP or a designated representative. Vessels will be allowed to transit the waters of the Potomac River outside the safety zone.</P>
                <HD SOURCE="HD1">IV. Regulatory Analyses</HD>
                <P>We developed this rule after considering numerous statutes and Executive orders related to rulemaking. Below we summarize our analyses based on a number of these statutes and Executive orders.</P>
                <HD SOURCE="HD2">A. Impact on Small Entities</HD>
                <P>The regulatory flexibility analysis provisions of the Regulatory Flexibility Act of 1980, 5 U.S.C. 601-612, do not apply to rules that are not subject to notice and comment. Because the Coast Guard has, for good cause, waived the notice and comment requirement that would otherwise apply to this rulemaking, the Regulatory Flexibility Act's flexibility analysis provisions do not apply here.</P>
                <P>
                    Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121), if this rule will affect your small business, organization, or governmental jurisdiction and you have questions, contact the person listed in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section.
                </P>
                <P>Small businesses may send comments to the Small Business and Agriculture Regulatory Enforcement Ombudsman and the Regional Small Business Regulatory Fairness Boards by calling 1-888-REG-FAIR (1-888-734-3247). The Coast Guard will not retaliate against small entities that question or complain about this rule or any policy or action of the Coast Guard.</P>
                <HD SOURCE="HD2">B. Collection of Information</HD>
                <P>This rule will not call for a new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520).</P>
                <HD SOURCE="HD2">C. Federalism and Indian Tribal Governments</HD>
                <P>We have analyzed this rule under Executive Order 13132, Federalism, and have determined that it is consistent with the fundamental federalism principles and preemption requirements described in that Order.</P>
                <P>Also, this rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it does not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes.</P>
                <HD SOURCE="HD2">D. Unfunded Mandates Reform Act</HD>
                <P>As required by The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538), the Coast Guard certifies that this rule will not result in an annual expenditure of $100,000,000 or more (adjusted for inflation) by a State, local, or tribal government, in the aggregate, or by the private sector.</P>
                <HD SOURCE="HD2">E. Environment</HD>
                <P>
                    We have analyzed this rule under Department of Homeland Security Directive 023-01, Rev. 1, associated implementing instructions, and Environmental Planning COMDTINST 5090.1 (series), which guide the Coast Guard in complying with the National Environmental Policy Act of 1969 (42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ), and have determined that this action is one of a category of actions that do not individually or cumulatively have a significant effect on the human environment.
                </P>
                <P>This rule is a safety zone. It is categorically excluded from further review under paragraph L60(a) of Appendix A, Table 1 of DHS Instruction Manual 023-01-001-01, Rev. 1. A Record of Environmental Consideration supporting this determination is available in the docket.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 33 CFR Part 165</HD>
                    <P>Harbors, Marine safety, Navigation (water), Reporting and recordkeeping requirements, Security measures, Waterways.</P>
                </LSTSUB>
                <P>For the reasons discussed in the preamble, the Coast Guard amends 33 CFR part 165 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 165—REGULATED NAVIGATION AREAS AND LIMITED ACCESS AREAS</HD>
                </PART>
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>1. The authority citation for part 165 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>46 U.S.C. 70034, 70051, 70124; 33 CFR 1.05-1, 6.04-1, 6.04-6, and 160.5; Department of Homeland Security Delegation No. 00170.1, Revision No. 01.4.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>2. Add § 165.T05-0803 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 165.T05-0803</SECTNO>
                        <SUBJECT>Safety Zone; Fireworks Display, Potomac River, Charles County, MD.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Location.</E>
                             The following area is a safety zone: All waters in the Potomac River, within a 600 feet radius of a fireworks discharge barge in approximate positions latitude 38°20′00.00″ N, longitude 077°14′48.31″ W, located approximately 700 feet from the shoreline at Fairview Beach, Virginia (NAD 1983).
                        </P>
                        <P>
                            (b) 
                            <E T="03">Definitions.</E>
                             As used in this section, 
                            <E T="03">designated representative</E>
                             means a Coast Guard Patrol Commander, including a Coast Guard coxswain, petty officer, or other officer operating a Coast Guard vessel and a Federal, State, and local officer designated by or assisting the Captain of the Port, Sector Maryland—National Capital Region (COTP) in the enforcement of the safety zone.
                            <PRTPAGE P="40898"/>
                        </P>
                        <P>
                            (c) 
                            <E T="03">Regulations.</E>
                             (1) Under the general safety zone regulations in subpart C of this part, you may not enter the safety zone described in paragraph (a) of this section unless authorized by the COTP or the COTP's designated representative.
                        </P>
                        <P>(2) To seek permission to enter, contact the COTP or the COTP's representative on VHF-FM channel 16 or by telephone at 410-576-2693. Those in the safety zone must comply with all lawful orders or directions given to them by the COTP or the COTP's designated representative.</P>
                        <P>
                            (d) 
                            <E T="03">Enforcement periods.</E>
                             This section will be enforced from 8:15 p.m. to 10:30 p.m. on July 11 or if necessary, due to inclement weather, from 8:15 p.m. to 10:30 p.m. on July 12, 2026.
                        </P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: June 26, 2026.</DATED>
                    <NAME>Patrick C. Burkett,</NAME>
                    <TITLE>Captain, U.S. Coast Guard, Captain of the Port Sector Maryland—National Capital Region.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13555 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-04-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <CFR>50 CFR Part 635</CFR>
                <DEPDOC>[Docket No. 220919-0193; RTID 0648-XF795]</DEPDOC>
                <SUBJECT>Atlantic Highly Migratory Species; Atlantic Bluefin Tuna Fisheries; Closure of the Angling Category Southern New England Area Trophy Fishery for 2026</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Temporary rule; closure.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        NMFS closes the Angling category Southern New England area fishery for large medium and giant (“trophy” (
                        <E T="03">i.e.,</E>
                         measuring 73 inches (185 centimeters (cm)) curved fork length or greater)) Atlantic bluefin tuna (BFT). This action applies to Highly Migratory Species (HMS) Angling and HMS Charter/Headboat permitted vessels when fishing recreationally.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective 11:30 p.m., local time, July 3, 2026, through December 31, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Becky Curtis, 
                        <E T="03">becky.curtis@noaa.gov</E>
                         or Larry Redd, Jr., 
                        <E T="03">larry.redd@noaa.gov</E>
                         by email, or by phone at 301-427-8503.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Atlantic BFT fisheries are managed under the 2006 Consolidated HMS Fishery Management Plan (HMS FMP) and its amendments, pursuant to the Magnuson-Stevens Fishery Conservation and Management Act (Magnuson-Stevens Act; 16 U.S.C. 1801 
                    <E T="03">et seq.</E>
                    ) and consistent with the Atlantic Tunas Convention Act (ATCA; 16 U.S.C. 971 
                    <E T="03">et seq.</E>
                    ). ATCA is the implementing statute for binding recommendations of the International Commission for the Conservation of Atlantic Tunas (ICCAT). The HMS FMP and its amendments are implemented by regulations at 50 CFR part 635. Section 635.27(a) divides the U.S. BFT quota, established by ICCAT and as implemented by the United States among the various domestic fishing categories, per the allocations established in the HMS FMP and its amendments. NMFS is required under the Magnuson-Stevens Act at 16 U.S.C. 1854(g)(1)(D) to provide U.S. fishing vessels with a reasonable opportunity to harvest quotas under relevant international fishery agreements such as the ICCAT Convention, which is implemented domestically pursuant to ATCA.
                </P>
                <P>Under § 635.28(a)(1), NMFS files a closure notice with the Office of the Federal Register for publication when a BFT quota (or subquota) is reached or is projected to be reached. Retaining, possessing, or landing BFT under that quota category is prohibited on and after the effective date and time of a closure notice for that category, for the remainder of the fishing year, until the opening of the subsequent quota period or until such date as specified.</P>
                <P>Every year, the BFT fishing year starts on January 1 and ends on December 31. The Angling category opens on January 1 and continues through December 31 or until the applicable quota or subquota is reached or projected to be reached, whichever comes first. As described in § 635.27(a), the current baseline U.S. BFT quota is 1,316.14 metric tons (mt) (not including the 25 mt ICCAT allocated to the United States to account for bycatch of BFT in pelagic longline fisheries in the Northeast Distant Gear Restricted Area per § 635.27(a)(3)). The Angling category baseline quota is 297.4 mt, of which 9.2 mt (3.1 percent of the annual Angling category quota) is sub-allocated for the harvest of large medium and giant (trophy) BFT by vessels fishing under the Angling category quota, with 2.3 mt (25 percent of the annual large medium and giant BFT Angling category quota) allocated for each of the following areas: north of latitude (lat.) 42° N (the Gulf of Maine area); south of lat. 42° N and north of lat. 39°18′ N (the Southern New England area); south of lat. 39°18′ N and outside of the Gulf of America (the southern area); and the Gulf of America region. Trophy BFT measure 73 inches (185 cm) curved fork length or greater. This closure action applies to the Southern New England area.</P>
                <P>Separate from this action, NMFS published a proposed rulemaking that would implement the 2025 ICCAT recommendation (Recommendation 25-05) regarding western BFT management (91 FR 24789, May 7, 2026). Consistent with the recommendation, that proposed rule would increase the baseline U.S. BFT quota from 1,316.14 to 1,509.98 mt and adjust all the subquotas accordingly. In that proposed rule, the Angling category baseline quota would increase from 297.4 to 341.3 mt and each trophy area subquota would increase from 2.3 to 2.6 mt. The comment period on that proposed rule ended on June 8, 2026. Any final rule implementing ICCAT Recommendation 25-05 would likely be effective in mid-2026 or later.</P>
                <HD SOURCE="HD1">Angling Category Trophy Bluefin Tuna Southern New England Area Fishery Closure</HD>
                <P>
                    Based on landings data from the NMFS Automated Catch Reporting System, as well as average catch rates and anticipated fishing conditions, NMFS has determined the Angling category Southern New England area trophy BFT subquota of 2.3 mt has been reached and exceeded. Therefore, retaining, possessing, or landing large medium or giant (
                    <E T="03">i.e.,</E>
                     measuring 73 inches (185 cm) curved fork length or greater) BFT in the Southern New England trophy area by persons aboard HMS Angling and HMS Charter/Headboat permitted vessels (when fishing recreationally) must cease at 11:30 p.m. local time on July 3, 2026. This closure will remain effective through December 31, 2026. This action applies to HMS Angling and HMS Charter/Headboat permitted vessels when fishing recreationally for BFT and is taken consistent with the regulations at § 635.28(a)(1). This action is intended to prevent further overharvest of the Angling category Southern New England area trophy BFT subquota. The Angling category BFT trophy fishery for the Gulf of Maine area remains open.
                </P>
                <P>
                    If needed to ensure available quotas or subquotas are not exceeded or to enhance fishing opportunities, subsequent Angling category adjustments or closures will be published in the 
                    <E T="04">Federal Register</E>
                     per §§ 635.27(a)(7) and 635.28(a)(1). Information regarding the Angling category fishery for Atlantic tunas, including daily retention limits for BFT 
                    <PRTPAGE P="40899"/>
                    measuring 27 inches (68.5 cm) to less than 73 inches (185 cm), and any further Angling category adjustments, is available at 
                    <E T="03">https://hmspermits.noaa.gov.</E>
                     During a closure, fishermen aboard HMS Angling and HMS Charter/Headboat permitted vessels when fishing recreationally may continue to catch and release (or tag and release) BFT of all sizes, subject to the requirements of the catch-and-release and tag-and-release programs at § 635.26. All BFT that are released must be handled in a manner that will maximize survival, and without removing the fish from the water, consistent with requirements at § 635.21(a)(1). For additional information on safe handling, see the “Careful Catch and Release” brochure available at 
                    <E T="03">https://www.fisheries.noaa.gov/resource/outreach-and-education/careful-catch-and-release-brochure/.</E>
                </P>
                <HD SOURCE="HD1">Monitoring and Reporting</HD>
                <P>
                    NMFS will continue to monitor the BFT fisheries closely. Per § 635.5(c)(1), HMS Angling and HMS Charter/Headboat permitted vessel owners are required to report the catch of all BFT retained or discarded dead, within 24 hours of the landing(s) or end of each trip, by accessing 
                    <E T="03">https://hmspermits.noaa.gov,</E>
                     using the HMS Catch Reporting app, or calling (888) 872-8862 (Monday through Friday from 8 a.m. until 4:30 p.m.).
                </P>
                <HD SOURCE="HD1">Classification</HD>
                <P>NMFS issues this action pursuant to section 305(d) of the Magnuson-Stevens Act (16 U.S.C. 1855(d)) and regulations at 50 CFR part 635, and this action is exempt from review under Executive Order 12866.</P>
                <P>The Assistant Administrator for NMFS (AA) finds that pursuant to 5 U.S.C. 553(b)(B), there is good cause to waive prior notice of, and an opportunity for public comment on, this action because it is impracticable and contrary to the public interest. Specifically, the regulations implementing the HMS FMP and its amendments provide for inseason retention limit adjustments and fishery closures to respond to the unpredictable nature of BFT availability on the fishing grounds, the migratory nature of this species, and the regional variations in the BFT fishery. Providing for prior notice and opportunity to comment is impracticable and contrary to the public interest as this fishery is currently underway and, based on the most recent landings information, the Angling category Southern New England area trophy BFT fishery subquota has been reached and exceeded. Delaying this action could result in further excessive trophy BFT landings that may result in future potential quota reductions for the Angling category, depending on the magnitude of a potential Angling category overharvest. NMFS must close the Southern New England area trophy BFT fishery before additional landings of these sizes of BFT occur. Taking this action does not raise conservation and management concerns and would support effective management of the BFT fishery. NMFS notes that the public had an opportunity to comment on the underlying rulemakings that established the U.S. BFT quota and the inseason adjustment criteria.</P>
                <P>For all of the above reasons, the AA also finds that pursuant to 5 U.S.C. 553(d)(3), there is good cause to waive the 30-day delay in effectiveness.</P>
                <P>
                    <E T="03">Authority:</E>
                     16 U.S.C. 971 
                    <E T="03">et seq.</E>
                     and 1801 
                    <E T="03">et seq.</E>
                </P>
                <SIG>
                    <DATED>Dated: July 1, 2026.</DATED>
                    <NAME>Kelly Denit,</NAME>
                    <TITLE>Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13630 Filed 7-1-26; 4:15 pm]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-P</BILCOD>
        </RULE>
    </RULES>
    <VOL>91</VOL>
    <NO>127</NO>
    <DATE>Monday, July 6, 2026</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <PRORULES>
        <PRORULE>
            <PREAMB>
                <PRTPAGE P="40900"/>
                <AGENCY TYPE="F">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. FAA-2026-7209; Project Identifier MCAI-2025-00629-E]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; Rolls-Royce Deutschland Ltd &amp; Co KG Engines</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) 2009-04-13, which applies to certain Rolls-Royce Deutschland Ltd &amp; Co KG (RRD) Model BR700-715A1-30, BR700-715B1-30, and BR700-715C1-30 engines. AD 2009-04-13 requires revising the airworthiness limitations section (ALS) of the operator's existing approved engine maintenance or inspection program, as applicable, to incorporate new or more restrictive tasks and limitations and associated thresholds and intervals for life-limited parts. AD 2009-04-13 also requires removing certain low pressure compressor (LPC) (fan) disc assemblies from service and completing the Life Limited Part Tracking Sheet. Since the FAA issued AD 2009-04-13, the manufacturer has revised the engine time limits manual (TLM) to introduce new or more restrictive tasks and limitations and associated thresholds and intervals for life-limited parts. This proposed AD would require revising the ALS of the existing approved engine maintenance or inspection program, as applicable, to incorporate new or more restrictive tasks and limitations and associated thresholds and intervals for life-limited parts. 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 NPRM by August 20, 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-7209; 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, the mandatory continuing airworthiness information (MCAI) any comments received, and other information. The street address for Docket Operations is listed above.
                    </P>
                    <P>
                        <E T="03">Material Incorporated by Reference:</E>
                    </P>
                    <P>
                        • For European Union Aviation Safety Agency (EASA) material identified in this proposed AD, contact EASA, Konrad-Adenauer-Ufer 3, 50668 Cologne, Germany; phone: +49 221 8999 000; email: 
                        <E T="03">ADs@easa.europa.eu;</E>
                         website: 
                        <E T="03">easa.europa.eu.</E>
                         You may find this material on the EASA website at 
                        <E T="03">ad.easa.europa.eu.</E>
                    </P>
                    <P>• You may view this material at the FAA, Airworthiness Products Section, Operational Safety Branch, 1200 District Avenue, Burlington, MA 01803. For information on the availability of this material at the FAA, call (817) 222-5110.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Alexis Whitaker, Aviation Safety Engineer, FAA, 2200 South 216th Street, Des Moines, WA 98198; phone: (516) 228-7309; email: 
                        <E T="03">alexis.j.whitaker@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 
                    <E T="02">ADDRESSES</E>
                    . Include “Docket No. FAA-2026-7209; Project Identifier MCAI-2025-00629-E” 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 the 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 
                    <E T="03">regulations.gov</E>
                    , including any personal information you provide. The agency will also post a report summarizing each substantive verbal contact received about this 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 Alexis Whitaker, Aviation Safety Engineer, FAA, 2200 South 216th Street, Des Moines, WA 98198. Any commentary that the FAA receives which is not specifically designated as CBI will be placed in the public docket for this rulemaking.</P>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    The FAA issued AD 2009-04-13, Amendment 39-15819 (74 FR 7643, February 19, 2009) (AD 2009-04-13), for RRD Model BR700-715A1-30, BR700-715B1-30, and BR700-715C1-30 engines, with an LPC compressor (fan) disc assembly, part number (P/N) BRH10048 or P/N BRH19253. AD 2009-04-13 was prompted by an MCAI originated by EASA, which is the Technical Agent for the Member States of the European Union. EASA issued EASA Emergency AD 2007-0116-E, dated May 4, 2007 (EASA Emergency 
                    <PRTPAGE P="40901"/>
                    AD 2007-0116-E) to address the manufacturer revising the engine TLM life limits to introduce new or more restrictive tasks and limitations and associated thresholds and intervals for life-limited parts.
                </P>
                <P>AD 2009-04-13 requires revising the ALS of the operator's existing approved engine maintenance or inspection program, as applicable, to incorporate new or more restrictive tasks and limitations and associated thresholds and intervals for life-limited parts. Additionally, AD 2009-04-13 requires removing LPC compressor (fan) disc assemblies from service that exceed a certain life limit, removing LPC compressor (fan) disc assemblies from service that do not pass the Hawaiian Flight Mission check, and completing the Life Limited Part Tracking Sheet.</P>
                <P>The FAA issued AD 2009-04-13 to prevent failure of critical rotating parts, which, if not addressed, could result in uncontained failure of the low-pressure compressor (fan) disc assembly and damage to the airplane.</P>
                <HD SOURCE="HD1">Actions Since AD 2009-04-13 was Issued</HD>
                <P>Since the FAA issued AD 2009-04-13, EASA superseded EASA Emergency AD 2007-0116-E and issued EASA AD 2025-0086, dated April 16, 2025 (EASA AD 2025-0086) (also referred to as the MCAI). The MCAI states that the manufacturer published a revised engine TLM to introduce new or more restrictive tasks and limitations and associated thresholds and intervals for life-limited parts.</P>
                <P>
                    You may examine the MCAI in the AD docket at 
                    <E T="03">regulations.gov</E>
                     under Docket No. FAA-2026-7209.
                </P>
                <HD SOURCE="HD1">Material Incorporated by Reference Under 1 CFR Part 51</HD>
                <P>The FAA reviewed EASA AD 2025-0086, which specifies revising the ALS of the existing approved engine maintenance or inspection program, as applicable, to incorporate new or more restrictive tasks and limitations and associated thresholds and intervals for life-limited parts.</P>
                <P>
                    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">FAA's Determination</HD>
                <P>These products have been approved by the civil aviation authority (CAA) of another country and are approved for operation in the United States. Pursuant to the FAA's bilateral agreement with this State of Design Authority, that authority has notified the FAA of the unsafe condition described in the MCAI referenced above. 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">Proposed AD Requirements in this NPRM</HD>
                <P>This proposed AD would require accomplishing the actions specified in EASA AD 2025-0086, described previously, as incorporated by reference, except for any differences identified as exceptions in the regulatory text of this AD. See “Differences Between this AD and the MCAI” for a discussion of the general differences included in this AD.</P>
                <HD SOURCE="HD1">Explanation of Required Compliance Information</HD>
                <P>In the FAA's ongoing efforts to improve the efficiency of the AD process, the FAA developed a process to use some CAA ADs as the primary source of information for compliance with requirements for corresponding FAA ADs. The FAA has been coordinating this process with manufacturers and CAAs. As a result, the FAA proposes to incorporate EASA AD 2025-0086 by reference in the FAA final rule. This proposed AD would, therefore, require compliance with EASA AD 2025-0086 in its entirety through that incorporation, except for any differences identified as exceptions in the regulatory text of this proposed AD. Using common terms that are the same as the heading of a particular section in EASA AD 2025-0086 does not mean that operators need comply only with that section. For example, where the AD requirement refers to “all required actions and compliance times,” compliance with this AD requirement is not limited to the section titled “Required Action(s) and Compliance Time(s)” in EASA AD 2025-0086. Material required by EASA AD 2025-0086 for compliance will be available at regulations.gov under Docket No. FAA-2026-7209 after the FAA final rule is published.</P>
                <HD SOURCE="HD1">Differences Between This Proposed AD and the MCAI</HD>
                <P>Where paragraph (3) of EASA AD 2025-0086 specifies revising the approved Aircraft Maintenance Programme (AMP) within 12 months after the effective date of EASA AD 2025-0086, this proposed AD would require revising the ALS of the existing approved engine maintenance or inspection program, as applicable, within 30 days after the effective date of this proposed AD.</P>
                <HD SOURCE="HD1">Costs of Compliance</HD>
                <P>The FAA estimates that this AD, if adopted as proposed, would affect 218 engines installed on airplanes of U.S. registry.</P>
                <P>The FAA estimates the following costs to comply with this proposed AD:</P>
                <GPOTABLE COLS="5" OPTS="L2,nj,i1" CDEF="s50,r100,12,12,12">
                    <TTITLE>Estimated Costs</TTITLE>
                    <BOXHD>
                        <CHED H="1">Action</CHED>
                        <CHED H="1">Labor cost</CHED>
                        <CHED H="1">Parts cost</CHED>
                        <CHED H="1">
                            Cost per
                            <LI>product</LI>
                        </CHED>
                        <CHED H="1">
                            Cost on U.S.
                            <LI>operators</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Revise the ALS</ENT>
                        <ENT>1 work-hour × $85 per hour = $85</ENT>
                        <ENT>$0</ENT>
                        <ENT>$85</ENT>
                        <ENT>$18,530</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 
                    <PRTPAGE P="40902"/>
                    on the distribution of power and responsibilities among the various levels of government.
                </P>
                <P>For the reasons discussed above, I certify that the 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 2009-04-13, Amendment 39-15819 (74 FR 7643, February 19, 2009); and</AMDPAR>
                <AMDPAR>b. Adding the following new airworthiness directive:</AMDPAR>
                <EXTRACT>
                    <P>
                        <E T="04">Rolls-Royce Deutschland Ltd &amp; Co KG:</E>
                         Docket No. FAA-2026-7209; Project Identifier MCAI-2025-00629-E.
                    </P>
                    <HD SOURCE="HD1">(a) Comments Due Date</HD>
                    <P>The FAA must receive comments on this airworthiness directive (AD) by August 20, 2026.</P>
                    <HD SOURCE="HD1">(b) Affected ADs</HD>
                    <P>This AD replaces AD 2009-04-13, Amendment 39-15819 (74 FR 7643, February 19, 2009).</P>
                    <HD SOURCE="HD1">(c) Applicability</HD>
                    <P>This AD applies to all Rolls-Royce Deutschland Ltd &amp; Co KG Model BR700-715A1-30, BR700-715B1-30, and BR700-715C1-30 engines.</P>
                    <HD SOURCE="HD1">(d) Subject</HD>
                    <P>Joint Aircraft System Component (JASC) Code 7200, Engine (Turbine/Turboprop).</P>
                    <HD SOURCE="HD1">(e) Unsafe Condition</HD>
                    <P>This AD was prompted by the manufacturer revising the engine time limits manual to introduce new or more restrictive tasks and limitations and associated thresholds and intervals for life-limited parts. The FAA is issuing this AD to prevent an unsafe condition identified as an uncontained failure of critical rotating parts. The unsafe condition, if not addressed, could result in uncontained failure of the low-pressure compressor (fan) disc assembly and damage to the airplane.</P>
                    <HD SOURCE="HD1">(f) Compliance</HD>
                    <P>Comply with this AD within the compliance times specified, unless already done.</P>
                    <HD SOURCE="HD1">(g) Required Actions</HD>
                    <P>Except as specified in paragraphs (h) and (i) of this AD, perform all required actions within the compliance times specified in, and in accordance with, European Union Aviation Safety Agency (EASA) AD 2025-0086, dated April 16, 2025 (EASA AD 2025-0086).</P>
                    <HD SOURCE="HD1">(h) Exceptions to EASA AD 2025-0086</HD>
                    <P>(1) Where EASA AD 2025-0086 refers to its effective date, this AD requires using the effective date of this AD.</P>
                    <P>(2) This AD does not require compliance with paragraphs (1), (2), (4), and (5) of EASA AD 2025-0086.</P>
                    <P>(3) Where paragraph (3) of EASA AD 2025-0086 specifies “Within 12 months after the effective date of this AD, revise the approved AMP”, this AD requires replacing that text with “Within 30 days after the effective date of this AD, revise the airworthiness limitation section (ALS) of the existing approved engine maintenance or inspection program, as applicable”.</P>
                    <P>(4) This AD does not adopt the “Remarks” section of EASA AD 2025-0086.</P>
                    <HD SOURCE="HD1">(i) Provisions for Alternative Actions and Intervals</HD>
                    <P>No alternative actions and associated thresholds and intervals, including life limits, are allowed for compliance with paragraph (g) of this AD unless they are approved as specified in the provisions of the “Ref. Publications” section of EASA AD 2025-0086.</P>
                    <HD SOURCE="HD1">(j) 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 local Flight Standards District Office, as appropriate. If sending information directly to the manager of the AIR-520 Continued Operational Safety Branch, send it to the attention of the person identified in paragraph (k) of this AD and email to: 
                        <E T="03">AMOC@faa.gov.</E>
                    </P>
                    <P>(2) Before using any approved AMOC, notify your appropriate principal inspector, or lacking a principal inspector, the manager of the local flight standards district office/certificate holding district office.</P>
                    <HD SOURCE="HD1">(k) Additional Information</HD>
                    <P>
                        For more information about this AD, contact Alexis Whitaker, Aviation Safety Engineer, FAA, 2200 South 216th Street, Des Moines, WA 98198; phone: (516) 228-7309; email: 
                        <E T="03">alexis.j.whitaker@faa.gov.</E>
                    </P>
                    <HD SOURCE="HD1">(l) Material Incorporated by Reference</HD>
                    <P>(1) The Director of the Federal Register approved the incorporation by reference (IBR) 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) European Union Aviation Safety Agency (EASA) AD 2025-0086, dated April 16, 2025.</P>
                    <P>(ii) [Reserved].</P>
                    <P>
                        (3) For EASA material identified in this AD, contact EASA, Konrad-Adenauer-Ufer 3, 50668 Cologne, Germany; phone: +49 221 8999 000; email: 
                        <E T="03">ADs@easa.europa.eu;</E>
                         website: 
                        <E T="03">easa.europa.eu.</E>
                         You may find this EASA AD on the EASA website at 
                        <E T="03">ad.easa.europa.eu.</E>
                    </P>
                    <P>(4) You may view this material at FAA, Operational Safety Branch, 1200 District Avenue, Burlington, MA 01803. For information on the availability of this material at the FAA, call (817) 222-5110.</P>
                    <P>
                        (5) You may view this material at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, visit 
                        <E T="03">www.archives.gov/federal-register/cfr/ibr-locations</E>
                         or email 
                        <E T="03">fr.inspection@nara.gov</E>
                        .
                    </P>
                </EXTRACT>
                <SIG>
                    <DATED>Issued on June 30, 2026.</DATED>
                    <NAME>Brian Knaup,</NAME>
                    <TITLE>Acting Deputy Director, Integrated Certificate Management Division, Aircraft Certification Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13541 Filed 7-2-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 Parts 117 and 121</CFR>
                <DEPDOC>[Docket No. FAA-2026-6739; Notice No. 26-06]</DEPDOC>
                <RIN>RIN 2120-AM27</RIN>
                <SUBJECT>Ensuring Passenger Safety by Preempting Duty and Rest Requirements</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), Department of Transportation (DOT).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking (NPRM).</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>FAA proposes to clarify that FAA regulations governing flightcrew member and flight attendant duty and rest periods preempt all State and local meal and rest break requirements. This proposed rule also explains the agency's view that State meal and rest break requirements are preempted by the Airline Deregulation Act of 1978 (ADA) due to their significant impact on air carrier prices, routes, and services.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Send comments on or before September 4, 2026.</P>
                </EFFDATE>
                <ADD>
                    <PRTPAGE P="40903"/>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Send comments identified by docket number FAA-2026-6739 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; U.S. Department of Transportation (DOT), 1200 New Jersey Avenue SE, West Building, 5th Floor (W58-213), Washington, DC 20590.
                    </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 20590 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 the Docket Operations in Room W58-213 of the West Building 5th Floor at 1200 New Jersey Avenue SE, Washington, DC 20590 between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        <E T="03">Technical information:</E>
                         Daniel Kelman, Flight Standards Service, Air Transportation Division, Federal Aviation Administration, 800 Independence Avenue SW, Washington, DC 20591; telephone (202) 267-8166; email 
                        <E T="03">9-AFS-200-Correspondence@faa.gov.</E>
                    </P>
                    <P>
                        <E T="03">Legal information:</E>
                         Adam Siple, Assistant Chief Counsel, Office of the Chief Counsel, Information, Data, and Technology Law Division, Federal Aviation Administration, 800 Independence Avenue SW, Washington, DC 20591; telephone (202) 267-0412; email 
                        <E T="03">9-AGC-AGC300Preemptionquestions@faa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Table of Contents</HD>
                <EXTRACT>
                    <FP SOURCE="FP-1">I. Background and Executive Summary</FP>
                    <FP SOURCE="FP-1">II. Authority for this Rulemaking</FP>
                    <FP SOURCE="FP-1">III. Discussion of the Proposal</FP>
                    <FP SOURCE="FP1-2">A. The Need for FAA to Clarify the Scope of Preemption</FP>
                    <FP SOURCE="FP1-2">B. Field Preemption</FP>
                    <FP SOURCE="FP1-2">C. Conflict with Federal Safety Regulations</FP>
                    <FP SOURCE="FP1-2">D. Airline Deregulation Act Express Preemption</FP>
                    <FP SOURCE="FP1-2">E. Flight Attendant Requirements</FP>
                    <FP SOURCE="FP-1">IV. Regulatory Notices and Analyses</FP>
                    <FP SOURCE="FP1-2">A. Regulatory Impact Analysis</FP>
                    <FP SOURCE="FP1-2">B. Regulatory Flexibility Act</FP>
                    <FP SOURCE="FP1-2">C. International Trade Impact Assessment</FP>
                    <FP SOURCE="FP1-2">D. Unfunded Mandates Assessment</FP>
                    <FP SOURCE="FP1-2">E. Paperwork Reduction Act</FP>
                    <FP SOURCE="FP1-2">F. International Compatibility</FP>
                    <FP SOURCE="FP1-2">G. Environmental Analysis</FP>
                    <FP SOURCE="FP-1">VI. Executive Order Determinations</FP>
                    <FP SOURCE="FP1-2">A. Executive Order 13132, Federalism</FP>
                    <FP SOURCE="FP1-2">B. Executive Order 13211, Regulations that Significantly Affect Energy Supply, Distribution, or Use</FP>
                    <FP SOURCE="FP1-2">C. Executive Order 13609, International Cooperation</FP>
                    <FP SOURCE="FP1-2">D. Executive Order 14192, Unleashing Prosperity Through Deregulation</FP>
                    <FP SOURCE="FP-1">VII. Additional Information</FP>
                    <FP SOURCE="FP1-2">A. Comments Invited</FP>
                    <FP SOURCE="FP1-2">B. Confidential Business Information</FP>
                    <FP SOURCE="FP1-2">C. Electronic Access and Filing</FP>
                    <FP SOURCE="FP1-2">D. Small Business Regulatory Enforcement Fairness Act</FP>
                </EXTRACT>
                <HD SOURCE="HD1">I. Background and Executive Summary</HD>
                <P>Recent litigation prompted FAA to review regulations relating to duty and rest for flightcrew members and flight attendants. To forestall any confusion relating to the preemptive effect of those regulations, FAA proposes clarifying regulations.</P>
                <P>
                    FAA proposes to add § 121.468 to title 14 of the Code of Federal Regulations to clarify and reiterate that FAA's flight attendant duty and rest period regulations preempt State and local laws that are covering the same subject matter.
                    <SU>1</SU>
                     While Federal regulations concerning flightcrew members have consistently preempted State action,
                    <SU>2</SU>
                     there have been efforts to apply some State laws to flight attendants.
                    <SU>3</SU>
                     FAA regulations relating to flightcrew members have consistently preempted State and local labor laws, and FAA proposes new § 117.31 as a conforming amendment to ensure FAA occupies the entire field of flightcrew member regulations to prevent future misapplications of State and local laws or misinterpretations of FAA regulations (as further discussed in section III of this preamble). Further, FAA asserts that the same field and conflict preemption that applies to flightcrew members applies to flight attendants because FAA thoroughly occupies this relevant field and State laws may conflict with FAA safety requirements. FAA proposes these regulations to further assert comprehensive regulation of flight attendant duty and rest to include meal and rest breaks during a duty period.
                </P>
                <P>
                    Like flightcrew members, flight attendants perform critical safety functions. Flight attendants are responsible for taking action during emergencies, including administering first aid, conducting aircraft evacuations, responding to inflight fires, managing medical emergencies, and handling passengers who threaten the safety of other passengers or might be unruly or disruptive.
                    <SU>4</SU>
                     FAA's regulations ensure that flight attendants are available to perform these duties as needed while also ensuring that post duty rest periods provide sufficient time to prevent fatigue. Conflicting State or local laws would create a complex patchwork of regulatory requirements that would frustrate the Federal regulatory scheme and inhibit aviation safety.
                </P>
                <P>Therefore, FAA proposes adding §§ 117.31 and 121.468 to ensure the duty and rest requirements of flightcrew members and flight attendants are subject only to Federal aviation regulations.</P>
                <P>To address the inconsistency created by judicial rulings and to ensure a cohesive national safety standard, FAA proposes a rule clarifying that a single, uniform set of requirements applies to the duty, rest, and break periods for both flightcrew members and flight attendants.</P>
                <P>This proposed rule clarifies that FAA's regulations—including 14 CFR part 117 and 14 CFR 121.467—occupy the entire field of flightcrew member and flight attendant duty and rest, including meal and rest breaks during duty periods. The same principles that support preemption of State meal and rest break laws for pilots should apply with equal force to flight attendants. This proposed rule, moreover, clarifies that air carriers may not permit flightcrew members or flight attendants to take off-duty breaks during a duty period and any State law requiring such breaks conflicts with FAA regulations and is preempted.</P>
                <HD SOURCE="HD1">II. Authority for This Rulemaking</HD>
                <P>
                    FAA's authority to issue rules on aviation safety is found in Title 49 of the United States Code (U.S.C.). 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. Section 44701(a)(4) requires the Administrator to promulgate regulations in the interest of safety for the “maximum hours or periods of service of airmen and other employees of air carriers.” Section 44701(a)(5) requires the Administrator to promulgate “regulations and minimum standards for cybersecurity and other practices, methods, and procedures that the Administrator finds necessary for safety in air commerce and national security.” In addition, 49 U.S.C. 44701(d)(1)(A) specifically states that the Administrator, when prescribing safety regulations, must consider the duty of an air carrier to provide service with the highest possible degree of safety in the public interest. Such authority applies to the oversight FAA 
                    <PRTPAGE P="40904"/>
                    exercises to ensure safety of air carrier operations, including crewmember flight, duty, and rest requirements.
                </P>
                <HD SOURCE="HD1">III. Discussion of the Proposal</HD>
                <HD SOURCE="HD2">A. The Need for FAA To Clarify the Scope of Preemption</HD>
                <P>
                    Recent litigation—most notably 
                    <E T="03">Bernstein</E>
                     v. 
                    <E T="03">Virgin America, Inc.</E>
                     and 
                    <E T="03">Wilson</E>
                     v. 
                    <E T="03">SkyWest Airlines, Inc.</E>
                    <SU>5</SU>
                    —over the applicability of State meal and rest break laws to flight attendants has underscored the need to propose regulations to remove confusion over which laws prevail in this field. Specifically, some State laws 
                    <SU>6</SU>
                     that have been applied to flight attendants pertain to when he or she is on duty or permitted to take time off during their duty period to have a meal or rest break; however, for the reasons discussed below, FAA regulations supersede these State laws and this proposed rule seeks to make that clarification. FAA proposes including paragraphs (b) of §§ 117.31 and 121.468 to clarify and reiterate that FAA's flightcrew member and flight attendant duty and rest period regulations preempt State and local laws related to flightcrew member and flight attendant duty and rest periods, including meal and rest breaks.
                </P>
                <HD SOURCE="HD2">B. Field Preemption</HD>
                <P>
                    Under principles of field preemption, “State law is pre-empted if federal law so thoroughly occupies a legislative field as to make reasonable the inference that Congress left no room for the States to supplement it.” 
                    <SU>7</SU>
                     When “Congress has entrusted an agency with the task of promulgating regulations to carry out the purposes of a statute, as part of the preemption analysis [courts] must consider whether the regulations evidence a desire to occupy a field completely.” 
                    <SU>8</SU>
                     Further, “if the pervasiveness of the regulations indicate that the agency sought to occupy the field, the question is whether that action was within the scope of the agency's delegated authority.” 
                    <SU>9</SU>
                </P>
                <P>
                    Congress has given FAA comprehensive authority to ensure the safety of air travel and the efficient use of the airspace.
                    <SU>10</SU>
                     This includes a specific statutory mandate to regulate “the maximum hours or periods of service of airmen and other employees of air carriers . . . .” 
                    <SU>11</SU>
                     FAA has issued regulations that cover every aspect of aviation safety. Consistent with FAA's statutory mandate, these regulations include duty and rest regulations for flightcrew members and flight attendants. FAA regulations require airlines to provide flight attendants on each flight and contemplate that those flight attendants will be available to ensure passenger safety.
                    <SU>12</SU>
                     FAA imposes specific requirements related to flight attendant number and activities during boarding, takeoff, landing, taxi, deplaning, and when passengers are on board a stationary aircraft on the ground.
                    <SU>13</SU>
                     FAA has also issued detailed regulations setting the maximum length of flight attendant duty periods and minimum length of flight attendant rest periods.
                    <SU>14</SU>
                     Through these regulations, FAA has not only occupied the field of aviation safety generally, but has specifically occupied the field of flight attendant duty regulations, consistent with the statutory requirement that it regulate “the maximum hours or periods of service of airmen and other employees of air carriers.” 
                    <SU>15</SU>
                     Therefore, State and local laws pertaining to flight attendant duty or rest periods, including rest and meal breaks, are preempted by FAA's regulations because FAA thoroughly occupies this relevant field and issues these kinds of regulations in accordance with its statutory authority.
                </P>
                <P>Despite this Federal regulatory framework, FAA is aware of efforts to apply State meal and rest break laws to flight attendants, including when those flight attendants are on board an aircraft in flight. This proposed rule clarifies that such State requirements are preempted. This proposed rule also intends to fill any potential gap in the field of FAA's regulation of flight attendant duty and rest, including meal and rest breaks, with provisions requiring air carriers to ensure flight attendants are available to perform safety-related responsibilities during a flight duty period, while also providing allowance for meeting physiological needs. Air carriers already incorporate meal and rest breaks for flight attendants in their operations as necessary and these provisions are not intended to alter the Federal regulatory status quo. FAA invites comments on any unintended effect of these provisions on air carrier operations.</P>
                <HD SOURCE="HD2">C. Conflict With Federal Safety Regulations</HD>
                <P>
                    State laws, including the California law at issue in 
                    <E T="03">Bernstein,</E>
                     are preempted when they conflict with Federal law. FAA regulations define duty periods for flightcrew members and flight attendants and are designed to ensure that flightcrew members and flight attendants are available to perform critical safety duties.
                    <SU>16</SU>
                     To the extent that a State law purports to restrict the availability of a flightcrew member or a flight attendant to perform their safety-related duties during a duty period, such a law conflicts with the Federal regulatory framework and is preempted.
                </P>
                <P>
                    Under 14 CFR 121.467(a), the “duty period” for a flight attendant is defined as the elapsed time from reporting for an assignment until the final release. Under 14 CFR 117.3, the “flight duty period” for a flightcrew member is defined as “a period when a flightcrew member is required to report for duty with the intention of conducting a flight * * * and ends when the aircraft is parked for the last flight and there is no intention for further aircraft movement.” For both flightcrew members and flight attendants, this duty period can include times before, between, and after flights. FAA regulations require that flightcrews remain on-duty and on-call throughout this entire period to respond to safety needs. Various State laws require employees on break to be relieved of all duty or employer control and free to come and go.
                    <SU>17</SU>
                     Applying this requirement to a flight in progress is physically impossible, as a flight attendant or flightcrew member cannot be free to come and go while mid-flight. These laws would also present clear and significant safety risks.
                </P>
                <P>
                    The primary mission of flight attendants is to ensure safety, a role that is undermined if a flight attendant is legally “off-duty” during an emergency. Flight attendants need to be ready to manage land and water evacuations, control inflight fires, manage medical emergencies, and handle unruly passengers among other tasks. In the event an emergency evacuation is necessary, flight attendants must need to be available immediately to assist when mere seconds can make a difference in the number of fatalities involved.
                    <SU>18</SU>
                </P>
                <P>
                    In addition, safety response relies on highly coordinated teamwork among flight attendants and flightcrew members. FAA regulations require airlines to provide FAA-approved crew resource management training to flightcrew members and flight attendants.
                    <SU>19</SU>
                     This FAA-required training as part of an FAA-approved air carrier training program serves to ensure appropriate interaction between flightcrew members and flight attendants, especially during emergency situations. This training contemplates flightcrew members and flight attendants who are not only available, but are required to perform safety functions. State laws mandating that flightcrew members or flight attendants be “off-duty” and free from responsibility during any portion of a duty period would conflict with this FAA-required crew resource management training, which is not 
                    <PRTPAGE P="40905"/>
                    designed to manage crew unavailability due to State laws.
                </P>
                <P>
                    In contrast to these State laws that present safety risk, FAA's regulations are intended to increase safety through fatigue mitigation, which FAA addresses by regulating rest periods between shifts rather than during them. Most recently, at Congress's direction,
                    <SU>20</SU>
                     FAA issued the 2022 Final Rule increasing the mandatory rest period for flight attendants to 10 consecutive hours to ensure they receive adequate rest and are fully recovered before starting a new duty period.
                    <SU>21</SU>
                </P>
                <P>Flightcrews function as highly coordinated safety teams. Rotating “on-duty” and “off-duty” members during a single flight segment increases the risk of confusion and undermines safety protocols. This is especially true since FAA regulations apply to all flight attendants on board a flight, not just a minimum required number. There is no Federal provision that allows a “surplus” attendant to be entirely off-duty and unresponsive while the aircraft is in operation.</P>
                <P>There are also economic impacts that increased flight attendant coverage would impose. Forcing airlines to block passenger seats for “relief” crew members reduces available capacity, increases ticket prices, and may make low-margin regional routes economically unviable. Finally, even with extra staff, the requirement for a crew member to be “free of all restraint” cannot be met while they are confined to an aircraft in flight.</P>
                <P>
                    In contrast to general-purpose State meal and rest break laws, FAA believes that the existing status quo under FAA regulations, which is a result of both FAA's rules about duty periods, collective bargaining agreements (CBA) reached between air carriers and labor unions, and other industry standards and specific air carrier crew resource management procedures, provides the appropriate policy balance. These provide a specialized, industry-specific balance between flight attendant health and aviation safety and utilize tailored provisions concerning meals and other rest breaks 
                    <SU>22</SU>
                     that do not conflict with FAA regulations or otherwise trigger the dangerous safety and operational conflicts inherent in rigid, “off-duty” State mandates. Although at this time FAA is not proposing to codify the approach taken in any specific CBA or crew resource management procedure, FAA is requesting comment on whether to do so in the final rule. In particular, if FAA proceeds to a final rule FAA seeks comments on what specific terms should be included in a regulation to ensure that safety is maintained without unnecessarily constricting any future agreements between air carriers and labor unions or air carrier procedures. FAA also seeks comments on if additional guidance material would be desirable on FAA regulations relating to flight attendant rest and duty periods or preemption.
                </P>
                <HD SOURCE="HD2">D. Airline Deregulation Act Express Preemption</HD>
                <P>
                    FAA believes its occupation of the field in aviation safety and the efficiency of the airspace and conflicts with its existing regulations concerning flight duty and rest are sufficient to show that State meal and rest break requirements are preempted. That said, these laws, if not preempted, would also have a “significant impact” on airline prices, routes, and services and thus are also preempted under the Airline Deregulation Act of 1978 (ADA),
                    <SU>23</SU>
                     which was enacted to ensure that the “maximum reliance on competitive market forces” remains the primary driver of efficiency, innovation, and low prices in the aviation industry.
                </P>
                <P>
                    To protect this Federal interest, the ADA's express preemption provision prohibits States from enacting or enforcing any law “related to a price, route, or service of an air carrier.” The Supreme Court has made clear that this preemption provision is to be read expansively, first in 
                    <E T="03">Morales</E>
                     v. 
                    <E T="03">Trans World Airlines, Inc.,</E>
                    <SU>24</SU>
                     and again in 
                    <E T="03">Rowe</E>
                     v. 
                    <E T="03">New Hampshire Motor Transportation Ass' </E>
                    <SU>25</SU>
                     The Supreme Court established in 
                    <E T="03">Morales</E>
                     v. 
                    <E T="03">Trans World Airlines, Inc.</E>
                     that State laws are preempted if they have a “significant impact” on airline rates. Complying with State laws would require airlines to hire additional crew members to stagger “off-duty” breaks, which would have direct labor and operational costs. Airlines would be forced to block off passenger seats to accommodate relief crew members, foregoing the revenue that could have been made through the sale of those seats. On regional aircraft with limited seating, the loss of even one or two seats for additional crew can eliminate the economic viability of the flight and may result in the elimination of low margin routes serving small communities. Applying these changes to the flights across their networks would result in significant costs to the airlines. These increased costs would inevitably be passed to consumers through significantly higher ticket prices.
                </P>
                <P>
                    Finally, a central purpose of the ADA's preemption clause is to prevent a patchwork of varying State requirements that would interfere with interstate commerce. State meal and rest break laws are not uniform and may at times be conflicting. For example, New York's labor laws require meal breaks at specific times of day (
                    <E T="03">e.g.,</E>
                     between 11:00 a.m. and 2:00 p.m.), while other States may use different intervals. Airlines providing interstate service are not required to and cannot practically track and comply with disparate laws for every crew member across different States on a single flight. This complexity creates regulatory uncertainty that disrupts standard nationwide scheduling and staffing practices which in turn has a significant effect on airline services, contrary to the prohibitions on State action in the ADA.
                </P>
                <P>
                    Unlike short-haul truck drivers, an inapt parallel drawn in 
                    <E T="03">Bernstein,</E>
                     airline crews cannot readily interrupt operations to accommodate State-mandated breaks without fundamentally altering and affecting the services and prices Congress intended to deregulate. Such a regime of multiple, conflicting State meal and rest break requirements would frustrate airlines' ability to provide safe, efficient and timely service to the travelling public throughout the United States.
                </P>
                <HD SOURCE="HD2">E. Flight Attendant Requirements</HD>
                <P>
                    In 14 CFR 121.467(a), a flight attendant serving in part 121 operations is defined as an individual, other than a flightcrew member, who is assigned by a certificate holder to duty in an aircraft during flight time and whose duties include activities related to ensuring cabin safety.
                    <SU>26</SU>
                     Section 121.391 specifies the minimum number of flight attendants required on board a flight, based on maximum payload capacity and seating capacity, for certificate holders conducting passenger-carrying operations under part 121.
                    <SU>27</SU>
                     Flight attendants are responsible for taking action during emergencies, including administering first aid, conducting aircraft evacuations, responding to inflight fires, managing medical emergencies, and handling passengers who threaten the safety of other passengers or might be unruly or disruptive.
                    <SU>28</SU>
                     They also need to be prepared to respond to situations that could threaten the safety of the passengers and the flight, including turbulent air, airplane decompression, and hijackings. Flight attendants need to know the location of emergency exits, fire extinguishers, first aid kits, flotation devices, oxygen masks, and emergency slides, and check emergency equipment before flight. In addition, they need to assess and verify the suitability of passengers that occupy exit seating, brief passengers on safety equipment and evacuation and emergency landing procedures, and ensure compliance 
                    <PRTPAGE P="40906"/>
                    with applicable safety and security regulations. A flight attendant needs to be able to perform these responsibilities during their duty period.
                </P>
                <P>
                    Under 14 CFR 121.467, duty period is defined as “the period of elapsed time between reporting for an assignment involving flight time and release from that assignment by the certificate holder conducting domestic, flag or supplemental operations.” FAA establishes duty period limitations to ensure flight attendants do not become overly fatigued during flight assignments to enhance the safety of the flying public.
                    <SU>29</SU>
                     In addition, the duty period limitations are designed to suit all operations that require flight attendants without imposing a significant burden on operators.
                    <SU>30</SU>
                </P>
                <P>A designated “off-duty” meal or rest break during a flight attendant's duty period when he or she would be unavailable to perform cabin safety-related responsibilities would pose a risk to aviation safety.</P>
                <P>
                    Flight attendants serve as a core component in cabin safety responsibilities. One of those responsibilities includes handling passengers who threaten the safety of other passengers or might be unruly or disruptive. Over the past five years, FAA received 14,343 reports of unruly passengers on flights.
                    <SU>31</SU>
                     Flight attendants handle these passengers to ensure the safety of other passengers. If a flight attendant is permitted during their duty period to be relieved of their safety responsibilities, including handling unruly passengers (
                    <E T="03">e.g.,</E>
                     a meal or rest break), there would be a critical gap in cabin safety coverage during the flight. In this situation, a flight attendant may not be available to handle a passenger's disruptive or violent behavior that could harm other passengers or cause risk to the operation of the aircraft. Flight attendants need to be available and ready to perform safety procedures during their duty period.
                </P>
                <P>
                    Another example of the aviation safety need for flight attendants to remain on duty during their duty period and perform safety responsibilities is the growing number of lithium battery events involving smoke, fire, or extreme heat in the aircraft cabin. Passengers frequently carry portable electronic devices powered by lithium-ion batteries, including cell phones, laptops, portable rechargers, watches, and cameras. As more of these lithium-ion battery devices are introduced to the aircraft cabin, the risk of smoke, fire, or extreme heat increases. Between March 3, 2006 and January 8, 2026, there were 693 verified incidents of lithium battery related events involving, smoke, fire or extreme heat.
                    <SU>32</SU>
                     The frequency of incidents has increased progressively from 39 incidents in 2020 to 93 incidents in 2025.
                    <SU>33</SU>
                     Flight attendants need to respond quickly to such an event to mitigate the risk of onboard lithium battery fires; this need is heightened given the likelihood that the number of these events will continue to increase. As previously stated, if a flight attendant was relieved of their safety responsibilities during a duty period, then he or she would not be responsible for responding to an emergency such as a fire, thus placing aviation safety at risk.
                </P>
                <P>
                    Therefore, FAA proposes new §§ 117.31(a) and 121.468(a) to ensure that FAA regulation of flight attendant and flightcrew member duty and rest periods preempt State and local laws and to clarify the availability of meal and rest breaks for flight attendants while on duty. Including meal or rest breaks during a duty period in which the flight attendant is relieved from all responsibilities does not enhance the safety of the flying public nor does it relieve a burden on certificate holders. As with pilots, FAA recognizes flight attendants will have physiological needs (
                    <E T="03">e.g.,</E>
                     using the restroom and consuming food and drink) during their duty period. Given this context, FAA understands many CBAs between certificate holders and labor unions or certificate holder's standard operating procedures cover the topic of physiological needs (
                    <E T="03">e.g.,</E>
                     meal and rest breaks). As such, FAA intends for certificate holders to determine how to ensure that all flight attendants are available to perform safety-related responsibilities and also be able to meet physiological needs during a duty period.
                </P>
                <P>
                    FAA proposes a conforming amendment by adding § 117.31(a) to forestall any confusion for flightcrew members responsibilities and to avoid any implication that FAA does not intend to preempt State and local law with regard to flightcrew members.
                    <SU>34</SU>
                </P>
                <P>In addition, because an air carrier may apply the duty and rest provisions of part 117 to flight attendants, pursuant to § 121.467(c), FAA believes it is necessary to include conforming amendments in part 117.</P>
                <P>
                    Finally, FAA proposes a technical amendment to revise the authority citation for 14 CFR part 117 that would remove the citation to title 49 of the United States Code (49 U.S.C.) 106(g) to reflect amendments resulting from the FAA Reauthorization Act of 2024 and would add the citation to 49 U.S.C. 106(f) to reflect FAA's current statutory rulemaking authority.
                    <SU>35</SU>
                </P>
                <HD SOURCE="HD1">IV. Regulatory Notices and Analyses</HD>
                <HD SOURCE="HD2">A. Regulatory Impact Analysis</HD>
                <P>Executive Orders 12866 (“Regulatory Planning and Review”) and 13563 (“Improving Regulation and Regulatory Review”) require agencies to regulate in the “most cost-effective manner,” to make a “reasoned determination that the benefits of the intended regulation justify its costs,” and to develop regulations that “impose the least burden on society.” The Office of Management and Budget determined this proposed rule is a significant regulatory action as defined in section 3(f) of Executive Order (E.O.) 12866.</P>
                <P>The decision in Bernstein and the potential for similar litigation to apply state meal and rest break laws to flight attendants presents the possibility of airlines having to comply with a patchwork of requirements. These requirements could also affect individual flight attendants at the same airline differently. There have been efforts to mitigate the decision—in March of 2023, the State of California amended its Labor Code (§ 512.2) to exempt flight attendants from standard meal and rest period requirements if they are covered by a CBA that addresses these breaks. However, not all airlines are covered by collective bargaining agreements.</P>
                <P>The proposed rule would clarify that FAA regulations pertaining to flightcrew member and flight attendant duty and rest periods preempt state-mandated meal and rest break laws. In doing so, the proposed rule would prevent the potential patchwork of requirements that could result through litigation. State meal and rest break requirements differ and the nature and result of any future litigation is unknown. Also unknown are subsequent actions, such as the amendment to California Labor Code, that might mitigate the impact of any decisions. However, the types of impacts industry may avoid by not having to comply with different state requirements include staffing flights with additional flight attendants; reserving passenger seats for additional flight attendants; disruption to flight operations; and wider route implications from increased costs. Airlines may also experience efficiency gains from only having to track and comply with FAA regulations for flight attendants.</P>
                <P>
                    In comparison, the ruling in 
                    <E T="03">Bernstein</E>
                     resulted in damages payable to flight attendants who were not afforded State mandated meal and rest breaks. The proposed rule would clarify that these State laws do not apply to flight attendants and prevent or discourage 
                    <PRTPAGE P="40907"/>
                    similar litigation. While airlines would not have to comply with the State requirements, flight attendants would also not be afforded any incremental breaks compared to those already identified in CBAs or airline policies.
                </P>
                <P>In summary, FAA anticipates the proposed rule will prevent airlines from having to comply with differing State meal and rest break requirements for flight attendants that could be costly and disruptive to operations. Flight attendants would not receive meal and rest breaks based on State laws and would instead continue under existing CBAs and airline policies. FAA requests comments on this analysis and the identified uncertainties.</P>
                <HD SOURCE="HD2">B. Regulatory Flexibility Act</HD>
                <P>The Regulatory Flexibility Act (RFA) of 1980, (5 U.S.C. 601-612), as amended by the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121) and the Small Business Jobs Act of 2010 (Pub. L. 111-240), requires Federal agencies to consider the effects of the regulatory action on small business and other small entities and to minimize any significant economic impact. The term “small entities” comprises small businesses and not-for-profit organizations independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000.</P>
                <P>If an agency determines a rulemaking will not result in a significant economic impact on a substantial number of small entities, the head of the agency may so certify under section 605(b) of the RFA. The proposed rule does not impose costs on any entities, including small entities (individuals are not small entities under the RFA). Also, the economic impacts of this rule with respect to cost savings are uncertain as they relate to potential future litigation. Therefore, FAA certifies the proposed rule would not result in a significant economic impact on a substantial number of small entities. FAA solicits comments regarding this determination.</P>
                <HD SOURCE="HD2">C. International Trade Impact Assessment</HD>
                <P>The Trade Agreements Act of 1979 (Pub. L. 96-39), as amended by the Uruguay Round Agreements Act (Pub. L. 103-465), prohibits Federal agencies from establishing standards or engaging in related activities that create unnecessary obstacles to the foreign commerce of the United States. Pursuant to these Acts, the establishment of standards is not considered an unnecessary obstacle to the foreign commerce of the United States, so long as the standard has a legitimate domestic objective, such as the protection of safety and does not operate in a manner that excludes imports that meet this objective. The statute also requires consideration of international standards and, where appropriate, that they be the basis for U.S. standards.</P>
                <P>FAA has assessed the potential effect of this proposed rule and determined it ensures the safety of the American public and does not exclude imports that meet this objective. As a result, FAA does not consider this proposed rule as creating an unnecessary obstacle to foreign commerce.</P>
                <HD SOURCE="HD2">D. Unfunded Mandates Assessment</HD>
                <P>The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) governs the issuance of Federal regulations that require unfunded mandates. An unfunded mandate is a regulation that requires a State, local, or Tribal government or the private sector to incur direct costs without the Federal Government having first provided the funds to pay those costs. FAA determined the proposed rule would not result in the expenditure of $187,000,000 or more ($100,000,000 adjusted for inflation using the most current Implicit Price Deflator for the Gross Domestic Product) by State, local, or Tribal governments, in the aggregate, or the private sector, in any one year.</P>
                <HD SOURCE="HD2">E. Paperwork Reduction Act</HD>
                <P>The Paperwork Reduction Act of 1995 (44 U.S.C. 3507(d)) requires FAA to consider the impact of paperwork and other information collection burdens imposed on the public. FAA has determined there would be no new requirement for information collection associated with this proposed rule.</P>
                <HD SOURCE="HD2">F. International Compatibility</HD>
                <P>In keeping with U.S. obligations under the Convention on International Civil Aviation, it is FAA policy to conform to International Civil Aviation Organization (ICAO) Standards and Recommended Practices to the maximum extent practicable. FAA has determined that there are no ICAO Standards and Recommended Practices that correspond to these regulations.</P>
                <HD SOURCE="HD2">G. Environmental Analysis</HD>
                <P>
                    FAA has analyzed the environmental impacts of this proposed rule pursuant to the National Environmental Policy Act of 1969 (NEPA) (42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ). FAA has determined this rule is categorically excluded pursuant to Paragraph B-2.6(f) of appendix B to FAA Order 1050.1G, FAA National Environmental Policy Act Implementing Procedures.
                    <SU>36</SU>
                     Categorical exclusions are categories of actions the agency has determined normally do not significantly affect the quality of the human environment and therefore do not require either an environmental assessment (EA) or environmental impact statement (EIS).
                    <SU>37</SU>
                     In analyzing the applicability of a categorical exclusion, the agency must also consider whether extraordinary circumstances are present that would warrant the preparation of an EA or EIS.
                    <SU>38</SU>
                     In analyzing the applicability of a categorical exclusion, the agency must also consider whether extraordinary circumstances are present that would warrant the preparation of an EA or EIS.
                    <SU>39</SU>
                     This rulemaking, which proposes to preempt duty and rest requirements to ensure passenger safety, is categorically excluded pursuant to Paragraph B-2.6f of FAA Order 1050.1G: “Regulations, standards, and exemptions (excluding those that if implemented may cause a significant impact on the human environment.” FAA does not anticipate any environmental impacts, and there are no extraordinary circumstances present in connection with this rulemaking.
                </P>
                <HD SOURCE="HD1">V. Executive Order Determinations</HD>
                <HD SOURCE="HD2">A. Executive Order 13132, Federalism</HD>
                <P>
                    FAA has analyzed this proposed rule under the principles and criteria of Executive Order (E.O.) 13132, Federalism. This proposed rule has “federalism implications” as defined by E.O. 13132, because it would have a “substantial direct effect” on the States and on the relationship between the Federal Government and the States. In accordance with section 2 of E.O. 13132, FAA has determined that the problem of inconsistent aircraft crew duty regulations is of “national significance” and requires a uniform Federal solution. Under section 4, an agency may only preempt State law when a statute contains express preemption or there is “clear evidence” that Congress intended preemption. FAA relies on the express preemption provision of the ADA (49 U.S.C. 41713(b)(1)) and clear evidence that State meal and rest break laws and rules “directly conflict” with Federal safety objectives. FAA has restricted this preemption to the “minimum level necessary” to achieve the safety and economic objectives of the Federal Aviation Act and the ADA. With regard to consultation with State and local officials, FAA has been clear throughout the litigation in 
                    <E T="03">Bernstein</E>
                     that it believes that these laws should be preempted and, in this NPRM, requests 
                    <PRTPAGE P="40908"/>
                    comment from States and local governments on this issue.
                </P>
                <HD SOURCE="HD2">B. Executive Order 13211, Regulations that Significantly Affect Energy Supply, Distribution, or Use</HD>
                <P>FAA analyzed this proposed rule under Executive Order 13211, Actions Concerning Regulations that Significantly Affect Energy Supply, Distribution, or Use. FAA has determined it would not be a “significant energy action” under the Executive order and would not be likely to have a significant adverse effect on the supply, distribution, or use of energy.</P>
                <HD SOURCE="HD2">C. Executive Order 13609, Promoting International Regulatory Cooperation</HD>
                <P>Executive Order 13609, Promoting International Regulatory Cooperation, promotes international regulatory cooperation to meet shared challenges involving health, safety, labor, security, environmental, and other issues and to reduce, eliminate, or prevent unnecessary differences in regulatory requirements. FAA has analyzed this action under the policies and agency responsibilities of Executive Order 13609 and has determined this action would have no effect on international regulatory cooperation.</P>
                <HD SOURCE="HD2">D. Executive Order 14192, Unleashing Prosperity Through Deregulation</HD>
                <P>This proposed rule, if finalized as proposed, is expected to be an Executive Order 14192 deregulatory action.</P>
                <HD SOURCE="HD1">VI. Additional Information</HD>
                <HD SOURCE="HD2">A. Comments Invited</HD>
                <P>FAA invites interested persons to participate in this rulemaking by submitting written comments, data, or views. FAA also invites comments relating to the economic, environmental, energy, or federalism impacts that might result from adopting the proposals in this document. 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>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 rule. Before acting on this proposal, FAA will consider all comments it receives on or before the closing date for comments. FAA will consider comments filed after the comment period has closed if it is possible to do so without incurring expense or delay. 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. 553(c), FAA solicits comments from the public to inform its rulemaking process better. FAA posts these comments, without edit, including any personal information the commenter provides, to 
                    <E T="03">www.regulations.gov,</E>
                     as described in the system of records notice (DOT/ALL-14 FDMS), which can be reviewed at 
                    <E T="03">www.dot.gov/privacy.</E>
                </P>
                <HD SOURCE="HD2">B. Confidential Business Information</HD>
                <P>
                    Confidential Business Information (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 you clearly designate the submitted comments as CBI. Please mark each page of your submission containing CBI as “PROPIN.” 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 the person in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section of this document. Any commentary FAA receives which is not specifically designated as CBI will be placed in the public docket for this rulemaking.
                </P>
                <HD SOURCE="HD2">C. Electronic Access and Filing</HD>
                <P>
                    A copy of this NPRM, all comments received, any final rule, and all background material may be viewed online at 
                    <E T="03">www.regulations.gov</E>
                     using the docket number listed above. Electronic retrieval help and guidelines are available on the website. It is available 24 hours each day, 365 days each year. An electronic copy of this document may also be downloaded from the Office of the Federal Register's website at 
                    <E T="03">www.federalregister.gov</E>
                     and the Government Publishing Office's website at 
                    <E T="03">www.govinfo.gov.</E>
                     A copy may also be found at FAA's Regulations and Policies website at 
                    <E T="03">www.faa.gov/regulations_policies.</E>
                </P>
                <P>Copies may also be obtained by sending a request to the Federal Aviation Administration, Office of Rulemaking, ARM-1, 800 Independence Avenue SW, Washington, DC 20591, or by calling (202) 267-9677. Commenters must identify the docket or notice number of this rulemaking.</P>
                <P>All documents FAA considered in developing this proposed rule, including economic analyses and technical reports, may be accessed in the electronic docket for this rulemaking.</P>
                <HD SOURCE="HD2">D. Small Business Regulatory Enforcement Fairness Act</HD>
                <P>
                    The Small Business Regulatory Enforcement Fairness Act (SBREFA) of 1996 requires FAA to comply with small entity requests for information or advice about compliance with statutes and regulations within its jurisdiction. A small entity with questions regarding this document may contact its local FAA official, or the person listed under the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     heading at the beginning of the preamble. To find out more about SBREFA on the internet, visit 
                    <E T="03">www.faa.gov/regulations_policies/rulemaking/sbre_act/.</E>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         FAA also proposes a conforming amendment to § 117.31(b) to mirror the proposed language in § 121.468(b) to reiterate FAA regulations preempt State laws.
                    </P>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See Ventress</E>
                         v. 
                        <E T="03">Japan Airlines,</E>
                         747 F.3d 716 (9th Cir. 2014); 
                        <E T="03">Kohr</E>
                         v. 
                        <E T="03">Allegheny Airlines, Inc.,</E>
                         504 F.2d 400, 404 (7th Cir. 1974); 
                        <E T="03">French</E>
                         v. 
                        <E T="03">Pan Am Exp., Inc.,</E>
                         869 F.2d 1, 5 (1st Cir. 1989).
                    </P>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See, e.g., Bernstein</E>
                         v. 
                        <E T="03">Virgin Am., Inc.,</E>
                         3 F.4th 1127 (9th Cir. 2021).
                    </P>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">Flight Attendant Duty Period Limitations and Rest Requirements</E>
                         final rule, 87 FR 61452 (Oct. 12, 2022).
                    </P>
                    <P>
                        <SU>5</SU>
                         No. 19-CV-01491-VC, 2021 WL 2913656 (1 (N.D. Cal. July 12, 2021) (“The plaintiffs' meal and rest break claims are not preempted by either the Airline Deregulation Act or the Federal Aviation Act. This result is compelled by the Ninth Circuit's decision in 
                        <E T="03">Bernstein</E>
                         v. 
                        <E T="03">Virgin America, Inc.,</E>
                         where the court held that California's meal and rest break requirements were not preempted by either statute as applied to the airline industry. 990 F.3d 1157, 1167-1170 (9th Cir. 2021).”).
                    </P>
                    <P>
                        <SU>6</SU>
                         See Colo. Code Regs. § 1103-1-5.1; Mass. Gen. Laws ch. 149, §§ 100-101; Minn. R. 5200.0120(4); Or. Admin. R. 839-020-0050(2)(a). See Cal. Lab. Code § 512; 7 Colo. Code Regs. § 1103-1-5.1; Conn. Gen. Stat. § 31-51ii(a); Del. Code Ann. tit. 19, § 707(a); 820 Ill. Comp. Stat. 140/3; Ky. Rev. Stat. Ann. § 337.355; Me. Rev. Stat. Ann. tit. 26, § 601; Mass. Gen. Laws ch. 149, §§ 100-01; Minn. Stat. § 177.254(3); Minn. R. 5200.0120(4); Nev. Rev. Stat. § 608.019(1); N.H. Rev. Stat. § 275:30-A; N.Y. Lab. Law § 162; N.D. Admin. Code 46-02-07-02(5); Or. Admin. R. 839-020-0050(2); R.I. Gen. Laws § 28-3-14; Tenn. Code Ann. § 50-2-103(h); Wash. Admin. Code § 296-126-092(1); W. Va. Code § 21-3-10a.
                    </P>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">Nat'l Fed'n of the Blind</E>
                         v. 
                        <E T="03">United Airlines, Inc.,</E>
                         813 F.3d 718, 733 (9th Cir. 2016).
                    </P>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See, e.g.,</E>
                         49 U.S.C. 44701(a) (requiring FAA to issue regulations to “promote safe flight of civil aircraft in air commerce”); id. § 40103(b)(2) (requiring FAA to “prescribe air traffic regulations”).
                    </P>
                    <P>
                        <SU>11 </SU>
                         49 U.S.C. 44701(a)(4).
                        <PRTPAGE/>
                    </P>
                    <P>
                        <SU>12</SU>
                         14 CFR 121.391.
                    </P>
                    <P>
                        <SU>13</SU>
                         14 CFR 121.391(d), 121.393, 121.394.
                    </P>
                    <P>
                        <SU>14</SU>
                         14 CFR 121.467.
                    </P>
                    <P>
                        <SU>15</SU>
                         49 U.S.C. 44701(a)(4).
                    </P>
                    <P>
                        <SU>16</SU>
                         See 14 CFR 117.3 and 14 CFR 121.467.
                    </P>
                    <P>
                        <SU>17</SU>
                         See footnote 7.
                    </P>
                    <P>
                        <SU>18</SU>
                         
                        <E T="03">See</E>
                         14 CFR 25.803 (FAA airworthiness regulation that requires a demonstration that an airplane can be evacuated within 90 seconds under simulated emergency conditions).
                    </P>
                    <P>
                        <SU>19</SU>
                         14 CFR 121.404.
                    </P>
                    <P>
                        <SU>20</SU>
                         Section 335(a) of the FAA Reauthorization Act of 2018 (Pub. L. 115-254, 132 Stat. 3186 (Oct. 5, 2018), codified at 49 U.S.C. 44701 note.
                    </P>
                    <P>
                        <SU>21</SU>
                         
                        <E T="03">See Flight Attendant Duty Period Limitations and Rest Requirements</E>
                         final rule, 87 FR 61452 at 61457.
                    </P>
                    <P>
                        <SU>22</SU>
                         
                        <E T="03">See, e.g.,</E>
                         CBA between American Airlines and AFPA, Section 4 (Expenses) and Section 38 (Crew Rest), available at 
                        <E T="03">www.apfa.org/contract/;</E>
                         CBA Between Alaska Airlines and AFPA, Letter of Agreement 10, “Flight Attendant Onboard Breaks,” available at 
                        <E T="03">https://afaalaska.org/wp-content/uploads/2025/11/2025-2028-AFA-Alaska-CBA-Interim-Document-11.21.2025.pdf.</E>
                    </P>
                    <P>
                        <SU>23</SU>
                         Pub. L. 95-504, 92 Stat. 1705 (Oct. 24, 1978).
                    </P>
                    <P>
                        <SU>24</SU>
                         504 U. S. 374 (1992).
                    </P>
                    <P>
                        <SU>25</SU>
                         552 U.S. 364 (2008).
                    </P>
                    <P>
                        <SU>26</SU>
                         14 CFR 121.467(a).
                    </P>
                    <P>
                        <SU>27</SU>
                         14 CFR 121.391 provides that a certificate holder may, however, use more than the required number of flight attendants.
                    </P>
                    <P>
                        <SU>28</SU>
                         
                        <E T="03">See generally Flight Attendant Duty Period Limitations and Rest Requirements</E>
                         final rule, 87 FR 61452 (Oct. 12, 2022).
                    </P>
                    <P>
                        <SU>29</SU>
                         
                        <E T="03">Flight Attendant Duty Period Limitations and Rest Requirements</E>
                         59 
                        <E T="04">Federal Register</E>
                         42977-42978 (Aug. 19, 1994).
                    </P>
                    <P>
                        <SU>30</SU>
                         Id. at 42978.
                    </P>
                    <P>
                        <SU>31</SU>
                         Federal Aviation Administration, “Dangerous Behavior Doesn't Fly,” 
                        <E T="03">www.faa.gov/unruly.</E>
                    </P>
                    <P>
                        <SU>32</SU>
                         Federal Aviation Administration, “Lithium Battery Incidents” 
                        <E T="03">www.faa.gov/hazmat/resources/lithium_batteries/incidents.</E>
                    </P>
                    <P>
                        <SU>33</SU>
                         Id.
                    </P>
                    <P>
                        <SU>34</SU>
                         FAA does not intend to alter the status quo of flightcrew member 
                        <E T="03">duty</E>
                         as defined in § 117.3 and the definition of a 
                        <E T="03">flightcrew member</E>
                         in § 1.1.
                    </P>
                    <P>
                        <SU>35</SU>
                         Pub. L. 118-63, sec. 204, 138 Stat. 1041 (May 16, 2024).
                    </P>
                    <P>
                        <SU>36</SU>
                         90 FR 29615 (Jul. 3, 2025).
                    </P>
                    <P>
                        <SU>37</SU>
                         
                        <E T="03">See</E>
                         DOT Order 5610.1D § 9.
                    </P>
                    <P>
                        <SU>38</SU>
                         Id. § 9(b).
                    </P>
                    <P>
                        <SU>39</SU>
                         Id. § 9(b).
                    </P>
                </FTNT>
                <LSTSUB>
                    <PRTPAGE P="40909"/>
                    <HD SOURCE="HED">List of Subjects</HD>
                    <CFR>14 CFR Part 117</CFR>
                    <P>Airmen, Aviation safety, Reporting and recordkeeping requirements.</P>
                    <CFR>14 CFR Part 121</CFR>
                    <P>Air carriers, Aircraft, Airmen, Aviation safety, Reporting and recordkeeping requirements, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Proposed Amendment</HD>
                <P>For the reasons discussed in the preamble, the Federal Aviation Administration proposes to amend chapter I of title 14, Code of Federal Regulations as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 117—FLIGHT AND DUTY LIMITATIONS AND REST REQUIREMENTS: FLIGHTCREW MEMBERS</HD>
                </PART>
                <AMDPAR>1. The authority citation for part 117 is revised to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P> 49 U.S.C. 106(f), 40113, 40119, 44101, 44701-44702, 44705, 44709-44711, 44713, 44716-44717, 44722, 46901, 44903-44904, 44912, 46105.</P>
                </AUTH>
                <AMDPAR>2. Add § 117.31 to read as follows:</AMDPAR>
                <SECTION>
                    <SECTNO>§ 117.31</SECTNO>
                    <SUBJECT>Preemption of State and local meal and rest break requirements.</SUBJECT>
                    <P>(a) Except as authorized under this part, a certificate holder must ensure that all flightcrew members are available to perform safety-related responsibilities during a flight duty period.</P>
                    <P>(b) This part preempts any State or local law, rule, regulation, order or standard, or enforcement thereof, covering the subject matter of flightcrew member duty and rest periods, including meal and rest breaks.</P>
                </SECTION>
                <PART>
                    <HD SOURCE="HED">PART 121—OPERATING REQUIREMENTS: DOMESTIC, FLAG, AND SUPPLEMENTAL OPERATIONS</HD>
                </PART>
                <AMDPAR>3. The authority citation for part 121 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P> 49 U.S.C. 106(f), 40103, 40113, 40119, 41706, 42301 preceding note added by Pub. L. 112-95, sec. 412, 126 Stat. 89, 44101, 44701-44702, 44705, 44709-44711, 44713, 44716-44717, 44722, 44729, 44732; 46105; Pub. L. 111-216, 124 Stat. 2348 (49 U.S.C. 44701 note); Pub. L. 112-95, 126 Stat. 62 (49 U.S.C. 44732 note); Pub. L. 115-254, 132 Stat. 3186 (49 U.S.C. 44701 note).</P>
                </AUTH>
                <AMDPAR>4. Add § 121.468 to read as follows:</AMDPAR>
                <SECTION>
                    <SECTNO>§ 121.468</SECTNO>
                    <SUBJECT>Preemption of State and local meal and rest break requirements.</SUBJECT>
                    <P>(a) Except as authorized under this part, a certificate holder must ensure that all flight attendants are available to perform safety-related responsibilities and also be able to meet physiological needs during a duty period.</P>
                    <P>(b) Section 121.467 of this part preempts any State or local law, rule, regulation, order or standard, or enforcement thereof, covering the subject matter of flight attendant duty and rest periods, including meal and rest breaks.</P>
                </SECTION>
                <SIG>
                    <P>Issued under authority provided by 49 U.S.C. 106(f) and 44701 in Washington, DC</P>
                    <NAME>Hugh J. Thomas,</NAME>
                    <TITLE>Executive Director, Flight Standards Service.</TITLE>
                    <NAME>William McKenna,</NAME>
                    <TITLE>Chief Counsel.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13546 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Drug Enforcement Administration</SUBAGY>
                <CFR>21 CFR Part 1308</CFR>
                <DEPDOC>[Docket No. DEA-1644]</DEPDOC>
                <SUBJECT>Schedules of Controlled Substances: Temporary Placement of Mitragynine Pseudoindoxyl, MGM-15, and MGM-16 in Schedule I</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Drug Enforcement Administration, Department of Justice.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed amendment; notice of intent.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Administrator of the Drug Enforcement Administration is issuing this notice of intent to publish a temporary order to schedule three 7-hydroxymitragynine-related substances (mitragynine pseudoindoxyl, MGM-15, and MGM-16), including their isomers, esters, ethers, salts, and salts of isomers, esters, and ethers, whenever the existence of such isomers, esters, ethers, and salts is possible, in schedule I of the Controlled Substances Act. When it is issued, the temporary scheduling order will impose the regulatory controls and administrative, civil, and criminal sanctions applicable to schedule I controlled substances on persons who handle (manufacture, distribute, reverse distribute, import, export, engage in research, conduct instructional activities or chemical analysis with, or possess) or propose to handle these three 7-hydroxymitragynine-related substances.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>July 6, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>8701 Morrissette Drive, Springfield, Virginia 22152.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Terrence L. Boos, Drug and Chemical Evaluation Section, Diversion Control Division, Drug Enforcement Administration; Mailing Address: 8701 Morrissette Drive, Springfield, Virginia 22152; Telephone: (571) 362-3249.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The notice of intent contained in this document is issued pursuant to the temporary scheduling provisions of 21 U.S.C. 811(h). The Drug Enforcement Administration (DEA) intends to issue a temporary scheduling order 
                    <SU>1</SU>
                    <FTREF/>
                     (in the form of a temporary amendment) to add three 7-hydroxymitragynine-related substances, including their isomers, esters, ethers, salts, and salts of isomers, 
                    <PRTPAGE P="40910"/>
                    esters, and ethers, whenever the existence of such isomers, esters, ethers, and salts is possible, to schedule I under the Controlled Substances Act (CSA):
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Though DEA has used the term “final order” with respect to temporary scheduling orders in the past, this notice of intent adheres to the statutory language of 21 U.S.C. 811(h), which refers to a “temporary scheduling order.” No substantive change is intended.
                    </P>
                </FTNT>
                <P>
                    • Methyl (
                    <E T="03">E</E>
                    )-2-((1′
                    <E T="03">S,</E>
                    6′
                    <E T="03">S,</E>
                    7′S)-6′-ethyl-4-methoxy-3-oxo-3′,5′,6′,7′,8′,8
                    <E T="03">a</E>
                    ′-hexahydro-2′
                    <E T="03">H</E>
                    -spiro[indoline-2,1′-indolizine]-7′-yl)-3-methoxyacrylate (commonly known as mitragynine pseudoindoxyl),
                </P>
                <P>
                    • Methyl (
                    <E T="03">E</E>
                    )-2-((2
                    <E T="03">S,</E>
                    3
                    <E T="03">S,</E>
                    7
                    <E T="03">aS,</E>
                    12
                    <E T="03">aR,</E>
                    12
                    <E T="03">bS</E>
                    )-3-ethyl-7
                    <E T="03">a</E>
                    -hydroxy-8-methoxy-1,2,3,4,6,7,7
                    <E T="03">a,</E>
                    12,12
                    <E T="03">a,</E>
                    12
                    <E T="03">b</E>
                    -decahydroindolo[2,3-
                    <E T="03">a</E>
                    ]quinolizin-2-yl)-3-methoxyacrylate (commonly known as dihydro-7-hydroxymitragynine, or MGM-15),
                </P>
                <P>
                    • Methyl (
                    <E T="03">E</E>
                    )-2-((2
                    <E T="03">S,</E>
                    3
                    <E T="03">S,</E>
                    7
                    <E T="03">aS,</E>
                    12
                    <E T="03">aR,</E>
                    12b
                    <E T="03">S</E>
                    )-3-ethyl-9-fluoro-7
                    <E T="03">a</E>
                    -hydroxy-8-methoxy-1,2,3,4,6,7,7
                    <E T="03">a,</E>
                    12,12
                    <E T="03">a,</E>
                    12
                    <E T="03">b</E>
                    -decahydroindolo[2,3-
                    <E T="03">a</E>
                    ]quinolizin-2-yl)-3-methoxyacrylate (commonly known as 9-fluoro-dihydro-7-hydroxymitragynine, or MGM-16).
                </P>
                <P>
                    The temporary scheduling order will be published in the 
                    <E T="04">Federal Register</E>
                     on or after August 5, 2026.
                </P>
                <HD SOURCE="HD1">Legal Authority</HD>
                <P>
                    The CSA provides the Attorney General with the authority to temporarily place a substance in schedule I of the CSA for two years without regard to the requirements of 21 U.S.C. 811(b), if he finds that such action is necessary to avoid an imminent hazard to public safety.
                    <SU>2</SU>
                    <FTREF/>
                     In addition, if proceedings to control a substance are initiated under 21 U.S.C. 811(a)(1) while the substance is temporarily controlled under section 811(h), the Attorney General may extend the temporary scheduling for up to one year.
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         21 U.S.C. 811(h)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         21 U.S.C. 811(h)(2).
                    </P>
                </FTNT>
                <P>
                    Where the necessary findings are made, a substance may be temporarily scheduled if it is not listed in any other schedule under 21 U.S.C. 812, or if there is no exemption or approval in effect for the substance under section 505 of the Federal Food, Drug, and Cosmetic Act, 21 U.S.C. 355.
                    <SU>4</SU>
                    <FTREF/>
                     The Attorney General has delegated scheduling authority under 21 U.S.C. 811 to the Administrator of DEA (Administrator).
                    <SU>5</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         21 U.S.C. 811(h)(1); 21 CFR part 1308.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         28 CFR 0.100.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    The CSA requires the Administrator to notify the Secretary of the Department of Health and Human Services (HHS) of this intent to issue a temporary scheduling order.
                    <SU>6</SU>
                    <FTREF/>
                     By letter dated December 15, 2025, the Administrator transmitted the required notice to place mitragynine pseudoindoxyl, MGM-15, and MGM-16 in schedule I on a temporary basis to the Assistant Secretary for Health of HHS (Assistant Secretary).
                    <SU>7</SU>
                    <FTREF/>
                     By letter dated January 20, 2026, the Assistant Secretary responded to this notice and advised that based on a review by the Food and Drug Administration (FDA), there were currently no investigational new drug applications (IND) or approved new drug applications (NDA) for mitragynine pseudoindoxyl, MGM-15, and MGM-16. The Assistant Secretary also stated that HHS had no objection to the temporary placement of these substances in schedule I of the CSA. Mitragynine pseudoindoxyl, MGM-15, and MGM-16 are not currently listed in any schedule under the CSA.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         21 U.S.C. 811(h)(4).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         The Secretary of HHS has delegated to the Assistant Secretary for Health of HHS the authority to make domestic drug scheduling recommendations. 
                        <E T="03">Comprehensive Drug Abuse Prevention and Control Act of 1970, Public Law 91-513, As Amended; Delegation of Authority,</E>
                         58 FR 35460 (July 1, 1993).
                    </P>
                </FTNT>
                <P>
                    To find that placing a substance temporarily in schedule I of the CSA is necessary to avoid an imminent hazard to public safety, the Administrator must consider three of the eight factors set forth in 21 U.S.C. 811(c): the substance's history and current pattern of abuse; the scope, duration and significance of abuse; and what, if any, risk there is to public health.
                    <SU>8</SU>
                    <FTREF/>
                     This consideration includes any information indicating actual abuse, diversion from legitimate channels, and clandestine importation, manufacture, or distribution of mitragynine pseudoindoxyl, MGM-15, and MGM-16.
                    <SU>9</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         21 U.S.C. 811(c)(4)-(6), (h)(3).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         21 U.S.C. 811(h)(3).
                    </P>
                </FTNT>
                <P>
                    Substances meeting the statutory requirements for temporary scheduling may only be placed in schedule I.
                    <SU>10</SU>
                    <FTREF/>
                     Substances in schedule I have high potential for abuse, no currently accepted medical use in treatment in the United States,
                    <SU>11</SU>
                    <FTREF/>
                     and a lack of accepted safety for use under medical supervision.
                    <SU>12</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         21 U.S.C. 811(h)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         When finding schedule I placement on a temporary basis is necessary to avoid imminent hazard to the public, 21 U.S.C 811(h) does not require DEA to consider whether the substance has a currently accepted medical use in treatment in the United States. Nonetheless, there is no evidence suggesting that mitragynine pseudoindoxyl, MGM-15, and MGM-16 have a currently accepted medical use in treatment in the United States. First, DEA looks to whether the drug or substance has FDA approval. When no FDA approval exists, DEA has traditionally applied a five-part test to determine whether a drug or substances has a currently accepted medical use: (1) the drug's chemistry must be known and reproducible; (2) there must be adequate safety studies; (3) there must be adequate and well-controlled studies proving efficacy; (4) the drug must be accepted by qualified experts; and (5) the scientific evidence must be widely available. 
                        <E T="03">Marijuana Scheduling Petition; Denial of Petition; Remand,</E>
                         57 FR 10499 (Mar. 26, 1992), pet. for rev. denied, 
                        <E T="03">Alliance for Cannabis Therapeutics</E>
                         v. 
                        <E T="03">Drug Enforcement Admin.,</E>
                         15 F.3d 1131, 1135 (D.C. Cir. 1994). DEA applied the traditional five-part test and concluded the test was not satisfied. In a recent published letter in a different context, HHS applied an additional two-part test to determine currently accepted medical use for substances that do not satisfy the five-part test: (1) whether there exists widespread, current experience with medical use of the substance by licensed health care providers operating in accordance with implemented jurisdiction-authorized programs, where medical use is recognized by entities that regulate the practice of medicine, and, if so, (2) whether there exists some credible scientific support for at least one of the medical conditions for which part (1) is satisfied. On April 11, 2024, the Department of Justice's Office of Legal Counsel (OLC) issued an opinion, which, among other things, concluded that HHS's two-part test would be sufficient to establish that a drug has a currently accepted medical use. Office of Legal Counsel, Memorandum for Merrick B. Garland Attorney General Re: Questions Related to the Potential Rescheduling of Marijuana at 3 (April 11, 2024). For purposes of this notice of intent, there is no evidence that health care providers have widespread experience with medical use of mitragynine pseudoindoxyl, MGM-15, and MGM-16, or that the use of these substances is recognized by entities that regulate the practice of medicine, so the two-part test also is not satisfied. In HHS' letter dated January 20, 2026, HHS advised DEA that there were currently no approved new drug applications or investigational new drug applications for mitragynine pseudoindoxyl, MGM-15, and MGM-16. Additionally, HHS noted it had no objections to the temporary placement of these substances in schedule I of the CSA.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         21 U.S.C. 812(b)(1).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Three 7-Hydroxymitragynine-Related Substances: Mitragynine Pseudoindoxyl, MGM-15, and MGM-16 </HD>
                <P>
                    The prevalence and misuse of 
                    <E T="03">Mitragyna speciosa</E>
                     (commonly known as kratom) and its psychoactive alkaloids, including mitragynine and 7-hydroxymitragynine, have led to the proliferation of commercial products containing opioids chemically synthesized from mitragynine or 7-hydroxymitragynine. In recent years, mitragynine pseudoindoxyl, which is a chemical rearrangement product of 7-hydroxymitragynine, and MGM-15, which is a derivative of 7-hydroxymitragynine, have recently emerged on the 
                    <E T="03">Mitragyna speciosa</E>
                     consumer markets. MGM-16 is a highly potent opioid and shares a similar pharmacological profile with mitragynine pseudoindoxyl and MGM-15. The chemical scaffolds of mitragynine or 7-hydroxymitragynine were used in scientific research to develop mitragynine pseudoindoxyl, MGM-15, or MGM-16 via chemical modifications of purified isolates. Evidence from the 
                    <E T="03">Mitragyna speciosa</E>
                      
                    <PRTPAGE P="40911"/>
                    retail markets demonstrates that mitragynine pseudoindoxyl and MGM-15 have transitioned from experimental substances studied in research to widely available commercial products. These products are commonly sold in different forms such as powders, tablets, and liquid shots. This is a significant evolution from the traditional administration of 
                    <E T="03">Mitragyna speciosa,</E>
                     which was once restricted to either chewing raw leaves or steeping the leaves into water decoctions and teas.
                </P>
                <P>
                    These products are sold under numerous brand names like Kama, Hydroxie, Fruity Perks, and Happie Tabs,
                    <SU>13</SU>
                    <FTREF/>
                     and they are easily purchased on the internet, as well as in gas stations, corner shops, and vape shops. These products are available in consumer-friendly forms to include flavored chewable tablets, which increases their appeal to a broader demographic. Also, the aggressive marketing of these semi-synthetic opioids (mitragynine pseudoindoxyl, MGM-15) as “precision-formulated products,” “botanical extracts,” or as “mood boosters” for the treatment of health conditions is deeply concerning. The branding creates a false sense of safety for unknowing consumers who may equate the term “botanical” with lower risk. Furthermore, there is paucity of data on quality control or standardized dosage available for these products, making their use especially dangerous.
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         The list of brand names is illustrative, non-exhaustive, and provided solely as market context.
                    </P>
                </FTNT>
                <P>
                    Mitragynine pseudoindoxyl, MGM-15, and MGM-16 are potent opioids that share a similar pharmacological profile with 7-hydroxymitragynine. Available pharmacology data demonstrate that mitragynine pseudoindoxyl, MGM-15, and MGM-16 exhibit strong affinity for the mu-opioid receptor (MOR) and function as MOR agonists.
                    <E T="51">14 15</E>
                    <FTREF/>
                     Data from preclinical studies show that these substances produce analgesic effects that is more potent than morphine.
                    <SU>16</SU>
                    <FTREF/>
                     oBecause mitragynine pseudoindoxyl, MGM-15, and MGM-16 are potent MOR agonists, they pose similar health risks as other mu-opioid agonists (
                    <E T="03">i.e.,</E>
                     morphine and fentanyl), including physical and psychological dependence, and respiratory depression.
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         Matsumoto, K., Narita, M., Muramatsu, N., Nakayama, T., Misawa, K., Kitajima, M., Tashima, K., Devi, L.A., Suzuki, T., Takayama, H., &amp; Horie, S. (2014). Orally active opioid μ/δ dual agonist MGM-16, a derivative of the indole alkaloid mitragynine, exhibits potent antiallodynic effect on neuropathic pain in mice. 
                        <E T="03">The Journal of Pharmacology and Experimental Therapeutics,</E>
                         348(3):383-392.
                    </P>
                    <P>
                        <SU>15</SU>
                         Yamamoto, L.T., Horie, S., Takayama, H., Aimi, N., Sakai, S., Yano, S., Shan, J., Pang, P.K., Ponglux, D., &amp; Watanabe, K. (1999). Opioid receptor agonistic characteristics of mitragynine pseudoindoxyl in comparison with mitragynine derived from Thai medicinal plant Mitragyna speciosa. 
                        <E T="03">General Pharmacology,</E>
                         33(1):73-81.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         Váradi, A., Marrone, G.F., Palmer, T.C., Narayan, A., Szabó, M.R., Le Rouzic, V., Grinnell, S.G., Subrath, J.J., Warner, E., Kalra, S., Hunkele, A., Pagirsky, J., Eans, S.O., Medina, J.M., Xu, J., Pan, Y.X., Borics, A., Pasternak, G.W., McLaughlin, J.P., &amp; Majumdar, S. (2016). Mitragynine/Corynantheidine Pseudoindoxyls As Opioid Analgesics with Mu Agonism and Delta Antagonism, Which Do Not Recruit β-Arrestin-2. 
                        <E T="03">Journal of Medicinal Chemistry,</E>
                         59(18):8381-8397.
                    </P>
                </FTNT>
                <P>A scan of retail data on the internet shows that vendors explicitly market mitragynine pseudoindoxyl and MGM-15 for their “clean and powerful” opioid-receptor activation, utilizing deceptive terminology to target individuals seeking alternatives to pharmaceutical opioids. These combinations and marketing strategies pose significant safety risks to unsuspecting consumers who use these products by exposing them to high doses of opioids. Recently, reports have confirmed the positive identification of mitragynine pseudoindoxyl and MGM-15 in toxicology cases in the United States, and evidence demonstrates that these substances are being misused. The lack of clinical data regarding their safety and efficacy, coupled with the risk of life-threatening respiratory depression and addiction, underscores the danger of marketing these unapproved, highly potent opioids under the guise of therapeutic or wellness products.</P>
                <P>
                    While no evidence supports the presence of MGM-16 on the 
                    <E T="03">Mitragyna speciosa</E>
                     consumer market, its profile as a highly potent opioid that is structurally related to 7-hydroxymitragynine lends itself as an attractive substitute that could emerge on the illicit drug market. MGM-16 is synthetically manufactured for research purposes and is not approved for any clinical indication in the United States. DEA's investigation of publicly available information, including popular online platform, revealed that at least some individuals intend to abuse MGM-16. Recent online surveillance of a vendor site 
                    <SU>17</SU>
                    <FTREF/>
                     lists MGM-16 for upcoming sale. The sale of products containing mitragynine pseudoindoxyl, and MGM-15, and the potential sale of MGM-16 poses an imminent hazard to public safety.
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         MGM Series Guide: Science of MGM-15 Alkaloids | Getwell Depot. 
                        <E T="03">https://getwelldepot.com/mgm/.</E>
                         Accessed April 9, 2026. (Web content subsequently modified or removed; hardcopy preserved in DEA administrative record).
                    </P>
                </FTNT>
                <P>
                    Available data and information for mitragynine pseudoindoxyl, MGM-15, and MGM-16, summarized below, indicate that these substances have a high potential for abuse, no currently accepted medical use in treatment in the United States, and a lack of accepted safety for use under medical supervision. DEA's three-factor analysis is available in its entirety under “Supporting and Related Material” of the public docket for this action at 
                    <E T="03">www.regulations.gov</E>
                     under Docket Number DEA-1644.
                </P>
                <HD SOURCE="HD1">Factor 4. History and Current Pattern of Abuse</HD>
                <P>
                    Mitragynine pseudoindoxyl, MGM-15, and MGM-16 are synthetic derivatives of the indole alkaloids, mitragynine or 7-hydroxymitragynine, of the 
                    <E T="03">Mitragyna speciosa</E>
                     plant. Unlike the indole alkaloids mitragynine and 7-hydroxymitragynine, which are naturally occurring in the plant, mitragynine pseudoindoxyl, MGM-15, and MGM-16 are produced through synthetic modifications of purified mitragynine isolates or 7-hydroxymitragynine.
                    <SU>18</SU>
                    <FTREF/>
                     The chemical scaffolds of mitragynine or 7-hydroxymitragynine were used in scientific research to develop novel mitragynine pseudoindoxyl, MGM-15, and MGM-16. The first mention of mitragynine pseudoindoxyl in scientific literature dates to 1974 when mitragynine pseudoindoxyl was isolated as a metabolite from bio transformed mitragynine. In 2014, as part of a drug discovery research, MGM-15 and MGM-16 were developed as potent opioid agonists, with potential therapeutic utility for pain.
                    <SU>19</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         
                        <E T="03">Id,</E>
                         13;14; Takayama, H., Ishikawa, H., Kurihara, M., Kitajima, M., Aimi, N., Ponglux, D., Koyama, F., Matsumoto, K., Moriyama, T., Yamamoto, L.T., Watanabe, K., Murayama, T., &amp; Horie, S. (2002). Studies on the synthesis and opioid agonistic activities of mitragynine-related indole alkaloids: discovery of opioid agonists structurally different from other opioid ligands. 
                        <E T="03">Journal of Medicinal Chemistry,</E>
                         45(9):1949-1956.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         
                        <E T="03">Id,</E>
                         13.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">Market Emergence and Designer-Drug Patterns</HD>
                <P>
                    The first confirmed appearance of mitragynine pseudoindoxyl in consumer products was reported in 2024.
                    <SU>20</SU>
                    <FTREF/>
                     The emergence of MGM-15 in commercially available products was in 
                    <PRTPAGE P="40912"/>
                    September 2025.
                    <SU>21</SU>
                    <FTREF/>
                     The introduction of these substances into the 
                    <E T="03">Mitragyna speciosa</E>
                     consumer market follows a classic pattern of new designer drugs, where packaging appears like those of designer novel psychoactive substances and are often advertised as “sold strictly for laboratory, botanical, and research purposes only” and “not intended for human consumption.” 
                    <SU>22</SU>
                    <FTREF/>
                     A study on products sold online containing mitragynine pseudoindoxyl showed that of the 51 total products sold online, 35 had an appealing flavor (
                    <E T="03">e.g.,</E>
                     various berry, mint, watermelon, pink lemonade, candy apple, grape, citrus, mango, pistachio, and vanilla bean), and 32 of the products had packaging that was formulated using bright colors. Seventy-six percent (39 of 51) of these products were chewable tablets, 18 percent were liquids (9 of 51), and the remaining three were either dried ice cream cones with ice cream (two products) or a chocolate bar (one product).
                    <SU>23</SU>
                    <FTREF/>
                     Many of the products typically feature serving sizes that require consumers to split tablets or doses.
                </P>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         Hill, K., Boyer, E.W., Grundmann, O., &amp; Smith, K.E. (2025). De facto opioids: Characterization of novel 7-hydroxymitragynine and mitragynine pseudoindoxyl product marketing. 
                        <E T="03">Drug and Alcohol Dependence,</E>
                         272: 112701; Krotulski, A.J.; Denn, M.T., Brower, J.O., Papsun, D.M., &amp; Logan, B.K. (2025). Evaluation of Commercially Available Smoke Shop Products Marketed as “7-Hydroxy Mitragynine” &amp; Related Alkaloids, Center for Forensic Science Research and Education, United States; Vadiei, N., Evoy, K.E., &amp; Grundmann, O. (2025). The Impact of Diverse Kratom Products on Use Patterns, Dependence, and Toxicity. 
                        <E T="03">Current Psychiatry Reports,</E>
                         27(10):584-592.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         Gour, A., Mukhopadhyay, S., Henderson, A., Awad, A., Seabra, M.A., Pullman, M., Leon, F., Cutler, J.C., McCurdy, C.R., &amp; Sharma A. (2025). From Kratom to Semi-Synthetic Opioids: The Rise and Risks of MGM-15. 
                        <E T="03">Drug Testing and Analysis,</E>
                         17(12):2384-2389.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         
                        <E T="03">Id,</E>
                         24.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         White, C.M., Belcourt, J., &amp; Sedensky, A. (2025). A Descriptive Assessment of Products Containing the Opioid Receptor Stimulator Mitragynine Pseudoindoxyl. 
                        <E T="03">Substance Use &amp; Misuse,</E>
                         60(12):1950-1954.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">Current Patterns of Use</HD>
                <P>
                    Users seek these 7-hydroxymitragynine-related products for their psychoactive effects and products are often advertised as mood enhancers or alternative to prescription opioid analgesics (
                    <E T="03">see</E>
                     Factor 5). These products are commonly sold in different product forms, such as powders, tablets, or liquid shots, which is a sharp contrast from the traditional mode of administration of 
                    <E T="03">Mitragyna speciosa,</E>
                     which was confined to either water decoctions or brewed into tea or chewing of fresh leaves. A review of vendor websites 
                    <SU>24</SU>
                    <FTREF/>
                     show that these products are explicitly marketed as “potent” and “fast-acting” substances and sold at low prices. For example, mitragynine pseudoindoxyl and MGM-15 tablets are sold in varying fruit flavors and in bright colors, and prices vary from about $2-4 per tablet or $34.99 per pack (single pack and 10-pack bulk). Of great concern to DEA is that the price of these products may facilitate high-frequency and rapid escalation of use (
                    <E T="03">see</E>
                     Table 1). Further, open-source signal detection demonstrates that users are seeking MGM-16 with the intent to abuse.
                    <SU>25</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         Market Audit of Online Retailers, Jan. 2026.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         Can anyone help with the MGM 16 rumors?r/KratomKorner. 
                        <E T="03">https://www.reddit.com/r/KratomKorner/comments/1kpz2u3/can_anyone_help_with_the_mgm_16_rumors/?rdt=48097.</E>
                         Accessed April 9, 2026.
                    </P>
                </FTNT>
                <GPOTABLE COLS="4" OPTS="L2,nj,i1" CDEF="s25,r25,r50,r100">
                    <TTITLE>Table 1—Retail Distribution of Mitragynine Pseudoindoxyl and MGM-15 Products</TTITLE>
                    <BOXHD>
                        <CHED H="1">Brand</CHED>
                        <CHED H="1">Product form</CHED>
                        <CHED H="1">Stated concentration</CHED>
                        <CHED H="1">Marketing narrative</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Overseas Organix</ENT>
                        <ENT>Extract Tablets</ENT>
                        <ENT>15 mg MGM-15</ENT>
                        <ENT>“Ultra-potent . . . . . . for experienced users who want strong, consistent effects with small serving sizes. available. 4-6-hour duration.”</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Majestic White</ENT>
                        <ENT>Sublingual Tablet</ENT>
                        <ENT>3.5 mg MGM-15 (+50 mg MIT)</ENT>
                        <ENT>“Next generation kratom formulation. . . Its sublingual design allows for fast absorption and precise serving control.”</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MGM-15 Tablets—Berries</ENT>
                        <ENT>Chewable Tablets (Berries)</ENT>
                        <ENT>30 mg MGM-15</ENT>
                        <ENT>“This single, pocket-ready tablet delivers consistent strength without the guesswork. Each tablet offering a fast-acting, predictable experience you can count on. To dissolve smoothly for quick onset.”</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Kama Pseudoindoxyl</ENT>
                        <ENT>Extract tablet</ENT>
                        <ENT>500 mg Kama 7-Hydroxy + Pseudo extracts</ENT>
                        <ENT>“Stop settling for weak kratom products. . . . Enjoy great flavor and precise dosing without the guesswork.”</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Kream</ENT>
                        <ENT>Liquid Shot</ENT>
                        <ENT>90 mg 7-Hydroxy + Pseudo</ENT>
                        <ENT>“Tired of slow supplements that give you a crash? delivering fast-acting effects and calm mental clarity in a discreet little bottle. This clean, lab-tested liquid shot features 7-hydroxy and pseudo in a citrus formula for consistent potency, making it easy to find focus and wellness without waiting long.”</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    The shift from natural leaf decoctions of 
                    <E T="03">Mitragyna speciosa</E>
                     to flavored, standardized, and high-potency semi-synthetic substances suggests an intentional market strategy to maximize consumer appeal and sale of products with rapid onset of effects. The use of “research chemical” labeling, a common tactic to bypass regulatory oversight, for flavored chewable products further demonstrates a pattern to reach a broader consumer demographics.
                </P>
                <HD SOURCE="HD1">Factor 5. Scope, Duration, and Significance of Abuse </HD>
                <P>The abuse of mitragynine pseudoindoxyl and MGM-15 is concerning due to their high opioid potency and commercial availability. Mitragynine pseudoindoxyl and MGM-15 products are sold in formulations that facilitate ease of use, bypass the traditional, lower-alkaloid preparation (chewing leaves or drinking tea) and provide a highly potent effect that mimics classical opioids such as morphine.</P>
                <HD SOURCE="HD2">Deceptive Branding and Market Infiltration</HD>
                <P>
                    Analysis of marketed mitragynine pseudoindoxyl products revealed misleading marketing strategies with claims that the products are “kratom.” Available information on vendor website indicates that the concentrated alkaloid products often contain more than one alkaloid with opioid activity (
                    <E T="03">e.g.,</E>
                     mitragynine and MGM-15 or 7-hydroxymitragynine and mitragynine pseudoindoxyl). These substance combinations and marketing practices pose significant safety risk to unsuspecting consumers by exposing them to high doses of opioids (
                    <E T="03">see</E>
                     Table 1). It is known that repeated use of opioids can lead to psychological and physical dependence. In fact, data show that chronic use of 7-hydroxymitragynine has sent users to opioid detox clinic and the need for opioid use disorder medication.
                    <FTREF/>
                    <SU>26</SU>
                     Furthermore, these products are labeled for “strong mood enhancement” and “analgesic properties.” Finally, the presence of these products containing mitragynine pseudoindoxyl and MGM-
                    <PRTPAGE P="40913"/>
                    15 is deeply concerning because the identity, purity, and quality of these products' formulation are uncertain, thus presenting additional safety concerns for unsuspecting users. The potential presence of MGM-16 in designer drug products would have similar concerns.
                </P>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         Wightman, R.S., &amp; Hu, D. (2025). A Case of 7-OH Mitragynine Use Requiring Inpatient Medically Managed Withdrawal. 
                        <E T="03">Journal of Addiction Medicine,</E>
                         10.1097/ADM.0000000000001558. Advance online publication.
                    </P>
                </FTNT>
                <P>
                    A study of products sold as mitragynine pseudoindoxyl over the internet found that the 51 unique products sold online as mitragynine pseudoindoxyl were marketed in child-appealing forms and contained other opioid alkaloids, with limited consumer safety information. The serving size varied and alkaloid concentrations for these marketed products were often higher than those in naturally occurring 
                    <E T="03">Mitragyna speciosa</E>
                     leaves. The analysis revealed that among the products sampled, 71 percent featured a combination of mitragynine pseudoindoxyl and 7-hydroxymitragynine, while 24 percent contained mitragynine pseudoindoxyl only. The remaining 6 percent contained combination of mitragynine pseudoindoxyl and other hydroxymitragynine forms (8-hydroxymitragynine or 11-hydroxymitragynine).
                    <SU>27</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         Wilson, L.L., Chakraborty, S., Eans, S.O., Cirino, T.J., Stacy, H.M., Simons, C.A., Uprety, R., Majumdar, S., &amp; McLaughlin, J.P. (2021). Kratom Alkaloids, Natural and Semi-Synthetic, Show Less Physical Dependence and Ameliorate Opioid Withdrawal. 
                        <E T="03">Cell Mol Neurobiol.,</E>
                         41(5):1131-1143. doi: 10.1007/s10571-020-01034-7.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">National E-Commerce</HD>
                <P>Data from online sources show that the availability of mitragynine pseudoindoxyl and MGM-15 are not isolated to a single region but have rapidly spread across the United States. Products containing mitragynine pseudoindoxyl and MGM-15 are sold on the internet and are delivered to most states where there are currently no kratom use restrictions, suggesting national distribution network facilitated by online sales and mass-market retail channels. The significance of the abuse of mitragynine pseudoindoxyl and MGM-15 is underscored by the potent opioid pharmacological profile of these substances and the specific health warnings acknowledged even by those who are marketing the substances. Vendor descriptions listed below provide insight into the duration and pattern of use that characterizes the abuse of these compounds:</P>
                <P>
                      
                    <E T="03">Sustained Effect:</E>
                     The duration of effects is reported to last “several hours.” 
                    <SU>28</SU>
                    <FTREF/>
                     This prolonged duration increases the likelihood of cumulative effects and potential for toxicity if doses are repeated.
                </P>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         
                        <E T="03">See</E>
                         Pseudoindoxyl Chewable Tablets—Red Vein—Advanced Alkaloids Descriptions, 
                        <E T="03">https://cbdamericanshaman.com/pseudoindoxyl-chewable-tablets-red-vein-advanced-alkaloids.</E>
                         Accessed January 2026.
                    </P>
                </FTNT>
                <P>
                      
                    <E T="03">Deceptive Marketing for Medical Conditions:</E>
                     Despite having no FDA-approved medical use, these products are explicitly marketed for “easing stress and tension,” “internal calm and reduced restlessness,” and as a “mental clarity.” 
                    <SU>29</SU>
                    <FTREF/>
                     This marketing encourages individuals with legitimate medical needs to utilize potent, unlawful opioids as self-treatment.
                </P>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         
                        <E T="03">See</E>
                         Dozo Perks Extremely Potent Pseudoindoxyl Chewable Tablet Grape 100mg Per Tablet, 
                        <E T="03">https://pureleafkratom.com/products/dozo-perks-100mg-pseudoindoxyl-grape-chewable-tablets-4ct.html.</E>
                         Accessed January 2026.
                    </P>
                </FTNT>
                <P>
                      
                    <E T="03">Deceptive “Natural” Branding:</E>
                     Vendors frequently frame these substances as “clean and powerful” alternatives to traditional kratom. This branding is used to minimize the perceived risk of what are highly potent semi-synthetic opioid agonists.
                </P>
                <P>
                      
                    <E T="03">Deceptive Safety Profiles:</E>
                     While products are marketed as a “midday stress relief” or “mental reset,” the inclusion of warnings for lethal respiratory depression on retail sites confirms that the products possess a toxicity profile identical to scheduled opioids.
                </P>
                <P>
                      
                    <E T="03">Low Barrier to Entry:</E>
                     The use of “fruity” flavors and “chewable” formats (
                    <E T="03">e.g.,</E>
                     Fruity Perks) suggests an effort to appeal to a broader, potentially younger demographic, significantly increasing the scope of potential abuse.
                </P>
                <HD SOURCE="HD2">Forensic Surveillance and Identification</HD>
                <P>
                    According to the National Forensic Laboratory Information System (NFLIS) 
                    <SU>30</SU>
                    <FTREF/>
                     database, which collects drug identification results from drug cases submitted to and analyzed by Federal State and local forensic laboratories, there has been one report of mitragynine pseudoindoxyl in New York (queried February 26, 2026). Further, recent monographs 
                    <SU>31</SU>
                    <FTREF/>
                     by Center for Forensic Science Research and Education (CFSRE), report that mitragynine pseudoindoxyl (n &gt; 10) and MGM-15 (n = 2) have been detected in at least 12 drug materials. MGM-15 was detected as a tan solid drug that originated from New England, and those involving mitragynine pseudoindoxyl (pills and tablets) initially originated from Pennsylvania and Illinois.
                </P>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         NFLIS represents an important resource in monitoring illicit drug trafficking, including the diversion of legally manufactured pharmaceuticals into illegal markets. NFLIS-Drug is a comprehensive information system that includes data from forensic laboratories that handle the nation's drug analysis cases. NFLIS-Drug participation rate, defined as the percentage of the national drug caseload represented by laboratories that have joined NFLIS, is currently 98.5 percent. NFLIS includes drug chemistry results from completed analyses only. While NFLIS data is not direct evidence of abuse, it can lead to an inference that a drug has been diverted and abused. 
                        <E T="03">See Schedules of Controlled Substances: Placement of Carisoprodol Into Schedule IV,</E>
                         76 FR 77330, 77332 (Dec. 12, 2011). NFLIS data was queried on December 5, 2025.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         
                        <E T="03">https://www.cfsre.org/nps-discovery/monographs/mitragynine-pseudoindoxyl.</E>
                         Report Date—November 7, 2025. Accessed January 9, 2026; 
                        <E T="03">https://www.cfsre.org/nps-discovery/monographs/dihydro-7-hydroxy-mitragynine.</E>
                         Report Date—November 11, 2025. Accessed January 9, 2026.
                    </P>
                </FTNT>
                <P>The paucity or lack of seizure data for some of these 7-hydroxymitragynine-related substances as reported in forensic laboratories casework may be due to lack of readily available analytical reference standards and other analytic challenges. Because these are new substances, it often takes time for forensic laboratories to develop and validate the necessary testing methods required for substance identification. Specifically, mitragynine pseudoindoxyl is an oxidative metabolite of 7-hydroxymitragynine, and such closely related compounds require specific method and instrumentation for accurate identification. Also, since these 7-hydroxymitragynine-related substances are not federally controlled under the CSA, some forensic laboratories may not analyze and track encounters of non-controlled substances and thus reporting could be limited.</P>
                <P>
                    The population likely to abuse mitragynine pseudoindoxyl, MGM-15, and MGM-16 appear to be the same as those abusing 
                    <E T="03">Mitragyna speciosa</E>
                     and prescription opioid analgesics. According to data from the National Survey on Drug Use and Health (NSDUH),
                    <SU>32</SU>
                    <FTREF/>
                     as of 2021, an estimated 1.7 million people aged 12 years or older used kratom in the past year. The highest users were among adults aged 26 or older (1.4 million people). The analysis of 2019 NSDUH survey data showed that kratom users base predominately non-Hispanic White and 
                    <PRTPAGE P="40914"/>
                    male. The survey finding also revealed a link between kratom use and substance use disorder, particularly nonmedical prescription opioid use disorder, indicative of a strong trend of use for self-managing opioid dependence.
                    <SU>33</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         The NSDUH, formerly known as the National Household Survey on Drug Abuse (NHSDA), is conducted annually by the Department of Health and Human Services Substance Abuse and Mental Health Services Administration (SAMHSA). It is the primary source of estimates of the prevalence and incidence of nonmedical use of pharmaceutical drugs, illicit drugs, alcohol, and tobacco use in the United States. The survey is based on a nationally representative sample of the civilian, non-institutionalized population 12 years of age and older. The survey excludes homeless people who do not use shelters, active military personnel, and residents of institutional group quarters such as jails and hospitals. The NSDUH provides yearly national and state level estimates of drug abuse, and includes prevalence estimates by lifetime (
                        <E T="03">i.e.,</E>
                         ever used), past year, and past month abuse or dependence.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         Palamar, J.J. (2021). Past-Year Kratom Use in the U.S.: Estimates From a Nationally Representative Sample. 
                        <E T="03">Am J Prev Med.,</E>
                         61(2):240-245: Rogers, J.M., Smith, K.E., Strickland, J.C., &amp; Epstein, D. H. (2021). Kratom Use in the US: Both a Regional Phenomenon and a White Middle-Class Phenomenon? Evidence From NSDUH 2019 and an Online Convenience Sample. 
                        <E T="03">Frontiers in Pharmacology,</E>
                         12:789075.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Factor 6. What, If Any, Risk There Is to Public Health </HD>
                <P>
                    Mitragynine pseudoindoxyl, MGM-15, and MGM-16 function as potent MOR agonist. This mechanism of action is inherently associated with high potential of abuse, physical dependence, and psychological dependence, consistent with the effects of controlled schedule I and II opioid substances. As of early 2026, mitragynine pseudoindoxyl and MGM-15 products are sold in smoke shops, gas stations, and through numerous online marketplaces, often marketed alongside traditional supplements, which mask their potent opioid nature. Data from preclinical studies demonstrate that mitragynine pseudoindoxyl is about 100 times more potent than mitragynine at the MOR, MGM-15 and MGM-16 are about 50 and 240 times more potent than morphine in animal models, respectively.
                    <SU>34</SU>
                    <FTREF/>
                     Because of the potency of these compounds, they can be abused in smaller, concentrated doses. It has been demonstrated that mitragynine pseudoindoxyl may cause development of signs of opioid physical dependence after chronic use in rodents. Pre-clinical studies demonstrated that chronic twice-daily administration of mitragynine pseudoindoxyl in rodents induces signs of opioid physical dependence and withdrawal symptoms in morphine addiction rodent models as evidenced by increased diarrhea, jumping, and rearing frequency occurring when naloxone was administered or when treatment with this alkaloid was tapered.
                    <SU>35</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         
                        <E T="03">Id</E>
                         13-14.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         Wilson, L.L., Chakraborty, S., Eans, S.O, Cirino, T.J., Stacy, H.M., &amp; Simons, C.A., Uprety, R., Majumdar, S., &amp; McLaughlin, J.P. (2021). Kratom Alkaloids, Natural and Semi-Synthetic, Show Less Physical Dependence and Ameliorate Opioid Withdrawal. 
                        <E T="03">Cell Mol Neurobiol.,</E>
                         41(5):1131-1143.
                    </P>
                </FTNT>
                <P>These products are easily accessible in unregulated retail environments often with no age restrictions, amplifying public health concerns, particularly to vulnerable populations. Vendor descriptions provide insight into the public health threat posed by the abuse of these compounds:</P>
                <P>
                      
                    <E T="03">Rapid Onset:</E>
                     Marketing materials for mitragynine pseudoindoxyl products emphasize a “quick onset,” typically occurring within 10 to 60 minutes, often described as a “wave of calm clarity,” “dual-action formula featuring 100mg per piece for maximum potency and a fast-acting hit.” 
                    <SU>36</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>36</SU>
                         See Kama Kratom 
                        <E T="03">https://greatcbdshop.com/product-category/brands/kama-kratom/</E>
                         and Pure Leaf Kratom 
                        <E T="03">https://pureleafkratom.com/kama-kratom/.</E>
                         Accessed March 2026.
                    </P>
                </FTNT>
                <P>
                      
                    <E T="03">Sustained Effect:</E>
                     The duration of effects is reported to last “several hours.” 
                    <SU>37</SU>
                    <FTREF/>
                     This prolonged duration increases the likelihood of cumulative effects and potential for toxicity if doses are repeated.
                </P>
                <FTNT>
                    <P>
                        <SU>37</SU>
                         
                        <E T="03">Id.</E>
                         26.
                    </P>
                </FTNT>
                <P>
                      
                    <E T="03">Potency Information:</E>
                     Marketing information of an MGM-15 product indicates this product contains a very large amount of MGM-15 “105 mg total per bottle,” 
                    <SU>38</SU>
                    <FTREF/>
                     which, given its extreme opioid potency, presents a significant threat to public health.
                </P>
                <FTNT>
                    <P>
                        <SU>38</SU>
                         MGM-15 | 7 count—15mg tablets (105mg total)—Can Vertex Bioscience Accessed March 2026. (Web content subsequently modified or removed; hardcopy preserved in DEA administrative record).
                    </P>
                </FTNT>
                <P>
                    <E T="03">Opioid Receptor Activation:</E>
                     Marketing materials explicitly state that these compounds directly activate opioid receptors and are “full agonist at mu receptors,” providing effects that mirror analgesic and stimulant effects (“pain relief and mood enhancement”).
                    <SU>39</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>39</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                      
                    <E T="03">Acknowledgment of Severe Risks:</E>
                     Notably, vendors acknowledge significant public health risks, advising users to monitor for “habit-forming behavior,” “high euphoria,” “dependence,” “overdose,” and “death”.
                    <SU>40</SU>
                    <FTREF/>
                     The mention of overdose and death is a significant indicator of the hazard these substances pose.
                </P>
                <FTNT>
                    <P>
                        <SU>40</SU>
                         
                        <E T="03">Id;</E>
                         See 7-OHFactory30mg MGM-15 Tablets—Berries. 
                        <E T="03">https://www.7ohfactory.com/products/30mg-mgm-15-tablets-berries</E>
                         Accessed March 2026.
                    </P>
                </FTNT>
                <P>
                    As with any MOR agonist, the potential health and safety risks for users of 7-hydroxymitragynine-related substances are high. Mitragynine pseudoindoxyl, MGM-15, and MGM-16 abuse carry a high risk of cardiotoxicity, hepatic and renal toxicity, respiratory depression, neurological effects, and physical dependence and withdrawal. According to data from poison control centers, from January to July 2025, there have been 1,690 exposure calls involving kratom, a significant increase from 2024 exposure calls. According to data from DEA Toxicology Testing Program (DEA TOX),
                    <SU>41</SU>
                    <FTREF/>
                     between February 2025—February 2026, mitragynine pseudoindoxyl has been identified in at least 31 overdose cases, of which 25 were fatal events. Recent monographs by CFSRE report that mitragynine pseudoindoxyl (n &gt;10) and MGM-15 (n = 1) have been detected in at least 12 toxicology cases. MGM-15 was co-identified with mitragynine, 7-hydroxymitragynine, and trace ketamine. Mitragynine pseudoindoxyl was co-identified with other kratom alkaloids.
                </P>
                <FTNT>
                    <P>
                        <SU>41</SU>
                         DEA TOX is a surveillance program that aims to detect novel psychoactive substances in fatal and nonfatal overdose cases within the United States. From these cases, biological samples, as well as drug paraphernalia (on limited occasions), are submitted for analysis by hospitals, medical examiners, poison centers, and law enforcement nationwide. Query date 2/27/2026.
                    </P>
                </FTNT>
                <P>
                    The sale of products with combination of high-potency opioids, explicit marketing for medical ailments, and the acknowledged potential for life-threatening respiratory depression and addiction highlights the danger posed by mitragynine pseudoindoxyl and MGM-15. While mitragynine pseudoindoxyl and MGM-15 have already been identified in fatal toxicological screening, the pharmacological profile of MGM-16 presents a significant health risk. As previously mentioned, MGM-16 is an opioid agonist with approximately 240-times the antinociceptive potency of morphine in animal studies. Recent online surveillance of a vendor site 
                    <SU>42</SU>
                    <FTREF/>
                     lists MGM-16 for upcoming sale. This transition from a research grade chemical to an accessible consumer product, combined with its opioid mechanism of action, underscores its potential as a highly attractive but lethal substitute. Thus, to schedule MGM-15 without MGM-16 would create a regulatory loophole that manufacturers are already poised to exploit. Its inclusion is necessary to prevent a market shift toward an even more potent derivative that poses a significant risk of respiratory depression.
                </P>
                <FTNT>
                    <P>
                        <SU>42</SU>
                         MGM Series Guide: Science of MGM-15 Alkaloids | Getwell Depot. 
                        <E T="03">https://getwelldepot.com/mgm/.</E>
                         Accessed April 9, 2026. (Web content subsequently modified or removed; hardcopy preserved in DEA administrative record).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Finding of Necessity of Schedule I Placement To Avoid Imminent Hazard to Public Safety</HD>
                <P>
                    In accordance with 21 U.S.C. 811(h)(3), based on the available data and information summarized above, the uncontrolled manufacture, distribution, reverse distribution, importation, exportation, conduct of research and chemical analysis, possession, and 
                    <PRTPAGE P="40915"/>
                    abuse of mitragynine pseudoindoxyl, MGM-15, and MGM-16 pose an imminent hazard to public safety. DEA is not aware of any currently accepted medical uses for mitragynine pseudoindoxyl, MGM-15, and MGM-16 in the United States. A substance meeting the statutory requirements for temporary scheduling, found in 21 U.S.C. 811(h)(1), may only be placed in schedule I. Substances in schedule I are those that have a high potential for abuse, no currently accepted medical use in treatment in the United States, and a lack of accepted safety for use under medical supervision. Available data and information for mitragynine pseudoindoxyl, MGM-15, and MGM-16 indicate that these substances have a high potential for abuse, no currently accepted medical use in treatment in the United States, and a lack of accepted safety for use under medical supervision.
                </P>
                <P>As required by 21 U.S.C. 811(h)(4), the Administrator notified the Assistant Secretary, via letter dated December 15, 2025 of DEA's intention to temporarily place mitragynine pseudoindoxyl, MGM-15, and MGM-16 in schedule I. In a letter dated January 20, 2026, the Assistant Secretary for Health had no objection to the temporary placement of these substances in schedule I.</P>
                <HD SOURCE="HD1">Conclusion</HD>
                <P>This notice of intent provides the 30-day notice pursuant to 21 U.S.C. 811(h)(1) of DEA's intent to issue a temporary scheduling order. In accordance with 21 U.S.C. 811(h)(1) and (3), the Administrator considered available data and information, herein set forth the grounds for his determination that it is necessary to temporarily schedule mitragynine pseudoindoxyl, MGM-15, and MGM-16 in schedule I of the CSA, and finds that placement of these substances in schedule I of the CSA is necessary in order to avoid an imminent hazard to the public's safety.</P>
                <P>
                    The temporary placement of mitragynine pseudoindoxyl, MGM-15, and MGM-16 in schedule I of the CSA will take effect pursuant to a temporary scheduling order, which will not be issued before August 5, 2026. Because the Administrator hereby finds that this temporary scheduling order is necessary to avoid an imminent hazard to public safety, it will take effect on the date the order is published in the 
                    <E T="04">Federal Register</E>
                     and remain in effect for two years, with a possible extension of an additional year, pending completion of the regular (permanent) scheduling process.
                    <SU>43</SU>
                    <FTREF/>
                     The Administrator intends to issue a temporary scheduling order as soon as possible after the expiration of 30 days from the date of publication of this document. Upon publication of the temporary order, mitragynine pseudoindoxyl, MGM-15, and MGM-16 will then be subject to the CSA's schedule I regulatory controls and administrative, civil, and criminal sanctions applicable to the manufacture, distribution, reverse distribution, importation, exportation, research, conduct of instructional activities and chemical analysis, and possession.
                </P>
                <FTNT>
                    <P>
                        <SU>43</SU>
                         21 U.S.C. 811(h)(1) and (2).
                    </P>
                </FTNT>
                <P>
                    The CSA sets forth specific criteria for scheduling drugs or other substances. Regular scheduling actions in accordance with 21 U.S.C. 811(a) are subject to formal rulemaking procedures “on the record after opportunity for a hearing” conducted pursuant to the provisions of 5 U.S.C. 556 and 557.
                    <SU>44</SU>
                    <FTREF/>
                     The regular scheduling process of formal rulemaking affords interested parties appropriate process and the government any additional relevant information needed to make a determination. Final decisions that conclude the regular scheduling process of formal rulemaking are subject to judicial review.
                    <SU>45</SU>
                    <FTREF/>
                     Temporary scheduling orders are not subject to judicial review.
                    <SU>46</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>44</SU>
                         21 U.S.C. 811.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>45</SU>
                         21 U.S.C. 877.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>46</SU>
                         21 U.S.C. 811(h)(6).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Regulatory Analyses </HD>
                <P>
                    The CSA provides for expedited temporary scheduling actions where necessary to avoid an imminent hazard to public safety. Under 21 U.S.C. 811(h)(1), the Administrator (as delegated by the Attorney General) may, by order, temporarily schedule substances in schedule I. Such orders may not be issued before the expiration of 30 days from: (1) the publication of a notice in the 
                    <E T="04">Federal Register</E>
                     of the intent to issue such order and the grounds upon which such order is to be issued, and (2) the date that notice of the proposed temporary scheduling order is transmitted to the Assistant Secretary of HHS, as delegated by the Secretary of HHS.
                    <SU>47</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>47</SU>
                         21 U.S.C. 811(h)(1).
                    </P>
                </FTNT>
                <P>
                    Inasmuch as section 811(h) directs that temporary scheduling actions be issued by order and sets forth the procedures by which such orders are to be issued, including the requirement of a publication in the 
                    <E T="04">Federal Register</E>
                     of a notice of intent, the notice-and-comment requirements of the Administrative Procedure Act (APA), 5 U.S.C. 553, do not apply to this notice of intent. The APA expressly differentiates between an order and a rule, as it defines an “order” to mean a “final disposition, whether affirmative, negative, injunctive, or declaratory in form, of an agency 
                    <E T="03">in a matter other than rule making.</E>
                    ” 
                    <SU>48</SU>
                    <FTREF/>
                     This contrasts with permanent scheduling actions, which are subject to formal rulemaking procedures done “on the record after opportunity for a hearing,” and final decisions that conclude the scheduling process and are subject to judicial review.
                    <SU>49</SU>
                    <FTREF/>
                     The specific language chosen by Congress indicates its intent that DEA issue 
                    <E T="03">orders</E>
                     instead of proceeding by rulemaking when temporarily scheduling substances. Given that Congress specifically requires the Administrator (as delegated by the Attorney General) to follow rulemaking procedures for 
                    <E T="03">other</E>
                     kinds of scheduling actions,
                    <SU>50</SU>
                    <FTREF/>
                     it is noteworthy that, in section 811(h)(1), Congress authorized the issuance of temporary scheduling actions by order rather than by rule.
                </P>
                <FTNT>
                    <P>
                        <SU>48</SU>
                         5 U.S.C. 551(6) (emphasis added).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>49</SU>
                         21 U.S.C. 811(a) and 877.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>50</SU>
                         
                        <E T="03">See</E>
                         21 U.S.C. 811(a).
                    </P>
                </FTNT>
                <P>Even assuming that this notice of intent is subject to the notice-and-comment requirements of the APA, the Administrator finds that there is good cause to forgo the those requirements pursuant to 5 U.S.C. 553(b)(B), as any further delays in the process for issuing temporary scheduling orders would be impracticable and contrary to the public interest given the manifest urgency to avoid an imminent hazard to public safety.</P>
                <P>Although DEA believes this notice of intent to issue a temporary scheduling order is not subject to the notice-and-comment requirements of the APA, DEA notes that in accordance with 21 U.S.C. 811(h)(4), the Administrator took into consideration comments submitted by the Assistant Secretary in response to the notice that DEA transmitted to the Assistant Secretary pursuant to such subsection.</P>
                <P>
                    Further, DEA believes that this temporary scheduling action is not a “rule” as defined by 5 U.S.C. 601(2), and, accordingly, is not subject to the requirements of the Regulatory Flexibility Act (RFA). The requirements for the preparation of an initial regulatory flexibility analysis in 5 U.S.C. 603(a) are not applicable where, as here, DEA is not required by the APA or any other law to publish a general notice of proposed rulemaking. As discussed above, DEA is issuing this notice of intent pursuant to DEA's authority to 
                    <PRTPAGE P="40916"/>
                    issue a temporary scheduling order.
                    <SU>51</SU>
                    <FTREF/>
                     Therefore, in this instance, since DEA believes this temporary scheduling action is not a “rule,” it is not subject to the requirements of the RFA when issuing this temporary action.
                </P>
                <FTNT>
                    <P>
                        <SU>51</SU>
                         21 U.S.C. 811(h)(1).
                    </P>
                </FTNT>
                <P>In accordance with the principles of Executive Orders (E.O.) 12866 and 13563, this action is not a significant regulatory action. E.O. 12866 directs 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). E.O. 13563 is supplemental to and reaffirms the principles, structures, and definitions governing regulatory review as established in E.O. 12866. Because this is not a rulemaking action, this is not a significant regulatory action as defined in Section 3(f) of E.O. 12866. In addition, 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>This action will not have substantial direct effects on the states, on the relationship between the national government and the states, or on the distribution of power and responsibilities among the various levels of government. Therefore, in accordance with E.O. 13132, it is determined that this action does not have sufficient federalism implications to warrant the preparation of a Federalism Assessment.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 21 CFR Part 1308</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 1308 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 1308—SCHEDULES OF CONTROLLED SUBSTANCES </HD>
                </PART>
                <AMDPAR>1. The authority citation for part 1308 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P> 21 U.S.C. 811, 812, 871(b), 956(b), unless otherwise noted.</P>
                </AUTH>
                <AMDPAR>2. In § 1308.11 add paragraphs (h)(88) through (90) to read as follows:</AMDPAR>
                <SECTION>
                    <SECTNO>§ 1308.11</SECTNO>
                    <SUBJECT>Schedule I </SUBJECT>
                    <STARS/>
                    <P>(h) * * *</P>
                    <GPOTABLE COLS="2" OPTS="L1,nj,tp0,p1,8/9,i1" CDEF="s200,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">
                                (88) Methyl (
                                <E T="03">E</E>
                                )-2-((1′
                                <E T="03">S,</E>
                                6′
                                <E T="03">S,</E>
                                7′S)-6′-ethyl-4-methoxy-3-oxo-3′,5′,6′,7′,8′,8
                                <E T="03">a</E>
                                ′-hexahydro-2′
                                <E T="03">H</E>
                                -spiro[indoline-2,1′-indolizine]-7′-yl)-3-methoxyacrylate (commonly known as mitragynine pseudoindoxyl)
                            </ENT>
                            <ENT>9672</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01" O="xl">
                                (89) Methyl (
                                <E T="03">E</E>
                                )- 2-((2
                                <E T="03">S,</E>
                                3
                                <E T="03">S,</E>
                                7
                                <E T="03">aS,</E>
                                12
                                <E T="03">aR,</E>
                                12
                                <E T="03">bS</E>
                                )-3-ethyl-7
                                <E T="03">a</E>
                                -hydroxy-8-methoxy-1,2,3,4,6,7,7
                                <E T="03">a,</E>
                                12,12
                                <E T="03">a,</E>
                                12
                                <E T="03">b</E>
                                -decahydroindolo
                                <LI>
                                     [2,3-
                                    <E T="03">a</E>
                                    ]quinolizin-2-yl)-3-methoxyacrylate (commonly known as MGM-15; also known as dihydro-7-hydroxymitragynine;)
                                </LI>
                            </ENT>
                            <ENT>9673</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01" O="xl">
                                (90) Methyl (
                                <E T="03">E</E>
                                )- 2-((2
                                <E T="03">S,</E>
                                3
                                <E T="03">S,</E>
                                7
                                <E T="03">aS,</E>
                                12
                                <E T="03">aR,</E>
                                12b
                                <E T="03">S</E>
                                )-3-ethyl-9-fluoro-7
                                <E T="03">a</E>
                                -hydroxy-8- methoxy-1,2,3,4,6,7,7
                                <E T="03">a,</E>
                                12,12
                                <E T="03">a,</E>
                                12
                                <E T="03">b</E>
                                -
                                <LI O="xl">
                                     decahydroindolo[2,3-
                                    <E T="03">a</E>
                                    ]quinolizin-2-yl)-3-methoxyacrylate (commonly known as MGM-16; also known as 9-fluoro derivate of 7-
                                </LI>
                                <LI> hydroxymitragynine;)</LI>
                            </ENT>
                            <ENT>9674</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 July 1, 2026, by DEA Administrator Terrance C. 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>Heather Achbach,</NAME>
                    <TITLE>Federal Register Liaison Officer, Drug Enforcement Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13581 Filed 7-1-26; 4:15 pm]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <PRTPAGE P="40917"/>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Drug Enforcement Administration</SUBAGY>
                <CFR>21 CFR Part 1308</CFR>
                <DEPDOC>[Docket No. DEA-1570]</DEPDOC>
                <SUBJECT>Schedules of Controlled Substance: Temporary Placement of 7-Hydroxymitragynine Above a Specified Threshold in Schedule I</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Drug Enforcement Administration, Department of Justice.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed amendment; notice of intent.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Administrator of the Drug Enforcement Administration is issuing this notice of intent to publish a temporary order to schedule 7-hydroxymitragynine above a specified threshold, including its isomers, esters, ethers, salts, and salts of isomers, esters, and ethers, whenever the existence of such isomers, esters, ethers, and salts is possible, in schedule I of the Controlled Substances Act. When it is issued, the temporary scheduling order will impose the regulatory controls and administrative, civil, and criminal sanctions applicable to schedule I controlled substances on persons who handle (manufacture, distribute, reverse distribute, import, export, engage in research, conduct instructional activities or chemical analysis with, or possess) or propose to handle 7-hydroxymitragynine above a specified threshold.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>July 6, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>8701 Morrissette Drive, Springfield, Virginia 22152.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Terrence L. Boos, Drug and Chemical Evaluation Section, Diversion Control Division, Drug Enforcement Administration; Mailing Address: 8701 Morrissette Drive, Springfield, Virginia 22152; Telephone: (571) 362-3249.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The notice of intent contained in this document is issued pursuant to the temporary scheduling provisions of 21 U.S.C. 811(h). The Drug Enforcement Administration (DEA) intends to issue a temporary scheduling order 
                    <SU>1</SU>
                    <FTREF/>
                     (in the form of a temporary amendment) to add 7-hydroxymitragynine 
                    <SU>2</SU>
                    <FTREF/>
                     above a specified threshold described herein, including its isomers, esters, ethers, salts, and salts of isomers, esters, and ethers whenever the existence of such isomers, esters, ethers, and salts is possible, to schedule I under the Controlled Substances Act (CSA). The specified threshold for 7-hydroxymitragynine was adapted from the definition used by the Department of Health and Human Services (HHS),
                    <SU>3</SU>
                    <FTREF/>
                     which is described as follows:
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Though DEA has used the term “final order” with respect to temporary scheduling orders in the past, this notice of intent adheres to the statutory language of 21 U.S.C. 811(h), which refers to a “temporary scheduling order.” No substantive change is intended.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Chemical name: Methyl (
                        <E T="03">E</E>
                        )-2-((2
                        <E T="03">S,</E>
                        3
                        <E T="03">S,</E>
                        7
                        <E T="03">aS</E>
                        )-3-ethyl-7
                        <E T="03">a</E>
                        -hydroxy-8-methoxy-1,2,3,4,6,7,7
                        <E T="03">a,</E>
                        12
                        <E T="03">b</E>
                        -octahydroindolo[2,3-
                        <E T="03">a</E>
                        ]quinolizin-2-yl)-3-methoxyacrylate (also known as: (αE,2
                        <E T="03">S,</E>
                        3
                        <E T="03">S,</E>
                        7a
                        <E T="03">S,</E>
                        12b
                        <E T="03">S</E>
                        )-3-ethyl-l,2,3,4,6,7,7a,12b-octahydro-7a-hydroxy-8-methoxy-a-(methoxymethylene)-indolo[2,3-
                        <E T="03">a</E>
                        ]quinolizine-2-acetic acid, methyl ester).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         In a letter dated July 28, 2025, pursuant to 21 U.S.C. 811(b) and (c), HHS provided to DEA a scientific and medical evaluation entitled “Basis for the Recommendation to Control 7-Hydroxymitragynine and its Salts, As Present in excess of the Specified Threshold Limit Described Herein, in Schedule I of the Controlled Substances Act.”
                    </P>
                </FTNT>
                <P>
                    (A) 
                    <E T="03">Any botanical material of the plant Mitragyna speciosa, also known as kratom, and contains more than 0.050 percentage of 7-hydroxymitragynine on a dry weight basis, or</E>
                </P>
                <P>
                    (B) 
                    <E T="03">Any alternative article to that described in (A), that is:</E>
                </P>
                <P>
                    i. 
                    <E T="03">Resulting from synthetic methods and containing 7-hydroxymitragynine present in amounts greater than 0.050 percentage by weight/weight, weight/volume, or volume/volume or greater than 1.00 milligram of 7-hydroxymitragynine in the article, or</E>
                </P>
                <P>
                    ii. 
                    <E T="03">Material derived from Mitragyna speciosa and further processed to manufacture alternative dosage forms such as extracts, concentrates, processed edibles, or pressed pills, and which may have materials that have been exposed to chemical, thermal, or other methods leading to chemical transformations that result in 7-hydroxymitragynine present in amounts greater than 0.050 percentage by weight/weight, weight/volume, or volume/volume, or greater than 1.00 milligram of 7-hydroxymitragynine in the article.</E>
                </P>
                <P>
                    The temporary scheduling order will be published in the 
                    <E T="04">Federal Register</E>
                     on or after August 5, 2026.
                </P>
                <HD SOURCE="HD1">Legal Authority</HD>
                <P>
                    The CSA provides the Attorney General with the authority to temporarily place a substance in schedule I of the CSA for two years without regard to the requirements of 21 U.S.C. 811(b), if he finds that such action is necessary to avoid an imminent hazard to public safety.
                    <SU>4</SU>
                    <FTREF/>
                     In addition, if proceedings to control a substance are initiated under 21 U.S.C. 811(a)(1) while the substance is temporarily controlled under section 811(h), the Attorney General may extend the temporary scheduling for up to one year.
                    <SU>5</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         21 U.S.C. 811(h)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         21 U.S.C. 811(h)(2).
                    </P>
                </FTNT>
                <P>
                    Where the necessary findings are made, a substance may be temporarily scheduled if it is not listed in any other schedule under 21 U.S.C. 812, or if there is no exemption or approval in effect for the substance under section 505 of the Federal Food, Drug, and Cosmetic Act (FD&amp;C Act), 21 U.S.C. 355.
                    <SU>6</SU>
                    <FTREF/>
                     The Attorney General has delegated scheduling authority under 21 U.S.C. 811 to the Administrator of DEA (Administrator).
                    <SU>7</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         21 U.S.C. 811(h)(1); 21 CFR part 1308.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         28 CFR 0.100.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    The CSA requires the Administrator to notify the Secretary of HHS of this intent to issue a temporary scheduling order.
                    <SU>8</SU>
                    <FTREF/>
                     By letter dated February 24, 2026, the Administrator transmitted the required notice to place 7-hydroxymitragynine above a specified threshold in schedule I on a temporary basis to the Assistant Secretary for Health of HHS (Assistant Secretary).
                    <SU>9</SU>
                    <FTREF/>
                     By letter dated March 6, 2026, the Assistant Secretary responded to this notice and advised that based on a review by the Food and Drug Administration (FDA), there were currently no investigational new drug applications (IND) or approved new drug applications (NDA) for these substances. The Assistant Secretary also stated that HHS had no objection to the temporary placement of this substance above the specified threshold in schedule I of the CSA.
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         21 U.S.C. 811(h)(4).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         The Secretary of HHS has delegated to the Assistant Secretary for Health of HHS the authority to make domestic drug scheduling recommendations. 
                        <E T="03">Comprehensive Drug Abuse Prevention and Control Act of 1970, Public Law 91-513, As Amended; Delegation of Authority,</E>
                         58 FR 35460 (July 1, 1993).
                    </P>
                </FTNT>
                <P>
                    To find that placing a substance temporarily in schedule I of the CSA is necessary to avoid an imminent hazard to public safety, the Administrator must consider three of the eight factors set forth in 21 U.S.C. 811(c): the substance's history and current pattern of abuse; the scope, duration and significance of abuse; and what, if any, risk there is to public health.
                    <SU>10</SU>
                    <FTREF/>
                     This consideration includes any information indicating actual abuse, diversion from legitimate channels, and clandestine importation, manufacture, or distribution of 7-hydroxymitragynine above the specified threshold.
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         21 U.S.C. 811(c)(4)-(6), (h)(3).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         21 U.S.C. 811(h)(3).
                    </P>
                </FTNT>
                <P>
                    Substances meeting the statutory requirements for temporary scheduling 
                    <PRTPAGE P="40918"/>
                    may only be placed in schedule I.
                    <SU>12</SU>
                    <FTREF/>
                     Substances in schedule I have high potential for abuse, no currently accepted medical use in treatment in the United States,
                    <SU>13</SU>
                    <FTREF/>
                     and a lack of accepted safety for use under medical supervision.
                    <SU>14</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         21 U.S.C. 811(h)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         When finding schedule I placement on a temporary basis is necessary to avoid imminent hazard to the public, 21 U.S.C 811(h) does not require DEA to consider whether the substance has a currently accepted medical use in treatment in the United States. Nonetheless, there is no evidence suggesting that 7-hydroxymitragynine has a currently accepted medical use in treatment in the United States. First, DEA looks to whether the drug or substance has FDA approval. When no FDA approval exists, DEA has traditionally applied a five-part test to determine whether a drug or substances has a currently accepted medical use: (1) the drug's chemistry must be known and reproducible; (2) there must be adequate safety studies; (3) there must be adequate and well-controlled studies proving efficacy; (4) the drug must be accepted by qualified experts; and (5) the scientific evidence must be widely available. 
                        <E T="03">Marijuana Scheduling Petition; Denial of Petition; Remand,</E>
                         57 FR 10499 (Mar. 26, 1992), pet. for rev. denied, 
                        <E T="03">Alliance for Cannabis Therapeutics</E>
                         v. 
                        <E T="03">Drug Enforcement Admin.,</E>
                         15 F.3d 1131, 1135 (D.C. Cir. 1994). DEA applied the traditional five-part test and concluded the test was not satisfied. In a recent published letter in a different context, HHS applied an additional two-part test to determine currently accepted medical use for substances that do not satisfy the five-part test: (1) whether there exists widespread, current experience with medical use of the substance by licensed health care providers operating in accordance with implemented jurisdiction-authorized programs, where medical use is recognized by entities that regulate the practice of medicine, and, if so, (2) whether there exists some credible scientific support for at least one of the medical conditions for which part (1) is satisfied. On April 11, 2024, the Department of Justice's Office of Legal Counsel (OLC) issued an opinion, which, among other things, concluded that HHS's two-part test would be sufficient to establish that a drug has a currently accepted medical use. Office of Legal Counsel, Memorandum for Merrick B. Garland Attorney General Re: Questions Related to the Potential Rescheduling of Marijuana at 3 (April 11, 2024). For purposes of this notice of intent, there is no evidence that health care providers have widespread experience with medical use of 7-hydroxymitragynine or that the use of this substance is recognized by entities that regulate the practice of medicine, so the two-part test also is not satisfied. In HHS' letter dated March 6, 2026, HHS advised DEA that there were currently no approved NDAs or INDs for these substances. Additionally, HHS noted it had no objections to the temporary placement of this 7-hydroxymitragynine above the specified threshold in schedule I of the CSA.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         21 U.S.C. 812(b)(1).
                    </P>
                </FTNT>
                <P>
                    7-Hydroxymitragynine Above a Specified Threshold 7-Hydroxymitragynine is a psychoactive alkaloid found in 
                    <E T="03">Mitragyna speciosa</E>
                     (
                    <E T="03">M. speciosa</E>
                    ) plant, a tropical evergreen tree indigenous to Southeast Asia. While the use of the plant was once geographically limited, the use of 
                    <E T="03">M. speciosa</E>
                     has since extended to the United States and other global markets. Among the numerous alkaloids identified in 
                    <E T="03">M. speciosa,</E>
                     the indole alkaloids mitragynine (major) and 7-hydroxymitragynine (minor) are primarily responsible for the plant's psychoactive effects. In its natural botanical form, 7-hydroxymitragynine makes up less than two percent of the total alkaloid content or occurs in trace amount in 
                    <E T="03">M. speciosa.</E>
                     However, 7-hydroxymitragynine can be synthesized from mitragynine through a one-step chemical reaction, and it also exists as an active oxidized metabolite of mitragynine 
                    <E T="03">in vivo.</E>
                     Despite the different origins of 7-hydroxymitragynine, the chemical structures of synthetic and naturally occurring 7-hydroxymitragynine are identical. Consequently, the intrinsic pharmacological profile, receptor affinity, and mechanism of action of 7-hydroxymitragynine molecule remain unchanged regardless of its source. While consumers of raw plant matrix may experience a modified or attenuated physiological effect due to the competitive, co-occurring alkaloids inherent to 
                    <E T="03">M.speciosa,</E>
                     isolated or semi-synthetically derived formulations deliver unattenuated, high-potency effects of the target alkaloid directly, representing a distinct public safety profile when concentrated above the proposed threshold.
                </P>
                <P>
                    Recently, the United States has seen a proliferation of 7-hydroxymitragynine products. Evidence suggests that commercially available products, including extracts and synthetic formulations, contain a significantly higher concentration of 7-hydroxymitragynine than what is found in botanical 
                    <E T="03">M. speciosa.</E>
                     These products are commonly sold on the internet and in retail outlets, such as gas stations and smoke shops, in various forms, including powders, tablets, gummies, and sublingual films designed for rapid absorption. To date, the safety profile of these concentrated products in humans remains unknown because no controlled clinical trials have been conducted to establish safe consumption limits or standardized dosing.
                </P>
                <P>
                    7-Hydroxymitragynine has opioidergic activity, sharing a similar pharmacological profile to schedule II opioids like morphine. Preclinical data 
                    <SU>15</SU>
                    <FTREF/>
                     indicates that 7-hydroxymitragynine carries a high abuse potential with safety risks, including tolerance, dependence, and respiratory depression, which are comparable to those of classic opioid analgesics. The United States has recently seen an emergence of products containing 7-hydroxymitragynine, which are often characterized by ambiguous dosages and misleading marketing, frequently being labeled as “natural 
                    <E T="03">M. speciosa</E>
                     extracts.” While sellers promote these products for their euphoric and opioidergic effects, evidence demonstrates they may also contain other opioid alkaloids, such as mitragynine pseudoindoxyl. These combinations, coupled with a lack of regulatory oversight, pose significant safety risk to unsuspecting consumers by exposing them to high doses of opioids. The absence of clinical evidence to support vendor health claims is deeply concerning. Consequently, 7-hydroxymitragynine products sold as unregulated dietary supplements pose significant health risks, as essential information regarding their purity, identity, quantity and long-term safety remain unknown.
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         Hemby, S.E., McIntosh, S., Leon, F., Cutler, S.J., &amp; McCurdy, C.R. (2019). Abuse liability and therapeutic potential of the Mitragyna speciosa (kratom) alkaloids mitragynine and 7-hydroxymitragynine. 
                        <E T="03">Addiction biology, 24</E>
                        (5), 874-885.
                    </P>
                </FTNT>
                <P>
                    7-Hydroxymitragynine does not meet the United States Food and Drug Administration (FDA) safety standard for dietary supplements, or dietary ingredients, and it has not been proven safe or effective for any drug use. FDA has issued warning letters to companies clarifying that 7-hydroxymitragyine is not an FDA-approved drug product and no food additive regulation has authorized the use of 7-hydroxymitragynine in food supply. Furthermore, FDA has warned consumers against using products labeled as 7-hydroxymitragynine, as they have not been proven safe or effective for any use.
                    <SU>16</SU>
                    <FTREF/>
                     Fatal overdoses involving 7-hydroxymitragynine have been reported, making its wide availability and unknown safety profile a significant threat to public health, which is particularly concerning in the midst of an opioid crisis. The availability of 7-hydroxymitragynine-containing substances in the United States' 
                    <E T="03">M. speciosa</E>
                     consumer market poses an imminent hazard to the public safety.
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         FDA Issues Warning Letters to Firms Marketing Products Containing 7-Hydroxymitragynine | FDA, 
                        <E T="03">available at https://www.fda.gov/news-events/press-announcements/fda-issues-warning-letters-firms-marketing-products-containing-7hydroxymitragynine#:~:text=FDA%20Issues%20Warning%20Letters%20to%20Firms%20Marketing%20Products%20Containing%207%2DHydroxymitragynine,-Alkaloid%20known%20as&amp;text=The%20U.S.%20Food%20and%20Drug,also%20known%20as%207%2DOH,</E>
                         Accessed July 31, 2025.
                    </P>
                </FTNT>
                <P>
                    Available data and information for 7-hydroxymitragynine, summarized below, indicate that this substance has a high potential for abuse, no currently accepted medical use in treatment in the United States, and a lack of accepted safety for use under medical 
                    <PRTPAGE P="40919"/>
                    supervision. DEA's three-factor analysis is available in its entirety under “Supporting and Related Material” of the public docket for this action at 
                    <E T="03">www.regulations.gov</E>
                     under Docket Number DEA-1570.
                </P>
                <HD SOURCE="HD1">Factor 4. History and Current Pattern of Abuse</HD>
                <P>
                    7-Hydroxymitragynine is most commonly used in isolated form or as component of 
                    <E T="03">M. speciosa.</E>
                     Historically, 
                    <E T="03">M. speciosa</E>
                     has been used for a variety of purposes, including as an opium substitute and a treatment of various opioid withdrawal symptoms, such as pain, cough, anxiety, diarrhea, and intestinal difficulty.
                    <SU>17</SU>
                    <FTREF/>
                     While its use was once geographically limited, the marketing in the United States of 7-hydroxymitragynine products has been aggressive and often indistinguishable from the sale of 
                    <E T="03">M. speciosa.</E>
                    <SU>18</SU>
                    <FTREF/>
                     In recent years, 7-hydroxymitragynine has been unlawfully marketed as a dietary supplement 
                    <SU>19</SU>
                    <FTREF/>
                     or natural extract despite failing to meet FDA's safety standard for dietary supplements or dietary ingredients. Anecdotal information from users who post on social media indicates that many users are self-treating chronic pain with unregulated 7-hydroxymitragynine products.
                    <SU>20</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         Grundmann, O., Green, M., Berthold, E., Yoon, S.L., &amp; Ray, D. (2025). Prevalence and Use Patterns of Kratom (
                        <E T="03">Mitragyna speciosa</E>
                         Korth.) in a US Nationally Representative Sample. 
                        <E T="03">Journal of psychoactive drugs,</E>
                         1-9.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         Smith, K.E., Boyer, E.W., Grundmann, O., McCurdy, C.R., &amp; Sharma, A. (2025). The rise of novel, semi-synthetic 7-hydroxymitragnine products. 
                        <E T="03">Addiction (Abingdon, England),</E>
                         120(2), 387-388.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         FDA issued warning letters to firms marketing products containing 7-hydroxymitragynine stating it is not a lawful dietary supplement, food additive, or ingredient in any approved drug”. FDA Issues Warning Letters to Firms Marketing Products Containing 7-Hydroxymitragynine | FDA, 
                        <E T="03">available at https://www.fda.gov/news-events/press-announcements/fda-issues-warning-letters-firms-marketing-products-containing-7-hydroxymitragynine#:~:text=FDA%20Issues%20Warning%20Letters%20to%20Firms%20Marketing%20Products%20Containing%207%2DHydroxymitragynine,-Alkaloid%20known%20as&amp;text=The%20U.S.%20Food%20and%20Drug,also%20known%20as%207%2DOH,</E>
                         accessed on July 15, 2025.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         National Drug Early Warning System (NDEWS). (2025). Alert from the NDEWS Web Monitoring Team: Online mentions of Kratom and Derivatives (May 30, 2025). Retrieved from 
                        <E T="03">ndews.org.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD2">Product Formulation and Marketing Claims</HD>
                <P>
                    7-Hydroxymitragynine products are readily obtained from smoke shops, gas stations, and online vendors in various forms, including tablets, liquid oral beverages (shots), capsules, powder, syrup, vapes, sublingual pouch/strips, nasal spray, chewable, and liquid extracts. These products are commonly sold with names such as “7 Ohmz,” “7-hydroxy,”, and “7-OH,” and they are presented in colorful packages. One investigation identified 250 products sold between September 2024 through February 2025, noting that chewable/sublingual tablets were the most common formulation.
                    <SU>21</SU>
                    <FTREF/>
                     These products were sold for general wellbeing and claims of increased focus. The investigation further highlighted the concerns regarding standardized dosing and cost. The concentration of 7-hydroxymitragynine products varied significantly, ranging from 1 mg to 700 mg in a single dose or serving. The average cost per dose across most products containing 7-hydroxymitragynine was about $3.97.
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         Hill, K., Boyer, E.W., Grundmann, O., &amp; Smith, K.E. (2025). De facto opioids: Characterization of novel 7-hydroxymitragynine and mitragynine pseudoindoxyl product marketing. 
                        <E T="03">Drug and Alcohol Dependence,</E>
                         272, 112701.
                    </P>
                </FTNT>
                <P>
                    Anecdotal information synthesized from user-contributed reports and subsequently analyzed by clinical educators 
                    <SU>22</SU>
                    <FTREF/>
                     between 2024 and early 2025 provide additional information on abuse patterns. Users consistently report transition from traditional kratom leaf to 7-hydroxymitragynine tablets (
                    <E T="03">e.g.,</E>
                     7OHMZ, Press'd, Hydroxie). 7-Hydroxymitragynine was described as “the cleanest and most euphoric high” that lacks “ceiling effect of nausea” of the plain leaf. A dominant theme is the short-lived nature of the 7-hydroxymitragynine high. Users report the urge to redose frequently.
                </P>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         University of Connecticut School of Pharmacy and Pharmaceutical Sciences. (2025), Kratom and Knock Offs, Should You Leaf Them Alone: You Asked for It!. 
                        <E T="03">available at https://pharmacy.uconn.edu/course/kratom/</E>
                        .
                    </P>
                </FTNT>
                <P>
                    The National Drug Early Warning System (NDEWS) conducted web monitoring on reddit mentions of kratom and its derivates. In the report, information provided by reddit discussants surrounding kratom and 7-hydroxymitragynine shows that users often compare 7-hydroxymitragynine effects to prescription opioids, like oxycodone and hydrocodone, with users expressing worry on how such potent products are legally available at smoke shops. Commenters mentioned the ease and convenience of buying products at gas stations and noted how this can be a concern for impulse use due to ease of accessibility. Further, discussions on full commercial retail package prices ranged from $15-40 per retail unit,
                    <SU>23</SU>
                    <FTREF/>
                     which is consistent with multi-dose presentation of these commercial formulations.
                </P>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         Alert from the NDEWS Web Monitoring Team: Online mentions of Kratom and Derivatives (May 30, 2025). Retrieved from 
                        <E T="03">ndews.org.</E>
                    </P>
                </FTNT>
                <P>In summary, 7-hydroxymitragynine products are available in different forms and can be purchased easily via several avenues, predominantly via the internet. This is a shift from traditional botanical use to aggressive marketing of highly concentrated opioid products in the United States.</P>
                <HD SOURCE="HD1">Factor 5. Scope, Duration, and Significance of Abuse</HD>
                <P>
                    The abuse of 7-hydroxymitragynine is increasing and widespread. Given its pharmacological profile as an opioid agonist and high abuse potential,
                    <SU>24</SU>
                    <FTREF/>
                     the marketing of 7-hydroxymitragynine products to consumers as botanical supplements constitute a significant public health risk. 7-Hydroxymitragynine, a potent opioid, presents overdose risk and toxicity to users because its chemical manufacturing process is inconsistent and does not adhere to good manufacturing practices. This lack of oversight may lead to variation in doses and composition in final products. Further, 7-hydroxymitragynine is sold as sublingual pouch/tablet, a formulation known to deliver drugs rapidly into the systemic circulation. This rapid delivery, coupled with 7-hydroxymitragynine's known pharmacokinetic profile, contributes to its high potential for abuse.
                    <SU>25</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         Hemby, S.E., McIntosh, S., Leon, F., Cutler, S.J., &amp; McCurdy, C.R. (2019). Abuse liability and therapeutic potential of the Mitragyna speciosa (kratom) alkaloids mitragynine and 7-hydroxymitragynine. 
                        <E T="03">Addiction Biology,</E>
                         24(5), 874-885.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         Hill, K., Boyer, E. W., Grundmann, O., &amp; Smith, K.E. (2025). De facto opioids: Characterization of novel 7-hydroxymitragynine and mitragynine pseudoindoxyl product marketing. 
                        <E T="03">Drug and Alcohol Dependence,</E>
                         272, 112701; Sharma, A., Smith, K.E., Kuntz, M.A., Berthold, E.C., Elashkar, O.I., Guadagnoli, N., Kanumuri, S. R.R., Mukhopadhyay, S., Panlilio, L.V., Epstein, D.H., &amp; McCurdy, C. R. (2025). Chemical Analysis and Alkaloid Intake for Kratom Products Available in the United States. 
                        <E T="03">Drug Testing and Analysis,</E>
                         17(10), 1974-1984.
                    </P>
                </FTNT>
                <P>
                    7-hydroxymitragynine sellers make claims of its opioidergic effects. Evidence demonstrates that 7-hydroxymitragynine products have been identified to contain other opioid alkaloids, such as mitragynine pseudoindoxyl.
                    <SU>26</SU>
                    <FTREF/>
                     These combinations and practice pose significant safety risks to unsuspecting consumers by exposing them to high doses of opioids. The lack of evidence to support health claims made by vendors selling 7-hydroxymitragynine products is 
                    <PRTPAGE P="40920"/>
                    worrisome. Hence, 7-hydroxymitragynine products sold as dietary supplements pose significant health risks to users because information on their purity, identity, quantity and safety is unknown.
                </P>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         7-Hydroxy Mitragynine NPS Discovery, 
                        <E T="03">available at https://www.cfsre.org/images/content/reports/public_alerts/7-Hydroxy_Mitragynine_NPS_Discovery_033125.pdf,</E>
                         accessed March 10, 2026.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">Law Enforcement Encounters</HD>
                <P>
                    The number of seizures for 7-hydroxymitragynine as reported in law enforcement systems is currently limited, primarily because forensic chemists often prioritize the identification of mitragynine, the major alkaloid in 
                    <E T="03">M. speciosa,</E>
                     rather than extending analysis to the identification of minor alkaloids, such as 7-hydroxymitragynine. Furthermore, because 7-hydroxymitragynine is not federally controlled under the CSA, specific forensic identification may be limited. Consequently, some forensic laboratories may not place emphasis on analyzing or tracking the encounters of non-controlled substances, making it unlikely to be fully reported to forensic laboratories databases. Nonetheless, available data from the National Forensic Laboratory Information System (NFLIS) database 
                    <SU>27</SU>
                    <FTREF/>
                     shows that, in 2025, there were 42 reports of 7-hydroxymitagynine from 12 states. This law enforcement data illustrates the widespread and increasing availability of products containing 7-hydroxymitragynine within the domestic kratom drug market.
                </P>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         NFLIS represents an important resource in monitoring illicit drug trafficking, including the diversion of legally manufactured pharmaceuticals into illegal markets. NFLIS is a comprehensive information system that includes data from forensic laboratories that handle more than 96 percent of an estimated 1.0 million distinct annual State and local drug analysis cases. NFLIS includes drug chemistry results from completed analyses only. While NFLIS data is not direct evidence of abuse, it can lead to an inference that a drug has been diverted and abused. 
                        <E T="03">See Schedules of Controlled Substances: Placement of Carisoprodol Into Schedule IV,</E>
                         76 FR 77330, 77332 (Dec. 12, 2011). NFLIS data were queried on February 26, 2026.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">FDA Warning Letters</HD>
                <P>
                    Between June and July 2025, FDA issued seven warning letters 
                    <SU>28</SU>
                    <FTREF/>
                     to marketers and distributors for the unlawful use of 7-hydroxymitragynine as a drug, dietary supplement, or added to conventional food. The warning letters explicitly stated that 7-hydroxymitragyine is not an FDA-approved drug product and that no food additive regulation has authorized the use of 7-hydroxymitragynine in food. FDA further classified 7-hydroxymitragynine as a “new dietary ingredient” under section 413(d) of the FD&amp;C Act, 21 U.S.C. 350b(d), because there is no evidence demonstrating it was marketed as a dietary ingredient in the United States before October 15, 1994. Additionally, some letters noted that, as a dietary supplement, 7-hydroxymitragynine is considered adulterated under section 402(f)(l)(B) of the FD&amp;C Act,21 U.S.C. 342(f)(l)(B). This is because there is inadequate information providing reasonable assurance that the ingredient does not present a significant or unreasonable risk of illness or injury. Of note was FDA's warning letter issued on June 25, 2025, to a company selling “7OHMZ 7-Hydroxymitragynine Gummies,” 
                    <SU>29</SU>
                    <FTREF/>
                     in which FDA cautioned that such products may be appealing to children due to their packaging. Other warning letters targeted the illegal sale of unapproved 7-hydroxymitragynine products marketed for the treatment of pain, relaxation, mood enhancement, and other medical conditions.
                    <SU>30</SU>
                    <FTREF/>
                     Vendors utilized websites and social media pages to make unproven medical claims for 7-hydroxymitragynine, such as describing tablets as “expertly formulated to provide a potent dose” or promising “intense relaxation and a feeling of pure bliss.”
                </P>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         FDA Issues Warning Letters to Firms Marketing Products Containing 7-Hydroxymitragynine | FDA, 
                        <E T="03">available at https://www.fda.gov/news-events/press-announcements/fda-issues-warning-letters-firms-marketing-products-containing-7-hydroxymitragynine</E>
                         ; 7Tabz Retail, LLC-709546-06/25/2025 | FDA, 
                        <E T="03">available at https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/7tabz-retail-llc-709546-06252025;</E>
                          
                        <E T="03">https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/hydroxie-llc-709661-06252025; https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/shaman-botanicals-llc-709622-06252025;</E>
                          
                        <E T="03">https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/royal-diamond-imports-inc-709540-06252025; https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/thang-botanicals-inc-dba-7ohmz-7-ohmz-or-7ohmz-710190-06252025;</E>
                          
                        <E T="03">https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/relax-relief-rejuvenate-trading-llc-dba-rrr-trading-or-edp-kratom-709475-06252025; https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/relax-relief-rejuvenate-trading-llc-dba-rrr-trading-or-edp-kratom-709475-06252025.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         Thang Botanicals, Inc. d/b/a 7ΩHMZ, 7-OHMZ, or 7OHMZ-710190-06/25/2025 | FDA, 
                        <E T="03">available at https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/thang-botanicals-inc-dba-7ohmz-7-ohmz-or-7ohmz-710190-06252025.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         FDA Warning Letter, Royal Diamond Imports, Inc. (June 25, 2025), 
                        <E T="03">available at https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/royal-diamond-imports-inc-709540-06252025;</E>
                         FDA Warning Letter, Hydroxie, LLC (June 25, 2025), 
                        <E T="03">available at https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/hydroxie-llc-709661-06252025.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD2">State Regulations and Controls</HD>
                <P>
                    Due to concerns over its abuse, several states have regulated or banned the consumption of 7-hydroxymitragynine or 
                    <E T="03">M. speciosa.</E>
                    <SU>31</SU>
                    <FTREF/>
                     Currently, nine states (Alabama, Arkansas, Florida, Indiana, Kentucky, Louisiana, Ohio, Vermont, and Wisconsin) have prohibited 7-hydroxymitragynine consumption. Additionally, some states, such as Arizona, Colorado, South Carolina, and Texas, have set restrictions on the limits of 7-hydroxymitragynine (not to exceed a specified percent of total alkaloid content).
                </P>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         Legislative Analysis and Public Policy Association, Kratom: Summary of State Laws (April 2025), 
                        <E T="03">available at https://legislativeanalysis.org/wp-content/uploads/2025/07/Kratom-Summary-of-State-Laws.pdf.</E>
                         Accessed August 8, 2025.
                    </P>
                </FTNT>
                <P>
                    Furthermore, 19 states have enacted model legislation known as the “kratom consumer protection Act (KCPA),” which requires that 
                    <E T="03">M. speciosa,</E>
                     mitragynine, or 7-hydroxymitragynine be manufactured safely, labeled accurately, and distributed appropriately to protect consumer under a certain age. These states are Arizona, Colorado, Florida, Georgia, Kentucky, Oklahoma, Maryland, Mississippi, Nebraska, Nevada, New York, Oregon, Rhode Island, South Carolina, South Dakota, Texas, Utah, Virginia, and West Virginia. Other states, like Illinois, New Hampshire, North Carolina, and Tennessee, have bans in some localities.
                    <SU>32</SU>
                    <FTREF/>
                     Of note, the state of Mississippi has set the limit per weight basis to one percent of total alkaloid content of 7-hydroxymitragynine or 0.5 mg per container. DEA's intent to temporarily control 7-hydroxymitragynine above the specified threshold does not preempt more restrictive state law regarding the consumption of 7-hydroxymitragynine and 7-hydroxymitragynine-related products.
                    <SU>33</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         American Kratom Association, Kratom State Legality and Legislation, 
                        <E T="03">available at https://www.americankratom.org/aka-in-your-state.</E>
                         Accessed on February 26, 2026.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         
                        <E T="03">See</E>
                         21 U.S.C. 903; 21 CFR 1307.02.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">Poison Control Center Data (National Poison Data System)</HD>
                <P>
                    The significance of 7-hydroxymitragynine abuse is demonstrated by an increasing volume of calls to poison control centers. Reporting for 7-hydroxymitragynine was historically limited within the National Poison Data System (NPDS); however, specific data codes for this substance were recently implemented between February and May 2025. During the initial tracking period from February 
                    <PRTPAGE P="40921"/>
                    2025 to April 2025, NPDS recorded a total of 53 case reports involving 7-hydroxymitragynine. Of these exposure calls, 37 cases involved single-substance exposure of 7-hydroxymitragynine alone, and 24 cases were classified as abuse involving other substances in combination with 7-hydroxymitragynine. Among the single-substance exposure calls, 16 cases were categorized as intentional abuse, while 13 calls involved moderate medical outcomes where the patients exhibited pronounced and prolonged systemic symptoms.
                </P>
                <P>
                    Expanded data from United States poison centers indicates a rapid escalation in reported incidents.
                    <SU>34</SU>
                    <FTREF/>
                     From January 1 through July 31, 2025, there were 165 exposure cases involving 7-hydroxymitragynine. Of those reporting exposures to 7-hydroxymitragynine alone, 35 percent of these cases resulted in serious health problems, and 67 percent of individuals were treated at a healthcare facility. Patients exposed to 7-hydroxymitragynine frequently exhibit a range of severe physiological and neurological symptoms, including: gastrointestinal (nausea and vomiting), neurological (agitation, confusion, loss of consciousness, and seizure), cardiovascular (sweating, tachycardia, and hypertension), and respiratory (difficulty breathing). According to HHS' review, users report several reasons for using 7-hydroxymitragynine, including the following:
                </P>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         America's Poison Centers, Health Advisory: Serious Illnesses Associated with 7-OH Use, 
                        <E T="03">available at https://poisoncenters.org/news-alerts/13531044.</E>
                         Accessed on August 26, 2025.
                    </P>
                </FTNT>
                <P>
                      
                    <E T="03">Desired Effects:</E>
                     Euphoria and an opioid-like “buzz”/high as motivation for using 7-hydroxymitragynine.
                </P>
                <P>
                      
                    <E T="03">Product Appeal:</E>
                     The availability of “candy-like” formulations of some 7-hydroxymitragynine tablets, which some users acknowledge as carrying health risk due to possibility of overconsumption.
                </P>
                <P>
                      
                    <E T="03">Self-Treatment:</E>
                     Claim of 7-hydroxymitragynine therapeutic value in self-treating pain and anxiety.
                </P>
                <P>
                      
                    <E T="03">Risk Awareness:</E>
                     There is an acknowledgement among users of products containing 7-hydroxymitragynine that these products can lead to addiction, withdrawal symptoms, overdose, and other serious health outcomes, including death.
                </P>
                <P>
                    In summary, the abuse of 7-hydroxymitragynine in the United States is fueled by its pharmacological similarities to opioid analgesics, a lack of regulatory controls, and the relative ease of obtaining 7-hydroxymitragynine products via smoke shops and the internet.
                    <SU>35</SU>
                    <FTREF/>
                     Furthermore, the consumption of 7-hydroxymitragynine alongside other mind-altering substances may exacerbate the potential acute and long-term hazards and risks to the user, especially drug dependence. FDA responded to the increase in sales of 7-hydroxymitragynine products and unsubstantiated medical claims by issuing warning letters to companies to protect public safety. Available information from published literatures and poison control centers suggests that 7-hydroxymitragynine is used by a diverse population for the self-treatment of various health conditions. The ingestion of 7-hydroxymitragynine, a potent opioid, alone or co-ingestion with other substances, commonly a CNS depressant, is of serious concern. The poison control center data and popularity of 7-hydroxymitragynine-products collectively underscores the severity and significance of abuse of 7-hydroxymitragynine in the United States.
                </P>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         internet sellers advertise, market, and provide false medical claims.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Factor 6. What, If Any, Risk There Is to Public Health </HD>
                <P>
                    7-hydroxymitragynine has opioidergic and addictive properties. Available preclinical data demonstrates that 7-hydroxymitragynine has an abuse potential similar to that of schedule I and II opioids, such as heroin, morphine, and fentanyl.
                    <SU>36</SU>
                    <FTREF/>
                     The abuse of 7-hydroxymitragynine presents severe risks to public health, including tolerance, dependence and addiction, respiratory depression, and death. Public health assessment is further complicated because 7-hydroxymitragynine is a known metabolite of mitragynine, making it difficult to distinguish between the ingestion of 
                    <E T="03">M. speciosa</E>
                     and other isolated 7-hydroxymitragynine products.
                </P>
                <FTNT>
                    <P>
                        <SU>36</SU>
                         Alsbrook, S., Pro, G., &amp; Koturbash, I. (2025). From kratom to 7-hydroxymitragynine: evolution of a natural remedy into a public-health threat. 
                        <E T="03">Pharmaceutical Biology,</E>
                         63(1), 896-911.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">FDA-Adverse Event Reporting System (FAERS)</HD>
                <P>On August 11, 2025, DEA queried the FAERS public dashboard for 7-hydroxymitragynine and noted that there were 1 case count in 2023, 2 cases in 2024, and 11 cases as of June 30, 2025. Most of the cases involved drug dependence (n = 6) and withdrawal syndrome (n = 4). A recent query of the database on February 27, 2026, revealed an increase in cases involving 7-hydroxymitragynine. The total count for 2025 increased to 66 with 17 new cases already reported for 2026. Of the total 86 cases currently within the database, 79 cases were reported as serious, including death. To date, 9 cases within the FAERS database have resulted in death.</P>
                <HD SOURCE="HD2">DEA Toxicology Testing Program (DEA TOX)</HD>
                <P>
                    DEA TOX program, which investigates the presence of new psychoactive substances in biological samples from drug overdoses, has identified 7-hydroxymitragynine in 85 cases since 2019.
                    <SU>37</SU>
                    <FTREF/>
                     Of these, 55 were fatal and 30 were non-fatal cases. These cases involved both males and females with a median age of 36. The average concentration of 7-hydroxymitragynine detected in biological samples was 463.23 ng/mL. Samples often contained other related alkaloids (mitragynine and mitragynine pseudoindoxyl) or other drug classes, such as opioids (
                    <E T="03">e.g.</E>
                     fentanyl), benzodiazepines (
                    <E T="03">e.g.</E>
                     bromazolam), and ketamine. Between 2020 and 2025, there has been a significant increase in the positive identification of 7-hydroxymitragynine in fatal overdose cases.
                </P>
                <FTNT>
                    <P>
                        <SU>37</SU>
                         DEA TOX is a surveillance program that aims to detect novel psychoactive substances in fatal and nonfatal overdose cases within the United States. From these cases, biological samples, as well as drug paraphernalia (on limited occasions), are submitted for analysis by hospitals, medical examiners, poison centers, and law enforcement nationwide. Queried on March 5, 2026.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">Case Reports Involving 7-Hydroxymitragynine</HD>
                <P>
                    In 2025, California,
                    <SU>38</SU>
                    <FTREF/>
                     Pennsylvania,
                    <SU>39</SU>
                    <FTREF/>
                     and Texas health authorities linked 7-hydroxymitragynine and concentrated extracts to several illness and overdose cases.
                    <SU>40</SU>
                    <FTREF/>
                     Other notable cases are summarized in the table below:
                </P>
                <FTNT>
                    <P>
                        <SU>38</SU>
                         LISTING OF DEPARTMENT OF PUBLIC HEALTH PRESS RELEASES, 
                        <E T="03">available at http://publichealth.lacounty.gov/phcommon/public/media/mediapubhpdetail.cfm?prid=5156.</E>
                         October 10, 2025.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>39</SU>
                         Increased Volume of Calls Related to Kratom/Mitragynine and 7-hydroxymitragynine (7-OH) to Pennsylvania's Poison Centers, 
                        <E T="03">available at https://www.pa.gov/content/dam/copapwp-pagov/en/health/documents/topics/documents/2025%20HAN/2025-802-%208-4-%20Kratom.pdf.</E>
                         August 4, 2025.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>40</SU>
                         Serious Illnesses Associated with 7-OH Use | Texas DSHS, 
                        <E T="03">available at https://www.dshs.texas.gov/news-alerts/serious-illnesses-associated-7-oh-use.</E>
                         September 2, 2025.
                    </P>
                </FTNT>
                <PRTPAGE P="40922"/>
                <GPOTABLE COLS="4" OPTS="L2,nj,i1" CDEF="s25,r15,r25,r100">
                    <TTITLE>7-Hydroxymitragynine Case reports </TTITLE>
                    <TDESC>[2014-2026]</TDESC>
                    <BOXHD>
                        <CHED H="1">Case report author</CHED>
                        <CHED H="1">Patient profile</CHED>
                        <CHED H="1">Primary complication</CHED>
                        <CHED H="1">Clinical finding</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">
                            Broul et al. (2025) 
                            <SU>41</SU>
                        </ENT>
                        <ENT>31 y/o male</ENT>
                        <ENT>Acute Psychosis</ENT>
                        <ENT>Severe Self-Harm: Documented 7-hydroxymitragynine induced psychosis leading to self-amputation (ears/genitalia).</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Karinen et al. (2014) 
                            <SU>42</SU>
                        </ENT>
                        <ENT>24 y/o male</ENT>
                        <ENT>Fatal Overdose</ENT>
                        <ENT>Fatality: Identified a 7-hydroxymitragynine blood concentration of 0.15 mg/L.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Pullman et al. (2026) 
                            <SU>43</SU>
                        </ENT>
                        <ENT>29 y/o male</ENT>
                        <ENT>Cardiopulmonary arrest</ENT>
                        <ENT>Naloxone Reversal: Confirmed 7-hydroxymitragynine causes opioid respiratory depression reversible with standard antagonist drug.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Wightman and Hu (2025) 
                            <SU>44</SU>
                        </ENT>
                        <ENT>38 y/o male</ENT>
                        <ENT>Severe Dependence</ENT>
                        <ENT>Clinical Detoxification: Patient required inpatient buprenorphine stabilization for high dose 7-hydroxymitragynine withdrawal.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    These 7-hydroxymitragynine products are obtained through unknown sources, where the identity, purity, and concentration of active ingredients are often unknown, uncertain, and inconsistent; thus, posing significant adverse health risks to users. The abuse of 7-hydroxymitragynine poses a substantial hazard to public safety. 7-Hydroxymitragynine is being abused for its opioid-like effects and shares health risks similar to other mu-opioid receptor agonists, such as morphine (schedule II). With no approved medical use, the positive identification of 7-hydroxymitragynine in non-fatal and fatal overdose cases poses a threat to public safety. 7-Hydroxymitragynine products are obtained through unknown sources (commonly through the internet); the identity, purity, and quantity of these substances are uncertain and inconsistent, thus posing significant adverse health risks to users.
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>41</SU>
                         Broul, M., Rudenko, X., Bajus, A., Král, J., Kyenge, D.M., Staňková, Z., &amp; Albrecht, J. (2025). Case Report: Cannabis and kratom-induced self-amputation of ears and penis. 
                        <E T="03">Frontiers in psychiatry, 16,</E>
                         1479863.
                    </P>
                    <P>
                        <SU>42</SU>
                         Karinen R., Posen J.T., Rogde S., &amp; Vindenes V. (2014). An accidental poisoning with mitragynine. 
                        <E T="03">Forensic Science International,</E>
                         245, 29-32.
                    </P>
                    <P>
                        <SU>43</SU>
                         Pullman M.K., Raju Kanumuri S.R., Leon J.F., Cutler S.F., McCurdy C.R., &amp; Sharma. A. (2026). Cardio-pulmonary arrest in a patient revived with naloxone following reported use of 7-hydroxymitragynine. 
                        <E T="03">Clinical Toxicology,</E>
                         64(1), 65-66.
                    </P>
                    <P>
                        <SU>44</SU>
                         Wightman, R.S., &amp; Hu, D. (2025). A Case of 7-OH Mitragynine Use Requiring Inpatient Medically Managed Withdrawal. 
                        <E T="03">Journal of Addiction Medicine,</E>
                         Aug 4. doi: 10.1097/ADM.0000000000001558. Advance online publication.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Finding of Necessity of Schedule I Placement To Avoid Imminent Hazard to Public Safety</HD>
                <P>In accordance with 21 U.S.C. 811(h)(3), based on the available data and information summarized above, the uncontrolled manufacture, distribution, reverse distribution, importation, exportation, conduct of research and chemical analysis, possession, and abuse of 7-hydroxymitragynine pose an imminent hazard to public safety. DEA is not aware of any currently accepted medical uses for 7-hydroxymitragynine in treatment in the United States. A substance meeting the statutory requirements for temporary scheduling, found in 21 U.S.C. 811(h)(1), may only be placed in schedule I. Substances in schedule I are those that have a high potential for abuse, no currently accepted medical use in treatment in the United States, and a lack of accepted safety for use under medical supervision. Available data and information for 7-hydroxymitragynine indicate that this substance has a high potential for abuse, no currently accepted medical use in treatment in the United States, and a lack of accepted safety for use under medical supervision.</P>
                <P>As required by 21 U.S.C. 811(h)(4), the Administrator notified the Assistant Secretary, via letter dated February 24, 2026, of DEA's intention to temporarily place 7-hydroxymitragynine above a specified threshold in schedule I. In a letter dated March 6, 2026, the Assistant Secretary for Health had no objection to the temporary placement of 7-hydroxymitragynine above the specified threshold in schedule I.</P>
                <HD SOURCE="HD1">Conclusion</HD>
                <P>This notice of intent provides the 30-day notice pursuant to 21 U.S.C. 811(h)(1) of DEA's intent to issue a temporary scheduling order. In accordance with 21 U.S.C. 811(h)(1) and (3), the Administrator considered available data and information, herein set forth the grounds for his determination that it is necessary to temporarily schedule 7-hydroxymitragynine above a specified threshold in schedule I of the CSA, and finds that placement of this substance above a specified threshold in schedule I of the CSA is necessary in order to avoid an imminent hazard to the public's safety.</P>
                <P>
                    The temporary placement of 7-hydroxymitragynine above a specified threshold in schedule I of the CSA will take effect pursuant to a temporary scheduling order, which will not be issued before August 5, 2026. Because the Administrator hereby finds that this temporary scheduling order is necessary to avoid an imminent hazard to public safety, it will take effect on the date the order is published in the 
                    <E T="04">Federal Register</E>
                     and remain in effect for two years, with a possible extension of an additional year, pending completion of the regular (permanent) scheduling process.
                    <SU>45</SU>
                    <FTREF/>
                     The Administrator intends to issue a temporary scheduling order as soon as possible after the expiration of 30 days from the date of publication of this document. Upon publication of the temporary order, 7-hydroxymitragynine above a specified threshold will then be subject to the CSA's schedule I regulatory controls and administrative, civil, and criminal sanctions applicable to the manufacture, distribution, reverse distribution, importation, exportation, research, conduct of instructional activities and chemical analysis, and possession.
                </P>
                <FTNT>
                    <P>
                        <SU>45</SU>
                         21 U.S.C. 811(h)(1) and (2).
                    </P>
                </FTNT>
                <P>
                    The CSA sets forth specific criteria for scheduling drugs or other substances. Regular scheduling actions in accordance with 21 U.S.C. 811(a) are subject to formal rulemaking procedures “on the record after opportunity for a hearing” conducted pursuant to the provisions of 5 U.S.C. 556 and 557.
                    <SU>46</SU>
                    <FTREF/>
                     The regular scheduling process of formal rulemaking affords interested parties appropriate process and the government any additional relevant information needed to make a determination. Final decisions that conclude the regular scheduling process of formal rulemaking are subject to judicial review.
                    <SU>47</SU>
                    <FTREF/>
                     Temporary scheduling orders are not subject to judicial review.
                    <SU>48</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>46</SU>
                         21 U.S.C. 811.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>47</SU>
                         21 U.S.C. 877.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>48</SU>
                         21 U.S.C. 811(h)(6).
                    </P>
                </FTNT>
                <PRTPAGE P="40923"/>
                <HD SOURCE="HD1">Regulatory Analyses </HD>
                <P>
                    The CSA provides for expedited temporary scheduling actions where necessary to avoid an imminent hazard to public safety. Under 21 U.S.C. 811(h)(1), the Administrator (as delegated by the Attorney General) may, by order, temporarily schedule substances in schedule I. Such orders may not be issued before the expiration of 30 days from: (1) the publication of a notice in the 
                    <E T="04">Federal Register</E>
                     of the intent to issue such order and the grounds upon which such order is to be issued, and (2) the date that notice of the proposed temporary scheduling order is transmitted to the Assistant Secretary of HHS, as delegated by the Secretary of HHS.
                    <SU>49</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>49</SU>
                         21 U.S.C. 811(h)(1).
                    </P>
                </FTNT>
                <P>
                    Inasmuch as section 811(h) directs that temporary scheduling actions be issued by order and sets forth the procedures by which such orders are to be issued, including the requirement of a publication in the 
                    <E T="04">Federal Register</E>
                     of a notice of intent, the notice-and-comment requirements of the Administrative Procedure Act (APA), 5 U.S.C. 553, do not apply to this notice of intent. The APA expressly differentiates between an order and a rule, as it defines an “order” to mean a “final disposition, whether affirmative, negative, injunctive, or declaratory in form, of an agency 
                    <E T="03">in a matter other than rule making.</E>
                    ” 
                    <SU>50</SU>
                    <FTREF/>
                     This contrasts with permanent scheduling actions, which are subject to formal rulemaking procedures done “on the record after opportunity for a hearing,” and final decisions that conclude the scheduling process and are subject to judicial review.
                    <SU>51</SU>
                    <FTREF/>
                     The specific language chosen by Congress indicates its intent that DEA issue 
                    <E T="03">orders</E>
                     instead of proceeding by rulemaking when temporarily scheduling substances. Given that Congress specifically requires the Administrator (as delegated by the Attorney General) to follow rulemaking procedures for 
                    <E T="03">other</E>
                     kinds of scheduling actions,
                    <SU>52</SU>
                    <FTREF/>
                     it is noteworthy that, in section 811(h)(1), Congress authorized the issuance of temporary scheduling actions by order rather than by rule.
                </P>
                <FTNT>
                    <P>
                        <SU>50</SU>
                         5 U.S.C. 551(6) (emphasis added).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>51</SU>
                         21 U.S.C. 811(a) and 877.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>52</SU>
                         
                        <E T="03">See</E>
                         21 U.S.C. 811(a).
                    </P>
                </FTNT>
                <P>Even assuming that this notice of intent is subject to the notice-and-comment requirements of the APA, the Administrator finds that there is good cause to forgo the those requirements pursuant to 5 U.S.C. 553(b)(B), as any further delays in the process for issuing temporary scheduling orders would be impracticable and contrary to the public interest given the manifest urgency to avoid an imminent hazard to public safety.</P>
                <P>Although DEA believes this notice of intent to issue a temporary scheduling order is not subject to the notice-and-comment requirements of the APA, DEA notes that in accordance with 21 U.S.C. 811(h)(4), the Administrator took into consideration comments submitted by the Acting Assistant Secretary in response to the notice that DEA transmitted to the Acting Assistant Secretary pursuant to such subsection.</P>
                <P>
                    Further, DEA believes that this temporary scheduling action is not a “rule” as defined by 5 U.S.C. 601(2), and, accordingly, is not subject to the requirements of the Regulatory Flexibility Act (RFA). The requirements for the preparation of an initial regulatory flexibility analysis in 5 U.S.C. 603(a) are not applicable where, as here, DEA is not required by the APA or any other law to publish a general notice of proposed rulemaking. As discussed above, DEA is issuing this notice of intent pursuant to DEA's authority to issue a temporary scheduling order.
                    <SU>53</SU>
                    <FTREF/>
                     Therefore, in this instance, since DEA believes this temporary scheduling action is not a “rule,” it is not subject to the requirements of the RFA when issuing this temporary action.
                </P>
                <FTNT>
                    <P>
                        <SU>53</SU>
                         21 U.S.C. 811(h)(1).
                    </P>
                </FTNT>
                <P>In accordance with the principles of Executive Orders (E.O.) 12866 and 13563, this action is not a significant regulatory action. E.O. 12866 directs 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). E.O. 13563 is supplemental to and reaffirms the principles, structures, and definitions governing regulatory review as established in E.O. 12866. Because this is not a rulemaking action, this is not a significant regulatory action as defined in Section 3(f) of E.O. 12866. In addition, 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>This action will not have substantial direct effects on the states, on the relationship between the national government and the states, or on the distribution of power and responsibilities among the various levels of government. Therefore, in accordance with E.O. 13132, it is determined that this action does not have sufficient federalism implications to warrant the preparation of a Federalism Assessment.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 21 CFR Part 1308</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 1308 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 1308—SCHEDULES OF CONTROLLED SUBSTANCES </HD>
                </PART>
                <AMDPAR>1. The authority citation for part 1308 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P> 21 U.S.C. 811, 812, 871(b), 956(b), unless otherwise noted.</P>
                </AUTH>
                <AMDPAR>2. In § 1308.11: Add paragraph (h)(91) to read as follows:</AMDPAR>
                <SECTION>
                    <SECTNO>§ 1308.11</SECTNO>
                    <SUBJECT>Schedule I </SUBJECT>
                    <STARS/>
                    <P>(h) * * *</P>
                    <GPOTABLE COLS="2" OPTS="L1,nj,tp0,p1,8/9,i1" CDEF="s200,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" O="xl">
                                (91) Methyl (
                                <E T="03">E</E>
                                )2-((2
                                <E T="03">S,</E>
                                3
                                <E T="03">S,</E>
                                7
                                <E T="03">aS</E>
                                )-3-ethyl-7
                                <E T="03">a</E>
                                -hydroxy-8-methoxy-1,2,3,4,6,7,7
                                <E T="03">a,</E>
                                12
                                <E T="03">b</E>
                                -octahydroindolo[2,3-
                                <E T="03">a</E>
                                ]quinolizin-2-yl)-3-methoxyacrylate (commonly known as 7-hydroxymitragynine; also known as (αE,2
                                <E T="03">S,</E>
                                3
                                <E T="03">S,</E>
                                7a
                                <E T="03">S,</E>
                                12b
                                <E T="03">S</E>
                                )-3-ethyl-l,2,3,4,6,7,7a,12b-octahydro-7a-hydroxy-8-methoxy-a-(methoxymethylene)-indolo[2,3-
                                <E T="03">a</E>
                                ]quinolizine-2-acetic acid, methyl ester) above a specified threshold, described as:
                            </ENT>
                            <ENT>9675</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">
                                (A) 
                                <E T="03">Any botanical material of the plant Mitragyna speciosa, also known as kratom, and contains more than 0.050 percentage of 7-hydroxymitragynine on a dry weight basis, or</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">
                                (B) 
                                <E T="03">Any alternative article or material to that described in (A), that is:</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">
                                i. 
                                <E T="03">Resulting from synthetic methods and containing 7-hydroxymitragynine present in amounts greater than 0.050 percentage weight/weight, weight/volume, or volume/volume or greater than 1.00 milligram of 7-hydroxymitragynine in the article, or</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="40924"/>
                            <ENT I="05">
                                ii. 
                                <E T="03">Material derived from Mitragyna speciosa and further processed to manufacture alternative dosage forms such as extracts, concentrates, processed edibles, or pressed pills, and which may have materials that have been exposed to chemical, thermal, or other methods leading to chemical transformations that result in 7-hydroxymitragynine present in amounts greater than 0.050 percentage weight/weight, weight/volume, or volume/volume or greater than 1.00 milligram of 7-hydroxymitragynine in the article.</E>
                            </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 July 1, 2026, by DEA Administrator Terrance C. 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>Heather Achbach,</NAME>
                    <TITLE>Federal Register Liaison Officer, Drug Enforcement Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13580 Filed 7-1-26; 4:15 pm]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Bureau of Alcohol, Tobacco, Firearms, and Explosives</SUBAGY>
                <CFR>27 CFR Parts 478 and 479</CFR>
                <DEPDOC>[Docket No. ATF-2026-0397; ATF 2025R-14P]</DEPDOC>
                <RIN>RIN 1140-AA63</RIN>
                <SUBJECT>Fingerprint and Photograph Requirements for Firearms Applications</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Alcohol, Tobacco, Firearms, and Explosives, 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 Bureau of Alcohol, Tobacco, Firearms, and Explosives (“ATF”) proposes amending regulatory requirements to submit fingerprints and photographs with firearms applications. Currently, applicants must submit 2″ × 2″ passport-style photographs and either one or two fingerprint cards, depending on the application type. ATF proposes that all applicants, whether individuals or responsible persons (“RPs”) for entity applicants, could instead submit a copy of a photo ID, and that individuals and Gun Control Act RPs would submit just one fingerprint card. RPs under the National Firearms Act would submit one fingerprint card only if needed to facilitate a background check.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted in writing, and must be submitted on or before (or, if mailed, must be postmarked on or before) October 5, 2026. Commenters should be aware that the federal e-rulemaking portal comment system will not accept comments after midnight Eastern Time on the last day of the comment period.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by RIN 1140-AA63, by either of the following methods—</P>
                    <P>
                        • 
                        <E T="03">Federal e-rulemaking portal: https://www.regulations.gov.</E>
                         Follow the instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         ATF Rulemaking Comments; Mail Stop 6N-518, Office of Regulatory Affairs; Enforcement Programs and Services; Bureau of Alcohol, Tobacco, Firearms, and Explosives; 99 New York Ave. NE; Washington, DC 20226; 
                        <E T="03">ATTN: ATF RIN 1140-AA63.</E>
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions must include the agency name and number (RIN 1140-AA63) for this notice of proposed rulemaking (“NPRM” or “proposed rule”). ATF may post all properly completed comments it receives from either of the methods described above, without change, to the federal e-rulemaking portal, 
                        <E T="03">https://www.regulations.gov.</E>
                         This includes any personally identifying information (“PII”) or business proprietary information (“PROPIN”) submitted in the body of the comment or as part of a related attachment they want posted. Commenters who submit through the federal e-rulemaking portal and do not want any of their PII posted on the internet should omit it from the body of their comment and any uploaded attachments that they want posted. If online commenters wish to submit PII with their comment, they should place it in a separate attachment and mark it at the top with the marking “CUI//PRVCY.” Commenters who submit through mail should likewise omit their PII or PROPIN from the body of the comment and provide any such information on the cover sheet only, marking it at the top as “CUI//PRVCY” for PII, or as “CUI//PROPIN” for PROPIN. For detailed instructions on submitting comments and additional information on the rulemaking process, see the “Public Participation” heading of the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section of this document. In accordance with 5 U.S.C. 553(b)(4), a summary of this rule may be found at 
                        <E T="03">https://www.regulations.gov.</E>
                         Commenters must submit comments by using one of the methods described above, not by emailing the address set forth in the following paragraph.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Office of Regulatory Affairs, by email at 
                        <E T="03">ORA@atf.gov,</E>
                         by mail at Office of Regulatory Affairs; Enforcement Programs and Services; Bureau of Alcohol, Tobacco, Firearms, and Explosives; 99 New York Ave. NE; Washington, DC 20226, or by telephone at 202-648-7070 (this is not a toll-free number).
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    The Attorney General is responsible for enforcing the Gun Control Act (“GCA”), as amended, and the National Firearms Act (“NFA”), as amended.
                    <SU>1</SU>
                    <FTREF/>
                     This includes the authority to promulgate regulations necessary to enforce the provisions of the GCA and NFA. 
                    <E T="03">See</E>
                     18 U.S.C. 926(a); 26 U.S.C. 7805(a). Congress and the Attorney General have delegated the responsibility for administering and enforcing the GCA and NFA to the Director of ATF (“Director”), subject to the direction of the Attorney General and the Deputy Attorney General. 
                    <E T="03">See</E>
                     28 U.S.C. 599A(b)(1), (c)(1); 28 CFR 0.130(a)(1)-(2); Treas. Order No. 221(2)(a), (d), 37 FR 11696-97 (June 10, 1972).
                    <SU>2</SU>
                    <FTREF/>
                     Accordingly, the Department 
                    <PRTPAGE P="40925"/>
                    and ATF have promulgated regulations to implement the GCA in 27 CFR part 478, and to implement the NFA in part 479.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Some NFA provisions still refer to the “Secretary of the Treasury.” However, the Homeland Security Act of 2002, Public Law 107-296, 116 Stat. 2135, transferred the functions of ATF from the Department of the Treasury to the Department of Justice, under the general authority of the Attorney General. 26 U.S.C. 7801(a)(2); 28 U.S.C. 599A(c)(1). Thus, for ease of reference, this proposed rule refers to the Attorney General where relevant.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         In Attorney General Order Number 6353-2025, the Attorney General delegated authority to the Director to issue regulations pertaining to matters within ATF's jurisdiction, including under the NFA, GCA, and Title XI of the Organized Crime Control Act. ATF's jurisdiction also includes the Arms Export Control Act and the Contraband Cigarette Trafficking Act.
                    </P>
                </FTNT>
                <P>
                    The NFA applies to machine guns; shotguns having a barrel or barrels of less than 18 inches in length; rifles having a barrel or barrels of less than 16 inches in length; weapons made from a rifle or shotgun with an overall length of less than 26 inches or with a barrel or barrels of less than 16 or 18 inches in length, respectively; silencers; destructive devices; and any other weapon as defined by the Act. 26 U.S.C. 5845(a). The GCA applies to firearms and destructive devices more broadly, in addition to specific subcategories of those weapons. 
                    <E T="03">See</E>
                     18 U.S.C. 921(a)(3)-(8).
                </P>
                <P>
                    Pursuant to the GCA at 18 U.S.C. 923(a), no person 
                    <SU>3</SU>
                    <FTREF/>
                     may import, manufacture, or deal in firearms or ammunition without a license to do so from the Attorney General. The license application must include information the Attorney General prescribes by regulation, and by statute must include the applicant's photograph and fingerprints. 
                    <E T="03">Id.</E>
                     ATF implemented these requirements in regulations at 27 CFR 478.44(a).
                    <SU>4</SU>
                    <FTREF/>
                     Paragraph (a)(1) requires persons to submit ATF Form 5310.12, Application for Federal Firearms License (“Form 7”) to apply for GCA licenses, and paragraph (a)(1)(ii) contains the fingerprint and photograph requirement for all GCA applicants.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         “Person” as defined in ATF regulations at §§ 478.11 and 479.11 includes individuals and entities.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         27 CFR 478.44 also includes paragraph (b), which covers persons applying for a license as a collector of curios or relics. These licensees do not deal firearms in commerce, and they thus do not have to provide photographs and fingerprints for background check purposes. However, they use the same Form 7 as other applicants (referred to in the existing regulatory text as Form 7CR because the two forms were once separate and had different names). Form 7 therefore includes instructions specifying that these applicants do not need to submit photos and prints with their applications if they are applying solely for this type of license. ATF is including a minor technical edit in this proposed rule to update the form references in § 478.44(b) from Form 7CR to Form 7 to reduce confusion by eliminating the outdated form number.
                    </P>
                </FTNT>
                <P>
                    Because entities do not have personal photographs or fingerprints to submit, it is not immediately obvious that they are facially covered by the 18 U.S.C. 923(a) requirements. However, section 923(d)(1)(B) further states that a GCA application will be approved only if, among other requirements, the applicant “(including, in the case of [an entity], any individual possessing, directly or indirectly, the power to direct or cause the direction of the management and policies of the [entity])” is not prohibited from possessing a firearm under sections 922(g) and (n). ATF refers to the directing individuals referenced in section 923(d)(1)(B) as “responsible persons” (“RPs”). 27 CFR 478.11.
                    <SU>5</SU>
                    <FTREF/>
                     Because of this statutory provision, ATF must collect identifying information on RPs for all firearms licensees, including entities, that is sufficient to determine that they are not prohibited persons.
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         Individuals who apply for federal firearms licenses under the GCA do so because they seek to engage in the business of dealing, manufacturing, or importing firearms. As a result, these individuals are essentially entities, though structured as sole proprietorships. Because each individual applicant for a firearms license is also the individual possessing the power to direct management and policies for their own operation, individual applicants are also responsible persons. As a result, Form 7, part B is titled “Responsible Person Questionnaire,” though both individual applicants and other responsible persons complete this part. When an entity has more than one RP, the entity attaches additional parts B and submits them with Form 7. ATF therefore does not distinguish between GCA individual applicants and entity applicants or between GCA individuals and RPs for purposes of this rule.
                    </P>
                </FTNT>
                <P>As a result, ATF's licensing regulations require all GCA applicants to submit certain identifying information used for that purpose, including fingerprints and photographs. More specifically, the regulations require applicants to complete Form 7 in accordance with the instructions on the Form. 27 CFR 478.44(a)(1). Form 7 requires that each applicant complete part B, whether they are an individual applicant/RP or an RP for a more complex entity. Part B collects the identifying information necessary to conduct a background check to determine if the person is prohibited, and currently specifies that GCA individual applicants/RPs must submit a 2″ × 2″ photograph and one properly completed FBI Form FD-258, Fingerprint Card (“fingerprint card” or “fingerprints”).</P>
                <P>
                    Similarly, pursuant to 26 U.S.C. 5822, an NFA firearm cannot be made unless the Attorney General approves the person to make and register the firearm and notes the approval on the application, and, per 26 U.S.C. 5812, an NFA firearm cannot be transferred without an application filed with and approved by the Attorney General. The Attorney General must deny such making and transfer applications if making, transferring, receiving, or possessing the NFA firearm would place the maker or transferee in violation of law. 26 U.S.C. 5812(a), 5822. The NFA requires that “individual” firearm makers and transferees include as part of these applications their fingerprints and photographs, in a manner prescribed by regulation.
                    <SU>6</SU>
                    <FTREF/>
                      
                    <E T="03">Id.</E>
                     But the statute imposes no fingerprint or photograph requirements on trusts or other legal entities. 
                    <E T="03">See id.</E>
                     The statute also requires applicants to use an application “form” prescribed by the Attorney General and to include on that form all information required by the statute, in a manner prescribed by regulation. 
                    <E T="03">Id.</E>
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         Under the NFA, individual applicants to make or receive an NFA firearm are most often not federal firearms licensees and are instead applying to make or acquire the firearm in their personal capacity. As a result, they are typically not also responsible persons. Accordingly, ATF is treating NFA individuals separately from NFA RPs in this proposed rule, unlike its approach to the GCA portions of the rule.
                    </P>
                </FTNT>
                <P>
                    Regulations at 27 CFR 479.62 implement these statutory requirements for NFA firearm makers, and prescribe that applicants must submit ATF Form 5320.1, Application to Make and Register NFA Firearm (“Form 1”), to ATF for approval, and include the information required by statute. Likewise, regulations at § 479.84 (for tax-paid transfers) and §§ 479.90 and 479.90a (for tax-exempt transfers) implement these statutory requirements for NFA firearm transferors, and prescribe that transferors must submit ATF Form 5320.4, Application to Transfer and Register NFA Firearm (Tax-Paid) (“Form 4”), or ATF Form 5320.5, Application to Transfer and Register NFA Firearm (Tax-Exempt) (“Form 5”), to ATF for approval, and include the transferee information required by statute. The NFA regulations currently require individual makers or transferees to submit a 2″ × 2″ photograph and fingerprints when applying using Forms 1, 4, or 5; but NFA regulations require two properly completed fingerprint cards, whereas Form 7 for GCA license applicants requires just one. 
                    <E T="03">See</E>
                     §§ 479.63(a), 479.85(a), and 479.90(b).
                </P>
                <P>
                    If a maker or transferee applicant is an entity, however, as discussed above, they do not have personal photographs or fingerprints to submit. So, similarly to the Form 7, part B, requirements for GCA license applicants, the NFA regulations require that each of the entity's RPs submit all the required individual information on ATF Form 5320.23, National Firearms Act (NFA) Responsible Person Questionnaire (“Form 23”).
                    <SU>7</SU>
                    <FTREF/>
                      
                    <E T="03">See</E>
                     §§ 479.63(b) and 479.85(b); 
                    <E T="03">see also</E>
                     27 CFR 479.11 (defining “responsible person” along 
                    <PRTPAGE P="40926"/>
                    the same lines as the relevant GCA regulation). For these entity applicants, §§ 479.63(b) and 479.85(b) require the entity to identify itself on ATF Form 1, 4, or 5, and attach to the form a completed Form 23 for each RP. In completing the Form 23, each RP must include a 2″ × 2″ photograph and two properly completed fingerprint cards.
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         However, whereas GCA individual applicants still complete the Form 7, part B, responsible person questionnaire, NFA individual applicants do not complete the Form 23 responsible person questionnaire. Instead, they simply include their personal information in Form 1, 4, or 5.
                    </P>
                </FTNT>
                <P>Pursuant to 26 U.S.C. 5801 and 5802, importers, manufacturers, and dealers in NFA firearms must pay a special occupational tax (“SOT”) and register with the Attorney General. The registration provision, section 5802, requires that individuals include with their SOT registration a photograph and fingerprints. The regulations implementing this process are 27 CFR 479.31 and 479.34. Similarly to the previously discussed applications, ATF has prescribed that persons submit ATF Form 5630.7, the title of which is being revised to NFA Special Occupational Tax (SOT) Registration/Return (“Form 5630.7”), for this purpose. In addition, § 479.34(e) requires the taxpayer, if an individual, to submit a 2″ × 2″ photograph and one properly completed fingerprint card with their initial Form 5630.7, unless they have filed a properly executed GCA license application (which includes fingerprints and a photograph) as specified in § 478.44(a). As a result, only individuals registering to import, manufacture, or deal in NFA firearms as a business, and who are not already licensed under the GCA, must submit a photograph and fingerprints with Form 5630.7.</P>
                <P>
                    In 2016, ATF published a final rule, “Machineguns, Destructive Devices, and Certain Other Firearms: Background Checks for Responsible Persons of a Trust or Legal Entity with Respect to Making or Transferring a Firearm,” which, in relevant part, required background checks on NFA RPs and enacted the fingerprint requirements under §§ 479.63(b) and 479.85(b). 81 FR 2658 (Jan. 15, 2016). Commenters at that time questioned whether there was sufficient statutory authority for ATF to require fingerprints and photographs for such RPs because the NFA requires that only individual applicants must submit fingerprints and photographs. 
                    <E T="03">Id.</E>
                     at 2683. At the time, ATF disagreed with these commenters. The NFA provides broad authority for the Attorney General to require identifying information from any applicant to make or transfer an NFA firearm. 
                    <E T="03">See</E>
                     26 U.S.C. 5812 and 5822. (Similarly, 18 U.S.C. 923 provides broad authority for the Attorney General to require identifying information from any license applicant under the GCA.) The final rule on the NFA making and transfer applications explained that requiring fingerprint cards and photographs was necessary to verify the identity of RPs associated with trusts and other legal entities. 81 FR at 2683.
                </P>
                <HD SOURCE="HD1">II. Proposed Rule</HD>
                <P>Nine years after the 2016 final rule, ATF recognizes that, even if it has the statutory authority to require fingerprints and photographs from both NFA and GCA RPs and individual applicants, the current regulations on those topics largely no longer serve a useful purpose. In almost all cases, fingerprint cards are of little utility to the Federal Bureau of Investigation (“FBI”) when it conducts National Instant Criminal Background Check System (“NICS”) background checks on applicants to make, transfer, and register NFA firearms or to become GCA licensees. According to ATF and FBI subject matter experts, fingerprint cards have only been helpful (and used) for NICS purposes in processing fewer than 1 percent of these applications. Similarly, 2″ × 2″ passport-style photographs serve little specific utility as a means of verifying an NFA or GCA applicant's identity. A copy of the applicant's photo identification would better serve this verification purpose, and providing a photo identification copy is easier than obtaining a 2″ × 2″ photograph. Thus, requiring fingerprints and a 2″ × 2″ photograph to be submitted with every NFA application is needlessly burdensome on applicants, as is requiring a 2″ × 2″ photograph with every GCA application. Accordingly, ATF is proposing the following revisions.</P>
                <HD SOURCE="HD2">A. Fingerprints</HD>
                <P>
                    For each making or transfer application under the NFA and license application under the GCA (except for collectors), ATF contacts NICS to conduct a background check and verify whether transferring, receiving, or possessing the firearm(s) would place the applicant in violation of the law. 
                    <E T="03">See</E>
                     28 CFR 25.6(j)(2). FBI regulations require the following descriptors to query NICS: (1) name; (2) sex; (3) race; (4) complete date of birth; and (5) residence state. 28 CFR 25.7. Notably, none of these descriptors require a fingerprint. For NFA applications, fingerprints are primarily used to coordinate with the FBI to resolve criminal-history issues or other similar issues that can arise during background checks. For example, fingerprints are useful when an applicant's biographic information matches that of another individual. The FBI also references NFA fingerprints with respect to resolving identity questions in its NICS appeals process. 
                    <E T="03">See</E>
                     28 CFR 25.10(b). The FBI uses fingerprints for the same purposes for GCA license applications, although ATF also has additional uses for fingerprints in the GCA licensing context (see discussion below) that it does not have for NFA maker and transferee applications.
                </P>
                <P>ATF routinely collaborates with the FBI on streamlining and modernizing the firearms application process. For example, in January 2022, ATF agreed to send fingerprint cards to the FBI only when helpful to resolve issues arising during a NICS background check. As a result, ATF now generally submits fingerprint cards to the FBI only when the FBI needs additional information and therefore requests the cards from ATF. Based on ATF and FBI estimates, the FBI has used fingerprints to resolve questions about a person's criminal history in only a small portion of all cases. The first column of Table 1 shows the total number of NFA and GCA individual and RP applicants from 2022 to 2025 who submitted an individual Form 1 or Form 4 (including fingerprints) or an RP Form 23 (including fingerprints) with Forms 1 and 4 applications to make and transfer under the NFA, or who completed an individual Form 7 (including fingerprints) or an RP stand-alone Form 7, part B (including fingerprints) with applications for a GCA license. The second and third columns show the subsets of those NFA and GCA applicants, respectively, for whom NICS requested fingerprints. The fourth column is the sum of the second and third columns. Of all fingerprint cards provided to ATF with the NFA and GCA applications (column 1) between 2022 and 2025 (the years during which ATF has been submitting only requested fingerprint cards to NICS), NICS requested between 1.3 and 2.3 percent per year (column 5).</P>
                <GPH SPAN="3" DEEP="258">
                    <PRTPAGE P="40927"/>
                    <GID>EP06JY26.007</GID>
                </GPH>
                <P>Because the FBI does not use fingerprints to process standard background checks in the ordinary course, ATF would, were it both legally possible and helpful to applicants, propose wholly eliminating the NFA and GCA regulations requiring applicants to submit fingerprints with Forms 1, 4, 5, 7, 23, and 5630.7 except as needed to resolve NICS background check issues or issues ATF needs to address for GCA license applicants. However, ATF cannot eliminate the requirement for individuals to submit fingerprints up front because fingerprints are currently statutorily required for individual applications under both the NFA and GCA. 26 U.S.C. 5802, 5812(a), and 5822(d). Even though collecting such fingerprints does not assist NICS in processing the background checks of over 97 percent of applicants, ATF cannot modify this statutory requirement by regulation. Moreover, with respect to GCA license applicants, in addition to submitting applicants' fingerprints to coordinate with the FBI to resolve issues that arise during NICS background checks, ATF also uses the fingerprints to respond to and resolve applicants' appeals from license denials. Collecting fingerprints from GCA applicants up front thus often benefits licensees.</P>
                <P>Therefore, regarding NFA making and transferee applications, ATF is instead proposing to reduce the number of fingerprint cards individuals must submit with Forms 1, 4, and 5 from two cards to one (Form 5630.7 already requires only one card). In addition, ATF is proposing to word the regulatory requirement for individuals to submit fingerprints as a reference to the statutory requirement, so that if that requirement is removed from the statute in the future, the regulations will align. Further, ATF is proposing to eliminate the requirement that RPs for a trust or other legal entity applying to make or transfer an NFA firearm submit their fingerprints with Form 23. Instead, such persons would be required to submit fingerprint cards only upon request by ATF, if necessary to efficiently complete a background check.</P>
                <P>Additionally, under this proposed rule, ATF would clarify that all persons required to submit fingerprints would be able to submit one digital fingerprint set if they apply electronically. Due to the advent of new technology, ATF has already shifted to accepting digital fingerprints, and a majority of the industry currently submits digital fingerprints with NFA applications. Finally, ATF proposes to remove language requiring that fingerprints be taken by someone specifically trained to take them because it is no longer applicable. Under this rule, individuals could take and submit their own fingerprints using FBI Form FD-258 or digital fingerprinting equipment, provided the fingerprints are clear enough to be accurately identified.</P>
                <P>To effectuate the proposed changes discussed above, ATF is proposing a new stand-alone § 479.27. This would allow all the NFA fingerprint requirements to be in one place, with cross-references elsewhere as appropriate, and would avoid unnecessarily duplicating requirements in multiple places. The new § 479.27 would be added under subpart C, Administrative and Miscellaneous Provisions, to clarify that NFA applicants and SOT taxpayers must submit fingerprint cards (and photographs) only when the statute specifically requires or, when not required by statute, upon the request of the Director as needed to efficiently conduct certain background checks. The new section would also provide that, when required or requested, persons would submit only one set of fingerprints, whether digital or on a paper card. ATF also proposes conforming changes to 27 CFR 479.34(e), 479.63, and 479.85.</P>
                <P>For GCA license applicants, as discussed above, ATF uses fingerprints to resolve appeals from license denials in addition to submitting the fingerprints to NICS. As a result, ATF is not proposing to make any changes to the current regulatory requirements for all GCA license applicants (including RPs) to submit one set of fingerprints with their initial applications. In addition, under the proposed rule ATF would continue its existing practice of not requiring GCA applicants to resubmit their fingerprints when they complete a renewal application or other document.</P>
                <HD SOURCE="HD2">B. Photographs</HD>
                <P>
                    As noted in section II.A of this preamble, FBI regulations on NICS 
                    <PRTPAGE P="40928"/>
                    require the following descriptors to query NICS: (1) name; (2) sex; (3) race; (4) complete date of birth; and (5) residence state. 28 CFR 25.7. As with fingerprints, none of these descriptors require a photograph. Nevertheless, the photograph's utility is in verifying an individual's identity as part of GCA and NFA application processes.
                </P>
                <P>Due to technological developments since ATF prescribed the 2″ × 2″ photograph requirements for GCA and NFA individuals and RPs, copies, scans, or similar reproductions of a photo identification document are now able to be just as clear and viable as original documents. As a result, ATF is proposing to include an option for applicants to submit a copy of a photo identification document to satisfy the statutory photograph requirements, in place of a stand-alone 2″ × 2″ passport-type photograph.</P>
                <P>In many cases, making a copy, scan, etc., of a photo identification document is easier, faster, and less burdensome and costly than taking a passport-type photograph. It does not decrease public safety because, in addition to including a picture of the individual, the photo identification document helps confirm the individual's name and, usually, the individual's address. This information aids in verifying an individual's identity more than just a stand-alone 2″ × 2″ photograph. Photo identification documents also confirm the information submitted on the NFA and GCA applications. Furthermore, Congress already mandates that federal firearms licensees (“FFLs”) collect photo identification documents to verify identity as part of the Brady Handgun Violence Prevention Act's background check process, so this would be consistent with that requirement as well. 18 U.S.C. 922(t)(1)(D).</P>
                <P>For these reasons, and in an effort to reduce public burden while maintaining a process to verify an applicant's identity, ATF is proposing an alternative to the requirement that individuals submitting Forms 1, 4, 5, 7, or 5630.7; NFA RPs submitting Form 23; and GCA RPs submitting only Form 7, part B, must submit a 2″ × 2″ passport-type photograph. ATF proposes to allow all individual applicants and RPs to submit a clear electronic or physical copy (such as a photocopy, a scanned copy, a digital image, etc.) of a valid photo identification document, as defined in 27 CFR 478.11, instead of requiring only a 2″ × 2″ passport-type photograph (which will remain an option for those who prefer). However, under the proposed new rule, ATF would still be able to request a passport-type photograph if needed to efficiently verify identity or complete a background check.</P>
                <P>
                    To effectuate these proposed changes for NFA applicants, the proposed new § 479.27 would state that, when part 479 requires individuals or RPs to submit a photograph, they may attach either a copy of their photo identification document, as defined in 27 CFR 478.11, or a 2″ × 2″ photograph, as currently required. However, the new section would also clarify that, even if individuals submit a copy of their photo identification as permitted, the Director may nonetheless require a 2″ × 2″ photograph, as necessary. ATF also proposes conforming changes to 27 CFR 479.34(e), 479.63, and 479.85.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         ATF also notes that other, non-conflicting changes are being proposed to §§ 479.63(a) and 479.85(a) in a separate proposed rule addressing spouses jointly applying to make or receive and register an NFA firearm. Such spouses would be akin to RPs for the fingerprint and photograph requirements in this proposed rule.
                    </P>
                </FTNT>
                <P>To effectuate this rule's proposed photograph changes for GCA applicants, ATF proposes to amend § 478.44(a)(1)(ii) to require individuals or RPs to submit a copy of their photo identification document, as defined in 27 CFR 478.11, or a 2″ × 2″ photograph, as currently required. This paragraph would also clarify that, even if individuals submit a copy of their photo identification as permitted, the Director may nonetheless require a 2″ × 2″ photograph, as necessary.</P>
                <P>Table 2 shows the changes the rule proposes for each group's fingerprints and photograph requirements.</P>
                <GPH SPAN="3" DEEP="179">
                    <GID>EP06JY26.008</GID>
                </GPH>
                <HD SOURCE="HD1">III. Statutory and Executive Order Review</HD>
                <HD SOURCE="HD2">A. Executive Orders 12866 and 13563</HD>
                <P>Executive Order 12866 (Regulatory Planning and Review) directs agencies to assess the costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits.</P>
                <P>Executive Order 13563 (Improving Regulation and Regulatory Review) emphasizes the importance of agencies quantifying both costs and benefits, reducing costs, harmonizing rules, and promoting public flexibility.</P>
                <P>
                    The Office of Management and Budget (“OMB”) has determined that this rule would be a “significant regulatory action” under section 3(f) of Executive Order 12866, but that it is not a section 3(f)(1) significant action because it 
                    <PRTPAGE P="40929"/>
                    would not have an impact of $100 million or more in any one year. Accordingly, this rule has been submitted to OMB for review. This proposed rule would remove the requirement for entity RPs submitting Forms 1, 4, or 5 to submit fingerprints with their Forms 23 and would allow them to instead submit fingerprints only at ATF's request, if needed to complete a background check. It would also reduce the number of fingerprint cards individuals must submit with Forms 1, 4, and 5 from two cards to one (Form 5630.7 already requires only one card). In addition, it would allow individual applicants using Forms 1, 4, 5, 7, or 5630.7, and RPs using Forms 23 or Forms 7/stand-alone Forms 7, part B, the option of submitting a copy of a photo identification document instead of a 2″ × 2″ photograph.
                </P>
                <P>Because this proposed rulemaking would be a “significant regulatory action” under Executive Order 12866, ATF has laid out the impacts of this proposed rulemaking in OMB's A-4 accounting statement in Table 3. Table 3 also illustrates the range of future estimates in a low, primary, and high range, as ATF's Circular A-4 sensitivity analysis. ATF then provides its normal regulatory cost-benefit analysis below the table.</P>
                <BILCOD>BILLING CODE 4410-FY-P</BILCOD>
                <GPH SPAN="3" DEEP="284">
                    <GID>EP06JY26.009</GID>
                </GPH>
                <BILCOD>BILLING CODE 4410-FY-C</BILCOD>
                <P>ATF has been permitting NFA applicants to submit Forms 1, 4, and 5 electronically via its online eForms platform for several years, which has included accepting digital fingerprints and photographs as that technology has developed. As a result, this cost-benefit analysis incorporates those existing industry standards as part of its assumptions when determining costs and benefits. Because NFA applicants have been able to submit electronically through email and then eForms for several years, almost 100 percent of these applicants submit electronically. Analysts in the National Firearms Act Division estimate that only two percent of NFA applicants currently submit paper documents. As a result, for purposes of this analysis, ATF incorporates this existing industry practice: that 98 percent of NFA applicants are submitting digital documents electronically and two percent are submitting paper documents by mail.</P>
                <P>Although ATF has also been permitting GCA applicants to submit Forms 7 electronically during the past few years via downloadable and fillable PDF forms submitted by email, accompanied by digital fingerprints and photographs, currently almost all GCA applicants submit paper documents by mail. However, ATF anticipates that, like NFA paper applications, GCA paper applications will decrease in the next few years, especially as ATF stops printing and distributing paper forms over the course of this year and moves GCA application forms to the eForms platform—which is more convenient than email submission. ATF has not been tracking the number of GCA applications submitted by email versus mail, but Federal Firearms Licensing Center analysts estimate that a very small percent of GCA applicants currently submit electronically. Therefore, for purposes of this analysis, ATF uses the same two percent assumption for GCA electronic submissions that applies to NFA paper ones, as the best available proxy. As a result, for this analysis, ATF incorporates this existing industry practice: that 98 percent of GCA applicants are submitting paper documents by mail and two percent are submitting digital documents electronically.</P>
                <HD SOURCE="HD3">1. Need Statement</HD>
                <P>
                    This proposed rule is necessary to reduce burdens for persons applying to make or obtain an NFA firearm or to obtain an FFL license under the GCA. It also updates the regulations to incorporate methods of meeting the statutory requirements with current technology. This proposed rule would 
                    <PRTPAGE P="40930"/>
                    codify in ATF regulations the existing industry practice whereby applicants can submit digital fingerprints and photographs to ATF. Furthermore, as to NFA applications using Forms 1, 4, 5, and 23, this proposed rule would also reduce or, in the case of RPs, rescind, the fingerprint requirements, unless ATF subsequently requests prints because they are needed to facilitate a given background check. Finally, the proposed rule would provide all applicants the option to submit a copy of their photo identification instead of a passport-type photograph. Overall, this rule would lessen regulatory burdens and provide savings to the public without impacting public safety.
                </P>
                <HD SOURCE="HD3">2. Benefits, Including Cost Savings</HD>
                <P>This proposed rule would result in benefits to the public in the form of cost savings because segments of the covered population would no longer need to obtain fingerprints or would obtain a reduced number, and segments of the population would no longer have to obtain photographs from vendors. NFA individual applicants and GCA individual/RP applicants who submit electronically would still obtain digital fingerprints and photographs as they do now, though they would have the additional convenience of submitting a digital copy of their photo identification instead. Individual NFA applicants who still submit paper applications would need to obtain only one fingerprint card instead of two, and would also have the option of submitting a copy of their photo identification instead of obtaining a photograph. NFA RPs, whether submitting electronically or on paper, would no longer have to submit fingerprints with their Forms 23 (although a subset might later need to submit fingerprints if ATF requests them so FBI can resolve a background check). Like GCA individuals/RPs, NFA RPs would also have the convenience of submitting a copy of their photo identification instead of obtaining a photograph, but only those applicants who submit paper documents would accrue a cost savings from this change.</P>
                <HD SOURCE="HD3">Population</HD>
                <P>To determine the population segments that would be affected by this proposed rule's provisions over the next ten years, ATF used data on the number of applications submitted historically by individuals and RPs under both the NFA and GCA to establish a baseline annual average growth rate for each group. ATF then used forecasting software to apply that annual average growth rate to future years, resulting in the projected number of future applications.</P>
                <P>For purposes of determining savings for NFA applicants, ATF used data on the number of NFA applications submitted over eight years, from 2017 to 2025. Table 4 shows the historical data on the size of the NFA applicant pool.</P>
                <GPH SPAN="3" DEEP="231">
                    <GID>EP06JY26.011</GID>
                </GPH>
                <P>In Table 5, ATF forecasts the annual number of NFA applications that individuals (Forms 1, 4, 5, and 5630.7) and RPs (Forms 23) would collectively submit over the next ten years. In addition, the table breaks out the number of individuals and RPs who would submit NFA applications in paper form and the number of NFA RPs who would submit documents electronically. We have not included a column for the number of NFA individual applicants who would submit electronically as they would not be impacted by the changes proposed in this rule. As noted above, approximately two percent of individuals and RPs currently still submit paper NFA applications. Table 5 uses this estimated percentage and the number of NFA individual and RP applications from Table 4 to calculate the annual number of paper and electronic applications for the relevant applicant categories.</P>
                <GPH SPAN="3" DEEP="289">
                    <PRTPAGE P="40931"/>
                    <GID>EP06JY26.012</GID>
                </GPH>
                <P>For the number of GCA applicants, ATF also used historical data from 2017 to 2025. ATF did not break out individual GCA applicants from other GCA RP applicants as it did for NFA applicants in Tables 4 and 5, because both GCA individuals and other RPs would realize the same benefits from this proposed rule. Table 6 shows the historical GCA data.</P>
                <GPH SPAN="3" DEEP="259">
                    <GID>EP06JY26.013</GID>
                </GPH>
                <P>
                    In Table 7, ATF forecasts the total annual number of GCA license applications (Forms 7 and attached Forms 7, part B, collectively) that individuals and other RPs would submit over the next ten years. In addition, the table breaks out the number of individuals/RPs who would submit GCA applications on paper. As noted 
                    <PRTPAGE P="40932"/>
                    above, ATF is using a proxy of two percent of individuals/RPs to estimate the number who currently submit GCA applications electronically. However, based on ATF's experience with permitting email submissions, we anticipate a moderate growth rate for emailed GCA applications during the first two years and thus, a corresponding decrease in paper submissions: we estimate in year one, 98 percent of applicants will submit paper documents; and in year two, 88 percent. Further, based on our experience with NFA forms that previously were made available on the eForms platform, ATF also anticipates that, once the GCA forms are on eForms (one to two years from now, so we use two years to be conservative), there will be a more significant growth rate for electronically submitted GCA applications during the following two years, and thus, a corresponding decrease in paper submissions. Specifically, we estimate in year three, 50 percent of applicants will submit paper documents; and in year four onward, 2 percent. Table 7 uses the number of GCA individual/RP applications from Table 6 to forecast the annual future number of paper GCA individual/RP applications.
                </P>
                <GPH SPAN="3" DEEP="264">
                    <GID>EP06JY26.014</GID>
                </GPH>
                <HD SOURCE="HD3">Fingerprint Cost Savings</HD>
                <P>
                    ATF is proposing to reduce the number of fingerprint cards NFA individual applicants must submit with Forms 1, 4, and 5 from two cards to one (Form 5630.7 submissions, like GCA individual and RP applications, already require only one card, so this change would not affect these applicants). Under the proposed rule, individual NFA applicants would still have to submit fingerprints with their application, but only one set. Because those who submit electronically already obtain and submit just one set of fingerprints, they would not accrue savings from this change. While the majority of NFA individual applicants submit their forms electronically, approximately two percent continue to submit via paper. As a result, that two percent would be affected by this proposed change. ATF estimates that the cost to obtain two sets of paper fingerprints is $50.
                    <SU>9</SU>
                    <FTREF/>
                     By reducing the number of paper cards NFA individual applicants who submit by mail would have to obtain, the proposed rule would reduce their fingerprint cost from $50 to $32,
                    <SU>10</SU>
                    <FTREF/>
                     resulting in a per-application savings of $18 for this two percent of applicants.
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         The average of $50 for two sets of paper fingerprint cards is derived from reviewing various internet sources. 
                        <E T="03">See, e.g.,</E>
                         ABC Fingerprinting Service, 
                        <E T="03">https://www.abcfingerprinting.com/</E>
                         [
                        <E T="03">https://perma.cc/FM7D-H4EK</E>
                        ]; Absolute Fingerprinting and Security Services, 
                        <E T="03">https://absoluteisi.com/fingerprinting/</E>
                         [
                        <E T="03">https://perma.cc/FJ6T-4X3U</E>
                        ]; Bayou City Fingerprinting, 
                        <E T="03">https://bayoucityfingerprinting.com/ink-fingerprinting/</E>
                         [
                        <E T="03">https://perma.cc/8TME-8EW7</E>
                        ].
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         Based on a review of sources available on various websites, most fingerprinting services provide a discount for the second set of fingerprints. 
                        <E T="03">See, e.g., https://absoluteisi.com/fingerprinting/</E>
                         [
                        <E T="03">https://perma.cc/E6GU-Y3YS</E>
                        ], 
                        <E T="03">https://fingerprinting-nm.com/pricing-hours</E>
                         [
                        <E T="03">https://perma.cc/PTT9-FJ3L</E>
                        ], 
                        <E T="03">https://www.fingerprint-phila.com/</E>
                         [
                        <E T="03">https://perma.cc/8JQA-PC7G</E>
                        ], 
                        <E T="03">https://txfingerprints.com/services/ink-fingerprinting/</E>
                         [
                        <E T="03">https://perma.cc/5HUA-SZE8</E>
                        ], 
                        <E T="03">https://www.wovois.com/colorado-fingerprinting-services</E>
                         [
                        <E T="03">https://perma.cc/GK5V-8H77</E>
                        ]. As a result, the reduced cost cited here is not half of the cost of two cards.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See</E>
                         US Postal Service, 
                        <E T="03">https://ips.usps.com/IdentityCapture/</E>
                         [
                        <E T="03">https://perma.cc/F9F3-5LV2</E>
                        ]; Passport Immigrant Photos, 
                        <E T="03">https://www.passportimmigrationphotos.com/atf-fingerprinting</E>
                         [
                        <E T="03">https://perma.cc/J28Z-Z5F6</E>
                        ]; Royal Printing, 
                        <E T="03">https://www.royalprinting123.com/fingerprinting.html</E>
                         [
                        <E T="03">https://perma.cc/LWM3-RMRW</E>
                        ]; Greater Houston Fingerprinting, 
                        <E T="03">https://square.site/book/QEHCT4XRC4G98/zarco-llc-pearland-tx</E>
                         [
                        <E T="03">https://perma.cc/GTG7-DJA5</E>
                        ].
                    </P>
                </FTNT>
                <P>
                    ATF is also proposing to eliminate the requirement for NFA RPs to submit fingerprints with their applications. Currently, NFA RP applicants are required to submit two sets of fingerprints with their Forms 23, although 98 percent of them submit digital fingerprints and thus submit just one digital set. Digital fingerprints cost $73 on average.
                    <SU>11</SU>
                     For the remaining two percent of NFA RPs, the cost of obtaining two sets of paper fingerprints is $50. As NFA RPs would no longer have to submit fingerprints with their 
                    <PRTPAGE P="40933"/>
                    Forms 23,
                    <SU>12</SU>
                    <FTREF/>
                     the proposed change would result in savings to RPs of up to $50 or $73 in capital costs per application, depending on whether they submit by mail or electronically. In addition, NFA RPs would save the time involved in obtaining fingerprints. However, a small number of NFA RPs would still need to submit a fingerprint set later, as requested by ATF, to coordinate with the FBI on resolving criminal history-related issues that can arise, for example, when an NFA applicant's biographic information matches that of another individual (see section 3, Savings offset, below for details).
                    <SU>13</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         Although individual applicants to make or transfer an NFA firearm are also RPs if they are licensees, they are still required to submit fingerprints as individuals with their Forms 1 or 4. That requirement would continue under the proposed rule.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         Although GCA applicants also incur a cost for obtaining fingerprints, ATF is not including that cost here because this rule would not affect the GCA fingerprint requirements. In addition, as discussed in the note to Table 1, Form 5 is not included in this analysis because the majority of Form 5 applications are transfers to the government, which does not have RPs. ATF does not have data on the number of Form 5 transfers that involve RPs, but it is a very small proportion of the total. Form 5630.7 is also not included because, although it would be submitted to ATF with a photograph and fingerprints if an individual applicant were not already licensed under the GCA (Form 7), in reality, there are no NFA 5630.7 applications from applicants who are not already licensed. As a result, applicants would already have had background checks during the licensing process, so there are no individual applicants submitting Forms 5630.7.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Photograph Cost Savings</HD>
                <P>ATF is also proposing that NFA and GCA individual and RP applicants would no longer have to submit 2″ × 2″ photographs with their applications. They would instead have a new option to submit a scan or copy of their photo identification document. Applicants who already submit electronically would not accrue a cost savings from this option, as they are already able to submit a self-generated digital photo instead of obtaining one by another means, but the proposed rule would provide them the convenience of scanning their photo ID if they preferred. Applicants who submit paper documents would save the cost of obtaining a paper photograph and the time spent doing so.</P>
                <P>
                    ATF estimates the average cost to obtain one photograph at up to $17.
                    <SU>14</SU>
                    <FTREF/>
                     Therefore, NFA and GCA individual and RP applicants who submit paper photographs could realize a capital savings of $17 per application if they choose to copy their photo identification instead.
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">See</E>
                         CVS passport photograph costs, 
                        <E T="03">https://www.cvs.com/photo/passport-photos</E>
                         [
                        <E T="03">https://perma.cc/8WQ4-7TPA</E>
                        ]; Walgreens passport photograph costs, 
                        <E T="03">https://photo.walgreens.com/store/passport-photos</E>
                         [
                        <E T="03">https://perma.cc/3CDM-5NKX</E>
                        ].
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Monetized Time Cost Savings</HD>
                <P>In addition to the costs of fingerprints, NFA RPs also incur a time cost to acquire fingerprints. NFA RPs acquiring fingerprints would likely be performing such actions during their leisure time because, if they are applying to make or purchase a firearm, it is most likely for personal use or as part of a personal trust, rather than as part of a business transaction. Therefore, ATF has estimated a leisure wage rate for NFA applicants in this proposed rule.</P>
                <P>
                    ATF estimated the leisure wage based on methodology from the Department of Health and Human Services (“HHS”), updated to account for the latest available data.
                    <SU>15</SU>
                    <FTREF/>
                     The HHS methodology is to first obtain the median U.S. non-leisure weekly wage from the Bureau of Labor Statistics (“BLS”) and divide it by 40 hours to derive the median hourly non-leisure wage. Step two is to obtain the average U.S. real household income before taxes and after taxes from the Census Bureau and divide the post-tax income by the pre-tax income to determine the net household income rate. Step three applies the net income rate to the median non-leisure hourly rate derived in step one, to calculate the hourly leisure wage. Table 8 shows the steps and data ATF used under this methodology to determine an updated leisure wage.
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">See Valuing Time in U.S. Department of Health and Human Services Regulatory Impact Analyses: Conceptual Framework and Best Practices, https://aspe.hhs.gov/sites/default/files/private/pdf/257746/VOT.pdf.</E>
                    </P>
                </FTNT>
                <GPH SPAN="3" DEEP="446">
                    <PRTPAGE P="40934"/>
                    <GID>EP06JY26.015</GID>
                </GPH>
                <P>Based on the methodology outlined by HHS, the estimated leisure wage is $26, which ATF used to calculate the hourly savings for NFA applicants. This leisure wage—the opportunity cost of leisure, meaning the time spent engaging in activities that could otherwise be spent earning income—is the product of multiplying the median hourly wage of $30.35 by the 0.86 net household income rate to derive the after tax median hourly wage ($26.10, rounded to $26). For NFA applicants, ATF used this hourly leisure wage rate to calculate the monetized time savings for all NFA RPs who would no longer obtain fingerprints and to calculate the monetized time savings for NFA individuals and RPs submitting paper applications who would no longer obtain paper photographs.</P>
                <P>
                    For GCA license applicants, who would be applying as part of their firearms business activities, ATF used the BLS hourly wage for a facilities manager of $53.42 per hour as an analogue for the hourly wage of an FFL manager.
                    <SU>16</SU>
                    <FTREF/>
                     To account for fringe employment benefits such as insurance, ATF determined an average load rate based on BLS's calculated national hourly compensation (salaries/wages plus paid benefits) for all private-sector occupations (an average of $44.20 for 2024) 
                    <SU>17</SU>
                    <FTREF/>
                     divided by the national average hourly wages and salaries without benefits (an average of $31.10 for 2024),
                    <SU>18</SU>
                    <FTREF/>
                     making a load rate of 1.42.
                    <SU>19</SU>
                    <FTREF/>
                     ATF then applied this load rate to the estimated hourly wage rate for an FFL manager to calculate their total compensation. Multiplying BLS's estimated hourly wage rate equivalent for an FFL manager ($53.42) by the load rate of 1.42, ATF estimated that an FFL would save $75.86, rounded to $76, in loaded monetized time per hour under this rule.
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         U.S. Bureau of Labor Statistics, 
                        <E T="03">Occupational Employment and Wages, May 2023,</E>
                         for 11-3013 Facilities Managers, 
                        <E T="03">https://www.bls.gov/oes/2023/may/oes_nat.htm</E>
                         [
                        <E T="03">https://perma.cc/3NNK-QH53</E>
                        ].
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         U.S. Bureau of Labor Statistics, 
                        <E T="03">Total compensation cost per hour worked for private industry workers (2023-2025), https://data.bls.gov/dataViewer/view/timeseries/CMU2010000000000D</E>
                         [
                        <E T="03">https://perma.cc/T2ZL-2UUB</E>
                        ].
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         U.S. Bureau of Labor Statistics, 
                        <E T="03">Employer cost for employee compensation, (2023-2025), https://data.bls.gov/dataViewer/view/timeseries/CMU2020000000000D</E>
                         [
                        <E T="03">https://perma.cc/8WEJ-2TRW</E>
                        ].
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         1.42 load rate = $44.20 total hourly compensation/$31.10 hourly wages and salaries.
                    </P>
                </FTNT>
                <PRTPAGE P="40935"/>
                <P>For purposes of this analysis, ATF estimates that it takes a person 15 minutes (0.25 hours) to obtain a photograph and one hour to obtain fingerprints, for a total potential time savings of up to 0.25 hours for GCA individual/RP applicants and NFA individual applicants who submit paper applications and would no longer have to obtain paper 2″ × 2″ photographs; up to one hour for NFA RP applicants who submit electronically and would no longer have to obtain digital fingerprints; and up to 1.25 hours for NFA RP applicants who submit paper applications and would no longer have to obtain paper 2″ × 2″ photographs or fingerprints. ATF uses the 0.25-hour time estimate for obtaining photographs because photographs are readily available at common retailers such as CVS and Walgreens. ATF estimates a longer time to obtain fingerprints because fingerprints are not as readily available.</P>
                <HD SOURCE="HD3">Combined Cost Savings</HD>
                <P>For GCA applicants who submit by paper, the combined savings would be the cost savings of no longer obtaining a 2″ × 2″ photograph ($17) and the monetized value of the time they would no longer have to spend obtaining the photograph. The monetized time savings would be $76 loaded hourly wage rate * 0.25 hours, or $19. The total savings for these GCA applicants would therefore be $36 per application (rounded). GCA applicants who submit electronically would not realize any savings as a result of this proposed rule.</P>
                <P>For NFA individuals, the two percent who submit paper documents would have a combined (rounded) savings of $42, which is the cost savings of submitting one fingerprint card instead of two ($18), the cost savings of no longer obtaining a 2″ × 2″ photograph ($17), and the monetized value of the time they would no longer have to spend obtaining the photograph ($7). For NFA RPs, the combined (rounded) savings would be $100 for RPs who submit paper documents or $99 for RPs who submit electronically. This consists of the cost savings from no longer obtaining fingerprints ($50 or $73, for paper or digital prints respectively), the monetized value of the time they would no longer have to spend obtaining fingerprints ($26, one hour's monetized value), and, for NFA RPs who submit paper applications, the cost savings of no longer obtaining a 2″ × 2″ photograph ($17), and the monetized value of the time they would no longer have to spend obtaining the photograph ($7, or $26 * 0.25 hours, rounded). Table 9 illustrates the per applicant cost savings per activity.</P>
                <GPH SPAN="3" DEEP="192">
                    <GID>EP06JY26.031</GID>
                </GPH>
                <P>Based on the anticipated number of applications from NFA individuals and RPs and GCA individuals/RPs over the next ten years, as well as the numbers of paper and electronic submissions (see Tables 5 and 7), ATF forecasts the cost savings over ten years in Table 10.</P>
                <GPH SPAN="3" DEEP="273">
                    <PRTPAGE P="40936"/>
                    <GID>EP06JY26.032</GID>
                </GPH>
                <HD SOURCE="HD3">3. Cost Savings Offset</HD>
                <P>Although the proposed rule would result in deregulatory cost savings regarding fingerprints for NFA RPs, there would still be instances in which ATF would request that an NFA RP submit fingerprints during the NICS background check. That could happen because of a need to resolve confusion about the RP's identity or criminal history, or for other similar reasons. Should ATF request fingerprints as a supplement to the standard background check, a sub-portion of the above cost savings for NFA RPs would be offset by the $73 fee to obtain digital fingerprints or the $50 fee to obtain paper prints, plus the opportunity cost of time to obtain fingerprints ($26 hourly leisure wage * 1 hour, or $26), resulting in a total fingerprint cost savings offset of $99 ($26 monetized time + $73 fee) per application for this subset of NFA RPs who submit electronically and $76 ($26 monetized time + $50 fee) per application for this subset of NFA RPs who submit paper applications.</P>
                <P>
                    Although ATF has historical data on the numbers of NFA individual and RP applications submitted to ATF with fingerprints (
                    <E T="03">see</E>
                     Table 4) and on the total number of NFA fingerprint sets sent from ATF to NICS as requested by NICS since 2022 (
                    <E T="03">see</E>
                     Table 1), ATF does not have data on the subset number of NFA RP fingerprint sets sent to NICS upon request. Therefore, to calculate a baseline historical estimate of that number, ATF started with the historical data on NFA applications from Tables 1 and 4. ATF relied specifically on the Table 1 and 4 data from 2022-2025, which is the period during which ATF has been submitting fingerprints to NICS solely upon request.
                </P>
                <P>ATF added the number of NFA individual applications and the number of NFA RP applications submitted to ATF in each of those years (from Table 4) to obtain the total number of NFA applications submitted in each of those years. Then, ATF used the number of NFA fingerprints sent to NICS upon request in each of those years (from Table 1, column 2) to calculate the percentage of NFA fingerprints submitted to NICS from the total submitted to ATF. ATF then used this percentage as a basis for estimating the number of NFA RP fingerprints that would have been submitted to NICS each year, on the assumption that RPs' fingerprints were requested in the same proportion as individuals' fingerprints. Table 11 shows the historical total number of NFA fingerprint sets; the historical number of NFA fingerprints sent to NICS; the percentage of the total represented by that number; and the estimated number of fingerprints submitted to NICS that were for RPs.</P>
                <GPH SPAN="3" DEEP="200">
                    <PRTPAGE P="40937"/>
                    <GID>EP06JY26.016</GID>
                </GPH>
                <P>Had this proposed rule been in effect from 2022-2025, the subset of NFA RPs whose fingerprints were requested by NICS in those years would have incurred the cost savings offset for providing fingerprints later upon request.</P>
                <P>To forecast the cost savings offset for the equivalent subset of NFA RPs who would continue to provide fingerprints by request under this proposed rule over the next ten years, ATF used the estimated number of NFA RP prints sent to NICS in 2022-2025 to establish a baseline annual average growth rate. ATF then used forecasting software to apply that annual average growth rate to future years, resulting in the projected subset of NFA RP fingerprints that would have to be submitted. Then, from the numbers forecasted for each year, ATF used the percentages discussed under the population section of the benefits analysis to calculate the portion of those future applicants who would submit paper documents versus digital ones. ATF provides the ten-year population cost savings offset numbers in Table 12 for the subset of RPs who would incur this continued fingerprinting cost under the proposed rule.</P>
                <GPH SPAN="3" DEEP="228">
                    <GID>EP06JY26.017</GID>
                </GPH>
                <P>
                    Finally, ATF multiplied the number of RPs who would submit paper prints by the $76 fingerprint cost savings offset per applicant, and multiplied the number of RPs who would submit digital prints by the $99 fingerprint cost savings offset per applicant, to determine the total cost savings offset for this group of NFA RPs. ATF provides a ten-year cost savings offset analysis in Table 13 for the subset of RPs who would incur this continued fingerprinting cost under the proposed rule (
                    <E T="03">i.e.,</E>
                     who would not receive the $76 or $99 cost savings that other NFA RPs would receive from no longer submitting any fingerprints).
                </P>
                <GPH SPAN="3" DEEP="325">
                    <PRTPAGE P="40938"/>
                    <GID>EP06JY26.018</GID>
                </GPH>
                <HD SOURCE="HD3">4. Total Net Cost Savings</HD>
                <P>Overall, this rule would create net cost savings for the public. To illustrate the net cost savings to the public, Table 14 provides a cost-savings and cost-savings-offset comparison over the ten-year period of analysis, as well as the resulting net outcome of subtracting the cost savings offset from the cost savings.</P>
                <GPH SPAN="3" DEEP="220">
                    <GID>EP06JY26.019</GID>
                </GPH>
                <P>Table 15 provides the overall net cost savings due to this proposed rule, accounting for the cost savings and cost savings offset described in the sections above.</P>
                <GPH SPAN="3" DEEP="290">
                    <PRTPAGE P="40939"/>
                    <GID>EP06JY26.020</GID>
                </GPH>
                <P>Overall, ATF anticipates that this rule would provide a cost savings of an undiscounted $646.9 million over the course of ten years, or an annualized $63.7 million at 3 percent and $62.4 million at 7 percent.</P>
                <HD SOURCE="HD3">5. Regulatory Alternatives</HD>
                <HD SOURCE="HD3">Alternative 1: Status-Quo Alternative</HD>
                <P>ATF considered taking no action and maintaining the status quo. The regulations require individuals and RPs to submit two paper fingerprint cards and a 2″ × 2″ photograph for each NFA application to make or transfer, and one paper fingerprint card and a 2″ × 2″ photograph for each NFA SOT taxpayer application and GCA license application. While ATF has already been permitting electronic submissions for both NFA and GCA applicants, ATF determined that the fingerprint requirement is still unduly burdensome in many cases because fingerprints are no longer useful in processing the vast majority of applications. At minimum, two sets of fingerprints are no longer necessary, and, due to technological advancements, a passport-style photograph is no longer the only, or even best, way to verify a person's identity.</P>
                <P>In addition, ATF also recognizes that new technologies have changed the options for obtaining fingerprints, such that paper fingerprint cards should no longer be the only allowable format in the regulations. While the costs for obtaining digital fingerprints are currently higher than for obtaining paper fingerprints, that balance is likely to change as the digital options become more common. Similarly, while capturing one's own fingerprints on paper is somewhat difficult and requires obtaining the necessary supplies, and capturing one's own fingerprints digitally is currently cost-prohibitive for many applicants because they would have to purchase equipment, ATF anticipates that capturing one's own fingerprints digitally will soon become accessible and affordable.</P>
                <P>As a result of both considerations, ATF believes that retaining the status quo is not the best alternative.</P>
                <HD SOURCE="HD3">Alternative 2: Eliminating All Fingerprints Alternative</HD>
                <P>Another alternative ATF considered was eliminating the requirement for fingerprints in all cases. This would eliminate cost and time burdens for all applicants and streamline submitting and processing applications. However, due to statutory requirements, that is not possible for individual NFA and GCA applicants. In addition, in some cases, fingerprints are necessary as a means of efficiently coordinating with the FBI to resolve personal-history-related issues when completing a NICS background investigation, and in the context of GCA license applications, ATF also needs the fingerprints to resolve applicant appeals. In those cases, both public safety and the interests of persons wishing to acquire a firearm are better served by requiring fingerprints.</P>
                <HD SOURCE="HD3">Alternative 3: Eliminating All Photographs Alternative</HD>
                <P>ATF also considered the alternative of eliminating the requirement to submit a photograph in all cases. Again, this option would eliminate cost and time burdens for all applicants and streamline submitting and processing applications. However, it is a statutory requirement that individual NFA and GCA applicants must submit photographs. In addition, photographic images are still important for verifying identity, particularly as between persons with the same name. As a result, ATF determined that this was not a viable alternative.</P>
                <HD SOURCE="HD3">Alternative 4: Proposed Alternative</HD>
                <P>
                    Given the constraints discussed above, ATF proposes to partially implement alternative 2 for NFA applicants by proposing that individual NFA applicants would be able to submit one set of fingerprints instead of two, and that NFA RPs would be able to forgo submitting fingerprints with their applications but could be requested to submit fingerprints later if needed in one of these rare cases. This proposed alternative streamlines the application 
                    <PRTPAGE P="40940"/>
                    process. It also reduces burden as much as possible while also ensuring public safety and accounting for the population segments who would still be required by statute to submit fingerprints or would need to submit prints to resolve a background check. The proposed rule also implements existing industry electronic submission practices for applicants across the board, so as to clarify that all applicants required to submit fingerprints may submit digital prints.
                </P>
                <P>ATF also proposes to partially implement alternative 3 by allowing individuals and RPs to submit a copy of their photo identification document instead of a 2″ × 2″ passport-style photograph, if they so elect. People have identification documents in their possession; copies are quick and easy to make and can be done anywhere; and using identification documents benefits public safety because such documents include additional information to verify the person's identity. This alternative thereby reduces burden and facilitates more easily submitting and processing applications. In addition, with technological developments, people can now use a cell phone to take photographs of themselves or make scans of their digital identification, further reducing the photograph requirement's burden.</P>
                <HD SOURCE="HD2">B. Executive Order 14192</HD>
                <P>Executive Order 14192 (Unleashing Prosperity Through Deregulation) requires an agency, unless prohibited by law, to identify at least ten existing regulations to be repealed or revised when the agency publicly proposes for notice and comment or otherwise promulgates a new regulation that qualifies as an Executive Order 14192 regulatory action (defined in OMB Memorandum M-25-20 as a final significant regulatory action under section 3(f) of Executive Order 12866 that imposes total costs greater than zero). In furtherance of this requirement, section 3(c) of Executive Order 14192 requires that any new incremental costs associated with such new regulations must, to the extent permitted by law, also be offset by eliminating existing costs associated with at least ten prior regulations. This rule as proposed is a significant regulatory action as defined by Executive Order 12866; however, this rule would not be an Executive Order 14192 regulatory action because it would not impose total costs greater than zero. It would remove or reduce regulatory requirements pertaining to fingerprints and photographs, saving the public the costs and burdens of complying with them. ATF therefore expects this rule, if finalized as proposed, to qualify as an Executive Order 14192 deregulatory action (defined by OMB Memorandum M-25-20 as a final action that imposes total costs less than zero).</P>
                <HD SOURCE="HD2">C. Executive Order 14294</HD>
                <P>Executive Order 14294 (Fighting Overcriminalization in Federal Regulations) 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 mens rea standard applicable to each element of those offenses. This proposed rule would not create a criminal regulatory offense and is thus exempt from Executive Order 14294 requirements.</P>
                <HD SOURCE="HD2">D. Executive Order 13132</HD>
                <P>This proposed rule would not have substantial direct effects on the states, the relationship between the federal government and the states, or the distribution of power and responsibilities among the various levels of government. Therefore, in accordance with section 6 of Executive Order 13132 (Federalism), the Director has determined that this proposed rule would not impose substantial direct compliance costs on state and local governments, preempt state law, or meaningfully implicate federalism. It thus does not warrant preparing a federalism summary impact statement.</P>
                <HD SOURCE="HD2">E. Executive Order 12988</HD>
                <P>This proposed rule meets the applicable standards set forth in sections 3(a) and 3(b)(2) of Executive Order 12988 (Civil Justice Reform).</P>
                <HD SOURCE="HD2">F. Regulatory Flexibility Act</HD>
                <P>Under the Regulatory Flexibility Act (“RFA”), 5 U.S.C. 601-612, agencies are required to conduct a regulatory flexibility analysis of any proposed rule subject to notice-and-comment rulemaking requirements unless the agency head certifies that the proposed rule would not have a significant economic impact on a substantial number of small entities. Small entities include certain small businesses, small not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of fewer than 50,000.</P>
                <P>ATF performed an initial regulatory flexibility analysis (“IRFA”) of the impacts on small businesses and other entities that would occur due to this proposed rule, if finalized as proposed. Based on the information from this analysis, ATF found—</P>
                <P>
                    • 
                    <E T="03">Direct costs and savings:</E>
                     there would be no direct costs, but there would be some savings to small businesses or entities that make or transfer NFA firearms or engage in business as licensees for GCA firearms. These savings would be $100 or $99 per NFA RP (with a savings offset of $76 or $99, respectively, for less than 1 percent of these NFA RPs who would need to provide fingerprints later upon request due to an irregularity in their background check) and $36 per GCA license applicant (assuming they submit a paper application). No adverse impact would accrue since these would be deregulatory savings that ATF considers beneficial to the small businesses.
                </P>
                <P>
                    • 
                    <E T="03">Indirect costs:</E>
                     an unknown number of businesses that deal in 2″ × 2″ photographs might incur an indirect cost in the form of potential unknown revenue reduction because individuals and RPs might no longer purchase paper 2″ × 2″ photographs. ATF estimates that a reduction in revenue would be $17 per 2″ × 2″ photograph. Assuming a low business revenue of $100,000 per year, a small business would need to lose 5,882 customers in a given year to realize a 1 percent reduction in revenue.
                </P>
                <P>
                    • 
                    <E T="03">Indirect costs:</E>
                     an unknown number of businesses that provide fingerprint services might incur an indirect cost in the form of potential unknown revenue reduction because NFA RPs would no longer purchase fingerprints, and individual NFA applicants submitting paper applications would purchase only one fingerprint card as opposed to two. The extent to which this would produce a net change in revenue for fingerprinting businesses is unknown since people also utilize fingerprinting services for other purposes, like job applications, childcare services, and more. The potential impact to fingerprinting businesses is thus unknown as well.
                </P>
                <HD SOURCE="HD3">Initial Regulatory Flexibility Analysis (IRFA)</HD>
                <P>
                    The RFA establishes “as a principle of regulatory issuance that agencies shall endeavor, consistent with the objectives of the rule and of applicable statutes, to fit regulatory and informational requirements to the scale of the businesses, organizations, and governmental jurisdictions subject to regulation. To achieve this principle, agencies are required to solicit and consider flexible regulatory proposals and to explain the rationale for their actions to ensure that such proposals are given serious consideration.” Public 
                    <PRTPAGE P="40941"/>
                    Law 96-354, sec. 2(b), 94 Stat. 1164 (1980).
                </P>
                <P>Under the RFA, the agency is required to consider whether the proposed rule would have a significant economic impact on a substantial number of small entities. Agencies must perform a review to determine whether the proposed rule would have such an impact. If the agency determines that it would, the agency must prepare an IRFA (or a regulatory flexibility analysis for a final rule) as described in the RFA.</P>
                <P>1. Describing the reasons why the agency is considering taking action.</P>
                <P>This proposed rule would reduce burdens and costs to small businesses that are comprised of one individual, as well as small businesses that have RPs. ATF does not anticipate this rule creating significant economic costs for small entities, as this rule would have deregulatory savings that would be beneficial to small businesses directly affected by ATF regulations.</P>
                <P>2. Succinctly stating the objectives of, and legal basis for, the proposed rule.</P>
                <P>
                    While Congress mandates that ATF collect adequate identifying information for all GCA license applicants, 
                    <E T="03">see</E>
                     18 U.S.C. 923(a) and (d)(1)(B), and also requires that ATF collect photographs and fingerprints from individual NFA (and GCA) applicants, 
                    <E T="03">see</E>
                     26 U.S.C. 5802, 5812(a), and 5822(d), there is no statutory requirement for entity NFA applicants to submit those materials. Nor is there any statutory requirement under either the GCA or NFA that fingerprints or photographs be submitted in a particular format or number. Accordingly, to minimize burdens to the public, ATF is proposing to eliminate its existing requirement for NFA entity applicants to submit an RP's fingerprints and would request fingerprints only if necessary to complete a background check. ATF is also proposing to reduce the number of required fingerprint sets from two to one for individual applicants who make and transfer NFA firearms, although this change will affect only applicants who submit paper fingerprint cards. Finally, ATF is proposing to adjust the requirements for submitting fingerprints and photographs to permit all GCA and NFA applicants to submit digital fingerprints and photographs, and also to submit copies of photo identification documents instead of 2″ × 2″ passport-type photographs.
                </P>
                <P>The objective of this proposed rulemaking is to reduce the regulatory burden of GCA licensing and NFA firearms ownership on the public by streamlining requirements to track the minimum information needed to comply with safety and statutory requirements while also incorporating advances in technology, such as digital options for fingerprints and photographs.</P>
                <P>3. Describing and, where feasible, estimating the number of small entities to which the proposed rule would apply.</P>
                <P>Even though this proposed rule is not economically significant, its economic impact consists of deregulatory savings, which reduce burdens and costs for the public and do not create additional barriers for small businesses. There are approximately 77,378 FFLs that would potentially benefit from this rule and an unknown number of trusts that would also benefit from this rule. ATF anticipates that most of these FFLs and trusts are small businesses.</P>
                <P>It is possible that there may be other indirect costs to other industries—mainly retail businesses that offer photograph and fingerprinting services. This proposed rulemaking would have an unknown indirect effect on their revenue. There are an unknown number of businesses that deal in 2″ × 2″ photographs. This proposed rule would indirectly cause an unknown reduction in revenue from GCA applicants no longer purchasing 2″ × 2″ photographs. ATF estimates that a reduction in revenue would be $17 per 2″ × 2″ photograph. Assuming a low business revenue of $100,000 a year, a small business would need to lose 5,882 customers in a given year to realize a 1 percent reduction in revenue.</P>
                <P>There are also an unknown number of businesses that deal in fingerprints. This proposed rule would indirectly cause an unknown reduction in their revenue because RPs dealing in NFA firearms would no longer need to purchase fingerprints and individual NFA applicants who obtain paper fingerprint cards would no longer need to purchase two cards. In addition, some applicants might instead choose to take their own digital fingerprints, bypassing fingerprinting services altogether. But ATF considers that option, while available, to be currently unlikely due to both the cost of obtaining equipment for at-home digital printing and the infrequency with which the affected applicant population would need to obtain prints.</P>
                <P>The overall impact to revenue is unknown because fingerprinting services would also continue to be used for background checks for employment purposes and other non-firearms reasons.</P>
                <P>4. Describing the proposed rule's projected reporting, record-keeping, and other compliance requirements, including an estimate of the classes of small entities which would be subject to the requirement and the type of professional skills necessary to prepare the report or record.</P>
                <P>There are no additional requirements or costs being imposed by this proposed rule. This rule would reduce costs and requirements for the public.</P>
                <P>5. Identifying, to the extent practicable, all relevant federal rules which might duplicate, overlap, or conflict with the proposed rule.</P>
                <P>This proposed rule would not duplicate or conflict with other federal rules.</P>
                <P>6. Describing any significant alternatives to the proposed rule which accomplish the stated objectives of applicable statutes and which minimize any significant economic impact the proposed rule might have on small entities</P>
                <P>ATF has considered the alternative of maintaining the status quo with respect to GCA and NFA application requirements. Maintaining the status quo would alleviate the indirect costs to companies providing photograph or fingerprinting services. However, ATF has determined that the direct economic benefits to the public from the proposed rule would significantly outweigh any indirect loss in revenue incurred by small businesses offering photograph or paper fingerprinting services.</P>
                <P>ATF also considered issuing guidance in lieu of rulemaking. ATF rejected issuing guidance instead because the existing requirements are in regulations and guidance would not be able to override the regulatory requirements.</P>
                <HD SOURCE="HD2">G. Unfunded Mandates Reform Act of 1995</HD>
                <P>This proposed rule does not include a federal mandate that might result in the expenditure by state, local, and tribal governments, in the aggregate, or by the private sector, of $100 million or more in any one year, and it would not significantly or uniquely affect small governments. Therefore, ATF has determined that no actions are necessary under the provisions of the Unfunded Mandates Reform Act of 1995.</P>
                <HD SOURCE="HD2">H. Paperwork Reduction Act of 1995</HD>
                <P>
                    Under the Paperwork Reduction Act of 1995 (“PRA”), 44 U.S.C. 3501-3521, agencies are required to submit to OMB, for review and approval, any information collection requirements a rule creates or any impacts it has on existing information collections. An information collection includes any reporting, record-keeping, monitoring, posting, labeling, or other similar actions an agency requires of the public. 
                    <PRTPAGE P="40942"/>
                    <E T="03">See</E>
                     5 CFR 1320.3(c). The proposed revisions in this rule would impact six existing information collections under the PRA.
                </P>
                <P>The six information collections that would be impacted are: (1) OMB control number 1140-0011: Application to Make and Register a Firearm (the title of which is being revised to read “Application to Make and Register NFA Firearm”), which includes ATF Form 5320.1 (“Form 1”); (2) OMB control number 1140-0014: Application for Tax-Paid Transfer and Registration of Firearm (the title of which is being revised to read “Application to Transfer and Register NFA Firearm (Tax-Paid)”), which includes ATF Form 5320.4 (“Form 4”); (3) OMB control number 1140-0015: Application for Tax-Exempt Transfer and Registration of Firearm (the title of which is being revised to read “Application to Transfer and Register NFA Firearm (Tax-Exempt)”), which includes ATF Form 5320.5 (“Form 5”); (4) OMB control number 1140-0107: National Firearms Act (NFA) Responsible Person Questionnaire (the title of which is being revised to read “NFA Responsible Person Questionnaire”), which includes ATF Form 5320.23 (“Form 23”); (5) OMB control number 1140-0090: National Firearms Act (NFA—Special Occupational Taxes (SOT)) (the title of which is being revised to read “NFA Special Tax Registration and Return”), which includes ATF Form 5630.7; and (6) OMB control number 1140-0018: Application for Federal Firearms License, which includes ATF Form 5310.12 (“Form 7”).</P>
                <P>This proposed rule would impact these information collections because it would change the fingerprint and photograph requirements for individuals who fill out Forms 1, 4, and 5, by requiring them to submit only one fingerprint card instead of two, and for individuals completing these forms, Form 5630.7, or Form 7, by allowing them the option to submit digital fingerprints and photographs and a copy of their photo identification document instead of a 2″ × 2″ passport-type photo, thereby potentially reducing cost or burden to such individuals in the future.</P>
                <P>The proposed rule would also impact these information collections because it would eliminate the requirement for RPs who fill out Form 23 to provide fingerprint cards with their form. This would result in savings from their current time burden and costs, although in some cases a small subset of these RPs would have to submit a fingerprint card upon request if necessary for the background check, thereby reducing the overall savings for less than 1 percent of these applicants. In addition, the proposed rule would allow RPs who fill out Form 23 or Form 7, part B, the same option to submit digital fingerprints and photographs and a copy of their photo identification document instead of a 2″ × 2″ passport-type photo, thereby also further reducing cost and burden to such individuals.</P>
                <P>As a result of these changes, the time burden and monetized costs for these collections would be reduced if this proposed rule becomes final. ATF will provide more details about the reduced information collection burdens in any final rule, but section III.A of this preamble provides equivalent details in the context of this proposed rule.</P>
                <HD SOURCE="HD2">I. Congressional Review Act</HD>
                <P>This proposed rule would not be a major rule as defined by the Congressional Review Act, 5 U.S.C. 804.</P>
                <HD SOURCE="HD1">IV. Public Participation</HD>
                <HD SOURCE="HD2">A. Comments Sought</HD>
                <P>ATF requests comments on the proposed rule from all interested persons. ATF specifically requests comments on the clarity of this proposed rule and how it may be made easier to understand. In addition, ATF requests comments on the costs or benefits of the proposed rule and on the appropriate methodology and data for calculating those costs and benefits.</P>
                <P>
                    All comments must reference this document's RIN 1140-AA63 and, if handwritten, must be legible. If submitting by mail, you must also include your complete first and last name and contact information. If submitting a comment through the federal e-rulemaking portal, as described in section IV.C of this preamble, you should carefully review and follow the website's instructions on submitting comments. Whether you submit comments online or by mail, ATF will post them online. If submitting online as an individual, any information you provide in the online fields for city, state, zip code, and phone will not be publicly viewable when ATF publishes the comment on 
                    <E T="03">https://www.regulations.gov.</E>
                     However, if you include such personally identifying information (“PII”) in the body of your online comment, it may be posted and viewable online. Similarly, if you submit a written comment with PII in the body of the comment, it may be posted and viewable online. Therefore, all commenters should review section IV.B of this preamble, “Confidentiality,” regarding how to submit PII if you do not want it published online. ATF may not consider, or respond to, comments that do not meet these requirements or comments containing excessive profanity. ATF will retain comments containing excessive profanity as part of this rulemaking's administrative record but will not publish such documents on 
                    <E T="03">https://www.regulations.gov.</E>
                     ATF will treat all comments as originals and will not acknowledge receipt of comments. In addition, if ATF cannot read your comment due to handwriting or technical difficulties and cannot contact you for clarification, ATF may not be able to consider your comment.
                </P>
                <P>ATF will carefully consider all comments, as appropriate, received on or before the closing date.</P>
                <HD SOURCE="HD2">B. Confidentiality</HD>
                <P>ATF will make all comments meeting the requirements of this section, whether submitted electronically or on paper, and except as provided below, available for public viewing on the internet through the federal e-rulemaking portal, and subject to the Freedom of Information Act (5 U.S.C. 552). Commenters who submit by mail and who do not want their name or other PII posted on the internet should submit their comments with a separate cover sheet containing their PII. The separate cover sheet should be marked with “CUI//PRVCY” at the top to identify it as protected PII under the Privacy Act. Both the cover sheet and comment must reference this RIN 1140-AA63. For comments submitted by mail, information contained on the cover sheet will not appear when posted on the internet, but any PII that appears within the body of a comment will not be redacted by ATF and may appear on the internet. Similarly, commenters who submit through the federal e-rulemaking portal and who do not want any of their PII posted on the internet should omit such PII from the body of their comment and any uploaded attachments. However, PII entered into the online fields designated for name, email, and other contact information will not be posted or viewable online.</P>
                <P>A commenter may submit to ATF by mail information identified as proprietary or confidential business information. To request that ATF handle this information as controlled unclassified information (“CUI”), the commenter must place any portion of a comment that is proprietary or confidential business information under law or regulation on pages separate from the balance of the comment, with each page prominently marked “CUI//PROPIN” at the top of the page.</P>
                <P>
                    ATF will not make proprietary or confidential business information 
                    <PRTPAGE P="40943"/>
                    submitted in compliance with these instructions available when disclosing the comments that it receives, but will disclose that the commenter provided proprietary or confidential business information that ATF is holding in a separate file to which the public does not have access. If ATF receives a request to examine or copy this information, it will treat it as any other request under the Freedom of Information Act (5 U.S.C. 552). In addition, ATF will disclose such proprietary or confidential business information to the extent required by other legal process.
                </P>
                <HD SOURCE="HD2">C. Submitting Comments</HD>
                <P>Submit comments using either of the two methods described below (but do not submit the same comment multiple times or by more than one method). Hand-delivered comments will not be accepted.</P>
                <P>
                    • 
                    <E T="03">Federal e-rulemaking portal:</E>
                     ATF recommends that you submit your comments to ATF via the federal e-rulemaking portal at 
                    <E T="03">https://www.regulations.gov</E>
                     and follow the instructions. Comments will be posted within a few days of being submitted. However, if large volumes of comments are being processed simultaneously, your comment may not be viewable for up to several weeks. Please keep the comment tracking number that is provided after you have successfully uploaded your comment.
                </P>
                <P>
                    • 
                    <E T="03">Mail:</E>
                     Send written comments to the address listed in the 
                    <E T="02">ADDRESSES</E>
                     section of this document. Written comments must appear in minimum 12-point font size, include the commenter's first and last name and full mailing address, and may be of any length. See also section IV.B of this preamble, “Confidentiality.”
                </P>
                <HD SOURCE="HD2">D. Request for Hearing</HD>
                <P>Any interested person who desires an opportunity to comment orally at a public hearing should submit his or her request, in writing, to the Director within the 90-day comment period. The Director, however, reserves the right to determine, in light of all circumstances, whether a public hearing is necessary.</P>
                <HD SOURCE="HD3">Disclosure</HD>
                <P>
                    Copies of this proposed rule and the comments received in response to it are available through the federal e-rulemaking portal, at 
                    <E T="03">https://www.regulations.gov</E>
                     (search for RIN 1140-AA63).
                </P>
                <HD SOURCE="HD3">Severability</HD>
                <P>Consistent with the Administrative Procedure Act, the issues raised in this proposed rule may be finalized, or not, independently of each other, after consideration of comments received. ATF has determined that this proposed rule implements and is fully consistent with governing law. However, in the event this proposed rule is finalized, if any provision of that final rule, an amendment or revision made by that rule, or the application of such provision or amendment or revision to any person or circumstance, is held to be invalid or unenforceable by its terms, the remainder of that final rule, the amendments or revisions made by that rule, and application of the provisions of the rule to any person or circumstance shall not be affected and shall be construed so as to give them the maximum effect permitted by law.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects</HD>
                    <CFR>27 CFR Part 478</CFR>
                    <P>Administrative practice and procedure, Arms and munitions, Exports, Freight, Imports, Intergovernmental relations, Law enforcement officers, Military personnel, Penalties, Reporting and record-keeping requirements, Research, Seizures and forfeitures, Transportation.</P>
                    <CFR> 27 CFR Part 479</CFR>
                    <P>Administrative practice and procedure, Arms and munitions, Exports, Imports, Military personnel, Penalties, Reporting and record-keeping requirements, Seizures and forfeitures, Taxes, Transportation.</P>
                </LSTSUB>
                <P>For the reasons discussed in the preamble, ATF proposes to amend 27 CFR parts 478 and 479 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 478—COMMERCE IN FIREARMS AND AMMUNITION</HD>
                </PART>
                <AMDPAR>1. The authority citation for 27 CFR part 478 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority: </HD>
                    <P>5 U.S.C. 552(a); 18 U.S.C. 847, 921-931; 44 U.S.C. 3504(h).</P>
                </AUTH>
                <AMDPAR>2. Amend § 478.44 by:</AMDPAR>
                <AMDPAR>a. In § 478.44(a), revising § 478.44(a)(1)(ii) and (2); and</AMDPAR>
                <AMDPAR>
                    b. In § 478.44(b), removing the clause “ATF Form 7CR (Curios and Relics)” and adding in its place “ATF Form 7” and by removing the entire last sentence of the paragraph and adding in its place “Persons may obtain Form 7 on ATF's website at 
                    <E T="03">https://www.atf.gov/resource-center/forms.</E>
                    ”
                </AMDPAR>
                <P>The revision reads as follows:</P>
                <SECTION>
                    <SECTNO>§ 478.44</SECTNO>
                    <SUBJECT>Original license.</SUBJECT>
                    <STARS/>
                    <P>
                        (ii) include fingerprints and a photograph as required in the instructions on the form. Persons may submit fingerprints in paper or digital form. Persons can meet the photograph requirement by attaching either a clear and true copy (
                        <E T="03">e.g.,</E>
                         a photocopy, or, if submitting an electronic application, a scan, digital photograph, or other electronic copy) of their photo identification document, as defined in 27 CFR 478.11, or a photograph (may be digital and submitted electronically if submitting an electronic application) of themselves that is 2 x 2 inches in size, clearly showing a full front-view of their features, with head bare of hats or other items that overlap the front hairline, with the distance from the top of the head to the point of the chin approximately 1
                        <FR>1/4</FR>
                         inches, and that was taken within six months prior to the date they submit the photograph. In necessary cases, the Director may require a person to submit a photograph, and refuse to accept a submitted photo identification copy, if the document is not an acceptable type, the copy is not clear, or for other issues that impede the background check;
                    </P>
                    <STARS/>
                    <P>
                        (2) Persons may obtain Form 7 on ATF's website at 
                        <E T="03">https://www.atf.gov/resource-center/forms.</E>
                    </P>
                </SECTION>
                <PART>
                    <HD SOURCE="HED">PART 479—MACHINE GUNS, DESTRUCTIVE DEVICES, AND CERTAIN OTHER FIREARMS</HD>
                </PART>
                <AMDPAR>3. The authority citation for 27 CFR part 479 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority: </HD>
                    <P>26 U.S.C. 5801-5822; 26 U.S.C. 7801; 26 U.S.C. 7805.</P>
                </AUTH>
                <AMDPAR>4. Add § 479.27 to subpart C to read as follows:</AMDPAR>
                <SECTION>
                    <SECTNO>§ 479.27</SECTNO>
                    <SUBJECT>Photographs and fingerprints.</SUBJECT>
                    <P>(a) When applying to make or transfer and register a firearm under the National Firearms Act, or to become a special (occupational) taxpayer, ATF does not require individual applicants and responsible persons to submit fingerprints unless:</P>
                    <P>(1) The National Firearms Act, 26 U.S.C. chapter 53, explicitly requires the applicant to submit fingerprints with the application; or</P>
                    <P>(2) The Director requests the person to submit fingerprints because the Director is unable to determine, based on the results of the initial background check, whether making or transferring the firearm as proposed would place the person in violation of law.</P>
                    <P>
                        (b) When fingerprints are required under this section, the individual applicant or responsible person must submit with the application one properly completed FBI Form FD-258 (Fingerprint Card) or, if applying electronically, an equivalent digital 
                        <PRTPAGE P="40944"/>
                        fingerprint set. The fingerprints must be clear for accurate classification.
                    </P>
                    <P>(c) When applying as described under paragraph (a) of this section, individual applicants and responsible persons must attach a photograph. Individual applicants and responsible persons can meet the photograph requirement by attaching one of the following:</P>
                    <P>
                        (1) A clear and true copy (
                        <E T="03">e.g.,</E>
                         a photocopy, or, if submitting an electronic application, a scan, digital photograph, or other electronic copy) of their photo identification document, as defined in 27 CFR 478.11; or
                    </P>
                    <P>
                        (2) A photograph (which may be digital and submitted electronically) of themselves that is 2 x 2 inches in size, clearly showing a full front-view of their features, with head bare of hats or other items that overlap the front hairline, with the distance from the top of the head to the point of the chin approximately 1
                        <FR>1/4</FR>
                         inches, and that was taken within six months prior to the date they submit the photograph.
                    </P>
                    <P>(d) In certain cases, the Director may require a person to submit a photograph as described in (c)(2) of this section, and refuse to accept the photo identification copy described in (c)(1) of this section, such as if the document is not of an acceptable type, the copy is not clear, or if there are other issues impeding the person's background check.</P>
                </SECTION>
                <AMDPAR>5. In § 479.34, revise paragraph (e) to read as follows:</AMDPAR>
                <SECTION>
                    <SECTNO>§ 479.34</SECTNO>
                    <SUBJECT>Special tax registration and return.</SUBJECT>
                    <STARS/>
                    <P>
                        (e) 
                        <E T="03">Taxpayer identity.</E>
                         If the taxpayer is an individual, the taxpayer must attach the documentation required under § 479.27 unless the taxpayer has filed with ATF a properly executed ATF Form 5310.12 (“Form 7”), Application for Federal Firearms License, as specified in 27 CFR 478.44(a).
                    </P>
                </SECTION>
                <AMDPAR>6. Amend § 479.63 by:</AMDPAR>
                <AMDPAR>a. Revising the section heading and paragraph (a);</AMDPAR>
                <AMDPAR>b. Removing the word “shall” and adding in its place the word “must” in paragraph (b) introductory text and in paragraph (b)(1);</AMDPAR>
                <AMDPAR>c. Adding “and” after the semi-colon at the end of paragraph (b)(2)(ii);</AMDPAR>
                <AMDPAR>d. Revising paragraph (b)(2)(iii); and</AMDPAR>
                <AMDPAR>e. Removing paragraph (b)(2)(iv).</AMDPAR>
                <P>The revisions read as follows:</P>
                <SECTION>
                    <SECTNO>§ 479.63</SECTNO>
                    <SUBJECT>Applicant identity.</SUBJECT>
                    <P>(a) If the applicant is an individual, the applicant must attach the documentation required under § 479.27.</P>
                    <P>(b) * * *</P>
                    <P>(2) * * *</P>
                    <P>(iii) A photograph as described in § 479.27(c).</P>
                    <STARS/>
                </SECTION>
                <AMDPAR>7. Amend § 479.85 by:</AMDPAR>
                <AMDPAR>a. Revising the section heading and paragraph (a);</AMDPAR>
                <AMDPAR>b. Removing the word “shall” and adding in its place the word “must” in paragraph (b) introductory text and in paragraph (b)(1);</AMDPAR>
                <AMDPAR>c. Adding “and” after the semi-colon at the end of paragraph (b)(2)(ii);</AMDPAR>
                <AMDPAR>d. Revising paragraph (b)(2)(iii); and</AMDPAR>
                <AMDPAR>e. Removing paragraph (b)(2)(iv).</AMDPAR>
                <P>The revisions read as follows:</P>
                <SECTION>
                    <SECTNO>§ 479.85</SECTNO>
                    <SUBJECT>Transferee identity.</SUBJECT>
                    <P>(a) If the transferee is an individual, the applicant must attach the documentation required under § 479.27.</P>
                    <P>(b) * * *</P>
                    <P>(2) * * *</P>
                    <P>(iii) A photograph as described in § 479.27(c).</P>
                    <STARS/>
                </SECTION>
                <SIG>
                    <NAME>Robert Cekada,</NAME>
                    <TITLE>Director.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13587 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-FY-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Bureau of Alcohol, Tobacco, Firearms, and Explosives</SUBAGY>
                <CFR>27 CFR part 479</CFR>
                <DEPDOC>[Docket No. ATF-2026-0298; ATF No. 2025R-22P]</DEPDOC>
                <RIN>RIN 1140-AA80</RIN>
                <SUBJECT>Registering NFA Firearms That Fall Out of Government Contract</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Alcohol, Tobacco, Firearms, and Explosives, 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 Bureau of Alcohol, Tobacco, Firearms, and Explosives (“ATF”) proposes amending Department of Justice (“Department”) regulations implementing a statutory exemption and a statutory authority to grant relief from certain National Firearms Act (“NFA”) requirements to better distinguish between them. ATF also proposes to amend manufacturer registration requirements to include a provision granting relief to manufacturers from registering firearms they manufacture for the U.S. Government (“USG”). In conjunction with this, ATF is proposing a new provision permitting manufacturers to register such firearms “late”—after the existing regulatory window for registering manufactured firearms—if they fall out of USG contract.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted in writing, and must be submitted on or before (or, if mailed, must be postmarked on or before) September 4, 2026. Commenters should be aware that the federal e-rulemaking portal comment system will not accept comments after midnight Eastern Time on the last day of the comment period.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by RIN 1140-AA80, by either of the following methods—</P>
                    <P>
                        • 
                        <E T="03">Federal e-rulemaking portal: https://www.regulations.gov.</E>
                         Follow the instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         ATF Rulemaking Comments; Mail Stop 6N-518, Office of Regulatory Affairs; Enforcement Programs and Services; Bureau of Alcohol, Tobacco, Firearms, and Explosives; 99 New York Ave NE; Washington, DC 20226; 
                        <E T="03">ATTN: RIN 1140-AA80.</E>
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions must include the agency name and number (RIN 1140-AA80) for this notice of proposed rulemaking (“NPRM” or “proposed rule”). ATF may post all properly completed comments it receives from either of the methods described above, without change, to the federal e-rulemaking portal, 
                        <E T="03">https://www.regulations.gov.</E>
                         This includes any personally identifying information (“PII”) or business proprietary information (“PROPIN”) submitted in the body of the comment or as part of a related attachment they want posted. Commenters who submit through the federal e-rulemaking portal and do not want any of their PII posted on the internet should omit it from the body of their comment and any uploaded attachments that they want posted. If online commenters wish to submit PII with their comment, they should place it in a separate attachment and mark it at the top with the marking “CUI//PRVCY.” Commenters who submit through mail should likewise omit their PII or PROPIN from the body of the comment and provide any such information on the cover sheet only, marking it at the top as “CUI//PRVCY” for PII, or as “CUI//PROPIN” for PROPIN. For detailed instructions on submitting comments and additional information on the rulemaking process, see the “Public Participation” heading of the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section of this document. In accordance with 5 U.S.C. 553(b)(4), a summary of this rule may be found at 
                        <E T="03">https://www.regulations.gov.</E>
                         Commenters must submit comments by using one of the methods described above, not by 
                        <PRTPAGE P="40945"/>
                        emailing the address set forth in the following paragraph.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Office of Regulatory Affairs, by email at 
                        <E T="03">ORA@atf.gov,</E>
                         by mail at Office of Regulatory Affairs; Enforcement Programs and Services; Bureau of Alcohol, Tobacco, Firearms, and Explosives; 99 New York Ave NE; Washington, DC 20226, or by telephone at 202-648-7070 (this is not a toll-free number).
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    The Attorney General is responsible for enforcing the National Firearms Act (“NFA”), as amended, 26 U.S.C. chapter 53.
                    <SU>1</SU>
                    <FTREF/>
                     Congress and the Attorney General have delegated the responsibility for administering and enforcing the NFA to the Director of ATF (“Director”), subject to the direction of the Attorney General and the Deputy Attorney General. 
                    <E T="03">See</E>
                     28 U.S.C. 599A(b)(1), (c)(1); 28 CFR 0.130(a)(1)-(2); Treas. Order No. 221(2)(a), (d), 37 FR 11696-97 (June 10, 1972).
                    <SU>2</SU>
                    <FTREF/>
                     Accordingly, the Department and ATF have promulgated regulations to implement the NFA in 27 CFR part 479.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Some NFA provisions still refer to the “Secretary of the Treasury.” However, the Homeland Security Act of 2002, Public Law 107-296, 116 Stat. 2135, transferred the functions of ATF from the Department of the Treasury to the Department of Justice, under the general authority of the Attorney General. 26 U.S.C. 7801(a)(2); 28 U.S.C. 599A(c)(1). Thus, for ease of reference, this proposed rule refers to the Attorney General where relevant.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         In Attorney General Order Number 6353-2025, the Attorney General delegated authority to the Director to issue regulations pertaining to matters within ATF's jurisdiction, including under the NFA, Gun Control Act, and Title XI of the Organized Crime Control Act. ATF's jurisdiction also includes those portions of sec. 38 of the Arms Export Control Act pertaining to permanently importing defense articles and services and the Contraband Cigarette Trafficking Act.
                    </P>
                </FTNT>
                <P>The NFA, at 26 U.S.C. 5845(a), defines “firearm” to include machine guns, a shotgun having a barrel or barrels of less than 18 inches in length, a rifle having a barrel or barrels of less than 16 inches in length, certain weapons made from a rifle, certain weapons made from a shotgun, silencers, destructive devices, and any other weapon as defined in 26 U.S.C. 5845(e) (“NFA firearm”). Section 5841(b) mandates that each manufacturer, importer, and maker must register each NFA firearm they manufacture, import, or make in the National Firearms Registration and Transfer Record (“NFRTR”), unless, as specified in section 5841(a), the United States Government (“USG”) possesses or controls the NFA firearm, in which case it is exempt from NFA registration requirements.</P>
                <P>A person engaged in the business of manufacturing or importing NFA firearms must pay a special (occupational) tax (“SOT”) under the NFA. 26 U.S.C. 5801. A federal firearms licensee who pays a manufacturing SOT or an importing SOT is then qualified to manufacture or import NFA-regulated firearms (sometimes referred to as a “qualified manufacturer” or “qualified importer”).</P>
                <P>The NFA defines a “manufacturer” as a person who engages in the business of manufacturing NFA firearms. 26 U.S.C. 5845(m). Section 5841(c) further requires that manufacturers notify the Attorney General in such manner as regulations prescribe that they have manufactured an NFA firearm, and that doing so serves to register the firearms in the NFRTR. Implementing regulations at 27 CFR 479.103 provide that manufacturers must register NFA firearms on ATF Form 5320.2, Notice of Manufactured or Imported NFA Firearms (“Form 2”), no later than the close of the next business day after they manufacture the firearm.</P>
                <P>However, 26 U.S.C. 5851(a) includes an exemption from the special (occupational) tax for manufacturers exclusively doing business with the USG, and 27 CFR 479.33(a) incorporates and mirrors the statutory exemption. The exemption excuses any persons from paying the SOT if they establish that they conduct business exclusively with, or on behalf of, the USG. Paragraph (b) in both the statute and regulation requires persons who wish to be exempt from paying the SOT to submit an application to the Director.</P>
                <P>In addition, section 5851(a) and § 479.33(a) authorize the Director to relieve persons manufacturing firearms for or on behalf of the USG from complying with any NFA regulatory provision with respect to conducting business involving those USG firearms, whether they do business exclusively with the USG or not. This portion of the provision does not create an exemption, but permits the Director to grant relief and, unlike the exemption, applies only to manufacturers and does not require that they do business exclusively with the USG. The Director has long applied this authority to relieve qualified manufacturers from registering firearms manufactured for or pursuant to a contract with the USG. In other words, under this grant of relief, manufacturers who manufacture NFA firearms pursuant to a contract with the USG do not have to provide notice to ATF on Form 2 or register such firearms in the NFRTR. The Director has granted this relief, but it has not been included in the regulations.</P>
                <HD SOURCE="HD1">II. Proposed Rule</HD>
                <P>ATF is proposing first to reorganize § 479.33 so that the SOT exemption and the Director's authority to grant relief are separated, for better clarity. In addition, ATF is proposing to amend § 479.103 to articulate the Director's existing grant of relief to manufacturers doing business with the USG from registering firearms they manufacture for, or on behalf of, the USG. In conjunction with this, ATF is also proposing to add to § 479.103 a provision allowing manufacturers to register such firearms later, if they fall out of USG contract.</P>
                <P>In addition, ATF is proposing minor technical plain writing edits and updates to form numbers and titles in §§ 479.33 and 479.103.</P>
                <HD SOURCE="HD2">A. Reorganizing and amending § 479.33</HD>
                <P>ATF is proposing to reorganize § 479.33 by moving the second sentence of § 479.33(a)—which states the Director's authority to grant relief—into a stand-alone paragraph separate from the SOT exemption (also in § 479.33(a)).</P>
                <P>The SOT exemption for licensees who conduct business exclusively with the USG applies to any licensee who is required to pay a SOT, not just manufacturers, and would remain at § 479.33(a). This regulatory exemption arises from the exemption in 26 U.S.C. 5851(a), which also provides a SOT exemption for any person required to pay a SOT who conducts business exclusively with the USG. The current paragraph (b) in the implementing regulation, which describes the requirements for this exemption, would remain paragraph (b).</P>
                <P>The second sentence of the current paragraph (a), the Director's authority to grant relief, would move to a new paragraph (c) to better clarify that it is not applicable only to those who conduct business exclusively with the USG but is applicable to manufacturers, though only with respect to firearms manufactured for or on the USG's behalf. The Director's regulatory authority to grant relief from other NFA requirements under what would now be § 479.33(c) mirrors the provision in 26 U.S.C. 5851(a) that allows the Director to grant relief to any person who manufactures NFA firearms for, or on behalf of, the USG from NFA requirements with regard to those items.</P>
                <P>
                    ATF is also proposing to add a new paragraph (d) that would parallel the existing paragraph (b) by providing the process a manufacturer would need to follow to request any specific relief they 
                    <PRTPAGE P="40946"/>
                    would like the Director to grant from an NFA requirement. The current paragraph (b) has been confusing by mixing elements applicable to both the exemption and the relief authority, so having one application requirements paragraph for each would be clearer. Like paragraph (b), new paragraph (d) would require the request to be in letter form and to contain the manner in which the manufacturer conducts business with the USG, the types of firearms involved in the request, and the nature and specifics of the USG contract(s) under which the manufacturer is requesting relief from a requirement. In addition, paragraph (d) would also require manufacturers to include the relief they are requesting and the reasons they are requesting relief, since this paragraph covers requests for relief.
                </P>
                <P>The Director has previously granted manufacturers relief from registering firearms they manufacture for the USG, as discussed above (though not currently included in regulation), and—as one of the terms of that grant—has been requiring manufacturers to submit their request in a letter so that ATF can verify the manufacturers are contracting with the USG and then, during inspections, can easily determine that they are relieved from the registration requirement with regard to firearms they manufactured for the USG. Therefore, ATF is also proposing to retain that requirement in this rule. However, ATF proposes including it in § 479.103 with the grant provision relieving manufacturers from registering so that all the terms of the relief are located in one place. The proposed revisions to § 479.103 are discussed in more detail in the next section.</P>
                <HD SOURCE="HD2">B. Relief From Registering Manufactured USG Firearms and From Timing Requirements</HD>
                <P>
                    ATF is proposing to amend § 479.103 to clarify that the Director has granted relief under 26 U.S.C. 5851(a) and the new 27 CFR 479.33(c) to manufacturers from the requirement to register NFA firearms that they manufacture for, or on behalf of, the USG. ATF is proposing to include this clarification specifically in its regulations as a new paragraph (b) under § 479.103, which governs registering manufactured NFA firearms. In addition, ATF is proposing to include in this new paragraph (b) both the existing requirement that manufacturers submit a letter to ATF to request the relief and a new grant of relief from the registration timing requirements. This new provision granting relief from timing requirements would permit such manufacturers to register, after the standard registration window, rejected, residual, or repurposed (collectively, “rejected”) USG firearms not previously registered when they were part of a contract with the USG (
                    <E T="03">e.g.,</E>
                     a contract with the Department of Defense).
                </P>
                <P>
                    Licensees who conduct business solely with the USG do not have to pay the SOT because the statute explicitly carves out this exemption. But licensees who also conduct business with others do still pay the SOT because those other business activities remain taxable. And the Director can grant relief from other NFA requirements to licensees conducting business with the USG, relevant to that portion of their business, pursuant to the last sentence of 26 U.S.C. 5851(a).
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         ATF notes that 26 U.S.C. 5852 also grants a making and transfer tax exemption for NFA firearms made for or transferred to the USG, which is consistent with other provisions exempting various entities conducting business with the USG from other taxes, registration, and NFA requirements, as long as the exemption applies to only the NFA items the licensees makes, manufactures, or imports for or transfers to the USG.
                    </P>
                </FTNT>
                <P>The Director's authority to grant relief from NFA requirements, even though it does not explicitly discuss granting relief to manufacturers from registering NFA firearms they manufacture for the USG, has been consistently interpreted and applied as including authority to grant registration relief. ATF has been offering this registration relief to manufacturers for many years although it has not been in the regulations. However, people new to the industry are often confused by this, and ATF considers it better to make the registration relief more explicit.</P>
                <P>Therefore, ATF also proposes to amend its regulations at § 479.103 to reflect the Director's grant of relief for manufacturers from the NFA registration requirement under what would become § 479.33(c). ATF has already been granting this relief, and it should be included in the regulations along with its existing requirement that manufacturers who wish to make use of this relief must submit a request letter to ATF that sets out the manner in which the manufacturers conduct business, the types of firearms they manufacture, and proof satisfactory to the Director of the USG contract under which they operate.</P>
                <P>
                    In addition, ATF proposes to add to the proposed new § 479.103(b) a new grant of relief, providing a mechanism for manufacturers approved for registration relief to subsequently register NFA firearms they manufactured under a USG contract but that have since fallen out of contract.
                    <SU>4</SU>
                    <FTREF/>
                     Without a mechanism to register the firearms once they are no longer covered by the USG contract, the firearms must be destroyed or exported.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         To “fall out of contract” (a term most often used in real estate) means a legally binding agreement fails, terminates, or is cancelled before the sale occurs, usually due to failed contingencies like financing, inspection issues, or other specific conditions not being met. It implies the deal “falls through,” allowing the buyer to withdraw without penalty or the seller to seek new offers. It differs from a “breach of contract,” which usually involves violating terms rather than failing to meet predefined conditions.
                    </P>
                </FTNT>
                <P>
                    Manufacturers have requested permission to register such firearms “late”—
                    <E T="03">i.e.,</E>
                     after they fall out of USG contract. For example, ATF has been presented with scenarios where a Type 10 SOT licensee, a Manufacturer of Destructive Devices, Ammunition for Destructive Devices, or Armor Piercing Ammunition, sells destructive device munitions to the USG, but the munitions fall out of contract. Reasons might include that the USG rejected the items or directed the licensee to redirect the items to a commercial customer, or that the firearms are residual munitions manufactured for testing and research or development pursuant to a USG contract. While these munitions still maintain commercial value, they currently cannot be registered in the NFRTR and resold by the manufacturer. There is no regulatory mechanism to register NFA firearms manufactured for the USG that have fallen out of USG contract, so manufacturers must destroy or export such items, which can be extremely costly and burdensome. In the past, however, ATF has issued variances pursuant to the Director's authority to grant relief under what would now become § 479.33(c). These variances have provided relief from the regulatory requirement at § 479.103 that firearms be registered by the close of the next business day after manufacture, and they have allowed such firearms to be registered “late.”
                </P>
                <P>
                    Because the firearms were originally procured for the USG under contract, the proposed change to § 479.103 would allow otherwise eligible manufacturers who were initially exempt from registering those NFA firearms to subsequently register them if they fall out of USG contract. This relief from the standard registration period would be codified in the proposed new § 479.103(b) after the new provision explicitly granting manufacturers relief from registering firearms manufactured for the USG. ATF is proposing to permit manufacturers to register rejected USG firearms within 15 days after the date on which the items fall out of USG 
                    <PRTPAGE P="40947"/>
                    contract. ATF has decided to provide 15 days because these items usually fall out of contract in large batches without much, if any, notice, and it takes time to mark and register them all. A similar timeframe exists in ATF regulations for imported items,
                    <SU>5</SU>
                    <FTREF/>
                     which are often imported in lots or batches, as well, and industry has found it to be sufficient time, while ATF has found it to not be an excessive delay in terms of firearms accountability and public safety. The proposed 15-day late registration window thus comports with existing regulatory provisions. As an example, if a licensee manufactured thousands of unmarked firearms for the US military and that contract fell through, the manufacturer—under the standard registration period in the current regulations—would be required to have every firearm marked and registered by the end of the next business day. That would be an unreasonable timeframe. A licensee manufacturing non-USG NFA firearms knows how many it can mark and run off the line in a day, so the licensee can plan its manufacturing accordingly. If an entire lot falls out of contract, the manufacturer would have a difficult time marking the entire lot in a day.
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         27 CFR 479.112(a).
                    </P>
                </FTNT>
                <P>
                    Although this provision would grant manufacturers relief from registering NFA firearms they manufacture for the USG, and would permit them to later register any such firearms that fall out of government contract, other NFA and GCA requirements would remain in effect. For example, the record-keeping and marking requirements of the GCA would remain applicable. 
                    <E T="03">See, e.g.,</E>
                     27 CFR 478.92. Although many USG contracts specify the required markings, some specify other markings that are not the same as those in ATF regulations. Licensees may apply for a marking variance for NFA firearms under § 479.102 or rely on ATF Ruling 2016-5, if applicable.
                    <SU>6</SU>
                    <FTREF/>
                     However, if those NFA firearms later fall out of USG contract, the licensees must comply with the regulatory marking requirements and apply those markings to the fallen firearms. Additionally, explosives regulations under 27 CFR part 555 would remain applicable.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         ATF Ruling 2016-5, 
                        <E T="03">Marking Variance for Government Defense Contractors,</E>
                         (Aug. 1, 2016), 
                        <E T="03">https://www.atf.gov/media/19141/download</E>
                         [
                        <E T="03">https://perma.cc/56VJ-HEDR</E>
                        ]
                    </P>
                </FTNT>
                <HD SOURCE="HD1">III. Statutory and Executive Order Review</HD>
                <HD SOURCE="HD2">A. Executive Orders 12866 and 13563</HD>
                <P>Executive Order 12866 (Regulatory Planning and Review) directs agencies to assess the costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits.</P>
                <P>Executive Order 13563 (Improving Regulation and Regulatory Review) emphasizes the importance of agencies quantifying both costs and benefits, reducing costs, harmonizing rules, and promoting public flexibility.</P>
                <P>The Office of Management and Budget (“OMB”) has determined that this proposed rule is a “significant regulatory action” under Executive Order 12866 because this rule is expected to have an annual effect on the economy of $100 million or more in any given year. As discussed above, this proposed rule would reduce the regulatory restrictions on NFA firearm manufacturers. The rule would allow manufacturers who do not register NFA firearms because they are part of a contract with the USG a period of time in which to register any such firearms that then fall out of government contract, which they would otherwise have to destroy or export.</P>
                <P>ATF notes that the cost-benefit analysis in this rule for the impact of permitting late registration focuses on manufacturers of destructive devices. Manufacturers have already been incurring the costs of dealing with unregistered firearms that fall out of USG contract and would thus be impacted on that front if this rule is finalized as proposed. ATF has occasionally permitted manufacturers, who are already eligible for what would become the § 479.33(c) exemption through variances, to register NFA firearms that fall out of USG contracts, but this most often occurs for manufacturers of firearms other than destructive devices. Manufacturers of destructive devices primarily have to destroy any destructive device that falls out of USG contract. ATF lacks data on manufacturers of NFA firearms (other than destructive devices) who would be affected by this proposed rule; ATF has data on manufacturers of destructive devices because some of these manufacturers provided data to support requests that ATF provide this registration option. As a result, ATF focuses this analysis on the group for which it has data as a representative example of manufacturer impacts from the late registration portion of this rule, and requests comments on the savings manufacturers of other types of NFA firearms would realize from the late registration option. ATF requests the following information on current expenses for NFA firearm manufacturers with respect to NFA firearms that fall out of USG contracts:</P>
                <P>1. Are you currently able to refurnish or resell NFA firearms (other than destructive devices) that fall out of a USG contract?</P>
                <P>2. How often do you, as an NFA manufacturer, or NFA manufacturers collectively, have such NFA firearms that fall out of a USG contract in a given year?</P>
                <P>3. How much does it cost to destroy such NFA firearms that fall out of a USG contract?</P>
                <P>4. How often do you have to destroy NFA firearms that fall out of a USG contract as opposed to exporting them to another country?</P>
                <P>5. How often can you export NFA firearms that fall out of a USG contract rather than destroy them?</P>
                <P>6. If you export NFA firearms, how much profit could you recoup?</P>
                <P>7. How much could you, or manufacturers collectively, profit if you were able to repurpose or resell items that fall out of a USG contract domestically instead of exporting and reselling them?</P>
                <P>
                    Because this proposed rulemaking would be a “significant regulatory action” under Executive Order 12866, ATF has laid out the impacts of this proposed rulemaking in OMB's A-4 accounting statement in Table 1. Table 1 also illustrates the range of future estimates in a low, primary, and high range as ATF's Circular A-4 sensitivity analysis. ATF then provides its normal regulatory cost-benefit analysis to comply with Executive Orders 12866 and 13563.
                    <PRTPAGE P="40948"/>
                </P>
                <GPOTABLE COLS="7" OPTS="L2,nj,i1" CDEF="s50,9C,9C,9C,10C,10C,10C">
                    <TTITLE>Table 1—OMB Circular A-4 Accounting Statement ($ millions) and Sensitivity Analysis</TTITLE>
                    <BOXHD>
                        <CHED H="1">Category</CHED>
                        <CHED H="1">
                            Primary 
                            <LI>estimate</LI>
                        </CHED>
                        <CHED H="1">
                            Minimum 
                            <LI>estimate</LI>
                        </CHED>
                        <CHED H="1">
                            Maximum 
                            <LI>estimate</LI>
                        </CHED>
                        <CHED H="1">Units</CHED>
                        <CHED H="2">
                            Dollar 
                            <LI>year</LI>
                        </CHED>
                        <CHED H="2">
                            Percent 
                            <LI>discount</LI>
                        </CHED>
                        <CHED H="2">
                            Period 
                            <LI>covered (years)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW EXPSTB="06" RUL="s">
                        <ENT I="21">
                            <E T="02">Benefits (deregulatory savings)</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">Annualized monetized benefits</ENT>
                        <ENT>$828.94</ENT>
                        <ENT>$9.27</ENT>
                        <ENT>$845.57</ENT>
                        <ENT>2025</ENT>
                        <ENT>7</ENT>
                        <ENT>10</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT> 828.94</ENT>
                        <ENT> 9.27</ENT>
                        <ENT> 845.57</ENT>
                        <ENT>2025</ENT>
                        <ENT>3</ENT>
                        <ENT>10</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Annualized quantified benefits</ENT>
                        <ENT>n/a</ENT>
                        <ENT>n/a</ENT>
                        <ENT>n/a</ENT>
                        <ENT>2025</ENT>
                        <ENT>7</ENT>
                        <ENT>10</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="22"> </ENT>
                        <ENT>n/a</ENT>
                        <ENT>n/a</ENT>
                        <ENT>n/a</ENT>
                        <ENT>2025</ENT>
                        <ENT>3</ENT>
                        <ENT>10</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">Annualized non-monetized benefits</ENT>
                        <ENT A="05">n/a</ENT>
                    </ROW>
                    <ROW EXPSTB="06" RUL="s">
                        <ENT I="21">
                            <E T="02">Costs</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">Annualized monetized Costs</ENT>
                        <ENT>0.02</ENT>
                        <ENT>0.02</ENT>
                        <ENT>0.02</ENT>
                        <ENT>2025</ENT>
                        <ENT>7</ENT>
                        <ENT>10</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>0.02</ENT>
                        <ENT>0.02</ENT>
                        <ENT>0.02</ENT>
                        <ENT>2025</ENT>
                        <ENT>3</ENT>
                        <ENT>10</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Annualized quantified costs</ENT>
                        <ENT>n/a</ENT>
                        <ENT>n/a</ENT>
                        <ENT>n/a</ENT>
                        <ENT>2025</ENT>
                        <ENT>7</ENT>
                        <ENT>10</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="22"> </ENT>
                        <ENT>n/a</ENT>
                        <ENT>n/a</ENT>
                        <ENT>n/a</ENT>
                        <ENT>2025</ENT>
                        <ENT>3</ENT>
                        <ENT>10</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">Annualized non-monetized costs</ENT>
                        <ENT A="05">n/a</ENT>
                    </ROW>
                    <ROW EXPSTB="06" RUL="s">
                        <ENT I="21">
                            <E T="02">Transfers</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">Federal annualized monetized transfers</ENT>
                        <ENT>n/a</ENT>
                        <ENT>n/a</ENT>
                        <ENT>n/a</ENT>
                        <ENT>2025</ENT>
                        <ENT>7</ENT>
                        <ENT>10</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="22"> </ENT>
                        <ENT>n/a</ENT>
                        <ENT>n/a</ENT>
                        <ENT>n/a</ENT>
                        <ENT>2025</ENT>
                        <ENT>3</ENT>
                        <ENT>10</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="22"> </ENT>
                        <ENT A="L02">From: federal government</ENT>
                        <ENT A="L02">To: individuals</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Other annualized monetized transfers</ENT>
                        <ENT>n/a</ENT>
                        <ENT>n/a</ENT>
                        <ENT>n/a</ENT>
                        <ENT>2025</ENT>
                        <ENT>7</ENT>
                        <ENT>10</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="22"> </ENT>
                        <ENT>n/a</ENT>
                        <ENT>n/a</ENT>
                        <ENT>n/a</ENT>
                        <ENT>2025</ENT>
                        <ENT>3</ENT>
                        <ENT>10</ENT>
                    </ROW>
                    <ROW EXPSTB="06" RUL="s">
                        <ENT I="21">
                            <E T="02">Effects</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">State, local, and/or tribal governments</ENT>
                        <ENT A="L05">The rule will not impose an intergovernmental mandate or have significant or unique effects on small governments, implicate federalism, or have tribal implications.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Small businesses</ENT>
                        <ENT A="L05">For direct costs, this rule is deregulatory and provides savings to FFLs who conduct business with the USG for NFA firearms. While small businesses might be among those who contract with the USG to manufacture NFA firearms, they would not be adversely impacted because this rule saves them lost revenue and costs of destroying or exporting firearms that fall out of USG contract.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Wages</ENT>
                        <ENT A="05">n/a</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Growth</ENT>
                        <ENT A="05">n/a</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Distribution effects</ENT>
                        <ENT A="05">n/a</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Alternatives</ENT>
                        <ENT A="L05">
                            <E T="03">No-change alternative:</E>
                             $0 cost and $0 benefits. This was rejected as more stringent without any incremental benefit.
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT A="L05">
                            <E T="03">Proposed alternative:</E>
                             $22,464 annual savings offset; $828.9 million in annualized net benefit. This alternative was selected because the benefits exceed costs.
                        </ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="22"> </ENT>
                        <ENT A="L05">
                            <E T="03">Issuing guidance alternative:</E>
                             This alternative was considered but rejected. While this alternative would not impose any additional costs, it would not have the force and effect of a regulation and thus would not be able to fully offset the existing regulatory requirements.
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="06" RUL="s">
                        <ENT I="21">
                            <E T="02">Net benefits</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">Annualized monetized net benefits</ENT>
                        <ENT>828.92</ENT>
                        <ENT>8.24</ENT>
                        <ENT>845.55</ENT>
                        <ENT>2025</ENT>
                        <ENT>7</ENT>
                        <ENT>10</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>828.92</ENT>
                        <ENT>8.24</ENT>
                        <ENT>845.55</ENT>
                        <ENT>2025</ENT>
                        <ENT>3</ENT>
                        <ENT>10</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD2">1. Need Statement</HD>
                <P>Currently, although manufacturers do not have to register NFA firearms they manufacture for the USG by the close of the next business day after they manufacture the items, they only have the option to later register any such items that fall out of USG contract by variance, and as a result often must destroy or export them, which presents a potential loss of revenue and costs. Manufacturers, particularly those of destructive devices, have requested from ATF the opportunity to register such “rejected USG firearms” after they fall out of contract to avoid those costs and lost revenue.</P>
                <P>
                    As discussed in section II of this preamble, ATF believes that there is no impediment to converting the existing variance option for manufacturers into the regulation, thereby making the registration relief clearer for licensees. In addition, ATF agrees with licensees that permitting manufacturers to register USG NFA firearms late if they fall out of contract would be beneficial to industry and would not present a public safety risk. It simply permits registering these particular firearms, which were specially exempt under the NFA because they were for the USG, at a later 
                    <PRTPAGE P="40949"/>
                    time in the NFRTR. The firearms are subject thereafter to all the requirements for registered NFA firearms, just like other NFA firearms that were registered when first manufactured. Historically, as reflected in ATF crime gun data, registered NFA firearms are not commonly used to commit crimes. Therefore, ATF does not consider it a risk to the public if more registered devices move in commerce, particularly as most NFA firearms and destructive devices manufactured for the USG would not be eligible to enter the non-government market.
                </P>
                <HD SOURCE="HD2">2. Benefits and Savings</HD>
                <P>Manufacturers of NFA firearms would receive benefits from this rule that include no longer incurring costs to destroy firearms that fall out of USG contract, and income from selling such items. To the extent that manufacturers of NFA firearms are currently able to export these firearms instead of destroying them, benefits stemming from this rule would be decreased by the amount of any profits manufacturers currently make from exporting and reselling. ATF has no data on whether manufacturers in this situation currently export firearms that have fallen out of USG contract, to what extent the rejected firearms consist of firearms permitted for export, how frequently this occurs, whether the manufacturers are able to make a profit beyond their exporting costs, or whether the net return is more than the costs for destroying these firearms. ATF therefore requests public comments on these topics and does not include exporting in this analysis.</P>
                <P>However, as discussed in the beginning of section III.A of this preamble, ATF also does not have data on the frequency with which manufactured NFA firearms of all types fall out of contract in a year or the costs for disposing of them; we have received such data for only some manufacturers of destructive devices. As a result, this portion of the analysis focuses on manufacturers of destructive devices to illustrate the benefits that would accrue from this rule—which could also accrue to manufacturers of other NFA firearms in an unknown amount.</P>
                <P>As discussed throughout this rule, manufacturers who manufacture destructive devices (one type of NFA firearm) for USG contracts may have some that fall out of contract—in other words, the items end up not being sold or used within the contract for various reasons. The regulations require that NFA firearms, including destructive devices, be registered in the NFRTR by the close of the next business day after they are manufactured. The regulations do not include a provision for registering these formerly excepted devices if they fall out of USG contract later than close of the next business day after they were manufactured. As a result, manufacturers of destructive devices for the USG that then fall out of contract cannot subsequently sell those destructive devices within the United States; they must destroy them. However, this proposed rule would relieve manufacturers from the requirement to register such firearms by close of the next business day. Instead, the proposed rule would allow these manufacturers to register such destructive devices within 15 days after they fall out of USG contract, thereby enabling the manufacturers to lawfully retain them for possible sale to another customer. This proposed rule would allow these manufacturers to make a profit on already made destructive devices, rather than dismantle or destroy them at a loss, or export them at additional cost (and sell them) if they are of a type that may lawfully be exported pursuant to Department of State or Department of Commerce authorization.</P>
                <P>To determine the number of these manufacturers that would accrue benefits from registering destructive devices that fall out of USG contract, ATF estimated the total active number of licensed manufacturers of destructive devices to establish a baseline population.</P>
                <P>Based on ATF licensing information, there are 384 FFLs licensed to manufacture destructive devices. ATF does not have data on how many of these FFLs conduct business with the USG or how many have devices fall out of contract each year. However, the vast majority of destructive devices are manufactured for the USG. Although 100 percent of this population might not be impacted by this proposed change or have devices fall out of contract, it is the best available data for this purpose.</P>
                <P>
                    Based on information provided by a few industry members who manufacture destructive devices, destructive devices may fall out of contract between one and five times per year. There are two main methods of disposing of a destructive device: dismantling or destroying. A licensee can either dismantle the destructive device and reuse the viable pieces in new devices, or it can ship the device to be destroyed at another site. While these two methods differ in cost, ATF does not have a break-down of costs by method. But the licensees provided estimates of their disposal costs per occurrence (which are typically for lots or batches of devices at one time). The costs ranged from $330 for a small contract to $1.2 million for a large contract. So, combining the frequency range and cost range provided, a licensee could incur from $330 to $6 million per year in disposal costs for destructive devices that fall out of USG contract, depending on how often it occurs for that licensee and the size of the affected contract(s).
                    <SU>7</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         $330 (least costly) * 1 (lowest frequency) + $1.2 million (most costly) * 5 (highest frequency) provides the annual range represented by these industry responses.
                    </P>
                </FTNT>
                <P>
                    To estimate the annual disposal costs, ATF averaged the frequency estimates provided by the industry members, resulting in an average of twice per year that a manufacturer would have destructive devices fall out of contract (in lots or batches). ATF then averaged the cost estimates provided by these industry members over the average number of times firearms fall out of contract in a given year.
                    <SU>8</SU>
                    <FTREF/>
                     From this, ATF estimates an average annual disposal cost of $566,777 per year, per manufacturer, for purposes of this illustrative example. Multiplying this number by the number of destructive device manufacturers (384), ATF estimates that this proposed rule could result in $217.6 million annually in savings on disposal costs.
                    <SU>9</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         ATF is not including the underlying data in this rule from these industry members because it was provided under a promise of confidentiality due to competitive market considerations.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         $217,642,368 in disposal costs = 384 importers * $566,777 in disposal costs per year.
                    </P>
                </FTNT>
                <P>
                    In addition to savings from disposal costs, these licensees would also be able to sell these destructive devices, primarily to another government entity. Depending on the type of contract the licensee had with the USG for the affected destructive devices, this might result in additional revenue (such as cases in which the USG paid for the devices and then did not take them) or could represent cost recoupment (such as cases in which the licensee manufactured more than the USG ended up needing in a task-order type of contract). ATF has no information on how often each type of situation might arise. However, based on estimates provided by the industry respondents, income (whether revenue or recoupment) from selling destructive devices that fall out of USG contract could range from $23,800 to $3.75 million annually, which, when calculating a weighted average using all the data points within that range, results in an estimated $ 1.6 million (rounded) 
                    <SU>10</SU>
                    <FTREF/>
                     in income per year, per 
                    <PRTPAGE P="40950"/>
                    manufacturer. This would be a benefit from this proposed rule in addition to the disposal savings. Manufacturers of destructive devices would thus collectively accrue an estimated annual profit from selling these destructive devices of $611.3 million annually.
                    <SU>11</SU>
                    <FTREF/>
                     Combined with the $217.6 million annually in savings on disposal costs, this proposed rule would have an effect of $828.9 million in savings and profit just for manufacturers of destructive devices.
                    <SU>12</SU>
                    <FTREF/>
                     Overall, these savings and profit would be offset by the unknown amount of any profit manufacturers currently make from exporting these items rather than selling them under this proposed rule to the domestic market.
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         ATF is not including the underlying data in this rule from these industry members because it 
                        <PRTPAGE/>
                        was provided under a promise of confidentiality due to competitive market considerations.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         $611,302,400 in sales = 384 importers * $1,591,933 in sales per year.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         $828.9 million in overall profit = 384 FFLs * (566,777 reduction in disposal costs + 1,591,933 in reduction from lost sales)
                    </P>
                </FTNT>
                <P>Although ATF does not have equivalent data for manufacturers of NFA firearms (other than destructive devices) for the USG, ATF believes they would also experience savings from no longer incurring disposal costs and would also earn additional income from being able to sell firearms that have fallen out of USG contract. Because of the specialized nature of destructive devices, it is likely that the disposal costs for other NFA firearms would differ from those for destructive devices. Likewise, because the secondary market for other firearms might be broader than the one for destructive devices, it is possible that income from reselling other NFA firearms might also differ for this population. ATF is not able to determine this factor and is requesting public comments on this proposed rule's impact for manufacturers of NFA firearms (other than destructive devices).</P>
                <HD SOURCE="HD3">3. Costs and Savings Offsets</HD>
                <P>Manufacturers of NFA firearms for the USG would accrue savings from no longer incurring costs to destroy such firearms that fall out of USG contract (less profits from exporting abroad), and would increase income from selling such items. However, manufacturers would need to submit Form 2 to register any NFA firearms that fall out of government contract that they intend to retain or resell, which would give rise to a savings offset from this proposed rule in the form of monetized time burden.</P>
                <P>To register manufactured NFA firearms, licensees must file Form 2 with ATF, listing the firearms, along with other information about them. In this case, manufacturers would submit Form 2 listing the NFA firearms they manufactured for the USG that have fallen out of the USG contract. There are no fees or other costs associated with licensees registering NFA firearms they manufactured.</P>
                <P>
                    The estimated hourly burden to complete Form 2 is 45 minutes (0.75 hours). Because ATF does not maintain a point of contact for representatives completing Form 2, for the purposes of this analysis, ATF estimates that a production, planning, and expediting clerk might complete and submit Form 2.
                    <SU>13</SU>
                    <FTREF/>
                     The Bureau of Labor Statistics (“BLS”) estimates such a clerk's salary at $27.70 per hour.
                    <SU>14</SU>
                    <FTREF/>
                     To account for fringe employment benefits paid by the employer, such as insurance, agencies multiply the estimated salary by a standard average load rate. ATF determined the average load rate based on BLS's calculated national hourly compensation (salaries/wages plus paid benefits) for all private-sector occupations (average of $44.20 for 2024) 
                    <SU>15</SU>
                    <FTREF/>
                     divided by the national average hourly wages and salaries without benefits (average of $31.95 for 2024),
                    <SU>16</SU>
                    <FTREF/>
                     making a load rate of 1.42.
                    <SU>17</SU>
                    <FTREF/>
                     ATF then applied this load rate to the production, planning, and expediting clerk wage to calculate their total compensation. Multiplying BLS's estimated hourly wage rate for such a clerk ($27.70) by the load rate of 1.42, ATF estimates that an FFL would incur $39.33 
                    <SU>18</SU>
                    <FTREF/>
                     (rounded to $39) costs in monetized time per hour for each Form 2.
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         U.S. Bureau of Lab. Stat., 
                        <E T="03">Occupational Employment and Wages, May 2023: 43-5061 Production, Planning, and Expediting Clerks</E>
                         (Apr. 3, 2024), 
                        <E T="03">https://www.bls.gov/oes/2023/may/oes435061.htm</E>
                         [
                        <E T="03">https://perma.cc/EQ3L-3EME</E>
                        ].
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         U.S. Bureau of Labor Statistics, 
                        <E T="03">Total compensation cost per hour worked for private industry workers (2023-2025), https://data.bls.gov/dataViewer/view/timeseries/CMU2010000000000D</E>
                         [
                        <E T="03">https://perma.cc/T2ZL-2UUB</E>
                        ].
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         U.S. Bureau of Labor Statistics, 
                        <E T="03">Wages and salaries cost per hour worked for private industry workers (2023-2025),</E>
                         CMU2020000000000D. 
                        <E T="03">https://data.bls.gov/dataViewer/view/timeseries/CMU2020000000000D [https://perma.cc/8WEJ-2TRW].</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         1.4 load rate = $44.20 hourly compensation/$31.95 hourly wages and salaries.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         $39.33 hourly wage rate of a production clerk = $27.70 mean hourly wage * 1.42 load rate.
                    </P>
                </FTNT>
                <P>
                    Based on the loaded hourly wage rate ($39) and the hourly burden of 0.75 hours, ATF estimates that the costs manufacturers of NFA firearms would accrue under this proposed rule would be a rounded $29 
                    <SU>19</SU>
                    <FTREF/>
                     per USG firearm that falls out of contract (or per-contract if all firearms for the contract fall out of contract, as they would register these firearms in one lot, which would be on one form).
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         $29 hourly time burden = $39 rounded, loaded hourly wage rate * 0.75 hours.
                    </P>
                </FTNT>
                <P>
                    This would result in an annual savings offset to destructive device manufacturers of $22,464.
                    <SU>20</SU>
                    <FTREF/>
                     Manufacturers of other NFA firearms would also incur the savings offset at a rate of $29 per Form 2 using the same numbers, but ATF cannot estimate their annual offset without data on how often this might occur for these manufacturers. ATF requests comments from manufacturers of NFA firearms (other than destructive devices) regarding how often firearms fall out of their USG contracts per year.
                </P>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         $22,464 cost for Form 2 application = 384 manufacturers of destructive devices * 2 annual responses * 0.75 burden hours per response * $39 loaded wage rate.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">4. Net Savings</HD>
                <P>Overall, ATF estimates, on the basis of the limited data outlined in this analysis, that manufacturers of destructive devices would accrue under this proposed rule an estimated annual combined savings and profit of $828.9 million (and manufacturers of other types of NFA firearms would accrue an unknown additional amount) and would generate a savings offset for manufacturers of destructive devices of $22,464 per year (as well as an unknown amount for the same offset for manufacturers of other NFA firearms, and an unknown offset amount for any exporting profits they might earn under the existing situation). Even with the unknown savings/profits and savings offsets, this rule would save the industry a net $828.9 million annually, or a net $8.3 billion over the course of 10 years. These numbers might be much higher with data for manufacturers of other NFA firearms, but ATF estimates it would still result in a substantial net savings.</P>
                <HD SOURCE="HD3">5. Regulatory Alternatives</HD>
                <P>
                    Alternative 1. Maintaining the status quo (the no-action alternative). This alternative would maintain the status quo in that licensees who deal in government contracts would have to destroy or export NFA firearms manufactured for the USG if they fall out of contract, rather than being able to register and repurpose or directly sell them. Destroying or exporting such items incurs a cost to the licensees which would represent lost additional income for licensees. No costs and no benefits were calculated for this alternative because of data limitations discussed above. This was rejected as more stringent than the proposed 
                    <PRTPAGE P="40951"/>
                    alternative without any incremental benefit.
                </P>
                <P>
                    Alternative 2. Rulemaking (the proposed alternative). This proposed alternative would address the concerns raised by licensees who have NFA firearms they manufacture for the USG that have fallen out of contract and are not registered. Manufacturers must either destroy such items or export them, under current regulatory requirements, which incurs costs. Manufacturers would like to sell such items for additional revenue instead. This would not only benefit them, but also possibly benefit state and local law enforcement organizations with less funding, who might be able to purchase such items at less cost than on the secondary market. This proposed rule would allow manufacturers to register these devices in the NFRTR and then sell them. This would address the need raised by these licensees. It would also assist in keeping costs lower, as they could reduce cost offsets for items that fall out of contract.
                    <SU>21</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         
                        <E T="03">See</E>
                         footnote 4, 
                        <E T="03">supra.</E>
                    </P>
                </FTNT>
                <P>ATF does not believe permitting licensees to register these firearms within 15 days after they fall out of USG contract presents an increased risk of harm to the public; it simply treats them as newly manufactured and ensures they are registered so they can be retained for future contracts or repurposed or sold. ATF believes most of these firearms would be sold to other government law enforcement entities because of their nature. The annualized cost to register imported NFA firearms that fall out of USG contract, as estimated in this analysis, would be $22,464 for all manufacturers. The annualized benefit to manufacturers of destructive devices due to no longer destroying such items and accruing additional income from subsequent sales would be an estimated net annualized benefit of $828.9 million (plus an additional unknown benefit for manufacturers of other NFA firearms). This alternative was selected because the estimated benefits exceed estimated costs.</P>
                <P>Alternative 3. Issuing guidance. ATF considered issuing guidance instead of a rulemaking. The guidance would have been a ruling that added the manufacturer exemption from registering NFA firearms they import for the USG, and that would have permitted manufacturers to register USG-government contracted firearms that fall out of contract. This alternative was considered because the Director's authority to grant relief from NFA requirements, such as registering firearms manufactured for the USG, is already in the regulations so a grant under that authority could be accomplished by guidance. However, ATF decided against guidance because the regulations contain the registration requirements. ATF decided it would be better to include the exemption and the later registration allowance in the same location so it would be easier for licensees and others to find and understand how they work together, particularly because multiple sections would be affected. In addition, administration priorities for these changes to have the longevity, force, and effect of a regulation also weighed against this alternative. As a result of these considerations, this alternative was rejected.</P>
                <HD SOURCE="HD2">B. Executive Order 14192</HD>
                <P>Executive Order 14192 (Unleashing Prosperity Through Deregulation) requires an agency, unless prohibited by law, to identify at least ten existing regulations to be repealed or revised when the agency publicly proposes for notice-and-comment or otherwise promulgates a new regulation that qualifies as an Executive Order 14192 regulatory action (defined in OMB Memorandum M-25-20 as a final significant regulatory action under section 3(f) of Executive Order 12866 that imposes total costs greater than zero). In furtherance of this requirement, section 3(c) of Executive Order 14192 requires that any new incremental costs associated with such new regulations must, to the extent permitted by law, also be offset by eliminating existing costs associated with at least ten prior regulations. While this rule is an Executive Order 14192 regulatory action because it is a significant regulatory action as defined by Executive Order 12866, ATF does not anticipate needing to identify ten regulations to repeal or revise because this proposed rule would provide the public net savings rather than imposing new costs. As discussed in the cost/benefit analysis above, this proposed rule would provide savings of over $100 million every year throughout its ten-year period of analysis. In addition, this proposed rule would remove registration obstacles for licensed manufacturers who conduct business with the USG and whose NFA firearms fall out of contract, thereby permitting these licensees to save the costs of destroying or exporting such items and allowing them to earn additional income from selling them, resulting in the mentioned savings. ATF therefore expects this rule, if finalized as proposed, to qualify as an Executive Order 14192 deregulatory action (defined by OMB Memorandum M-25-20 as a final action that imposes total costs less than zero).</P>
                <HD SOURCE="HD2">C. Executive Order 14294</HD>
                <P>Executive Order 14294 (Fighting Overcriminalization in Federal Regulations) 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 mens rea standard applicable to each element of those offenses. This proposed rule would not create a criminal regulatory offense and is thus exempt from Executive Order 14294 requirements.</P>
                <HD SOURCE="HD2">D. Executive Order 13132</HD>
                <P>This proposed rule would not have substantial direct effects on the states, the relationship between the federal government and the states, or the distribution of power and responsibilities among the various levels of government. Therefore, in accordance with section 6 of Executive Order 13132 (Federalism), the Director has determined that this proposed rule would not impose substantial direct compliance costs on state and local governments, preempt state law, or meaningfully implicate federalism. It thus does not warrant preparing a federalism summary impact statement.</P>
                <HD SOURCE="HD2">E. Executive Order 12988</HD>
                <P>This proposed rule meets the applicable standards set forth in sections 3(a) and 3(b)(2) of Executive Order 12988 (Civil Justice Reform).</P>
                <HD SOURCE="HD2">F. Regulatory Flexibility Act</HD>
                <P>Under the Regulatory Flexibility Act, 5 U.S.C. 601-612, agencies are required to conduct a regulatory flexibility analysis of any proposed rule subject to notice-and-comment rulemaking requirements unless the agency head certifies, including a statement of the factual basis, that the proposed rule would not have a significant economic impact on a substantial number of small entities. Small entities include certain small businesses, small not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000.</P>
                <P>
                    The Director certifies, after consideration, that this proposed rule would not have a significant negative economic impact on a substantial number of small entities. Currently, manufacturers, including small businesses, must destroy or export NFA 
                    <PRTPAGE P="40952"/>
                    firearms that fall out of USG contract. They cannot sell them within the United States, and thus lose revenue for every such firearm (see cost-benefit analysis above for details), while also incurring costs to destroy or export them. This is an existing dynamic that affects small businesses, serving as a barrier to entry or a loss in revenue. This proposed rule would permit them to register these firearms, thereby removing those hurdles and such lost revenue, and providing a benefit and additional revenue to small businesses. However, that overall benefit would be slightly offset by the time burden of completing and submitting a Form 2 to register the firearms first. As described above, ATF estimates this offset cost to be 
                    <E T="03">de minimis</E>
                    —$58 annual cost per manufacturer.
                </P>
                <HD SOURCE="HD2">G. Small Business Regulatory Enforcement Fairness Act of 1996</HD>
                <P>This proposed rule is not likely to have a significant economic impact on a substantial number of small entities under the Small Business Regulatory Enforcement Fairness Act of 1996, 5 U.S.C. 601 note and 15 U.S.C. 657. This rule would provide significant benefits for small businesses because they would no longer have to destroy NFA firearms they had invested money in manufacturing but that the government no longer needed. For small businesses, the cost of destroying or exporting extra firearms could present a significant hurdle to entering this market or a significant loss of revenue. Due to this proposed rule, they would no longer incur such risk. They would instead incur the time burden for registering these firearms, which is a minor burden that would not present the same obstacles or costs for small businesses. For more information regarding the impact on small businesses, refer to section III.F above.</P>
                <HD SOURCE="HD2">H. Unfunded Mandates Reform Act of 1995</HD>
                <P>This proposed rule does not include a federal mandate that might result in the expenditure by state, local, and tribal governments, in the aggregate, or by the private sector, of $100 million or more in any one year, and it would not significantly or uniquely affect small governments.</P>
                <P>Therefore, ATF has determined that no actions are necessary under the provisions of the Unfunded Mandates Reform Act of 1995.</P>
                <HD SOURCE="HD2">I. Paperwork Reduction Act of 1995</HD>
                <P>Under the Paperwork Reduction Act of 1995 (“PRA”), 44 U.S.C. 3501-3521, agencies are required to submit to OMB, for review and approval, any information collection requirements a rule creates or any impacts it has on existing information collections. As defined in 5 CFR 1320.3(c), an information collection includes any reporting, record-keeping, monitoring, posting, labeling, or other similar actions an agency requires of the public. This proposed rule would impact one existing information collection covered under the PRA. The title and description of the information collection impacted by this rule, a description of those who provide the information, and an estimate of the total annual burden follow. The estimate covers the time for reviewing instructions, searching existing sources of data, gathering and maintaining the data needed, and completing and reviewing the collection. This proposed rule would not change most of the information below, but it would likely increase the number of responses to this information collection. Currently, manufacturers do not register items that fall out of USG contract, but would be able to do so under the proposed rule, thereby increasing the number of responses.</P>
                <P>
                    <E T="03">Title:</E>
                     Notice of Manufactured or Imported NFA Firearms, ATF Form 5320.2 (“Form 2”).
                </P>
                <P>
                    <E T="03">OMB control number:</E>
                     1140-0012.
                </P>
                <P>
                    <E T="03">Summary of the information collection:</E>
                     Each manufacturer and importer must register each NFA firearm they manufacture or import, as required by 27 CFR part 479. In general, under 26 U.S.C. 5822, no person can make an NFA firearm until they have applied for and received approval from the Attorney General (delegated to ATF). Section 5841(b) provides that each manufacturer and importer must register each firearm they manufacture or import. Section 5841(c) provides that each manufacturer must notify the Attorney General about a manufactured firearm, as provided by the regulations. Importers also must obtain authorization prior to importing a firearm. However, there are certain statutory exemptions, including firearms in the government's possession or imported for the government. 26 U.S.C. 5841(a). This proposed rule would add that manufacturers conducting business with the USG are exempt from registering firearms they manufacture for the USG, thereby reducing the number of respondents covered by this information collection. The proposed rule would also increase the number of respondents by permitting manufacturers to register USG firearms that fall out of contract, which they currently cannot do, but this increase would be smaller than the aforementioned decrease, resulting in a net decrease in respondents.
                </P>
                <P>
                    <E T="03">Need for information:</E>
                     ATF must collect certain information from applicants to register the firearms and to determine whether the person is authorized to possess a firearm. Not conducting this information collection would result in unregistered manufactured and imported firearms, which violate existing laws requiring manufacturers and importers to register all firearms not possessed or controlled by the USG. Firearms excepted from the requirement include those manufactured pursuant to a USG contract. However, sometimes such firearms are then not needed or otherwise fall out of contract. They then become NFA firearms that are no longer excepted from the registration requirement. This proposed rule would allow manufacturers to register such firearms when they fall out of contract. The consequence of not adding these registrations to this information collection would be that such firearms would remain unregistered and in violation of statutory requirements, increasing risk to the public, and causing the manufacturer to be unable to lawfully retain or sell them.
                </P>
                <P>
                    <E T="03">Proposed use of information:</E>
                     ATF uses Form 2 as the collection tool for information necessary to identify the firearms involved, to identify the person manufacturing or importing the firearm and whether the person is permitted to do so, and to register the firearm in the NFRTR. Registration in the NFRTR becomes the basis from which to verify any subsequent transfer of the NFA firearms and register them to the transferee.
                </P>
                <P>
                    <E T="03">Description of the respondents:</E>
                     Manufacturers and importers of NFA firearms.
                </P>
                <P>
                    <E T="03">Number of respondents:</E>
                     14,384 (at last renewal); some of which are manufacturers who might be impacted by this proposed rule because they do business exclusively for or on behalf of the USG, or partly for or on behalf of the USG, if they have firearms that fall out of such contract.
                </P>
                <P>
                    <E T="03">Frequency of response:</E>
                     Twice a year.
                </P>
                <P>
                    <E T="03">Burden of response:</E>
                     7,192 hours annually (at last renewal); pursuant to this proposed rule, a decrease of 576 hours stemming from 384 manufacturers of destructive devices no longer registering when they manufacture firearms for the USG. Although ATF does not have data on the number of manufacturers of NFA firearms (other than destructive devices) who would also decrease registrations for this reason, there would be an additional decrease in hourly burden from them. 
                    <PRTPAGE P="40953"/>
                    All the impacted manufacturers would also potentially have some firearms fall out of USG contract and be registered later, so the decreases above would be offset by a smaller increase, resulting in a net decrease to this information collection's hourly burden.
                </P>
                <HD SOURCE="HD2">J. Congressional Review Act</HD>
                <P>
                    Pursuant to the Congressional Review Act, 5 U.S.C. 801 
                    <E T="03">et seq.,</E>
                     ATF anticipates that this proposed rule would meet the criteria in 5 U.S.C. 804(2) because it would result in an annual effect on the economy of $100 million or more (in this case $100 million or more in savings); a major increase in costs or prices; or significant adverse effects on competition, employment, investment, productivity, innovation, or on the ability of United States-based enterprises to compete with foreign-based enterprises in domestic and export markets. However, this rule would not cause a major increase in costs or prices, or a significant adverse effect on competition, employment, investment, productivity, innovation, or U.S. enterprises' ability to compete with foreign-based enterprises, as this rule would provide significant savings and benefit to the public rather than adding costs or adversely affecting the economy.
                </P>
                <HD SOURCE="HD1">IV. Public Participation</HD>
                <HD SOURCE="HD2">A. Comments Sought</HD>
                <P>ATF requests comments on the proposed rule from all interested persons. ATF specifically requests comments on the clarity of this proposed rule and how it may be made easier to understand. In addition, ATF requests comments on the costs or benefits of the proposed rule and on the appropriate methodology and data for calculating those costs and benefits.</P>
                <P>
                    All comments must reference this document's RIN 1140-AA80 and, if handwritten, must be legible. If submitting by mail, you must also include your complete first and last name and contact information. If submitting a comment through the federal e-rulemaking portal, as described in section IV.C of this preamble, you should carefully review and follow the website's instructions on submitting comments. Whether you submit comments online or by mail, ATF will post them online. If submitting online as an individual, any information you provide in the online fields for city, state, zip code, and phone will not be publicly viewable when ATF publishes the comment on 
                    <E T="03">https://www.regulations.gov.</E>
                     However, if you include such personally identifying information (“PII”) in the body of your online comment, it may be posted and viewable online. Similarly, if you submit a written comment with PII in the body of the comment, it may be posted and viewable online. Therefore, all commenters should review section IV.B of this preamble, “Confidentiality,” regarding how to submit PII if you do not want it published online. ATF may not consider, or respond to, comments that do not meet these requirements or comments containing excessive profanity. ATF will retain comments containing excessive profanity as part of this rulemaking's administrative record, but will not publish such documents on 
                    <E T="03">https://www.regulations.gov.</E>
                     ATF will treat all comments as originals and will not acknowledge receipt of comments. In addition, if ATF cannot read your comment due to handwriting or technical difficulties and cannot contact you for clarification, ATF may not be able to consider your comment.
                </P>
                <P>ATF will carefully consider all comments, as appropriate, received on or before the closing date.</P>
                <HD SOURCE="HD2">B. Confidentiality</HD>
                <P>ATF will make all comments meeting the requirements of this section, whether submitted electronically or on paper, and except as provided below, available for public viewing on the internet through the federal e-rulemaking portal, and subject to the Freedom of Information Act (5 U.S.C. 552). Commenters who submit by mail and who do not want their name or other PII posted on the internet should submit their comments with a separate cover sheet containing their PII. The separate cover sheet should be marked with “CUI//PRVCY” at the top to identify it as protected PII under the Privacy Act. Both the cover sheet and comment must reference this RIN 1140-AA80. For comments submitted by mail, information contained on the cover sheet will not appear when posted on the internet, but any PII that appears within the body of a comment will not be redacted by ATF and may appear on the internet. Similarly, commenters who submit through the federal e-rulemaking portal and who do not want any of their PII posted on the internet should omit such PII from the body of their comment and any uploaded attachments. However, PII entered into the online fields designated for name, email, and other contact information will not be posted or viewable online.</P>
                <P>A commenter may submit to ATF information identified as proprietary or confidential business information by mail. To request that ATF handle this information as controlled unclassified information (“CUI”), the commenter must place any portion of a comment that is proprietary or confidential business information under law or regulation on pages separate from the balance of the comment, with each page prominently marked “CUI//PROPIN” at the top of the page.</P>
                <P>ATF will not make proprietary or confidential business information submitted in compliance with these instructions available when disclosing the comments that it receives, but will disclose that the commenter provided proprietary or confidential business information that ATF is holding in a separate file to which the public does not have access. If ATF receives a request to examine or copy this information, it will treat it as any other request under the Freedom of Information Act (5 U.S.C. 552). In addition, ATF will disclose such proprietary or confidential business information to the extent required by other legal process.</P>
                <HD SOURCE="HD2">C. Submitting comments</HD>
                <P>Submit comments using either of the two methods described below (but do not submit the same comment multiple times or by more than one method). Hand-delivered comments will not be accepted.</P>
                <P>
                    • 
                    <E T="03">Federal e-rulemaking portal:</E>
                     ATF recommends that you submit your comments to ATF via the federal e-rulemaking portal at 
                    <E T="03">https://www.regulations.gov</E>
                     and follow the instructions. Comments will be posted within a few days of being submitted. However, if large volumes of comments are being processed simultaneously, your comment may not be viewable for up to several weeks. Please keep the comment tracking number that is provided after you have successfully uploaded your comment.
                </P>
                <P>
                    • 
                    <E T="03">Mail:</E>
                     Send written comments to the address listed in the 
                    <E T="02">ADDRESSES</E>
                     section of this document. Written comments must appear in minimum 12-point font size, include the commenter's first and last name and full mailing address, and may be of any length. See also section IV.B of this preamble, “Confidentiality.”
                </P>
                <HD SOURCE="HD3">Disclosure</HD>
                <P>
                    Copies of this proposed rule and the comments received in response to it are available through the federal e-rulemaking portal, at 
                    <E T="03">https://www.regulations.gov</E>
                     (search for RIN 1140-AA80).
                </P>
                <HD SOURCE="HD3">Severability</HD>
                <P>
                    Consistent with the Administrative Procedure Act, the issues raised in this 
                    <PRTPAGE P="40954"/>
                    proposed rule may be finalized, or not, independently of each other, after consideration of comments received. ATF has determined that this proposed rule implements and is fully consistent with governing law. However, in the event this proposed rule is finalized, if any provision of that final rule, an amendment or revision made by that rule, or the application of such provision or amendment or revision to any person or circumstance, is held to be invalid or unenforceable by its terms, the remainder of that final rule, the amendments or revisions made by that rule, and application of the provisions of the rule to any person or circumstance shall not be affected and shall be construed so as to give them the maximum effect permitted by law.
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 27 CFR Part 479</HD>
                    <P>Administrative practice and procedure, Arms and munitions, Exports, Imports, Military personnel, Penalties, Reporting and record-keeping requirements, Seizures and forfeitures, Taxes, Transportation.</P>
                </LSTSUB>
                <P>For the reasons discussed in the preamble, ATF proposes to amend 27 CFR part 479 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 479—MACHINE GUNS, DESTRUCTIVE DEVICES, AND CERTAIN OTHER FIREARMS</HD>
                </PART>
                <AMDPAR>1. The authority citation for 27 CFR part 479 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority: </HD>
                    <P>26 U.S.C. 5801-5822; 26 U.S.C. 7801; 26 U.S.C. 7805.</P>
                </AUTH>
                <AMDPAR>2. Revise § 479.33, including its heading, to read as follows:</AMDPAR>
                <SECTION>
                    <SECTNO>§ 479.33</SECTNO>
                    <SUBJECT>Special exemption and grants of relief.</SUBJECT>
                    <P>(a) Any persons required to pay special (occupational) tax under this part will be relieved from paying that tax if they establish to the Director's satisfaction that they conduct their firearms business exclusively with, or on behalf of, the United States or any department, independent establishment, or agency thereof (USG).</P>
                    <P>(b) Persons may obtain the exemption in paragraph (a) by submitting a letter to the Director applying for the exemption. The letter must set out the manner in which the persons conduct business, the types of firearms they manufacture, import, or deal, and proof satisfactory to the Director of the USG contract under which they operate.</P>
                    <P>(c) The Director may also relieve any persons manufacturing firearms for or on behalf of the USG from complying with any provision of 26 U.S.C. chapter 53 or this part in conducting business with respect to such firearms.</P>
                    <P>(d) Manufacturers may request relief from a specific NFA requirement under paragraph (c) by submitting a letter to the Director. The letter must set out the manner in which the manufacturer conducts business with the USG, the types of firearms they manufacture, the nature and specifics of the USG contract or contracting operations under which the manufacturer is requesting relief from a requirement, the relief the manufacturer is requesting, and the reasons the manufacturer is requesting relief.</P>
                </SECTION>
                <AMDPAR>3. In § 479.103:</AMDPAR>
                <AMDPAR>a. Revise the section heading and designate the undesignated paragraph as paragraph (a);</AMDPAR>
                <AMDPAR>b. Amend new paragraph (a) by removing “Form 2 (Firearms), Notice of Firearms Manufactured or Imported” from the first sentence, adding in its place “ATF Form 5320.2, Notice of Manufactured or Imported NFA Firearms (“Form 2”)”, and removing the parenthetical “(Firearms)” after the three subsequent references to Form 2 in the paragraph; and</AMDPAR>
                <AMDPAR>c. Add new paragraph (b) to read as follows:</AMDPAR>
                <SECTION>
                    <SECTNO>§ 479.103</SECTNO>
                    <SUBJECT>Registering manufactured firearms.</SUBJECT>
                    <STARS/>
                    <P>(b) Pursuant to § 479.33(c) of this part, the Director relieves qualified manufacturers who manufacture firearms under a contract for the USG from the requirement to register firearms they manufacture for, or on behalf of, the USG pursuant to a contract.</P>
                    <P>(1) Manufacturers must request approval to participate in the relief granted under paragraph (b) by submitting a letter to the Director. The letter must set out the manner in which they conduct business, the types of firearms they manufacture, and proof satisfactory to the Director of the USG contract under which they operate.</P>
                    <P>(2) In addition, the Director relieves manufacturers who have been approved for relief under paragraph (b) from the prohibition against registering firearms beyond the next business day after they are manufactured. This second grant of relief applies only to firearms the licensees manufacture for, or on behalf of, the USG that are later rejected, repurposed, or become residuals of such contract (hereafter, rejected USG firearms), and the manufacturers must comply with the alternate registration terms in paragraph (b)(3).</P>
                    <P>(3) Approved manufacturers may register rejected USG firearms pursuant to paragraph (b)(2) by filing with the Director an accurate notice on Form 2, executed under the penalties of perjury, no later than 15 days after the date they are notified that the firearms have fallen out of contract. The manufacturers must comply with all marking requirements in § 479.102 of this part and must submit with Form 2 the government's official rejection notice or other documents demonstrating that the firearms are no longer subject to the USG contract.</P>
                </SECTION>
                <SIG>
                    <NAME>Robert Cekada,</NAME>
                    <TITLE>Director.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13586 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-FY-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">PENSION BENEFIT GUARANTY CORPORATION</AGENCY>
                <CFR>29 CFR Part 4022</CFR>
                <RIN>RIN 1212-AB47</RIN>
                <SUBJECT>Improvements to Rules on Recoupment of Benefit Overpayments</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Pension Benefit Guaranty Corporation.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Pension Benefit Guaranty Corporation (PBGC) is proposing to improve its rules on recoupment of benefit overpayments under PBGC's insurance program for single-employer terminated plans trusteed by PBGC. These proposed improvements include changing the recoupment methodology to a flat rate of 5 percent of a participant's monthly benefit and eliminating recoupment from a participant's surviving beneficiary.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted on or before September 4, 2026 to be assured of consideration.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments may be submitted by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal: https://www.regulations.gov.</E>
                         Follow the online instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Email: reg.comments@pbgc.gov.</E>
                         Refer to RIN 1212-AB47 in the subject line.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail or Hand Delivery:</E>
                         Legislative and Regulatory Division, Office of the General Counsel, Pension Benefit Guaranty Corporation, 445 12th Street SW, Washington, DC 20024-2101.
                    </P>
                    <P>Commenters are strongly encouraged to submit comments electronically. Commenters who submit comments on paper by mail should allow sufficient time for mailed comments to be received before the close of the comment period.</P>
                    <P>
                        All submissions must include the agency's name (Pension Benefit 
                        <PRTPAGE P="40955"/>
                        Guaranty Corporation or PBGC), the title for this rulemaking (Improvements to Rules on Recoupment of Benefit Overpayments), and the Regulation Identifier Number for this rulemaking (RIN 1212-AB47). Comments received will be posted without change to PBGC's website, 
                        <E T="03">www.pbgc.gov,</E>
                         including any personal information provided. Do not submit comments that include any personally identifiable information (such as name, address, or other contact information) or confidential business information that you do not want publicly disclosed. Comments may be submitted anonymously.
                    </P>
                    <P>
                        Copies of comments may also be obtained by writing to Disclosure Division (
                        <E T="03">disclosure@pbgc.gov</E>
                        ), Office of the General Counsel, Pension Benefit Guaranty Corporation, 445 12th Street SW, Washington, DC 20024-2101, or calling 202-326-4040 during normal business hours. If you are deaf or hard of hearing, or have a speech disability, please dial 7-1-1 to access telecommunications relay services.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Joseph Krettek (
                        <E T="03">krettek.joseph@pbgc.gov</E>
                        ), Assistant General Counsel for Legislative and Regulatory Division, Office of the General Counsel, at 202-229-6772; Office of the General Counsel, Pension Benefit Guaranty Corporation, 445 12th Street SW, Washington, DC 20024-2101. If you are deaf or hard of hearing, or have a speech disability, please dial 7-1-1 to access telecommunications relay services.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Executive Summary</HD>
                <HD SOURCE="HD2">A. Purpose and Authority</HD>
                <P>This proposed rule would amend the Pension Benefit Guaranty Corporation's (PBGC) recoupment rules under PBGC's insurance program for single-employer terminated plans trusteed by PBGC to simplify the repayment of benefit overpayments. The amendments would provide clarity and predictability, making the repayment process easier to communicate to participants and for participants to understand. The amendments would also allow for greater administrative efficiency.</P>
                <P>PBGC's legal authority for this rulemaking comes from section 4002(b)(3) of the Employee Retirement Income Security Act of 1974 (ERISA), which authorizes PBGC to issue regulations to carry out the purposes of title IV of ERISA, and section 4022 of ERISA (Single-Employer Plan Benefits Guaranteed), which sets limits on the benefits PBGC guarantees and pays.</P>
                <HD SOURCE="HD2">B. Major Provisions</HD>
                <P>The major provisions of this proposed rule would amend PBGC's recoupment rules under subpart E of part 4022 as follows.</P>
                <P>• Simplify the recoupment methodology to eliminate the actuarial reduction (capped, generally, at 10 percent of a participant's monthly benefit), and instead recoup at a flat rate of 5 percent of a participant's monthly benefit.</P>
                <P>• Waive overpayment amounts of $250 or less.</P>
                <P>• Eliminate recoupment of a participant's overpayment from a participant's surviving spouse or other designated beneficiary.</P>
                <P>• Eliminate recoupment on a revised benefit determination, except under specified circumstances such as where there is a post-benefit determination qualified domestic relations order (QDRO).</P>
                <P>Major provisions of the recoupment rules that are not changing are as follows.</P>
                <P>• No interest is ever charged by PBGC on net overpayments.</P>
                <P>• Recoupment ends one month early if the amount remaining to be recouped in the final month is less than the amount of the monthly reduction.</P>
                <P>• Recoupment constitutes full repayment of the net overpayment.</P>
                <P>The proposed rule would also codify PBGC's policy of administrative correction to correct payment errors and clarify when PBGC uses recovery methods instead of recoupment.</P>
                <HD SOURCE="HD1">II. Background</HD>
                <P>PBGC administers two insurance programs for private-sector defined benefit pension plans under title IV of ERISA: a single-employer plan termination insurance program and a multiemployer plan insolvency insurance program. In addition, PBGC administers a special financial assistance program for eligible financially distressed multiemployer plans. The proposed amendments in this rulemaking would apply only to the single-employer plan termination insurance program.</P>
                <P>Under the single-employer plan termination insurance program, covered plans that are underfunded may terminate either in a distress termination under section 4041(c) of ERISA or in an involuntary termination (one initiated by PBGC) under section 4042 of ERISA. When such a plan terminates, PBGC typically is appointed statutory trustee of the plan and becomes responsible for paying benefits in accordance with the provisions of title IV.</P>
                <P>The benefits paid by PBGC under a terminated trusteed plan are determined by several factors. The starting point is the plan—PBGC pays only those benefits that the plan provides under the plan's terms. Thus, PBGC begins by determining each participant's accrued plan benefit.</P>
                <P>After PBGC determines the amount of the participant's plan benefit, PBGC determines the amount it can guarantee. There are limitations on the benefits that PBGC can guarantee. One limitation, under sections 4001(a)(8) and 4022(a) of ERISA, is that PBGC guarantees only those benefits that are “nonforfeitable.” For purposes of title IV, a benefit is nonforfeitable if the participant had satisfied the plan's (or ERISA's) requirements for the benefit by the plan's termination date (or, if applicable, by the bankruptcy filing date of a contributing plan sponsor).</P>
                <P>Another limitation is the maximum guaranteeable benefit rule in section 4022(b)(3) of ERISA, which caps the amount that PBGC can guarantee. The cap for a participant in a plan with a termination date in 2025 (or, if applicable, a bankruptcy filing date of a contributing sponsor in 2025), who retires at age 65 under a straight-life annuity, is $7,431.82 per month. PBGC's guarantee is further limited by the phase-in rule, under which PBGC's guarantee of a plan's benefit increases during the 5-year period ending on the plan's termination date (or, if applicable, the bankruptcy filing date of a contributing sponsor) is phased in at the number of years the benefit increase has been in effect, multiplied by the greater of: (1) 20 percent of the amount of the benefit increase; or (2) $20 per month. The phase-in rule protects the insurance program from losses when the sponsor of an underfunded pension plan increases benefits shortly before the plan terminates. Another limitation is the accrued-at-normal limitation, which is equal to the dollar amount of a participant's benefit in the straight life annuity form at normal retirement age. The portion that exceeds this limitation is not a PBGC guaranteeable benefit.</P>
                <P>In some cases, a participant may receive more than the participant's guaranteed benefit under title IV, depending on the allocation of the plan's assets under section 4044(a) of ERISA or the allocation of PBGC's recoveries under section 4022(c) of ERISA, or both.</P>
                <P>
                    Although PBGC's obligation to pay benefits at title IV levels arises on the plan termination date, it usually takes several months after becoming the statutory trustee of a plan before PBGC 
                    <PRTPAGE P="40956"/>
                    can take any action to reduce benefits to title IV levels.
                </P>
                <P>In a distress termination, the plan administrator is required, beginning on the proposed termination date, to reduce benefits in pay status to the estimated levels payable under title IV. But compliance with this requirement does not always occur. When a plan is terminated in a distress termination, PBGC's preliminary review, upon becoming statutory trustee, focuses on whether the plan administrator's estimates of benefit entitlement were accurate, and PBGC adjusts benefits accordingly.</P>
                <P>In a PBGC-initiated termination, the plan administrator does not reduce benefits to estimated title IV levels. Once PBGC becomes statutory trustee, PBGC undertakes a preliminary review of the benefits to which each participant in the plan is being paid. After this review is completed, PBGC makes a preliminary estimate of the title IV benefits to which each participant is entitled. If the amount previously paid exceeds this preliminary estimate, PBGC reduces the benefit to the amount estimated to be the participant's benefit entitlement under title IV. If the amount previously paid is lower than this preliminary estimate, PBGC increases the benefit to the amount estimated to be the participant's benefit entitlement under title IV and pays the participant the back underpayment amount with interest.</P>
                <P>When PBGC pays the estimated title IV benefit amount, PBGC informs participants that their benefit payments at this preliminary stage are only estimates of the amounts to which they are entitled under title IV. PBGC also informs participants that, when PBGC completes its review of the pension plan and the plan's records, PBGC will issue a benefit determination that will set forth PBGC's determination of the amount to which the participant is entitled under title IV. PBGC further informs participants that when the benefit determination is issued, it may be appealed to the PBGC Appeals Board if the participant believes that PBGC's determination is incorrect.</P>
                <P>PBGC may pay estimated benefits for an extended period (which can be several years) until PBGC finishes its plan valuation and determines final benefit amounts. In the period between trusteeship and determination of final benefit amounts, overpayments or underpayments may occur, even after the initial adjustments that PBGC implements based on the preliminary estimate. For example, overpayments can occur because the plan-level benefit is higher than the participant's benefit under title IV levels. Overpayments and underpayments may also occur because PBGC was not aware of relevant plan amendments or other information when initial reductions were made.</P>
                <HD SOURCE="HD1">III. Recoupment, Recovery, and Administrative Correction of Benefit Overpayments</HD>
                <P>
                    Since the late 1970s, PBGC has sought recoupment of benefit overpayments. Because ERISA does not authorize PBGC to pay benefits in excess of title IV levels and imposes on PBGC an obligation to maintain premiums at the lowest level consistent with its other duties (see section 4002(a) of ERISA), PBGC's position is that failure to recoup excess payments would be inconsistent with the statutory scheme.
                    <SU>1</SU>
                    <FTREF/>
                     In 
                    <E T="03">Bechtel</E>
                     v. 
                    <E T="03">PBGC,</E>
                     the United States Court of Appeals, District of Columbia Circuit, affirmed that PBGC may recoup benefit overpayments and that PBGC's obligation to pay benefits to participants in trusteed plans is clearly subject to limitations under ERISA. Because there may be a delay in the calculation of title IV guaranteed benefits, the Court stated that “it's likely that some payments may be made at levels above those guaranteed by ERISA,” creating overpayments.
                    <SU>2</SU>
                    <FTREF/>
                     The Court went on to say that “Congress did not intend such delays, even those involving negligence by the PBGC, to create a windfall for some ERISA beneficiaries at the expense of others and the guaranty system as a whole.” 
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See</E>
                         PBGC's 1985 final rule (50 FR 3892, 3895-96 (Jan. 29, 1985)). 
                        <E T="03">See also Bechtel</E>
                         v. 
                        <E T="03">PBGC,</E>
                         624 F. Supp. 590, 593 (D.D.C. 1984), aff'd, 
                        <E T="03">Bechtel</E>
                         v. 
                        <E T="03">PBGC,</E>
                         781 F.2d 906, 907 (D.C. Cir. 1986).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">Bechtel</E>
                         v. 
                        <E T="03">PBGC,</E>
                         781 F.2d 906, 907 (D.C. Cir. 1986).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    PBGC's current recoupment methodology was established in a final rule published on January 29, 1985, at 50 FR 3892 and codified in subpart E of 29 CFR part 4022. A subsequent rule, published in 1998, amended the regulation to provide that recoupment ends once the total amount of the overpayment is repaid and gives PBGC discretion to waive recoupment of net overpayments that it determines to be de minimis.
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See</E>
                         63 FR 29354 (May 29, 1998). The rules also were amended in 2002 (to clarify that if there is a net overpayment at the time of the participant's death, and the participant was not entitled to future annuity benefits as of the plan's termination date, PBGC may seek repayment of the overpayment from the participant's estate), and in 2011 (explicitly stating that the rules regarding the overpayments (and underpayments) that will be taken into account in determining any amount to be recouped (or reimbursed) by PBGC apply regardless of whether the termination is a Pension Protection Act (PPA) 2006 bankruptcy termination). 
                        <E T="03">See</E>
                         67 FR 16950 (Apr. 8, 2002) and 76 FR 34590 (June 14, 2011)).
                    </P>
                </FTNT>
                <P>
                    PBGC's recoupment rules under § 4022.81(a) provide that if a participant has been paid more (on a net basis) than the amount to which the participant is entitled, and the participant is entitled to future benefit payments (
                    <E T="03">i.e.,</E>
                     monthly annuity payments) as of the termination date, PBGC will seek to recoup this net overpayment. Section 4022.81(a) also provides that PBGC may, in its discretion, seek repayment of overpayments by methods other than recouping, but PBGC will not normally do so unless benefits paid after the termination date exceed the participant's benefit entitlement under the plan.
                </P>
                <P>
                    PBGC recoups overpayments by reducing future benefit payments by an actuarial reduction, which is the recoupment percentage. Net overpayments are determined using a month-to-month tally of overpayments and underpayments occurring after the plan's termination date or the date PBGC issues a notice of determination under section 4042 of ERISA, if later. Section 4022.82(a) of PBGC's current regulation provides that the recoupment percentage equals the net overpayment divided by the present value (as of the termination date) of the participant's title IV benefit entitlement and is capped at 10 percent in most cases. Recoupment ends at the earlier of when the net overpayment is repaid or when monthly benefit payments cease. Recoupment continues to apply to the survivor benefit if the participant dies before the net overpayment has been repaid. For example, if a participant's net overpayment is $4,000 and the present value as of the plan's termination date of the benefit entitlement is $100,000, the recoupment percentage is 4 percent (4,000/100,000), regardless of the start date for recoupment, which is often many years after PBGC assumes responsibility for benefit payments. Future monthly benefits are reduced by 4 percent until: (a) the sum of repayments equals $4,000, or (b) monthly benefits cease (
                    <E T="03">i.e.,</E>
                     when the participant and any survivor beneficiary die).
                </P>
                <P>
                    Under § 4022.82(a)(2), PBGC generally limits recoupment of a net overpayment to the greater of either (i) 10 percent of a participant's monthly benefit payment, or (ii) for very large overpayments to a participant with a high benefit, the dollar amount per month in excess of the maximum guaranteeable benefit payable under section 4022(b)(3)(B) of ERISA, determined without adjustment for age 
                    <PRTPAGE P="40957"/>
                    and benefit form (what PBGC refers to as “the maximum insurance limitation”). Also, PBGC may recoup at a higher rate or seek repayment by recovery (in accordance with the rules under 29 CFR part 4903) where net benefits paid to a participant after the termination date exceed those to which the participant and any beneficiary is entitled under the terms of the plan, or where benefit payments were based on false information, error, or omission by the participant of information material to the benefit amount, benefit entitlement, or eligibility. PBGC may also recoup at a higher rate or seek repayment by recovery where PBGC has reason to believe that the person who received a benefit overpayment knew or should have known that the payment was made in error and failed to notify PBGC of the error.
                </P>
                <P>PBGC does not charge interest on net overpayments subject to recoupment. In addition, PBGC has discretion under current § 4022.82(a)(4) to waive overpayments PBGC determines are de minimis.</P>
                <P>
                    In addition to recoupment and recovery, PBGC uses administrative correction to correct payment errors. Before PBGC determines there is an overpayment, PBGC first tries to immediately correct any payment errors (
                    <E T="03">e.g.,</E>
                     duplicate monthly payments, payments to deceased participants or beneficiaries, and other clerical or arithmetic errors). Administrative correction includes methods such as reversal or reclamation of electronic payments (
                    <E T="03">e.g.,</E>
                     through Automated Clearing House (ACH)), stop-payment orders, and benefit suspension for one to two months.
                </P>
                <P>
                    PBGC seeks repayment by recovery if administrative correction and recoupment do not apply, or if administrative correction is unsuccessful. These situations may include, for example, where a lump sum paid by PBGC exceeded the participant's benefit entitlement under the terms of the plan; where the participant was not entitled to a benefit from PBGC (
                    <E T="03">e.g.,</E>
                     the participant was not vested, or the benefit amount was paid to the incorrect person); where payments were made to the participant after a communicated end date (such as with a term-certain annuity); or where payments were based on false information, error, or omission by the participant that materially affected the benefit amount, benefit entitlement, or eligibility.
                </P>
                <HD SOURCE="HD1">IV. Reasons for Change</HD>
                <P>Based on PBGC's experience and its review of the recoupment rules, PBGC determined that the current process of correcting benefit overpayments is unclear and unpredictable. In particular, PBGC is concerned that the recoupment methodology, which is based on actuarial concepts unfamiliar to many participants, makes the rules difficult to explain to participants and for participants to understand. The amendments in this proposed rule are designed to improve the repayment process for benefit overpayments by making that process clearer and predictable, and to allow for greater administrative efficiency.</P>
                <HD SOURCE="HD1">V. Proposed Amendments</HD>
                <HD SOURCE="HD2">A. Recoupment Methodology Including De Minimis Overpayment Amounts</HD>
                <P>
                    PBGC proposes to amend its recoupment methodology by replacing the actuarial reduction subject to, generally, a 10 percent cap, with a flat rate of 5 percent. This revised method is straightforward, and therefore simpler to communicate to participants and easier for participants to understand. A flat rate also would be simpler to administer, decreasing the potential for multiple notices to participants about recoupment and their guaranteed benefit. The flat rate would recoup the vast majority of participants at 5 percent. Under the current methodology, a larger percentage of participants with small monthly benefits of $300 or less are recouped at 10 percent, compared to participants with larger monthly benefits of $1,500 or more who are often recouped at a lower rate.
                    <SU>5</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         Of participants being recouped at 10 percent, 48 percent have monthly benefits of $300 or less and 3 percent have a monthly benefit of $1,500 or more. PBGC data estimates (2019).
                    </P>
                </FTNT>
                <P>PBGC estimates that changing to a flat rate of 5 percent would increase PBGC's expected repayment from participants and beneficiaries subject to recoupment. On average, PBGC collects 51% of a debt under its current method, which would increase to 65% under the proposal. The average, per-participant amount currently being repaid is $388 each year.</P>
                <P>
                    In addition to recoupment at a flat rate of 5 percent, PBGC would not seek to recoup net overpayments of $250 or less (
                    <E T="03">i.e.,</E>
                     those amounts treated as de minimis). PBGC estimates that, under this proposed change, 500 payees will avoid a total of $5,000 in recoupments each year. Consistent with current § 4022.82(a)(4), under the proposed rule, PBGC would retain discretion to not recoup additional net overpayment amounts that it determines to be de minimis to ensure that, over time, the amount remains appropriate based on changing benefit and overpayment trends in PBGC-trusteed plans and the administrative cost of recouping small amounts.
                </P>
                <P>The proposal also would provide that if a participant's net overpayment is equal to or less than the $250 de minimis amount and the net overpayment increases solely because unadjusted benefit payments are continuing during the pendency of the participant's appeal of their benefit determination to the PBGC Appeals Board, PBGC nevertheless will regard the participant's net overpayment as not having increased during the pendency of such appeal. This means the participant will not be treated as having lost out on the $250 or less de minimis exception because an appeal is pending. This provision would avoid a potential chilling effect on a participant considering an appeal of their benefit determination.</P>
                <HD SOURCE="HD2">B. Eliminate Recoupment From a Surviving Beneficiary</HD>
                <P>
                    Under current § 4022.81(d), recoupment of a participant's net overpayment continues to the surviving spouse or other beneficiary receiving survivor benefits under the participant's pension, if the participant dies and the net overpayment has not been repaid. This is because, in most cases where the benefit is paid in a joint-life form, the actuarial reduction considers the lives of both the participant and the surviving beneficiary. PBGC proposes to eliminate this provision and not recoup any remaining portion of a participant's net overpayment from benefits payable to a surviving beneficiary. In such a case, the surviving beneficiary was not the individual who received the net overpayment and may not even know that there was a net overpayment. Eliminating recoupment of a participant's net overpayment from a surviving spouse or other designated surviving beneficiary would alleviate this unnecessary confusion and be more equitable. PBGC estimates that eliminating recoupment from a surviving beneficiary will save 4,000 beneficiaries approximately a total of $900,000 per year. In addition, under a flat 5 percent recoupment, the expected benefits to be paid to the participant's surviving beneficiary is not a factor in calculating the recoupment percentage. Finally, this proposed amendment would be consistent with a provision applicable to ongoing pension plans under section 206(h)(4)(E) of ERISA, as added by the SECURE 2.0 Act, under which recoupment of past overpayments to a participant may not 
                    <PRTPAGE P="40958"/>
                    be sought from any beneficiary of the participant.
                    <SU>6</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         section 301 of the SECURE 2.0 Act of 2022, Division T of the Consolidated Appropriations Act, 2023, Public Law 117-328 (Dec. 29, 2022).
                    </P>
                </FTNT>
                <P>Under § 4022.83(b)(1) of this proposed rule, recoupment would end at the date of death of the participant or beneficiary who received the net overpayment. The provision would be applicable for participants and beneficiaries with a date of death on or after the effective date of the final rule.</P>
                <HD SOURCE="HD2">C. Eliminate Recoupment on a Revised Benefit Determination</HD>
                <P>Under certain circumstances, PBGC will revise a benefit determination where the calculation later is found to be incorrect. For example, if after a benefit determination is sent to a participant, PBGC becomes aware of plan information affecting factors used by PBGC in calculating the participant's benefit, PBGC will revise the participant's benefit payment going forward accordingly. If the revision results in a net overpayment, PBGC initiates recoupment. If the participant is receiving benefits and there is a net overpayment on the original benefit determination that is being recouped, the net overpayment amount must be adjusted.</P>
                <P>PBGC is proposing to eliminate recoupment on revised benefit determinations in most cases. This means that while future benefit payments must be adjusted to reflect the revised determination, PBGC generally will not initiate recoupment on the revised determination or increase the amount of the net overpayment to be recouped. While revising a benefit determination may be infrequent, it may cause confusion to participants, who rely on the benefit determination they initially received.</P>
                <P>The proposed rule provides that PBGC generally will not recoup on revised benefit determinations unless any of the following circumstances exist:</P>
                <P>• Benefit payments were made based on false information, error, or omission by the participant that materially affected the benefit amount, benefit entitlement, or eligibility.</P>
                <P>• PBGC has reason to believe the person receiving the payment knew or should have known the payment was made in error and failed to notify PBGC of the error.</P>
                <P>• Benefit payments were reduced by a settlement agreement.</P>
                <P>In addition, the proposed change to recoupment on revised benefit determinations would not apply where the participant or beneficiary comes forward with new information that would change their title IV benefit entitlement. This occurs when a domestic relations order (such as a shared payment order or a child support order) is submitted and qualified (so that the order is a “QDRO”) after a benefit determination was issued. PBGC must revise the benefit determination and the net overpayment (if any) where there is a QDRO.</P>
                <P>PBGC estimates that, by generally eliminating recoupment on revised benefit determinations, 270 payees will avoid a total of $8,640 in recoupments each year.</P>
                <HD SOURCE="HD2">D. Exceptions to Recoupment at 5 Percent</HD>
                <P>As described earlier in the preamble, PBGC's current regulation and policy allow for exceptions to the 10 percent cap on recoupment in several situations. PBGC is proposing to codify the policy exceptions that allow PBGC to recoup above the cap to provide more transparency to the recoupment process. The proposed rule provides that PBGC may recoup more than 5 percent of a monthly benefit or use recovery, but generally will not do so unless any of the following circumstances exist:</P>
                <P>• Benefit payments were made based on false information, error, or omission by the participant that materially affected the benefit amount, benefit entitlement, or eligibility.</P>
                <P>• PBGC has reason to believe the person receiving the payment knew or should have known the payment was made in error and failed to notify PBGC of the error.</P>
                <P>• Benefit payments were reduced by a settlement agreement.</P>
                <HD SOURCE="HD2">E. Administrative Correction and Recovery</HD>
                <P>
                    As described in the “Background” section earlier in the preamble, recoupment is not the only method of seeking repayment of a benefit overpayment. In appropriate cases, PBGC first tries to promptly correct a payment error before treating the payment error as a net overpayment subject to recoupment or recovery. This proposed rule would codify this policy of administrative correction. The proposed rule would also codify that if administrative correction was unsuccessful, such as where benefit payments are made after death and PBGC is unable to obtain the funds (
                    <E T="03">e.g.,</E>
                     through ACH reclamation or stop payment order), the payment error would be treated as a net overpayment, and PBGC would seek return of the funds via recovery from the person holding the net overpayment, including a financial institution, estate, or other person.
                </P>
                <P>
                    Under the proposed rule, PBGC would also clarify that recovery applies if a participant or beneficiary is not entitled to future benefit payments when a net overpayment is determined (
                    <E T="03">e.g.,</E>
                     in a benefit determination). In this situation, there is no payment stream from which to recoup. PBGC would have discretion to use recovery, which reflects current PBGC policy, and PBGC generally would do so in any of the following situations:
                </P>
                <P>
                    • Benefit payments were made after an unambiguous payment end date, that was communicated to the participant by PBGC or the plan administrator of the terminated plan (such as with a term-certain annuity (
                    <E T="03">e.g.,</E>
                     a 10-year certain annuity)).
                </P>
                <P>• Benefit payments were made based on false information, error, or omission by the participant that materially affected the benefit amount, benefit entitlement, or eligibility.</P>
                <P>• PBGC has reason to believe the person receiving the payment knew or should have known the payment was made in error and failed to notify PBGC of the error.</P>
                <P>PBGC is eliminating the discretion it had preserved to seek repayment “by methods other than recouping” where benefits paid after the termination date exceeded the participant's benefit entitlement under the terminated plan. PBGC has rarely, if ever, relied on this provision as it exists in § 4022.81(a). Eliminating it would enhance clarity for the regulated public and simplify the regulatory structure.</P>
                <HD SOURCE="HD2">F. Reorganization of Subpart E</HD>
                <P>
                    PBGC is proposing to reorganize subpart E of part 4022, which includes the regulations for calculating and processing net overpayments and net underpayments. There are no substantive changes to the rules for reimbursement of net underpayments. The rates used to credit interest on net underpayments for May 1998 and earlier are provided in a table to § 4022.82(b)(2). The table is derived from the rates historically used for lump sum valuations, which are posted on PBGC's website at 
                    <E T="03">www.pbgc.gov.</E>
                     The reorganization and table are only intended to improve the readability and understandability of subpart E.
                </P>
                <HD SOURCE="HD1">VI. Section 301 of the SECURE 2.0 Act</HD>
                <P>
                    In December 2022, Congress enacted SECURE 2.0. Division T of the Consolidated Appropriations Act, 2023, Public Law 117-328, 136 Stat. 4459. Section 301 addresses the fiduciary 
                    <PRTPAGE P="40959"/>
                    duties of ongoing plans regarding correction of benefit overpayments by any pension plan. In addressing plan fiduciaries' discretion for correcting overpayments, it places several limitations on ongoing plans where they decide to pursue collection. For example, a plan cannot seek recovery if the first overpayment occurred more than 3 years before written notification of the overpayment error to the participant or beneficiary, except in the case of fraud or misrepresentation by the participant or beneficiary. Section 301 amends title I of ERISA, adding section 206(h), and its text clearly applies to the duties of fiduciaries of ongoing plans—for example, it directs a fiduciary to take into account whether the “failure to recover all or part of the overpayment faster than required under [the] funding rules would materially affect the plan's ability to pay benefits due to other participants and beneficiaries[.]” It also amends section 414 of the Code, addressing benefit overpayments and a plan's satisfaction of qualification requirements such as minimum funding and compensation limitations under sections 401(a)(17) and 415(b).
                </P>
                <P>SECURE 2.0, section 301 specifies no changes to PBGC's methodology. And PBGC concludes that section 301's rules for ongoing plans do not carry over to the title IV context. PBGC's termination and trusteeship program is not an individual ongoing pension plan but a government program that pays benefits to participants and beneficiaries of trusteed single employer plans using a combination of trusteed plan assets and government insurance funds. Unlike individual pension plans that pay benefits solely in accordance with plan terms, the PBGC program requires PBGC to determine a PBGC-payable benefit, taking into account the detailed limitations under sections 4022 and 4044 of ERISA. PBGC's work often requires years of processing before PBGC can determine final benefit amounts. Clearly PBGC's process for determining title IV benefits contains distinguishing elements not applicable to ongoing plans subject to title I. Lastly, as a government program, PBGC's corrections of overpayments are subject to laws—such as the Federal debt collection procedures and, in some areas, the Payment Integrity Information Act of 2019—which are not applicable to private, ongoing pension plans.</P>
                <P>Notwithstanding the above, PBGC notes that both its current recoupment methodology and the one described in this proposed rule generally conform to the limitations Congress prescribed for ongoing plans in section 301 of SECURE 2.0. The proposed elimination of recoupment on survivor benefits would make this even more so. The special elements and timing in PBGC's determination of title IV benefits, however, prevent PBGC from including a 3-year rule as found in section 206(h)(4)(F) of ERISA.</P>
                <HD SOURCE="HD2">Request for Public Comments</HD>
                <P>Section 301 of the SECURE 2.0 Act added section 206(h) to title I of ERISA to address recoupment of inadvertent overpayments from pension plans under title I of ERISA. PBGC is considering to what extent, if any, section 206(h) interacts with this proposed rule and PBGC's recoupment or recovery of overpayments.</P>
                <P>PBGC requests comments as to whether the rule should address recoupment or recovery by continuing the actions implemented by the former plan administrator of overpayments made before the termination date and, more broadly, where there is a series of overpayments, some of which occurred before the plan termination date.</P>
                <HD SOURCE="HD1">VII. Applicability Date</HD>
                <P>Except as otherwise provided, the amendments described in this proposed rule would apply to recoupment, recovery, or administrative corrections initiated on or after the effective date of the final rule. Recoupment and recovery are initiated by the issuance of a benefit determination or other written notice sent to the participant or beneficiary. Administrative correction is initiated by PBGC action to correct a payment error. The amendments in § 4022.83(b)(1) that would end recoupment at the death of the participant or beneficiary who received the net overpayment would apply for participants and beneficiaries with a date of death on or after the effective date of the final rule. The amendments in § 4022.84(d) that would provide that PBGC will not seek recoupment on a revised benefit determination would apply to revised benefit determinations that are initiated on or after the effective date of the final rule.</P>
                <P>However, some of the amendments codify policies and practices that PBGC has followed for many years, and PBGC will continue to follow these policies and practices in the interim.</P>
                <HD SOURCE="HD1">VIII. Compliance With Rulemaking Guidelines</HD>
                <HD SOURCE="HD2">A. Executive Orders 12866, 13563, and 14192</HD>
                <P>The Office of Management and Budget (OMB) has determined that this rulemaking is not a “significant regulatory action” under Executive Order 12866, as amended by Executive Order 14094. Accordingly, OMB has not reviewed the proposed rule.</P>
                <P>Executive Order 12866 directs 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). Although this proposed rule is not a significant regulatory action, PBGC has examined the economic and policy implications of the rulemaking and has concluded that there would be no significant economic or policy impact because of the proposed rulemaking.</P>
                <P>
                    Some of the proposed amendments mentioned earlier in the preamble would merely codify existing PBGC policies and practices. Making these policies and practices more transparent should decrease uncertainty where PBGC has determined there is a benefit overpayment, reducing, in particular, the potential for a participant to be confused by the recoupment method or repayment process generally. Other amendments simplify the recoupment methodology, notably changing it to a flat rate of 5 percent and waiving recoupment on de minimis net overpayment amounts of $250 or less. PBGC estimates that this change in methodology would not significantly change the overall amount recouped.
                    <SU>7</SU>
                    <FTREF/>
                     A flat rate recoupment would improve overall communications with participants about net overpayments by making recoupment predictable and easier to understand. It would also make administration of recoupment less prone to error, thereby improving PBGC's ability to pay pension benefits on time and accurately.
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         While the amount that PBGC recoups varies year-to-year, overall the amount PBGC recoups is not significant. For example, in calendar year 2023, PBGC recouped $10.9 million from 43,530 participants and beneficiaries. In the same year, PBGC paid $6 billion in benefit payments.
                    </P>
                </FTNT>
                <P>
                    Section 6 of Executive Order 13563 requires agencies to rethink existing regulations by periodically reviewing their regulatory programs for rules that “may be outmoded, ineffective, insufficient, or excessively burdensome.” These rules should be modified, streamlined, expanded, or repealed as appropriate. This proposed rulemaking is consistent with the principles for review under Executive Order 13563 because it would improve PBGC's decades-old regulation on recoupment of benefit overpayments by clarifying and simplifying the 
                    <PRTPAGE P="40960"/>
                    repayment process and providing greater transparency for when PBGC may administratively correct payment errors and recover net overpayments.
                </P>
                <P>
                    Executive Order 14192 requires agencies to identify at least ten existing regulations to be repealed when the agency issues a new regulation and that new incremental costs associated with new regulations shall, to the extent permitted by law, be offset by the elimination of existing costs associated with prior regulations. As OMB explains in its memorandum, “Guidance Implementing Section 3 of Executive Order 14192, Titled `Unleashing Prosperity Through Deregulation,' ” an “Executive Order 14192 regulatory action” is defined as a significant regulatory action (as defined in section 3(f) of Executive Order 12866) that would impose total costs greater than zero.
                    <SU>8</SU>
                    <FTREF/>
                     Because this proposed rule is not a significant regulatory action under Executive Order 12866, it is not an Executive Order 14192 regulatory action. However, PBGC believes this rule, if finalized, qualifies as an “Executive Order 14192 deregulatory action” (as defined in M-25-20), by simplifying the recoupment methodology, improving communications to participants, and promoting transparency, which are intended to reduce any regulatory burden on the public. This includes eliminating a provision, under current rules, for administrative discretion in cases where benefits paid after the termination date exceeded the participant's benefit entitlement under the terminated plan.
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         Office of Management and Budget, Memorandum M-25-20: Guidance Implementing Section 3 of Executive Order 14192, Titled “Unleashing Prosperity Through Deregulation” (Mar. 26, 2025).
                    </P>
                </FTNT>
                <P>Moreover, the proposed rule would satisfy the goal of “reduc[ing] the real resources used by Federal agencies to accomplish their goals,” with estimated annual cost savings to PBGC of $356,000 due to limiting recoupment from surviving beneficiaries. The estimated savings are from letters not sent to participants; time not spent calculating recoupment; and time not spent answering questions from participants. And the proposed rule would further reduce costs on the regulated community, with estimated annual cost savings of $4,480 due to reduced attorney time and fees where a participant disagrees with PBGC's application of recoupment or recovery and uses an attorney in preparing an appeal. The proposed rule's switch to a flat-rate methodology, its removal of the ambiguous discretionary provision, and its clarifications regarding when PBGC will use recovery instead of recoupment (currently described only in internal agency manuals), will reduce attorney review time and the need to obtain documents beyond the regulation.</P>
                <HD SOURCE="HD2">B. Regulatory Flexibility Act</HD>
                <P>This rulemaking affects only individuals. Therefore, PBGC certifies that, if adopted, the amendments will not have a significant economic effect on a substantial number of small entities. Accordingly, as provided in section 605(b) of the Regulatory Flexibility Act, sections 603 and 604 do not apply.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 29 CFR Part 4022</HD>
                    <P>Employee benefit plans, Pension insurance, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <P>For the reasons stated in the preamble, PBGC proposes to amend 29 CFR part 4022 to read as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 4022—BENEFITS PAYABLE IN TERMINATED SINGLE-EMPLOYER PLANS</HD>
                </PART>
                <AMDPAR>1. The authority citation for part 4022 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>29 U.S.C. 1302, 1322, 1322b, 1341(c)(3)(D), and 1344.</P>
                </AUTH>
                <AMDPAR>2. Revise subpart E to read as follows:</AMDPAR>
                <SUBPART>
                    <HD SOURCE="HED">SUBPART E—PBGC RECOUPMENT AND REIMBURSEMENT OF BENEFIT OVERPAYMENTS AND UNDERPAYMENTS</HD>
                </SUBPART>
                <CONTENTS>
                    <SECHD>Sec.</SECHD>
                    <SECTNO>4022.81</SECTNO>
                    <SUBJECT>Correction of benefit overpayments and underpayments—in general.</SUBJECT>
                    <SECTNO>4022.82</SECTNO>
                    <SUBJECT>Netting benefit overpayments and underpayments.</SUBJECT>
                    <SECTNO>4022.83</SECTNO>
                    <SUBJECT>Recoupment of benefit overpayments—in general.</SUBJECT>
                    <SECTNO>4022.84</SECTNO>
                    <SUBJECT>Recoupment—exceptions.</SUBJECT>
                    <SECTNO>4022.85</SECTNO>
                    <SUBJECT>Recovery of benefit overpayments.</SUBJECT>
                    <SECTNO>4022.86</SECTNO>
                    <SUBJECT>Administrative correction.</SUBJECT>
                    <SECTNO>4022.87</SECTNO>
                    <SUBJECT>Reimbursement of benefit underpayments.</SUBJECT>
                </CONTENTS>
                <SECTION>
                    <SECTNO>§ 4022.81</SECTNO>
                    <SUBJECT>Correction of benefit overpayments and underpayments—in general.</SUBJECT>
                    <P>This subpart sets forth rules about PBGC's responses to overpayments and underpayments of benefits of participants and beneficiaries in plans of which PBGC is trustee. PBGC's responses include recoupment, recovery, administrative correction, and reimbursement. This subpart is not a complete description of options and methods that may be available to PBGC.</P>
                </SECTION>
                <SECTION>
                    <SECTNO>§ 4022.82</SECTNO>
                    <SUBJECT>Netting benefit overpayments and underpayments.</SUBJECT>
                    <P>
                        (a) 
                        <E T="03">Amount to be recouped or reimbursed.</E>
                         In order to determine the amount to be recouped from, or reimbursed to, a participant or beneficiary, PBGC will calculate a monthly account balance for each month ending after the termination date. PBGC will start with a balance of zero as of the end of the calendar month ending immediately before the termination date and determine the account balance as of the end of each month thereafter as follows:
                    </P>
                    <P>
                        (1) 
                        <E T="03">Debit for overpayments.</E>
                         PBGC will subtract from the account balance the amount of overpayments made in that month. Only overpayments made on or after the latest of the proposed termination date, the termination date, or, if no notice of intent to terminate was issued, the date on which proceedings to terminate the plan are instituted pursuant to section 4042 of ERISA will be included.
                    </P>
                    <P>
                        (2) 
                        <E T="03">Credit for underpayments.</E>
                         PBGC will add to the account balance the amount of underpayments made in that month. Only underpayments made on or after the termination date will be included.
                    </P>
                    <P>
                        (3) 
                        <E T="03">PPA 2006 bankruptcy termination.</E>
                         The provisions of paragraphs (a)(1) and (2) of this section regarding the overpayments and underpayments that will be included in the account balance apply regardless of whether the termination is a PPA 2006 bankruptcy termination.
                    </P>
                    <P>
                        (b) 
                        <E T="03">Credit for interest on net underpayments.</E>
                         If at the end of a month there is a positive account balance (a net underpayment), PBGC will add to the account balance interest thereon for that month using—
                    </P>
                    <P>(1) For months after May 1998, the applicable Federal mid-term rate (as determined by the Secretary of the Treasury pursuant to section 1274(d)(1)(C)(ii) of the Code) for that month (or, where the rate for a month is not available at the time PBGC calculates the amount to be recouped or reimbursed, the most recent month for which the rate is available) based on monthly compounding; or</P>
                    <P>(2) For May 1998 and earlier months, the rate for the last day of the month set forth in table 1 to this paragraph (b)(2).</P>
                    <PRTPAGE P="40961"/>
                    <GPOTABLE COLS="3" OPTS="L2,nj,i1" CDEF="xs50,12,10">
                        <TTITLE>
                            Table 1 to paragraph (
                            <E T="01">b</E>
                            )(2)—Rates Used To Credit Interest on Net Underpayments May 1998 and Earlier
                        </TTITLE>
                        <BOXHD>
                            <CHED H="1">On or after</CHED>
                            <CHED H="1">Before</CHED>
                            <CHED H="1">
                                Rate
                                <LI>(percent)</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">09/02/1974</ENT>
                            <ENT>10/01/1975</ENT>
                            <ENT>8.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">10/01/1975</ENT>
                            <ENT>01/01/1976</ENT>
                            <ENT>7.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">01/01/1976</ENT>
                            <ENT>03/01/1976</ENT>
                            <ENT>8.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">03/01/1976</ENT>
                            <ENT>06/01/1976</ENT>
                            <ENT>7.25</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">06/01/1976</ENT>
                            <ENT>09/01/1976</ENT>
                            <ENT>7.25</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">09/01/1976</ENT>
                            <ENT>12/01/1976</ENT>
                            <ENT>7.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">12/01/1976</ENT>
                            <ENT>03/01/1977</ENT>
                            <ENT>7.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">03/01/1977</ENT>
                            <ENT>06/01/1977</ENT>
                            <ENT>7.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">06/01/1977</ENT>
                            <ENT>12/01/1977</ENT>
                            <ENT>6.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">12/01/1977</ENT>
                            <ENT>03/01/1978</ENT>
                            <ENT>6.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">03/01/1978</ENT>
                            <ENT>06/01/1978</ENT>
                            <ENT>7.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">06/01/1978</ENT>
                            <ENT>09/01/1978</ENT>
                            <ENT>7.25</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">09/01/1978</ENT>
                            <ENT>03/01/1979</ENT>
                            <ENT>7.25</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">03/01/1979</ENT>
                            <ENT>06/01/1979</ENT>
                            <ENT>7.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">06/01/1979</ENT>
                            <ENT>09/01/1979</ENT>
                            <ENT>7.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">09/01/1979</ENT>
                            <ENT>12/01/1979</ENT>
                            <ENT>7.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">12/01/1979</ENT>
                            <ENT>03/01/1980</ENT>
                            <ENT>8.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">03/01/1980</ENT>
                            <ENT>06/01/1980</ENT>
                            <ENT>8.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">06/01/1980</ENT>
                            <ENT>09/01/1980</ENT>
                            <ENT>8.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">09/01/1980</ENT>
                            <ENT>12/01/1980</ENT>
                            <ENT>9.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">12/01/1980</ENT>
                            <ENT>01/01/1981</ENT>
                            <ENT>9.25</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">01/01/1981</ENT>
                            <ENT>02/01/1981</ENT>
                            <ENT>9.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">02/01/1981</ENT>
                            <ENT>04/01/1981</ENT>
                            <ENT>9.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">04/01/1981</ENT>
                            <ENT>06/01/1981</ENT>
                            <ENT>10.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">06/01/1981</ENT>
                            <ENT>07/01/1981</ENT>
                            <ENT>10.25</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">07/01/1981</ENT>
                            <ENT>08/01/1981</ENT>
                            <ENT>10.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">08/01/1981</ENT>
                            <ENT>10/01/1981</ENT>
                            <ENT>10.25</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">10/01/1981</ENT>
                            <ENT>11/01/1981</ENT>
                            <ENT>10.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">11/01/1981</ENT>
                            <ENT>12/01/1981</ENT>
                            <ENT>10.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">12/01/1981</ENT>
                            <ENT>01/01/1982</ENT>
                            <ENT>11.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">01/01/1982</ENT>
                            <ENT>02/01/1982</ENT>
                            <ENT>10.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">02/01/1982</ENT>
                            <ENT>03/01/1982</ENT>
                            <ENT>10.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">03/01/1982</ENT>
                            <ENT>06/01/1982</ENT>
                            <ENT>11.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">06/01/1982</ENT>
                            <ENT>08/01/1982</ENT>
                            <ENT>10.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">08/01/1982</ENT>
                            <ENT>10/01/1982</ENT>
                            <ENT>11.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">10/01/1982</ENT>
                            <ENT>11/01/1982</ENT>
                            <ENT>10.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">11/01/1982</ENT>
                            <ENT>12/01/1982</ENT>
                            <ENT>10.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">12/01/1982</ENT>
                            <ENT>01/01/1983</ENT>
                            <ENT>10.25</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">01/01/1983</ENT>
                            <ENT>02/01/1983</ENT>
                            <ENT>10.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">02/01/1983</ENT>
                            <ENT>04/01/1983</ENT>
                            <ENT>9.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">04/01/1983</ENT>
                            <ENT>06/01/1983</ENT>
                            <ENT>9.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">06/01/1983</ENT>
                            <ENT>09/01/1983</ENT>
                            <ENT>9.25</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">09/01/1983</ENT>
                            <ENT>02/01/1984</ENT>
                            <ENT>9.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">02/01/1984</ENT>
                            <ENT>03/01/1984</ENT>
                            <ENT>9.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">03/01/1984</ENT>
                            <ENT>04/01/1984</ENT>
                            <ENT>9.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">04/01/1984</ENT>
                            <ENT>05/01/1984</ENT>
                            <ENT>9.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">05/01/1984</ENT>
                            <ENT>07/01/1984</ENT>
                            <ENT>10.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">07/01/1984</ENT>
                            <ENT>08/01/1984</ENT>
                            <ENT>10.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">08/01/1984</ENT>
                            <ENT>09/01/1984</ENT>
                            <ENT>10.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">09/01/1984</ENT>
                            <ENT>11/01/1984</ENT>
                            <ENT>10.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">11/01/1984</ENT>
                            <ENT>12/01/1984</ENT>
                            <ENT>10.25</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">12/01/1984</ENT>
                            <ENT>01/01/1985</ENT>
                            <ENT>10.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">01/01/1985</ENT>
                            <ENT>03/01/1985</ENT>
                            <ENT>9.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">03/01/1985</ENT>
                            <ENT>04/01/1985</ENT>
                            <ENT>9.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">04/01/1985</ENT>
                            <ENT>05/01/1985</ENT>
                            <ENT>9.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">05/01/1985</ENT>
                            <ENT>06/01/1985</ENT>
                            <ENT>10.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">06/01/1985</ENT>
                            <ENT>07/01/1985</ENT>
                            <ENT>9.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">07/01/1985</ENT>
                            <ENT>10/01/1985</ENT>
                            <ENT>9.25</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">10/01/1985</ENT>
                            <ENT>01/01/1986</ENT>
                            <ENT>9.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">01/01/1986</ENT>
                            <ENT>02/01/1986</ENT>
                            <ENT>8.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">02/01/1986</ENT>
                            <ENT>04/01/1986</ENT>
                            <ENT>8.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">04/01/1986</ENT>
                            <ENT>05/01/1986</ENT>
                            <ENT>8.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">05/01/1986</ENT>
                            <ENT>10/01/1986</ENT>
                            <ENT>7.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">10/01/1986</ENT>
                            <ENT>11/01/1986</ENT>
                            <ENT>7.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">11/01/1986</ENT>
                            <ENT>12/01/1986</ENT>
                            <ENT>7.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">12/01/1986</ENT>
                            <ENT>03/01/1987</ENT>
                            <ENT>7.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">03/01/1987</ENT>
                            <ENT>06/01/1987</ENT>
                            <ENT>7.25</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">06/01/1987</ENT>
                            <ENT>07/01/1987</ENT>
                            <ENT>7.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">07/01/1987</ENT>
                            <ENT>10/01/1987</ENT>
                            <ENT>7.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">10/01/1987</ENT>
                            <ENT>11/01/1987</ENT>
                            <ENT>8.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">11/01/1987</ENT>
                            <ENT>03/01/1988</ENT>
                            <ENT>8.25</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">03/01/1988</ENT>
                            <ENT>04/01/1988</ENT>
                            <ENT>8.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">04/01/1988</ENT>
                            <ENT>06/01/1988</ENT>
                            <ENT>7.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">06/01/1988</ENT>
                            <ENT>09/01/1988</ENT>
                            <ENT>8.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">09/01/1988</ENT>
                            <ENT>11/01/1988</ENT>
                            <ENT>8.25</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">11/01/1988</ENT>
                            <ENT>04/01/1989</ENT>
                            <ENT>7.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">04/01/1989</ENT>
                            <ENT>06/01/1989</ENT>
                            <ENT>8.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">06/01/1989</ENT>
                            <ENT>08/01/1989</ENT>
                            <ENT>7.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">08/01/1989</ENT>
                            <ENT>09/01/1989</ENT>
                            <ENT>7.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">09/01/1989</ENT>
                            <ENT>10/01/1989</ENT>
                            <ENT>7.25</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">10/01/1989</ENT>
                            <ENT>12/01/1989</ENT>
                            <ENT>7.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">12/01/1989</ENT>
                            <ENT>03/01/1990</ENT>
                            <ENT>7.25</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">03/01/1990</ENT>
                            <ENT>06/01/1990</ENT>
                            <ENT>7.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">06/01/1990</ENT>
                            <ENT>07/01/1990</ENT>
                            <ENT>7.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">07/01/1990</ENT>
                            <ENT>09/01/1990</ENT>
                            <ENT>7.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">09/01/1990</ENT>
                            <ENT>10/01/1990</ENT>
                            <ENT>7.25</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">10/01/1990</ENT>
                            <ENT>11/01/1990</ENT>
                            <ENT>7.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">11/01/1990</ENT>
                            <ENT>12/01/1990</ENT>
                            <ENT>7.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">12/01/1990</ENT>
                            <ENT>01/01/1991</ENT>
                            <ENT>7.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">01/01/1991</ENT>
                            <ENT>03/01/1991</ENT>
                            <ENT>7.25</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">03/01/1991</ENT>
                            <ENT>06/01/1991</ENT>
                            <ENT>7.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">06/01/1991</ENT>
                            <ENT>07/01/1991</ENT>
                            <ENT>6.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">07/01/1991</ENT>
                            <ENT>10/01/1991</ENT>
                            <ENT>7.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">10/01/1991</ENT>
                            <ENT>01/01/1992</ENT>
                            <ENT>6.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">01/01/1992</ENT>
                            <ENT>02/01/1992</ENT>
                            <ENT>6.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">02/01/1992</ENT>
                            <ENT>03/01/1992</ENT>
                            <ENT>6.25</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">03/01/1992</ENT>
                            <ENT>07/01/1992</ENT>
                            <ENT>6.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">07/01/1992</ENT>
                            <ENT>08/01/1992</ENT>
                            <ENT>6.25</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">08/01/1992</ENT>
                            <ENT>09/01/1992</ENT>
                            <ENT>6.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">09/01/1992</ENT>
                            <ENT>12/01/1992</ENT>
                            <ENT>5.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">12/01/1992</ENT>
                            <ENT>01/01/1993</ENT>
                            <ENT>6.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">01/01/1993</ENT>
                            <ENT>02/01/1993</ENT>
                            <ENT>5.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">02/01/1993</ENT>
                            <ENT>03/01/1993</ENT>
                            <ENT>5.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">03/01/1993</ENT>
                            <ENT>04/01/1993</ENT>
                            <ENT>5.25</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">04/01/1993</ENT>
                            <ENT>08/01/1993</ENT>
                            <ENT>5.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">08/01/1993</ENT>
                            <ENT>10/01/1993</ENT>
                            <ENT>4.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">10/01/1993</ENT>
                            <ENT>11/01/1993</ENT>
                            <ENT>4.25</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">11/01/1993</ENT>
                            <ENT>01/01/1994</ENT>
                            <ENT>4.25</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">01/01/1994</ENT>
                            <ENT>04/01/1994</ENT>
                            <ENT>4.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">04/01/1994</ENT>
                            <ENT>05/01/1994</ENT>
                            <ENT>4.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">05/01/1994</ENT>
                            <ENT>07/01/1994</ENT>
                            <ENT>5.25</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">07/01/1994</ENT>
                            <ENT>08/01/1994</ENT>
                            <ENT>5.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">08/01/1994</ENT>
                            <ENT>09/01/1994</ENT>
                            <ENT>5.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">09/01/1994</ENT>
                            <ENT>11/01/1994</ENT>
                            <ENT>5.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">11/01/1994</ENT>
                            <ENT>12/01/1994</ENT>
                            <ENT>6.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">12/01/1994</ENT>
                            <ENT>01/01/1995</ENT>
                            <ENT>6.25</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">01/01/1995</ENT>
                            <ENT>04/01/1995</ENT>
                            <ENT>6.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">04/01/1995</ENT>
                            <ENT>05/01/1995</ENT>
                            <ENT>5.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">05/01/1995</ENT>
                            <ENT>07/01/1995</ENT>
                            <ENT>5.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">07/01/1995</ENT>
                            <ENT>09/01/1995</ENT>
                            <ENT>4.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">09/01/1995</ENT>
                            <ENT>10/01/1995</ENT>
                            <ENT>5.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">10/01/1995</ENT>
                            <ENT>12/01/1995</ENT>
                            <ENT>4.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">12/01/1995</ENT>
                            <ENT>02/01/1996</ENT>
                            <ENT>4.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">02/01/1996</ENT>
                            <ENT>04/01/1996</ENT>
                            <ENT>4.25</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">04/01/1996</ENT>
                            <ENT>05/01/1996</ENT>
                            <ENT>4.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">05/01/1996</ENT>
                            <ENT>08/01/1996</ENT>
                            <ENT>5.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">08/01/1996</ENT>
                            <ENT>11/01/1996</ENT>
                            <ENT>5.25</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">11/01/1996</ENT>
                            <ENT>12/01/1996</ENT>
                            <ENT>5.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">12/01/1996</ENT>
                            <ENT>01/01/1997</ENT>
                            <ENT>4.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">01/01/1997</ENT>
                            <ENT>02/01/1997</ENT>
                            <ENT>4.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">02/01/1997</ENT>
                            <ENT>03/01/1997</ENT>
                            <ENT>4.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">03/01/1997</ENT>
                            <ENT>04/01/1997</ENT>
                            <ENT>5.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">04/01/1997</ENT>
                            <ENT>05/01/1997</ENT>
                            <ENT>4.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">05/01/1997</ENT>
                            <ENT>06/01/1997</ENT>
                            <ENT>5.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">06/01/1997</ENT>
                            <ENT>08/01/1997</ENT>
                            <ENT>5.25</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">08/01/1997</ENT>
                            <ENT>09/01/1997</ENT>
                            <ENT>4.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">09/01/1997</ENT>
                            <ENT>10/01/1997</ENT>
                            <ENT>4.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">10/01/1997</ENT>
                            <ENT>11/01/1997</ENT>
                            <ENT>4.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">11/01/1997</ENT>
                            <ENT>01/01/1998</ENT>
                            <ENT>4.50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">01/01/1998</ENT>
                            <ENT>06/01/1998</ENT>
                            <ENT>4.25</ENT>
                        </ROW>
                    </GPOTABLE>
                    <P>
                        (c) 
                        <E T="03">No interest on net overpayments.</E>
                         If at the end of a month there is a negative account balance (a net overpayment), there will be no interest adjustment for that month.
                    </P>
                </SECTION>
                <SECTION>
                    <SECTNO>§ 4022.83</SECTNO>
                    <SUBJECT>Recoupment of benefit overpayments—in general.</SUBJECT>
                    <P>
                        (a) 
                        <E T="03">When recoupment applies.</E>
                         Recoupment is the practice of reducing future periodic benefit payments from PBGC to a participant or beneficiary to correct a net overpayment of benefits to the participant or beneficiary as calculated under § 4022.82. Recoupment is available at any time PBGC determines that—
                    </P>
                    <P>(1) A participant's or beneficiary's account balance is a net overpayment, and the participant or beneficiary is, as of the benefit determination date or if later as of the time the net overpayment is determined, entitled to receive future benefit payments; and</P>
                    <P>(2) The net overpayment is greater than the “de minimis net overpayment amount” defined for purposes of this part as $250. PBGC may, in its discretion, decide not to recoup additional net overpayment amounts that it determines to be de minimis.</P>
                    <P>
                        (b) 
                        <E T="03">How recoupment works.</E>
                         A net overpayment is recouped by reducing by 5 percent each periodic benefit payment from PBGC to a participant or beneficiary until the earliest of when—
                    </P>
                    <P>(1) The participant or beneficiary dies;</P>
                    <P>(2) The amount remaining to be recouped is less than 5 percent of the participant's or beneficiary's benefit payment; or</P>
                    <P>(3) The net overpayment is repaid in full.</P>
                    <P>
                        (c) 
                        <E T="03">Effect of recoupment.</E>
                         When recoupment ends as described in paragraph (b) of this section, the recoupment constitutes full satisfaction of debt for overpayment of the recoverable amount.
                    </P>
                    <P>
                        (d) 
                        <E T="03">Notice of recoupment.</E>
                         Before recouping, PBGC will provide a notice to the participant or beneficiary of the amount of the net overpayment and of the amount of the reduced benefit computed under this section.
                        <PRTPAGE P="40962"/>
                    </P>
                    <P>
                        (e) 
                        <E T="03">Recoupment from surviving beneficiaries.</E>
                         As provided in paragraph (b)(1) of this section, recoupment of an overpayment made to a participant does not continue to the surviving spouse or any other surviving beneficiary.
                    </P>
                    <P>
                        (f) 
                        <E T="03">Repayment of a net overpayment.</E>
                         PBGC may accept repayment ahead of the recoupment schedule.
                    </P>
                </SECTION>
                <SECTION>
                    <SECTNO>§ 4022.84</SECTNO>
                    <SUBJECT>Recoupment—exceptions.</SUBJECT>
                    <P>
                        (a) 
                        <E T="03">Fairness.</E>
                         In exercising its discretion under this subpart, PBGC will treat like cases in like manner.
                    </P>
                    <P>
                        (b) 
                        <E T="03">Higher recoupment rate.</E>
                         PBGC may recoup at a rate higher than the 5 percent recoupment rate provided in § 4022.83(b) or use recovery under part 4903 of this chapter in appropriate circumstances, such as—
                    </P>
                    <P>(1) Where benefit payments were made based on false information, error, or omission by the participant or beneficiary that materially affected the benefit amount, benefit entitlement, or eligibility;</P>
                    <P>(2) Where PBGC has reason to believe that the person who received a benefit overpayment knew or should have known that the payment was made in error and failed to notify PBGC of the error; or</P>
                    <P>(3) Where there is a settlement agreement that reduces the participant's or beneficiary's benefit payments.</P>
                    <P>
                        (c) 
                        <E T="03">No payments to recoup against.</E>
                         Where no future benefit stream exists as of the benefit determination date or if later as of the time the net overpayment is determined, PBGC may, in its discretion, seek recovery under part 4903 of this chapter.
                    </P>
                    <P>
                        (d) 
                        <E T="03">Revised benefit determinations.</E>
                         If a participant's or beneficiary's monthly benefit amount payable going forward is decreased by a revised benefit determination, PBGC will not increase the amount of the net overpayment to be recouped, except in appropriate circumstances, such as where the circumstances in paragraphs (b)(1) through (3) of this section exist, or in the case of a post-benefit determination qualified domestic relations order.
                    </P>
                    <P>
                        (e) 
                        <E T="03">De minimis net overpayments and appeals.</E>
                         If a participant or beneficiary has a net overpayment that is not zero and that is equal to or less than the de minimis net overpayment amount described in § 4022.83(a)(2), and the net overpayment increases because unadjusted benefit payments continue during the pendency of the participant's or beneficiary's appeal to the PBGC Appeals Board, PBGC nevertheless will regard the net overpayment as not having increased during the pendency of such appeal.
                    </P>
                </SECTION>
                <SECTION>
                    <SECTNO>§ 4022.85</SECTNO>
                    <SUBJECT>Recovery of benefit overpayments.</SUBJECT>
                    <P>
                        (a) 
                        <E T="03">Recovery—in general.</E>
                         This section deals generally with the scope of recovery for net overpayments. Under § 4903.2 of this chapter, recovery applies to the collection of debts owed to PBGC other than those subject to recoupment. As specified in § 4022.84, PBGC may combine recovery with recoupment in exceptional cases.
                    </P>
                    <P>
                        (b) 
                        <E T="03">Recovery; cases when sought.</E>
                         PBGC generally will seek recovery in cases where:
                    </P>
                    <P>(1) Benefit payments were made to a participant or beneficiary after an unambiguous payment end date that was communicated to the participant or beneficiary by a plan administrator of the terminated plan or PBGC.</P>
                    <P>(2) Benefit payments were made to a participant or beneficiary based on false information, error, or omission by the participant or beneficiary that materially affected the benefit amount, benefit entitlement, or eligibility.</P>
                    <P>(3) PBGC has reason to believe that the person who received a benefit overpayment knew or should have known that the payment was made in error and failed to notify PBGC of the error.</P>
                    <P>
                        (c) 
                        <E T="03">Payments after death.</E>
                         Where benefit payments are made after death and PBGC is unable to obtain the funds through administrative correction, PBGC generally seeks return of the funds under part 4903 of this chapter from the financial institution, estate, or other person holding the overpayment.
                    </P>
                </SECTION>
                <SECTION>
                    <SECTNO>§ 4022.86</SECTNO>
                    <SUBJECT>Administrative correction.</SUBJECT>
                    <P>
                        (a) 
                        <E T="03">Administrative correction—in general.</E>
                         Administrative correction refers to rectifying payment errors such as duplicate payments, clerical or arithmetic errors, payments made after death, or payments to the incorrect account or payee.
                    </P>
                    <P>
                        (b) 
                        <E T="03">Administrative correction methods.</E>
                         PBGC will seek to administratively correct payment errors promptly through methods such as stop payment orders, reclamation or reversal of electronic payments, or delaying or suspending temporarily benefit payments.
                    </P>
                    <P>
                        (c) 
                        <E T="03">Unsuccessful administrative correction.</E>
                         If PBGC is unable to administratively correct payment errors, any excess payment constitutes a debt to the Federal Government and PBGC generally seeks recovery under part 4903 of this chapter.
                    </P>
                </SECTION>
                <SECTION>
                    <SECTNO>§ 4022.87</SECTNO>
                    <SUBJECT>Reimbursement of benefit underpayments.</SUBJECT>
                    <P>
                        (a) 
                        <E T="03">Reimbursement of benefit underpayments.</E>
                         At any time PBGC determines that a participant's or beneficiary's account balance is a net underpayment as calculated under § 4022.82, PBGC will reimburse the participant or beneficiary for the net underpayment in a single payment.
                    </P>
                    <P>
                        (b) 
                        <E T="03">Death of participant.</E>
                         If PBGC determines that, at the time of a participant's death, there was a net underpayment to the participant—
                    </P>
                    <P>
                        (1) 
                        <E T="03">Future annuity payments.</E>
                         If the benefit is in the form of a joint-and-survivor or other annuity under which payments may continue after the participant's death, PBGC will pay the underpayment to the person who is receiving survivor benefits; for this purpose, if the person receiving survivor benefits is an alternate payee under a qualified domestic relations order, PBGC will treat the benefit as if payments do not continue after the participant's death (see paragraph (b)(2) of this section).
                    </P>
                    <P>
                        (2) 
                        <E T="03">No future annuity payments.</E>
                         If the benefit is not in the form of a joint-and-survivor or other annuity (
                        <E T="03">e.g.,</E>
                         a certain-and-continuous annuity) under which payments may continue after the participant's death or although the benefit is in such a form payments do not continue after the participant's death (
                        <E T="03">i.e.,</E>
                         in the case of a joint-and-survivor annuity, the person designated to receive survivor benefits predeceased the participant or, in the case of another annuity under which payments may continue after the participant's death the participant died with no payments owed for future periods), PBGC will pay the underpayment to the person determined under the rules in §§ 4022.91 through 4022.95.
                    </P>
                </SECTION>
                <SIG>
                    <NAME>Janet Dhillon,</NAME>
                    <TITLE>Director, Pension Benefit Guaranty Corporation.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13639 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7709-02-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <CFR>40 CFR Parts 174 and 180</CFR>
                <DEPDOC>[EPA-HQ-OPP-2026-0332; FRL-13201-04-OCSPP]</DEPDOC>
                <SUBJECT>Receipt of Pesticide Petitions Filed for Residues of Pesticide Chemicals in or on Various Commodities—April 2026</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of filing of petitions and request for comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This document announces the Agency's receipt of and solicits public 
                        <PRTPAGE P="40963"/>
                        comment on initial filings of pesticide petitions requesting the establishment or modification of regulations for residues of pesticide chemicals in or on various commodities. The Agency is providing this notice in accordance with the Federal Food, Drug, and Cosmetic Act (FFDCA). EPA uses the month and year in the title to identify when the Agency compiled the petitions identified in this notice of filing. Unit II. of this document identifies certain petitions received in 2025 and 2026 that are currently being evaluated by EPA, along with information about each petition, including who submitted the petition and the requested action.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before August 5, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit your comments, identified by docket identification (ID) number and the pesticide petition (PP) of interest identified in Unit II. of this document, online at 
                        <E T="03">https://www.regulations.gov.</E>
                         Follow the online instructions for submitting comments. Do not submit electronically any information you consider to be Confidential Business Information (CBI) or other information whose disclosure is restricted by statute. Additional instructions on commenting on and visiting the docket, along with more information about dockets generally, are available at 
                        <E T="03">https://www.epa.gov/dockets.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Each application summary in Unit II. specifies a contact division. The appropriate division contacts are identified as follows:</P>
                    <P>
                        • RD (Registration Division) (Mail Code 7505T); Charles Smith; main telephone number: (202) 566-1030; email address: 
                        <E T="03">RDFRNotices@epa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Executive Summary</HD>
                <HD SOURCE="HD2">A. Does this action apply to me?</HD>
                <P>This action provides information that is directed to the public in general.</P>
                <HD SOURCE="HD2">B. What is the Agency's authority for taking this action?</HD>
                <P>
                    EPA regulations for residues of pesticide chemicals in or on various food commodities are established under section 408 of the Federal Food, Drug, and Cosmetic Act (FFDCA), 21 U.S.C. 346a. FFDCA section 408(d)(3), 21 U.S.C. 346a(d)(3), requires EPA to publish a notice of receipt of these petitions in the 
                    <E T="04">Federal Register</E>
                     and provide an opportunity for public comment on the requests.
                </P>
                <HD SOURCE="HD2">C. What action is the Agency taking?</HD>
                <P>As specified in FFDCA section 408(d)(3), 21 U.S.C. 346a(d)(3), EPA is publishing notice of the receipt of pesticide petitions filed under FFDCA section 408 that request the establishment or modification of regulations for residues of pesticide chemicals in or on various food commodities. The Agency is taking public comments on the requests before responding to the petitioner. Pursuant to 40 CFR 180.7(f), a summary of the petition identified in this document, prepared by the petitioner, is included in a docket. EPA has determined that the pesticide petitions described in this document contain data or information prescribed in FFDCA section 408(d)(2), 21 U.S.C. 346a(d)(2), and 40 CFR 180.7(b); however, EPA has not fully evaluated the sufficiency of the submitted data at this time or whether the data supports granting the pesticide petitions. After considering the public comments, EPA intends to evaluate whether and what action may be warranted. Additional data may be needed before EPA can make a final determination on these pesticide petitions.</P>
                <P>
                    Based upon review of the data supporting these petitions and in accordance with its authority under FFDCA section 408(d)(4)(A)(i), EPA may establish a final tolerance or tolerance exemption that “may vary from that sought by the petitioner.” For example, EPA may determine that it is appropriate to vary the commodity name for consistency with EPA's Food and Feed Commodity Vocabulary, which is located here 
                    <E T="03">https://www.epa.gov/pesticide-tolerances/food-and-feed-commodity-vocabulary,</E>
                     or vary the tolerance level based on available data, harmonization interests, or the trailing zeros policy. In addition, when evaluating a petition's requests for a tolerance or exemption, EPA will consider how use of the pesticide on a crop for which a tolerance is requested may result in residues in or on commodities related to that requested commodity (
                    <E T="03">e.g.,</E>
                     whether use on sugar beets for which a tolerance was requested on sugar beet root also requires a tolerance on sugar beet tops or whether use on a cereal grain for which a grain tolerance was requested also requires a tolerance on related animal feed commodities derived from that cereal grain). Public commenters should consider the possibility of such revisions in preparing comments on these petitions.
                </P>
                <HD SOURCE="HD2">D. What should I consider as I prepare my comments for EPA?</HD>
                <P>
                    1. 
                    <E T="03">Submitting CBI.</E>
                     Do not submit CBI to EPA through 
                    <E T="03">https://www.regulations.gov</E>
                     or email. If you wish to include CBI in your comment, please follow the applicable instructions at 
                    <E T="03">https://www.epa.gov/dockets/commenting-epa-dockets#rules</E>
                     and clearly mark the information that you claim to be CBI. In addition to one complete version of the comment that includes CBI, a copy of the comment without CBI must be submitted for inclusion in the public docket. Information marked as CBI will not be disclosed except in accordance with procedures set forth in 40 CFR part 2.
                </P>
                <P>
                    2. 
                    <E T="03">Tips for preparing your comments.</E>
                     When preparing and submitting your comments, see the commenting tips at 
                    <E T="03">https://www.epa.gov//epa-dockets.</E>
                </P>
                <HD SOURCE="HD1">II. Petitions Received</HD>
                <P>This unit provides the following information about the petitions:</P>
                <P>• The Pesticide Petition (PP) Identification (IN) number.</P>
                <P>• EPA docket ID number for the petition.</P>
                <P>
                    • Information about the petition (
                    <E T="03">i.e.,</E>
                     name of the petitioner, name of the pesticide chemical residue and the commodities for which a tolerance or exemption is sought).
                </P>
                <P>• The analytical method available to detect and measure the pesticide chemical residue or the petitioner's statement about why such a method is not needed; and</P>
                <P>• The division to contact for that petition.</P>
                <P>Additional information on the petitions may be obtained through the petition summaries that were prepared by the petitioners pursuant to 21 U.S.C. 346a(d)(2)(A)(i)(I) and 40 CFR 180.7(b)(1), which are included in the docket for the petition as identified in this unit.</P>
                <P>
                    • 
                    <E T="03">PP IN-12499.</E>
                     (EPA-HQ-OPP-2025-3954). Evonik Corporation, 2 Turner Place, Piscataway, NJ 08854, requests to establish an exemption from the requirement of a tolerance for residues of Silane, trimethoxyoctyl-, hydrolysis products with silica (CAS Reg. No. 92797-60-9) when used as a pesticide inert ingredient (dispersant) in pesticide formulations under 40 CFR 180.920. The petitioner believes no analytical method is needed because it is not required for an exemption from the requirement of a tolerance. 
                    <E T="03">Contact:</E>
                     RD.
                </P>
                <P>
                    • 
                    <E T="03">PP 5E9203.</E>
                     (EPA-HQ-OPP-2026-0628). Valent U.S.A. LLC, 4600 Norris Canyon Road, San Ramon, CA 94583, 
                    <PRTPAGE P="40964"/>
                    requests to establish a tolerance in 40 CFR part 180 for residues of the fungicide mandestrobin in or on cherry subgroup 12-12A at 3.0 parts per million (ppm) and peach subgroup 12-12B at 2.0 ppm. LC-MS/MS (liquid chromatography-tandem mass spectrometry) methods are used to measure and evaluate the chemical mandestrobin. 
                    <E T="03">Contact:</E>
                     RD.
                </P>
                <P>
                    • 
                    <E T="03">PP 5E9215.</E>
                     (EPA-HQ-OPP-2026-1783). Syngenta Crop Protection, LLC, P.O. Box 18300, Greensboro, NC 27419, requests to establish a tolerance in 40 CFR part 180 for residues of the fungicide, nematocide cyclobutrifluram in or on coffee at 0.15 ppm and banana at 0.05. The GRM076.07A and GRM076.11A methods is/are used to measure and evaluate the chemical cyclobutrifluram. 
                    <E T="03">Contact:</E>
                     RD.
                </P>
                <P>
                    • 
                    <E T="03">PP 5E9225.</E>
                     (EPA-HQ-OPP-2025-1905). Interregional Research Project Number 4 (IR-4) Project Headquarters, NC State University, 1730 Varsity Drive, Venture IV, Suite 210, Raleigh, NC 27606, requests to establish a tolerance in 40 CFR part 180 for residues of the herbicide cycloate in or on quinoa at 1.0 ppm. The LC-MS/MS and GC-MS/MS methods are used to measure and evaluate the chemical cycloate. 
                    <E T="03">Contac</E>
                    t: RD.
                </P>
                <P>
                    • 
                    <E T="03">PP 5F9192.</E>
                     (EPA-HQ-OPP-2025-2500). Bayer CropScience LLC, 800 N. Lindbergh Blvd., St. Louis, MO 63167, requests to establish tolerances in 40 CFR part 180 for residues of the herbicide bromoxynil in or on the raw agricultural commodities crop subgroup 20A (rapeseed, except flax, seed), crop subgroup 6-22E (vegetable, legume, pulse, bean, dried shelled, except soybean), and crop subgroup 6-22F (vegetable, legume, pulse, pea, dried shelled) at 0.01 ppm. The (GLC/MCD), (GC/ECD), or GC/MCD methods are used to measure and evaluate the chemical bromoxynil. 
                    <E T="03">Contact:</E>
                     RD.
                </P>
                <P>
                    • 
                    <E T="03">PP 5F9212.</E>
                     (EPA-HQ-OPP-2026-1783). Syngenta Crop Protection, LLC, P.O. Box 18300, Greensboro, NC 27419, requests to establish a tolerance in 40 CFR part 180 for residues of the fungicide, nematocide cyclobutrifluram in or on tuberous and corm vegetables (except ginseng) (CSG 1A) at 1.0 ppm; tuberous and corm (CSG 1C) at 0.2 ppm; tuberous and corm (CSG 1D) at 1.0 ppm; vegetable, leaves of root and tuber (CG2) at 1.5 ppm; bulb vegetables (CG 3-07); onion, bulb (CSG 3-07A) at 0.5 ppm; onion, green (CSG 3-07B) at 0.8 ppm; leafy vegetables (CG 4-16) at 2.0 ppm; brassica, head and stem (CG 5-16) at 0.8 ppm; legume vegetable (CG 6-22) (except soybean); edible podded peas and beans at 2.0m ppm; succulent peas and beans at 2.0 ppm; dried peas and beans at 2.0 ppm; pea and bean, forage/vines at 2.0 ppm; pea and bean, hay at 6.0 ppm; fruiting vegetables (CG 8-10) at 0.7 ppm; cucurbit vegetables (CG 9) at 0.7 ppm; citrus fruit (CG 10-10) at 0.08 ppm; pome fruit (CG 11-10) at 0.05 ppm; stone fruit (CG 12-12) at 0.07 ppm; small fruit vine climbing (except fuzzy kiwifruit) (CSG 13-07F) at 0.08 ppm; low growing berry (CSG 13-7G) (except cranberry) at 0.7 ppm; tree nut (CG 14) at 0.05 ppm; almond hulls at 0.3 ppm; grain, cereal (CG 15-22) at 1.5 ppm; grain, cereal, forage, hay, stover, and straw, group 16-22, forage at 5.0 ppm; grain, cereal, forage, hay, stover, and straw, group 16-22, hay at 6.0 ppm; grain, cereal, forage, hay, stover, and straw, group 16-22, stover at 0.5ppm; grain, cereal, forage, hay, stover, and straw, group 16-22, straw at 0.5ppm; cotton, undelinted seed (CSG 20C) at 2.0 ppm; cotton, gin byproducts at 6.0 ppm; leaf petiole vegetable (CSG 22B) at 0.6 ppm; sugarcane at 0.1 ppm; peanut, nutmeat at 0.2 ppm; peanut, hay at 5.0 ppm; cattle fat at 0.02 ppm; cattle meat at 0.1 ppm; cattle meat byproducts at 0.1 ppm; eggs at 0.1 ppm; goat fat at &lt;0.03 ppm; goat meat at 0.1 ppm; goat meat byproducts at 0.1 ppm; goat liver at 0.5 ppm; goat kidney at 0.09 ppm; hog fat at &lt;0.03 ppm; hog meat at 0.1 ppm; hog meat byproducts at 0.1 ppm; hog liver at 0.5 ppm; hog kidney at 0.09 ppm; horse fat at &lt;0.03 ppm; horse meat at 0.1 ppm; horse meat byproducts at 0.1 ppm; horse liver at 0.5 ppm; horse kidney at 0.09 ppm; milk at 0.3 ppm; poultry fat at &lt;0.03 ppm; poultry meat at 0.1 ppm; poultry meat byproducts at 0.1 ppm; poultry liver at 0.5 ppm; poultry kidney at 0.09 ppm; sheep fat at &lt;0.03 ppm; sheep meat at 0.1 ppm; sheep meat byproducts at 0.1 ppm; sheep liver at 0.5 ppm; sheep kidney at 0.09 ppm; inadvertent tolerances for grass, forage, fodder and hay (CG 17) forage at 5.0 ppm; grass, forage, fodder and hay (CG 17) hay at 6.0 ppm; animal feed, non-grass (CG 18), forage at 4.0 ppm; animal feed, non-grass (CG 18), hay at 8.0 ppm and herb group (CG 25) at 2.0 ppm. The GRM076.07A and GRM076.11A methods is/are used to measure and evaluate the chemical cyclobutrifluram. 
                    <E T="03">Contact:</E>
                     RD.
                </P>
                <P>
                    • 
                    <E T="03">PP 5F9219.</E>
                     (EPA-HQ-OPP-2026-1784) Nissan Chemical Corporation, 5-1, Nihonbashi 2-Chome, Chuo-ku, Tokyo 103-6119, Japan, requests to establish a tolerance in 40 CFR part 180 for residues of the herbicide, iptriazopyrid, as measured by the sum of 1,2,4-Triazolo[4,3-a]pyridine-8-carboxamide, 3-[[(1-methylethyl)sulfonyl] methyl]-N-(5-methyl-1,3,4-oxadiazol-2-yl)-5-(trifluoromethyl)- and 5-methyl-1,3,4-oxadiazol-2-amine, expressed as 1,2,4-Triazolo[4,3-a]pyridine-8-carboxamide, 3-[[(1-methylethyl)sulfonyl]methyl]-N-(5-methyl-1,3,4-oxadiazol-2-yl)-5-(trifluoromethyl)- equivalent in or on rice, grain at 0.60 ppm; rice, straw at 0.02 ppm, cattle, fat at 0.01 ppm; cattle, kidney at 0.10 ppm; cattle, liver at 0.10 ppm; cattle, meat at 0.01 ppm; fish, shellfish, crustacean at 0.04 ppm; goat, fat at 0.01 ppm; goat, kidney at 0.10 ppm; goat, liver at 0.10 ppm; goat, meat at 0.01 ppm; horse, fat at 0.01 ppm; horse, kidney at 0.10 ppm; horse, liver at 0.10 ppm; horse, meat at 0.01 ppm; hog, fat at 0.01 ppm; hog, kidney at 0.08 ppm; hog, liver at 0.08 ppm; hog, meat at 0.01 ppm; milk at 0.01 ppm; poultry, eggs at 0.01 ppm; poultry, fat at 0.01 ppm; poultry, liver at 0.40 ppm; poultry, muscle at 0.01 ppm; sheep, fat at 0.01 ppm; sheep, kidney at 0.10 ppm; sheep, liver at 0.10 ppm; and sheep, meat at 0.01 ppm. Liquid Chromatography-MS/MS is used to measure and evaluate the chemical iptriazopyrid. 
                    <E T="03">Contact:</E>
                     RD
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority: </HD>
                    <P>21 U.S.C. 346a.</P>
                </AUTH>
                <SIG>
                    <DATED>Dated: June 29, 2026.</DATED>
                    <NAME>Edward Messina,</NAME>
                    <TITLE>Director, Office of Pesticide Programs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13557 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                <CFR>47 CFR Part 25</CFR>
                <DEPDOC>[SB Docket No. 25-157; Report No. 3234; FR ID 353423]</DEPDOC>
                <SUBJECT>Petition for Reconsideration of Action in Rulemaking Proceeding</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Petition for reconsideration.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>A Petition for Reconsideration (Petition) has been filed in the Commission's proceeding by Brenna Sparks on behalf of DIRECTV, LLC.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Oppositions to the Petition must be filed on or before July 21, 2026. Replies to oppositions to the Petition must be filed on or before July 31, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Federal Communications Commission, 45 L Street NE, Washington, DC 20554.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Clay DeCell, 202-418-0803.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    This is a summary of the Commission's document, in SB Docket No. 25-157; Report No. 3234, released June 23, 2026. The full text of the Petition can be 
                    <PRTPAGE P="40965"/>
                    accessed online via the Commission's Electronic Comment Filing System at: 
                    <E T="03">http://apps.fcc.gov/ecfs/.</E>
                     The Commission will not send a Congressional Review Act (CRA) submission to Congress or the Government Accountability Office pursuant to the CRA, 5 U.S.C. 801(a)(1)(A), because no rules are being adopted by the Commission.
                </P>
                <P>
                    <E T="03">Subject:</E>
                     Modernizing Spectrum Sharing for Satellite Broadband (SB Docket No. 25-157).
                </P>
                <P>Number of Petitions Filed: 1.</P>
                <SIG>
                    <FP>Federal Communications Commission.</FP>
                    <NAME>Marlene Dortch,</NAME>
                    <TITLE>Secretary, Office of the Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13611 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </PRORULE>
    </PRORULES>
    <VOL>91</VOL>
    <NO>127</NO>
    <DATE>Monday, July 6, 2026</DATE>
    <UNITNAME>Notices</UNITNAME>
    <NOTICES>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="40966"/>
                <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 required 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 5, 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.
                </P>
                <P>An agency may not conduct or sponsor a collection of information unless the collection of information displays a currently valid OMB control number and the agency informs potential persons who are to respond to the collection of information that such persons are not required to respond to the collection of information unless it displays a currently valid OMB control number.</P>
                <HD SOURCE="HD1">Animal and Plant Health Inspection Service</HD>
                <P>
                    <E T="03">Title:</E>
                     Animal Welfare.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     0579-0036.
                </P>
                <P>
                    <E T="03">Summary of Collection:</E>
                </P>
                <P>
                    This is a reinstatement of a previously approved information collection request. Under the Animal Welfare Act (AWA, 7 U.S.C. 2131 
                    <E T="03">et seq.</E>
                    ), the Secretary of Agriculture is authorized to promulgate standards and other requirements governing the humane handling, care, treatment, and transportation of certain animals by dealers, exhibitors, operators of auction sales, research facilities, carriers and intermediate handlers. The Secretary has delegated responsibility for administering the AWA to the U.S. Department of Agriculture's Animal and Plant Health Inspection Service (APHIS), Animal Care.
                </P>
                <P>Definitions, regulations, and standards established under the AWA are contained in 9 CFR parts 1, 2, and 3 (referred to below as the regulations). Part 1 contains definitions for terms used in parts 2 and 3. Part 2 provides administrative requirements and sets forth institutional responsibilities for regulated parties, including licensing requirements for dealers, exhibitors, and operators of auction sales. Dealers, exhibitors, and operators of auction sales are required to comply in all respects with the regulations and standards (9 CFR 2.100(a)) and to allow APHIS officials access their place of business, facilities, animals, and records to inspect for compliance (9 CFR 2.126). Part 3 provides standards for the humane handling, care, treatment, and transportation of covered animals. Part 3 consists of subparts A through E, which contain specific standards for dogs and cats, guinea pigs and hamsters, rabbits, nonhuman primates, and marine mammals, respectively, and subpart F, which sets forth general standards for warm-blooded animals not otherwise specified in part 3.</P>
                <HD SOURCE="HD2">Need and Use of the Information</HD>
                <P>Administering the AWA requires the use of several information collection activities such as license applications and renewals, which now include a request to identify whether the business mailing address is a personal residence or not a personal residence; registration applications and updates; annual reports; acknowledgement of regulations and standards; inspections; requests; notifications; agreements; plans; written program of veterinary care and health records; itineraries; applications and permits; records of acquisition, disposition, or transport of animals; official identification; variances; protocols; health certificates; complaints; marking requirements; and recordkeeping. The information is used to provide APHIS with the data necessary to review and evaluate program compliance by regulated facilities and provide a workable system to administer the requirements of the AWA and intent of Congress without resorting to more detailed and stringent regulations and standards that could be more burdensome to regulated facilities.</P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     381,316.
                </P>
                <P>
                    <E T="03">Frequency of Responses:</E>
                     Recordkeeping; Reporting; Third Party Disclosure: On occasion.
                </P>
                <P>
                    <E T="03">Total Burden Hours:</E>
                     228,953.
                </P>
                <SIG>
                    <NAME>Rachelle Ragland-Greene,</NAME>
                    <TITLE>Departmental Information Collection Clearance Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13618 Filed 7-2-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 required 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.
                    <PRTPAGE P="40967"/>
                </P>
                <P>
                    Comments regarding this information collection received by August 5, 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.
                </P>
                <P>An agency may not conduct or sponsor a collection of information unless the collection of information displays a currently valid OMB control number and the agency informs potential persons who are to respond to the collection of information that such persons are not required to respond to the collection of information unless it displays a currently valid OMB control number.</P>
                <HD SOURCE="HD1">Farm Service Agency</HD>
                <P>
                    <E T="03">Title:</E>
                     Application for Payment of Amounts Due Persons Who Have Died, Disappeared or Declared Incompetent.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     0560-0026.
                </P>
                <P>
                    <E T="03">Summary of Collection:</E>
                     This is a reinstatement of a previously approved information collection request. Representatives or survivors of persons who die, disappear, or are declared incompetent must be afforded a method of obtaining any payment intended for the person. 7 CFR 707 provides that form, FSA-325, to be used as the form of application for person desiring to claim such payments. It is necessary to collect information recorded on FSA-325 to determine whether representatives or survivors of a person are entitled to receive payments earned by a person who dies, disappears, or is declared incompetent before receiving the payments due.
                </P>
                <P>
                    <E T="03">Need and Use of the Information:</E>
                     FSA will collect information using the FSA-325 form to determine if the survivors have rights to the existing payments or to the unpaid portions of the person's payments. Survivors must show proof of death, disappearance, or incompetency.
                </P>
                <P>
                    <E T="03">Description of Respondents:</E>
                     Individuals or households.
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     2,000.
                </P>
                <P>
                    <E T="03">Frequency of Responses:</E>
                     Reporting: Other (when necessary).
                </P>
                <P>
                    <E T="03">Annual Burden Hours:</E>
                     1,000.
                </P>
                <SIG>
                    <NAME>Rachelle Ragland-Greene,</NAME>
                    <TITLE>Departmental Information Collection Clearance Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13589 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3410-05-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBAGY>Farm Service Agency</SUBAGY>
                <DEPDOC>[Docket ID: FSA-2026-0430]</DEPDOC>
                <SUBJECT>Information Collection Request; General Program Administration</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Farm Service Agency, USDA.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; request for comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Paperwork Reduction Act of 1995, the Farm Service Agency (FSA) is requesting comments from all interested individuals and organizations on a revision of a currently approved collection associated with the General Program Administration. In the General Program Administration, the information collected is used to ensure that applicants meet statutory eligibility requirements, loan funds are used for authorized purposes, and the Government's interest in security is adequately protected.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>We will consider comments that we receive by September 4, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>We invite you to submit comments on the notice. You may submit comments by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">http://regulations.gov</E>
                         and search for docket ID FSA-2026-0430. Follow the online instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Lee Nault, Loan Servicing and Properties Management Division, USDA, FSA, Farm Loan Programs, 1400 Independence Ave. SW, Mail Stop 0523, Washington, DC 20250-00523.
                    </P>
                    <P>
                        Comments will be available for inspection online at 
                        <E T="03">http://www.regulations.gov.</E>
                         Copies of the information collection may be requested by contacting Lee Nault (see 
                        <E T="02">For Further Information Contact</E>
                         below). You may also send comments to the Desk Officer for Agriculture, Office of Information and Regulatory Affairs, Office of Management and Budget, Washington, DC 20503.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Lee Nault, (202) 720-6834; email: 
                        <E T="03">Lee.Nault@usda.gov.</E>
                         Persons with disabilities who require alternative means for communication should contact the USDA Target Center at (202) 720-2600 (voice).
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Description of Information Collection Request</HD>
                <P>
                    <E T="03">Title:</E>
                     General Program Administration.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     0560-0238.
                </P>
                <P>
                    <E T="03">Expiration Date of Approval:</E>
                     October 31, 2026.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Revision of a currently approved information collection.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     General Program Administration, as specified in the 7 CFR 761, contains requirements that are applicable to making and servicing direct loans. The information collections are necessary to ensure that applicants meet statutory eligibility requirements, loan funds are used for authorized purposes, and the Federal Government's interest in security is adequately protected. Specific information collection requirements include financial information in the form of a balance sheet and cash flow projection used in loan making and servicing decisions; information needed to establish joint bank accounts in which loan funds, proceeds derived from the sale of loan security and insurance proceeds, may be deposited; collateral pledges from financial institutions when the balance of a supervised bank account will exceed the maximum amount insurable by the Federal Government; and documents that construction plans and specifications to comply with state and local building standards.
                </P>
                <P>The number of respondents, responses, and burden hours show an increase from the last submission. This increase is primarily due to an over increase of program participation. For the prior submission, new loan requests and overall FSA loan caseload numbers had experienced several years of decrease following impacts of COVID-19 and the recovery period on the farming market resulting in projections that were reflective of anticipated further declines in program participation. However, over the last three years, FSA has experienced an increase in new loan activity as well as an increase in the total number of customers remaining in the direct farm loan portfolio. An increase in the number customers remaining in the portfolio will increase the number of required routine loan servicing activities as well as increasing the potential for distressed loan servicing activities. Anticipated respondents, responses, and burden hours have been updated to reflect these changes. For the following estimated total annual burden on respondents, the formula used to calculate the total burden hour is the estimated average time per responses hours multiplied by the estimated total annual responses.</P>
                <P>
                    <E T="03">Estimate of Respondent Burden:</E>
                     Public reporting burden for this collection of information is estimated to average 1.06 hours per response.
                    <PRTPAGE P="40968"/>
                </P>
                <P>
                    <E T="03">Type of Respondents:</E>
                     Individuals or households, business or other for-profit, and farms.
                </P>
                <P>
                    <E T="03">Estimated Annual Number of Respondents:</E>
                     66,041.
                </P>
                <P>
                    <E T="03">Estimated Number of Responses per Respondent:</E>
                     2.33
                </P>
                <P>
                    <E T="03">Estimated Total Annual Responses:</E>
                     153,976.
                </P>
                <P>
                    <E T="03">Estimated Average Time per Responses:</E>
                     1.06 hours.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden on Respondents:</E>
                     163,108 hours.
                </P>
                <P>We are requesting comments on all aspects of this information collection to help us to:</P>
                <P>(1) Evaluate whether the collection of information is necessary for the proper performance of the functions of FSA, including whether the information will have practical utility;</P>
                <P>(2) Evaluate the accuracy of FSA's estimate of burden including the validity of the methodology and assumptions used;</P>
                <P>(3) Enhance the quality, utility, and clarity of the information to be collected;</P>
                <P>(4) Minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology.</P>
                <P>All responses to this notice, including names and addresses when provided, will be summarized and included in the request for OMB approval. All comments will also become a matter of public record.</P>
                <SIG>
                    <NAME>Jared Hagert,</NAME>
                    <TITLE>Acting Administrator, Farm Service Agency.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13606 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3411-E2-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBAGY>Rural Utilities Service</SUBAGY>
                <DEPDOC>[Docket: RUS-26-AGENCY-0133]</DEPDOC>
                <SUBJECT>60-Day Notice of Request for Revision of a Currently Approved Information Collection: OneRD Loan Guarantee Program</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Rural Utilities Service, Department of Agriculture.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Paperwork Reduction Act of 1995 (44 U.S.C. Chapter 35), this notice invites comments on the OneRD Loan Guarantee Program information collection package and announces the Rural Utilities Service intention to request a revision to a currently approved information collection from the Office of Management and Budget (OMB).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments on this notice must be received by September 4, 2026 to be assured of consideration.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments may be submitted by the Federal eRulemaking Portal: Go to 
                        <E T="03">http://www.regulations.gov</E>
                         and, in the “Search Field” box, labeled “Search for Rules, Proposed Rules, Notices, or Supporting Documents,” enter the following docket number: (RUS-26-AGENCY-0133). To submit or view public comments, click the “Documents” tab, then select the following document title: (Notice of Request for Revision of a Currently Approved Information Collection OneRD Loan Guarantee Program) from the “Search Results,” and select the “Comment” button. Before inputting your comments, you may also review the “Commenter's Checklist” (optional). Insert your comments under the “Comment” title, click “Browse” to attach files (if available). Input your email address and select “Submit Comment.” Information on using 
                        <E T="03">Regulations.gov</E>
                        , including instructions for accessing documents, submitting comments, and viewing the docket after the close of the comment period, is available through the site's “FAQ” link.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Lisa Day, Innovation Center, Regulations Management Division, U.S. Department of Agriculture, 1400 Independence Ave., SW, Washington, DC 20250; Tel: 971-313-4750; Email: 
                        <E T="03">Lisa.Day@usda.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>The Office of Management and Budget's regulation (5 CFR 1320) implementing provisions of the Paperwork Reduction Act of 1995 (Pub. L. 104-13) requires that interested members of the public and affected agencies have an opportunity to comment on information collection and recordkeeping activities (see 5 CFR 1320.8(d)). This notice identifies an information collection that the Agency is submitting to OMB for revision.</P>
                <P>Comments are invited on (a) whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility; (b) the accuracy of the agency's estimate of burden including the validity of the methodology and assumption 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 those who are to respond, including the use of appropriate automated, electronic, mechanical, or other technological collection techniques on other forms and information technology.</P>
                <P>
                    <E T="03">Title:</E>
                     OneRD Loan Guarantee Program.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     0572-0155.
                </P>
                <P>
                    <E T="03">Expiration Date of Approval:</E>
                     06/30/2027.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Revision of a currently approved information collection.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Rural Development has a consolidated guaranteed loan regulation that covers four guaranteed loan programs in one regulation (Community Facilities, Water and Waste Disposal, Business and Industry, and Rural Energy for America Program). Rural Development, a mission area of the U.S. Department of Agriculture (USDA), is comprised of three agencies (Rural Utilities Service (RUS), Rural Housing Service (RHS), and Rural Business-Cooperative Service (RBCS)), that together administer loans through the OneRD Guaranteed Loan Program (or Program) pursuant to 7 CFR, Part 5001. Loans are used for water and waste disposal systems, essential community infrastructure such as healthcare, libraries and fire stations, and the development and improvement of businesses and industries in rural communities. The Program encourages lender participation and provides specific guidance in the processing and servicing of guaranteed loans. Revisions to the currently approved collection of information include reconciling recent regulatory revisions codified at 7 CFR 5001 and documenting new electronic filing procedures and reporting procedures.
                </P>
                <P>
                    <E T="03">Estimate of Burden:</E>
                     Public reporting burden for this collection of information is estimated to average 3.84 hours per response.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Public Bodies; Non-Profits; Special Districts; Tribal Organizations.
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     725.
                </P>
                <P>
                    <E T="03">Estimated Number of Responses per Respondent:</E>
                     19.09.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden on Respondents:</E>
                     53,110.75.
                </P>
                <P>Copies of this information collection can be obtained from Lisa Day, Rural Development Innovation Center, Regulations Management Division, at 971-313-4750. All responses to this notice will be summarized and included in the request for OMB approval. All comments will also become a matter of public record.</P>
                <P>
                    All responses to this notice will be summarized and included in the request 
                    <PRTPAGE P="40969"/>
                    for OMB approval. All comments will become a matter of public record.
                </P>
                <SIG>
                    <NAME>Karl Elmshaeuser,</NAME>
                    <TITLE>Administrator, Rural Utilities Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13622 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3410-15-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>International Trade Administration</SUBAGY>
                <DEPDOC>[A-570-026, C-570-027]</DEPDOC>
                <SUBJECT>Certain Corrosion-Resistant Steel Products From the People's Republic of China: Initiation of Circumvention Inquiry on the Antidumping and Countervailing Duty Orders</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Enforcement and Compliance, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In response to requests from Nucor Corporation and Steel Dynamics, Inc. (collectively, the requesters), the U.S. Department of Commerce (Commerce) is initiating a country-wide circumvention inquiry to determine whether certain corrosion-resistant steel products (CORE) from the People's Republic of China (China), completed in Thailand using components produced in China, are circumventing the antidumping duty (AD) and countervailing duty (CVD) orders on CORE from China.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Applicable July 6, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Colton Dulin, AD/CVD Operations, Office II Enforcement and Compliance, International Trade Administration, U.S. Department of Commerce, 1401 Constitution Avenue NW, Washington, DC 20230; telephone: (202) 482-1222.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On February 26, 2026, pursuant to section 781(b) of the Tariff Act of 1930, as amended (the Act), and 19 CFR 351.226(a) and (c), the requesters filed a circumvention inquiry request alleging that CORE completed in Thailand using components manufactured in China is circumventing the AD and CVD orders on CORE from China 
                    <SU>1</SU>
                    <FTREF/>
                     and, accordingly, should be included within the scope of the 
                    <E T="03">Orders.</E>
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See Certain Corrosion-Resistant Steel Products from India, Italy, the People's Republic of China, the Republic of Korea and Taiwan: Amended Final Affirmative Antidumping Determination for India and Taiwan, and Antidumping Duty Orders,</E>
                         81 FR 48390 (July 25, 2016); 
                        <E T="03">see also Certain Corrosion-Resistant Steel Products from India, Italy, the People's Republic of China, the Republic of Korea, and Taiwan: Notice of Correction to the Antidumping Duty Orders,</E>
                         81 FR 58475 (August 25, 2016); and 
                        <E T="03">Certain Corrosion-Resistant Steel Products from India, Italy, Republic of Korea and the People's Republic of China: Countervailing Duty Order,</E>
                         81 FR 48387, (July 25, 2016) (collectively, 
                        <E T="03">Orders</E>
                        ).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See</E>
                         Requesters' Letter, “Request for Circumvention Ruling Pursuant to Section 781(b) of the Tariff Act of 1930,” dated February 26, 2026.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Scope of the Orders</HD>
                <P>
                    The merchandise covered by the scope of the 
                    <E T="03">Orders</E>
                     is CORE from China. For a complete description of the scope of the 
                    <E T="03">Orders, see</E>
                     the Circumvention Initiation Checklist.
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         Checklist, “Certain Corrosion-Resistant Steel Products from the People's Republic of China Order,” dated concurrently with, and hereby adopted by, this notice (Circumvention Initiation Checklist), at Attachment 1.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Merchandise Subject to the Circumvention Inquiry</HD>
                <P>This circumvention inquiry covers CORE completed in Thailand using Chinese-origin components that is subsequently exported from Thailand to the United States.</P>
                <HD SOURCE="HD1">Initiation of Circumvention Inquiry</HD>
                <P>
                    Section 351.226(d) of Commerce's regulations states that if Commerce determines that a request for a circumvention inquiry satisfies the requirements of 19 CFR 351.226(c), then Commerce “will accept the request and initiate a circumvention inquiry.” Section 351.226(c)(1) of Commerce's regulations, in turn, requires that each circumvention inquiry request allege “that the elements necessary for a circumvention determination under section 781 of the Act exist” and be “accompanied by information reasonably available to the interested party supporting these allegations.” The deadline to initiate is typically 30 days after receiving the request from the petitioners; however, the initiation date is being made late because the filing was overlooked in Enforcement and Compliance's Antidumping and Countervailing Duty Centralized Electronic Service System (ACCESS). However, 19 CFR 351.226(d) does not have language which automatically accepts circumvention inquiries if no response is sent within 30 days, also 19 CFR 351.302(b) states Commerce may extend “any time limit established by this part.” 
                    <SU>4</SU>
                    <FTREF/>
                     The requesters allege circumvention exists pursuant to section 781(b) of the Act (
                    <E T="03">i.e.,</E>
                     merchandise completed or assembled in other foreign countries).
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See Goodluck India Limited</E>
                         v. 
                        <E T="03">United States,</E>
                         670 F. Supp. 3d 1353 (CIT 2023).
                    </P>
                </FTNT>
                <P>Section 781(b)(1) of the Act provides that Commerce may find circumvention of an order when merchandise of the same class or kind subject to the order is completed or assembled in a foreign country other than the country to which the order applies. In conducting a circumvention inquiry, under section 781(b)(1) of the Act, Commerce relies on the following criteria: (A) merchandise imported into the United States is of the same class or kind as any merchandise produced in a foreign country that is the subject or an AD or CVD order; (B) before importation into the United States, such imported merchandise is completed or assembled in another foreign country from merchandise which is subject to the order or is produced in the foreign country that is subject to the order; (C) the process of assembly or completion in the foreign country referred to in section (B) is minor or insignificant; (D) the value of the merchandise produced in the foreign country to which the AD or CVD order applies is a significant portion of the total value of the merchandise exported to the United States; and (E) the administering authority determines that action is appropriate to prevent evasion of such order.</P>
                <P>
                    In determining whether the process of assembly or completion in the foreign country is minor or insignificant under section 781(b)(1)(C) of the Act, section 781(b)(2) of the Act directs Commerce to consider: (A) the level of investment in the foreign country; (B) the level of research and development in the foreign country; (C) the nature of the production process in the foreign country; (D) the extent of production facilities in the foreign country; and (E) whether or not the value of the processing performed in the foreign country represents a small proportion of the value of the merchandise imported into the United States. However, no single factor, by itself, controls Commerce's determination of whether the process of assembly or completion in the foreign country is minor or insignificant.
                    <SU>5</SU>
                    <FTREF/>
                     Accordingly, it is Commerce's practice to evaluate each of these five factors as they exist in the foreign country, and to reach an affirmative or negative circumvention determination based on the totality of the circumstances of the particular circumvention inquiry.
                    <SU>6</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         Statement of Administrative Action Accompanying the Uruguay Round Agreements Act, H.R. Doc. No. 103316, Vol. 1 (1994) (SAA), at 893.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See, e.g., Hydrofluorocarbon Blends from the People's Republic of China: Final Affirmative Determination of Circumvention with Respect to R-410B, R-407G, and a Certain Custom Blend from the People's Republic of China,</E>
                         89 FR 56848 (July 11, 2024).
                    </P>
                </FTNT>
                <P>
                    In addition, section 781(b)(3) of the Act sets forth additional factors to 
                    <PRTPAGE P="40970"/>
                    consider in determining whether to include merchandise assembled or completed in a foreign country within the scope of an AD or CVD order. Specifically, Commerce shall take into account such factors as: (A) the pattern of trade, including sourcing patterns; (B) whether the manufacturer or exporter of the merchandise that was shipped to the foreign country is affiliated with the person who, in the foreign country, uses the merchandise to complete or assemble the merchandise which is subsequently imported into the United States; and (C) whether imports of the merchandise into the foreign country have increased after the initiation of the investigation which resulted in the issuance of such order.
                </P>
                <HD SOURCE="HD1">Analysis</HD>
                <P>
                    Based on our analysis of the requesters' circumvention request, Commerce determines that the requesters have satisfied the criteria under 19 CFR 351.226(c) to warrant the initiation of a circumvention inquiry of the 
                    <E T="03">Orders.</E>
                     Thus, pursuant to 19 CFR 351.226(d)(1)(iii), we are initiating the requested circumvention inquiry. For a full discussion of the basis for our decision to initiate the circumvention inquiry, 
                    <E T="03">see</E>
                     the Circumvention Initiation Checklist.
                    <SU>7</SU>
                    <FTREF/>
                     As explained in the Circumvention Initiation Checklist, the information provided by the requesters warrants initiating this circumvention inquiry on a country-wide basis. Commerce has taken this approach in prior circumvention inquiries, where the facts warranted initiation on a country-wide basis.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         Circumvention Initiation Checklist.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See, e.g., Certain Corrosion-Resistant Steel Products from the Republic of Korea and Taiwan: Initiation of Anti- Circumvention Inquiries on the Antidumping Duty and Countervailing Duty Orders,</E>
                         83 FR 37785 (August 2, 2018); 
                        <E T="03">Carbon Steel Butt-Weld Pipe Fittings from the People's Republic of China: Initiation of Anti-Circumvention Inquiry on the Antidumping Duty Order,</E>
                         82 FR 40556, 40560 (August 25, 2017); and 
                        <E T="03">Certain Corrosion-Resistant Steel Products from the People's Republic of China: Initiation of Anti-Circumvention Inquiries on the Antidumping Duty and Countervailing Duty Orders,</E>
                         81 FR 79454, 79458 (November 14, 2016).
                    </P>
                </FTNT>
                <P>Consistent with the approach in the prior circumvention inquiries that were initiated on a country-wide basis, Commerce intends to issue a questionnaire to solicit information from producers and exporters in Thailand concerning their production of CORE and their shipments thereof to the United States.</P>
                <HD SOURCE="HD1">Respondent Selection</HD>
                <P>
                    Commerce intends to base respondent selection on U.S. Customs and Border Protection (CBP) data. Commerce intends to place the CBP data on the record of this proceeding within five days of the publication of this initiation notice, which will be available on ACCESS. ACCESS is available to registered users at 
                    <E T="03">https://access.trade.gov.</E>
                     Comments regarding the CBP data and respondent selection should be submitted within seven days after placement of the CBP data on the record of the inquiry.
                </P>
                <P>Commerce intends to establish a schedule for questionnaire responses after respondent selection. A company's failure to completely respond to Commerce's requests for information may result in the application of partial or total facts available, pursuant to section 776(a) of the Act, which may include adverse inferences, pursuant to section 776(b) of the Act.</P>
                <HD SOURCE="HD1">Suspension of Liquidation</HD>
                <P>
                    Pursuant to 19 CFR 351.226(l)(1), Commerce will notify CBP of the initiation of this circumvention inquiry and direct CBP to continue the suspension of liquidation of entries of products subject to the circumvention inquiry that were already subject to the suspension of liquidation under the 
                    <E T="03">Orders,</E>
                     and to apply the cash deposit rate that would be applicable if the product was determined to be covered by the scope of the 
                    <E T="03">Orders.</E>
                     Should Commerce issue preliminary or final circumvention determinations, Commerce will follow the suspension of liquidation rules under 19 CFR 351.226(l)(2)-(4).
                </P>
                <HD SOURCE="HD1">Notification to Interested Parties</HD>
                <P>
                    In accordance with 19 CFR 351.226(d) and section 781(b) of the Act, Commerce determines that the requesters' request for a circumvention inquiry satisfies the requirements of 19 CFR 351.226(c). Accordingly, Commerce is notifying all interested parties of the initiation of this circumvention inquiry to determine whether CORE from Thailand using components manufactured in China is circumventing the 
                    <E T="03">Orders.</E>
                     In addition, we have included a description of the products that are the subject of this inquiry, and an explanation of the reasons for Commerce's decision to initiate this inquiry as provided above and in the accompanying Circumvention Initiation Checklist.
                    <SU>9</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See</E>
                         Circumvention Initiation Checklist.
                    </P>
                </FTNT>
                <P>
                    In accordance with 19 CFR 351.226(e)(1), Commerce intends to issue its preliminary circumvention determination within 150 days from the date of publication of the notice of initiation of a circumvention inquiry in the 
                    <E T="04">Federal Register</E>
                    . Furthermore, in accordance with section 781(f) of the Act and 19 CFR 351.226(e)(2), unless the circumvention inquiry is rescinded, in whole or in part, or extended, Commerce intends to issue its final determination within 300 days from the date of publication of the notice of initiation of the circumvention inquiry in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <P>This notice is published in accordance with section 781(b) of the Act and 19 CFR 351.226(d)(1)(iii).</P>
                <SIG>
                    <DATED>Dated: June 15, 2026.</DATED>
                    <NAME>Christopher Abbott,</NAME>
                    <TITLE>Deputy Assistant Secretary for Policy and Negotiations, performing the non-exclusive functions and duties of the Assistant Secretary for Enforcement and Compliance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13607 Filed 7-2-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>
                <DEPDOC>[C-721-002]</DEPDOC>
                <SUBJECT>Steel Concrete Reinforcing Bar From Algeria: Countervailing Duty Order</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Enforcement and Compliance, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Based on affirmative final determination by the U.S. Department of Commerce (Commerce), Commerce is issuing the countervailing duty (CVD) order on steel concrete reinforcing bar (rebar) from Algeria.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Applicable July 6, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Henry Wolfe or Shane Subler, AD/CVD Operations, Office VIII, Enforcement and Compliance, International Trade Administration, U.S. Department of Commerce, 1401 Constitution Avenue NW, Washington, DC 20230; telephone: (202) 482-0574 or (202) 482-6241, respectively.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    In accordance with sections 705(d) and 777(i) of the Tariff Act of 1930, as amended (the Act), on March 27, 2026, Commerce published its affirmative final determination that countervailable subsidies are being provided to producers and exporters of rebar from Algeria.
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See Steel Concrete Reinforcing Bar from Algeria: Final Affirmative Countervailing Duty Determination,</E>
                         91 FR 14808 (March 27, 2026) (
                        <E T="03">Final Determination</E>
                        ).
                    </P>
                </FTNT>
                <P>
                    On May 18, 2026, pursuant to section 701(c) of the Act, the ITC notified Commerce of its closure of the ITC CVD investigation of steel concrete 
                    <PRTPAGE P="40971"/>
                    reinforcing bar from Algeria.
                    <SU>2</SU>
                    <FTREF/>
                     The ITC stated that the Office of the United States Trade Representative has advised the ITC of its determination that Algeria is not a Subsidies Agreement country as described under section 701(b) of the Act.
                    <SU>3</SU>
                    <FTREF/>
                     As such, the ITC did not make a final determination for the countervailing duty investigation concerning steel concrete reinforcing bar from Algeria.
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See</E>
                         ITC's Letter, “Closure of Investigation,” dated May 18, 2026.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See Status of Algeria Under the Tariff Act of 1930, as Amended,</E>
                         90 FR 34334 (July 21, 2025).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Scope of the Order</HD>
                <P>
                    The product covered by this investigation is rebar from Algeria. For a complete description of the scope of this order, 
                    <E T="03">see</E>
                     the appendix to this notice.
                </P>
                <HD SOURCE="HD1">Countervailing Duty Order</HD>
                <P>
                    Based on the ITC's confirmation that a material injury determination is not required for this countervailing duty investigation, consistent with section 701(c) of the Act,
                    <SU>4</SU>
                    <FTREF/>
                     and the ITC's subsequent closure of its investigation, in accordance with section 705(c)(2) of the Act, Commerce is issuing this CVD order. Moreover, because a material injury determination is not required in this countervailing duty investigation, unliquidated entries of such merchandise entered, or withdrawn from warehouse, for consumption, are subject to the assessment of countervailing duties.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Suspension of Liquidation and Cash Deposits</HD>
                <P>
                    In accordance with section 706 of the Act, Commerce intends to instruct CBP to reinstitute the suspension of liquidation of effective on the date of publication of the ITC's notification of the closure of investigation in the 
                    <E T="04">Federal Register,</E>
                     and to assess, upon further instruction by Commerce, pursuant to section 706(a)(1) of the Act, countervailing duties on each entry of subject merchandise in an amount based on the net countervailable subsidy rates below. These instructions suspending liquidation will remain in effect until further notice. Commerce also intends, pursuant to section 706(a)(1) of the Act, to instruct CBP to require cash deposits equal to the amounts as indicated below. Accordingly, effective on the date of publication of the ITC's notification of the closure of investigation in the 
                    <E T="04">Federal Register</E>
                    , CBP will require, at the same time as importers would normally deposit estimated customs duties on the subject merchandise, a cash deposit for each entry of subject merchandise equal to the subsidy rates listed in the 
                    <E T="03">Final Determination.</E>
                    <SU>5</SU>
                    <FTREF/>
                     The all-others rate applies to all producers or exporters not specifically listed, as appropriate.
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See Final Determination,</E>
                         91 FR at 14808-09; section 706(a)(3) of the Act.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Estimated Countervailable Subsidy Rates</HD>
                <P>The estimated countervailable subsidy rates are as follows:</P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s50,12">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Company</CHED>
                        <CHED H="1">
                            Subsidy Rate
                            <LI>
                                (percent 
                                <E T="03">ad valorem</E>
                                )
                            </LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Tosyali Iron Steel Industry Algeria SPA</ENT>
                        <ENT>* 72.94</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">All Others</ENT>
                        <ENT>* 72.94</ENT>
                    </ROW>
                    <TNOTE>* This rate is based on facts available with adverse inferences.</TNOTE>
                </GPOTABLE>
                <HD SOURCE="HD1">Provisional Measures</HD>
                <P>
                    Section 703(d) of the Act states that the suspension of liquidation pursuant to an affirmative preliminary determination may not remain in effect for more than four months. Commerce published the 
                    <E T="03">Preliminary Determination</E>
                     on January 13, 2026.
                    <SU>6</SU>
                    <FTREF/>
                     As such, the four-month period beginning on the date of the publication of the 
                    <E T="03">Preliminary Determinations</E>
                     ended on May 12, 2026.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See Steel Concrete Reinforcing Bar from Algeria: Preliminary Affirmative Countervailing Duty Determination,</E>
                         91 FR 1261 (January 13, 2026) (
                        <E T="03">Preliminary Determination</E>
                        ).
                    </P>
                </FTNT>
                <P>
                    Therefore, in accordance with section 703(d) of the Act, we instructed CBP to terminate the suspension of liquidation and to liquidate, without regard to countervailing duties, unliquidated entries of rebar from Algeria entered, or withdrawn from warehouse, for consumption, on or after May 13, 2026, the date on which the provisional measures expired, until and through the day preceding the date of publication of the ITC's notification of the closure of investigation in the 
                    <E T="04">Federal Register</E>
                    . Suspension of liquidation and the collection of cash deposits will resume on the date of publication of the ITC's notification of the closure of investigation in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <HD SOURCE="HD1">Establishment of the Annual Inquiry Service Lists</HD>
                <P>
                    On September 20, 2021, Commerce published the 
                    <E T="03">Final Rule</E>
                     in the 
                    <E T="04">Federal Register</E>
                    .
                    <SU>7</SU>
                    <FTREF/>
                     On September 27, 2021, Commerce also published the 
                    <E T="03">Procedural Guidance</E>
                     in the 
                    <E T="04">Federal Register</E>
                    .
                    <SU>8</SU>
                    <FTREF/>
                     The 
                    <E T="03">Final Rule</E>
                     and 
                    <E T="03">Procedural Guidance</E>
                     provide that Commerce will maintain an annual inquiry service list for each order or suspended investigation, and any interested party submitting a scope ruling application or request for circumvention inquiry shall serve a copy of the application or request on the persons on the annual inquiry service list for that order, as well as any companion order covering the same merchandise from the same country of origin.
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See Regulations to Improve Administration and Enforcement of Antidumping and Countervailing Duty Laws,</E>
                         86 FR 52300 (September 20, 2021) (
                        <E T="03">Final Rule</E>
                        ).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See Scope Ruling Application; Annual Inquiry Service List; and Informational Sessions,</E>
                         86 FR 53205 (September 27, 2021) (
                        <E T="03">Procedural Guidance</E>
                        ).
                    </P>
                </FTNT>
                <P>
                    In accordance with the 
                    <E T="03">Procedural Guidance,</E>
                     for orders published in the 
                    <E T="04">Federal Register</E>
                     after November 4, 2021, Commerce will create an annual inquiry service list segment in Commerce's online e-filing and document management system, Antidumping and Countervailing Duty Electronic Service System (ACCESS), available at 
                    <E T="03">https://access.trade.gov,</E>
                     within five business days of publication of the notice of the order. Each annual inquiry service list will be saved in ACCESS, under each case number, and under a specific segment type called “AISL-Annual Inquiry Service List.” 
                    <SU>9</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         This segment will be combined with the ACCESS Segment Specific Information (SSI) field which will display the month in which the notice of the order or suspended investigation was published in the 
                        <E T="04">Federal Register</E>
                        <E T="03">,</E>
                         also known as the anniversary month. For example, for an order under case number A-000-000 that was published in the 
                        <E T="04">Federal Register</E>
                         in January, the relevant segment and SSI combination will appear in ACCESS as “AISL-January Anniversary.” Note that there will be only one annual inquiry service list segment per case number, and the anniversary month will be pre-populated in ACCESS.
                    </P>
                </FTNT>
                <P>
                    Interested parties who wish to be added to the annual inquiry service list for an order must submit an entry of appearance to the annual inquiry service list segment for the order in ACCESS within 30 days after the date of publication of the order. For ease of administration, Commerce requests that law firms with more than one attorney representing interested parties in an order designate a lead attorney to be included on the annual inquiry service list. Commerce will finalize the annual inquiry service list within five business days thereafter. As mentioned in the 
                    <E T="03">Procedural Guidance,</E>
                    <SU>10</SU>
                    <FTREF/>
                     the new annual inquiry service list will be in place until the following year, when the 
                    <E T="03">Opportunity Notice</E>
                     for the anniversary month of the order is published.
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See Procedural Guidance,</E>
                         86 FR at 53206.
                    </P>
                </FTNT>
                <P>
                    Commerce may update an annual inquiry service list at any time as needed based on interested parties' amendments to their entries of 
                    <PRTPAGE P="40972"/>
                    appearance to remove or otherwise modify their list of members and representatives, or to update contact information. Any changes or announcements pertaining to these procedures will be posted to the ACCESS website at 
                    <E T="03">https://access.trade.gov.</E>
                </P>
                <HD SOURCE="HD1">Special Instructions for the Petitioner and Foreign Governments</HD>
                <P>
                    In the Final Rule, Commerce stated that, “after an initial request and placement on the annual inquiry service list, both petitioners and foreign governments will automatically be placed on the annual inquiry service list in the years that follow.” 
                    <SU>11</SU>
                    <FTREF/>
                     Accordingly, as stated above, the petitioner and foreign governments should submit their initial entries of appearance after publication of this notice in order to appear in the first annual inquiry service lists for this order. Pursuant to 19 CFR 351.225(n)(3), the petitioner and foreign governments will not need to resubmit their entries of appearance each year to continue to be included on the annual inquiry service list. However, the petitioner and foreign governments are responsible for making amendments to their entries of appearance during the annual update to the annual inquiry service list in accordance with the procedures described above.
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See Final Rule,</E>
                         86 FR at 52335.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Notification to Interested Parties</HD>
                <P>
                    This notice constitutes the CVD order with respect to rebar from Algeria, pursuant to section 706(a) of the Act. Interested parties can find a list of antidumping duty and CVD orders currently in effect at 
                    <E T="03">https://www.trade.gov/data-visualization/adcvd-orders-and-suspension-agreements.</E>
                </P>
                <P>This CVD order is issued and published in accordance with section 706(a) of the Act and 19 CFR 351.211(b).</P>
                <SIG>
                    <DATED>Dated: June 29, 2026.</DATED>
                    <NAME>Christopher Abbott,</NAME>
                    <TITLE>Deputy Assistant Secretary for Policy and Negotiations, performing the non-exclusive functions and duties of the Assistant Secretary for Enforcement and Compliance.</TITLE>
                </SIG>
                <APPENDIX>
                    <HD SOURCE="HED">Appendix</HD>
                    <HD SOURCE="HD1">Scope of the Order</HD>
                    <P>The merchandise subject to this order is steel concrete reinforcing bar imported in either straight length or coil form (rebar) regardless of metallurgy, length, diameter, or grade or lack thereof.</P>
                    <P>The subject merchandise includes rebar that has been further processed in the subject country or a third country, including but not limited to cutting, grinding, galvanizing, painting, coating, or any other processing that would not otherwise remove the merchandise from the scope of this investigation if performed in the country of manufacture of the rebar.</P>
                    <P>
                        Specifically excluded are plain rounds (
                        <E T="03">i.e.,</E>
                         nondeformed or smooth rebar).
                    </P>
                    <P>The subject merchandise is classifiable in the Harmonized Tariff Schedule of the United States (HTSUS) primarily under subheadings 7213.10.0000, 7214.20.0000, and 7228.30.8010. The subject merchandise may also enter under other HTSUS subheadings including 221.00.0017, 7221.00.0018, 7221.00.0030, 7221.00.0045, 7222.11.0001, 7222.11.0057, 7222.11.0059, 7222.30.0001, 7227.20.0080, 7227.90.6030, 7227.90.6035, 7227.90.6040, 7228.20.1000, and 7228.60.6000. HTSUS subheadings are provided for convenience and customs purposes; however, the written description of the scope remains dispositive.</P>
                </APPENDIX>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13488 Filed 7-2-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>
                <DEPDOC>[A-525-001, A-351-854, A-891-001, A-729-803, A-428-849, A-533-895, A-560-835, A-475-842, A-523-814, A-485-809, A-801-001, A-856-001, A-791-825, A-469-820, A-583-867, A-489-839]</DEPDOC>
                <SUBJECT>Common Alloy Aluminum Sheet From Bahrain, Brazil, Croatia, Egypt, Germany, India, Indonesia, Italy, Oman, Romania, Serbia, Slovenia, South Africa, Spain, Taiwan, and the Republic of Türkiye: Final Results of the Expedited First Sunset Reviews of the Antidumping Duty Orders</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Enforcement and Compliance, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The U.S. Department of Commerce (Commerce) finds that revocation of the antidumping duty (AD) orders on common alloy aluminum sheet (aluminum sheet) from Bahrain, Brazil, Croatia, Egypt, Germany, India, Indonesia, Italy, Oman, Romania, Serbia, Slovenia, South Africa, Spain, Taiwan, and the Republic of Türkiye (Türkiye) would be likely to lead to continuation or recurrence of dumping, at the levels indicated in the “Final Results of Sunset Reviews” section of this notice.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Applicable July 6, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>David De Falco, Trade Agreements Policy and Negotiations, Enforcement and Compliance, International Trade Administration, U.S. Department of Commerce, 1401 Constitution Avenue NW, Washington, DC 20230; telephone: (202) 482-2178.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On April 27, 2021, Commerce published the 
                    <E T="03">Orders</E>
                     in the 
                    <E T="04">Federal Register</E>
                    .
                    <SU>1</SU>
                    <FTREF/>
                     On March 2, 2026, Commerce published the notice of initiation of this first sunset review of the 
                    <E T="03">Orders,</E>
                     pursuant to section 751(c) of the Tariff Act of 1930, as amended (the Act).
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See Common Alloy Aluminum Sheet from Bahrain, Brazil, Croatia, Egypt, Germany, India, Indonesia, Italy, Oman, Romania, Serbia, Slovenia, South Africa, Spain, Taiwan, and the Republic of Turkey: Antidumping Duty Orders,</E>
                         86 FR 22139 (April 27, 2021) (
                        <E T="03">Bahrain Order, Brazil Order, Croatia Order, Egypt Order, Germany Order, India Order, Indonesia Order, Italy Order, Oman Order, Romania Order, Serbia Order, Slovenia Order, South Africa Order, Spain Order, Taiwan Order,</E>
                         and 
                        <E T="03">Türkiye Order</E>
                        ) (collectively, 
                        <E T="03">Orders</E>
                        ).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See Initiation of Five-Year (Sunset) Reviews,</E>
                         91 FR 10053 (March 2, 2026).
                    </P>
                </FTNT>
                <P>
                    Between March 10 and March 17, 2026, Commerce received a timely and complete notice of intent to participate in the sunset review from domestic interested parties 
                    <SU>3</SU>
                    <FTREF/>
                     within the deadline specified in the 19 CFR 351.218(d)(1)(i).
                    <SU>4</SU>
                    <FTREF/>
                     The petitioners 
                    <PRTPAGE P="40973"/>
                    claimed interested party status within the meaning of section 771(9)(E) of the Act as a trade or business association, a majority of whose members manufacture, produce, or wholesale a domestic like product in the United States.
                    <SU>5</SU>
                    <FTREF/>
                     Aluminum Dynamics claimed interested party status within the meaning of section 771(9)(C) of the Act as a domestic producer of aluminum sheet.
                    <SU>6</SU>
                    <FTREF/>
                     On March 24, 2026, Commerce notified the U.S. International Trade Commission (ITC) that it had received a notice of intent to participate from the domestic interested parties.
                    <SU>7</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         The Aluminum Association Common Alloy Aluminum Sheet Trade Enforcement Working Group and its Individual Members, Aleris Rolled Products, Inc., Arconic, Inc., Constellium Rolled Products Ravenswood, LLC, JW Aluminum Company, Novelis Corporation, and Texarkana Aluminum, Inc. (collectively, the petitioners).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See</E>
                         Petitioners' Letter, “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Bahrain—Petitioners' Notice of Intent to Participate,” dated March 13, 2026 (Petitioners Intent to Participate); Aluminum Dynamics' Letter, “Five-Year (“Sunset”) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Bahrain: Notice of Intent to Participate,” dated March 17, 2026 (Aluminum Dynamics Intent to Participate); Petitioners' Letter, “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Brazil—Petitioners' Notice of Intent to Participate,” dated March 11, 2026; Aluminum Dynamics' Letter, “Five-Year (“Sunset”) Review of the Antidumping Duty Order on Common Alloy Sheet from Brazil: Notice of Intent to Participate,” dated March 17, 2026; Petitioners' Letter, “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Croatia—Petitioners' Notice of Intent to Participate,” dated March 10, 2026; Aluminum Dynamics' Letter, “Five-Year (“Sunset”) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Croatia: Notice of Intent to Participate,” dated March 17, 2026; Petitioners' Letter, “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Egypt—Petitioners' Notice of Intent to Participate,” dated March 12, 2026; Aluminum Dynamics' Letter, “Five-Year (“Sunset”) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Egypt: Notice of Intent to Participate,” dated March 17, 2026; Petitioners' Letter, “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Germany—Petitioners' Notice of Intent to Participate,” dated March 12, 2026; Aluminum Dynamics' Letter “Five-Year (“Sunset”) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Germany: Notice of Intent to Participate,” dated March 17, 2026; Petitioners' Letter, “Five-Year (1st 
                        <PRTPAGE/>
                        Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from India—Petitioners' Notice of Intent to Participate,” dated March 11, 2026; Aluminum Dynamics' Letter, “Five-Year (“Sunset”) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from India: Notice of Intent to Participate,” dated March 17, 2026; Petitioners' Letter, “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Indonesia—Petitioners' Notice of Intent to Participate,” dated March 11, 2026; Aluminum Dynamics' Letter “Five-Year (“Sunset”) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Indonesia: Notice of Intent to Participate,” dated March 17, 2026; Petitioners' Letter “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Italy—Petitioners' Notice of Intent to Participate,” dated March 10, 2026; Aluminum Dynamics' Letter, “Five-Year (“Sunset”) Review of the Antidumping Duty Order on Common Alloy Sheet from Italy: Notice of Intent to Participate,” dated March 17, 2026; Petitioners' Letter, “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Oman—Petitioners' Notice of Intent to Participate,” dated March 13, 2026; Aluminum Dynamics' Letter, “Five-Year (“Sunset”) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Oman: Notice of Intent to Participate,” dated March 17, 2026; Petitioners' Letter, “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Romania—Petitioners' Notice of Intent to Participate,” dated March 10, 2026; Aluminum Dynamics' Letter, “Five-Year (“Sunset”) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Romania: Notice of Intent to Participate,” dated March 17, 2026; Petitioners' Letter, “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Serbia—Petitioners' Notice of Intent to Participate,” dated March 10, 2026; Aluminum Dynamics' Letter, “Five-Year (“Sunset”) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Serbia: Notice of Intent to Participate,” dated March 17, 2026; Petitioners' Letter, “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Slovenia—Petitioners' Notice of Intent to Participate,” dated March 10, 2026; Aluminum Dynamics' Letter, “Five-Year (“Sunset”) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Slovenia: Notice of Intent to Participate,” dated March 17, 2026; Petitioners' Letter, “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from South Africa—Petitioners' Notice of Intent to Participate,” dated March 13, 2026; Aluminum Dynamics' Letter, “Five-Year (“Sunset”) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from South Africa: Notice of Intent to Participate,” dated March 17, 2026; Petitioners' Letter, “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Spain—Petitioners' Notice of Intent to Participate,” dated March 10, 2026; Aluminum Dynamics' Letter, “Five-Year (“Sunset”) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Spain: Notice of Intent to Participate,” dated March 17, 2026; Petitioners' Letter, “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Taiwan—Petitioners' Notice of Intent to Participate,” dated March 13, 2026; Aluminum Dynamics' Letter, “Five-Year (“Sunset”) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Taiwan: Notice of Intent to Participate,” dated March 17, 2026; Petitioners' Letter, “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Turkey—Petitioners' Notice of Intent to Participate,” dated March 11, 2026; Aluminum Dynamics' Letter, “Five-Year (“Sunset”) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Turkey: Notice of Intent to Participate,” dated March 17, 2026.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         Petitioners Intent to Participate at 4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         Aluminum Dynamics Intent to Participate at 2.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         Commerce's Letter, “Sunset Reviews Initiated on March 2, 2026,” dated March 24, 2026.
                    </P>
                </FTNT>
                <P>
                    Between March 30 and April 1, 2026, pursuant to 19 CFR 351.218(d)(3)(i), domestic interested parties filed timely and adequate substantive responses.
                    <SU>8</SU>
                    <FTREF/>
                     Commerce did not receive a substantive response from any respondent interested party. On April 29. 2026, Commerce notified the ITC that it did not receive substantive response from any respondent interested parties.
                    <SU>9</SU>
                    <FTREF/>
                     As a result, pursuant to section 751(c)(3)(B) of the Act and 19 CFR 351.218(e)(1)(ii)(C)(2), Commerce is conducting expedited (120-day) sunset reviews of the 
                    <E T="03">Orders.</E>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         Petitioners' Letter, “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Bahrain—Petitioners' Substantive Response to the Notice of Initiation,” dated March 31, 2026 (Bahrain Substantive Response); “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Brazil—Petitioners' Substantive Response to the Notice of Initiation,” dated March 31, 2026 (Brazil Substantive Response); “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Croatia—Petitioners' Substantive Response to the Notice of Initiation,” dated March 31, 2026 (Croatia Substantive Response); “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Egypt—Petitioners' Substantive Response to the Notice of Initiation,” dated March 31, 2026 (Egypt Substantive Response); “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Germany—Petitioners Substantive Response to the Notice of Initiation,” dated April 1, 2026 (Germany Substantive Response); “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from India—Petitioners Substantive Response to the Notice of Initiation,” dated March 31, 2026 (India Substantive Response); “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Indonesia—Petitioners Substantive Response to the Notice of Initiation,” dated March 31, 2026 (Indonesia Substantive Response); “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Italy—Petitioners Substantive Response to the Notice of Initiation,” dated March 30, 2026 (Italy Substantive Response); “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Oman—Petitioners Substantive Response to the Notice of Initiation,” dated March 31, 2026 (Oman Substantive Response); “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Romania—Petitioners Substantive Response to the Notice of Initiation,” dated March 30, 2026 (Romania Substantive Response); “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Serbia—Petitioners Substantive Response to the Notice of Initiation,” dated March 31, 2026 (Serbia Substantive Response); “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Slovenia—Petitioners Substantive Response to the Notice of Initiation,” dated March 30, 2026 (Slovenia Substantive Response); “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from South Africa—Petitioners Substantive Response to the Notice of Initiation,” dated March 31, 2026 (South Africa Substantive Response); “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Spain—Petitioners Substantive Response to the Notice of Initiation,” dated March 30, 2026 (Spain Substantive Response); “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Taiwan—Petitioners Substantive Response to the Notice of Initiation,” dated March 31, 2026 (Taiwan Substantive Response); “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Common Alloy Aluminum Sheet from Turkey—Petitioners Substantive Response to the Notice of Initiation,” dated March 31, 2026 (Türkiye Substantive Response).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See</E>
                         Commerce's Letter, “Sunset Reviews Initiated on March 2, 2026,” dated April 29, 2026.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Scope of the Orders</HD>
                <P>
                    The product covered by these 
                    <E T="03">Orders</E>
                     is aluminum sheet from Bahrain, Brazil, Croatia, Egypt, Germany, India, Indonesia, Italy, Oman, Romania, Serbia, Slovenia, South Africa, Spain, Taiwan, and Türkiye. For the full description of the scope of the 
                    <E T="03">Orders, see</E>
                     the Issues and Decisions Memorandum.
                    <SU>10</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See</E>
                         Memorandum, “Issues and Decision Memorandum for the Final Results of the Expedited First Sunset Reviews of the Antidumping Duty Orders on Common Alloy Aluminum Sheet from Bahrain, Brazil, Croatia, Egypt, Germany, India, Indonesia, Italy, Oman, Romania, Serbia, Slovenia, South Africa, Spain, Taiwan, and the Republic of Türkiye,” dated concurrently with, and hereby adopted by, this notice (Issues and Decision Memorandum).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Analysis of Comments Received</HD>
                <P>
                    A complete discussion of all issues raised in these sunset reviews, including the likelihood of continuation or recurrence of dumping in the event of revocation of the 
                    <E T="03">Orders</E>
                     and the magnitude of the margins likely to prevail if the 
                    <E T="03">Orders</E>
                     were to be revoked, is provided in the Issues and Decision Memorandum.
                    <SU>11</SU>
                    <FTREF/>
                     A list of the topics 
                    <PRTPAGE P="40974"/>
                    discussed in the Issues and Decision Memorandum is attached in the appendix to this notice. The Issues and Decision Memorandum is a public document and is on file electronically via Enforcement and Compliance's Antidumping and Countervailing Duty Centralized Electronic Service System (ACCESS), which is available to registered users at 
                    <E T="03">https://access.trade.gov.</E>
                     In addition, a complete version of the Issues and Decision Memorandum can be directly accessed at 
                    <E T="03">https://access.trade.gov/frnotices.</E>
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Final Results of Sunset Reviews</HD>
                <P>
                    Pursuant to sections 751(c)(1), 752(c)(1) and (3) of the Act, Commerce determines that revocation of the 
                    <E T="03">Orders</E>
                     would be likely to lead to continuation or recurrence of dumping, and that the magnitude of the dumping margins likely to prevail would be weighted-average dumping margins up to 4.83 percent for Bahrain, 137.06 for Brazil, 3.19 for Croatia, 12.11 for Egypt, 242.80 for Germany, 47.92 for India, 32.12 for Indonesia, 29.13 for Italy, 5.29 for Oman, 37.26 for Romania, 25.84 for Serbia, 13.43 for Slovenia, 8.85 for South Africa, 24.23 for Spain, 17.50 for Taiwan, and 13.56 for Türkiye.
                </P>
                <HD SOURCE="HD1">Notification Regarding Administrative Protective Order (APO)</HD>
                <P>This notice also serves as the only reminder to parties subject to an APO of their responsibility concerning the return or destruction of proprietary information disclosed under APO in accordance with 19 CFR 351.305. Timely notification of the return or destruction of APO materials, or conversion to judicial protective, orders is hereby requested. Failure to comply with the regulations and terms of an APO is a violation which is subject to sanction.</P>
                <HD SOURCE="HD1">Notification to Interested Parties</HD>
                <P>We are issuing and publishing these final results in accordance with sections 751(c), 752(c), and 777(i)(1) of the Act, and 19 CFR 351.218 and 19 CFR 351.221(c)(5)(ii).</P>
                <SIG>
                    <DATED>Dated: June 30, 2026.</DATED>
                    <NAME>Scot Fullerton,</NAME>
                    <TITLE>Acting Deputy Assistant Secretary for Antidumping and Countervailing Duty Operations.</TITLE>
                </SIG>
                <HD SOURCE="HD1">Appendix</HD>
                <EXTRACT>
                    <HD SOURCE="HD1">List of Topics Discussed in the Issues and Decision Memorandum</HD>
                    <FP SOURCE="FP-2">I. Summary</FP>
                    <FP SOURCE="FP-2">II. Background</FP>
                    <FP SOURCE="FP-2">
                        III. Scope of the 
                        <E T="03">Orders</E>
                    </FP>
                    <FP SOURCE="FP-2">
                        IV. History of the 
                        <E T="03">Orders</E>
                    </FP>
                    <FP SOURCE="FP-2">V. Legal Framework</FP>
                    <FP SOURCE="FP-2">VI. Discussion of the Issues</FP>
                    <FP SOURCE="FP1-2">1. Likelihood of Continuation or Recurrence of Dumping</FP>
                    <FP SOURCE="FP1-2">2. Magnitude of the Margins of Dumping Likely to Prevail</FP>
                    <FP SOURCE="FP-2">VII. Final Results of Sunset Reviews</FP>
                    <FP SOURCE="FP-2">VIII. Recommendation</FP>
                </EXTRACT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13511 Filed 7-2-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>
                <DEPDOC>[A-201-830]</DEPDOC>
                <SUBJECT>Carbon and Certain Alloy Steel Wire Rod from Mexico: Final Results of Antidumping Duty Administrative Review; 2023-2024</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Enforcement and Compliance, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The U.S. Department of Commerce (Commerce) determines that producers/exporters subject to this review made sales of subject merchandise at less than normal value (NV) during the period of review (POR) October 1, 2023, through September 30, 2024.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Applicable July 6, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Matthew Palmer, AD/CVD Operations, Office III, Enforcement and Compliance, International Trade Administration, U.S. Department of Commerce, 1401 Constitution Avenue NW, Washington, DC 20230; telephone: (202) 482-1678.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On February 12, 2026, Commerce published the 
                    <E T="03">Preliminary Results</E>
                     for this administrative review in the 
                    <E T="04">Federal Register</E>
                     and invited interested parties to comment.
                    <SU>1</SU>
                    <FTREF/>
                     This review covers Deacero S.A.P.I de C.V. (Deacero) and Deacero Summit S.A.P.I. de C.V. (Deacero Summit) (collectively, Deacero/Deacero Summit), the sole mandatory respondent selected for individual examination.
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See Carbon and Certain Alloy Steel Wire Rod from Mexico: Preliminary Results and Partial Rescission of the Antidumping Duty Administrative Review; 2023-2024,</E>
                         91 FR 6617 (February 12, 2026) (
                        <E T="03">Preliminary Results</E>
                        ), and accompanying Preliminary Decision Memorandum.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See Preliminary Results,</E>
                         91 FR 6619 (showing that, while we selected two mandatory respondents for this administrative review, these entities were otherwise collapsed, and as a result, are treated as a single entity for the purposes of our examination).
                    </P>
                </FTNT>
                <P>
                    On March 11, 2026, we received case briefs from Nucor Corporation and Commercial Metal Company (collectively, Nucor/CMC) as well as Deacero/Deacero Summit.
                    <SU>3</SU>
                    <FTREF/>
                     On March 23, 2026, we received rebuttal briefs from both aforementioned parties.
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         Nucor/CMC's Letter, “Case Brief,” dated March 11, 2026; 
                        <E T="03">see also</E>
                         Deacero's Letter, “Case Brief,” dated March 11, 2026.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See</E>
                         Nucor/CMC's Letter, “Rebuttal Brief,” dated March 23, 2026; 
                        <E T="03">see also</E>
                         Deacero/Deacero Summit's Letter, “Rebuttal Brief,” dated March 23, 2026.
                    </P>
                </FTNT>
                <P>
                    A complete summary of the events that occurred since publication of the 
                    <E T="03">Preliminary Results</E>
                     is found in the Issues and Decision Memorandum.
                    <SU>5</SU>
                    <FTREF/>
                     Commerce conducted this review in accordance with section 751(a) of the Tariff Act of 1930, as amended (the Act).
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         Memorandum, “Issues and Decision Memorandum for the Final Results of Antidumping Duty Administrative Review: Carbon and Certain Alloy Steel Wire Rod from Mexico; 2023-2024,” dated concurrently with, and hereby adopted by, this notice (Issues and Decision Memorandum).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">
                    Scope of the Order 
                    <E T="51">6</E>
                    <FTREF/>
                </HD>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See Notice of Antidumping Duty Orders: Carbon and Certain Alloy Steel Wire Rod from Brazil, Indonesia, Mexico, Moldova, Trinidad and Tobago, and Ukraine,</E>
                         67 FR 65945 (October 29, 2002) (
                        <E T="03">Order</E>
                        ).
                    </P>
                </FTNT>
                <P>
                    The merchandise subject to the 
                    <E T="03">Order</E>
                     is certain hot-rolled products of carbon steel and alloy steel, in coils, of approximately round cross section, 5.00 mm or more, but less than 19.00 mm, in solid cross-sectional diameter. For the full text of the scope of the 
                    <E T="03">Order, see</E>
                     the Issues and Decision Memorandum.
                </P>
                <HD SOURCE="HD1">Analysis of the Comments Received</HD>
                <P>
                    All issues raised in the case and rebuttal briefs that were submitted by interested parties are addressed in the Issues and Decision Memorandum. A list of the issues which parties raised, and to which we respond in the Issues and Decision Memorandum, is attached in the appendix to this notice. The Issues and Decision Memorandum is a public document and is on file electronically via Enforcement and Compliance's Antidumping and Countervailing Duty Centralized Electronic System (ACCESS), which is available to registered users at 
                    <E T="03">https://access.trade.gov.</E>
                     In addition, the Issues and Decision Memorandum can be accessed directly at 
                    <E T="03">https://access.trade.gov/frnotices.</E>
                </P>
                <HD SOURCE="HD1">Changes Since the Preliminary Results</HD>
                <P>
                    Based on a review of the record and analysis of the comments received from interested parties regarding the 
                    <E T="03">Preliminary Results,</E>
                     we made changes to the preliminary weighted-average dumping margin calculated for Deacero/Deacero Summit. For detailed information on these changes, 
                    <E T="03">see</E>
                     the Issues and Decision Memorandum.
                    <PRTPAGE P="40975"/>
                </P>
                <HD SOURCE="HD1">Final Results of Review</HD>
                <P>Commerce determines the following estimated weighted-average dumping margins exist for the period October 1, 2023, through September 30, 2024:</P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s50,10C">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Producer/exporter</CHED>
                        <CHED H="1">
                            Weighted-average dumping margin
                            <LI>(percent)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Deacero S.A.P.I. de C.V./Deacero Summit S.A.P.I. de C.V</ENT>
                        <ENT>14.67</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Disclosure</HD>
                <P>
                    Commerce intends to disclose its calculations and analysis performed to interested parties in these final results within five days of any public announcement or, if there is no public announcement, within five days of the date of publication of this notice in the 
                    <E T="04">Federal Register</E>
                    , in accordance with 19 CFR 351.224(b).
                </P>
                <HD SOURCE="HD1">Assessment Rates</HD>
                <P>
                    Pursuant to section 751(a)(2)(A) of the Act and 19 CFR 351.212(b)(1), Commerce will determine, and U.S. Customs and Border Protection (CBP) shall assess, antidumping duties on all appropriate entries of subject merchandise in accordance with the final results of this review. Pursuant to 19 CFR 351.212(b)(1), we calculated importer-specific 
                    <E T="03">ad valorem</E>
                     duty assessment rates based on the ratio of the total amount of dumping calculated for the examined sales to the total entered value of those sales. Where the respondent did not report entered value, we calculated a per-unit assessment rate for each importer by dividing the total amount of dumping calculated for the examined sales made to that importer by the total quantity associated with those sales. To determine whether an importer-specific, per-unit assessment rate is 
                    <E T="03">de minimis,</E>
                     in accordance with 19 CFR 351.106(c)(2), we also calculated an importer-specific 
                    <E T="03">ad valorem</E>
                     ratio based on estimated entered values. Where either the respondent's weighted-average dumping margin is zero or 
                    <E T="03">de minimis</E>
                     within the meaning of 19 CFR 351.106(c)(1), or an importer-specific assessment rate is zero or 
                    <E T="03">de minimis,</E>
                     we will instruct CBP to liquidate the appropriate entries without regard to antidumping duties.
                    <SU>7</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         In these final results, Commerce applied the assessment rate calculation method adopted in 
                        <E T="03">Antidumping Proceedings: Calculation of the Weighted-Average Dumping Margin and Assessment Rate in Certain Antidumping Duty Proceedings; Final Modification,</E>
                         77 FR 8101 (February 14, 2012).
                    </P>
                </FTNT>
                <P>
                    For entries of subject merchandise during the POR produced by Deacero for which they did not know their merchandise they sold to an intermediary (
                    <E T="03">e.g.,</E>
                     a reseller, trading company, or exporter) was destined for the United States, we will instruct CBP to liquidate unreviewed entries at the all-others rate if there is no rate for the intermediate company(ies) involved in the transaction. The final results of this review shall be the basis for the assessment of antidumping duties on entries of merchandise covered by the final results of this review and for future deposits of estimated duties, where applicable.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         section 751(a)(2)(C) of the Act.
                    </P>
                </FTNT>
                <P>
                    Commerce intends to issue assessment instructions to CBP no earlier than 41 days after the date of publication of the final results of this review in the 
                    <E T="04">Federal Register</E>
                     in accordance with 19 CFR 356.8(a).
                </P>
                <HD SOURCE="HD1">Cash Deposit Requirements</HD>
                <P>
                    The following cash deposit requirements will be effective for all shipments of subject merchandise entered, or withdrawn from warehouse, for consumption on or after the publication date of the final results of this administrative review, as provided by section 751(a)(2)(C) of the Act: (1) the cash deposit rate for the companies listed above will be equal to the weighted-average dumping margins established in the final results of this administrative review; (2) for merchandise exported by producers or exporters not covered in this review but covered in a prior completed segment of the proceeding, the cash deposit rate will continue to be the company-specific rate published for the most recent period; (3) if the exporter is not a firm covered in this review, a prior review, or the original investigation, but the producer has been covered in a prior complete segment of this proceeding, then the cash deposit rate will be the rate established for the most recent period for the producer of the merchandise; (4) the cash deposit rate for all other manufacturers or exporters will continue to be 20.11 percent.
                    <SU>9</SU>
                    <FTREF/>
                     These cash deposit requirements, when imposed, shall remain in effect until further notice.
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See Order,</E>
                         67 FR at 65947.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Notification to Importers</HD>
                <P>This notice also serves as a final reminder to importers of their responsibility under 19 CFR 351.402(f)(2) to file a certificate regarding the reimbursement of antidumping duties prior to liquidation of the relevant entries during this review period. Failure to comply with this requirement could result in Commerce's presumption that reimbursement of antidumping duties occurred and the subsequent assessment of double antidumping duties.</P>
                <HD SOURCE="HD1">Administrative Protective Order (APO)</HD>
                <P>This notice also serves as a reminder to parties subject to an APO of their responsibility concerning the disposition of proprietary information disclosed under APO in accordance with 19 CFR 351.305(a)(3). Timely written notification of return/destruction of APO materials or conversion to judicial protective order is hereby requested. Failure to comply with the regulations and the terms of an APO is a sanctionable violation.</P>
                <HD SOURCE="HD1">Notification to Interested Parties</HD>
                <P>We are issuing and publishing these final results of administrative review in accordance with sections 751(a)(1) and 777(i)(1) of the Act, and 19 CFR 351.221(b)(5).</P>
                <SIG>
                    <DATED>Dated: June 29, 2026.</DATED>
                    <NAME>Christopher Abbott,</NAME>
                    <TITLE>Deputy Assistant Secretary for Policy and Negotiations, performing the non-exclusive functions and duties of the Assistant Secretary for Enforcement and Compliance.</TITLE>
                </SIG>
                <HD SOURCE="HD1">Appendix</HD>
                <EXTRACT>
                    <HD SOURCE="HD1">List of Topics Discussed in the Issues and Decision Memorandum</HD>
                    <FP SOURCE="FP-2">I. Summary</FP>
                    <FP SOURCE="FP-2">II. Background</FP>
                    <FP SOURCE="FP-2">
                        III. Scope of the 
                        <E T="03">Order</E>
                    </FP>
                    <FP SOURCE="FP-2">
                        IV. Changes Since the 
                        <E T="03">Preliminary Results</E>
                    </FP>
                    <FP SOURCE="FP-2">V. Discussion of the Issues</FP>
                    <FP SOURCE="FP1-2">Comment 1: Whether to Apply Adverse Facts Available (AFA) to Deacero/Deacero Summit</FP>
                    <FP SOURCE="FP1-2">Comment 2: Whether to Continue to Collapse Deacero and Deacero Summit</FP>
                    <FP SOURCE="FP1-2">Comment 3: Whether to Cap Home Market Insurance Revenue by Warranty Expenses</FP>
                    <FP SOURCE="FP1-2">Comment 4: Whether to Revise the Preliminary Calculation of Deacero/Deacero Summit's Margin to Correct for a Programming Error</FP>
                    <FP SOURCE="FP-2">VI. Recommendation</FP>
                </EXTRACT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13567 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="40976"/>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>International Trade Administration</SUBAGY>
                <DEPDOC>[A-570-900]</DEPDOC>
                <SUBJECT>Diamond Sawblades and Parts Thereof From the People's Republic of China: Final Results of the Expedited Third Sunset Review of the Antidumping Duty Order</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Enforcement and Compliance, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The U.S. Department of Commerce (Commerce) finds that revocation of the antidumping duty (AD) order on Diamond Sawblades and Parts Thereof (diamond sawblades) from the People's Republic of China (China) would be likely to lead to continuation or recurrence of dumping, at the levels indicated in the “Final Results of Sunset Review” section of this notice.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Applicable July 6, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>David De Falco, Trade Agreements Policy and Negotiations, Enforcement and Compliance, International Trade Administration, U.S. Department of Commerce, 1401 Constitution Avenue NW, Washington, DC 20230; telephone: 202-482-2178.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On November 4, 2009, Commerce published the 
                    <E T="03">Order</E>
                     in the 
                    <E T="04">Federal Register</E>
                    .
                    <SU>1</SU>
                    <FTREF/>
                     On March 2, 2026, Commerce published the notice of initiation of this third sunset review of the 
                    <E T="03">Order,</E>
                     pursuant to section 751(c) of the Tariff Act of 1930 (the Act).
                    <SU>2</SU>
                    <FTREF/>
                     On March 12, 2026, Commerce received a timely and complete notice of intent to participate in the sunset review for domestic interested party within the deadline specified in the 19 CFR 351.218(d)(1)(i).
                    <SU>3</SU>
                    <FTREF/>
                     The domestic interested party claimed the interested party status within the meaning of section 771(9)(E) of the Act as a coalition of U.S. producers of the domestic like product.
                    <SU>4</SU>
                    <FTREF/>
                     On March 24, 2026, Commerce notified the U.S. International Trade Commission (ITC) that it had received a notice of intent to participate from the domestic interested parties.
                    <SU>5</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See Diamond Sawblades and Parts Thereof from the People's Republic of China and the Republic of Korea: Antidumping Duty Orders,</E>
                         74 FR 57145 (November 4, 2009) (
                        <E T="03">Order</E>
                        ).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See Initiation of Five-Year (Sunset) Reviews,</E>
                         91 FR 10053 (March 2, 2026).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         Domestic Interested Party's Letter, “Diamond Sawblades and Parts Thereof from the People's Republic of China: Notice of Intent to Participate,” dated March 12, 2026.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">Id.</E>
                         at 2.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         Commerce's Letter, “Sunset Reviews Initiated on March 2, 2026,” dated March 24, 2026.
                    </P>
                </FTNT>
                <P>
                    On March 31, 2026, pursuant to 19 CFR 351.218(d)(3)(i), domestic interested parties filed a timely and adequate substantive response.
                    <SU>6</SU>
                    <FTREF/>
                     Commerce did not receive a substantive response from any respondent interested party. On April 29, 2026, Commerce notified the ITC that it did not receive substantive response from any respondent interested parties.
                    <SU>7</SU>
                    <FTREF/>
                     As a result, pursuant to section 751(c)(3)(B) of the Act and 19 CFR 351.218(e)(1)(ii)(C)(2), Commerce is conducting an expedited (120-day) sunset review of the 
                    <E T="03">Order.</E>
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         Domestic Interested Party's Letter, “Diamond Sawblades and Parts Thereof from the People's Republic of China: Substantive Response to the Notice Initiating Sunset Review,” dated March 31, 2026 (Substantive Response).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         Commerce's Letter, “Sunset Reviews Initiated on March 2, 2026,” dated April 29, 2026.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Scope of the Order</HD>
                <P>
                    The product covered by this 
                    <E T="03">Order</E>
                     is diamond sawblades from China. For the full description of the scope of the 
                    <E T="03">Order, see</E>
                     the Issues and Decisions Memorandum.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         Memorandum, “Issues and Decision Memorandum for the Final Results of the Expedited Third Sunset Reviews of the Antidumping Duty Order on Diamond Sawblades and Parts Thereof from the People's Republic of China,” dated concurrently with, and hereby adopted by, this notice.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Analysis of Comments Received</HD>
                <P>
                    A complete discussion of all issues raised in this sunset review, including the likelihood of continuation or recurrence of dumping in the event of revocation of the 
                    <E T="03">Order</E>
                     and the magnitude of the margins likely to prevail if the 
                    <E T="03">Order</E>
                     were to be revoked, is provided in the accompanying Issues and Decision Memorandum.
                    <SU>9</SU>
                    <FTREF/>
                     A list of the topics discussed in the Issues and Decision Memorandum is attached in the Appendix to this notice. The Issues and Decision Memorandum is a public document and is on file electronically via Enforcement and Compliance's Antidumping and Countervailing Duty Centralized Electronic Service System (ACCESS). ACCESS is available to registered users at 
                    <E T="03">https://access.trade.gov.</E>
                     In addition, a complete version of the Issues and Decision Memorandum can be directly accessed at 
                    <E T="03">https://access.trade.gov/frnotices.</E>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Final Results of Sunset Review</HD>
                <P>
                    Pursuant to sections 751(c)(1), 752(c)(1) and (3) of the Act, Commerce determines that revocation of the 
                    <E T="03">Order</E>
                     would be likely to lead to continuation or recurrence of dumping, and that the magnitude of the dumping margins likely to prevail would be weighted-average dumping margins up to 164.09 percent for China.
                </P>
                <HD SOURCE="HD1">Notification Regarding Administrative Protective Orders</HD>
                <P>This notice also serves as the only reminder to parties subject to administrative protective order (APO) of their responsibility concerning the return or destruction of proprietary information disclosed under APO in accordance with 19 CFR 351.305. Timely notification of the return or destruction of APO materials, or conversion to judicial protective, orders is hereby requested. Failure to comply with the regulations and terms of an APO is a violation which is subject to sanction.</P>
                <HD SOURCE="HD1">Notification to Interested Parties</HD>
                <P>We are issuing and publishing these final results in accordance with sections 751(c), 752(c), and 777(i)(1) of the Act, and 19 CFR 351.218 and 19 CFR 351.221(c)(5)(ii).</P>
                <SIG>
                    <DATED>Dated: June 30, 2026.</DATED>
                    <NAME>Scot Fullerton,</NAME>
                    <TITLE>Acting Deputy Assistant Secretary for Antidumping and Countervailing Duty Operations.</TITLE>
                </SIG>
                <HD SOURCE="HD1">Appendix </HD>
                <EXTRACT>
                    <HD SOURCE="HD1">List of Topics Discussed in the Issues and Decision Memorandum</HD>
                    <FP SOURCE="FP-2">I. Summary</FP>
                    <FP SOURCE="FP-2">II. Background</FP>
                    <FP SOURCE="FP-2">
                        III. Scope of the 
                        <E T="03">Order</E>
                    </FP>
                    <FP SOURCE="FP-2">
                        IV. History of the 
                        <E T="03">Order</E>
                    </FP>
                    <FP SOURCE="FP-2">V. Legal Framework</FP>
                    <FP SOURCE="FP-2">VI. Discussion of the Issues</FP>
                    <FP SOURCE="FP1-2">1. Likelihood of Continuation or Recurrence of Dumping</FP>
                    <FP SOURCE="FP1-2">2. Magnitude of the Margins of Dumping Likely to Prevail</FP>
                    <FP SOURCE="FP-2">VII. Final Results of Sunset Review</FP>
                    <FP SOURCE="FP-2">VIII. Recommendation.</FP>
                </EXTRACT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13573 Filed 7-2-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>
                <DEPDOC>[A-201-853]</DEPDOC>
                <SUBJECT>Standard Steel Welded Wire Mesh From Mexico: Final Results of the Expedited First Sunset Review of the Antidumping Duty Order</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Enforcement and Compliance, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The U.S. Department of Commerce (Commerce) finds that 
                        <PRTPAGE P="40977"/>
                        revocation of the antidumping duty (AD) order on standard steel welded wire mesh (wire mesh) from Mexico would be likely to lead to continuation or recurrence of dumping, at the levels indicated in the “Final Results of Sunset Review” section of this notice.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Applicable July 6, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>David De Falco, Trade Agreements Policy and Negotiations, Enforcement and Compliance, International Trade Administration, U.S. Department of Commerce, 1401 Constitution Avenue NW, Washington, DC 20230; telephone: 202-482-2178.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On August 9, 2021, Commerce published the 
                    <E T="03">Order</E>
                     in the 
                    <E T="04">Federal Register</E>
                    .
                    <SU>1</SU>
                    <FTREF/>
                     On March 2, 2026, Commerce published the notice of initiation of this first sunset review of the 
                    <E T="03">Order,</E>
                     pursuant to section 751(c) of the Tariff Act of 1930 (the Act).
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See Standard Steel Welded Wire Mesh from Mexico: Antidumping Duty Order,</E>
                         86 FR 43525 (August 9, 2021), 
                        <E T="03">corrected in Standard Steel Welded Wire Mesh from Mexico: Antidumping Duty Order; Correction,</E>
                         86 FR 45709 (August 16, 2021) (
                        <E T="03">Order</E>
                        ).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See Initiation of Five-Year (Sunset) Reviews,</E>
                         91 FR 10053 (March 2, 2026).
                    </P>
                </FTNT>
                <P>
                    On March 16, 2026, Commerce received a timely and complete notice of intent to participate in the sunset review for domestic interested parties within the deadline specified in 19 CFR 351.218(d)(1)(i).
                    <SU>3</SU>
                    <FTREF/>
                     The domestic interested parties claimed the interested party status within the meaning of section 771(9)(C) of the Act as U.S. producers of the domestic like product.
                    <SU>4</SU>
                    <FTREF/>
                     On March 24, 2026, Commerce notified the U.S. International Trade Commission (ITC) that it had received a notice of intent to participate from the domestic interested parties.
                    <SU>5</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         Domestic Interested Party's Letter, “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Steel Welded Wire Mesh from Mexico—Domestic Interested Parties' Notice of Intent to Participate” dated March 16, 2026.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">Id.</E>
                         at 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         Commerce's Letter, “Sunset Reviews Initiated on March 2, 2026,” dated March 24, 2026.
                    </P>
                </FTNT>
                <P>
                    On March 31, 2026, pursuant to 19 CFR 351.218(d)(3)(i), domestic interested parties filed a timely and adequate substantive response.
                    <SU>6</SU>
                    <FTREF/>
                     Commerce did not receive a substantive response from any respondent interested party. On April 29, 2026, Commerce notified the ITC that it did not receive substantive response from any respondent interested parties.
                    <SU>7</SU>
                    <FTREF/>
                     As a result, pursuant to section 751(c)(3)(B) of the Act and 19 CFR 351.218(e)(1)(ii)(C)(2), Commerce is conducting an expedited (120-day) sunset review of the 
                    <E T="03">Order.</E>
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         Domestic Interested Party's Letter, “Five-Year (1st Sunset) Review of the Antidumping Duty Order on Standard Steel Welded Wire Mesh from Mexico—Domestic Interested Parties' Substantive Response to the Notice of Initiation,” dated March 31, 2026 (Substantive Response).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         Commerce's Letter, “Sunset Reviews Initiated on March 2, 2026,” dated April 29, 2026.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Scope of the Order</HD>
                <P>
                    The product covered by the 
                    <E T="03">Order</E>
                     is wire mesh from Mexico. For the full description of the scope of the 
                    <E T="03">Order, see</E>
                     the Issues and Decisions Memorandum.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         Memorandum, “Issues and Decision Memorandum for the Final Results of the Expedited First Sunset Reviews of the Antidumping Duty Order on Standard Steel Welded Wire Mesh from Mexico,” dated concurrently with, and hereby adopted by, this notice.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Analysis of Comments Received</HD>
                <P>
                    A complete discussion of all issues raised in this sunset review, including the likelihood of continuation or recurrence of dumping in the event of revocation of the 
                    <E T="03">Order</E>
                     and the magnitude of the margins likely to prevail if the 
                    <E T="03">Order</E>
                     were to be revoked, is provided in the accompanying Issues and Decision Memorandum.
                    <SU>9</SU>
                    <FTREF/>
                     A list of the topics discussed in the Issues and Decision Memorandum is attached in the Appendix to this notice. The Issues and Decision Memorandum is a public document and is on file electronically via Enforcement and Compliance's Antidumping and Countervailing Duty Centralized Electronic Service System (ACCESS). ACCESS is available to registered users at 
                    <E T="03">https://access.trade.gov.</E>
                     In addition, a complete version of the Issues and Decision Memorandum can be directly accessed at 
                    <E T="03">https://access.trade.gov/frnotices.</E>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Final Results of Sunset Review</HD>
                <P>
                    Pursuant to sections 751(c)(1), 752(c)(1) and (3) of the Act, Commerce determines that revocation of the 
                    <E T="03">Order</E>
                     would be likely to lead to continuation or recurrence of dumping, and that the magnitude of the dumping margins likely to prevail would be weighted-average dumping margins up to 110.42 percent.
                </P>
                <HD SOURCE="HD1">Notification Regarding Administrative Protective Orders</HD>
                <P>This notice also serves as the only reminder to parties subject to administrative protective order (APO) of their responsibility concerning the return or destruction of proprietary information disclosed under APO in accordance with 19 CFR 351.305. Timely notification of the return or destruction of APO materials, or conversion to judicial protective, orders is hereby requested. Failure to comply with the regulations and terms of an APO is a violation which is subject to sanction.</P>
                <HD SOURCE="HD1">Notification to Interested Parties</HD>
                <P>We are issuing and publishing these final results in accordance with sections 751(c), 752(c), and 777(i)(1) of the Act, and 19 CFR 351.218 and 19 CFR 351.221(c)(5)(ii).</P>
                <SIG>
                    <DATED>Dated: June 30, 2026.</DATED>
                    <NAME>Scot Fullerton,</NAME>
                    <TITLE>Acting Deputy Assistant Secretary for Antidumping and Countervailing Duty Operations.</TITLE>
                </SIG>
                <HD SOURCE="HD1">Appendix</HD>
                <EXTRACT>
                    <HD SOURCE="HD1">List of Topics Discussed in the Issues and Decision Memorandum</HD>
                    <FP SOURCE="FP-2">I. Summary</FP>
                    <FP SOURCE="FP-2">II. Background</FP>
                    <FP SOURCE="FP-2">
                        III. Scope of the 
                        <E T="03">Order</E>
                    </FP>
                    <FP SOURCE="FP-2">
                        IV. History of the 
                        <E T="03">Order</E>
                    </FP>
                    <FP SOURCE="FP-2">V. Legal Framework</FP>
                    <FP SOURCE="FP-2">VI. Discussion of the Issues</FP>
                    <FP SOURCE="FP1-2">1. Likelihood of Continuation or Recurrence of Dumping</FP>
                    <FP SOURCE="FP1-2">2. Magnitude of the Margins of Dumping Likely to Prevail</FP>
                    <FP SOURCE="FP-2">VII. Final Results of Sunset Review</FP>
                    <FP SOURCE="FP-2">VIII. Recommendation</FP>
                </EXTRACT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13510 Filed 7-2-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>
                <DEPDOC>[A-489-839]</DEPDOC>
                <SUBJECT>Common Alloy Aluminum Sheet From the Republic of Türkiye: Notice of Court Decision Not in Harmony With the Final Determination of Antidumping Investigation; Notice of Amended Final Determination</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Enforcement and Compliance, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        On June 17, 2026, the U.S. Court of International Trade (CIT) issued its final judgment in 
                        <E T="03">Assan Aluminyum Sanayi ve Ticaret A.S.</E>
                         v. 
                        <E T="03">United States,</E>
                         Consol. Court No. 21-00246, sustaining the U.S. Department of Commerce's (Commerce) third remand redetermination pertaining to the antidumping duty (AD) investigation of common alloy aluminum sheet from the Republic of Türkiye (Türkiye) covering the period of investigation from January 1, 2019, 
                        <PRTPAGE P="40978"/>
                        through December 31, 2019.
                        <SU>1</SU>
                        <FTREF/>
                         Commerce is notifying the public that the CIT's final judgment is not in harmony with Commerce's final determination in the investigation and that Commerce is amending the final determination and the resulting AD order with respect to the dumping margin assigned to Assan Aluminyum Sanayi ve Ticaret A.S. (Assan).
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             
                            <E T="03">See Common Alloy Aluminum Sheet From Turkey: Final Affirmative Determination of Sales at Less Than Fair Value,</E>
                             86 FR 13326 (March 8, 2021) (
                            <E T="03">Final Determination),</E>
                             and accompanying Issues and Decision Memorandum.
                        </P>
                    </FTNT>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Applicable June 27, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Nathan Depew, AD/CVD Operations, Office VII, Enforcement and Compliance, International Trade Administration, U.S. Department of Commerce, 1401 Constitution Avenue NW, Washington, DC 20230; telephone: (202) 482-5823.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On March 8, 2021, Commerce published its 
                    <E T="03">Final Determination</E>
                     in the AD investigation of common alloy aluminum sheet from Türkiye. Commerce calculated weighted-average dumping margins of 2.02 percent for Assan, 13.56 percent for Teknik Aluminyum Sanayi A.S. (Teknik), and 4.85 percent for all other producers and exporters.
                    <SU>2</SU>
                    <FTREF/>
                     Commerce subsequently published the AD order on common alloy aluminum sheet from Türkiye.
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See Common Alloy Aluminum Sheet From Bahrain, Brazil, Croatia, Egypt, Germany, India, Indonesia, Italy, Oman, Romania, Serbia, Slovenia, South Africa, Spain, Taiwan and the Republic of Turkey: Antidumping Duty Orders,</E>
                         86 FR 22139, 22142 (April 27, 2021) (
                        <E T="03">Order</E>
                        ).
                    </P>
                </FTNT>
                <P>
                    Assan and the Aluminum Association 
                    <SU>4</SU>
                    <FTREF/>
                     both appealed the 
                    <E T="03">Final Determination.</E>
                     On July 27, 2021, the CIT consolidated the actions challenging the determination. On March 1, 2023, the CIT remanded the 
                    <E T="03">Final Determination</E>
                     for Commerce to reconsider or further explain, among other issues, Commerce's duty drawback adjustment methodology in light of recent precedent given by the U.S. Court of Appeals for the Federal Circuit (Federal Circuit).
                    <SU>5</SU>
                    <FTREF/>
                     In its first remand redetermination, issued on May 31, 2023, Commerce recalculated Assan's dumping margin to be below the 
                    <E T="03">de minimis</E>
                     level of two percent.
                    <SU>6</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         The Aluminum Association Common Alloy Aluminum Sheet Trade Enforcement Working Group and its Individual Members, Aleris Rolled Products, Inc., Arconic, Inc., Constellium Rolled Products Ravenswood, LLC, JW Aluminum Company, Novelis Corporation, and Texarkana Aluminum, Inc. (collectively, Aluminum Association).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See Assan Aluminyum Sanayi ve Ticaret A.S.</E>
                         v. 
                        <E T="03">United States,</E>
                         624 F. Supp. 3d 1343, 1362 (CIT 2023) (
                        <E T="03">Assan</E>
                        ).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         Final Results of Redetermination Pursuant to Court Remand, (Dep't Commerce May 31, 2023), ECF No. 94 (
                        <E T="03">First Remand Results</E>
                        ), discussed in 
                        <E T="03">Assan Aluminyum Sanayi ve Ticaret A.S.</E>
                         v. 
                        <E T="03">United States,</E>
                         Consol. Court No. 21-00246, 701 F. Supp. 3d 1321, 1326 (CIT 2024) (
                        <E T="03">Assan II</E>
                        ).
                    </P>
                </FTNT>
                <P>
                    The Aluminum Association challenged Commerce's method of calculating the duty drawback adjustment in the 
                    <E T="03">First Remand Results.</E>
                     On April 11, 2024, the CIT remanded the first remand redetermination for Commerce to reconsider or further explain its duty drawback methodology and respond to the Aluminum Association's arguments.
                    <SU>7</SU>
                    <FTREF/>
                     On July 31, 2024, Commerce issued its second remand redetermination, in which Commerce accepted Assan's June 6 and June 20, 2024, submissions, granted a duty drawback adjustment for sales associated with IPC 7905 and IPC 7734, and again found a 
                    <E T="03">de minimis</E>
                     dumping margin for Assan.
                    <SU>8</SU>
                    <FTREF/>
                     On May 21, 2025, the CIT remanded the second remand redetermination for Commerce to address remaining arguments concerning Assan's drawback eligibility, including arguments regarding the timeliness of Assan's June 20 submission and verification.
                    <SU>9</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See Assan II,</E>
                         701 F. Supp. 3d at 1326.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         Final Results of Second Redetermination Pursuant to Court Remand, (Dep't Commerce July 31, 2024), ECF No. 122 (Second Remand Results),discussed in 
                        <E T="03">Assan Aluminyum Sanayi ve Ticaret A.S.</E>
                         v. 
                        <E T="03">United States,</E>
                         789 F. Supp. 3d 1257, 1269 (CIT 2025) (
                        <E T="03">Assan III</E>
                        ).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See Assan III,</E>
                         789 F. Supp. 3d at 1269.
                    </P>
                </FTNT>
                <P>
                    On September 9, 2025, Commerce issued its third remand redetermination. In the third remand redetermination, Commerce determined that Assan's June 20 submission was untimely, concluded that although IPC 7734 was closed there was insufficient support on the record to grant a per unit duty drawback adjustment for that IPC, and found that further verification was unwarranted. In this remand redetermination, Commerce recalculated Assan's dumping margin to 2.14 percent.
                    <SU>10</SU>
                    <FTREF/>
                     On June 17, 2026, the CIT sustained Commerce's third remand redetermination.
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See</E>
                         Final Results of Third Redetermination Pursuant to Court Remand, (Dep't Commerce September 9, 2025), ECF no. 158, 159 (Third Remand Results); 
                        <E T="03">Assan Aluminyum Sanayi ve Ticaret A.S.</E>
                         v. 
                        <E T="03">United States,</E>
                         Consol. Court No. 21-00246, Slip Op. 26-65 (CIT June 17, 2026) (
                        <E T="03">Assan IV</E>
                        ) (sustaining Commerce's Third Remand Results).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Timken Notice</HD>
                <P>
                    In its decision in 
                    <E T="03">Timken,</E>
                    <SU>11</SU>
                    <FTREF/>
                     as clarified by 
                    <E T="03">Diamond Sawblades,</E>
                    <SU>12</SU>
                    <FTREF/>
                     the Federal Circuit held that, pursuant to sections 516A(c) and (e) of the Tariff Act of 1930, as amended (the Act), Commerce must publish a notice of court decision that is not “in harmony” with a Commerce determination and must suspend liquidation of entries pending a “conclusive” court decision. The CIT's June 17, 2026, judgment constitutes a final decision of the CIT that is not in harmony with Commerce's 
                    <E T="03">Final Determination.</E>
                     Thus, this notice is published in fulfillment of the publication requirements of 
                    <E T="03">Timken.</E>
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See Timken Co.</E>
                         v. 
                        <E T="03">United States,</E>
                         893 F.2d 337 (Fed. Cir. 1990) (
                        <E T="03">Timken</E>
                        ).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">See Diamond Sawblades Manufacturers Coalition</E>
                         v. 
                        <E T="03">United States,</E>
                         626 F.3d 1374 (Fed. Cir. 2010) (
                        <E T="03">Diamond Sawblades</E>
                        ).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">
                    Amended Final Determination
                    <FTREF/>
                </HD>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See Final Determination; see also Order.</E>
                    </P>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">See</E>
                         Third Remand Results.
                    </P>
                </FTNT>
                <P>
                    Because there is now a final court judgment, Commerce is amending its 
                    <E T="03">Final Determination</E>
                     with respect to Assan as follows:
                </P>
                <GPOTABLE COLS="3" OPTS="L2,nj,tp0,i1" CDEF="s100,18,18">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Exporter or producer</CHED>
                        <CHED H="1">
                            Final determination
                            <LI>weighted-average</LI>
                            <LI>
                                dumping margin 
                                <SU>13</SU>
                            </LI>
                            <LI>(percent)</LI>
                        </CHED>
                        <CHED H="1">
                            Amended final
                            <LI>determination</LI>
                            <LI>weighted-average</LI>
                            <LI>
                                dumping margin 
                                <SU>14</SU>
                            </LI>
                            <LI>(percent)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Assan Aluminyum Sanayi ve Ticaret A.S</ENT>
                        <ENT>2.02</ENT>
                        <ENT>2.14</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Teknik Aluminyum Sanayi A.S</ENT>
                        <ENT>13.56</ENT>
                        <ENT>13.56</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">All Others</ENT>
                        <ENT>4.85</ENT>
                        <ENT>4.85</ENT>
                    </ROW>
                </GPOTABLE>
                <PRTPAGE P="40979"/>
                <HD SOURCE="HD1">Cash Deposit Requirements</HD>
                <P>Commerce will issue revised cash deposit instructions to U.S. Customs and Border Protection (CBP).</P>
                <P>
                    Because Assan has a superseding cash deposit rate, 
                    <E T="03">i.e.,</E>
                     there have been final results published in a subsequent administrative review, this notice will not affect the current cash deposit rate for Assan. For all other producers and exporters that do not have a superseding cash deposit rate, Commerce will issue revised deposit instructions to CBP.
                </P>
                <HD SOURCE="HD1">Notification to Interested Parties</HD>
                <P>This notice is issued and published in accordance with sections 516A(c) and (e), and 777(i)(1) of the Act.</P>
                <SIG>
                    <DATED>Dated: June 30, 2026.</DATED>
                    <NAME>Christopher Abbott,</NAME>
                    <TITLE>Deputy Assistant Secretary for Policy and Negotiations, performing the non-exclusive functions and duties of the Assistant Secretary for Enforcement and Compliance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13513 Filed 7-2-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>
                <DEPDOC>[C-525-002, C-533-896, C-489-840]</DEPDOC>
                <SUBJECT>Common Alloy Aluminum Sheet From Bahrain, India, and the Republic of Türkiye: Final Results of the Expedited First Sunset Reviews of the Countervailing Duty Orders</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Enforcement and Compliance, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The U.S. Department of Commerce (Commerce) finds that revocation of the countervailing duty (CVD) orders on common alloy aluminum sheet (aluminum sheet) from Bahrain, India, and the Republic of Türkiye (Türkiye) would be likely to lead to continuation or recurrence of countervailable subsidies at the levels indicated in the “Final Results of Sunset Review(s)” section of this notice.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Applicable July 6, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>David De Falco, Trade Agreements Policy and Negotiations, Enforcement and Compliance, International Trade Administration, U.S. Department of Commerce, 1401 Constitution Avenue NW, Washington, DC 20230; telephone: 202-482-2178.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On April 27, 2021, the U.S. Department of Commerce (Commerce) published the 
                    <E T="03">Order</E>
                     on aluminum sheet from Bahrain, India, and Türkiye.
                    <SU>1</SU>
                    <FTREF/>
                     On March 2, 2026, Commerce published the notice of initiation of the first sunset review of the 
                    <E T="03">Orders,</E>
                     pursuant to section 751(c) of the Tariff Act of 1930 (the Act) and 19 CFR 351.218(c).
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See Common Alloy Aluminum Sheet from Bahrain, India, and the Republic of Turkey: Countervailing Duty Orders,</E>
                         86 FR 22144 (April 27, 2021) (
                        <E T="03">Bahrain Order, India Order, Türkiye Order</E>
                        ) (collectively, 
                        <E T="03">Orders</E>
                        ).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See Initiation of Five-Year (Sunset) Reviews,</E>
                         91 FR 10053 (March 2, 2026).
                    </P>
                </FTNT>
                <P>
                    Between March 11, 2026 and March 17, 2026, Commerce received notices of intent to participate in this review from the Aluminum Association Common Alloy Aluminum Sheet Trade Enforcement Working Group (the Petitioners) and Aluminum Dynamics, LLC (Aluminum Dynamics) (the domestic interested parties), within the deadline specified in 19 CFR 351.218(d)(1)(i).
                    <SU>3</SU>
                    <FTREF/>
                     The petitioners claim that they have interested party status within the meaning of section 771(9)(E) of the Act and 19 CFR 351.102(b)(29)(vii) as a trade or business association, a majority of whose members manufacture, produce, or wholesale a domestic like product in the United States.
                    <SU>4</SU>
                    <FTREF/>
                     Aluminum Dynamics claim that is has interested party status within the meaning of section 771(9)(C) of the Act and 19 CFR 351.102(b)(29)(v) as a domestic producer of aluminum sheet in the United States.
                    <SU>5</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         the Petitioners' Letter, “Five-Year (1st Sunset) Review of the Countervailing Duty Order on Common Alloy Aluminum Sheet from Bahrain—Petitioners' Notice of Intent to Participate,” dated March 13, 2026; Petitioners' Letter, “Five-Year (1st Sunset) Review of the Countervailing Duty Order On Common Alloy Aluminum Sheet from India—Petitioners' Notice of Intent to Participate,” dated March 12, 2026; Petitioner's Letter, “Five-Year (1st Sunset) Review of the Countervailing Duty Order on Common Alloy Aluminum Sheet from Türkiye—Petitioners' Notice of Intent to Participate,” dated March 11, 2026 (Petitioner's Intent to Participate); and Aluminum Dynamics' Letter, “Five-Year (“Sunset”) Review of the Countervailing Duty Order on Common Alloy Aluminum Sheet from Bahrain: Notice of Intent to Participate,” dated March 17, 2026; Aluminum Dynamics” Letter, “Five-Year (“Sunset”) Review of the Countervailing Duty Order on Common Alloy Aluminum Sheet from India: Notice of Intent to Participate,” dated March 17, 2026; and Aluminum Dynamics' Letter, “Five-Year (“Sunset”) Review of the Countervailing Duty Order on Common Alloy Aluminum Sheet from the Republic of Türkiye: Notice of Intent to Participate,” dated March 17, 2026 (Aluminum Dynamics' Intent to Participate).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See</E>
                         Petitioners Intent to Participate at 4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         Aluminum Dynamics' Intent to Participate at 2.
                    </P>
                </FTNT>
                <P>
                    On March 31, 2026, Commerce received an adequate substantive response from the domestic interested parties, within the 30-day deadline specified in 19 CFR 351.218(d)(3)(i).
                    <SU>6</SU>
                    <FTREF/>
                     Commerce did not receive a substantive response from the Governments of Bahrain, India, or Türkiye or a respondent interested party to this proceeding. On April 29, 2026, Commerce notified the U.S. International Trade Commission (ITC) that it did not receive an adequate substantive response from respondent interested parties.
                    <SU>7</SU>
                    <FTREF/>
                     As a result, Commerce conducted an expedited (120-day) sunset review of the 
                    <E T="03">Orders,</E>
                     pursuant to section 751(c)(3)(B) of the Act and 19 CFR 351.218(e)(1)(ii)(B)(2) and (C)(2).
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         Petitioners' Letter, “Five-Year (1st Sunset) Review of the Countervailing Duty Order on Common Alloy Aluminum Sheet from Bahrain—Petitioner's Substantive Response to the Notice of Initiation,” dated March 31, 2026; Petitioners' Letter (Bahrain Substantive Response), “Five-Year (1st Sunset) Review of the Countervailing Duty Order on Common Alloy Aluminum Sheet from India—Petitioners' Substantive Response to the Notice of Initiation,” dated March 31, 2026 (India Substantive Response); and Petitioners' Letter, “Five-Year (1st Sunset) Review of the Countervailing Duty Order on Common Alloy Aluminum Sheet from Türkiye—Petitioners” Substantive Response to the Notice of Initiation,” dated March 31, 2026 (Türkiye Substantive Response).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         Commerce's Letter, “Sunset Reviews Initiated on March 2, 2026,” dated April 29, 2026.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Scope of the Orders</HD>
                <P>
                    The product covered by these 
                    <E T="03">Orders</E>
                     is aluminum sheet from Bahrain, India, and Türkiye. For the full description of the scope of the 
                    <E T="03">Orders, see</E>
                     the Issues and Decisions Memorandum.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         Memorandum, “Issues and Decision Memorandum for the Final Results of the Expedited Sunset Review of the Countervailing Duty Order on Common Alloy Aluminum Sheet from Bahrain, India, and the Republic of Türkiye,” dated concurrently with, and hereby adopted by, this notice.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Analysis of Comments Received</HD>
                <P>
                    A complete discussion of all issues raised in these sunset reviews, including the likelihood of continuation or recurrence of subsidization and the countervailable subsidy rates likely to prevail if the 
                    <E T="03">Orders</E>
                     were to be revoked, is contained in the accompanying Issues and Decision Memorandum.
                    <SU>9</SU>
                    <FTREF/>
                     A list of the topics discussed in the Issues and Decision Memorandum is attached as an appendix to this notice. The Issues and Decision Memorandum is a public document and is on file electronically via Enforcement and Compliance's Antidumping and Countervailing Duty Centralized Electronic Service System (ACCESS), which is available to registered users at 
                    <E T="03">https://access.trade.gov.</E>
                     In addition, complete versions of the Issues and Decision Memorandum can be accessed directly at 
                    <E T="03">https://access.trade.gov/frnotices.</E>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <PRTPAGE P="40980"/>
                <HD SOURCE="HD1">Final Results of Sunset Reviews</HD>
                <P>
                    Pursuant to sections 751(c) and 752(b) of the Act, Commerce determines that revocation of the 
                    <E T="03">Orders</E>
                     would be likely to lead to continuation or recurrence of countervailable subsidies at the following net countervailable subsidy rates:
                </P>
                <HD SOURCE="HD1">Bahrain</HD>
                <GPOTABLE COLS="2" OPTS="L2,nj,tp0,i1" CDEF="s100,18">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Producers/exporters</CHED>
                        <CHED H="1">
                            Net countervailable
                            <LI>subsidy rate</LI>
                            <LI>
                                (percent
                                <E T="03"> ad valorem</E>
                                )
                            </LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Gulf Aluminium Rolling Mill B.S.C</ENT>
                        <ENT>6.44</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">All Others</ENT>
                        <ENT>6.44</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">India</HD>
                <GPOTABLE COLS="2" OPTS="L2,nj,tp0,i1" CDEF="s100,18">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Producers/exporters</CHED>
                        <CHED H="1">
                            Net countervailable
                            <LI>subsidy rate</LI>
                            <LI>
                                (percent
                                <E T="03"> ad valorem</E>
                                )
                            </LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Hindalco Industries Limited</ENT>
                        <ENT>35.67</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Manaksia Aluminium Company Limited</ENT>
                        <ENT>5.70</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">All Others</ENT>
                        <ENT>30.77</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Türkiye</HD>
                <GPOTABLE COLS="2" OPTS="L2,nj,tp0,i1" CDEF="s100,18">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Producers/exporters</CHED>
                        <CHED H="1">
                            Net countervailable
                            <LI>subsidy rate</LI>
                            <LI>
                                (percent
                                <E T="03"> ad valorem</E>
                                )
                            </LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Assan Aluminyum Sanayi ve Ticaret A.S</ENT>
                        <ENT>6.28</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Teknik Aluminyum Sanayi A.S</ENT>
                        <ENT>4.94</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">All Others</ENT>
                        <ENT>7.59</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Notification Regarding Administrative Protective Orders</HD>
                <P>This notice also serves as the only reminder to parties subject to administrative protective order (APO) of their responsibility concerning the return or destruction of proprietary information disclosed under APO in accordance with 19 CFR 351.305. Timely notification of the return or destruction of APO materials, or conversion to judicial protective, orders is hereby requested. Failure to comply with the regulations and terms of an APO is a violation which is subject to sanction.</P>
                <HD SOURCE="HD1">Notification to Interested Parties</HD>
                <P>We are issuing and publishing these final results in accordance with sections 751(c), 752(b), and 777(i)(1) of the Act, and 19 CFR 351.221(c)(5)(ii).</P>
                <SIG>
                    <DATED>Dated: June 30, 2026.</DATED>
                    <NAME>Scot Fullerton,</NAME>
                    <TITLE>Acting Deputy Assistant Secretary for Antidumping and Countervailing Duty Operations.</TITLE>
                </SIG>
                <HD SOURCE="HD1">Appendix</HD>
                <EXTRACT>
                    <HD SOURCE="HD1">List of Topics Discussed in the Issues and Decision Memorandum</HD>
                    <FP SOURCE="FP-2">I. Summary</FP>
                    <FP SOURCE="FP-2">II. Background</FP>
                    <FP SOURCE="FP-2">
                        III. Scope of the 
                        <E T="03">Orders</E>
                    </FP>
                    <FP SOURCE="FP-2">
                        IV. History of the 
                        <E T="03">Orders</E>
                    </FP>
                    <FP SOURCE="FP-2">V. Legal Framework</FP>
                    <FP SOURCE="FP-2">VI. Discussion of the Issues</FP>
                    <FP SOURCE="FP1-2">1. Likelihood of Continuation or Recurrence of a Countervailable Subsidy</FP>
                    <FP SOURCE="FP1-2">2. Net Countervailable Subsidy Rates Likely To Prevail</FP>
                    <FP SOURCE="FP1-2">3. Nature of the Subsidies</FP>
                    <FP SOURCE="FP-2">VII. Final Results of Sunset Reviews</FP>
                    <FP SOURCE="FP-2">VIII. Recommendation</FP>
                </EXTRACT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13509 Filed 7-2-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>
                <DEPDOC>[A-851-804, A-580-909, A-821-826, A-823-819]</DEPDOC>
                <SUBJECT>Seamless Carbon and Alloy Steel Standard, Line, and Pressure Pipe From the Czech Republic, Republic of Korea, the Russian Federation, and Ukraine: Final Results of the Expedited First Sunset Reviews of the Antidumping Duty Orders</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Enforcement and Compliance, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The U.S. Department of Commerce (Commerce) finds that revocation of the antidumping duty (AD) orders on seamless carbon and alloy steel standard, line, and pressure pipe from the Czech Republic, Republic of Korea (Korea), the Russian Federation (Russia), and Ukraine would be likely to lead to continuation or recurrence of dumping, at the levels indicated in the “Final Results of Sunset Reviews” section of this notice.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Applicable July 6, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>David De Falco, Trade Agreements Policy and Negotiations, Enforcement and Compliance, International Trade Administration, U.S. Department of Commerce, 1401 Constitution Avenue NW, Washington, DC 20230; telephone: 202-482-2178.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On April 26, 2021, Commerce published the 
                    <E T="03">Czech Order</E>
                     in the 
                    <E T="04">Federal Register</E>
                     and on August 23, 2021, Commerce published the 
                    <E T="03">Korea Order, Russia Order,</E>
                     and 
                    <E T="03">Ukraine Order</E>
                     in the 
                    <E T="04">Federal Register</E>
                    .
                    <SU>1</SU>
                    <FTREF/>
                     On March 2, 2026, Commerce published the notice of initiation of this first sunset review of the 
                    <E T="03">Orders,</E>
                     pursuant to section 751(c) of 
                    <PRTPAGE P="40981"/>
                    the Tariff Act of 1930, as amended (the Act).
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See Seamless Carbon and Alloy Steel Standard, Line, and Pressure Pipe From the Republic of Korea, the Russian Federation, and Ukraine: Antidumping Duty Orders,</E>
                         86 FR 47055 (August 23, 2021) (
                        <E T="03">Korea Order, Russia Order, and Ukraine Order</E>
                        ); 
                        <E T="03">Seamless Carbon and Alloy Steel Standard, Line, and Pressure Pipe From the Czech Republic: Antidumping Duty Order,</E>
                         86 FR 22031, (April 26, 2021) (
                        <E T="03">Czech Order</E>
                        ) (collectively, 
                        <E T="03">Orders</E>
                        ).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See Initiation of Five-Year (Sunset) Reviews,</E>
                         91 FR 10053 (March 2, 2026).
                    </P>
                </FTNT>
                <P>
                    On March 16, 2026, Commerce received timely and complete notices of intent to participate in the sunset reviews from domestic interested party, Vallourec Star, LP (Vallourec), within the deadline specified in the 19 CFR 351.218(d)(1)(i).
                    <SU>3</SU>
                    <FTREF/>
                     Vallourec claimed interested party status under section 771(9)(C) of the Act as a U.S. producer of the domestic like product.
                    <SU>4</SU>
                    <FTREF/>
                     On March 24, 2026, Commerce notified the U.S. International Trade Commission (ITC) that it had received a notice of intent to participate from the domestic interested parties.
                    <SU>5</SU>
                    <FTREF/>
                     On March 31, 2026, pursuant to 19 CFR 351.218(d)(3)(i), domestic interested parties filed timely and adequate substantive responses.
                    <SU>6</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         Vallourec's Letter, “Five-Year (“Sunset”) Review of the Antidumping Duty Order on Seamless Carbon and Alloy Steel Standard, Line, and Pressure Pipe from the Russian Federation: Domestic Interested Parties' Notice of Intent to Participate,” dated March 16, 2026; Vallourec's Letter, “Notice of Intent to Participate in the First Five-Year Review of the Antidumping Duty Order on Seamless Carbon and Alloy Steel Standard, Line and Pressure Pipe from the Czech Republic,” dated March 16, 2026; Vallourec's Letter, “Notice of Intent to Participate in the First Five-Year Review of the Antidumping Duty Order on Seamless Carbon and Alloy Steel Standard, Line and Pressure Pipe from the Republic of Korea,” dated March 16, 2026; and Vallourec's Letter, “Notice of Intent to Participate in the First Five-Year Review of the Antidumping Duty Order on Seamless Carbon and Alloy Steel Standard, Line and Pressure Pipe from Ukraine,” dated March 16, 2026. (collectively, Notice of Intent Letters).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See</E>
                         Notice of Intent Letters.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         Commerce's Letter, “Sunset Reviews Initiated on March 2, 2026,” dated March 24, 2026.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         Vallourec's Letter, “Seamless Carbon and Alloy Steel Standard, Line and Pressure Pipe from the Czech Republic: Domestic Interested Party's Substantive Response to the Notice of Initiation,” dated March 31, 2026; Vallourec's Letter, “Five-Year (“Sunset”) Review of the Antidumping Duty Order on Seamless Carbon and Alloy Steel Standard, Line, and Pressure Pipe from the Russian Federation: Vallourec's Substantive Response,” dated March 31, 2026; Vallourec's Letter, “Seamless Carbon and Alloy Steel Standard, Line and Pressure Pipe from the Republic of Korea, the Russian Federation, and Ukraine: Domestic Interested Party's Substantive Response to the Notice of Initiation,” dated March 31, 2026; and Vallourec's Substantive Response,” dated March 31, 2026; Vallourec's Letter, “Notice of Intent to Participate in the First Five-Year Review of the Antidumping Duty Order on Seamless Carbon and Alloy Steel Standard, Line and Pressure Pipe from the Republic of Korea,” dated March 31, 2026.
                    </P>
                </FTNT>
                <P>
                    Commerce did not receive a substantive response from any respondent interested party. On April 29, 2026, Commerce notified the ITC that it did not receive substantive response from any respondent interested parties.
                    <SU>7</SU>
                    <FTREF/>
                     As a result, pursuant to section 751(c)(3)(B) of the Act and 19 CFR 351.218(e)(1)(ii)(C)(2), Commerce is conducting expedited (120-day) sunset reviews of the 
                    <E T="03">Orders.</E>
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         Commerce's Letter, “Sunset Reviews Initiated on March 2, 2026,” dated April 29, 2026.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Scope of the Orders</HD>
                <P>
                    The product covered by these 
                    <E T="03">Orders</E>
                     is Seamless Carbon and Alloy Steel Standard, Line, and Pressure Pipe from the Czech Republic, Korea, Russia, and Ukraine. For the full description of the scope of the 
                    <E T="03">Orders, see</E>
                     the Issues and Decisions Memorandum.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         Memorandum, “Issues and Decision Memorandum for the Final Results of the Expedited First Sunset Reviews of the Antidumping Duty Orders on Seamless Carbon and Alloy Steel Standard, Line, and Pressure Pipe from the Czech Republic, Republic of Korea, the Russian Federation, and Ukraine,” dated concurrently with, and hereby adopted by, this notice.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Analysis of Comments Received</HD>
                <P>
                    A complete discussion of all issues raised in this sunset review, including the likelihood of continuation or recurrence of dumping in the event of revocation of the 
                    <E T="03">Orders</E>
                     and the magnitude of the margins likely to prevail if the 
                    <E T="03">Orders</E>
                     were to be revoked, is provided in the accompanying Issues and Decision Memorandum.
                    <SU>9</SU>
                    <FTREF/>
                     A list of the topics discussed in the Issues and Decision Memorandum is attached in the appendix to this notice. The Issues and Decision Memorandum is a public document and is on file electronically via Enforcement and Compliance's Antidumping and Countervailing Duty Centralized Electronic Service System (ACCESS). ACCESS is available to registered users at 
                    <E T="03">https://access.trade.gov.</E>
                     In addition, a complete version of the Issues and Decision Memorandum can be directly accessed at 
                    <E T="03">https://access.trade.gov/frnotices.</E>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Final Results of Sunset Reviews</HD>
                <P>
                    Pursuant to sections 751(c)(1), 752(c)(1) and (3) of the Act, Commerce determines that revocation of the 
                    <E T="03">Orders</E>
                     would be likely to lead to continuation or recurrence of dumping, and that the magnitude of the dumping margins likely to prevail would be weighted-average dumping margins up to 51.70 percent for the Czech Republic, 4.48 percent for Korea, 209.72 percent for Russia, and 23.75 percent for Ukraine.
                </P>
                <HD SOURCE="HD1">Notification Regarding Administrative Protective Orders</HD>
                <P>This notice also serves as the only reminder to parties subject to administrative protective order (APO) of their responsibility concerning the return or destruction of proprietary information disclosed under APO in accordance with 19 CFR 351.305. Timely notification of the return or destruction of APO materials, or conversion to judicial protective, orders is hereby requested. Failure to comply with the regulations and terms of an APO is a violation which is subject to sanction.</P>
                <HD SOURCE="HD1">Notification to Interested Parties</HD>
                <P>We are issuing and publishing these final results in accordance with sections 751(c), 752(c), and 777(i)(1) of the Act, and 19 CFR 351.218 and 19 CFR 351.221(c)(5)(ii).</P>
                <SIG>
                    <DATED>Dated: June 30, 2026.</DATED>
                    <NAME>Scot Fullerton,</NAME>
                    <TITLE>Acting Deputy Assistant Secretary for Antidumping and Countervailing Duty Operations.</TITLE>
                </SIG>
                <APPENDIX>
                    <HD SOURCE="HED">Appendix</HD>
                    <HD SOURCE="HD1">List of Topics Discussed in the Issues and Decision Memorandum</HD>
                    <FP SOURCE="FP-2">I. Summary</FP>
                    <FP SOURCE="FP-2">II. Background</FP>
                    <FP SOURCE="FP-2">III. Scope of the Orders</FP>
                    <FP SOURCE="FP-2">IV. History of the Orders</FP>
                    <FP SOURCE="FP-2">V. Legal Framework</FP>
                    <FP SOURCE="FP-2">VI. Discussion of the Issues</FP>
                    <FP SOURCE="FP1-2">1. Likelihood of Continuation or Recurrence of Dumping</FP>
                    <FP SOURCE="FP1-2">2. Magnitude of the Margins of Dumping Likely to Prevail</FP>
                    <FP SOURCE="FP-2">VII. Final Results of Sunset Reviews</FP>
                    <FP SOURCE="FP-2">VIII. Recommendation</FP>
                </APPENDIX>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13489 Filed 7-2-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>Agency Information Collection Activities; Submission to the Office of Management and Budget (OMB) for Review and Approval; Comment Request; Request for Duty-Free Entry of Scientific Instrument or Apparatus</SUBJECT>
                <P>
                    The Department of Commerce will submit the following information collection request to the Office of Management and Budget (OMB) for review and clearance in accordance with the Paperwork Reduction Act of 1995, on or after the date of publication of this notice. We invite the general public and other Federal agencies to comment on proposed, and continuing information collections, which helps us assess the impact of our information collection requirements and minimize the public's reporting burden. Public comments were previously requested via the 
                    <E T="04">Federal Register</E>
                     on April 10, 2026, during a 60-day comment period. This notice allows for an additional 30 days for public comments.
                    <PRTPAGE P="40982"/>
                </P>
                <P>
                    <E T="03">Agency:</E>
                     Enforcement &amp; Compliance, International Trade Administration, Commerce.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Request for Duty-Free Entry of Scientific Instrument or Apparatus.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     0625-0037.
                </P>
                <P>
                    <E T="03">Form Number(s):</E>
                     ITA-338P.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Regular Submission, extension of a current information collection.
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     500.
                </P>
                <P>
                    <E T="03">Average Hours Per Response:</E>
                     2 hours.
                </P>
                <P>
                    <E T="03">Burden Hours:</E>
                     1000.
                </P>
                <P>
                    <E T="03">Needs and Uses:</E>
                     The Departments of Commerce and Homeland Security (“DHS”) are required to determine whether nonprofit institutions established for scientific or educational purposes are entitled to duty-free entry for scientific instruments the institutions import under the Florence Agreement. Form ITA-338P enables: (1) DHS to determine whether the statutory eligibility requirements for the institution and the instrument are fulfilled, and (2) Commerce to make a comparison and finding as to the scientific equivalency of comparable instruments being manufactured in the United States. Without the collection of information, DHS and Commerce would not have the necessary information to carry out the responsibilities of determining eligibility for duty-free entry assigned by law.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     State or local government; Federal agencies; not for-profit institutions.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     Every time respondent seeks to import qualifying equipment duty free.
                </P>
                <P>
                    <E T="03">Respondent's Obligation:</E>
                     Voluntary.
                </P>
                <P>
                    <E T="03">Legal Authority:</E>
                     19 U.S.C. 1202; 15 CFR 301.
                </P>
                <P>
                    This information collection request may be viewed at 
                    <E T="03">www.reginfo.gov.</E>
                     Follow the instructions to view the Department of Commerce collections currently under review by OMB.
                </P>
                <P>
                    Written comments and recommendations for the proposed information collection should be submitted within 30 days of the publication of this notice on the following website 
                    <E T="03">www.reginfo.gov/public/do/PRAMain.</E>
                     Find this particular information collection by selecting “Currently under 30-day Review—Open for Public Comments” or by using the search function and entering either the title of the collection or the OMB Control Number 0625-0037.
                </P>
                <SIG>
                    <NAME>Sheleen Dumas,</NAME>
                    <TITLE>Departmental PRA Compliance Officer, Office of the Under Secretary for Economic Affairs, Commerce Department.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13626 Filed 7-2-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>
                <DEPDOC>[C-580-910, C-821-827]</DEPDOC>
                <SUBJECT>Seamless Carbon and Alloy Steel Standard, Line, and Pressure Pipe From the Republic of Korea and the Russian Federation: Final Results of the Expedited First Sunset Review of the Countervailing Duty Orders</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Enforcement and Compliance, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The U.S. Department of Commerce (Commerce) finds that revocation of the countervailing duty (CVD) orders on seamless carbon and alloy steel standard, line, and pressure pipe (seamless pipe) from the Republic of Korea (Korea) and the Russian Federation (Russia) would be likely to lead to continuation or recurrence of countervailable subsidies at the levels indicated in the “Final Results of Sunset Reviews” section of this notice.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Applicable July 6, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>David De Falco, Trade Agreements Policy and Negotiations, Enforcement and Compliance, International Trade Administration, U.S. Department of Commerce, 1401 Constitution Avenue NW, Washington, DC 20230; telephone: 202-482-2178.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On August 23, 2021, the U.S. Department of Commerce (Commerce) published the 
                    <E T="03">Orders</E>
                     on seamless pipe from Korea and Russia.
                    <SU>1</SU>
                    <FTREF/>
                     On March 2, 2026, Commerce published the notice of initiation of the first sunset review of the 
                    <E T="03">Order,</E>
                     pursuant to section 751(c) of the Tariff Act of 1930 (the Act) and 19 CFR 351.218(c).
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See Seamless Carbon and Alloy Steel Standard, Line, and Pressure Pipe from the Republic of Korea and the Russian Federation: Countervailing Duty Orders,</E>
                         86 FR 47060 (August 23, 2021) (
                        <E T="03">Korea Order</E>
                        ) (
                        <E T="03">Russia Order</E>
                        ) (collectively, 
                        <E T="03">Orders</E>
                        ).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See Initiation of Five-Year (Sunset) Reviews,</E>
                         91 FR 10053 (March 2, 2026).
                    </P>
                </FTNT>
                <P>
                    On March 16, 2026, Commerce received a notice of intent to participate in this review from Vallourec Star, LP (Vallourec) (the domestic interested party), within the deadline specified in 19 CFR 351.218(d)(1)(i).
                    <SU>3</SU>
                    <FTREF/>
                     The domestic interested party claims that it has interested party status within the meaning of section 771(9)(C) of the Act and 19 CFR 351.102(b)(29)(v) as a producer of the domestic like product.
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         Vallourec's Letter, “Notice of Intent to Participate in the First Five-Year Review of the Countervailing Duty Order on Seamless Carbon and Alloy Steel Standard, Line and Pressure Pipe from the Republic of Korea,” dated March 16, 2026; and Vallourec's Letter “Five-Year (“Sunset”) Review of the Countervailing Duty Order on Seamless Carbon and Alloy Steel Standard, Line, and Pressure Pipe from the Russian Federation: Domestic Interested Parties' Notice of Intent to Participate”, dated March 16, 2026 (Intent to Participate).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">Id.</E>
                         at 2.
                    </P>
                </FTNT>
                <P>
                    On March 31, 2026, Commerce received an adequate substantive response from the domestic interested party, within the 30-day deadline specified in 19 CFR 351.218(d)(3)(i).
                    <SU>5</SU>
                    <FTREF/>
                     Commerce did not receive a substantive response from either the Government of Korea and Russia or a respondent interested party to this proceeding. On April 29, 2026, Commerce notified the U.S. International Trade Commission (ITC) that it did not receive an adequate substantive response from respondent interested parties.
                    <SU>6</SU>
                    <FTREF/>
                     As a result, Commerce conducted an expedited (120-day) sunset review of the 
                    <E T="03">Order,</E>
                     pursuant to section 751(c)(3)(B) of the Act and 19 CFR 351.218(e)(1)(ii)(B)(2) and (C)(2).
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         Vallourec's Letter, “Seamless Carbon and Alloy Steel Standard, Line and Pressure Pipe from the Republic of Korea, the Russian Federation, and Ukraine: Domestic Interested Party's Substantive Response to the Notice of Initiation” dated March 31, 2026 (Korea Substantive Response) and Vallourec's Letter “Five-Year (“Sunset”) Review of the Countervailing Duty Order on Seamless Carbon and Alloy Steel Standard, Line, and Pressure Pipe from the Russian Federation: Vallourec's Substantive Response,” dated March 31, 2026 (Russia Substantive Response).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         Commerce's Letter, “Sunset Reviews Initiated March 2, 2026,” dated April 29, 2026.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Scope of the Orders</HD>
                <P>
                    The product covered by these 
                    <E T="03">Orders</E>
                     is seamless pipe from Korea and Russia. For the full description of the scope of the 
                    <E T="03">Orders, see</E>
                     the Issues and Decisions Memorandum.
                    <SU>7</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         Memorandum, “Issues and Decision Memorandum for the Final Results of the Expedited Sunset Review of the Countervailing Duty Order on Seamless Carbon and Alloy Steel Standard, Line, and Pressure Pipe from the Republic of Korea and the Russian Federation,” dated concurrently with, and hereby adopted by, this notice.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Analysis of Comments Received</HD>
                <P>
                    A complete discussion of all issues raised in these sunset reviews, including the likelihood of continuation or recurrence of subsidization and the countervailable subsidy rates likely to prevail if the 
                    <E T="03">Orders</E>
                     were to be revoked, is contained in the accompanying Issues and Decision Memorandum.
                    <SU>8</SU>
                    <FTREF/>
                     A list of the topics discussed in the Issues and Decision Memorandum is attached as an appendix to this notice. The Issues and Decision Memorandum is a public document and is on file electronically via Enforcement and Compliance's 
                    <PRTPAGE P="40983"/>
                    Antidumping and Countervailing Duty Centralized Electronic Service System (ACCESS), which is available to registered users at 
                    <E T="03">https://access.trade.gov.</E>
                     In addition, complete versions of the Issues and Decision Memorandum can be accessed directly at 
                    <E T="03">https://access.trade.gov/frnotices.</E>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Final Results of Sunset Reviews</HD>
                <P>
                    Pursuant to sections 751(c) and 752(b) of the Act, Commerce determines that revocation of the 
                    <E T="03">Orders</E>
                     would be likely to lead to continuation or recurrence of countervailable subsidies at the following net countervailable subsidy rates:
                </P>
                <HD SOURCE="HD1">Korea</HD>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s50,12">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Producers/Exporters</CHED>
                        <CHED H="1">
                            Net countervailable subsidy rate (percent 
                            <E T="03">ad valorem</E>
                            )
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">ILJIN Steel Corporation</ENT>
                        <ENT>1.78</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">All Others</ENT>
                        <ENT>1.78</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Russia</HD>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s50,12">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Producers/Exporters</CHED>
                        <CHED H="1">
                            Net countervailable subsidy rate
                            <LI>
                                (percent 
                                <E T="03">ad valorem</E>
                                )
                            </LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">PAO TMK/Volzhsky Pipe Plant Joint Stock Company</ENT>
                        <ENT>48.38</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">All Others</ENT>
                        <ENT>48.38</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Notification Regarding Administrative Protective Orders</HD>
                <P>This notice also serves as the only reminder to parties subject to administrative protective order (APO) of their responsibility concerning the return or destruction of proprietary information disclosed under APO in accordance with 19 CFR 351.305. Timely notification of the return or destruction of APO materials, or conversion to judicial protective, orders is hereby requested. Failure to comply with the regulations and terms of an APO is a violation which is subject to sanction.</P>
                <HD SOURCE="HD1">Notification to Interested Parties</HD>
                <P>We are issuing and publishing these final results in accordance with sections 751(c), 752(b), and 777(i)(1) of the Act, and 19 CFR 351.221(c)(5)(ii).</P>
                <SIG>
                    <DATED>Dated: June 29, 2026.</DATED>
                    <NAME>Scot Fullerton,</NAME>
                    <TITLE>Acting Deputy Assistant Secretary for Antidumping and Countervailing Duty Operations.</TITLE>
                </SIG>
                <APPENDIX>
                    <HD SOURCE="HED">Appendix</HD>
                    <HD SOURCE="HD1">List of Topics Discussed in the Issues and Decision Memorandum</HD>
                    <FP SOURCE="FP-2">I. Summary</FP>
                    <FP SOURCE="FP-2">II. Background</FP>
                    <FP SOURCE="FP-2">III. Scope of the Orders</FP>
                    <FP SOURCE="FP-2">IV. History of the Orders</FP>
                    <FP SOURCE="FP-2">V. Legal Framework</FP>
                    <FP SOURCE="FP-2">VI. Discussion of the Issues</FP>
                    <FP SOURCE="FP1-2">1. Likelihood of Continuation or Recurrence of a Countervailable Subsidy</FP>
                    <FP SOURCE="FP1-2">2. Net Countervailable Subsidy Rates Likely to Prevail</FP>
                    <FP SOURCE="FP1-2">3. Nature of the Subsidies</FP>
                    <FP SOURCE="FP-2">VII. Final Results of Sunset Reviews</FP>
                    <FP SOURCE="FP-2">VIII. Recommendation</FP>
                </APPENDIX>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13490 Filed 7-2-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>
                <DEPDOC>[A-893-001, A-400-001, A-557-820]</DEPDOC>
                <SUBJECT>Silicon Metal From Bosnia and Herzegovina, Iceland, and Malaysia: Final Results of the Expedited First Sunset Reviews of the Antidumping Duty Orders</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Enforcement and Compliance, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The U.S. Department of Commerce (Commerce) finds that revocation of the antidumping duty (AD) orders on silicon metal from Bosnia and Herzegovina, Iceland, and Malaysia would be likely to lead to continuation or recurrence of dumping, at the levels indicated in the “Final Results of Sunset Reviews” section of this notice.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Applicable July 6, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>David De Falco, Trade Agreements Policy and Negotiations, Enforcement and Compliance, International Trade Administration, U.S. Department of Commerce, 1401 Constitution Avenue NW, Washington, DC 20230; telephone: (202) 482-2178.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On April 19, 2021, Commerce published the 
                    <E T="03">Bosnia and Herzegovina Order</E>
                     and the 
                    <E T="03">Iceland Order,</E>
                     and on August 19 2021, Commerce published the 
                    <E T="03">Malaysia Order</E>
                     in the 
                    <E T="04">Federal Register</E>
                    .
                    <SU>1</SU>
                    <FTREF/>
                     On March 2, 2026, Commerce published the notice of initiation of these first sunset reviews of the 
                    <E T="03">Orders,</E>
                     pursuant to section 751(c) of the Tariff Act of 1930, as amended (the Act).
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See Silicon Metal from Bosnia and Herzegovina and Iceland: Antidumping Duty Orders,</E>
                         86 FR 20364 (April 19, 2021) (
                        <E T="03">Bosnia and Herzegovina Order, Iceland Order</E>
                        ); and 
                        <E T="03">Silicon Metal from Malaysia: Antidumping Duty Order,</E>
                         86 FR 46677 (August 19, 2021) (
                        <E T="03">Malaysia Order</E>
                        ) (collectively, 
                        <E T="03">Orders</E>
                        ).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See Initiation of Five-Year (Sunset) Reviews,</E>
                         91 FR 10053 (March 2, 2026).
                    </P>
                </FTNT>
                <P>
                    On March 17 2026, Commerce received a timely and complete notice of intent to participate in the sunset review from the domestic interested parties 
                    <SU>3</SU>
                    <FTREF/>
                     within the deadline specified in the 19 CFR 351.218(d)(1)(i).
                    <SU>4</SU>
                    <FTREF/>
                     The domestic interested parties claimed the interested party status within the meaning of section 771(9)(C) of the Act as domestic producers of subject merchandise.
                    <SU>5</SU>
                    <FTREF/>
                     On March 24, 2026, Commerce notified the U.S. International Trade Commission (ITC) that it had received a notice of intent to participate from the domestic interested parties.
                    <SU>6</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         The domestic interested parties are Ferroglobe USA, Inc. and Mississippi Silicon LLC.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See</E>
                         Domestic Interested Party's Letter, “Silicon Metal from Bosnia and Herzegovina: Notice of Intent to Participate in Sunset Review,” dated March 17, 2026, “Silicon Metal from Iceland: Notice of Intent to Participate in Sunset Review,” dated March 17, 2026, and “Silicon Metal from Malaysia: Notice of Intent to Participate in Sunset Review,” dated March 17, 2026.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">Id.</E>
                         at 1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         Commerce's Letter, “Sunset Reviews Initiated on March 2, 2026,” dated March 24, 2026.
                    </P>
                </FTNT>
                <P>
                    On April 1, 2026, pursuant to 19 CFR 351.218(d)(3)(i), domestic interested parties filed a timely and adequate substantive response.
                    <SU>7</SU>
                    <FTREF/>
                     Commerce did not receive a substantive response from any respondent interested party. On April 29, 2026, Commerce notified the ITC that it did not receive substantive response from any respondent interested parties.
                    <SU>8</SU>
                    <FTREF/>
                     As a result, pursuant to section 751(c)(3)(B) of the Act and 19 CFR 351.218(e)(1)(ii)(C)(2), Commerce is conducting expedited (120-day) sunset reviews of the 
                    <E T="03">Orders.</E>
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         Domestic Interested Party's Letters, “Silicon Metal from Bosnia and Herzegovina: Substantive Response to Notice of Initiation of Sunset Review,” dated April 1, 2026, “Silicon Metal from Iceland: Substantive Response to Notice of Initiation of Sunset Review,” dated April 1, 2026, and “Silicon Metal from Malaysia: Substantive Response to Notice of Initiation of Sunset Review,” dated April 1, 2026.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         Commerce's Letter, “Sunset Reviews Initiated on March 2, 2026,” dated April 29, 2026.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Scope of the Orders</HD>
                <P>
                    The product covered by these 
                    <E T="03">Orders</E>
                     is silicon metal from Bosnia and Herzegovina, Iceland, and Malaysia. For the full description of the scope of the 
                    <PRTPAGE P="40984"/>
                    <E T="03">Orders, see</E>
                     the Issues and Decisions Memorandum.
                    <SU>9</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See</E>
                         Memorandum, “Issues and Decision Memorandum for the Final Results of the Expedited First Sunset Reviews of the Antidumping Duty Order on Silicon Metal from Bosnia and Herzegovina, Iceland and Malaysia,” dated concurrently with, and hereby adopted by, this notice (Issues and Decision Memorandum).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Analysis of Comments Received</HD>
                <P>
                    A complete discussion of all issues raised in these sunset reviews, including the likelihood of continuation or recurrence of dumping in the event of revocation of the 
                    <E T="03">Orders</E>
                     and the magnitude of the margins likely to prevail if the 
                    <E T="03">Orders</E>
                     were to be revoked, is provided in the Issues and Decision Memorandum.
                    <SU>10</SU>
                    <FTREF/>
                     A list of the topics discussed in the Issues and Decision Memorandum is attached in the appendix to this notice. The Issues and Decision Memorandum is a public document and is on file electronically via Enforcement and Compliance's Antidumping and Countervailing Duty Centralized Electronic Service System (ACCESS), which is available to registered users at 
                    <E T="03">https://access.trade.gov.</E>
                     In addition, a complete version of the Issues and Decision Memorandum can be directly accessed at 
                    <E T="03">https://access.trade.gov/frnotices.</E>
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Final Results of Sunset Reviews</HD>
                <P>
                    Pursuant to sections 751(c)(1), 752(c)(1) and (3) of the Act, Commerce determines that revocation of the 
                    <E T="03">Orders</E>
                     would be likely to lead to continuation or recurrence of dumping, and that the magnitude of the dumping margins likely to prevail would be weighted-average dumping margins up to 21.41 percent for Bosnia and Herzegovina, 47.54 percent for Iceland, and 12.27 percent for Malaysia.
                </P>
                <HD SOURCE="HD1">Notification Regarding Administrative Protective Order (APO)</HD>
                <P>This notice also serves as the only reminder to parties subject to an APO of their responsibility concerning the return or destruction of proprietary information disclosed under APO in accordance with 19 CFR 351.305. Timely notification of the return or destruction of APO materials, or conversion to judicial protective, orders is hereby requested. Failure to comply with the regulations and terms of an APO is a violation which is subject to sanction.</P>
                <HD SOURCE="HD1">Notification to Interested Parties</HD>
                <P>We are issuing and publishing these final results in accordance with sections 751(c), 752(c), and 777(i)(1) of the Act, and 19 CFR 351.218 and 19 CFR 351.221(c)(5)(ii).</P>
                <SIG>
                    <DATED>Dated: June 30, 2026.</DATED>
                    <NAME>Scot Fullerton,</NAME>
                    <TITLE>Acting Deputy Assistant Secretary for Antidumping and Countervailing Duty Operations.</TITLE>
                </SIG>
                <HD SOURCE="HD1">Appendix</HD>
                <EXTRACT>
                    <HD SOURCE="HD1">List of Topics Discussed in the Issues and Decision Memorandum</HD>
                    <FP SOURCE="FP-2">I. Summary</FP>
                    <FP SOURCE="FP-2">II. Background</FP>
                    <FP SOURCE="FP-2">
                        III. Scope of the 
                        <E T="03">Orders</E>
                    </FP>
                    <FP SOURCE="FP-2">
                        IV. History of the 
                        <E T="03">Orders</E>
                    </FP>
                    <FP SOURCE="FP-2">V. Legal Framework</FP>
                    <FP SOURCE="FP-2">VI. Discussion of the Issues</FP>
                    <FP SOURCE="FP1-2">1. Likelihood of Continuation or Recurrence of Dumping</FP>
                    <FP SOURCE="FP1-2">2. Magnitude of the Margins of Dumping Likely to Prevail</FP>
                    <FP SOURCE="FP-2">VII. Final Results of Sunset Reviews</FP>
                    <FP SOURCE="FP-2">VIII. Recommendation</FP>
                </EXTRACT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13512 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <SUBJECT>Agency Information Collection Activities; Submission to the Office of Management and Budget (OMB) for Review and Approval; Comment Request; Wage Mariner Hiring Portal</SUBJECT>
                <P>
                    The Department of Commerce will submit the following information collection request to the Office of Management and Budget (OMB) for review and clearance in accordance with the Paperwork Reduction Act of 1995, on or after the date of publication of this notice. We invite the general public and other Federal agencies to comment on proposed, and continuing information collections, which helps us assess the impact of our information collection requirements and minimize the public's reporting burden. Public comments were previously requested via the 
                    <E T="04">Federal Register</E>
                     on May 1, 2026, during a 60-day comment period. This notice allows for an additional 30 days for public comments.
                </P>
                <P>
                    <E T="03">Agency:</E>
                     National Oceanic and Atmospheric Administration, Commerce.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Wage Mariner Hiring Portal.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     0648-0790.
                </P>
                <P>
                    <E T="03">Form Number(s):</E>
                     None.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Regular submission [extension of a current information collection].
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     1,000.
                </P>
                <P>
                    <E T="03">Average Hours Per Response:</E>
                     60 minutes: 5 minutes to fill our applicant's first and last name and contact mobile and or home number and email address; 5 minutes to fill out wage mariner license specific information; 40 minutes to enter wage mariner certifications and relevant past work history; and 10 minutes to fill out relevant educational history.
                </P>
                <P>
                    <E T="03">Total Annual Burden Hours:</E>
                     1,000.
                </P>
                <P>
                    <E T="03">Needs and Uses:</E>
                     This is a request for extension of an existing information collection.
                </P>
                <P>The Wage Mariner Hiring Portal (WMHP) is an internet-based system (website) that is designed to allow an applicant to apply for a “wage mariner” position within the National Oceanic and Atmospheric Administration (NOAA) fleet of maritime vessels. The WMHP system collects basic user information, wage mariner licensing, certifications, and relevant current and or past work history. The Department of Commerce (DOC), through NOAA, Office of Marine and Aviation Operations (OMAO) has special hiring authority under Code of Federal Regulations (CFR), Title 5, Chapter 1, Subchapter A, Part 3, § 3.2 and under the DOC Department Administrative Order (DAO) 202-302 Section 2, Subsection .02a. specific to the hiring of federal wage mariner employees. The regulations allow OMAO to hire wage mariners into excepted service positions within the NOAA fleet of ocean-going vessels in order to maintain adequate operations, maintenance, and safe staffing of the maritime ships.</P>
                <P>No physical forms are used in this collection, it is all online. Applicants fill out basic personal, licensure, and work history information into a profile resume. Once their basic profile is complete, applicants can submit this resume to available wage mariner positions as shown on the WMHP website. The application information received is used to determine if the applicant meets the basic job qualification. The applicant's information is then passed on to the hiring official or it is placed in a pool of prospective candidates for future openings. Application information includes: first and last name, contact number and email address, wage mariner licenses and certifications, relevant work history.</P>
                <P>
                    <E T="03">Affected Public:</E>
                     Individuals or households.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     Once.
                </P>
                <P>
                    <E T="03">Respondent's Obligation:</E>
                     Required to Obtain or Retain Benefits.
                </P>
                <P>
                    <E T="03">Legal Authority:</E>
                     Code of Federal Regulations (CFR), Title 5, Chapter 1, Subchapter A, Part 3, § 3.2.
                </P>
                <P>
                    This information collection request may be viewed at 
                    <E T="03">www.reginfo.gov.</E>
                     Follow the instructions to view the 
                    <PRTPAGE P="40985"/>
                    Department of Commerce collections currently under review by OMB.
                </P>
                <P>
                    Written comments and recommendations for the proposed information collection should be submitted within 30 days of the publication of this notice on the following website 
                    <E T="03">www.reginfo.gov/public/do/PRAMain.</E>
                     Find this particular information collection by selecting “Currently under 30-day Review—Open for Public Comments” or by using the search function and entering either the title of the collection or the OMB Control Number 0648-0790.
                </P>
                <SIG>
                    <NAME>Sheleen Dumas,</NAME>
                    <TITLE>Departmental PRA Compliance Officer, Office of the Under Secretary for Economic Affairs, Commerce Department.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13625 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-12-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF DEFENSE</AGENCY>
                <SUBAGY>Office of the Secretary</SUBAGY>
                <SUBJECT>TRICARE Demonstration Project for TRICARE Ambulance Add-On Reimbursement for Pre-Hospital Blood Transfusion</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Defense Health Agency, Department of Defense (DoD).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of demonstration project.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The DoD (referred to herein as “the Department”, “Department of War” or “DoW”) is announcing a new demonstration project under the TRICARE program, titled the “TRICARE Demonstration Project for Pre-Hospital Blood Transfusion Ambulance Add-On Reimbursement,” also called “The TRICARE PHBT Demonstration” or “PHBTD”. This five-year demonstration will test the effectiveness of providing separate, unbundled add-on reimbursement to the TRICARE ambulance fee schedule for the cost of medically necessary blood products and professional services administered by authorized ambulance providers in a pre-hospital (ambulance, air or ground) setting. The goal is to evaluate whether this payment modification improves health outcomes for trauma patients, impacts total cost of care, enhances beneficiary access to care and network adequacy, and is a feasible and advisable permanent change to the TRICARE reimbursement methodology for ambulance services.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This demonstration project will be effective January 1, 2027.</P>
                    <P>
                        <E T="03">Demonstration Duration:</E>
                         The demonstration will run for a period of five years, concluding on December 31, 2031. Defense Health Agency (DHA) may extend the demonstration to allow for further data collection and analysis; extensions will be published in the implementing instructions (TRICARE Manuals). The Director, DHA, may also terminate the demonstration early or make modifications to the demonstration, as described in the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                        .
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Ms. Elan Green, (303) 676-3907, 
                        <E T="03">elan.p.green.civ@health.mil.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">A. Background</HD>
                <HD SOURCE="HD2">1. Need for Demonstration</HD>
                <P>The administration of blood products in the pre-hospital environment, a practice pioneered by military medicine, is a critical, life-saving intervention that stabilizes patients and improves survival rates. As a result of its proven success, civilian Emergency Medical Services (EMS) agencies are increasingly seeking to adopt PHBT protocols. When medically necessary, pre-hospital blood transfusions are extremely important and there is extensive literature that discusses the life-saving effects of receiving PHBT. Despite the potential health benefits of receiving PHBT, not all TRICARE beneficiaries have access to PHBT.</P>
                <P>This demonstration is prompted by recent Federal action and significant stakeholder feedback regarding reimbursement for pre-hospital blood. The Centers for Medicare &amp; Medicaid Services recently finalized a rule that expands the definition of Advanced Life Support, Level 2 (ALS2) to include PHBT, and bundles the payment into the existing ALS2 rate. Key stakeholder groups, including America's Blood Centers, the Association for the Advancement of Blood &amp; Biotherapies, and the Prehospital Blood Transfusion Initiative Coalition, argued that this bundled payment is financially unsustainable for most EMS agencies. These groups highlight that the bundled rate fails to cover the high costs of blood products, initial equipment, and annual program maintenance. This financial barrier may prevent the widespread adoption of PHBT, limiting access for all patients, including TRICARE beneficiaries.</P>
                <P>The Agency's initial analysis suggests that PHBT may not be adequately reimbursed by the ALS2 rate. Under the Outpatient Prospective Payment System (OPPS), Medicare and TRICARE reimburse hospital outpatient departments approximately $225 (as of October 1, 2025) for a unit of blood using Healthcare Common Procedure Coding System (HCPCS) code P9010. This is likely a lower-bound estimate of the overall cost of providing blood in an ambulance for two major reasons: first, although $225 is a reasonable cost for packed red blood cells, the blood delivered in ambulances is typically low titer O positive whole blood (LTOPWB), which is more expensive. The costs of PHBT in an ambulance may also be higher because of the overhead costs associated with maintaining a blood supply. One researcher reports that the cost of PHBT is approximately $925 per patient due to both factors. Another researcher found that in 2024, of the EMS agencies that responded to a survey, over 70 percent reported costs over $500 per unit of blood and that over one-third of those who responded had costs above $800 (Hurson, 2025). If one bases the cost of a unit of blood on the OPPS allowed amount ($225), the difference between ALS1 and ALS2 reimbursement ($237) is more than the cost of the blood. For more expensive blood products that are typically used in an ambulance (such as LTOPWB) the costs of blood alone exceed the $237 difference.</P>
                <P>Even if the additional amount received by ambulance providers for an ALS2 transport relative to an ALS1 ($237) exceeds the costs of a unit of blood, it does not necessarily mean that there is not a gap in reimbursement because the ALS2 differential also must cover the other costly services that ALS2 patients receive relative to ALS1 patients. To qualify for reimbursement as an ALS2 transport in 2025, an ambulance must provide at least three separate intravenous (IV) administrations of medications or provide at least one of the following eight services: (1) manual defibrillation; (2) endotracheal intubation; (3) a central venous line; (4) cardiac pacing; (5) chest decompression; (6) a surgical airway; (7) an intraosseous line; or (8) PHBT.</P>
                <HD SOURCE="HD2">2. Current TRICARE Reimbursement for PHBT in Relation to the Cost</HD>
                <P>
                    By law, TRICARE reimburses both ground and air ambulance services according to the Medicare Ambulance Fee Schedule (AFS), which bundles the cost of all medical supplies into a single base rate payment. Under the AFS, Medicare and TRICARE pay a base fee and a separate mileage fee for each emergency transport. The level of the base payment for ground ambulances is a function of the type of care provided. For example, in 2025, the Medicare/TRICARE base reimbursement amount for Basic Life Support Emergency transport was $446.37 while the base payment for ALS1 Emergency transport was $530.06. Although Medicare does 
                    <PRTPAGE P="40986"/>
                    not provide a separate additional reimbursement amount for the costs of PHBT, starting in 2025, any emergency transport that uses PHBT qualifies under Medicare (and TRICARE) for reimbursement as ALS2 Emergency transport, which has a base amount of $767.20.
                </P>
                <HD SOURCE="HD2">3. Statutory Authority for Demonstration</HD>
                <P>This demonstration project is established under the authority of section 1092 of title 10, United States Code (U.S.C.), which permits the Secretary of War to conduct studies and demonstration projects to test the feasibility of alternative methods of payment for and innovative approaches to the delivery and financing of health and medical care services. For TRICARE For Life (TFL) beneficiaries, the statutory requirement at 10 U.S.C. 1086(d)(3)(A) establishes that TRICARE payment is strictly limited to the beneficiary's actual out-of-pocket costs remaining after Medicare reimburses for covered services and limits the amount the Department's reimbursement to what it would have paid as primary. If these statutory limits were applied to the proposed PHBT add-on, TRICARE would be restricted in what it could reimburse, effectively placing TFL beneficiaries on the hook for 75% or more of this new add-on cost. To mitigate this and properly evaluate the payment model, the demonstration will test the TRICARE add-on payment without limiting the amount paid for TFL beneficiaries to their standard Medicare liability for only those claims where PHB is provided.</P>
                <P>However, should the agency find the demonstration to be successful and wish to implement the add-on reimbursement permanently for TFL beneficiaries, statutory relief from 10 U.S.C. 1086(d)(3) will be required. Otherwise, TFL beneficiaries must be excluded from the permanent implementation of an add-on reimbursement.</P>
                <HD SOURCE="HD1">B. Description of Demonstration Project</HD>
                <HD SOURCE="HD2">1. Purpose</HD>
                <P>The purpose of this demonstration is to test the hypothesis that providing a supplementary add-on reimbursement for PHBT rendered during a medically necessary ALS2, Specialty Care Transport (SCT), or air ambulance transport will: (1) improve beneficiary outcomes during hemorrhagic shock; (2) reduce total cost of care; (3) improve access to PHBT and/or ambulance network adequacy; and (3) be administratively feasible to implement.</P>
                <HD SOURCE="HD2">2. Eligible Beneficiaries</HD>
                <P>Eligible beneficiaries are those with coverage under TRICARE Prime-including Active-Duty Service Members, TRICARE Select, or TRICARE for Life (including those enrolled in a Medicare Advantage Plan). Beneficiaries enrolled in the Uniformed Services Family Health Plan, Competitive Plans Demonstration (or future iterations), or claims outside of the 50 United States and territories (where the AFS does not apply) are also excluded. Beneficiaries with Other Health Insurance where TRICARE is not primary are also excluded.</P>
                <HD SOURCE="HD2">3. Eligible Providers</HD>
                <P>Providers eligible to participate are TRICARE-authorized ground and air ambulance companies as described in 32 CFR 199.6 and reimbursed in accordance with § 199.14 and limited to those ambulance providers who are authorized to administer PHB under the scope of their license.</P>
                <HD SOURCE="HD2">4. Eligible Services</HD>
                <P>The add-on reimbursement will apply to the administration of Low Titer O+ and O- Whole Blood, Packed Red Blood Cells (PRBCs), Plasma, or a combination of PRBCs and plasma provided during medically necessary ALS2, SCT, or air transport, where the administration of the blood product was medically necessary. An additional add-on reimbursement will also be available for the professional services required in the administration of medically necessary blood products.</P>
                <HD SOURCE="HD2">5. Add-on Reimbursement Methodology</HD>
                <P>The gap in reimbursement of PHBT under ALS2 reimbursement is unclear; thus, establishing an add-on reimbursement rate is challenging. Journal articles on the subject show wide variability in reported costs associated with the provision of PHBT depending on a variety of factors and the individual facts of each transport. However, to ensure that this is administratively feasible to operate, the Agency has determined that a two-tiered add-on reimbursement will be the most administratively feasible and will provide financial predictability to both providers and the Department. For the purposes of this demonstration, the Agency is establishing an add-on reimbursement at the highest of:</P>
                <P>(1) The rate used for the TRICARE Hospital OPPS for blood products using the appropriate HCPCS code—which we anticipate will most commonly be HCPCS code P9010 (or updated/revised codes, if modified in the future). Under this approach, if an ambulance provider billed for a medically necessary ALS2, SCT, or air transport, and provided PHBT with whole blood, the ambulance provider would be required to include HCPCS code P9010 on the claim to receive the add-on reimbursement at the OPPS rate per unit of blood (currently $189.84).</P>
                <P>(2) The cost of the blood products as provided on an invoice from the blood bank or supplier. Blood suppliers generally operate on a cost-reimbursable basis; that is, they are non-profit organizations that charge for the cost of the blood product collection and processing. Under this option, ambulance providers may be reimbursed for the actual cost of the blood that is provided if an invoice for the PHBT is provided with the ambulance claim. Ambulance providers will not be required to provide an invoice, however, if they do not submit an invoice they will be paid the OPPS rate.</P>
                <P>Ambulance providers may also bill for the administration of the transfusion using CPT 36430, direct blood transfusion administration (or subsequent codes, if modified), one time during the transport. This code will be eligible for reimbursement at the rate established by the CHAMPUS Maximum Allowable Charge system, which is currently approximately $40. Additional payments for supplies will not be allowed, as supplies (to include fluid re-warmers and intravenous drug therapy supplies) are already bundled into the ALS2 rate.</P>
                <HD SOURCE="HD2">6. Implementation Details</HD>
                <P>
                    The DHA will publish additional details on implementation of the demonstration in the TRICARE Manuals. The TRICARE Manuals may be accessed at 
                    <E T="03">http://manuals.health.mil/.</E>
                </P>
                <HD SOURCE="HD2">7. Demonstration Modification or Termination</HD>
                <P>
                    The Director, DHA, or designee, may terminate or modify this demonstration at any time should it be determined that the ongoing demonstration as implemented is no longer in the interest of the Department. Justification for termination or modification may include but not be limited to: changes by Medicare in their reimbursement methodology related to PHBT; minimal use of the demonstration (
                    <E T="03">e.g.,</E>
                     fewer than 250 claims in one year); or lack of evidence that the add-on reimbursement is achieving the goals of this demonstration. Modifications will be published in the implementing instructions. Termination will be 
                    <PRTPAGE P="40987"/>
                    published in a subsequent 
                    <E T="04">Federal Register</E>
                     notice.
                </P>
                <HD SOURCE="HD2">8. Cost Estimate</HD>
                <P>We estimate this demonstration will cost approximately $100,000.00 in administrative costs. $4.6M in health care costs over the five years, and $500,000 for the program evaluation. There is substantial uncertainty surrounding this estimate, as it is very challenging to predict the uptake or expansion of PHBT.</P>
                <HD SOURCE="HD2">9. Beneficiary Cost Sharing</HD>
                <P>Beneficiaries will be subject to the cost-sharing, deductibles, and co-payments that apply to their plan. As most ambulance providers are out of network, and beneficiaries have percentage-based copayments for out of network providers, beneficiaries may experience increases in their out-of-pocket costs. These increases are a result of the increased allowable amounts under this demonstration. Although TFL beneficiaries generally have their Medicare liability limited to their Medicare co-payments, under this demonstration project TFL beneficiaries will have an add-on co-pay of 25 percent of the TRICARE allowed ambulance add-on reimbursement for authorized PHBT.</P>
                <HD SOURCE="HD2">10. Demonstration Analysis</HD>
                <P>The Department will evaluate the success of the demonstration in Year 5. The evaluation will attempt to determine if the add-on reimbursement for PHBT: (1) improved beneficiary outcomes; (2) reduced total cost of care; (3) improved access to PHBT and/or ambulance network adequacy; and (4) was administratively feasible to implement. This analysis will be primarily based on retrospective claims data and thus will be limited in its ability to draw conclusions regarding causality.</P>
                <SIG>
                    <DATED>Dated: June 30, 2026.</DATED>
                    <NAME>Stephanie J. Bost,</NAME>
                    <TITLE>Alternate OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13515 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6001-FR-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
                <SUBAGY>Office of the Secretary</SUBAGY>
                <SUBJECT>Department of Defense Wage Committee (DoDWC); Notice of Federal Advisory Committee Meetings</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Under Secretary of Defense for Personnel and Readiness (USD(P&amp;R)), Department of Defense (DoD).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of closed Federal advisory committee meetings.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The DoD (referred to herein as “the Department”, “Department of War” or “DoW”) is publishing this notice to announce that the following Federal Advisory Committee meetings of the DoDWC will take place.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P/>
                    <P>Tuesday, June 23, 2026, from 10:00 a.m. to 11:30 a.m. and will be closed to the public.</P>
                    <P>Tuesday, July 7, 2026, from 10:00 a.m. to 10:30 a.m. and will be closed to the public.</P>
                    <P>Tuesday, July 21, 2026, from 10:00 a.m. to 11:30 a.m. and will be closed to the public.</P>
                    <P>Tuesday, August 4, 2026, from 10:00 a.m. to 10:30 a.m. and will be closed to the public.</P>
                    <P>Tuesday, August 18, 2026, from 10:00 a.m. to 11:30 a.m. and will be closed to the public.</P>
                    <P>Tuesday, September 1, 2026, from 10:00 a.m. to 10:30 a.m. and will be closed to the public.</P>
                    <P>Tuesday, September 15, 2026, from 10:00 a.m. to 11:00 a.m. and will be closed to the public.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Meetings will be held via Microsoft Teams.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Mr. Karl Fendt, Designated Federal Officer (DFO) (571) 372-1618 (voice), 
                        <E T="03">karl.h.fendt.civ@mail.mil</E>
                        . (email), 4800 Mark Center Drive, Suite 05G21, Alexandria, Virginia 22350 (mailing address). Any agenda updates can be found at the DoDWC's official website: 
                        <E T="03">https://wageandsalary.dcpas.osd.mil/BWN/DODWC/</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>These meetings are held under the provisions of chapter 10 of title 5, United States Code (U.S.C.) (commonly known as the “Federal Advisory Committee Act” or “FACA”), subsection 552b(c) of title 5, U.S.C. and 41 Code of Federal Regulations (CFR) 102-3.140 and 102-3.155.</P>
                <P>
                    <E T="03">Purpose of the Meeting:</E>
                     The purpose of these meetings is to provide independent advice and recommendations on matters relating to the conduct of wage surveys and the establishment of wage schedules for all appropriated fund and non-appropriated fund areas of blue-collar employees within the DoW.
                </P>
                <P>Due to circumstances beyond the control of the DFO and the DoW, the DoDWC was unable to provide public notification required by 41 CFR 102-3.150(a) concerning its June 23, 2026 meeting. Accordingly, the Advisory Committee Management Officer for the DoW, pursuant to 41 CFR 102-3.150(b), waives the public notification requirement.</P>
                <P>Due to circumstances beyond the control of the DFO and the DoW, the DoDWC was unable to provide public notification required by 41 CFR 102-3.150(a) concerning its July 7, 2026 meeting. Accordingly, the Advisory Committee Management Officer for the DoW, pursuant to 41 CFR 102-3.150(b), waives the public notification requirement.</P>
                <HD SOURCE="HD1">Agenda</HD>
                <HD SOURCE="HD2">June 23, 2026</HD>
                <P>Opening Remarks by Chair, Mr. Eric Clayton, and DFO, Mr. Karl Fendt.</P>
                <P>Reviewing survey results and/or survey specifications for the following Non-appropriated Fund areas:</P>
                <P>1. Any items needing further clarification or action from the previous meeting.</P>
                <P>2. Wage Schedule (Full Scale) for the Cumberland, Pennsylvania wage area (AC-092).</P>
                <P>3. Wage Schedule (Full Scale) for the York, Pennsylvania wage area (AC-093).</P>
                <P>4. Wage Schedule (Full Scale) for the Honolulu, Hawaii wage area (AC-106).</P>
                <P>5. Wage Schedule (Full Scale) for the Norfolk-Portsmouth-VA Beach, Virginia wage area (AC-111).</P>
                <P>6. Wage Schedule (Full Scale) for the Hampton-Newport News, Virginia wage area (AC-112).</P>
                <P>7. Wage Schedule (Full Scale) for the Harford, Maryland wage area (AC-148).</P>
                <P>8. Wage Schedule (Wage Change) for the McLennan, Texas wage area (AC-022).</P>
                <P>9. Wage Schedule (Wage Change) for the Jefferson, New York wage area (AC-101).</P>
                <P>10. Wage Schedule (Wage Change) for the Orange, New York wage area (AC-103).</P>
                <P>11. Wage Schedule (Wage Change) for the Macomb, Michigan wage area (AC-162).</P>
                <P>12. Wage Schedule (Wage Change) for the Niagara, New York wage area (AC-163).</P>
                <P>Reviewing survey results and/or survey specifications for the following Appropriated Fund areas:</P>
                <P>13. Wage Schedule (Full Scale) for the Huntsville, Alabama wage area (AC-004).</P>
                <P>14. Wage Schedule (Full Scale) for the Tampa-St. Petersburg, Florida wage area (AC-035).</P>
                <P>15. Wage Schedule (Wage Change) for the New Haven-Hartford, Connecticut wage area (AC-024).</P>
                <P>
                    16. Wage Schedule (Wage Change) for the Cleveland-Akron-Canton, Ohio wage area (AC-105).
                    <PRTPAGE P="40988"/>
                </P>
                <P>17. Wage Schedule (Wage Change) for the Texarkana, Texas wage area (AC-136).</P>
                <P>18. Survey Specifications for the Panama City, Florida wage area (AC-033).</P>
                <P>19. Survey Specifications for the Seattle-Everett, Washington wage area (AC-143).</P>
                <P>20. Any items needing further clarification from this agenda may be discussed during future scheduled meetings.</P>
                <HD SOURCE="HD2">July 7, 2026</HD>
                <P>Opening Remarks by Chair, Mr. Eric Clayton, and DFO, Mr. Karl Fendt.</P>
                <P>Reviewing survey results and/or survey specifications for the following Non-appropriated Fund areas:</P>
                <P>1. Any items needing further clarification or action from the previous meeting.</P>
                <P>Reviewing survey results and/or survey specifications for the following Appropriated Fund areas:</P>
                <P>2. Wage Schedule (Full Scale) for the Shreveport, Louisiana wage area (AC-062).</P>
                <P>3. Wage Schedule (Full Scale) for the Central North Carolina wage area (AC-099).</P>
                <P>4. Wage Schedule (Full Scale) for the Columbia, South Carolina wage area (AC-120).</P>
                <P>5. Wage Schedule (Full Scale) for the Virginia Beach-Chesapeake, Virginia wage area (AC-140).</P>
                <P>6. Wage Schedule (Wage Change) for the Atlanta, Georgia wage area (AC-037).</P>
                <P>7. Any items needing further clarification from this agenda may be discussed during future scheduled meetings.</P>
                <HD SOURCE="HD2">July 21, 2026</HD>
                <P>Opening Remarks by Chair, Mr. Eric Clayton, and DFO, Mr. Karl Fendt.</P>
                <P>Reviewing survey results and/or survey specifications for the following Non-appropriated Fund areas:</P>
                <P>1. Any items needing further clarification or action from the previous meeting.</P>
                <P>2. Wage Schedule (Full Scale) for the Pennington, South Dakota wage area (AC-086).</P>
                <P>3. Wage Schedule (Full Scale) for the Nueces, Texas wage area (AC-115).</P>
                <P>4. Wage Schedule (Full Scale) for the Bexar, Texas wage area (AC-117).</P>
                <P>5. Wage Schedule (Full Scale) for the Anchorage, Alaska wage area (AC-118).</P>
                <P>6. Wage Schedule (Full Scale) for the Kitsap, Washington wage area (AC-142).</P>
                <P>7. Wage Schedule (Full Scale) for the Dallas, Texas wage area (AC-152).</P>
                <P>8. Wage Schedule (Full Scale) for the Tarrant, Texas wage area (AC-156).</P>
                <P>9. Wage Schedule (Wage Change) for the Orleans, Louisiana wage area (AC-006).</P>
                <P>10. Wage Schedule (Wage Change) for the Bell, Texas wage area (AC-028).</P>
                <P>11. Wage Schedule (Wage Change) for the Curry, New Mexico wage area (AC-030).</P>
                <P>12. Wage Schedule (Wage Change) for the Tom Green, Texas wage area (AC-032).</P>
                <P>13. Wage Schedule (Wage Change) for the Cobb, Georgia wage area (AC-034).</P>
                <P>14. Wage Schedule (Wage Change) for the Columbus, Georgia wage area (AC-067).</P>
                <P>Reviewing survey results and/or survey specifications for the following Appropriated Fund areas:</P>
                <P>15. Wage Schedule (Full Scale) for the Augusta, Maine wage area (AC-063).</P>
                <P>16. Wage Schedule (Full Scale) for the Harrisburg-York-Lebanon, Pennsylvania wage area (AC-114).</P>
                <P>17. Wage Schedule (Wage Change) for the Savannah, Georgia wage area (AC-042).</P>
                <P>18. Wage Schedule (Wage Change) for the Western Texas wage area (AC-127).</P>
                <P>19. Wage Schedule (Wage Change) for the Waco, Texas wage area (AC-137).</P>
                <P>20. Survey Specifications for the Fort Wayne-Marion, Indiana wage area (AC-049).</P>
                <P>21. Survey Specifications for the St. Louis, Missouri wage area (AC-081).</P>
                <P>22. Survey Specifications for the Dallas-Fort Worth, Texas wage area (AC-131).</P>
                <P>23. Special Pay—Western Texas Special Rate</P>
                <P>24. Any items needing further clarification from this agenda may be discussed during future scheduled meetings.</P>
                <HD SOURCE="HD2">August 4, 2026</HD>
                <P>Opening Remarks by Chair, Mr. Eric Clayton, and DFO, Mr. Karl Fendt.</P>
                <P>Reviewing survey results and/or survey specifications for the following Non-appropriated Fund areas:</P>
                <P>1. Any items needing further clarification or action from the previous meeting.</P>
                <P>Reviewing survey results and/or survey specifications for the following Appropriated Fund areas:</P>
                <P>2. Wage Schedule (Full Scale) for the Hawaii wage area (AC-044).</P>
                <P>3. Wage Schedule (Full Scale) for the Asheville, North Carolina wage area (AC-098).</P>
                <P>4. Wage Schedule (Full Scale) for the Austin, Texas wage area (AC-129).</P>
                <P>5. Wage Schedule (Full Scale) for the Southwestern Wisconsin wage area (AC-149).</P>
                <P>6. Wage Schedule (Wage Change) for the Augusta, Georgia wage area (AC-038).</P>
                <P>7. Wage Schedule (Wage Change) for the Macon, Georgia wage area (AC-041).</P>
                <P>8. Wage Schedule (Wage Change) for the Southeastern Washington-Eastern Oregon wage area (AC-144).</P>
                <P>9. Survey Specifications for the Evansville-Henderson, Indiana wage area (AC-048).</P>
                <P>10. Survey Specifications for the Indianapolis-Carmel-Muncie, Indiana wage area (AC-050).</P>
                <P>11. Survey Specifications for the Kansas City, Missouri wage area (AC-080).</P>
                <P>12. Survey Specifications for the Southern Missouri wage area (AC-082).</P>
                <P>13. Survey Specifications for the Omaha, Nebraska wage area (AC-084).</P>
                <P>14. Special Pay—Macon, Georgia Special Rate</P>
                <P>15. Any items needing further clarification from this agenda may be discussed during future scheduled meetings.</P>
                <HD SOURCE="HD2">August 18, 2026</HD>
                <P>Opening Remarks by Chair, Mr. Eric Clayton, and DFO, Mr. Karl Fendt.</P>
                <P>Reviewing survey results and/or survey specifications for the following Non-appropriated Fund areas:</P>
                <P>1. Any items needing further clarification or action from the previous meeting.</P>
                <P>2. Wage Schedule (Full Scale) for the Arapahoe-Denver, Colorado wage area (AC-084).</P>
                <P>3. Wage Schedule (Full Scale) for the El Paso, Colorado wage area (AC-085).</P>
                <P>4. Wage Schedule (Full Scale) for the Laramie, Wyoming wage area (AC-087).</P>
                <P>5. Wage Schedule (Full Scale) for the New London, Connecticut wage area (AC-136).</P>
                <P>6. Wage Schedule (Full Scale) for the Snohomish, Washington wage area (AC-141).</P>
                <P>7. Wage Schedule (Full Scale) for the Pierce, Washington wage area (AC-143).</P>
                <P>8. Wage Schedule (Full Scale) for the Newport, Rhode Island wage area (AC-167).</P>
                <P>9. Wage Schedule (Wage Change) for the Grand Forks, North Dakota wage area (AC-017).</P>
                <P>10. Wage Schedule (Wage Change) for the Davis-Weber-Salt Lake, Utah wage area (AC-018).</P>
                <P>11. Wage Schedule (Wage Change) for the Ada-Elmore, Idaho wage area (AC-038).</P>
                <P>12. Wage Schedule (Wage Change) for the Cascade, Montana wage area (AC-040).</P>
                <P>
                    13. Wage Schedule (Wage Change) for the Spokane, Washington wage area (AC-043).
                    <PRTPAGE P="40989"/>
                </P>
                <P>Reviewing survey results and/or survey specifications for the following Appropriated Fund areas:</P>
                <P>14. Wage Schedule (Full Scale) for the New Orleans, Louisiana wage area (AC-061).</P>
                <P>15. Wage Schedule (Full Scale) for the Central and Northern Maine wage area (AC-064).</P>
                <P>16. Wage Schedule (Full Scale) for the Southwestern Oregon wage area (AC-113).</P>
                <P>17. Wage Schedule (Full Scale) for the Corpus Christi-Kingsville-Alice, Texas wage area (AC-130).</P>
                <P>18. Wage Schedule (Wage Change) for the Duluth, Minnesota wage area (AC-074).</P>
                <P>19. Wage Schedule (Wage Change) for the San Antonio, Texas wage area (AC-135).</P>
                <P>20. Wage Schedule (Wage Change) for the Milwaukee-Racine-Waukesha, Wisconsin wage area (AC-148).</P>
                <P>21. Survey Specifications for the Los Angeles, California wage area (AC-013).</P>
                <P>22. Survey Specifications for the Minneapolis-St. Paul, Minnesota wage area (AC-075).</P>
                <P>23. Survey Specifications for the Richmond, Virginia wage area (AC-141).</P>
                <P>24. Special Pay—Southwestern Oregon Special Rate</P>
                <P>25. Any items needing further clarification from this agenda may be discussed during future scheduled meetings.</P>
                <HD SOURCE="HD2">September 1, 2026</HD>
                <P>Opening Remarks by Chair, Mr. Eric Clayton, and DFO, Mr. Karl Fendt.</P>
                <P>Reviewing survey results and/or survey specifications for the following Non-appropriated Fund areas:</P>
                <P>1. Any items needing further clarification or action from the previous meeting.</P>
                <P>2. Survey Specifications for the Brevard, Florida wage area (AC-061).</P>
                <P>3. Survey Specifications for the Hillsborough, Florida wage area (AC-119).</P>
                <P>4. Survey Specifications for the Miami-Dade, Florida wage area (AC-158).</P>
                <P>5. Survey Specifications for the Duval, Florida wage area (AC-159).</P>
                <P>6. Survey Specifications for the Monroe, Florida wage area (AC-160).</P>
                <P>Reviewing survey results and/or survey specifications for the following Appropriated Fund areas:</P>
                <P>7. Any items needing further clarification from this agenda may be discussed during future scheduled meetings.</P>
                <HD SOURCE="HD2">September 15, 2026</HD>
                <P>Opening Remarks by Chair, Mr. Eric Clayton, and DFO, Mr. Karl Fendt.</P>
                <P>Reviewing survey results and/or survey specifications for the following Non-appropriated Fund areas:</P>
                <P>1. Any items needing further clarification or action from the previous meeting.</P>
                <P>2. Wage Schedule (Full Scale) for the Frederick, Maryland wage area (AC-088).</P>
                <P>3. Wage Schedule (Full Scale) for the Washington, District of Columbia wage area (AC-124).</P>
                <P>4. Wage Schedule (Full Scale) for the Alexandria-Arlington-Fairfax, Virginia wage area (AC-125).</P>
                <P>5. Wage Schedule (Full Scale) for the Prince William, Virginia wage area (AC-126).</P>
                <P>6. Wage Schedule (Full Scale) for the Prince George's-Montgomery, Maryland wage area (AC-127).</P>
                <P>7. Wage Schedule (Full Scale) for the Charles-St. Mary's, Maryland wage area (AC-128).</P>
                <P>8. Wage Schedule (Full Scale) for the Anne Arundel, Maryland wage area (AC-147).</P>
                <P>9. Wage Schedule (Wage Change) for the Burlington, New Jersey wage area (AC-071).</P>
                <P>10. Wage Schedule (Wage Change) for the Kent, Delaware wage area (AC-076).</P>
                <P>11. Wage Schedule (Wage Change) for the Richmond-Chesterfield, Virginia wage area (AC-082).</P>
                <P>12. Wage Schedule (Wage Change) for the Morris, New Jersey wage area (AC-090).</P>
                <P>Reviewing survey results and/or survey specifications for the following Appropriated Fund areas:</P>
                <P>13. Wage Schedule (Full Scale) for the Alaska wage area (AC-007).</P>
                <P>14. Wage Schedule (Full Scale) for the Montana wage area (AC-083).</P>
                <P>15. Wage Schedule (Full Scale) for the Charleston, South Carolina wage area (AC-119).</P>
                <P>16. Wage Schedule (Wage Change) for the Boise, Idaho wage area (AC-045).</P>
                <P>17. Wage Schedule (Wage Change) for Utah wage area (AC-139).</P>
                <P>18. Wage Schedule (Wage Change) for the Spokane, Washington wage area (AC-145).</P>
                <P>19. Wage Schedule (Wage Change) for the Puerto Rico wage area (AC-151).</P>
                <P>20. Special Pay—Puerto Rico Special Rates.</P>
                <P>21. Any items needing further clarification from this agenda may be discussed during future scheduled meetings.</P>
                <P>Closing Remarks by Chair, Mr. Eric Clayton.</P>
                <P>
                    <E T="03">Meeting Accessibility:</E>
                     Pursuant to 5 U.S.C. 552b(c)(4), the DoW has determined that the meetings shall be closed to the public. The USW(P&amp;R), in consultation with the DoW Office of General Counsel, has determined in writing that each of these meetings is likely to disclose trade secrets and commercial or financial information obtained from a person and privileged or confidential.
                </P>
                <P>
                    <E T="03">Written Statements:</E>
                     Pursuant to 5 U.S.C. 1009(a)(3) and 41 CFR 102-3.140, interested persons may submit written statements to the DFO for the DoDWC at any time, whether after the meeting has already been held or prior to the meetings that have not been held. Written statements should be submitted to the DFO at the email or mailing address listed in 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    . If statements pertain to a specific topic being discussed at a planned meeting, then these statements must be submitted no later than five (5) business days prior to the meeting in question. Written statements received after this date may not be provided to or considered by the DoDWC until its next meeting. The DFO will review all submitted written statements and provide copies to all the committee members before or after the meetings that are the subject of this notice.
                </P>
                <P>Due to negative impacts to pay for Federal Wage System employees that directly support national defense, the 7-day notice period was unable to be met for the June 23rd meeting. The delay was unavoidable for the lead agency and additional delays would have increased the severity of negative implications for all agencies that employ Federal Wage System employees.</P>
                <SIG>
                    <DATED>Dated: June 30, 2026.</DATED>
                    <NAME>Stephanie J. Bost,</NAME>
                    <TITLE>Alternate OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13516 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6001-FR-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
                <SUBAGY>Office of the Secretary of Defense</SUBAGY>
                <SUBJECT>Renewal of Department of Defense Federal Advisory Committee—Department of Defense Board of Actuaries</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of Defense (DoD).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Renewal of Federal advisory committee.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The DoD (referred to herein as “the Department”, “Department of War” or “DoW”) is publishing this notice to 
                        <PRTPAGE P="40990"/>
                        announce that it is renewing the charter for the Department of Defense Board of Actuaries (DoD BoA) as a non-discretionary Federal advisory committee.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Jim Freeman, Advisory Committee Management Officer for the Department of War, 703-692-5952.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The DoD BoA charter is being renewed in accordance with chapter 10 of title 5, United States Code (U.S.C.) (commonly known as “the Federal Advisory Committee Act” or “FACA”) and 41 Code of Federal Regulations (CFR) 102-3.50(a). The DoD BoA, required by 10 U.S.C. 183, provides independent advice and recommendations on matters relating to the DoW Military Retirement Fund (“the Retirement Fund”), the Department of Defense Education Benefits Fund (“the Education Fund”), the Department of Defense Voluntary Separation Incentive Fund (“the Incentive Fund”), and such other funds as the Secretary of War (SecWar) shall specify.</P>
                <P>Pursuant to 10 U.S.C. 183(c) and (e), the DoD BoA shall submit to the SecWar on an annual basis a report on the actuarial status of each of the funds listed above in section 3 and, in doing so, shall:</P>
                <P>i. Review valuations of the Retirement Fund, in accordance with 10 U.S.C 1465(c), and submit to the President and Congress, not less often than once every four years, a report on the status of the Retirement Fund, including such recommendations for modifications to the funding or amortization of the Retirement Fund as the DoD BoA considers appropriate and necessary to maintain the Retirement Fund on a sound actuarial basis;</P>
                <P>ii. Review valuations of the “the Education Fund”, in accordance with 10 U.S.C. 2006(e), and make recommendations to the President and Congress on such modifications to the funding or amortization of the Education Fund as the DoD BoA considers appropriate to maintain the Education Fund on a sound actuarial basis;</P>
                <P>iii. Review valuations of the “the Incentive Fund” and make recommendations to the President and Congress on such modifications to the funding or amortization of the Incentive Fund as the DoD BoA considers appropriate to maintain the Incentive Fund on a sound actuarial basis;</P>
                <P>iv. Review valuations of such other funds as the SecWar shall specify for purposes of 10 U.S.C. 183 and make recommendations to the President and Congress on such modifications to the funding or amortization of such funds as the DoD BoA considers appropriate to maintain such funds on a sound actuarial basis; and</P>
                <P>v. Furnish advice and opinions on matters referred to the DoD BoA by the SecWar.</P>
                <P>The SecWar shall ensure that the DoD BoA has access to such records regarding the Retirement Fund, the Education Fund, the Incentive Fund, and such other funds specified by the SecWar for purposes of 10 U.S.C. 183 as the DoD BoA shall require to determine the actuarial status of such funds.</P>
                <P>The DoD BoA reports to the SecWar or the Deputy Secretary of War (“the DoW Appointing Authority”) through the Under Secretary of War for Personnel and Readiness (USW(P&amp;R)), who may act upon the DoD BoA's advice and recommendations in accordance with DoW policy and procedures.</P>
                <P>The DoD BoA, pursuant to 10 U.S.C. 183(b), shall consist of three members chosen from among qualified professional actuaries who are members of the Society of Actuaries.</P>
                <P>The appointment of DoD BoA members shall be approved by the DoW Appointing Authority for a term of service of 15 years, except that a DoD BoA member appointed to fill a vacancy occurring before the end of the term for which the member's predecessor was appointed shall only serve until the end of such term. A DoD BoA member may serve after the end of the member's term until a successor has taken the oath of office. The DoD BoA membership appointments are staggered so that a new member is appointed every five years. A DoD BoA member may be removed by the DoW Appointing Authority only for misconduct or failure to perform functions vested in the DoD BoA. DoD BoA members are not subject to annual renewals.</P>
                <P>DoD BoA members who are not full-time or permanent part-time Federal civilian officers or employees, or active-duty members of the Uniformed Services, will be appointed as experts or consultants pursuant to 5 U.S.C. 3109 to serve as special government employee members. DoD BoA members who are full-time or permanent part-time Federal civilian officers or employees, or active-duty members of the Uniformed Services, will be designated pursuant to 41 CFR 102-3.130(a) to serve as regular government employee members. No member, unless authorized by the DoW Appointing Authority, may serve on more than two DoW Federal advisory committees at one time.</P>
                <P>A DoD BoA member who is not an employee of the United States is entitled to receive pay at the daily equivalent of the annual rate of basic pay of the highest rate of basic pay under the General Schedule of subchapter III of chapter 53 of title 5, for each day the member is engaged in the performance of the duties of the DoD BoA. All members are entitled to reimbursement for official DoD BoA-related travel and per diem.</P>
                <P>The DoW Appointing Authority shall appoint the DoD BoA's Chair from among the membership previously approved, and in accordance with policy approved by the DoW Appointing Authority, the Chair shall serve a five-year term of service without annual renewals, which shall not exceed the member's approved DoD BoA appointment.</P>
                <P>The DoW shall provide non-voting technical advisors to assist the DoD BoA in the execution of its duties. The following individuals shall designate one DoW employee for each fund under the DoD BoA's purview (the Retirement Fund, the Education Fund, the Incentive Fund, and such other funds specified by the SecWar for purposes of 10 U.S.C. 183) to serve as a non-voting advisor to assist the DoD BoA:</P>
                <P>a. Under Secretary of War (Comptroller)/Chief Financial Officer, Department of War;</P>
                <P>b. Assistant Secretary of War for Manpower and Reserve Affairs, through the Deputy Assistant Secretary of War for Military Personnel Policy;</P>
                <P>c. General Counsel of the Department of War.</P>
                <P>In addition, the DoW Chief Actuary shall serve as a non-voting advisor and the Executive Secretary for the DoD BoA. These individuals will not participate in the discussions and deliberations of the DoD BoA.</P>
                <P>Each DoD BoA member is appointed to exercise their own best judgment on behalf of the DoW, without representing any particular point of view, and to discuss and deliberate in a manner that is free from conflict of interest.</P>
                <P>
                    The public or interested organizations may submit written statements about the DoD BoA mission and functions. Written statements may be submitted at any time or in response to the stated agenda of planned meetings of the DoD BoA. All written statements shall be submitted to the DoD BoA's Designated Federal Officer (DFO), and this individual will ensure that the written statements are provided to the membership for their consideration. The DoD BoA's DFO is Mr. Peter Zouras, and he may be contacted at (571) 372-1975, or 
                    <E T="03">peter.m.zouras.civ@mail.mil.</E>
                </P>
                <SIG>
                    <PRTPAGE P="40991"/>
                    <DATED>Dated: June 30, 2026.</DATED>
                    <NAME>Stephanie J. Bost,</NAME>
                    <TITLE>Alternate OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13514 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6001-FR-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF EDUCATION</AGENCY>
                <DEPDOC>[Docket No.: ED-2026-SCC-1354]</DEPDOC>
                <SUBJECT>Foreign Gifts and Contracts Disclosures; Correction</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Student Aid (FSA), Department of Education (ED).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Correction Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        On June 29, 2026, the U.S. Department of Education published a 30-day comment period notice in the 
                        <E T="04">Federal Register</E>
                        . The PRA Coordinator, Strategic Collections and Clearance, Office of the Chief Data Officer, Office of Planning, Evaluation and Policy Development, hereby issues a correction notice as required by the Paperwork Reduction Act of 1995.
                    </P>
                </SUM>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Correction</HD>
                <P>
                    In the 
                    <E T="04">Federal Register</E>
                     of June 29, 2026, in FR Doc. 2026-13078, on page 39088, in the second column, correct the “Dates” caption to read:
                </P>
                <SUPLHD>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Interested persons are invited to submit comments on or before July 29, 2026.</P>
                </SUPLHD>
                <SIG>
                    <DATED>Dated: July 1, 2026.</DATED>
                    <NAME>Ross Santy</NAME>
                    <TITLE>Chief Data Officer, Office of Planning, Evaluation and Policy Development.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13605 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4000-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF ENERGY</AGENCY>
                <DEPDOC>[DOE-HQ-2025-0175]</DEPDOC>
                <SUBJECT>Implementing Voluntary Agreements Under the Defense Production Act</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Nuclear Energy, U.S. Department of Energy (DOE).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        On October 23, 2025, the Department of Energy held a public meeting to discuss the development of voluntary agreements and plans of action under the Defense Production Act. As part of that meeting, a draft voluntary agreement was released to the accompanying docket and published in the 
                        <E T="04">Federal Register</E>
                         for comment. This notice publishes the “Nuclear Fuel Cycle Consortium” Voluntary Agreement approved by the Secretary of Energy, after consultation by the Attorney General and Chairman of the Federal Trade Commission.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Ms. Sarah McPhee Charrez, U.S. Department of Energy, 1000 Independence Avenue SW, Washington, DC 20585. Telephone: (202) 587-1092. Email: 
                        <E T="03">DPA consortium@nuclear.energy.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Authority and Background</HD>
                <P>
                    On August 25, 2025, the Department of Energy (“DOE”) published an interim final rule to codify standards and procedures for developing and implementing voluntary agreements pursuant to section 708 of the Defense Production Act of 1950 (“DPA”), Public Law 81-774 (Sept. 8, 1950) (codified at 50 U.S.C. 4558). 
                    <E T="03">See</E>
                     90 FR 41279. As explained in that interim final rule, DOE's procedures were developed in accordance with the DPA statute and are consistent with recent Executive orders related to nuclear energy and a Presidential declaration of a national energy emergency. 
                    <E T="03">See</E>
                     Executive Order (E.O.”) 14302 (Reinvigorating the Nuclear Industrial Base), 90 FR 22595 (May 29, 2025) and E.O. 14156 (Declaring a National Energy Emergency), 90 FR 8433 (Jan. 29, 2025). E.O. 14302 charges DOE with developing and maintaining a resilient, secure, and sustainable nuclear fuel supply chain, from mining through the management of spent nuclear fuel and high-level radioactive waste, for purposes of national security and energy independence.
                </P>
                <P>
                    Consistent with this charge, the DPA, and DOE's related rule, DOE held a public meeting on October 23, 2025, to discuss the development of voluntary agreements and plans of action pursuant to section 708 of the DPA. 
                    <E T="03">See</E>
                     90 FR 48268 (Oct. 15, 2025). At that meeting, DOE presented for discussion and comment a draft voluntary agreement concerning the nuclear fuel cycle that set out the broad framework to be followed with respect to furthering the goals of E.O. 14302. That draft agreement was placed in the public docket and made available for public comment. DOE also reproduced that draft agreement in the 
                    <E T="04">Federal Register</E>
                     and solicited further public comment. 
                    <E T="03">See</E>
                     90 FR 51208 (Nov. 17, 2025).
                </P>
                <P>In response to the posting of the draft voluntary agreement, DOE received several comments offering suggested changes to the draft—both specific line edits and general conceptual suggestions. Comments were received from the following individuals and entities:</P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s150,r50">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">
                            Commenters
                            <LI>comment ID No.</LI>
                        </CHED>
                        <CHED H="1">Type of commenter</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Greg Czyryca, DOE-HQ-2025-0175-0012</ENT>
                        <ENT>Individual.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Donivan Porterfield (“Porterfield”), DOE-HQ-2025-0175-0013</ENT>
                        <ENT>Individual.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Anonymous 1, DOE-HQ-2025-0175-0014</ENT>
                        <ENT>Individual.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Ziqin (Joseph) Ding (“Ding”), DOE-HQ-2025-0175-0015</ENT>
                        <ENT>Individual.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Anonymous 2, DOE-HQ-2025-0175-0016</ENT>
                        <ENT>Individual.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Anonymous 3, DOE-HQ-2025-0175-0017</ENT>
                        <ENT>Individual.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DISA Technologies, Inc. (“DISA”), DOE-HQ-2025-0175-0018</ENT>
                        <ENT>Advanced technology company.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Center for Regulatory Freedom (“CRF”), DOE-HQ-2025-0175-0019</ENT>
                        <ENT>Non-Governmental Organization.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SuperCritical Technologies (“SCT”), DOE-HQ-2025-0175-0021</ENT>
                        <ENT>Uranium-sourcing company.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    While some of the comments were expressions of support for DOE's efforts, others offered specific suggestions for DOE to consider. DOE has carefully considered the suggestions and has decided to adopt some of the suggested changes while declining to adopt others.
                    <SU>1</SU>
                    <FTREF/>
                     In particular, DOE has decided to adopt a number of the suggestions made by Porterfield that help clarify specific points within the Voluntary Agreement. These suggestions were:
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         DOE also made certain organizational adjustments to provide some additional flexibility in implementing the various activities that would follow from any subsequent plans of action that may be developed.
                    </P>
                </FTNT>
                <P>
                    1. Under Section I (Preface), DOE is adopting the suggestion that it emphasize that E.O. 14302 focuses on ensuring the national 
                    <E T="03">defense</E>
                     security of the United States through its invoking of 
                    <PRTPAGE P="40992"/>
                    section 708 of the DPA. (Emphasis added.)
                </P>
                <P>
                    2. Under the section covering Information Management and Responsibilities, DOE is adopting the suggestion that it include the phrase “and information” under Item 1 to clarify that appropriate safeguards will apply to Participant use and dissemination of other Participants' data 
                    <E T="03">and information.</E>
                     (Emphasis added.)
                </P>
                <P>
                    3. Within the Oversight section of the Voluntary Agreement, first paragraph, DOE is adopting the suggestion that it include the phrase “and information” at the end of the second sentence to clarify that a review of proposed actions will include the provision of data 
                    <E T="03">and information.</E>
                     (Emphasis added.)
                </P>
                <P>
                    In response to suggestions from CRF and SCT, DOE has also added language regarding information sharing as part of its Committee Governance provision under the agreement's Documentation &amp; Recordkeeping section to help improve data sharing protections. These adopted provisions will be incorporated into the Documentation &amp; Recordkeeping section and will require the use of password protection on shared documents containing sensitive information and limiting committee record access within DOE to specific individuals (
                    <E T="03">e.g.</E>
                     the Consortium Secretariat).
                </P>
                <P>Regarding the remaining comments for which suggestions were made, these are addressed in the next section and organized by commenter.</P>
                <HD SOURCE="HD2">Commenter Czyryca</HD>
                <P>Commenter Czyryca suggested broadening the scope to provide anti-trust protection or guidance with respect to “classified information.” (Czyryca at 1)</P>
                <HD SOURCE="HD2">DOE Response</HD>
                <P>DOE revised the Voluntary Agreement, including through the addition of appendices that address a variety of subjects. Among these appendices, DOE included language regarding the treatment of confidential information. DOE will evaluate the appropriateness of applying one of these exemptions consistent with its current procedures and the applicable law. With respect to anti-trust protection, the Voluntary Agreement includes an explicit provision detailing the application of anti-trust defenses. The availability of these defenses to individual participants to a given Voluntary Agreement or Plan of Action is governed and set out by statute.</P>
                <HD SOURCE="HD2">Commenter Ding</HD>
                <P>Commenter Ding supported DOE's efforts and suggested that additional clarity be provided to ensure that the anti-trust safe harbor be tightly cabined to “pro-competitive” “resilience-enhancing conduct” and does not inadvertently create a privileged status for large entities. In so doing, Commenter Ding suggested that DOE include more explicit criteria for Participant selection and for Committee and Plan of Action scope decisions to reduce perceptions of favoritism and to strengthen the administrative record. Commenter Ding also suggested that DOE should commit to baseline confidentiality, aggregation, and “need-to-know” principles, with a clear default against exchanging price, bid, output, or customer-allocation information unless DOJ/FTC approve a narrow exception. Finally, Commenter Ding suggested that DOE should address the participation of small entities by encouraging the Plans of Action to provide scalable compliance expectations and technical support so that rebuilding domestic capacity does not consolidate the market or exclude emerging suppliers. In his view, these adjustments would preserve the Voluntary Agreement's emergency-response value while ensuring it remains the least-anticompetitive tool reasonably available consistent with section 708 of the DPA. (Ding at 1)</P>
                <HD SOURCE="HD2">DOE Response</HD>
                <P>
                    DOE appreciates the concerns noted by the commenter. As a general matter, the Voluntary Agreement is intended to foster a close working relationship between DOE and the Participants—under the supervision of the DOJ and FTC. With the involvement of the DOJ and FTC throughout the process in developing and implementing the Voluntary Agreement and subsequent Plans of Action, potential anti-trust issues will be addressed during that process. The oversight provided by the DOJ and FTC aligns with the safeguards provided under 50 U.S.C. 4558, such as requiring that a voluntary agreement cannot become effect until the Attorney General (after consultation with the Chairman of the Federal Trade Commission) finds (in writing) that to meet the purpose of helping provide for the national defense, such purpose may not reasonably be achieved through a voluntary agreement or plan of action having less anticompetitive effects. (
                    <E T="03">See</E>
                     50 U.S.C. 4558(c)(1) and (f)(1)(B)). Regarding the issue of entity participation, DOE notes that 50 U.S.C. 4551 provides for small business concerns to be given the maximum opportunity to participate in advisory committees as may be established under the DPA. (
                    <E T="03">See</E>
                     50 U.S.C. 4558(c)). To this end, DOE notes that the Voluntary Agreement includes governance oversight provisions focusing on seeking participation from a broad cross-section of the industry, including small business entities. Specifically, the Information Management &amp; Responsibilities section of the final version of the Voluntary Agreement addresses these types of logistical and organizational concerns. DOE also notes that in accordance with the DPA, small business concerns shall be given the maximum practicable opportunity to participate as contractors, and subcontractors at various tiers, in this program concerning the nuclear fuel cycle to maintain and strengthen the Nation's industrial base and technology base. (
                    <E T="03">See</E>
                     50 U.S.C. 4558(a)).
                </P>
                <HD SOURCE="HD2">Anonymous 2</HD>
                <P>The commenter inquired whether “non-confidential” notice can be provided before competitive information is shared so that participants can decline to receive that information. (Anonymous 2 at 1).</P>
                <HD SOURCE="HD2">DOE Response</HD>
                <P>DOE appreciates the issue raised by the commenter but notes that the suggested approach would pose practical problems that would hinder the collaborative nature of the process. DOE also notes that the final version of the voluntary agreement contains provisions addressing information management and accompanying responsibilities and believes that section will effectively address potential information-sharing concerns.</P>
                <HD SOURCE="HD2">DISA</HD>
                <P>DISA suggested that DOE ensure that remediation driven uranium recovery, legacy waste processing, and recycling of previously mined materials are explicitly recognized within the scope of covered fuel-cycle activities under the Voluntary Agreement. It also expressed its support for establishing coordinated Plans of Action. (DISA at 1).</P>
                <HD SOURCE="HD2">DOE Response</HD>
                <P>
                    DOE notes that these types of specific issues are intended to be addressed through the individual committees covering specific sections of the nuclear fuel cycle. To help meet the objectives of E.O. 14302, DOE has established individual committees to address the different technical aspects of the nuclear fuel cycle, namely—Mining &amp; Milling; Enrichment; Conversion; Fabrication &amp; Deconversion; Recycling &amp; Reprocessing; Utilities; and Reactors. DOE is also examining long-term, cross-
                    <PRTPAGE P="40993"/>
                    cutting issues that affect the domestic nuclear fuel cycle while supporting the technical committees' plans of action. With respect to DISA's specific suggestion, DOE anticipates that the specific Recycling &amp; Reprocessing Committee handling spent nuclear fuel recycling and reprocessing will address these issues in greater detail.
                </P>
                <HD SOURCE="HD2">CRF</HD>
                <P>CRF generally supported DOE's efforts in using a voluntary agreement as a tool for coordinated industry action, provided it is structured with clarity, transparency, and “disciplined respect” for statutory limits. To this end, CRF broadly suggested that DOE strengthen the voluntary agreement by clarifying or otherwise enhancing definitions, procedural steps, and transparency. (CRF at 4).</P>
                <HD SOURCE="HD2">DOE Response</HD>
                <P>As noted earlier, DOE made certain changes in response to CRF's concerns related to information security. DOE also notes that many of the issues noted by CRF are addressed in the Voluntary Agreement's Committee Governance provisions addressing the conduct of meetings in the context of addressing transparency and confidentiality issues. The Committee Governance section also addresses Committee jurisdictional issues, procedures for verifying compliance, the reviewing of records, and the handling of potential deviations. DOE also expects these issues to be addressed as part of the individual Plans of Action that may develop from each Committee. With regard the articulation of membership criteria, which CRF urged DOE to ensure are transparent and objective, DOE believes the current set of requirements are sufficient in that they set out specified criteria for participation.</P>
                <HD SOURCE="HD2">SCT</HD>
                <P>SCT offered suggestions that included: replacing the use of the term “mining” with “uranium sourcing” along with an appropriate definition for that new term; explicitly recognizing water-based engineered, and future extraction methods in the Agreements; establishing standing subcommittees and pilot plans of action for non-traditional sourcing; implementing tiered data sharing with intellectual property protection (including through the use of explicit FOIA-related “carve-outs”) to encourage pre-commercial participation; incorporating execution milestones, funding, and regulatory fast-lanes to accelerate operational readiness; and integrating explicit language requiring cross-sector integration plans of action (to include shared data frameworks, multi-stage planning exercises, and coordinated capacity forecasts). (SCT at 1). SCT also offered additional specifics based on these broader suggestions. (SCT at 2-4).</P>
                <HD SOURCE="HD2">DOE Response</HD>
                <P>
                    DOE has carefully considered the suggestions offered by SCT and as noted at the beginning of this discussion, DOE has adopted one of these suggestions to help improve the management of information sharing activities under the Voluntary Agreement. However, DOE is declining SCT's suggestion that specific carve-out language related to exempt information under the Freedom of Information Act (“FOIA”) be added to include “pre-commercial proprietary process parameters and intellectual property” in addition to “classic trade secrets.” In DOE's view, this type of information would be treated in a manner consistent with the exemptions offered under FOIA's legal framework and DOE's related disclosure regulations under 10 CFR part 1004. With respect to the remaining suggestions, these items are generally either anticipated to be addressed at the specific Committee levels handling individual topic areas or are already addressed by statute, such as the use of the term “Plan of Action.” 
                    <E T="03">See</E>
                     50 U.S.C. 4558(b)(2) (providing that “[t]he term “plan of action” means any of 1 or more documented methods adopted by participants in an existing voluntary agreement to implement that agreement”). DOE expects each Plan of Action to be an implementation document for execution by the participating entities. With respect to the use of the term “uranium sourcing,” DOE will consider its use as appropriate within the context of the relevant.
                </P>
                <P>
                    Finally, DOE also received a submission characterized as a “Petition to Correct Procedural and Analytical Deficiencies and to Reissue the Rule Through Notice-and Comment.” 
                    <SU>2</SU>
                    <FTREF/>
                     As DOE's notice of availability sought public input on the draft voluntary agreement and did not seek to reopen or address aspects related to the August 25, 2025, interim final rule concerning the standards and procedures for developing and implementing voluntary agreements under the DPA, whose comment period closed on September 24, 2025, we do not address the substance of that submission.
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         See Docket ID No. DOE-HQ-2025-0175-0020 from the Citizens Rulemaking Alliance.
                    </P>
                </FTNT>
                <P>The text of the final version of the Voluntary Agreement that integrates those suggestions from commenters that were adopted by DOE follows at the end of this document.</P>
                <HD SOURCE="HD1">Signing Authority</HD>
                <P>
                    This document of the Department of Energy was signed on June 2, 2026, by Theodore Garrish, Assistant Secretary for Nuclear Energy, pursuant to delegated authority from the Secretary of Energy. The 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 June 30, 2026.</DATED>
                    <NAME>Treena V. Garrett,</NAME>
                    <TITLE>Federal Register Liaison Officer, U.S. Department of Energy.</TITLE>
                </SIG>
                <P>Set forth below is the full text of the final version of the Voluntary Agreement. </P>
                <FP SOURCE="FP-1">Defense Production Act, Section 708 Voluntary Agreement</FP>
                <FP SOURCE="FP-1">Department of Energy Nuclear Fuel Cycle Consortium</FP>
                <FP SOURCE="FP-1">April 2026</FP>
                <HD SOURCE="HD1">I. Preface</HD>
                <P>This Voluntary Agreement (“Agreement”) is entered into pursuant to section 708 of the Defense Production Act (DPA) of 1950, as amended (50 U.S.C. 4558), and under the authority and supervision of the United States Department of Energy (DOE), Office of Nuclear Energy, after consultation with the Attorney General of the United States (Attorney General) and the Chairman of the Federal Trade Commission (FTC). This Agreement is established in furtherance of the goals set forth in Executive Order (E.O.) 14302, “Reinvigorating the Nuclear Industrial Base,” signed May 23, 2025, directing DOE to develop and maintain a resilient, secure, and sustainable nuclear fuel supply chain, from mining through waste management, for purposes of national defense and energy independence. The activities contemplated by this Agreement are limited to those necessary to strengthen the domestic nuclear industry, at the sole determination of DOE, the Department of Justice (DOJ), and the FTC.</P>
                <P>
                    This Agreement affords Participants a defense to any civil or criminal action 
                    <PRTPAGE P="40994"/>
                    brought under the Federal antitrust laws (or any similar laws of any State) with respect to any action taken to develop or carry out any agreement or Plan of Action (POA) consistent with the provisions under 50 U.S.C. 4558(j) (see Section VI: Antitrust Defenses). This Agreement is intended to foster a close working relationship between DOE and the Participants, under the supervision of the DOJ and FTC. When implemented through a POA, this Agreement affords Participants a safe harbor to exchange information, collaborate and adjust commercial operations as to particular products and services, as DOE and DOJ, in consultation with the FTC, determine is necessary to address the national energy emergency declared on January 20, 2025, through E.O. 14156, “Declaring a National Energy Emergency.”
                </P>
                <P>This Agreement has been reviewed and approved by the Attorney General and the Chairman of the FTC, pursuant to the requirements of the DPA and applicable antitrust law safeguards.</P>
                <HD SOURCE="HD1">II. Scope</HD>
                <P>This Agreement between DOE and Participants shall apply to all activities across the full nuclear fuel cycle, including, but not limited to:</P>
                <FP SOURCE="FP-1">1. Uranium mining and milling</FP>
                <FP SOURCE="FP-1">2. Uranium conversion</FP>
                <FP SOURCE="FP-1">3. Uranium enrichment</FP>
                <FP SOURCE="FP-1">4. Fuel fabrication &amp; deconversion</FP>
                <FP SOURCE="FP-1">5. Spent nuclear fuel recycling and reprocessing</FP>
                <FP SOURCE="FP-1">6. Utilities</FP>
                <FP SOURCE="FP-1">7. Reactors </FP>
                <P>This Agreement covers coordination, strategic planning, data sharing, and collaboration necessary to support DOE's mission to ensure domestic capability and resilience in each stage of the nuclear fuel cycle.</P>
                <HD SOURCE="HD1">III. Authorities</HD>
                <P>Section 708, Defense Production Act (50 U.S.C. 4558); Section 161, Atomic Energy Act (42 U.S.C. 2201); Section 123, Atomic Energy Act (42 U.S.C. 2153); Section 124, Atomic Energy Act (42 U.S.C. 2154); Executive Order (E.O.) 14156 Declaring a National Energy Emergency; E.O. 14302, 90 FR 22595. Pursuant to DPA section 708(f)(1)(A), the Assistant Secretary for Nuclear Energy certifies that this Agreement is necessary for the national defense.</P>
                <HD SOURCE="HD1">IV. General Provisions</HD>
                <HD SOURCE="HD2">A. Definitions</HD>
                <P>
                    1. 
                    <E T="03">Advisory Forum</E>
                    —The DPA Nuclear Fuel Cycle Consortium Advisory Forum (“Advisory Forum”) provides independent, non-commercial technical, policy, and implementation insight in support of consortium activities. The Forum is advisory only and is intentionally structured to strengthen technical rigor, reduce implementation risk, and preserve strong antitrust and governance safeguards. Members of the Advisory Forum may be standing members of a Committee if identified in a POA.
                </P>
                <P>
                    2. 
                    <E T="03">Agreement</E>
                    —The Voluntary Agreement. Participants who have been invited to join and agreed to the terms of this Agreement as described in Section VII below may join the DOE DPA Nuclear Fuel Cycle Consortium.
                </P>
                <P>
                    3. 
                    <E T="03">Attendees</E>
                    —Subject matter experts (SME), invited by the Chairperson to attend meetings authorized under this Agreement, to provide technical advice or to represent other Government agencies or interested parties. Attendees are not Members of the Committee.
                </P>
                <P>
                    4. 
                    <E T="03">Chairperson</E>
                    —The Assistant Secretary for Nuclear Energy, as delegated by the Secretary of Energy, to chair the DOE DPA Nuclear Fuel Cycle Consortium. The Chairperson (or “Chair”) shall be responsible for the overall management and administration of the Committee, this Agreement, and Plans of Action developed under this Agreement while remaining under the supervision of the Secretary; may create Committees, determine policies, recommend actions, and make decisions necessary to carry out this Agreement; may delegate these tasks to the Principal Deputy Assistant Secretary for Nuclear Energy; and otherwise shall carry out all duties and responsibilities assigned to them. The Chairperson shall be assisted and represented by a Vice-Chairperson (or “Vice-Chair”), the Deputy Assistant Secretary for Nuclear Fuel Cycle.
                </P>
                <P>
                    5. 
                    <E T="03">Committee</E>
                    —A forum to maximize the effectiveness of DOE and industry participants to respond to E.O. 14156 (Declaring a National Energy Emergency) through integrated coordination, planning, and identification and development of Plans of Action needed to enable the continued reliable operation of the Nation's existing, and future, nuclear reactors, including making recommendations on the creation of a Plan of Action.
                </P>
                <P>
                    6. 
                    <E T="03">Competitively Sensitive Information</E>
                    —Competitively Sensitive Information (CSI) that is shared pursuant to this Plan of Action may include any Document or other tangible thing or oral transmission that contains financial, business, commercial, scientific, technical, economic, or engineering information or data, including, but not limited to:
                </P>
                <FP SOURCE="FP-1">a. financial statements and data,</FP>
                <FP SOURCE="FP-1">b. customer and supplier lists,</FP>
                <FP SOURCE="FP-1">c. price and other terms of sale to customers,</FP>
                <FP SOURCE="FP-1">d. sales records, projections, and forecasts,</FP>
                <FP SOURCE="FP-1">e. inventory levels,</FP>
                <FP SOURCE="FP-1">f. capacity and capacity utilization,</FP>
                <FP SOURCE="FP-1">g. cost information,</FP>
                <FP SOURCE="FP-1">h. sourcing and procurement information,</FP>
                <FP SOURCE="FP-1">i. manufacturing and production information,</FP>
                <FP SOURCE="FP-1">j. delivery and shipping information,</FP>
                <FP SOURCE="FP-1">k. systems and data designs, and</FP>
                <FP SOURCE="FP-1">l. methods, techniques, processes, procedures, programs, codes, or similar information, whether tangible or intangible, and regardless of the method of storage, compilation, or recordation, if the owner thereof has taken reasonable measures to protect the information from disclosure to the public or competitors. These measures may be evidenced by marking or labeling the items as “Competitively Sensitive Information” during submission to DOE or in the Participant's customary and existing treatment of such information (regardless of labeling). </FP>
                <P>
                    7. 
                    <E T="03">Consortium</E>
                    —The DOE DPA Nuclear Fuel Cycle Consortium established under this Agreement.
                </P>
                <P>
                    8. 
                    <E T="03">Documents</E>
                    —Any information, on paper or in electronic format, including written, recorded, and graphic materials of every kind, in the possession, custody, or control of the Participant.
                </P>
                <P>
                    9. 
                    <E T="03">Members</E>
                    —Collectively the Chairperson, Representatives, and Participants of the Committee. Jointly responsible for developing all decisions necessary to carry out this Agreement and to develop and execute Plans of Action under this Agreement.
                </P>
                <P>
                    10. 
                    <E T="03">Nuclear Fuel Cycle</E>
                    —The various activities associated with inputs to the production of electricity from nuclear reactions, starting with the mining of uranium and ending with the disposal of nuclear waste. With the reprocessing of used fuel as an option for nuclear energy, the stages form a true cycle.
                </P>
                <P>
                    11. 
                    <E T="03">Participant</E>
                    —Any domestic private-sector company, regardless of the location of the ultimate business owner, that has substantive capabilities, resources or expertise to carry out the purpose of this Agreement, that has been specifically invited to participate in this Agreement by the Chairperson, and that has applied and agreed to the terms of this Agreement in Section VII below. “Participant” includes a corporate entity entering into this Agreement and all subsidiaries and affiliates of that entity in which that entity has 50 percent or more control 
                    <PRTPAGE P="40995"/>
                    either by stock ownership, board majority, or otherwise. The Chairperson may invite Participants to join this Agreement at any time during its effective period.
                </P>
                <P>
                    12. 
                    <E T="03">Plan of Action</E>
                    —A documented method, pursuant to 50 U.S.C. 4558(b)(2), proposed by DOE and adopted by invited Participants, to implement this Agreement, through a Committee focused on a particular aspect of the Nuclear Fuel Cycle or functional area necessary for the national defense.
                </P>
                <P>
                    13. 
                    <E T="03">Representatives</E>
                    —The representatives the Chairperson or Vice-Chairperson identifies and invites to the Consortium from DOE and other Federal agencies with equities in this Agreement, and empowered to speak on behalf of their agencies' interests. The Attorney General and the Chairman of the FTC, or their delegates, may also attend any meeting as a Representative.
                </P>
                <P>
                    14. 
                    <E T="03">Steering Committee</E>
                    —Senior officials from DOE and representatives from industry to guide priorities and provide feedback on activities.
                </P>
                <P>
                    15. 
                    <E T="03">Sub-Committee</E>
                    —A group formed by a Committee from select Participants to further implement a Plan of Action.
                </P>
                <P>
                    16. 
                    <E T="03">Subcommittee Co-lead</E>
                    —A DOE official, appointed by the Chairperson, to chair a Subcommittee to develop or implement a Plan of Action. The Subcommittee Chairperson (or “Subcommittee Chair”) shall be responsible for the overall management and administration of the Subcommittee in furtherance of this Plan of Action while remaining under the supervision of the Secretary of Energy and the Chairperson.
                </P>
                <HD SOURCE="HD2">B. Governance Structure</HD>
                <P>
                    1. 
                    <E T="03">Chairperson</E>
                    —Assistant Secretary for Nuclear Energy, as delegated by the Secretary of Energy. Chairs the Consortium and ensures compliance.
                </P>
                <P>
                    2. 
                    <E T="03">Vice-Chairperson</E>
                    —Deputy Assistant Secretary for Nuclear Fuel Cycle, as delegated by the Assistant Secretary for Nuclear Energy. Performs deputized tasks as appropriate for the Chairperson.
                </P>
                <P>
                    3. 
                    <E T="03">Convening Chair</E>
                    —DOE official tasked with supporting the regular operations of a Committee (may also be referred to as “Committee Chair”).
                </P>
                <P>
                    4. 
                    <E T="03">Steering Committee</E>
                    —Senior representatives from DOE, National Nuclear Security Administration (NNSA), DOJ, FTC, and industry to guide priorities, along with representatives from other federal agencies as appropriate. Members include the Deputy Assistant Secretaries for Nuclear Reactors and High-Level Waste and Disposition. Industry representation will include one representative from invited trade organizations.
                </P>
                <P>
                    5. 
                    <E T="03">Committees</E>
                    —Organized by fuel cycle stage; each develops POAs.
                </P>
                <P>
                    6. 
                    <E T="03">Secretariat</E>
                    —Ensures the maintenance of records, agendas, and minutes, coordinates activities as appropriate.
                </P>
                <HD SOURCE="HD1">V. Committee Participation</HD>
                <P>
                    The Committees established under this Agreement will consist of (1) a DOE official, (2) Representatives from NNSA, DOJ, FTC and other Federal agencies with equities in this Agreement, and (3) Participants that have substantive capabilities, resources or expertise to carry out the purpose of this Agreement. Other Attendees, invited by the Convening Chair as SMEs to provide technical advice or to represent the interests of other Government agencies or interested parties, may also participate in Committee meetings. Collectively, the Convening Chair, Representatives and Participants will serve as Members of the Committee. Public notice will be provided as each Participant joins or withdraws from this Agreement. The list of Participants will be published annually in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <HD SOURCE="HD2">A. Effective Dates and Duration of Participation</HD>
                <P>This Agreement is effective immediately upon the signature of the Participant or their authorized designees. This Agreement shall remain in effect until terminated in accordance with 10 CFR 821.5, or in any case, it shall be effective no more than five (5) years from the date the requirements of DPA section 708(f)(1) are satisfied as to the initial Voluntary Agreement regarding the development and maintenance of a resilient, secure, and sustainable nuclear fuel supply chain, from mining through waste management, for purposes of national defense and energy independence, unless otherwise terminated pursuant to DPA section 708(h)(9) and 10 CFR 821.5 or extended as set forth in DPA section 708(f)(2). No action may take place under this Agreement until it is activated, as described below.</P>
                <HD SOURCE="HD2">B. Withdrawal</HD>
                <P>Participants may withdraw from this Agreement at any point, subject to the fulfillment of obligations incurred under this Agreement prior to the date this agreement is terminated with regard to such Participant, by giving written notice to the Chairperson at least fifteen (15) calendar days prior to the effective date of that Participant's withdrawal. Following receipt of such notice, the Chairperson will inform the other Participants of the date of the withdrawal. Upon the effective date of the withdrawal, the Participant must cease all activities under this Agreement.</P>
                <HD SOURCE="HD2">C. Removal</HD>
                <P>Committee Members shall actively participate in designated working groups, providing subject matter expertise, data, and/or other resources as defined in their company's approved capability statement (see Appendix 2). Failure to meet participation requirements, defined as no less than 75% of scheduled meetings and timely submission of accepted deliverables, may result in suspension of membership privileges, including loss of voting rights and removal from the Committee. Participants may be removed from this Agreement at any point if not actively participating in at least one Committee or at the discretion of the Consortium Chairperson. If such a determination is made, the Participant will receive written notice from the Chairperson at least fifteen (15) calendar days prior to the effective date of that Participant's removal, during which time the Participant may appeal the removal in writing. Following receipt of such notice, the Chairperson will inform the other Participants of the date of the removal.</P>
                <P>Upon the effective date of the removal, the Participant must cease all activities under this Agreement.</P>
                <HD SOURCE="HD2">D. Plan of Action Activation and Deactivation</HD>
                <P>
                    The Chairperson may authorize a POA and Committee for one or more specific workstreams, 
                    <E T="03">e.g.,</E>
                     a fuel fabrication plan of action, or a conversion plan of action, or a mining &amp; milling plan of action. The Chairperson will invite a select group of Participants who are representative of the segment of the industry for which the POA is intended to participate on the Committee. The POA will be activated for each invited Participant when the Participant executes a POA Agreement. Actions taken by Participants to develop a POA and actions taken after executing a POA Agreement to collectively coordinate, plan and collaborate, pursuant to that POA and as directed and supervised by DOE, will constitute action taken to develop and carry out this Agreement pursuant to 50 U.S.C. 4558(j).
                </P>
                <P>
                    Committees will meet only for the purposes specified in this Agreement and as provided for in writing by the Chairperson. They will report directly to 
                    <PRTPAGE P="40996"/>
                    the Committee regarding all actions taken by them, and any POA adopted by a Committee must be approved first by the Chairperson. A POA may not become effective unless and until the Attorney General (after consultation with the Chairman of the FTC) finds, in writing, that such purpose(s) of the POA may not reasonably be achieved through a POA having less anticompetitive effects or without any POA and publishes such finding in the 
                    <E T="04">Federal Register</E>
                    . The Chairperson will appoint a Committee Convening Chair to preside over each Committee as a delegate of the Chairperson; however, the Chairperson retains responsibility for all Committees and for administerial and recordkeeping requirements of any meetings held by such Committees, including providing public notice as required of any meetings.
                </P>
                <P>When recommended by the Committee Convening Chair, the Chairperson will provide notice of a POA Deactivation. Any actions taken by Participants after the Deactivation date are outside the scope of the POA Agreement and those defenses to antitrust violations that were previously afforded to Participants are no longer available.</P>
                <HD SOURCE="HD2">E. Rules and Regulations</HD>
                <P>Participants acknowledge and agree to comply with all provisions of DPA section 708, as amended, and regulations related thereto which are promulgated by DOE, the Attorney General, and the FTC. DOE has promulgated standards and procedures pertaining to voluntary agreements in 10 CFR part 821. Prior to participation in this Agreement or a POA, Participants agree to consult with internal or external antitrust or compliance counsel about the scope of the antitrust defense as outlined herein or in any subsequent POA. The Chairperson shall inform Participants of new rules and regulations as they are issued.</P>
                <HD SOURCE="HD2">F. Modification and Amendment</HD>
                <P>The Secretary of Energy, after consultation with the Attorney General and the Chairman of the FTC, may terminate or modify, in writing, this Agreement or a POA at any time, and may remove Participants from this Agreement or a POA at any time.</P>
                <P>Participants may propose modifications or amendments to this Agreement at any time. The Chairperson shall inform Participants of modifications or amendments to this Agreement as they are issued. If a Participant indicates an intent to withdraw from the Agreement due to a modification or amendment of the Agreement, the Participant will not be required to perform actions directed by that modification or amendment.</P>
                <P>The Attorney General, after consultation with the Chairman of the FTC and the Secretary of Energy, may terminate or modify, in writing, this Agreement or a POA at any time, and may remove Participants from this Agreement or a Plan of Action at any time. If the Attorney General decides to use this authority, the Attorney General will notify the Chairperson as soon as possible, who will in turn notify Participants. Any actions taken by a Participant after the Participant's withdrawal or removal from this Agreement or a POA are outside the scope of a POA Agreement. Accordingly, defenses against antitrust violations that were previously afforded to the Participant would no longer be available.</P>
                <HD SOURCE="HD2">G. Expenses</HD>
                <P>Participation in this Agreement does not confer funds to Participants, nor does it limit or prohibit any pre-existing source of funds. Unless otherwise specified, all expenses, administrative or otherwise, incurred by Participants associated with participation in this Agreement shall be borne exclusively by the Participants.</P>
                <HD SOURCE="HD2">H. Recordkeeping</HD>
                <P>The Chairperson shall have primary responsibility for maintaining records in accordance with 10 CFR 821.3 and shall be the official custodian of records related to carrying out this Agreement. These activities may be delegated to the Secretariat.</P>
                <P>Each Participant shall maintain for five (5) years all records, documents, and other data, including any communications with other Participants or with any other member of the Committee, including drafts, related to the carrying out of this Agreement or any POA or incorporating data or information received in the course of carrying out this Agreement or any POA. Each Participant agrees to produce to the Secretary of Energy, the Attorney General, and the Chairman of the FTC upon request any item that this section requires the Participant to maintain. Any record maintained in accordance with 10 CFR part 821 shall be available for public inspection and copying, unless exempted on the grounds specified in 5 U.S.C. 552(b)(1), (3) or (4) or identified as privileged and confidential information in accordance with DPA section 708(d), and 10 CFR part 821.</P>
                <HD SOURCE="HD1">VI. Antitrust Defense</HD>
                <P>Under the provisions of DPA section 708(j), each Participant in this Agreement shall have available as a defense to any civil or criminal action brought for violation of the antitrust laws (or any similar law of any State) with respect to any action to develop or carry out this Agreement or a POA, insofar as such action was taken by the Participant in the course of developing or carrying out this Agreement or a POA, that the Participant fully complied with the provisions of DPA section 708 and the rules promulgated thereunder, and that the Participant acted in accordance with the terms of this Agreement and any relevant POA. Except in the case of actions taken to develop this Agreement or a POA, this defense shall be available only if and to the extent the Participant asserting the defense demonstrates that the action was specified in, or was within the scope of, this Agreement or a POA. Prior to participation in this Agreement or a POA, Participants agree to consult with internal or external antitrust or compliance counsel about the scope of the antitrust defense as outlined herein or in any subsequent POA.</P>
                <P>This defense shall not apply to any action occurring after the termination of this Agreement or a POA, or after the withdrawal or removal of a Participant. Immediately upon modification of this Agreement or a POA, no antitrust defense shall apply to any subsequent action that is beyond the scope of the modified Agreement or POA. The Participant asserting the defense bears the burden of proof to establish the elements of the defense. The defense shall not be available if the person against whom the defense is asserted shows that the action was taken for the purpose of violating the antitrust laws.</P>
                <P>Except as specifically provided in section 708(j) of the DPA, nothing in this Agreement shall be deemed to convey to any Participant any immunity from civil or criminal liability, or to create defenses to actions, under the antitrust laws.</P>
                <HD SOURCE="HD1">VII. Terms and Conditions</HD>
                <P>Each Participant agrees to voluntarily collaborate with all Consortium Members to recommend POAs and Sub-Committees that will, at the direction of and under the supervision of DOE, bolster the domestic nuclear fuel cycle to enable the continued reliable operation of the Nation's existing, and future, nuclear reactors.</P>
                <P>
                    As the sponsoring agency, DOE will maintain oversight over Committee and Sub-Committee activities and direct and 
                    <PRTPAGE P="40997"/>
                    supervise actions taken to carry out this Agreement and subsequent POAs, including by retaining decision-making authority over actions taken pursuant to this Agreement and subsequent POAs to ensure such actions are necessary to address a direct threat to the national defense. The DOJ and FTC will monitor activities of the Committee and Sub-Committees to ensure they execute their responsibilities in a manner consistent with this Agreement having the least anticompetitive effects possible.
                </P>
                <HD SOURCE="HD1">VIII. Plan of Action Execution</HD>
                <P>Specific Member obligations and actions to be undertaken will only be provided for in individual POAs, not in the Agreement. Activities taken in the course of developing a POA or to carry out a POA that has been activated under the Committee Participation section will provide Participants with the antitrust defense described in the Antitrust Defenses section above. Each POA will identify the conduct that Participants will undertake in carrying out the POA and that would be subject to the defense described in the Antitrust Defenses section.</P>
                <P>Each POA will describe what information Members will share, as directed by DOE and under DOE's supervision. Each POA, and information gathered pursuant to that plan, will be used to support efforts to ensure that the nuclear fuel supply chain capacity, including milling, conversion, enrichment, deconversion, fabrication, recycling, or reprocessing, is available to enable the continued reliable operation of the Nation's existing, and future, nuclear reactors.</P>
                <HD SOURCE="HD1">IX. Information Management and Responsibilities</HD>
                <P>DOE will request only those data and information from Participants that are necessary to meet the objectives of a POA. Upon signing a POA Agreement, Participants should endeavor to cooperate to the greatest extent possible to share data and information necessary to meet the objectives of the POA.</P>
                <P>The specific data requested, procedures for sharing that data, and data management and disposition will be tailored for each specific POA. Where feasible and to the greatest extent possible, DOE will incorporate the following principles regarding data sharing into each POA:</P>
                <P>1. Participants will not share competitively sensitive information (CSI) directly with other Participants. Direct sharing of information among Participants will be requested only when necessary to accomplish the goals outlined in the POA and will be closely supervised by DOE, DOJ, and FTC, including requiring appropriate safeguards regarding Participant use and dissemination of other Participants' data and information.</P>
                <P>2. DOE will only request direct sharing of CSI among Participants during Exigent Circumstances where there is a mission critical need or timeline such that sharing only through DOE is impractical or threatens the outcome of the POA or Committee. Such requests, if made, will be only among Participants whose participation is necessary to meet the objectives of the Plan, will be limited in scope to the greatest extent possible, and will be shared only pursuant to safeguards subject to prior review and audit by DOJ and FTC.</P>
                <P>
                    3. If DOE needs to share information with parties outside a Committee (
                    <E T="03">e.g.</E>
                     the Consortium Chair or DOE General Counsel), DOE will limit the amount and type of information shared to the greatest extent feasible and permitted by law, while still furthering the objectives of the POA.
                </P>
                <P>4. Prior to distribution within or outside the Committee, DOE will aggregate and anonymize data in such a way that will maximize the effectiveness of the POA without compromising CSI.</P>
                <P>5. Pursuant to 5 U.S.C. 552(b)(4) and 10 CFR 821.6, DOE will withhold from disclosure under the Freedom of Information Act (FOIA) Participant trade secrets and commercial or financial information that is privileged or confidential and will restrict Committee meeting attendance where necessary to protect such information.</P>
                <P>6. Any party receiving CSI through a POA shall use such information solely for the purposes outlined in the POA and take steps, such as imposing firewalls or tracking usage, to ensure such information is not used for any other purpose. Disclosure and use of competitively sensitive information will be limited to the greatest extent possible.</P>
                <P>7. At the conclusion of a Participant's involvement in a POA (due to the deactivation of the POA or due to the Participant's withdrawal or removal) each Participant will be requested to sequester any and all CSI received through participation in the POA. This sequestration will include the deletion of all CSI unless required to be kept pursuant to the Recordkeeping requirements as described supra, Section I, 10 CFR 821.6, or any other provision of law.</P>
                <HD SOURCE="HD1">X. Oversight</HD>
                <P>
                    The Chairperson is responsible for ensuring the Attorney General, or suitable delegate(s) from DOJ, and the FTC Chairman, or suitable delegate(s) from the FTC, have awareness of activities under this Agreement, including POA activation, deactivation, and scheduling of meetings. The Attorney General, the FTC Chairman, or their delegates may attend Consortium and Committee meetings and request to be apprised of any activities taken in accordance with activities under this Agreement or a POA. DOJ or FTC Representatives may request and review any proposed action by the Consortium, Committee, or Participants undertaken pursuant to this Agreement or POA, including the provision of data and information. If any DOJ or FTC Representative believes any action proposed or taken is not consistent with the antitrust laws, accounting for the antitrust defenses provided by the DPA, he or she shall provide warning and guidance to the Committee as soon as the potential issue is identified. If questions arise about the antitrust defense applicable to any particular action, DOE may request that DOJ, in consultation with the FTC, provide an opinion on the legality of the action under the antitrust laws and the potential applicability of the DPA antitrust defense. The Consortium Chairperson shall notify the Attorney General, the Chairman of the FTC, Representatives, and Participants of the time, place, and nature of each meeting and of the proposed agenda of each meeting to be held to carry out this Agreement. Additionally, the Chairperson shall provide for publication in the 
                    <E T="04">Federal Register</E>
                     of a notice of the time, place, and nature of each Consortium meeting. If a meeting is open, a 
                    <E T="04">Federal Register</E>
                     notice will be published reasonably in advance of the meeting. The Consortium Chairperson may restrict attendance at meetings only on the grounds outlined by 10 CFR 821.6. If a meeting is closed, a 
                    <E T="04">Federal Register</E>
                     notice will be published within 10 days of the meeting and will include the reasons for that decision.
                </P>
                <P>
                    The Chairperson shall establish the agenda for each Consortium meeting, be responsible for adherence to the agenda, and provide for a written summary or other record of each Consortium meeting and provide copies of transcripts or other records to DOE, the Attorney General, the Chairman of the FTC, and all Participants. The Chair shall take necessary actions to protect from public disclosure any data 
                    <PRTPAGE P="40998"/>
                    discussed with or obtained from Participants which a Participant has identified as a trade secret or as privileged and confidential in accordance with DPA sections 708(h)(3) and 705(d), or which qualifies for withholding under 10 CFR 821.6.
                </P>
                <HD SOURCE="HD1">XI. Application and Agreement</HD>
                <P>
                    The Participant agrees to join in the U.S. Department of Energy-sponsored Voluntary Agreement entitled “DOE Nuclear Fuel Cycle Defense Production Act (DPA) Consortium” and to become a Participant in this Consortium. This Agreement will be published in the 
                    <E T="04">Federal Register</E>
                    . This Agreement is authorized under section 708 of the Defense Production Act of 1950, as amended. Regulations governing this Agreement appear at 10 CFR part 821. The applicant, as Participant, agrees to comply with the provisions of section 708 of the Defense Production Act of 1950, as amended, the regulations at 10 CFR part 821, and the terms of this Agreement.
                </P>
                <P>No Participant may assign or transfer this Agreement, in whole or in part, or any protections, rights or obligations hereunder without the prior written consent of the Chairperson. When requested, the Chairperson will respond to written requests for consent within 10 business days of receipt.</P>
                <HD SOURCE="HD1">Appendix 1: DPA Consortium Committee Governance Model</HD>
                <EXTRACT>
                    <HD SOURCE="HD2">Overview</HD>
                    <P>Technical committees are led by U.S. Government (USG) and industry co-leads, with outputs monitored by the Deputy Assistant Secretary (DAS) for Nuclear Fuel. The rotating co-lead model ensures equitable leadership, continuity of effort, and diverse representation across the DPA Consortium, emphasizing shared stewardship, transparency, and continuity.</P>
                    <HD SOURCE="HD2">Benefits of the Co-lead Role</HD>
                    <P>Serving as a co-lead provides organizations with the ability to:</P>
                    <P>• Shape the Consortium's agenda by identifying key focus areas and leading workstreams during their term.</P>
                    <P>• Gain national visibility and credibility as a trusted leader within the nuclear fuel supply chain community.</P>
                    <P>• Directly contribute to DPA policy alignment and programmatic recommendations to DOE and interagency partners.</P>
                    <P>• Develop lasting partnerships across government, industry, and allied stakeholders.</P>
                    <P>• Promote innovation and cross-sector collaboration through engagement and outreach.</P>
                    <P>• Leave a measurable legacy via defined deliverables and end-of-term recommendations.</P>
                    <P>• Receive recognition in official DPA events, consortium documentation, and federal briefings.</P>
                    <HD SOURCE="HD2">Structure and Mechanics</HD>
                    <P>The co-lead model operates on staggered six-month terms supported by an overlap system that ensures mentorship, institutional memory, and seamless continuity between rotations.</P>
                    <HD SOURCE="HD2">Term Length and Rotation</HD>
                    <P>• Each co-lead serves a six-month term.</P>
                    <P>• Terms are staggered: one co-lead rotates off while another rotates on.</P>
                    <P>• The initial 'anchor term' for one co-lead lasts nine months, the second co-lead serves the standard six months, with DOE as a voting member to stabilize the process.</P>
                    <GPH SPAN="3" DEEP="73">
                        <GID>EN06JY26.000</GID>
                    </GPH>
                    <HD SOURCE="HD2">Triumvirate Leadership Model</HD>
                    <P>At any given time, three co-leads are active, forming a triumvirate:</P>
                    <P>• DOE Co-lead: represents DOE, provides continuity and historical context.</P>
                    <P>• Current Co-Lead: drives agenda-setting and manages deliverables.</P>
                    <P>• Incoming Co-Lead: shadows, learns, and prepares to assume leadership.</P>
                    <P>This system ensures leadership continuity and mitigates disruption.</P>
                    <HD SOURCE="HD2">Agenda-Setting and Decision-Making</HD>
                    <P>• Industry Co-Leads coordinate with DOE to propose 2-3 focus areas per term to guide committee priorities.</P>
                    <P>• Consensus is preferred but decisions will be made by majority vote (2 of 3 Co-Leads), with DOE acting as a tie-breaker.</P>
                    <P>• DOE, together with its partners the U.S. Department of Justice, Antitrust Division and the Federal Trade Commission, will maintain procedural oversight to ensure compliance, fairness, accordance with competition laws, and documentation integrity.</P>
                    <HD SOURCE="HD3">Recognition and Reporting</HD>
                    <P>• Each term concludes with a briefing to the Steering Committee summarizing key accomplishments and recommendations.</P>
                    <P>• Outgoing Co-leads receive recognition during Steering Committee meetings and published consortium reports.</P>
                    <P>• Each transition includes a formal handoff meeting to sustain momentum and knowledge transfer.</P>
                    <HD SOURCE="HD2">Consortium-Level Benefits</HD>
                    <P>The rotating co-lead structure supports the consortium's mission by:</P>
                    <P>• Preventing concentration of influence in any one entity.</P>
                    <P>• Encouraging active participation from diverse industry partners.</P>
                    <P>• Maintaining operational momentum and institutional memory.</P>
                    <P>• Fostering leadership development and broad stakeholder engagement.</P>
                    <HD SOURCE="HD2">Implementation Timeline</HD>
                    <P>The inaugural term (Anchor Phase) launches with DOE and two founding co-leads, one serving nine months. After this phase, a new co-lead joins every three months, ensuring a constant overlap of outgoing, current, and incoming leaders. This staggered rotation builds a continuous leadership cycle and reinforces long-term continuity.</P>
                    <HD SOURCE="HD3">Procedure for Election of Industry Co-Leads in Newly Formed Committees</HD>
                    <HD SOURCE="HD2">Purpose</HD>
                    <P>This procedure establishes the process for electing industry co-leads within newly formed Consortium committees. It ensures that selections are conducted in a transparent, standardized, and equitable manner while minimizing administrative burden.</P>
                    <HD SOURCE="HD2">Scope</HD>
                    <P>This procedure applies to all committees convened under the consortium structure following initial formation. It covers eligibility, nomination, evaluation, voting, and recordkeeping requirements for the selection of industry co-leads.</P>
                    <HD SOURCE="HD2">Responsibilities</HD>
                    <P>• Consortium Secretariat: Issues the call for nominations, compiles capability statements, manages the voting process, and maintains official documentation.</P>
                    <P>• Committee Members: Review candidate materials and participate in the rank-choice voting process.</P>
                    <P>
                        • DOE Co-lead: Serve as facilitators, NE-1 liaisons, and compliance reviewers.
                        <PRTPAGE P="40999"/>
                    </P>
                    <HD SOURCE="HD2">Eligibility and Nomination</HD>
                    <P>1. Any organization actively participating in the consortium may nominate itself for an industry co-lead position.</P>
                    <P>2. Each candidate organization must submit a Capability Statement Form not exceeding two pages.</P>
                    <P>3. The capability statement must include:</P>
                    <P>a. Organization overview and relevant role within the nuclear fuel cycle.</P>
                    <P>b. A brief mission alignment statement describing how the organization supports the committee's purpose.</P>
                    <P>c. Summary of key capabilities, resources, or facilities relevant to the committee.</P>
                    <P>d. Designation of a proposed representative and confirmation of their authority to serve as co-lead.</P>
                    <P>e. Level of commitment in terms of personnel, data, or engagement.</P>
                    <P>4. All submissions must be received by the deadline indicated in the call for nominations.</P>
                    <HD SOURCE="HD2">Review and Summary</HD>
                    <P>The Secretariat shall compile all capability statements into a single review packet and prepare a one-page summary sheet listing each candidate's key attributes for efficient review by committee members.</P>
                    <HD SOURCE="HD2">Voting Process</HD>
                    <P>1. Each committee will elect one or more industry co-leads using rank-choice voting.</P>
                    <P>2. Voting will be conducted electronically through Microsoft Forms.</P>
                    <P>3. Each committee member may rank up to three candidates in order of preference.</P>
                    <P>4. Votes will be tallied using instant-runoff methodology: the lowest-ranked candidate is eliminated in successive rounds until one candidate receives a majority of votes.</P>
                    <P>5. Voting is anonymous. The Secretariat will record and verify results.</P>
                    <P>6. In the event of a tie after runoff elimination, preference shall be given to the candidate whose capability statement demonstrates the strongest mission alignment, as determined by a 1-to-5 scale review by the Secretariat.</P>
                    <HD SOURCE="HD1">Timeline</HD>
                    <GPOTABLE COLS="4" OPTS="L2,tp0,i1" CDEF="s15,r50,r50,r50">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1">Step</CHED>
                            <CHED H="1">Activity</CHED>
                            <CHED H="1">Responsible party</CHED>
                            <CHED H="1">Timeline</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">1</ENT>
                            <ENT>Call for nominations issued</ENT>
                            <ENT>Secretariat</ENT>
                            <ENT>Day 0.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">2</ENT>
                            <ENT>Capability statements submitted</ENT>
                            <ENT>Candidate organizations</ENT>
                            <ENT>Day 10.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">3</ENT>
                            <ENT>Review packet distributed</ENT>
                            <ENT>Secretariat</ENT>
                            <ENT>Day 12.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">4</ENT>
                            <ENT>Voting period open</ENT>
                            <ENT>Committee members</ENT>
                            <ENT>Days 13-18.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">5</ENT>
                            <ENT>Results verified and announced</ENT>
                            <ENT>Secretariat/DOE</ENT>
                            <ENT>Day 20.</ENT>
                        </ROW>
                    </GPOTABLE>
                    <HD SOURCE="HD2">Term and Transition</HD>
                    <P>Co-leads (other than the anchor) shall serve a six-month term. There are no term limits, but no company shall be represented as a co-lead more than twice in a row. Outgoing co-leads will support transition activities and mentor incoming co-leads for at least 30 days following election confirmation.</P>
                    <HD SOURCE="HD2">Consolidation and Division of Committees</HD>
                    <P>In those instances where a decision is made to consolidate the efforts of more than one committee into a larger, single committee, the consolidating committees may do so at the suggestion of the Steering Committee Chairperson or of their own volition. Similarly, an existing committee may divide into two or more committees at the suggestion of the Steering Committee Chairperson or of its own volition. Prior to any such consolidation (or division), members of the existing committees shall be informed of any planned consolidation (or division) and be permitted to vote in favor of the co-leads who shall lead the consolidated committee or newly-formed committees. Notice shall be provided to committee members of at least one (1) calendar day, not to exceed up to seven (7) calendar days, prior to the holding of a vote for co-leads. All other aspects of the consolidated committee or newly-formed committees shall conform to the other rules and procedures that apply to committees as outlined in this Voluntary Agreement.</P>
                    <HD SOURCE="HD2">Documentation and Recordkeeping</HD>
                    <P>All materials—including the call for nominations, capability statements, summary sheets, ballots, and final results—shall be maintained in a single electronic folder for audit and transparency purposes. Meeting records need only include a brief summary of the process and final outcome for public record. Parties will use password protection on documents when emailing sensitive information. Access within DOE to committee records will be limited to the Consortium Secretariat, the DPA Administrative Coordinator, the committee's DOE co-lead and the committee's NNSA representatives, as appropriate.</P>
                    <P>
                        DOE will aim to publish monthly committee meeting schedules in the 
                        <E T="04">Federal Register</E>
                         around the beginning of each month, and these submissions will include summaries and participation reports from the previous month's meetings. Committee meetings will be recorded with transcripts on Microsoft TEAMS, and DOE will maintain these files. All committee-level meetings will be closed by default due to the need to be able to share sensitive information.
                    </P>
                    <HD SOURCE="HD2">Capability Statement (Maximum 2 Pages)</HD>
                    <P>Each Company must submit a Capability Statement to be part of a committee, renewable every six months. Each statement must include:</P>
                    <P>• Committee Name</P>
                    <P>• Company</P>
                    <P>• Primary Contact/Proposed Co-Lead—Identify each point of contact (POC) on the Committee, and any POCs nominated for co-lead. Include titles and emails.</P>
                    <P>• Organization Overview (≤100 words)</P>
                    <P>• Mission Alignment (≤150 words)—Explanation of how the organization's activities or expertise support the mission and objectives of the committee.</P>
                    <P>• Key Capabilities &amp; Resources—List of up to 5 relevant assets, technologies, or experiences.</P>
                    <P>• Commitment Summary—Description of expected level of engagement (meetings, data, staff time, etc.).</P>
                    <P>• Certification—“I certify that the information provided is accurate and that the POC(s)/proposed co-lead has authority to serve on behalf of the organization.”</P>
                    <P>• Signature(s)/Date</P>
                </EXTRACT>
                <HD SOURCE="HD1">Appendix 2: The DPA Consortium Advisory Forum</HD>
                <EXTRACT>
                    <HD SOURCE="HD3">1. Purpose</HD>
                    <P>The DPA Nuclear Fuel Cycle Consortium Advisory Forum (“Advisory Forum”) is established to provide independent, non-commercial technical, policy, and implementation insight in support of consortium activities. The Forum is advisory only and is intentionally structured to strengthen technical rigor, reduce implementation risk, and preserve strong antitrust and governance safeguards.</P>
                    <HD SOURCE="HD3">2. Role in the Consortium Planning &amp; Execution Cycle</HD>
                    <P>The Advisory Forum is intentionally positioned after Plan of Action (POA) approval. Its role is to:</P>
                    <P>• Review implementation assumptions and offer peer review</P>
                    <P>• Identify execution-phase risks</P>
                    <P>• Highlight regulatory, safety, cyber, and environmental vulnerabilities</P>
                    <P>The Forum does not participate in the creation of POAs, but SMEs may be consulted.</P>
                    <HD SOURCE="HD3">3. Standing Approved SME Roster</HD>
                    <P>The Advisory Forum will serve as a standing roster of pre-vetted, approved SMEs from which advisory support may be drawn on demand. SMEs may be engaged individually, in small technical panels, or through full Forum meetings.</P>
                    <P>Representative SME categories may include, but are not limited to:</P>
                    <P>• Nuclear policy</P>
                    <P>• Nuclear engineering &amp; reactor physics</P>
                    <P>• Fuel cycle science (mining through recycling)</P>
                    <P>• Safeguards, material control &amp; accounting</P>
                    <P>• Cybersecurity for critical infrastructure</P>
                    <P>
                        • Artificial Intelligence &amp; high-performance computing
                        <PRTPAGE P="41000"/>
                    </P>
                    <P>• Environmental remediation &amp; waste management</P>
                    <P>• Radiological health &amp; emergency preparedness</P>
                    <P>• Supply chain resilience &amp; critical materials</P>
                    <P>• Export controls and nonproliferation</P>
                    <P>• Workforce development &amp; labor economics</P>
                    <HD SOURCE="HD3">4. Membership Model: Organization-Based Participation</HD>
                    <P>SME participation is approved at the organization level rather than as private individuals, although each POC must be identified and vetted. This structure provides institutional accountability, professional liability coverage, and quality control, while also allowing experienced former government officials to participate through their established consulting firms or research institutions.</P>
                    <P>Acceptable organization types include:</P>
                    <P>• National laboratories</P>
                    <P>• Universities and national research institutes</P>
                    <P>• Nonprofit policy and technical institutes</P>
                    <P>• Independent consulting firms with nuclear, energy, cyber, or safety specialization</P>
                    <P>Private citizens acting solely in an individual capacity are not eligible for direct roster inclusion.</P>
                    <HD SOURCE="HD3">5. SME Vetting &amp; Approval Process</HD>
                    <P>All organizations seeking SME participation must complete a formal vetting process.</P>
                    <P>1. Submission of organizational profile and individual SME qualifications</P>
                    <P>2. Disclosure of current and recent commercial affiliations</P>
                    <P>3. Conflict-of-interest disclosure for each named SME</P>
                    <P>4. Certification of non-industry advisory role</P>
                    <P>5. Acceptance of Consortium information-handling and ethics rules</P>
                    <P>Final approval authority rests within the Consortium Chair and DOE General Counsel.</P>
                    <HD SOURCE="HD3">6. Legal, Antitrust &amp; Information Safeguards</HD>
                    <P>• SMEs operate in a non-commercial, non-competitive advisory capacity only</P>
                    <P>• No pricing, procurement strategy, vendor comparison, or market allocation discussions are permitted</P>
                    <P>• Access is limited to aggregated, non-market-sensitive technical data</P>
                    <P>• All engagements require a defined scope of work and documented outputs</P>
                    <P>• SMEs must reaffirm conflict disclosures annually</P>
                    <HD SOURCE="HD3">7. Meeting &amp; Engagement Structure</HD>
                    <P>The Advisory Forum may convene as a group to support the Consortium. Ad hoc SME engagements may occur as needed to support specific technical reviews, panels, or implementation challenges. Organizations in the Advisory Forum may be identified as standing SMEs in a POA.</P>
                    <HD SOURCE="HD3">8. Liability &amp; Risk Control</HD>
                    <P>All SMEs participate under written advisory agreements that include liability limitations, confidentiality provisions, and indemnification language as approved by counsel.</P>
                    <HD SOURCE="HD3">9. Summary Statement</HD>
                    <P>The Advisory Forum provides a mechanism for incorporating subject matter expertise into Consortium execution. Organization-level membership, formal vetting, and strict antitrust safeguards ensure high-value insight while complying with DPA section 708.</P>
                    <HD SOURCE="HD1">Appendix 3: DPA Consortium Plan of Action Instructions &amp; Template</HD>
                    <HD SOURCE="HD2">Authorities</HD>
                    <P>Section 708, Defense Production Act (50 U.S.C. 4558); Section 161, Atomic Energy Act (42 U.S.C. 2201); Section 123, Atomic Energy Act (42 U.S.C. 2153); Section 124, Atomic Energy Act (42 U.S.C. 2154); Executive Order (E.O.) 14156, Declaring a National Energy Emergency (90 FR 8433); E.O. 14302, Reinvigorating the Nuclear Industrial Base (90 FR 22595). Pursuant to DPA section 708(f)(1)(A), the Assistant Secretary for Nuclear Energy certifies that this Agreement is necessary to help provide for the national defense.</P>
                    <HD SOURCE="HD2">Plan of Action Instructions</HD>
                    <P>The following template is designed for use by committees formed under the DOE Defense Production Act (DPA) Consortium framework. Each committee may use this template to develop a specific plan of action (POA) for its chosen project(s). This document should be adapted as needed to align with project objectives, legal requirements, and coordination needs.</P>
                    <P>Each POA shall include the following elements, incorporating the guidance therein.</P>
                    <HD SOURCE="HD3">1. Committee Name &amp; Mission Statement</HD>
                    <P>
                        Each POA will identify the Committee name (
                        <E T="03">e.g.</E>
                         Fabrication Committee, Conversion Committee, etc.) and mission statement.
                    </P>
                    <HD SOURCE="HD3">2. Scope of Activities</HD>
                    <P>• Each Committee will identify at least one activity, addressing how each activity advances the goal of ensuring “that the nuclear fuel supply chain capacity, including milling, conversion, enrichment, deconversion, fabrication, recycling or reprocessing, is available to enable the continued reliable operation of the Nation's existing, and future, nuclear reactors.”</P>
                    <P>• The Federal Trade Commission (FTC) and Department of Justice (DOJ) will be available to consult with the Committee regarding the identified activities, potential alternatives, and any potential or likely anticompetitive effects. Prior to participation in this Agreement or a POA, all Participants in each Committee agree to consult with internal or external antitrust or compliance counsel about the scope of the antitrust defense as outlined herein or in any subsequent POA.</P>
                    <HD SOURCE="HD3">3. Participation Criteria</HD>
                    <P>Committee Members shall actively participate in designated working groups, providing subject matter expertise, data, and/or other resources as defined in their company's approved capability statement (as described below). Failure to meet participation requirements, defined as no less than 75% of scheduled meetings and timely submission of accepted deliverables, may result in suspension of membership privileges, including loss of voting rights and removal from the Committee.</P>
                    <P>• Each Committee will have one DOE Committee Chair who will convene the group, convey DOE priorities and concerns, coordinate activities between Participants, and ensure administration of the POA. Each Committee will report through the Committee Chair all milestones and achievements.</P>
                    <P>• Each Committee will have two Committee Co-leads, as voted by the other participants. This role will be staggered and rotate every six months among the members of each Committee.</P>
                    <P>• Each company will submit a short “capability statement” that maps their contribution to the Committee's goals.</P>
                    <P>• Coordination with the broader USG as well as interagency engagement should be identified and defined in this space.</P>
                    <P>• Subject Matter Experts (SME) have no standing role in the DPA Consortium but may be invited through the Advisory Forum. An Advisory Forum SME List will be made available to each Committee with a brief description of each group's capabilities and interests.</P>
                    <P>• A representative of the Federal Trade Commission and/or the Department of Justice must be in attendance at each Committee meeting to provide oversight and guidance.</P>
                    <P>• Committee sub-groups and working groups are at the discretion of the Committee leadership but should be identified.</P>
                </EXTRACT>
                <HD SOURCE="HD3">4. Roles and Responsibilities</HD>
                <EXTRACT>
                    <P>Each POA shall outline the specific roles and responsibilities for each Participant. All Participants must have a specific role and identified responsibilities.</P>
                    <HD SOURCE="HD3">5. Reporting &amp; Recordkeeping</HD>
                    <P>• Each Committee meeting shall produce a record of participants, objectives, outcomes, and next steps. The DOE Chair will keep this record.</P>
                    <P>• See “Recordkeeping” under Section V. “Committee Participation” and Section IX “Information Management and Responsibilities” in the Voluntary Agreement for more details on recordkeeping.</P>
                    <HD SOURCE="HD3">6. Timelines and Milestones</HD>
                    <P>• Milestones and Timelines shall be defined in the POA, corresponding with the “Scope of Activity” section above.</P>
                    <P>• POAs shall be reviewed every six months, and updated as necessary.</P>
                    <HD SOURCE="HD3">7. Resources Required</HD>
                    <P>Each POA will identify the resources required to accomplish the identified work. Unless explicitly identified in a previous or future federal program of record, no USG funding should be assumed.</P>
                    <HD SOURCE="HD3">8. Signatures</HD>
                    <P>Each POA will be approved by the DOE Committee Chair and the Consortium Steering Committee Vice Chair prior to submission to the Steering Committee.</P>
                </EXTRACT>
                <PRTPAGE P="41001"/>
                <HD SOURCE="HD1">Appendix 4: Participant Agreement for the DPA Consortium Voluntary Agreement </HD>
                <EXTRACT>
                    <P>This Participant Agreement (“Agreement”) is made and entered into by and between the United States Department of Energy (“DOE”) and the undersigned entity (“Participant”) for the purpose of participation in the Department's Defense Production Act (“DPA”) Section 708 Voluntary Agreement for the Nuclear Fuel Cycle Consortium (“Voluntary Agreement”).</P>
                    <HD SOURCE="HD3">1. Purpose and Authority</HD>
                    <P>This Agreement is entered into pursuant to Section 708 of the Defense Production Act of 1950, as amended (50 U.S.C. 4558), and implementing regulations at 10 CFR part 821. The purpose of this Agreement is to formalize the Participant's acknowledgment of, and agreement to, the terms, conditions, and obligations of participation under the Voluntary Agreement.</P>
                    <HD SOURCE="HD3">2. Voluntary Participation</HD>
                    <P>The Participant acknowledges that participation in the Voluntary Agreement is voluntary. The Participant may withdraw from participation at any time by providing written notice to DOE. Withdrawal shall not affect obligations or protections applicable to actions taken while participating in the Voluntary Agreement.</P>
                    <HD SOURCE="HD3">3. Compliance and Conduct</HD>
                    <P>The Participant agrees to comply with all terms, conditions, and procedures established by DOE for the administration of the Voluntary Agreement, including participation in meetings, sharing relevant non-public information subject to applicable confidentiality protections, and maintaining appropriate records of actions taken under the Voluntary Agreement.</P>
                    <HD SOURCE="HD3">4. Antitrust Protections</HD>
                    <P>Pursuant to section 708(j) of the DPA and implementing regulations, the Participant understands that activities conducted in accordance with this Voluntary Agreement, and under the supervision of DOE, are eligible for limited antitrust defense as specified by law.</P>
                    <HD SOURCE="HD3">5. Confidentiality and Records</HD>
                    <P>DOE will maintain records and documentation of meetings, decisions, and activities conducted under the Voluntary Agreement in accordance with applicable regulations. Participant acknowledges that certain information shared under the Voluntary Agreement may be subject to protection from public disclosure under the Freedom of Information Act consistent with DPA section 708 and DOE implementing DOE regulations at 10 CFR part 821.</P>
                    <P>By executing this Voluntary Agreement, each Participant agrees that the substance of discussions, statements, materials, data, analyses, and information exchanged during meetings, workshops, working groups, or other activities conducted pursuant to this Agreement, whether oral, written, or otherwise, shall be treated as confidential and shall not be disclosed to any non-Participant without prior written consent of the disclosing Participant and DOE.</P>
                    <P>Participants expressly agree not to attribute statements, positions, proposals, concerns, data, or views expressed during any meeting or activity under this Agreement to any other Participant outside the confines of this Agreement.</P>
                    <P>This confidentiality obligation applies regardless of whether the information is marked as confidential and survives the termination or expiration of this Agreement.</P>
                    <HD SOURCE="HD2">Permitted Disclosures</HD>
                    <P>Confidentiality obligations under this section shall not apply to information that:</P>
                    <P>1. Is already publicly available;</P>
                    <P>2. Was lawfully in the receiving Participant's possession prior to disclosure under this Agreement;</P>
                    <P>3. Is independently developed without the use of information obtained under this Agreement; or</P>
                    <P>4. Is required to be disclosed by law, regulation, court order, subpoena, or valid governmental request, provided that the receiving Participant gives prompt notice to the Government, and where practicable, the affected disclosing Participant.</P>
                    <HD SOURCE="HD3">6. Effective Date and Termination</HD>
                    <P>This Agreement becomes effective upon the date of the last signature below and remains in effect for the duration of the Participant's involvement in the Voluntary Agreement, unless withdrawn or terminated by DOE in accordance with applicable regulations.</P>
                    <HD SOURCE="HD3">7. Signatures</HD>
                    <FP SOURCE="FP-1">In witness whereof, the parties have executed this Participant Agreement: </FP>
                    <FP SOURCE="FP-1">Participant Organization: _______ </FP>
                    <FP SOURCE="FP-1">Authorized Representative (Name/Title): _______ </FP>
                    <FP SOURCE="FP-1">Signature: _______ </FP>
                    <FP SOURCE="FP-1">Date: _______ </FP>
                    <FP SOURCE="FP-1">U.S. Department of Energy (DOE)</FP>
                    <FP SOURCE="FP-1">Authorized Official (Name/Title): _______ </FP>
                    <FP SOURCE="FP-1">Signature: _______ </FP>
                    <FP SOURCE="FP-1">Date: _______</FP>
                </EXTRACT>
                <HD SOURCE="HD1">Appendix 5: Plan of Action Participation Acknowledgment</HD>
                <EXTRACT>
                    <P>This Acknowledgment is executed by the undersigned Participant to confirm participation in the following Plan of Action (“POA”) developed pursuant to the Department of Energy (“DOE”) Defense Production Act (“DPA”) Section 708 Voluntary Agreement for the Nuclear Fuel Cycle Consortium.</P>
                    <HD SOURCE="HD3">1. Identification of the Plan of Action</HD>
                    <FP SOURCE="FP-1">Title of Plan of Action: _______ </FP>
                    <FP SOURCE="FP-1">Date Approved by DOE: _______ </FP>
                    <FP SOURCE="FP-1">Federal Register Reference for VA Establishment: _______ </FP>
                    <HD SOURCE="HD3">2. Purpose and Scope</HD>
                    <P>The Participant acknowledges that this Plan of Action is established under the DOE DPA Voluntary Agreement and is designed to facilitate coordinated planning and execution of specific activities within the nuclear fuel cycle in support of the national defense and energy security objectives.</P>
                    <HD SOURCE="HD3">3. Agreement to Participate</HD>
                    <P>The Participant agrees to participate in this Plan of Action in accordance with its stated objectives, scope, and procedures as approved by DOE. The Participant further agrees to comply with confidentiality provisions, reporting requirements, and meeting protocols established for the Plan of Action.</P>
                    <HD SOURCE="HD3">4. Confidentiality and Antitrust Provisions</HD>
                    <P>The Participant acknowledges that all discussions and data exchanges under this Plan of Action must comply with the confidentiality and antitrust provisions of the underlying Voluntary Agreement and applicable law. DOE shall ensure all meetings are conducted in accordance with section 708 regulations, and DOE representatives shall be present during all substantive discussions among participants.</P>
                    <HD SOURCE="HD3">5. Term and Withdrawal</HD>
                    <P>This Acknowledgment remains effective for the duration of the Plan of Action or until the Participant provides written notice of withdrawal to DOE. Withdrawal from this Plan of Action does not affect the Participant's standing in other Plans of Action or the underlying Voluntary Agreement unless separately withdrawn.</P>
                    <HD SOURCE="HD3">6. Signatures</HD>
                    <FP SOURCE="FP-1">In witness whereof, the parties have executed this Plan of Action Participation Acknowledgment:</FP>
                    <FP SOURCE="FP-1">Participant Organization: _______ </FP>
                    <FP SOURCE="FP-1">Authorized Representative (Name/Title): _______ </FP>
                    <FP SOURCE="FP-1">Signature: _______ </FP>
                    <FP SOURCE="FP-1">Date: _______ </FP>
                    <FP SOURCE="FP-1">U.S. Department of Energy (DOE)</FP>
                    <FP SOURCE="FP-1">Authorized Official (Name/Title): _______ </FP>
                    <FP SOURCE="FP-1">Signature: _______ </FP>
                    <FP SOURCE="FP-1">Date: _______</FP>
                </EXTRACT>
                <HD SOURCE="HD1">Appendix 6: DPA Consortium Structure</HD>
                <EXTRACT>
                    <GPH SPAN="3" DEEP="357">
                        <PRTPAGE P="41002"/>
                        <GID>EN06JY26.001</GID>
                    </GPH>
                    <P>Set forth below is a full list of companies who have signed the Department's Defense Production Act Section 708 Voluntary Agreement for the Nuclear Fuel Cycle Consortium. </P>
                    <FP SOURCE="FP-1">3M Company</FP>
                    <FP SOURCE="FP-1">ALD Vacuum Technologies North America, Inc.</FP>
                    <FP SOURCE="FP-1">Alpha Nur, Inc.</FP>
                    <FP SOURCE="FP-1">Amentum Environment &amp; Energy, Inc.</FP>
                    <FP SOURCE="FP-1">Ameren Corporation</FP>
                    <FP SOURCE="FP-1">American Atomics Inc.</FP>
                    <FP SOURCE="FP-1">American Electric Power (AEP)</FP>
                    <FP SOURCE="FP-1">American Energy Technologies Co. (AETC)</FP>
                    <FP SOURCE="FP-1">American Nuclear Society</FP>
                    <FP SOURCE="FP-1">AmForge Corporation</FP>
                    <FP SOURCE="FP-1">Anfield Energy, Inc.</FP>
                    <FP SOURCE="FP-1">Antares Nuclear Inc.</FP>
                    <FP SOURCE="FP-1">Arbor Halides Inc.</FP>
                    <FP SOURCE="FP-1">Arizona Public Service Company (APS)</FP>
                    <FP SOURCE="FP-1">ATS Ohio, Inc.</FP>
                    <FP SOURCE="FP-1">BWX Technologies Inc.</FP>
                    <FP SOURCE="FP-1">Cameco US Holdings Inc.</FP>
                    <FP SOURCE="FP-1">Centrus Energy Corp.</FP>
                    <FP SOURCE="FP-1">Constellation Energy Generation, LLC</FP>
                    <FP SOURCE="FP-1">ConverDyn</FP>
                    <FP SOURCE="FP-1">Curio Solutions, LLC</FP>
                    <FP SOURCE="FP-1">Disa Technologies, Inc.</FP>
                    <FP SOURCE="FP-1">Dominion Energy</FP>
                    <FP SOURCE="FP-1">Duke Energy</FP>
                    <FP SOURCE="FP-1">Eagle Nuclear Energy Corp.</FP>
                    <FP SOURCE="FP-1">enCore Energy</FP>
                    <FP SOURCE="FP-1">Energy Fuels Resources (USA) Inc.</FP>
                    <FP SOURCE="FP-1">Energy Northwest</FP>
                    <FP SOURCE="FP-1">EnergySolutions</FP>
                    <FP SOURCE="FP-1">Entergy Services, LLC</FP>
                    <FP SOURCE="FP-1">Exodys Energy Inc</FP>
                    <FP SOURCE="FP-1">First American Nuclear Co. (FANCO)</FP>
                    <FP SOURCE="FP-1">Flibe Energy, Inc. (FEI)</FP>
                    <FP SOURCE="FP-1">Framatome Inc.</FP>
                    <FP SOURCE="FP-1">Frontier Nuclear and Minerals Inc.</FP>
                    <FP SOURCE="FP-1">General Matter</FP>
                    <FP SOURCE="FP-1">Global Laser Enrichment (GLE)</FP>
                    <FP SOURCE="FP-1">Global Nuclear Fuels—America, LLC</FP>
                    <FP SOURCE="FP-1">GreenMet</FP>
                    <FP SOURCE="FP-1">Hexium Inc.</FP>
                    <FP SOURCE="FP-1">IsoEnergy Ltd.</FP>
                    <FP SOURCE="FP-1">Kairos Power</FP>
                    <FP SOURCE="FP-1">Laramide Resources/NuFuels</FP>
                    <FP SOURCE="FP-1">Lightbridge Corporation</FP>
                    <FP SOURCE="FP-1">Louisiana Energy Services, LLC d/b/a Urenco USA</FP>
                    <FP SOURCE="FP-1">Mirion Technologies</FP>
                    <FP SOURCE="FP-1">NANO Nuclear Energy, Inc.</FP>
                    <FP SOURCE="FP-1">Natura Resources</FP>
                    <FP SOURCE="FP-1">Nuclear Energy Institute</FP>
                    <FP SOURCE="FP-1">Nusano, Inc.</FP>
                    <FP SOURCE="FP-1">NuScale Power, LLC</FP>
                    <FP SOURCE="FP-1">Oklo Inc.</FP>
                    <FP SOURCE="FP-1">Omega Project Co.</FP>
                    <FP SOURCE="FP-1">Orano USA LLC</FP>
                    <FP SOURCE="FP-1">ORAU</FP>
                    <FP SOURCE="FP-1">Pelican Energy Partners Base Zero GP LP</FP>
                    <FP SOURCE="FP-1">Pioneer Nuclear Inc.</FP>
                    <FP SOURCE="FP-1">Purdue University</FP>
                    <FP SOURCE="FP-1">Quadrant Nuclear Industries, Inc.</FP>
                    <FP SOURCE="FP-1">Quantum Leap Energy</FP>
                    <FP SOURCE="FP-1">Radiant Industries Incorporated</FP>
                    <FP SOURCE="FP-1">Raven-Flint Nuclear Corporation</FP>
                    <FP SOURCE="FP-1">SHINE Technologies, LLC</FP>
                    <FP SOURCE="FP-1">Solstice Advanced Materials</FP>
                    <FP SOURCE="FP-1">Southern California Edison</FP>
                    <FP SOURCE="FP-1">Southern Nuclear Operating Company</FP>
                    <FP SOURCE="FP-1">Standard Nuclear, Inc.</FP>
                    <FP SOURCE="FP-1">STP Nuclear Operating Company</FP>
                    <FP SOURCE="FP-1">Strata Energy</FP>
                    <FP SOURCE="FP-1">SuperCritical Technologies Corp</FP>
                    <FP SOURCE="FP-1">Talen Energy</FP>
                    <FP SOURCE="FP-1">Thorium Energy Alliance</FP>
                    <FP SOURCE="FP-1">Traxys North America, LLC</FP>
                    <FP SOURCE="FP-1">Triso-X, LLC</FP>
                    <FP SOURCE="FP-1">Uranium Energy Corp (UEC)</FP>
                    <FP SOURCE="FP-1">Ur-Energy, Inc.</FP>
                    <FP SOURCE="FP-1">Valar Atomics</FP>
                    <FP SOURCE="FP-1">Vistra Operations Company</FP>
                    <FP SOURCE="FP-1">Western Uranium &amp; Vanadium</FP>
                    <FP SOURCE="FP-1">WMC Energy Corp</FP>
                    <FP SOURCE="FP-1">Wolf Creek Nuclear Operating Corporation</FP>
                    <FP SOURCE="FP-1">Xcel Energy</FP>
                    <FP SOURCE="FP-1">X-Energy, LLC</FP>
                    <FP SOURCE="FP-1">Zeno Power Systems, Inc.</FP>
                </EXTRACT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13486 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6450-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="41003"/>
                <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 Accounting Request filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     AC26-89-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     ITC Midwest LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     ITC Midwest LLC submits supplement to correct inadvertent error on previous transmittal letter re sale of certain electric facilities to Midland Power Cooperative.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/26/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260626-5218.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/17/26.
                </P>
                <P>Take notice that the Commission received the following electric corporate filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     EC26-118-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     UGI Utilities, Inc., Wyoming Valley Electric Holdings LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Joint Application for Authorization Under Section 203 of the Federal Power Act of UGI Utilities, Inc., et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/26/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260626-5274.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/17/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     EC26-119-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Chief Conemaugh Power, LLC, Chief Keystone Power, LLC, Avenue Energy Opportunities Fund II AIV, L.P.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Joint Application for Authorization Under Section 203 of the Federal Power Act of Chief Conemaugh Power, LLC, et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5258.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/20/26.
                </P>
                <P>Take notice that the Commission received the following electric rate filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER10-2249-012.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Portland General Electric Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Supplement to 06/30/2025, Updated Triennial Market Power Analysis for Northwest Region of Portland General Electric Company.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/26/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260626-5276.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/17/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER10-2249-015.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Portland General Electric Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Change in Status and MBR Tariff Revisions for EDAM to be effective 12/31/9998.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5186.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/20/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-1085-002.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Midcontinent Independent System Operator, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: 2026-06-30_SA 4656 ATXI-Ameren MO 2nd Sub GIA (E0013) to be effective 3/22/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5057.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-1990-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     PSEG Energy Resources &amp; Trade LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: Response to Deficiency Notice to be effective 6/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5184.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/20/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-1999-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Midcontinent Independent System Operator, Inc., Entergy Services, LLC, Entergy Arkansas, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: Entergy Arkansas, LLC submits tariff filing per 35.17(b): 2026-06-29_Deficiency Response Entergy Companies Revisions Related to Order 898 to be effective 6/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5173.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/20/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-2993-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Alabama Power Company, Georgia Power Company, Mississippi Power Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Alabama Power Company submits tariff filing per 35.13(a)(2)(iii: Wadley BESS SISA Filing to be effective 6/16/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5169.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/20/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-2994-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Kentucky Utilities Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: PJM AFS FERC Rate Schedule No. 537 to be effective 6/30/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5171.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/20/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-2995-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Midcontinent Independent System Operator, Inc., Ameren Illinois Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Ameren Illinois Company submits tariff filing per 35.13(a)(2)(iii: 2026-06-29_SA 2685 Ameren-SIPC_Beckemeyer Proj Spec No. 8 to be effective 8/29/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5178.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/20/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-2996-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Hardin Wind LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Northeast Triennial MBR Update to be effective 6/30/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5182.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/28/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-2997-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Pleasant Hill Solar, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Northeast Triennial MBR Update to be effective 6/30/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5183.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/28/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-2998-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Jackpot Holdings, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Revised Market-Based Rate Tariff to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5191.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/20/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-2999-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Jones Farm Lane Solar, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Revised Market-Based Rate Tariff to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5194.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/20/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3000-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Mesa Wind Power LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Revised Market-Based Rate Tariff to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5196.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/20/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3001-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     North Allegheny Wind, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Revised Market-Based Rate Tariff to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5199.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/20/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3002-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Water Strider Solar, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Northeast Triennial MBR Update to be effective 6/30/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5200.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/28/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3003-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     North Rosamond Solar, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Revised Market-Based Rate Tariff to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5201.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/20/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3004-000.
                    <PRTPAGE P="41004"/>
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Pike Solar LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Revised Market-Based Rate Tariff to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5203.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/20/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3005-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Spanish Peaks Solar LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Revised Market-Based Rate Tariff to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5206.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/20/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3006-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Sweetland Wind Farm, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Revised Market-Based Rate Tariff to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5208.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/20/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3007-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Watlington Solar, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Northeast Triennial MBR Update to be effective 6/30/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5209.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/28/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3008-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Wildflower Solar LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Revised Market-Based Rate Tariff to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5212.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/20/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3009-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Alton Post Office Solar, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Revised Market-Based Rate Tariff to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5216.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/20/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3010-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Wildcat Wind Farm I, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Northeast Triennial MBR Update to be effective 6/30/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5222.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/28/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3011-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     AM Wind Repower LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Revised Market-Based Rate Tariff to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5223.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/20/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3012-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Foxglove Solar Project, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Revised Market-Based Rate Tariff to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5225.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/20/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3013-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Aspen Road Solar 1, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Revised Market-Based Rate Tariff to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5229.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/20/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3014-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Franklin Solar LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Revised Market-Based Rate Tariff to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5230.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/20/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3015-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Goose Prairie Solar LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Revised Market-Based Rate Tariff to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5233.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/20/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3016-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Wythe County Solar Project, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Northeast Triennial MBR Update to be effective 6/30/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5235.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/28/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3017-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Bitter Ridge Wind Farm, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Revised Market-Based Rate Tariff to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5239.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/20/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3018-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Radford's Run Wind Farm, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Northeast Triennial MBR Update to be effective 6/30/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5242.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/28/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3019-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Black Mesa Energy, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Revised Market-Based Rate Tariff to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5243.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/20/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3020-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Crystal Hill Solar, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Revised Market-Based Rate Tariff to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5246.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/20/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3021-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Stony Creek Wind Farm, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Northeast Triennial MBR Update to be effective 6/30/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5001.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/31/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3022-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Union Ridge Solar, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Northeast Triennial MBR Update to be effective 6/30/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5002.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/31/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3023-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Southwest Power Pool, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: 1636R35 Kansas Electric Power Cooperative, Inc. NITSA and NOA to be effective 9/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5004.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3024-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Southwest Power Pool, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: 1875R11 Kansas Electric Power Cooperative, Inc. NITSA and NOA to be effective 9/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5005.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3025-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Mid-Atlantic Interstate Transmission, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: MAIT submits a new Construction Agmt—SA No. 7684 to be effective 8/30/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5030.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3026-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Willowbrook Solar I, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Northeast Triennial MBR Update to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5082.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/31/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3027-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Southwest Power Pool, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: 3218R2 Evergy Metro and Evergy MO 
                    <PRTPAGE P="41005"/>
                    West Interconnection Agr to be effective 4/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5087.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3028-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     PJM Interconnection, L.L.C., Buckeye Power, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: PJM Interconnection, L.L.C. submits tariff filing per 35.13(a)(2)(iii: Revised SA No. 4753—NITSA Among PJM and Buckeye Power, Inc. to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5095.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3029-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     New York State Electric &amp; Gas Corporation.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: NYSEG-NYPA Attachment C—O&amp;M Annual Update to be effective 9/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5111.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3030-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     New York State Electric &amp; Gas Corporation.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Rate Schedule FERC No. 87 Supplement to be effective 9/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5116.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/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: June 30, 2026.</DATED>
                    <NAME>Carlos D. Clay,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13563 Filed 7-2-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. 2275-052]</DEPDOC>
                <SUBJECT>Public Service Company of Colorado; Notice of Intent To Prepare an Environmental Assessment</SUBJECT>
                <P>On January 16, 2026, the Public Service Company of Colorado (licensee) filed an application to surrender its license and decommission the Salida Hydro Nos. 1 &amp; 2 Project No. 2275. The project is located on the South Arkansas River and Fooses Creek in Chaffee County, Colorado. The project partially occupies federal land managed by the U.S. Forest Service (USFS) within the Pike-San Isabel National Forests.</P>
                <P>The licensee is proposing to surrender the project license and decommission and remove certain Salida U2 facilities (forebay, dam, penstock, outbuildings, etc.) and the previously decommissioned Salida U1 powerhouse and adjacent substation located on USFS lands administered by the Pike-San Isabel National Forests &amp; Cimarron and Comanche National Grasslands—Salida Ranger District, PSCo-owned lands, and privately owned lands. After decommissioning the site would be restored. A Notice of Application for Surrender of License Accepted for Filing and Soliciting Comments, Motions to Intervene, and Protests was issued on February 23, 2026. No comments were filed pursuant to the notice.</P>
                <P>
                    This notice identifies Commission staff's intention to prepare an environmental assessment (EA) under the National Environmental Policy Act (42 U.S.C. 4321 
                    <E T="03">et seq)</E>
                     for the project.
                    <SU>1</SU>
                    <FTREF/>
                     Commission staff plans to issue an EA by October 20, 2026. Revisions to the schedule may be made as appropriate. The EA will be issued for a 30-day comment period. All comments filed on the EA will be reviewed by staff and considered in the Commission's final decision on the proceeding.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         The unique identification number for documents relating to this environmental review is EAXX-019-20-000-1780990050.
                    </P>
                </FTNT>
                <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>
                <P>
                    Any questions regarding this notice may be directed to Rebecca Martin at 202-502-6012 or 
                    <E T="03">Rebecca.martin@ferc.gov.</E>
                </P>
                <EXTRACT>
                    <FP>(Authority: 18 CFR 2.1.)</FP>
                </EXTRACT>
                <SIG>
                    <DATED> Dated: June 30, 2026.</DATED>
                    <NAME>Debbie-Anne A. Reese,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13595 Filed 7-2-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>[Docket No. CP26-543-000]</DEPDOC>
                <SUBJECT>Southeast Supply Header, LLC; Notice of Application and Establishing Intervention Deadline</SUBJECT>
                <P>Take notice that on June 15, 2026, Southeast Supply Header, LLC (SESH), 915 N. Eldridge Parkway, Suite 1100, Houston, Texas 77079, filed an application pursuant to sections 7(b) and 7(c) of the Natural Gas Act and Part 157 of the Commission's regulations requesting authorization for its Tupelo Trail Project in George and Jefferson Davis Counties, Mississippi, and Richland Parish, Louisiana (Project).</P>
                <P>The Project consists of installing a new 23,470 horsepower Titan 130 turbine driven compressor unit and related appurtenances at the existing Lucedale Compressor Station; replacing the compressor on an existing compressor unit at the Lucedale Compressor Station; replacing the existing engine on Compressor Unit 2 at the Gwinville Compressor Station; uprating compressor engines at the Delhi, Gwinville, and Lucedale Compressor Stations by removing software controls that limit horsepower; and performing associated appurtenant activities.</P>
                <P>The Project will increase the design capacity on the SESH system by 110,000 dekatherms per day to serve the electric generation Plant Daniel in Jackson County, Mississippi, under a fully subscribed precedent agreement with Southern Company Services, Inc. SESH estimates the total cost of the Project to be $87,599,997 and proposes a rolled-in rate treatment for project costs and an incremental fuel rate for the firm service created by the Project, all as more fully set forth in the application which is on file with the Commission and open for public inspection.</P>
                <P>
                    In addition to publishing the full text of this document in the 
                    <E T="04">Federal Register</E>
                    , the Commission provides all interested persons an opportunity to view and/or print the contents of this document via the internet through the Commission's Home Page (
                    <E T="03">http://www.ferc.gov</E>
                    ). From the Commission's Home Page on the internet, this information is available on eLibrary. 
                    <PRTPAGE P="41006"/>
                    The full text of this document is available on eLibrary in PDF and Microsoft Word format for viewing, printing, and/or downloading. To access this document in eLibrary, type the docket number excluding the last three digits of this document in the docket number field.
                </P>
                <P>
                    User assistance is available for eLibrary and the Commission's website during normal business hours from FERC Online Support at (202) 502-6652 (toll free at 1-866-208-3676) or email at 
                    <E T="03">ferconlinesupport@ferc.gov,</E>
                     or the Public Reference Room at (202) 502-8371, TTY (202) 502-8659. Email the Public Reference Room at 
                    <E T="03">public.referenceroom@ferc.gov.</E>
                </P>
                <P>
                    Any questions regarding the proposed project should be directed to Estela D. Lozano, Regulatory Director, Southeast Supply Header, LLC, 915 N. Eldridge Parkway, Suite 1100, Houston, Texas 77079, by phone at (713) 627-4522, or by email at 
                    <E T="03">estela.lozano@enbridge.com.</E>
                </P>
                <P>
                    Pursuant to section 157.9 of the Commission's Rules of Practice and Procedure,
                    <SU>1</SU>
                    <FTREF/>
                     within 90 days of this Notice the Commission staff will either: complete its environmental review and place it into the Commission's public record (eLibrary) for this proceeding; or issue a Notice of Schedule for Environmental Review. If a Notice of Schedule for Environmental Review is issued, it will indicate, among other milestones, the anticipated date for the Commission staff's issuance of the final environmental impact statement (FEIS) or environmental assessment (EA) for this proposal. The filing of an EA in the Commission's public record for this proceeding or the issuance of a Notice of Schedule for Environmental Review will serve to notify federal and state agencies of the timing for the completion of all necessary reviews, and the subsequent need to complete all federal authorizations within 90 days of the date of issuance of the Commission staff's FEIS or EA.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         18 CFR 157.9.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Public Participation</HD>
                <P>There are three ways to become involved in the Commission's review of this project: you can file comments on the project, you can protest the filing, and you can file a motion to intervene in the proceeding. There is no fee or cost for filing comments or intervening. The deadline for filing a motion to intervene is 5:00 p.m. Eastern Time on July 21, 2026. How to file protests, motions to intervene, and comments is explained below.</P>
                <P>
                    For public inquiries and assistance with making filings such as interventions, comments, or requests for rehearing, contact the Office of Public Participation (OPP) at (202) 502-6595 or 
                    <E T="03">OPP@ferc.gov.</E>
                </P>
                <HD SOURCE="HD2">Comments</HD>
                <P>Any person wishing to comment on the project may do so. Comments may include statements of support or objections, to the project as a whole or specific aspects of the project. The more specific your comments, the more useful they will be.</P>
                <HD SOURCE="HD2">Protests</HD>
                <P>
                    Pursuant to sections 157.10(a)(4) 
                    <SU>2</SU>
                    <FTREF/>
                     and 385.211 
                    <SU>3</SU>
                    <FTREF/>
                     of the Commission's regulations under the NGA, any person 
                    <SU>4</SU>
                    <FTREF/>
                     may file a protest to the application. Protests must comply with the requirements specified in section 385.2001 
                    <SU>5</SU>
                    <FTREF/>
                     of the Commission's regulations. A protest may also serve as a motion to intervene so long as the protestor states it also seeks to be an intervenor.
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         18 CFR 157.10(a)(4).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         18 CFR 385.211.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         Persons include individuals, organizations, businesses, municipalities, and other entities. 18 CFR 385.102(d).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         18 CFR 385.2001.
                    </P>
                </FTNT>
                <P>To ensure that your comments or protests are timely and properly recorded, please submit your comments on or before 5:00 p.m. Eastern Time on July 21, 2026.</P>
                <P>There are three methods you can use to submit your comments or protests to the Commission. In all instances, please reference the Project docket number CP26-543-000 in your submission.</P>
                <P>
                    (1) You may file your comments electronically by using the eComment feature, which is located on the Commission's website at 
                    <E T="03">www.ferc.gov</E>
                     under the link to Documents and Filings. Using eComment is an easy method for interested persons to submit brief, text-only comments on a project;
                </P>
                <P>
                    (2) You may file your comments or protests 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 Documents and Filings. 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; first select “General” and then select “Comment on a Filing”; or
                </P>
                <P>(3) You can file a paper copy of your comments or protests by mailing them to the following address below. Your written comments must reference the Project docket number (CP26-543-000).</P>
                <P>To file via USPS: Debbie-Anne A. Reese, Secretary, Federal Energy Regulatory Commission, 888 First Street NE, Washington, DC 20426.</P>
                <P>To file via any other courier: Debbie-Anne A. Reese, Secretary, Federal Energy Regulatory Commission 12225 Wilkins Avenue, Rockville, Maryland 20852.</P>
                <P>
                    The Commission encourages electronic filing of comments (options 1 and 2 above) and has eFiling staff available to assist you at (202) 502-8258 or 
                    <E T="03">FercOnlineSupport@ferc.gov.</E>
                </P>
                <P>Persons who comment on the environmental review of this project will be placed on the Commission's environmental mailing list, and will receive notification when the environmental documents (EA or EIS) are issued for this project and will be notified of meetings associated with the Commission's environmental review process.</P>
                <P>The Commission considers all comments received about the project in determining the appropriate action to be taken. However, the filing of a comment alone will not serve to make the filer a party to the proceeding. To become a party, you must intervene in the proceeding. For instructions on how to intervene, see below.</P>
                <HD SOURCE="HD2">Interventions</HD>
                <P>
                    Any person, which includes individuals, organizations, businesses, municipalities, and other entities,
                    <SU>6</SU>
                    <FTREF/>
                     has the option to file a motion to intervene in this proceeding. Only intervenors have the right to request rehearing of Commission orders issued in this proceeding and to subsequently challenge the Commission's orders in the U.S. Circuit Courts of Appeal.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         18 CFR 385.102(d).
                    </P>
                </FTNT>
                <P>
                    To intervene, you must submit a motion to intervene to the Commission in accordance with Rule 214 of the Commission's Rules of Practice and Procedure 
                    <SU>7</SU>
                    <FTREF/>
                     and the regulations under the NGA 
                    <SU>8</SU>
                    <FTREF/>
                     by the intervention deadline for the project, which is 5:00 p.m. Eastern Time on July 21, 2026. As described further in Rule 214, your motion to intervene must state, to the extent known, your position regarding the proceeding, as well as your interest in the proceeding. For an individual, this could include your status as a landowner, ratepayer, resident of an impacted community, or recreationist. You do not need to have property directly impacted by the project in order to intervene. For more information about motions to intervene, refer to the 
                    <PRTPAGE P="41007"/>
                    FERC website at 
                    <E T="03">https://www.ferc.gov/resources/guides/how-to/intervene.asp.</E>
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         18 CFR 385.214.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         18 CFR 157.10.
                    </P>
                </FTNT>
                <P>There are two ways to submit your motion to intervene. In both instances, please reference the Project docket number CP26-543-000 in your submission.</P>
                <P>
                    (1) You may file your motion to intervene by using the Commission's eFiling feature, which is located on the Commission's website (
                    <E T="03">www.ferc.gov)</E>
                     under the link to Documents and Filings. 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; first select “General” and then select “Intervention.” The eFiling feature includes a document-less intervention option; for more information, visit 
                    <E T="03">https://www.ferc.gov/docs-filing/efiling/document-less-intervention.pdf.;</E>
                     or
                </P>
                <P>(2) You can file a paper copy of your motion to intervene, along with three copies, by mailing the documents to the address below. Your motion to intervene must reference the Project docket number CP26-543-000.</P>
                <P>To file via USPS: Debbie-Anne A. Reese, Secretary, Federal Energy Regulatory Commission, 888 First Street NE, Washington, DC 20426.</P>
                <P>To file via any other courier: Debbie-Anne A. Reese, Secretary, Federal Energy Regulatory Commission, 12225 Wilkins Avenue, Rockville, Maryland 20852.</P>
                <P>
                    The Commission encourages electronic filing of motions to intervene (option 1 above) and has eFiling staff available to assist you at (202) 502-8258 or 
                    <E T="03">FercOnlineSupport@ferc.gov.</E>
                </P>
                <P>
                    Protests and motions to intervene must be served on the applicant either by mail at: Estela D. Lozano, Regulatory Director, Southeast Supply Header, LLC, 915 N. Eldridge Parkway, Suite 1100, Houston, Texas 77079, or by email (with a link to the document) at 
                    <E T="03">estela.lozano@enbridge.com.</E>
                     Any subsequent submissions by an intervenor must be served on the applicant and all other parties to the proceeding. Contact information for parties can be downloaded from the service list at the eService link on FERC Online. Service can be via email with a link to the document.
                </P>
                <P>
                    All timely, unopposed 
                    <SU>9</SU>
                    <FTREF/>
                     motions to intervene are automatically granted by operation of Rule 214(c)(1).
                    <SU>10</SU>
                    <FTREF/>
                     Motions to intervene that are filed after the intervention deadline are untimely, and may be denied. Any late-filed motion to intervene must show good cause for being late and must explain why the time limitation should be waived and provide justification by reference to factors set forth in Rule 214(d) of the Commission's Rules and Regulations.
                    <SU>11</SU>
                    <FTREF/>
                     A person obtaining party status will be placed on the service list maintained by the Secretary of the Commission and will receive copies (paper or electronic) of all documents filed by the applicant and by all other parties.
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         The applicant has 15 days from the submittal of a motion to intervene to file a written objection to the intervention.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         18 CFR 385.214(c)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         18 CFR 385.214(b)(3) and (d).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Tracking the Proceeding</HD>
                <P>
                    Throughout the proceeding, additional information about the project will be available from OPP at (202) 502-6595 or on the FERC website at 
                    <E T="03">www.ferc.gov</E>
                     using the “eLibrary” link as described above. The eLibrary link also provides access to the texts of all formal documents issued by the Commission, such as orders, notices, and rulemakings.
                </P>
                <P>
                    In addition, the Commission offers a free service called eSubscription which allows you to keep track of all formal issuances and submittals in specific dockets. This can reduce the amount of time you spend researching proceedings by automatically providing you with notification of these filings, document summaries, and direct links to the documents. For more information and to register, go to 
                    <E T="03">www.ferc.gov/docs-filing/esubscription.asp.</E>
                </P>
                <P>
                    <E T="03">Intervention Deadline:</E>
                     5:00 p.m. Eastern Time on July 21, 2026.
                </P>
                <EXTRACT>
                    <FP>(Authority: 18 CFR 2.1.)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: June 30, 2026.</DATED>
                    <NAME>Debbie-Anne A. Reese,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13598 Filed 7-2-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>[Docket No. CP26-527-000]</DEPDOC>
                <SUBJECT>Columbia Gas Transmission, LLC; Notice of Scoping Period Requesting Comments on Environmental Issues for the Proposed Majorsville-Heard Storage Complex Abandonment Project</SUBJECT>
                <P>The staff of the Federal Energy Regulatory Commission (FERC or Commission) will prepare an environmental document that will discuss the environmental impacts of the Majorsville-Heard Storage Complex Abandonment Project (Project), involving abandonment of facilities by Columbia Gas Transmission, LLC (Columbia) in Marshall County, West Virginia and Greene and Washington Counties, Pennsylvania. The Commission will use this environmental document in its decision-making process to determine whether the project is in the public interest.</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 impacts 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 July 30, 2026. Comments may be submitted in written 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 impacts. Your input will help the Commission staff determine what issues they need to evaluate in the environmental document. Commission staff will consider all written 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 May 21, 2026 you will need to file those comments in Docket No. CP26-527-000 to ensure they are considered as part of this proceeding.</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 
                    <PRTPAGE P="41008"/>
                    proposed 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 proposed 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>
                    Columbia provided landowners with a fact sheet prepared by the FERC entitled “An Interstate Natural Gas Facility On My Land? What Do I Need To Know?” which 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 three 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 (CP26-527-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>
                    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 Proposed Project</HD>
                <P>Columbia proposes to abandon the Heard Storage Field, the Majorsville Shallow Storage Field, and the Majorsville Deep Storage Field, including all associated facilities and base gas, located in Marshall County, West Virginia and Greene and Washington Counties, Pennsylvania. Specifically, Columbia proposes to abandon 57 injection/withdrawal wells, 14 observation wells, the Majorsville Compressor Station, and all associated pipelines and aboveground appurtenances.</P>
                <P>Columbia proposes a phased approach to construction and would require up to ten years to complete all proposed activities. This phased approach would minimize operational risk, and ensure compliance with all applicable regulatory requirements while ensuring Columbia's system reliability. The Project would eliminate Columbia's need for continued operating and maintenance expenditures associated with facilities that are no longer required to meet Columbia's current firm service obligations.</P>
                <P>
                    The general location of the project facilities is shown in appendix 1.
                    <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>
                <HD SOURCE="HD1">Land Requirements for Construction</HD>
                <P>Columbia proposes utilizing approximately 199 acres of land during abandonment activities.</P>
                <HD SOURCE="HD1">NEPA Process and the Environmental Document</HD>
                <P>Any environmental document issued by the Commission will discuss impacts that could occur as a result of the construction and operation of the proposed 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;</P>
                <P>• air quality and noise; and</P>
                <P>• reliability and safety.</P>
                <P>Commission staff will also evaluate reasonable alternatives to the proposed project or portions of the project and make recommendations on how to lessen or avoid impacts 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>
                    Following this scoping period, Commission staff will 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 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 decision regarding 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, which will open up an additional comment period. Staff will then prepare a draft EIS which will be issued for public comment. Commission staff will 
                    <PRTPAGE P="41009"/>
                    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>2</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>2</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 of this project to formally cooperate in the preparation of the environmental document.
                    <SU>3</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>3</SU>
                         Cooperating agency responsibilities are addressed in Section 107(a)(3) of NEPA (42 U.S.C. 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>4</SU>
                    <FTREF/>
                     The environmental document for this project will document findings on the impacts on historic properties and summarize the status of consultations under section 106.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         The Advisory Council on Historic Preservation's 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 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 proposed 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 CP26-527-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>OR</P>
                <P>(2) Return the attached “Mailing List Update Form” (appendix 2).</P>
                <HD SOURCE="HD1">Additional Information</HD>
                <P>
                    Additional information about the project is available from the FERC website at 
                    <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 (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: June 30, 2026.</DATED>
                    <NAME>Debbie-Anne A. Reese,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13600 Filed 7-2-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. 7883-020]</DEPDOC>
                <SUBJECT>Powerhouse Systems, LLC; Notice of Intent To Prepare an Environmental Assessment</SUBJECT>
                <P>On October 2, 2023, Powerhouse Systems, LLC filed an application to relicense the 540-kilowatt Weston Dam Hydroelectric Project No. 7883. The project is located on the Upper Ammonoosuc River in Coos County, New Hampshire.</P>
                <P>
                    In accordance with the Commission's regulations, on April 6, 2026, Commission staff issued a notice that the project was ready for environmental analysis (REA notice). Based on the information in the record, including comments filed on the REA notice, staff does not anticipate that licensing the project would constitute a major federal action significantly affecting the quality of the human environment. Therefore, staff intends to prepare an environmental assessment (EA) on the application to relicense the Weston Dam Project.
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         For tracking purposes under the National Environmental Policy Act, the unique identification number for documents relating to this environmental review is EAXX-019-20-000-1780577933.
                    </P>
                </FTNT>
                <P>The EA will be issued and circulated for review by all interested parties. All comments filed on the EA will be analyzed by staff and considered in the Commission's final licensing decision.</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>
                <P>The application will be processed according to the following schedule. The EA will be issued for a 30-day comment period. Revisions to the schedule may be made as appropriate.</P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s50,r50">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Milestone</CHED>
                        <CHED H="1">Target date</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Commission issues EA</ENT>
                        <ENT>April 30, 2027.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    Any questions regarding this notice may be directed to Eric Fitzpatrick at (202) 502-8584 or 
                    <E T="03">eric.fitzpatrick@ferc.gov.</E>
                </P>
                <EXTRACT>
                    <FP>(Authority: 18 CFR 2.1.)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: June 30, 2026.</DATED>
                    <NAME>Debbie-Anne A. Reese,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13594 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="41010"/>
                <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 electric rate filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER10-2906-026; ER19-1716-014; ER24-2560-002; ER26-496-005; ER26-863-002; ER26-864-002; ER26-865-002; ER26-866-002; ER26-867-002; ER26-868-002; ER26-869-002; ER26-870-002; ER11-3460-013; ER12-1301-012.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Zone J Tolling Co., LLC, Bayonne Energy Center, LLC, Energy Prepay XX, LLC, Energy Prepay XIX, LLC, Energy Prepay XVIII, LLC, Energy Prepay XVII, LLC, Energy Prepay XVI, LLC, Energy Prepay XV, LLC, Energy Prepay XIV, LLC, Energy Prepay XII, LLC, Energy Prepay X, LLC, Energy Prepay I, LLC, Morgan Stanley Energy Structuring, L.L.C., Morgan Stanley Capital Group Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Triennial Market Power Analysis for Northeast Region of Morgan Stanley Capital Group Inc., et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/26/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260626-5262.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/25/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER15-1494-007; ER13-1793-020; ER12-1260-018; ER22-541-004; ER22-542-004; ER22-543-005; ER22-544-004; ER22-545-004; ER24-1980-004; ER24-1981-004; ER24-1983-004; ER25-1837-001; ER25-2676-001; ER25-2675-001; ER24-750-006; ER26-1467-001; ER26-1466-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Holyoke Energy Storage 1 LLC, Bensonhurst Energy Storage 1 LLC, Town Hill Energy Storage 1 LLC, West Boylston Energy Storage I LLC, OSCII Gildersleeve, LLC, OSCII Gun Hill LLC, West Warwick Energy Storage 3 LLC, West Warwick Energy Storage 2 LLC, West Warwick Energy Storage 1 LLC, NSF Chaumont Site 5 LLC, Bracewell LLP, NSF Chaumont Site 4 LLC, Bracewell LLP, NSF Chaumont Site 3 LLC, Bracewell LLP, NSF Chaumont Site 2 LLC, Bracewell LLP, NSF Chaumont Site 1 LLC, Bracewell LLP, Stephentown Spindle, LLC, Hazle Spindle, LLC, Convergent Energy and Power Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Triennial Market Power Analysis for Northeast Region of Convergent Energy and Power LP, et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/26/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260626-5285. 
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/25/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1409-010.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Birdsboro Power LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Compliance Filing Regarding Effective Date to be effective 4/25/2025.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5161.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1409-011.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Birdsboro Power LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Compliance Filing Regarding Effective Date to be effective 12/1/2025.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5162.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER25-279-004; ER17-991-013; ER13-823-010; ER24-2589-005; ER24-2590-005; ER17-2012-003; ER15-1348-005; ER22-1703-006.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Salem Harbor Power Development LP, Roseton Generating LLC, Rensselaer Generating LLC, Castleton Commodities Energy Trading LLC, Castleton Commodities Energy Services LLC, Castleton Commodities Merchant Trading L.P., Hunlock Energy, LLC, Hunlock Creek Generating LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Triennial Market Power Analysis for Northeast Region of Hunlock Creek Generating LLC, et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/25/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260625-5264.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/24/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-2023-001. 
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Midcontinent Independent System Operator, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: 2026-06-30_SA 4726 Deficiency Resp Ameren Missouri-Ameren Missouri GIA (E0017) to be effective 3/26/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5159.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-2133-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Ameren Illinois Company, Midcontinent Independent System Operator, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: Ameren Illinois Company submits tariff filing per 35.17(b): 2026-06-30_SA 3028 Ameren IL-Prairie Power Sub Orig Project #44 Incobrasa to be effective 6/13/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5154.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-2457-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     1803 Electric Cooperative, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Request to Recover Costs Associated with Acting as a Local Balancing Authority of 1803 Electric Cooperative, Inc.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/4/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260504-5383.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-2600-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Southwest Power Pool, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: 4618R1 Municipal Energy Agency of Nebraska NITSA and NOA Amended to be effective 5/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5118.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3031-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     PacifiCorp.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: UAMPS Engineering Services Agreement (RS No. 810) to be effective 8/30/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5119.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3032-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     New England Power Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: 2026-06-30 Amendments to Tariff 1—IFA Sch. III-B &amp; Request for Notice Waiver to be effective 3/19/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5123.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3033-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Southwest Power Pool, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: 1154R15 Associated Electric Cooperative NITSA and NOA to be effective 6/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5124.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3034-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Southwest Power Pool, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: 3055R5 Associated Electric Cooperative, Inc. NITSA NOA to be effective 6/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5137.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3035-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     New York Independent System Operator, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: LIPA Filing: ATRR for 2026 Rate Year and Proposed Revisions to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5141.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3036-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Bowfin KeyCon Energy, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Normal filing 2026 change in status to be effective 12/2/2025.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5165.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3037-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Bowfin KeyCon Power, LLC.
                    <PRTPAGE P="41011"/>
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Normal filing 2026 change in status to be effective 12/2/2025.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5167.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3038-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Bridgewater Power Company, L.P.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Normal filing 2026 change in status to be effective 12/2/2025.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5169.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3039-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Conemaugh Power LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Normal filing 2026 change in status to be effective 12/2/2025.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5174.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3040-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Keystone Power LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Normal filing 2026 change in status to be effective 12/2/2025.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5177.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3041-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Northampton Generating Company, L.P.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Normal filing 2026 change in status to be effective 12/2/2025.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5180.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3042-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Vermont Transco LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: 2026 Annual Exhibit A Informational Filing for 1991 Transmission Agreement to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5184.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3043-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Blue Sky West, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Request for Category 1 Seller Status in the NE Region and Revised MBR Tariff to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5185.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3044-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     EnergyMark, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Request for Category 1 Seller Status in the NE Region and Revised MBR Tariff to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5195.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3045-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Southwest Power Pool, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Revisions to Extend Tariff Administration between SPP and SPA through 12/31/2027 to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5198.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3046-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Evergreen Wind Power II, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Request for Category 1 Seller Status in the NE Region and Revised MBR Tariff to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5199.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3047-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     ISO New England Inc., New England Power Pool Participants Committee.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: ISO New England Inc. submits tariff filing per 35.13(a)(2)(iii: ISO-NE; Revisions to Change the Capacity Performance Rate to $3,500 per MWh to be effective 9/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5201.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3048-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Hancock Wind, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Request for Category 1 Seller Status in the NE Region and Revised MBR Tariff to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5203.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3049-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Marina Energy, LLC 
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Request for Category 1 Seller Status in the NE Region and Revised MBR Tariff to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5206.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3050-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     CP Energy Marketing (US) Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Notice of Change in Status to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5211.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/21/26.
                </P>
                <P>Take notice that the Commission received the following electric reliability filings</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RD26-8-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     North American Electric Reliability Corporation.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Petition of the North American Electric Reliability Corporation for Approval of Proposed Reliability Standard EOP-004-5 under RD26-8.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/26/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260626-5284.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/30/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: June 30, 2026.</DATED>
                    <NAME>Carlos D. Clay,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13564 Filed 7-2-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>[Docket No. CP26-545-000]</DEPDOC>
                <SUBJECT>Steel Reef Pipelines US LLC; Notice of Application and Establishing Intervention Deadline</SUBJECT>
                <P>
                    Take notice that on June 17, 2026, Steel Reef Pipelines US LLC (Steel Reef Pipelines), 8131 Highway 2, Stanley, North Dakota 58784, filed an application under section 3 of the Natural Gas Act (NGA) and Part 153 of the Commission's regulations requesting authorization for its Border Crossing Facilities Project (Project) which consists of a 0.65-mile-long 10-inch-diameter segment of the Flat Lake Access Pipeline gathering system to be 
                    <PRTPAGE P="41012"/>
                    constructed by Steel Reef Pipelines 
                    <SU>1</SU>
                    <FTREF/>
                     and a Presidential Permit for such facilities. The Flat Lake Access Pipeline is designed to export up to 80 million cubic feet per day (MMcf/d) of sour natural gas from an existing Compressor Station near Fortuna, North Dakota, to the Flat Lake Gas Plant in Saskatchewan, Canada, and to import approximately 6 MMcf/d of fuel gas to supply the Compressor Station (via a collocated 6-inch-diameter pipeline), all as more fully set forth in the application which is on file with the Commission and open for public inspection.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         The Flat Lake Access Pipeline will be an approximately 8-mile-long gathering system to be constructed by Steel Reef Pipelines to export unprocessed sour natural gas from an existing compressor station near Fortuna, North Dakota across the international border to the existing Flat Lake Gas Plant, located approximately 3 miles north of the international border in Saskatchewan, Canada. The 0.65-mile-long jurisdictional portion of the Flat Lake Access Pipeline run from milepost (MP) 0 at the Canada/United States border, to MP 0.65 in North Dakota.
                    </P>
                </FTNT>
                <P>
                    In addition to publishing the full text of this document in the 
                    <E T="04">Federal Register</E>
                    , the Commission provides all interested persons an opportunity to view and/or print the contents of this document via the internet through the Commission's Home Page (
                    <E T="03">http://www.ferc.gov</E>
                    ). From the Commission's Home Page on the internet, this information is available on eLibrary. The full text of this document is available on eLibrary in PDF and Microsoft Word format for viewing, printing, and/or downloading. To access this document in eLibrary, type the docket number excluding the last three digits of this document in the docket number field.
                </P>
                <P>
                    User assistance is available for eLibrary and the Commission's website during normal business hours from FERC Online Support at (202) 502-6652 (toll free at 1-866-208-3676) or email at 
                    <E T="03">ferconlinesupport@ferc.gov,</E>
                     or the Public Reference Room at (202) 502-8371, TTY (202) 502-8659. Email the Public Reference Room at 
                    <E T="03">public.referenceroom@ferc.gov.</E>
                </P>
                <P>
                    Any questions regarding the proposed project should be directed to Jodi Wilson, Vice President and General Counsel, 1600, 333 7th Avenue SW, Calgary, AB Canada T2P 2Z1, by phone at (403) 263-8333, or by email at 
                    <E T="03">jodi.wilson@steelreef.ca.</E>
                </P>
                <P>
                    Pursuant to section 157.9 of the Commission's Rules of Practice and Procedure,
                    <SU>2</SU>
                    <FTREF/>
                     within 90 days of this Notice the Commission staff will either: complete its environmental review and place it into the Commission's public record (eLibrary) for this proceeding; or issue a Notice of Schedule for Environmental Review. If a Notice of Schedule for Environmental Review is issued, it will indicate, among other milestones, the anticipated date for the Commission staff's issuance of the final environmental impact statement (FEIS) or environmental assessment (EA) for this proposal. The filing of an EA in the Commission's public record for this proceeding or the issuance of a Notice of Schedule for Environmental Review will serve to notify federal and state agencies of the timing for the completion of all necessary reviews, and the subsequent need to complete all federal authorizations within 90 days of the date of issuance of the Commission staff's FEIS or EA.
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         18 CFR 157.9.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Public Participation</HD>
                <P>There are three ways to become involved in the Commission's review of this project: you can file comments on the project, you can protest the filing, and you can file a motion to intervene in the proceeding. There is no fee or cost for filing comments or intervening. The deadline for filing a motion to intervene is 5:00 p.m. Eastern Time on July 21, 2026. How to file protests, motions to intervene, and comments is explained below.</P>
                <P>
                    For public inquiries and assistance with making filings such as interventions, comments, or requests for rehearing, contact the Office of Public Participation (OPP) at (202) 502-6595 or 
                    <E T="03">OPP@ferc.gov.</E>
                </P>
                <HD SOURCE="HD2">Comments</HD>
                <P>Any person wishing to comment on the project may do so. Comments may include statements of support or objections, to the project as a whole or specific aspects of the project. The more specific your comments, the more useful they will be.</P>
                <HD SOURCE="HD2">Protests</HD>
                <P>
                    Pursuant to sections 157.10(a)(4) 
                    <SU>3</SU>
                    <FTREF/>
                     and 385.211 
                    <SU>4</SU>
                    <FTREF/>
                     of the Commission's regulations under the NGA, any person 
                    <SU>5</SU>
                    <FTREF/>
                     may file a protest to the application. Protests must comply with the requirements specified in section 385.2001 
                    <SU>6</SU>
                    <FTREF/>
                     of the Commission's regulations. A protest may also serve as a motion to intervene so long as the protestor states it also seeks to be an intervenor.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         18 CFR 157.10(a)(4).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         18 CFR 385.211.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         Persons include individuals, organizations, businesses, municipalities, and other entities. 18 CFR 385.102(d).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         18 CFR 385.2001.
                    </P>
                </FTNT>
                <P>To ensure that your comments or protests are timely and properly recorded, please submit your comments on or before 5:00 p.m. Eastern Time on July 21, 2026.</P>
                <P>There are three methods you can use to submit your comments or protests to the Commission. In all instances, please reference the Project docket number CP26-545-000 in your submission.</P>
                <P>
                    (1) You may file your comments electronically by using the eComment feature, which is located on the Commission's website at 
                    <E T="03">www.ferc.gov</E>
                     under the link to Documents and Filings. Using eComment is an easy method for interested persons to submit brief, text-only comments on a project;
                </P>
                <P>
                    (2) You may file your comments or protests 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 Documents and Filings. 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; first select “General” and then select “Comment on a Filing”; or
                </P>
                <P>(3) You can file a paper copy of your comments or protests by mailing them to the following address below. Your written comments must reference the Project docket number (CP26-545-000).</P>
                <P>
                    <E T="03">To file via USPS:</E>
                     Debbie-Anne A. Reese, Secretary, Federal Energy Regulatory Commission, 888 First Street NE, Washington, DC 20426.
                </P>
                <P>
                    <E T="03">To file via any other courier:</E>
                     Debbie-Anne A. Reese, Secretary, Federal Energy Regulatory Commission, 12225 Wilkins Avenue, Rockville, Maryland 20852.
                </P>
                <P>
                    The Commission encourages electronic filing of comments (options 1 and 2 above) and has eFiling staff available to assist you at (202) 502-8258 or 
                    <E T="03">FercOnlineSupport@ferc.gov.</E>
                </P>
                <P>Persons who comment on the environmental review of this project will be placed on the Commission's environmental mailing list, and will receive notification when the environmental documents (EA or EIS) are issued for this project and will be notified of meetings associated with the Commission's environmental review process.</P>
                <P>
                    The Commission considers all comments received about the project in determining the appropriate action to be taken. However, the filing of a comment alone will not serve to make the filer a party to the proceeding. To become a party, you must intervene in the proceeding. For instructions on how to intervene, see below.
                    <PRTPAGE P="41013"/>
                </P>
                <HD SOURCE="HD2">Interventions</HD>
                <P>
                    Any person, which includes individuals, organizations, businesses, municipalities, and other entities,
                    <SU>7</SU>
                    <FTREF/>
                     has the option to file a motion to intervene in this proceeding. Only intervenors have the right to request rehearing of Commission orders issued in this proceeding and to subsequently challenge the Commission's orders in the U.S. Circuit Courts of Appeal.
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         18 CFR 385.102(d).
                    </P>
                </FTNT>
                <P>
                    To intervene, you must submit a motion to intervene to the Commission in accordance with Rule 214 of the Commission's Rules of Practice and Procedure 
                    <SU>8</SU>
                    <FTREF/>
                     and the regulations under the NGA 
                    <SU>9</SU>
                    <FTREF/>
                     by the intervention deadline for the project, which is 5:00 p.m. Eastern Time on July 21, 2026. As described further in Rule 214, your motion to intervene must state, to the extent known, your position regarding the proceeding, as well as your interest in the proceeding. For an individual, this could include your status as a landowner, ratepayer, resident of an impacted community, or recreationist. You do not need to have property directly impacted by the project in order to intervene. For more information about motions to intervene, refer to the FERC website at 
                    <E T="03">https://www.ferc.gov/resources/guides/how-to/intervene.asp.</E>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         18 CFR 385.214.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         18 CFR 157.10.
                    </P>
                </FTNT>
                <P>There are two ways to submit your motion to intervene. In both instances, please reference the Project docket number CP26-545-000 in your submission.</P>
                <P>
                    (1) You may file your motion to intervene by using the Commission's eFiling feature, which is located on the Commission's website (
                    <E T="03">www.ferc.gov</E>
                    ) under the link to Documents and Filings. 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; first select “General” and then select “Intervention.” The eFiling feature includes a document-less intervention option; for more information, visit 
                    <E T="03">https://www.ferc.gov/docs-filing/efiling/document-less-intervention.pdf.;</E>
                     or
                </P>
                <P>(2) You can file a paper copy of your motion to intervene, along with three copies, by mailing the documents to the address below. Your motion to intervene must reference the Project docket number CP26-545-000.</P>
                <P>
                    <E T="03">To file via USPS:</E>
                     Debbie-Anne A. Reese, Secretary, Federal Energy Regulatory Commission, 888 First Street NE, Washington, DC 20426.
                </P>
                <P>
                    <E T="03">To file via any other courier:</E>
                     Debbie-Anne A. Reese, Secretary, Federal Energy Regulatory Commission, 12225 Wilkins Avenue, Rockville, Maryland 20852.
                </P>
                <P>
                    The Commission encourages electronic filing of motions to intervene (option 1 above) and has eFiling staff available to assist you at (202) 502-8258 or 
                    <E T="03">FercOnlineSupport@ferc.gov.</E>
                </P>
                <P>
                    Protests and motions to intervene must be served on the applicant either by mail at: Jodi Wilson, Vice President and General Counsel, 1600, 333 7th Avenue SW, Calgary, AB Canada T2P 2Z1, or by email (with a link to the document) at 
                    <E T="03">jodi.wilson@steelreef.ca.</E>
                     Any subsequent submissions by an intervenor must be served on the applicant and all other parties to the proceeding. Contact information for parties can be downloaded from the service list at the eService link on FERC Online. Service can be via email with a link to the document.
                </P>
                <P>
                    All timely, unopposed 
                    <SU>10</SU>
                    <FTREF/>
                     motions to intervene are automatically granted by operation of Rule 214(c)(1).
                    <SU>11</SU>
                    <FTREF/>
                     Motions to intervene that are filed after the intervention deadline are untimely, and may be denied. Any late-filed motion to intervene must show good cause for being late and must explain why the time limitation should be waived and provide justification by reference to factors set forth in Rule 214(d) of the Commission's Rules and Regulations.
                    <SU>12</SU>
                    <FTREF/>
                     A person obtaining party status will be placed on the service list maintained by the Secretary of the Commission and will receive copies (paper or electronic) of all documents filed by the applicant and by all other parties.
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         The applicant has 15 days from the submittal of a motion to intervene to file a written objection to the intervention.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         18 CFR 385.214(c)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         18 CFR 385.214(b)(3) and (d).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Tracking the Proceeding</HD>
                <P>
                    Throughout the proceeding, additional information about the project will be available from OPP at (202) 502-6595 or on the FERC website at 
                    <E T="03">www.ferc.gov</E>
                     using the “eLibrary” link as described above. The eLibrary link also provides access to the texts of all formal documents issued by the Commission, such as orders, notices, and rulemakings.
                </P>
                <P>
                    In addition, the Commission offers a free service called eSubscription which allows you to keep track of all formal issuances and submittals in specific dockets. This can reduce the amount of time you spend researching proceedings by automatically providing you with notification of these filings, document summaries, and direct links to the documents. For more information and to register, go to 
                    <E T="03">www.ferc.gov/docs-filing/esubscription.asp.</E>
                </P>
                <P>
                    <E T="03">Intervention Deadline:</E>
                     5:00 p.m. Eastern Time on July 21, 2026.
                </P>
                <EXTRACT>
                    <FP>(Authority: 18 CFR 2.1)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: June 30, 2026.</DATED>
                    <NAME>Debbie-Anne A. Reese,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13597 Filed 7-2-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:</P>
                <HD SOURCE="HD1">Filings Instituting Proceedings</HD>
                <P>
                    <E T="03">Docket Numbers:</E>
                     PR26-65-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Gulf Coast Express Pipeline LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 284.123(g) Rate Filing: Revised Fuel Allocation Provisions to be effective 6/23/2025.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5097.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/20/26.
                </P>
                <P>
                    <E T="03">§ 284.123(g) Protest:</E>
                     5 p.m. ET 8/28/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     PR26-66-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Black Hills Wyoming Gas, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 284.123 Rate Filing: Black Hills Wyoming Gas LAUF Filing to be effective 6/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5026.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/20/26. 
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-939-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Eastern Gas Transmission and Storage, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: EGTS—2026 Section 4 General Rate Case to be effective 8/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5036.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/13/26. 
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-940-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Trailblazer Pipeline Company LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: TPC 2026-06-30 Negotiated Rate Agreement Amendments to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5047.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/13/26. 
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-940-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Trailblazer Pipeline Company LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: TPC 2026-06-30 Negotiated Rate Agreement Amendments to be effective 7/1/2026.
                    <PRTPAGE P="41014"/>
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5047.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/13/26. 
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-941-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Trunkline Gas Company, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: Amended Neg Rate Agreement—DCP South_3 to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5072.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/13/26. 
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-942-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Texas Eastern Transmission, LP.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: TETLP EPC AUG 2026 FILING to be effective 8/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5083.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/13/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-943-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Alliance Pipeline L.P.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: Negotiated Rates—Releases 07-01-2026 to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5091.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/13/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-944-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Equitrans, L.P.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: Negotiated Rate Agreement—7/1/2026 to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5105.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/13/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-945-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Southeast Supply Header, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: Negotiated Rates—July 2026 to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5108.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/13/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-946-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     RH energytrans, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Compliance study report to Docket No. CP18-6-000 to be effective N/A.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5122.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/13/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-947-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Tennessee Gas Pipeline Company, L.L.C.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: TGP MBR Informational Filing (GCX Expansion) to be effective N/A.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5127.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/13/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.  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: June 30, 2026.</DATED>
                    <NAME>Carlos D. Clay,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13565 Filed 7-2-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>[Docket No. RM98-1-000]</DEPDOC>
                <SUBJECT>Records Governing Off-the-Record Communications; Public Notice</SUBJECT>
                <P>This constitutes notice, in accordance with 18 CFR 385.2201(b), of the receipt of prohibited and exempt off-the-record communications.</P>
                <P>Order No. 607 (64 FR 51222, September 22, 1999) requires Commission decisional employees, who make or receive a prohibited or exempt off-the-record communication relevant to the merits of a contested proceeding, to deliver to the Secretary of the Commission, a copy of the communication, if written, or a summary of the substance of any oral communication.</P>
                <P>Prohibited communications are included in a public, non-decisional file associated with, but not a part of, the decisional record of the proceeding. Unless the Commission determines that the prohibited communication and any responses thereto should become a part of the decisional record, the prohibited off-the-record communication will not be considered by the Commission in reaching its decision. Parties to a proceeding may seek the opportunity to respond to any facts or contentions made in a prohibited off-the-record communication and may request that the Commission place the prohibited communication and responses thereto in the decisional record. The Commission will grant such a request only when it determines that fairness so requires. Any person identified below as having made a prohibited off-the-record communication shall serve the document on all parties listed on the official service list for the applicable proceeding in accordance with Rule 2010, 18 CFR 385.2010.</P>
                <P>Exempt off-the-record communications are included in the decisional record of the proceeding, unless the communication was with a cooperating agency as described by 40 CFR 1501.6, made under 18 CFR 385.2201(e) (1) (v).</P>
                <P>
                    The following is a list of off-the-record communications recently received by the Secretary of the Commission. Each filing may be viewed on the Commission's website at 
                    <E T="03">http://www.ferc.gov</E>
                     using the eLibrary link. Enter the docket number, excluding the last three digits, in the docket number field to access the document. 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.
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Letter communication dated 6/16/26 from the Maryland General Assembly Members.
                    </P>
                </FTNT>
                <GPOTABLE COLS="3" OPTS="L2,nj,tp0,i1" CDEF="s50,12,r50">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Docket nos.</CHED>
                        <CHED H="1">File date</CHED>
                        <CHED H="1">
                            Presenter
                            <LI>or requester</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="22">Prohibited:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">NONE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Exempt:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">1. EL26-63-000</ENT>
                        <ENT>06-17-2026</ENT>
                        <ENT>
                            FERC Staff.
                            <SU>1</SU>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">2. CP26-9-000</ENT>
                        <ENT>06-24-2026</ENT>
                        <ENT>U.S. Representative Dan Meuser.</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="41015"/>
                        <ENT I="03">3. EL26-79-000</ENT>
                        <ENT>06-25-2026</ENT>
                        <ENT>U. S. Senator Richard Blumenthal.</ENT>
                    </ROW>
                </GPOTABLE>
                <SIG>
                    <DATED>Dated: June 30, 2026.</DATED>
                    <NAME>Carlos D. Clay,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13566 Filed 7-2-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. 1894-238]</DEPDOC>
                <SUBJECT>Dominion Energy South Carolina, Inc.; Notice of Application for Amendment to Turbine Venting Plan and Article 401(B) In Part Accepted for Filing and Soliciting Comments, Motions To Intervene, and Protests</SUBJECT>
                <P>Take notice that the following hydroelectric application has been filed with the Commission and is available for public inspection:</P>
                <P>
                    a. 
                    <E T="03">Application Type:</E>
                     Amendment to Turbine Venting Period and Article 401(b) in part.
                </P>
                <P>
                    b. 
                    <E T="03">Project No.:</E>
                     1894-238.
                </P>
                <P>
                    c. 
                    <E T="03">Date Filed:</E>
                     June 4, 2026.
                </P>
                <P>
                    d. 
                    <E T="03">Applicant:</E>
                     Dominion Energy South Carolina, Inc. (licensee).
                </P>
                <P>
                    e. 
                    <E T="03">Name of Project:</E>
                     Parr Hydroelectric Project.
                </P>
                <P>
                    f. 
                    <E T="03">Location:</E>
                     The project is located on the Broad River in Newberry and Fairfield counties, South Carolina, and occupies federal lands within the Sumter National Forest, administered by the U.S. Department of Agriculture, Forest Service.
                </P>
                <P>
                    g. 
                    <E T="03">Filed Pursuant to:</E>
                     Federal Power Act, 16 U.S.C. 791(a)-825(r).
                </P>
                <P>
                    h. 
                    <E T="03">Applicant Contact:</E>
                     Ms. Amy Bresnahan, Dominion Energy South Carolina, Inc., 220 Operation Way, Mail Code B223, Cayce, South Carolina 29033; (803) 217-9965; 
                    <E T="03">amy.bresnahan@dominionenergy.com.</E>
                </P>
                <P>
                    i. 
                    <E T="03">FERC Contact:</E>
                     Joy Kurtz, (202) 502-6760, 
                    <E T="03">joy.kurtz@ferc.gov.</E>
                </P>
                <P>
                    j. 
                    <E T="03">Cooperating agencies:</E>
                     With this notice, the Commission is inviting federal, state, local, and Tribal agencies with jurisdiction and/or special expertise with respect to environmental issues affected by the proposal, that wish to cooperate in the preparation of any environmental document, if applicable, to follow the instructions for filing such requests described in item k below. Cooperating agencies should note the Commission's policy that agencies that cooperate in the preparation of any environmental document cannot also intervene. 
                    <E T="03">See</E>
                     94 FERC ¶ 61,076 (2001).
                </P>
                <P>k. Deadline for filing comments, motions to intervene, and protests is  July 30, 2026 5:00 p.m. Eastern Time.</P>
                <P>
                    The Commission strongly encourages electronic filing. Please file comments, motions to intervene, and protests using the Commission's eFiling system at 
                    <E T="03">http://www.ferc.gov/docs-filing/efiling.asp.</E>
                     Commenters can submit brief comments up to 6,000 characters, without prior registration, using the eComment system at 
                    <E T="03">http://www.ferc.gov/docs-filing/ecomment.asp.</E>
                     You must include your name and contact information at the end of your comments. For assistance, please contact FERC Online Support at 
                    <E T="03">FERCOnlineSupport@ferc.gov,</E>
                     (866) 208-3676 (toll free), or (202) 502-8659 (TTY). In lieu of electronic filing, you may submit a paper copy. Submissions sent via the U.S. Postal Service must be addressed to: 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. The first page of any filing should include docket number P-1894-238. Comments emailed to Commission staff are not considered part of the Commission record.
                </P>
                <P>The Commission's Rules of Practice and Procedure require all intervenors filing documents with the Commission to serve a copy of that document on each person whose name appears on the official service list for the project. Further, if an intervenor files comments or documents with the Commission relating to the merits of an issue that may affect the responsibilities of a particular resource agency, they must also serve a copy of the document on that resource agency.</P>
                <P>
                    l. 
                    <E T="03">Description of Request:</E>
                     The licensee requests Commission approval to amend the project's Turbine Venting Plan (Plan) such that the seasonal turbine venting window specified in the Plan, currently June 15 through August 31, be modified to June 15 through October 31. The intent of turbine venting under the Plan is to improve dissolved oxygen concentrations downstream of Parr Shoals Dam. In recent years, Commission staff have annually approved the licensee's requests to extend the venting through October 31 to prolong the benefits of venting at the request of South Carolina Department of Natural Resources and South Carolina Department of Health and Environmental Control. The licensee requests to permanently extend the venting window to avoid recurring annual temporary variance requests of the requirement.
                </P>
                <P>
                    Article 401(b) of the project license requires the licensee to obtain Commission approval for extensions of the current venting window that exceed 30 days (
                    <E T="03">i.e.,</E>
                     extensions beyond September 30). The licensee requests Article 401(b) be amended so that it is consistent with the turbine venting window described above in the amended Plan.
                </P>
                <P>
                    m. 
                    <E T="03">Locations of the Application:</E>
                     This filing may be viewed on the Commission's website at 
                    <E T="03">http://www.ferc.gov</E>
                     using the “eLibrary” link. Enter the docket number excluding the last three digits in the docket number field to access the document. You may also register online at 
                    <E T="03">http://www.ferc.gov/docs-filing/esubscription.asp</E>
                     to be notified via email of new filings and issuances related to this or other pending projects. For assistance, call 1-866-208-3676 or email 
                    <E T="03">FERCOnlineSupport@ferc.gov,</E>
                     for TTY, call (202) 502-8659. Agencies may obtain copies of the application directly from the applicant.
                </P>
                <P>n. Individuals desiring to be included on the Commission's mailing list should so indicate by writing to the Secretary of the Commission.</P>
                <P>
                    o. 
                    <E T="03">Comments, Protests, or Motions to Intervene:</E>
                     Anyone may submit comments, a protest, or a motion to intervene in accordance with the requirements of Rules of Practice and Procedure, 18 CFR 385.210, .211, .214. In determining the appropriate action to take, the Commission will consider all protests or other comments filed, but only those who file a motion to intervene in accordance with the Commission's Rules may become a party to the proceeding. Any comments, protests, or motions to intervene must be received on or before the specified comment date for the particular application.
                </P>
                <P>
                    p. 
                    <E T="03">Filing and Service of Responsive Documents:</E>
                     All filings must (1) bear in all capital letters the title 
                    <PRTPAGE P="41016"/>
                    “COMMENTS”, “PROTEST”, or “MOTION TO INTERVENE” as applicable; (2) set forth in the heading the name of the applicant and the project number of the application to which the filing responds; (3) furnish the name, address, and telephone number of the person protesting or intervening; and (4) otherwise comply with the requirements of 18 CFR 385.2001 through 385.2005. All comments, motions to intervene, or protests must set forth their evidentiary basis. A copy of all other filings in reference to this application must be accompanied by proof of service on all persons listed in the service list prepared by the Commission in this proceeding, in accordance with 385.2010.
                </P>
                <P>
                    q. 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>
                <EXTRACT>
                    <FP>(Authority: 18 CFR 2.1.)</FP>
                </EXTRACT>
                <SIG>
                    <DATED> Dated: June 30, 2026.</DATED>
                    <NAME>Debbie-Anne A. Reese,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13596 Filed 7-2-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>[Docket No. CP26-544-000]</DEPDOC>
                <SUBJECT>Vinton Dome Storage Hub, LLC; Notice of Application and Establishing Intervention Deadline</SUBJECT>
                <P>Take notice that on June 16, 2026, Vinton Dome Storage Hub, LLC (Vinton Dome), 2417 Shell Beach Drive, Lake Charles, Louisiana 70601, filed an application under section 7(c) of the Natural Gas Act (NGA) and Part 157 of the Commission's regulations requesting authorization for its Vinton Dome Project (Project). The Project consists of constructing, owning, operating, and maintaining a new natural gas storage facility with approximately 44.5 billion cubic feet of working gas capacity across five (5) new storage caverns, a new 55,000 horsepower compressor station, and related facilities including natural gas pipeline interconnections and laterals to multiple existing and planned interstate pipelines, all located in Calcasieu Parish, Louisiana.</P>
                <P>Vinton Dome also requests (1) a blanket certificate, pursuant to Part 157, Subpart F of the Commission's regulations, authorizing the construction of certain facilities; (2) a blanket certificate, pursuant to Part 284, Subpart G of the Commission's regulations, authorizing open access transportation; (3) authorization to charge market-based rates for its proposed services; (4) approval of Vinton Dome's pro forma FERC gas tariff, and (5) waivers of certain regulatory requirements. Vinton Dome asserts that the Project will provide necessary storage, parking, loaning and wheeling services to meet the increasing natural gas system balancing needs of power generators, local distribution companies, liquefied natural gas exporters, natural gas pipelines, natural gas producers, and residential, commercial, and industrial natural gas consumers, all as more fully set forth in the application which is on file with the Commission and open for public inspection.</P>
                <P>
                    In addition to publishing the full text of this document in the 
                    <E T="04">Federal Register</E>
                    , the Commission provides all interested persons an opportunity to view and/or print the contents of this document via the internet through the Commission's Home Page (
                    <E T="03">http://www.ferc.gov</E>
                    ). From the Commission's Home Page on the internet, this information is available on eLibrary. The full text of this document is available on eLibrary in PDF and Microsoft Word format for viewing, printing, and/or downloading. To access this document in eLibrary, type the docket number excluding the last three digits of this document in the docket number field.
                </P>
                <P>
                    User assistance is available for eLibrary and the Commission's website during normal business hours from FERC Online Support at (202) 502-6652 (toll free at 1-866-208-3676) or email at 
                    <E T="03">ferconlinesupport@ferc.gov,</E>
                     or the Public Reference Room at (202) 502-8371, TTY (202) 502-8659. Email the Public Reference Room at 
                    <E T="03">public.referenceroom@ferc.gov.</E>
                </P>
                <P>
                    Any questions regarding the proposed project should be directed to J. Gordon Pennington, Attorney at Law (Attorney for Vinton Dome Storage Hub, LLC), Georgetown Place, 1101 30th Street NW, Suite 500, Washington, DC 20007, by phone at (202) 365-5996, or by email at 
                    <E T="03">gordon@jgpennlaw.com.</E>
                </P>
                <P>
                    Pursuant to section 157.9 of the Commission's Rules of Practice and Procedure,
                    <SU>1</SU>
                    <FTREF/>
                     within 90 days of this Notice the Commission staff will either: complete its environmental review and place it into the Commission's public record (eLibrary) for this proceeding; or issue a Notice of Schedule for Environmental Review. If a Notice of Schedule for Environmental Review is issued, it will indicate, among other milestones, the anticipated date for the Commission staff's issuance of the final environmental impact statement (FEIS) or environmental assessment (EA) for this proposal. The filing of an EA in the Commission's public record for this proceeding or the issuance of a Notice of Schedule for Environmental Review will serve to notify federal and state agencies of the timing for the completion of all necessary reviews, and the subsequent need to complete all federal authorizations within 90 days of the date of issuance of the Commission staff's FEIS or EA.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         18 CFR 157.9.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Public Participation</HD>
                <P>There are three ways to become involved in the Commission's review of this project: you can file comments on the project, you can protest the filing, and you can file a motion to intervene in the proceeding. There is no fee or cost for filing comments or intervening. The deadline for filing a motion to intervene is 5:00 p.m. Eastern Time on July 21, 2026. How to file protests, motions to intervene, and comments is explained below.</P>
                <P>
                    For public inquiries and assistance with making filings such as interventions, comments, or requests for rehearing, contact the Office of Public Participation (OPP) at (202) 502-6595 or 
                    <E T="03">OPP@ferc.gov.</E>
                </P>
                <HD SOURCE="HD2">Comments</HD>
                <P>Any person wishing to comment on the project may do so. Comments may include statements of support or objections, to the project as a whole or specific aspects of the project. The more specific your comments, the more useful they will be.</P>
                <HD SOURCE="HD2">Protests</HD>
                <P>
                    Pursuant to sections 157.10(a)(4) 
                    <SU>2</SU>
                    <FTREF/>
                     and 385.211 
                    <SU>3</SU>
                    <FTREF/>
                     of the Commission's regulations under the NGA, any person 
                    <SU>4</SU>
                    <FTREF/>
                     may file a protest to the application. Protests must comply with the requirements specified in section 385.2001 
                    <SU>5</SU>
                    <FTREF/>
                     of the Commission's regulations. A protest may also serve as a motion to intervene so long as the protestor states it also seeks to be an intervenor.
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         18 CFR 157.10(a)(4).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         18 CFR 385.211.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         Persons include individuals, organizations, businesses, municipalities, and other entities. 18 CFR 385.102(d).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         18 CFR 385.2001.
                    </P>
                </FTNT>
                <P>
                    To ensure that your comments or protests are timely and properly recorded, please submit your comments 
                    <PRTPAGE P="41017"/>
                    on or before 5:00 p.m. Eastern Time on July 21, 2026.
                </P>
                <P>There are three methods you can use to submit your comments or protests to the Commission. In all instances, please reference the Project docket number CP26-544-000 in your submission.</P>
                <P>
                    (1) You may file your comments electronically by using the eComment feature, which is located on the Commission's website at 
                    <E T="03">www.ferc.gov</E>
                     under the link to Documents and Filings. Using eComment is an easy method for interested persons to submit brief, text-only comments on a project;
                </P>
                <P>
                    (2) You may file your comments or protests 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 Documents and Filings. 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; first select “General” and then select “Comment on a Filing”; or
                </P>
                <P>(3) You can file a paper copy of your comments or protests by mailing them to the following address below. Your written comments must reference the Project docket number (CP26-544-000).</P>
                <P>To file via USPS: Debbie-Anne A. Reese, Secretary, Federal Energy Regulatory Commission, 888 First Street NE, Washington, DC 20426.</P>
                <P>To file via any other courier: Debbie-Anne A. Reese, Secretary, Federal Energy Regulatory Commission, 12225 Wilkins Avenue Rockville, Maryland 20852.</P>
                <P>
                    The Commission encourages electronic filing of comments (options 1 and 2 above) and has eFiling staff available to assist you at (202) 502-8258 or 
                    <E T="03">FercOnlineSupport@ferc.gov.</E>
                </P>
                <P>Persons who comment on the environmental review of this project will be placed on the Commission's environmental mailing list, and will receive notification when the environmental documents (EA or EIS) are issued for this project and will be notified of meetings associated with the Commission's environmental review process.</P>
                <P>The Commission considers all comments received about the project in determining the appropriate action to be taken. However, the filing of a comment alone will not serve to make the filer a party to the proceeding. To become a party, you must intervene in the proceeding. For instructions on how to intervene, see below.</P>
                <HD SOURCE="HD2">Interventions</HD>
                <P>
                    Any person, which includes individuals, organizations, businesses, municipalities, and other entities,
                    <SU>6</SU>
                    <FTREF/>
                     has the option to file a motion to intervene in this proceeding. Only intervenors have the right to request rehearing of Commission orders issued in this proceeding and to subsequently challenge the Commission's orders in the U.S. Circuit Courts of Appeal.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         18 CFR 385.102(d).
                    </P>
                </FTNT>
                <P>
                    To intervene, you must submit a motion to intervene to the Commission in accordance with Rule 214 of the Commission's Rules of Practice and Procedure 
                    <SU>7</SU>
                    <FTREF/>
                     and the regulations under the NGA 
                    <SU>8</SU>
                    <FTREF/>
                     by the intervention deadline for the project, which is 5:00 p.m. Eastern Time on July 21, 2026. As described further in Rule 214, your motion to intervene must state, to the extent known, your position regarding the proceeding, as well as your interest in the proceeding. For an individual, this could include your status as a landowner, ratepayer, resident of an impacted community, or recreationist. You do not need to have property directly impacted by the project in order to intervene. For more information about motions to intervene, refer to the FERC website at 
                    <E T="03">https://www.ferc.gov/resources/guides/how-to/intervene.asp.</E>
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         18 CFR 385.214.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         18 CFR 157.10.
                    </P>
                </FTNT>
                <P>There are two ways to submit your motion to intervene. In both instances, please reference the Project docket number CP26-544-000 in your submission.</P>
                <P>
                    (1) You may file your motion to intervene by using the Commission's eFiling feature, which is located on the Commission's website (
                    <E T="03">www.ferc.gov)</E>
                     under the link to Documents and Filings. 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; first select “General” and then select “Intervention.” The eFiling feature includes a document-less intervention option; for more information, visit 
                    <E T="03">https://www.ferc.gov/docs-filing/efiling/document-less-intervention.pdf.;</E>
                     or
                </P>
                <P>(2) You can file a paper copy of your motion to intervene, along with three copies, by mailing the documents to the address below. Your motion to intervene must reference the Project docket number CP26-544-000.</P>
                <P>To file via USPS: Debbie-Anne A. Reese, Secretary, ,Federal Energy Regulatory Commission, 888 First Street NE, Washington, DC 20426, </P>
                <P>
                    <E T="03">To file via any other courier:</E>
                     Debbie-Anne A. Reese, Secretary, Federal Energy Regulatory Commission, 12225 Wilkins Avenue, Rockville, Maryland 20852.
                </P>
                <P>
                    The Commission encourages electronic filing of motions to intervene (option 1 above) and has eFiling staff available to assist you at (202) 502-8258 or 
                    <E T="03">FercOnlineSupport@ferc.gov.</E>
                </P>
                <P>
                    Protests and motions to intervene must be served on the applicant either by mail at: J. Gordon Pennington, Attorney at Law (Attorney for Vinton Dome Storage Hub, LLC), Georgetown Place, 1101 30th Street, NW, Suite 500, Washington, DC 20007 or by email (with a link to the document) at 
                    <E T="03">gordon@jgpennlaw.com.</E>
                     Any subsequent submissions by an intervenor must be served on the applicant and all other parties to the proceeding. Contact information for parties can be downloaded from the service list at the eService link on FERC Online. Service can be via email with a link to the document.
                </P>
                <P>
                    All timely, unopposed 
                    <SU>9</SU>
                    <FTREF/>
                     motions to intervene are automatically granted by operation of Rule 214(c)(1).
                    <SU>10</SU>
                    <FTREF/>
                     Motions to intervene that are filed after the intervention deadline are untimely, and may be denied. Any late-filed motion to intervene must show good cause for being late and must explain why the time limitation should be waived and provide justification by reference to factors set forth in Rule 214(d) of the Commission's Rules and Regulations.
                    <SU>11</SU>
                    <FTREF/>
                     A person obtaining party status will be placed on the service list maintained by the Secretary of the Commission and will receive copies (paper or electronic) of all documents filed by the applicant and by all other parties.
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         The applicant has 15 days from the submittal of a motion to intervene to file a written objection to the intervention.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         18 CFR 385.214(c)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         18 CFR 385.214(b)(3) and (d).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Tracking the Proceeding</HD>
                <P>
                    Throughout the proceeding, additional information about the project will be available from OPP at (202) 502-6595 or on the FERC website at 
                    <E T="03">www.ferc.gov</E>
                     using the “eLibrary” link as described above. The eLibrary link also provides access to the texts of all formal documents issued by the Commission, such as orders, notices, and rulemakings.
                </P>
                <P>
                    In addition, the Commission offers a free service called eSubscription which allows you to keep track of all formal issuances and submittals in specific dockets. This can reduce the amount of time you spend researching proceedings by automatically providing you with notification of these filings, document 
                    <PRTPAGE P="41018"/>
                    summaries, and direct links to the documents. For more information and to register, go to 
                    <E T="03">www.ferc.gov/docs-filing/esubscription.asp.</E>
                </P>
                <P>Intervention Deadline: 5:00 p.m. Eastern Time on July 21, 2026.</P>
                <EXTRACT>
                    <FP>(Authority: 18 CFR 2.1.)</FP>
                </EXTRACT>
                <SIG>
                    <DATED> Dated: June 30, 2026.</DATED>
                    <NAME>Debbie-Anne A. Reese,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13599 Filed 7-2-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-OPP-2026-0334; FRL-13199-04-OCSPP]</DEPDOC>
                <SUBJECT>Pesticide Product Registration; Receipt of Applications for New Uses (April 2026)</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of receipt and request for comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document announces the Agency's receipt of and solicits comments on applications to register new pesticide products containing currently registered active ingredients that would entail a change in use pattern. The Agency is providing this notice in accordance with the Federal Insecticide, Fungicide, and Rodenticide Act (FIFRA). EPA uses the month and year in the title to identify when the Agency compiled the applications identified in this notice of receipt. Unit II. of this document identifies certain applications received in 2025 and 2026 that are currently being evaluated by EPA, along with information about each application, including when it was received, who submitted the application, and the purpose of the application.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before August 5, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit your comments, identified by the docket identification (ID) number and the 
                        <E T="03">EPA File Symbol</E>
                         or the 
                        <E T="03">EPA Registration Number</E>
                         of interest as shown in Unit II. of this document, online at 
                        <E T="03">https://www.regulations.gov.</E>
                         Follow the online instructions for submitting comments. Do not submit electronically any information you consider to be Confidential Business Information (CBI) or other information whose disclosure is restricted by statute. Additional instructions on commenting on and visiting the docket, along with more information about dockets generally, are available at 
                        <E T="03">https://www.epa.gov/.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Each application summary in Unit II. specifies a contact division. The appropriate division contacts are identified as follows:</P>
                    <P>
                        • RD (Registration Division) (Mail Code 7505T); Charles Smith; main telephone number: (202) 566-1030; email address: 
                        <E T="03">RDFRNotices@epa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Executive Summary</HD>
                <HD SOURCE="HD2">A. Does this action apply to me?</HD>
                <P>This action provides information that is directed to the public in general.</P>
                <HD SOURCE="HD2">B. What is the Agency's authority for taking this action?</HD>
                <P>EPA is taking this action pursuant to section 3(c)(4) of the Federal Insecticide, Fungicide, and Rodenticide Act (FIFRA), 7 U.S.C. 136a(c)(4), and 40 CFR 152.102.</P>
                <HD SOURCE="HD2">C. What action is the Agency taking?</HD>
                <P>
                    EPA is hereby providing notice of receipt and opportunity to comment on applications to register new pesticide products containing currently registered active ingredients that would entail a change in use pattern. EPA provides a notice of receipt on a monthly basis, using the month and year in the title to help distinguish one document from the other. This document identifies the applications that were received since the last notice that was issued and are currently being evaluated by EPA in accordance with the Federal Insecticide, Fungicide, and Rodenticide Act (FIFRA). Notice of receipt of these applications does not imply a decision by the Agency on these applications. For actions being evaluated under EPA's public participation process for registration actions, there will be an additional opportunity for public comment on the proposed decisions. Please see EPA's public participation website for additional information on this process (
                    <E T="03">https://www.epa.gov/registration/participation-process-registration-actions</E>
                    ).
                </P>
                <HD SOURCE="HD2">D. What should I consider as I prepare my comments for EPA?</HD>
                <P>
                    1. 
                    <E T="03">Submitting CBI.</E>
                     Do not submit CBI to EPA through 
                    <E T="03">https://www.regulations.gov</E>
                     or email. If you wish to include CBI in your comment, please follow the applicable instructions at 
                    <E T="03">https://www.epa.gov/dockets/commenting-epa-dockets#rules</E>
                     and clearly mark the information that you claim to be CBI. In addition to one complete version of the comment that includes CBI, a copy of the comment without CBI must be submitted for inclusion in the public docket. Information marked as CBI will not be disclosed except in accordance with procedures set forth in 40 CFR part 2.
                </P>
                <P>
                    2. 
                    <E T="03">Tips for preparing your comments.</E>
                     When preparing and submitting your comments, see the commenting tips at 
                    <E T="03">https://www.epa.gov//epa-dockets.</E>
                </P>
                <HD SOURCE="HD1">II. Applications to Register New Uses</HD>
                <P>This unit provides the following information about each application received: The EPA File Symbol or Registration number(s); EPA docket ID number for the application; Name and address of the applicant; Name of the active ingredient, product type and proposed uses; and the division to contact for that application. Additional information about the application may also be available in the docket for the application as identified in this unit.</P>
                <P>
                    • 
                    <E T="03">EPA Registration Number:</E>
                     100-1721. 
                    <E T="03">Docket ID number:</E>
                     EPA-HQ-OPP-2026-1783. 
                    <E T="03">Applicant:</E>
                     Syngenta Crop Protection, LLC, P.O. Box 18300, Greensboro, NC 27419. 
                    <E T="03">Active ingredient:</E>
                     Cyclobutrifluram. 
                    <E T="03">Product type:</E>
                     Fungicide/nematocide. 
                    <E T="03">Proposed uses:</E>
                     Tuberous and corm vegetables (except ginseng) (CSG 1A), tuberous and corm (CSG 1C), tuberous and corm (CSG 1D), vegetable, leaves of root and tuber (CG2), bulb vegetables (CG 3-07), onion, bulb (CSG 3-07A), onion, green (CSG 3-07B), leafy vegetables (CG 4-16), brassica, head and stem (CG 5-16), legume vegetable (CG 6-22) (except soybean), edible podded peas and beans, succulent peas and beans, dried peas and beans, pea and bean, forage/vines, pea and bean, hay, fruiting vegetables (CG 8-10), cucurbit vegetables (CG 9), citrus fruit (CG 10-10), pome fruit (CG 11-10), stone fruit (CG 12-12), small fruit vine climbing (except fuzzy kiwifruit) (CSG 13-07F), low growing berry (CSG 13-7G) (except cranberry), tree nut (CG 14), almond hulls, grain, cereal (CG 15-22), grain, cereal, forage, hay, stover, and straw, group 16-22, forage, grain, cereal, forage, hay, stover, and straw, group 16-22, hay, grain, cereal, forage, hay, stover, and straw, group 16-22, stover, grain, cereal, forage, hay, stover, and straw, group 16-22, straw, cotton, undelinted seed (CSG 20C), cotton, gin byproducts, leaf petiole vegetable (CSG 22B), sugarcane, peanut, nutmeat, peanut, hay, cattle fat, cattle meat, cattle meat byproducts, eggs, goat fat, goat meat, goat meat byproducts, goat liver, goat kidney, hog fat, hog meat, hog meat byproducts, hog liver, hog kidney, horse fat, horse meat, horse meat byproducts, horse liver, horse kidney, milk, poultry 
                    <PRTPAGE P="41019"/>
                    fat, poultry meat, poultry meat byproducts, poultry liver, poultry kidney, sheep fat, sheep meat, sheep meat byproducts, sheep liver, sheep kidney, inadvertent tolerances for grass, forage, fodder and hay (CG 17) forage, grass, forage, fodder and hay (CG 17) hay, animal feed, non-grass (CG 18), forage; animal feed, non-grass (CG 18), hay and herb group (CG 25). 
                    <E T="03">Date of Receipt:</E>
                     March 24, 2026. 
                    <E T="03">Contact:</E>
                     RD.
                </P>
                <P>
                    • 
                    <E T="03">EPA Registration Number:</E>
                     264-533. 
                    <E T="03">Docket ID number:</E>
                     EPA-HQ-OPP-2025-2500. 
                    <E T="03">Applicant:</E>
                     Bayer CropScience LLC, 800 N. Lindbergh Blvd., St. Louis, MO 63167. 
                    <E T="03">Active ingredient:</E>
                     Bromoxynil. 
                    <E T="03">Product type:</E>
                     Herbicide. 
                    <E T="03">Proposed uses:</E>
                     Crop subgroup 20A (rapeseed, except flax, seed), crop subgroup 6-22E (vegetable, legume, pulse, bean, dried shelled, except soybean), and crop subgroup 6-22F (vegetable, legume, pulse, pea, dried shelled). 
                    <E T="03">Date of Receipt:</E>
                     June 27, 2025. 
                    <E T="03">Contact:</E>
                     RD.
                </P>
                <P>
                    • 
                    <E T="03">EPA Registration Number:</E>
                     74530-16. 
                    <E T="03">Docket ID number:</E>
                     EPA-HQ-OPP-2025-1905. 
                    <E T="03">Applicant:</E>
                     Interregional Research Project Number 4 (IR-4) Project Headquarters, NC State University, 1730 Varsity Drive, Venture IV, Suite 210, Raleigh, NC 27606. 
                    <E T="03">Active ingredient:</E>
                     Cycloate. 
                    <E T="03">Product type:</E>
                     Herbicide. 
                    <E T="03">Proposed use:</E>
                     Quinoa. 
                    <E T="03">Date of receipt:</E>
                     December 17, 2025. 
                    <E T="03">Contact:</E>
                     RD.
                </P>
                <P>
                    <E T="03">Authority:</E>
                     7 U.S.C. 136 
                    <E T="03">et seq.</E>
                </P>
                <SIG>
                    <DATED>Dated: June 29, 2026.</DATED>
                    <NAME>Edward Messina,</NAME>
                    <TITLE>Director, Office of Pesticide Programs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13552 Filed 7-2-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-OPP-2026-0333; FRL-13200-04-OCSPP]</DEPDOC>
                <SUBJECT>Pesticide Product Registration; Receipt of Applications for New Active Ingredients (April 2026)</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of receipt and request for comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document announces the Agency's receipt of and solicits comments on applications to register pesticide products containing active ingredients not included in any currently registered pesticide products. The Agency is providing this notice in accordance with the Federal Insecticide, Fungicide, and Rodenticide Act (FIFRA). EPA uses the month and year in the title to identify when the Agency compiled the applications identified in this notice of receipt. Unit II. of this document identifies certain applications received in 2025 that are currently being evaluated by EPA, along with information about each application, including when it was received, who submitted the application, and the purpose of the application.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before August 5, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit your comments, identified by the docket identification (ID) number and the 
                        <E T="03">EPA File Symbol</E>
                         or the 
                        <E T="03">EPA Registration Number</E>
                         of interest as shown in Unit II. of this document, online at 
                        <E T="03">https://www.regulations.gov.</E>
                         Follow the online instructions for submitting comments. Do not submit electronically any information you consider to be Confidential Business Information (CBI) or other information whose disclosure is restricted by statute. Additional instructions on commenting on and visiting the docket, along with more information about dockets generally, are available at 
                        <E T="03">https://www.epa.gov/dockets.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Each application summary in Unit II. specifies a contact division. The appropriate division contacts are identified as follows:</P>
                    <P>
                        • BPPD (Biopesticides and Pollution Prevention Division) (Mail Code 7511M); Alan Reynolds; main telephone number: (202) 566-1471; email address: 
                        <E T="03">BPPDFRNotices@epa.gov.</E>
                    </P>
                    <P>
                        • RD (Registration Division) (Mail Code 7505T); Charles Smith; main telephone number: (202) 566-1030; email address: 
                        <E T="03">RDFRNotices@epa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Executive Summary</HD>
                <HD SOURCE="HD2">A. Does this action apply to me?</HD>
                <P>This action provides information that is directed to the public in general.</P>
                <HD SOURCE="HD2">B. What is the Agency's authority for taking this action?</HD>
                <P>EPA is taking this action pursuant to section 3(c)(4) of the Federal Insecticide, Fungicide, and Rodenticide Act (FIFRA), 7 U.S.C. 136a(c)(4), and 40 CFR 152.102.</P>
                <HD SOURCE="HD2">C. What action is the Agency taking?</HD>
                <P>
                    EPA is hereby providing notice of receipt and opportunity to comment on applications to register pesticide products containing active ingredients not included in any currently registered pesticide products. Notice of receipt of these applications does not imply a decision by the Agency on these applications. The applications identified in this document were received since the last notice that was issued and are currently being evaluated by EPA in accordance with the Federal Insecticide, Fungicide, and Rodenticide Act (FIFRA). For actions being evaluated under EPA's public participation process for registration actions, there will be an additional opportunity for public comment on the proposed decisions. Please see EPA's public participation website for additional information on this process (
                    <E T="03">https://www.epa.gov/registration/participation-process-registration-actions</E>
                    ).
                </P>
                <HD SOURCE="HD2">D. What should I consider as I prepare my comments for EPA?</HD>
                <P>
                    1. 
                    <E T="03">Submitting CBI.</E>
                     Do not submit CBI to EPA through 
                    <E T="03">https://www.regulations.gov</E>
                     or email. If you wish to include CBI in your comment, please follow the applicable instructions at 
                    <E T="03">https://www.epa.gov/dockets/commenting-epa-dockets#rules</E>
                     and clearly mark the information that you claim to be CBI. In addition to one complete version of the comment that includes CBI, a copy of the comment without CBI must be submitted for inclusion in the public docket. Information marked as CBI will not be disclosed except in accordance with procedures set forth in 40 CFR part 2.
                </P>
                <P>
                    2. 
                    <E T="03">Tips for preparing your comments.</E>
                     When preparing and submitting your comments, see the commenting tips at 
                    <E T="03">https://www.epa.gov/dockets/commenting-epa-dockets.</E>
                </P>
                <HD SOURCE="HD1">II. Registration Applications Received</HD>
                <P>This unit provides the following information about the applications received: The EPA File Symbol or Registration number(s); EPA docket ID number for the application; Name and address of the applicant; Name of the active ingredient, product type and proposed uses; and the division to contact for that application. Additional information about the application may also be available in the docket for the application as identified in this unit.</P>
                <P>
                    • 
                    <E T="03">File Symbol:</E>
                     29964-GI. 
                    <E T="03">Docket ID Number:</E>
                     EPA-HQ-OPP-2026-1255. 
                    <E T="03">Applicant:</E>
                     PIONEER HI-BRED INTERNATIONAL, INC. 7300 NW 62nd Avenue Johnston, IA 50131. 
                    <E T="03">Product Name:</E>
                     COR121 Maize. 
                    <E T="03">Active Ingredient:</E>
                     Insecticide—Adiantum trapeziform var. braziliense IPD083Cb Protein and the genetic material (PHP98529 T-DNA) necessary for its production. 
                    <E T="03">Proposed Use:</E>
                     Plant Incorporated Protectant. 
                    <E T="03">Date of Receipt:</E>
                     December 22, 2025. 
                    <E T="03">Contact:</E>
                     BPPD.
                </P>
                <P>
                    • 
                    <E T="03">File Symbols:</E>
                     33906-GR; 33906-GN. 
                    <E T="03">Docket ID Number:</E>
                     EPA-HQ-OPP-
                    <PRTPAGE P="41020"/>
                    2026-1784. 
                    <E T="03">Applicant:</E>
                     Nissan Chemical Corporation, 5-1, Nihonbashi 2-Chome, Chuo-ku, Tokyo 103-6119, Japan. 
                    <E T="03">Product Names:</E>
                     Iptriazopyrid Technical; Iptriazopyrid 100 g/L SC. 
                    <E T="03">Active Ingredient:</E>
                     Herbicide—Iptriazopyrid at 98.5%; 9.1%. 
                    <E T="03">Proposed Use:</E>
                     Rice. 
                    <E T="03">Date of Receipt:</E>
                     November 26, 2025. 
                    <E T="03">Contact:</E>
                     RD.
                </P>
                <P>
                    <E T="03">Authority:</E>
                     7 U.S.C. 136 
                    <E T="03">et seq.</E>
                </P>
                <SIG>
                    <DATED>Dated: June 29, 2026.</DATED>
                    <NAME>Edward Messina,</NAME>
                    <TITLE>Director, Office of Pesticide Programs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13553 Filed 7-2-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-2509; FRL-13318-01-OW]</DEPDOC>
                <SUBJECT>Draft Guidance for Reducing Risk From Perfluorooctanoic Acid (PFOA) and Perfluorooctane Sulfonic Acid (PFOS) in Biosolids; Establishment of a Public Docket; Request for Feedback</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability of draft guidance and request for comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The U.S. Environmental Protection Agency (EPA) is making available a draft memorandum that would, if finalized, provide guidance to operators of wastewater treatment plants (WWTPs) and related facilities, landowners and farmers, State and Tribal water agencies, and the public on ways to reduce potential risks posed by perfluorooctanoic acid (PFOA) and perfluorooctane sulfonic acid (PFOS) in biosolids, as well as seeking feedback on potential next steps. The EPA is soliciting public comments on the draft memorandum and next steps for 60 days. This draft guidance memorandum does not have the force and effect of law, nor does it bind the public in any way. This draft guidance memorandum cannot be relied on by any person in litigation against the United States. The intent of draft guidance memorandum is to provide non-binding or voluntary recommendations for how to mitigate risks from PFOA and PFOS in sewage sludge and biosolids based on information currently available to the EPA.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before September 4, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may send comments, identified by Docket ID No. EPA-HQ-OW-2026-2509, by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal erulemaking Portal: https://www.regulations.gov/</E>
                         (our preferred method). Follow the online instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         U.S. Environmental Protection Agency, EPA Docket Center, Office of Water Docket, Mail Code 28221T, 1200 Pennsylvania Avenue NW, Washington, DC 20460.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions received must include the Docket ID No. for this rulemaking. Comments received may be posted without change to 
                        <E T="03">https://www.regulations.gov/,</E>
                         including any personal information provided. For detailed instructions on sending comments and additional information on the rulemaking process, see the “Public Participation” heading of the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section of this document.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Tess Richman, Engineering and Science Division, Office of Water (4504-T), Environmental Protection Agency, 1200 Pennsylvania Avenue NW, Washington, DC 20460; email address: 
                        <E T="03">biosolidsprogram@epa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>The U.S. Environmental Protection Agency (EPA) understands that certain landowners, utilities, and members of the public have questions or concerns about how to safely use or dispose of biosolids or sewage sludge that may be contaminated with perfluorooctanoic acid (PFOA) and perfluorooctane sulfonic acid (PFOS). In this document, the EPA is providing draft guidance to operators of wastewater treatment plants (WWTPs) and related facilities, landowners and farmers, State and Tribal water agencies, and the public. It is designed to provide non-binding, voluntary recommendations for potential ways to mitigate risks from, and seek feedback on EPA's next steps for managing, PFOA and PFOS in biosolids and sewage sludge.</P>
                <P>When domestic sewage is received by WWTP, it is treated to separate liquids from the solids, which produces a semi-solid, nutrient-rich product known as sewage sludge. In some instances, WWTPs receive wastewater from industrial facilities and commercial enterprises, not just domestic sewage from homes, and this wastewater is combined with domestic sewage during treatment. The terms “biosolids” and “sewage sludge” are often used interchangeably by the public; however, the EPA typically uses the term “biosolids” to mean sewage sludge that is intended to be land applied as a soil amendment or fertilizer and that has been treated by a WWTP to meet the requirements in the EPA's Clean Water Act (CWA) regulation entitled, “Standards for the Use or Disposal of Sewage Sludge,” found at 40 CFR part 503 (Part 503). The Part 503 regulations govern minimum requirements for sewage sludge quality, management practices, and monitoring and reporting applicable to the generation of sewage sludge from a treatment works treating domestic sewage and to the use or disposal of that sewage sludge by any person.</P>
                <P>
                    In the United States, there are generally three options for use or disposal of sewage sludge. Based on available data, (1) approximately 60 percent of the nation's sewage sludge is land applied as a soil conditioner or fertilizer (roughly 32 percent is applied to agricultural land and 28 percent is applied to other lands, such as reclamation sites, home lawns and gardens, and golf courses); (2) approximately 25 percent is disposed of in a sewage sludge monofill or municipal solid waste (MSW) landfill, and (3) approximately 14 percent is incinerated.
                    <SU>1</SU>
                    <FTREF/>
                     Land application is the spraying, spreading, incorporation, or injection of sewage sludge into or onto the land to either condition the soil or fertilize crops or vegetation grown in the soil. Under existing Federal regulations, biosolids can be applied to agricultural lands, forests, tree farms, golf courses, turf farms, and other types of land. Biosolids can also be bagged and sold at stores to the public, generally to be used on lawns or in home gardens. Biosolids generally are not used on specialty crops, such as fresh produce, and generally are used on crops where edible parts are not in contact with the soil. Some states, Tribes, or counties also have additional rules around the use of sewage sludge and biosolids.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         An additional 1 percent of sewage sludge is disposed of using other management practices (
                        <E T="03">e.g.,</E>
                         deep-well injection, use as an auxiliary fuel).
                    </P>
                </FTNT>
                <P>
                    The EPA has endorsed and encouraged the land application of biosolids for decades. The continued practice of using biosolids for fertilizer is critical for both WWTPs seeking to manage sewage sludge in a manner that has environmental benefits, and farmers who rely on the biosolids for fertilizer. While the EPA estimates that biosolids are applied to less than 1% of America's farmland annually, the agency recognizes that nearly 60% of sewage sludge is land applied as biosolids. Land application is therefore a crucial and cost-effective management option for our nation's utilities, especially in locations where landfill and incinerator 
                    <PRTPAGE P="41021"/>
                    capacity is limited. To be clear, only biosolids, which are treated prior to use, can be land-applied on farm fields under specific circumstances. Untreated sewage sludge may not be land applied under existing Federal regulations.
                </P>
                <P>Per- and polyfluoroalkyl substances (PFAS) are a category of chemicals that can cause serious health problems if you are exposed to them over a long period of time, or at certain critical life stages like pregnancy and early childhood. PFOA and PFOS are two chemicals in the larger class of PFAS. PFOA and PFOS persist in the environment for long periods of time and have been linked to a variety of significant adverse human health effects. Domestic production and import of PFOA has been phased out in the United States by the companies participating in the 2010/2015 PFOA Stewardship Program. However, quantities of PFOA may be produced, imported, and used by companies not participating in the PFOA Stewardship Program and some uses of PFOS may be ongoing.</P>
                <P>
                    Statewide surveys have found that PFOA and PFOS have been detected at varying levels in sewage sludge even at WWTPs that do not receive wastewater from industrial users of the chemicals (
                    <E T="03">i.e.,</E>
                     they only receive wastewater from residential and commercial users). Traditional wastewater treatment technology does not remove nor destroy PFOA or PFOS, and these chemicals typically accumulate in the sewage sludge. It is important to note that not all sewage sludge has been found to have detectable or elevated levels of PFOA or PFOS.
                </P>
                <P>
                    In 2019, as part of the PFAS Action Plan, the Trump EPA announced the beginning stages of a risk assessment to evaluate potential harm to humans and the environment posed by sewage sludge contaminated with PFOA and PFOS. On January 14, 2025, the Biden EPA released a draft risk assessment (Draft Risk Assessment) aimed at understanding potential risks (
                    <E T="03">i.e.,</E>
                     the chance of harmful effects to humans) posed by PFOA and PFOS in sewage sludge. The current administration extended the comment period twice to allow interested parties additional time to thoroughly review and analyze the Draft Risk Assessment and provide feedback.
                </P>
                <P>After careful review of the comments provided by stakeholders, the EPA has determined that the Draft Risk Assessment exhibited a number of flaws as discussed below that have caused confusion among the public and the regulated community. This confusion has resulted in a lack of clarity in how the public could apply the preliminary findings of the Draft Risk Assessment in their daily lives, or put another way, in how to determine what the findings of the Draft Risk Assessment might mean for them.</P>
                <P>First, the EPA departed from typical agency practice by failing to conduct a national survey to document occurrence nationally, which is helpful to determine how much of a chemical, in this case PFOA and PFOS, may actually be present in biosolids and therefore the range of potential risks they pose. Second, the Draft Risk Assessment only evaluated sewage sludge management practices with higher potential for human health risk in hypothetical scenarios that do not reflect the majority of land application in the U.S. In these higher-risk hypothetical scenarios, the Draft Risk Assessment found that PFOA and PFOS in sewage sludge may contaminate soil, livestock, food crops, fish, and drinking water. However, the agency did not estimate how often these higher-risk scenarios occur in the U.S. Nor did the agency assess risks to the public, as the public often has a diversity of sources for their food and do not live on or near an impacted property.</P>
                <P>
                    Finally, the preliminary findings of the Draft Risk Assessment suggested that sometimes risks of adverse health effects were possible when using or disposing of sewage sludge containing 1 part per billion (ppb) of PFOA or PFOS. This concentration was only used as a starting concentration to determine 
                    <E T="03">if</E>
                     use or disposal would result in 
                    <E T="03">any</E>
                     unacceptable risk for the hypothetical circumstances presented.The use of 1 ppb was not intended to be interpreted as a “safe level” of PFOA or PFOS in sewage sludge in all circumstances.
                </P>
                <P>
                    Based on the hypothetical biosolids and sewage sludge use and disposal scenarios modeled and presented in the Draft Risk Assessment, a misconception has arisen that 
                    <E T="03">all</E>
                     biosolids and sewage sludge use and disposal practices will negatively affect the public. This stems from the agency's focus on higher-risk scenarios, the lack of discussion about risks to the public, and the use of 1 ppb as the modeled concentration. This draft guidance aims to provide clarity to stakeholders about the more common potential risks from PFOA and PFOS and identify some potential practices that can be taken to reduce PFOA and PFOS exposures.
                </P>
                <P>The agency is providing this draft guidance for operators of WWTPs and related facilities, landowners and farmers, State and Tribal water agencies, and the public. It provides non-binding, voluntary recommendations for potential ways to mitigate risks from PFOA and PFOS involving the use and disposal of sewage sludge. The EPA is soliciting public comment on this draft guidance for 60 days. The EPA also may use public comments filed to help inform any future agency actions.</P>
                <HD SOURCE="HD1">II. Stakeholder Feedback Opportunities</HD>
                <P>To assist the EPA in better understanding potential risks from PFOA and PFOS in biosolids and sewage sludge and help inform next steps, the agency welcomes feedback on specific questions regarding its Draft Guidance Memorandum “Draft Guidance for Reducing Risk from Perfluorooctanoic Acid (PFOA) and Perfluorooctane Sulfonic Acid (PFOS) in Biosolids” that can be provided by submitting comments through the docket. This feedback will help inform any final guidance on this topic and potential future administrative actions. However, the agency does not anticipate providing specific written responses to individual submissions.</P>
                <P>• Are the recommendations for farmers and bulk land appliers of biosolids sufficient to provide clarity? What other information should the agency consider?</P>
                <P>• Are the recommendations related to surface disposal and incineration of sewage sludge sufficient to provide clarity to stakeholders? What other information should the agency consider?</P>
                <P>• Are the recommendations related to the protection of public health and pollution prevention sufficient to provide clarity to states, Tribes, and utilities about how to reduce concentrations of PFOA and PFOS in sewage sludge and biosolids? What other information should the agency consider?</P>
                <P>• Several states have taken an approach to reducing PFAS concentrations in sewage sludge that is not risk-based but instead focuses on achieving practical reductions of PFOA and PFOS by addressing discharges from industrial facilities through the implementation of source identification and targeted source reduction. The EPA is seeking feedback and data demonstrating whether and how these approaches can reduce concentrations of PFOA and PFOS in biosolids and sewage sludge, and feedback and data on the effectiveness of these reductions in mitigating risks to public health.</P>
                <P>
                    • The EPA is seeking feedback on practices not included in the draft guidance that can reduce risk when land applying biosolids. Please provide any conditions, controls, monitoring, best management practices, or permitting practices and any examples of 
                    <PRTPAGE P="41022"/>
                    implementation from State, Tribal, or local programs.
                </P>
                <P>• The EPA is seeking feedback on practices not included in the draft guidance that can reduce risk when surface disposing or incinerating sewage sludge contaminated with PFOA and PFOS. Please provide any conditions, controls, monitoring, best management practices, or permitting practices and any examples of implementation from State, Tribal, or local programs that the EPA should consider.</P>
                <P>• What next steps should the EPA take regarding the Draft Risk Assessment, and how would this help provide clarity about potential risks from use and disposal of biosolids and sewage sludge? Should the agency also reevaluate the underlying framework for the Draft Risk Assessment, and if so, how? What specific data or other information is available that may help inform the agency's potential next steps on the Draft Risk Assessment and other potential future actions related to PFAS in biosolids and sewage sludge?</P>
                <P>
                    • Given that risks can depend on land use decisions (
                    <E T="03">e.g.,</E>
                     risks are different for growing textile crops than produce), should the EPA evaluate policy options that would consider current and future land use practices (
                    <E T="03">e.g.,</E>
                     different land use or planted crops after a change in ownership)? What strategies should the EPA consider for protecting public health, future land uses, landowners, and property values?
                </P>
                <HD SOURCE="HD1">III. Public Participation</HD>
                <HD SOURCE="HD2">A. How do I access a copy of this guidance?</HD>
                <P>
                    You may access this document electronically at 
                    <E T="03">https://www.epa.gov/biosolids</E>
                     or at 
                    <E T="03">https://www.federalregister.gov.</E>
                     The EPA has established an official public docket for receiving comments under Docket ID No. EPA-HQ-OW-2026-2509 which is accessible electronically at 
                    <E T="03">http://www.regulations.gov</E>
                     that will also contain copies of this 
                    <E T="04">Federal Register</E>
                     publication. The public docket does not include CBI or other information whose disclosure is restricted by statute.
                </P>
                <HD SOURCE="HD2">B. How do I submit a comment?</HD>
                <P>
                    Submit your comments, identified by Docket ID No. EPA-HQ-OW-2026-2509, at 
                    <E T="03">https://www.regulations.gov</E>
                     (our preferred method), or the other methods identified in the 
                    <E T="02">ADDRESSES</E>
                     section. Once submitted, comments cannot be edited or removed from the docket. The EPA may publish any comment received to its public docket. Do not submit to EPA's docket at 
                    <E T="03">https://www.regulations.gov</E>
                     any information you consider to be Confidential Business Information (CBI), Proprietary Business Information (PBI), 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). Please visit 
                    <E T="03">https://www.epa.gov/dockets/commenting-epa-dockets</E>
                     for additional submission methods; the full EPA public comment policy; information about CBI, PBI, or multimedia submissions; and general guidance on making effective comments.
                </P>
                <EXTRACT>
                    <FP>(Authority: CWA section 405(g)(1), 33 U.S.C. 1345(g)(1)).)</FP>
                </EXTRACT>
                <SIG>
                    <NAME>Andrew D. Sawyers,</NAME>
                    <TITLE>Director, Office of Wastewater Management, Office of Water.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13615 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">EQUAL EMPLOYMENT OPPORTUNITY COMMISSION</AGENCY>
                <SUBJECT>Sunshine Act Meetings</SUBJECT>
                <PREAMHD>
                    <HD SOURCE="HED">FEDERAL REGISTER CITATION OF PREVIOUS ANNOUNCEMENT:</HD>
                    <P>91 FR 38710.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">PREVIOUSLY ANNOUNCED TIME AND DATE OF THE MEETING:</HD>
                    <P>Wednesday, July 1, 2026, 10:00 a.m. Eastern Time.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">CHANGES IN THE MEETING:</HD>
                    <P>
                        This notice announces that the meeting was cancelled. On June 26, 2026, the EEOC published a notice in the 
                        <E T="04">Federal Register</E>
                        , 91 FR 38710, announcing an open meeting of the Commission to consider the following matters: (1) EEOC Strategic Plan for Fiscal Years 2026-2030; and (2) Rescission of Guidelines on Affirmative Action Appropriate Under Title VII of the Civil Rights Act of 1964, as Amended; and (3) Rescission of Compliance Manual Section 607—Affirmative Action. The meeting was to be held on July 1, 2026, at EEOC Headquarters, Jacqueline A. Berrien Training Center, 131 M Street NE, Washington, DC 20507. The matters to be considered were decided by the Commissioners by notation vote pursuant to Commission voting procedures. Thus, the meeting became unnecessary.
                    </P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">CONTACT PERSON FOR MORE INFORMATION:</HD>
                    <P>Raymond Windmiller, Executive Officer, (202) 921-2705.</P>
                    <P>This action is taken pursuant to the Government in the Sunshine Act, 5 U.S.C. 552b.</P>
                </PREAMHD>
                <SIG>
                    <DATED>Dated: July 1, 2026.</DATED>
                    <P>For the Equal Employment Opportunity Commission.</P>
                    <NAME>Raymond D. Windmiller,</NAME>
                    <TITLE>Executive Officer, Office of the Executive Secretariat.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13584 Filed 7-2-26; 4:15 pm]</FRDOC>
            <BILCOD>BILLING CODE 6570-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                <DEPDOC>[OMB 3060-0716; FR ID 353279]</DEPDOC>
                <SUBJECT>Information Collection Being Reviewed by the Federal Communications Commission Under Delegated Authority</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>As part of its continuing effort to reduce paperwork burdens, and as required by the Paperwork Reduction Act of 1995 (PRA), the Federal Communications Commission (FCC or Commission) invites the general public and other Federal agencies to take this opportunity to comment on the following information collections. Comments are requested concerning: whether the proposed collection of information is necessary for the proper performance of the functions of the Commission, including whether the information shall have practical utility; the accuracy of the Commission's burden estimate; ways to enhance the quality, utility, and clarity of the information collected; ways to minimize the burden of the collection of information on the respondents, including the use of automated collection techniques or other forms of information technology; and ways to further reduce the information collection burden on small business concerns with fewer than 25 employees. The FCC may not conduct or sponsor a collection of information unless it displays a currently valid Office of Management and Budget (OMB) control number. No person shall be subject to any penalty for failing to comply with a collection of information subject to the PRA that does not display a valid OMB control number.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Written comments should be submitted on or before September 4, 2026. If you anticipate that you will be submitting comments, but find it difficult to do so within the period of time allowed by this notice, you should 
                        <PRTPAGE P="41023"/>
                        advise the contacts below as soon as possible.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Direct all PRA comments to Cathy Williams, FCC, via email: 
                        <E T="03">PRA@fcc.gov</E>
                         and to 
                        <E T="03">Cathy.Williams@fcc.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>For additional information about the information collection, contact Cathy Williams at (202) 418-2918.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    <E T="03">OMB Control Number:</E>
                     3060-0716.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Sections 73.88, 73.718, 73.685, Blanketing Interference.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     N/A.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of a currently approved collection.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit entities; and Not-for-profit institutions.
                </P>
                <P>
                    <E T="03">Number of Respondents and Responses:</E>
                     200 respondents and 200 responses.
                </P>
                <P>
                    <E T="03">Estimated Time per Response:</E>
                     2 hours.
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     Third party disclosure requirement.
                </P>
                <P>
                    <E T="03">Total Annual Burden:</E>
                     400 hours.
                </P>
                <P>
                    <E T="03">Total Annual Cost:</E>
                     No cost.
                </P>
                <P>
                    <E T="03">Obligation To Respond:</E>
                     Required to obtain or retain benefits. The statutory authority for this collection of information is contained in section 154(i) of the Communications Act of 1934, as amended.
                </P>
                <P>
                    <E T="03">Needs and Uses:</E>
                     The information collection requirements approved under this collection are contained under the following rule sections:
                </P>
                <P>47 CFR 73.88 states that the licensee of each broadcast station is required to satisfy all reasonable complaints of blanketing interference within the 1V/m contour.</P>
                <P>47 CFR 73.318(b) states that after January 1, 1985, permittees or licensees who either (1) commence program tests, (2) replace the antennas, or (3) request facilities modifications and are issued a new construction permit must satisfy all complaints of blanketing interference which are received by the station during a one-year period.</P>
                <P>47 CFR 73.318(c) states that a permittee collocating with one or more existing stations and beginning program tests on or after January 1, 1985, must assume full financial responsibility for remedying new complaints of blanketing interference for a period of one year.</P>
                <P>Under 47 CFR 73.88, and 73.685(d), the license is financially responsible for resolving complaints of interference within one year of program test authority when certain conditions are met. After the first year, a license is only required to provide technical assistance to determine the cause of interference.</P>
                <SIG>
                    <P>Federal Communications Commission.</P>
                    <NAME>Marlene Dortch, </NAME>
                    <TITLE>Secretary, Office of the Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13593 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                <DEPDOC>[PSHSB &amp; OET: PS Docket No. 26-72; DA 26-635; FR ID 354261]</DEPDOC>
                <SUBJECT>Prohibiting Importation and Marketing of Previously Authorized Covered Communications Equipment Added to the Covered List in 2024 or Earlier</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In this document, the Public Safety and Homeland Security Bureau (PSHSB) and the Office of Engineering and Technology (OET) prohibit the continued importation and marketing of certain previously authorized equipment that has been determined to pose an unacceptable risk to the national security of the United States or the security and safety of United States persons. Through Public Notice, acting pursuant to § 2.939 of the Federal Communications Commission's rules, PSHSB and OET apply such prohibitions to communications equipment added to the Covered List in 2024 or earlier.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        As described in the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section below, this prohibition takes effect July 16, 2026.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Chris Smeenk, Attorney Advisor, at 202-418-1630 or 
                        <E T="03">Chris.Smeenk@fcc.gov,</E>
                         or Rebecca Clinton, Deputy Chief, Legal, at 202-418-7815 or 
                        <E T="03">Rebecca.Clinton@fcc.gov,</E>
                         Operations and Emergency Management Division, Public Safety and Homeland Security Bureau.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    This is a summary of the Public Notice released on June 26, 2026 in PS Docket No. 26-72, DA 26-635. The full text of this document is available at: 
                    <E T="03">https://www.fcc.gov/document/fcc-prohibits-importation-and-marketing-certain-covered-equipment</E>
                    .
                </P>
                <P>
                    In November 2022, the Commission adopted rules to prohibit authorization of equipment identified on the Covered List. However, the Commission did not revoke previously granted authorizations of covered equipment. In October 2025, the Commission adopted the 
                    <E T="03">EA Security Second R&amp;O</E>
                     (90 FR 53227) which, among other things, established a procedure to limit the scope of an existing authorization of covered equipment to prohibit continued importation or marketing of such equipment, without revoking the underlying authorization. The Commission noted that its goal was to mitigate potential national security risks associated with covered equipment in the nation's supply chain that was authorized prior to a Covered List addition under 47 U.S.C. 1601(b). The Commission directed PSHSB and OET to “institute proceedings to determine whether to apply these prohibitions to some or all of the equipment currently on the Covered List” and it delegated authority to PSHSB and OET to apply such prohibitions pursuant to the framework and process outlined in the 
                    <E T="03">EA Security Second R&amp;O.</E>
                </P>
                <P>The Commission specifically directed PSHSB and OET to conduct a public interest analysis pursuant to that framework, giving “particular weight to the fact that the relevant equipment was determined to pose `an unacceptable risk to the national security of the United States or the safety and security of United States persons'.”</P>
                <P>On March 27, 2026, PSHSB and OET released a Public Notice (March 27 Public Notice) (91 FR 17275) seeking comment on whether the Commission should prohibit the continued importation and marketing of certain previously authorized covered equipment and the relevant factors, including national security and economic and supply chain considerations, that would justify such a prohibition.</P>
                <P>
                    Based on the record, we prohibit the continued importation and marketing of any covered equipment added to the Covered List in 2024 or earlier. This prohibition specifically applies to all such covered equipment that received FCC equipment authorization before the adoption of our 2022 rules and takes effect 10 days after publication of this Notice in the 
                    <E T="04">Federal Register</E>
                    . As explained further below, however, the prohibition is temporarily suspended for certain equipment added to the Covered List on March 12, 2021, when used for the purpose of physical security surveillance of critical infrastructure, until the Commission adopts a definition of “critical infrastructure.” And, for the avoidance of doubt, the prohibition does not apply to any equipment added to the Covered List after 2024.
                </P>
                <P>
                    <E T="03">National security impacts.</E>
                     Protecting national security remains one of the Commission's primary objectives, and the focus of our analysis in this proceeding. Moreover, as the 
                    <PRTPAGE P="41024"/>
                    Commission stated in the 
                    <E T="03">EA Security Second R&amp;O,</E>
                     “no governmental interest is more compelling than the security of the Nation.” Consistent with our tentative conclusions in the March 27 Public Notice, we find that prohibiting the continued importation and marketing of previously authorized equipment added to the Covered List in 2024 or earlier is necessary to mitigate national security risks to the U.S. communications sector. In determining whether to adopt such a prohibition, the Commission directed that PSHSB and OET “must give particular weight” to the national security determinations made concerning the targeted equipment. The 2021 additions to the Covered List were pursuant to a specific national security determination made by Congress, which the Commission previously found constituted a specific determination that such equipment poses an “unacceptable risk to the national security of the United States or the security and safety of United States persons.” Separately, the 2024 addition of “equipment with integrated Kaspersky Lab, Inc. (or any of its successors and assignees) cybersecurity or anti-virus software” was based on a specific determination by the Department of Commerce that “Kaspersky's provision of cybersecurity and anti-virus software to U.S. persons, including through third-party entities that integrate Kaspersky cybersecurity or anti-virus software into commercial hardware or software, poses undue and unacceptable risks to U.S. national security and to the security and safety of U.S. persons.” We agree with CTIA that our action will “help to mitigate clear national security risks . . . because all of the entities captured in the proposed restrictions have been found by Congress or national security agencies to be subject to the control, direction, or influence of foreign adversary countries.”
                </P>
                <P>After review of the record filed in response to the March 27 Public Notice, we reaffirm the Commission's previous finding that older models of covered equipment—many of which remain widely available in the United States—continue to pose an unacceptable risk to national security when imported or marketed in the United States, not only when newly introduced to the market. We agree with the Foundation for Defense of Democracies (FDD) that equipment added to the Covered List in 2024 or earlier “is often functionally identical to these firms' more recently banned products” that have been deemed to pose an unacceptable national security risk. We agree as well with FDD that authorized equipment produced by the entities subject to our prohibition “may still be sold in the United States despite the firms” that produce or provide such equipment “continuing to engage in troubling patterns of behavior,” including cyberespionage. As FDD states, “[a]llowing them to sell and market previously authorized equipment to the American market will perpetuate vulnerabilities in U.S. telecommunications infrastructure.” FDD argues that we “must act to prevent adversaries from exploiting regulatory loopholes to maintain access to U.S. critical infrastructure.” Accordingly, we conclude that prohibiting the continued importation and marketing of previously authorized equipment added in 2024 or earlier serves the public interest and is necessary to protect national security by mitigating risks to the U.S. communications sector. No commenter disputed the national security concerns associated with such equipment.</P>
                <P>After careful consideration of the record, we also find that arguments concerning economic and supply chain harms do not overcome the preexisting national security determinations and the national security risks posed by the continued importation and marketing of previously authorized covered equipment subject to this action. We disagree with commenters who argue that the Commission should refrain from extending the prohibition to previously authorized covered equipment because doing so may impose economic costs. We recognize that some parties may face added compliance obligations and lost sales revenue, but those concerns do not override the Commission's responsibility to protect national security. The commenters opposing expansion of the prohibition largely focus on the financial impacts, especially on particular entities. However, these commenters do not meaningfully address the broader consequences of continuing to import and market devices that have been determined to pose “unacceptable risks” or provide data for us to consider on those issues, as we invited in the March 27 Public Notice.</P>
                <P>As CTIA notes, “the universe of equipment targeted by the [March 27 Public Notice] . . . is produced by a handful of entities,” and “[i]n the period since this equipment was added to the Covered List, experience has demonstrated the availability of alternatives.” Moreover, devices added to the Covered List as part of the Kaspersky listing in 2024 are already prohibited from importation or marketing under Department of Commerce's rules and equipment added to the Covered List in the initial 2021 listing has not received authorization since November 11, 2022, over three years ago. Thus, we conclude that the national security considerations outweigh the economic and supply chain concerns that commenters raised in the record.</P>
                <P>
                    <E T="03">Scope of prohibition for certain equipment.</E>
                     Some of the equipment on the Covered List that was added in 2024 or earlier is “covered” for all uses and purposes. However, as we noted in the March 27 Public Notice, certain equipment added to the Covered List on March 12, 2021, is only on the Covered List when used for specific purposes—namely, “for the purpose of public safety, security of government facilities, physical security surveillance of critical infrastructure, and other national security purposes.” Under the approach the Commission adopted in the 
                    <E T="03">EA Security R&amp;O</E>
                     (88 FR 7592), new equipment authorization applications for covered equipment produced by entities subject to use-based restrictions (
                    <E T="03">i.e.,</E>
                     equipment that is covered when “used for the purpose of public safety, security of government facilities, physical security surveillance of critical infrastructure, and other national security purposes”) are generally prohibited until those manufacturers have submitted, and received Commission approval for, compliance plans. The Commission has yet to approve any such compliance plans, because the Commission's definition of critical infrastructure was the subject of litigation.
                </P>
                <P>
                    Given this backdrop, for any equipment that is “covered” when used for certain purposes, the prohibitions on continued importation and marketing that we adopt in this Notice will not apply to importation and marketing for non-“covered” uses. Therefore, the importation and marketing prohibitions will apply 
                    <E T="03">only</E>
                     to equipment “used for the purpose of public safety, security of government facilities, physical security surveillance of critical infrastructure, and other national security purposes.” We find that, as urged by two commenters, permitting the importation or marketing of such already-authorized equipment is consistent with the Covered List, the Secure and Trusted Communications Networks Act of 2019, and the Secure Equipment Act of 2021 (Secure Equipment Act). Furthermore, because the Commission currently lacks a definition of, and guidance for interpreting the statutory term “critical infrastructure,” we suspend the prohibition on the importation or 
                    <PRTPAGE P="41025"/>
                    marketing of such equipment for the purpose of physical security surveillance of critical infrastructure until the Commission adopts such definition and guidance. On the effective date of any Commission Order adopting a definition of “critical infrastructure,” importation and marketing will be prohibited for the purpose of “security surveillance of critical infrastructure.” Therefore, the importation and marketing of already-authorized equipment subject only to a use-based Covered List entry will only be prohibited if imported or marketed for the purpose of the following, as interpreted in the 
                    <E T="03">EA Security 2d R&amp;O</E>
                    :
                </P>
                <P>• Public safety;</P>
                <P>• Government facilities;</P>
                <P>• (Suspended, pending finalized definition of, and guidance for interpreting, “critical infrastructure”) physical surveillance of critical infrastructure; and</P>
                <P>• “Other national security purposes.”</P>
                <P>
                    Finally, if at any point there is a new specific determination that removes the use-based limits on a Covered List entry, we retain the authority to issue another Public Notice expanding this prohibition to include the importation and marketing of that covered equipment for 
                    <E T="03">all</E>
                     purposes.
                </P>
                <P>
                    <E T="03">Legal Authority.</E>
                     Without reopening the issue of the Commission's legal authority, we nonetheless note our continued disagreement with Hikvision's arguments that we lack the statutory authority to impose prohibitions on the continued importation and marketing of already-authorized covered equipment. The Commission has previously made clear and explained at length that it has multiple sources of legal authority to limit existing authorizations of equipment that would no longer be eligible to receive authorizations today due to unacceptable national security risks.
                </P>
                <P>We also reject Hikvision's argument that the March 27 Public Notice fails to provide specific notice of affected authorizations under § 2.939 of the Commission's rules. The March 27 Public Notice sufficiently identifies the devices targeted for potential limitation with specific reference to covered equipment that was added to the Covered List in 2024 or earlier. The Covered List clearly reflects the specific equipment that was added to the Covered List, and the date such equipment was added.</P>
                <P>
                    Finally, Hytera-US, Inc. (Hytera-US) and Hytera Communications Corporation Limited (HCC) contend that their land mobile radio and digital mobile radio equipment is not “video surveillance and telecommunications equipment,” and therefore, in their view, is not covered equipment. As such, they argue that before taking any further action, the Commission must clarify that any restrictions on importing and marketing do not apply to equipment that is not covered equipment. In addition, Hytera-US argues the Commission must lift its hold on Hytera-US's applications for equipment authorizations. HCC similarly argues that the Commission should proceed with a different procedural mechanism than the framework adopted by the Commission in the 
                    <E T="03">EA Security 2d R&amp;O,</E>
                     so that authorization holders have the ability to contest whether their equipment is subject to the Covered List prohibitions. These arguments do not address the proposals in the March 27 Public Notice, and therefore, we reject these arguments as unresponsive.
                </P>
                <P>
                    <E T="03">Existing authorizations.</E>
                     As the Commission has stated, the prohibition on continued importation and marketing does not affect the continued use or operation of previously authorized covered equipment; consumers may continue to use any device or equipment that they currently possess, if the equipment was legally purchased and maintains an existing equipment authorization. Commenters support this approach and no commenter opposed this approach, which is consistent with the 
                    <E T="03">EA Security 2d R&amp;O.</E>
                     We also note that the importation and marketing prohibitions do not apply to marketing activities that are excepted under statute and the Commission's rules or for importation under the conditions listed in § 2.1204(a)(3)-(11) of the Commission's rules.
                </P>
                <P>
                    <E T="03">Implementation timeline.</E>
                     The prohibition on importation and marketing will take effect 10 days after publication in the 
                    <E T="04">Federal Register</E>
                    . As of that date, entities will be prohibited from importing or marketing any covered equipment added to the Covered List in 2024 or earlier. While this approach differs from our proposal in the March 27 Public Notice, which would have required entities to cease all importation and marketing activities within 30 days of the release of this Public Notice, we believe that 10 days following 
                    <E T="04">Federal Register</E>
                     publication will create more notice to the public and federal partners. The need for expedited action is especially acute, because a delayed, but looming, prohibition would encourage importers and marketers to flood the U.S. market with covered equipment—a prospect that this proceeding is premised on preventing.
                </P>
                <P>We agree with CTIA that “several factors significantly mitigate any potential supply chain or economic impacts” that may occur as a result of this action, “including previous efforts under the Commission's `Rip and Replace' program and the long period of time since any equipment produced by the relevant entities has been eligible to be authorized.” As CTIA notes, several alternatives have been brought to market since this equipment was added to the Covered List and “participants in the ICT ecosystem can effectively serve the U.S. market without this equipment in their networks or these producers in their supply chains.”</P>
                <P>We disagree with commenters like NCTA and USTelecom who contend (without specific data to support their arguments) that we should adopt longer and more flexible transition periods to account for supply chain considerations, in-transit equipment, existing inventory, and contractual obligations and reject calls for a “phased implementation.” We also disagree with HCC's suggestion that we should broadly exempt from the prohibition “equipment that is used for spare parts, updates and replacements” for existing devices or otherwise “provide a process for reimbursement . . . to allow users to replace the affected equipment.” Allowing imports and marketing replacements for existing covered equipment would defeat the entire purpose of this prohibition. As we concluded above, the national security risks of allowing covered equipment to continue to be imported and marketed in the United States far outweigh the potential economic impacts and supply chain disruptions that may occur as a result of this prohibition, and the national security demand for urgent action to avoid flooding the market outweighs any disruption.</P>
                <P>
                    <E T="03">Authority:</E>
                     47 U.S.C. 1601-1609.
                </P>
                <SIG>
                    <FP>Federal Communications Commission.</FP>
                    <NAME>Zenji Nakazawa,</NAME>
                    <TITLE>Chief, Public Safety and Homeland Security Bureau.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13518 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                <DEPDOC>[OMB 3060-0716; FR ID 353280]</DEPDOC>
                <SUBJECT>Information Collection Being Reviewed by the Federal Communications Commission</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; request for comments.</P>
                </ACT>
                <SUM>
                    <PRTPAGE P="41026"/>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>As part of its continuing effort to reduce paperwork burdens, and as required by the Paperwork Reduction Act of 1995 (PRA), the Federal Communications Commission (FCC or Commission) invites the general public and other Federal agencies to take this opportunity to comment on the following information collections. Comments are requested concerning: whether the proposed collection of information is necessary for the proper performance of the functions of the Commission, including whether the information shall have practical utility; the accuracy of the Commission's burden estimate; ways to enhance the quality, utility, and clarity of the information collected; ways to minimize the burden of the collection of information on the respondents, including the use of automated collection techniques or other forms of information technology; and ways to further reduce the information collection burden on small business concerns with fewer than 25 employees.</P>
                    <P>The FCC may not conduct or sponsor a collection of information unless it displays a currently valid Office of Management and Budget (OMB) control number. No person shall be subject to any penalty for failing to comply with a collection of information subject to the PRA that does not display a valid OMB control number.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be submitted on or before September 4, 2026. If you anticipate that you will be submitting comments, but find it difficult to do so within the period of time allowed by this notice, you should advise the contacts below as soon as possible.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Direct all PRA comments to Cathy Williams, FCC, via email: 
                        <E T="03">PRA@fcc.gov</E>
                         and to 
                        <E T="03">Cathy.Williams@fcc.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>For additional information about the information collection, contact Cathy Williams at (202) 418-2918.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    <E T="03">OMB Control Number:</E>
                     3060-0214.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Sections 73.3526 and 73.3527, Local Public Inspection Files; Sections 73.1212, 76.1701 and 73.1943, Political Files.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     N/A.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of a currently approved collection.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for profit entities; Not for profit institutions; State, Local or Tribal government; Individuals or households.
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     24,178 respondents; 67,440 responses.
                </P>
                <P>
                    <E T="03">Estimated Time per Response:</E>
                     1-52 hours.
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion reporting requirement, Recordkeeping requirement, Third party disclosure requirement.
                </P>
                <P>
                    <E T="03">Obligation to Respond:</E>
                     Required to obtain or retain benefits. Statutory authority for these collections is contained in Sections 151, 152, 154(i), 303, 307, 308, and 315 of the Communications Act of 1934, as amended.
                </P>
                <P>
                    <E T="03">Total Annual Burden:</E>
                     2,093,127 hours.
                </P>
                <P>
                    <E T="03">Total Annual Cost:</E>
                     No cost.
                </P>
                <P>
                    <E T="03">Needs and Uses:</E>
                     Commission rules require broadcast licensees and cable television operators to maintain political files and public inspection files and to include specified records. These rules, which are contained in 47 CFR 73.1212, 73.3526, 73.3527, 73.1943, and 76.1701, remain unchanged since last approved by OMB.
                </P>
                <P>47 CFR 73.1943(a) and 76.1701(a) require each broadcast station licensee and each cable television system to maintain in its online political file a complete record of any request to purchase broadcast and cablecast time that is made by or on behalf of a candidate for public office, or that communicates a message relating to any political matter of national importance, including a legally qualified candidate, any election to Federal office, or a national legislative issue of public importance.</P>
                <P>47 CFR 73.1943(b) and 76.1701(b) specify the records that each broadcast station licensee and each cable television system must maintain in its online political file:</P>
                <P>(1) whether the request to purchase broadcast or cablecast time is accepted or rejected by the broadcast licensee or cable television system operator;</P>
                <P>(2) the rate charged for the broadcast or cablecast time;</P>
                <P>(3) the date and time on which the communication is aired;</P>
                <P>(4) the class of time that is purchased;</P>
                <P>(5) the name of the candidate to which the communication refers and the office to which the candidate is seeking election, the election to which the communication refers, or the issue to which the communication refers (as applicable);</P>
                <P>(6) in the case of a request made by, or on behalf of, a candidate, the name of the candidate, the authorized committee of the candidate, and the treasurer of such committee; and</P>
                <P>(7) in the case of any other request, the name of the person purchasing the time, the name, address, and phone number of a contact person for such person, and a list of the chief executive officers or members of the executive committee or of the board of directors of such person.</P>
                <P>47 CFR 73.3526(a) and 73.3527(a) require that licensees and permittees of commercial and noncommercial educational broadcast stations maintain a public inspection file. The contents of the file vary according to type of service and status. A separate file shall be maintained for each station for which an application is pending or for which an authorization is outstanding. The public inspection file must be maintained so long as an authorization to operate the station is outstanding.</P>
                <P>47 CFR 73.3526(b) and 73.3527(b) specify the location at which the public inspection file must be maintained. An applicant for a new station or change of community shall maintain its file at an accessible place in the proposed community of license or at its proposed main studio. Commercial and noncommercial television and radio stations are required to place their records in an online public file hosted by the Commission, with the exception of letters and emails from the public, which may be maintained at the station. Stations must also provide a link to the online file from the home page of their own websites, if they have one, and provide contact information for a station representative on their websites who can assist persons with disabilities with issues related to the content of the public files. Stations are also required to include in the online public file the station's main studio address and telephone number and the email address of the station's designated contact for questions about the public file. With respect to the station's political file, new material must be placed in the online file hosted by the Commission, but political material that existed prior to the effective date of the online political file requirements may continue to be retained at the station until the end of the applicable retention period.</P>
                <P>
                    47 CFR 73.3526(c) and 73.3527(c) require the licensee/permittee to make the local public file available for public inspection at any time during regular business hours. All or part of this file may be maintained in a computer database as long as a computer terminal is made available to members of the public. Materials in the public file must be made available for review, printing, or reproduction upon request. Licensees that maintain their main studios and public file outside their communities of license are required to mail a copy of “The Public and Broadcasting” to anyone requesting a copy. Licensees shall be prepared to assist members of the public in identifying the documents 
                    <PRTPAGE P="41027"/>
                    they may want to be sent to them by mail. An applicant, permittee, or licensee must provide information regarding the location of the public file, or the applicable portion of the file, within one business day of a request for such information.
                </P>
                <P>47 CFR 73.3526(d) and 73.3527(d) require an assignor to maintain the public inspection file until such time as the assignment is consummated. At that time, the assignee is required to maintain the file.</P>
                <P>47 CFR 73.3526(e) and 73.3527(e) specify the contents of the public inspection files. Separate rule sections not subject to this information collection require the creation and submission to the Commission of many of the items that must be retained in the public inspection file. As such, the burden estimates for creation and submission of these documents are calculated in other information collections. The burden estimates included in this information collection pertain only to making these items publicly available. The documents to be retained in the public inspection files are as follows:</P>
                <P>A copy of the current FCC authorization to construct or operate the station, as well as any other documents necessary to reflect any modifications thereto or any conditions that the FCC has placed on the authorization;</P>
                <P>A copy of any application tendered for filing with the FCC, together with all related material, and copies of Initial Decision and Final Decisions in hearing cases. If petitions to deny are filed against the application, a statement that such a petition has been filed shall be maintained in the file together with the name and address of the party filing the petition;</P>
                <P>For commercial broadcast stations, a copy of every written citizen agreement;</P>
                <P>A copy of any service contour maps, submitted with any application, together with any other information in the application showing service contours and/or main studio and transmitter location;</P>
                <P>A copy of the most recent, complete Ownership Report (FCC Form 323) filed with the FCC for the station, together with any statements filed with the FCC certifying that the current Report is accurate;</P>
                <P>A political file of records required by 47 CFR 73.1943 concerning broadcasts by candidates for public office;</P>
                <P>An Equal Employment Opportunity File required by 47 CFR 73.2080;</P>
                <P>A copy of the most recent edition of the manual entitled “The Public and Broadcasting;”</P>
                <P>Material having a substantial bearing on a matter which is the subject of an FCC investigation or complaint to the FCC of which the applicant/permittee/licensee has been advised;</P>
                <P>For commercial radio and TV broadcast stations and non-exempt NCE broadcast stations, a list of programs that have provided the station's most significant treatment of community issues. This list must be updated on a quarterly basis and contain a brief description of how each issue was treated;</P>
                <P>For commercial TV broadcast stations, records sufficient to permit substantiation of the station's certification, in its license renewal application, of compliance with the commercial limits on children's television programming. The records must be placed in the public file annually. In addition, the FCC Form 398, Children's Television Programming Reports, reflecting efforts made by the licensee during the preceding year, and efforts planned for the next year, to serve the educational and informational needs of children must be placed in the public file annually;</P>
                <P>For NCE stations, a list of donors supporting specific programs. The list is to be retained for two years from the date of the broadcast of the specific program supported, and will be reserved for sponsors/underwriters of specific programming;</P>
                <P>Each applicant for renewal of license shall place in the public file a statement certifying compliance with the post-filing local public notice announcements within 7 days of the last day of broadcast;</P>
                <P>Commercial radio and TV licensees that provide programming to another licensee's station pursuant to time brokerage agreements are required to keep copies of those agreements in their public inspection files, with confidential information blocked out where appropriate;</P>
                <P>Commercial TV stations must make an election between retransmission consent and must-carry status once every three years and must place this election statement in the station's public inspection file;</P>
                <P>NCE television stations requesting mandatory carriage on any cable system pursuant to 47 CFR 76.56 shall place in their public inspection files the request and relevant correspondence;</P>
                <P>Commercial radio and TV licensees who have entered into joint sales agreements must place the agreements in the public inspection file, with confidential and propriety information blocked out where appropriate; and</P>
                <P>Commercial TV licensees who have entered into shared service agreements must place the agreements in the public inspection file, with confidential and proprietary information blocked out where appropriate.</P>
                <P>
                    47 CFR 73.3526(e)(14)—
                    <E T="03">Radio and television time brokerage agreements.</E>
                     For commercial radio and television stations, a copy of every agreement or contract involving time brokerage of the licensee's station or of another station by the licensee, whether the agreement involves stations in the same markets or in differing markets, with confidential or proprietary information redacted where appropriate. These agreements shall be placed in the public file within 30 days of execution and retained in the file as long as the contract or agreement is in force.
                </P>
                <P>
                    47 CFR 73.3526(e)(15)—
                    <E T="03">Must-carry or retransmission consent election.</E>
                     Statements of a commercial television or Class A television station's election with respect to either must-carry or re-transmission consent, as defined in §§ 76.64 and 76.1608 of this chapter. These records shall be retained for the duration of the three-year election period to which the statement applies. Commercial television stations shall, no later than July 31, 2020, provide an up-to-date email address and phone number for carriage-related questions and respond as soon as is reasonably possible to messages or calls from MVPDs. Each commercial television station is responsible for the continuing accuracy and completeness of the information furnished.
                </P>
                <P>
                    47 CFR 73.3526(e)(16)—
                    <E T="03">Radio and television joint sales agreements.</E>
                     For commercial radio and commercial television stations, a copy of agreement for the joint sale of advertising time involving the station, whether the agreement involves stations in the same markets or in differing markets, with confidential or proprietary information redacted where appropriate. These agreements shall be placed in the public file within 30 days of execution and retained in the file as long as the contract or agreement is in force.
                </P>
                <P>
                    47 CFR 73.3527(e)(4)—
                    <E T="03">Ownership reports and related materials.</E>
                     A copy of the most recent, complete ownership report filed with the FCC for the station, together with any subsequent statement filed with the FCC certifying that the current report is accurate, and together with all related material. These materials shall be retained until a new, complete ownership report is filed with the FCC, at which time a copy of the new report and any related materials shall be placed in the file. The permittee or licensee must retain in the public file 
                    <PRTPAGE P="41028"/>
                    either a copy of the station documents listed in § 73.3613(a)-(c) or an up-to-date list of such documents. If the permittee or licensee elects to maintain an up-to-date list of such documents, the list must include all the information that the permittee or licensee is required to provide on ownership reports for each document, including, but not limited to, a description of the document, the parties to the document, the month and year of execution, the month and year of expiration, and the document type (
                    <E T="03">e.g.,</E>
                     network affiliation agreement, articles of incorporation, bylaws, management consultant agreement with independent contractor). Regardless of which of these two options the permittee or licensee chooses, it must update the inventory of § 73.3613 documents in the public file to reflect newly executed § 73.3613 documents, amendments, supplements, and cancellations within 30 days of execution thereof. Licensees and permittees that choose to maintain a list of § 73.3613 documents must provide a copy of any § 73.3613 document(s) to requesting parties within 7 days. In maintaining copies of such documents in the public file or providing copies upon request, confidential or proprietary information may be redacted where appropriate.
                </P>
                <P>47 CFR 73.3526(e)(11)(ii)—commercial TV and Class A TV broadcast must maintain records sufficient to permit substantiation of the station's certification, in its license renewal application, of compliance with the commercial limits on children's programming established in 47 U.S.C. 303a and 47 CFR 73.670. These stations must place these records in their public files annually within 30 days after the end of the calendar year.</P>
                <P>47 CFR 73.3526(e)(11)(iii)—requires that commercial television stations place in their public files their Children's Television Programming Reports (FCC Form 2100 Schedule H) on an annual basis, within 30 days after the end of the calendar year.</P>
                <P>
                    47 CFR 73.3527(e)(12)—
                    <E T="03">Must-carry requests.</E>
                     States noncommercial television stations shall, no later than July 31, 2020, provide an up-to-date email address and phone number for carriage-related questions and respond as soon as is reasonably possible to messages or calls from MVPDs. Each noncommercial television station is responsible for the continuing accuracy and completeness of the information furnished. Any such station requesting mandatory carriage pursuant to Part 76 of this chapter shall place a copy of such request in its public file and shall retain both the request and relevant correspondence for the duration of any period to which the request applies.
                </P>
                <P>
                    47 CFR 73.3526(e)(13)—
                    <E T="03">Local public notice announcements.</E>
                     Each applicant for renewal of license shall, within 7 days of the last day of broadcast of the local public notice of filing announcements required pursuant to § 73.3580(c)(3), place in the station's online public inspection file a statement certifying compliance with this requirement. The dates and times that the on-air announcements were broadcast shall be made part of the certifying statement. The certifying statement shall be retained in the public file for the period specified in § 73.3580(e)(2) (for as long as the application to which it refers).
                </P>
                <P>
                    47 CFR 73.3527(e)(10)—
                    <E T="03">Local public notice announcements.</E>
                     Each applicant for renewal of license shall, within 7 days of the last day of broadcast of the local public notice of filing announcements required pursuant to § 73.3580(c)(3), place in the station's online public inspection file a statement certifying compliance with this requirement. The dates and times that the on-air announcements were broadcast shall be made part of the certifying statement. The certifying statement shall be retained in the public file for the period specified in § 73.3580(e)(2) (for as long as the application to which it refers).
                </P>
                <P>
                    47 CFR 73.3526(e)(19)—
                    <E T="03">Foreign sponsorship disclosures.</E>
                     Documentation sufficient to demonstrate that the station is continuing to meet the requirements set forth at § 73.1212(j)(6).
                </P>
                <P>
                    47 CFR 73.3527(e)(15)—
                    <E T="03">Foreign sponsorship disclosures.</E>
                     Documentation sufficient to demonstrate that the station is continuing to meet the requirements set forth at § 73.1212(j)(6).
                </P>
                <P>47 CFR 73.1212(k)—The requirements in § 73.1212(j) shall apply to programs permitted to be delivered to foreign broadcast stations under an authorization pursuant to the Section 325(c) of the Communications Act of 1934 (47 U.S.C. 325(c)) if any part of the material has been sponsored, paid for, or furnished for free as an inducement to air on the foreign station by a foreign governmental entity. A Section 325(c) permit holder shall place copies of the disclosures required along with the name of the program to which the disclosures were appended in the International Bureau's public filing System (IBFS) under the relevant IBFS Section 325(c) permit file. The filing must state the date and time the program aired. In the case of repeat airings of the program, those additional dates and times should also be included. Where an aural announcement was made, its contents must be reduced to writing and placed in the IBFS in the same manner.</P>
                <P>47 CFR 73.1943(c) and 76.1701(c) provide that when a broadcast station licensee or a cable television system provides free time for use by or on behalf of candidates, a record of the free time provided must be placed in the political file.</P>
                <P>47 CFR 73.1943(d) and 76.1701(d) state that the records required to be maintained in a broadcast station licensee's or cable television system's political file must be placed in the political file as soon as possible and retained for a period of two years. As soon as possible means immediately absent unusual circumstances.</P>
                <P>47 CFR 73.1212(e) and 76.1701(e) require that, when an entity sponsors broadcast or cablecast material that concerns a political matter or a discussion of a controversial issue of public importance, a list must be maintained in the public file of the system that includes the sponsoring entity's chief executive officers, or members of its executive committee or of its board of directors.</P>
                <SIG>
                    <P>Federal Communications Commission.</P>
                    <NAME>Marlene Dortch, </NAME>
                    <TITLE>Secretary, Office of the Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13601 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL DEPOSIT INSURANCE CORPORATION</AGENCY>
                <DEPDOC>[OMB No. 3064-127]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Proposed Collection Renewal; Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Deposit Insurance Corporation (FDIC).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The FDIC, as part of its obligations under the Paperwork Reduction Act of 1995 (PRA), invites the general public and other Federal agencies to take this opportunity to comment on this extension without change of the existing information collection described below (OMB Control No. 3064-0127). The notice of proposed renewal for this collection was previously published in the 
                        <E T="04">Federal Register</E>
                         on April 23, 2026, allowing for a 60-day comment period. No comments were received.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted on or before August 5, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Interested parties are invited to submit written comments to 
                        <PRTPAGE P="41029"/>
                        the FDIC by any of the following methods:
                    </P>
                    <P>
                        • 
                        <E T="03">Agency Website: https://www.fdic.gov/resources/regulations/federal-register-publications/.</E>
                    </P>
                    <P>
                        • 
                        <E T="03">Email: comments@fdic.gov.</E>
                         Include the name and number of the collection in the subject line of the message.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Robert Meiers, Regulatory Counsel, MB-3013, Federal Deposit Insurance Corporation, 550 17th Street NW, Washington, DC 20429.
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery:</E>
                         Comments may be hand-delivered to the guard station at the rear of the 17th Street NW building (located on F Street NW), on business days between 7 a.m. and 5 p.m.
                    </P>
                    <P>All comments should refer to the relevant OMB control number. A copy of the comments may also be submitted to the OMB desk officer for the FDIC: Office of Information and Regulatory Affairs, Office of Management and Budget, New Executive Office Building, Washington, DC 20503.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION, CONTACT: </HD>
                    <P>
                        Robert Meiers, Regulatory Attorney, 
                        <E T="03">Romeiers@fdic.gov,</E>
                         MB-3013, Federal Deposit Insurance Corporation, 550 17th Street NW, Washington, DC 20429.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Proposal to renew the following currently approved collection of information:</E>
                </P>
                <P>
                    1. 
                    <E T="03">Title:</E>
                     Fast-Track Generic Clearance for the Collection of Qualitative Feedback.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     3064-0127.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     n/a.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Private sector, business and other for-profit entities.
                </P>
                <P>
                    <E T="03">Burden Estimate:</E>
                </P>
                <GPOTABLE COLS="6" OPTS="L2,nj,i1" CDEF="s50,r25,12,12,12,12">
                    <TTITLE>Table 1—Summary of Estimated Annual Burden </TTITLE>
                    <TDESC>[OMB No. 3064-0127]</TDESC>
                    <BOXHD>
                        <CHED H="1">
                            Information collection (IC)
                            <LI>(obligation to respond)</LI>
                        </CHED>
                        <CHED H="1">
                            Type of burden
                            <LI>(frequency of response)</LI>
                        </CHED>
                        <CHED H="1">
                            Number of 
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Number of 
                            <LI>responses per </LI>
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Average time 
                            <LI>per response </LI>
                            <LI>(HH:MM)</LI>
                        </CHED>
                        <CHED H="1">
                            Annual burden 
                            <LI>(hours)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW RUL="n,n,s">
                        <ENT I="01">1. Fast-Track Generic Clearance for the Collection of Qualitative Feedback, (Voluntary)</ENT>
                        <ENT>Reporting (Once)</ENT>
                        <ENT>17,000</ENT>
                        <ENT>1</ENT>
                        <ENT>01:00</ENT>
                        <ENT>17,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total Annual Burden (Hours)</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT>17,000</ENT>
                    </ROW>
                    <TNOTE>Source: FDIC.</TNOTE>
                    <TNOTE>
                        <E T="02">Note:</E>
                         The estimated annual IC time burden is the product, rounded to the nearest hour, of the estimated annual number of responses and the estimated time per response for a given IC. The estimated annual number of responses is the product, rounded to the nearest whole number, of the estimated annual number of respondents and the estimated annual number of responses per respondent. This methodology ensures the estimated annual burdens in the table are consistent with the values recorded in OMB's consolidated information system.
                    </TNOTE>
                </GPOTABLE>
                <P>
                    <E T="03">General Description of Collection:</E>
                     This information collection establishes ongoing authority for FDIC to conduct yet-to-be-determined occasional quality of service surveys under OMB's generic survey program. Once this information collection extension request is approved by OMB, FDIC will be able to obtain expedited approval of individual surveys by following a special submission process that does not require the publication of 
                    <E T="04">Federal Register</E>
                     notices for each individual survey. Generic clearance requests should be approved by OMB within five business days of submission. FDIC estimates that the generic surveys to be deployed under this information collection each will involve an average of 850 respondents, generally should not require more than one hour per respondent to complete, and are always voluntary in nature. FDIC estimates that it will deploy approximately 20 such surveys annually. The purpose of the surveys is, in general terms, to obtain anecdotal information on a voluntary basis about quality of service, regulatory burden, problems or successes in the bank supervisory process (including exams related to both safety and soundness, and compliance with consumer protection laws and regulations), the perceived need for regulatory or statutory change, and similar concerns. There is no change in the substance or methodology of this information collection and the estimated annual burden remains unchanged.
                </P>
                <HD SOURCE="HD1">Request for Comment</HD>
                <P>Comments are invited on: (a) whether the collections of information are necessary for the proper performance of the FDIC's functions, including whether the information has practical utility; (b) the accuracy of the estimates of the burden of the information collections, including the validity of the methodology and assumptions used; (c) ways to enhance the quality, utility, and clarity of the information to be collected; and (d) ways to minimize the burden of the collections of information on respondents, including through the use of automated collection techniques or other forms of information technology. All comments will become a matter of public record.</P>
                <SIG>
                    <FP>Federal Deposit Insurance Corporation.</FP>
                    <DATED>Dated at Washington, DC, on June 30, 2026.</DATED>
                    <NAME>Jennifer M. Jones,</NAME>
                    <TITLE>Deputy Executive Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13506 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6714-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL RESERVE SYSTEM</AGENCY>
                <SUBJECT>Change in Bank Control Notices; Acquisitions of Shares of a Bank or Bank Holding Company</SUBJECT>
                <P>The notificants listed below have applied under the Change in Bank Control Act (Act) (12 U.S.C. 1817(j)) and § 225.41 of the Board's Regulation Y (12 CFR 225.41) to acquire shares of a bank or bank holding company. The factors that are considered in acting on the applications are set forth in paragraph 7 of the Act (12 U.S.C. 1817(j)(7)).</P>
                <P>
                    The public portions of the applications listed below, as well as other related filings required by the Board, if any, are available for immediate inspection at the Federal Reserve Bank(s) indicated below and at the offices of the Board of Governors. This information may also be obtained on an expedited basis, upon request, by contacting the appropriate Federal Reserve Bank and from the Board's Freedom of Information Office at 
                    <E T="03">https://www.federalreserve.gov/foia/request.htm.</E>
                     Interested persons may express their views in writing on the standards enumerated in paragraph 7 of the Act.
                </P>
                <P>
                    Comments 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 
                    <PRTPAGE P="41030"/>
                    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 July 21, 2026.</P>
                <P>
                    <E T="03">A. Federal Reserve Bank of Dallas</E>
                     (Lindsey Wieck, Director, Mergers &amp; Acquisitions) 2200 North Pearl Street Dallas, Texas 75201-2272. Comments can also be sent electronically to 
                    <E T="03">Comments.applications@dal.frb.org:</E>
                </P>
                <P>
                    1. 
                    <E T="03">William Horwood, Lonnie Horwood, Tristan Himes, Katlin Horwood, Tate Horwood, Larry Horwood, Linda Horwood, Lathen Horwood, and Lane Horwood, all of Sterling City, Texas; Carly Horwood Janca, San Angelo, Texas; Trisha Horwood Halfmann, Garden City, Texas; Lyle Horwood, Ringgold, Texas; Lisa Horwood Spanjer, San Antonio, Texas; Laura Bibb, Llano, Texas; and Ellen Shoemake</E>
                    r, 
                    <E T="03">Helotes, Texas;</E>
                     to form the Horwood Family Control Group, a group acting in concert, to retain voting shares of Sterling City Bancshares, Inc., and thereby indirectly retain voting shares of The First National Bank of Sterling City, both of Sterling City, Texas.
                </P>
                <SIG>
                    <P>Board of Governors of the Federal Reserve System.</P>
                    <NAME>Erin Cayce,</NAME>
                    <TITLE>Assistant Secretary of the Board.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13591 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Agency for Healthcare Research and Quality</SUBAGY>
                <SUBJECT>Patient Safety Organizations: Voluntary Relinquishment for the Cassatt Patient Safety Organization</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Agency for Healthcare Research and Quality (AHRQ), Department of Health and Human Services (HHS).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of delisting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Patient Safety and Quality Improvement Final Rule (Patient Safety Rule) authorizes AHRQ, on behalf of the Secretary of HHS, to list as a patient safety organization (PSO) an entity that attests that it meets the statutory and regulatory requirements for listing. A PSO can be “delisted” by the Secretary if it is found to no longer meet the requirements of the Patient Safety and Quality Improvement Act of 2005 (Patient Safety Act) and Patient Safety Rule, such as when a PSO chooses to voluntarily relinquish its status as a PSO for any reason or when a PSO's listing expires. AHRQ accepted a notification of proposed voluntary relinquishment from the Cassatt Patient Safety Organization, PSO number P0136, of its status as a PSO and has delisted the PSO accordingly.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The delisting was effective at 12:00 Midnight ET (2400) on June 8, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The directories for both listed and delisted PSOs are ongoing and reviewed weekly by AHRQ. Both directories can be accessed electronically at the following HHS website: 
                        <E T="03">https://www.pso.ahrq.gov/listed.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Cathryn Bach, Center for Quality Improvement and Patient Safety, AHRQ, 5600 Fishers Lane, MS 07N66B, Rockville, MD 20857; Telephone (toll free): (866) 403-3697; Telephone (local): (301) 427-1111; TTY (toll free): (866) 438-7231; TTY (local): (301) 427-1130; Email: 
                        <E T="03">pso@ahrq.hhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    The Patient Safety Act, 42 U.S.C. 299b-21 to 299b-26, and the related Patient Safety Rule, 42 CFR part 3, published in the 
                    <E T="04">Federal Register</E>
                     on November 21, 2008 (73 FR 70732-70814), establish a framework by which individuals and entities that meet the definition of provider in the Patient Safety Rule may voluntarily report information to PSOs listed by AHRQ, on a privileged and confidential basis, for the aggregation and analysis of patient safety work product.
                </P>
                <P>The Patient Safety Act authorizes the listing of PSOs, which are entities or component organizations whose mission and primary activity are to conduct activities to improve patient safety and the quality of health care delivery.</P>
                <P>HHS issued the Patient Safety Rule to implement the Patient Safety Act. AHRQ administers the provisions of the Patient Safety Act and Patient Safety Rule relating to the listing and operation of PSOs. The Patient Safety Rule authorizes AHRQ to list as a PSO an entity that attests that it meets the statutory and regulatory requirements for listing. A PSO can be “delisted” if it is found to no longer meet the requirements of the Patient Safety Act and Patient Safety Rule, when a PSO chooses to voluntarily relinquish its status as a PSO for any reason, or when a PSO's listing expires. Section 3.108(d) of the Patient Safety Rule requires AHRQ to provide public notice when it removes an organization from the list of PSOs.</P>
                <P>AHRQ has accepted a notification of proposed voluntary relinquishment from the Cassatt Patient Safety Organization to voluntarily relinquish its status as a PSO. Accordingly, the Cassatt Patient Safety Organization, PSO number P0136, was delisted effective at 12:00 Midnight ET (2400) on June 8, 2026.</P>
                <P>Cassatt Patient Safety Organization has patient safety work product (PSWP) in its possession. The PSO will meet the requirements of section 3.108(c)(2)(i) of the Patient Safety Rule regarding notification to providers that have reported to the PSO and of section 3.108(c)(2)(ii) regarding disposition of PSWP consistent with section 3.108(b)(3). According to section 3.108(b)(3) of the Patient Safety Rule, the PSO has 90 days from the effective date of delisting and revocation to complete the disposition of PSWP that is currently in the PSO's possession.</P>
                <P>
                    More information on PSOs can be obtained through AHRQ's PSO website at 
                    <E T="03">http://www.pso.ahrq.gov.</E>
                </P>
                <SIG>
                    <NAME>Roger D. Klein,</NAME>
                    <TITLE>Director.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13604 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4160-90-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Centers for Disease Control and Prevention</SUBAGY>
                <DEPDOC>[30Day-26-1419]</DEPDOC>
                <SUBJECT>Agency Forms Undergoing Paperwork Reduction Act Review</SUBJECT>
                <P>
                    In accordance with the Paperwork Reduction Act of 1995, the Centers for Disease Control and Prevention (CDC) has submitted the information collection request titled “Public Health/Public Safety Strategies to Reduce Drug Overdose Data Collection” to the Office of Management and Budget (OMB) for review and approval. CDC previously published a “Proposed Data Collection Submitted for Public Comment and Recommendations” notice on April 7, 2026 to obtain comments from the public and affected agencies. CDC received eight comments related to the previous notice. This notice serves to 
                    <PRTPAGE P="41031"/>
                    allow an additional 30 days for public and affected agency comments.
                </P>
                <P>CDC will accept all comments for this proposed information collection project. The Office of Management and Budget is particularly interested in comments that:</P>
                <P>(a) Evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility;</P>
                <P>(b) Evaluate the accuracy of the agencies estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used;</P>
                <P>(c) Enhance the quality, utility, and clarity of the information to be collected;</P>
                <P>
                    (d) Minimize the burden of the collection of information on those who are to respond, including, through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, 
                    <E T="03">e.g.,</E>
                     permitting electronic submission of responses; and
                </P>
                <P>(e) Assess information collection costs.</P>
                <P>
                    To request additional information on the proposed project or to obtain a copy of the information collection plan and instruments, call (404) 639-7570. Comments and recommendations for the proposed information collection should be sent within 30 days of publication of this notice to 
                    <E T="03">www.reginfo.gov/public/do/PRAMain.</E>
                     Find this particular information collection by selecting “Currently under 30-day Review—Open for Public Comments” or by using the search function. Direct written comments and/or suggestions regarding the items contained in this notice to the Attention: CDC Desk Officer, Office of Management and Budget, 725 17th Street, NW, Washington, DC 20503 or by fax to (202) 395-5806. Provide written comments within 30 days of notice publication.
                </P>
                <HD SOURCE="HD1">Proposed Project</HD>
                <P>Public Health/Public Safety Strategies to Reduce Drug Overdose Data Collection (OMB Control No. 0920-1419, Exp. 10/31/2026)—Revision—National Center for Injury Prevention and Control (NCIPC), Centers for Disease Control and Prevention (CDC).</P>
                <HD SOURCE="HD2">Background and Brief Description</HD>
                <P>
                    The drug overdose epidemic continues to pose a threat to communities across the country. In 2024, there were 79,384 overdose deaths, which equates to about 217 overdose deaths each day. While this indicates a decline in deaths since 2022, overdose remains the leading cause of death for Americans aged 18-44. In December 2025, the declaration of the opioid crisis as a national public health emergency was renewed yet again. Adding to this challenge, drug availability and overdose trends continue to change, shaped most recently by the widespread inclusion of adulterants in the drug supply (
                    <E T="03">e.g.,</E>
                     fentanyl, xylazine, medetomidine) and an increase in the number of overdose deaths with evidence of smoking.
                </P>
                <P>Multisector collaboration is critical to saving lives and reducing the overdose epidemic. Two key sectors in this response, public health and public safety (PH/PS), are both on the front lines and tasked with improving community safety and well-being. CDC demonstrates strong commitment to PH/PS partnerships through implementation of several national programs. In September 2019, CDC launched the first multiyear Overdose Data to Action (OD2A) cooperative agreement that enhanced surveillance and prevention of fatal and nonfatal opioid overdoses in 47 states and 19 localities. In August 2023, CDC awarded new cooperative agreements to 49 states and 40 localities that aimed to apply lessons learned from the previous funding opportunity, continue to enhance surveillance, and close gaps in prevention. The current iteration of the program requires recipients to carry out prevention activities in partnership with public safety or in public safety settings. Since 2017, CDC has supported the Overdose Response Strategy (ORS), a unique collaboration between public health and public safety partners created to help local communities reduce drug overdose and save lives. Finally, CDC leads the Opioid Rapid Response Program, an interagency, coordinated federal effort with the HHS Office of Inspector General, the Drug Enforcement Administration, and other federal agencies, to help mitigate overdose risks among patients who lose access to a prescriber of opioids due to law enforcement actions. As PH/PS strategies for overdose prevention continue to be leveraged, a comprehensive understanding of their design, implementation, and effects is needed to inform these national programs.</P>
                <P>The goal of this Revision to this Generic Clearance information collection request (ICR) is to continue to collect data to improve overdose prevention efforts that involve PH/PS sectors or address populations at increased risk of overdose in the public safety setting. This requires practical information and experiential knowledge on current implementation of overdose prevention efforts by PH/PS. Based on previous experience, NCIPC has revised this ICR to removed objective C: Identify disparities in access to, or the effectiveness of, strategies, as it is no longer needed.</P>
                <P>This Generic Clearance will continue to allow for the gathering of information about PH/PS strategies to identify actions to improve responses to the overdose crisis. The assessments conducted and information gathered through this Generic Clearance are used to rapidly improve the implementation of programs enacted through these partnerships throughout the lifespan of CDC's national programs and more broadly. In this context, a routine ICR does not suffice, as not collecting this information in a timely manner impedes CDC from responding to state or local requests for assistance and delays identifying new strategies or modifying existing ones that could lead to reduced overdose morbidity and mortality.</P>
                <P>CDC requests OMB approval for an estimated 2,500 annual burden hours. There is no cost to respondents other than their time to participate.</P>
                <GPOTABLE COLS="5" OPTS="L2,nj,i1" CDEF="s50,r50,12,12,12">
                    <TTITLE>Estimated Annualized Burden Hours</TTITLE>
                    <BOXHD>
                        <CHED H="1">Type of respondent</CHED>
                        <CHED H="1">Form name</CHED>
                        <CHED H="1">
                            Number of 
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Number of 
                            <LI>responses per </LI>
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Average 
                            <LI>burden per </LI>
                            <LI>response </LI>
                            <LI>(in hours)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Public Health/Public Safety Strategies Data Collection Participants</ENT>
                        <ENT>Public Health/Public Safety Strategies Data Collection Instruments</ENT>
                        <ENT>5,000</ENT>
                        <ENT>1</ENT>
                        <ENT>30/60</ENT>
                    </ROW>
                </GPOTABLE>
                <SIG>
                    <PRTPAGE P="41032"/>
                    <NAME>Jeffrey M. Zirger,</NAME>
                    <TITLE>Lead, Information Collection Review Office, Office of Public Health Ethics and Regulations, Office of Science, Centers for Disease Control and Prevention.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13558 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4163-18-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Centers for Disease Control and Prevention</SUBAGY>
                <DEPDOC>[60Day-26-0841; Docket No. CDC-2026-1156]</DEPDOC>
                <SUBJECT>Proposed Data Collection Submitted for Public Comment and Recommendations</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Disease Control and Prevention (CDC), Department of Health and Human Services (HHS).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice with comment period.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Centers for Disease Control and Prevention (CDC), as part of its continuing effort to reduce public burden and maximize the utility of government information, invites the general public and other federal agencies the opportunity to comment on a continuing information collection, as required by the Paperwork Reduction Act of 1995. This notice invites comment on a proposed information collection project titled Management Information System for Comprehensive Cancer Control Programs. This CDC project is designed to use annual key informant interviews and biennial surveys to monitor program outcomes and report progress to CDC annually.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>CDC must receive written comments on or before September 4, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by Docket No. CDC-2026-1156 by either of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal: www.regulations.gov.</E>
                         Follow the instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Jeffrey M. Zirger, Information Collection Review Office, Centers for Disease Control and Prevention, 1600 Clifton Road NE, MS H21-8, Atlanta, Georgia 30329.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions received must include the agency name and Docket Number. CDC will post, without change, all relevant comments to 
                        <E T="03">www.regulations.gov.</E>
                    </P>
                    <P>
                        <E T="03">Please note:</E>
                         Submit all comments through the Federal eRulemaking portal (
                        <E T="03">www.regulations.gov</E>
                        ) or by U.S. mail to the address listed above.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        To request more information on the proposed project or to obtain a copy of the information collection plan and instruments, contact Jeffrey M. Zirger, Information Collection Review Office, Centers for Disease Control and Prevention, 1600 Clifton Road NE, MS H21-8, Atlanta, Georgia 30329; Telephone: 404-639-7570; Email: 
                        <E T="03">omb@cdc.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Under the Paperwork Reduction Act of 1995 (PRA) (44 U.S.C. 3501-3520), federal agencies must obtain approval from the Office of Management and Budget (OMB) for each collection of information they conduct or sponsor. In addition, the PRA also requires federal agencies to provide a 60-day notice in the 
                    <E T="04">Federal Register</E>
                     concerning each proposed collection of information, including each new proposed collection, each proposed extension of existing collection of information, and each reinstatement of previously approved information collection before submitting the collection to the OMB for approval. To comply with this requirement, we are publishing this notice of a proposed data collection as described below.
                </P>
                <P>The OMB is particularly interested in comments that will help:</P>
                <P>1. Evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility;</P>
                <P>2. Evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used;</P>
                <P>3. Enhance the quality, utility, and clarity of the information to be collected;</P>
                <P>
                    4. Minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, 
                    <E T="03">e.g.,</E>
                     permitting electronic submissions of responses; and
                </P>
                <P>5. Assess information collection costs.</P>
                <HD SOURCE="HD1">Proposed Project</HD>
                <P>Management Information System for Comprehensive Cancer Control Programs (OMB Control No. 0920-0841, Exp 09/30/2026)—Revision—National Center for Chronic Disease Prevention and Health Promotion (NCCDPHP), Centers for Disease Control and Prevention (CDC)</P>
                <HD SOURCE="HD2">Background and Brief Description</HD>
                <P>CDC requests clearance of a Revision for the National Comprehensive Cancer Control Program's (NCCCP) Management Information System for Comprehensive Cancer Control Programs (OMB Control No. 0920-0841, Exp. 9/30/2026) to continue electronic data collection of information about the NCCCP, funded by the Comprehensive Cancer Control Branch of the Centers for Disease Control and Prevention (CDC). OMB approval is requested for three years. This information collection is authorized by the Public Health Service Act, section 301, 241(a).</P>
                <P>The Comprehensive Cancer Control Branh manages the NCCCP, which provides funding to 66 recipients representing State Health Departments, the District of Columbia, U.S. Territories and Freely Associated States, Federally Recognized American Indian Tribes, Tribal Organizations, Alaska Native Organizations, and Urban Indian Organization; or their Bona Fide Agents, to design, implement, and evaluate comprehensive cancer control plans to reduce the burden of cancer locally. Support for these programs is a cornerstone of CDC efforts to reduce the burden of cancer throughout the nation. Awards to individual applicants are made for a five-year program period. Continuation awards for subsequent budget periods are made on the basis of satisfactory progress in achieving both national and program-specific goals and objectives, as well as the availability of funds.</P>
                <P>In 2022, 66 recipients were selected for funding for DP22-2202 (“Cancer Prevention and Control Programs for State, Territorial, and Tribal Organizations”) to implement a program to support cancer coalition efforts that leverage resources to plan and implement evidence-based strategies to promote the primary prevention of cancer; support cancer early detection efforts, address the needs of cancer survivors; and promote health for all. Consistent with programmatic changes, the proposed data collection plan for DP22-2202 has been redesigned to increase efficiency by updating existing and adding new data collection instruments, which were previously approved under the current OMB package, and associated Generic Clearance package (OMB Control No. 0920-0879). This revised data collection will allow CDC to continue providing routine feedback to recipients based on their data submissions, tailor technical assistance as needed, support program planning, and assess program outcomes.</P>
                <P>
                    In this Revision, CDC seeks OMB approval to continue using an interview and web-based survey to collect, store, retrieve, share, and report accurate and timely information to monitor and 
                    <PRTPAGE P="41033"/>
                    evaluate recipient performance. Questions have been refined to better support comprehensive assessment of the program recipients and their partners, and CDC has strengthened the alignment of all data collection instruments used for the assessment of the cooperative agreement DP22-2202. The instruments were reviewed for consistency, streamlined where possible to remove duplicative questions, and updated to improve clarity and usability for respondents. Key revisions included updates to evidence-based intervention questions to ensure consistent and aligned terminology. In addition, instructions for these questions were streamlined to emphasize identification of primary interventions. CDC requests OMB approval for a total estimated annualized burden of 183 hours. There are no costs to respondents other than their time.
                </P>
                <GPOTABLE COLS="6" OPTS="L2,nj,i1" CDEF="s75,r50,11,12,10,10">
                    <TTITLE>Estimated Annualized Burden Hours</TTITLE>
                    <BOXHD>
                        <CHED H="1">Type of respondents</CHED>
                        <CHED H="1">Form name</CHED>
                        <CHED H="1">
                            Number of
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Number of
                            <LI>responses per</LI>
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Average
                            <LI>burden per</LI>
                            <LI>response</LI>
                            <LI>(in hours)</LI>
                        </CHED>
                        <CHED H="1">
                            Total
                            <LI>burden</LI>
                            <LI>(in hours)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Program Director for State-, Tribal-, or Territorial-based Cancer Prevention and Control Program</ENT>
                        <ENT>NCCCP Program Director Survey</ENT>
                        <ENT>44</ENT>
                        <ENT>1</ENT>
                        <ENT>90/60</ENT>
                        <ENT>66</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Partner for State-, Tribal-, or Territorial-based Cancer Prevention and Control Program</ENT>
                        <ENT>NCCCP Partner Survey</ENT>
                        <ENT>44</ENT>
                        <ENT>1</ENT>
                        <ENT>60/60</ENT>
                        <ENT>44</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Program Director for State-, Tribal-, or Territorial-based Cancer Prevention and Control Program</ENT>
                        <ENT>NCCCP Key Informant Interview Guide—Program Director</ENT>
                        <ENT>18</ENT>
                        <ENT>1</ENT>
                        <ENT>75/60</ENT>
                        <ENT>23</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Program Implementer for State-, Tribal-, or Territorial-based Cancer Prevention and Control Program</ENT>
                        <ENT>NCCCP Key Informant Interview Guide—Program Implementer</ENT>
                        <ENT>18</ENT>
                        <ENT>1</ENT>
                        <ENT>75/60</ENT>
                        <ENT>23</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Partner for State-, Tribal-, or Territorial-based Cancer Prevention and Control Program</ENT>
                        <ENT>NCCCP Key Informant Interview Guide—Partner</ENT>
                        <ENT>18</ENT>
                        <ENT>1</ENT>
                        <ENT>60/60</ENT>
                        <ENT>18</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01">Program Director for State-, Tribal-, or Territorial-based Cancer Prevention and Control Program</ENT>
                        <ENT>NCCCP Interview Pre-Planning Worksheet</ENT>
                        <ENT>18</ENT>
                        <ENT>1</ENT>
                        <ENT>30/60</ENT>
                        <ENT>9</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT>183</ENT>
                    </ROW>
                </GPOTABLE>
                <SIG>
                    <NAME>Jeffrey M. Zirger,</NAME>
                    <TITLE>Lead, Information Collection Review Office, Office of Public Health Ethics and Regulations, Office of Science, Centers for Disease Control and Prevention.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13559 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4163-18-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Centers for Disease Control and Prevention</SUBAGY>
                <DEPDOC>[60Day-26-1423; Docket No. CDC-2026-1190]</DEPDOC>
                <SUBJECT>Proposed Data Collection Submitted for Public Comment and Recommendations</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Disease Control and Prevention (CDC), Department of Health and Human Services (HHS).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice with comment period.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Centers for Disease Control and Prevention (CDC), as part of its continuing effort to reduce public burden and maximize the utility of government information, invites the general public and other Federal agencies the opportunity to comment on a continuing information collection, as required by the Paperwork Reduction Act of 1995. This notice invites comment on a proposed information collection project titled Expanding PrEP in Communities of Color (EPICC). This project is designed to facilitate preexposure prophylaxis (PrEP) shared decision making, train providers on the use of Evidence Based Tools (EBT), and evaluate the impact within a longitudinal cohort.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>CDC must receive written comments on or before September 4, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by Docket No. CDC-2026-1190 by either of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                          
                        <E T="03">www.regulations.gov.</E>
                         Follow the instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Jeffrey M. Zirger, Information Collection Review Office, Centers for Disease Control and Prevention, 1600 Clifton Road, NE, MS H21-8, Atlanta, Georgia 30329.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions received must include the agency name and Docket Number. CDC will post, without change, all relevant comments to 
                        <E T="03">www.regulations.gov.</E>
                    </P>
                    <P>
                        <E T="03">Please note:</E>
                         Submit all comments through the Federal eRulemaking portal (
                        <E T="03">www.regulations.gov</E>
                        ) or by U.S. mail to the address listed above.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        To request more information on the proposed project or to obtain a copy of the information collection plan and instruments, contact Jeffrey M. Zirger, Information Collection Review Office, Centers for Disease Control and Prevention, 1600 Clifton Road NE MS H21-8, Atlanta, Georgia 30329; Telephone: 404-639-7118; Email: 
                        <E T="03">omb@cdc.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Under the Paperwork Reduction Act of 1995 (PRA) (44 U.S.C. 3501-3520), federal agencies must obtain approval from the Office of Management and Budget (OMB) for each collection of information they conduct or sponsor. In addition, the PRA also requires federal agencies to provide a 60-day notice in the 
                    <E T="04">Federal Register</E>
                     concerning each proposed collection of information, including each new proposed collection, each proposed extension of existing collection of information, and each reinstatement of previously approved information collection before submitting the collection to the OMB for approval. To comply with this requirement, we are publishing this notice of a proposed data collection as described below.
                </P>
                <P>The OMB is particularly interested in comments that will help:</P>
                <P>
                    1. Evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including 
                    <PRTPAGE P="41034"/>
                    whether the information will have practical utility;
                </P>
                <P>2. Evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used;</P>
                <P>3. Enhance the quality, utility, and clarity of the information to be collected;</P>
                <P>
                    4. Minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, 
                    <E T="03">e.g.,</E>
                     permitting electronic submissions of responses; and
                </P>
                <P>5. Assess information collection costs.</P>
                <HD SOURCE="HD1">Proposed Project</HD>
                <P>Expanding PrEP in Communities of Color (EPICC) (OMB Control No. 0920-1423, Exp. 12/31/2026)—Extension—National Center for HIV/AIDS, Viral Hepatitis, STD, and TB Prevention (NCHHSTP), Centers for Disease Control and Prevention (CDC).</P>
                <HD SOURCE="HD2">Background and Brief Description</HD>
                <P>The Expanding PrEP in Communities of Color (EPICC) project proposes to: (1) adapt and implement existing Evidence Based Tools (EBTs) to facilitate preexposure prophylaxis (PrEP) shared decision making (SDM); (2) train providers on the use of EBT; and (3) evaluate the impact within a longitudinal cohort of racially and geographically diverse young men who have sex with men (YMSM) (ages 18-39). We refer to this combination of interventions as the EPICC+ intervention package, which includes provider training, EBT for providers, and a mobile app-based platform (EPICC+ app) to support ongoing participant engagement and monitoring, as well as to provide additional adherence support. This study will be carried out in seven clinics located in New York City, NY; Philadelphia, PA; Charlotte, NC; Raleigh, NC; Tuscaloosa, AL; Tampa, FL; and Houston, TX. This study will consist of three distinct aims (Aim 1, 2a, and 2b) to adapt and implement the EBT and materials.</P>
                <P>Aim 1 will include 30 health care providers from the seven clinic sites, all involved in the direct delivery of PrEP services. Providers may include but are not limited to medical doctors, nurses, adherence counselors, pharmacists, and social workers. Health providers will be recruited via staff emails. Aim 2a participants will include 400 YMSM ages 18-39, inclusive, with an active prescription for PrEP and receiving care at one of the seven participating study sites, providing a mailing address within the 50 states where packages can be received; have daily smartphone access; and be fluent in written/spoken English or Spanish. We will use purposive sampling to ensure at least 60% patient sample is African American or Black or Hispanic/Latino/Latinx. Patient participants will be recruited to study using a combination of approaches including social media, referral and in-person outreach.</P>
                <P>Quantitative and qualitative assessments will be used to collect information from providers and YMSM participants. Provider participants will complete Pre- and Post-training Provider Surveys, and patient interaction assessments (competency assessments) post-training and three months post-training. For Aim 2a, YMSM participants will be asked to complete a baseline assessment and quarterly assessments at 3, 6, 9, 12, 15, and 18 months to assess PrEP adherence; PrEP knowledge, usage and choice; sexual risk behaviors; HIV status of partners); and substance use assessment. A subset of YMSM participants from Aim 2a will be asked to complete an exit interview that will focus on understanding factors that influenced participants' selection of PrEP regimens, changes and/or discontinuations, as well as perceptions of the counseling they received by providers at PrEP initiation and follow-up, receipt of tools or materials that influenced choice and feasibility/acceptability of the EPICC+ app. We will also conduct focus groups with providers in Aim 2b to gather feedback on overall perceptions of the barriers and facilitators to EBT implementation within their clinical site. The study will also collect data from electronic health records; biological specimens collected at quarterly intervals; and a clinic assessment tool delivered every six months.</P>
                <P>The total number of burden hours requested is 2,259 across 36 months of data collection. The total estimated annualized burden hours are 753. There are no costs to the participant other than their time.</P>
                <GPOTABLE COLS="6" OPTS="L2,nj,i1" CDEF="s50,r50,12,12,12,12">
                    <TTITLE>Estimated Annualized Burden Hours</TTITLE>
                    <BOXHD>
                        <CHED H="1">Type of respondent</CHED>
                        <CHED H="1">Form name</CHED>
                        <CHED H="1">
                            Number of
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Number of
                            <LI>responses</LI>
                            <LI>per </LI>
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Average 
                            <LI>burden</LI>
                            <LI>per response</LI>
                            <LI>(in hr)</LI>
                        </CHED>
                        <CHED H="1">
                            Total burden
                            <LI>(in hr)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Health Practitioners</ENT>
                        <ENT>Aim 1 Provider Training Screener</ENT>
                        <ENT>20</ENT>
                        <ENT>1</ENT>
                        <ENT>5/60</ENT>
                        <ENT>2</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Health Practitioners</ENT>
                        <ENT>Aim 1 Provider Training Contact Information</ENT>
                        <ENT>10</ENT>
                        <ENT>1</ENT>
                        <ENT>5/60</ENT>
                        <ENT>1</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Health Practitioners</ENT>
                        <ENT>Aim 1 Provider Pre-Training Survey</ENT>
                        <ENT>10</ENT>
                        <ENT>1</ENT>
                        <ENT>15/60</ENT>
                        <ENT>3</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Health Practitioners</ENT>
                        <ENT>Aim 1 Provider Post-Training Survey</ENT>
                        <ENT>10</ENT>
                        <ENT>1</ENT>
                        <ENT>15/60</ENT>
                        <ENT>3</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Health Practitioners</ENT>
                        <ENT>Aim 1 Provider Patient Interaction Rating Scale (Baseline and Final)</ENT>
                        <ENT>10</ENT>
                        <ENT>2</ENT>
                        <ENT>15/60</ENT>
                        <ENT>5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">General Public—Adults</ENT>
                        <ENT>Aim 2a Cohort Screener (English/Spanish)</ENT>
                        <ENT>267</ENT>
                        <ENT>1</ENT>
                        <ENT>5/60</ENT>
                        <ENT>22</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">General Public—Adults</ENT>
                        <ENT>Aim 2a Cohort Contact Information (English/Spanish)</ENT>
                        <ENT>134</ENT>
                        <ENT>1</ENT>
                        <ENT>5/60</ENT>
                        <ENT>11</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">General Public—Adults</ENT>
                        <ENT>Aim 2a Cohort HIPPA Form (English/Spanish)</ENT>
                        <ENT>134</ENT>
                        <ENT>1</ENT>
                        <ENT>5/60</ENT>
                        <ENT>11</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">General Public—Adults</ENT>
                        <ENT>Aim 2a Cohort Baseline Assessment (English/Spanish)</ENT>
                        <ENT>134</ENT>
                        <ENT>1</ENT>
                        <ENT>45/60</ENT>
                        <ENT>101</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">General Public—Adults</ENT>
                        <ENT>
                            Aim 2a Cohort Follow-up Survey
                            <LI>(English/Spanish)</LI>
                        </ENT>
                        <ENT>134</ENT>
                        <ENT>3</ENT>
                        <ENT>45/60</ENT>
                        <ENT>302</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">General Public—Adults</ENT>
                        <ENT>Aim 2a Cohort App Setup (English/Spanish)</ENT>
                        <ENT>134</ENT>
                        <ENT>1</ENT>
                        <ENT>30/60</ENT>
                        <ENT>67</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">General Public—Adults</ENT>
                        <ENT>Aim 2a Cohort Blood Collection Instructions (English/Spanish)</ENT>
                        <ENT>134</ENT>
                        <ENT>2</ENT>
                        <ENT>30/60</ENT>
                        <ENT>134</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="41035"/>
                        <ENT I="01">General Public—Adults</ENT>
                        <ENT>Aim 2a Cohort Exit Interview (English/Spanish)</ENT>
                        <ENT>15</ENT>
                        <ENT>1</ENT>
                        <ENT>60/60</ENT>
                        <ENT>15</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Health Practitioners</ENT>
                        <ENT>Aim 2b Provider Focus Group Screener</ENT>
                        <ENT>32</ENT>
                        <ENT>1</ENT>
                        <ENT>5/60</ENT>
                        <ENT>3</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Health Practitioners</ENT>
                        <ENT>Aim 2b Provider Focus Group Contact Information</ENT>
                        <ENT>16</ENT>
                        <ENT>1</ENT>
                        <ENT>5/60</ENT>
                        <ENT>1</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Health Practitioners</ENT>
                        <ENT>Aim 2b Provider Pre-Focus Group Survey</ENT>
                        <ENT>16</ENT>
                        <ENT>1</ENT>
                        <ENT>5/60</ENT>
                        <ENT>1</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Health Practitioners</ENT>
                        <ENT>Aim 2b Provider Focus Group Guide</ENT>
                        <ENT>16</ENT>
                        <ENT>1</ENT>
                        <ENT>2.0</ENT>
                        <ENT>32</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Health Practitioners</ENT>
                        <ENT>Aims 1&amp;2 Clinic Assessment (Baseline a&amp; Final)</ENT>
                        <ENT>7</ENT>
                        <ENT>1</ENT>
                        <ENT>130/60</ENT>
                        <ENT>15</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01">Health Practitioners</ENT>
                        <ENT>Aims 1&amp;2 Clinic Assessment (every 6 months)</ENT>
                        <ENT>7</ENT>
                        <ENT>2</ENT>
                        <ENT>100/60</ENT>
                        <ENT>24</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT>753</ENT>
                    </ROW>
                </GPOTABLE>
                <SIG>
                    <NAME>Jeffrey M. Zirger,</NAME>
                    <TITLE>Lead, Information Collection Review Office, Office of Public Health Ethics and Regulations, Office of Science, Centers for Disease Control and Prevention.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13560 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4163-18-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Centers for Disease Control and Prevention</SUBAGY>
                <DEPDOC>[60Day-26-1428; Docket No. CDC-2026-1189]</DEPDOC>
                <SUBJECT>Proposed Data Collection Submitted for Public Comment and Recommendations</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Disease Control and Prevention (CDC), Department of Health and Human Services (HHS).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice with comment period.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Centers for Disease Control and Prevention (CDC), as part of its continuing effort to reduce public burden and maximize the utility of government information, invites the general public and other federal agencies the opportunity to comment on a continuing information collection, as required by the Paperwork Reduction Act of 1995. This notice invites comment on a proposed information collection project titled mChoice: Improving PrEP Uptake and Adherence among Minority MSM through Tailored Provider Training and Adherence Assistance in Two High Priority Settings. The collection is part of a research study designed to implement and evaluate the effectiveness of an intervention that utilizes evidence-based education and support tools to improve preexposure prophylaxis (PrEP) adherence among young men who have sex with men (YMSM).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>CDC must receive written comments on or before September 4, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by Docket No. CDC-2026-1189 by either of the following methods:</P>
                    <P>
                        ☐ 
                        <E T="03">Federal eRulemaking Portal:</E>
                          
                        <E T="03">www.regulations.gov.</E>
                         Follow the instructions for submitting comments.
                    </P>
                    <P>
                        ☐ 
                        <E T="03">Mail:</E>
                         Jeffrey M. Zirger, Information Collection Review Office, Centers for Disease Control and Prevention, 1600 Clifton Road NE, MS H21-8, Atlanta, Georgia 30329.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions received must include the agency name and Docket Number. CDC will post, without change, all relevant comments to 
                        <E T="03">www.regulations.gov.</E>
                    </P>
                    <P>
                        <E T="03">Please note:</E>
                         Submit all comments through the Federal eRulemaking portal (
                        <E T="03">www.regulations.gov</E>
                        ) or by U.S. mail to the address listed above.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        To request more information on the proposed project or to obtain a copy of the information collection plan and instruments, contact Jeffrey M. Zirger, Information Collection Review Office, Centers for Disease Control and Prevention, 1600 Clifton Road NE, MS H21-8, Atlanta, Georgia 30329; Telephone: 404-639-7118; Email: 
                        <E T="03">omb@cdc.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Under the Paperwork Reduction Act of 1995 (PRA) (44 U.S.C. 3501-3520), federal agencies must obtain approval from the Office of Management and Budget (OMB) for each collection of information they conduct or sponsor. In addition, the PRA also requires federal agencies to provide a 60-day notice in the 
                    <E T="04">Federal Register</E>
                     concerning each proposed collection of information, including each new proposed collection, each proposed extension of existing collection of information, and each reinstatement of previously approved information collection before submitting the collection to the OMB for approval. To comply with this requirement, we are publishing this notice of a proposed data collection as described below. The OMB is particularly interested in comments that will help:
                </P>
                <P>1. Evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility;</P>
                <P>2. Evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used;</P>
                <P>3. Enhance the quality, utility, and clarity of the information to be collected;</P>
                <P>
                    4. Minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, 
                    <E T="03">e.g.,</E>
                     permitting electronic submissions of responses; and
                </P>
                <P>5. Assess information collection costs.</P>
                <HD SOURCE="HD1">Proposed Project</HD>
                <P>
                    <E T="03">mChoice:</E>
                     Improving PrEP Uptake and Adherence among Minority MSM through Tailored Provider Training and Adherence Assistance in Two High Priority Settings (OMB Control No. 0920-1428, Exp. 1/31/2027)—Extension—National Center for HIV/AIDS, Viral Hepatitis, STD, and TB 
                    <PRTPAGE P="41036"/>
                    Prevention (NCHHSTP), Centers for Disease Control and Prevention (CDC).
                </P>
                <HD SOURCE="HD2">Background and Brief Description</HD>
                <P>The National Center for HIV/AIDS, Viral Hepatitis, STD and TB Prevention (NCHHSTP) is requesting approval for a 36-month Extension of data collection for mChoice: Improving PrEP Uptake and Adherence among Minority MSM through Tailored Provider Training and Adherence Assistance in Two High Priority Settings. The purpose of this study is to implement and evaluate the effectiveness of a clinic-based intervention that utilizes evidence-based education and support tools to improve preexposure prophylaxis (PrEP) adherence among young men who have sex with men (YMSM). The goals of this research study are to: (1) improve the overall PrEP experience of providers and YMSM patients; and (2) increase our understanding of provider and patient factors that influence the choice of PrEP regimen by MSM in clinical settings. This study will be carried out in four clinics in New York, NY (two clinics) and Birmingham, AL (two clinics).</P>
                <P>Aim 1 of the study will enroll 400 YMSM (ages 18-39) who have sex with men; are using or initiating PrEP; own a smartphone; understand and read English or Spanish; and live in the New York City or Birmingham, AL area. Participants may identify as any race or ethnicity, but to ensure a diverse sample comprised mainly of racial/ethnic minority participants, the study will utilize recruitment controls to enroll at least 50% African American/Black and/or Hispanic/Latino participants. Patient participants will be recruited to the study through a combination of approaches including flyers and social media, referral, in-person outreach, and through word of mouth. Rolling enrollment will continue until enrollment targets are reached. Each Aim 1 participant will be followed for 12 months. All participants will receive PrEP clinical services congruent with CDC PrEP guidelines. Participants using oral PrEP will receive CleverCap, an electronic medication monitoring device, that will track and support medication adherence. At the 3-month study visit, participants using oral PrEP will receive the mChoice mobile phone application, an evidence-based intervention that supports PrEP use through medication monitoring, study staff interaction, and other resources. Aim 1 assessments include: a baseline survey of self-reported demographic factors, sexual and drug use behaviors, and potential cofactors of sexual and drug use behavior including attitudes, beliefs, knowledge, traits, and other psychosocial factors; follow-up surveys at 3-, 6-, 9-, and 12-month study visits which will assess experiences with PrEP, PrEP adherence, and behavioral and social factors; medication adherence data from CleverCap; participant use and voluntary self-reported adherence and HIV exposure risk-related data from the mChoice app; PrEP clinical care data from clinic electronic medical records; and urine studies assessing PrEP adherence. The information collected in Aim 1 will be used to evaluate the effectiveness of the mChoice intervention to improve PrEP adherence and persistence, and to increase understanding of PrEP experiences and factors that influence PrEP choices among MSM in clinical settings.</P>
                <P>Aim 2 of the study will enroll 30 YMSM who participated in Aim 1; 15 from New York and 15 from Alabama. Participants will be recruited at Aim 1 study visits. Study staff will conduct in-depth interviews with Aim 2 participants exploring their experiences with PrEP, reasons for PrEP choices, and thoughts about the mChoice intervention. Data collected in Aim 2 will contribute to the evaluation of the mChoice intervention, implementation, and contribute to understanding factors that influence PrEP choices by MSM in clinical settings.</P>
                <P>Aim 3 of the study will include 20 health care providers (10 from New York and 10 from Alabama) involved in the direct delivery of PrEP services at participating clinical sites. Providers may include nurse practitioners, physicians, PrEP coordinators/navigators, medical assistants, and other cross-trained coordinators from the participating clinics. Providers will be recruited via flyers, emails to clinic staff, and referrals. Providers will receive education and training designed to improve knowledge of PrEP options and clinical recommendations and enhance provider communications with patients. Aim 3 includes practice facilitation, an intervention that includes identification of a clinic champion who will engage other providers in embracing PrEP recommendations, as well as ongoing support from a practice coach who will offer tools, resources, hands-on guidance, and content expertise to assist the clinic team in developing strategies to improve clinical PrEP services. Aim 3 assessments include notes from practice facilitation coaching sessions; in-depth interviews of participating providers exploring their experiences with the intervention and thoughts about providing PrEP clinical services; and a clinic assessment completed by clinic staff every six months to describe the current implementation of PrEP services at their clinical site. These data will inform ongoing practice improvement in PrEP clinical services and increase understanding of provider experiences with providing PrEP clinical services.</P>
                <P>It is expected that half of screened persons will meet study eligibility. For all aims we anticipate that screening and completion of the locator form will each take five minutes. Study staff will assist Aim 1 participants with onboarding the CleverCap device and mChoice app, a process that will take 20 minutes. Aim 1 participants will complete the baseline survey once (anticipated 30 minutes completion time) and the follow-up survey four times (anticipated completion time 30 minutes each) over their 12-month participation period. Total study enrollment for Aim 1 is 400, over the 3-year data collection period the estimated annual enrollment is 134. Aims 2 and 3 interviews will take 60 minutes to complete. For Aim 2, total study enrollment is 30, over the 3-year data collection period the estimated annual enrollment is 10. For Aim 3, total study enrollment is 20, over the 3-year data collection period the estimated annual enrollment is seven. Additionally, a single Aim 3 participant at each of the four participating clinic sites will complete a clinic assessment form every six months throughout the study period.</P>
                <P>
                    Total enrollment for the study is 424. For the Aim 1 patient trial, we will enroll a total of 400 YMSM; over the 3-year data collection period the estimated annual enrollment will be 134. It is expected that 50% of YMSM screened will meet study eligibility criteria and agree to join the study; therefore, we expect to screen 267 YMSM annually. The collection of initial screening information will take approximately 10 minutes to complete. Once enrolled, the collection of locator information will take approximately 10 minutes to complete. YMSM participants will complete a baseline assessment which will take approximately 45 minutes to complete. YMSM participants will also complete a series of follow-up assessments at 3, 6, 9, 12 and 18-month time points. The follow-up assessments will take approximately 45 minutes to complete. Participants will receive their CleverCap and be asked to install the CleverCap app on their mobile phones. We estimate the CleverCap onboarding process will take approximately 10 minutes to complete. While all 
                    <PRTPAGE P="41037"/>
                    participants will be asked to install the app, use of the app after the initial install will be optional.
                </P>
                <P>For Aim 2 of the study, a subset (30 total) of the YMSM participants will be invited to participate in an in-depth interview. The interview will take approximately 90 minutes to complete. For the Aim 3 healthcare provider training, we will enroll a total of 20 healthcare providers. Over the 3-year data collection period, the estimated annual enrollment will be 7. It is expected that 50% of healthcare providers screened will meet study eligibility criteria and agree to join the study. Thus, we expect to screen 14 providers annually. The collection of initial screening information from the 14 providers will take approximately 10 minutes to complete. The collection of locator information from the 7 providers enrolled each year will take approximately 10 minutes to complete. Healthcare provider participants will be asked to complete an assessment before and after the PrEP training. The pre-training assessment and the post-training assessment are expected to take 30 minutes each to complete. Providers will also be asked to take part in a 60-minute interview.</P>
                <P>In addition to the training and provider-level assessments, every 6 months during the 36-month data collection period, each of the four participating clinic sites will complete the clinic assessment tool to describe PrEP services implementation at the facility level. The clinic assessment will be completed by a single member of the clinic staff at each clinic (four respondents total). Clinic-level assessments at baseline and study end are estimated to take 120 minutes to complete. Clinic-level assessments conducted at six-month intervals between the baseline and study end points are expected to take 90 minutes to complete.</P>
                <P>The total number of burden hours is 2,210 across 36 months of data collection. The total estimated annualized burden hours are 551. There are no costs to the participants other than their time to participate.</P>
                <GPOTABLE COLS="6" OPTS="L2,nj,i1" CDEF="s50,r50,11,10,12,10">
                    <TTITLE>Estimated Annualized Burden Hours</TTITLE>
                    <BOXHD>
                        <CHED H="1">Type of respondent</CHED>
                        <CHED H="1">Form name</CHED>
                        <CHED H="1">
                            Number of
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Number of
                            <LI>responses per </LI>
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Average 
                            <LI>burden per </LI>
                            <LI>response</LI>
                            <LI>(in hrs)</LI>
                        </CHED>
                        <CHED H="1">
                            Total
                            <LI>burden</LI>
                            <LI>(in hrs)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">General Public—Adults</ENT>
                        <ENT>Patient Screener (English/Spanish)</ENT>
                        <ENT>267</ENT>
                        <ENT>1</ENT>
                        <ENT>10/60</ENT>
                        <ENT>45</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">General Public—Adults</ENT>
                        <ENT>Patient Locator Form (English/Spanish)</ENT>
                        <ENT>134</ENT>
                        <ENT>1</ENT>
                        <ENT>10/60</ENT>
                        <ENT>23</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">General Public—Adults</ENT>
                        <ENT>Patient Baseline Assessment (English/Spanish)</ENT>
                        <ENT>134</ENT>
                        <ENT>1</ENT>
                        <ENT>45/60</ENT>
                        <ENT>101</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">General Public—Adults</ENT>
                        <ENT>Patient Quarterly Assessment (English/Spanish)</ENT>
                        <ENT>134</ENT>
                        <ENT>3</ENT>
                        <ENT>45/60</ENT>
                        <ENT>302</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">General Public—Adults</ENT>
                        <ENT>CleverCap App Setup (English/Spanish)</ENT>
                        <ENT>134</ENT>
                        <ENT>1</ENT>
                        <ENT>10/60</ENT>
                        <ENT>23</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">General Public—Adults</ENT>
                        <ENT>Patient Interview Guide (English/Spanish)</ENT>
                        <ENT>10</ENT>
                        <ENT>1</ENT>
                        <ENT>90/60</ENT>
                        <ENT>15</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Health Practitioners</ENT>
                        <ENT>Provider Screener</ENT>
                        <ENT>14</ENT>
                        <ENT>1</ENT>
                        <ENT>10/90</ENT>
                        <ENT>3</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Health Practitioners</ENT>
                        <ENT>Provider Locator Form</ENT>
                        <ENT>7</ENT>
                        <ENT>1</ENT>
                        <ENT>10/90</ENT>
                        <ENT>2</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Health Practitioners</ENT>
                        <ENT>Provider Pre-Training Assessment</ENT>
                        <ENT>7</ENT>
                        <ENT>1</ENT>
                        <ENT>30/60</ENT>
                        <ENT>4</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Health Practitioners</ENT>
                        <ENT>Provider Post-Training Assessment</ENT>
                        <ENT>7</ENT>
                        <ENT>1</ENT>
                        <ENT>30/60</ENT>
                        <ENT>4</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Health Practitioners</ENT>
                        <ENT>Provider Interview</ENT>
                        <ENT>7</ENT>
                        <ENT>1</ENT>
                        <ENT>60/60</ENT>
                        <ENT>7</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Health Practitioners</ENT>
                        <ENT>Clinic Assessment Baseline and Final</ENT>
                        <ENT>4</ENT>
                        <ENT>1</ENT>
                        <ENT>130/60</ENT>
                        <ENT>9</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01">Health Practitioners</ENT>
                        <ENT>Clinic Assessment Every Six Months</ENT>
                        <ENT>4</ENT>
                        <ENT>2</ENT>
                        <ENT>100/60</ENT>
                        <ENT>13</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT>551</ENT>
                    </ROW>
                </GPOTABLE>
                <SIG>
                    <NAME>Jeffrey M. Zirger,</NAME>
                    <TITLE>Lead, Information Collection Review Office, Office of Public Health Ethics and Regulations, Office of Science, Centers for Disease Control and Prevention.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13561 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4163-18-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Centers for Medicare and Medicaid Services</SUBAGY>
                <SUBJECT>Privacy Act of 1974; Matching Program</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Medicare &amp; Medicaid Services, Department of Health and Human Services</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of a new matching program.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with subsection (e)(12) of the Privacy Act of 1974, as amended, the Department of Health and Human Services (HHS), Centers for Medicare &amp; Medicaid Services (CMS) is providing notice of a new matching program between CMS and the Department of Veterans Affairs (VA), “Verification of Eligibility for Insurance Affordability Programs Under the Patient Protection and Affordable Care Act.”</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The deadline for comments on this notice is August 5, 2026. The re-established matching program will commence not sooner than 30 days after publication of this notice, provided no comments are received that warrant a change to this notice. The matching program will be conducted for an initial term of 18 months (from approximately May 15, 2026 to November 15, 2027) and within 3 months of expiration may be renewed for one additional year if the parties make no change to the matching program and certify that the program has been conducted in compliance with the matching agreement.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Interested parties may submit written comments on this notice, by mail or email, to the CMS Privacy Officer, Division of Security, Privacy Policy &amp; Oversight, Information Security &amp; Privacy Group, Office of Information Technology, Centers for Medicare &amp; Medicaid Services, Location: N1-14-56, 7500 Security Blvd., Baltimore, MD 21244-1850, to 
                        <E T="03">barbara.demopulos@cms.hhs.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        If you have questions about the matching program, you may contact Terrence Kane, Director, Division of Automated Verifications and SEP Policy, Marketplace Eligibility and Enrollment 
                        <PRTPAGE P="41038"/>
                        Group, Center for Consumer Information and Insurance Oversight, CMS, at (301) 492-4449 or by email at 
                        <E T="03">terrenc.kane@cms.hhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Privacy Act of 1974, as amended (5 U.S.C. 552a) provides certain protections for individuals applying for and receiving federal benefits. The law governs the use of computer matching by federal agencies when records in a system of records (meaning, federal agency records about individuals retrieved by name or other personal identifier) are matched with records of other federal or non-federal agencies. The Privacy Act requires agencies involved in a matching program to:</P>
                <P>1. Enter into a written agreement, which must be prepared in accordance with the Privacy Act, approved by the Data Integrity Board of each source and recipient federal agency, provided to Congress and the Office of Management and Budget (OMB), and made available to the public, as required by 5 U.S.C. 552a(o), (u)(3)(A), and (u)(4).</P>
                <P>2. Notify the individuals whose information will be used in the matching program that the information they provide is subject to verification through matching, as required by 5 U.S.C. 552a(o)(1)(D).</P>
                <P>3. Verify match findings before suspending, terminating, reducing, or making a final denial of an individual's benefits or payments or taking other adverse action against the individual, as required by 5 U.S.C. 552a(p).</P>
                <P>4. Report the matching program to Congress and the OMB, in advance and annually, as required by 5 U.S.C. 552a(o) (2)(A)(i), (r), and (u)(3)(D).</P>
                <P>
                    5. Publish advance notice of the matching program in the 
                    <E T="04">Federal Register</E>
                     as required by 5 U.S.C. 552a(e)(12).
                </P>
                <P>This matching program meets these requirements.</P>
                <SIG>
                    <NAME>Barbara Demopulos,</NAME>
                    <TITLE>CMS Privacy Act Officer, Division of Security, Privacy Policy &amp; Oversight, Information Security and Privacy Group,Office of Information Technology, Centers for Medicare &amp; Medicaid Services.</TITLE>
                </SIG>
                <P>
                    <E T="03">Participating Agencies:</E>
                     The Department of Health and Human Services (HHS), Centers for Medicare &amp; Medicaid Services (CMS) is the recipient agency, and the Department of Veterans Affairs (VA), is the source agency.
                </P>
                <P>
                    <E T="03">Authority for Conducting the Matching Program:</E>
                     The matching program is authorized under 42 U.S.C. 18001.
                </P>
                <P>
                    <E T="03">Purpose(s):</E>
                     The purpose of this matching program is to assist CMS in determining individuals' eligibility for Insurance Affordability Programs (IAPs). In this matching program, VHA provides CMS with data when State Administering Entities (AE) request it and VHA is authorized to release it, verifying whether an individual is enrolled in Minimum Essential Coverage (MEC) through a VHA Health Care Program. CMS makes the data provided by VHA available to the requesting AE through a data services hub (Hub) to verify an Applicant's enrollment in MEC to use in determining the enrollee's eligibility for financial assistance, Medicaid, the Children's Health Insurance Program (CHIP) and the Basic Health Program. CMS and AEs will use the VA's disability data for determining eligibility for advance payments of the premium tax credit (APTC) and cost-sharing reductions (CSRs). VHA health plans provide minimum essential coverage, and eligibility for such plans usually precludes eligibility for financial assistance in paying for private coverage. The data provided by VHA under this matching program will be used by CMS and AEs to authenticate identity, determine eligibility for financial assistance, and determine the amount of the financial assistance.
                </P>
                <P>
                    <E T="03">Categories of Individuals:</E>
                     The categories of individuals whose information is involved in the matching program are:
                </P>
                <P>• Veterans whose records at VHA match data provided to VHA by CMS (submitted by AEs) about individuals who are applying for or are enrolled in an insurance coverage plan through a federally-facilitated health insurance exchange.</P>
                <P>
                    <E T="03">Categories of Records:</E>
                     The categories of records used in this matching program are identity records and minimum essential coverage period records consisting of the following data elements:
                </P>
                <P>Data provided by CMS to VHA:</P>
                <P>a. First Name(required).</P>
                <P>b. Middle Name/Initial (if provided by applicant).</P>
                <P>c. Surname (Applicant's Last Name) (required).</P>
                <P>d. Date of Birth (required).</P>
                <P>e. Sex (required).</P>
                <P>f. SSN (required).</P>
                <P>g. Requested Qualified Health Plan (QHP) Coverage Effective Date (required).</P>
                <P>h. Requested QHP Coverage End Date (required).</P>
                <P>i. State Identification.</P>
                <P>j. Transaction ID(required).</P>
                <P>Data provided by VHA to CMS:</P>
                <P>a. SSN (required).</P>
                <P>b. Start/End Date{s) of enrollment period(s) (when match occurs).</P>
                <P>c. A blank date response when a non-match occurs.</P>
                <P>d. If CMS transmits request and a match is made, but VA's record contains a Date of Death, VA will respond in the same manner as a non-match response, with a blank date.</P>
                <P>e. Enrollment period(s) is/are defined as the timeframe during which the individual was enrolled in a VHA Health Care Program.</P>
                <P>Data provided from CMS to VBA:</P>
                <P>a. First Name (required).</P>
                <P>b. Last Name (required).</P>
                <P>c. Date of Birth (required)..</P>
                <P>d. Sex (required).</P>
                <P>e. Social Security Number (required unless address is provided).</P>
                <P>f. Street Address (required unless SSN is provided).</P>
                <P>g. City (required unless SSN is provided).</P>
                <P>h. State (required unless SSN is provided).</P>
                <P>i. Country (required unless SSN is provided).</P>
                <P>j. Zip Code (required unless SSN is provided).</P>
                <P>k. Middle Name (optional).</P>
                <P>l. Sex (optional).</P>
                <P>m. Mother's Maiden Name (optional).</P>
                <P>n. Home Phone Number (optional).</P>
                <P>o. Birth Place City (optional).</P>
                <P>p. Birth Place State (optional).</P>
                <P>q. Birth Place Country (optional) Data provided by VBA to CMS:</P>
                <P>a. Combined disability rating.</P>
                <P>b. Effective date for combined disability rating.</P>
                <P>c. Individual disability rating(s).</P>
                <P>d. Individual disability rating decision(s).</P>
                <P>e. Individual disability rating effective date(s).</P>
                <P>f. Individual disability rating end date(s).</P>
                <P>g. Individual disability rating percentage(s).</P>
                <P>h. Indicator of whether individual disability rating is static.</P>
                <P>i. Permanent and total service-connected status.</P>
                <P>j. Total Disability status individual unemployability status.</P>
                <P>
                    <E T="03">System(s) of Records:</E>
                     The data used in this matching program will be disclosed from the following systems of records, based on the routine uses identified:
                </P>
                <P>• Health Insurance Exchanges System (HIX), CMS System No. 09-70-0560, last published in full at 78 FR 63211 (Oct. 23, 2013), as amended at 83 FR 6591 (Feb. 14, 2018).</P>
                <P>
                    • Veterans and Beneficiaries Purchased Care Community Health Care Claims, Correspondence, Eligibility, Inquiry and Payment Files-VA,” System No. 54VA10, last fully published at 90 FR 4447354 (September 15, 2025).
                    <PRTPAGE P="41039"/>
                </P>
                <P>• Compensation, Pension, Education, and Vocational Rehabilitation and Employment Records—VA (58VA21/22/28), last published at 88 FR 61858.</P>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13572 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4120-03-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Centers for Medicare &amp; Medicaid Services</SUBAGY>
                <DEPDOC>[Document Identifier: CMS-10949 and CMS-10717]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Submission for OMB Review; Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Medicare &amp; Medicaid Services, Health and Human Services (HHS).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Centers for Medicare &amp; Medicaid Services (CMS) is announcing an opportunity for the public to comment on CMS' intention to collect information from the public. Under the Paperwork Reduction Act of 1995 (PRA), federal agencies are required to publish notice in the 
                        <E T="04">Federal Register</E>
                         concerning each proposed collection of information, including each proposed extension or reinstatement of an existing collection of information, and to allow a second opportunity for public comment on the notice. Interested persons are invited to send comments regarding the burden estimate or any other aspect of this collection of information, including the necessity and utility of the proposed information collection for the proper performance of the agency's functions, the accuracy of the estimated burden, ways to enhance the quality, utility, and clarity of the information to be collected, and the use of automated collection techniques or other forms of information technology to minimize the information collection burden.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments on the collection(s) of information must be received by the OMB desk officer by August 5, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Written comments and recommendations for the proposed information collection should be sent within 30 days of publication of this notice to 
                        <E T="03">www.reginfo.gov/public/do/PRAMain.</E>
                         Find this particular information collection by selecting “Currently under 30-day Review—Open for Public Comments” or by using the search function.
                    </P>
                    <P>
                        To obtain copies of a supporting statement and any related forms for the proposed collection(s) summarized in this notice, please access the CMS PRA website by copying and pasting the following web address into your web browser: 
                        <E T="03">https://www.cms.gov/Regulations-and-Guidance/Legislation/PaperworkReductionActof1995/PRA-Listing.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>William Parham at (410) 786-4669.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Under the Paperwork Reduction Act of 1995 (PRA) (44 U.S.C. 3501-3520), federal agencies must obtain approval from the Office of Management and Budget (OMB) for each collection of information they conduct or sponsor. The term “collection of information” is defined in 44 U.S.C. 3502(3) and 5 CFR 1320.3(c) and includes agency requests or requirements that members of the public submit reports, keep records, or provide information to a third party. Section 3506(c)(2)(A) of the PRA (44 U.S.C. 3506(c)(2)(A)) requires federal agencies to publish a 30-day notice in the 
                    <E T="04">Federal Register</E>
                     concerning each proposed collection of information, including each proposed extension or reinstatement of an existing collection of information, before submitting the collection to OMB for approval. To comply with this requirement, CMS is publishing this notice that summarizes the following proposed collection(s) of information for public comment.
                </P>
                <HD SOURCE="HD2">Information Collection</HD>
                <P>
                    1. 
                    <E T="03">Type of Information Collection Request:</E>
                     New collection (Request for a new OMB control number); 
                    <E T="03">Title of Information Collection:</E>
                     Rural Health Transformation Program Reporting; 
                    <E T="03">Use:</E>
                     On July 4, 2025, President Trump signed Public Law 119-21 which the Centers for Medicare &amp; Medicaid Services (CMS) refers to as the “Working Families Tax Cut” (WFTC) legislation, into law. The legislation authorized the Rural Health Transformation (RHT) Program, marking a significant federal investment of up to $50 billion over five years and is designed to empower as many as 50 State awardees to catalyze transformative improvements within their rural healthcare ecosystems. The principal objective is to enhance healthcare access, quality, and outcomes through innovative, system-wide change, thereby investing in the health of rural communities for future generations.
                </P>
                <P>Funding for approved State awardees is determined through a formal scoring and allocation process. The financial architecture of the program is composed of two primary streams: baseline funding, distributed equally among all awardees, and performance-based workload funding, which is allocated based on the scoring of specific rural and technical score factors within each State's application and their subsequent annual performance.</P>
                <P>
                    To ensure continued eligibility and funding, State awardees must adhere to key program requirements, including the submission of annual and quarterly reports. CMS will re-calculate each approved State's technical score and corresponding Workload funding amount for each subsequent budget period based on the information and data the approved State provides in the required annual reporting each year. In these reports, States will provide updates on programmatic milestones, report on performance and evaluation metrics, and detail the expenditure of funds. 
                    <E T="03">Form Number:</E>
                     CMS-10949 (OMB control number: 0938-TBD); 
                    <E T="03">Frequency:</E>
                     Quarterly and yearly; 
                    <E T="03">Affected Public:</E>
                     State, Local, or Tribal Governments; 
                    <E T="03">Number of Respondents:</E>
                     50; 
                    <E T="03">Total Annual Responses:</E>
                     200; 
                    <E T="03">Total Annual Hours:</E>
                     20,000. (For policy questions regarding this collection contact Anthony (Tony) DiFondi at 215-861-4318.)
                </P>
                <P>
                    2. 
                    <E T="03">Type of Information Collection Request:</E>
                     Revision of a currently approved collection; 
                    <E T="03">Title of Information Collection:</E>
                     Medicare Part C and Part D Program Audit and Industry-Wide Part C Timeliness Monitoring Project (TMP) Protocols; 
                    <E T="03">Use:</E>
                     CMS is responsible for overseeing the Medicare Advantage (MA) and Part D programs to ensure that beneficiaries receive appropriate and timely benefits, services, and drugs. Under Sections 1857(d) and 1860D-12 of the Social Security Act, and related regulations at 42 CFR 422.503, 422.504, 422.516, 423.504, and 423.505, CMS has the authority to inspect, evaluate, and monitor the benefits provided by Sponsoring organizations. To carry out this oversight, Sponsoring organizations must provide CMS with access to relevant records, documentation, and systems. They are also required to report information on service utilization and other data as requested by CMS to confirm ongoing compliance with program requirements. CMS uses the data collected by way of these audit protocols to thoroughly assess whether Sponsoring organizations are meeting specific federal requirements.
                </P>
                <P>
                    The information gathered during this program audit will be used by the Medicare Parts C and D Oversight and Enforcement Group (MOEG) within the Center for Medicare (CM) to assess Sponsoring organizations' compliance 
                    <PRTPAGE P="41040"/>
                    with Medicare program requirements. MOEG reviews submitted data and selected samples from that data to ensure appropriate enrollee access to benefits, services and drugs. Specifically, CMS reviews data to ensure Part D organizations are administering their formulary and transition benefit in accordance with their CMS-approved formulary; CMS reviews coverage requests and appeals to ensure regulatory requirements are followed when enrollees request services; and, if the audited MA organization offers a SNP, MOEG's review evaluates whether the SNP is coordinating care in accordance with CMS requirements. 
                    <E T="03">Form Number:</E>
                     CMS-10717 (OMB control number: 0938-1395); 
                    <E T="03">Frequency:</E>
                     Annually; 
                    <E T="03">Affected Public:</E>
                     Private sector, State, Local, or Tribal Governments, Federal Government, Business or other for-profits, Not-for-Profit Institutions; 
                    <E T="03">Number of Respondents:</E>
                     30; 
                    <E T="03">Total Annual Responses:</E>
                     30; 
                    <E T="03">Total Annual Hours:</E>
                     12,795. (For policy questions regarding this collection contact Caroline Zeman at 410-786-0116 or 
                    <E T="03">caroline.zeman@cms.hhs.gov.</E>
                    )
                </P>
                <SIG>
                    <NAME>William N. Parham, III,</NAME>
                    <TITLE>Director, Division of Information Collections and Regulatory Impacts, Office of Strategic Operations and Regulatory Affairs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13603 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4169-69-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. FDA-2026-N-2431]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Submission for Office of Management and Budget Review; Comment Request; Administrative Practices and Procedures; Formal Hearings</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Food and Drug Administration (FDA) is announcing that a proposed collection of information has been submitted to the Office of Management and Budget (OMB) for review and clearance under the Paperwork Reduction Act of 1995.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit written comments (including recommendations) on the collection of information by August 5, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        To ensure that comments on the information collection are received, OMB recommends that written comments be submitted to 
                        <E T="03">https://www.reginfo.gov/public/do/PRAMain.</E>
                         Find this particular information collection by selecting “Currently under Review—Open for Public Comments” or by using the search function. The OMB control number for this information collection is 0910-0191. Also include the FDA docket number found in brackets in the heading of this document.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Kelly Covington, Office of Operations, Food and Drug Administration, Three White Flint North, 10A-12M, 11601 Landsdown St., North Bethesda, MD 20852, 240-402-5661, 
                        <E T="03">PRAStaff@fda.hhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>In compliance with 44 U.S.C. 3507, FDA has submitted the following proposed collection of information to OMB for review and clearance.</P>
                <HD SOURCE="HD1">Administrative Practices and Procedures; Formal Hearings—21 CFR Parts 10, 12-16, and 19</HD>
                <HD SOURCE="HD2">OMB Control Number 0910-0191—Extension</HD>
                <P>This information collection supports Food and Drug Administration (FDA, the agency, us or we) regulations found in 21 CFR part 10, 21 CFR parts 12 through 16, and 21 CFR part 19 (21 CFR 10, 12-16, and 19), which implement general provisions of the Federal Food, Drug, and Cosmetic Act (FD&amp;C Act). The regulations were promulgated in accordance with the Administrative Procedures Act and establish administrative practice and procedures to give instructions to those conducting business with FDA. Regulations in part 10 (21 CFR part 10) describe general administrative practices and include content and format instructions on submitting information to the agency, petitions for agency action, and other topics such as the public calendar. Regulations in 21 CFR parts 12 through 16 cover formal evidentiary, public, and regulatory hearings. We also account for burden associated with waiver requests under 21 CFR part 10.19. Unless a waiver, suspension, or modification submitted under § 10.19 (21 CFR 10.19) is granted by the Commissioner of Food and Drugs (the Commissioner), the regulations in 21 CFR part 10 apply to all petitions, hearings, and other administrative proceedings and activities conducted by FDA. Although we have not received requests under § 10.19, to reflect the attendant burden resulting from submitting such a request, we provide an estimate of 1 response and 1 burden hour annually, as reflected in Question-12 of this supporting statement. Also, because most information associated with regulations in parts 12-16 is obtained during the conduct of an official administrative action as described under 5 CFR 1320.4, we only include burden associated with initiating hearings pursuant to the applicable regulations.</P>
                <P>The information collection also includes activities and burden associated with general meeting requests and correspondence submitted under section 10.65 (21 CFR 10.65), as well and general submissions associated with section 10.115—which provides for public participation in the development of agency guidance documents through requests to our Dockets Management Staff. Although most submissions and attendant burden associated with recommendations found in FDA guidance documents is accounted for in topic-specific and approved ICRs, here we account for burden associated with general public submissions as described in § 10.115(f)(3).</P>
                <P>
                    The information collection also includes burden associated with recommendations discussed in the guidance document entitled, “
                    <E T="03">Citizen Petitions and Petitions for Stay of Action Subject to Section 505(q) of the Federal Food, Drug, and Cosmetic Act.</E>
                    ” The guidance document communicates FDA's interpretation of section 505(q) of the Federal Food, Drug, and Cosmetic Act (FD&amp;C Act) (21 U.S.C. 355(q)): 
                    <E T="03">Petitions and Civil Actions Regarding Approval of Certain Applications.</E>
                     The guidance identifies and discusses submission elements including certification, as well as verification of supplemental information. It also addresses the relationship between the review of petitions and pending ANDAs, 505(b)(2) applications, and 351(k) applications for which a decision on approvability has not yet been made.
                </P>
                <P>
                    The information collection also includes burden associated with requests for FDA speakers. FDA receives thousands of requests each year from trade associations and industry-based groups for speakers to participate in external meetings, conferences, and workshops. To facilitate the processing of these requests and determine participation, we have designated contacts throughout the agency and have developed web-based request templates which can be found on our website at 
                    <E T="03">https://www.fda.gov/training-and-continuing-education/contacts-requesting-fda-speaker.</E>
                    <PRTPAGE P="41041"/>
                </P>
                <P>
                    In the 
                    <E T="04">Federal Register</E>
                     of April 7, 2026 (91 FR 17658), FDA published a 60-day notice requesting public comment on the proposed collection of information. Three comments were received. One comment was not responsive to the questions posed in § 1320.8(d). Two comments supported the collection of information, however, one commentor stated that our time estimates for citizen petitions seemed low. They also suggested our online submission system could be easier to use and that simple templates or examples would be helpful.
                </P>
                <P>FDA appreciates the comments. We base our estimates regarding citizen petitions on our historical experience. However, we will continue to monitor and make changes as evidence warrants. Currently, FDA provides a number of guidance documents and templates to assist with submissions:</P>
                <P>1. 21 CFR part 10.30—provides a template of the format and information needed to submit a citizen petition.</P>
                <P>
                    2. In the guidance document entitled, “
                    <E T="03">Citizen Petitions and Petitions for Stay of Action Subject to Section 505(q) of the Federal Food, Drug, and Cosmetic Act,</E>
                    ” the guidance identifies and discusses submission elements including certification, as well as verification of supplemental information.
                </P>
                <P>
                    3. A list of contacts and request templates can be found on our website at 
                    <E T="03">https://www.fda.gov/training-and-continuing-education/contacts-requesting-fda-speaker.</E>
                </P>
                <P>
                    4. Information regarding small business assistance can be found on our website at 
                    <E T="03">https://www.fda.gov/industry/small-business-assistance.</E>
                </P>
                <P>FDA estimates the burden of this collection of information as follows:</P>
                <GPOTABLE COLS="6" OPTS="L2,nj,i1" CDEF="s50,12,12,12,r50,12">
                    <TTITLE>
                        Table 1—Estimated Annual Reporting Burden 
                        <SU>1</SU>
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">21 CFR section</CHED>
                        <CHED H="1">
                            Number of
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Number of
                            <LI>responses per</LI>
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Total annual
                            <LI>responses</LI>
                        </CHED>
                        <CHED H="1">Average burden per response</CHED>
                        <CHED H="1">Total hours</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">10.19—request for waiver, suspension, or modification of requirements</ENT>
                        <ENT>2</ENT>
                        <ENT>1</ENT>
                        <ENT>2</ENT>
                        <ENT>1</ENT>
                        <ENT>2</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            10.30 and 10.31—citizen petitions and petitions related to ANDAs 
                            <SU>2</SU>
                             certain NDAs,
                            <SU>3</SU>
                             or certain BLAs 
                            <SU>4</SU>
                        </ENT>
                        <ENT>330</ENT>
                        <ENT>1</ENT>
                        <ENT>330</ENT>
                        <ENT>24</ENT>
                        <ENT>7,920</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">10.33—administrative reconsideration of action</ENT>
                        <ENT>13</ENT>
                        <ENT>1</ENT>
                        <ENT>13</ENT>
                        <ENT>10</ENT>
                        <ENT>130</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">10.35—administrative stay of action</ENT>
                        <ENT>28</ENT>
                        <ENT>1</ENT>
                        <ENT>28</ENT>
                        <ENT>10</ENT>
                        <ENT>280</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">10.65—meetings and correspondence</ENT>
                        <ENT>18</ENT>
                        <ENT>1</ENT>
                        <ENT>18</ENT>
                        <ENT>5</ENT>
                        <ENT>90</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">10.85—requests for Advisory opinions</ENT>
                        <ENT>3</ENT>
                        <ENT>1</ENT>
                        <ENT>3</ENT>
                        <ENT>16</ENT>
                        <ENT>48</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">10.115(f)(3)—submitting draft guidance proposals</ENT>
                        <ENT>1</ENT>
                        <ENT>1</ENT>
                        <ENT>1</ENT>
                        <ENT>4</ENT>
                        <ENT>4</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12.22—Filing objections and requests for a hearing on a regulation or order</ENT>
                        <ENT>15</ENT>
                        <ENT>1</ENT>
                        <ENT>15</ENT>
                        <ENT>20</ENT>
                        <ENT>300</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12.45—Notice of participation</ENT>
                        <ENT>1</ENT>
                        <ENT>1</ENT>
                        <ENT>1</ENT>
                        <ENT>3</ENT>
                        <ENT>3</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">External requests for FDA speakers</ENT>
                        <ENT>3,900</ENT>
                        <ENT>1</ENT>
                        <ENT>3,900</ENT>
                        <ENT>0.17 (10 minutes)</ENT>
                        <ENT>663</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>4,311</ENT>
                        <ENT/>
                        <ENT>9,440</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>1</SU>
                         There are no capital costs or operating and maintenance costs associated with this collection of information.
                    </TNOTE>
                    <TNOTE>
                        <SU>2</SU>
                         Abbreviated New Drug Applications.
                    </TNOTE>
                    <TNOTE>
                        <SU>3</SU>
                         New Drug Applications.
                    </TNOTE>
                    <TNOTE>
                        <SU>4</SU>
                         Biologics License Applications.
                    </TNOTE>
                </GPOTABLE>
                <P>Based on submissions to FDA's Division of Dockets Management since our last evaluation of the information collection, we have adjusted burden estimates associated with the individual activities that correspond to the applicable provisions. As a result, the information collection reflects an increase of 3,080 annual burden hours.</P>
                <SIG>
                    <NAME>Grace R. Graham,</NAME>
                    <TITLE>Deputy Commissioner for Policy, Legislation, and International Affairs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13534 Filed 7-2-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>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. FDA-2026-P-0525]</DEPDOC>
                <SUBJECT>Determination That VASOPRESSIN IN SODIUM CHLORIDE (vasopressin) 0.9%, Injection, 50 units/50 milliliters (1 unit/milliliters) Was Not Withdrawn From Sale for Reasons of Safety or Effectiveness</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Food and Drug Administration (FDA or Agency) has determined that VASOPRESSIN IN SODIUM CHLORIDE (vasopressin) 0.9%, injection, 50 units/50 milliliters (mL) (1 unit/mL) was not withdrawn from sale for reasons of safety or effectiveness. This determination will allow FDA to approve abbreviated new drug applications (ANDAs) for VASOPRESSIN IN SODIUM CHLORIDE (vasopressin) 0.9%, injection, 50 units/50 mL (1 unit/mL), if all other legal and regulatory requirements are met.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Molly Arndt, Center for Drug Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 51, Rm. 6281, Silver Spring, MD 20993-0002, 301-402-6919, 
                        <E T="03">molly.arndt@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. 
                    <PRTPAGE P="41042"/>
                    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>VASOPRESSIN IN SODIUM CHLORIDE (vasopressin) 0.9%, injection, 50 units/50 mL (1 unit/mL), is the subject of NDA 217766, held by Long Grove Pharmaceuticals, LLC, and initially approved on July 11, 2024. VASOPRESSIN IN SODIUM CHLORIDE 0.9% is indicated to increase blood pressure in adults with vasodilatory shock who remain hypotensive despite fluids and catecholamines.</P>
                <P>In a letter dated May 9, 2025, Long Grove Pharmaceuticals notified FDA that VASOPRESSIN IN SODIUM CHLORIDE 0.9% (vasopressin) injection, 50 units/50 mL (1 unit/mL), was being discontinued, and FDA moved the drug product to the “Discontinued Drug Product List” section of the Orange Book.</P>
                <P>Fresenius Kabi USA, LLC submitted a citizen petition dated January 15, 2026 (Docket No. FDA-2026-P-0525), under 21 CFR 10.30, requesting that the Agency determine whether VASOPRESSIN IN SODIUM CHLORIDE (vasopressin) 0.9%, injection, 50 units/50 mL (1 unit/mL), was 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 VASOPRESSIN IN SODIUM CHLORIDE 0.9% (vasopressin) .9%, injection, 50 units/50 mL (1 unit/mL) was not withdrawn for reasons of safety or effectiveness. The petitioner has identified no data or other information suggesting that VASOPRESSIN IN SODIUM CHLORIDE (vasopressin) 0.9%, injection, 50 units/50 mL (1 unit/mL), was withdrawn for reasons of safety or effectiveness. We have carefully reviewed our files for records concerning the withdrawal of VASOPRESSIN IN SODIUM CHLORIDE 0.9% (vasopressin), from sale. We have also independently evaluated relevant literature and data for possible postmarketing adverse events. We have reviewed the available evidence and determined that this drug product was not withdrawn from sale for reasons of safety or effectiveness.</P>
                <P>Accordingly, the Agency will continue to list VASOPRESSIN IN SODIUM CHLORIDE 0.9% (vasopressin), injection, 50 units/50 mL (1 unit/mL) in the “Discontinued Drug Product List” section of the Orange Book. The “Discontinued Drug Product List” delineates, among other items, drug products that have been discontinued from marketing for reasons other than safety or effectiveness. ANDAs that refer to VASOPRESSIN IN SODIUM CHLORIDE (vasopressin) 0.9%, injection, 50 units/50 mL (1 unit/mL) 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-13492 Filed 7-2-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>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. FDA-2026-N-2915]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Submission for Office of Management and Budget Review; Comment Request; Premarket Approval of Medical Devices</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Food and Drug Administration (FDA) is announcing that a proposed collection of information has been submitted to the Office of Management and Budget (OMB) for review and clearance under the Paperwork Reduction Act of 1995.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit written comments (including recommendations) on the collection of information by August 5, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        To ensure that comments on the information collection are received, OMB recommends that written comments be submitted to 
                        <E T="03">https://www.reginfo.gov/public/do/PRAMain.</E>
                         Find this particular information collection by selecting “Currently under Review—Open for Public Comments” or by using the search function. The OMB control number for this information collection is 0910-0231.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Amber Barrett, Office of Operations, Food and Drug Administration, Three White Flint North, 10A-12M, 11601 Landsdown St., North Bethesda, MD 20852, 301-796-8867, 
                        <E T="03">PRAStaff@fda.hhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>In compliance with 44 U.S.C. 3507, FDA has submitted the following proposed collection of information to OMB for review and clearance.</P>
                <HD SOURCE="HD1">Premarket Approval of Medical Devices</HD>
                <HD SOURCE="HD2">OMB Control Number 0910-0231—Extension</HD>
                <P>
                    This information collection supports implementation of statutory and regulatory requirements that govern premarket approval of medical devices. Premarket approval (PMA) is the FDA process of scientific and regulatory review to evaluate the safety and effectiveness of Class III medical devices. Class III devices are those that support or sustain human life, are of substantial importance in preventing impairment of human health, or which present a potential, unreasonable risk of 
                    <PRTPAGE P="41043"/>
                    illness or injury. Due to the level of risk associated with Class III devices, FDA has determined that general and special controls alone are insufficient to assure the safety and effectiveness of Class III devices. Therefore, these devices require a premarket approval (PMA) application under section 515 of the FD&amp;C Act (21 U.S.C. 360e) in order to obtain marketing approval. Please note that PMA requirements apply differently to pre-amendments devices, post amendments devices, and transitional class III devices and some Class III pre-amendment devices may require a Class III 510(k). See the PMA Historical Background Web page at 
                    <E T="03">https://www.fda.gov/medical-devices/premarket-approval-pma/pma-historical-background</E>
                     for additional information. Section 515A of the FD&amp;C Act (21 U.S.C. 360e-1) governs pediatric uses of devices.
                </P>
                <P>The PMA is the most stringent type of device marketing application required by FDA. Applicants must receive FDA approval of a PMA application prior to marketing the device. PMA approval is based on a determination that the PMA contains sufficient valid scientific evidence to assure that the device is safe and effective for its intended use(s). Respondents to the information collection are PMA applicants, or persons who own the rights, or otherwise have authorized access, to the data and other information to be submitted in support of FDA approval. This person may be an individual, partnership, corporation, association, scientific or academic establishment, government agency or organizational unit, or other legal entity. The applicant is often the inventor/developer and ultimately the manufacturer. A Class III device that fails to meet PMA requirements is considered to be adulterated under section 501(f) of the FD&amp;C Act (21 U.S.C. 351(f)) and may not be marketed.</P>
                <P>FDA regulations in part 814 (21 CFR part 814) implement section 515 and 515A of the FD&amp;C Act and establish procedures for the premarket approval of medical devices intended for human use, including the submission of information concerning use in pediatric patients. Regulations in part 814, subpart A (§§  814.1 to 814.19) set forth general provisions pertaining to the confidentiality of data and information submitted to FDA in a PMA, research conducted outside the United States, service of orders, and product development protocols. Provisions in part 814, subparts B and C (§§  814.20 to 814.47) establish format and content elements that must be included in an application, explain submission, and review schedules, and address the withdrawal and temporary suspension of a PMA. post approval requirements, including reports required under 21 CFR part 803 (medical device reporting), are covered in regulations in part 814, subpart E (§§  814.80 to 814.84). Burden attributable to information collection associated with regulations in part 814, subpart H (§§  814.100 to 814.126) pertaining to Humanitarian Use Devices is currently approved in OMB control number 0910-0332.</P>
                <P>
                    For operational efficiency, we are revising the information collection to include burden that may be associated with recommendations found in the Agency guidance document entitled, “Providing Information about Pediatric Uses of Medical Devices” (May 2014), currently approved in OMB control number 0910-0748. The guidance document describes how to compile and submit the readily available pediatric use information required under section 515A of the FD&amp;C Act. The guidance document is available for download from our website at 
                    <E T="03">https://www.fda.gov/regulatory-information/search-fda-guidance-documents/providing-information-about-pediatric-uses-medical-devices.</E>
                </P>
                <P>Relatedly, we are revising the information collection to include burden that may be associated with the submission of information on pediatric use of medical devices under section 515A of the FD&amp;C Act, also currently approved in OMB control number 0910-0748. Section 515A(a) of the FD&amp;C Act requires applicants who submit information to include readily available information providing a description of any pediatric subpopulations that suffer from the disease or condition that the device is intended to treat, diagnose, or cure, and the number of affected pediatric patients. This information allows FDA to track the number of approved devices for which there is a pediatric subpopulation that suffers from the disease or condition that the device is intended to treat, diagnose, or cure and the review time for each such device application.</P>
                <P>
                    We are also revising the information collection to include burden applicable to implementing requirements under section 402(j)(5)(B) of the Public Health Service (PHS) Act (42 U.S.C. 282(j)(5)(B)), and set forth in regulations at 42 CFR part 11 (see 81 FR 64982, September 21, 2016). Specifically, applications under sections 505, 515, or 520(m) of the FD&amp;C Act (21 U.S.C. 355, 360e, or 360j(m)), or under section 351 of the PHS Act (42 U.S.C. 262), or submission of a report under section 510(k) of the FD&amp;C Act, must be accompanied by a certification. Where available, such certification must include the appropriate National Clinical Trial numbers. We have developed Form FDA 3674 (“Certification of Compliance Under 42 U.S.C. 282(j)(5)(B), with Requirements of ClinicalTrials.gov Data Bank (includes instructions”), available at 
                    <E T="03">https://www.fda.gov/science-research/clinical-trials-and-human-subject-protection/clinical-trial-forms</E>
                     for respondents to submit the requisite information.
                </P>
                <P>
                    Respondents can make single submissions in an electronic format that includes eCopies, submissions submitted on CD, DVD, or flash drive and mailed to FDA and eSubmissions, submissions created using an electronic submission template (
                    <E T="03">e.g.,</E>
                     “electronic Submission Template and Resource” (eSTAR)). Consistent with our authority in section 745A(b) of the FD&amp;C Act (21 U.S.C. 379k-1(b)), and performance goals found in our current Medical Device User Fee Amendments Commitment Letter, we developed eSTAR for use through the Center for Devices and Radiological Health Customer Collaboration Portal. We use eSTAR as a tool to facilitate the preparation of submissions in electronic format (available on FDA's website at 
                    <E T="03">https://www.fda.gov/medical-devices/how-study-and-market-your-device/voluntary-estar-program</E>
                     and identified as Form FDA 4062 “Electronic Submission Template and Resource (eSTAR)” (for Non-In Vitro Diagnostic submissions) and form FDA 4078 “Electronic Submission Template and Resource (eSTAR)” (for In Vitro Diagnostic submissions)). We believe respondents' use of eSTAR will significantly reduce burden attendant to application submissions by providing a uniform format for requisite elements and by enhancing user interface through the use of modernized technology.
                </P>
                <P>
                    In the 
                    <E T="04">Federal Register</E>
                     of April 10, 2026 (91 FR 18468), FDA published a 60-day notice requesting public comment on the proposed collection of information. No comments were received.
                </P>
                <P>
                    FDA estimates the burden of this collection of information as follows:
                    <PRTPAGE P="41044"/>
                </P>
                <GPOTABLE COLS="6" OPTS="L2,nj,p7,7/8,i1" CDEF="s50,12,12,12,xs100,12">
                    <TTITLE>
                        Table 1—Estimated Annual Reporting Burden
                        <SU>1</SU>
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">Activity/21 CFR or FD&amp;C Act section</CHED>
                        <CHED H="1">
                            No. of
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            No. of
                            <LI>responses per respondent</LI>
                        </CHED>
                        <CHED H="1">Total annual responses</CHED>
                        <CHED H="1">Average burden per response (hours)</CHED>
                        <CHED H="1">Total hours</CHED>
                    </BOXHD>
                    <ROW EXPSTB="05" RUL="s">
                        <ENT I="21">
                            <E T="02">Premarket Approval Submissions (“traditional” and eSTAR preparation; eCopy submission):</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="21">
                            <E T="02">21 CFR Part 814, Premarket Approval of Medical Devices</E>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Subpart A—General:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Research conducted outside the United States (814.15(b))</ENT>
                        <ENT>18</ENT>
                        <ENT>1</ENT>
                        <ENT>18</ENT>
                        <ENT>2</ENT>
                        <ENT>36</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Subpart B—Premarket Approval Application (PMA)</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">PMA application (814.20)</ENT>
                        <ENT>61</ENT>
                        <ENT>1</ENT>
                        <ENT>61</ENT>
                        <ENT>654.6 (654 hours, 38 minutes)</ENT>
                        <ENT>39,931</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Information on clinical investigations conducted outside the United States (814.20(b)(6)(ii)(C))</ENT>
                        <ENT>18</ENT>
                        <ENT>1</ENT>
                        <ENT>18</ENT>
                        <ENT>0.5 (30 minutes)</ENT>
                        <ENT>9</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">PMA amendments and resubmitted PMAs (814.37(a)-(c) and (e))</ENT>
                        <ENT>1,125</ENT>
                        <ENT>4</ENT>
                        <ENT>4,500</ENT>
                        <ENT>167</ENT>
                        <ENT>751,500</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">PMA supplements (814.39(a))</ENT>
                        <ENT>598</ENT>
                        <ENT>3</ENT>
                        <ENT>1,794</ENT>
                        <ENT>0.983 (59.11 minutes)</ENT>
                        <ENT>1,764</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Special PMA supplement—changes being affected (814.39(d))</ENT>
                        <ENT>85</ENT>
                        <ENT>2</ENT>
                        <ENT>170</ENT>
                        <ENT>6</ENT>
                        <ENT>1,020</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="03">30-day notice (814.39(f))</ENT>
                        <ENT>1,499</ENT>
                        <ENT>15</ENT>
                        <ENT>22,485</ENT>
                        <ENT>16</ENT>
                        <ENT>359,760</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">Subtotal subpart B</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT>1,153,984</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Subpart C—FDA Action on a PMA:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Panel of experts request (814.42 and 515(c)(3) of the FD&amp;C Act)</ENT>
                        <ENT>4</ENT>
                        <ENT>1</ENT>
                        <ENT>4</ENT>
                        <ENT>30</ENT>
                        <ENT>120</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Subpart E—Postapproval Requirements:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Postapproval requirements (814.82(a)(9))</ENT>
                        <ENT>14</ENT>
                        <ENT>1</ENT>
                        <ENT>14</ENT>
                        <ENT>135</ENT>
                        <ENT>1890</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="03">Periodic reports (814.84(b))</ENT>
                        <ENT>860</ENT>
                        <ENT>2</ENT>
                        <ENT>1,720</ENT>
                        <ENT>10</ENT>
                        <ENT>17,200</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="05">Subtotal subpart E</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT>19,090</ENT>
                    </ROW>
                    <ROW EXPSTB="05" RUL="s">
                        <ENT I="21">
                            <E T="02">42 CFR part 11, Clinical Trials Registration and Results Information Submission, subparts D and E; and FDA Guidance “Form FDA 3674—Certifications To Accompany Drug, Biological Product, and Device Applications/Submissions”</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00" RUL="s">
                        <ENT I="01">Certification to accompany PMA submissions (Form FDA 3674)</ENT>
                        <ENT>61</ENT>
                        <ENT>1</ENT>
                        <ENT>61</ENT>
                        <ENT>0.75 (45 minutes)</ENT>
                        <ENT>46</ENT>
                    </ROW>
                    <ROW EXPSTB="05" RUL="s">
                        <ENT I="21">
                            <E T="02">FD&amp;C Act section 515A Pediatric Uses of Devices and FDA Guidance “Providing Information about Pediatric Uses of Medical Devices”:</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">Pediatric information in a PMA, PDP, or PMA supplement</ENT>
                        <ENT>659</ENT>
                        <ENT>6</ENT>
                        <ENT>3,954</ENT>
                        <ENT>2.10 (2 hours, 6 minutes)</ENT>
                        <ENT>8,303</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Pediatric use information outside approved indication</ENT>
                        <ENT>6</ENT>
                        <ENT>1</ENT>
                        <ENT>6</ENT>
                        <ENT>0.5 (30 minutes)</ENT>
                        <ENT>3</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="05">Subtotal</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT>8,306</ENT>
                    </ROW>
                    <ROW EXPSTB="05" RUL="s">
                        <ENT I="21">
                            <E T="02">Premarket Approval Submissions (eSTAR preparation):</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00" RUL="n,s">
                        <ENT I="01">eSTAR setup</ENT>
                        <ENT>1,529</ENT>
                        <ENT>6</ENT>
                        <ENT>9,174</ENT>
                        <ENT>0.08 (5 minutes)</ENT>
                        <ENT>734</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="07">Total</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT>1,182,316</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>1</SU>
                         There are no capital costs or operating and maintenance costs associated with this collection of information.
                    </TNOTE>
                </GPOTABLE>
                <P>Our estimate is based on the annual rate of receipt of PMA submissions, including PDPs and PMA supplements, for fiscal years 2022 through 2024 and our expectation of submissions to come in the next few years. We also account for referrals of PMAs to a panel for review, as provided for under §  814.44(a). FDA may refer the PMA to a panel on its own initiative, and will do so upon request of an applicant, unless FDA determines that the application substantially duplicates information previously reviewed by a panel. We have adjusted our figures to reflect an overall decrease, which we attribute to respondents' use of modernized submission technologies including eSTAR. At the same time, we include in our estimate an initial burden attributable to respondents who need to set up an eSTAR account for the first time.</P>
                <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s100,12C,12C,12C,12C,12C">
                    <TTITLE>
                        Table 2—Estimated Annual Recordkeeping Burden 
                        <SU>1</SU>
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">Number of recordkeepers</CHED>
                        <CHED H="1">Number of recordkeepers</CHED>
                        <CHED H="1">Number of recordkeepers</CHED>
                        <CHED H="1">Number of recordkeepers</CHED>
                        <CHED H="1">
                            Average 
                            <LI>burden per </LI>
                            <LI>recordkeeping</LI>
                        </CHED>
                        <CHED H="1">Total hours</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">860</ENT>
                        <ENT>860</ENT>
                        <ENT>860</ENT>
                        <ENT>860</ENT>
                        <ENT>17</ENT>
                        <ENT>29,240</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>1</SU>
                         There are no capital costs or operating and maintenance costs associated with this collection of information.
                    </TNOTE>
                </GPOTABLE>
                <P>
                    The regulations require the maintenance of records, which are used to trace patients, and the organization and indexing of records into identifiable files to ensure a device's continued safety and effectiveness. These records are required of all applicants who have an approved PMA. Currently there are 860 active PMAs that could be subject to these requirements, based on FDA data, and approximately 33 new PMAs are approved each year. We estimate our annual recordkeeping burden based on an average of 860 PMA holders. The applicant determines which records should be maintained during product development to document and/or substantiate the device's safety and 
                    <PRTPAGE P="41045"/>
                    effectiveness. Records required under 21 CFR part 820 may be relevant to a PMA review and may be submitted as part of an application. In individual instances, records may be required as conditions of approval to ensure the device's continuing safety and effectiveness.
                </P>
                <P>The overall burden increase of approximately 244% for reporting and 212% for recordkeeping represents a substantial change in the estimated regulatory burden for the PMA program. The increases are driven primarily by changes in estimated submission frequency rather than changes in the number of regulated entities or per-response burden estimates. The most significant factor is the dramatic increase in responses per respondent across multiple categories, particularly for 30-day notices (15× increase), PMA amendments (4× increase), pediatric information (6× increase), and eSTAR setup (6× increase). These changes suggest that the current estimates better capture the actual submission patterns and regulatory interactions that occur throughout the lifecycle of approved medical devices, reflecting more frequent modifications, updates, and communications between industry and FDA than were captured in the previous estimates based on 2019-2021 data.</P>
                <SIG>
                    <NAME>Grace R. Graham,</NAME>
                    <TITLE>Deputy Commissioner for Policy, Legislation, and International Affairs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13519 Filed 7-2-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>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. FDA-2026-N-6809]</DEPDOC>
                <SUBJECT>Endo Operations Limited, et al.; Withdrawal of Approval of 34 New Drug Applications</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Food and Drug Administration (FDA or Agency) is withdrawing approval of 34 new drug applications (NDAs) from multiple applicants. The applicants notified the Agency in writing that the drug products were no longer marketed and requested that the approval of the applications be withdrawn.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Approval is withdrawn as of August 5, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Kimberly Lehrfeld, Center for Drug Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 51, Rm. 6250, Silver Spring, MD 20993-0002, 301-796-3137, 
                        <E T="03">Kimberly.Lehrfeld@fda.hhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The applicants listed in table 1 have informed FDA that these drug products are no longer marketed and have requested that FDA withdraw approval of the applications under the process in § 314.150(c) (21 CFR 314.150(c)). The applicants have also, by their requests, waived their opportunity for a hearing. Withdrawal of approval of an application or abbreviated application under § 314.150(c) is without prejudice to refiling.</P>
                <GPOTABLE COLS="3" OPTS="L2,nj,i1" CDEF="xs66,r100,r100">
                    <TTITLE>Table 1—NDAs for Which Approval Is Withdrawn</TTITLE>
                    <BOXHD>
                        <CHED H="1">Application No.</CHED>
                        <CHED H="1">Drug</CHED>
                        <CHED H="1">Applicant</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">NDA 007337</ENT>
                        <ENT>
                            Percodan (aspirin; oxycodone hydrochloride (HCl)) Tablets, 325 milligrams (mg); 4.8355 mg
                            <LI O="xl">Percodan (aspirin; oxycodone HCl; oxycodone terephthalate) Tablets, 325 mg; 4.5 mg; 0.38 mg.</LI>
                        </ENT>
                        <ENT>Endo Operations Limited c/o Endo USA, Inc., 9 Great Valley Parkway, Malvern, PA 19355.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Percodan-Demi (aspirin; oxycodone HCl; oxycodone terephthalate) Tablets, 325 mg; 4.5 mg; 0.19 mg</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 017376</ENT>
                        <ENT>
                            Septra (sulfamethoxazole; trimethoprim) Tablets, 80 mg; 400 mg
                            <LI O="xl">Septra DS (sulfamethoxazole; trimethoprim) Tablets, 160 mg; 800 mg.</LI>
                        </ENT>
                        <ENT>Monarch Pharmaceuticals, LLC c/o Pfizer Inc., 66 Hudson Blvd. East, New York, NY 10001.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 017994</ENT>
                        <ENT>Psorcon E (diflorasone diacetate) Ointment, 0.05%</ENT>
                        <ENT>Pfizer Inc., 66 Hudson Blvd. East, New York, NY 10001.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 018701</ENT>
                        <ENT>Haldol (haloperidol decanoate) Injectable, equivalent to (EQ) 50 mg base/milliliter (mL) and EQ 100 mg base/mL</ENT>
                        <ENT>Janssen Pharmaceuticals, Inc., c/o Janssen Research and Development, 920 U.S. Highway 202, P.O. Box 300, Raritan NJ 08869-0602.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 019151</ENT>
                        <ENT>Rythmol (propafenone HCl) Tablets, 150 mg, 225 mg, and 300 mg</ENT>
                        <ENT>GlaxoSmithKline LLC, 2929 Walnut St., Suite 1700, Philadelphia, PA 19104.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 019260</ENT>
                        <ENT>Psorcon (diflorasone diacetate) Ointment, 0.05%</ENT>
                        <ENT>Pfizer Inc., 66 Hudson Blvd. East, New York, NY 10001.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 019795</ENT>
                        <ENT>Condylox (podofilox) Solution, 0.5%</ENT>
                        <ENT>Teva Branded Pharmaceutical Products R&amp;D LLC, 145 Brandywine Pkwy., West Chester, PA 19380.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 020140</ENT>
                        <ENT>Fusilev (levoleucovorin calcium) Powder, EQ 50 mg base/vial, EQ 175 mg base/17.5 mL (EQ 10 mg base/mL), and EQ 250 mg base/25 mL (EQ 10 mg base/mL)</ENT>
                        <ENT>Acrotech Biopharma Inc., 279 Princeton Hightstown Rd., East Windsor, NJ 08520.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 020337</ENT>
                        <ENT>Temovate (clobetasol propionate) Gel, 0.05%</ENT>
                        <ENT>Fougera Pharmaceuticals LLC, 60 Baylis Rd., P.O. Box 2006, Melville, NY 11747.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 020490</ENT>
                        <ENT>Alphagan (brimonidine tartrate) Solution/Drops, 0.5%</ENT>
                        <ENT>Allergan, Inc., 2525 Dupont Dr., P.O. Box 19534, Irvine, CA 92623-9534.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 020579</ENT>
                        <ENT>Flomax (tamsulosin HCl) Capsule, 0.4 mg</ENT>
                        <ENT>Sanofi-Aventis U.S. LLC, 100 Morris Ave., Morristown, NJ 07960.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 020657</ENT>
                        <ENT>Sporanox (itraconazole) oral solution, 10 mg/ml</ENT>
                        <ENT>Janssen Pharmaceuticals, Inc., 1125 Trenton-Harbourton Rd., Titusville, NJ 08560.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 021040</ENT>
                        <ENT>Prefest (estradiol 1mg and estradiol; norgestimate 1 mg; 0.09 mg), Tablets</ENT>
                        <ENT>Teva Women's Health, Inc., 145 Brandywine Pkwy., West Chester, PA 19380.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 021292</ENT>
                        <ENT>Euthyrox (levothyroxine sodium) Tablets, 0.025 mg, 0.05 mg, 0.075 mg, 0.088 mg, 0.1 mg, 0.112 mg, 0.125 mg, 0.137 mg, 0.15 mg, 0.175 mg, 0.2 mg, and 0.3 mg</ENT>
                        <ENT>EMD Serono, Inc. c/o ICON Clinical Research LLC, 731 Arbor Way, Suite 100, Blue Bell, PA 19422.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 021416</ENT>
                        <ENT>Rythmol SR (propafenone HCl) Extended-Release Capsules, 225 mg, 325 mg, and 425 mg.</ENT>
                        <ENT>GlaxoSmithKline LLC, 2929 Walnut St., Suite 1700, Philadelphia, PA 19104.</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="41046"/>
                        <ENT I="01">NDA 021481</ENT>
                        <ENT>Fuzeon (enfuviritide) Injectable, 90 mg/vial.</ENT>
                        <ENT>Hoffmann-La Roche Inc. c/o Genentech, Inc., 1 DNA Way, South San Francisco, CA 94080.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 021548</ENT>
                        <ENT>Lexivia (fosamprenavir calcium) Tablet, EQ 700 mg base.</ENT>
                        <ENT>Viiv Healthcare Co., 410 Blackwell St., Durham, NC 27701.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 021606</ENT>
                        <ENT>Zemplar (paricalcitol) Capsules, 1 microgram (mcg), 2 mcg, and 4 mcg</ENT>
                        <ENT>AbbVie Inc., 1 N Waukegan Rd., North Chicago, IL 60064.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 021656</ENT>
                        <ENT>TriCor (fenofibrate) Tablets, 48 mg and 145 mg</ENT>
                        <ENT>AbbVie Inc., 1 N Waukegan Rd., North Chicago, IL 60064.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 021779</ENT>
                        <ENT>Ventavis (iloprost) Solution, 10 mcg/mL (10 mcg/mL), 20 mcg/2 mL (10 mcg/mL) and 20 mcg/mL (20 mcg/mL)</ENT>
                        <ENT>Actelion Pharmaceuticals US, Inc., 1125 Trenton-Harbourton Rd., Titusville, NJ 08560.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 021947</ENT>
                        <ENT>Fentora (fentanyl citrate) Tablets, EQ 0.1 mg base, EQ 0.2 mg base, EQ 0.3 mg base, EQ 0.4 mg base, EQ 0.6 mg base, and EQ 0.8 mg base</ENT>
                        <ENT>Cephalon LLC, a wholly owned subsidiary of Teva Pharmaceuticals USA Inc., 145 Brandywine Pkwy., West Chester, PA 19380.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 022116</ENT>
                        <ENT>Lexivia (fosamprenavir calcium) Suspension, EQ 50 mg base/mL</ENT>
                        <ENT>Viiv Healthcare Co., 410 Blackwell St., Durham, NC 27701.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 022206</ENT>
                        <ENT>Rapaflo (silodosin) Capsules, 4 mg and 8 mg</ENT>
                        <ENT>AbbVie Inc., 1 N Waukegan Rd., North Chicago, IL 60064.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 022224</ENT>
                        <ENT>Trilipix (choline fenofibrate) Delayed-Release Capsules, EQ 45 mg fenofibric acid and EQ 135 mg fenofibric acid</ENT>
                        <ENT>AbbVie Inc., 1 N Waukegan Rd., North Chicago, IL 60064.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 022511</ENT>
                        <ENT>Vimovo (esomeprazole magnesium; naproxen) Delayed-Release Tablets, EQ 20 mg base; 375 mg, and EQ 20 mg base; 500 mg</ENT>
                        <ENT>Horizon Therapeutics USA, Inc., 1 Horizon Way, Deerfield, IL 60015.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 050467</ENT>
                        <ENT>Doxorubicin Hydrochloride (doxorubicin HCl) Injectable, 10 mg/vial, 20 mg/vial, 50 mg/vial, and 150 mg/vial</ENT>
                        <ENT>Pfizer Inc., 66 Hudson Blvd. East, New York, NY 10001.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 201194</ENT>
                        <ENT>Oxycodone Hydrocholoride (oxycodone HCl) Solution, 5 mg/5 mL</ENT>
                        <ENT>VistaPharm, LLC, 20 Waterview Blvd., Suite 303, Parsippany, NJ 07054.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 202020</ENT>
                        <ENT>Rayos (prednisone) Delayed-Release Tablets, 1 mg, 2 mg, and 5 mg</ENT>
                        <ENT>Horizon Therapeutics USA, Inc., 1 Horizon Way, Deerfield, IL 60015.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 204623</ENT>
                        <ENT>Pennsaid (diclofenac sodium) Solution, 2%</ENT>
                        <ENT>Horizon Therapeutics Ireland DAC c/o Horizon Therapeutics USA, Inc., 1 Horizon Way, Deerfield, IL 60015.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 204803</ENT>
                        <ENT>Posimir (bupivacaine) Solution, 660 mg/5 mL (132 mg/mL)</ENT>
                        <ENT>Innocoll Pharmaceuticals Limited c/o Allucent, 2000 Centregreen Way, Suite 300, Cary, NC 27513.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 206030</ENT>
                        <ENT>Carnexiv (carbamazepine) Solution, 200 mg/20 mL (10 mg/mL)</ENT>
                        <ENT>Lundbeck Pharmaceuticals LLC, 6 Pkwy. North, Suite 400, Deerfield, IL 60015.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 209128</ENT>
                        <ENT>Dsuvia (sufentanil citrate) Tablet, EQ 0.03 mg base</ENT>
                        <ENT>Vertical Pharmaceuticals, LLC, 1880 McFarland Pkwy., Suite 110B, Alpharetta, GA 30005.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 209511</ENT>
                        <ENT>Xaracoll (bupivacaine HCl) Implant, 100 mg</ENT>
                        <ENT>Innocoll Pharmaceuticals Limited c/o Allucent, 2000 Centregreen Way, Suite 300, Cary, NC 27513.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 211280</ENT>
                        <ENT>Reyvow (lasmiditan succinate) Tablets, EQ 50 mg base, EQ 100 mg base, and EQ 200 mg base</ENT>
                        <ENT>Eli Lilly and Company, Lilly Corporate Center, Drop Code 2543, Indianapolis, IN 46285.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>Therefore, approval of the applications listed in table 1, and all amendments and supplements thereto, is hereby withdrawn as of August 5, 2026. Approval of each entire application is withdrawn, including any strengths and dosage forms included in the application but inadvertently missing from table 1. Introduction or delivery for introduction into interstate commerce of products listed in table 1 without an approved NDA violates sections 505(a) and 301(d) of the Federal Food, Drug, and Cosmetic Act (21 U.S.C. 355(a) and 331(d)). Drug products that are listed in table 1 that are in inventory on August 5, 2026 may continue to be dispensed until the inventories have been depleted or the drug products have reached their expiration dates or otherwise become violative, whichever occurs first.</P>
                <SIG>
                    <NAME>Grace R. Graham,</NAME>
                    <TITLE>Deputy Commissioner for Policy, Legislation, and International Affairs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13616 Filed 7-2-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>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. FDA-2026-N-6667]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Proposed Collection; Comment Request; Biologics License Applications, Procedures and Requirements</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Food and Drug Administration (FDA or Agency) is announcing an opportunity for public comment on the proposed collection of certain information by the Agency. Under the Paperwork Reduction Act of 1995 (PRA), Federal Agencies are required to publish notice in the 
                        <E T="04">Federal Register</E>
                         concerning each proposed collection of information, including each proposed extension of an existing collection of information, and to allow 60 days for public comment in response to the notice. This notice solicits comments on information collection activities associated with Biologics License Applications, Procedures and Requirements.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Either electronic or written comments on the collection of information must be submitted by September 4, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may submit comments as follows. Please note that late, untimely filed comments will not be considered. The 
                        <E T="03">https://www.regulations.gov</E>
                         electronic filing system will accept comments until 11:59 p.m. Eastern Time at the end of September 4, 2026. Comments received by mail/hand delivery/courier (for written/paper submissions) will be considered timely if they are received on or before that date.
                    </P>
                </ADD>
                <HD SOURCE="HD2">Electronic Submissions</HD>
                <P>Submit electronic comments in the following way:</P>
                <P>
                    • 
                    <E T="03">Federal eRulemaking Portal:</E>
                      
                    <E T="03">https://www.regulations.gov.</E>
                     Follow the instructions for submitting comments. 
                    <PRTPAGE P="41047"/>
                    Comments submitted electronically, including attachments, to 
                    <E T="03">https://www.regulations.gov</E>
                     will be posted to the docket unchanged. Because your comment will be made public, you are solely responsible for ensuring that your comment does not include any confidential information that you or a third party may not wish to be posted, such as medical information, your or anyone else's Social Security number, or confidential business information, such as a manufacturing process. Please note that if you include your name, contact information, or other information that identifies you in the body of your comments, that information will be posted on 
                    <E T="03">https://www.regulations.gov.</E>
                </P>
                <P>• If you want to submit a comment with confidential information that you do not wish to be made available to the public, submit the comment as a written/paper submission and in the manner detailed (see “Written/Paper Submissions” and “Instructions”).</P>
                <HD SOURCE="HD2">Written/Paper Submissions</HD>
                <P>Submit written/paper submissions as follows:</P>
                <P>
                    • 
                    <E T="03">Mail/Hand Delivery/Courier (for written/paper submissions)</E>
                    : Dockets Management Staff (HFA-305), Food and Drug Administration, 5630 Fishers Lane, Rm. 1061, Rockville, MD 20852.
                </P>
                <P>• For written/paper comments submitted to the Dockets Management Staff, FDA will post your comment, as well as any attachments, except for information submitted, marked and identified, as confidential, if submitted as detailed in “Instructions.”</P>
                <P>
                    <E T="03">Instructions:</E>
                     All submissions received must include the Docket No. FDA-2026-N-6667 for “Agency Information Collection Activities; Proposed Collection; Comment Request; Biologics License Applications, Procedures and Requirements.” Received comments, those filed in a timely manner (see 
                    <E T="02">ADDRESSES</E>
                    ), will be placed in the docket and, except for those submitted as “Confidential Submissions,” publicly viewable at 
                    <E T="03">https://www.regulations.gov</E>
                     or at the Dockets Management Staff between 9 a.m. and 4 p.m., Monday through Friday, 240-402-7500.
                </P>
                <P>
                    • Confidential Submissions—To submit a comment with confidential information that you do not wish to be made publicly available, submit your comments only as a written/paper submission. You should submit two copies total. One copy will include the information you claim to be confidential with a heading or cover note that states “THIS DOCUMENT CONTAINS CONFIDENTIAL INFORMATION.” The Agency will review this copy, including the claimed confidential information, in its consideration of comments. The second copy, which will have the claimed confidential information redacted/blacked out, will be available for public viewing and posted on 
                    <E T="03">https://www.regulations.gov.</E>
                     Submit both copies to the Dockets Management Staff. If you do not wish your name and contact information to be made publicly available, you can provide this information on the cover sheet and not in the body of your comments and you must identify this information as “confidential.” Any information marked as “confidential” will not be disclosed except in accordance with 21 CFR 10.20 and other applicable disclosure law. For more information about FDA's posting of comments to public dockets, see 80 FR 56469, September 18, 2015, or access the information at: 
                    <E T="03">https://www.govinfo.gov/content/pkg/FR-2015-09-18/pdf/2015-23389.pdf.</E>
                </P>
                <P>
                    <E T="03">Docket:</E>
                     For access to the docket to read background documents or the electronic and written/paper comments received, go to 
                    <E T="03">https://www.regulations.gov</E>
                     and insert the docket number, found in brackets in the heading of this document, into the “Search” box and follow the prompts and/or go to the Dockets Management Staff, 5630 Fishers Lane, Rm. 1061, Rockville, MD 20852, 240-402-7500.
                </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Domini Bean, Office of Operations, Food and Drug Administration, Three White Flint North, 10A-12M, 11601 Landsdown St., North Bethesda, MD 20852, 301-796-5733, 
                        <E T="03">PRAStaff@fda.hhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Under the PRA (44 U.S.C. 3501-3521), Federal Agencies must obtain approval from the Office of Management and Budget (OMB) for each collection of information they conduct or sponsor. “Collection of information” is defined in 44 U.S.C. 3502(3) and 5 CFR 1320.3(c) and includes Agency requests or requirements that members of the public submit reports, keep records, or provide information to a third party. Section 3506(c)(2)(A) of the PRA (44 U.S.C. 3506(c)(2)(A)) requires Federal Agencies to provide a 60-day notice in the 
                    <E T="04">Federal Register</E>
                     concerning each proposed collection of information, including each proposed extension of an existing collection of information, before submitting the collection to OMB for approval. To comply with this requirement, FDA is publishing notice of the proposed collection of information set forth in this document.
                </P>
                <P>With respect to the following collection of information, FDA invites comments on these topics: (1) whether the proposed collection of information is necessary for the proper performance of FDA's functions, including whether the information will have practical utility; (2) the accuracy of FDA's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used; (3) ways to enhance the quality, utility, and clarity of the information to be collected; and (4) ways to minimize the burden of the collection of information on respondents, including through the use of automated collection techniques, when appropriate, and other forms of information technology.</P>
                <HD SOURCE="HD1">Biologics License Applications (BLAs), Procedures and Requirements</HD>
                <HD SOURCE="HD1">OMB Control Number 0910-0338—Extension</HD>
                <P>
                    This information collection helps support implementation of statutory and regulatory requirements under the Public Health Service Act (PHS) and the Federal Food, Drug, and Cosmetic Act (FD&amp;C Act) that govern biologics product licensing. The Food and Drug Administration (FDA) has promulgated regulations in 21 CFR parts 600-680 setting forth applicable standards and procedures that include associated reporting, recordkeeping, and disclosure requirements. Respondents to the information collection are persons or entities who engage in manufacture of biologics. Respondents to this collection of information are licensed manufacturers of biological products. Based on existing data, we estimate there are 371 such respondents. We provide relevant information and resources on our website at 
                    <E T="03">https://www.fda.gov/vaccines-blood-biologics/development-approval-process-cber/biologics-license-applications-bla-process-cber</E>
                     regarding biologics license applications (BLAs).
                </P>
                <P>
                    Regulations in 21 CFR part 600, subparts A through C (21 CFR 600-600.21), and regulations in 21 CFR 601, subpart A (21 CFR 601.2-21 CFR 601.9) cover genera provisions and prescribe requisite content and format elements for applications. Regulations in 21 CFR part 601, subpart C (21 CFR 601.12-21 CFR 601.29) pertain to BLA changes; the electronic submission of information; the suspension, revocation, and reissuance of BLAs; and also provide for the availability of guidance documents by FDA to assist respondents in complying with applicable requirements (21 CFR 601.29). Regulations in 21 CFR 601, subparts D and E, respectively, establish requirements applicable to diagnostic radiopharmaceuticals and for 
                    <PRTPAGE P="41048"/>
                    the accelerated approval of biological products for serious or life-threatening illnesses. Confidentiality of information submitted to FDA is covered in 21 CFR 601, subpart F (601.50-601.51). The regulations also provide for the approval of biological products when human efficacy studies are not ethical or feasible, as established in 21 CFR 601, subpart H. Finally, regulations in 21 CFR parts 610-680 establish both general and specific standards applicable to all biological products, including FDA requests for and protocols as required under 21 CFR 610.2, 660.6, 660.36, and 660.46 (previously approved under OMB control no. 0910-0206), as well as labeling provisions pertaining to exceptions or alternatives to the labeling of products in the Strategic National Stockpile (SNS) established in 21 CFR 610.28 (previously approved under OMB control no. 0910-0616).
                </P>
                <P>To assist respondents with individual information collection elements, we have developed the following instruments, noting that FDA forms may be approved for use in other information collections:</P>
                <HD SOURCE="HD2">Forms</HD>
                <P>
                    Form FDA 356h, 
                    <E T="03">Application to Market a New or Abbreviated New Drug or Biologic for Human Use,</E>
                     provides a uniform format for submitting BLAs. Form FDA 356h is a fillable PDF form that may be submitted through our Electronic Submission Gateway (ESG), for which respondents must create and maintain a user account. Utilizing Form FDA 356h helps to ensure that an application is complete and contains all the necessary information, so that delays due to lack of information may be avoided. In addition, the form provides key information to FDA for efficient handling and distribution to the appropriate staff for review.
                </P>
                <P>
                    Form FDA 2252, 
                    <E T="03">Transmittal of Annual Report for Drugs and Biologics for Human Use,</E>
                     is used by an applicant of a licensed biological product to submit annual reports required by § 601.70(b) (21 CFR 601.70(b)). Form FDA 2252 is also a fillable PDF form.
                </P>
                <P>
                    Form FDA 2253, 
                    <E T="03">Transmittal of Advertisements and Promotional Labeling for Drugs and Biologics for Human Use,</E>
                     was developed for use by respondents to transmit specimens of advertisements and promotional labeling (
                    <E T="03">e.g.,</E>
                     circulars, package labels, container labels, etc.), as well as labeling changes. The submission of this information is required by § 601.12 (21 CFR 601.12) for biological products and by 21 CFR 314.81 for drug products. Form FDA 2253 is a fillable PDF form.
                </P>
                <P>
                    Form FDA 3674, 
                    <E T="03">Certificate of Compliance Under 42 U.S.C. 282(j)(5)(B), with Requirements of ClinicalTrials.gov</E>
                     Data Bank, was developed for use by respondents to certify submissions as required by section 402(j)(5)(B) of the Public Health Service (PHS) Act and is submitted through our ESG.
                </P>
                <HD SOURCE="HD2">Cover Sheets</HD>
                <P>
                    As provided for under 21 CFR part 601.2(a), FDA utilizes cover sheets, so denoted for purposes of identifying specific content information within a given application. For more information regarding BLA cover sheets, please refer to 
                    <E T="03">https://www.fda.gov/vaccines-blood-biologics/development-approval-process-cber/regulatory-submissions-electronic-format-cber-regulated-products.</E>
                </P>
                <HD SOURCE="HD2">Guidance Documents</HD>
                <P>Agency regulations in 21 CFR 601.29 complement our Good Guidance Practice regulations in 21 CFR 10.115 by providing for the issuance of guidance documents to assist respondents with applicable requirements in 21 CFR part 601. We have issued the following guidance documents to assist respondents with activities covered by the information collection:</P>
                <P>
                    • The guidance document “
                    <E T="03">Cooperative Manufacturing Arrangements for Licensed Biologics,”</E>
                     (November 2008), available at 
                    <E T="03">https://www.fda.gov/regulatory-information/search-fda-guidance-documents/cooperative-manufacturing-arrangements-licensed-biologics,</E>
                     discusses strategies for meeting an increased need for flexible manufacturing arrangements. Since cooperative manufacturing arrangements can take a considerable amount of time to develop, the guidance is intended to be useful for planning purposes in the early phases of product development. Many companies that perform only limited aspects of manufacturing processes are interested in sharing or contracting parts of manufacturing in order to facilitate product development and manufacturing flexibility. The guidance document discusses recommended communication between licensed manufacturers and contract manufacturers regarding changes to production and facilities, results of tests and investigations regarding the product, types of products manufactured in the contract facility, and standard operating procedures. We believe that the information collection provisions in the guidance do not create a new burden for respondents but incorporate reporting and recordkeeping provisions that are part of usual and customary business practices.
                </P>
                <P>
                    • The guidance document entitled, “Voluntary Consensus Standards Recognition Program for Regenerative Medicine Therapies” (October 2023), describes a standards recognition program for regenerative medicine therapies (SRP-RMT) designed to identify and recognize Voluntary Consensus Standards (VCS) to facilitate the development and assessment of regenerative medicine therapy (RMT) products when such standards are appropriate. The guidance document also explains that any interested party may request recognition of a VCS. The guidance document is available for download from our website at 
                    <E T="03">https://www.fda.gov/regulatory-information/search-fda-guidance-documents/voluntary-consensus-standards-recognition-program-regenerative-medicine-therapies.</E>
                </P>
                <P>We estimate the burden of the information collection as follows:</P>
                <GPOTABLE COLS="7" OPTS="L2,nj,p7,7/8,i1" CDEF="s100,12,12,13,12,r35,12">
                    <TTITLE>
                        Table 1—Estimated Annual Reporting Burden 
                        <SU>1</SU>
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">21 CFR subchapter F: biologics or other authority; information collection activity</CHED>
                        <CHED H="1">Form FDA No.</CHED>
                        <CHED H="1">
                            Number of
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Number of
                            <LI>responses per</LI>
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Total annual
                            <LI>responses</LI>
                        </CHED>
                        <CHED H="1">Average burden per response</CHED>
                        <CHED H="1">
                            Total hours 
                            <SU>2</SU>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Parts 601 (§§ 601.2-601.95); applications and changes, including applicable labeling standards in part 610 (610.15, 610.65)</ENT>
                        <ENT>356h</ENT>
                        <ENT>371</ENT>
                        <ENT>177.40</ENT>
                        <ENT>65,814</ENT>
                        <ENT>~12.35</ENT>
                        <ENT>812,607</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">601.12; Changes to an approved application</ENT>
                        <ENT>356h</ENT>
                        <ENT>170</ENT>
                        <ENT>27.888</ENT>
                        <ENT>4,741</ENT>
                        <ENT>10</ENT>
                        <ENT>47,410</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">
                            Guidance documents issued in accordance with 601.29:
                            <LI O="oi3" O1="xl">• Cooperative Manufacturing Agreements</LI>
                            <LI O="oi3" O1="xl">• Voluntary Consensus Standard Programs</LI>
                        </ENT>
                        <ENT>NA</ENT>
                        <ENT>9</ENT>
                        <ENT>1</ENT>
                        <ENT>9</ENT>
                        <ENT>3</ENT>
                        <ENT>27</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">610.15(d); Request for exceptions or alternatives to the regulation for constituent materials</ENT>
                        <ENT>NA</ENT>
                        <ENT>1</ENT>
                        <ENT>1</ENT>
                        <ENT>1</ENT>
                        <ENT>1</ENT>
                        <ENT>1</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="41049"/>
                        <ENT I="01">Part 680 (§§ 680.1-680.3); additional standards</ENT>
                        <ENT>NA</ENT>
                        <ENT>10</ENT>
                        <ENT>1</ENT>
                        <ENT>10</ENT>
                        <ENT>2</ENT>
                        <ENT>20</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Section 402(j)(5)(B) of the PHS Act (42 U.S.C.); Certification to accompany biological product applications</ENT>
                        <ENT>3,674</ENT>
                        <ENT>371</ENT>
                        <ENT>1</ENT>
                        <ENT>371</ENT>
                        <ENT>0.28 (17 minutes)</ENT>
                        <ENT>105</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT/>
                        <ENT>371</ENT>
                        <ENT/>
                        <ENT>70,946</ENT>
                        <ENT/>
                        <ENT>860,170</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>1</SU>
                         There are no capital costs or operating and maintenance costs associated with this collection of information.
                    </TNOTE>
                    <TNOTE>
                        <SU>2</SU>
                         The numbers in this column have been rounded.
                    </TNOTE>
                </GPOTABLE>
                <P>Noting that 5 CFR 1320.3(m) defines a recordkeeping requirement to include the reporting to the Federal government regarding such records, we have characterized the submission tasks reflected in Table 1 as reporting burden, assuming that respondents retain records in support of the respective submissions.</P>
                <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s100,12,13,12,r35,8">
                    <TTITLE>
                        Table 2—Estimated Annual Third-Party Disclosure Burden 
                        <SU>1</SU>
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">21 CFR section; activity</CHED>
                        <CHED H="1">
                            Number of
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Number of
                            <LI>disclosures per</LI>
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Total annual
                            <LI>disclosures</LI>
                        </CHED>
                        <CHED H="1">
                            Average
                            <LI>burden per</LI>
                            <LI>disclosure</LI>
                        </CHED>
                        <CHED H="1">
                            Total hours 
                            <SU>2</SU>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">601.6(a); Requirement to notify selling agents and distributors upon suspension of license</ENT>
                        <ENT>1</ENT>
                        <ENT>20</ENT>
                        <ENT>20</ENT>
                        <ENT>0.33 (20 minutes)</ENT>
                        <ENT>7</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>1</SU>
                         There are no capital costs or operating and maintenance costs associated with this collection of information.
                    </TNOTE>
                    <TNOTE>
                        <SU>2</SU>
                         The number in this column has been rounded to the nearest whole number.
                    </TNOTE>
                </GPOTABLE>
                <P>Based on our experience with the information collection, we account for disclosures under 21 CFR 601.6(a) distinctly, as reflected above in Table 2. Again, FDA assumes that respondents subject to regulatory requirements in 21 CFR 601.6 will retain corresponding records.</P>
                <P>Cumulatively, these adjustments result in an average decrease of 2,168 responses and an average increase of 29,133 burden hours annually. We consider these nominal adjustments that reflect minimal change in the number of submissions and burden attributable to applicable requirements.</P>
                <SIG>
                    <NAME>Grace R. Graham,</NAME>
                    <TITLE>Deputy Commissioner for Policy, Legislation, and International Affairs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13533 Filed 7-2-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>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. FDA-2026-N-4699]</DEPDOC>
                <SUBJECT>Expedited Investigational New Drug Pilot Program; Request for Information; Correction</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; correction.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Food and Drug Administration (FDA) is correcting a notice that appeared in the 
                        <E T="04">Federal Register</E>
                         of June 24, 2026. That notice opened a public docket to solicit input and comments on a proposal to establish a pilot program, the Expedited Investigational New Drug pilot program, to shorten the time it takes from drug identification to first-in-human study, while protecting clinical trial participants. FDA is correcting the email address of the document.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Benjamin Cook, Office of the Commissioner, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 2, Rm. 2114, Silver Spring, MD 20993-0002, 240-338-4685, 
                        <E T="03">ExpeditedINDPilot@fda.hhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    In the 
                    <E T="04">Federal Register</E>
                     of Wednesday, June 24, 2026 (91 FR 37996), in FR Doc. 2026-12621, the following correction is made:
                </P>
                <P>
                    On page 37997, in the third column, in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section, the email is corrected to 
                    <E T="03">ExpeditedINDPilot@fda.hhs.gov.</E>
                </P>
                <SIG>
                    <NAME>Grace R. Graham,</NAME>
                    <TITLE>Deputy Commissioner for Policy, Legislation, and International Affairs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13592 Filed 7-2-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>
                <DEPDOC>[Docket No. HHS-OASH-2026-0232]</DEPDOC>
                <SUBJECT>Temporary Placement of 7-Hydroxymitragynine Above a Specified Threshold in Schedule I; Request for Information</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Assistant Secretary for Health, Department of Health and Human Services.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; request for information; establishment of a public docket.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Office of the Assistant Secretary for Health (OASH or we) is opening a public docket to solicit input and comments on a proposed threshold for 7-hydroxymitragynine (7-OH) scheduling under the Controlled Substances Act. Public comments submitted to this docket will be provided by the Secretary for Health and Human Services for consideration by the Attorney General.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit either electronic or written comments, data, or information by July 31, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        <E T="03">Request for Information (RFI) Docket:</E>
                         You may examine the RFI docket at 
                        <E T="03">regulations.gov</E>
                         under HHS-OASH-2026-0232. The docket contains this RFI and all comments received to date. To submit a response, click the “Comment” button inside Docket: HHS-OASH-2026-0232 and follow all instructions.
                    </P>
                </ADD>
                <FURINF>
                    <PRTPAGE P="41050"/>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Ruben Hernandez Segarra, 
                        <E T="03">Ruben.HernandezSegarra@hhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    Elsewhere in this issue of the 
                    <E T="04">Federal Register</E>
                    , the Drug Enforcement Administration (DEA) has published a document entitled “Schedules of Controlled Substance: Temporary Placement of 7-Hydroxymitragynine Above a Specified Threshold in Schedule I.” In that document, the DEA noted their intent to issue a temporary scheduling order (in the form of a temporary amendment) to add 7-hydroxymitragynine above a specified threshold, including its isomers, esters, ethers, salts, and salts of isomers, esters, and ethers whenever the existence of such isomers, esters, ethers, and salts is possible, to schedule I under the Controlled Substances Act (CSA). The DEA's specified threshold for 7-hydroxymitragynine is as follows:
                </P>
                <P>
                    (A) 
                    <E T="03">Any botanical material of the plant Mitragyna speciosa, also known as kratom, and contains more than 0.050 percentage of 7-hydroxymitragynine on a dry weight basis, or</E>
                </P>
                <P>
                    (B) 
                    <E T="03">Any alternative article or material to that described in (A), that is:</E>
                </P>
                <P>
                    i. 
                    <E T="03">Resulting from synthetic methods and containing 7-hydroxymitragynine present in amounts greater than 0.050 percentage weight/weight, weight/volume, or volume/volume or greater than 1.00 milligram of 7-hydroxymitragynine in the article, or</E>
                </P>
                <P>
                    ii. 
                    <E T="03">Material derived from Mitragyna speciosa and further processed to manufacture alternative dosage forms such as extracts, concentrates, processed edibles, or pressed pills, and which may have materials that have been exposed to chemical, thermal, or other methods leading to chemical transformations that result in 7-hydroxymitragynine present in amounts greater than 0.050 percentage weight/weight, weight/volume, or volume/volume, or greater than 1.00 milligram of 7-hydroxymitragynine in the article.</E>
                </P>
                <HD SOURCE="HD1">II. Topics for Public Input</HD>
                <P>This notice is seeking input on the 7-OH threshold identified and justified above. In particular, comments are sought on the following topics:</P>
                <P>
                    1. Whether any additional data exist that further support this or an alternative threshold level, and specifically, what concentration or quantity of 7-OH in a product constitutes an imminent hazard to public safety 
                    <SU>1</SU>
                    <FTREF/>
                     and
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         The Controlled Substances Act (CSA) provides the Attorney General with the authority to temporarily place a substance in schedule I of the CSA for two years without regard to the requirements of 21 U.S.C. 811(b), if he finds that such action is necessary to avoid an imminent hazard to public safety (21 U.S.C. 811(h)(1)). When issuing an order under 21 U.S.C. 811(h)(1), the Attorney General shall be required to consider, with respect to the finding of an imminent hazard to the public safety, only those factors set forth in 21 U.S.C. 811(c)(4), (5), and (6), including actual abuse, diversion from legitimate channels, and clandestine importation, manufacture, or distribution (21 U.S.C. 811(h)(3)).
                    </P>
                </FTNT>
                <P>2. Whether data exist supporting alternative measurement expressions for purposes of specifying the threshold level that is necessary to avoid an imminent hazard to public safety.</P>
                <P>Note that OASH is not soliciting comment on any permanent scheduling decision, the general safety or utility of kratom-derived products, or other policy questions outside the scope of the threshold determination for temporary scheduling. Public comments submitted to this docket will be provided by the Secretary for Health and Human Services for consideration by the Attorney General.</P>
                <SIG>
                    <NAME>Brian Christine,</NAME>
                    <TITLE>Assistant Secretary for Health, Department of Health and Human Services.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13608 Filed 7-1-26; 4:15 pm]</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>Proposed Collection; 60-day Comment Request; Generic Clearance for NIH Citizen Science and Crowdsourcing Projects (Office of the Director)</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Institutes of Health, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In compliance with the requirement of the Paperwork Reduction Act of 1995 to provide opportunity for public comment on proposed data collection projects, the National Institutes of Health will publish periodic summaries of proposed projects to be submitted to the Office of Management and Budget (OMB) for review and approval.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments regarding this information collection are best assured of having their full effect if received by September 4, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        To obtain a copy of the data collection plans and instruments, submit comments in writing, or request more information on the proposed project, contact: Mikia Currie, Chief, Project Clearance Branch (PCB), Office of Policy and Extramural Research Administration (OPERA), Office of the Director (OD), Office of Extramural Research (OER), NIH, 6705 Rockledge Drive, Bethesda, Maryland 20892, MSC 7980, or call non-toll-free number (301) 435-0941 or Email your request, including your address to: 
                        <E T="03">ProjectClearanceBranch@mail.nih.gov.</E>
                         Formal requests for additional plans and instruments must be requested in writing.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Section 3506(c)(2)(A) of the Paperwork Reduction Act of 1995 requires: written comments and/or suggestions from the public and affected agencies are invited to address one or more of the following points: (1) Whether the proposed collection of information is necessary for the proper performance of the function of the agency, including whether the information will have practical utility; (2) 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; (3) Ways to enhance the quality, utility, and clarity of the information to be collected; and (4) Ways to minimize the burden of the collection of information on those who are to respond, including the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology.</P>
                <P>
                    <E T="03">Proposed Collection:</E>
                     Generic Clearance for NIH Citizen Science and Crowdsourcing Projects -0925-0766—exp., date 09/30/2026, EXTENSION, Project Clearance Branch (PCB), Office of Policy and Extramural Research Administration (OPERA), Office of the Director (OD), Office of Extramural Research (OER), National Institutes of Health (NIH).
                </P>
                <P>
                    <E T="03">Need and Use of Information Collection:</E>
                     Projects under this generic clearance will allow Agency researchers and program staff to test ideas more quickly, respond to the project's needs as they evolve, and incorporate feedback from participants for flexible, innovative research methods. The purpose of this information collection is to:
                </P>
                <P>• Accelerate scientific research.</P>
                <P>• Increase cost-effectiveness to maximize the return on taxpayer dollars.</P>
                <P>• Address societal needs.</P>
                <P>
                    • Provide hands-on learning in STEM education.
                    <PRTPAGE P="41051"/>
                </P>
                <P>• Connect members of the public directly to federal science missions and each other.</P>
                <P>• Identify and disseminate resources more broadly to the public, on the Institutes' and Centers' (ICs) websites, and/or.</P>
                <P>• Collect information for agency internal use to improve scientific practices and/or assist in scientific reviews.</P>
                <P>OMB approval is requested for 3 years. There are no costs to respondents other than their time. The total estimated annualized burden hours are 18,584.</P>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s100,12,12,12,12">
                    <TTITLE>Estimated Annualized Burden Hours</TTITLE>
                    <BOXHD>
                        <CHED H="1">Type of collection</CHED>
                        <CHED H="1">
                            Number of 
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Number of 
                            <LI>responses per </LI>
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Time per 
                            <LI>response </LI>
                            <LI>(in hours)</LI>
                        </CHED>
                        <CHED H="1">Total hours</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Call for Nominations/Resources</ENT>
                        <ENT>1,000</ENT>
                        <ENT>1</ENT>
                        <ENT>10/60</ENT>
                        <ENT>167</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Recommendations of scientific reviewers</ENT>
                        <ENT>1,000</ENT>
                        <ENT>1</ENT>
                        <ENT>5/60</ENT>
                        <ENT>83</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Request for Population Characteristics</ENT>
                        <ENT>20,000</ENT>
                        <ENT>1</ENT>
                        <ENT>5/60</ENT>
                        <ENT>1,667</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Repository of Tools and Best Practices</ENT>
                        <ENT>100,000</ENT>
                        <ENT>1</ENT>
                        <ENT>10/60</ENT>
                        <ENT>16,667</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT/>
                        <ENT>122,000</ENT>
                        <ENT/>
                        <ENT>18,584</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    The Deputy Director for Extramural Research, Jon Lorsch, having reviewed and approved this document, authorizes Alycia Booth, who is the 
                    <E T="04">Federal Register</E>
                     Liaison, to electronically sign this document for purposes of publication in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <SIG>
                    <DATED>Dated: July 1, 2026.</DATED>
                    <NAME>Alycia Booth, </NAME>
                    <TITLE>Federal Register Liaison, National Institutes of Health.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13583 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4167&amp;ndash05-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 Member Conflict: Epidemiology and Population Health.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 29, 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>Address: 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>
                         Magnus A. Azuine, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892, (301) 435-7579, 
                        <E T="03">magnus.azuine@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Population Sciences and Epidemiology Integrated Review Group Reproductive, Perinatal and Pediatric Health Study Section.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 29-30, 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>
                         Sheila Pirooznia, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892, (301) 594-7259, 
                        <E T="03">sheila.pirooznia@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel Bacterial Innate Immunomodulation and Pathogenesis.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 29, 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>
                         Mairi Noverr, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892, (240) 747-7530, 
                        <E T="03">mairi.noverr@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel Member Conflict: Clinical Care, Treatment and Disease Management.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 29, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10:00 a.m. to 2: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>
                         Karin Eyrich Garg, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institute of Health, 6701 Rockledge Drive, Bethesda, MD 20892, (301) 594-2988, 
                        <E T="03">karin.garg@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel Fellowships: Synthetic and Medicinal Chemistry and Chemical Biology.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 29-30, 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>
                         John J. Laffan, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Dr., Bethesda, MD 20892, (301) 443-7154, 
                        <E T="03">laffanjo@mail.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel Member Conflict: Neurodegenerative Diseases.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 29, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10:00 a.m. to 7: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>
                         Kathryn Partlow, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 1016D, Bethesda, MD 20892, (301) 594-2138, 
                        <E T="03">partlowkc@csr.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel Member Conflict: Topics in Bacterial Interspecies, Host Interactions, and Pathogenesis.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 29, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         11:00 a.m. to 3:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                        <PRTPAGE P="41052"/>
                    </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>
                         Yong Gao, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892, (240) 402-8633, 
                        <E T="03">yong.gao@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel Contracts: Chemistry, Manufacturing and Controls and Related Services for Development of Drug Product.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 29, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         1:00 p.m. to 4: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>
                         Rahat Rani Khan, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20817, (301) 594-7214, 
                        <E T="03">Khanr2@mail.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel Early Career and Training Special Emphasis Panel.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 30, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:30 a.m. to 2: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>
                         Leroy Worth, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892, (301) 594-9434, 
                        <E T="03">leroy.worth@nih.gov.</E>
                    </P>
                    <P>(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)</P>
                </EXTRACT>
                <SIG>
                    <DATED> Dated: July 1, 2026. </DATED>
                    <NAME>Rosalind M Niamke, </NAME>
                    <TITLE>Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13612 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4167-05-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Substance Abuse and Mental Health Services Administration</SUBAGY>
                <SUBJECT>Agency Information Collection Activities: Submission for OMB Review; Comment Request</SUBJECT>
                <P>Periodically, the Substance Abuse and Mental Health Services Administration (SAMHSA) will publish a summary of information collection requests under OMB review, in compliance with the Paperwork Reduction Act (44 U.S.C. Chapter 35). To request a copy of these documents, call the SAMHSA Reports Clearance Officer on (240) 276-0361.</P>
                <HD SOURCE="HD1">Project: Projects for Assistance in Transition From Homelessness (PATH) Program Annual Report Manual (OMB No. 0930-0205)—Reinstatement With Change</HD>
                <P>
                    SAMHSA awards PATH grants each fiscal year to states, the District of Columbia, the Commonwealth of Puerto Rico, the U.S. Virgin Islands, Guam, American Samoa, and the Commonwealth of the Northern Mariana Islands (hereafter referred to as “states”), from allotments authorized under the PATH program established by Public Law 101-645, 42 U.S.C. 290cc-21 
                    <E T="03">et seq.,</E>
                     the Stewart B. McKinney Homeless Assistance Amendments Act of 1990 [Section 521 
                    <E T="03">et seq.</E>
                     of the Public Health Service (PHS) Act and the 21st Century Cures Act (Pub. L. 114-255), hereafter referred to as “the Act”]. Section 522 of the Act specifies that states must expend their payments solely for making grants to political subdivisions of the state, and to non-profit private entities (including community-based veterans' organizations and other community organizations) for the purpose of providing services specified in the Act. Available funding is allotted in accordance with the formula provision of Section 524 of the PHS Act.
                </P>
                <P>This submission is for a reinstatement with change to the approved PATH Annual Report Manual. Section 528 of the Act specifies, not later than January 31 of each fiscal year, a funded entity will “prepare and submit to the Secretary a report in such form and containing such information as the Secretary determines to be necessary for: (1) securing a record and a description of the purposes for which amounts received under Section 521 were expended during the preceding fiscal year and of the recipients of such amounts; and (2) determining whether such amounts were expended in accordance with the provisions of this part.”</P>
                <P>The proposed changes to the PATH 2026 Annual Report Manual are as follows:</P>
                <HD SOURCE="HD2">Homeless Management Information System (HMIS) Data Standards Updates</HD>
                <P>In September 2025, HUD released the FY2026 Data Standards. HMIS Leads and System Administrators were notified of the changes and HMIS software vendors were given access to the necessary programming documentation and were instructed to be ready to deploy by October 1, 2025. The FY2026 updates included HMIS PATH Programming Specifications (Version 1.0), which removed the demographic question for gender, added the demographic question for sex, and updated the label for a question on Hispanic ethnicity. Field response options and questions have been updated to align with the most recent version of the HMIS Data Standards.</P>
                <HD SOURCE="HD2">Summary of Changes</HD>
                <P>
                    <E T="03">Q26a:</E>
                     Removed question including Gender information.
                </P>
                <P>
                    <E T="03">Q26c:</E>
                     Updated label for Hispanic/Latina/e/o to Hispanic/Latina/o.
                </P>
                <P>
                    <E T="03">Q26l:</E>
                     Added question including Sex information.
                </P>
                <P>The requested changes will not increase the overall burden.</P>
                <P>The estimated annual burden for these reporting requirements is summarized in the table below.</P>
                <GPOTABLE COLS="9" OPTS="L2,nj,tp0,i1" CDEF="s50,r50,10,10,10,8,10,8,11">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Instrument/activity</CHED>
                        <CHED H="1">Respondents</CHED>
                        <CHED H="1">
                            Number of
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Responses per
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Total
                            <LI>responses</LI>
                        </CHED>
                        <CHED H="1">Hours per response</CHED>
                        <CHED H="1">Total hour burden</CHED>
                        <CHED H="1">Hourly wage rate</CHED>
                        <CHED H="1">Total hour cost</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Annual Report Completion</ENT>
                        <ENT>States</ENT>
                        <ENT>56</ENT>
                        <ENT>1</ENT>
                        <ENT>56</ENT>
                        <ENT>15</ENT>
                        <ENT>840</ENT>
                        <ENT>$38.74</ENT>
                        <ENT>$32,541.60</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Annual Report Completion</ENT>
                        <ENT>Local provider agencies</ENT>
                        <ENT>408</ENT>
                        <ENT>1</ENT>
                        <ENT>408</ENT>
                        <ENT>15</ENT>
                        <ENT>6,120</ENT>
                        <ENT>38.74</ENT>
                        <ENT>237,088.80</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT/>
                        <ENT>464</ENT>
                        <ENT/>
                        <ENT>464</ENT>
                        <ENT/>
                        <ENT>6,960</ENT>
                        <ENT/>
                        <ENT>269,630.40</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    Written comments and recommendations for the proposed information collection should be sent within 30 days of publication of this notice to 
                    <E T="03">http://www.reginfo.gov/public/do/PRAMain.</E>
                     Find this particular 
                    <PRTPAGE P="41053"/>
                    collection of information by selecting “Currently under 30-day Review—Open for Public Comments” or by using the search function.
                </P>
                <SIG>
                    <NAME>Alicia Broadus,</NAME>
                    <TITLE>Public Health Advisor.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13621 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4162-20-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>U.S. Customs and Border Protection</SUBAGY>
                <SUBJECT>Approval of The Strawn Group (Houston, TX) as a Commercial Gauger</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Customs and Border Protection, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of approval of The Strawn Group (Houston, TX) as a commercial gauger.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Notice is hereby given, pursuant to CBP regulations, that The Strawn Group (Houston, TX) has been approved to gauge petroleum and certain petroleum products for customs purposes for the next three years as of September 27, 2024.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The Strawn Group (Houston, TX) was approved as a commercial gauger as of September 27, 2024. The next triennial inspection date will be scheduled for September 2027.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Dr. Laura Granell-Ortiz, Laboratories and Scientific Services, U.S. Customs and Border Protection, 1331 Pennsylvania Avenue NW, Suite 1501A North, Washington, DC 20004, tel. 202-344-1060.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Notice is hereby given pursuant to 19 CFR 151.13, that The Strawn Group, 3855 Villa Ridge, Houston, TX 77068, has been approved to gauge petroleum and certain petroleum products for customs purposes, in accordance with the provisions of 19 CFR 151.13.</P>
                <P>The Strawn Group (Houston, TX) is approved for the following gauging procedures for petroleum and certain petroleum products from the American Petroleum Institute (API):</P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s50,r100">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">API Chapters</CHED>
                        <CHED H="1">Title</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">8.2</ENT>
                        <ENT>Standard Practice for Automatic Sampling of Petroleum and Petroleum Products.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">8.3</ENT>
                        <ENT>Standard Practice for Mixing and Handling of Liquid Samples of Petroleum and Petroleum Products.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    Anyone wishing to employ this entity to conduct gauger services should request and receive written assurances from the entity that it is approved by the U.S. Customs and Border Protection to conduct the specific gauger service requested. Alternatively, inquiries regarding the specific gauger service this entity is approved to perform may be directed to the U.S. Customs and Border Protection by calling (202) 344-1060. The inquiry may also be sent to 
                    <E T="03">CBPGaugersLabs@cbp.dhs.gov.</E>
                     Please reference the website listed below for a complete listing of CBP approved gaugers and accredited laboratories. 
                    <E T="03">http://www.cbp.gov/about/labs-scientific/commercial-gaugers-and-laboratories.</E>
                </P>
                <SIG>
                    <NAME>Patricia A. Coleman,</NAME>
                    <TITLE>Acting Assistant Commissioner, Laboratories and Scientific Services.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13575 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9111-14-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>U.S. Customs and Border Protection</SUBAGY>
                <SUBJECT>Modification and Clarification of the National Customs Automation Program Test Regarding Post-Summary Corrections</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Customs and Border Protection, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>General notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document announces modifications and a clarification to U.S. Customs and Border Protection's (CBP) National Customs Automation Program (NCAP) test pertaining to the processing of post-summary corrections (PSCs) and the payment of increases in estimated duties, taxes, and fees resulting from a PSC. Except to the extent expressly announced or modified by this document, all aspects, rules, terms and conditions announced in previous notices regarding the test remain in effect. For ease of reference, the entire test is reproduced, with the changes, in this document.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        The modifications announced in this test will become operational and participants must comply with the modifications as of August 5, 2026. The test will continue until concluded by an announcement published in the 
                        <E T="04">Federal Register</E>
                        .
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments concerning this test program may be submitted via email to Kellee Gross at 
                        <E T="03">kellee.m.gross@cbp.dhs.gov</E>
                         with a subject line identifier reading, “PSC Test.”
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For policy-related questions, contact Kellee Gross, Supervisory Trade Analyst, Office of Trade, at (202) 816-1699 or via email at 
                        <E T="03">kellee.m.gross@cbp.dhs.gov.</E>
                         For technical questions related to transmissions using the Automated Broker Interface (ABI), contact your assigned client representative. Interested parties without an assigned client representative should direct their questions to the Client Services Division via email at 
                        <E T="03">gmb.clientrepoutreach@cbp.dhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    On June 24, 2011, U.S. Customs and Border Protection (CBP) published a notice in the 
                    <E T="04">Federal Register</E>
                     that announced a plan to conduct a test allowing importers to electronically correct certain entry summaries prior to liquidation by filing a post-summary correction (PSC) using the Automated Broker Interface (hereinafter, referred to as the “PSC test”).
                    <SU>1</SU>
                    <FTREF/>
                      
                    <E T="03">See</E>
                     76 FR 37136 (June 24, 2011). CBP modified and clarified various aspects of the PSC test in five subsequent 
                    <E T="04">Federal Register</E>
                     notices published on: November 19, 2013 (78 FR 69434); December 12, 2016 (81 FR 89482); January 9, 2017 (82 FR 2385); November 1, 2017 (82 FR 50656); and August 14, 2019 (84 FR 40430).
                    <SU>2</SU>
                    <FTREF/>
                     This document announces three modifications and a clarification to the test, which are discussed below.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         For information regarding the PSC test, see 
                        <E T="03">https://www.cbp.gov/trade/programs-administration/entry-summary/post-summary-correction.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See</E>
                         82 FR 4901 (January 17, 2017); 82 FR 26699 (June 8, 2017); 82 FR 29910 (June 30, 2017) (announcing delayed effective date for test modifications announced on December 12, 2016, and January 9, 2017).
                    </P>
                </FTNT>
                <P>
                    First, this document announces that test participants must transmit electronic payment of an increase in estimated duties, taxes, and fees resulting from a PSC via Automated Clearinghouse (ACH) starting on August 5, 2026 and will no longer be able to pay such increases via check or cash. However, test participants who are ready to make electronic payments prior to this date may do so. To make electronic payments, test participants must first enroll in either the ACH Debit process or ACH Credit process as described below in Section V. To pay via ACH Debit or ACH Credit, test participants must follow the regular payment process implemented by CBP for ACH payments found at 
                    <E T="03">https://www.cbp.gov/trade/basic-import-export/automated-clearinghouse-ach.</E>
                     For any questions regarding the ACH enrollment process, test participants 
                    <PRTPAGE P="41054"/>
                    may contact CBP at 
                    <E T="03">ACH-CUSTOMS@cbp.dhs.gov.</E>
                </P>
                <P>Second, this document announces that test participants may choose to pay the full amount of the increase in estimated duties, taxes, and fees resulting from a PSC prior to liquidation or wait to be billed at liquidation before making a payment. A test participant may not submit a subsequent PSC until the increase in duties, taxes, and fees resulting from a previously filed PSC is paid in full and processed by CBP. In other words, if only a partial payment of increased estimated duties, taxes, and fees resulting from a PSC is made, a test participant will not be able to submit a subsequent PSC.</P>
                <P>
                    Third, this document modifies the test regarding the timeframe for filing PSCs in the case of suspended liquidations. This modification allows test participants to submit a PSC outside of the regular 300-day timeframe for filing a PSC for entries where liquidation of those entries is suspended beyond 300 days after the date of entry,
                    <SU>3</SU>
                    <FTREF/>
                     and the entries have an associated suspension basis (such as Countervailing Duty (CVD) Suspend, Antidumping Duty (ADD) Suspend, AD/CVD Suspend, Subject to Enforce and Protect Act (EAPA), or Subject to Court Injunction 
                    <SU>4</SU>
                    <FTREF/>
                    ) at the time of PSC filing. CBP will post the allowable suspension bases on CBP.gov.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         In practice, CBP has permitted PSCs outside of the 300-day timeframe for entries for which liquidation is suspended beyond 300 days after date of entry since 2022, as reflected on the CBP web page (CBP.gov) and in the Automated Commercial Environment (ACE) Entry Summary Business Rules and Processes document (
                        <E T="03">https://www.cbp.gov/document/guides/ace-entry-summary-business-process</E>
                        ). This 
                        <E T="04">Federal Register</E>
                         notice formalizes this modification.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         Each suspension basis, identified by a specific code in ACE, indicates the reason for a suspension of the entry summary liquidation. 
                        <E T="03">See</E>
                         CBP, ACE CATAIR Entry Summary Query (v26), available at
                        <E T="03"> https://www.cbp.gov/document/guidance/ace-catair-entry-summary-query</E>
                         (last modified May 11, 2026).
                    </P>
                </FTNT>
                <P>This document further clarifies that interest payment on the increased estimated duties, taxes, and fees resulting from a PSC will not be accepted prior to liquidation. Test participants must pay any interest owed to CBP as a result of the PSC once CBP liquidates the entry and issues a bill, if necessary. This clarification is intended to ensure proper application of payments to open bills and improve enforcement of PSCs by CBP.</P>
                <P>For ease of reference, this document republishes the PSC test in its entirety, with updates to reflect the modifications and clarification made by this document in Section V below.</P>
                <HD SOURCE="HD1">I. Background on National Customs Automation Program</HD>
                <P>The National Customs Automation Program (NCAP) was established by Subtitle B of Title VI—Customs Modernization in the North American Free Trade Agreement (NAFTA) Implementation Act (Customs Modernization Act) (Pub. L. 103-182, 107 Stat. 2057, 2170, December 8, 1993) (19 U.S.C. 1411). Through NCAP, the thrust of customs modernization was on trade compliance and the development of ACE as the electronic data interchange (EDI) system authorized by CBP. ACE is an automated and electronic system for commercial trade processing which is intended to streamline business processes, facilitate growth in trade, ensure cargo security, and foster participation in global commerce, while ensuring compliance with U.S. laws and regulations and reducing costs for CBP and all of its communities of interest. The ability to meet these objectives depends on successfully modernizing CBP's business functions and the information technology that supports those functions. CBP's modernization efforts are accomplished through phased releases of ACE component functionality, which update the system and add new functionality.</P>
                <HD SOURCE="HD1">II. Authorization for the Test</HD>
                <P>
                    The Customs Modernization Act authorizes the Commissioner of CBP to conduct limited test programs or procedures designed to evaluate planned components of the NCAP. Section 101.9(b) of title 19 of the Code of Federal Regulations (19 CFR 101.9(b)) provides for the testing of NCAP components. 
                    <E T="03">See</E>
                     T.D. 95-21 (60 FR 14211) (March 16, 1995); 
                    <E T="03">see also</E>
                     19 U.S.C. 1411-1413.
                </P>
                <HD SOURCE="HD1">III. General Description of the Test</HD>
                <P>
                    Under the post-summary correction test, importers are allowed to file PSCs for certain entry summaries using the Automated Broker Interface (ABI). Importers and brokers are allowed to file a PSC to those pre-liquidation entry summaries that have been accepted by CBP and are fully paid and under CBP control. A PSC transaction contains all the data elements in the original entry summary and constitutes a complete replacement of that entry summary, as well as a complete replacement of any prior PSC that may have been made to the original entry summary, but does not replace the date of entry or the date of entry summary filing.
                    <SU>5</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         The phrase “complete replacement” means the replacement of all data elements in an original entry summary filed in ACE with new data elements found in a superseding PSC. A complete replacement does not mean that the replaced data is null and void. Any obligations that vested under the original entry or entry summary remain valid. Obligations that vest subsequent to the replacement are attributable to the PSC. For example, when an entry summary is filed outside the 10 working days after cargo release, and liquidated damages are incurred, the filing of a PSC on that entry summary is deemed to “replace” the entry summary data elements but does not cancel the liquidated damages that were incurred. The date of entry and date of entry summary filing, and all legal obligations flowing therefrom, remain unchanged. CBP updated the definition of “complete or full replacement” (originally issued in a 
                        <E T="04">Federal Register</E>
                         notice published on November 19, 2013 (78 FR 69434)) in this notice for clarity.
                    </P>
                </FTNT>
                <P>
                    When a PSC is filed, the filer of the original entry summary will be notified that the entry summary has been fully replaced by a PSC and the original filer will have full access to the new filing. Similarly, if a subsequent PSC is filed, it fully replaces the previously filed PSC, and the filer of the previously filed PSC will be notified that the previously filed PSC has been fully replaced by a new PSC and will have full access to the new filing. All the information in the latest version of the entry summary and all subsequent PSCs will be accessible to all the filers. Under the terms and conditions of this test, importers and filers acknowledge that by filing a PSC, they are making any commercial and confidential business information contained within the PSC available to all the parties described in this test, 
                    <E T="03">i.e.,</E>
                     the filer of the original entry summary and any filers of a PSC correcting that entry summary. An importer should not file a PSC under the terms and conditions of this test if the importer does not want the original entry summary filer or any PSC filer for the same entry to have full access to all information contained within a subsequent PSC that was filed by a different filer.
                </P>
                <FP SOURCE="FP-1">A PSC may be filed for the following entry types:</FP>
                <FP SOURCE="FP-1">• 01—Consumption—Free and Dutiable</FP>
                <FP SOURCE="FP-1">• 02—Consumption—Quota/Visa</FP>
                <FP SOURCE="FP-1">• 03—Consumption—Antidumping/Countervailing Duty</FP>
                <FP SOURCE="FP-1">• 06—Consumption—Foreign Trade Zone (FTZ)</FP>
                <FP SOURCE="FP-1">• 07—Consumption—Antidumping/Countervailing Duty and Quota/Visa Combination</FP>
                <FP SOURCE="FP-1">• 21—Warehouse</FP>
                <FP SOURCE="FP-1">• 22—Re-Warehouse</FP>
                <FP SOURCE="FP-1">• 23—Temporary Importation Bond (TIB)</FP>
                <FP SOURCE="FP-1">• 31—Warehouse Withdrawal—Consumption</FP>
                <FP SOURCE="FP-1">• 32—Warehouse Withdrawal—Quota</FP>
                <FP SOURCE="FP-1">
                    • 34—Warehouse Withdrawal—Antidumping/Countervailing Duty
                    <PRTPAGE P="41055"/>
                </FP>
                <FP SOURCE="FP-1">• 38—Warehouse Withdrawal—Antidumping/Countervailing Duty &amp; Quota/Visa Combination</FP>
                <FP SOURCE="FP-1">• 51—Defense Contract Administration Service Region (DCASR)</FP>
                <FP SOURCE="FP-1">• 52—Government—Dutiable</FP>
                <P>Note that a PSC may be filed to change an entry type 01 to an entry type 03 and vice versa. No other changes to entry type are permitted.</P>
                <HD SOURCE="HD1">IV. Data Elements That Cannot Be Changed Via PSC</HD>
                <P>Certain data elements cannot be changed via PSC and CBP will reject any PSC submission containing changes to prohibited data elements. The following is a list of data elements that cannot be changed via PSC:</P>
                <FP SOURCE="FP-1">• Importer of record</FP>
                <FP SOURCE="FP-1">• Date of entry</FP>
                <FP SOURCE="FP-1">• Date of entry summary</FP>
                <FP SOURCE="FP-1">• Bond</FP>
                <FP SOURCE="FP-1">• Surety code</FP>
                <FP SOURCE="FP-1">• Consolidated summary indicator</FP>
                <FP SOURCE="FP-1">• Data elements, such as classification of an article, that change an entry type 23 (TIB) to another entry type and vice versa</FP>
                <FP SOURCE="FP-1">• Port of entry</FP>
                <FP SOURCE="FP-1">• Cargo release certification request indicator (this includes Department of</FP>
                <FP SOURCE="FP-1">Transportation (DOT) grouping; Food and Drug Administration (FDA) grouping; and Partner Government Agency (PGA) grouping)</FP>
                <FP SOURCE="FP-1">• Live entry indicator</FP>
                <FP SOURCE="FP-1">• Trade Agreement (19 U.S.C. 1520(d)) indicator for specific special programs</FP>
                <FP SOURCE="FP-1">• Reconciliation issue code</FP>
                <FP SOURCE="FP-1">• Preliminary statement print date</FP>
                <FP SOURCE="FP-1">• Periodic monthly statement</FP>
                <FP SOURCE="FP-1">• Statement client branch identifier</FP>
                <FP SOURCE="FP-1">• Location of goods code</FP>
                <FP SOURCE="FP-1">• Any release detail</FP>
                <HD SOURCE="HD1">V. Criteria and Rules for Filing a PSC</HD>
                <P>To file a PSC on an existing entry, the original entry summary or previously filed PSC must satisfy the following requirements:</P>
                <P>• The entry summary or previously filed PSC cannot be liquidated.</P>
                <P>• The entry summary or previously filed PSC must be fully paid or revenue free, meaning no additional estimated duties, taxes, or fees are owed as a result of the PSC submission.</P>
                <P>
                    • The entry summary or previously filed PSC must be in “accepted” status.
                    <SU>6</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         “Accepted” status is defined as an entry summary or previously filed PSC that has passed through all technical edits and validations. The entry summary or previously filed PSC must be in “CBP control,” accepted and fully paid, and not in “trade control.” The entry summary or previously filed PSC is in “trade control” when it is successfully accepted in the system and not on a statement. The entry summary or previously filed PSC is in “CBP control” when it is placed on a statement. 
                        <E T="03">See</E>
                         76 FR 37136 (June 24, 2011).
                    </P>
                </FTNT>
                <P>
                    • The entry summary or previously filed PSC cannot be under CBP review.
                    <SU>7</SU>
                    <FTREF/>
                     The filer will receive a message indicating “PSC not allowed under CBP Review” if a PSC is submitted and the entry summary or previously filed PSC is in CBP review.
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         The term “under U.S. Customs and Border Protection (CBP) review” means the period of time when CBP is reviewing the data elements and supporting documents of either an original entry summary or PSC prior to CBP's disposition of the original entry summary or PSC. 
                        <E T="03">See</E>
                         78 FR 69434 (Nov. 19, 2013).
                    </P>
                </FTNT>
                <P>• An entry summary or previously filed PSC that has been flagged for reconciliation may only be corrected by a PSC that does not affect the flagged issue.</P>
                <P>• A PSC cannot be made on entries that are associated with a protest.</P>
                <P>
                    • When a PSC is filed that increases the test participant's estimated liability for duties, taxes, and fees, the test participant must submit electronic payment of those additional duties, taxes, and fees via ACH. CBP offers two ACH payment options, ACH Debit and ACH Credit. Importers wishing to participate in the PSC test must enroll in either the ACH Debit process or ACH Credit process by submitting the respective information to CBP.
                    <SU>8</SU>
                    <FTREF/>
                     Test participants must pay the increase in estimated duties, taxes, and fees, in full, prior to submitting another PSC. If no other PSC is filed, the test participant may choose to pay the full amount of the increase resulting from the PSC, other than AD/CVD, prior to liquidation or wait until CBP issues a bill at liquidation before making payment.
                    <SU>9</SU>
                    <FTREF/>
                     Test participants will not be able to file a subsequent PSC until the increase in estimated duties, taxes, and fees resulting from the previously filed PSC is paid in full and processed by CBP. In other words, if only a partial payment of increased estimated duties, taxes, and fees resulting from a PSC is made, a test participant will not be able to submit a subsequent PSC.
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         Instructions on how to apply and make payments via ACH may be found at 
                        <E T="03">https://www.cbp.gov/trade/basic-import-export/automated-clearinghouse-ach.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         In accordance with 19 U.S.C. 1505 and 19 CFR 24.3a, the interest for any underpayment will be assessed upon liquidation, accruing from the date the importer of record is required to deposit estimated duties, taxes, fees until the date on which full payment is made (if the payment is made prior to liquidation), or otherwise until the date of the liquidation with the associated bill.
                    </P>
                </FTNT>
                <P>• When a PSC is filed that increases the test participant's liability for AD/CVD, the test participant must submit electronic payment of the additional AD/CVD via ACH within three business days of submitting the PSC. CBP offers two ACH payment options, ACH Debit and ACH Credit, as discussed above.</P>
                <P>• Interest payments on a PSC made before liquidation will not be accepted. Test participants must pay any interest owed once CBP liquidates the entry and issues a bill, if necessary, for any interest that is due, consistent with 19 CFR 24.3a.</P>
                <P>• The PSC filing must be transmitted within 300 days of the date of entry or up to 15 days prior to the scheduled liquidation date, whichever date is earlier. However, if a test participant requests and is granted an extension of time for liquidation pursuant to 19 CFR 159.12, a PSC must be transmitted up to 15 days prior to the scheduled liquidation date. A test participant also may submit a PSC outside of the 300-day timeframe for filing a PSC for entries where liquidation of those entries is suspended beyond 300 days after the date of entry, and the entries have an associated suspension basis (such as CVD Suspend, ADD Suspend, AD/CVD Suspend, Subject to EAPA, or Subject to Court Injunction) at the time of the PSC filing. CBP will post the allowable suspension bases on CBP.gov.</P>
                <P>• A text explanation and at least one reason code (both to be submitted electronically with the PSC entry summary) are required for each PSC submission.</P>
                <P>• There is no limitation on the number of PSCs that can be submitted for any one entry, so long as the PSC meets all criteria, rules, and requirements of the PSC test.</P>
                <HD SOURCE="HD1">VI. Bonding and PSC Filing</HD>
                <P>For purposes of the test, the same bond and surety remain obligated on an entry for which a PSC is filed. The following guidelines apply:</P>
                <P>• If, prior to a PSC filing, a superseding bond is filed pursuant to 19 CFR 142.4(b) or 19 CFR 141.20 (as authorized by 19 U.S.C. 1485(d)), that bond will continue to be obligated for the entry. All obligations vesting under the original entry, prior to the filing of a PSC, remain vested and are not obviated by a subsequent PSC filing.</P>
                <P>• If a PSC is filed and accepted by CBP, the bond obligated at the time of entry, as well as any subsequent superseding bonds, remain obligated accordingly for the original entry and the entry summary against which the PSC was filed.</P>
                <P>• New bond data will not be accepted through a PSC.</P>
                <HD SOURCE="HD1">VII. Rejection of a PSC</HD>
                <P>
                    CBP retains the authority to reject any PSC that may be found to be incomplete 
                    <PRTPAGE P="41056"/>
                    or not in compliance with the requirements described in this test. A PSC which has been rejected in ACE back to the filer may be re-transmitted within two (2) business days of the rejection. If there is no timely re-transmission, CBP will correct the entry summary and set the entry summary for immediate liquidation, unless the liquidation of such previously accepted entry summary has been suspended pursuant to statute or court order.
                </P>
                <HD SOURCE="HD1">VIII. Deemed Liquidation</HD>
                <P>Pursuant to 19 U.S.C. 1504(a), consumption entries that are “deemed liquidated” must be liquidated at the rate of duty, value, quantity and amount of duties asserted by the importer of record. For purposes of this test, when a PSC has been properly filed, CBP interprets the statutory phrase “deemed liquidated” to mean liquidation at the rate of duty, value, quantity and amount of duties asserted by the importer of record at the time of CBP's acceptance of the most recently accepted PSC.</P>
                <HD SOURCE="HD1">IX. Misconduct Under the Test</HD>
                <P>A test participant may be subject to civil and criminal penalties, administrative sanctions, liquidated damages, and/or suspension from this test for any of the following:</P>
                <P>• Failure to follow the terms and conditions of this test.</P>
                <P>• Failure to exercise reasonable care in the execution of participant obligations.</P>
                <P>• Failure to abide by applicable laws and regulations.</P>
                <P>• Failure to timely deposit estimated duties, taxes, and fees, including any applicable AD/CVD cash deposits.</P>
                <P>• Misuse of the ACE Portal.</P>
                <P>• Engagement in any unauthorized disclosure.</P>
                <P>• Engagement in any unauthorized access to the ACE Portal.</P>
                <P>Suspensions for misconduct will be administered by the Executive Director, Trade Programs, Office of Trade. A written notice proposing suspension will be issued to the participant that apprises the participant of the facts or conduct warranting a suspension, informs the participant of the date the suspension will begin, and provides an opportunity to demonstrate or achieve compliance with all lawful requirements. Any decision proposing a suspension of a participant may be appealed in writing to the Executive Assistant Commissioner, Office of Trade, within 15 calendar days of the notification date. An appeal of a proposed suspension must address the facts or conduct charges contained in the notice and state how compliance will be achieved. In cases of willful misconduct or where public health interests or safety are concerned, a suspension may be effective immediately.</P>
                <HD SOURCE="HD1">X. Confidentiality</HD>
                <P>Data submitted and entered into ACE may include confidential commercial or financial information which may be protected under the Trade Secrets Act (18 U.S.C. 1905), and the Privacy Act (5 U.S.C. 552a). However, participation in this or any of the previous ACE tests is not confidential and, therefore, upon receipt of a written Freedom of Information Act request, the name(s) of an approved participant(s) will be disclosed by CBP in accordance with 5 U.S.C. 552.</P>
                <HD SOURCE="HD1">XI. Paperwork Reduction Act</HD>
                <P>The Paperwork Reduction Act (PRA) of 1995 (44 U.S.C. 3507(d)) requires that CBP consider the impact of paperwork and other information collection burdens imposed on the public. An agency may not conduct or sponsor, and an individual is not required to respond to, a collection of information unless the collection of information displays a valid Office of Management and Budget (OMB) control number assigned by OMB. This PSC test modification does not involve any material change to an existing approved information collection. The PRA does not apply to banking account information required as part of the ACH Debit enrollment for the PSC test.</P>
                <HD SOURCE="HD1">XII. Suspension of Regulations</HD>
                <P>
                    For purposes of this test, any provision in title 19 of the CFR including, but not limited to, the provisions found in parts 141, 142, 143 and 151 thereof relating to entry summary filing and processing that are inconsistent with the requirements set forth in this notice are waived for test participants for the duration of the test. 
                    <E T="03">See</E>
                     19 CFR 101.9(b). This document does not waive any recordkeeping requirements found in 19 CFR part 163 and the Appendix to part 163 (commonly known as the “(a)(1)(A) list”).
                </P>
                <SIG>
                    <NAME>Susan S. Thomas,</NAME>
                    <TITLE>Executive Assistant Commissioner, Office of Trade.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13574 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9111-14-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>U.S. Customs and Border Protection</SUBAGY>
                <SUBJECT>Accreditation and Approval of NMK Resources, Inc. (Thorofare, NJ), as a Commercial Gauger and Laboratory</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Customs and Border Protection, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of accreditation and approval of NMK Resources, Inc. (Thorofare, NJ), as a commercial gauger and laboratory.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Notice is hereby given, pursuant to CBP regulations, that NMK Resources, Inc. (Thorofare, NJ), has been approved to gauge petroleum and certain petroleum products and accredited to test petroleum and certain petroleum products for customs purposes for the next three years as of August 12, 2025.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>NMK Resources, Inc. (Thorofare, NJ), was approved and accredited as a commercial gauger and laboratory as of August 12, 2025. The next triennial inspection date will be scheduled for August 2028.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Dr. Laura Granell-Ortiz, Laboratories and Scientific Services, U.S. Customs and Border Protection, 1331 Pennsylvania Avenue NW, Suite 1501A North, Washington, DC 20004, tel. 202-344-1060.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Notice is hereby given pursuant to 19 CFR 151.12 and 19 CFR 151.13, that NMK Resources, Inc., 650 Grove Rd., Suite 111,</P>
                <P>West Deptford, NJ 08066, has been approved to gauge petroleum and certain petroleum products and accredited to test petroleum and certain petroleum products for customs purposes, in accordance with the provisions of 19 CFR 151.12 and 19 CFR 151.13.</P>
                <P>NMK Resources, Inc. (Thorofare, NJ), is approved for the following gauging procedures for petroleum and certain petroleum products from the American Petroleum Institute (API):</P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s25,r50">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">API Chapters</CHED>
                        <CHED H="1">Title</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">3</ENT>
                        <ENT>Tank Gauging.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">7</ENT>
                        <ENT>Temperature Determination.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">8</ENT>
                        <ENT>Sampling.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">11</ENT>
                        <ENT>Physical Properties Data.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12</ENT>
                        <ENT>Calculations.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">17</ENT>
                        <ENT>Marine Measurement.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    NMK Resources, Inc. (Thorofare, NJ), is accredited for the following laboratory analysis procedures and 
                    <PRTPAGE P="41057"/>
                    methods for petroleum and certain petroleum products set forth by the U.S. Customs and Border Protection Laboratory Methods (CBPL) and American Society for Testing and Materials (ASTM):
                </P>
                <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="xs60,xls30,r100">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">CBPL No.</CHED>
                        <CHED H="1">ASTM</CHED>
                        <CHED H="1">Title</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">27-04</ENT>
                        <ENT>D95</ENT>
                        <ENT>Standard Test Method for Water in Petroleum Products and Bituminous Materials by Distillation.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-11</ENT>
                        <ENT>D445</ENT>
                        <ENT>Standard Test Method for Kinematic Viscosity of Transparent and Opaque Liquids (and Calculation of Dynamic Viscosity).</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-13</ENT>
                        <ENT>D4294</ENT>
                        <ENT>Standard Test Method for Sulfur in Petroleum and Petroleum Products by Energy-Dispersive X-ray Fluorescence Spectrometry.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-46</ENT>
                        <ENT>D5002</ENT>
                        <ENT>Standard Test Method for Density, Relative Density, and API Gravity of Crude Oils by Digital Density Analyzer.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-48</ENT>
                        <ENT>D4052</ENT>
                        <ENT>Standard Test Method for Density, Relative Density, and API Gravity of Liquids by Digital Density Meter.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-50</ENT>
                        <ENT>D93</ENT>
                        <ENT>Standard Test Methods for Flash Point by Pensky-Martens Closed Cup Tester.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">N/A</ENT>
                        <ENT>D97</ENT>
                        <ENT>Standard Test Method for Pour Point of Petroleum Products.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">N/A</ENT>
                        <ENT>D482</ENT>
                        <ENT>Standard Test Method for Ash from Petroleum Products.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">N/A</ENT>
                        <ENT>D664</ENT>
                        <ENT>Standard Test Method for Acid Number of Petroleum Products by Potentiometric Titration.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">N/A</ENT>
                        <ENT>D1160</ENT>
                        <ENT>Standard Test Method for Distillation of Petroleum Products at Reduced Pressure.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">N/A</ENT>
                        <ENT>D4530</ENT>
                        <ENT>Standard Test Method for Determination of Carbon Residue (Micro Method).</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">N/A</ENT>
                        <ENT>D5762</ENT>
                        <ENT>Standard Test Method for Nitrogen in Liquid Hydrocarbons, Petroleum and Petroleum Products by Boat-Inlet Chemiluminescence.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    Anyone wishing to employ this entity to conduct laboratory analyses and gauger services should request and receive written assurances from the entity that it is accredited or approved by the U.S. Customs and Border Protection to conduct the specific test or gauger service requested. Alternatively, inquiries regarding the specific test or gauger service this entity is accredited or approved to perform may be directed to the U.S. Customs and Border Protection by calling (202) 344-1060. The inquiry may also be sent to 
                    <E T="03">CBPGaugersLabs@cbp.dhs.gov.</E>
                     Please reference the website listed below for a complete listing of CBP approved gaugers and accredited laboratories.
                </P>
                <P>
                    <E T="03">http://www.cbp.gov/about/labs-scientific/commercial-gaugers-and-laboratories.</E>
                </P>
                <SIG>
                    <NAME>Patricia A. Coleman,</NAME>
                    <TITLE>Acting Assistant Commissioner, Laboratories and Scientific Services.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13578 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9111-14-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>U.S. Customs and Border Protection</SUBAGY>
                <SUBJECT>Accreditation and Approval of NMK Resources, Inc., (Pasadena, TX) as a Commercial Gauger and Laboratory</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Customs and Border Protection, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of accreditation and approval of NMK Resources, Inc. (Pasadena, TX), as a commercial gauger and laboratory.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Notice is hereby given, pursuant to CBP regulations, that NMK Resources, Inc. (Pasadena, TX), has been approved to gauge petroleum and certain petroleum products and accredited to test petroleum and certain petroleum products for customs purposes for the next three years as of September 18, 2024.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>NMK Resources, Inc. (Pasadena, TX) was approved and accredited as a commercial gauger and laboratory as of September 18, 2024. The next triennial inspection date will be scheduled for September 2027.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Dr. Laura Granell-Ortiz, Laboratories and Scientific Services, U.S. Customs and Border Protection, 1331 Pennsylvania Avenue NW, Suite 1501A North, Washington, DC 20004, tel. 202-344-1060.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Notice is hereby given pursuant to 19 CFR 151.12 and 19 CFR 151.13, that NMK Resources, Inc.,1107 Center Street, Pasadena TX 77506, has been approved to gauge petroleum and certain petroleum products and accredited to test petroleum and certain petroleum products for customs purposes, in accordance with the provisions of 19 CFR 151.12 and 19 CFR 151.13.</P>
                <P>NMK Resources, Inc. (Pasadena, TX) is approved for the following gauging procedures for petroleum and certain petroleum products from the American Petroleum Institute (API):</P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s25,r50">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">API Chapters</CHED>
                        <CHED H="1">Title</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">3</ENT>
                        <ENT>Tank Gauging.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">7</ENT>
                        <ENT>Temperature Determination.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">8</ENT>
                        <ENT>Sampling.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">11</ENT>
                        <ENT>Physical Properties Data.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12</ENT>
                        <ENT>Calculations.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">17</ENT>
                        <ENT>Marine Measurement.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>NMK Resources, Inc. (Pasadena, TX) is accredited for the following laboratory analysis procedures and methods for petroleum and certain petroleum products set forth by the U.S. Customs and Border Protection Laboratory Methods (CBPL) and American Society for Testing and Materials (ASTM):</P>
                <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="xs50,xls30,r100">
                    <BOXHD>
                        <CHED H="1">CBPL No.</CHED>
                        <CHED H="1">ASTM</CHED>
                        <CHED H="1">Title</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">27-04</ENT>
                        <ENT>D95</ENT>
                        <ENT>Standard Test Method for Water in Petroleum Products and Bituminous Materials by Distillation.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-06</ENT>
                        <ENT>D473</ENT>
                        <ENT>Standard Test Method for Sediment in Crude Oils and Fuel Oils by the Extraction Method.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-46</ENT>
                        <ENT>D5002</ENT>
                        <ENT>Standard Test Method for Density, Relative Density, and API Gravity of Crude Oils by Digital Density Analyzer.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-48</ENT>
                        <ENT>D4052</ENT>
                        <ENT>Standard Test Method for Density, Relative Density, and API Gravity of Liquids by Digital Density Meter.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-50</ENT>
                        <ENT>D93</ENT>
                        <ENT>Standard Test Methods for Flash Point by Pensky-Martens Closed Cup Tester.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">N/A</ENT>
                        <ENT>D97</ENT>
                        <ENT>Standard Test Method for Pour Point of Petroleum Products.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">N/A</ENT>
                        <ENT>D482</ENT>
                        <ENT>Standard Test Method for Ash from Petroleum Products.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">N/A</ENT>
                        <ENT>D664</ENT>
                        <ENT>Standard Test Method for Acid Number of Petroleum Products by Potentiometric Titration.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">N/A</ENT>
                        <ENT>D1160</ENT>
                        <ENT>Standard Test Method for Distillation of Petroleum Products at Reduced Pressure.</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="41058"/>
                        <ENT I="01">N/A</ENT>
                        <ENT>D4530</ENT>
                        <ENT>Standard Test Method for Determination of Carbon Residue (Micro Method).</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">N/A</ENT>
                        <ENT>D5762</ENT>
                        <ENT>Standard Test Method for Nitrogen in Liquid Hydrocarbons, Petroleum and Petroleum Products by Boat-Inlet Chemiluminescence.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    Anyone wishing to employ this entity to conduct laboratory analyses and gauger services should request and receive written assurances from the entity that it is accredited or approved by the U.S. Customs and Border Protection to conduct the specific test or gauger service requested. Alternatively, inquiries regarding the specific test or gauger service this entity is accredited or approved to perform may be directed to the U.S. Customs and Border Protection by calling (202) 344-1060. The inquiry may also be sent to 
                    <E T="03">CBPGaugersLabs@cbp.dhs.gov.</E>
                     Please reference the website listed below for a complete listing of CBP approved gaugers and accredited laboratories. 
                    <E T="03">http://www.cbp.gov/about/labs-scientific/commercial-gaugers-and-laboratories.</E>
                </P>
                <SIG>
                    <NAME>Patricia A. Coleman,</NAME>
                    <TITLE>Deputy Assistant Commissioner,Laboratories and Scientific Services.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13577 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9111-14-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT</AGENCY>
                <DEPDOC>[Docket No. FR-7106-N-30]</DEPDOC>
                <SUBJECT>Privacy Act of 1974; System of Records</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Public and Indian Housing (PIH), HUD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of a Rescindment of a System of Records.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Pursuant to the provisions of the Privacy Act of 1974, as amended, the Department of Housing and Urban Development (HUD) gives notice of its intent to rescind the Office of Public and Indian Housing (PIH), Real Estate Assessment Center (REAC) Privacy Act system of records titled One Stop Customer Service (OSCS). HUD has determined that OSCS is duplicative and that its functions are fully covered under the Customer Relationship Management (CRM) system of records (SOR). Records previously maintained in OSCS were consolidated into CRM as of October 30, 2024, which provides comprehensive coverage for customer service interactions across HUD programs.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This action is effective immediately upon publication. July 6, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by docket number or one of the following methods:</P>
                    <P>
                        <E T="03">Federal e-Rulemaking Portal: http://www.regulations.gov.</E>
                         Follow the instructions provided on that site to submit comments electronically.
                    </P>
                    <P>
                        <E T="03">Fax:</E>
                         202-619-8365.
                    </P>
                    <P>
                        <E T="03">Email: privacy@hud.gov.</E>
                    </P>
                    <P>
                        <E T="03">Mail:</E>
                         Attention: Privacy Office; Kimberly Morton, Acting Chief Privacy Officer; The Executive Secretariat; 451 7th Street SW, Room 10139; Washington, DC 20410-0001.
                    </P>
                    <P>
                        All submissions received must include the agency name and docket number. All comments received will be posted without change to 
                        <E T="03">http://www.regulations.gov,</E>
                         including any personal information provided.
                    </P>
                    <P>
                        For access to the docket to read background documents or comments received, go to 
                        <E T="03">http://www.regulations.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Kimberly Morton, Acting Chief Privacy Officer, 451 7th Street SW, Room 10139, Washington, DC 20410-0001; telephone number (804) 822-4801. 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 has consolidated the functions previously performed by OSCS into the CRM SOR (Docket No. FR-7092-N-39, 89 FR 86352, October 30, 2024). CRM documents the collection, maintenance, and use of information within HUD's customer relationship platforms, including Microsoft Dynamics and HUD Central, to manage, track, route, and respond to customer service inquiries and interactions across HUD programs. As a result of this consolidation, records formerly maintained in OSCS (Under GRS Authority: DAA-GRS-2017-0003-0002; Temporary. Destroy upon verification of successful creation of the final document or file, or when no longer needed for business use, or whichever is later.) are now managed under CRM, and OSCS is no longer necessary as a separate SOR.</P>
                <PRIACT>
                    <HD SOURCE="HD1">SYSTEM NAME AND NUMBER:</HD>
                    <P>One Stop Customer Service (OSCS), HUD-PIH 03.</P>
                    <HD SOURCE="HD2">HISTORY:</HD>
                    <P>Docket No. FR-7077-N-10, 88 FR 44389, July 12, 2023.</P>
                </PRIACT>
                <SIG>
                    <NAME>Kimberly Morton,</NAME>
                    <TITLE>Acting Chief Privacy Officer, Office of Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13543 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4210-67-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT</AGENCY>
                <DEPDOC>[Docket No. FR-6607-N-01]</DEPDOC>
                <SUBJECT>Section 8 Housing Assistance Payments Program—Fiscal Year (FY) 2026 Inflation Factors for Public Housing Agency (PHA) Renewal Funding</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Assistant Secretary for Policy Development and Research, HUD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This notice establishes Renewal Funding Inflation Factors (RFIFs) to adjust Fiscal Year (FY) 2026 renewal funding for the Housing Choice Voucher (HCV) Program of each public housing agency (PHA), as required by the Transportation, Housing and Urban Development, and Related Agencies Appropriations Act, 2026, enacted as part of the Consolidated Appropriations Act, 2026. The notice apportions the expected percent change in national Per Unit Cost (PUC) for the HCV program, 2.337 percent, to each PHA based on the change in Fair Market Rent (FMR) for their operating area(s) to produce the FY 2026 RFIFs. HUD continues to use the methodology refined in FY 2025 to produce the national PUC forecast. This approach adjusts the gross rent component by empirically weighting projected recent-mover rents, as measured by the FMR, with an independent forecast of all-mover rents, as measured by the Consumer Price Index (CPI). In addition, HUD is seeking comment on potential RFIF methodological changes it is considering for FY 2027 which would 
                        <PRTPAGE P="41059"/>
                        incorporate an additional factor to partially adjust the local inflation adjustment an area would otherwise receive if there is indication that local land use policies, permitting policies, or other local regulatory housing policies may be influencing local inflation in rents.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The FY 2026 Renewal Funding Inflation Factors are effective July 6, 2026.</P>
                    <P>
                        <E T="03">Comments are due:</E>
                         August 5, 2026.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>HUD invites interested persons to submit comments regarding the renewal funding inflation factor methodology. Communications must refer to the above docket number and title. There are two methods for submitting public comments:</P>
                    <P>
                        1. 
                        <E T="03">Electronic Submission of Comments.</E>
                         Interested persons may submit comments electronically through the Federal eRulemaking Portal at 
                        <E T="03">https://www.regulations.gov.</E>
                         HUD strongly encourages commenters to submit comments electronically. Electronic submission of comments allows the author maximum time to prepare and submit a comment, ensures timely receipt by HUD, and enables HUD to make them immediately available to the public. Comments submitted electronically through the 
                        <E T="03">https://www.regulations.gov</E>
                         website can be viewed by other submitters and interested members of the public. Commenters follow the instructions provided on that site to submit comments electronically.
                    </P>
                    <P>
                        2. 
                        <E T="03">Submission of Comments by Mail.</E>
                         Members of the public may submit comments by mail to the Regulations Division, Office of General Counsel, Department of Housing and Urban Development, 451 7th Street SW, Room 10276, Washington, DC 20410-0500.
                    </P>
                </ADD>
                <NOTE>
                    <HD SOURCE="HED">Note:</HD>
                    <P>To receive consideration as public comments, comments or requests must be submitted through one of the two methods specified above. Again, all submissions must refer to the docket number and title of the notice.</P>
                </NOTE>
                <P>No Facsimile Comments. HUD does not accept facsimile (FAX) comments.</P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Miguel A. Fontanez, Director, Housing Voucher Financial Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Room 4222, Department of Housing and Urban Development, 451 Seventh Street SW, Washington, DC 20410; telephone (202) 422-0278 (this is not a toll-free number). Adam Bibler, Program Parameters and Research Division, Office of Policy Development and Research, Room 8208, Department of Housing and Urban Development, 451 Seventh Street SW, Washington, DC 20410; telephone (202) 402-6057 (this is not a toll-free number), for technical information regarding the development of the schedules for specific areas or the methods used for calculating the inflation factors. 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>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    Division D, Title II of the Consolidated Appropriations Act, 2026, requires that the HUD Secretary, for the calendar year 2026 funding cycle, provide renewal funding for each PHA based on validated voucher management system (VMS) leasing and cost data for the prior calendar year and by applying an inflation factor, as established by the Secretary, by notice published in the 
                    <E T="04">Federal Register</E>
                    . This notice announces the FY 2026 inflation factors and describes the methodology for calculating them. Tables in PDF and Microsoft Excel formats showing RFIFs by HUD FMR Area are available electronically at: 
                    <E T="03">https://www.huduser.gov/portal/datasets/rfif/rfif.html.</E>
                </P>
                <HD SOURCE="HD1">II. Methodology</HD>
                <P>
                    RFIFs are used to adjust the allocation of HCV renewal funds to PHAs for local changes in rents, utility costs, and tenant incomes. To calculate the RFIFs, HUD first forecasts a national inflation factor, which is the annual change in the national average PUC. HUD then calculates individual area inflation factors, which are based on the annual change in the two-bedroom FMR for each area. Finally, HUD adjusts the individual area inflation factors to be consistent with the national inflation factor.
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See</E>
                         42 U.S.C. 1437f(dd).
                    </P>
                </FTNT>
                <P>Since FY 2017, HUD's method of projecting the national average PUC has been based on independent forecasts of gross rent and tenant income. Each forecast is produced using historical and forecasted macroeconomic data as independent variables, where the macroeconomic data forecasts are consistent with the Economic Assumptions of the Administration's Budget. HUD calculates a “notional” PUC as the difference between the gross rent value and 30 percent of tenant income (the standard for tenant rent contribution in the voucher program). HUD uses a notional PUC as opposed to the actual PUC to project costs that are consistent with PHAs leasing the same number and quality of units. The change between the forecasted CY 2026 notional PUC and the CY 2025 notional PUC is the expected national change in PUC, which for 2026 is 2.337 percent.</P>
                <P>
                    HUD continues to use the methodology refined in FY 2025 for developing the gross rent component of the national PUC forecast. Under this approach, the gross rent component is based on a combination of projected recent-mover rents, as represented by the national average FMR, and rents for in-place tenants, as represented by the national gross rent CPI. By regulation, FMRs are required to reflect rents paid by recent movers, which HUD defines as renter households that moved into their current residence within the past one or two years. For purposes of forecasting PUC, the gross rent component is intended to reflect the full composition of tenants in the HCV program, including new admissions and recent movers as well as those staying in place. When calculating the gross rent component of PUCs, the national FMR is weighted at approximately 56 percent, and the national CPI gross rent inflation index measure is weighted at approximately 44 percent, unchanged from the weights used in 2025. HUD determined the weights empirically in a manner that best predicts the historical voucher tenant's average gross rents.
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Specifically, HUD attempted to predict each year's tenant gross rent using a weighted average of FMR and CPI change, then compared the predicted gross rent to the actual historical gross rent. HUD then generated an error measure as the difference between the predicted and actual rent. HUD then solved for the weights that minimize the root mean squared error of the predicted and actual rents. HUD updated this calculation with actual data through 2025.
                    </P>
                </FTNT>
                <P>
                    The inflation factor for an individual geographic area is based on the change in the area's two bedroom FMR between FY 2025 and FY 2026. These changes in FMRs are then scaled such that the voucher-weighted average of all individual area inflation factors is equal to the national inflation factor, 
                    <E T="03">i.e.,</E>
                     the expected annual change in national PUC from CY 2025 to CY 2026, and such that no area has a factor less than one. For PHAs operating in multiple FMR areas, HUD calculates a voucher-weighted average inflation factor based on the count of vouchers in each FMR area administered by the PHA as captured in HUD administrative data as of December 31, 2025.
                    <PRTPAGE P="41060"/>
                </P>
                <HD SOURCE="HD1">III. The Use of Inflation Factors</HD>
                <P>HUD subsequently applies the calculated individual area inflation factors to eligible renewal funding for each PHA based on VMS leasing and cost data for the prior calendar year.</P>
                <HD SOURCE="HD1">IV. Geographic Areas and Area Definitions</HD>
                <P>
                    As explained above, inflation factors based on area FMR changes are produced for all FMR areas and applied to eligible renewal funding for each PHA. The tables showing the RFIFs, available electronically from the HUD data information page, list the inflation factors for each FMR area on a state-by-state basis. The inflation factors use the same Office of Management and Budget (OMB) metropolitan area definitions, as revised by HUD, that are used in FY 2026 FMRs. PHAs should refer to the Area Definitions Table on the following web page to make certain that they are referencing the correct inflation factors: 
                    <E T="03">http://www.huduser.org/portal/datasets/rfif/FY2026/FY2026_RFIF_FMR_AREA_REPORT.pdf.</E>
                     The Area Definitions Table lists areas in alphabetical order by state and the counties associated with each area. In the six New England states, the listings are for counties or parts of counties as defined by towns or cities. Note that for purposes of RFIF calculation and publication, HUD groups all towns in Connecticut with their respective metropolitan statistical areas or non-metropolitan planning district, unlike the FY 2026 FMR publication, where HUD listed certain towns as exception areas to preserve the limit on year-to-year declines in FMRs. HUD is also releasing the data in Microsoft Excel format to assist users who may wish to use these data in other calculations. The Excel file is available at 
                    <E T="03">https://www.huduser.gov/portal/datasets/rfif/rfif.html.</E>
                     Note that, as described earlier, the actual renewal funding inflation factor applied to agency funding will be the voucher-weighted average of the FMR area factors when the PHA operates in multiple areas.
                </P>
                <HD SOURCE="HD1">V. Request for Comment</HD>
                <P>HUD accepts public comments on the methods used to calculate renewal funding inflation factors for 30 days after the publication of this notice. Although HUD will not adjust the FY 2026 inflation factors, HUD will consider any comments for potential changes to the RFIF methodology in FY 2027.</P>
                <P>In addition to seeking general public comments on the FY 2026 methodology, HUD is considering further changes to the local inflation factor for incorporation into the FY 2027 RFIF. As described in the Methodology section above, HUD uses the RFIF to calculate HCV renewal funds to account for local changes in rents and utility costs, and national changes in tenant incomes. Among other requirements, Division D, Title II of the Consolidated Appropriations Act, 2026 requires the Secretary to incorporate an inflation factor in its allocation formula, and HUD's methodology currently adjusts allocations both based on local inflation (as measured by the two-bedroom FMR for each area) and by a national inflation factor. However, local housing and land-use policies can influence the cost of housing by altering the supply of housing. On the margin, the current RFIF methodology may result in increasing the relative allocation of HCV funding toward PHAs in jurisdictions where local housing inflation is driven by local policies and decreasing the relative allocation to PHAs in jurisdictions that have done a more effective job calibrating local policies to address housing demand.</P>
                <P>HUD is considering whether, beginning with the FY 2027 RFIF, it should refine the local inflation component of the RFIF methodology to incorporate an additional factor which considers the extent to which rent inflation in a local market may be influenced by local land use policies, permitting practices, or other local regulatory or policy factors that impact new housing supply. HUD recognizes that local rent growth may reflect multiple factors, including changes in demand, construction costs, interest rates, utility costs, tenant income, and regulatory constraints. At the same time, HUD is interested in whether the RFIF methodology could be improved to avoid allocating shares of renewal funding to areas where rent increases may be substantially impacted by policy-driven determinants of housing supply.</P>
                <P>HUD seeks comment on whether and how any such adjustment could be designed using objective, transparent, and annually available measures.</P>
                <P>HUD specifically seeks comment on the following questions:</P>
                <P>1. Should HUD consider adjusting the FY 2027 RFIF methodology to incorporate a factor that discounts the full local inflation adjustment in areas where there is an indication that housing supply is relatively constrained, such as constraints on land use, permitting, or development approval policies? Should HUD consider incorporating a markup on the full local inflation adjustments in areas where there is an indication that housing supply is relatively unconstrained?</P>
                <P>2. What type of factor could HUD incorporate into the RFIF methodology to modify the full inflation adjustment for areas with particularly high or low housing supply or regulatory restrictions on housing construction?</P>
                <P>3. What data sources that are already publicly available and regularly updated should HUD consider using in developing a factor that identifies areas with particularly high or low housing supply or regulatory restrictions on housing construction? Should HUD consider, for example, building permits issued or housing completions, housing units relative to population or job growth, rent-to-income trends, price-to-construction cost ratios, or some other measure or measures? What sources provide this information? How should HUD incorporate the measure(s) into the inflation factor?</P>
                <P>4. What methodologies exist to effectively provide comparative restrictiveness of land-use policies across jurisdictions that have in place a wide variety (both in number and scale) of housing-related policies?</P>
                <P>
                    5. Given that local rent inflation may be affected by factors not controllable by a jurisdiction, such as changes in demand, construction costs, interest rates, or utility costs, how could HUD calibrate this factor to account both for particularly high or low housing supply 
                    <E T="03">and,</E>
                     respectively, significant or limited regulatory restrictions to housing construction?
                </P>
                <P>6. Should the methodology consider only year-over-year changes or account for multi-year periods?</P>
                <P>7. If HUD were to set a cap or limit to how much the local inflation factor would be altered for areas where it is determined that supply or regulations on housing construction are impacting local inflation, what should that limit be and how should HUD incorporate it into the formula?</P>
                <P>
                    8. Given that many PHAs administer a small number of HCVs, are there other ways that HUD could target this methodological change toward areas where it may have the greatest impact while minimizing complexity, such as, for example, only applying the alternative methodology to PHAs that administer above a certain threshold of HCVs (
                    <E T="03">e.g.</E>
                     2,000 HCVs annually)?
                </P>
                <P>
                    9. Are there other methodological, programmatic, regulatory, or statutory considerations HUD should take into account when developing this factor?
                    <PRTPAGE P="41061"/>
                </P>
                <HD SOURCE="HD1">VI. Environmental Impact</HD>
                <P>This notice involves a statutorily required establishment of a rate or cost determination which does not constitute a development decision affecting the physical condition of specific project areas or building sites. Accordingly, under 24 CFR 50.19(c)(6), this notice is categorically excluded from environmental review under the National Environmental Policy Act of 1969 (42 U.S.C. 4321).</P>
                <SIG>
                    <NAME>Todd Richardson,</NAME>
                    <TITLE>General Deputy Assistant Secretary for Policy Development and Research.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13542 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4210-67-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT</AGENCY>
                <DEPDOC>[Docket No. FR-6534-N-03]</DEPDOC>
                <SUBJECT>Notice of Regulatory Waiver Requests Granted for the Third Quarter of Calendar Year 2025</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the General Counsel, HUD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        Section 106 of the Department of Housing and Urban Development Reform Act of 1989 (the HUD Reform Act) requires HUD to publish quarterly 
                        <E T="04">Federal Register</E>
                         notices of all regulatory waivers that HUD has approved. Each notice covers the quarterly period since the previous 
                        <E T="04">Federal Register</E>
                         notice. The purpose of this notice is to comply with the requirements of section 106 of the HUD Reform Act. This notice contains a list of regulatory waivers granted by HUD during the period beginning on July 1, 2025 and ending on September 30, 2025.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>For general information about this notice, contact Amanda Wahlig, Acting Associate General Counsel for Legislation and Regulations, Department of Housing and Urban Development, 451 7th Street SW, Room 10282, Washington, DC 20410-0500, telephone 202-708-5300 (this is not a toll-free number). HUD welcomes and is prepared to receive calls from individuals who are deaf or hard of hearing, as well as individuals with speech and communication disabilities.</P>
                    <P>
                        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>
                    <P>For information concerning a particular waiver that was granted and for which public notice is provided in this document, contact the person whose name and address follow the description of the waiver granted in the accompanying list of waivers that have been granted in the third quarter of calendar year 2025.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Section 106 of the HUD Reform Act added a new section 7(q) to the Department of Housing and Urban Development Act (42 U.S.C. 3535(q)), which provides that:</P>
                <P>1. Any waiver of a regulation must be in writing and must specify the grounds for approving the waiver;</P>
                <P>2. Authority to approve a waiver of a regulation may be delegated by the Secretary only to an individual of Assistant Secretary or equivalent rank, and the person to whom authority to waive is delegated must also have authority to issue the particular regulation to be waived;</P>
                <P>
                    3. Not less than quarterly, the Secretary must notify the public of all waivers of regulations that HUD has approved, by publishing a notice in the 
                    <E T="04">Federal Register</E>
                    . These notices (each covering the period since the most recent previous notification) shall:
                </P>
                <P>a. Identify the project, activity, or undertaking involved;</P>
                <P>b. Describe the nature of the provision waived and the designation of the provision;</P>
                <P>c. Indicate the name and title of the person who granted the waiver request;</P>
                <P>d. Describe briefly the grounds for approval of the request; and</P>
                <P>e. State how additional information about a particular waiver may be obtained.</P>
                <P>Section 106 of the HUD Reform Act also contains requirements applicable to waivers of HUD handbook provisions that are not relevant to the purpose of this notice.</P>
                <P>This notice follows procedures provided in HUD's Statement of Policy on Waiver of Regulations and Directives issued on April 22, 1991 (56 FR 16337). In accordance with those procedures and with the requirements of section 106 of the HUD Reform Act, waivers of regulations are granted by the Assistant Secretary with jurisdiction over the regulations for which a waiver was requested. In those cases in which a General Deputy Assistant Secretary granted the waiver, the General Deputy Assistant Secretary was serving in the absence of the Assistant Secretary in accordance with the office's Order of Succession.</P>
                <P>This notice covers waivers of regulations granted by HUD from July 1, 2025 through September 30, 2025. For ease of reference, the waivers granted by HUD are listed by HUD program office (for example, the Office of Community Planning and Development, the Office of Fair Housing and Equal Opportunity, the Office of Housing, and the Office of Public and Indian Housing, etc.). Within each program office grouping, the waivers are listed sequentially by the regulatory section of title 24 of the Code of Federal Regulations (CFR) that is being waived. For example, a waiver of a provision in 24 CFR part 58 would be listed before a waiver of a provision in 24 CFR part 570.</P>
                <P>Where more than one regulatory provision is involved in the grant of a particular waiver request, the action is listed under the section number of the first regulatory requirement that appears in 24 CFR and that is being waived. For example, a waiver of both § 58.73 and § 58.74 would appear sequentially in the listing under § 58.73.</P>
                <P>Waiver of regulations that involve the same initial regulatory citation are in time sequence beginning with the earliest-dated regulatory waiver.</P>
                <P>Should HUD receive additional information about waivers granted during the period covered by this report (the third quarter of calendar year 2025) before the next report is published (the fourth quarter of calendar year 2025), HUD will include any additional waivers granted for the third quarter in the next report.</P>
                <P>Accordingly, information about approved waiver requests pertaining to HUD regulations is provided in the Appendix that follows this notice.</P>
                <SIG>
                    <NAME>David C. Woll,</NAME>
                    <TITLE>General Counsel.</TITLE>
                </SIG>
                <HD SOURCE="HD1">Appendix</HD>
                <EXTRACT>
                    <HD SOURCE="HD1">Listing of Waivers of Regulatory Requirements Granted by Offices of the Department of Housing and Urban Development July 1, 2025 Through September 30, 2025</HD>
                    <P>
                        <E T="03">Note to Reader:</E>
                         More information about the granting of these waivers, including a copy of the waiver request and approval, may be obtained by contacting the person whose name is listed as the contact person directly after each set of regulatory waivers granted.
                    </P>
                    <P>The regulatory waivers granted appear in the following order:</P>
                    <FP SOURCE="FP-2">I. Regulatory waivers granted by the Office of Community Planning and Development.</FP>
                    <FP SOURCE="FP-2">II. Regulatory waivers granted by the Office of Housing</FP>
                    <FP SOURCE="FP-2">III. Regulatory waivers granted by the Office of Public and Indian Housing</FP>
                    <HD SOURCE="HD1">I. Regulatory Waivers Granted by the Office of Community Planning and Development</HD>
                    <P>
                        For further information about the following regulatory waivers, please see the name of the contact person that immediately follows the description of the waiver granted.
                        <PRTPAGE P="41062"/>
                    </P>
                    <P>• Regulation: 24 CFR 92.103(b)(3).</P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         The City of Miami Gardens, Florida requested a waiver of 24 CFR 92.103(b)(3) to allow additional time for the City Council to budget and approve the balance of funding needed to meet the participation threshold to become a participating jurisdiction under the HOME Investment Partnerships Program (HOME).
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         The HOME regulation at 24 CFR 92.103(b)(3) applies to a unit of local government that intends to become a participating jurisdiction and qualified for a formula allocation of less than $500,000 in fiscal years in which Congress appropriates less than $1.5 billion for the HOME program. In such case, this provision requires that the unit of general local government must submit, with its notice of intent, evidence that it has met the threshold allocation requirements of 24 CFR 92.102(b) including a letter from its chief executive officer indicating that the required funds have been approved and budgeted.
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         David C. Woll, Jr., Principal Deputy Assistant Secretary for Community Planning and Development.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         July 7, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         The Department determined that a waiver of 24 CFR 92.103(b)(3) is justified based on the need for the city council to budget and approve the balance of funds needed to meet the HOME participation threshold of $500,000. This waiver will ensure that the city has enough time to budget and approve the funding, so that it may become a HOME participating jurisdiction.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Peter Huber, Acting Director, Office of Affordable Housing Programs, Office of Community Planning and Development, Department of Housing and Urban Development, 451 Seventh Street SW, Room 7282, Washington, DC 20410, telephone (202) 402-3941, email: 
                        <E T="03">Peter.H.Huber@hud.gov</E>
                        .
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 92.214(a)(6).
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Macomb County, Michigan, requested a waiver of 24 CFR 92.214(a)(6) to permit it to invest additional HOME Investment Partnerships Program (HOME) funds in Oakwood Manor Senior Living, a HOME-assisted rental project, for the development of additional affordable housing units and expansion of the existing community center. The existing rental project is midway through its 20-year period of affordability.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         The HOME regulation at 24 CFR 92.214(a)(6) prohibits a participating jurisdiction from investing additional HOME funds in a previously assisted HOME project during its required affordability period.
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Bryan Horn, Acting Principal Deputy Assistant Secretary for Community Planning and Development.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         August 11, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         The Department determined that the proposed development of 22 affordable units on vacant land on the Oakwood Manor Senior Living project site would provide a cost-effective means of increasing the number of affordable units in the community while not negatively impacting the existing HOME project. Therefore, the waiver was granted to permit the County to invest additional HOME funds for the production of 22 affordable rental housing units for seniors and to expand the existing community center.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Peter Huber, Acting Director, Office of Affordable Housing Programs, Office of Community Planning and Development, Department of Housing and Urban Development, 451 Seventh Street SW, Room 7282, Washington, DC 20410, (202) 402-3941, email 
                        <E T="03">Peter.H.Huber@hud.gov.</E>
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         Section 104(b)(3) of the Housing and Community Development Act of 1974, as amended (HCDA), 42 U.S.C. 5304(b)(3), and 24 CFR 570.484, as modified by the 
                        <E T="04">Federal Register</E>
                         notices published at 87 FR 31636 on May 24, 2022, and 88 FR 3198 on January 18, 2023; 24 CFR 570.208(a)(1) and 24 CFR 570.483(b)(1).
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Community Development Block Grant Disaster Recovery (CDBG-DR) funds allocated to the State of Washington pursuant to the Department of Housing and Urban Development (HUD) Appropriations Act, 2021 (Pub. L. 117-43) for major disasters occurring in 2021 (the “Appropriations Act”), as provided under the allocations announced in the May 24, 2022, Notice (87 FR 31636) and January 18, 2023, Notice (88 FR 3198), and as modified by Memorandum 22-01 on December 7, 2022 (the “Prior Notices”). This waiver and alternative requirement applies to infrastructure projects where the service area has less than 51 percent low- and moderate-income (LMI) residents, allowing the State of Washington to apply proportional infrastructure costs toward meeting the overall LMI benefit requirement under 24 CFR 570.484.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         HUD allocated CDBG-DR funds to the State of Washington under the May 24, 2022, Notice (87 FR 31636) and the January 18, 2023, Notice (88 FR 3198), as modified by Memorandum 22-01 (together, the “Prior Notices”). These notices, combined with 24 CFR 570.484, require grantees to meet the overall benefit requirement by ensuring that at least 70 percent of CDBG-DR funds benefit low- and moderate-income (LMI) persons. For infrastructure projects using the low- and moderate-income area (LMA) benefit national objective, the Prior Notices require that LMI residents comprise at least 51 percent of the project's service area.
                    </P>
                    <P>In response to a request from the State of Washington, this waiver and alternative requirement (1) permits the State to count proportional infrastructure costs toward meeting the LMI overall benefit threshold in service areas with less than 51 percent LMI residents, and (2) allows the State to multiply the total cost of an activity by the percentage of LMI persons in the service area, provided that the amount counted does not exceed the CDBG-DR funds invested. This flexibility enables the State to implement large-scale infrastructure projects, better reflect the benefits to LMI residents, and maintain compliance with the 70 percent overall benefit requirement for its 2021 CDBG-DR grant, while supporting critical disaster recovery and mitigation efforts.</P>
                    <P>
                        <E T="03">Granted By:</E>
                         Bryan W. Horn, Acting Principal Deputy Assistant Secretary for Community Planning and Development.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 29, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         The State of Washington demonstrated good cause that large-scale infrastructure projects funded under its 2021 CDBG-DR allocation provide significant benefits to LMI persons, but due to broad service areas, the percentage of LMI residents falls below the 51 percent threshold required for the LMA national objective. Without the requested waiver, the State would be unable to meet the 70 percent overall LMI benefit requirement, given that a substantial portion of its allocation is dedicated to infrastructure and mitigation activities. HUD determined that the waiver and alternative requirement are not inconsistent with the overall purposes of Title I of the HCDA and will allow the State of Washington to calculate proportional LMI benefit for infrastructure activities by multiplying total project costs by the percentage of LMI persons in the service area, not to exceed the amount of CDBG-DR funds invested.
                    </P>
                    <P>
                        <E T="03">Applicability:</E>
                         This waiver and alternative requirement is applicable solely to the 2021 CDBG-DR funds awarded to the State of Washington under Public Law 117-43. It allows the State to calculate proportional LMI benefit for infrastructure projects in service areas with less than 51 percent LMI residents, for purposes of meeting the 70 percent overall LMI benefit requirement. The waiver and alternative requirement are effective as of September 29, 2025, and remain in effect for the duration of the State's 2021 CDBG-DR grant.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Gerilee W. Bennett, Acting Director, Office of Disaster Recovery, Office of Community Planning and Development, Department of Housing and Urban Development, 451 Seventh Street SW, Room 7282, Washington, DC 20410, telephone (202) 708-3587, email: 
                        <E T="03">Gerilee.W.Bennett@hud.gov.</E>
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         Sections II, III, and IV of the Consolidated Notice (Appendix B to HUD's Community Development Block Grant Disaster Recovery (CDBG-DR) notices published in the 
                        <E T="04">Federal Register</E>
                         on May 24, 2022, at 87 FR 31636 (the “May 2022 Notice”) and May 18, 2023, at 88 FR 32046 (the “May 2023 Notice”)), as modified by Memorandum 22-01 for Detroit, Michigan.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         CDBG-DR funds allocated to the City of Detroit, Michigan, pursuant to the Department of Housing and Urban Development (HUD) Appropriations Act, 2023 (Pub. L. 117-43), for major disasters occurring in 2021, and St. Clair County, Illinois, pursuant to the Department of Housing and Urban Development (HUD) Appropriations Act, 2023 (Pub. L. 117-328) for major disasters occurring in 2022 (the “Appropriations Acts”).
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         HUD allocated CDBG-DR funds to the City of Detroit, Michigan, under the May 2022 Notice and to St. Clair County, Illinois, under the May 2023 Notice, both of which include the Consolidated Notice as Appendix B.
                    </P>
                    <P>
                        Sections II, III, and IV of the Consolidated Notice and the May 2022 and May 2023 Notices establish the administrative, planning, and program implementation requirements for grantees receiving CDBG-DR funding, including Action Plan 
                        <PRTPAGE P="41063"/>
                        development, policies and procedures, and compliance with reporting and grant management requirements.
                    </P>
                    <P>In response to requests from the City of Detroit and St. Clair County, this waiver and alternative requirement (1) allows the grantees to apply the requirements of sections I, II, and III and appendices A, B, and C of the Universal Notice (published at 90 FR 1754 on January 8, 2025, as amended), in lieu of the corresponding provisions in the May 2022 or May 2023 Notices and the Consolidated Notice, and (2) permits the grantees to align policies and procedures across multiple CDBG-DR allocations for the 2021 (Detroit) and 2022 (St. Clair County) disasters, reducing administrative burden and supporting coordinated recovery efforts.</P>
                    <P>
                        <E T="03">Granted By:</E>
                         Bryan W. Horn, Acting Principal Deputy Assistant Secretary for Community Planning and Development.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 29, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         The City of Detroit and St. Clair County demonstrated good cause that aligning the requirements of their CDBG-DR funds with the Universal Notice would reduce administrative burden, enhance long-term project viability, and ensure consistent treatment of subrecipients and program beneficiaries across multiple disaster allocations. HUD determined that waiving sections II, III, and IV of the May 2022 and May 2023 Notices, and the Consolidated Notice at Appendix B, and replacing them with the Universal Notice's requirements is not inconsistent with the overall purposes of Title I of the HCDA, provided that the grantees revise their Action Plans and program-specific policies accordingly.
                    </P>
                    <P>
                        <E T="03">Applicability:</E>
                         This waiver and alternative requirement is applicable solely to CDBG-DR funds awarded to the City of Detroit, Michigan, for a disaster occurring in 2021 under Public Law 117-43, and to St. Clair County, Illinois, for a disaster occurring in 2022 under Public Law 117-328. The waiver allows these grantees to adopt the Universal Notice requirements in lieu of prior notice requirements, for the duration of their respective CDBG-DR grants.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Gerilee W. Bennett, Acting Director, Office of Disaster Recovery, Office of Community Planning and Development, Department of Housing and Urban Development, 451 Seventh Street SW, Room 7282, Washington, DC 20410, telephone (202) 708-3587, email: 
                        <E T="03">Gerilee.W.Bennett@hud.gov.</E>
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         Sections II, III, and IV of the Consolidated Notice (Appendix B to HUD's Community Development Block Grant Disaster Recovery (CDBG-DR) notice published in the 
                        <E T="04">Federal Register</E>
                         on November 27, 2023, at 88 FR 82982 (the “November 2023 Notice”)).
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         CDBG-DR funds allocated to the State of Alabama, the State of California, and the State of Georgia pursuant to the Department of Housing and Urban Development (HUD) Appropriations Act, 2023 (Pub. L. 117-328), for major disasters occurring in January 2023 (the “Appropriations Act”), as provided under the allocations announced in the November 27, 2023, Notice (88 FR 82982). This waiver and alternative requirement applies to all activities funded under these allocations, allowing the States to apply the requirements in the Universal Notice, including sections I through V and appendices A through C, uniformly across their CDBG-DR grants.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         HUD allocated CDBG-DR funds to the States of Alabama, California, and Georgia under the November 2023 Notice, which includes the Consolidated Notice as Appendix B.
                    </P>
                    <P>Sections II, III, and IV of the Consolidated Notice and the November 2023 Notice establish the administrative, planning, and program implementation requirements for grantees receiving CDBG-DR funding, including the development of Action Plans, adoption of program-specific policies and procedures, and compliance with reporting and grant management requirements.</P>
                    <P>In response to requests from Alabama, California, and Georgia, this waiver and alternative requirement (1) allows the grantees to apply the requirements of sections I, II, and III and appendices A, B, and C of the Universal Notice (published at 90 FR 1754 on January 8, 2025, as amended), in lieu of the corresponding provisions in the November 2023 Notice and the Consolidated Notice, and (2) permits the grantees to align policies and procedures across multiple CDBG-DR allocations for the January 2023 disasters, reducing administrative burden and supporting coordinated recovery efforts.</P>
                    <P>
                        <E T="03">Granted By:</E>
                         Bryan W. Horn, Acting Principal Deputy Assistant Secretary for Community Planning and Development.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 29, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         The States demonstrated good cause that aligning the requirements of their January 2023 disaster allocations with the Universal Notice would reduce administrative burden, provide consistent requirements across multiple funding awards, and enhance program efficiency. HUD determined that waiving sections II, III, and IV of the November 2023 Notice and the Consolidated Notice at Appendix B and adopting the Universal Notice's requirements is not inconsistent with the overall purposes of Title I of the HCDA, provided the States revise their Action Plans and program-specific policies accordingly.
                    </P>
                    <P>
                        <E T="03">Applicability:</E>
                         This waiver and alternative requirement is applicable solely to CDBG-DR funds awarded to the State of Alabama, the State of California, and the State of Georgia for disasters occurring in January 2023 under Public Law 117-328. It allows these grantees to adopt the Universal Notice requirements in lieu of the November 2023 Notice and Consolidated Notice requirements for the duration of their respective CDBG-DR grants.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Gerilee W. Bennett, Acting Director, Office of Disaster Recovery, Office of Community Planning and Development, Department of Housing and Urban Development, 451 Seventh Street SW, Room 7282, Washington, DC 20410, telephone (202) 708-3587, email: 
                        <E T="03">Gerilee.W.Bennett@hud.gov.</E>
                    </P>
                    <P>
                        <E T="03">Regulation:</E>
                         Paragraph III.F.5 of the Consolidated Notice (Appendix B to HUD's Community Development Block Grant Disaster Recovery (CDBG-DR) notice published in the 
                        <E T="04">Federal Register</E>
                         on May 18, 2023, at 88 FR 32046) (the “May 2023 Notice”), as modified by Memorandum 24-02.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         CDBG-DR funds allocated to Sarasota County, Florida, pursuant to the Department of Housing and Urban Development (HUD) Appropriations Act, 2023 (Pub. L. 117-328), for major disasters occurring in 2022 (the “Appropriations Act”), as provided under the allocations announced in the May 18, 2023, Notice (88 FR 32046) and as modified by Memorandum 24-02 on August 8, 2024 (the “Prior Notices”). This waiver and alternative requirement apply to the Homeowner Reimbursement Program, extending the reimbursement application deadline for an additional year beyond the previously approved timeline to allow more disaster survivors to apply.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         HUD allocated CDBG-DR funds to Sarasota County, Florida, under the May 2023 Notice, which includes the Consolidated Notice as Appendix B. Paragraph III.F.5 of the Consolidated Notice permits grantees to reimburse eligible pre-application costs incurred by homeowners, renters, businesses, and other qualifying entities, provided such costs were incurred within one year after the applicability date of the Allocation Announcement Notice or the date of the disaster, whichever is later. Sarasota County previously received a one-year extension under Memorandum 24-02, extending the reimbursement deadline from May 23, 2024, to May 23, 2025.
                    </P>
                    <P>In response to a request from Sarasota County, this waiver and alternative requirement (1) grants a second one-year extension of the reimbursement deadline to May 23, 2026, and (2) permits the County to reimburse beneficiaries who applied for eligible pre-application costs between May 23, 2025, and the applicability date of this memorandum, provided all other requirements in paragraph III.F.5 are satisfied. This extension will allow additional recovery assistance to more eligible low- and moderate-income households, reducing administrative burden and supporting recovery efforts.</P>
                    <P>
                        <E T="03">Granted By:</E>
                         Bryan W. Horn, Acting Principal Deputy Assistant Secretary for Community Planning and Development.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 29, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         Sarasota County requested a waiver to extend the reimbursement deadline from May 23, 2025, to May 23, 2026, due to widespread insurance delays, contractor shortages, and persistent challenges impacting homeowner recovery, particularly for low- and moderate-income households. HUD determined there is good cause to extend the deadline and provided an alternative requirement permitting reimbursement for pre-application costs incurred between May 23, 2025, and the applicability date of this memorandum, provided other requirements of Section III.F.5 are met.
                    </P>
                    <P>
                        <E T="03">Applicability:</E>
                         This waiver and alternative requirement is applicable solely to CDBG-DR funds awarded to Sarasota County, Florida, for disasters occurring in 2022 under Public Law 117-328. It extends the reimbursement application deadline for eligible pre-application costs under Section III.F.5 of the Consolidated Notice to May 23, 2026.
                        <PRTPAGE P="41064"/>
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Gerilee W. Bennett, Acting Director, Office of Disaster Recovery, Office of Community Planning and Development, Department of Housing and Urban Development, 451 Seventh Street SW, Room 7282, Washington, DC 20410, telephone (202) 664-9481, email: 
                        <E T="03">Gerilee.W.Bennett@hud.gov.</E>
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         2 CFR 200.414 and the Part 200 appendices that grantees attach an approved indirect cost rate schedule to their Community Development Block Grant Disaster Recovery (CDBG-DR) grant agreements.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         CDBG-DR funds allocated to the Texas General Land Office (GLO) pursuant to the Department of Housing and Urban Development (HUD) Appropriations Act, 2021 (Pub. L. 117-43) and 2025 (Pub. L. 118-158), for major disasters occurring in 2021 and 2024, as provided under the allocations announced in the applicable CDBG-DR 
                        <E T="04">Federal Register</E>
                         Notices. This waiver and alternative requirement applies to the grantee's attachment of its indirect cost rate schedule and the use of the provisional indirect cost rate of 58.90 percent in grant agreements for disasters occurring in 2021 (B-21-DF-48-0001 and B-22-DF-48-0001) and 2024 (B-25-DU-48-0001), pending execution of a new negotiated indirect cost rate agreement (NICRA).
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         HUD allocated CDBG-DR funds to the Texas General Land Office (GLO) for disasters occurring in 2021 (B-21-DF-48-0001 and B-22-DF-48-0001) and 2024 (B-25-DU-48-0001). The Department requires grantees to attach an approved indirect cost rate schedule to CDBG-DR grant agreements to ensure compliance with federal cost principles and allow proper allocation of administrative costs. GLO previously held a provisional indirect cost rate of 58.90 percent, which expired on August 31, 2023, and has not yet received a new negotiated indirect cost rate agreement (NICRA).
                    </P>
                    <P>In response to a request from GLO, this waiver and alternative requirement (1) permits the grantee to continue using its provisional indirect cost rate of 58.90 percent pending approval of a new NICRA and (2) allows GLO to attach the provisional rate schedule to the grant agreements for the 2021 and 2024 disaster allocations unless a new NICRA is approved and executed prior to execution of the grant agreements. This exception ensures continuity in cost allocation, reduces administrative burden, and supports timely implementation of disaster recovery activities.</P>
                    <P>
                        <E T="03">Granted By:</E>
                         Andrew D. Hughes, Deputy Secretary, Department of Housing and Urban Development.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 5, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         The Texas General Land Office (GLO) requested a waiver to continue using its provisional indirect cost rate of 58.90 percent because its last approved NICRA expired on August 31, 2023, and HUD, or its servicing agency, has not been able to finalize a new rate despite GLO's ongoing efforts to negotiate. HUD determined there is good cause to grant an exception under 2 CFR 200.102(c) to allow GLO to attach and use the provisional rate in its CDBG-DR grant agreements for disasters occurring in 2021 and 2024, pending execution of a new NICRA, thereby ensuring continuity in cost allocation and supporting timely disaster recovery activities.
                    </P>
                    <P>
                        <E T="03">Applicability:</E>
                         This waiver and alternative requirement is applicable solely to CDBG-DR funds awarded to the Texas General Land Office (GLO) for disasters occurring in 2021 and 2024 under the relevant HUD appropriation authorities. It permits GLO to attach and use the provisional indirect cost rate of 58.90 percent in its grant agreements for B-21-DF-48-0001, B-22-DF-48-0001, and B-25-DU-48-0001 pending execution of a new negotiated indirect cost rate agreement (NICRA).
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer Carpenter, Policy Division Director, Office of Disaster Recovery, Office of Community Planning and Development, Department of Housing and Urban Development, 451 Seventh Street SW, Room 7282, Washington, DC 20410, telephone (202) 402-4318, email 
                        <E T="03">Jennifer.Hylton.Carpenter@hud.gov.</E>
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         Section 105(a) of the Housing and Community Development Act of 1974, as amended (HCDA), 24 CFR 570.207(b)(3), and 24 CFR 570.309.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Hurricane Harvey and subsequent severe weather caused damage and destruction to many housing units within the declared disaster areas in Harris County, Texas. The county used Community Development Block Grant Disaster Recovery (CDBG-DR) funds as a subrecipient of the state of Texas to develop two new construction single-family developments, with a total of 114 units, at least 90 of which were provided for low- and moderate-income (LMI) households. One of these CDBG-DR housing developments, currently known as Vista and located in Pasadena, Texas, had gaps in the pro forma. The state transferred $8,955,179.92 of program income to the county, which was required to receipt the funds as part of its annual Community Development Block Grant (CDBG) program. The county anticipates completing the Vista project with the transferred program income to further its disaster recovery efforts.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         Section 105(a) of the HCDA and 24 CFR 570.207(b)(3) generally prohibit grantees from using CDBG funds to construct new permanent residential structures or for any program to subsidize or assist such new construction, except when carried out by a Community Based Development Organization (CBDO) or other nonprofit entities specified in Section 105(a)(15) of the HCDA and pursuant to 24 CFR 570.204(a). 24 CFR 570.309 states that a CDBG grantee may assist an activity outside the jurisdiction of the grantee only if the grantee determines that such an activity is necessary to further the purposes of the HCDA and the recipient's community development objectives, and that reasonable benefits from the activity will accrue to residents within the jurisdiction of the grantee.
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         David C. Woll, Jr., Principal Deputy Assistant Secretary for Community Planning and Development.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         July 30, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         These waivers will permit the county to continue to use funds consistent with the requirements of the CDBG-DR grant but not generally permitted under the CDBG program. HUD recognizes that Hurricane Harvey and subsequent severe weather caused damage and destruction to many housing units within the declared disaster areas. Allowing new housing construction in an entitlement community will enable the county to replace affordable housing units that were lost because of the disaster. This authority is available until September 30, 2027, for the county to use within the City of Pasadena, Texas, and is limited to new housing construction and reconstruction of damaged homes and buildings with the use of CDBG funds.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         James Höemann, Director, Entitlement Communities Division, Community Planning and Development, Department of Housing and Urban Development, 451 Seventh Street SW, Room 7282, Washington, DC 20410, telephone (202) 402-4548, email: 
                        <E T="03">James.E.Hoemann@hud.gov</E>
                        .
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         Section 105(a) of the HCDA, 24 CFR 570.201(e) and 24 CFR 570.207(b)(4).
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Due to Tropical Storm Helene, the City of Asheville, North Carolina requested an extension of the suspension of Community Development Block Grant (CDBG) public services cap and emergency grant payments from the end of its program year, June 30, 2025, until December 31, 2025.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         Section 105(a)(8) and 24 CFR 570.201(e) limit the amount of CDBG funds that may be used to provide public services to 15 percent of the grantee's most recent CDBG grant, plus 15 percent of program income received. Section 105(a)(8) of the HCDA, 24 CFR 570.201(e), and 24 CFR 570.207(b)(4) limit the amount emergency grant payments a period of up to three consecutive months to the provider of such items or services on behalf of an individual or family.
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         David C. Woll, Jr., Principal Deputy Assistant Secretary for Community Planning and Development.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         July 30, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         The Tropical Storm Helene caused substantial damage to neighborhoods throughout the City of Asheville. A Presidentially declared disaster declaration (FEMA-DR-4827-NC), as amended, was issued on September 28, 2024, for Buncombe County, which covers Asheville. In response to the disaster, the city requested statutory suspensions and regulatory waivers for the CDBG program associated with the July 1, 2024 “streamlined waiver” that the Department of Housing and Urban Development (HUD) had already made available to recipients of Community Planning and Development (CPD) grant programs impacted by Presidentially declared major disasters through the 
                        <E T="03">Availability of Waivers of Community Planning and Development Grant Program and Consolidated Plan Requirements to Facilitate Recovery from Presidentially Declared Major Disasters</E>
                         memorandum. The waivers granted allowed the city to expedite recovery efforts for low- and moderate-income (LMI) residents affected by the disaster through the end of its program year of June 30, 2025. In a letter to the HUD 
                        <PRTPAGE P="41065"/>
                        Greensboro Field Office dated June 16, 2025, the city requested an extension of the public services cap suspension and emergency grant payments waiver through December 31, 2025.
                    </P>
                    <P>By providing an extension of six months of the suspension of the public services cap and making emergency grant payments available for six months instead of three months, the city can further address the needs of its LMI residents affected by the disaster.</P>
                    <P>
                        <E T="03">Contact:</E>
                         James Höemann, Director, Entitlement Communities Division, Office of Community Planning and Development, Department of Housing and Urban Development, 451 Seventh Street SW, Room 7282, Washington, DC 20410, telephone (202) 402-4548, email: 
                        <E T="03">James.E.Hoemann@hud.gov.</E>
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 51.104(b)(2).
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Stonehawk Capital Partners, LLC, in partnership with the Garland Housing Finance Corporation, has proposed the new construction of StoneHawk Rosehill, a 269-unit apartment development in Garland, Texas. The project will include 27 units (10 percent) restricted to households at or below 60 percent of Area Median Income (AMI), 109 units (41 percent) restricted to households at or below 80 percent of AMI, and 133 units (49 percent) that will be unrestricted and rented at market rates.
                    </P>
                    <P>StoneHawk Rosehill will be located approximately 13 miles east of downtown Dallas on a rectangular site situated between IH-30 and Bobtown Road. A noise mitigation study prepared by dP(A) Acoustics, Inc. indicated that two of the eleven Noise Assessment Locations had outdoor noise levels of 76 dB(A), placing them within the Unacceptable Noise Zone.</P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         An Environmental Impact Statement (EIS) is required prior to the approval of projects with unacceptable noise exposure. Projects located wholly or partially within an Unacceptable Noise Zone must be submitted to the Assistant Secretary for Community Planning and Development, or to the Certifying Officer for activities subject to 24 CFR part 58, for approval.
                    </P>
                    <P>Pursuant to 24 CFR 51.104(b)(2), the Assistant Secretary or the Certifying Officer may waive the EIS requirement when noise is the sole environmental issue and no outdoor noise-sensitive activities will occur on the site. In such cases, an environmental review must be completed in accordance with 24 CFR parts 50 or 58, as applicable.</P>
                    <P>
                        <E T="03">Granted By:</E>
                         Bryan W. Horn, Principal Deputy Assistant Secretary for Community Planning and Development.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 5, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         Pursuant to 24 CFR 51.104(b)(2), the Assistant Secretary for Community Planning and Development may waive the Environmental Impact Statement (EIS) requirement when noise is the sole environmental issue, no unmitigated outdoor noise-sensitive activities will occur on the site, and indoor noise levels are mitigated to the Department of Housing and Urban Development (HUD) standards.
                    </P>
                    <P>Dwight Capital certified that noise is the only unmitigated environmental concern. HUD concurs based on its review of the Environmental Report, completion of the Floodplain Management Eight-Step Decision-Making Process, and the approved HUD Environmental Review Online System (HEROS) compliance entries. In addition, the StoneHawk Rosehill project will incorporate mitigation measures to achieve compliance with HUD's interior and exterior noise standards, and no other unmitigated environmental conditions are anticipated to result from the project.</P>
                    <P>
                        <E T="03">Contact:</E>
                         Sara Jensen, Environmental Specialist, Office of Housing, Department of Housing and Urban Development, 909 First Ave., Suite 300, Seattle, WA 98104, telephone (206) 202-5226, email: 
                        <E T="03">sara.jenson@hud.gov.</E>
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 51.104(b)(2).
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         The subject property consists of approximately 13.45 acres of undeveloped land located at 2210 Legge Boulevard in Winchester, Virginia. The developer, Castle Development Partners, proposes to construct 247 Class A apartment units utilizing the Section 221(d)(4) program. The project will include 12 residential buildings and a centrally located clubhouse. The four-story buildings will be elevator-serviced, while the three-story buildings will be garden-style walk-up structures.
                    </P>
                    <P>The community clubhouse will be approximately 8,000 square feet and will include an on-site leasing office, conference room, great room with kitchen, resident lounge with bar and pool tables, fitness center, pet cleaning station, and a covered outdoor patio. Adjacent amenities will include a saltwater pool, outdoor grill and kitchen area, fire pit, garden area with picnic tables, and an outdoor bocce court. The development will also provide covered parking spaces and storage units available for rent.</P>
                    <P>The subject property is located within 1,000 feet of Interstate 81 and in close proximity to a CSX railroad and a regional airport. A third-party environmental analyst, Dominion Due Diligence Group (D3G), completed Sound Transmission Class (STC) calculations in accordance with the Department of Housing and Urban Development (HUD) Noise Guidebook, Chapter 4. The HUD noise assessment identified a projected Day-Night Level (DNL) value of 78 dB in the most noise-impacted areas of the site, placing the project within the Unacceptable Noise Zone.</P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         An Environmental Impact Statement (EIS) is required prior to the approval of projects with unacceptable noise exposure. Projects located wholly or partially within an Unacceptable Noise Zone must be submitted to the Assistant Secretary for Community Planning and Development, or to the Certifying Officer for activities subject to 24 CFR part 58, for approval.
                    </P>
                    <P>Pursuant to 24 CFR 51.104(b)(2), the Assistant Secretary or the Certifying Officer may waive the EIS requirement when noise is the sole environmental issue and no outdoor noise-sensitive activities will occur on the site. In such cases, an environmental review must be completed in accordance with 24 CFR parts 50 or 58, as applicable.</P>
                    <P>
                        <E T="03">Granted By:</E>
                         Bryan W. Horn, Principal Deputy Assistant Secretary for Community Planning and Development.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 30, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         Pursuant to 24 CFR 51.104(b)(2), the Assistant Secretary for Community Planning and Development may waive the Environmental Impact Statement (EIS) requirement when noise is the sole environmental issue, no unmitigated outdoor noise-sensitive activities will occur on the site, and indoor noise levels are mitigated to HUD standards.
                    </P>
                    <P>HUD has reviewed the environmental review and verified that all other environmental issues will be appropriately mitigated. In addition, the project will incorporate sound attenuation measures, as documented by D3G, sufficient to bring the development into compliance with HUD's interior noise standards, and no other unmitigated environmental conditions are anticipated to result.</P>
                    <P>
                        <E T="03">Contact:</E>
                         Sara Jensen, Environmental Specialist, Office of Housing, Department of Housing and Urban Development, 909 First Ave., Suite 300, Seattle, WA 98104, telephone (206) 202-5226, email: 
                        <E T="03">sara.jenson@hud.gov.</E>
                    </P>
                    <HD SOURCE="HD1">II. Regulatory Waivers Granted by the Office of Housing</HD>
                    <P>For further information about the following regulatory waivers, please see the name of the contact person that immediately follows the description of the waiver granted.</P>
                    <P>
                        <E T="03">Regulation:</E>
                         24 CFR 880.205(c) stipulates that an owner's equity investment for the purposes of calculating distributions shall be based on “the replacement cost of the part of the project attributable to dwelling use” at the point of cost certification. The proposed Owner of Indian Hills (Indian Hills II, LP) seeks approval instead to calculate distributions based on the Low-Income Housing Tax Credit (LIHTC) equity they are contributing to the project's recapitalization.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         The project is financed with a 221(d)(4) HUD-insured loan and a mortgage restructuring note (MRN), both of which will be repaid by the proposed Owner at closing; HUD HQ has approved the payoff. Once the MRN has been paid in full, the project will again be subject to the limitation on distributions laid out in the initial HAP contract. The project has been well-maintained, but the units need significant renovations and upgrades. The proposed Owner plans to invest approximately $139,000 in hard costs per unit to rehabilitate the project, including repairs to the building exterior and in-unit renovations. This renovation will be financed with an FHA-insured loan, 9 percent LIHTCs, a deferred developer fee, interim operating funds, and funds from the project's reserve for replacement account. The proposed Owner's equity investment will be calculated based on the LIHTC equity investment. The LIHTC investor will not agree to close on the transaction if paying off the MRN results in a return to a 6 percent limitation on distributions, calculated as stipulated in 24 CFR 880.205(c). Without approval of 2 the waiver, the recapitalization transaction will be infeasible. The field office supports the proposed Owner's request for a waiver of this regulation.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 880.205(c) stipulates that an owner's equity investment 
                        <PRTPAGE P="41066"/>
                        for the purposes of calculating distributions shall be based on “the replacement cost of the part of the project attributable to dwelling use” at the point of cost certification.
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Frank Cassidy, Principal Deputy Assistant Secretary for Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         July 1, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         Without approval of the waiver, the recapitalization transaction of this affordable property will be infeasible.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer Larson, Director, Office of Asset Management, Office of Housing, Department of Housing and Urban Development, 451 Seventh Street SW, Washington, DC 20410, telephone (202) 402-7769, email: 
                        <E T="03">Jennifer.Larson@hud.gov.</E>
                    </P>
                    <P>
                        <E T="03">Regulation:</E>
                         The owner of Yorkshire Commons, York Housing Authority (YHA), is requesting a regulatory waiver of the requirements under 24 CFR 883.306(a) and paragraph 2.6(e)(1) of the Section 8 Housing Assistance Payments Program State Housing Agencies—Housing Assistance Payments Contract where non-profit owners are not entitled to distributions of project funds.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         YHA is exploring affordable housing development of a parcel abutting Yorkshire Commons. It is also pursuing the acquisition of an existing mobile home park to preserve it as naturally occurring, unsubsidized affordable housing (and ownership) opportunity in the area. Release of excess Project funds will allow YHA to pursue these 3 important projects in furtherance of maintaining and increasing the supply of affordable housing in southern Maine. Nature of Requirement: 1. Under 24 CFR 883.306(a), non-profit owners are not entitled to distributions of project funds. YHA is a tax-exempt public body corporate and politically organized municipal housing authority under Maine State Law and, as such, is not a profit-motivated owner. 2. Pursuant to a memorandum dated February 22, 2010, from Deputy Assistant Secretary Galante to all HUD, HUD explicitly stated that it would permit a waiver request for a nonprofit to obtain unlimited distributions in connection with a Chapter 15 Section 8 renewal request. On March 27, 2023, HUD published changes to the Section 8 Renewal Guide Section 2-12A.2.a, where a nonprofit owner is not entitled to distributions of excess project funds unless HUD approves the nonprofit owner's request for a waiver. Under the revised Section 8 Renewal Guide Section 2-18. A, an owner could establish “good cause” for its request by explaining how the use of funds would further its nonprofit mission and benefit tenants in the Project.
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Frank Cassidy, Principal Deputy Assistant Secretary for Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         August 19, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         Allowing YHA access to the surplus cash earned by Yorkshire Commons would allow YHA to expand its stock of affordable housing projects, particularly to seniors, in York and continue to expand its resident service offering, enriching the lives of its elderly residents.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer Larson, Director, Office of Asset Management, Office of Housing, Department of Housing and Urban Development, 451 Seventh Street SW, Washington, DC 20410, telephone (202) 402-7769, email: 
                        <E T="03">jennifer.larson@hud.gov.</E>
                    </P>
                    <HD SOURCE="HD1">III. Regulatory Waivers Granted by the Office of Public and Indian Housing</HD>
                    <P>For further information about the following regulatory waivers, please see the name of the contact person that immediately follows the description of the waiver granted.</P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 983.52(c), 983.251(a)(2), 983.258, 983.211, 983.301, and 983.353(b)(1).
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 983.52(c) pertains to Housing Assistance Payment (HAP) contracts, specifically requiring that a PHA determine whether a unit is occupied and, if occupied, whether the unit's occupants are eligible for such assistance before the PHA places a specific unit under a HAP contract. 983.251(a)(2) states that a PHA may only select families determined eligible for admission at commencement of Project-Based Voucher (PBV) assistance, using information received and verified by the PHA within a period of 60 days before commencement of PBV assistance. 983.258 pertains to HAPs, stating that payments continue until tenant rent equals the “rent to owner,” but that cessation of payments does not affect other rights under the lease. 983.211 pertains to the removal of a unit from HAP contract based on a family's increased income. 983.301 pertains to determining rent to owner. 983.353(b)(1) states that the family is responsible for paying the tenant rent (total tenant payment minus the utility allowance).
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of Bergen County (HABC).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         July 7, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waivers on the basis of good cause, citing that HABC demonstrated the monthly two-bedroom Rental Assistance Demonstration Gross Rent is less than 30 percent of the monthly income of a family of four at the midpoint between the Very Low Income HUD Income Limit and Extremely Low Income HUD Income Limit for the area in which the Covered Project is located.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Melissa West, Senior Housing Program Specialist, Office of Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street, SW, Washington, DC 20410, email 
                        <E T="03">Melissa.West@hud.gov,</E>
                         telephone (303) 672-5352.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 5.801(d)(1) and 24 CFR 902.62(a)(3).
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 5.801(d)(1) and 24 CFR 902.62(a)(3) pertain to the submission window of public housing agencies' (PHAs') audited financial statements in relation to the fiscal year's end (FYE) and the receipt of a late presumptive failure score of zero if that requirement is not met.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Cook County Housing Authority (CCHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         July 10, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waivers on the basis of good cause, citing that CCHA contends that the audit commenced later than expected due to delays in finalizing the FYE 2022 audit that were beyond its control. To enhance efficiency, CCHA retained a new auditing firm and a professional accounting firm to assist in preparing records, ensuring a more streamlined audit process moving forward.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Lara Philbert, Assessment Manager, Integrated Assessment Team, Real Estate Assessment Center, Office of Public and Indian Housing, Department of Housing and Urban Development, 550 12th Street SW, Washington, DC 20024, email 
                        <E T="03">Lara.Philbert@hud.gov,</E>
                         telephone (202) 475-8930.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 5.711(c)(2).
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 5.711(c)(2) requires that PHAs conduct a survey of an entire project on the property scores less than 60 on a public housing inspection report.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of the City of Erie (HACE).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         July 14, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HACE is facing several challenges that have made it difficult to meet the self-inspection report deadline, including a misunderstanding of the regulatory timeframe for inspections following low scores, logistical difficulties due to appeal requests for its two developments, and severe winter weather. A state of emergency was declared on November 29, 2024, lasting 14 days, followed by continued snowfall throughout December and below-zero wind chills in January, making inspections unfeasible. To address these challenges, HACE engaged a third-party inspection team and scheduled inspections to begin on February 10, 2025, with an expected completion by March 7, 2025.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Lara Philbert, Assessment Manager, Integrated Assessment Team, Real Estate Assessment Center, Office of Public and Indian Housing, Department of Housing and Urban Development, 550 12th Street SW, Washington, DC 20024, email 
                        <E T="03">Lara.Philbert@hud.gov,</E>
                         telephone (202) 475-8930.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.207(b)(3).
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.207(b)(3) states that a PHA may not adopt a preference for the admission of families that include a person with disabilities.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Texas Department of Housing and Community Affairs (TDHCA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         July 18, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that the waivers will allow TDCHA to continue administering a portion of its Housing Choice Vouchers (HCVs) consistent with its Project Access program. The Project Access program assists low-income non-elderly people with disabilities to transition from institutions into the community. This housing voucher pilot was developed by HUD and the Department of Health and Human Services in 
                        <PRTPAGE P="41067"/>
                        2001. Although the pilot program expired, TDHCA has continued to administer a portion of its HCVs in a manner consistent with the program, maintaining strong coordination with the State health and disability services departments. The waiver will allow TDHCA to use 20 of its 140 vouchers under the Project Access program for individuals exiting or recently exited from the State's psychiatric hospital. HUD originally approved a waiver for 10 vouchers in 2014 and again in 2020, each time for a 5-year period, and TDHCA is requesting a renewal of the waiver and increase to 20 vouchers for which the waiver may be applied.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Susannah Roetlin, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street, SW, Washington, DC 20410, email 
                        <E T="03">Susannah.S.Roetlin@hud.gov,</E>
                         telephone (303) 672-5090.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 5.801(d)(1) and 24 CFR 902.62(a)(3).
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 5.801(d)(1) and 24 CFR 902.62(a)(3) pertain to the submission window of PHAs' audited financial statements in relation to the FYE and the receipt of a late presumptive failure score of zero if that requirement is not met.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Ironton Metropolitan Housing Authority (IMHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         August 4, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that IMHA indicated it was unable to meet the original reporting deadline due to delays associated with the completion of its FY 2023 audit, which was conducted by the Ohio State Auditor. These delays subsequently affected the PHA's ability to complete the FY 2024 audit in a timely manner.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Lara Philbert, Assessment Manager, Integrated Assessment Team, Real Estate Assessment Center, Office of Public and Indian Housing, Department of Housing and Urban Development, 550 12th Street SW, Washington, DC 20024, email 
                        <E T="03">Lara.Philbert@hud.gov,</E>
                         telephone (202) 475-8930.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Everett Housing Authority (EHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         August 6, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that EHA has approximately 52 Emergency Housing Voucher (EHV) families at risk of losing housing due to the end of EHV funding. EHA is concerned that it will not be able to reach all the families in its EHV program to inform them of the opportunity to be placed on the HCV waiting list. This waiver will ensure that all EHV families will be placed on the HCV waiting list, thereby allowing them to transition to the HCV program so they can remain housed.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         San Francisco Housing Authority (SFHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         August 14, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that SFHA currently has over 950 families in its EHV program. SFHA is also currently in shortfall and unable to issue regular HCV through the waiting list but is still allowed, and obligated, to fill Project-Based Voucher (PBV) vacancies. SFHA is requesting this waiver to allow it to place EHV families on the HCV and PBV waiting lists. This waiver is necessary to ensure that all currently subsidized EHV families will have the opportunity to remain housed without placing undue burden on the families. Due to the number of EHV families, automatically adding participants will be crucial to ensuring timely processing and preventing EHV funding from running out prior to transferring families to HCV or PBV since current projections show EHV funding being exhausted by June 2026.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of the City of Fresno (Fresno Housing).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         August 14, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that Fresno Housing states that this waiver is needed in order to ensure that all EHV families are placed on the HCV waiting list. Although Fresno Housing would reach out to existing EHV families, there is a risk that EHV families may not receive the information about having to apply to the HCV waiting list with the new preferences and lose out on the opportunity to transition to HCV. Further, Fresno Housing states that opening its list, even only for EHV families, will cause confusion amongst applicants and the community and cause additional burden on staff who would be responding to inquiries from the public, which will take time away from other essential work.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of the City of Long Beach (HACLB).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         August 14, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HACLB currently serves over 500 EHV families, all of whom represent some of the most vulnerable populations in our community, primarily seniors, individuals with disabilities, and families with limited or no access to resources and support systems. Many of these families were initially assisted by caseworkers or social service providers during the EHV intake process, but these supports are no longer available to guide them through a new HCV application. Requiring these families to reapply individually for the HCV program poses a significant risk of disruption to their housing stability, particularly for those who are no longer connected with supportive services and may struggle to navigate the application process independently.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of the County of Santa Cruz (HACSC).
                        <PRTPAGE P="41068"/>
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         August 14, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that without this waiver, HACSC will need to engage with each EHV family individually to add them to the HCV waiting list. This increases the administrative burden and costs. Significantly, it will delay moving EHV participants onto the HCV waiting list and the transition of EHV families into the HCV program. As a result, HACSC will expend EHV funds more quickly, reducing the length of time the remaining EHV families may be able to be continually assisted with EHV.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         St. Petersburg Housing Authority (SPHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         August 14, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that without this waiver, SPHA would need to process individual applications for each EHV family, which would delay transitioning EHV families to HCV assistance and potentially lead to gaps in service. Further, EHV families may lose assistance if they are unable to navigate the application process in time, especially those with barriers such as limited literacy, language access, or trauma. SPHA currently has sufficient HCV turnover capacity to absorb a portion of EHV families, and this waiver would support our plan for transitioning families.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Ocala Housing Authority (OHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         August 14, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that OHA recently attempted to contact as many EHV families as possible to inform them of the opportunity to apply to the HCV waiting list and was unable to reach most of them. Without this waiver, OHA is concerned that it will not be able to reach all the families in its EHV program to inform them of the opportunity to be placed on the HCV waiting list, which would put them at risk of homelessness.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Chicago Housing Authority (CHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         August 14, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that CHA currently has more than 1,000 EHV families. Without this waiver, CHA would need to contact each family individually to have them apply to the HCV waiting list, which would delay transitioning families to the HCV program and risk families losing their assistance due to their inability to comprehend the notices or to respond in a timely fashion. Further, it will take significant staff time to assist EHV families in navigating the HCV application process.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of Cook County (HACC).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         August 14, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HACC needs this waiver because opening the HCV waiting list for EHV families would delay its ability to transition EHV families to HCV, putting them at risk of losing assistance altogether. With nearly 300 EHV families, to ensure sufficient outreach so that everyone who is eligible to apply actually applies, HACC would need to leave the waiting list open for a longer period of time, which would increase the total number of applications received. The demand for rental assistance is so high that HACC typically receives thousands of applications when it opens its waiting list, including from people who do not qualify. The process of reviewing each application received to determine if the family is a current EHV family and eligible for this preference and notifying applicants that were not selected would be very time consuming and financially burdensome and delay the transition of EHV families to HCV, putting EHV families at risk of losing assistance altogether.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Ann Arbor Housing Commission (AAHC).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         August 14, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that Incorporating EHV participants under our standard waiting list procedures would trigger a significant administrative burden and delay the ability to transition EHV families to HCV. EHV families would face 8- to 12-week delays before they appear on its HCV waiting list. Households nearing lease deadlines could incur housing instability if they cannot access the HCV program seamlessly, potentially resulting in emergency shelter stays or return to homelessness. Further, a significant share of EHV families face barriers to completing a multi-step application process, such as limited literacy or lack of reliable internet access. If EHV families are required to follow the standard waiting-list procedures, several families will see their Housing Assistance Payment (HAP) contracts halted and leases jeopardized. Many will cycle into emergency shelter or face eviction before they ever get on the HCV waiting list. Additionally, AAHC staff would be forced to spend time tracking down non-responsive families and fielding landlord inquiries, which would divert resources from critical housing search assistance, inspections scheduling, and supportive services—further slowing the transition process.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher 
                        <PRTPAGE P="41069"/>
                        Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         St. Cloud Housing and Redevelopment Authority (SCHRA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         August 14, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that this waiver will allow families to remain continuously housed and not become homeless. If this waiver is not granted, the delay in requiring individual applications would put the families at risk of losing assistance. Due to the large number of families, it is unlikely that the agency would be able to do the necessary outreach and follow up to ensure each family is informed and able to apply, jeopardizing their rental assistance.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Mankato Economic Development Authority (MEDA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         August 14, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that this waiver would enable MEDA to ensure all families in the EHV program could be transitioned prior to the sunset of the program and prevent EHV families from a lapse in rental assistance. If the waiver is not granted, some EHV families may not transition. EHV families are less likely to respond to communications from the MEDA as turnover with phone and emails is higher.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of Kansas City (HAKC).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         August 14, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HAKC has 75 families in its EHV program. Without this waiver, HAKC will be required to rely on an individual application process for each family, which will delay the transition, increase administrative burden, and create potential risks for households that face technological, literacy, or other access barriers. This could result in EHV families losing their housing assistance and experiencing homelessness.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of the City of Winston-Salem (Aspire).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         August 14, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that many EHV families were referred through partner agencies and did not apply directly through Aspire's HCV application process. Requiring them to submit a new application will pose operational and programmatic challenges and place unnecessary barriers on EHV families, putting these families at risk of losing their housing. Further, if EHV families cannot transition to the HCV program promptly, the PHA risks losing landlord participation in the HCV program as a result of the loss of rental assistance, which may force families to be evicted from their home.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         New Hampshire Housing and Finance Authority (NHHFA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         August 14, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that NHHFA currently has 96 families leased under the EHV program. With the uncertainty of continued EHV funding, NHHFA must move quickly to convert all EHV families to the HCV program while it has the budget authority to do so. Without knowing 2026 budget numbers for the HCV program, NHHFA cannot be confident that it would be able to convert EHV families to HCV after 2025. Further, if the waiver is not provided, NHHFA would need to notify all EHV families of the funding uncertainty and ask them to apply to the open waiting list before they could select them from the waiting list for an HCV. Given the many barriers that EHV families face, it could cause undue stress and ultimately lead to some families not responding in a timely manner. Therefore, this waiver was necessary to expeditiously and effectively protect critical rental assistance for 96 EHV families.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         New York City Housing Authority (NYCHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         August 14, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that NYCHA states that this waiver is necessary because it is unlikely that it would be able to perform the outreach and assistance necessary to have all of its 5,454 EHV families complete the application process for HCV assistance. At the onset of the EHV program, the EHV families required assistance from Continuum of Care (CoC) case workers to successfully complete the application process. If the waiver was not approved, NYCHA would be required to assist the EHV families in the completion of the waitlist applications. This prolonged process would increase the risk that EHV families would lose HCV assistance as a result of the exhaustion of EHV funds and be at risk of homelessness.
                        <PRTPAGE P="41070"/>
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Greater Dayton Premier Management (GDPM).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         August 14, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that GDPM has 73 families using EHV vouchers. Without this waiver, EHV families would face gaps in assistance as they must wait for formal application processing and selection from the HCV waiting list. Additionally, due to staff attrition and limited administrative capacity, the PHA did not have the staffing levels to process individual HCV applications from all EHV families.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Home Forward.
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         August 14, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that Home Forward has 436 families in its EHV program. Due to the large number of EHV families, it was unlikely Home Forward could complete the necessary outreach and follow up to ensure that each family is informed of their opportunity to be placed on the HCV waiting list, which would risk EHV families losing assistance and returning to homelessness.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of Yamhill County (HAYC).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         August 14, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HAYC states it is unlikely that EHV families, especially those with the highest needs, would be able to apply to the HCV waiting list. Many of the EHV families are out of coordinated care and HAYC lacks the staffing to follow up with EHV families individually, putting them at risk of losing their assistance and becoming homeless.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of Bexar County (HABC).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         August 14, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that without the waiver, HABC staff would be required to process each EHV family application individually, including case-by-case follow-up. Given the vulnerability of these households, one-on-one support would be necessary, further increasing the workload. This process would divert staff time from other essential duties and delay progress across multiple programs. The individual application process will also require technical setup and additional administrative support, increasing operational costs and placing unnecessary strain on already limited agency resources. Setting up and managing the reapplication process would significantly delay the transition from EHV to HCV, potentially disrupting housing stability for at-risk families.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Concordia Parish Police Jury Housing Authority (CPPJHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         August 14, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that CPPJHA states that a waiver is necessary so families could transition to the HCV program before the end of their EHV assistance and avoid a gap in housing assistance. CPPJHA also stated that many EHV families face systemic challenges—such as limited mobility, cognitive or mental health conditions, lack of technology access, or language barriers—that make completing a separate HCV application burdensome or unfeasible. Without automatic placement on the HCV waiting list, some eligible families may never successfully apply, resulting in lost opportunities for stable housing.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 983.3.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 983.3 provides that a project can be a single building, multiple contiguous buildings, or multiple buildings on contiguous parcels of land.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         NYCHA Jackie Robinson Houses and Harlem Scattered Sites.
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 5, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that NYCHA was particularly impacted by the application of the regulatory definition of “project” as applied to the redevelopment, and through this waiver request sought to provide continuity by maintaining the current management and administration structure of these projects under the public housing program to the greatest extent feasible. The consolidations have the potential to directly benefit residents (
                        <E T="03">e.g.,</E>
                         help facilitate and expedite transfers between buildings under the same Rental Assistance Demonstration-PBV Housing Assistance Payment (RAD-PBV HAP) contract, noting the urgency of such transfer requests). The administrative efficiencies resulting from consolidating the RAD-PBV HAP contracts in the manner NYCHA has proposed for redevelopment would significantly reduce the administrative burden on NYCHA staff, allowing more staff time to address the needs and concerns of residents.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Kristin Baugh, Office of Public Housing and Voucher Programs, Office of 
                        <PRTPAGE P="41071"/>
                        Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington DC 20410, email 
                        <E T="03">Kristin.M.Baugh@hud.gov,</E>
                         telephone (913) 551-5573.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 983.3.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 983.3 provides that a project can be a single building, multiple contiguous buildings, or multiple buildings on contiguous parcels of land.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         NYCHA Ocean Hill-Stuyvesant Gardens
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 5, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that NYCHA was particularly impacted by the application of the regulatory definition of “project” as applied to the redevelopment, and through this waiver request sought to provide continuity by maintaining the current management and administration structure of these projects under the public housing program to the greatest extent feasible. The consolidations have the potential to directly benefit residents (
                        <E T="03">e.g.,</E>
                         help facilitate and expedite transfers between buildings under the same RAD-PBV HAP contract, noting the urgency of such transfer requests). The administrative efficiencies resulting from consolidating the RAD-PBV HAP contracts in the manner NYCHA proposed that redevelopment would significantly reduce the administrative burden on NYCHA staff, allowing more staff time to address the needs and concerns of residents.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Kristin Baugh, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington DC 20410, email 
                        <E T="03">Kristin.M.Baugh@hud.gov,</E>
                         telephone (913) 551-5573.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         City of Phoenix Housing Department.
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that the City of Phoenix Housing Department has over 300 EHV families. It is unlikely that the Housing Department would be able to effectively and efficiently provide correspondence to all EHV families to inform them that as a result of the EHV program sunsetting in 2026, they must apply for the HCV program and submit applications in order to be put on the waiting list. Without this waiver, EHV families could possibly lose assistance if they do not successfully apply to the HCV program. In addition, the Housing Department currently has the capacity and funding available in its HCV program for 2025 to successfully transition a large portion of EHV families into the HCV program. With funding for 2026 currently unknown, the more EHV families that can be transitioned into the HCV program in 2025, the better for the PHA and the EHV families. It also significantly reduces the chances of an EHV family being terminated due to the exhaustion of EHV funding in 2026
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         County of Sacramento Housing Authority's (CSHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that CSHA currently is in shortfall and has about 460 active EHV participants (representing 962 individuals, of which 398 are children). CSHA staff is unable to do the necessary individual outreach and follow up to ensure that each family, including those that have ported out, is informed of their opportunity to be placed on the waiting list and is able to submit an application. It is likely that all EHV families would lose the opportunity to apply for future assistance without this high level of support. A phased approach to converting families from EHV to HCV, as vouchers become available, is necessary. When vouchers become available, the first priority should be to preserve the housing for homeless families currently housed and this waiver would help to make that happen.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Community Development Commission of Mendocino County (CDC).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that CDC serves a large volume of EHV families. Without this waiver, requiring each family to complete a new HCV application would overwhelm staff, detracting from core responsibilities such as inspections, reexaminations, and ongoing case management. The delay from requiring individual applications would also put families at risk of losing assistance. EHV families face barriers to completing the application process, such as limited internet access and mobility issues, which increases the likelihood that families may unintentionally lose rental assistance due to being unable to complete the application process.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Catalyst.
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that Housing Catalyst completed an EHV Transition Impact Analysis and Outreach Summary, which found the large number of families (19) served under their EHV program makes individualized application processing logistically unfeasible within the limited timeframe given their limited administrative capacity. Due to the time required to conduct individualized outreach, assist families with application completion, and verify receipt, EHV families would be at risk of losing housing assistance before the transition can occur. Access to means of reliable resources are limited for some of their EHV families as some are without transportation, phone, or email. Geographic dispersion and rural areas add further barriers, making in-person outreach and support more time and resource intensive. These factors place EHV families at imminent risk of housing instability.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of the City of Daytona Beach (HACDB).
                        <PRTPAGE P="41072"/>
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HACDB requested the waiver to expedite the process for the families it serves that may have limited access to technology and to eliminate the risk of families that may miss the opportunity to complete the online application. HACDB recently opened its public housing waiting list and received over 3,000 applications in 30 days. The agency would have to send denial letters to any applicant that applies during the time the waiting list is opened. This waiver will reduce the administrative burden of removing families that are not eligible to apply to the HCV waiting list.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         City of Pensacola Housing (CPH).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that CPH states that requiring individual applications for EHV participants to be placed on the HCV waiting list can create confusion and anxiety among vulnerable families and could result in EHV participants losing their housing assistance when the program ends. The complex application process may deter or delay some EHV families from completing the steps required to join the HCV waiting list, potentially leading to evictions and a return to homelessness or housing instability. Were this to occur, it would likely discourage property owners from participating in the HCV program and have a negative impact on the availability of affordable housing locally. Providing automatic placement with an EHV preference eliminates unnecessary steps, simplifies the transition, and ensures a clearer path to continue housing assistance for these families.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Augusta Housing Authority (AHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that AHA states that EHV families would be at risk of losing assistance due to the exhaustion of EHV funds if they had to go through the application process to be added to the HCV waiting list. Also, it was unlikely that the AHA would be able to do the necessary outreach and follow up to ensure that each family was informed of their opportunity to be submit an application and be placed on the HCV waiting list, which would put families at risk of losing assistance.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of DeKalb County (HADC).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HADC is requested a waiver to avoid putting families at risk of losing housing assistance, which the delay from requiring individual applications would cause. Due to the 96 EHV families that HADC serves, it was unlikely staff will have the capacity to do the necessary outreach and follow-up required to ensure that each family was informed and able to apply, jeopardizing their assistance. If HADC were not granted this waiver, it was very likely that EHV families will lose their housing.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Boise City Housing Authority (BCHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that BCHA had sufficient HCV funding to absorb their EHV families; however, the ability to use this funding would be jeopardized were a waiver not granted. BCHA would experience an administrative burden, given that staff would need to conduct extensive individual outreach, collect and process separate applications from each household, and manually enter each applicant into the waiting list with the appropriate preference. For applicants, the individual application requirements introduce unnecessary barriers, particularly for vulnerable households who may face challenges with technology, paperwork, or timely response. The extended processing timelines could significantly delay transitions, potentially resulting in eligible families missing the opportunity to apply under the preference, placing their housing stability at risk. This waiver allowed BCHA to act quickly to preserve housing stability for current EHV families while ensuring program efficiency and equity.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of Elgin (HAE).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that many current EHV participants came to HAE under a CoC with connected agencies, many of whom had assistance completing the applications, verifications for income, and banking information. It was crucial for HAE to be able to manually add the EHV currently assisted families to the HCV waitlist because it eliminated the potential confusion required of these households—many of whom face barriers such as disability, limited access to technology, or trauma—to reapply under standard HCV application procedures. Without the ability to automatically transfer the currently assisted EHV voucher residents to the current HCV waitlist, there was a severely heightened risk of housing loss once EHV assistance ends and significant administrative and operational burdens on HAE staff.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, 
                        <PRTPAGE P="41073"/>
                        Office of Public and Indian Housing, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Johnson County Housing Authority (JCHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that JCHA would like to add the remaining 32 EHV families to the regular HCV waiting list because of the difficulty involved in contacting the families and the administrative burden on staff. As former homeless individuals and families, any additional requirements could potentially place their long-term stability in jeopardy. JCHA added a local preference for EHV families to its draft 2026 Admin Plan changes for adoption on January 1, 2026. This waiver would prevent the EHV families from unintentionally losing their assistance.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Jefferson Parish Housing Services Development District (JPHSDD).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that JPHSDD has 41 families enrolled in the EHV program. Due to this large number of families and limited staff, it would be difficult to do the necessary outreach and follow up to ensure that each family was informed of their opportunity to be placed on the waiting list and was able to submit an application, which would risk EHV families losing assistance due to the exhaustion of EHV funds. If this waiver was not provided, it could delay our opening of the HCV waitlist, as the same employees are involved in both processes.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Boston Housing Authority (BHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that current regulations require individuals to follow standard waiting list procedures for the HCV program, which can delay and/or terminate access to permanent housing for EHV families once their temporary vouchers are terminated. EHV families are among the most vulnerable population, many face challenges, including trauma-related disorders, anxiety, or cognitive imparements, which may impair their ability to navigate the complex administrative process of the HCV waiting list application. Delays in transitioning to the HCV program could result in housing instability, undermining the primary goal of the EHV program. Additionally, the manual processing required of EHV families through standard waiting list protocols creates a significant administrative burden, requiring additional staff time, resources, and documentation. By granting this waiver, BHA could streamline the process by automatically placing EHV families on the HCV waiting list with a preference that reflects their urgent needs, ensuring continuity of housing assistance.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Lansing Housing Commission (LHC).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that with the impending conclusion of EHV funding, all EHV households face a high risk of losing their housing assistance. Many EHV families face complex barriers—such as limited literacy, technology access, or language proficiency—that make it difficult to complete an additional application process. Requiring individual applications at this stage may result in administrative delays, confusion, or lack of timely response by participants. Individually processing applications for every EHV participant during the EHV closeout period would strain its administrative capacity. Staff would be required to contact, assist, and process applications for every household, which may lead to delays, errors, or missed deadlines, which jeopardize successful transitions. Automatically placing EHV families on the waiting list provides a safety net to prevent abrupt termination and potential homelessness.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Michigan State Housing Development Authority (MSHDA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that due to the large number of families in the EHV program, MSHDA was unlikely to perform the necessary outreach and follow-up in a timely manner to ensure that each family was informed of their opportunity to be placed on the HCV waiting list, was able to submit an application, and was otherwise transitioned to the HCV program. Such administrative delay would create an unnecessary and unreasonable risk of EHV families losing assistance and/or housing due to the exhaustion of EHV funds.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing and Redevelopment Authority of Duluth (HRA of Duluth).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that the HRA of Duluth continues to experience high demand for rental assistance from extremely low-income and special-needs populations. Requiring vulnerable EHV households to re-verify and re-apply after the EHV program ends would be a duplicative intake process, create potential delays, and burden 
                        <PRTPAGE P="41074"/>
                        participating households and their landlords, potentially leading to a return to homelessness or unsafe housing conditions. Given HRA of Duluth's limited resources, requiring EHV households to re-apply would create an administrative strain on staff. Granting this waiver would allow for a smooth transition and reduce strain on participating households and ensure that they are not penalized for initially entering HUD programs through emergency resources rather than the standard HCV route. Additionally, it would allow staff to transition EHV families to long-term housing solutions efficiently and humanely, consistent with HUD's mission and the intent of the EHV program.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Western Piedmont Council of Government (WPCOG).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that WPCOG had 19 (EHV families. These families represent a highly vulnerable population, including persons who are disabled and/or elderly and persons, who were experiencing literal homelessness at the time of lease up. Without this waiver, these families would have to wait until the WPCOG publicly opens its HCV waiting list, which is currently closed with around 2,300 applicants on the list. Since WPCOG expects that it could be a year or longer before it opens its HCV waiting list, current EHV families would reach the end of their assistance before they are able to apply to the HCV waiting list. Approval of this waiver will support a more efficient and streamlined transition process from EHV to HCV, reducing administrative burdens and helping to safeguard against housing disruptions.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Atlantic City Housing Authority (ACHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that ACHA projects it would exhaust EHV funding in 2025, which would require termination of five EHV families this year. ACHA analyzed the Two-Year Tool and determined it would be able to absorb all EHV families into its HCV program in 2025, but this may not be the case in 2026. Without this waiver, there would be a delay in transitioning EHV families into the HCV program, which means ACHA would be able to transition fewer EHV families to HCV by the end of the year. Further, ACHA expected some EHV families would not be able to complete the HCV application process and therefore risk losing their housing assistance due to the impending exhaustion of EHV funds.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of the City of Reno (HACR).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HACR requested the waiver to place all EHV households onto its HCV waiting list without having to open it or require individual applications. Although it would be allowed to open the HCV list to just EHV households, HACR found its community will apply to any open waiting list, even if they know they do not qualify. This causes confusion in the community and requires admissions staff to spend months processing unnecessary applications and sending withdrawal letters, which then further upsets the applicants. In addition, these EHV households exited the trauma of homelessness when they received their voucher assistance and requiring them to reapply to avoid returning to homelessness may retraumatize them unnecessarily.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Nevada Rural Housing Authority (NRHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that without a waiver, NRHA would be required to formally reopen the waiting list solely to allow current EHV families to apply, which would require significant administrative time and cost, cause confusion among the public and applicants not eligible for the EHV preference, and delay urgent transitions needed to preserve housing stability. Additionally, requiring EHV families to complete the HCV application process would create unnecessary barriers since most EHV families would need case management support to navigate the application process, putting them at risk of losing assistance if they are not able to complete the process.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Hempstead Housing Authority (HHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing HHA requested a waiver to allow the current seven EHV households, referred through the Nassau/Suffolk Coalition for the Homeless, to convert their EHVs directly to HCVs without requiring them to complete the standard waitlist application process. These families are among the most vulnerable, facing mental health challenges, limited computer literacy, and risk of housing instability that would make navigating the open waitlist process burdensome and potentially prohibitive. Additionally, HHA has limited staffing that would face increased administrative burdens, as staff would need to provide individualized assistance to each EHV household to ensure proper submission and compliance with standard waitlist requirements. For EHV households, these delays could result in prolonged homelessness, instability, and heightened vulnerability, undermining the core intent of the EHV program to provide rapid rehousing. Granting this waiver would preserve housing stability, prevent a return to 
                        <PRTPAGE P="41075"/>
                        homelessness, and uphold HUD's commitment to serving the most vulnerable.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Trust Fund Corporation (HTFC).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HTFC currently administers assistance to over 1,400 families under the EHV program. Due to the number of families currently receiving EHV assistance, HTFC anticipates a significant administrative burden on the PHA to conduct individualized outreach and follow-up for each household, which may jeopardize the ability of some families to maintain continuous housing assistance. Additionally, without this waiver, it is possible that some eligible families could miss the opportunity to apply, putting them at risk of losing rental assistance.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Cuyahoga Metropolitan Housing Authority (CMHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that the EHV program provided 339 vouchers to assist individuals and families who are homeless, at risk of homelessness, fleeing domestic violence, or transitioning out of homelessness. With strong coordination with its partners at the CoC, CMHA was able to utilize these vouchers for the community. As of then, 267 EHVs remain utilized and requiring household to re-apply for housing would cause significant hardship since many of the EHV families had assistance to complete all housing related paperwork. Due to the limited funding available in EHV, CMHA estimates HAP payments will cease in March 2026. Without this waiver families would likely not apply for housing on their own and a majority of the 267 EHV assisted households would return to homelessness, which would add to the large homeless population and potentially exceed the capacity of its CoC and shelter system.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Klamath Housing Authority (KHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that KHA's EHV clients tend to be more high needs, and the reapplication process would be a hardship for them. The EHV families would fall through the cracks and lose housing assistance in the process, which negates the original goal of the program. As a result, KHA requested the waiver to move EHV families to the HCV waitlist without families having to individually apply.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Westmoreland County Housing Authority (WCHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that WCHA requested a waiver so current EHV families can easily transition to the HCV program. This would eliminate the chance that any of these households would experience delays or interruptions of housing due to the potential challenges they may have in successfully completing the application process. Without this waiver, EHV households would risk a return to homelessness. Additionally, the added administrative processing time required with the full application process would be much greater, creating additional strain on existing WCHA operations.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Delaware County Housing Authority (DCHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that due to the number of EHV families (41) in the program, it was unlikely DCHA would be able to complete the necessary outreach required to provide the required assistance in a timely manner. This waiver was necessary to avoid a delay in completing the individual application process in a timely manner to avoid the risk of EHV families losing assistance due to the exhaustion of funds and potentially becoming homeless. If DCHA has funding available to transition EHV families into the HCV program once EHV funding has been exhausted, this waiver would be necessary to assist with that transition. This waiver would prevent EHV participants from losing assistance prior to the exhaustion of the EHV funding.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Municipality of Aguadilla.
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that the current process of requiring individual applications from EHV families introduces significant delays, which puts vulnerable families at risk of losing their housing, exacerbating their already precarious situations. Further, this requirement would place significant burden on staff; the increased workload can lead to processing delays, further jeopardizing the timely transition of EHV families to the HCV program and could also divert resources away from other critical services. The uncertainty and delays associated with the individual application process can cause 
                        <PRTPAGE P="41076"/>
                        considerable emotional and financial stress for EHV families, many of whom already face challenging circumstances. The potential loss of assistance due to procedural delays could disrupt the stability these families have started to achieve with the help of the EHV program. The streamlined process that the waiver would allow would ensure that no family is left without assistance due to the procedural delays.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Municipio de Camuy.
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that the Municipio de Camuy has 11 EHV families. Subjecting these families to the process of applying for and obtaining assistance through the HCV program would take a lot of time and delay the transition of the families. This could lead to the funds being depleted and the families losing assistance. The Municipio de Camuy had space in its HCV program for these families and updated its Administrative Plan to adopt a preference for EHV families. This waiver would facilitate the transition from EHV to HCV for these families and provide them with stability and continuity in their housing assistance.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Municipality of Lajas.
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that the Municipality of Lajas has 11 families in its EHV program. The Municipality of Lajas projects that it will be able to transition all these families into its EHV program in calendar year 2025, and the delay caused by having to require individual applications from EHV families would put families at risk of not being able to transition to the HCV program. Further, the Municipality of Lajas would not be able to do the necessary outreach and follow up to ensure that each family was able to submit an application and be placed on the HCV waiting list, putting them at risk of losing assistance.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         North Charleston Housing Authority (NCHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that NCHA has 46 EHV participants and many of them face significant barriers to completing the HCV application process. This is especially true for those who are elderly, have limited digital literacy, or have unstable or non-existent internet access. Without the ability to place EHV families directly onto the HCV waiting list, these vulnerable families face a high risk of losing assistance due to the complexity of the application process, staffing limitations, and lack of awareness of their need to reapply. Additionally, NCHA has only recently emerged from a multiyear shortfall period and staffing for intake remains a challenge. NCHA does not currently have sufficient administrative capacity to support the reopening of the waiting list or intensive intake process. Granting this waiver would allow NCHA to prioritize existing EHV families without jeopardizing the integrity of its waiting list procedures.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         East Tennessee Human Resource Agency (ETHRA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that due to the wide geographical area and number of families involved, ETHRA may not be able to do an adequate amount of outreach and follow-up to ensure each family could submit an application in a timely manner, which could ultimately result in the loss of assistance when EHV funds are discontinued. This waiver would ensure a smooth transition to the HCV program with no gaps in assistance because it had HCV HAP funds available for all remaining EHV families.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Houston Housing Authority (HHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that due to the scale of HHA's EHV program (593 families), the administrative burden of requesting that each EHV family complete and submit an individual application would be considerable for both HHA and affected families. HHA expects that EHV families may require significant support from HHA staff in completing an application and would require notifying families, support in completing the application, and tracking progress throughout the application process. These barriers and challenges associated with a requirement for EHV families to submit individual applications may result in a loss or gap in housing assistance. HHA anticipates that this waiver would mitigate barriers related to applying to the HCV program and prevent a loss or gap in housing assistance for EHV families. Furthering efforts to support EHV families, HHA is in process of revising the HCV Administrative Plan to provide a local preference in the HCV program for currently assisted EHV families whose assistance is at risk of termination due to lack of program funding.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 
                        <PRTPAGE P="41077"/>
                        requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Dallas County Health and Human Services (DCHHS).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that requiring separate applications and standard selection would create significant administrative burden, extend the transition timelines, and increase the risk of funding gaps. This would further heighten the risk of assistance interruptions for households already experiencing housing instability and could lead to housing loss. DCHHS sought and received approval from the Dallas County Commissioners Court and formally revised its FY 2025 HCV program Administrative Plan to adopt a local preference specifically for transitioning EHV families at risk of losing assistance. Granting a waiver would allow DCHHS to place all 87 EHV families directly onto the HCV waiting list, enabling a coordinated, equitable transition that protects vulnerable households, preserves uninterrupted assistance for those households, and maintains program compliance.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Virginia Housing Development Authority (VHDA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that VHDA administers the HCV program in partnership with 26 local housing agencies, managing separate waiting lists across a geographically vast and decentralized service area. Were a waiver not granted, waiting lists across the State would have to be opened to reach every region VHDA serves. This area would span urban centers, rural communities, and regions with limited local infrastructure. This influx would place a strain on VHDA's system, with more than 5,200 households across these waiting lists. Prior partnerships with 15 CoCs across the State, who VHDA has historically relied on to support with outreach and housing support of the most vulnerable EHV households, have limited capacity due to recent funding cuts. It is unlikely that VHDA can conduct the level of individualized outreach and follow-up needed to ensure each EHV household was informed of the opportunity to apply to multiple waiting lists. Additionally, participants may be unable to complete the necessary applications timely due to lack of transportation, limited internet access, language barriers, or other disabling conditions or needs. Without continued rental support, many of these families are at risk of returning to homelessness.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Worcester Housing Authority (WHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that WHA serves 58 families through the EHV program. WHA faces significant operational challenges in conducting timely outreach, follow-up, and application intake for each EHV participant. Without a waiver, WHA would be required to request and process individual applications, a process that would substantially delay the ability to transfer EHV families to the HCV waiting list.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Missoula Housing Authority (MHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that MHA has a lot of disabled adults with kids in its EHV program and the requirement to go through the HCV application process would pose a barrier to transitioning to the HCV program before the exhaustion of EHV funds. The application process can be difficult for EHV families, and they could end up losing their housing if they are not able to transition to the HCV program in a timely manner.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         East Orange Housing Authority (EOHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that EOHA would endure delays in transitioning EHV families to HCV if it requires them to submit individual applications, putting EHV families at risk of losing assistance due to the exhaustion of EHV funds.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         NYC Department of Housing Preservation and Development (HPD).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HPD has over 2,000 families in the EHV program. EHV participants joined the program through a referral system established between HPD and community-based organizations (CBOs), which did not involve a paper-based application. Without the direct support from our partnering CBOs, HPD would not be able to engage households with the level of attention needed to ensure their applications were submitted properly and in a timely manner. This will result in EHV families failing to convert and lose assistance and potentially their overall housing stability.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                        <PRTPAGE P="41078"/>
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Youngstown Metropolitan Housing Agency (YMHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that the process of applying for the HCV program would be confusing to EHV families, and without their full understanding of what is occurring, homelessness is likely to occur for these families. In order to successfully transition EHV families to the HCV program, staff would need to follow up with all stakeholders in this subsidy process, families would suffer depression from not understanding the full process, and owners and social services agencies would be frustrated from the various phone calls that clients may place to agencies. This waiver would allow a smooth transition so that families will not lose assistance.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Akron Metropolitan Housing Authority (AMHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that the AMHA needs the waiver to streamline the process to add all EHV families to the HCV waiting list to avoid creating more of an administrative burden for our families and staff. AMHA is concerned that, based on the population served by EHV, these vulnerable families would not understand why they had to reapply when they already had housing and may not complete the required paperwork. If the families missed the required steps, it would force them back into homelessness rather than maintaining the stable housing they have already worked to achieve. Requiring EHV families to individually apply would also require additional AMHA staff time to process the applications, review them for accuracy, contact the EHV families, and answer questions.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Linn-Benton Housing Authority (LBHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that this waiver was necessary because it was unlikely that EHV families—particularly those with the greatest needs—would be able to complete the process of applying to the HCV waiting list. This was compounded by the fact that LBHA serves a rural area that spans over 80 miles which makes it difficult for families to interact with the office. Many EHV families are no longer connected to services or coordinated care, which puts them at risk of losing their assistance and becoming homeless. LBHA also does not have the staffing capacity to follow up with each family individually, increasing their risk of losing their assistance and becoming homeless.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of Washington County (HAWC).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HAWC has 80 families currently participating in its EHV program and the capacity to absorb 20 EHV households into permanent voucher programs administered through the HCV waiting list. Any delay in these program transfers would limit HAWC's capacity to extend the EHV timeline. The waiver was necessary for its ability to act quickly and efficiently to transition households from EHV to permanent rental assistance programs, while limiting the administrative burden for staff and participants.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Allentown Housing Authority (AHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that this waiver was needed to ensure continuity of housing assistance for this highly vulnerable population. This waiver would ensure that EHV families are not excluded from housing assistance due to lack of capacity to complete paperwork or meet deadlines or due to delays and inefficiencies caused by the increased administrative burden on the PHA.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Municipality of San Germán (MSG).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that MSG has not been able to maintain 100 percent voucher utilization due to the limited availability of affordable housing units in our jurisdiction. EHV families have already been determined eligible, are currently receiving rental assistance, and are residing in units that have passed HUD-required inspections. Their transition into the HCV program would not require the typical eligibility screening or initial Housing Quality Standards inspection processes, which not only reduces the administrative burden on its staff but also expedites the process of maintaining assistance for these households. Requiring each EHV household to reapply for HCV assistance would create unnecessary procedural barriers, which could delay or even jeopardize their continued housing stability. This waiver would allow MSG to maintain support for its most at-risk populations while maximizing voucher utilization and aligning with HUD's goals of reducing homelessness and improving program efficiency.
                        <PRTPAGE P="41079"/>
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Tennessee Housing Development Agency (THDA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that THDA requested HUD approval to use the EHV preference to protect vulnerable households from potential loss of assistance, reduce administrative workload, and support HUD's objective of streamlining PHA processes. Given the volatility in its local housing market—marked by rising rents and limited availability—any disruption in assistance could lead to displacement or homelessness for families who are already rent-burdened. This waiver would allow THDA to provide a smooth and uninterrupted transition for the 207 families receiving EHV assistance. Without this waiver, these vulnerable families risk experiencing a lapse in rental assistance, which would create avoidable instability and hardship.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Prince William County Office of Housing and Community Development (OHCD).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that EHV families face significant barriers to completing the HCV application process, such as limited knowledge in the usage of computers, difficulty maneuvering technological devices, and lack of access to transportation to obtain in-person assistance. Due to these limitations, EHV families would be at risk of losing their housing assistance if this waiver was not granted and they were required to go through the HCV application process.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Yakima Housing Authority (YHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that YHA projects that it will exhaust EHV funding in 2025 and that this will require termination of 13 EHV families this year. YHA analyzed the Two-Year Tool and determined that it would be able to absorb some EHV families into its HCV program in 2025, but this may not be the case again in 2026. Without this waiver, there would be a delay in transitioning EHV families into the HCV program, which means that YHA would be able to transition fewer EHV families to HCV by the end of the year. Further, YHA expects that some EHV families would not be able to complete the HCV application process and therefore risk losing their housing assistance due to the impending exhaustion of EHV funds.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Mesa Housing Authority (MHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that MHA currently has 82 families receiving assistance through the EHV program. By granting this waiver, MHA will be able to place all EHV families on the HCV waiting list after establishing an EHV preference, without requiring each family to individually apply. This administrative flexibility would reduce barriers for families, prevent unnecessary gaps in assistance, and streamline the transition process, ensuring continuous housing support. Approval of this waiver request would allow MHA sufficient time to prepare to move EHV families to the regular HCV program, allowing MHA to avoid causing 82 EHV families to become homeless.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of the County of Kern (HACK).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HACK had 164 families assisted through the EHV program and does not believe it has adequate staff capacity to complete the individual applications for the HCV program. Each family would need to be sent a letter, then followed by phone contact and an in-person appointment to complete their application. This population has demonstrated that a more hands-on approach is needed than families in the regular HCV program, as evidenced by their need for additional assistance to complete annual and interim re-certifications. To ensure the continued housing stability of its EHV families, HACK requested a waiver to add all EHV families to the HCV waiting list after establishing an EHV preference without families having to individually apply for the HCV program.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of the County of San Joaquin (HACSJ)
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that EHV families are some of the most vulnerable populations and reducing barriers to transitioning to the HCV program would reduce the risk of delays and housing interruptions. Without this waiver, HACSJ would have to contact each family individually, which would delay housing 
                        <PRTPAGE P="41080"/>
                        support and put EHV families at risk of not being able to transition to HCV due to error, lack of documentation, and significant administrative delays.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Marin Housing Authority (MHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that MHA had 97 families in its EHV program. These families often face technology, mobility, and literacy barriers. When initially enrolled, EHV families received case management support through Coordinated Entry, but only 24 percent of EHV families had case managers at this time. If this waiver were not granted, many EHV families may struggle to complete the application process, putting them at risk of losing assistance. Additionally, if MHA were required to publicly open its HCV waiting list, it expects to receive a high volume of ineligible applications, which would require significant time to review and remove non-qualifying entries, creating delays and administrative burden.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of the County of Humboldt (HACH).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HACH serves a rural population with extremely limited transportational options. Many participants are living with significant disabilities and mental health challenges. This is compounded by their requirement of intensive and specialized assistance, which creates challenges in their ability to timely and successfully complete basic paperwork, putting them at risk of losing their housing assistance if they must go through the application process to be added to the HCV waiting list.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Santa Monica Housing Authority (SMHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that SMHA's EHV program includes individuals and families who are homeless, fleeing domestic violence, or living with disabilities. Requiring them to submit a new application would create unnecessary barriers for people who are already facing significant challenges just to remain housed. When SMHA admitted participants to the EHV program, it did not make broad use of the flexibilities offered under the EHV program. In the few cases where families were admitted without full documentation, it tracked those files and made sure to collect the required Social Security and citizenship documentation well within the 180-day window. All active EHV participants have provided full documentation and are eligible for continued assistance under the HCV program. Housing in Santa Monica is extremely expensive, and the recent wildfires in the region only made the rental market more difficult. Rents have gone up, affordable units are harder to find, and SMHA is seeing more displacement across the city. Without the waiver, it risked unnecessary delays and disruptions that could harm families we have worked hard to stabilize.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Boulder County Housing Authority (BCHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that BCHA's EHV program supported 26 households, which included 26 children, 4 seniors over the age of 62, and 3 individuals with documented disabilities. All households experienced difficulty completing paperwork at initial intake due to barriers such as limited literacy, lack of internet access, and general instability. Requiring them to apply to the HCV waiting list would create significant hardship and pose a risk to their housing stability.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Jefferson County Housing Authority (JCHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that if this waiver were not granted, JCHA would have to require individual applications from EHV families and publicly open its HCV waiting list, which would cause the transition to HCV to become slower, less predictable, and more complex to manage administratively for JCHA. This would also pose barriers for EHV families, putting them at risk of losing assistance and becoming homeless.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Gary Housing Authority (GHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that GHA had enough HCVs to issue to all 21 EHV families. However, it would be difficult for GHA to provide a reasonable amount of time for EHV families to apply for the HCV program and be selected from the waiting list before the 
                        <PRTPAGE P="41081"/>
                        exhaustion of EHV funds. Additionally, it was unlikely that GHA would be able to do the necessary outreach and follow up to ensure that each EHV family was able to submit an EHV application, which would put EHV families at risk of losing assistance.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 pertains to the need for families to apply to be placed on a waiting list. 24 CFR 982.206 requires that the PHA provide public notice of the opening of the waiting list.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Indiana Housing and Community Development Authority (IHCDA)
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that IHCDA had 239 EHV participants. Having to individually apply will be time-consuming for this vulnerable population. Staff would also have an increased workload and would not be able to complete the 239 application reviews for each tenant. Without this waiver, IHCDA's EHV families were at risk of returning to homelessness. Therefore, IHCDA requested this waiver to add all applicants to the waitlist at one time to prevent any burden on operations and EHV families.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, 451 7th Street SW, Washington, DC 20410, email 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.201(e) and 983.251(a)(2).
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.201(e) and 983.251(a)(2) pertain to verification of date of birth, disability status, eligibility determination, and income verification for the HCV and PBV programs.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Michigan State Housing Development Authority (MSHDA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 26, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that, from July 2023 to June 2024, 53 percent of all new admissions to MSHDA's HCV program were individuals and families experiencing homelessness. Additionally, 47 percent of MSHDA's HCV program participants are disabled. Allowing participants the ability to self-certify their date of birth, disability status, and income verification requirements when other verification methods are not immediately available increases accessibility for families and individuals with a disability. In partnership with CoCs and Housing Assessment and Resource Agencies State-wide, MSHDA continues to offer a preference for individuals and families experiencing homelessness. The homeless preference is to ensure that critical, long-term housing subsidies are directed to those experiencing homelessness. It is incorporated as part of MSHDA's Emergency Solutions Grant (ESG) program to allow partners statewide to refer eligible households to the HCV waitlist under this preference, utilizing it as another tool to help end homelessness. MSHDA adopted self-certification waivers for date of birth and income verifications for both EHV and the Stability Vouchers. These waivers allowed MSHDA to relieve the burden of documentation collection on individuals and families experiencing homelessness without experiencing any significant or measurable impact to Enterprise Income Verification identity verification errors or miscalculations of income, assets, and expenses. Individuals and families in these programs were able to provide self-certification when documents were not immediately available. This has a proven track record of reducing the time it takes MSHDA to issue a family a voucher to search for housing with when these flexibilities are adopted. If the waiver is not provided, MSHDA states it would continue to experience delays in the lease-up process for families and individuals who are experiencing homelessness. The requirement to collect Social Security cards, birth certificates, and other verifications with no option to accept self-certification or allow lease up would present delays and even denial of assistance for homeless families. During this time, the family remains unhoused in shelters and on the street. Additionally, families and individuals who made requests for required documentation but are delayed in lease up continue to occupy shelters and require emergency funding that could be used for other families once they are permanently housed with an HCV.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Carmen Chow, Housing Program Specialist, Housing Voucher and Management Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC, email 
                        <E T="03">Carmen.Chow@hud.gov,</E>
                         telephone (312) 913-8523.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.503(a)(2) and 982.503(b).
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.503(a)(2) and 982.503(b) provide that the PHA must adopt a payment standard schedule that establishes voucher payment standard amounts for each fair market rent area in the PHA jurisdiction. And, for each payment standard area, the PHA must establish a payment standard amount for each unit size, measured by number of bedrooms. These payment standard amounts comprise the PHA's payment standard schedule and are used to calculate the monthly housing assistance payment for a family.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Cuyahoga Metropolitan Housing Authority (CMHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 26, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that the waivers would allow CMHA to balance its budget constraints with the requirements of the demonstration. CMHA states that due to its current budget utilization for calendar year 2025, it cannot support higher subsidies for all HCV participants who move to an opportunity area. CMHA is projected to have a $11,913,345 HCV shortfall. CMHA has implemented several cost savings measures, such as ceasing issuance of new vouchers to applicants, restricting voucher extensions, stopping the absorption of incoming portability, and removing vacant PBV units from existing contracts. However, to meet the requirements of their participation in the demonstration, CMHA must continue to offer payment standards that are adequate in opportunity areas in CMHA's local jurisdiction. As such, CMHA sought to establish a separate payment schedule for the demonstration. In accordance with 85 FR 42890, a family's participation in the demonstration is defined as being enrolled in the demonstration at CMHA and assigned to a control or treatment group.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Carmen Chow, Housing Program Specialist, Housing Voucher and Management Operations Division, Office of Public Housing and Voucher Programs, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC, email 
                        <E T="03">Carmen.Chow@hud.gov,</E>
                         telephone (312) 913-8523.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         Section 9(g)(1) of the United States Housing Act of 1937
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         Section 9(g)(1) states that public housing agencies may not use more than 20 percent of Capital Fund Formula grants for eligible Operating Fund activities as described in Section 9(e)(1)(C) of the Act.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of Kansas City (HAKC).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 26, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HAKC was experiencing high rates of violent crime and property crime, which posed a serious threat to the health and safety of the PHA's public housing residents at the following public housing developments: MO002000013 Brush Creek Towers, 1800 Emmanuel Cleaver II Blvd. and MO002000025 Pemberton Heights, 3710 East 51st Street. HAKC provided local crime data and projections for FY 2023 and 2024. HAKC indicated the specific activities it plans to undertake to address the crime problem identified, including protective services. HAKC provided a justification for the request based on the FY 2023 and 2024 Capital Fund Processing Guidance. HAKC requests authorization to allocate up to 34.06 percent of $4,779,630 of HAKC's FY 2023 Capital Fund formula grant and up to 33.71 percent of $4,974,861 of HAKC's FY 2024 Capital Fund formula grant for above-
                        <PRTPAGE P="41082"/>
                        baseline services for eligible antidrug and anticrime activities to be used for the current police contract.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         David Fleischman, Director in HUD's Capital Program Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 7th Street SW, Washington, DC 20410, 
                        <E T="03">David.Fleischman@hud.gov,</E>
                         telephone (202) 402-2071.
                    </P>
                </EXTRACT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13537 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4210-67-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Bureau of Land Management</SUBAGY>
                <DEPDOC>[A2407-014-004-065516; O2509-014-004-125222; LLES961000]</DEPDOC>
                <SUBJECT>Notice of Filing of Plats of Survey; Minnesota</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Land Management, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of official filing.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The plats of survey of the following described lands are scheduled to be officially filed in the Bureau of land Management (BLM), Eastern States State Office, Falls Church, Virginia, 30 calendar days from the date of this publication. The surveys, executed at the request of the United States Forest Service, Region 9, were performed to meet requirements for transfer of lands under the Leech Lake Band of Ojibwe Reservation Restoration Act (LLBORRA).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Unless there are protests of this action, the filing of the plats described in this notice will happen on August 5, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Written notices protesting any of these surveys must be sent to the State Director, BLM Eastern States, 5275 Leesburg Pike, Suite 102-A, Falls Church, VA, 22041.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Frank D. Radford, Chief Cadastral Surveyor for Eastern States; (703) 558-7759; email: 
                        <E T="03">fradford@blm.gov;</E>
                         or U.S. Postal Service: BLM-ES, 5275 Leesburg Pike, Suite 102-A, Falls Church, VA, 22041. Attn: Cadastral Survey. Individuals in the United States who are deaf, deafblind, hard of hearing, or have a speech disability may dial 711 (TTY, TDD, or TeleBraille) to access telecommunications relay services. Individuals outside the United States should use the relay services offered within their country to make international calls to the point-of-contact in the United States.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Fifth Principal Meridian, Minnesota</HD>
                <FP>T. 146 N., R. 27 W.</FP>
                <P>The dependent resurvey of a portion of the subdivisional lines, a portion of the record meander lines, the subdivision of section 29, and the survey of a partition line for the transfer of lands pursuant to the LLBORRA, Cass County, Minnesota, was accepted on September 30, 2025.</P>
                <FP>T. 145 N., R. 29 W.</FP>
                <P>The dependent resurvey of a portion of the east boundary, a portion of the subdivisional lines, a portion of the record meander lines, the subdivision of section 12, and the survey of a partition line for the transfer of lands pursuant to the LLBORRA, Cass County, Minnesota, was accepted September 30, 2025.</P>
                <FP>T. 146 N., R. 29 W.</FP>
                <P>The dependent resurvey of a portion of the south boundary, a portion of the subdivisional lines, a portion of the record meander lines, a portion of the subdivision of section 34, and the survey of a partition line for the transfer of lands pursuant to the LLBORRA, Cass County, Minnesota, was accepted September 30, 2025.</P>
                <FP>T. 142 N., R. 31 W.</FP>
                <P>The dependent resurvey of a portion of the subdivisional lines, a portion of the record meander lines, the subdivision of section 14, and the survey of the partition lines for the transfer of lands pursuant to the LLBORRA, Cass County, Minnesota, was accepted March 31, 2025.</P>
                <FP>T. 143 N., R. 31 W.</FP>
                <P>The dependent resurvey of a portion of the subdivisional lines, and a portion of the record meander lines, and the survey of partition lines for the transfer of lands pursuant to the LLBORRA in lot 1 of section 26, Cass County, Minnesota, was accepted September 30, 2024.</P>
                <FP>T. 145 N., R. 31 W.</FP>
                <P>The dependent resurvey of portions of the east boundary, a portion of the subdivisional lines, a portion of the record meander line, the subdivision of sections 13, 22, and 36, and the survey of partition lines for the transfer of lands pursuant to the LLBORRA, Cass County, Minnesota, was accepted September 18, 2025.</P>
                <P>
                    A person or party who wishes to protest a survey must file a written notice of protest within 30 calendar days from the date of this publication at the address listed in the 
                    <E T="02">ADDRESSES</E>
                     section of this notice. A notice of protest is considered filed on the date it is received by the State Director for Eastern States during regular business hours; if received after regular business hours, a notice of protest will be considered filed the next business day. Any notice of protest filed after the scheduled date of official filing will be untimely and will not be considered. A statement of reasons for the protest may be filed with the notice of protest and must be filed within 30 calendar days after the protest is filed. If a notice of protest against the survey is received prior to the date of official filing, the filing will be stayed pending consideration of the protest. A plat will not be officially filed until the next business day after all protests have been dismissed or otherwise resolved.
                </P>
                <P>Before including your address, phone number, email address, or other personal identifiable information in your notice of protest or statement of reasons, please be aware that your entire protest, including your personal identifiable information may be made publicly available at any time. While you can ask us in your comment to withhold your personal identifiable information from public review, we cannot guarantee that we will be able to do so.</P>
                <P>A copy of the described plats will be placed in the open files, and available to the public, as a matter of information.</P>
                <EXTRACT>
                    <FP>(Authority: 43 U.S.C. Chap. 3)</FP>
                </EXTRACT>
                <SIG>
                    <NAME>Frank D. Radford,</NAME>
                    <TITLE>Chief Cadastral Surveyor for Eastern States.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13503 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4331-18-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Office of Natural Resources Revenue</SUBAGY>
                <DEPDOC>[Docket No. ONRR-2012-0006; DS63636400 DRT000000.CH7000267D1113RT] OMB Control Number 1012-0005</DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Federal Oil and Gas Valuation</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Natural Resources Revenue (ONRR), Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of information collection; request for comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In accordance with the Paperwork Reduction Act of 1995 (PRA), ONRR is proposing to renew an information collection. Through this Information Collection Request (ICR), ONRR seeks renewed authority to collect information necessary to verify proper reporting and payment of royalties and other amounts due to the United States under Federal oil and gas leases; determine requests for prepayment or accounting and auditing 
                        <PRTPAGE P="41083"/>
                        relief for certain marginal properties; and to evaluate requests to exceed transportation and processing allowance limits. ONRR uses Form ONRR-4393 (Request to Exceed Regulatory Allowance Limitation) as part of these information collection requirements.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Your written comments must be received on or before August 5, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        All comment submissions must (1) reference “Office of Management and Budget (OMB) Control Number 1012-0005” in the subject line; (2) be sent to ONRR before the close of the comment period listed under 
                        <E T="02">DATES</E>
                        ; and (3) be sent through one of the following two methods:
                    </P>
                    <P>
                        • 
                        <E T="03">Electronically via the Federal eRulemaking Portal:</E>
                         Please visit 
                        <E T="03">https://www.regulations.gov.</E>
                         Enter the Docket ID Number for this ICR renewal (“ONRR-2012-0006”) and click “Search” to view the publications associated with the docket folder. Locate the document with an open comment period and click the “Comment” button. Follow the prompts to submit your comment prior to the close of the comment period.
                    </P>
                    <P>
                        • 
                        <E T="03">Email Submissions:</E>
                         Please submit your comments to 
                        <E T="03">ONRR_RegulationsMailbox@onrr.gov</E>
                         with the OMB Control Number (“OMB Control No. 1012-0005”) listed in the subject line of your email. Email submissions must be postmarked on or before the close of the comment period.
                    </P>
                    <P>
                        <E T="03">Docket:</E>
                         To access the docket folder to view the ICR 
                        <E T="04">Federal Register</E>
                         publications, go to 
                        <E T="03">https://www.regulations.gov</E>
                         and search “ONRR-2012-0006” to view renewal notices recently published in the 
                        <E T="04">Federal Register</E>
                        , publications associated with prior renewals, and applicable public comments received for this ICR. ONRR will make the comments submitted in response to this notice available for public viewing at 
                        <E T="03">https://www.regulations.gov.</E>
                    </P>
                    <P>
                        <E T="03">OMB ICR Data:</E>
                         OMB also maintains information on ICR renewals and approvals. You may access this information at 
                        <E T="03">https://www.reginfo.gov/public/do/PRASearch.</E>
                         Please use the following instructions: Under the “OMB Control Number” heading enter “1012-0005” and click the “Search” button located at the bottom of the page. To view the ICR renewal or OMB approval status, click on the latest entry based on the most recent date. On the “View ICR—OIRA Conclusion” page, check the box next to “All” to display all available ICR information provided by OMB.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        To request additional information about this ICR, please contact Jonathan Fairbairn, Royalty Valuation, ONRR, by email at 
                        <E T="03">Jonathan.Fairbairn@onrr.gov</E>
                         or by telephone at (303) 231-3337. 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>
                    Pursuant to the PRA, 44 U.S.C. 3501 
                    <E T="03">et seq.,</E>
                     and 5 CFR 1320.5, all information collections, as defined in 5 CFR 1320.3, require approval by OMB. ONRR may not conduct or sponsor, and you are not required to respond to, a collection of information unless it displays a currently valid OMB control number.
                </P>
                <P>As part of ONRR's continuing effort to reduce paperwork and respondent burdens, ONRR is inviting the public and other Federal agencies to comment on new, proposed, revised, and continuing collections of information in accordance with the PRA and 5 CFR 1320.8(d)(1). This helps ONRR to assess the impact of its information collection requirements and minimize the public's reporting burden. It also helps the public understand ONRR's information collection requirements and provide the requested data in the desired format.</P>
                <P>ONRR is especially interested in public comments addressing the following:</P>
                <P>(1) Whether the collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility.</P>
                <P>(2) The accuracy of ONRR's estimate of the burden for this collection of information, including the validity of the methodology and assumptions used.</P>
                <P>(3) Ways to enhance the quality, utility, and clarity of the information to be collected.</P>
                <P>
                    (4) How might the agency minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, 
                    <E T="03">e.g.,</E>
                     permitting electronic submission of response.
                </P>
                <P>
                    As required in 5 CFR 1320.8(d), ONRR published a 60-day notice, for review and comment, in the 
                    <E T="04">Federal Register</E>
                     on March 3, 2026 (91 FR 10413). ONRR reached out to five contacts for input and received no comments.
                </P>
                <P>Comments that you submit in response to this notice are a matter of public record. ONRR will include or summarize each comment in its request to OMB to approve this ICR. Before including your address, phone number, email address, or other personal identifying information in your comment, you should be aware that your entire comment—including your personal identifying information—may be made publicly available at any time. While you can ask ONRR in your comment to withhold your personal identifying information from public review, ONRR cannot guarantee that it will be able to do so.</P>
                <HD SOURCE="HD1">(a) General Information</HD>
                <P>
                    ONRR reviews and audits the reporting and payment of royalties and other amounts due to the United States under Federal oil and gas leases. 
                    <E T="03">See</E>
                     U.S. Department of the Interior Departmental Manual, 112 DM 34.1 (Dec. 9, 2020). ONRR's responsibilities include valuing oil and gas for royalty purposes, evaluating claimed transportation and processing allowances, and granting royalty prepayment, accounting, and other relief for marginal properties in appropriate circumstances. ONRR collects the information covered by this ICR for these purposes. ONRR shares information with the Bureau of Land Management, Bureau of Indian Affairs, Bureau of Safety and Environmental Enforcement, Bureau of Ocean Energy Management, and State governments for their land and lease management responsibilities.
                </P>
                <HD SOURCE="HD1">(b) Federal Oil and Gas Royalties and Valuation</HD>
                <P>
                    Title 30 CFR part 1202—Royalties, subparts B and C, and 30 CFR part 1206—Product Valuation, subparts C and D, require a lessee to provide certain information necessary to calculate royalties due to the United States. Information collected under these subparts is used for valuing oil and gas, calculating and allocating transportation and processing allowances, determining location and quality differentials, and allocating residue gas and gas plant products to leases. 
                    <E T="03">See</E>
                     §§ 1206.102, 1206.108, 1206.110, 1206.113, 1206.141, 1206.142, 1206.148, 1206.150, 1206.152 to 1206.154, 1206.160, and 1206.161.
                </P>
                <P>
                    Some information collected under parts 1202 and 1206 is submitted on Form ONRR-2014 (Report of Sales and Royalty Remittance). This ICR does not include burden hours for submitting information on form ONRR-2014 because those burden hours are addressed in ONRR's ICR 1012-0004 (Royalty and Production Reporting). 
                    <E T="03">See</E>
                      
                    <PRTPAGE P="41084"/>
                    Agency Information Collection Activities; Royalty and Production Reporting, 90 FR 36068 (July 31, 2025).
                </P>
                <HD SOURCE="HD1">(c) Accounting and Auditing Relief for Marginal Properties</HD>
                <P>
                    ONRR's regulations, at 30 CFR part 1204, allow ONRR or a State that receives a statutorily prescribed portion of the royalties from a Federal lease to grant certain relief for marginal properties. This relief includes allowing a lessee to make a lump-sum advance payment of royalties instead of monthly royalty payments and various accounting and auditing relief options. 
                    <E T="03">See</E>
                     30 CFR 1204.3. Lessees must submit information to ONRR for this relief. 
                    <E T="03">See</E>
                     §§ 1204.202, 1204.203, 1204.205, 1204.206, and 1204.209 through 1204.211.
                </P>
                <HD SOURCE="HD1">(d) Requests To Exceed Allowance Limits</HD>
                <P>
                    Title 30 CFR part 1206—Product Valuation, subparts C and D, prior to their amendment effective January 1, 2017, permitted a Federal oil and gas lessee to request to exceed certain caps that ONRR's regulations placed on transportation and processing allowances by filing form ONRR-4393 (Request to Exceed Regulatory Allowance Limitation), with supporting documentation. 
                    <E T="03">See</E>
                     §§ 1206.109(c)(2), 1206.153(c)(3), and 1206.158(c)(3). Subject to the statute of limitations, a lessee may file this form to request to exceed the caps for oil and gas produced prior to January 1, 2017. ONRR revised the form's general instructions to align with current regulations and to update the mailstop number.
                </P>
                <P>This ICR does not include burden hours for submitting information on Form ONRR-4393 for Indian leases because those burden hours are addressed in ONRR's ICR 1012-0002 (Indian Oil and Gas Valuation).</P>
                <HD SOURCE="HD1">(e) Information Collections</HD>
                <P>This ICR covers the paperwork requirements under 30 CFR parts 1202, 1204, and 1206.</P>
                <P>
                    <E T="03">Title of Collection:</E>
                     Federal Oil and Gas Valuation—30 CFR parts 1202, 1204 and 1206.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     1012-0005.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     ONRR-4393.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of a currently approved collection.
                </P>
                <P>
                    <E T="03">Respondents/Affected Public:</E>
                     Businesses.
                </P>
                <P>
                    <E T="03">Total Estimated Number of Annual Respondents:</E>
                     100 Federal lessees/designees and 7 States for Federal oil and gas.
                </P>
                <P>
                    <E T="03">Total Estimated Number of Annual Responses:</E>
                     110.
                </P>
                <P>
                    <E T="03">Estimated Completion Time per Response:</E>
                     The average completion time is 70.8 hours per response. The average completion time is calculated by dividing the total estimated burden hours (7,788) by the estimated annual responses (110).
                </P>
                <P>
                    <E T="03">Estimated Number of Annual Burden Hours:</E>
                     7,788 hours.
                </P>
                <P>
                    <E T="03">Respondent's Obligation:</E>
                     The information that a lessee must submit pursuant to 30 CFR parts 1202 and 1206 for calculating royalties and other payment obligations for Federal oil and gas leases is mandatory. The information that a lessee must submit to obtain prepayment, accounting, or auditing relief for qualifying Federal marginal properties or to exceed the transportation and processing regulatory caps for oil and gas produced is required to obtain or retain a benefit.
                </P>
                <P>
                    <E T="03">Frequency of Collection:</E>
                     Annually and on occasion.
                </P>
                <P>
                    <E T="03">Estimated Annual Nonhour Burden Cost:</E>
                     ONRR has identified no “nonhour” cost burden associated with the collection of information.
                </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">Authority:</E>
                     Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ).
                </P>
                <SIG>
                    <NAME>April Lockler,</NAME>
                    <TITLE>Acting Director of the Office of Natural Resources Revenue.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13536 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4335-30-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">INTERNATIONAL TRADE COMMISSION</AGENCY>
                <DEPDOC>[Investigation No. 731-TA-1092 (Third Review)]</DEPDOC>
                <SUBJECT>Diamond Sawblades and Parts Thereof From China; Scheduling of an Expedited Five-Year Review</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>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Commission hereby gives notice of the scheduling of an expedited review pursuant to the Tariff Act of 1930 (“the Act”) to determine whether revocation of the antidumping duty order on diamond sawblades and parts thereof from China would be likely to lead to continuation or recurrence of material injury within a reasonably foreseeable time.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>June 5, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Alexis Yim (202-708-1446), 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/>
                <P>
                    <E T="03">Background.</E>
                    —On June 5, 2026, the Commission determined that the domestic interested party group response to its notice of institution (91 FR 10131, March 2, 2026) of the subject five-year review was adequate and that the respondent interested party group response was inadequate. The Commission did not find any other circumstances that would warrant conducting a full review.
                    <SU>1</SU>
                    <FTREF/>
                     Accordingly, the Commission determined that it would conduct an expedited review pursuant to section 751(c)(3) of the Act (19 U.S.C. 1675(c)(3)).
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         A record of the Commissioners' votes, the Commission's statement on adequacy, and any individual Commissioner's statements will be available from the Office of the Secretary and at the Commission's website.
                    </P>
                </FTNT>
                <P>For further information concerning the conduct of this review and rules of general application, consult the Commission's Rules of Practice and Procedure, part 201, subparts A and B (19 CFR part 201), and part 207, subparts A, D, E, and F (19 CFR part 207).</P>
                <P>
                    <E T="03">Staff report.</E>
                    —A staff report containing information concerning the subject matter of the review has been placed in the nonpublic record, and will be made available to persons on the Administrative Protective Order service list for this review on July 22, 2026. A public version will be issued thereafter, pursuant to § 207.62(d)(4) of the Commission's rules.
                </P>
                <P>
                    <E T="03">Written submissions.</E>
                    —As provided in § 207.62(d) of the Commission's rules, interested parties that are parties to the review and that have provided individually adequate responses to the notice of institution,
                    <SU>2</SU>
                    <FTREF/>
                     and any party 
                    <PRTPAGE P="41085"/>
                    other than an interested party to the review may file written comments with the Secretary on what determination the Commission should reach in the review. Comments are due on or before 5:15 p.m. on July 29, 2026 and may not contain new factual information. Any person that is neither a party to the five-year review nor an interested party may submit a brief written statement (which shall not contain any new factual information) pertinent to the review by July 29, 2026. However, should the Department of Commerce (“Commerce”) extend the time limit for its completion of the final results of its review, the deadline for comments (which may not contain new factual information) on Commerce's final results is three business days after the issuance of Commerce's results. If comments contain business proprietary information (BPI), they must conform with the requirements of §§ 201.6, 207.3, and 207.7 of the Commission's rules. The Commission's 
                    <E T="03">Handbook on Filing Procedures,</E>
                     available on the Commission's website at 
                    <E T="03">https://www.usitc.gov/documents/handbook_on_filing_procedures.pdf,</E>
                     elaborates upon the Commission's procedures with respect to filings.
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         The Commission has found the responses submitted on behalf of the Diamond Sawblades Manufacturers' Coalition (“DSMC”) to be individually adequate. Comments from other interested parties will not be accepted (
                        <E T="03">see</E>
                         19 CFR 207.62(d)(2)).
                    </P>
                </FTNT>
                <P>In accordance with §§ 201.16(c) and 207.3 of the rules, each document filed by a party to the review must be served on all other parties to the review (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>
                    <E T="03">Determination.</E>
                    —The Commission has determined this review is extraordinarily complicated and therefore has determined to exercise its authority to extend the review period by up to 90 days pursuant to 19 U.S.C. 1675(c)(5)(B).
                </P>
                <P>
                    <E T="03">Authority:</E>
                     This review is being conducted under authority of title VII of the Tariff Act of 1930; this notice is published pursuant to § 207.62 of the Commission's rules.
                </P>
                <SIG>
                    <P>By order of the Commission.</P>
                    <DATED>Issued: July 1, 2026.</DATED>
                    <NAME>Lisa Barton,</NAME>
                    <TITLE>Secretary to the Commission.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13610 Filed 7-2-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-799 and 731-TA-1795 (Preliminary)]</DEPDOC>
                <SUBJECT>Glyphosate From China; Institution of Antidumping and Countervailing Duty Investigations and Scheduling of Preliminary Phase 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>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Commission hereby gives notice of the institution of investigations and commencement of preliminary phase antidumping and countervailing duty investigation Nos. 701-TA-799 and 731-TA-1795 (Preliminary) pursuant to the Tariff Act of 1930 to determine whether there is a reasonable indication that an industry in the United States is materially injured or threatened with material injury, or the establishment of an industry in the United States is materially retarded, by reason of imports of glyphosate from China, provided for in subheadings 2931.49.00 and 3808.93.50 of the Harmonized Tariff Schedule of the United States, that are alleged to be sold in the United States at less than fair value and alleged to be subsidized by the Government of China. Unless the Department of Commerce (“Commerce”) extends the time for initiation, the Commission must reach a preliminary determination in antidumping and countervailing duty investigations in 45 days, or in this case by August 14, 2026. The Commission's views must be transmitted to Commerce within five business days thereafter, or by August 21, 2026.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATE:</HD>
                    <P>June 30, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Charles Cummings((202) 708-1666), 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 these investigations may be viewed on the Commission's electronic docket (EDIS) at 
                        <E T="03">https://edis.usitc.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Background.</E>
                    —These investigations are being instituted, pursuant to sections 703(a) and 733(a) of the Tariff Act of 1930 (19 U.S.C. 1671b(a) and 1673b(a)), in response to petitions filed on June 30, 2026, by Monsanto Company and its wholly owned subsidiary Ruveon LLC (St. Louis, Missouri).
                </P>
                <P>For further information concerning the conduct of these investigations and rules of general application, consult the Commission's Rules of Practice and Procedure, part 201, subparts A and B (19 CFR part 201), and part 207, subparts A and B (19 CFR part 207).</P>
                <P>
                    <E T="03">Participation in the investigations and public service list.</E>
                    —Persons wishing to participate in the investigations as parties must file an entry of appearance with the Secretary to the Commission, as provided in §§ 201.11 and 207.10 of the Commission's rules, not later than seven days after publication of this notice in the 
                    <E T="04">Federal Register</E>
                    . Industrial users and (if the merchandise under investigation is sold at the retail level) representative consumer organizations have the right to appear as parties in Commission antidumping duty and countervailing duty investigations. The Secretary will prepare a public service list containing the names and addresses of all persons, or their representatives, who are parties to these investigations upon the expiration of the period for filing entries of appearance.
                </P>
                <P>
                    <E T="03">Limited disclosure of business proprietary information (BPI) under an administrative protective order (APO) and BPI service list.</E>
                    —Pursuant to § 207.7(a) of the Commission's rules, the Secretary will make BPI gathered in these investigations available to authorized applicants representing interested parties (as defined in 19 U.S.C. 1677(9)) who are parties to the investigations under the APO issued in the investigations, provided that the application is made not later than seven days after the publication of this notice in the 
                    <E T="04">Federal Register</E>
                    . A separate service list will be maintained by the Secretary for those parties authorized to receive BPI under the APO.
                </P>
                <P>
                    <E T="03">Conference.</E>
                    —The Office of Investigations will hold a staff conference in connection with the preliminary phase of these investigations beginning at 9:30 a.m. on Tuesday, July 21, 2026. Requests to appear at the conference should be emailed to 
                    <E T="03">preliminaryconferences@usitc.gov</E>
                     (DO NOT FILE ON EDIS) on or before noon on Friday, July 17, 2026. Please provide an email address for each conference participant in the email. Information on conference procedures, format, and participation, including guidance for requests to appear as a 
                    <PRTPAGE P="41086"/>
                    witness via videoconference, will be available on the Commission's Public Calendar (Calendar (USITC) | United States International Trade Commission). A nonparty who has testimony that may aid the Commission's deliberations may request permission to participate by submitting a short statement.
                </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">Written submissions.</E>
                    —As provided in §§ 201.8 and 207.15 of the Commission's rules, any person may submit to the Commission on or before 5:15 p.m. on July 24, 2026, a written brief containing information and arguments pertinent to the subject matter of the investigations. Parties shall file written testimony and supplementary material in connection with their presentation at the conference no later than 4:00 p.m. on July 20, 2026. All written submissions must conform with the provisions of § 201.8 of the Commission's rules; any submissions that contain BPI must also conform with the requirements of §§ 201.6, 207.3, and 207.7 of the Commission's rules. The Commission's 
                    <E T="03">Handbook on Filing Procedures,</E>
                     available on the Commission's website at 
                    <E T="03">https://www.usitc.gov/documents/handbook_on_filing_procedures.pdf,</E>
                     elaborates upon the Commission's procedures with respect to filings.
                </P>
                <P>In accordance with §§ 201.16(c) and 207.3 of the rules, each document filed by a party to the investigations must be served on all other parties to the investigations (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>
                    <E T="03">Certification.</E>
                    —Pursuant to § 207.3 of the Commission's rules, any person submitting information to the Commission in connection with these investigations must certify that the information is accurate and complete to the best of the submitter's knowledge. In making the certification, the submitter will acknowledge that any information that it submits to the Commission during these investigations may be disclosed to and used: (i) by the Commission, its employees and Offices, and contract personnel (a) for developing or maintaining the records of these or related investigations or reviews, or (b) in internal investigations, audits, reviews, and evaluations relating to the programs, personnel, and operations of the Commission including under 5 U.S.C. Appendix 3; or (ii) by U.S. government employees and contract personnel, solely for cybersecurity purposes. All contract personnel will sign appropriate nondisclosure agreements.
                </P>
                <P>
                    <E T="03">Authority:</E>
                     These investigations are being conducted under authority of title VII of the Tariff Act of 1930; this notice is published pursuant to § 207.12 of the Commission's rules.
                </P>
                <SIG>
                    <P>By order of the Commission.</P>
                    <DATED>Issued: June 30, 2026.</DATED>
                    <NAME>Lisa Barton,</NAME>
                    <TITLE>Secretary to the Commission.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13517 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7020-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">NATIONAL ARCHIVES AND RECORDS ADMINISTRATION</AGENCY>
                <DEPDOC>[NARA-2026-027]</DEPDOC>
                <SUBJECT>State, Local, Tribal, and Private Sector Policy Advisory Committee (SLTPS-PAC); Meeting</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Information Security Oversight Office (ISOO), National Archives and Records Administration (NARA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of Federal Advisory Committee meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>We are announcing an upcoming meeting of the State, Local, Tribal, and Private Sector Policy Advisory Committee (SLTPS-PAC) in accordance with the Federal Advisory Committee Act and implementing regulations.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The meeting will be on July 22, 2026, from 11:30 a.m. to 12:30 p.m.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>This meeting will be a hybrid of virtual and in person in the Madison Conference Room, 700 Pennsylvania Avenue; Washington, DC 20408. We will send instructions on how to access the meeting to those who register according to the instructions below.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Heather Harris Pagán, ISOO Senior Program Analyst, at 
                        <E T="03">SLTPS_PAC@nara.gov</E>
                         or 301-550-1902. Contact ISOO at 
                        <E T="03">ISOO@nara.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This meeting is open to the public in accordance with the Federal Advisory Committee Act (5 U.S.C. app 2) and implementing regulations at 41 CFR 102-3. The Committee will discuss matters relating to the classified national security information program for state, local, tribal, and private sector entities.</P>
                <P>
                    <E T="03">Procedures:</E>
                     Members of the public must register in advance for the meeting through the link 
                    <E T="03">https://www.zoomgov.com/meeting/register/KAlvecawRaOOlkiCYYWWng</E>
                     if they wish to attend. Please notify Heather Harris Pagán if you will be in person.
                </P>
                <SIG>
                    <NAME>Merrily Harris,</NAME>
                    <TITLE>Committee Management Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13590 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7515-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">NATIONAL FOUNDATION ON THE ARTS AND THE HUMANITIES</AGENCY>
                <SUBAGY>National Endowment for the Arts</SUBAGY>
                <SUBJECT>Arts Advisory Panel Meetings</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Endowment for the Arts.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of meetings.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Pursuant to the Federal Advisory Committee Act, as amended, notice is hereby given that 11 meetings of the Arts Advisory Panel to the National Council on the Arts will be held by teleconference or videoconference.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        See the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section for individual meeting times and dates. All meetings are Eastern time and ending times are approximate:
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>National Endowment for the Arts, Constitution Center, 400 7th St. SW, Washington, DC 20506.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Further information with reference to these meetings can be obtained from Daniel Beattie, Office of Guidelines &amp; Panel Operations, National Endowment for the Arts, Washington, DC 20506; 
                        <E T="03">ogpo@arts.gov,</E>
                         or call 202-682-5688.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The closed portions of meetings are for the purpose of Panel review, discussion, evaluation, and recommendations on financial assistance under the National Foundation on the Arts and the Humanities Act of 1965, as amended, including information given in confidence to the agency. In accordance with the determination of the Chair of April 30, 2026, these sessions will be closed to the public pursuant to 5 U.S.C. 10.</P>
                <P>
                    <E T="03">The upcoming meetings are:</E>
                </P>
                <P>
                    <E T="03">Opera (review of applications):</E>
                     This meeting will be closed.
                </P>
                <P>
                    <E T="03">Date and time:</E>
                     July 14, 2026; 11:30 a.m. to 1:30 p.m.
                </P>
                <P>
                    <E T="03">Dance (review of applications):</E>
                     This meeting will be closed.
                    <PRTPAGE P="41087"/>
                </P>
                <P>
                    <E T="03">Date and time:</E>
                     August 3, 2026; 1:00 p.m. to 3:00 p.m.
                </P>
                <P>
                    <E T="03">Theater (review of applications):</E>
                     This meeting will be closed.
                </P>
                <P>
                    <E T="03">Date and time:</E>
                     August 4, 2026; 12:00 p.m. to 2:00 p.m.
                </P>
                <P>
                    <E T="03">Dance (review of applications):</E>
                     This meeting will be closed.
                </P>
                <P>
                    <E T="03">Date and time:</E>
                     August 4, 2026; 1:00 p.m. to 3:00 p.m.
                </P>
                <P>
                    <E T="03">Theater (review of applications):</E>
                     This meeting will be closed.
                </P>
                <P>
                    <E T="03">Date and time:</E>
                     August 4, 2026; 3:00 p.m. to 5:00 p.m.
                </P>
                <P>
                    <E T="03">Media Arts (review of applications):</E>
                     This meeting will be closed.
                </P>
                <P>
                    <E T="03">Date and time:</E>
                     August 5, 2026; 11:30 a.m. to 1:30 p.m.
                </P>
                <P>
                    <E T="03">Dance (review of applications):</E>
                     This meeting will be closed.
                </P>
                <P>
                    <E T="03">Date and time:</E>
                     August 5, 2026; 1:00 p.m. to 3:00 p.m.
                </P>
                <P>
                    <E T="03">Media Arts (review of applications):</E>
                     This meeting will be closed.
                </P>
                <P>
                    <E T="03">Date and time:</E>
                     August 5, 2026; 2:30 p.m. to 4:30 p.m.
                </P>
                <P>
                    <E T="03">Dance (review of applications):</E>
                     This meeting will be closed.
                </P>
                <P>
                    <E T="03">Date and time:</E>
                     August 6, 2026; 1:00 p.m. to 3:00 p.m.
                </P>
                <P>
                    <E T="03">Media Arts (review of applications):</E>
                     This meeting will be closed.
                </P>
                <P>
                    <E T="03">Date and time:</E>
                     August 6, 2026; 2:30 p.m. to 4:30 p.m.
                </P>
                <P>
                    <E T="03">Presenting and Multidisciplinary Works (review of applications):</E>
                     This meeting will be closed.
                </P>
                <P>
                    <E T="03">Date and time:</E>
                     August 6, 2026; 3:00 p.m. to 5:00 p.m.
                </P>
                <SIG>
                    <DATED>Dated: July 1, 2026.</DATED>
                    <NAME>David Travis,</NAME>
                    <TITLE>Specialist, Guidelines &amp; Panel Operations, National Endowment for the Arts.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13613 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7537-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">POSTAL REGULATORY COMMISSION</AGENCY>
                <DEPDOC>[Docket Nos. MC2026-287 and K2026-284; MC2026-288 and K2026-285]</DEPDOC>
                <SUBJECT>New Postal Products</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Postal Regulatory Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Commission is noticing a recent Postal Service filing for the Commission's consideration concerning a negotiated service agreement. This notice informs the public of the filing, invites public comment, and takes other administrative steps.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Comments are due:</E>
                         July 8, 2026.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit comments electronically via the Commission's Filing Online system at 
                        <E T="03">https://www.prc.gov.</E>
                         Those who cannot submit comments electronically should contact the person identified in the 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section by telephone for advice on filing alternatives.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>David A. Trissell, General Counsel, at 202-789-6820.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Table of Contents</HD>
                <EXTRACT>
                    <FP SOURCE="FP-2">I. Introduction</FP>
                    <FP SOURCE="FP-2">II. Public Proceeding(s)</FP>
                    <FP SOURCE="FP-2">III. Summary Proceeding(s)</FP>
                </EXTRACT>
                <HD SOURCE="HD1">I. Introduction</HD>
                <P>Pursuant to 39 CFR 3041.405, the Commission gives notice that the Postal Service filed request(s) for the Commission to consider matters related to Competitive negotiated service agreement(s). The request(s) may propose the addition of a negotiated service agreement from the Competitive product list or the modification of an existing product currently appearing on the Competitive product list.</P>
                <P>
                    The public portions of the Postal Service's request(s) can be accessed via the Commission's website (
                    <E T="03">http://www.prc.gov</E>
                    ). Non-public portions of the Postal Service's request(s), if any, can be accessed through compliance with the requirements of 39 CFR 3011.301.
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See</E>
                         Docket No. RM2018-3, Order Adopting Final Rules Relating to Non-Public Information, June 27, 2018, Attachment A at 19-22 (Order No. 4679).
                    </P>
                </FTNT>
                <P>Section II identifies the docket number(s) associated with each Postal Service request, if any, that will be reviewed in a public proceeding as defined by 39 CFR 3010.101(p), the title of each such request, the request's acceptance date, and the authority cited by the Postal Service for each request. For each such request, the Commission appoints an officer of the Commission to represent the interests of the general public in the proceeding, pursuant to 39 U.S.C. 505 and 39 CFR 3000.114 (Public Representative). The Public Representative does not represent any individual person, entity or particular point of view, and, when Commission attorneys are appointed, no attorney-client relationship is established. Section II also establishes comment deadline(s) pertaining to each such request.</P>
                <P>The Commission invites comments on whether the Postal Service's request(s) identified in Section II, if any, are consistent with the policies of title 39. Applicable statutory and regulatory requirements include 39 U.S.C. 3632, 39 U.S.C. 3633, 39 U.S.C. 3642, 39 CFR part 3035, and 39 CFR part 3041. Comment deadline(s) for each such request, if any, appear in Section II.</P>
                <P>
                    Section III identifies the docket number(s) associated with each Postal Service request, if any, to add a standardized distinct product to the Competitive product list or to amend a standardized distinct product, the title of each such request, the request's acceptance date, and the authority cited by the Postal Service for each request. Standardized distinct products are negotiated service agreements that are variations of one or more Competitive products, and for which financial models, minimum rates, and classification criteria have undergone advance Commission review. 
                    <E T="03">See</E>
                     39 CFR 3041.110(n); 39 CFR 3041.205(a). Such requests are reviewed in summary proceedings pursuant to 39 CFR 3041.325(c)(2) and 39 CFR 3041.505(f)(1). Pursuant to 39 CFR 3041.405(c)-(d), the Commission does not appoint a Public Representative or request public comment in proceedings to review such requests.
                </P>
                <HD SOURCE="HD1">II. Public Proceeding(s)</HD>
                <P>
                    1. 
                    <E T="03">Docket No(s).:</E>
                     MC2026-287 and K2026-284; Filing Title: USPS Request to Add Priority Mail Express International, Priority Mail International &amp; First-Class Package International Service Contract 116 to Competitive Product List and Notice of Filing Materials Under Seal; Filing Acceptance Date: June 30, 2026; Filing Authority: 39 U.S.C. 3642, 39 CFR 3035.105, and 39 CFR 3041.310; Public Representative: Maxine Bradley; Comments Due: July 8, 2026.
                </P>
                <HD SOURCE="HD1">III. Summary Proceeding(s)</HD>
                <P>
                    1. 
                    <E T="03">Docket No(s).:</E>
                     MC2026-288 and K2026-285; Filing Title: USPS Request to Add New Fulfillment Standardized Distinct Product, PM-GA Contract 1027, and Notice of Filing Materials Under Seal; Filing Acceptance Date: June 30, 2026; Filing Authority: 39 U.S.C. 3642 and 3633, 39 CFR 3035.105, and 39 CFR 3041.325.
                </P>
                <P>
                    This Notice will be published in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <SIG>
                    <NAME>Danielle LeFlore,</NAME>
                    <TITLE>Legal Assistant.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13617 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7710-FW-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="41088"/>
                <AGENCY TYPE="N">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release No. 34-105818; File No. SR-BOX-2026-14]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; BOX Exchange LLC; Notice of Filing and Immediate Effectiveness of a Proposed Rule Change To Amend the Review of Professional Orders</SUBJECT>
                <DATE>June 30, 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 17, 2026, BOX Exchange LLC (the “Exchange”) filed with the Securities and Exchange Commission (“Commission”) the proposed rule change as described in Items I and II below, which Items have been prepared by the self-regulatory organization. The Commission is publishing this notice to solicit comments on the proposed rule from interested persons.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>
                <P>
                    The Exchange proposes to amend BOX Rule 100(a)(52) (Definitions) to amend the Exchange's quarterly review of Professional 
                    <SU>3</SU>
                    <FTREF/>
                     orders. The text of the proposed rule change is available from the principal office of the Exchange, at the Commission's Public Reference Room and also on the Exchange's internet website at 
                    <E T="03">https://rules.boxexchange.com/rulefilings.</E>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         BOX Rule 100(a)(52). The term “Professional” means any person or entity that (i) is not a broker or dealer in securities, and (ii) places more than 390 orders in listed options per day on average during a calendar month for its own beneficial account(s). All Professional orders shall be appropriately marked by Participants. A Professional will be treated in the same manner as a broker-dealer for purposes of Rules 7150 and 7245.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <P>In its filing with the Commission, the self-regulatory organization included statements concerning the purpose of, and basis for, the proposed rule change and discussed any comments it received on the proposed rule change. The text of these statements may be examined at the places specified in Item IV below. The self-regulatory organization 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 BOX Rule 100(a)(52) (Definitions) to amend the Exchange's quarterly review of Professional orders. This filing is based on a proposal recently submitted by Nasdaq ISE, LLC (“ISE”).
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 105218 (April 13, 2026), 91 FR 20542 (April 16, 2026) (SR-ISE-2026-16) (Notice of Filing and Immediate Effectiveness of Proposed Rule Change To Amend the Review of Professional Orders).
                    </P>
                </FTNT>
                <P>
                    Today, orders for any Public Customer 
                    <SU>5</SU>
                    <FTREF/>
                     that averages more than 390 orders per day during any month of a calendar quarter must be represented as Professional orders for the next calendar quarter.
                    <SU>6</SU>
                    <FTREF/>
                     In order to properly represent orders entered on the Exchange, Participants 
                    <SU>7</SU>
                    <FTREF/>
                     are required currently to review their Public Customers' activity and, on at least a quarterly basis, designate orders as Public Customer Orders 
                    <SU>8</SU>
                    <FTREF/>
                     or Professional orders.
                    <SU>9</SU>
                    <FTREF/>
                     Specifically, Participants are required to conduct a quarterly review and make any appropriate changes to the way in which they are representing orders within five days after the end of each calendar quarter.
                    <SU>10</SU>
                    <FTREF/>
                     While Participants are required to designate accounts on a quarterly basis, if during a quarter the Exchange identifies a customer for which orders are being represented as Public Customer Orders but that has averaged more than 390 orders per day during a month, the Exchange will notify the Participant and the Participant is required to change the manner in which it is representing the customer's orders within five days.
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         BOX Rule 100(a)(53). The term “Public Customer” means a person that is not a broker or dealer in securities.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         The requirement to review Public Customers' activity on at least a quarterly basis to determine whether orders that are not for the account of a broker-dealer should be represented as Public Customer Orders or Professional orders is not in the current rule text, however it was described in the adopting proposal. 
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 77580 (April 11, 2016), 81 FR 22328 (April 15, 2016) (SR-BOX-2016-13) (Notice of Filing and Immediate Effectiveness of Proposed Rule Change to Amend BOX Rule 100 (Definitions) Relating to Professionals). The instant proposal seeks to codify the timing for review of Public Customers' activity.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         BOX Rule 100(a)(42). The term “Participant” means a firm, or organization that is registered with the Exchange pursuant to the Rule 2000 Series for purposes of participating in trading on a facility of the Exchange.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         BOX Rule 100(a)(54). The term “Public Customer Order” means an order for the account of a Public Customer.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See</E>
                         81 FR 22328 at 22331.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Proposal</HD>
                <P>At this time, the Exchange proposes to shorten the quarterly review and designation to a monthly review. The Exchange proposes to state at Rule 100(a)(52) that orders for any customer that had an average of more than 390 orders per day during any calendar month must be represented as Professional orders for the next calendar month.</P>
                <P>As noted, currently, each Participant is required to monitor Public Customer Orders to determine if the Public Customer has averaged more than 390 orders per day during a month. Determining whether a Public Customer has executed more than 390 orders per day during a month requires computing a daily average. As such, Participants should be performing the workflow necessary to designate orders on a daily basis. Therefore, the proposal does not amend the current workflow, rather, the proposal amends the timeframe to change the manner in which the customer's order is being represented from five days after the end of each calendar quarter to five days after the end of each calendar month.</P>
                <P>The Exchange does not believe that this amendment is a significant departure from the current rule, nor does it impose any burden on any Participant because each broker-dealer is required currently to perform the necessary calculation daily to arrive at the requisite average. Further, in addition to the calculation, broker-dealers are subject to know-your-customer and suitability requirements under FINRA Rules 2090 (Know Your Customer) and 2111 (Suitability) and would need to consider whether a customer meets the Professional designation for purposes of determining best execution and making appropriate recommendations. The Exchange notes that the trading behavior of a Public Customer can be distinguished from that of a Professional which is the purpose of the separate designations. Finally, it is the Exchange's understanding that some Participants currently designate a Public Customer that has averaged more than 390 orders per day during a month as a Professional on a more expedited basis, not waiting until five days after the quarter.</P>
                <P>
                    The Exchange believes that a calendar month is a sufficient time period to determine whether the activity of a customer meets the criteria for a Professional order. The Exchange believes that the shortened time period will ensure that the spirit of the designation of Professional order is met in that Participants will make any 
                    <PRTPAGE P="41089"/>
                    appropriate changes to the way in which they are representing orders in a 30-day timeframe as opposed to a 90-day timeframe, thereby ensuring the designation is applied in a more expeditious manner.
                </P>
                <P>The Exchange continues to believe that identifying Professional orders based upon the average number of orders entered in qualified accounts is an appropriate and objective approach to reasonably distinguish such persons and entities from retail investors or market participants.</P>
                <HD SOURCE="HD3">Implementation</HD>
                <P>The Exchange proposes implementing this rule change on July 1, 2026. The Exchange will issue a Regulatory Notice to provide notice to Participants of the proposed change.</P>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    The Exchange believes that the proposal is consistent with the requirements of Section 6(b) of the Securities Exchange Act of 1934 (the “Act”),
                    <SU>12</SU>
                    <FTREF/>
                     in general, and Section 6(b)(5) of the Act,
                    <SU>13</SU>
                    <FTREF/>
                     in particular, in that it is designed to prevent fraudulent and manipulative acts and practices, to promote just and equitable principles of trade, to foster cooperation and coordination with persons engaged in facilitating transactions in securities, to remove impediments to and perfect the mechanism of a free and open market and a national market system, and, in general to protect investors and the public interest.
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         15 U.S.C. 78f(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <P>In particular, the Exchange's proposal to shorten the quarterly look-back to a monthly look-back is consistent with the Act because it will ensure that the spirit of the designation of Professional order continues to be met, only on a more expedited basis—removing a potential delay of two months before affecting a change in the designation. The Exchange believes that this amendment will remove impediments to and perfect the mechanism of a free and open market and a national market system by promoting the consistent application of its rules and shortening the timeframe to change the designation for all Participants while continuing to provide a sufficient time period to determine whether the activity of a customer meets the criteria for a Professional order. Further, the Exchange believes that the shortened time period will continue to promote consistency in the treatment of orders as Professional orders while also preventing Participants with high volume from receiving benefits reserved for Public Customer Orders.</P>
                <P>As noted, currently, each Participant is required to monitor Public Customer Orders to determine if the Public Customer has averaged more than 390 orders per day during a month. Determining whether a Public Customer has executed more than 390 orders per day during a month requires computing a daily average. As such, Participants should be performing the workflow necessary to designate orders on a daily basis. Therefore, the proposal does not amend the current workflow, rather, the proposal amends the timeframe to change the manner in which the customer's order is being represented from five days after the end of each calendar quarter to five days after the end of each calendar month.</P>
                <P>
                    The Exchange does not believe that this amendment is a significant departure from the current rule, nor does it impose any burden on any Participant because each broker-dealer is required currently to perform the necessary calculation daily to arrive at the requisite average. Further, in addition to the calculation, broker-dealers are subject to know-your-customer and suitability requirements under FINRA Rules 2090 (Know Your Customer) and 2111 (Suitability) and would need to consider whether a customer meets the Professional designation for purposes of determining best execution and making appropriate recommendations. Finally, some Participants currently designate a Public Customer that has averaged more than 390 orders per day during a month as a Professional on a more expedited basis, not waiting until five days after the quarter. The Exchange notes that the trading behavior of a Public Customer can be distinguished from that of a Professional which is the purpose of the separate designations. The Exchange continues to believe that identifying Professional orders based upon the average number of orders entered in qualified accounts is an appropriately objective approach to reasonably distinguish such persons and entities from retail investors or market participants. Priority is one of the marketplace advantages provided to Public Customer Orders on the Exchange. Public Customer Orders are given execution priority over non-Public Customer orders and quotations of market makers at the same price in accordance with Exchange Rules.
                    <SU>14</SU>
                    <FTREF/>
                     Another marketplace advantage afforded to Public Customer Orders on the Exchange is that Participants are generally not assessed transaction fees or are assessed lower fees for the execution of Public Customer Orders. The purpose of these marketplace advantages is to attract retail order flow to the Exchange by leveling the playing field for retail investors over market Professionals. This proposal will continue to provide Public Customer accounts with marketplace advantages and distinguish those accounts non-Professional retail investors from the Professionals accounts. The Exchange notes that some non-broker-dealer individuals and entities have access to information and technology that enables them to Professionally trade listed options in the same manner as a broker or dealer in securities.
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">See, e.g.,</E>
                         Rule 7150 (Price Improvement Period (“PIP”)).
                    </P>
                </FTNT>
                <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. In this regard and as indicated above, the Exchange notes that the rule change is substantially similar to a filing recently submitted by ISE.
                    <SU>15</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">See supra</E>
                         note 4.
                    </P>
                </FTNT>
                <P>Specifically, the Exchange does not believe that the proposed rule change will impose any burden on intra-market competition because, today, each Participant is required to monitor Public Customer Orders to determine if the Public Customer has averaged more than 390 orders per day during a month. Determining whether a Public Customer has executed more than 390 orders per day during a month requires computing a daily average. As such, Participants should be performing the workflow necessary to designate orders on a daily basis. Therefore, the proposal does not amend the current workflow, rather, the proposal amends the timeframe to change the manner in which the customer's order is being represented from five days after the end of each calendar quarter to five days after the end of each calendar month.</P>
                <P>
                    The Exchange does not believe that this amendment is a significant departure from the current rule, nor does it impose any burden on any Participant because each broker-dealer is required currently to perform the necessary calculation daily to arrive at the requisite average. Further, in addition to the calculation, broker-dealers are subject to know-your-customer and suitability requirements under FINRA Rules 2090 (Know Your Customer) and 2111 (Suitability) and 
                    <PRTPAGE P="41090"/>
                    would need to consider whether a customer meets the Professional designation for purposes of determining best execution and making appropriate recommendations. Finally, some Participants currently designate a Public Customer that has averaged more than 390 orders per day during a month as a Professional on a more expedited basis, not waiting until five days after the quarter. The Exchange notes that the trading behavior of a Public Customer can be distinguished from that of a Professional which is the purpose of the separate designations.
                </P>
                <P>Further, the designation of Professional orders would not result in any different treatment of such orders for purposes of compliance with the Exchange's Rules. Public Customers have been granted certain priority over other non-broker-dealer individuals and entities that have access to information and technology that enables them to Professionally trade listed options in the same manner as a broker or dealer in securities. Further, the Public Customer designation allows the Exchange to attract order flow or create more competitive markets.</P>
                <P>Also, the Exchange does not believe that the proposed rule change will impose any burden on inter-market competition because other exchanges are expected to adopt similar rules.</P>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants, or Others</HD>
                <P>The Exchange has neither solicited nor received 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 Exchange has filed the proposed rule change pursuant to Section 19(b)(3)(A) of the Act 
                    <SU>16</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) 
                    <SU>17</SU>
                    <FTREF/>
                     thereunder. Because the foregoing proposed rule change does not: (i) significantly affect the protection of investors or the public interest; (ii) impose any significant burden on competition; and (iii) become operative for 30 days from the date on which it was filed, or such shorter time as the Commission may designate, it has become effective pursuant to Section 19(b)(3)(A) of the Act 
                    <SU>18</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) 
                    <SU>19</SU>
                    <FTREF/>
                     thereunder.
                    <SU>20</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         15 U.S.C. 78s(b)(3)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         17 CFR 240.19b-4(f)(6).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         15 U.S.C. 78s(b)(3)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         17 CFR 240.19b-4(f)(6).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         17 CFR 240.19b-4(f)(6). In addition, Rule 19b-4(f)(6) requires a self-regulatory organization to give the Commission written notice of its intent to file the proposed rule change at least five business days prior to the date of filing of the proposed rule change, or such shorter time as designated by the Commission. The Exchange has satisfied this requirement.
                    </P>
                </FTNT>
                <P>
                    A proposed rule change filed under Rule 19b-4(f)(6) 
                    <SU>21</SU>
                    <FTREF/>
                     normally does not become operative prior to 30 days after the date of the filing. However, pursuant to Rule 19b-4(f)(6)(iii),
                    <SU>22</SU>
                    <FTREF/>
                     the Commission may designate a shorter time if such action is consistent with the protection of investors and the public interest. The Exchange requested that the Commission waive the 30-day operative delay so that the proposal may become operative immediately upon filing. The Commission believes that waiving the 30-day operative delay is consistent with the protection of investors and the public interest as the proposal does not raise any new or novel issues. Accordingly, the Commission waives the 30-day operative delay and designates the proposed rule change operative upon filing.
                    <SU>23</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         17 CFR 240.19b-4(f)(6).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         17 CFR 240.19b-4(f)(6)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         For purposes only of waiving the 30-day operative delay, the Commission has considered the proposed rule's impact on efficiency, competition, and capital formation. 
                        <E T="03">See</E>
                         15 U.S.C. 78c(f).
                    </P>
                </FTNT>
                <P>At any time within 60 days of the filing of the proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act. If the Commission takes such action, the Commission shall institute proceedings to determine whether the proposed rule should be approved or 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">http://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-BOX-2026-14 on the subject line.
                </P>
                <HD SOURCE="HD2">Paper Comments</HD>
                <P>• Send paper comments in triplicate to Secretary, Securities and Exchange Commission, 100 F Street NE, Washington, DC 20549-1090.</P>
                <FP>
                    All submissions should refer to File Number SR-BOX-2026-14. This file number should be included on the subject line if email is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's internet website (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ). Copies of such filing will be available for inspection and copying at the principal office of the Exchange. All comments received will be posted without change. 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-BOX-2026-14 and should be submitted on or before July 27, 2026.
                </FP>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>24</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>24</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-13524 Filed 7-2-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. 36234; File No. 813-00423]</DEPDOC>
                <SUBJECT>Manulife Investment Management Private Markets (US) LLC; Manulife Employee Securities Company 2025, L.P.</SUBJECT>
                <DATE>June 30, 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 application for an order (“Order”) under sections 6(b) and 6(e) of the Investment Company Act of 1940 (the “Act”) granting an exemption from all provisions of the Act, except sections 9, 17, 30, and 36 through 53, and the rules and regulations under the Act (the “Rules and Regulations”). With respect to sections 17(a), (d), (e), (f), (g), and (j) of the Act, sections 30(a), (b), (e), and (h) of the Act and the Rules and Regulations and rule 38a-1 under the Act, Applicants request a limited exemption as set forth in the application.</P>
                <P>
                    <E T="03">Summary of Application:</E>
                     Applicants request an order to exempt certain limited partnerships, limited liability 
                    <PRTPAGE P="41091"/>
                    companies, corporations, business or statutory trusts or other entities (“Funds”) organized primarily for the benefit of eligible employees of Manulife Investment Management Private Markets (US) LLC and its affiliates from certain provisions of the Act. Each Fund, and each series thereof (to the extent such series is an issuer for purposes of the Act), will be an “employees' securities company” within the meaning of section 2(a)(13) of the Act.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Manulife Investment Management Private Markets (US) LLC and Manulife Employee Securities Company 2025, L.P.
                </P>
                <P>
                    <E T="03">Filing Dates:</E>
                     The application was filed on March 14, 2025, and amended on October 3, 2025, April 16, 2026, and May 22, 2026.
                </P>
                <P>
                    <E T="03">Hearing or Notification of Hearing:</E>
                     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 Applicants with a copy of the request by email, if an email address is listed for Applicants below, or personally or by mail, if a physical address is listed for Applicants 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 27, 2026, and should be accompanied by proof of service on 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.
                </P>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The Commission: 
                        <E T="03">Secretarys-Office@sec.gov.</E>
                         Applicants: Michael Lebowitz, Manulife Investment Management Private Markets (US) LLC, 
                        <E T="03">mlebowitz@manulife.com;</E>
                         and John Hunt, Sullivan &amp; Worcester LLP, 
                        <E T="03">jhunt@sullivanlaw.com.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Erin Loomis Moore, Senior Counsel, or Matthew Cook, 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' third amended and restated application, dated May 22, 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-13569 Filed 7-2-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-0531]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Proposed Collection; Comment Request; Extension: Rule 0-1 Under the Investment Company Act of 1940, Definition of Terms Used in This Part</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 proposed collection of information described below.
                </P>
                <P>
                    The Investment Company Act of 1940 (the “Investment Company Act”) 
                    <SU>1</SU>
                    <FTREF/>
                     establishes a comprehensive framework for regulating the organization and operation of investment companies (“funds”). A principal objective of the Investment Company Act is to protect fund investors by addressing the conflicts of interest that exist between funds and their investment advisers and other affiliated persons. The Investment Company Act places significant responsibility on the fund board of directors in overseeing the operations of the fund and policing the relevant conflicts of interest.
                    <SU>2</SU>
                    <FTREF/>
                     Rule 0-1 (17 CFR 270.0-1), as amended, provides definitions for the terms used by the Commission in the rules and regulations it has adopted pursuant to the Investment Company Act. The rule also contains a number of rules of construction for terms that are defined either in the Investment Company Act itself or elsewhere in the Commission's rules and regulations. Finally, rule 0-1 defines terms that serve as conditions to the availability of certain of the Commission's exemptive rules. More specifically, the term “independent legal counsel,” as defined in paragraph (a)(6) of rule 0-1, sets out conditions that funds must meet in order to rely on any of ten exemptive rules (“exemptive rules”) under the Investment Company Act.
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 80a 
                        <E T="03">et seq.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         For example, fund directors must approve investment advisory and distribution contracts. See 15 U.S.C. 80a-15(a), (b), and (c).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         See 17 CFR 270.0-1(a)(7). The relevant exemptive rules are: rule 10f-3 (17 CFR 270.10f-3), rule 12b-1 (17 CFR 270.12b-1), rule 15a-4(b)(2) (17 CFR 270.15a-4(b)(2)), rule 17a-7 (17 CFR 270.17a-7), rule 17a-8 (17 CFR 270.17a-8), rule 17d-1(d)(7) (17 CFR 270.17d-1(d)(7)), rule 17e-1(c) (17 CFR 270.17e-1(c)), rule 17g-1 (17 CFR 270.17g-1), rule 18f-3 (17 CFR 270.18f-3), and rule 23c-3 (17 CFR 270.23c-3).
                    </P>
                </FTNT>
                <P>
                    If the board's counsel has represented the fund's investment adviser, principal underwriter, administrator (collectively, “management organizations”) or their “control persons” 
                    <SU>4</SU>
                    <FTREF/>
                     during the past two years, rule 0-1 requires that the board's independent directors make a determination about the adequacy of the counsel's independence. A majority of the board's independent directors are required to reasonably determine, in the exercise of their judgment, that the counsel's prior or current representation of the management organizations or their control persons was sufficiently limited to conclude that it is unlikely to adversely affect the counsel's professional judgment and legal representation.
                    <SU>5</SU>
                    <FTREF/>
                     Rule 0-1 also requires that a record for the basis of this determination is made in the minutes of the directors' meeting. In addition, the independent directors must have obtained an undertaking from the counsel to provide them with the information necessary to make their determination and to update promptly that information when the person begins to represent a management organization or control person, or when he or she materially increases his or her representation.
                    <SU>6</SU>
                    <FTREF/>
                     Generally, the independent directors must re-evaluate their determination no less frequently than annually.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         A “control person” is any person—other than a fund—directly or indirectly controlling, controlled by, or under common control, with any of the fund's management organizations. See 17 CFR 270.01(a)(6)(iv)(B).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         17 CFR 270.0-1(a)(6)(i)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         17 CFR 270.0-1(a)(6)(i)(B).
                    </P>
                </FTNT>
                <P>
                    Under rule 0-1, if a majority of a fund's independent directors makes a determination that the counsel's representation of fund management organizations (or any of their control persons) is or was so limited that it will 
                    <PRTPAGE P="41092"/>
                    not adversely affect the counsel's ability to provide impartial advice to the independent directors, the basis for that determination must be recorded in the board's meeting minutes. The records maintained under the rule are not submitted to the Commission, but may be reviewed by the Commission staff upon request to ensure compliance with the rule. Compliance with rule 0-1 is required to obtain or retain benefits.
                </P>
                <P>We estimate that approximately 920 funds would need to make the required determination in order for their counsel to meet the definition of independent legal counsel under rule 0-1. Based on conversations with fund representatives and the Commission's experience with the use of rule 0-1, we estimate that the recordkeeping burden of compliance with rule 0-1 is approximately 1 hour per respondent. This time is spent, for example, preparing the materials and minutes. Accordingly, we calculate the total estimated annual internal burden of complying with rule 0-1 to be approximately 920 hours. The total annual external cost is estimated to be $0.</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>Written comments are invited on: (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 4, 2026.
                </P>
                <SIG>
                    <DATED> Dated: June 30, 2026.</DATED>
                    <NAME>Sherry R. Haywood,</NAME>
                    <TITLE>Assistant Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13495 Filed 7-2-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-105820; File No. SR-TXSE-2026-009]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; Texas Stock Exchange LLC; Notice of Filing of a Proposed Rule Change To Amend a Continued Listing Standard Relating to Beneficial Holders Applicable to ETF Shares Listed on the Exchange Under Rule 17.104(b)(2)(B)</SUBJECT>
                <DATE>June 30, 2026.</DATE>
                <P>
                    Pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (the “Act”),
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     notice is hereby given that on June 16, 2026, Texas Stock Exchange LLC (the “Exchange” or “TXSE”) filed with the Securities and Exchange Commission (“Commission”) the proposed rule change as described in Items I, II, and III below, which Items have been prepared by the Exchange. The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>
                <P>The Exchange filed a proposal to amend Rule 17.104 related to the continued listing requirements on the Exchange for Exchange Traded Fund Shares (“ETF Shares”), as further described below.</P>
                <P>The text of the proposed rule change is provided in Exhibit 5.</P>
                <P>
                    The text of the proposed rule change is available on the Commission's website (
                    <E T="03">https://www.sec.gov/rules/sro.shtml</E>
                    ) at the Exchange's website (
                    <E T="03">https://txse.com/rule-filings</E>
                    ), and at the principal office of the Exchange.
                </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 parts 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 change to Rule 17.104(b)(2)(B) (the “Beneficial Holders Rule”) in order to amend the continued listing standard applicable to ETF Shares 
                    <SU>3</SU>
                    <FTREF/>
                     listed on the Exchange.
                    <SU>4</SU>
                    <FTREF/>
                     Currently, the Exchange's continued listing standard for ETF Shares under the Beneficial Holders Rule requires that, following the initial 12-month period after commencement of trading on the Exchange, the Exchange shall consider the suspension of trading in and will commence delisting proceedings under Rule 16.500 for a series of ETF Shares for which there are fewer than 50 Beneficial Holders.
                    <SU>5</SU>
                    <FTREF/>
                     The Exchange is proposing to eliminate the Beneficial Holders Rule because it believes that the rule does not advance any investment protection objective specific to ETFs, produces arbitrary and negative outcomes for investors and for products that are otherwise operating normally, and that the competitive market for ETF Shares efficiently incentivizes stagnant and unprofitable funds to wind down. The Exchange is also proposing to renumber Rule 17.104(b)(2) in order to reflect the deletion of Rule 17.104(b)(2)(B).
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         The term “ETF Shares” means shares of stock issued by an Exchange-Traded Fund. 
                        <E T="03">See</E>
                         Exchange Rule 17.104(a)(1)(B). The term “Exchange-Traded Fund” has the same meaning as the term “exchange-traded fund” as defined in Rule 6c-11 under the Investment Act of 1940. See Exchange Rule 17.104(a)(1)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                          The Exchange notes that its Rules related to the listing and trading of other product types (that is, products listed pursuant to Chapter 17 that are not ETF Shares as defined above) have similar requirements related to Beneficial Holders which the Exchange is not proposing to change at this time. Specifically, the Exchange is only proposing to amend the Beneficial Holders Rules as it pertains to ETF Shares because such product type represents the vast majority of products listed on U.S. exchanges. The Exchange may consider proposing to amend the Beneficial Holders standards for other product types in a future proposal.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                          As it relates to this filing, “Beneficial Holders” shall mean beneficial holders and, where applicable in a particular continued listing standard, record holders.
                    </P>
                </FTNT>
                <P>
                    Minimum shareholder requirements have applied to listed operating companies long before ETFs were listed in the United States and for such securities operate as a safeguard against manipulation and liquidity concerns related to a small and concentrated float. In that context, such a requirement makes sense: the supply of shares is relatively fixed and a security with limited distribution is more easily subject to manipulation. ETFs, however, 
                    <PRTPAGE P="41093"/>
                    have structural features that mitigate those risks.
                </P>
                <P>
                    The defining feature of ETFs is the creation and redemption mechanism. Authorized participants can create new shares by delivering cash or other will assets to the trust or redeem existing shares in exchange for cash or other assets. This mechanism ensures that an ETF generally trades in line with the value of its underlying holdings (“NAV”) by creating an economic incentive for market participants to create shares and sell them at the market when the market price of an ETF is trading above NAV and to buy shares on the market and redeem them when the ETF is trading below NAV. The Commission has long recognized this feature as distinguishing ETFs from other product classes and it justifies the distinct regulatory framework that applies to ETF Shares under Rule 6c-11 (the “ETF Rule”).
                    <SU>6</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         Investment Company Act Release No. 33646 (September 25, 2019), 84 FR 57162 (October 24, 2019).
                    </P>
                </FTNT>
                <P>Because of the economic incentives for market participants to keep the price of an ETF in line with its NAV through the arbitrage process (rather than price formation strictly through trading behavior of existing holders), the number of beneficial holders bears little relationship to how well an ETF tracks its NAV, its susceptibility to manipulation, or whether a fair and orderly market in the ETF can be maintained. An ETF with a small beneficial holder base and an ETF with a larger one are both generally held in line with their NAV by authorized participants under the same arbitrage incentives. The investor protection and fair and orderly markets rationales that historically supported beneficial holder requirements for operating company stock does not translate to a product class whose price is set by reference to a derivative value rather than by the supply and demand dynamics of a more fixed float.</P>
                <P>
                    The structure of the rule itself reflects the lack of clarity around exactly how it protects investors and helps maintain fair and orderly markets. The Beneficial Holders Rule does not apply to newly listed ETFs during the first 12 months following listing. The Beneficial Holders Rule and equivalent rules at other exchanges generally provide that an ETF has an additional 180 days to comply with the 50 beneficial holders requirement after receiving a deficiency notification. Under recently approved amendments to the equivalent rule on Cboe BZX Exchange, Inc. (“BZX”),
                    <SU>7</SU>
                    <FTREF/>
                     a product that is out of compliance even after that 180-day additional period may now receive an additional 180 days to meet the 50 beneficial holder requirement. Practically, this means that an ETF may remain listed and trading for approximately two years with fewer than 50 beneficial holders. If the beneficial holder threshold were addressing a genuine and time-sensitive risk to investors or to market integrity, neither the initial year nor the additional 360 days would be an acceptable “grace period.” The Exchange believes that the BZX Approval reflects a recognition that sub-threshold beneficial holder counts do not, standing alone, present risks that warrant immediate delisting, and that the proper response is to eliminate the Beneficial Holders Rule rather than to continue calibrating progressively longer cure periods around it.
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         Exchange Act Release No. 104970 (March 11, 2026), 91 FR 12650 (March 16, 2026) (Order Granting Approval of a Proposed Rule Change To Amend Exchange Rule 14.12) (the “BZX Approval”).
                    </P>
                </FTNT>
                <P>
                    The Exchange also believes that the Beneficial Holders Rule is not necessary to prevent products lacking investor interest from remaining listed indefinitely and becoming “zombie ETFs.” Recent industry data indicates that the average lifespan of an ETF liquidated in 2026 has fallen to approximately one year and nine months, down from approximately three years and six months in 2025 and approximately four years and eight months in 2024.
                    <SU>8</SU>
                    <FTREF/>
                     Additionally, more than 600 ETFs liquidated across 2023 (226 liquidations),
                    <SU>9</SU>
                    <FTREF/>
                     2024 (187 liquidations),
                    <SU>10</SU>
                    <FTREF/>
                     and 2025 (232 liquidations).
                    <SU>11</SU>
                    <FTREF/>
                     This trend reflects ordinary market dynamics. Morningstar data indicates that ETFs typically incur approximately $250,000 in annual fixed costs and require approximately $33 million in assets to reach breakeven, with the result that products failing to attract a viable asset base are routinely liquidated by their issuers.
                    <SU>12</SU>
                    <FTREF/>
                     A product that has fewer than 50 beneficial holders after an extended period is likely under substantial commercial pressure toward voluntary liquidation. The Beneficial Holders Rule adds no clear protections to this existing market dynamic, it adds only an arbitrary regulatory deadline that may force delisting at a moment unrelated to the actual interest of investors in the product.
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See Average ETF Lifespan Collapses With Wall Street Antsy for Scale,</E>
                         Bloomberg by Katie Greifeld (April 2, 2026), available at: 
                        <E T="03">https://www.bloomberg.com/news/articles/2026-04-02/average-etf-lifespan-collapses-with-wall-street-antsy-for-scale.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See 6 ETF Investing Predictions for 2025,</E>
                         Morningstar by Bryan Armour (January 8, 2025), available at: 
                        <E T="03">https://www.morningstar.com/funds/6-etf-investing-predictions-2025.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See Active ETF Launches and Closures: 2025 in Review,</E>
                         Morningstar by Jason Kephart, Bryan Armour, and Stephen Welch (February 13, 2026), available at: 
                        <E T="03">https://www.morningstar.com/business/insights/blog/active-etf-launches-and-liquidations-2025.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    The Exchange further notes that the Beneficial Holders Rule can produce outcomes that are contrary to investor protection. As the Commission acknowledged in the BZX Approval, the requirement can force delisting of products that are making demonstrable progress toward compliance and can produce reductions in beneficial holders across an entire series of related products as a result of distress in a single tranche, including in tranches that are themselves in full compliance with all other listing standards.
                    <SU>13</SU>
                    <FTREF/>
                     The Commission's approval of an extended cure period in that release reflects a recognition that delisting on the basis of temporary beneficial holder deficiencies can harm investors. The Exchange believes the more direct response to that recognition is to eliminate the threshold rather than to retain a rule that can produce negative outcomes for investors.
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See</E>
                         BZX Approval at 12651.
                    </P>
                </FTNT>
                <P>
                    To the extent that valid concerns exist about manipulation, liquidity, or distribution in ETFs, those concerns are addressed directly and more accurately by other elements of the listing and regulatory framework. Trading surveillance conducted by the Exchange and FINRA addresses manipulation risk on an evidence-based rather than a proxy basis. The creation and redemption mechanism itself operates within a substantial regulatory framework, including the basket-construction and portfolio-transparency requirements of the ETF Rule, the broker-dealer regulation applicable to authorized participants as FINRA and exchange member firms, and the anti-manipulation provisions of the Exchange Act and rules thereunder. These existing protections address the price-integrity concerns that beneficial holder requirements were historically designed to address in the operating company context. The proposed amendment therefore does not leave any genuine risk unaddressed. It removes a vestigial rule that is poorly suited to the product class while leaving in place the structures that provide investor protections and ensure the maintenance of a fair and orderly market.
                    <PRTPAGE P="41094"/>
                </P>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    The Exchange believes that the proposed rule change is consistent with Section 6(b) of the Act,
                    <SU>14</SU>
                    <FTREF/>
                     in general, and furthers the objectives of Section 6(b)(5) of the Act,
                    <SU>15</SU>
                    <FTREF/>
                     in particular, in that it is designed to prevent fraudulent and manipulative acts and practices, to promote just and equitable principles of trade, to remove impediments to and perfect the mechanism of a free and open market and a national market system, and, in general, to protect investors and the public interest.
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         15 U.S.C. 78f(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <P>The Exchange believes that eliminating the Beneficial Holders Rule is consistent with these requirements because the rule does not advance any investor protection objective specific to ETFs. Minimum shareholder requirements have applied to listed operating companies long before ETFs were listed in the United States and, for such securities, operate as a safeguard against manipulation and liquidity concerns related to a small and concentrated float. ETFs, however, have structural features that mitigate those risks. The defining feature of ETFs is the creation and redemption mechanism, which the Commission has long recognized as distinguishing ETFs from other product classes and which justifies the distinct regulatory framework that applies to ETF Shares under the ETF Rule. Because authorized participants have economic incentives to keep the price of an ETF in line with its NAV through the arbitrage process, the number of beneficial holders bears little relationship to how well an ETF tracks its NAV, its susceptibility to manipulation, or whether a fair and orderly market in the ETF can be maintained. An ETF with a small beneficial holder base and an ETF with a larger one are both generally held in line with their NAV by authorized participants under the same arbitrage incentives. The investor protection and fair and orderly markets rationales that historically supported beneficial holder requirements for operating company stock do not translate to a product class whose price is set by reference to a derivative value rather than by the supply and demand dynamics of a more fixed float.</P>
                <P>The Exchange further believes that the structure of the rule itself reflects the lack of clarity around exactly how it protects investors and helps maintain fair and orderly markets. The rule does not apply to newly listed ETFs during the first 12 months following listing, and the Beneficial Holders Rule and equivalent rules at other exchanges generally provide that an ETF has an additional 180 days to comply with the 50 beneficial holders requirement after receiving a deficiency notification. Under recently approved amendments to the equivalent rule on BZX, a product that is out of compliance even after that 180-day additional period may now receive an additional 180 days to meet the 50 beneficial holder requirement. An ETF may therefore remain listed and trading for approximately two years with fewer than 50 beneficial holders. If the beneficial holder threshold were addressing a genuine and time-sensitive risk to investors or to market integrity, neither the initial year nor the additional 360 days would be an acceptable grace period. The Exchange believes that the BZX Approval reflects a recognition that sub-threshold beneficial holder counts do not, standing alone, present risks that warrant immediate delisting, and that the proper response is to eliminate the Beneficial Holders Rule rather than to continue calibrating progressively longer cure periods around it.</P>
                <P>The Exchange also believes that elimination of the Beneficial Holders Rule is consistent with Section 6(b)(5) because the rule is not necessary to prevent products lacking investor interest from remaining listed indefinitely and becoming “zombie ETFs.” Ordinary market dynamics already perform that function. More than 600 ETFs liquidated across 2023, 2024, and 2025, and the average lifespan of an ETF liquidated in 2026 has fallen to approximately one year and nine months. ETFs incur meaningful annual fixed costs and require a substantial asset base to reach breakeven, with the result that products failing to attract a viable asset base are routinely liquidated by their issuers. A product that has fewer than 50 beneficial holders after an extended period is therefore already under substantial commercial pressure toward voluntary liquidation. The Beneficial Holders Rule adds no clear protections to this existing market dynamic; it adds only an arbitrary regulatory deadline that may force delisting at a moment unrelated to the actual interest of investors in the product.</P>
                <P>The Exchange further believes that elimination of the Beneficial Holders Rule is consistent with the protection of investors because the rule can produce outcomes that are contrary to investor protection. As the Commission acknowledged in the BZX Approval, the requirement can force delisting of products that are making demonstrable progress toward compliance and can produce reductions in beneficial holders across an entire series of related products as a result of distress in a single tranche, including in tranches that are themselves in full compliance with all other listing standards. The Commission's approval of an extended cure period in that release reflects a recognition that delisting on the basis of temporary beneficial holder deficiencies can harm investors. The Exchange believes the more direct response to that recognition is to eliminate the threshold rather than to retain a rule that can produce negative outcomes for investors.</P>
                <P>Finally, the Exchange believes that elimination of the Beneficial Holders Rule is consistent with Section 6(b)(5) because, to the extent that valid concerns exist about manipulation, liquidity, or distribution in ETFs, those concerns are addressed directly and more accurately by other elements of the listing and regulatory framework. Trading surveillance conducted by the Exchange and FINRA addresses manipulation risk on an evidence-based rather than a proxy basis. The creation and redemption mechanism itself operates within a substantial regulatory framework, including the basket-construction and portfolio-transparency requirements of the ETF Rule, the broker-dealer regulation applicable to authorized participants as FINRA and exchange member firms, and the anti-manipulation provisions of the Exchange Act and rules thereunder. These existing protections address the price-integrity concerns that beneficial holder requirements were historically designed to address in the operating company context. The proposed amendment therefore does not leave any genuine risk unaddressed. It removes a vestigial rule that is poorly suited to the product class while leaving in place the structures that provide investor protections and ensure the maintenance of a fair and orderly market.</P>
                <P>Finally, the Exchange believes that the proposed renumbering of Rule 17.104(b)(2) is consistent with the Act because it will make the Exchange's Rules more clear and understandable in light of the proposed deletion of current Rule 17.104(b)(2)(B).</P>
                <P>For these reasons, the Exchange believes that the proposed changes are consistent with the Act.</P>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition</HD>
                <P>
                    The Exchange does not believe that the proposed rule change will impose any burden on competition that is not 
                    <PRTPAGE P="41095"/>
                    necessary or appropriate in furtherance of the purposes of the Act.
                </P>
                <P>The proposed rule change does not impose any burden on intramarket competition because the elimination of the Beneficial Holders Rule will apply uniformly to all series of ETF Shares listed on the Exchange. The proposed rule change removes a continued listing requirement that will place all listed ETF Shares on the same footing with respect to continued listing standards.</P>
                <P>The proposed rule change does not impose any burden on intermarket competition. To the extent it has any effect on intermarket competition, the proposed rule change should promote competition by removing a listing requirement that does not advance any investor protection objective specific to ETFs and that can produce arbitrary outcomes for products that are otherwise operating normally. Other exchanges that list ETF Shares remain free to maintain or modify their own continued listing standards as they see fit, and the Exchange welcomes the opportunity for issuers to choose among listing venues based on the merits of the listing frameworks each exchange provides.</P>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants, or Others</HD>
                <P>The Exchange has neither solicited nor received written comments on the proposed rule change.</P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
                <P>
                    Within 45 days of the date of publication of this notice in the 
                    <E T="04">Federal Register</E>
                     or within such longer period up to 90 days (i) as the Commission may designate if it finds such longer period to be appropriate and publishes its reasons for so finding or (ii) as to which the Exchange consents, the Commission will:
                </P>
                <P>A. by order approve or disapprove such proposed rule change, or</P>
                <P>B. institute proceedings to determine whether the proposed rule change should be disapproved.</P>
                <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
                <P>Interested persons are invited to submit written data, views and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:</P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's internet comment form (
                    <E T="03">https://www.sec.gov/rules/sro.shtml</E>
                    ); or
                </P>
                <P>
                    • Send an email to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include file number SR-TXSE-2026-009 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-TXSE-2026-009. 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-TXSE-2026-009 and should be submitted on or before July 27, 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-13526 Filed 7-2-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-105816; File No. SR-MIAX-2026-26]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; Miami International Securities Exchange, LLC; Notice of Filing and Immediate Effectiveness of a Proposed Rule Change To Amend the By-Laws To Establish the Role of Observers</SUBJECT>
                <DATE>June 30, 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 26, 2026, Miami International Securities Exchange, LLC (“MIAX” or the “Company”),
                    <SU>3</SU>
                    <FTREF/>
                     filed with the Securities and Exchange Commission (“Commission”) a proposed rule change as described in Items I, II, and III below, which Items have been prepared by the Exchange. The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         As used throughout the By-Laws of MIAX, the term “Company” means Miami International Securities Exchange, LLC, a Delaware limited liability company. 
                        <E T="03">See</E>
                         By-Laws of MIAX, Article I, subparagraph (g) (Effective Date of February 10, 2025), 
                        <E T="03">available at</E>
                          
                        <E T="03">https://www.miaxglobal.com/miax_amended_and_restated_by_laws.pdf</E>
                         (referred to herein as the “By-Laws”).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>
                <P>
                    The Exchange proposes to amend the By-Laws to establish the role of Observers (defined and described below) to the Board,
                    <SU>4</SU>
                    <FTREF/>
                     including, among other things, the rights of Observers and the nomination process. The Company also proposes to remove outdated text regarding the Equity Rights Programs (“ERPs”) and initial committees. All changes to the By-Laws proposed herein are referred to as the “By-Law Amendments”. The By-Laws of the Company may be amended by written consent of the LLC Member 
                    <SU>5</SU>
                    <FTREF/>
                     or at any regular or special meeting of the Board of MIAX by a resolution adopted by the Board.
                    <SU>6</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         The term “Board” or “Board of Directors” means the Board of Directors of the Company. 
                        <E T="03">See</E>
                         By-Laws, Article I, subparagraph (c).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         The term “LLC Member” means any person who maintains a direct ownership interest in the Company. The sole LLC Member of the Company is Miami International Holdings, Inc. 
                        <E T="03">See</E>
                         By-Laws, Article I, subparagraph (x).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         By-Laws, Article VIII, Section 8.1.
                    </P>
                </FTNT>
                <P>
                    The text of the proposed rule change is available on the Exchange's website at 
                    <E T="03">https://www.miaxglobal.com/markets/us-options/miax-options/rule-filings</E>
                     and at MIAX's principal office.
                </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.
                    <PRTPAGE P="41096"/>
                </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 Company proposes to amend the By-Laws to establish a new role of Observers 
                    <SU>7</SU>
                    <FTREF/>
                     to the Board, including, among other things, the rights of Observers and the nomination process. The Company believes that individuals who are employed by, or otherwise affiliated with, its Exchange Members 
                    <SU>8</SU>
                    <FTREF/>
                     may provide valuable expertise and knowledge to help the Company carry out its business but may not be able, or willing, to serve as a Board member for one reason or another. Accordingly, the Company believes that the proposed Observer position may provide a suitable alternative for these individuals to serve the Company in a similar manner to observer positions established by the Company's affiliates, MIAX Emerald, LLC (“MIAX Emerald”) and MIAX Sapphire, LLC (“MIAX Sapphire”),
                    <SU>9</SU>
                    <FTREF/>
                     and positions that at least one other exchange has in place. The Company also proposes to remove outdated text regarding the ERPs and initial committees.
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         The Company notes that currently, the term “Observer” is defined as the meaning set forth in Article II, Section 2.2 of the By-Laws. 
                        <E T="03">See</E>
                         By-Laws, Article I, subparagraph (ff). Section 2.2(g) of the By-Laws currently provides for ERP Observers rights. As described herein, the Company proposes to remove all references to “ERPs”, including ERP Observers as the ERPs are now expired. The Company proposes to amend the defined term “Observer” to now describe the new Observer position being created by this filing, which is in line with the MIAX Emerald and MIAX Sapphire Observer positions.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         The term “Exchange Member” means any registered broker or dealer that has been admitted to membership in the national securities exchange operated by the Company. An Exchange Member is not a member of the Company by reason of being an Exchange Member. An Exchange Member will have the status of a “member” of the Exchange as that term is defined in Section 3(a)(3) of the Act. 
                        <E T="03">See</E>
                         By-Laws, Article I, subparagraph (p).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See, generally,</E>
                         MIAX Emerald By-Laws, Article II, Section 2.21 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article II, Section 2.21. 
                        <E T="03">See also</E>
                         Securities Exchange Act Release Nos. 104941 (March 6, 2026), 91 FR 12018 (March 11, 2026) (SR-EMERALD-2026-07) 
                        <E T="03">and</E>
                         104940 (March 6, 2026), 91 FR 12024 (March 11, 2026) (SR-SAPPHIRE-2026-07).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Proposal To Establish the Role of Observers, Rights and Nomination Process</HD>
                <P>
                    First, the Company proposes to amend Article I, Definitions, of the By-Laws to establish the following defined terms for “Observer” and “Observer Threshold”, which will be numbered as proposed subparagraphs (bb) and (cc),
                    <SU>10</SU>
                    <FTREF/>
                     respectively:
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         In connection with the amendment and addition of the proposed defined terms, the Company also proposes to renumber current subparagraphs (o) through (x) to now be (l) through (u), renumber current subparagraphs (z) through (ee) to now be (v) through (aa), and renumber current subparagraphs (hh) through (nn) to now be (dd) through (jj) in Article I of the By-Laws. The purpose of these changes is to provide uniformity and clarity in the By-Laws with the amendment and addition of the newly proposed definitions, all of which are in alphabetical order. Part of this renumbering scheme is due to the Company's proposal to remove ERP terms in Article I, as described in more detail below. In sum, the Company proposes to delete current subparagraphs (l) through (n), subparagraph (y), subparagraph (gg), and subparagraph (oo), all of which refer to terms used in the ERPs.
                    </P>
                </FTNT>
                <P>• “Observer” shall mean a person affiliated with an Exchange Member that is elected by the LLC Member to be an observer to the Board, after having been nominated by the Member Nominating Committee, all as set forth in Section 2.21 below.</P>
                <P>• “Observer Threshold” means the minimum percentage of issued and outstanding shares of common stock or securities exercisable or convertible into shares of common stock of the LLC Member that an Exchange Member (including its affiliates) must own in order to qualify for a person affiliated with such Exchange Member being elected as an Observer to the Board, all as set forth in Section 2.21 below. The Observer Threshold shall be equal to at least one percent (1%) of the issued and outstanding shares of common stock of the LLC Member, taking into account securities that are exercisable or convertible into shares of common stock of the LLC Member.</P>
                <P>The purpose of the proposed changes to amend the By-Laws to add the defined terms for “Observer” and “Observer Threshold” is to provide clarity to Exchange Members regarding the proposed new position of Observer to the Board, which is unrelated to the current ERP Observer position, and the requirements for being able to nominate an individual in such capacity.</P>
                <P>
                    The proposed defined terms are not new or novel. The By-Laws for MIAX Emerald and MIAX Sapphire, the Company's affiliates, provide for identical defined terms, allowing their members to nominate observers to the boards of those exchanges in the same capacity, providing that certain thresholds and other requirements are met.
                    <SU>11</SU>
                    <FTREF/>
                     MEMX LLC (“MEMX”) also provides for the ability of certain of its members to nominate observers to its board of directors in a similar capacity as proposed herein, and the corporate governance documents of MEMX and its parent holding company, MEMX Holdings LLC (“MEMX Holdco”), when read together, provide for similarly defined terms.
                    <SU>12</SU>
                    <FTREF/>
                     In particular, the MEMX LLC Agreement defines “Observer Threshold” as follows:
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article I, subparagraphs (cc)-(dd) 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article I, subparagraphs (cc)-(dd).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">See, generally,</E>
                         Third Amended and Restated Limited Liability Company Agreement of MEMX (dated as of June 5, 2025), 
                        <E T="03">available at</E>
                          
                        <E T="03">https://info.memxtrading.com/wp-content/uploads/2025/08/MEMX-LLC-3rdAR_LLCA.pdf</E>
                         (referred to herein as the “MEMX LLC Agreement”) 
                        <E T="03">and</E>
                         Eighth Amended and Restated Limited Liability Company Agreement of MEMX Holdco (dated as of July 29, 2025), 
                        <E T="03">available at</E>
                          
                        <E T="03">https://info.memxtrading.com/wp-content/uploads/2026/01/MEMX-Holdings-LLC-8th-AR-LLC-Agreement-12.16.25-1.pdf</E>
                         (referred to herein as “MEMX Holdco LLC Agreement”).
                    </P>
                </FTNT>
                <EXTRACT>
                    <P>
                        “Observer Threshold” means the minimum number of units of Holdco Class A Units that an Investor Holdco Member must hold in order to have the right to appoint a Board Observer pursuant to Section 8.18(g) of the Holdco LLC Agreement.
                        <SU>13</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>13</SU>
                             
                            <E T="03">See</E>
                             MEMX LLC Agreement, Section 1.1. The MEMX Holdco LLC Agreement provides the specific requirement for the number of units that must be held in order for MEMX members to be able to appoint an observer to the MEMX exchange board of directors. 
                            <E T="03">See</E>
                             MEMX Holdco LLC Agreement, Section 8.18(g) (providing, in summary, that “each Exchange Board Observer Appointing Member shall have the right, but not the obligation, to appoint one (1) observer to each Exchange Board . . . for so long as such Exchange Board Observer Appointing Member holds an aggregate number of Class A Units, Class C Units and/or Class D Units equal to at least 1,250,000 (subject to adjustment . . .”).
                        </P>
                    </FTNT>
                </EXTRACT>
                <P>
                    The Company notes that MEMX's board observer provisions in its corporate documents automatically grant the right to its exchange members to appoint an observer (barring any disqualifier, such as already having a director position on the same board) so long as the requisite ownership threshold is met.
                    <SU>14</SU>
                    <FTREF/>
                     This is slightly different from the Company's proposal that Exchange Members that satisfy the proposed Observer Threshold (and all other proposed Observer requirements, as described further below), may submit candidate names to the Member Nominating Committee 
                    <SU>15</SU>
                    <FTREF/>
                     for consideration for nomination as an Observer. The Company believes this slight difference is reasonable due to the difference in ownership structures of MEMX and the Company, including its affiliated regulated exchanges (MIAX PEARL, LLC (“MIAX Pearl”); MIAX Emerald; and MIAX Sapphire). MEMX, through its holding company, MEMX Holdco, is a privately owned company while the Company and its affiliated exchanges are wholly-owned subsidiaries of a publicly-traded company, Miami International 
                    <PRTPAGE P="41097"/>
                    Holdings, Inc. (
                    <E T="03">i.e.,</E>
                     the LLC Member). As such, MEMX Holdco is able to restrict ownership in itself and subsidiaries to particular market participants and, therefore, only those particular members of MEMX would be able to meet the requirements to appoint a board observer. In the Company's case, its stock is publicly traded and any Exchange Member may acquire the requisite percentage of securities to be able to nominate a candidate for consideration by the Member Nominating Committee for nomination as an Observer to the Board. The Company believes this proposed part of the nominating process, whereby the Member Nominating Committee reviews candidate submissions for the Observer positions, provides an additional benefit of ensuring only the appropriate individuals are nominated for election to Observer positions.
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">See</E>
                         MEMX LLC Agreement, Section 7.3(c)(ix).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         The term “Member Nominating Committee” means the Member Nominating Committee elected pursuant to these By-Laws. 
                        <E T="03">See</E>
                         By-Laws, Article I, subparagraph (z).
                    </P>
                </FTNT>
                <P>
                    Next, the Company proposes to amend Section 2.9 of the By-Laws to provide for removal and resignation provisions for Observers. In particular, the Company proposes to amend Section 2.9(a) of the By-Laws to provide that any Observer to the Board may be removed or expelled with or without cause by the LLC Member, which is similar to the removal provision applicable to Directors.
                    <SU>16</SU>
                    <FTREF/>
                     The purpose of this proposed provision is to ensure that the LLC Member retains discretion to be able to remove an Observer from such position in a similar manner as Directors of the Company.
                    <SU>17</SU>
                    <FTREF/>
                     In connection with this proposed change to the first sentence of Section 2.9(a), the Company also proposes to amend that sentence to specify that a Director may be removed by the Board of Directors in the manner provided by Article II, Section 2.9(b). The purpose of this proposed provision is to clarify that the provisions of Section 2.9(b) apply solely to the removal process for Directors, not Observers. The Company also proposes to amend Section 2.9(c) of the By-Laws to specify that an Observer, like a Director, may resign at any time either upon notice of resignation to the Chairman of the Board, the President or Secretary. The purpose of this proposed provision is to make it clear that Observers retain the right to be able to resign from such position in the event that they need to do so, while also providing the requisite notice to the Company to effectuate such removal.
                    <SU>18</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         The term “Director” means the persons elected or appointed to the Board of Directors from time to time in accordance with the LLC Agreement and the By-Laws in their capacity as managers of the Company. 
                        <E T="03">See</E>
                         By-Laws, Article I, subparagraph (j).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         MIAX Emerald and MIAX Sapphire provide for the same provisions in their respective by-laws. 
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article II, Section 2.9(a) 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article II, Section 2.9(a). The Company also notes that this removal provision is comparable to the similar provision in the MEMX LLC Agreement concerning the removal of its board observers. 
                        <E T="03">See</E>
                         MEMX LLC Agreement, Section 7.6(a) (providing, in relevant part, that “[a] Board Observer may be removed at any time by [MEMX] Holdco (subject, in each case, to the provisions of [the MEMX LLC] Agreement and the [MEMX] Holdco LLC Agreement regarding the right to nominate and remove [MEMX] Board Observers.”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         MIAX Emerald and MIAX Sapphire provide for the same provisions in their respective by-laws. 
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article II, Section 2.9(c) 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article II, Section 2.9(c). This provision is also comparable to the similar resignation provision in the MEMX LLC Agreement concerning the resignation of board observers. 
                        <E T="03">See</E>
                         MEMX LLC Agreement, Section 7.6(c) (“Any Director or Board Observer may resign at any time from his or her position as such upon notice of resignation to the Chairman of the Board, the CEO or the Secretary.”).
                    </P>
                </FTNT>
                <P>
                    Next, the Company proposes to amend Section 2.10 of the By-Laws to specify that Observers may participate in a meeting of the Board either at the place of the meeting or via the same mode of communication as provided to the members of the Board. The purpose of this change is to provide the right of Observers to be able to attend Board meetings in the same manner and through the same mode of communication as provided to Directors and members of any committee of the Board.
                    <SU>19</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         MIAX Emerald and MIAX Sapphire provide for the same provision in their respective by-laws. 
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article II, Section 2.10 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article II, Section 2.10. The Company also believes that the MEMX LLC Agreement provides for similar provisions. 
                        <E T="03">See</E>
                         MEMX LLC Agreement, Section 7.7(a) (providing, in sum, that meetings of the board may be held either in person or by means of telephone or video conference or other communications device that permits all participants to hear each other) 
                        <E T="03">and</E>
                         MEMX LLC Agreement, Section 7.3(c)(xi) (providing, in sum, that board observers have the right to participate in any discussions taking place at a meeting of the board of directors of MEMX).
                    </P>
                </FTNT>
                <P>
                    Next, the Company proposes to amend Section 2.18 of the By-Laws to include Observers in the list of individuals that the Board may provide for the reasonable compensation (in addition to the Chairman, Directors and members of committees). By including Observers in the first sentence of Section 2.18, the Company also intends that the Board may provide for reimbursement of reasonable expenses incurred by Observers, along with the Chairman, Directors and members of committees, in connection with the business of the Company. The purpose of this change is to provide the Board with discretion to offer reasonable compensation to Observers and reimburse reasonable expenses for Observers in connection with the business of the Company (
                    <E T="03">i.e.,</E>
                     reimbursement of travel expenses for Observers to attend in-person Board meetings).
                    <SU>20</SU>
                    <FTREF/>
                     The Company believes this proposed change is reasonable because the decision of whether to compensate Observers and/or reimburse reasonable expenses of Observers related to the business of the Company will ultimately remain with the Board.
                </P>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         MIAX Emerald and MIAX Sapphire provide for the same provision in their respective by-laws. 
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article II, Section 2.18 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article II, Section 2.18.
                    </P>
                </FTNT>
                <P>
                    Next, the Company proposes to amend Section 2.20 of the By-Laws to amend the provisions regarding conflicts of interest as well as contracts and transactions involving Directors to include Observers in those subparagraphs. In particular, the Company proposes to amend subparagraph (a) of Section 2.20 to provide that an Observer, along with Directors and members of any committee, may not participate in the consideration or decision of any matter relating to a particular Exchange Member, company, or individual if such Observer has a material interest in, or a professional, business, or personal relationship with, that Exchange Member, company, or individual, or if such participation shall create an appearance of impropriety. The Company proposes to further amend subparagraph (a) to provide that in any such case resulting in the appearance of impropriety, an Observer (along with Directors and members of any committee) shall recuse himself or herself or shall be disqualified.
                    <SU>21</SU>
                    <FTREF/>
                     The purpose of this change is to provide that Observers will be subject to the substantively similar conflicts of interest provisions as the Company's Directors and members of any committee.
                    <SU>22</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         The Company notes that the disqualification language pertains to Directors or committee members recusing themselves from any vote taking place; however, Observers will not have voting rights, as such, this last phrase “disqualified” in subparagraph (a) of Section 2.20 will not apply to Observers recusing themselves.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         MIAX Emerald and MIAX Sapphire provide for the same provision in their respective by-laws. 
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article II, Section 2.20(a) 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article II, Section 2.20(a). These changes are also in line with the similar conflicts of interest provisions in the MEMX LLC Agreement. 
                        <E T="03">See</E>
                         MEMX LLC Agreement, Section 7.9(a).
                    </P>
                </FTNT>
                <P>
                    The Company also proposes to amend subparagraph (b) of Section 2.20 of the By-Laws to include Observers in the provisions concerning certain contracts or transactions between the Company and Directors or Officers. In particular, the Company proposes to amend subparagraph (b) to provide that no 
                    <PRTPAGE P="41098"/>
                    contract or transaction between the Company and one or more Observers (along with Directors or officers), or between the Company and any other corporation, partnership, association, or other organization in which one or more Observers (or Directors or officers) are directors or officers, or have a financial interest, shall be void or voidable solely for this reason if: (i) the material facts pertaining to such Observer's (or Director's or officer's) relationship or interest and the contract or transaction are disclosed or are known to the Board or the committee, and the Board or committee in good faith authorizes the contract or transaction by the affirmative vote of a majority of the disinterested Directors, even though the disinterested Directors be less than a quorum; or (ii) the material facts are disclosed or become known to the Board or committee after the contract or transaction is entered into, and the Board or committee in good faith ratifies the contract or transaction by the affirmative vote of a majority of the disinterested Directors, even though the disinterested Directors be less than a quorum. The purpose of this change is to provide that Observers will be subject to the same provisions allowing certain contracts or transactions with the Company in substantially similar circumstances as the Company's Directors, officers and members of any committee.
                    <SU>23</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         MIAX Emerald and MIAX Sapphire provide for the same provision in their respective by-laws. 
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article II, Section 2.20(b) 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article II, Section 2.20(b). This provision is also in line with the similar provisions in the MEMX LLC Agreement. 
                        <E T="03">See</E>
                         MEMX LLC Agreement, Section 7.9(b).
                    </P>
                </FTNT>
                <P>
                    Next, the Company proposes to establish new Section 2.21 of the By-Laws, titled “Observers,” which will contain subparagraphs describing the number, term, nomination and election process, and rights and obligations for Observers. In particular, proposed Section 2.21(a) will provide that there may be up to three (3) Observers to the Board at any time, as determined by the LLC Member in its sole and absolute discretion.
                    <SU>24</SU>
                    <FTREF/>
                     Further, proposed subparagraph (a) will provide that no current Observer may be affiliated 
                    <SU>25</SU>
                    <FTREF/>
                     with another current Observer or current Director of the Board. The purpose of these provisions is to place a limit 
                    <SU>26</SU>
                    <FTREF/>
                     on the number of Observers that may be appointed and specify that no Observer may be affiliated with another Observer or Director.
                    <SU>27</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         At the time of this filing, the Company does not believe that more than three (3) Exchange Members would meet the requirements to be able to nominate a candidate for appointment as an Observer. In the event that there was a significant change whereby more Exchange Members could meet the requirements to be able to nominate a candidate for appointment as an Observer, the Company would consider whether additional changes to the By-Laws were needed at that time. If the Company decides that more than three (3) Observers are needed, it will file another 19b-4 Rule Filing with the Securities and Exchange Commission (“Commission”) to amend the By-Laws. MIAX Emerald and MIAX Sapphire provide for the same provision in their respective by-laws. 
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article II, Section 2.21(a) 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article II, Section 2.21(a).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         An “affiliate” of, or person “affiliated” with a specific person, is a person that directly, or indirectly through one or more intermediaries, controls or is controlled by, or is under common control with, the person specified. 
                        <E T="03">See</E>
                         By-Laws, Article I, subparagraph (b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         The Company does not believe that this limit will impede any Exchange Member from being able to appoint an Observer for those Exchange Members that meet the Observer Threshold and other requirements to be able to nominate a candidate to the Member Nominating Committee for nomination as an Observer. Certain Exchange Members already have an individual serving in a Director capacity on the Board, thereby eliminating their ability to also have an Observer to the Board pursuant to proposed Section 2.21(a) of the By-Laws. Further, the Company's affiliated exchanges (MIAX Pearl, MIAX Emerald, and MIAX Sapphire) plan to (or already have) filed with the Commission to amend their by-laws to provide for the same Observer provisions as proposed herein. 
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article II, Section 2.21(a) 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article II, Section 2.21(a). As such, the Company's Exchange Members who are also members of one or more of the Company's affiliated exchanges will have the opportunity to nominate a candidate to be considered for the Board Observer position by the Member Nominating Committees of those exchanges. At the time of this filing, the Company and all of its affiliated exchanges hold their board meetings at the same time, effectively allowing Board Observers for each affiliated exchange to be present at one time.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         MIAX Emerald and MIAX Sapphire provide for the same provision in their respective by-laws. 
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article II, Section 2.21(a) 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article II, Section 2.21(a). This is also in line with the similar provision in the MEMX LLC Agreement which does not permit an exchange member to have individuals holding a director position and observer position at the same time. 
                        <E T="03">See also</E>
                         MEMX LLC Agreement, Section 7.3(c)(x) (“When a Nominating Investor Holdco Member reaches its turn in the Investor Director Nomination Rotation and its Investor Director nominee is elected to the Board . . . and is seated as a Director, its Board Observer (if any) shall be deemed automatically removed from his or her position . . . and, for as long as such Nominating Investor Holdco Member's Investor Director nominee is serving as an Investor Director, such Nominating Investor Holdco Member shall have no right to have a Board Observer.”).
                    </P>
                </FTNT>
                <P>Proposed subparagraph (b) of Section 2.21 of the By-Laws will describe the terms for Observers. In particular, proposed subparagraph (b) will provide that term of office for each Observer shall be three (3) years from the date of their election. An Observer may serve for any number of terms, consecutive or otherwise. Observers shall be divided into up to three (3) classes, designated Class I, Class II, and Class III. Observers shall serve staggered three-year terms, with the term of one class expiring each year. In order to commence such staggered three-year terms, Observers in Class I shall serve until the second annual election of the Board of Directors, Observers in Class II shall initially serve until the third annual election of the Board of Directors, and Observers in Class III shall initially serve until the fourth annual election of the Board of Directors. Commencing with the second annual election of the Board of Directors, the term for each class of Observers elected at such time shall be three years from the date of their election. Notwithstanding the foregoing, in the case of any new Observer as contemplated by (proposed) Article II, Section 2.21(a), such Observer shall be added to a class, as determined by the Board at the time of such Observer's initial election or appointment, and shall have an initial term expiring at the same time as the term of the class to which such Observer has been added. The Exchange Member affiliated with an Observer must continue to satisfy the Observer Threshold for the duration of the Observer's term. If the Exchange Member affiliated with an Observer fails to meet the Observer Threshold at any time during the duration of the Observer's term, the Observer's term shall immediately terminate at such time. The Exchange Member affiliated with an Observer has an ongoing obligation to immediately notify the Company if such Exchange Member no longer meets the Observer Threshold.</P>
                <P>
                    The proposed term lengths and classes for Observers are based on the similar term provisions for the Company's Directors, which are also divided into three classes with staggered terms.
                    <SU>28</SU>
                    <FTREF/>
                     The purpose of this provision is to provide Observers with the same term length as Directors and avoid the Company having to go through lengthy nomination processes each year in the event there are several Observers. The requirement that the Exchange Member affiliated with an Observer must maintain the ownership requirement set forth in the Observer Threshold is to ensure that Exchange Members who meet such threshold continue to do so throughout the entire term of the Observer.
                    <SU>29</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         
                        <E T="03">See</E>
                         By-Laws, Article II, Section 2.3(b). MIAX Emerald and MIAX Sapphire provide for the same provision in their respective by-laws. 
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article II, Section 2.21(b) 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article II, Section 2.21(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         MIAX Emerald and MIAX Sapphire provide for the same provision in their respective by-laws. See MIAX Emerald By-Laws, Article II, Section 2.21(b) 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article II, Section 2.21(b). This holding requirement is also in line with the similar provision in the MEMX LLC Agreement. 
                        <E T="03">See</E>
                         MEMX LLC Agreement, Section 
                        <PRTPAGE/>
                        7.3(d)(vi) (“An individual Board Observer position shall be immediately terminated following a Transfer of Holdco Units by an Investor Holdco Member which, after giving effect to such Transfer, results in such Investor Holdco Member holding a number of Holdco Class A Units that is less than the Observer Threshold . . .”).
                    </P>
                </FTNT>
                <PRTPAGE P="41099"/>
                <P>
                    Proposed subparagraph (c) of Section 2.21 will describe the nomination and election process for Observers. In particular, proposed subparagraph (c) will provide that an Exchange Member that meets the requirements for the Observer Threshold and as specified in Section 2.21 may submit candidate names to the Member Nominating Committee for consideration for nomination as an Observer. The Member Nominating Committee shall consult with the Nominating Committee 
                    <SU>30</SU>
                    <FTREF/>
                     and the Chairman and Chief Executive Officer for the purpose of nominating candidates for election as an Observer to the Board at the annual meeting of the LLC Member. The Nominating Committee shall nominate only those persons whose names have been submitted by the Member Nominating Committee. The LLC Member shall elect the persons nominated by the Nominating Committee to be Observers to the Board at the annual meeting of the LLC Member. The purpose of conducting the nomination and election process for Observers in the manner described above is to keep this process in line with the process used to nominate and elect Member Representative Directors.
                    <SU>31</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         The term “Nominating Committee” means the Nominating Committee elected pursuant to the By-Laws. 
                        <E T="03">See</E>
                         By-Laws, Article I, subparagraph (cc).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         
                        <E T="03">See</E>
                         By-Laws, Article II, Section 2.4(b). MIAX Emerald and MIAX Sapphire provide for the same provision in their respective by-laws. 
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article II, Section 2.21(c) 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article II, Section 2.21(c). The Company notes that the process for nominating and electing Observers does not include the petition process for the Member Representative Director elections, as described in subparagraphs (c)-(f) of Section 2.4 of the By-Laws. The Company believes the petition process is not needed for Observers as Observers have no voting rights, the pool of candidates is much smaller for Observers as compared to Member Representative Directors, and Exchange Members that are members of the Company's affiliated exchanges and meet the requirements to be able to nominate a candidate as an Observer, may submit candidate names to the Member Nominating Committees of the Company's affiliated exchanges for consideration for nomination as an Observer.
                    </P>
                </FTNT>
                <P>
                    Proposed subparagraph (d) to Section 2.21 of the By-Laws would describe the rights and obligations of Observers. In particular, subparagraph (d) will provide that the Company shall invite the Observers to attend all meetings of its Board of Directors in a non-voting observer capacity, and, in this respect, shall give Observers copies of all notices, minutes, consents, and other materials that it provides to Directors, at the same time and in the same manner as provided to such Directors; provided, however, that such Observers shall agree in writing to hold in confidence and trust and to act in a fiduciary manner with respect to all information so provided; and provided further, that the Company reserves the right to withhold any information and to exclude any such Observers from any meeting or portion thereof if access to such information or attendance at such meeting could adversely affect the attorney-client privilege between the Company and its counsel or result in disclosure of trade secrets or a conflict of interest.
                    <SU>32</SU>
                    <FTREF/>
                     The purpose of this provision is to clarify the rights of Observers and limitations on their capacity to attend Board meetings and receive Board materials.
                    <SU>33</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         The Company notes that proposed Section 2.21(d) does not override the confidentiality provisions related to the Company's self-regulatory function that are described in Section 10.4 of the By-Laws.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         MIAX Emerald and MIAX Sapphire provide for the same provision in their respective by-laws. 
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article II, Section 2.21(d) 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article II, Section 2.21(d). This is also in line with the similar provision in the MEMX LLC Agreement describing the rights, obligations and limitations for its board observers. 
                        <E T="03">See</E>
                         MEMX LLC Agreement, Section 7.3(c)(xi).
                    </P>
                </FTNT>
                <P>
                    Next, the Company proposes to amend Section 3.1(a) of the By-Laws to include Observers in the list of individuals that are to be elected at the annual meeting of the LLC Member, with such time and place of the annual meeting to be determined by the Board. The purpose of this change is to provide specific details concerning the time and place for Observer candidates to be elected to such position. The Company believes this to be reasonable as it would allow Observers to be elected at the same annual meeting as Directors and committee members, as described in proposed Section 3.1(a) of the By-Laws.
                    <SU>34</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         MIAX Emerald and MIAX Sapphire provide for the same provision in their respective by-laws. 
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article III, Section 3.1 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article III, Section 3.1.
                    </P>
                </FTNT>
                <P>
                    The Company also proposes to amend Section 5.3 of the By-Laws to add a sentence regarding the Member Nominating Committee's role in connection with the nomination of Observers. As described above, proposed Section 2.21(c) will provide, among other things, that the Member Nominating Committee shall consult with the Nominating Committee and the Chairman and Chief Executive Officer for the purpose of nominating candidates for election as an Observer to the Board at the annual meeting of the LLC Member. The Company proposes to amend Section 5.3 to add that same sentence since this section also discusses the Member Nominating Committee's role in nominating candidates for certain positions on the Board.
                    <SU>35</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         MIAX Emerald and MIAX Sapphire provide for the same provision in their respective by-laws. 
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article V, Section 5.3 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article V, Section 5.3.
                    </P>
                </FTNT>
                <P>
                    The Company proposes to amend Section 10.3 of the By-Laws to remove Observers from the last sentence of Section 10.3. Currently, it provides that “[i]n no event shall members of the Board of Directors of Miami International Holdings, Inc. who are not also members of the Board, Observers, or any officers, staff, counsel or advisors of Miami International Holdings, Inc. who are not also officers, staff, counsel or advisors of the Company (or any committees of the Company), be allowed to participate in any meetings of the Board (or any committee of the Company) pertaining to the self-regulatory function of the Company (including disciplinary matters).” The Exchange notes that currently there are no observers to the board of Miami International Holdings, Inc. The purpose of the proposed change is to align the Company's By-Laws with the By-Laws of its affiliated regulated exchanges (MIAX Emerald and MIAX Sapphire).
                    <SU>36</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>36</SU>
                         
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article X, Section 10.3 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article X, Section 10.3.
                    </P>
                </FTNT>
                <P>
                    Finally, the Exchange proposes to amend Section 10.4 of the By-Laws to remove Observers from the list of individuals who may have access to the books and records of the Company that contains confidential information pertaining to the self-regulatory function of the Company. The purpose of the proposed change is to align the Company's By-Laws with the By-Laws of its affiliated regulated exchanges (MIAX Emerald and MIAX Sapphire).
                    <SU>37</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>37</SU>
                         
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article X, Section 10.4 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article X, Section 10.4.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Proposal To Remove References to Initial Committees and ERPs</HD>
                <P>
                    The Company proposes to amend Section 5.1 of the By-Laws to delete outdated references to initial committees. On December 3, 2012, the Commission approved the Company's Form 1 application for registration as a national securities exchange under Section 6 of the Exchange Act.
                    <SU>38</SU>
                    <FTREF/>
                     On 
                    <PRTPAGE P="41100"/>
                    December 7, 2012, the Company launched electronic operations as a national securities exchange.
                    <SU>39</SU>
                    <FTREF/>
                     Pursuant to the By-Laws and prior to commencing operations, the LLC Member (
                    <E T="03">i.e.,</E>
                     Miami International Holdings, Inc.) appointed the initial Nominating Committee and Member Nominating Committee. The initial Nominating Committee and Member Nominating Committee served until the second annual meeting of the LLC Member.
                    <SU>40</SU>
                    <FTREF/>
                     Accordingly, the Company proposes to amend Section 5.1 of the By-Laws to remove all references relating to the initial Nominating Committee and Member Nominating Committee as those provisions are outdated.
                </P>
                <FTNT>
                    <P>
                        <SU>38</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 68341 (December 3, 2012), 77 FR 73065 (December 7, 2012) (File No. 10-207) (order approving 
                        <PRTPAGE/>
                        application of the Exchange for registration as a national securities exchange.).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>39</SU>
                         
                        <E T="03">See</E>
                         Press Release, MIAX Options Exchange Successfully Launches (dated December 7, 2012), 
                        <E T="03">available at</E>
                          
                        <E T="03">https://www.miaxglobal.com/sites/default/files/press_release-files/MIAX_Press_Release_12072012A.pdf.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>40</SU>
                         
                        <E T="03">See</E>
                         By-Laws, Article V, Section 5.1.
                    </P>
                </FTNT>
                <P>
                    In addition, the Company proposes to amend various subparagraphs and sections of the By-Laws to delete outdated references to the ERPs. On September 13, 2013, the Company filed a proposed rule change with the Commission to implement an equity rights program (“the Initial ERP”) pursuant to which units representing the right to acquire equity in the Exchange's parent holding company, Miami International Holdings, Inc. (“MIH”) were issued to a participating Member 
                    <SU>41</SU>
                    <FTREF/>
                     in exchange for payment of an initial purchase price or the prepayment of certain transaction fees and the achievement of certain liquidity volume thresholds on the Exchange over a 23-month period commencing September 13, 2013.
                    <SU>42</SU>
                    <FTREF/>
                     On January 6, 2015, the Company filed a proposed rule change with the Commission to implement a second equity rights program (“the Second ERP”) under which units representing the right to acquire equity in the Exchange's parent holding company, MIH, were issued to a participating Member in exchange for payment of an initial purchase price or the prepayment of certain transaction fees and the achievement of certain liquidity volume thresholds on the Exchange over a 29-month period commencing February 1, 2015.
                    <SU>43</SU>
                    <FTREF/>
                     On June 8, 2017, the Company filed a proposed rule change with the Commission to implement a third equity rights program (“the Third ERP”) under which units representing the right to acquire equity in the Exchange's parent holding company, MIH, were issued to a participating Member in exchange for payment of an initial purchase price or the prepayment of certain transaction fees and the achievement of certain liquidity volume thresholds on the Exchange over a 42-month period commencing July 3, 2017.
                    <SU>44</SU>
                    <FTREF/>
                     Each ERP is independent. The Exchange notes that all three ERPs expired and currently there is no ERP Director 
                    <SU>45</SU>
                    <FTREF/>
                     or Observer appointed by an ERP Member serving on the Board.
                    <SU>46</SU>
                    <FTREF/>
                     Accordingly, the Company proposes to amend the By-Laws to remove all references and sections relating to ERPs as those provisions are outdated. In particular, the Company proposes to make the following changes:
                </P>
                <FTNT>
                    <P>
                        <SU>41</SU>
                         The term “Member” means an individual or organization approved to exercise the trading rights associated with a Trading Permit. Members are deemed “members” under the Exchange Act. 
                        <E T="03">See</E>
                         MIAX Options Exchange Rule 100.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>42</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 70498 (September 25, 2013), 78 FR 60348 (October 1, 2013) (SR-MIAX-2013-43) (Notice of Filing and Immediate Effectiveness of a Proposed Rule Change To Implement an Equity Rights Program) (“Initial ERP Filing”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>43</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 74095 (January 20, 2015), 80 FR 4011 (January 26, 2015) (SR-MIAX-2015-02) (Notice of Filing and Immediate Effectiveness of a Proposed Rule Change To Implement an Equity Rights Program) (“Second ERP Filing”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>44</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 80909 (June 12, 2017), 82 FR 27743 (June 16, 2017) (SR-MIAX-2017-28) (Notice of Filing and Immediate Effectiveness of a Proposed Rule Change To Implement an Equity Rights Program) (“Third ERP Filing”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>45</SU>
                         “ERP Director” means an Industry Director who has been nominated by an ERP Member and appointed to the Board of Directors. 
                        <E T="03">See</E>
                         By-Laws, Article I, subparagraph (m).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>46</SU>
                         “ERP Member” means an Exchange Member who acquired Units pursuant to an ERP Agreement sufficient to acquire an ERP Director or an Observer position. 
                        <E T="03">See</E>
                         By-Laws, Article I, subparagraph (n).
                    </P>
                </FTNT>
                <P>• delete subparagraphs (l)-(n), (y), (gg), and (oo) in Article I;</P>
                <P>• remove “and Observer Rights” from the heading of Section 2.2;</P>
                <P>• remove references to ERP Directors from Section 2.2 (b), subparagraphs (i) and (ii);</P>
                <P>• delete subparagraphs (e)-(g) of Section 2.2;</P>
                <P>• remove references to ERP Directors from Section 2.3 (b);</P>
                <P>• delete subparagraphs (c)-(e) of Section 2.3;</P>
                <P>• delete the last sentence related to ERP Directors from Section 2.4 (a); and</P>
                <P>• delete subparagraph (c) of Section 2.8;</P>
                <P>The purpose of these proposed changes is to update the By-Laws to remove outdated references, which will provide clarity to market participants regarding the ERPs, Nominating Committee and Member Nominating Committee throughout the By-Laws.</P>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    The Company believes that the proposed By-Law Amendments are consistent with Section 6(b) of the Exchange Act,
                    <SU>47</SU>
                    <FTREF/>
                     in general, and furthers the objectives of Section 6(b)(1) 
                    <SU>48</SU>
                    <FTREF/>
                     in particular, in that it enables the Company to be so organized as to have the capacity to be able to carry out the purposes of the Exchange Act and to comply, and to enforce compliance by its Exchange Members and persons associated with its Exchange Members, with the provisions of the Exchange Act, the rules and regulations thereunder, and the rules of the Company. The Company also believes that the proposed By-Law Amendments are consistent with Section 6(b)(5) of the Exchange Act,
                    <SU>49</SU>
                    <FTREF/>
                     in that they are designed to prevent fraudulent and manipulative acts and practices, promote just and equitable principles of trade, foster cooperation and coordination with persons engaged in facilitating transactions in securities, remove impediments to and perfect the mechanism of a free and open market and a national market system and, in general, protect investors and the public interest.
                </P>
                <FTNT>
                    <P>
                        <SU>47</SU>
                         15 U.S.C. 78f(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>48</SU>
                         15 U.S.C. 78f(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>49</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Proposal To Establish the Role of Observers, Rights and Nomination Process</HD>
                <P>
                    The Company believes its proposal to amend the By-Laws to establish the role of Observers to the Board is consistent with the Act as this may facilitate additional participation by individuals affiliated with Exchange Members who have the expertise and knowledge in securities markets to help the Board in carrying out the Company's business. Although Observers will not have the right to vote on Company matters at Board meetings, they will be able to attend, review Board materials and participate in Board meetings, which may provide additional view points for relevant issues concerning the business of the Company that may impact other Exchange Members. Thus, the Company does not believe the creation of the Observer position to the Board will have any impact on the Company's ability to be organized as to have the capacity to carry out the purposes of the Act and to comply with the provisions of the Act, the rules and regulations thereunder, and the rules of the Company, which promotes just and equitable principles of trade and continues to protect investors and the public interest. Further, the Company believes the 
                    <PRTPAGE P="41101"/>
                    proposed changes to the By-Laws are consistent with, and will not interfere with, the self-regulatory obligations of the Company.
                </P>
                <P>The Company believes the proposed Observer provisions in the amended By-Laws are consistent with the Act because the Observer position will provide a means for individuals who are employed by, or otherwise affiliated with, an Exchange Member but may not be able, or willing, to serve as a Board member for one reason or another, to now be able to serve the Company in an advisory role and provide such valuable expertise and knowledge to help the Company carry out its business.</P>
                <P>
                    The Company believes the proposed changes to the By-Laws pertaining to Observers enables the Company to be so organized as to have the capacity to be able to carry out the purposes of the Exchange Act because all of the changes are based on similar provisions already in place at the Company for its Directors (or committee members) or are substantively similar to provisions in place at a competing exchange that provides for board observers. The addition of the proposed defined terms for “Observer” and “Observer Threshold” will provide clarity to Exchange Members regarding the Observer position and are identical to the same terms for the observer positions for Company's affiliates, MIAX Emerald and MIAX Sapphire.
                    <SU>50</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>50</SU>
                         
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article I 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article I.
                    </P>
                </FTNT>
                <P>
                    The proposed terms are also similar to the corresponding terms in the MEMX LLC Agreement and MEMX Holdco LLC Agreement.
                    <SU>51</SU>
                    <FTREF/>
                     As noted above, the Company believes the slight difference between its proposal and MEMX's corporate documents, which automatically grant the right to its exchange members to appoint an observer (assuming the threshold and other requirements are met), is reasonable due to the difference in ownership structures. The Company's proposal provides that Exchange Members that meet the Observer Threshold and requirements of proposed Section 2.21, may nominate a candidate to the Member Nominating Committee for consideration as an Observer. The Company believes that this nomination structure enables the Company to be so organized as to have the capacity to be able to carry out the purposes of the Exchange Act by not granting Exchange Members the automatic right to appoint Observers; rather, those candidates must go through a standard nomination and election process with the Member Nominating Committee consulting with the Nominating Committee and the Chairman and Chief Executive Officer.
                </P>
                <FTNT>
                    <P>
                        <SU>51</SU>
                         
                        <E T="03">See supra</E>
                         note 12.
                    </P>
                </FTNT>
                <P>
                    The following proposed Observer provisions are all substantively similar to provisions already in the By-Laws for Directors (or committee members) and identical to the provisions in the MIAX Emerald and MIAX Sapphire By-Laws, and in place at MEMX and, therefore, will enable the Company to continue to be so organized as to have the capacity to be able to carry out the purposes of the Exchange Act: removal and resignation of Observers; 
                    <SU>52</SU>
                    <FTREF/>
                     participation by Observers at Board meetings; 
                    <SU>53</SU>
                    <FTREF/>
                     the ability of the Board to provide for reasonable compensation and reimbursement of expenses for Observers; 
                    <SU>54</SU>
                    <FTREF/>
                     conflicts of interest related to Observers; 
                    <SU>55</SU>
                    <FTREF/>
                     contracts and transactions with the Company that may involve Observers; 
                    <SU>56</SU>
                    <FTREF/>
                     the requirement that Observers not be affiliated with any other Director or Observer; 
                    <SU>57</SU>
                    <FTREF/>
                     term length and staggered classes for Observers; 
                    <SU>58</SU>
                    <FTREF/>
                     the nomination and election process for Observers; 
                    <SU>59</SU>
                    <FTREF/>
                     and certain rights and obligations of Observers.
                    <SU>60</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>52</SU>
                         
                        <E T="03">See supra</E>
                         notes 17 and 18.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>53</SU>
                         
                        <E T="03">See supra</E>
                         notes 19 and 33.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>54</SU>
                         
                        <E T="03">See</E>
                         By-Laws, Section 2.18.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>55</SU>
                         
                        <E T="03">See supra</E>
                         note 22.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>56</SU>
                         
                        <E T="03">See supra</E>
                         notes 22 and 23.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>57</SU>
                         
                        <E T="03">See supra</E>
                         note 27.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>58</SU>
                         
                        <E T="03">See supra</E>
                         note 28.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>59</SU>
                         
                        <E T="03">See supra</E>
                         note 31.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>60</SU>
                         
                        <E T="03">See supra</E>
                         note 33.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Proposal To Remove References to the Initial Committees and ERPs</HD>
                <P>The Company believes its proposal to amend various subparagraphs and sections of the By-Laws to delete outdated references to the initial committees and ERPs enables the Company to be so organized as to have the capacity to be able to carry out the purposes of the Exchange Act because it will remove outdated text. Pursuant to the By-Laws and prior to commencing operations, the LLC Member appointed the initial Nominating Committee and Member Nominating Committee. The initial Nominating Committee and Member Nominating Committee served until the second annual meeting of the LLC Member. Accordingly, the initial Nominating Committee and Member Nominating Committee served until their specified time expired. The Initial ERP, Second ERP and Third ERP have expired and currently there is no ERP Director or Observer appointed by an ERP Member serving on the Board. The Company further believes these proposed changes remove impediments to and perfects the mechanism of a free and open market by providing greater transparency and clarity in the Company's governing documents. It is in the public interest for the Company's By-Laws to be up-to-date and accurate, which protects investors by providing transparency and clarity, thereby reducing potential confusion.</P>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition</HD>
                <P>The Company does not believe that the proposed By-Law Amendments will impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. The proposed By-Law Amendments relate to the corporate governance of the Company and not to the Company's operations. As such, the proposed By-Law Amendments do not impact competition among the various market participants of the Company or among competing exchanges. This is not intended to address competitive issues and, therefore, imposes no burden on competition. The proposed By-Laws Amendments are also substantively similar (or identical) to the comparable by-law provisions already in place for MIAX Emerald and MIAX Sapphire.</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>Written comments were neither solicited nor received.</P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
                <P>
                    Because the foregoing proposed rule change does not (i) significantly affect the protection of investors or the public interest; (ii) impose any significant burden on competition; and (iii) become operative for 30 days after the date of the filing, or such shorter time as the Commission may designate, it has become effective pursuant to Section 19(b)(3)(A) of the Act 
                    <SU>61</SU>
                    <FTREF/>
                     and subparagraph (f)(6) of Rule 19b-4 thereunder.
                    <SU>62</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>61</SU>
                         15 U.S.C. 78s(b)(3)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>62</SU>
                         17 CFR 240.19b-4(f)(6). In addition, Rule 19b-4(f)(6)(iii) requires a self-regulatory organization to give the Commission written notice of its intent to file the proposed rule change, along with a brief description and text of the proposed rule change, at least five business days prior to the date of filing of the proposed rule change, or such shorter time as designated by the Commission. The Exchange has satisfied this requirement.
                    </P>
                </FTNT>
                <P>
                    At any time within 60 days of the filing of the proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such 
                    <PRTPAGE P="41102"/>
                    action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act. If the Commission takes such action, the Commission shall institute proceedings under Section 19(b)(2)(B) 
                    <SU>63</SU>
                    <FTREF/>
                     of the Act to determine whether the proposed rule change should be approved or disapproved.
                </P>
                <FTNT>
                    <P>
                        <SU>63</SU>
                         15 U.S.C. 78s(B)(2)(B).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
                <P>Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:</P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's internet comment form (
                    <E T="03">https://www.sec.gov/rules/sro.shtml</E>
                    ). or
                </P>
                <P>
                    • Send an email to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include file number SR-  MIAX-2026-26 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-MIAX-2026-26. 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 also will be available for inspection and copying at the principal office of the Exchange. Do not include personal identifiable information in submissions; you should submit only information that you wish to make available publicly. We may redact in part or withhold entirely from publication submitted material that is obscene or subject to copyright protection. All submissions should refer to file number SR-MIAX-2026-26 and should be submitted on or before July 27, 2026.
                </FP>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>64</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>64</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-13522 Filed 7-2-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. 36235; 812-15924]</DEPDOC>
                <SUBJECT>Blue Tractor ETF Trust, et al.</SUBJECT>
                <DATE>June 30, 2026.</DATE>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Securities and Exchange Commission (“Commission”).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of an application to amend a prior order for exemptive relief.</P>
                </ACT>
                <PREAMHD>
                    <HD SOURCE="HED">Summary of Application:</HD>
                    <P>Applicants request an order (“Amended Order”) that would amend a Prior Order (as defined below) to expand the universe of instruments in which a Fund (as defined below) is permitted to invest.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">Applicants:</HD>
                    <P>Blue Tractor ETF Trust and Blue Tractor Group, LLC.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">Filing Dates:</HD>
                    <P>The application was filed on October 24, 2025, and amended on April 2, 2026 and June 23, 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 by emailing the Commission's Secretary at 
                        <E T="03">Secretarys-Office@sec.gov</E>
                         and serving 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. Hearing requests should be received by the Commission by 5:30 p.m. Eastern time on July 27, 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 Investment Company Act of 1940 (“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/>
                    <P>
                        <E T="03">The Commission:</E>
                         Commission's Secretary, 
                        <E T="03">Secretarys-Office@sec.gov.</E>
                    </P>
                    <P>
                        <E T="03">Applicants:</E>
                         Michael W. Mundt, Esq., Stradley Ronon Stevens &amp; Young, LLP, 
                        <E T="03">MMundt@stradley.com.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Kris Easter Guidroz, Senior Counsel; Thomas Ahmadifar, Branch Chief, or Daniele Marchesani, Assistant Chief Counsel, 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' second amended and restated application, dated June 23, 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. The SEC's EDGAR system may be searched at 
                    <E T="03">https://www.sec.gov/edgar/searchedgar/companysearch 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>
                <HD SOURCE="HD1">I. Introduction</HD>
                <P>
                    1. On March 9, 2021 and then on February 27, 2024 the Commission issued orders to the Applicants under section 6(c) of the Investment Company Act of 1940 granting an exemption from sections 2(a)(32), 5(a)(1), and 22(d) of the Act and rule 22c-1 thereunder, and under sections 6(c) and 17(b) of the Act granting an exemption from sections 17(a)(1) and 17(a)(2) of the Act (respectively, the “Custom Basket Order” and the “Long/Short Order”),
                    <SU>1</SU>
                    <FTREF/>
                     both of which amended an order issued on December 10, 2019 (the “Original Order” 
                    <SU>2</SU>
                    <FTREF/>
                     and, as subsequently amended by the Custom Basket Order and Long/Short Order, the “Prior Order”).
                    <SU>3</SU>
                    <FTREF/>
                     The Prior Order allows Applicants to operate actively-managed exchange-traded 
                    <PRTPAGE P="41103"/>
                    funds (“ETFs”) that are not required to disclose their full portfolio holdings on a daily basis (each, a “Fund”). Rather, pursuant to the Prior Order, on each Business Day 
                    <SU>4</SU>
                    <FTREF/>
                     each Fund publishes a Dynamic SSR Portfolio (a “Portfolio Reference Basket”) designed to closely correlate to the daily performance of the Fund, along with a Guardrail Amount reflecting the maximum amount by which the weightings of specific securities and cash positions in the Portfolio Reference Basket will deviate that day from those specific securities and cash positions in the Fund's actual portfolio.
                    <SU>5</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See</E>
                         Blue Tractor ETF Trust and Blue Tractor Group, LLC, Investment Company Act Release No. 34194 (Feb. 10, 2021) (the “Custom Basket Notice”) and Investment Company Act Release No. 34221 (Mar. 9, 2021) (the “Custom Basket Order”). 
                        <E T="03">See also</E>
                         Blue Tractor ETF Trust, et al., Investment Company Act Release No. 35121 (Jan. 31, 2024) (the “Long/Short Notice”) and Investment Company Act Release No. 35148 (Feb. 27, 2024) (the “Long/Short Order”) (allowing the Funds to engage in short selling but only in Portfolio Instruments).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See</E>
                         Blue Tractor ETF Trust and Blue Tractor Group, LLC, Investment Company Act Release No. 33682 (Nov. 14, 2019) (the “Original Notice”) and Investment Company Act Release No. 33710 (Dec. 10, 2019) (the “Original Order”). The Original Order also granted, under section 12(d)(1)(J) of the Act, an exemption from sections 12(d)(1)(A) and 12(d)(1)(B) of the Act (the “Section 12(d)(1) Relief”). The Section 12(d)(1) Relief expired on January 19, 2022. 
                        <E T="03">See</E>
                         Fund of Funds Arrangements, Investment Company Act Rel. No. 10871 (Oct. 7, 2020), at III.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         Except as specifically noted in the application for an Amended Order, as amended and restated and filed with the Commission on June 23, 2026 (File No. 812-15924), all representations and conditions contained in the amended and restated application for the Original Order (File No. 812-14625) as filed with the Commission on October 23, 2019 (the “Original Application”), as modified by the amended and restated application for the Custom Basket Order (File No. 812-15162) filed with the Commission on January 19, 2021 and the application for the Long/Short Order (File No. 812-15209) (“Long/Short Application”) filed with the Commission on January 30, 2024, remain applicable to the operation of the Funds and will apply to any Funds relying on the Amended Order.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         All capitalized terms not otherwise defined in this notice have the meanings ascribed to them in the Prior Order.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         Original Application at 10.
                    </P>
                </FTNT>
                <P>
                    2. Under the Prior Order, a Fund is permitted to invest only in certain enumerated instruments,
                    <SU>6</SU>
                    <FTREF/>
                     and to engage in short selling of instruments in which the Fund is permitted to hold as long positions.
                    <SU>7</SU>
                    <FTREF/>
                     Applicants now seek to amend the Prior Order to permit a Fund to invest in securities and instruments in addition to Prior Order Investments, including but not limited to fixed income securities, foreign investments that do not trade contemporaneously with Shares, and derivatives (“Amended Order Investments”). As a condition of Applicants' requested amendment, each Fund would comply with additional requirements, including disclosing additional information about its portfolio.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         Original Application at 8.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         Long/Short Application at 3.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">II. The Application</HD>
                <HD SOURCE="HD2">A. Applicants' Proposal</HD>
                <P>
                    3. The Amended Order would give Funds the same investment flexibility to choose its investments as ETFs relying on rule 6c-11 under the Act (“Rule 6c-11 ETFs”) 
                    <SU>8</SU>
                    <FTREF/>
                     subject to the same portfolio holdings disclosure requirements as Rule 6c-11 ETFs with respect to Amended Order Investments. Pursuant to the Amended Order, each Fund's portfolio will be invested in two sleeves. A Fund will invest the first sleeve solely in Prior Order Investments for which the Fund will disclose a Portfolio Reference Basket designed to track closely the daily performance of the sleeve (the “Semi-Transparent Sleeve”). A Fund will invest the second sleeve solely in Amended Order Investments and will publicly disclose all such investments daily in accordance with the requirements of rule 6c-11(c) under the Act (the “Fully-Transparent Sleeve”). Applicants represent that the Funds do not intend to use Amended Order Investments to hedge or otherwise offset exposure to Prior Order Investments. Applicants also represent that any Fund that invests in Amended Order Investments will not engage in short sales or hold short positions and, to the extent a Fund invests in Amended Order Investments that are derivatives, such derivatives will not be used for short exposure.
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         The Funds are not able to operate in reliance on rule 6c-11 and will not be able to do so under the Amended Order, because they do not and will not disclose all of their portfolio holdings daily as required by the rule. See rule 6c-11(c)(1)(i) (requiring an ETF to disclose prominently on its website, publicly available and free of charge, the portfolio holdings that will form the basis for the Fund's calculation of per share NAV).
                    </P>
                </FTNT>
                <P>4. Under the Amended Order, the published Portfolio Reference Basket for a Fund that invests in Amended Order Investments will consist of two distinct portions: (i) a first portion corresponding to the Semi-Transparent Sleeve of the Fund's portfolio, constructed in accordance with the terms and conditions of the Prior Order; and (ii) a second portion corresponding to the Fully-Transparent Sleeve of the Fund's portfolio, disclosing all Amended Order Investments in accordance with the portfolio holdings disclosure requirements of rule 6c-11(c)(1) under the Act. The ratio of the Fully-Transparent Sleeve portion of the Portfolio Reference Basket to the total Portfolio Reference Basket will correspond to the ratio of the Amended Order Investments to the Fund's aggregate portfolio holdings. The ratio of the Semi-Transparent Sleeve portion of the Portfolio Reference Basket to the total Portfolio Reference Basket will correspond to the ratio of all investments other than Amended Order Investments to the Fund's aggregate portfolio holdings. The Guardrail Amount will represent the maximum potential deviation in the weightings of specific securities and cash positions in the Semi-Transparent Sleeve of the Portfolio Reference Basket from the weightings of those specific securities and cash positions in the Semi-Transparent Sleeve of the Fund's actual portfolio as of the beginning of each trading day.</P>
                <P>5. Under the Prior Order, for at least the first three years after a Fund's launch, the Adviser must monitor the Fund's Tracking Error, Premiums/Discounts, and trading spreads and promptly call a Board meeting if any of these surpass Board-approved thresholds (the “Three-Year Requirement”). Under the Amended Order, a Fund will be subject to a new Three-Year Requirement on the date the Fund first acquires Amended Order Investments, to enable the Adviser and Board to evaluate the Fund's arbitrage processes and trading performance.</P>
                <HD SOURCE="HD2">B. Considerations Relating to the Requested Relief</HD>
                <P>6. Applicants represent that, given the Funds will disclose all Amended Order Investments in accordance with rule 6c-11, allowing a Fund to have the requested investment flexibility does not give rise to any new policy concerns and will not cause any negative impacts to the Funds' arbitrage processes, bid-ask spreads, premiums/discounts, or otherwise adversely affect the Funds' operations. Further, Applicants stated that they anticipate a Fund's daily disclosure of a Portfolio Reference Basket that includes all Amended Order Investments in its portfolio in their actual weights, along with periodic disclosure of full portfolio holdings in accordance with the Funds' portfolio holdings disclosure policies, will allow market participants to understand the relationship between the performance of a Fund and its Portfolio Reference Basket and will facilitate the arbitrage process that keeps a Fund's per share market price close to its NAV.</P>
                <P>7. Further, Applicants stated they do not expect a Fund's investments in Amended Order Investments to cause investor confusion because the Fund's prospectus, market materials, and website will describe the semi-transparent nature of the Fund and will explain the differences between the Semi-Transparent Sleeve and the Fully-Transparent Sleeve, including the investment types that may be included in each sleeve.</P>
                <HD SOURCE="HD1">III. Requested Exemptive Relief</HD>
                <P>Applicants believe that the Prior Order continues to meet the relevant standards for relief pursuant to section 6(c) of the Act for an exemption from sections 2(a)(32), 5(a)(1), and 22(d) 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>
                <HD SOURCE="HD1">IV. Applicants' Conditions</HD>
                <P>Applicants agree that any Amended Order of the Commission granting the requested relief will be subject to all of the conditions in the Prior Order and will be subject to new conditions as follows:</P>
                <P>
                    11. To the extent a Fund invests in Amended Order Investments, the Fund will publish a new Portfolio Reference Basket that consists of two distinct portions: (i) a first portion corresponding to the Semi-Transparent Sleeve; and (ii) a second portion corresponding to the Fully-Transparent 
                    <PRTPAGE P="41104"/>
                    Sleeve that fully discloses all Amended Order Investments in a manner consistent with Rule 6c-11(c)(1). The ratio of the Fully-Transparent Sleeve portion of the Portfolio Reference Basket to the total Portfolio Reference Basket will correspond to the ratio of the Amended Order Investments to the ETF's aggregate portfolio holdings. The ratio of the Semi-Transparent portion of the Portfolio Reference Basket to the total Portfolio Reference Basket will correspond to the ratio of all investments other than Amended Order Investments to the ETF's aggregate portfolio holdings.
                </P>
                <P>12. Each Fund that invests in Amended Order Investments will publish prominently on its website, which is publicly available and free of charge, on a daily basis, all Amended Order Investments held in its portfolio as of the end of the prior Business Day in accordance with the requirements of Rule 6c-11(c)(1)(i).</P>
                <SIG>
                    <P>For the Commission, by the Division of Investment Management, pursuant to delegated authority.</P>
                    <NAME>Sherry R. Haywood,</NAME>
                    <TITLE>Assistant Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13493 Filed 7-2-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-105821; File No. SR-NYSEAMER-2026-55]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; NYSE American LLC; Notice of Filing and Immediate Effectiveness of a Proposed Rule Change To Amend the Connectivity Fee Schedule</SUBJECT>
                <DATE>June 30, 2026.</DATE>
                <P>
                    Pursuant to Section 19(b)(1) 
                    <SU>1</SU>
                    <FTREF/>
                     of the Securities Exchange Act of 1934 (“Act”) 
                    <SU>2</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>3</SU>
                    <FTREF/>
                     notice is hereby given that, on June 18, 2026, NYSE American LLC (“NYSE American” or “Exchange”) filed with the Securities and Exchange Commission (“Commission”) the proposed rule change as described in Items I and II below, which Items have been prepared by the self-regulatory organization. The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         15 U.S.C. 78a.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>
                <P>
                    The Exchange proposes to amend the Connectivity Fee Schedule to amend the list of third party data feeds to which Users can connect. The proposed rule change is available on the Exchange's website at 
                    <E T="03">www.nyse.com</E>
                     and at the principal office of the Exchange.
                </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <P>In its filing with the Commission, the self-regulatory organization included statements concerning the purpose of, and basis for, the proposed rule change and discussed any comments it received on the proposed rule change. The text of those statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in sections A, B, and C below, of the most significant parts of such statements.</P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and the Statutory Basis for, the Proposed Rule Change</HD>
                <HD SOURCE="HD3">1. Purpose</HD>
                <P>
                    The Exchange proposes to amend the Connectivity Fee Schedule to amend the list of third party data feeds to which Users 
                    <SU>4</SU>
                    <FTREF/>
                     can connect. Currently, Users are offered connectivity to data feeds from third party markets and other content service providers (“Third Party Data Feeds”) at the Mahwah, New Jersey data center (“MDC”).
                    <SU>5</SU>
                    <FTREF/>
                     The Exchange now proposes to amend the names of the Cboe Global Markets, Inc. Third Party Data Feeds (excluding Cboe Canada) (“Cboe Data Feeds”) and incorporate a new feed from Investors Exchange LLC (“IEX”).
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         For purposes of the Exchange's colocation services, a “User” means any market participant that requests to receive colocation services directly from the Exchange. 
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 76009 (September 29, 2015), 80 FR 60213 (October 5, 2015) (SR-NYSEMKT-2015-67). As specified in the Fee Schedule, a User that incurs colocation fees for a particular colocation service pursuant thereto would not be subject to colocation fees for the same colocation service charged by the New York Stock Exchange LLC, NYSE Arca, Inc., NYSE National, Inc. and NYSE Texas, Inc. (together, the “Affiliate SROs”). Each Affiliate SRO has submitted substantially the same proposed rule change to propose the change described herein.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         Through its Fixed Income and Data Services (“FIDS”) business, Intercontinental Exchange, Inc. (“ICE”) operates the MDC. The Exchange and the Affiliate SROs are indirect subsidiaries of ICE.
                    </P>
                </FTNT>
                <P>The Exchange expects that the proposed rule change would become operative by August 31, 2026. The Exchange will announce the date through a customer notice.</P>
                <HD SOURCE="HD3">Proposed Change to the Cboe Data Feeds</HD>
                <P>
                    Currently, the Cboe Data Feeds are set forth in the list of Third Party Data Feeds by market. However, Users have requested that certain of the Cboe Data Feeds be broken out by asset class instead, so that if a User wanted all of the Cboe equities 
                    <SU>6</SU>
                    <FTREF/>
                     data, Cboe options 
                    <SU>7</SU>
                    <FTREF/>
                     data, or Cboe indices data 
                    <SU>8</SU>
                    <FTREF/>
                     it would not have to sign up for connectivity to more than one Third Party Data Feed.
                    <SU>9</SU>
                    <FTREF/>
                     The Exchange proposes to make the requested change and to indicate the exchanges from which data is included in the Cboe equities (“Cboe U.S. Equites”) and Cboe options (“Cboe Options”) data feeds.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         Cboe U.S. Equities | Cboe (representing the four U.S. equities exchanges that Cboe operates as BZX Equities, BYX Equities, EDGA Equities, and EDGX Equities).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         See Cboe U.S. Options | Trade Equity, Index &amp; ETF Options | Cboe (stating that the four U.S.-listed cash equity options markets that Cboe operates are the Cboe Options Exchange, the Cboe C2 Options Exchange, Cboe BZX Options Exchange, and Cboe EDGX Options Exchange).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         The Cboe indices data is set out in the Cboe Global Indices Feed. See Cboe Global Indices Feed (stating that the Cboe Global Indices Feed has more than 1,900 Index Values available).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         Currently, in order to connect to all of the Cboe U.S. Equity data feeds a User would have to connect to two Third Party Data Feeds, and to connect to all of the Cboe Options data feeds a User would have to connect to three Third Party Data Feeds. In order to connect to the Cboe indices data a User currently would have to connect to one Third Party Data Feed and the proposed change would ensure that remains true.
                    </P>
                </FTNT>
                <P>
                    The Exchange also proposes to change the name of “Cboe CFE Futures” to “Cboe Futures Exchange (CFE)” to mirror the name of Cboe Futures Exchange 
                    <SU>10</SU>
                    <FTREF/>
                     and to reorder the Cboe Data Feeds to maintain alphabetical order.
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See, e.g.,</E>
                         Exchange Act Release No. 104973 (March 11, 2026), 91 FR 12631 (March 16, 2026) (SR-CFE-2026-002) (presenting the name as “Cboe Futures Exchange, LLC,” abbreviated to “CFE”).
                    </P>
                </FTNT>
                <P>
                    Accordingly, the Exchange proposes to make the following changes to the Cboe Data Feeds listed under “Connectivity to Third Party Data Feeds” (proposed additions italicized, proposed deletions in brackets):
                    <PRTPAGE P="41105"/>
                </P>
                <GPOTABLE COLS="2" OPTS="L2,nj,tp0,i1" CDEF="s100,15">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Third party data feed</CHED>
                        <CHED H="1">Monthly recurring connectivity fee per third party data feed</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">[Cboe BZX Exchange (CboeBZX) and Cboe BYX Exchange (CboeBYX)]</ENT>
                        <ENT>[$1,500]</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Cboe Canada</ENT>
                        <ENT>2,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Cboe [CFE] Futures 
                            <E T="03">Exchange (CFE)</E>
                        </ENT>
                        <ENT>1,500</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            <E T="03">Cboe Global Indices Feed</E>
                        </ENT>
                        <ENT>
                            <E T="03">1,500</E>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Cboe 
                            <E T="03">Options</E>
                            [EDGX] Exchange
                            <E T="03">s</E>
                             (
                            <E T="03">Cboe Options Exchange, Cboe C2 Options Exchange, Cboe BZX Options Exchange, and</E>
                             Cboe EDGX
                            <E T="03"> Options Exchange</E>
                            ) [and Cboe EDGA Exchange (CboeEDGA)]
                        </ENT>
                        <ENT>1,500</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Cboe 
                            <E T="03">U.S Equities</E>
                             Exchange
                            <E T="03">s</E>
                             (Cboe 
                            <E T="03">EDGA Equities, Cboe EDGX Equities, Cboe BYX Equities and Cboe BZX Equities</E>
                            ) [and C2 Exchange (C2)]
                        </ENT>
                        <ENT>1,500</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD3">Proposed Change to the IEX Third Party Data Feed</HD>
                <P>
                    IEX has announced that it will launch a new options exchange (“IEX Options”) 
                    <SU>11</SU>
                    <FTREF/>
                     and that it intends to launch IEX Options on October 2, 2026.
                    <SU>12</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See</E>
                         “IEX Announces Planned Launch of Options Exchange End of Q1 2026,” available at 
                        <E T="03">https://www.iex.io/article/iex-announces-planned-launch-of-options-exchange-end-of-q1-2026.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">See</E>
                         “IEX Options Frequently Asked Questions,” question 1, available at 
                        <E T="03">https://cdn.prod.website-files.com/696f8ac812dcabe749e3aa49/69d7ddd79256713d06405c46_IEX%20Options%20FAQs.pdf.</E>
                         The proposed rule change is proposed to become operative before IEX offers IEX Options in order to allow Users time to connect, and test their connection, to IEX Options. The Exchange does not plan to charge for the connection until the IEX Options Third Party Data Feed is available.
                    </P>
                </FTNT>
                <P>So that the Exchange may both offer connectivity to IEX Options and distinguish between IEX Options and the existing IEX equities exchange (“IEX Equities”), it proposes to make the following changes to the list of available Third Party Data Feeds (proposed additions italicized):</P>
                <GPOTABLE COLS="2" OPTS="L2,nj,tp0,i1" CDEF="s100,15">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Third party data feed</CHED>
                        <CHED H="1">Monthly recurring connectivity fee per third party data feed</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">
                            Investors Exchange (IEX) 
                            <E T="03">Equities</E>
                        </ENT>
                        <ENT>$1,300</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            <E T="03">Investors Exchange (IEX) Options</E>
                        </ENT>
                        <ENT>
                            <E T="03">1,300</E>
                        </ENT>
                    </ROW>
                </GPOTABLE>
                <P>The Exchange would provide connectivity to IEX Options as a convenience to Users.</P>
                <P>As with the existing connections to Third Party Data Feeds, including the existing connections to Cboe Data Feeds and to the IEX Equities data feed, the Exchange would receive a connection to the IEX Options data feed (the “Proposed Third Party Data Feed”) from the content service provider at the relevant source. The Exchange would then provide connectivity to that data to Users for a fee. Users would connect to IEX Options over the internet protocol (“IP”) network, a local area network available in the MDC. The Proposed Third Party Data Feed would include trading and other information concerning the securities that are traded on IEX Options.</P>
                <P>As with the existing connections to Third Party Data Feeds, including the existing connection to Cboe Data Feeds and the IEX Equities data feed, in order to connect to a Proposed Third Party Data Feed, a User would enter into a contract with the third party content service provider, pursuant to which it may charge the User for the data feed. The Exchange would receive the Proposed Third Party Data Feed in remote locations and transport it over its fiber optic network to the MDC. After the content service provider and User entered into an agreement and the Exchange received authorization from the content service provider, the Exchange would retransmit the data to the User over the User's port. The Exchange would charge the User for connectivity to the Proposed Third Party Data Feed. A User would only receive, and would only be charged the fee for, connectivity to a Proposed Third Party Data Feed for which it entered into a contract.</P>
                <P>The Exchange has no affiliation with the seller of the Proposed Third Party Data Feed and would have no right to use the feed other than as a redistributor of the data. The Proposed Third Party Data Feed would not provide access or order entry to the Exchange's execution system. The Proposed Third Party Data Feed would not provide access or order entry service to the execution systems of any third party generating the feed. The Exchange would receive the Proposed Third Party Data Feed via arms-length agreements and would have no inherent advantage over any other distributor of such data.</P>
                <HD SOURCE="HD3">Application and Impact of the Proposed Changes</HD>
                <P>The proposed rule change would not apply differently to distinct types or sizes of market participants. Rather, it would apply to all Users equally. As is currently the case, the purchase of any colocation service is completely voluntary and the Connectivity Fee Schedule is applied uniformly to all Users.</P>
                <P>Users have requested that certain of the Cboe Data Feeds be broken out by asset class, instead of by market. The Exchange believes that one current User would benefit from the change. It does not expect to gain customers as a result of breaking out certain of the Cboe Data Feeds by asset class or the other proposed changes to the Cboe Data Feeds.</P>
                <P>Connectivity to the Proposed Third Party Data Feed was requested by Users, but the Exchange believes that it would gain at most a handful of new customers due to the proposed change to the IEX data feeds.</P>
                <HD SOURCE="HD3">Competitive Environment</HD>
                <P>
                    The Exchange operates in a highly competitive market in which other vendors offer colocation services as a means to facilitate the trading and other market activities of those market participants who believe that colocation enhances the efficiency of their operations. The Commission has repeatedly expressed its preference for 
                    <PRTPAGE P="41106"/>
                    competition over regulatory intervention in determining prices, products, and services in the securities markets. Specifically, in Regulation NMS, the Commission highlighted the importance of market forces in determining prices and SRO revenues and, also, recognized that current regulation of the market system “has been remarkably successful in promoting market competition in its broader forms that are most important to investors and listed companies.” 
                    <SU>13</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 51808 (June 9, 2005), 70 FR 37496, 37499 (June 29, 2005).
                    </P>
                </FTNT>
                <P>As explained below, the Exchange's provision of connectivity to the Proposed Third Party Data Feed (“Connectivity”) may compete with connectivity provided by other third parties. Third-party vendors are not at any competitive disadvantage created by the Exchange.</P>
                <P>The proposed change is not otherwise intended to address any other issues relating to colocation services or related fees, and the Exchange is not aware of any problems that Users would have in complying with the proposed change.</P>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    The Exchange believes that the proposed rule change is consistent with Section 6(b) of the Act,
                    <SU>14</SU>
                    <FTREF/>
                     in general, and furthers the objectives of Section 6(b)(5) of the Act,
                    <SU>15</SU>
                    <FTREF/>
                     in particular, because it is designed to prevent fraudulent and manipulative acts and practices, to promote just and equitable principles of trade, to foster cooperation and coordination with persons engaged in regulating, clearing, settling, processing information with respect to, and facilitating transactions in securities, to remove impediments to and perfect the mechanism of a free and open market and a national market system, and, in general, to protect investors and the public interest and because it is not designed to permit unfair discrimination between customers, issuers, brokers, or dealers. The Exchange further believes that the proposed rule change is consistent with Section 6(b)(4) of the Act,
                    <SU>16</SU>
                    <FTREF/>
                     because it provides for the equitable allocation of reasonable dues, fees, and other charges among its members and issuers and other persons using its facilities.
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         15 U.S.C. 78f(b).0 [sic]
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         15 U.S.C. 78f(b)(4).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">The Proposed Rule Change Is Reasonable</HD>
                <P>The Exchange believes that the proposed rule change is reasonable.</P>
                <P>
                    In considering the reasonableness of proposed services and fees, the Commission's market-based test considers “whether the exchange was subject to significant competitive forces in setting the terms of its proposal . . . , including the level of any fees.” 
                    <SU>17</SU>
                    <FTREF/>
                     If the Exchange meets that burden, “the Commission will find that its proposal is consistent with the Act unless `there is a substantial countervailing basis to find that the terms' of the proposal violate the Act or the rules thereunder.” 
                    <SU>18</SU>
                    <FTREF/>
                     Here, the Exchange is subject to significant competitive forces in setting the terms on which it offers its proposal, in particular because substantially similar substitutes are available and the Exchange has not placed present or future third party vendors at a competitive disadvantage created by the Exchange.
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 90209 (October 15, 2020), 85 FR 67044, 67049 (October 21, 2020) (Order Granting Accelerated Approval to Establish a Wireless Fee Schedule Setting Forth Available Wireless Bandwidth Connections and Wireless Market Data Connections) (SR-NYSE-2020-05, SR-NYSEAMER-2020-05, SR-NYSEARCA-2020-08, SR-NYSECHX-2020-02, SR-NYSENAT-2020-03, SR-NYSE-2020-11, SR-NYSEAMER-2020-10, SR-NYSEArca-2020-15, SR-NYSECHX-2020-05, SR-NYSENAT-2020-08) (“Wireless Approval Order”), citing Securities Exchange Act Release No. 59039 (December 2, 2008), 73 FR 74770, 74781 (December 9, 2008) (“2008 ArcaBook Approval Order”). 
                        <E T="03">See NetCoalition</E>
                         v. 
                        <E T="03">SEC,</E>
                         615 F.3d 525 (D.C. Cir. 2010).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         
                        <E T="03">See</E>
                         Wireless Approval Order, 
                        <E T="03">supra</E>
                         note 17, at 67049, citing 2008 ArcaBook Approval Order, 
                        <E T="03">supra</E>
                         note 17, at 74781.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Substantially Similar Substitutes Are Available</HD>
                <P>
                    As described above,
                    <SU>19</SU>
                    <FTREF/>
                     Users may connect to the Proposed Third Party Data Feed independent of the options provided by the Exchange, creating competition for the Exchange's proposed Connectivity. A User may connect to a Proposed Third Party Data Feed by, first, entering into an agreement with the relevant third party for connectivity, and second, connecting to the Proposed Third Party Data Feed through one of the Telecoms. Users that establish access or connectivity independent of the Connectivity offered by the Exchange are not at any competitive disadvantage created by the Exchange. As of April 30, 2026, more than 98% of the circuits for which Users contracted were supplied by the Telecoms. Although IEX Options does not currently offer the Proposed Third Party Data Feed, the Exchange believes that once it is available, Users may independently establish connectivity to the Proposed Third Party Data Feed through one of the Telecoms.
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         
                        <E T="03">See</E>
                         “Competitive Environment,” above.
                    </P>
                </FTNT>
                <P>
                    Because Users are third parties and are not required to make such information public, the Exchange does not have visibility into how many Users will connect to the Proposed Third Party Data Feed (once it becomes available) independently, as described above.
                    <SU>20</SU>
                    <FTREF/>
                     However, the market for connectivity to the Proposed Third Party Data Feed is competitive, and there is no reason to believe that other actual or potential Users would not obtain connectivity independently if they considered it to be in their commercial interest.
                </P>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         As they are third parties, the Exchange does not have visibility into whether Users intend to connect to the Proposed Third Party Data Feed (once it is available) for their own use, or if they intend to offer other Users such connectivity.
                    </P>
                </FTNT>
                <P>
                    Such Users compete, or would compete, with the Exchange's Connectivity and exert, or would exert, significant competitive forces on the Exchange in setting the terms of its proposal, including the level of the Exchange's proposed fees.
                    <SU>21</SU>
                    <FTREF/>
                     If the Exchange were to set its proposed fees too high, Users could respond by instead selecting other substantially similar access and connectivity by independently establishing access and connectivity as described above.
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         
                        <E T="03">See</E>
                         2008 ArcaBook Approval Order, 
                        <E T="03">supra</E>
                         note 17, at 74789 and n.295 (recognizing that products need not be identical to be substitutable).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Users Are Not at a Competitive Disadvantage Created by the Exchange</HD>
                <P>The Exchange does not believe that FIDS would have any competitive advantage over Users that establish independent connectivity to the Proposed Third Party Data Feed. The Exchange's proposed service for Connectivity does not have (a) any special access to the Proposed Third Party Data Feeds or (b) advantage within the MDC, as all distances in the MDC are normalized.</P>
                <P>Moreover, the Exchange does not believe that FIDS would have any competitive advantage because it would charge for connectivity only, not the Proposed Third Party Data Feed itself. All Users that connect to the Proposed Third Party Data Feed, whether they elect to connect using the Exchange's proposed service or not, would have to pay a third party for the Proposed Third Party Data Feed.</P>
                <P>
                    Nor does the Exchange believe that FIDS has a competitive advantage by virtue of the fact that ICE owns and operates the MDC's meet-me-rooms. Users purchasing Connectivity—like Users of any other colocation service—would require a circuit connecting out of the MDC, and in most cases, such circuits are provided by Telecoms.
                    <FTREF/>
                    <SU>22</SU>
                      
                    <PRTPAGE P="41107"/>
                    Currently, 17 Telecoms operate in the meet-me-rooms and provide a variety of circuit choices. It is in the Exchange's best interest to set the fees that Telecoms pay to operate in the meet-me-rooms at a reasonable level 
                    <SU>23</SU>
                    <FTREF/>
                     so that market participants, including Telecoms, will maximize their use of the MDC. By setting the meet-me-room fees at a reasonable level, the Exchange encourages Telecoms to participate in the meet-me-rooms and to sell circuits to Users for connecting into and out of the MDC. These Telecoms then compete with each other by pricing such circuits at competitive rates. These competitive rates for circuits help draw in more Users and Hosted Customers to the MDC, which directly benefits the Exchange by increasing the customer base to whom the Exchange can sell its colocation services, which include cabinets, power, ports, and connectivity to many third-party data feeds, and because having more Users and Hosted Customers leads, in many cases, to greater participation on the Exchange. In this way, by setting the meet-me-room fees at a level attractive to telecommunications firms, the Exchange spurs demand for all of the services it sells at the MDC, while setting the meet-me-room fees too high would negatively affect the Exchange's ability to sell its services at the MDC.
                    <SU>24</SU>
                    <FTREF/>
                     Accordingly, there are real constraints on the meet-me-room fees the Exchange charges, such that the Exchange does not have an advantage in terms of costs when compared to third parties that enter the MDC through the meet-me-rooms to provide services to compete with the Exchange's services.
                </P>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         Note that in the case of wireless connectivity, a User in colocation still requires a fiber circuit to 
                        <PRTPAGE/>
                        transport data. If a Telecom is used, the data is transmitted wirelessly to the relevant pole, and then from the pole to the meet-me-room using a fiber circuit.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 97999 (July 26, 2023), 88 FR 50190 (August 1, 2023) (SR-NYSEAmer-2023-36) (“MMR Notice”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         
                        <E T="03">See id.</E>
                         at 50193. Importantly, the Exchange is prevented from making any alteration to its meet-me-room services or fees without filing a proposal for such changes with the Commission.
                    </P>
                </FTNT>
                <P>If anything, the Exchange would be subject to a competitive disadvantage vis-à-vis Users regarding connectivity to the Proposed Third Party Data Feed. Users that choose to independently establish connectivity may negotiate terms with the Telecoms through whom such connectivity is delivered, in response to competitive forces. Such prices are not required to be filed by any party with the Commission. In contrast, the Exchange's service and pricing would be standardized as set out in this filing, and the Exchange would be unable to respond to pricing pressure from its competitors without seeking a formal fee change in a filing before the Commission.</P>
                <P>
                    In sum, because the Exchange is subject to significant competitive forces in setting the terms on which it offers its proposal, in particular because the Exchange believes that a substantially similar substitute is available, and the Exchange has not placed actual or proposed Users that already have or establish connectivity at a competitive disadvantage created by the Exchange, the proposed fee for the Exchange's access to the Proposed Third Party Data Feed is reasonable.
                    <SU>25</SU>
                    <FTREF/>
                     If the Exchange were to set its prices for connectivity to the Proposed Third Party Data Feeds at a level that Users found to be too high, Users could easily choose to connect to the Proposed Third Party Data Feed through Telecoms, as detailed above.
                </P>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         
                        <E T="03">See</E>
                         Wireless Approval Order, 
                        <E T="03">supra</E>
                         note 17.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Additional Considerations</HD>
                <P>
                    The Exchange believes that the proposed changes to the Cboe Data Feeds are reasonable. Specifically, the Exchange believes that the proposed changes are a reasonable response to the request from Users that certain Cboe Data Feeds be broken out by asset class, instead of by market. Under the proposed change, if a User wanted all Cboe U.S. Equities data, Cboe Options data or Cboe indices data it would not have to sign up for connectivity to more than one Third Party Data Feed. The Exchange believes that changing the placement of the “CFE” in, and adding the word “Exchange” to, Cboe Futures Exchange would be reasonable, given that the resulting change would mirror the name of the Cboe Futures Exchange.
                    <SU>26</SU>
                    <FTREF/>
                     The monthly recurring connectivity fees for each Cboe Data Feed would remain the same as they are now.
                </P>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         
                        <E T="03">See supra</E>
                         note 10.
                    </P>
                </FTNT>
                <P>Additionally, as with the Proposed Third Party Data Feed, Users may connect to the Cboe Data Feeds independent of the options provided by the Exchange, creating competition for the Exchange's proposed Connectivity. A User may connect to a Cboe Data Feed by, first, entering into an agreement with the relevant third party for connectivity, and second, connecting to the Cboe Data Feed through one of the Telecoms.</P>
                <P>The Exchange believes that the proposed fee for the Proposed Third Party Data Feed is reasonable, as it is the same as the existing fee for connectivity to IEX, which encompasses IEX Equities only. The Exchange believes that adding “Equities” after the existing text for connectivity to the IEX feed is reasonable, as it would clarify which IEX data feed was referenced.</P>
                <HD SOURCE="HD3">The Proposed Rule Change Is Equitable</HD>
                <P>The Exchange believes that the proposed rule change is equitable.</P>
                <P>The Exchange believes that the proposed changes to the Cboe Data Feeds is equitable because the monthly recurring connectivity fee for each Cboe Data Feed would remain the same as it is now. However, under the proposed change, if a User wanted all Cboe U.S. Equities data, Cboe Options data or Cboe indices data it would not have to sign up for connectivity to more than one Third Party Data Feed.</P>
                <P>
                    The Exchange believes that changing the placement of the “CFE” in, and adding “Exchange” to, Cboe Futures Exchange would be equitable, given that the resulting change would mirror the name of the Cboe Futures Exchange.
                    <SU>27</SU>
                    <FTREF/>
                     The proposed changes would make the Fee Schedule easier to read and understand and alleviate any possible market participant confusion caused by the current text.
                </P>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <P>For the same reason, the Exchange believes that adding “Equities” after the existing text for connectivity to the IEX feed is equitable, as it would clarify which IEX data feed was referenced, therefore making the Fee Schedule easier to read and understand and alleviating any possible market participant confusion caused by the current text.</P>
                <P>The Exchange believes that the proposed fee for connectivity to the Proposed Third Party Data Feed is an equitable allocation of fees. The proposed fee is the same as the existing fee for connectivity to IEX Equities.</P>
                <P>Without this proposed rule change, Users would have fewer options for connectivity to the Proposed Third Party Data Feed, once that feed becomes available. By offering Connectivity, the Exchange gives each User additional options for addressing its needs, responding to User demand for options. Offering these additional services would help each User tailor its data center operations to the requirements of its business operations by allowing it to select the form and latency of connectivity that best suits its needs. Users that do not opt to utilize the Exchange's proposed Connectivity would still be able to connect to the Proposed Third Party Data Feed using Telecoms.</P>
                <P>
                    The Exchange believes that the proposed change is equitable because it will result in fees being charged only to Users that voluntarily select to receive 
                    <PRTPAGE P="41108"/>
                    the corresponding services and because those services will be available to all Users.
                </P>
                <P>
                    Furthermore, the Exchange believes that the services and fees proposed herein are equitably allocated because, in addition to the services being completely voluntary, they are available to all Users on an equal basis (
                    <E T="03">i.e.,</E>
                     the same products and services are available to all Users). All Users that voluntarily select the Exchange's Connectivity would be charged the same amount for the same services. Users who opt not to use Connectivity would not be charged. In this way, the proposed rule change equitably allocates the proposed fees only to Users who choose to use the Exchange's Connectivity.
                </P>
                <HD SOURCE="HD3">The Proposed Change Is Not Unfairly Discriminatory</HD>
                <P>The Exchange believes that the proposed rule change is not unfairly discriminatory, for the following reasons.</P>
                <P>The Exchange believes that the proposed changes to the Cboe Data Feeds are not unfairly discriminatory because the monthly recurring connectivity fee for each Cboe Data Feed would remain the same as they are now. However, under the proposed change, if a User wanted all Cboe U.S. Equities data, Cboe Options data or Cboe indices data it would not have to sign up for connectivity to more than one Third Party Data Feed.</P>
                <P>Without this proposed rule change, Users would have fewer options for connectivity to the Proposed Third Party Data Feed. The proposed change would provide Users with an additional choice with respect to the form and optimal latency of their connectivity to the Proposed Third Party Data Feed, allowing a User to select the connectivity that better suits its needs, helping it tailor its colocation operations to the requirements of its business operations. Users that do not opt to utilize the Exchange's proposed Connectivity would still be able to connect to the Proposed Third Party Data Feed using Telecoms.</P>
                <P>
                    The Exchange believes that the proposed change is not unfairly discriminatory because it will result in fees being charged only to Users that voluntarily select to receive the corresponding services and because those services will be available to all Users. Furthermore, the Exchange believes that the services and fees proposed herein are not unfairly discriminatory because, in addition to the services being completely voluntary, they are available to all Users on an equal basis (
                    <E T="03">i.e.,</E>
                     the same products and services are available to all Users). All Users that voluntarily select the Exchange's Connectivity would be charged the same amount for the same services.
                </P>
                <P>For all these reasons, the Exchange believes that the proposal is consistent with the Act.</P>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition</HD>
                <P>
                    In accordance with Section 6(b)(8) of the Act,
                    <SU>28</SU>
                    <FTREF/>
                     the Exchange believes that the proposed rule change will not impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. The proposed change would not affect competition among national securities exchanges or among members of the Exchange, but rather between FIDS and its commercial competitors.
                </P>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         15 U.S.C. 78f(b)(8).
                    </P>
                </FTNT>
                <P>The Exchange does not believe that the proposed rule change regarding Cboe Data Feeds will impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. The monthly recurring connectivity fee for each Cboe Data Feed would remain the same as it is now. However, under the proposed change, if a User wanted all Cboe U.S. Equities data, Cboe Options data or Cboe indices data it would not have to sign up for connectivity to more than one Third Party Data Feed. The other changes to the Cboe Data Feeds would not affect competition.</P>
                <P>By offering Connectivity, the Exchange would give each User additional options for addressing its needs, responding to User demand for options. Providing additional services would help each User tailor its data center operations to the requirements of its business operations by allowing it to select the form and latency of connectivity that best suits its needs. Users that do not opt to utilize the Exchange's proposed Connectivity would still be able to connect to the Proposed Third Party Data Feed using Telecoms.</P>
                <P>The Exchange does not believe that FIDS would have any competitive advantage over Users that establish independent connectivity to the Proposed Third Party Data Feed. The Exchange's proposed service for Connectivity does not have (a) any special access to the Proposed Third Party Data Feed or (b) advantage within the MDC, as all distances in the MDC are normalized.</P>
                <P>Moreover, the Exchange does not believe that FIDS would have any competitive advantage because it would charge for connectivity only, not the Proposed Third Party Data Feed itself. All Users that connect to the Proposed Third Party Data Feed, whether they elect to connect using the Exchange's proposed service or not, would have to pay a third party for the Proposed Third Party Data Feed.</P>
                <P>
                    Nor does the Exchange believe that FIDS has a competitive advantage over any third-party competitors offering connectivity by virtue of the fact that ICE owns and operates the MDC's meet-me-rooms. Users purchasing Connectivity—like Users of any other colocation service—would require a circuit connecting out of the MDC, and in most cases, such circuits are provided by third-party Telecoms. Currently, 17 Telecoms operate in the meet-me-rooms and provide a variety of circuit choices. It is in the Exchange's best interest to set the fees that Telecoms pay to operate in the meet-me-rooms at a reasonable level 
                    <SU>29</SU>
                    <FTREF/>
                     so that market participants, including Telecoms, will maximize their use of the MDC. By setting the meet-me-room fees at a reasonable level, the Exchange encourages Telecoms to participate in the meet-me-rooms and to sell circuits to Users for connecting into and out of the MDC. These Telecoms then compete with each other by pricing such circuits at competitive rates. These competitive rates for circuits help draw in more Users and Hosted Customers to the MDC, which directly benefits the Exchange by increasing the customer base to whom the Exchange can sell its colocation services, which include cabinets, power, ports, and connectivity to many third-party data feeds, and because having more Users and Hosted Customers leads, in many cases, to greater participation on the Exchange. In this way, by setting the meet-me-room fees at a level attractive to telecommunications firms, the Exchange spurs demand for all of the services it sells at the MDC, while setting the meet-me-room fees too high would negatively affect the Exchange's ability to sell its services at the MDC.
                    <SU>30</SU>
                    <FTREF/>
                     Accordingly, there are real constraints on the meet-me-room fees the Exchange charges, such that the Exchange does not have an advantage in terms of costs when compared to third parties that enter the MDC through the meet-me-rooms to provide services to compete with the Exchange's services.
                </P>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         
                        <E T="03">See</E>
                         MMR Notice, 
                        <E T="03">supra</E>
                         note 23.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         
                        <E T="03">See supra</E>
                         note 24.
                    </P>
                </FTNT>
                <P>
                    If anything, the Exchange would be subject to a competitive disadvantage vis-à-vis Users regarding connectivity to the Proposed Third Party Data Feed. Users that choose to independently 
                    <PRTPAGE P="41109"/>
                    establish connectivity may negotiate terms with the Telecoms or other Users through whom such connectivity is delivered, in response to competitive forces. Such prices are not required to be filed by any party with the Commission. In contrast, the Exchange's service and pricing would be standardized as set out in this filing, and the Exchange would be unable to respond to pricing pressure from its competitors without seeking a formal fee change in a filing before the Commission.
                </P>
                <P>The changes would not put any market participants at a relative disadvantage compared to other market participants or penalize one or more categories of market participants in a manner that would impose an undue burden on competition.</P>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants, or Others</HD>
                <P>No written comments were solicited or received with respect to the proposed rule change.</P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
                <P>
                    The Exchange has filed the proposed rule change pursuant to Section 19(b)(3)(A)(iii) of the Act 
                    <SU>31</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) thereunder.
                    <SU>32</SU>
                    <FTREF/>
                     Because the proposed rule change does not: (i) significantly affect the protection of investors or the public interest; (ii) impose any significant burden on competition; and (iii) become operative prior to 30 days from the date on which it was filed, or such shorter time as the Commission may designate, if consistent with the protection of investors and the public interest, the proposed rule change has become effective pursuant to Section 19(b)(3)(A) of the Act 
                    <SU>33</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) 
                    <SU>34</SU>
                    <FTREF/>
                     thereunder.
                </P>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         15 U.S.C. 78s(b)(3)(A)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         17 CFR 240.19b-4(f)(6).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         15 U.S.C. 78s(b)(3)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         17 CFR 240.19b-4(f)(6). In addition, Rule 19b-4(f)(6) requires a self-regulatory organization to give the Commission written notice of its intent to file the proposed rule change, along with a brief description and text of the proposed rule change, at least five business days prior to the date of filing of the proposed rule change, or such shorter time as designated by the Commission. The Exchange has satisfied this requirement.
                    </P>
                </FTNT>
                <P>
                    At any time within 60 days of the filing of such proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act. If the Commission takes such action, the Commission shall institute proceedings under Section 19(b)(2)(B) 
                    <SU>35</SU>
                    <FTREF/>
                     of the Act to determine whether the proposed rule change should be approved or disapproved.
                </P>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         15 U.S.C. 78s(b)(2)(B).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
                <P>Interested persons are invited to submit written data, views and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:</P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's internet comment form (
                    <E T="03">https://www.sec.gov/rules/sro.shtml</E>
                    ); or
                </P>
                <P>
                    • Send an email to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include file number SR-NYSEAMER-2026-55 on the subject line.
                </P>
                <HD SOURCE="HD2">Paper Comments</HD>
                <P>• Send paper comments in triplicate to Secretary, Securities and Exchange Commission, 100 F Street NE, Washington, DC 20549-1090.</P>
                <FP>
                    All submissions should refer to file number SR-NYSEAMER-2026-55. 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-NYSEAMER-2026-55 and should be submitted on or before July 27, 2026.
                </FP>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>36</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>36</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-13527 Filed 7-2-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-105824; File No. SR-FINRA-2026-012]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; Financial Industry Regulatory Authority, Inc.; Notice of Designation of a Longer Period for Commission Action on a Proposed Rule Change To Adopt FINRA Rule 4321 (Allocations of Fail To Deliver Positions) and Amend FINRA Rule 4560 (Short-Interest Reporting)</SUBJECT>
                <DATE>June 30, 2026.</DATE>
                <P>
                    On May 1, 2026, the Financial Industry Regulatory Authority, Inc. (“FINRA”) 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 (1) amend FINRA Rule 4560 (Short-Interest Reporting) to increase the frequency and granularity of the short interest information collected and disseminated by FINRA, and (2) adopt FINRA Rule 4321 (Allocations of Fail to Deliver Positions) to require members to report to FINRA on a monthly basis their daily allocations of fail to deliver positions to correspondent firms. The proposed rule change was published for comment in the 
                    <E T="04">Federal Register</E>
                     on May 18, 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. 105482 (May 13, 2026), 91 FR 28699 (May 18, 2026).
                    </P>
                </FTNT>
                <P>
                    Section 19(b)(2) of the Act 
                    <SU>4</SU>
                    <FTREF/>
                     provides that within 45 days of the publication of notice of the filing of a proposed rule change, or within such longer period up to 90 days as the Commission may designate if it finds such longer period to be appropriate and publishes its reasons for so finding or as to which the self-regulatory organization consents, the Commission shall either approve the proposed rule change, disapprove the proposed rule change, or institute proceedings to determine whether the proposed rule change should be disapproved. The 45th day after publication of the notice for this proposed rule change is July 2, 2026. The Commission is extending this 45-day time period.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         15 U.S.C. 78s(b)(2).
                    </P>
                </FTNT>
                <P>
                    The Commission finds it appropriate to designate a longer period within which to take action on the proposed rule change so that it has sufficient time to consider the proposed rule change and the issues raised therein. Accordingly, the Commission, pursuant 
                    <PRTPAGE P="41110"/>
                    to Section 19(b)(2) of the Act,
                    <SU>5</SU>
                    <FTREF/>
                     designates August 14, 2026, as the date by which the Commission shall either approve or disapprove, or institute proceedings to determine whether to disapprove, the proposed rule change (File No. SR-FINRA-2026-012).
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         15 U.S.C. 78s(b)(2).
                    </P>
                </FTNT>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>6</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>6</SU>
                             17 CFR 200.30-3(a)(31).
                        </P>
                    </FTNT>
                    <NAME>Sherry R. Haywood,</NAME>
                    <TITLE>Assistant Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13530 Filed 7-2-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-105826; File No. SR-NYSEARCA-2026-70]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; NYSE Arca, Inc.; Notice of Filing and Immediate Effectiveness of a Proposed Rule Change To Modify the NYSE Arca Options Fee Schedule Regarding Fees and Rebates Applicable to Manual Transactions</SUBJECT>
                <DATE>June 30, 2026.</DATE>
                <P>
                    Pursuant to Section 19(b)(1) 
                    <SU>1</SU>
                    <FTREF/>
                     of the Securities Exchange Act of 1934 (“Act”),
                    <SU>2</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>3</SU>
                    <FTREF/>
                     notice is hereby given that on June 22, 2026, NYSE Arca, Inc. (“NYSE Arca” or the “Exchange”) filed with the Securities and Exchange Commission (the “Commission”) the proposed rule change as described in Items I and II below, which Items have been prepared by the self-regulatory organization. The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         15 U.S.C. 78a.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>
                <P>
                    The Exchange proposes to modify the NYSE Arca Options Fee Schedule (“Fee Schedule”) regarding fees and rebates applicable to Manual transactions. The proposed rule change is available on the Exchange's website at 
                    <E T="03">www.nyse.com</E>
                     and at the principal office of the Exchange.
                </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <P>In its filing with the Commission, the self-regulatory organization included statements concerning the purpose of, and basis for, the proposed rule change and discussed any comments it received on the proposed rule change. The text of those statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in sections A, B, and C below, of the most significant parts of such statements.</P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and the Statutory Basis for, the Proposed Rule Change</HD>
                <HD SOURCE="HD3">1. Purpose</HD>
                <P>
                    The purpose of this filing is to amend the Fee Schedule to modify fees and rebates applicable to Manual transactions. Specifically, the Exchange proposes to (1) amend fees applicable to Manual transactions in non-Penny issues executed by LMMs and Market Makers (collectively, “Market Makers”), and (2) establish a rebate payable to Floor Broker orders that trade with a Market Maker order on the Trading Floor (“Trading Floor” or “Floor”). The Exchange proposes the fee change to be effective June 22 2026.
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         The Exchange previously filed to amend the Fee Schedule several times beginning on January 2, 2026, all of which filings were withdrawn and replaced by another filing. Most recently, the Exchange amended the Fee Schedule on May 6, 2026 (SR-NYSEARCA-2026-49) which filing the Exchange withdrew on June 22, 2026. The Exchange notes that previous filing proposed changes to a complex order surcharge that are not included in this filing.
                    </P>
                </FTNT>
                <P>
                    The Fee Schedule sets forth per contract transaction fees applicable to Manual executions.
                    <SU>5</SU>
                    <FTREF/>
                     Currently, a $0.50 per contract fee applies to Market Makers' Manual transactions in both Penny and non-Penny issues (except for Manual transactions in MXEA, MXEF, MXUSA, MXWLD, and MXACW). The Exchange proposes to amend the Fee Schedule to increase this fee to $1.00 per contract for Market Makers' Manual transactions in non-Penny issues (excluding transactions in MXEA, MXEF, MXUSA, MXWLD, and MXACW).
                    <SU>6</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         NYSE Arca OPTIONS: TRADE-RELATED CHARGES FOR STANDARD OPTIONS, TRANSACTION FEE FOR MANUAL EXECUTIONS—PER CONTRACT.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         The Exchange also proposes a formatting change to the table setting forth Manual transaction fees to delineate fees applicable to executions in Penny vs. non-Penny issues. The Exchange is not proposing to amend any fees other than those applicable to Market Maker Manual transactions in non-Penny issues as described above. The Exchange also proposes a clarifying change in the text defining Penny and non-Penny issues (preceding the table setting forth Manual transaction fees), to specify that a Penny issue or class refers to option classes that participate in the Penny Interval Program, as described in Rules 6.72-O and 6.72A-O.
                    </P>
                </FTNT>
                <P>
                    The Exchange also proposes to establish a rebate of $0.20 per contract payable to Floor Broker orders that trade with Market Maker orders on the Trading Floor. For Floor Brokers that participate in the FB Prepay Program,
                    <SU>7</SU>
                    <FTREF/>
                     the proposed rebate would apply in lieu of any rebates earned through the Manual Billable Rebate Program as provided in the Fee Schedule. The Exchange proposes to add new text describing this rebate to Endnote 17.
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         The Exchange also proposes a non-substantive change to correct a typo in the portion of the Fee Schedule describing the FB Prepay Program. 
                        <E T="03">See</E>
                         proposed Fee Schedule, FLOOR BROKER FIXED COST PREPAYMENT INCENTIVE PROGRAM (the “FB Prepay Program”).
                    </P>
                </FTNT>
                <P>
                    The Exchange believes that the proposed rebate would continue to incentivize Floor Brokers to participate on the Trading Floor, including when the counterparty to such trading is a Market Maker. In addition, although the proposed change to the Market Maker fee for Manual transactions in non-Penny issues would increase the fee for such executions, the Exchange believes the proposed change, taken together with the proposed Floor Broker rebate would, on balance, not discourage Market Makers from continuing to participate in transactions on the Trading Floor, thereby promoting trading opportunities and competition on the Floor to the benefit of all market participants. The Exchange also notes that the amount of the proposed fee for Market Maker Manual transactions in non-Penny issues is within the range of fees currently in place for transactions by Market Makers (and other market participants) in non-Penny issues.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See, e.g.,</E>
                         Fee Schedule, TRANSACTION FEE FOR ELECTRONIC EXECUTIONS—PER CONTRACT (providing for $1.20 take fee for Market Maker electronic executions in non-Penny issues and $1.10 take fee for Professional Customer electronic executions in non-Penny issues).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    The Exchange believes that the proposed rule change is consistent with Section 6(b) of the Act,
                    <SU>9</SU>
                    <FTREF/>
                     in general, and furthers the objectives of Sections 6(b)(4) and (5) of the Act,
                    <SU>10</SU>
                    <FTREF/>
                     in particular, because it provides for the equitable allocation of reasonable dues, fees, and other charges among its members, issuers and other persons using its facilities and does not unfairly discriminate 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)(4) and (5).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">The Proposed Rule Change Is Reasonable</HD>
                <P>
                    The Exchange operates in a highly competitive market. The Commission 
                    <PRTPAGE P="41111"/>
                    has repeatedly expressed its preference for competition over regulatory intervention in determining prices, products, and services in the securities markets. In Regulation NMS, the Commission highlighted the importance of market forces in determining prices and SRO revenues and, also, recognized that current regulation of the market system “has been remarkably successful in promoting market competition in its broader forms that are most important to investors and listed companies.” 
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 51808 (June 9, 2005), 70 FR 37496, 37499 (June 29, 2005) (S7-10-04) (“Reg NMS Adopting Release”).
                    </P>
                </FTNT>
                <P>
                    There are currently 18 registered options exchanges competing for order flow. Based on publicly-available information, and excluding index-based options, no single exchange has more than 16% of the market share of executed volume of multiply-listed equity and ETF options trades.
                    <SU>12</SU>
                    <FTREF/>
                     Therefore, currently no exchange possesses significant pricing power in the execution of multiply-listed equity and ETF options order flow. More specifically, in May 2026, the Exchange had 10.64% market share of executed volume of multiply-listed equity and ETF options trades.
                    <SU>13</SU>
                    <FTREF/>
                     In such a low-concentrated and highly competitive market, no single options exchange possesses significant pricing power in the execution of options order flow. Within this environment, market participants can freely and often do shift their order flow among the Exchange and competing venues in response to changes in their respective pricing schedules.
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         The OCC publishes options and futures volume in a variety of formats, including daily and monthly volume by exchange, available here: 
                        <E T="03">https://www.theocc.com/Market-Data/Market-Data-Reports/Volume-and-Open-Interest/Monthly-Weekly-Volume-Statistics.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         Based on a compilation of OCC data for monthly volume of equity-based options and monthly volume of equity-based ETF options, 
                        <E T="03">see id.,</E>
                         the Exchange's market share in equity-based options decreased from 11.66% for the month of May 2025 to 10.64% for the month of May 2026.
                    </P>
                </FTNT>
                <P>The Exchange believes that the ever-shifting market share among the exchanges from month to month demonstrates that market participants can shift order flow or discontinue or reduce use of certain categories of products, in response to fee changes. Accordingly, competitive forces constrain options exchange transaction fees.</P>
                <P>The Exchange believes that the proposed rebate is reasonable because it would incentivize Floor Brokers to direct additional Manual orders to the Exchange, thereby creating more trading opportunities on the Trading Floor for all market participants, including Market Makers, who, therefore, would not be discouraged from continuing to quote and trade actively on the Exchange. The Exchange also believes that, in addition to benefitting all market participants, the amount of the proposed fee for Market Maker Manual transactions in non-Penny issues is reasonable, as it remains within the range of fees set forth in the Fee Schedule for transactions by Market Makers in non-Penny issues and more closely aligns with the fee applicable to electronic transactions by Market Makers in non-Penny issues.</P>
                <P>
                    Furthermore, the Exchange believes that assessing a higher fee for manual transactions on the Trading Floor is reasonable considering the distinct advantages afforded to Floor-based Market Makers. In May 2026, approximately 100% of Market Maker Manual volume in non-Penny issues was generated by Trading Floor-based Market Makers who, by virtue of their physical presence and participation model, are uniquely positioned to evaluate the full terms of a transaction, including size, pricing, and counterparty interest, immediately prior to execution. This capability enables Market Makers to exercise discretion in determining whether to engage in a trade under informed conditions that are not available to off-floor or fully electronic participants. In addition, the Exchange's rules provide Floor-based Market Makers with a guaranteed participation entitlement of up to 60% of the trade for Facilitation Cross Transactions,
                    <SU>14</SU>
                    <FTREF/>
                     even in the absence of price improvement. This allocation represents a meaningful structural advantage as it ensures a substantial share of order flow once a Floor-based Market Maker elects to participate.
                    <SU>15</SU>
                    <FTREF/>
                     Together, these features—the ability to assess trading opportunities in real time before committing capital and the certainty of receiving a guaranteed, significant allocation—enhance the likelihood of favorable execution outcomes and revenue opportunities for Floor-based Market Makers. Accordingly, the Exchange believes it is reasonable to assess higher fees on Market Maker Manual transactions in non-Penny issues. The differential reflects the enhanced trading privileges, informational advantages, and allocation guarantees that are uniquely available to Trading Floor-based participants and serves to appropriately align fees with the relative value of these benefits as compared to other market participants operating without such advantages.
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">See</E>
                         Rule 6.47-O.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         This is a significant benefit. While some Market Maker Manual volume derives from upstairs paired transactions, where these benefits are not present, such activity constitutes only a small percentage of overall Market Maker Manual activity.
                    </P>
                </FTNT>
                <P>
                    The Exchange believes that the proposed changes are reasonably designed to incent Floor Brokers (and other participants on the Trading Floor) to increase the number of Manual orders sent to the Exchange. Any increase in trading volume would create more trading opportunities for all market participants and would in turn attract additional order flow to the Exchange, further contributing to a deeper, more liquid market to the benefit of all market participants. The Exchange also notes that the proposed rebate is similar in structure to incentive programs for Floor Brokers offered by competing options exchanges.
                    <SU>16</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         
                        <E T="03">See, e.g.,</E>
                         BOX Exchange Fee Schedule, Section V. Manual Transaction Fees, available at 
                        <E T="03">https://boxexchange.com/assets/BOX-Fee-Schedule-as-of-January-22-2026.pdf</E>
                         (offering Floor Brokers that submit QOO and FOO Orders a $0.20 per contract enhanced rebate for executions that trade with a Floor Market Maker, in lieu of lesser per contract rebates also available to Floor Brokers); MIAX Sapphire Options Exchange, Section 1) c) Trading Floor Transactions, available at 
                        <E T="03">https://www.miaxglobal.com/sites/default/files/fee_schedule-files/MIAX_Sapphire_Fee_Schedule_01212026_b.pdf</E>
                         (providing for the “Floor Broker Breakup Credit,” a $0.20 credit applicable to Floor Brokers that submit a QFO or cQFO for executions that trade with a Floor Market Maker, instead of the $0.10 Floor Broker rebate otherwise available).
                    </P>
                </FTNT>
                <P>The Exchange further believes the proposed change is reasonable because it is designed to offset costs associated with the proposed Floor Broker rebate, which, as noted above, is being proposed to create more trading opportunities on the Trading Floor for all market participants, including Market Makers. To the extent this purpose is achieved, the Exchange believes that the proposed change would not disincentivize Market Maker activity on the Trading Floor because increased order flow from Floor Brokers seeking to earn the proposed rebate would result in more opportunities to trade for all market participants. In addition, the Exchange notes that market participants are free to conduct transactions on competing venues instead if they believe other markets offer more favorable fees and credits.</P>
                <P>
                    To the extent the proposed rule change continues to attract greater volume and liquidity by encouraging Floor Brokers to increase their options volume on the Exchange in an effort to earn the proposed rebate, the Exchange believes the proposed changes would improve the Exchange's overall competitiveness and strengthen its market quality for all market 
                    <PRTPAGE P="41112"/>
                    participants. Against the backdrop of the competitive environment in which the Exchange operates, the proposed rule change is a reasonable attempt by the Exchange to increase the depth of its market and improve its market share relative to its competitors.
                </P>
                <HD SOURCE="HD3">The Proposed Rule Change Is an Equitable Allocation of Credits and Fees</HD>
                <P>
                    The Exchange believes the proposed rule change is an equitable allocation of its fees and credits because the proposed rebate is based on the amount and type of business transacted on the Exchange, and Floor Brokers can try to earn the proposed rebate, or not. The Exchange also believes that the proposed change to the fee applicable to Market Maker Manual transactions in non-Penny issues is equitable because it is designed to balance costs associated with encouraging increased execution opportunities on the Trading Floor, and an increase in such orders would in turn enhance trading opportunities for all market participants. In addition, the proposed fee is within the range of fees currently applicable to transactions by Market Makers and other market participants in non-Penny issues. The Exchange further believes that assessing Market Makers a higher fee for Manual transactions in non-Penny issues is equitable because Floor-based Market Makers, who account for the majority of such volume, occupy a uniquely advantaged position relative to other market participants. Specifically, they benefit from the exclusive ability to evaluate the terms of a transaction immediately prior to execution as well as a guaranteed participation allocation of up to 60% of the trade under the Exchange's rules.
                    <SU>17</SU>
                    <FTREF/>
                     The Exchange also believes that the proposed rebate to Floor Brokers is an equitable allocation of fees and credits because it is intended to support Floor Brokers' role in facilitating the execution of Manual orders, which function benefits all market participants on the Trading Floor, including Market Makers.
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         
                        <E T="03">See</E>
                         note 14, 
                        <E T="03">supra.</E>
                    </P>
                </FTNT>
                <P>Moreover, the proposal is designed to incent participation on the Trading Floor in an effort to make the Exchange a primary execution venue and to attract more Manual transactions to the Exchange. To the extent that the proposed change attracts more Floor Broker orders to the Exchange, this increased order flow would continue to make the Exchange a more competitive venue for, among other things, order execution. Thus, the Exchange believes the proposed rule change would improve market quality for all market participants on the Exchange and, as a consequence, attract more order flow to the Exchange thereby improving market-wide quality and price discovery.</P>
                <HD SOURCE="HD3">The Proposed Rule Change Is Not Unfairly Discriminatory</HD>
                <P>
                    The Exchange believes it is not unfairly discriminatory to modify the fee applicable to Market Maker Manual transactions in non-Penny issues because the proposed change would apply to all similarly-situated Market Maker orders equally, and as discussed above, the Exchange believes it is not unfairly discriminatory to incent order flow to the Exchange, which would enhance liquidity on the Exchange to the benefit of all market participants. The Exchange also believes that the proposed rebate payable to Floor Brokers for a Manual order that trades with a Market Maker order on the Trading Floor is not unfairly discriminatory because it would be available to all similarly situated market participants on an equal and non-discriminatory basis. The Exchange further believes that the proposed rebate available to Floor Brokers is not unfairly discriminatory to other market participants because it is intended to encourage the role performed by Floor Brokers in facilitating the execution of orders via open outcry, a function which the Exchange wishes to support for the benefit of all market participants. In addition, although the proposed change would increase the fee applicable to Market Maker Manual transactions in non-Penny issues, the Exchange notes that the amount of the proposed fee is within the range of fees currently applicable to transactions by Market Makers and other market participants in non-Penny issues and believes that Market Makers would not be discouraged from continuing to participate actively on the Trading Floor and would benefit from increased Manual order flow, including from Floor Brokers seeking to earn the proposed rebate, as a result of the proposed change. The Exchange also believes that the higher fee assessed to Market Makers for Manual transactions in non-Penny issues is not unfairly discriminatory because it reasonably reflects the uniquely advantaged position of Trading Floor-based Market Makers, who generate a significant portion of such volume, relative to other market participants. In particular, these Trading Floor-based Market Makers possess the exclusive ability to evaluate the full terms of a transaction immediately prior to execution and benefit from a guaranteed participation allocation of up to 60% of the trade under the Exchange's rules.
                    <SU>18</SU>
                    <FTREF/>
                     These features provide Floor-based Market Makers with meaningful informational and allocation advantages that are not available to off-floor or purely electronic participants. Accordingly, the Exchange believes that the differential in fees is appropriately calibrated to the distinct structural benefits available to Trading Floor-based Market Makers and therefore does not constitute unfair discrimination. Rather, the higher fee reflects a rational alignment between pricing and the value of the enhanced trading opportunities and execution certainty afforded to these participants. Moreover, to the extent that the exercise of these advantages contributes to increased Trading Floor activity and attracts additional order flow, the proposed fee would enhance overall market quality, deepen liquidity, and promote additional trading opportunities for all market participants on the Exchange.
                </P>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         
                        <E T="03">See</E>
                         note 14, 
                        <E T="03">supra.</E>
                    </P>
                </FTNT>
                <P>Finally, the Exchange believes that it is subject to significant competitive forces, as described below in the Exchange's statement regarding the burden on competition.</P>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition</HD>
                <P>
                    In accordance with Section 6(b)(8) of the Act, the Exchange does not believe that the proposed rule change would impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. Instead, as discussed above, the Exchange believes that the proposed changes would encourage the submission of additional liquidity to a public exchange, thereby promoting market depth, price discovery and transparency and enhancing order execution opportunities for all market participants. As a result, the Exchange believes that the proposed change furthers the Commission's goal in adopting Regulation NMS of fostering integrated competition among orders, which promotes “more efficient pricing of individual stocks for all types of orders, large and small.” 
                    <SU>19</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         
                        <E T="03">See</E>
                         Reg NMS Adopting Release, note 11 
                        <E T="03">supra</E>
                         at 37499.
                    </P>
                </FTNT>
                <P>
                    <E T="03">Intramarket Competition.</E>
                     The proposed change is designed to attract additional order flow to the Exchange. The Exchange believes that the proposed change to Market Maker fees for Manual transactions in non-Penny issues, and the proposed rebate payable to the Floor Broker orders that trade against Market Maker orders on the Trading Floor would encourage Floor 
                    <PRTPAGE P="41113"/>
                    Broker Manual order flow and would not disincentivize Market Maker activity on the Trading Floor. Greater liquidity benefits all market participants on the Exchange and increased order flow would increase opportunities for execution of other trading interest. The proposed changes would apply and be available to all similarly situated market participants that execute Manual transactions on the Trading Floor, and, accordingly, the proposed changes would not impose a disparate burden on competition among market participants on the Exchange.
                </P>
                <P>
                    <E T="03">Intermarket Competition.</E>
                     The Exchange operates in a highly competitive market in which market participants can readily favor one of the other 18 competing options exchanges if they deem the Exchange's fee levels to be excessive. In such an environment, the Exchange must continually adjust its fees to remain competitive with other exchanges and to attract order flow to the Exchange. Based on publicly available information, and excluding index-based options, no single exchange has more than 16% of the market share of executed volume of multiply-listed equity and ETF options trades.
                    <SU>20</SU>
                    <FTREF/>
                     Therefore, currently no exchange possesses significant pricing power in the execution of multiply-listed equity and ETF options order flow. More specifically, in May 2026, the Exchange had 10.64% market share of executed volume of multiply-listed equity and ETF options trades.
                    <SU>21</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         The OCC publishes options and futures volume in a variety of formats, including daily and monthly volume by exchange, available here: 
                        <E T="03">https://www.theocc.com/Market-Data/Market-Data-Reports/Volume-and-Open-Interest/Monthly-Weekly-Volume-Statistics.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         Based on a compilation of OCC data for monthly volume of equity-based options and monthly volume of equity-based ETF options, 
                        <E T="03">see id.,</E>
                         the Exchange's market share in equity-based options increased from 11.66% for the month of May 2025 to 10.64% for the month of May 2026.
                    </P>
                </FTNT>
                <P>The Exchange believes that the proposed rule change reflects this competitive environment because it modifies the Exchange's fees in a manner designed to continue to incent participants on the Trading Floor to direct trading interest to the Exchange, to provide liquidity and to attract additional order flow. To the extent that Floor Brokers are encouraged to utilize the Exchange as a primary trading venue for all transactions, all Exchange market participants stand to benefit from the improved market quality and increased opportunities for price improvement. The Exchange notes that it operates in a highly competitive market in which market participants can readily favor competing venues. In such an environment, the Exchange must continually review, and consider adjusting, its fees and credits to remain competitive with other exchanges. For the reasons described above, the Exchange believes that the proposed rule change reflects this competitive environment.</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>No written comments were solicited or received with respect to the proposed rule change.</P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
                <P>
                    The foregoing rule change is effective upon filing pursuant to Section 19(b)(3)(A) 
                    <SU>22</SU>
                    <FTREF/>
                     of the Act and subparagraph (f)(2) of Rule 19b-4 
                    <SU>23</SU>
                    <FTREF/>
                     thereunder, because it establishes a due, fee, or other charge imposed by the Exchange.
                </P>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         15 U.S.C. 78s(b)(3)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         17 CFR 240.19b-4(f)(2).
                    </P>
                </FTNT>
                <P>
                    At any time within 60 days of the filing of such proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act. If the Commission takes such action, the Commission shall institute proceedings under Section 19(b)(2)(B) 
                    <SU>24</SU>
                    <FTREF/>
                     of the Act to determine whether the proposed rule change should be approved or disapproved.
                </P>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         15 U.S.C. 78s(b)(2)(B).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
                <P>Interested persons are invited to submit written data, views and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:</P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's internet comment form (
                    <E T="03">https://www.sec.gov/rules/sro.shtml</E>
                    ); or
                </P>
                <P>
                    • Send an email to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include file number SR-NYSEARCA-2026-70 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-NYSEARCA-2026-70. 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-NYSEARCA-2026-70 and should be submitted on or before July 27, 2026.
                </FP>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>25</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>25</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-13535 Filed 7-2-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-0177]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Proposed Collection; Comment Request; Extension: Rule 6e-2 and Form N-6EI-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 proposed collection of information.
                </P>
                <P>Rule 6e-2 (17 CFR 270.6e-2) under the Investment Company Act of 1940 (“Act”) (15 U.S.C. 80a) is an exemptive rule that provides separate accounts formed by life insurance companies to fund certain variable life insurance products, exemptions from certain provisions of the Act, subject to conditions set forth in the rule.</P>
                <P>
                    Rule 6e-2 provides a separate account with an exemption from the registration provisions of section 8(a) of the Act if the account files with the Commission 
                    <PRTPAGE P="41114"/>
                    Form N-6EI-1 (17 CFR 274.301), a notification of claim of exemption.
                </P>
                <P>The rule also exempts a separate account from a number of other sections of the Act, provided that the separate account makes certain disclosure in its registration statements (in the case of those separate accounts that elect to register), reports to contract holders, proxy solicitations, and submissions to state regulatory authorities, as prescribed by the rule.</P>
                <P>Since 2008, there have been no filings of Form N-6EI-1 by separate accounts. Therefore, there has been no cost or burden to the industry since that time. The Commission requests authorization to maintain an inventory of one burden hour for administrative purposes.</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>Written comments are invited on: (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 4, 2026.
                </P>
                <SIG>
                    <DATED>Dated: June 30, 2026.</DATED>
                    <NAME>Sherry R. Haywood,</NAME>
                    <TITLE>Assistant Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13496 Filed 7-2-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-105814; File No. SR-PEARL-2026-29]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; MIAX PEARL, LLC; Notice of Filing and Immediate Effectiveness of a Proposed Rule Change by To Amend the By-Laws To Establish the Role of Observers</SUBJECT>
                <DATE>June 30, 2026.</DATE>
                <P>
                    Pursuant to the provisions of 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 26, 2026, MIAX PEARL, LLC (“MIAX Pearl” or the “Company”),
                    <SU>3</SU>
                    <FTREF/>
                     filed with the Securities and Exchange Commission (“Commission”) a proposed rule change as described in Items I, II, and III below, which Items have been prepared by the Exchange. The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         As used throughout the By-Laws of MIAX PEARL, the term “Company” means MIAX PEARL, LLC, a Delaware limited liability company. 
                        <E T="03">See</E>
                         By-Laws of MIAX PEARL, Article I, subparagraph (g) (Effective Date of February 10, 2025), 
                        <E T="03">available at https://www.miaxglobal.com/miax_pearl_amended_and_restated_by_laws.pdf</E>
                         (referred to herein as the “By-Laws”).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>
                <P>
                    The Company proposes to amend the By-Laws to establish the role of Observers (defined and described below) to the Board 
                    <SU>4</SU>
                    <FTREF/>
                    , including, among other things, the rights of Observers and the nomination process. The Company also proposes to remove outdated text regarding the Equity Rights Programs (“ERPs”) and initial committees. All changes to the By-Laws proposed herein are referred to as the “By-Law Amendments”. The By-Laws of the Company may be amended by written consent of the LLC Member 
                    <SU>5</SU>
                    <FTREF/>
                     or at any regular or special meeting of the Board of MIAX PEARL by a resolution adopted by the Board.
                    <SU>6</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         The term “Board” or “Board of Directors” means the Board of Directors of the Company. 
                        <E T="03">See</E>
                         By-Laws, Article I, subparagraph (c).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         The term “LLC Member” means any person who maintains a direct ownership interest in the Company. The sole LLC Member of the Company is Miami International Holdings, Inc. 
                        <E T="03">See</E>
                         By-Laws, Article I, subparagraph (x).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         By-Laws, Article VIII, Section 8.1.
                    </P>
                </FTNT>
                <P>
                    The text of the proposed rule change is available on the Exchange's website at 
                    <E T="03">https://www.miaxglobal.com/markets/us-options/pearl-options/rule-filings</E>
                     and at MIAX Pearl's principal office.
                </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 Company proposes to amend the By-Laws to establish a new role of Observers 
                    <SU>7</SU>
                    <FTREF/>
                     to the Board, including, among other things, the rights of Observers and the nomination process. The Company believes that individuals who are employed by, or otherwise affiliated with, its Exchange Members 
                    <SU>8</SU>
                    <FTREF/>
                     may provide valuable expertise and knowledge to help the Company carry out its business but may not be able, or willing, to serve as a Board member for one reason or another. Accordingly, the Company believes that the proposed Observer position may provide a suitable alternative for these individuals to serve the Company in a similar manner to observer positions established by the Company's affiliates, MIAX Emerald, LLC (“MIAX Emerald”) and MIAX Sapphire, LLC (“MIAX Sapphire”),
                    <SU>9</SU>
                    <FTREF/>
                     and positions that at least 
                    <PRTPAGE P="41115"/>
                    one other exchange has in place. The Company also proposes to remove outdated text regarding the ERPs and initial committees.
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         The Company notes that currently, the term “Observer” is defined as the meaning set forth in Article II, Section 2.2 of the By-Laws. 
                        <E T="03">See</E>
                         By-Laws, Article I, subparagraph (gg). Section 2.2(g) of the By-Laws currently provides for ERP Observers rights. As described herein, the Company proposes to remove all references to “ERPs”, including ERP Observers as the ERPs are now expired. The Company proposes to amend the defined term “Observer” to now describe the new Observer position being created by this filing, which is in line with the MIAX Emerald and MIAX Sapphire Observer positions.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         The term “Exchange Member” means any registered broker or dealer that has been admitted to membership in the national securities exchange operated by the Company. An Exchange Member is not a member of the Company by reason of being an Exchange Member. An Exchange Member will have the status of a “member” of the Exchange as that term is defined in Section 3(a)(3) of the Act. 
                        <E T="03">See</E>
                         By-Laws, Article I, subparagraph (p).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See, generally,</E>
                         MIAX Emerald By-Laws, Article II, Section 2.21 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article II, Section 2.21. 
                        <E T="03">See also</E>
                         Securities 
                        <PRTPAGE/>
                        Exchange Act Release Nos. 104941 (March 6, 2026), 91 FR 12018 (March 11, 2026) (SR-EMERALD-2026-07) 
                        <E T="03">and</E>
                         104940 (March 6, 2026), 91 FR 12024 (March 11, 2026) (SR-SAPPHIRE-2026-07).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Proposal To Establish the Role of Observers, Rights and Nomination Process</HD>
                <P>
                    First, the Company proposes to amend Article I, Definitions, of the By-Laws to establish the following defined terms for “Observer” and “Observer Threshold”, which will be numbered as proposed subparagraphs (cc) and (dd),
                    <SU>10</SU>
                    <FTREF/>
                     respectively:
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         In connection with the amendment and addition of the proposed defined terms, the Company also proposes to renumber current subparagraphs (o) through (x) to now be (l) through (u), renumber current subparagraphs (z) through (gg) to now be (v) through (cc), and renumber current subparagraphs (ii) through (oo) to now be (ee) through (kk) in Article I of the By-Laws. The purpose of these changes is to provide uniformity and clarity in the By-Laws with the amendment and addition of the newly proposed definitions, all of which are in alphabetical order. Part of this renumbering scheme is due to the Company's proposal to remove ERP terms in Article I, as described in more detail below. In sum, the Company proposes to delete current subparagraphs (l) through (n), subparagraph (y), subparagraph (hh), and subparagraph (pp), all of which refer to terms used in the ERPs.
                    </P>
                </FTNT>
                <P>• “Observer” shall mean a person affiliated with an Exchange Member that is elected by the LLC Member to be an observer to the Board, after having been nominated by the Member Nominating Committee, all as set forth in Section 2.21 below.</P>
                <P>• “Observer Threshold” means the minimum percentage of issued and outstanding shares of common stock or securities exercisable or convertible into shares of common stock of the LLC Member that an Exchange Member (including its affiliates) must own in order to qualify for a person affiliated with such Exchange Member being elected as an Observer to the Board, all as set forth in Section 2.21 below. The Observer Threshold shall be equal to at least one percent (1%) of the issued and outstanding shares of common stock of the LLC Member, taking into account securities that are exercisable or convertible into shares of common stock of the LLC Member.</P>
                <P>The purpose of the proposed changes to amend the By-Laws to add the defined terms for “Observer” and “Observer Threshold” is to provide clarity to Exchange Members regarding the proposed new position of Observer to the Board, which is unrelated to the current ERP Observer position, and the requirements for being able to nominate an individual in such capacity.</P>
                <P>
                    The proposed defined terms are not new or novel. The By-Laws for MIAX Emerald and MIAX Sapphire, the Company's affiliates, provide for identical defined terms, allowing their members to nominate observers to the boards of those exchanges in the same capacity, providing that certain thresholds and other requirements are met.
                    <SU>11</SU>
                    <FTREF/>
                     MEMX LLC (“MEMX”) also provides for the ability of certain of its members to nominate observers to its board of directors in a similar capacity as proposed herein, and the corporate governance documents of MEMX and its parent holding company, MEMX Holdings LLC (“MEMX Holdco”), when read together, provide for similarly defined terms.
                    <SU>12</SU>
                    <FTREF/>
                     In particular, the MEMX LLC Agreement defines “Observer Threshold” as follows:
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article I, subparagraphs (cc)-(dd) 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article I, subparagraphs (cc)-(dd).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">See, generally,</E>
                         Third Amended and Restated Limited Liability Company Agreement of MEMX (dated as of June 5, 2025), 
                        <E T="03">available at</E>
                          
                        <E T="03">https://info.memxtrading.com/wp-content/uploads/2025/08/MEMX-LLC-3rdAR_LLCA.pdf</E>
                         (referred to herein as the “MEMX LLC Agreement”) 
                        <E T="03">and</E>
                         Eighth Amended and Restated Limited Liability Company Agreement of MEMX Holdco (dated as of July 29, 2025), 
                        <E T="03">available at</E>
                          
                        <E T="03">https://info.memxtrading.com/wp-content/uploads/2026/01/MEMX-Holdings-LLC-8th-AR-LLC-Agreement-12.16.25-1.pdf</E>
                         (referred to herein as “MEMX Holdco LLC Agreement”).
                    </P>
                </FTNT>
                <EXTRACT>
                    <P>
                        “Observer Threshold” means the minimum number of units of Holdco Class A Units that an Investor Holdco Member must hold in order to have the right to appoint a Board Observer pursuant to Section 8.18(g) of the Holdco LLC Agreement.
                        <SU>13</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>13</SU>
                             
                            <E T="03">See</E>
                             MEMX LLC Agreement, Section 1.1. The MEMX Holdco LLC Agreement provides the specific requirement for the number of units that must be held in order for MEMX members to be able to appoint an observer to the MEMX exchange board of directors. 
                            <E T="03">See</E>
                             MEMX Holdco LLC Agreement, Section 8.18(g) (providing, in summary, that “each Exchange Board Observer Appointing Member shall have the right, but not the obligation, to appoint one (1) observer to each Exchange Board . . . for so long as such Exchange Board Observer Appointing Member holds an aggregate number of Class A Units, Class C Units and/or Class D Units equal to at least 1,250,000 (subject to adjustment. . .”).
                        </P>
                    </FTNT>
                </EXTRACT>
                <P>
                    The Company notes that MEMX's board observer provisions in its corporate documents automatically grant the right to its exchange members to appoint an observer (barring any disqualifier, such as already having a director position on the same board) so long as the requisite ownership threshold is met.
                    <SU>14</SU>
                    <FTREF/>
                     This is slightly different from the Company's proposal that Exchange Members that satisfy the proposed Observer Threshold (and all other proposed Observer requirements, as described further below), may submit candidate names to the Member Nominating Committee 
                    <SU>15</SU>
                    <FTREF/>
                     for consideration for nomination as an Observer. The Company believes this slight difference is reasonable due to the difference in ownership structures of MEMX and the Company, including its affiliated regulated exchanges (Miami International Securities Exchange, LLC (“MIAX”); MIAX Emerald; and MIAX Sapphire). MEMX, through its holding company, MEMX Holdco, is a privately owned company while the Company and its affiliated exchanges are wholly-owned subsidiaries of a publicly-traded company, Miami International Holdings, Inc. (
                    <E T="03">i.e.,</E>
                     the LLC Member). As such, MEMX Holdco is able to restrict ownership in itself and subsidiaries to particular market participants and, therefore, only those particular members of MEMX would be able to meet the requirements to appoint a board observer. In the Company's case, its stock is publicly traded and any Exchange Member may acquire the requisite percentage of securities to be able to nominate a candidate for consideration by the Member Nominating Committee for nomination as an Observer to the Board. The Company believes this proposed part of the nominating process, whereby the Member Nominating Committee reviews candidate submissions for the Observer positions, provides an additional benefit of ensuring only the appropriate individuals are nominated for election to Observer positions.
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">See</E>
                         MEMX LLC Agreement, Section 7.3(c)(ix).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         The term “Member Nominating Committee” means the Member Nominating Committee elected pursuant to these By-Laws. 
                        <E T="03">See</E>
                         By-Laws, Article I, subparagraph (z).
                    </P>
                </FTNT>
                <P>
                    Next, the Company proposes to amend Section 2.9 of the By-Laws to provide for removal and resignation provisions for Observers. In particular, the Company proposes to amend Section 2.9(a) of the By-Laws to provide that any Observer to the Board may be removed or expelled with or without cause by the LLC Member, which is similar to the removal provision applicable to Directors.
                    <SU>16</SU>
                    <FTREF/>
                     The purpose of this proposed provision is to ensure that the LLC Member retains discretion to be able to remove an Observer from such position in a similar manner as Directors of the Company.
                    <SU>17</SU>
                    <FTREF/>
                     In 
                    <PRTPAGE P="41116"/>
                    connection with this proposed change to the first sentence of Section 2.9(a), the Company also proposes to amend that sentence to specify that a Director may be removed by the Board of Directors in the manner provided by Article II, Section 2.9(b). The purpose of this proposed provision is to clarify that the provisions of Section 2.9(b) apply solely to the removal process for Directors, not Observers. The Company also proposes to amend Section 2.9(c) of the By-Laws to specify that an Observer, like a Director, may resign at any time either upon notice of resignation to the Chairman of the Board, the President or Secretary. The purpose of this proposed provision is to make it clear that Observers retain the right to be able to resign from such position in the event that they need to do so, while also providing the requisite notice to the Company to effectuate such removal.
                    <SU>18</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         The term “Director” means the persons elected or appointed to the Board of Directors from time to time in accordance with the LLC Agreement and the By-Laws in their capacity as managers of the Company. 
                        <E T="03">See</E>
                         By-Laws, Article I, subparagraph (j).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         MIAX Emerald and MIAX Sapphire provide for the same provisions in their respective by-laws. 
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article II, Section 2.9(a) 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article II, Section 
                        <PRTPAGE/>
                        2.9(a). The Company also notes that this removal provision is comparable to the similar provision in the MEMX LLC Agreement concerning the removal of its board observers. 
                        <E T="03">See</E>
                         MEMX LLC Agreement, Section 7.6(a) (providing, in relevant part, that “[a] Board Observer may be removed at any time by [MEMX] Holdco (subject, in each case, to the provisions of [the MEMX LLC] Agreement and the [MEMX] Holdco LLC Agreement regarding the right to nominate and remove [MEMX] Board Observers.”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         MIAX Emerald and MIAX Sapphire provide for the same provisions in their respective by-laws. 
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article II, Section 2.9(c) 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article II, Section 2.9(c). This provision is also comparable to the similar resignation provision in the MEMX LLC Agreement concerning the resignation of board observers. 
                        <E T="03">See</E>
                         MEMX LLC Agreement, Section 7.6(c) (“Any Director or Board Observer may resign at any time from his or her position as such upon notice of resignation to the Chairman of the Board, the CEO or the Secretary.”).
                    </P>
                </FTNT>
                <P>
                    Next, the Company proposes to amend Section 2.10 of the By-Laws to specify that Observers may participate in a meeting of the Board either at the place of the meeting or via the same mode of communication as provided to the members of the Board. The purpose of this change is to provide the right of Observers to be able to attend Board meetings in the same manner and through the same mode of communication as provided to Directors and members of any committee of the Board.
                    <SU>19</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         MIAX Emerald and MIAX Sapphire provide for the same provision in their respective by-laws. 
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article II, Section 2.10 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article II, Section 2.10. The Company also believes that the MEMX LLC Agreement provides for similar provisions. 
                        <E T="03">See</E>
                         MEMX LLC Agreement, Section 7.7(a) (providing, in sum, that meetings of the board may be held either in person or by means of telephone or video conference or other communications device that permits all participants to hear each other) 
                        <E T="03">and</E>
                         MEMX LLC Agreement, Section 7.3(c)(xi) (providing, in sum, that board observers have the right to participate in any discussions taking place at a meeting of the board of directors of MEMX).
                    </P>
                </FTNT>
                <P>
                    Next, the Company proposes to amend Section 2.18 of the By-Laws to include Observers in the list of individuals that the Board may provide for the reasonable compensation (in addition to the Chairman, Directors and members of committees). By including Observers in the first sentence of Section 2.18, the Company also intends that the Board may provide for reimbursement of reasonable expenses incurred by Observers, along with the Chairman, Directors and members of committees, in connection with the business of the Company. The purpose of this change is to provide the Board with discretion to offer reasonable compensation to Observers and reimburse reasonable expenses for Observers in connection with the business of the Company (
                    <E T="03">i.e.,</E>
                     reimbursement of travel expenses for Observers to attend in-person Board meetings).
                    <SU>20</SU>
                    <FTREF/>
                     The Company believes this proposed change is reasonable because the decision of whether to compensate Observers and/or reimburse reasonable expenses of Observers related to the business of the Company will ultimately remain with the Board.
                </P>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         MIAX Emerald and MIAX Sapphire provide for the same provision in their respective by-laws. 
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article II, Section 2.18 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article II, Section 2.18.
                    </P>
                </FTNT>
                <P>
                    Next, the Company proposes to amend Section 2.20 of the By-Laws to amend the provisions regarding conflicts of interest as well as contracts and transactions involving Directors to include Observers in those subparagraphs. In particular, the Company proposes to amend subparagraph (a) of Section 2.20 to provide that an Observer, along with Directors and members of any committee, may not participate in the consideration or decision of any matter relating to a particular Exchange Member, company, or individual if such Observer has a material interest in, or a professional, business, or personal relationship with, that Exchange Member, company, or individual, or if such participation shall create an appearance of impropriety. The Company proposes to further amend subparagraph (a) to provide that in any such case resulting in the appearance of impropriety, an Observer (along with Directors and members of any committee) shall recuse himself or herself or shall be disqualified.
                    <SU>21</SU>
                    <FTREF/>
                     The purpose of this change is to provide that Observers will be subject to the substantively similar conflicts of interest provisions as the Company's Directors and members of any committee.
                    <SU>22</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         The Company notes that the disqualification language pertains to Directors or committee members recusing themselves from any vote taking place; however, Observers will not have voting rights, as such, this last phrase “disqualified” in subparagraph (a) of Section 2.20 will not apply to Observers recusing themselves.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         MIAX Emerald and MIAX Sapphire provide for the same provision in their respective by-laws. 
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article II, Section 2.20(a) 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article II, Section 2.20(a). These changes are also in line with the similar conflicts of interest provisions in the MEMX LLC Agreement. 
                        <E T="03">See</E>
                         MEMX LLC Agreement, Section 7.9(a).
                    </P>
                </FTNT>
                <P>
                    The Company also proposes to amend subparagraph (b) of Section 2.20 of the By-Laws to include Observers in the provisions concerning certain contracts or transactions between the Company and Directors or Officers. In particular, the Company proposes to amend subparagraph (b) to provide that no contract or transaction between the Company and one or more Observers (along with Directors or officers), or between the Company and any other corporation, partnership, association, or other organization in which one or more Observers (or Directors or officers) are directors or officers, or have a financial interest, shall be void or voidable solely for this reason if: (i) the material facts pertaining to such Observer's (or Director's or officer's) relationship or interest and the contract or transaction are disclosed or are known to the Board or the committee, and the Board or committee in good faith authorizes the contract or transaction by the affirmative vote of a majority of the disinterested Directors, even though the disinterested Directors be less than a quorum; or (ii) the material facts are disclosed or become known to the Board or committee after the contract or transaction is entered into, and the Board or committee in good faith ratifies the contract or transaction by the affirmative vote of a majority of the disinterested Directors, even though the disinterested Directors be less than a quorum. The purpose of this change is to provide that Observers will be subject to the same provisions allowing certain contracts or transactions with the Company in substantially similar circumstances as the Company's Directors, officers and members of any committee.
                    <SU>23</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         MIAX Emerald and MIAX Sapphire provide for the same provision in their respective by-laws. 
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article II, Section 2.20(b) 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article II, Section 2.20(b). This provision is also in line with the similar provisions in the MEMX LLC Agreement. 
                        <E T="03">See</E>
                         MEMX LLC Agreement, Section 7.9(b).
                    </P>
                </FTNT>
                <P>
                    Next, the Company proposes to establish new Section 2.21 of the By-Laws, titled “Observers,” which will contain subparagraphs describing the 
                    <PRTPAGE P="41117"/>
                    number, term, nomination and election process, and rights and obligations for Observers. In particular, proposed Section 2.21(a) will provide that there may be up to three (3) Observers to the Board at any time, as determined by the LLC Member in its sole and absolute discretion.
                    <SU>24</SU>
                    <FTREF/>
                     Further, proposed subparagraph (a) will provide that no current Observer may be affiliated 
                    <SU>25</SU>
                    <FTREF/>
                     with another current Observer or current Director of the Board. The purpose of these provisions is to place a limit 
                    <SU>26</SU>
                    <FTREF/>
                     on the number of Observers that may be appointed and specify that no Observer may be affiliated with another Observer or Director.
                    <SU>27</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         At the time of this filing, the Company does not believe that more than three (3) Exchange Members would meet the requirements to be able to nominate a candidate for appointment as an Observer. In the event that there was a significant change whereby more Exchange Members could meet the requirements to be able to nominate a candidate for appointment as an Observer, the Company would consider whether additional changes to the By-Laws were needed at that time. If the Company decides that more than three (3) Observers are needed, it will file another 19b-4 Rule Filing with the Securities and Exchange Commission (“Commission”) to amend the By-Laws. MIAX Emerald and MIAX Sapphire provide for the same provision in their respective by-laws. 
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article II, Section 2.21(a) 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article II, Section 2.21(a).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         An “affiliate” of, or person “affiliated” with a specific person, is a person that directly, or indirectly through one or more intermediaries, controls or is controlled by, or is under common control with, the person specified. 
                        <E T="03">See</E>
                         By-Laws, Article I, subparagraph (b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         The Company does not believe that this limit will impede any Exchange Member from being able to appoint an Observer for those Exchange Members that meet the Observer Threshold and other requirements to be able to nominate a candidate to the Member Nominating Committee for nomination as an Observer. Certain Exchange Members already have an individual serving in a Director capacity on the Board, thereby eliminating their ability to also have an Observer to the Board pursuant to proposed Section 2.21(a) of the By-Laws. Further, the Company's affiliated exchanges (MIAX, MIAX Emerald, and MIAX Sapphire) plan to (or already have) filed with the Commission to amend their by-laws to provide for the same Observer provisions as proposed herein. 
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article II, Section 2.21(a) 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article II, Section 2.21(a). As such, the Company's Exchange Members who are also members of one or more of the Company's affiliated exchanges will have the opportunity to nominate a candidate to be considered for the Board Observer position by the Member Nominating Committees of those exchanges. At the time of this filing, the Company and all of its affiliated exchanges hold their board meetings at the same time, effectively allowing Board Observers for each affiliated exchange to be present at one time.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         MIAX Emerald and MIAX Sapphire provide for the same provision in their respective by-laws. 
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article II, Section 2.21(a) 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article II, Section 2.21(a). This is also in line with the similar provision in the MEMX LLC Agreement which does not permit an exchange member to have individuals holding a director position and observer position at the same time. 
                        <E T="03">See</E>
                         MEMX LLC Agreement, Section 7.3(c)(x) (“When a Nominating Investor Holdco Member reaches its turn in the Investor Director Nomination Rotation and its Investor Director nominee is elected to the Board. . .and is seated as a Director, its Board Observer (if any) shall be deemed automatically removed from his or her position. . .and, for as long as such Nominating Investor Holdco Member's Investor Director nominee is serving as an Investor Director, such Nominating Investor Holdco Member shall have no right to have a Board Observer.”).
                    </P>
                </FTNT>
                <P>Proposed subparagraph (b) of Section 2.21 of the By-Laws will describe the terms for Observers. In particular, proposed subparagraph (b) will provide that term of office for each Observer shall be three (3) years from the date of their election. An Observer may serve for any number of terms, consecutive or otherwise. Observers shall be divided into up to three (3) classes, designated Class I, Class II, and Class III. Observers shall serve staggered three-year terms, with the term of one class expiring each year. In order to commence such staggered three-year terms, Observers in Class I shall serve until the second annual election of the Board of Directors, Observers in Class II shall initially serve until the third annual election of the Board of Directors, and Observers in Class III shall initially serve until the fourth annual election of the Board of Directors. Commencing with the second annual election of the Board of Directors, the term for each class of Observers elected at such time shall be three years from the date of their election. Notwithstanding the foregoing, in the case of any new Observer as contemplated by (proposed) Article II, Section 2.21(a), such Observer shall be added to a class, as determined by the Board at the time of such Observer's initial election or appointment, and shall have an initial term expiring at the same time as the term of the class to which such Observer has been added. </P>
                <P>The Exchange Member affiliated with an Observer must continue to satisfy the Observer Threshold for the duration of the Observer's term. If the Exchange Member affiliated with an Observer fails to meet the Observer Threshold at any time during the duration of the Observer's term, the Observer's term shall immediately terminate at such time. The Exchange Member affiliated with an Observer has an ongoing obligation to immediately notify the Company if such Exchange Member no longer meets the Observer Threshold.</P>
                <P>
                    The proposed term lengths and classes for Observers are based on the similar term provisions for the Company's Directors, which are also divided into three classes with staggered terms.
                    <SU>28</SU>
                    <FTREF/>
                     The purpose of this provision is to provide Observers with the same term length as Directors and avoid the Company having to go through lengthy nomination processes each year in the event there are several Observers. The requirement that the Exchange Member affiliated with an Observer must maintain the ownership requirement set forth in the Observer Threshold is to ensure that Exchange Members who meet such threshold continue to do so throughout the entire term of the Observer.
                    <SU>29</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         
                        <E T="03">See</E>
                         By-Laws, Article II, Section 2.3(b). MIAX Emerald and MIAX Sapphire provide for the same provision in their respective by-laws. 
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article II, Section 2.21(b) 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article II, Section 2.21(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         MIAX Emerald and MIAX Sapphire provide for the same provision in their respective by-laws. See MIAX Emerald By-Laws, Article II, Section 2.21(b) 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article II, Section 2.21(b). This holding requirement is also in line with the similar provision in the MEMX LLC Agreement. 
                        <E T="03">See</E>
                         MEMX LLC Agreement, Section 7.3(d)(vi) (“An individual Board Observer position shall be immediately terminated following a Transfer of Holdco Units by an Investor Holdco Member which, after giving effect to such Transfer, results in such Investor Holdco Member holding a number of Holdco Class A Units that is less than the Observer Threshold. . .”).
                    </P>
                </FTNT>
                <P>
                    Proposed subparagraph (c) of Section 2.21 will describe the nomination and election process for Observers. In particular, proposed subparagraph (c) will provide that an Exchange Member that meets the requirements for the Observer Threshold and as specified in Section 2.21 may submit candidate names to the Member Nominating Committee for consideration for nomination as an Observer. The Member Nominating Committee shall consult with the Nominating Committee 
                    <SU>30</SU>
                    <FTREF/>
                     and the Chairman and Chief Executive Officer for the purpose of nominating candidates for election as an Observer to the Board at the annual meeting of the LLC Member. The Nominating Committee shall nominate only those persons whose names have been submitted by the Member Nominating Committee. The LLC Member shall elect the persons nominated by the Nominating Committee to be Observers to the Board at the annual meeting of the LLC Member. The purpose of conducting the nomination and election process for Observers in the manner described above is to keep this process in line with the process used to nominate and elect Member Representative Directors.
                    <SU>31</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         The term “Nominating Committee” means the Nominating Committee elected pursuant to the By-Laws. 
                        <E T="03">See</E>
                         By-Laws, Article I, subparagraph (dd).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         
                        <E T="03">See</E>
                         By-Laws, Article II, Section 2.4(b). MIAX Emerald and MIAX Sapphire provide for the same provision in their respective by-laws. 
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article II, Section 2.21(c) 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article II, Section 2.21(c). The Company notes that the process for nominating 
                        <PRTPAGE/>
                        and electing Observers does not include the petition process for the Member Representative Director elections, as described in subparagraphs (c)-(f) of Section 2.4 of the By-Laws. The Company believes the petition process is not needed for Observers as Observers have no voting rights, the pool of candidates is much smaller for Observers as compared to Member Representative Directors, and Exchange Members that are members of the Company's affiliated exchanges and meet the requirements to be able to nominate a candidate as an Observer, may submit candidate names to the Member Nominating Committees of the Company's affiliated exchanges for consideration for nomination as an Observer.
                    </P>
                </FTNT>
                <PRTPAGE P="41118"/>
                <P>
                    Proposed subparagraph (d) to Section 2.21 of the By-Laws would describe the rights and obligations of Observers. In particular, subparagraph (d) will provide that the Company shall invite the Observers to attend all meetings of its Board of Directors in a non-voting observer capacity, and, in this respect, shall give Observers copies of all notices, minutes, consents, and other materials that it provides to Directors, at the same time and in the same manner as provided to such Directors; provided, however, that such Observers shall agree in writing to hold in confidence and trust and to act in a fiduciary manner with respect to all information so provided; and provided further, that the Company reserves the right to withhold any information and to exclude any such Observers from any meeting or portion thereof if access to such information or attendance at such meeting could adversely affect the attorney-client privilege between the Company and its counsel or result in disclosure of trade secrets or a conflict of interest.
                    <SU>32</SU>
                    <FTREF/>
                     The purpose of this provision is to clarify the rights of Observers and limitations on their capacity to attend Board meetings and receive Board materials.
                    <SU>33</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         The Company notes that proposed Section 2.21(d) does not override the confidentiality provisions related to the Company's self-regulatory function that are described in Section 10.4 of the By-Laws.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         MIAX Emerald and MIAX Sapphire provide for the same provision in their respective by-laws. 
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article II, Section 2.21(d) 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article II, Section 2.21(d). This is also in line with the similar provision in the MEMX LLC Agreement describing the rights, obligations and limitations for its board observers. 
                        <E T="03">See</E>
                         MEMX LLC Agreement, Section 7.3(c)(xi).
                    </P>
                </FTNT>
                <P>
                    Next, the Company proposes to amend Section 3.1(a) of the By-Laws to include Observers in the list of individuals that are to be elected at the annual meeting of the LLC Member, with such time and place of the annual meeting to be determined by the Board. The purpose of this change is to provide specific details concerning the time and place for Observer candidates to be elected to such position. The Company believes this to be reasonable as it would allow Observers to be elected at the same annual meeting as Directors and committee members, as described in proposed Section 3.1(a) of the By-Laws.
                    <SU>34</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         MIAX Emerald and MIAX Sapphire provide for the same provision in their respective by-laws. 
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article III, Section 3.1 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article III, Section 3.1.
                    </P>
                </FTNT>
                <P>
                    The Company also proposes to amend Section 5.3 of the By-Laws to add a sentence regarding the Member Nominating Committee's role in connection with the nomination of Observers. As described above, proposed Section 2.21(c) will provide, among other things, that the Member Nominating Committee shall consult with the Nominating Committee and the Chairman and Chief Executive Officer for the purpose of nominating candidates for election as an Observer to the Board at the annual meeting of the LLC Member. The Company proposes to amend Section 5.3 to add that same sentence since this section also discusses the Member Nominating Committee's role in nominating candidates for certain positions on the Board.
                    <SU>35</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         MIAX Emerald and MIAX Sapphire provide for the same provision in their respective by-laws. 
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article V, Section 5.3 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article V, Section 5.3.
                    </P>
                </FTNT>
                <P>
                    The Company proposes to amend Section 10.3 of the By-Laws to remove Observers from the last sentence of Section 10.3. Currently, it provides that “[i]n no event shall members of the Board of Directors of Miami International Holdings, Inc. who are not also members of the Board, Observers, or any officers, staff, counsel or advisors of Miami International Holdings, Inc. who are not also officers, staff, counsel or advisors of the Company (or any committees of the Company), be allowed to participate in any meetings of the Board (or any committee of the Company) pertaining to the self-regulatory function of the Company (including disciplinary matters).” The Exchange notes that currently there are no observers to the board of Miami International Holdings, Inc. The purpose of the proposed change is to align the Company's By-Laws with the By-Laws of its affiliated regulated exchanges (MIAX Emerald and MIAX Sapphire).
                    <SU>36</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>36</SU>
                         
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article X, Section 10.3 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article X, Section 10.3.
                    </P>
                </FTNT>
                <P>
                    Finally, the Exchange proposes to amend Section 10.4 of the By-Laws to remove Observers from the list of individuals who may have access to the books and records of the Company that contains confidential information pertaining to the self-regulatory function of the Company. The purpose of the proposed change is to align the Company's By-Laws with the By-Laws of its affiliated regulated exchanges (MIAX Emerald and MIAX Sapphire).
                    <SU>37</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>37</SU>
                         
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article X, Section 10.4 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article X, Section 10.4.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Proposal To Remove References to Initial Committees and ERPs</HD>
                <P>
                    The Company proposes to amend Section 5.1 of the By-Laws to delete outdated references to initial committees. On December 13, 2016, the Commission approved the Company's Form 1 application for registration as a national securities exchange under Section 6 of the Exchange Act.
                    <SU>38</SU>
                    <FTREF/>
                     On February 6, 2017, the Company launched electronic operations as a national securities exchange.
                    <SU>39</SU>
                    <FTREF/>
                     Pursuant to the By-Laws and prior to commencing operations, the LLC Member (
                    <E T="03">i.e.,</E>
                     Miami International Holdings, Inc.) appointed the initial Nominating Committee and Member Nominating Committee. The initial Nominating Committee and Member Nominating Committee served until the second annual meeting of the LLC Member.
                    <SU>40</SU>
                    <FTREF/>
                     Accordingly, the Company proposes to amend Section 5.1 of the By-Laws to remove all references relating to the initial Nominating Committee and Member Nominating Committee as those provisions are outdated.
                </P>
                <FTNT>
                    <P>
                        <SU>38</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 79543 (December 13, 2016), 81 FR 92901 (December 20, 2016) (File No. 10-227).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>39</SU>
                         
                        <E T="03">See</E>
                         Press Release, MIAX Pearl Successfully Launches Trading Operations (dated February 6, 2017), 
                        <E T="03">available at</E>
                          
                        <E T="03">https://www.miaxglobal.com/sites/default/files/alert-files/MIAX_Press_Release_02062017.pdf.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>40</SU>
                         
                        <E T="03">See</E>
                         By-Laws, Article V, Section 5.1.
                    </P>
                </FTNT>
                <P>
                    In addition, the Company proposes to amend various subparagraphs and sections of the By-Laws to delete outdated references to the ERPs. On April 6, 2018, the Company filed a proposed rule change with the Commission to implement an equity rights program (“the Initial ERP”) pursuant to which units representing the right to acquire equity in the Exchange's parent holding company, Miami International Holdings, Inc. (“MIH”) were issued to a participating Member 
                    <SU>41</SU>
                    <FTREF/>
                     in exchange for payment of an initial purchase price or the prepayment of certain ERP Exchange 
                    <PRTPAGE P="41119"/>
                    Fees 
                    <SU>42</SU>
                    <FTREF/>
                     and the achievement of certain liquidity volume thresholds on the Exchange over a 32-month period commencing May 1, 2018.
                    <SU>43</SU>
                    <FTREF/>
                     On August 20, 2020, the Company filed a proposed rule change with the Commission to implement a second equity rights program (“the Second ERP”) under which ERP Exchange fees would be expanded to include fees incurred on and after October 1, 2020 through June 30, 2024 for trading equity securities on MIAX PEARL Equities 
                    <SU>44</SU>
                    <FTREF/>
                     and the achievement of certain liquidity volume thresholds on MIAX PEARL Equities over a 42-month period commencing January 1, 2021.
                    <SU>45</SU>
                    <FTREF/>
                     The Second ERP is independent of the Initial ERP. The Exchange notes that both the Initial ERP and Second ERP expired and currently there is no ERP Director 
                    <SU>46</SU>
                    <FTREF/>
                     or Observer appointed by an ERP Member serving on the Board.
                    <SU>47</SU>
                    <FTREF/>
                     Accordingly, the Company proposes to amend the By-Laws to remove all references and sections relating to ERPs as those provisions are outdated. In particular, the Company proposes to make the following changes:
                </P>
                <FTNT>
                    <P>
                        <SU>41</SU>
                         The term “Member” means an individual or organization that is registered with the Exchange pursuant to Chapter II of the Exchange's Rules for purposes of trading on the Exchange as an “Electronic Exchange Member” or “Market Maker.” Members are deemed “members” under the Exchange Act. 
                        <E T="03">See</E>
                         MIAX Pearl Options Exchange Rule 100.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>42</SU>
                         The ERP Exchange fees under the Initial ERP consist of: (a) transaction fees as set forth in Section 1)a of the MIAX PEARL Options Fee Schedule; (b) membership fees as set forth in Section 3 of the MIAX PEARL Options Fee Schedule; (c) system connectivity fees as set forth in Section 5 of the MIAX PEARL Options Fee Schedule; and (d) market data fees as set forth in Section 6 of the MIAX PEARL Options Fee Schedule (collectively, the “ERP Exchange Fees”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>43</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 83012 (April 9, 2018), 83 FR 16163 (April 13, 2018) (SR-PEARL-2018-08) (Notice of Filing and Immediate Effectiveness of a Proposed Rule Change To Implement an Equity Rights Program) (“Initial ERP Filing”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>44</SU>
                         The term “MIAX Pearl Equities” shall mean MIAX Pearl Equities, a facility of MIAX PEARL, LLC. 
                        <E T="03">See</E>
                         MIAX Pearl Equities Exchange Rule 1901.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>45</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 89730 (September 1, 2020), 85 FR 55530 (September 8, 2020) (SR-PEARL-2020-10) (Notice of Filing and Immediate Effectiveness of a Proposed Rule Change To Implement a Second Equity Rights Program) (“Second ERP Filing”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>46</SU>
                         “ERP Director” means a MIAX PEARL Equities Industry Director who has been nominated by an ERP Member and appointed to the Board of Directors. 
                        <E T="03">See</E>
                         By-Laws, Article I, subparagraph (m).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>47</SU>
                         “ERP Member” means an Exchange Member who acquired Units pursuant to an ERP Agreement sufficient to acquire an ERP Director or an Observer position. 
                        <E T="03">See</E>
                         By-Laws, Article I, subparagraph (n).
                    </P>
                </FTNT>
                <P>• delete subparagraphs (l)-(n), (y), (hh), and (pp) in Article I;</P>
                <P>• remove “and Observer Rights” from the heading of Section 2.2;</P>
                <P>• remove references to ERP Directors from Section 2.2 (b), subparagraphs (i) and (ii);</P>
                <P>• delete subparagraphs (e)-(g) of Section 2.2;</P>
                <P>• remove references to ERP Directors from Section 2.3 (b);</P>
                <P>• delete subparagraphs (c)-(d) of Section 2.3;</P>
                <P>• delete the last sentence related to ERP Directors from Section 2.4 (a); and</P>
                <P>• delete subparagraph (c) of Section 2.8;</P>
                <P>The purpose of these proposed changes is to update the By-Laws to remove outdated references, which will provide clarity to market participants regarding the ERPs, Nominating Committee and Member Nominating Committee throughout the By-Laws.</P>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    The Company believes that the proposed By-Law Amendments are consistent with Section 6(b) of the Exchange Act,
                    <SU>48</SU>
                    <FTREF/>
                     in general, and furthers the objectives of Section 6(b)(1) 
                    <SU>49</SU>
                    <FTREF/>
                     in particular, in that it enables the Company to be so organized as to have the capacity to be able to carry out the purposes of the Exchange Act and to comply, and to enforce compliance by its Exchange Members and persons associated with its Exchange Members, with the provisions of the Exchange Act, the rules and regulations thereunder, and the rules of the Company. The Company also believes that the proposed By-Law Amendments are consistent with Section 6(b)(5) of the Exchange Act,
                    <SU>50</SU>
                    <FTREF/>
                     in that they are designed to prevent fraudulent and manipulative acts and practices, promote just and equitable principles of trade, foster cooperation and coordination with persons engaged in facilitating transactions in securities, remove impediments to and perfect the mechanism of a free and open market and a national market system and, in general, protect investors and the public interest.
                </P>
                <FTNT>
                    <P>
                        <SU>48</SU>
                         15 U.S.C. 78f(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>49</SU>
                         15 U.S.C. 78f(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>50</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Proposal To Establish the Role of Observers, Rights and Nomination Process</HD>
                <P>The Company believes its proposal to amend the By-Laws to establish the role of Observers to the Board is consistent with the Act as this may facilitate additional participation by individuals affiliated with Exchange Members who have the expertise and knowledge in securities markets to help the Board in carrying out the Company's business. Although Observers will not have the right to vote on Company matters at Board meetings, they will be able to attend, review Board materials and participate in Board meetings, which may provide additional view points for relevant issues concerning the business of the Company that may impact other Exchange Members. Thus, the Company does not believe the creation of the Observer position to the Board will have any impact on the Company's ability to be organized as to have the capacity to carry out the purposes of the Act and to comply with the provisions of the Act, the rules and regulations thereunder, and the rules of the Company, which promotes just and equitable principles of trade and continues to protect investors and the public interest. Further, the Company believes the proposed changes to the By-Laws are consistent with, and will not interfere with, the self-regulatory obligations of the Company.</P>
                <P>
                    The Company believes the proposed changes to the By-Laws pertaining to Observers enables the Company to be so organized as to have the capacity to be able to carry out the purposes of the Exchange Act because all of the changes are based on similar provisions already in place at the Company for its Directors (or committee members) or are substantively similar to provisions in place at a competing exchange that provides for board observers. The addition of the proposed defined terms for “Observer” and “Observer Threshold” will provide clarity to Exchange Members regarding the Observer position and are identical to the same terms for the observer positions for Company's affiliates, MIAX Emerald and MIAX Sapphire.
                    <SU>51</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>51</SU>
                         
                        <E T="03">See</E>
                         MIAX Emerald By-Laws, Article I 
                        <E T="03">and</E>
                         MIAX Sapphire By-Laws, Article I.
                    </P>
                </FTNT>
                <P>
                    The proposed terms are also similar to the corresponding terms in the MEMX LLC Agreement and MEMX Holdco LLC Agreement.
                    <SU>52</SU>
                    <FTREF/>
                     As noted above, the Company believes the slight difference between its proposal and MEMX's corporate documents, which automatically grant the right to its exchange members to appoint an observer (assuming the threshold and other requirements are met), is reasonable due to the difference in ownership structures. The Company's proposal provides that Exchange Members that meet the Observer Threshold and requirements of proposed Section 2.21, may nominate a candidate to the Member Nominating Committee for consideration as an Observer. The Company believes that this nomination structure enables the Company to be so organized as to have the capacity to be able to carry out the purposes of the Exchange Act by not granting Exchange Members the automatic right to appoint Observers; rather, those candidates must go 
                    <PRTPAGE P="41120"/>
                    through a standard nomination and election process with the Member Nominating Committee consulting with the Nominating Committee and the Chairman and Chief Executive Officer.
                </P>
                <FTNT>
                    <P>
                        <SU>52</SU>
                         
                        <E T="03">See supra</E>
                         note 12.
                    </P>
                </FTNT>
                <P>
                    The following proposed Observer provisions are all substantively similar to provisions already in the By-Laws for Directors (or committee members) and identical to the provisions in the MIAX Emerald and MIAX Sapphire By-Laws, and in place at MEMX and, therefore, will enable the Company to continue to be so organized as to have the capacity to be able to carry out the purposes of the Exchange Act: removal and resignation of Observers; 
                    <SU>53</SU>
                    <FTREF/>
                     participation by Observers at Board meetings; 
                    <SU>54</SU>
                    <FTREF/>
                    ; the ability of the Board to provide for reasonable compensation and reimbursement of expenses for Observers; 
                    <SU>55</SU>
                    <FTREF/>
                     conflicts of interest related to Observers; 
                    <SU>56</SU>
                    <FTREF/>
                     contracts and transactions with the Company that may involve Observers; 
                    <SU>57</SU>
                    <FTREF/>
                     the requirement that Observers not be affiliated with any other Director or Observer; 
                    <SU>58</SU>
                    <FTREF/>
                     term length and staggered classes for Observers; 
                    <SU>59</SU>
                    <FTREF/>
                     the nomination and election process for Observers; 
                    <SU>60</SU>
                    <FTREF/>
                     and certain rights and obligations of Observers.
                    <SU>61</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>53</SU>
                         
                        <E T="03">See supra</E>
                         notes 17 and 18.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>54</SU>
                         
                        <E T="03">See supra</E>
                         notes 19 and 33.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>55</SU>
                         
                        <E T="03">See</E>
                         By-Laws, Section 2.18.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>56</SU>
                         
                        <E T="03">See supra</E>
                         note 22.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>57</SU>
                         
                        <E T="03">See supra</E>
                         notes 22 and 23.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>58</SU>
                         
                        <E T="03">See supra</E>
                         note 27.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>59</SU>
                         
                        <E T="03">See supra</E>
                         note 28.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>60</SU>
                         
                        <E T="03">See supra</E>
                         note 31.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>61</SU>
                         
                        <E T="03">See supra</E>
                         note 33.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Proposal To Remove References to the Initial Committees and ERPs</HD>
                <P>The Company believes its proposal to amend various subparagraphs and sections of the By-Laws to delete outdated references to the initial committees and ERPs enables the Company to be so organized as to have the capacity to be able to carry out the purposes of the Exchange Act because it will remove outdated text. Pursuant to the By-Laws and prior to commencing operations, the LLC Member appointed the initial Nominating Committee and Member Nominating Committee. The initial Nominating Committee and Member Nominating Committee served until the second annual meeting of the LLC Member. Accordingly, the initial Nominating Committee and Member Nominating Committee served until their specified time expired. Both the Initial ERP and Second ERP have expired and currently there is no ERP Director or Observer appointed by an ERP Member serving on the Board. The Company further believes these proposed changes remove impediments to and perfects the mechanism of a free and open market by providing greater transparency and clarity in the Company's governing documents. It is in the public interest for the Company's By-Laws to be up-to-date and accurate, which protects investors by providing transparency and clarity, thereby reducing potential confusion.</P>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition</HD>
                <P>The Company does not believe that the proposed By-Law Amendments will impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. The proposed By-Law Amendments relate to the corporate governance of the Company and not to the Company's operations. As such, the proposed By-Law Amendments do not impact competition among the various market participants of the Company or among competing exchanges. This is not intended to address competitive issues and, therefore, imposes no burden on competition. The proposed By-Laws Amendments are also substantively similar (or identical) to the comparable by-law provisions already in place for MIAX Emerald and MIAX Sapphire.</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>Written comments were neither solicited nor received.</P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
                <P>
                    Because the foregoing proposed rule change does not (i) significantly affect the protection of investors or the public interest; (ii) impose any significant burden on competition; and (iii) become operative for 30 days after the date of the filing, or such shorter time as the Commission may designate, it has become effective pursuant to Section 19(b)(3)(A) of the Act 
                    <SU>62</SU>
                    <FTREF/>
                     and subparagraph (f)(6) of Rule 19b-4 thereunder.
                    <SU>63</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>62</SU>
                         15 U.S.C. 78s(b)(3)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>63</SU>
                         17 CFR 240.19b-4(f)(6). In addition, Rule 19b-4(f)(6)(iii) requires a self-regulatory organization to give the Commission written notice of its intent to file the proposed rule change, along with a brief description and text of the proposed rule change, at least five business days prior to the date of filing of the proposed rule change, or such shorter time as designated by the Commission. The Exchange has satisfied this requirement.
                    </P>
                </FTNT>
                <P>
                    At any time within 60 days of the filing of the proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act. If the Commission takes such action, the Commission shall institute proceedings under Section 19(b)(2)(B) 
                    <SU>64</SU>
                    <FTREF/>
                     of the Act to determine whether the proposed rule change should be approved or disapproved.
                </P>
                <FTNT>
                    <P>
                        <SU>64</SU>
                         15 U.S.C. 78s(B)(2)(B).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
                <P>Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:</P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's internet comment form (
                    <E T="03">https://www.sec.gov/rules/sro.shtml</E>
                    ); or
                </P>
                <P>
                    • Send an email to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include file number SR-PEARL-2026-29 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-PEARL-2026-29. 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-PEARL-2026-29 and should be submitted on or before July 27, 2026.
                </FP>
                <SIG>
                    <P>For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.</P>
                    <NAME>Sherry R. Haywood,</NAME>
                    <TITLE>Assistant Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13520 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="41121"/>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release No. 34-105815; File No. SR-NYSETEX-2026-27]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; NYSE Texas, Inc.; Notice of Filing and Immediate Effectiveness of Proposed Rule Change To Adopt a Policy Relating to the Exchange's Treatment of Trade Reports</SUBJECT>
                <DATE>June 30, 2026.</DATE>
                <P>
                    Pursuant to Section 19(b)(1) 
                    <SU>1</SU>
                    <FTREF/>
                     of the Securities Exchange Act of 1934 (“Act”) 
                    <SU>2</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>3</SU>
                    <FTREF/>
                     notice is hereby given that, on June 22, 2026, the NYSE Texas, Inc. (“NYSE Texas” or the “Exchange”) filed with the Securities and Exchange Commission (the “Commission”) the proposed rule change as described in Items I and II below, which Items have been prepared by the self-regulatory organization. The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         15 U.S.C. 78a.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>
                <P>
                    The Exchange proposes to adopt a policy relating to the Exchange's treatment of trade reports that it determines to be inconsistent with the prevailing market. The proposed rule change is available on the Exchange's website at 
                    <E T="03">www.nyse.com</E>
                     and at the principal office of the Exchange.
                </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <P>In its filing with the Commission, the self-regulatory organization included statements concerning the purpose of, and basis for, the proposed rule change and discussed any comments it received on the proposed rule change. The text of those statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in sections A, B, and C below, of the most significant parts of such statements.</P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and the Statutory Basis for, the Proposed Rule Change</HD>
                <HD SOURCE="HD3">1. Purpose</HD>
                <P>
                    Trades in listed securities occasionally occur at prices that deviate from prevailing market prices, and those trades sometimes establish a high, low or last sale price for a security that does not reflect its true market. The Consolidated Tape Association (“CTA”) Plan and the Nasdaq UTP Plan (“UTP Plan”) each offer participants in such plans with the discretion to append an Aberrant Report Indicator to a trade report to indicate that the market believes that the trade price of a particular trade executed on the participant's market does not accurately reflect the prevailing market for the security in question.
                    <SU>4</SU>
                    <FTREF/>
                     Several national securities exchanges, including The New York Stock Exchange (“NYSE”) 
                    <SU>5</SU>
                    <FTREF/>
                     and Nasdaq Stock Market (“Nasdaq”),
                    <SU>6</SU>
                    <FTREF/>
                     and more recently, Investors Exchange LLC (“IEX”),
                    <SU>7</SU>
                    <FTREF/>
                     have adopted policies related to use of the Aberrant Report Indicator for equities trades that, while not eligible for cancellation pursuant to applicable exchange rules governing clearly erroneous executions, are determined not to accurately reflect the prevailing market for the security in question. The Exchange believes that such policies are appropriate to identify such trades to vendors and market participants so that they may exclude such trades from relevant pricing metrics (
                    <E T="03">e.g.,</E>
                     high, low and last sale prices). Accordingly, NYSE Texas is proposing to adopt a policy substantially similar to the existing policies of such other national securities exchanges as described below.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         The CTA recommends that data recipients should exclude the price of any trade to which the Aberrant Report Indicator has been appended from any calculation of the high, low and last sale prices for the security.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 58736 (October 6, 2008), 73 FR 60380 (October 10, 2008) (SR-NYSE-2008-91).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 59151 (December 23, 2008), 74 FR 158 (January 2, 2009) (SR-NASDAQ-2008-100).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 81278 (August 1, 2017), 82 FR 36837 (August 7, 2017) (SR-IEX-2017-24).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See supra,</E>
                         notes 5-7.
                    </P>
                </FTNT>
                <P>
                    During the course of surveillance by the Exchange or as a result of notification by another market, listed company,
                    <SU>9</SU>
                    <FTREF/>
                     or market participant, the Exchange may become aware of trade prices that do not accurately reflect the prevailing market for a particular security. In such a case, the Exchange will contact the listing exchange (if the Exchange is not the listing exchange) and other markets (in the case of executions that take place across multiple markets) to seek consensus as to whether the trade price is consistent with the prevailing market for the security. If the Exchange determines that the trade price is inconsistent with the prevailing market for the security after considering the factors discussed below, the Exchange will append an Aberrant Report Indicator to the trade pursuant to applicable CTA and UTP procedures. Appending an Aberrant Report Indicator to the trade will have no effect on the validity of the underlying trade.
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         On March 28, 2025, NYSE Chicago, Inc. equities market became NYSE Texas, Inc. 
                        <E T="03">See</E>
                         Securities Exchange Act Release No.102507 (February 28, 2025), 90 FR 11445 (March 6, 2025) (SR-NYSECHX-2025-01) (Notice of Filing and Immediate Effectiveness of Proposed Rule Change To Repeal the Exchange's Certificate of Incorporation; Adopt the Certificate of Formation of NYSE Texas, Inc.; Amend the Exchange's By-Laws, Rules, and Certain Fee Schedules; and Amend the Certificate of Incorporation and By-Laws of the Exchange's Holding Company To Reflect the Conversion of the Exchange to a Texas Corporation and the Renaming of NYSE Chicago Holdings, Inc.). On April 29, 2025, the Commission approved the Exchange's proposal to adopt initial and continued listing standards to permit the listing and trading of shares of certain exchange-traded products on the Exchange. 
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 102957 (April 29, 2025), 90 FR 19054 (May 5, 2025) (SR-NYSECHX-2025-04) (Notice of Filing of Amendment No. 1, and Order Granting Accelerated Approval of a Proposed Rule Change, as Modified by Amendment No. 1, To Amend Exchange Rules 1.1, 5, 7.18, 8 and Exchange Article 22, Rules 24-27). The Exchange plans to begin a listing program for corporate securities in 2026.
                    </P>
                </FTNT>
                <P>NYSE Texas currently trades securities on an unlisted trading privilege (“UTP”) basis, that are listed on other exchanges. NYSE Texas also intends to become a primary listing exchange for corporate securities. The proposed policy would be applicable to trades that occur on NYSE Texas, whether traded on a UTP basis or listed on NYSE Texas.</P>
                <P>In making the determination to append the Aberrant Report Indicator to a particular trade, the Exchange shall consider all factors related to a trade, including, but not limited to, the following:</P>
                <P>• Material news released for the security;</P>
                <P>• Suspicious trading activity;</P>
                <P>• System malfunctions or disruptions;</P>
                <P>• Locked or crossed markets;</P>
                <P>• A recent trading halt or resumption of trading in the security;</P>
                <P>• Whether the security is in its initial public offering;</P>
                <P>• Volume and volatility for the security;</P>
                <P>• Whether the trade represents a 52-week high or low for the security;</P>
                <P>• Whether the trade price deviates significantly from recent trading patterns in the security;</P>
                <P>
                    • Whether the trade price reflects a stock-split, reorganization or other corporate action;
                    <PRTPAGE P="41122"/>
                </P>
                <P>• The validity of consolidated tape trades and quotes in comparison to national best bids and offers; and</P>
                <P>• The general volatility of market conditions.</P>
                <P>
                    In determining whether trade prices are inconsistent with the prevailing market, the Exchange proposes that its policy shall be to follow the following general guidelines: The Exchange will review whether a trade price does not reflect the prevailing market for a security if the trade occurs during regular trading hours (
                    <E T="03">i.e.,</E>
                     9:30 a.m. to 4 p.m.) and occurs at a price that deviates from the “Reference Price” by an amount that meets or exceeds the following thresholds:
                </P>
                <GPOTABLE COLS="2" OPTS="L2,nj,tp0,i1" CDEF="s25,12">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Trade price</CHED>
                        <CHED H="1">
                            Numerical
                            <LI>threshold</LI>
                            <LI>(percent)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Between $0 and $15.00 </ENT>
                        <ENT>7</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Between $15.01 and $50.00 </ENT>
                        <ENT>5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">In excess of $50.00 </ENT>
                        <ENT>3</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The “Reference Price” refers to (a) if the primary market for the security is open at the time of the trade, the national best bid or offer for the security, or (b) if the primary market for the security is not open at the time of the trade, the first executable quote or print for the security on the primary market after execution of the trade in question. However, if the circumstances suggest that a different Reference Price would be more appropriate, the Exchange will use the different Reference Price. For instance, if the national best bid and offer for the security are so wide apart as to fail to reflect the market for the security, the Exchange might use as the Reference Price a trade price or best bid or offer that was available prior to the trade in question.</P>
                <P>If NYSE Texas determines that a trade price does not reflect the prevailing market for a security and the trade represented the last sale of the security on the Exchange during a trading session, the Exchange may also determine to remove that trade's designation as the last sale and the preceding last sale eligible trade would become the new last sale. NYSE Texas may do so either on the day of the trade or at a later date, so as to provide reasonable time for the Exchange to conduct due diligence regarding the trade, including the consideration of input from markets and other market participants.</P>
                <P>
                    In connection with the proposed policy, NYSE Texas shall discourage vendors and other data recipients from using prices to which the Exchange has appended the Aberrant Report Indicator in any calculation of the high, low or last sale price of a security; and will urge vendors to disclose the exclusion from high, low or last sale price data of any trades with an Aberrant Report Indicator and exclude them from high, low or last sale price information they disseminate and to provide to data users an explanation of the parameters used in the Exchange's aberrant trade policy.
                    <SU>10</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         The Exchange will advise each listed company of the aberrant trade policy, including that any trade for which the Aberrant Report Indicator is applied will remain a valid trade.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    The Exchange believes that the proposed rule change is consistent with Section 6(b) of the Act,
                    <SU>11</SU>
                    <FTREF/>
                     in general, and furthers the objectives of Section 6(b)(5) of the Act,
                    <SU>12</SU>
                    <FTREF/>
                     in particular, in that it is designed to prevent fraudulent and manipulative acts and practices, to promote just and equitable principles of trade, to remove impediments to and perfect the mechanism of a free and open market and a national market system, and, in general, to protect investors and the public interest.
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         15 U.S.C. 78f(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <P>In particular, and as described in rule change proposals of NYSE, Nasdaq, and IEX to adopt a policy on the use of the Aberrant Report Indicator, the Exchange believes that the Aberrant Report Indicator is consistent with the protection of investors and the public interest in that the Exchange will seek to ensure a proper understanding of the Aberrant Report Indicator among securities market participants by: (i) urging vendors to disclose the exclusion from high, low or last sale price data of any aberrant trades excluded from high, low or last sale price information they disseminate and to provide to data users an explanation of the parameters used in the Exchange's aberrant trade policy; (ii) informing the affected listed company each time the Exchange or another market appends the Aberrant Report Indicator to an Exchange-listed stock; and (iii) reminding the users of the information that these are still valid trades in that they were executed and not unwound as in the case of a clearly erroneous trade.</P>
                <P>Additionally, the Exchange believes that the proposed rule change is a reasonable means to alert investors and others that the Exchange believes that the trade price for a particular trade executed in its market does not accurately reflect the prevailing market for the security. Further, the Exchange will use the same factors, including objective numerical thresholds in determining whether a trade report is eligible to have an Aberrant Trade Indictor appended to it. As discussed above, other national securities exchanges have adopted a substantially similar policy. Accordingly, the proposed rule change does not raise any new or novel issues that have not already been considered by the Commission.</P>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition</HD>
                <P>NYSE Texas does not believe that the proposed rule change will result in any burden on competition. The proposed rule change is designed to enable the Exchange to apply the Aberrant Report Indicator in a manner consistent with its existing use by other national securities exchanges, thereby increasing transparency regarding trades executed at prices that do not reflect the prevailing market, and not to address any competitive issues. The Exchange will utilize the indicator in a consistent manner with respect to all Exchange members and listed companies. The Exchange thus does not believe the proposal will burden competition because it will provide for consistency between the Exchange's policy related to use of the Aberrant Trade Indicator and those of other national securities exchanges.</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>No written comments were solicited or received with respect to the proposed rule change.</P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
                <P>
                    The Exchange has filed the proposed rule change pursuant to Section 19(b)(3)(A)(iii) of the Act 
                    <SU>13</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) thereunder.
                    <SU>14</SU>
                    <FTREF/>
                     Because the proposed rule change does not: (i) significantly affect the protection of investors or the public interest; (ii) impose any significant burden on competition; and (iii) become operative prior to 30 days from the date on which it was filed, or such shorter time as the Commission may designate, if consistent with the protection of investors and the public interest, the proposed rule change has become effective pursuant to Section 19(b)(3)(A) 
                    <PRTPAGE P="41123"/>
                    of the Act and Rule 19b-4(f)(6)(iii) thereunder.
                    <SU>15</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         15 U.S.C. 78s(b)(3)(A)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         17 CFR 240.19b-4(f)(6).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         17 CFR 240.19b-4(f)(6)(iii). In addition, Rule 19b-4(f)(6) requires a self-regulatory organization to give the Commission written notice of its intent to file the proposed rule change at least five business days prior to the date of filing of the proposed rule change, or such shorter time as designated by the Commission. The Exchange has satisfied this requirement.
                    </P>
                </FTNT>
                <P>
                    At any time within 60 days of the filing of such proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act. If the Commission takes such action, the Commission shall institute proceedings under Section 19(b)(2)(B) 
                    <SU>16</SU>
                    <FTREF/>
                     of the Act to determine whether the proposed rule change should be approved or disapproved.
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         15 U.S.C. 78s(b)(2)(B).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">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-NYSETEX-2026-27 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-NYSETEX-2026-27. 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-NYSETEX-2026-27 and should be submitted on or before July 27, 2026.
                </FP>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>17</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>17</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-13521 Filed 7-2-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-105822; File No. SR-NYSEARCA-2026-69]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; NYSE Arca, Inc.; Notice of Filing and Immediate Effectiveness of a Proposed Rule Change To Amend the Connectivity Fee Schedule</SUBJECT>
                <DATE>June 30, 2026.</DATE>
                <P>
                    Pursuant to Section 19(b)(1) 
                    <SU>1</SU>
                    <FTREF/>
                     of the Securities Exchange Act of 1934 (“Act”) 
                    <SU>2</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>3</SU>
                    <FTREF/>
                     notice is hereby given that, on June 18, 2026, NYSE Arca, Inc. (“NYSE Arca” or “Exchange”) filed with the Securities and Exchange Commission (“Commission”) the proposed rule change as described in Items I and II below, which Items have been prepared by the self-regulatory organization. The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         15 U.S.C. 78a.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>
                <P>
                    The Exchange proposes to amend the Connectivity Fee Schedule to amend the list of third party data feeds to which Users can connect. The proposed rule change is available on the Exchange's website at 
                    <E T="03">www.nyse.com</E>
                     and at the principal office of the Exchange.
                </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <P>In its filing with the Commission, the self-regulatory organization included statements concerning the purpose of, and basis for, the proposed rule change and discussed any comments it received on the proposed rule change. The text of those statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in sections A, B, and C below, of the most significant parts of such statements.</P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and the Statutory Basis for, the Proposed Rule Change</HD>
                <HD SOURCE="HD3">1. Purpose</HD>
                <P>
                    The Exchange proposes to amend the Connectivity Fee Schedule to amend the list of third party data feeds to which Users 
                    <SU>4</SU>
                    <FTREF/>
                     can connect. Currently, Users are offered connectivity to data feeds from third party markets and other content service providers (“Third Party Data Feeds”) at the Mahwah, New Jersey data center (“MDC”).
                    <SU>5</SU>
                    <FTREF/>
                     The Exchange now proposes to amend the names of the Cboe Global Markets, Inc. Third Party Data Feeds (excluding Cboe Canada) (“Cboe Data Feeds”) and incorporate a new feed from Investors Exchange LLC (“IEX”).
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         For purposes of the Exchange's colocation services, a “User” means any market participant that requests to receive colocation services directly from the Exchange. 
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 76010 (September 29, 2015), 80 FR 60197 (October 5, 2015) (SR-NYSEArca-2015-82). As specified in the Fee Schedule, a User that incurs colocation fees for a particular colocation service pursuant thereto would not be subject to colocation fees for the same colocation service charged by the New York Stock Exchange LLC, NYSE American LLC, NYSE National, Inc. and NYSE Texas, Inc. (together, the “Affiliate SROs”). Each Affiliate SRO has submitted substantially the same proposed rule change to propose the change described herein.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         Through its Fixed Income and Data Services (“FIDS”) business, Intercontinental Exchange, Inc. (“ICE”) operates the MDC. The Exchange and the Affiliate SROs are indirect subsidiaries of ICE.
                    </P>
                </FTNT>
                <P>The Exchange expects that the proposed rule change would become operative by August 31, 2026. The Exchange will announce the date through a customer notice.</P>
                <HD SOURCE="HD3">Proposed Change to the Cboe Data Feeds</HD>
                <P>
                    Currently, the Cboe Data Feeds are set forth in the list of Third Party Data Feeds by market. However, Users have requested that certain of the Cboe Data Feeds be broken out by asset class instead, so that if a User wanted all of the Cboe equities 
                    <SU>6</SU>
                    <FTREF/>
                     data, Cboe options 
                    <FTREF/>
                    <SU>7</SU>
                     data, or Cboe indices data 
                    <SU>8</SU>
                    <FTREF/>
                     it would not have to sign up for connectivity to more 
                    <PRTPAGE P="41124"/>
                    than one Third Party Data Feed.
                    <SU>9</SU>
                    <FTREF/>
                     The Exchange proposes to make the requested change and to indicate the exchanges from which data is included in the Cboe equities (“Cboe U.S. Equites”) and Cboe options (“Cboe Options”) data feeds.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         Cboe U.S. Equities | Cboe (representing the four U.S. equities exchanges that Cboe operates as BZX Equities, BYX Equities, EDGA Equities, and EDGX Equities).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         See Cboe U.S. Options | Trade Equity, Index &amp; ETF Options | Cboe (stating that the four U.S.-listed cash equity options markets that Cboe operates are the Cboe Options Exchange, the Cboe C2 Options Exchange, Cboe BZX Options Exchange, and Cboe EDGX Options Exchange).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         The Cboe indices data is set out in the Cboe Global Indices Feed. See Cboe Global Indices Feed (stating that the Cboe Global Indices Feed has more than 1,900 Index Values available).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         Currently, in order to connect to all of the Cboe U.S. Equity data feeds a User would have to connect to two Third Party Data Feeds, and to connect to all of the Cboe Options data feeds a User would have to connect to three Third Party Data Feeds. In order to connect to the Cboe indices data a User currently would have to connect to one Third Party Data Feed and the proposed change would ensure that remains true.
                    </P>
                </FTNT>
                <P>
                    The Exchange also proposes to change the name of “Cboe CFE Futures” to “Cboe Futures Exchange (CFE)” to mirror the name of Cboe Futures Exchange 
                    <SU>10</SU>
                    <FTREF/>
                     and to reorder the Cboe Data Feeds to maintain alphabetical order.
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See, e.g.,</E>
                         Exchange Act Release No. 104973 (March 11, 2026), 91 FR 12631 (March 16, 2026) (SR-CFE-2026-002) (presenting the name as “Cboe Futures Exchange, LLC,” abbreviated to “CFE”).
                    </P>
                </FTNT>
                <P>Accordingly, the Exchange proposes to make the following changes to the Cboe Data Feeds listed under “Connectivity to Third Party Data Feeds” (proposed additions italicized, proposed deletions in brackets):</P>
                <GPOTABLE COLS="2" OPTS="L2,nj,tp0,i1" CDEF="s100,17">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Third party data feed</CHED>
                        <CHED H="1">
                            Monthly recurring
                            <LI>connectivity fee</LI>
                            <LI>per third party</LI>
                            <LI>data feed</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">[Cboe BZX Exchange (CboeBZX) and Cboe BYX Exchange (CboeBYX)]</ENT>
                        <ENT>[$1,500]</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Cboe Canada</ENT>
                        <ENT>2,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Cboe [CFE] Futures 
                            <E T="03">Exchange (CFE)</E>
                        </ENT>
                        <ENT>1,500</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            <E T="03">Cboe Global Indices Feed</E>
                        </ENT>
                        <ENT>
                            <E T="03">1,500</E>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Cboe 
                            <E T="03">Options</E>
                            [EDGX] Exchange
                            <E T="03">s</E>
                             (
                            <E T="03">Cboe Options Exchange, Cboe C2 Options Exchange, Cboe BZX Options Exchange, and</E>
                             Cboe EDGX
                            <E T="03"> Options Exchange</E>
                            ) [and Cboe EDGA Exchange (CboeEDGA)]
                        </ENT>
                        <ENT>1,500</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Cboe 
                            <E T="03">U.S Equities</E>
                             Exchange
                            <E T="03">s</E>
                             (Cboe 
                            <E T="03">EDGA Equities, Cboe EDGX Equities, Cboe BYX Equities and Cboe BZX Equities</E>
                            ) [and C2 Exchange (C2)]
                        </ENT>
                        <ENT>1,500</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD3">Proposed Change to the IEX Third Party Data Feed</HD>
                <P>
                    IEX has announced that it will launch a new options exchange (“IEX Options”) 
                    <SU>11</SU>
                    <FTREF/>
                     and that it intends to launch IEX Options on October 2, 2026.
                    <SU>12</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See</E>
                         “IEX Announces Planned Launch of Options Exchange End of Q1 2026,” available at 
                        <E T="03">https://www.iex.io/article/iex-announces-planned-launch-of-options-exchange-end-of-q1-2026.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">See</E>
                         “IEX Options Frequently Asked Questions,” question 1, available at 
                        <E T="03">https://cdn.prod.website-files.com/696f8ac812dcabe749e3aa49/69d7ddd79256713d06405c46_IEX%20Options%20FAQs.pdf.</E>
                         The proposed rule change is proposed to become operative before IEX offers IEX Options in order to allow Users time to connect, and test their connection, to IEX Options. The Exchange does not plan to charge for the connection until the IEX Options Third Party Data Feed is available.
                    </P>
                </FTNT>
                <P>So that the Exchange may both offer connectivity to IEX Options and distinguish between IEX Options and the existing IEX equities exchange (“IEX Equities”), it proposes to make the following changes to the list of available Third Party Data Feeds (proposed additions italicized):</P>
                <GPOTABLE COLS="2" OPTS="L2,nj,tp0,i1" CDEF="s100,17">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Third party data feed</CHED>
                        <CHED H="1">
                            Monthly recurring
                            <LI>connectivity fee</LI>
                            <LI>per third party</LI>
                            <LI>data feed</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">
                            Investors Exchange (IEX) 
                            <E T="03">Equities</E>
                        </ENT>
                        <ENT>$1,300</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            <E T="03">Investors Exchange (IEX) Options</E>
                        </ENT>
                        <ENT>
                            <E T="03">1,300</E>
                        </ENT>
                    </ROW>
                </GPOTABLE>
                <P>The Exchange would provide connectivity to IEX Options as a convenience to Users.</P>
                <P>As with the existing connections to Third Party Data Feeds, including the existing connections to Cboe Data Feeds and to the IEX Equities data feed, the Exchange would receive a connection to the IEX Options data feed (the “Proposed Third Party Data Feed”) from the content service provider at the relevant source. The Exchange would then provide connectivity to that data to Users for a fee. Users would connect to IEX Options over the internet protocol (“IP”) network, a local area network available in the MDC. The Proposed Third Party Data Feed would include trading and other information concerning the securities that are traded on IEX Options.</P>
                <P>As with the existing connections to Third Party Data Feeds, including the existing connection to Cboe Data Feeds and the IEX Equities data feed, in order to connect to a Proposed Third Party Data Feed, a User would enter into a contract with the third party content service provider, pursuant to which it may charge the User for the data feed. The Exchange would receive the Proposed Third Party Data Feed in remote locations and transport it over its fiber optic network to the MDC. After the content service provider and User entered into an agreement and the Exchange received authorization from the content service provider, the Exchange would retransmit the data to the User over the User's port. The Exchange would charge the User for connectivity to the Proposed Third Party Data Feed. A User would only receive, and would only be charged the fee for, connectivity to a Proposed Third Party Data Feed for which it entered into a contract.</P>
                <P>The Exchange has no affiliation with the seller of the Proposed Third Party Data Feed and would have no right to use the feed other than as a redistributor of the data. The Proposed Third Party Data Feed would not provide access or order entry to the Exchange's execution system. The Proposed Third Party Data Feed would not provide access or order entry service to the execution systems of any third party generating the feed. The Exchange would receive the Proposed Third Party Data Feed via arms-length agreements and would have no inherent advantage over any other distributor of such data.</P>
                <HD SOURCE="HD3">Application and Impact of the Proposed Changes</HD>
                <P>
                    The proposed rule change would not apply differently to distinct types or 
                    <PRTPAGE P="41125"/>
                    sizes of market participants. Rather, it would apply to all Users equally. As is currently the case, the purchase of any colocation service is completely voluntary and the Connectivity Fee Schedule is applied uniformly to all Users.
                </P>
                <P>Users have requested that certain of the Cboe Data Feeds be broken out by asset class, instead of by market. The Exchange believes that one current User would benefit from the change. It does not expect to gain customers as a result of breaking out certain of the Cboe Data Feeds by asset class or the other proposed changes to the Cboe Data Feeds.</P>
                <P>Connectivity to the Proposed Third Party Data Feed was requested by Users, but the Exchange believes that it would gain at most a handful of new customers due to the proposed change to the IEX data feeds.</P>
                <HD SOURCE="HD3">Competitive Environment</HD>
                <P>
                    The Exchange operates in a highly competitive market in which other vendors offer colocation services as a means to facilitate the trading and other market activities of those market participants who believe that colocation enhances the efficiency of their operations. The Commission has repeatedly expressed its preference for competition over regulatory intervention in determining prices, products, and services in the securities markets. Specifically, in Regulation NMS, the Commission highlighted the importance of market forces in determining prices and SRO revenues and, also, recognized that current regulation of the market system “has been remarkably successful in promoting market competition in its broader forms that are most important to investors and listed companies.” 
                    <SU>13</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 51808 (June 9, 2005), 70 FR 37496, 37499 (June 29, 2005).
                    </P>
                </FTNT>
                <P>As explained below, the Exchange's provision of connectivity to the Proposed Third Party Data Feed (“Connectivity”) may compete with connectivity provided by other third parties. Third-party vendors are not at any competitive disadvantage created by the Exchange.</P>
                <P>The proposed change is not otherwise intended to address any other issues relating to colocation services or related fees, and the Exchange is not aware of any problems that Users would have in complying with the proposed change.</P>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    The Exchange believes that the proposed rule change is consistent with Section 6(b) of the Act,
                    <SU>14</SU>
                    <FTREF/>
                     in general, and furthers the objectives of Section 6(b)(5) of the Act,
                    <SU>15</SU>
                    <FTREF/>
                     in particular, because it is designed to prevent fraudulent and manipulative acts and practices, to promote just and equitable principles of trade, to foster cooperation and coordination with persons engaged in regulating, clearing, settling, processing information with respect to, and facilitating transactions in securities, to remove impediments to and perfect the mechanism of a free and open market and a national market system, and, in general, to protect investors and the public interest and because it is not designed to permit unfair discrimination between customers, issuers, brokers, or dealers. The Exchange further believes that the proposed rule change is consistent with Section 6(b)(4) of the Act,
                    <SU>16</SU>
                    <FTREF/>
                     because it provides for the equitable allocation of reasonable dues, fees, and other charges among its members and issuers and other persons using its facilities.
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         15 U.S.C. 78f(b).0 [sic]
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         15 U.S.C. 78f(b)(4).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">The Proposed Rule Change Is Reasonable</HD>
                <P>The Exchange believes that the proposed rule change is reasonable.</P>
                <P>
                    In considering the reasonableness of proposed services and fees, the Commission's market-based test considers “whether the exchange was subject to significant competitive forces in setting the terms of its proposal . . . , including the level of any fees.” 
                    <SU>17</SU>
                    <FTREF/>
                     If the Exchange meets that burden, “the Commission will find that its proposal is consistent with the Act unless `there is a substantial countervailing basis to find that the terms' of the proposal violate the Act or the rules thereunder.” 
                    <SU>18</SU>
                    <FTREF/>
                     Here, the Exchange is subject to significant competitive forces in setting the terms on which it offers its proposal, in particular because substantially similar substitutes are available and the Exchange has not placed present or future third party vendors at a competitive disadvantage created by the Exchange.
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 90209 (October 15, 2020), 85 FR 67044, 67049 (October 21, 2020) (Order Granting Accelerated Approval to Establish a Wireless Fee Schedule Setting Forth Available Wireless Bandwidth Connections and Wireless Market Data Connections) (SR-NYSE-2020-05, SR-NYSEAMER-2020-05, SR-NYSEARCA-2020-08, SR-NYSECHX-2020-02, SR-NYSENAT-2020-03, SR-NYSE-2020-11, SR-NYSEAMER-2020-10, SR-NYSEArca-2020-15, SR-NYSECHX-2020-05, SR-NYSENAT-2020-08) (“Wireless Approval Order”), citing Securities Exchange Act Release No. 59039 (December 2, 2008), 73 FR 74770, 74781 (December 9, 2008) (“2008 ArcaBook Approval Order”). 
                        <E T="03">See NetCoalition</E>
                         v. 
                        <E T="03">SEC,</E>
                         615 F.3d 525 (D.C. Cir. 2010).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         
                        <E T="03">See</E>
                         Wireless Approval Order, 
                        <E T="03">supra</E>
                         note 17, at 67049, citing 2008 ArcaBook Approval Order, 
                        <E T="03">supra</E>
                         note 17, at 74781.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Substantially Similar Substitutes Are Available</HD>
                <P>
                    As described above,
                    <SU>19</SU>
                    <FTREF/>
                     Users may connect to the Proposed Third Party Data Feed independent of the options provided by the Exchange, creating competition for the Exchange's proposed Connectivity. A User may connect to a Proposed Third Party Data Feed by, first, entering into an agreement with the relevant third party for connectivity, and second, connecting to the Proposed Third Party Data Feed through one of the Telecoms. Users that establish access or connectivity independent of the Connectivity offered by the Exchange are not at any competitive disadvantage created by the Exchange. As of April 30, 2026, more than 98% of the circuits for which Users contracted were supplied by the Telecoms. Although IEX Options does not currently offer the Proposed Third Party Data Feed, the Exchange believes that once it is available, Users may independently establish connectivity to the Proposed Third Party Data Feed through one of the Telecoms.
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         
                        <E T="03">See</E>
                         “Competitive Environment,” above.
                    </P>
                </FTNT>
                <P>
                    Because Users are third parties and are not required to make such information public, the Exchange does not have visibility into how many Users will connect to the Proposed Third Party Data Feed (once it becomes available) independently, as described above.
                    <SU>20</SU>
                    <FTREF/>
                     However, the market for connectivity to the Proposed Third Party Data Feed is competitive, and there is no reason to believe that other actual or potential Users would not obtain connectivity independently if they considered it to be in their commercial interest.
                </P>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         As they are third parties, the Exchange does not have visibility into whether Users intend to connect to the Proposed Third Party Data Feed (once it is available) for their own use, or if they intend to offer other Users such connectivity.
                    </P>
                </FTNT>
                <P>
                    Such Users compete, or would compete, with the Exchange's Connectivity and exert, or would exert, significant competitive forces on the Exchange in setting the terms of its proposal, including the level of the Exchange's proposed fees.
                    <SU>21</SU>
                    <FTREF/>
                     If the Exchange were to set its proposed fees too high, Users could respond by instead selecting other substantially similar access and connectivity by 
                    <PRTPAGE P="41126"/>
                    independently establishing access and connectivity as described above.
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         
                        <E T="03">See</E>
                         2008 ArcaBook Approval Order, 
                        <E T="03">supra</E>
                         note 17, at 74789 and n.295 (recognizing that products need not be identical to be substitutable).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Users Are Not at a Competitive Disadvantage Created by the Exchange</HD>
                <P>The Exchange does not believe that FIDS would have any competitive advantage over Users that establish independent connectivity to the Proposed Third Party Data Feed. The Exchange's proposed service for Connectivity does not have (a) any special access to the Proposed Third Party Data Feeds or (b) advantage within the MDC, as all distances in the MDC are normalized.</P>
                <P>Moreover, the Exchange does not believe that FIDS would have any competitive advantage because it would charge for connectivity only, not the Proposed Third Party Data Feed itself. All Users that connect to the Proposed Third Party Data Feed, whether they elect to connect using the Exchange's proposed service or not, would have to pay a third party for the Proposed Third Party Data Feed.</P>
                <P>
                    Nor does the Exchange believe that FIDS has a competitive advantage by virtue of the fact that ICE owns and operates the MDC's meet-me-rooms. Users purchasing Connectivity—like Users of any other colocation service—would require a circuit connecting out of the MDC, and in most cases, such circuits are provided by Telecoms.
                    <SU>22</SU>
                    <FTREF/>
                     Currently, 17 Telecoms operate in the meet-me-rooms and provide a variety of circuit choices. It is in the Exchange's best interest to set the fees that Telecoms pay to operate in the meet-me-rooms at a reasonable level 
                    <SU>23</SU>
                    <FTREF/>
                     so that market participants, including Telecoms, will maximize their use of the MDC. By setting the meet-me-room fees at a reasonable level, the Exchange encourages Telecoms to participate in the meet-me-rooms and to sell circuits to Users for connecting into and out of the MDC. These Telecoms then compete with each other by pricing such circuits at competitive rates. These competitive rates for circuits help draw in more Users and Hosted Customers to the MDC, which directly benefits the Exchange by increasing the customer base to whom the Exchange can sell its colocation services, which include cabinets, power, ports, and connectivity to many third-party data feeds, and because having more Users and Hosted Customers leads, in many cases, to greater participation on the Exchange. In this way, by setting the meet-me-room fees at a level attractive to telecommunications firms, the Exchange spurs demand for all of the services it sells at the MDC, while setting the meet-me-room fees too high would negatively affect the Exchange's ability to sell its services at the MDC.
                    <SU>24</SU>
                    <FTREF/>
                     Accordingly, there are real constraints on the meet-me-room fees the Exchange charges, such that the Exchange does not have an advantage in terms of costs when compared to third parties that enter the MDC through the meet-me-rooms to provide services to compete with the Exchange's services.
                </P>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         Note that in the case of wireless connectivity, a User in colocation still requires a fiber circuit to transport data. If a Telecom is used, the data is transmitted wirelessly to the relevant pole, and then from the pole to the meet-me-room using a fiber circuit.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 98000 (July 26, 2023), 88 FR 50244 (August 1, 2023) (SR-NYSEArca-2023-47) (“MMR Notice”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         
                        <E T="03">See id.</E>
                         at 50246. Importantly, the Exchange is prevented from making any alteration to its meet-me-room services or fees without filing a proposal for such changes with the Commission.
                    </P>
                </FTNT>
                <P>If anything, the Exchange would be subject to a competitive disadvantage vis-à-vis Users regarding connectivity to the Proposed Third Party Data Feed. Users that choose to independently establish connectivity may negotiate terms with the Telecoms through whom such connectivity is delivered, in response to competitive forces. Such prices are not required to be filed by any party with the Commission. In contrast, the Exchange's service and pricing would be standardized as set out in this filing, and the Exchange would be unable to respond to pricing pressure from its competitors without seeking a formal fee change in a filing before the Commission.</P>
                <P>
                    In sum, because the Exchange is subject to significant competitive forces in setting the terms on which it offers its proposal, in particular because the Exchange believes that a substantially similar substitute is available, and the Exchange has not placed actual or proposed Users that already have or establish connectivity at a competitive disadvantage created by the Exchange, the proposed fee for the Exchange's access to the Proposed Third Party Data Feed is reasonable.
                    <SU>25</SU>
                    <FTREF/>
                     If the Exchange were to set its prices for connectivity to the Proposed Third Party Data Feeds at a level that Users found to be too high, Users could easily choose to connect to the Proposed Third Party Data Feed through Telecoms, as detailed above.
                </P>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         
                        <E T="03">See</E>
                         Wireless Approval Order, 
                        <E T="03">supra</E>
                         note 17.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Additional Considerations</HD>
                <P>
                    The Exchange believes that the proposed changes to the Cboe Data Feeds are reasonable. Specifically, the Exchange believes that the proposed changes are a reasonable response to the request from Users that certain Cboe Data Feeds be broken out by asset class, instead of by market. Under the proposed change, if a User wanted all Cboe U.S. Equities data, Cboe Options data or Cboe indices data it would not have to sign up for connectivity to more than one Third Party Data Feed. The Exchange believes that changing the placement of the “CFE” in, and adding the word “Exchange” to, Cboe Futures Exchange would be reasonable, given that the resulting change would mirror the name of the Cboe Futures Exchange.
                    <SU>26</SU>
                    <FTREF/>
                     The monthly recurring connectivity fees for each Cboe Data Feed would remain the same as they are now.
                </P>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         
                        <E T="03">See supra</E>
                         note 10.
                    </P>
                </FTNT>
                <P>Additionally, as with the Proposed Third Party Data Feed, Users may connect to the Cboe Data Feeds independent of the options provided by the Exchange, creating competition for the Exchange's proposed Connectivity. A User may connect to a Cboe Data Feed by, first, entering into an agreement with the relevant third party for connectivity, and second, connecting to the Cboe Data Feed through one of the Telecoms.</P>
                <P>The Exchange believes that the proposed fee for the Proposed Third Party Data Feed is reasonable, as it is the same as the existing fee for connectivity to IEX, which encompasses IEX Equities only. The Exchange believes that adding “Equities” after the existing text for connectivity to the IEX feed is reasonable, as it would clarify which IEX data feed was referenced.</P>
                <HD SOURCE="HD3">The Proposed Rule Change Is Equitable</HD>
                <P>The Exchange believes that the proposed rule change is equitable.</P>
                <P>The Exchange believes that the proposed changes to the Cboe Data Feeds is equitable because the monthly recurring connectivity fee for each Cboe Data Feed would remain the same as it is now. However, under the proposed change, if a User wanted all Cboe U.S. Equities data, Cboe Options data or Cboe indices data it would not have to sign up for connectivity to more than one Third Party Data Feed.</P>
                <P>
                    The Exchange believes that changing the placement of the “CFE” in, and adding “Exchange” to, Cboe Futures Exchange would be equitable, given that the resulting change would mirror the name of the Cboe Futures Exchange.
                    <SU>27</SU>
                    <FTREF/>
                     The proposed changes would make the Fee Schedule easier to read and understand and alleviate any possible market participant confusion caused by the current text.
                </P>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <PRTPAGE P="41127"/>
                <P>For the same reason, the Exchange believes that adding “Equities” after the existing text for connectivity to the IEX feed is equitable, as it would clarify which IEX data feed was referenced, therefore making the Fee Schedule easier to read and understand and alleviating any possible market participant confusion caused by the current text.</P>
                <P>The Exchange believes that the proposed fee for connectivity to the Proposed Third Party Data Feed is an equitable allocation of fees. The proposed fee is the same as the existing fee for connectivity to IEX Equities.</P>
                <P>Without this proposed rule change, Users would have fewer options for connectivity to the Proposed Third Party Data Feed, once that feed becomes available. By offering Connectivity, the Exchange gives each User additional options for addressing its needs, responding to User demand for options. Offering these additional services would help each User tailor its data center operations to the requirements of its business operations by allowing it to select the form and latency of connectivity that best suits its needs. Users that do not opt to utilize the Exchange's proposed Connectivity would still be able to connect to the Proposed Third Party Data Feed using Telecoms.</P>
                <P>The Exchange believes that the proposed change is equitable because it will result in fees being charged only to Users that voluntarily select to receive the corresponding services and because those services will be available to all Users.</P>
                <P>
                    Furthermore, the Exchange believes that the services and fees proposed herein are equitably allocated because, in addition to the services being completely voluntary, they are available to all Users on an equal basis (
                    <E T="03">i.e.,</E>
                     the same products and services are available to all Users). All Users that voluntarily select the Exchange's Connectivity would be charged the same amount for the same services. Users who opt not to use Connectivity would not be charged. In this way, the proposed rule change equitably allocates the proposed fees only to Users who choose to use the Exchange's Connectivity.
                </P>
                <HD SOURCE="HD3">The Proposed Change Is Not Unfairly Discriminatory</HD>
                <P>The Exchange believes that the proposed rule change is not unfairly discriminatory, for the following reasons.</P>
                <P>The Exchange believes that the proposed changes to the Cboe Data Feeds are not unfairly discriminatory because the monthly recurring connectivity fee for each Cboe Data Feed would remain the same as they are now. However, under the proposed change, if a User wanted all Cboe U.S. Equities data, Cboe Options data or Cboe indices data it would not have to sign up for connectivity to more than one Third Party Data Feed.</P>
                <P>Without this proposed rule change, Users would have fewer options for connectivity to the Proposed Third Party Data Feed. The proposed change would provide Users with an additional choice with respect to the form and optimal latency of their connectivity to the Proposed Third Party Data Feed, allowing a User to select the connectivity that better suits its needs, helping it tailor its colocation operations to the requirements of its business operations. Users that do not opt to utilize the Exchange's proposed Connectivity would still be able to connect to the Proposed Third Party Data Feed using Telecoms.</P>
                <P>
                    The Exchange believes that the proposed change is not unfairly discriminatory because it will result in fees being charged only to Users that voluntarily select to receive the corresponding services and because those services will be available to all Users. Furthermore, the Exchange believes that the services and fees proposed herein are not unfairly discriminatory because, in addition to the services being completely voluntary, they are available to all Users on an equal basis (
                    <E T="03">i.e.,</E>
                     the same products and services are available to all Users). All Users that voluntarily select the Exchange's Connectivity would be charged the same amount for the same services.
                </P>
                <P>For all these reasons, the Exchange believes that the proposal is consistent with the Act.</P>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition</HD>
                <P>
                    In accordance with Section 6(b)(8) of the Act,
                    <SU>28</SU>
                    <FTREF/>
                     the Exchange believes that the proposed rule change will not impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. The proposed change would not affect competition among national securities exchanges or among members of the Exchange, but rather between FIDS and its commercial competitors.
                </P>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         15 U.S.C. 78f(b)(8).
                    </P>
                </FTNT>
                <P>The Exchange does not believe that the proposed rule change regarding Cboe Data Feeds will impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. The monthly recurring connectivity fee for each Cboe Data Feed would remain the same as it is now. However, under the proposed change, if a User wanted all Cboe U.S. Equities data, Cboe Options data or Cboe indices data it would not have to sign up for connectivity to more than one Third Party Data Feed. The other changes to the Cboe Data Feeds would not affect competition.</P>
                <P>By offering Connectivity, the Exchange would give each User additional options for addressing its needs, responding to User demand for options. Providing additional services would help each User tailor its data center operations to the requirements of its business operations by allowing it to select the form and latency of connectivity that best suits its needs. Users that do not opt to utilize the Exchange's proposed Connectivity would still be able to connect to the Proposed Third Party Data Feed using Telecoms.</P>
                <P>The Exchange does not believe that FIDS would have any competitive advantage over Users that establish independent connectivity to the Proposed Third Party Data Feed. The Exchange's proposed service for Connectivity does not have (a) any special access to the Proposed Third Party Data Feed or (b) advantage within the MDC, as all distances in the MDC are normalized.</P>
                <P>Moreover, the Exchange does not believe that FIDS would have any competitive advantage because it would charge for connectivity only, not the Proposed Third Party Data Feed itself. All Users that connect to the Proposed Third Party Data Feed, whether they elect to connect using the Exchange's proposed service or not, would have to pay a third party for the Proposed Third Party Data Feed.</P>
                <P>
                    Nor does the Exchange believe that FIDS has a competitive advantage over any third-party competitors offering connectivity by virtue of the fact that ICE owns and operates the MDC's meet-me-rooms. Users purchasing Connectivity—like Users of any other colocation service—would require a circuit connecting out of the MDC, and in most cases, such circuits are provided by third-party Telecoms. Currently, 17 Telecoms operate in the meet-me-rooms and provide a variety of circuit choices. It is in the Exchange's best interest to set the fees that Telecoms pay to operate in the meet-me-rooms at a reasonable level 
                    <SU>29</SU>
                    <FTREF/>
                     so that market participants, including Telecoms, will maximize their use of the MDC. By setting the meet-me-room fees at a reasonable level, 
                    <PRTPAGE P="41128"/>
                    the Exchange encourages Telecoms to participate in the meet-me-rooms and to sell circuits to Users for connecting into and out of the MDC. These Telecoms then compete with each other by pricing such circuits at competitive rates. These competitive rates for circuits help draw in more Users and Hosted Customers to the MDC, which directly benefits the Exchange by increasing the customer base to whom the Exchange can sell its colocation services, which include cabinets, power, ports, and connectivity to many third-party data feeds, and because having more Users and Hosted Customers leads, in many cases, to greater participation on the Exchange. In this way, by setting the meet-me-room fees at a level attractive to telecommunications firms, the Exchange spurs demand for all of the services it sells at the MDC, while setting the meet-me-room fees too high would negatively affect the Exchange's ability to sell its services at the MDC.
                    <SU>30</SU>
                    <FTREF/>
                     Accordingly, there are real constraints on the meet-me-room fees the Exchange charges, such that the Exchange does not have an advantage in terms of costs when compared to third parties that enter the MDC through the meet-me-rooms to provide services to compete with the Exchange's services.
                </P>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         
                        <E T="03">See</E>
                         MMR Notice, 
                        <E T="03">supra</E>
                         note 23.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         
                        <E T="03">See supra</E>
                         note 24.
                    </P>
                </FTNT>
                <P>If anything, the Exchange would be subject to a competitive disadvantage vis-à-vis Users regarding connectivity to the Proposed Third Party Data Feed. Users that choose to independently establish connectivity may negotiate terms with the Telecoms or other Users through whom such connectivity is delivered, in response to competitive forces. Such prices are not required to be filed by any party with the Commission. In contrast, the Exchange's service and pricing would be standardized as set out in this filing, and the Exchange would be unable to respond to pricing pressure from its competitors without seeking a formal fee change in a filing before the Commission.</P>
                <P>The changes would not put any market participants at a relative disadvantage compared to other market participants or penalize one or more categories of market participants in a manner that would impose an undue burden on competition.</P>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants, or Others</HD>
                <P>No written comments were solicited or received with respect to the proposed rule change.</P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
                <P>
                    The Exchange has filed the proposed rule change pursuant to Section 19(b)(3)(A)(iii) of the Act 
                    <SU>31</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) thereunder.
                    <SU>32</SU>
                    <FTREF/>
                     Because the proposed rule change does not: (i) significantly affect the protection of investors or the public interest; (ii) impose any significant burden on competition; and (iii) become operative prior to 30 days from the date on which it was filed, or such shorter time as the Commission may designate, if consistent with the protection of investors and the public interest, the proposed rule change has become effective pursuant to Section 19(b)(3)(A) of the Act 
                    <SU>33</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) 
                    <SU>34</SU>
                    <FTREF/>
                     thereunder.
                </P>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         15 U.S.C. 78s(b)(3)(A)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         17 CFR 240.19b-4(f)(6).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         15 U.S.C. 78s(b)(3)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         17 CFR 240.19b-4(f)(6). In addition, Rule 19b-4(f)(6) requires a self-regulatory organization to give the Commission written notice of its intent to file the proposed rule change, along with a brief description and text of the proposed rule change, at least five business days prior to the date of filing of the proposed rule change, or such shorter time as designated by the Commission. The Exchange has satisfied this requirement.
                    </P>
                </FTNT>
                <P>
                    At any time within 60 days of the filing of such proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act. If the Commission takes such action, the Commission shall institute proceedings under Section 19(b)(2)(B) 
                    <SU>35</SU>
                    <FTREF/>
                     of the Act to determine whether the proposed rule change should be approved or disapproved.
                </P>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         15 U.S.C. 78s(b)(2)(B).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
                <P>Interested persons are invited to submit written data, views and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:</P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's internet comment form (
                    <E T="03">https://www.sec.gov/rules/sro.shtml</E>
                    ); or
                </P>
                <P>
                    • Send an email to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include file number SR-NYSEARCA-2026-69  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-NYSEARCA-2026-69. 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-NYSEARCA-2026-69 and should be submitted on or before July 27, 2026.
                </FP>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>36</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>36</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-13528 Filed 7-2-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-105817; File No. SR-NSCC-2026-009]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; National Securities Clearing Corporation; Notice of Filing of Proposed Rule Change To Enhance the Supplemental Liquidity Deposit Rules, Methodology and Processes</SUBJECT>
                <DATE>June 30, 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 18, 2026, National Securities Clearing Corporation (“NSCC”) 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 
                    <PRTPAGE P="41129"/>
                    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 amendments to the NSCC Rules &amp; Procedures (“NSCC Rules”) to enhance NSCC's Supplemental Liquidity Deposit (“SLD”) rules, methodology and processes (“SLD Rules”).
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         Capitalized terms not defined herein shall have the meaning assigned to such terms in the NSCC Rules, 
                        <E T="03">available at www.dtcc.com/legal/rules-and-procedures.</E>
                    </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 of Proposed Changes</HD>
                <P>
                    The proposed rule change would (i) standardize the netting methodology and processes used by NSCC to project its intraday liquidity needs and determine intraday SLD Obligations; 
                    <SU>4</SU>
                    <FTREF/>
                     (ii) provide a more detailed description of the factors considered by NSCC when projecting its intraday liquidity needs and determining intraday SLD Obligations; (iii) modify the NSCC Rules for determining the pro rata allocation of SLD Obligations across Supplemental Liquidity Providers when more than one Member is driving NSCC's liquidity needs; (iv) codify existing obligations for Members to provide reporting and information to NSCC regarding anticipated trading and settlement activity that would impact NSCC's liquidity needs; and (v) make other clarifying and cleanup changes to Rule 4A.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         As part of the proposed rule change, NSCC would adopt a new defined term, “SLD Obligation,” to mean, on any Business Day, the amount of SLD required to be provided by a Supplemental Liquidity Provider as determined by NSCC in accordance with Rule 4A (Supplemental Liquidity Deposits). The proposed changes to defined terms in Rule 4A are discussed in further detail below.
                    </P>
                </FTNT>
                <P>First, the proposed rule change would enhance the NSCC Rules to provide Members with a clearer understanding of NSCC's methodology for calculating its intraday liquidity needs and any resulting SLD Obligations. More specifically, the proposed rule change would standardize the way NSCC calculates Intraday Supplemental Liquidity Calls (or intraday SLD Obligations, as proposed herein) by using a more precise netting methodology based on Members' current positions for all of NSCC's intraday SLD calculations, regardless of the point in time within or outside of any options expiration cycle. The proposed netting methodology would more closely align with the netting methodology used for NSCC's start-of-day (“SOD”) liquidity need calculations, which uses open NSCC positions, rather than using an estimated netting percentage for the first business day of every options expiry period. NSCC believes the proposed netting changes would result in more accurate estimations of the actual liquidity exposures of each Member and would therefore result in more accurate SLD Obligations for Members.</P>
                <P>
                    The proposed rule change is also intended to improve Members' understanding of NSCC's intraday SLD calculation methodology by providing additional details regarding the factors (in addition to netting) that NSCC takes into consideration when projecting liquidity needs and determining SLD Obligations. For example, the proposed rules would describe how NSCC incorporates projected or anticipated trading or settlement activity reported to NSCC by Members, The Options Clearing Corporation (“OCC”),
                    <SU>5</SU>
                    <FTREF/>
                     trade matching platforms, and Index Receipt Agents into its projected Daily Liquidity Need 
                    <SU>6</SU>
                    <FTREF/>
                     determinations, as well as consideration of potential offsets from anticipated deliveries from a Member's free inventory at The Depository Trust Company (“DTC”). The proposed rule change would also describe additional adjustments that NSCC may make to its intraday SLD Obligation determinations to ensure coverage of NSCC's liquidity risk tolerance, which is designed to account for potential variations between NSCC's intraday liquidity projections and its final simulated liquidity needs on Settlement Date.
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         OCC and NSCC are parties to the Amended and Restated Stock Options and Futures Settlement Agreement, which provides for the clearance and settlement of exercises and assignments of options on eligible securities or the maturity of eligible stock futures contracts through NSCC (“OCC E&amp;A Activity”). Each business day, NSCC receives information from OCC regarding projected OCC E&amp;A Activity to inform NSCC's liquidity risk projections (“E&amp;A Projection Files”). 
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 99733 (Mar. 14, 2024), 89 FR 19896 (Mar. 20, 2024) (SR-NSCC-2023-007).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         Daily Liquid Need is currently defined as the payment obligations of NSCC as a central counterparty, as calculated and determined by NSCC, for all projected same day, intraday and multiday settlement activity (where appropriate), assuming the default on that day of an Unaffiliated Member/Affiliated Family. 
                        <E T="03">See</E>
                         NSCC Rule 4A, Section 2, 
                        <E T="03">supra</E>
                         note 3.
                    </P>
                </FTNT>
                <P>In addition, to the changes related to intraday liquidity needs and SLD Obligations, the proposal would make other enhancements to Rule 4A related to the operation of the SLD Rules. First, the proposed rule change would enhance Rule 4A concerning the pro rata allocation of SLD Obligations to limit excess liquidity and funding burdens on NSCC's Members. Specifically, NSCC would eliminate the $2 billion threshold for pro rata allocations and apply a standardized pro rata allocation approach to both SOD and intraday SLD Obligations.</P>
                <P>Second, the proposed rule change would codify obligations for Members to (i) provide additional reports and information concerning anticipated trading and settlement activity, as deemed necessary or advisable by NSCC to support NSCC's liquidity projections; (ii) track settlement activities that generate liquidity needs across all trading desks, systems or platforms and manage their liquidity needs; (iii) notify NSCC of anticipated significant changes in such activity; and (iv) identify to NSCC contact persons responsible for responding to NSCC's inquiries concerning settlement activity and liquidity management.</P>
                <P>Finally, the proposed rule change would make organizational and drafting improvements to Rule 4A to more clearly and concisely describe NSCC's methodology and processes for determining SLD Obligations on an SOD and intraday basis, modify the process for returning excess SLD amounts to Members, and make other clarifying, organizational and cleanup changes to Rule 4A.</P>
                <P>
                    Collectively, the proposed rule changes set forth in this proposal reflect NSCC's ongoing efforts to enhance its ability to monitor and assess its liquidity needs. By describing the various factors NSCC considers when projecting liquidity needs, the proposed changes would support NSCC's ability to collect sufficient liquidity resources to effect settlement of its payment obligations in the event of a Member default as required by Rule 17ad-
                    <PRTPAGE P="41130"/>
                    22(e)(7) under the Act.
                    <SU>7</SU>
                    <FTREF/>
                     The proposed rule change would also provide additional details in the NSCC Rules for Members and the public to improve their understanding of NSCC's SLD methodology and better anticipate Members' obligations related to liquidity risk management.
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         Rule 17ad-22(e)(7) under the Act requires, among other things, that NSCC maintains 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 plausible market conditions (generally referred to as a “Cover 1” standard or requirement). 
                        <E T="03">See</E>
                         17 CFR 240.17ad-22(e)(7).
                    </P>
                </FTNT>
                <P>
                    NSCC believes the proposed changes would result in more accurate projections of NSCC's actual liquidity needs on an intraday basis. NSCC notes that, with respect to the proposed rule changes related to the pro rata allocation of SLD Obligations, the total SLD collected would be equal to the amount of the largest daily liquidity shortfall, pro-rated among those Members that observed a liquidity shortfall. As a result, NSCC would continue to collect qualifying liquid resources 
                    <SU>8</SU>
                    <FTREF/>
                     sufficient to meet its Cover 1 requirement while reducing the resource allocation and funding burdens on Members associated with collecting resources in excess of this Cover 1 amount, which would result in a more efficient and effective SLD process.
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         Qualifying liquid resources is defined in Rule 17ad-22(a) under the Act. 
                        <E T="03">See</E>
                         17 CFR 240.17ad-22(a). “Qualifying Liquid Resources,” for purposes of the NSCC Rules, is defined in Section 2 of Rule 4A. 
                        <E T="03">See</E>
                         NSCC Rule 4A, Section 2, 
                        <E T="03">supra</E>
                         note 3. NSCC's qualifying liquid resources include, for example: (1) the cash in the Clearing Fund; (2) the cash that would be obtained from NSCC's committed 364-day credit facility with a consortium of lenders; (3) cash proceeds from NSCC's commercial paper and extendable note program; and (4) cash proceeds from NSCC's Senior Unsecured Notes. 
                        <E T="03">See</E>
                         NSCC Disclosure Framework for Covered Clearing Agencies and Financial Market Infrastructures, December 2025, p. 65 
                        <E T="03">available at www.dtcc.com/-/media/Files/Downloads/legal/policy-and-compliance/nscc-disclosure-framework-2025-q4.pdf.</E>
                         NSCC and its affiliate clearing agencies (DTC and Fixed Income Clearing Corporation) have also adopted a Clearing Agency Liquidity Risk Management Framework that sets forth, among other things, the qualifying liquid resources of NSCC. 
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 82377 (Dec. 21, 2017), 82 FR 61617 (Dec. 28, 2017) (SR-DTC-2017-004; SR-FICC-2017-008; SR-NSCC-2017-005).
                    </P>
                </FTNT>
                <P>NSCC has discussed this proposal with Members, who generally expressed support for the proposed changes. NSCC believes the proposal would benefit Members because it would (i) improve the accuracy of NSCC's SLD calculations by, for example, allowing NSCC to monitor and evaluate its intraday liquidity needs using a standardized process and more accurate netting methodology; (ii) enhance the overall accuracy of NSCC's liquidity need projections and improve Member understanding the methodology and processes associated therewith; (iii) minimize the burdens of potentially over-collecting resources from Members to address NSCC's liquidity needs, particularly through the use of enhanced netting calculations and the pro rata distribution of NSCC's largest liquidity needs; and (iv) provide for more standardized, clear and transparent rules for NSCC's SLD processes.</P>
                <P>The proposed rule change is discussed in detail below.</P>
                <HD SOURCE="HD3">Background</HD>
                <P>
                    Under NSCC Rule 4A, NSCC collects additional cash deposits, both at the SOD and on an intraday basis, in the form of SLD to the Clearing Fund to cover the liquidity exposures presented by Members (whether individually or as part of an affiliated Member family) whose activity generates liquidity needs in excess of NSCC's then available qualifying liquid resources. SLD is typically collected during times of increased trading activity, particularly those that arise around Options Expiration Activity Periods.
                    <SU>9</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         An Options Expiration Activity Period is generally the period beginning at the opening of business on the monthly expiration date and ending at the close of business on the Settlement Date following such date. 
                        <E T="03">See</E>
                         NSCC Rule 4A, Section 2, 
                        <E T="03">supra</E>
                         note 3.
                    </P>
                </FTNT>
                <P>
                    Each Business Day, NSCC determines the peak liquidity need of each Member over a 24-month lookback period, and the 30 (or fewer) Members/Affiliated Families with the largest peak liquidity need during the lookback period may be designated “Supplemental Liquidity Providers” for that Business Day.
                    <SU>10</SU>
                    <FTREF/>
                     Each Supplemental Liquidity Provider may then have a Supplemental Liquidity Obligation to NSCC based on the calculation set forth in Rule 4A, with such obligation being equal to the Daily Liquidity Need of the Supplemental Liquidity Provider calculated for that Business Day minus the Qualifying Liquid Resources available to NSCC on such date.
                    <SU>11</SU>
                    <FTREF/>
                     This Supplemental Liquidity Obligation is collected at the start of each Business Day, as applicable. If two or more Supplemental Liquidity Providers have a Supplemental Liquidity Obligation of more than $2 billion, NSCC may allocate the Supplemental Liquidity Obligation of each Supplemental Liquidity Provider as its pro rata share of the largest Supplemental Liquidity Obligation calculated for that Business Day.
                    <SU>12</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See</E>
                         NSCC Rule 4A, Section 3, 
                        <E T="03">supra</E>
                         note 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See</E>
                         NSCC Rule 4A, Section 4.a., 
                        <E T="03">supra</E>
                         note 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">See</E>
                         NSCC Rule 4A, Section 4.b., 
                        <E T="03">supra</E>
                         note 3.
                    </P>
                </FTNT>
                <P>
                    In addition to SOD Supplemental Liquidity Obligations, NSCC may also issue Intraday Supplemental Liquidity Calls to Supplemental Liquidity Providers during Options Expiration Activity Periods. NSCC issues Intraday Supplemental Liquidity Calls calculated and collected, when applicable, on the first Business Day (typically a Friday) of an options expiry period.
                    <SU>13</SU>
                    <FTREF/>
                     A Supplemental Liquidity Provider's Intraday Supplemental Liquidity Call is equal to the difference between NSCC's qualifying liquid resources and NSCC's Daily Liquidity Need based on the Supplemental Liquidity Provider's settlement activity at the start of the Business Day, adjusted to account for both the Supplemental Liquidity Provider's increased settlement activity submitted to NSCC over the course of the day and its projected settlement activity with respect to the monthly expiration of stock options.
                    <SU>14</SU>
                    <FTREF/>
                     NSCC adjusts this recalculated Daily Liquidity Need using an estimated netting percentage that is based on that Supplemental Liquidity Provider's average percentage of netting observed over the prior 24 months.
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See</E>
                         NSCC Rule 4A, Section 7.a., 
                        <E T="03">supra</E>
                         note 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         In this case, the recalculation is based on the data NSCC receives from OCC later in the day on Thursday.
                    </P>
                </FTNT>
                <P>
                    On the remaining days of any Options Expiration Activity Period, NSCC may issue an intraday call on Supplemental Liquidity Providers whose increase in activity levels caused (or was the primary cause of) an observed increase in NSCC's Daily Liquidity Need. These discretionary Intraday Supplemental Liquidity Calls are issued in an amount equal to the difference between (i) the Daily Liquidity Need associated with the Supplemental Liquidity Provider on such Business Day, adjusted to account for such increased activity levels, and (ii) the sum of NSCC's Qualifying Liquid Resources.
                    <SU>15</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">See</E>
                         NSCC Rule 4A, Section 7.b., 
                        <E T="03">supra</E>
                         note 3.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Proposed Changes to the NSCC Rules</HD>
                <P>NSCC proposes to amend Rule 4A to make the following changes:</P>
                <P>• Make organizational and drafting improvements to Rule 4A to more clearly and concisely describe NSCC's methodology and processes for determining SLD Obligations on an SOD and intraday basis;</P>
                <P>
                    • Standardize the netting methodology, calculations and 
                    <PRTPAGE P="41131"/>
                    processes used by NSCC to determine Daily Liquidity Needs and intraday SLD Obligations, regardless of the point in time within or outside of any Options Expiration Activity Period;
                </P>
                <P>• Provide additional details regarding the factors considered by NSCC when projecting liquidity needs and determining SLD Obligations to improve Members' understanding of NSCC's SLD calculations;</P>
                <P>• Codify and clarify existing obligations for Members to provide reporting and information to NSCC regarding anticipated trading and settlement activity that would impact NSCC's liquidity needs;</P>
                <P>• Modify the NSCC Rules for determining the pro rata allocation of SOD and intraday SLD Obligations when more than one Member is driving NSCC's liquidity needs;</P>
                <P>• Modify the process for returning excess SLD amounts to Members; and</P>
                <P>• Make other clarifying, organizational and cleanup changes to Rule 4A.</P>
                <P>The proposed changes are discussed in further detail below.</P>
                <HD SOURCE="HD3">Proposed Organizational and Drafting Changes to SOD and Intraday SLD Rules</HD>
                <P>NSCC proposes to reorganize, consolidate and streamline the NSCC Rules describing how NSCC determines SLD Obligations to improve Members' understanding of NSCC's SLD methodology and processes and their obligations thereunder. Under the proposed rule change, NSCC would modify Section 4 of Rule 4A, which describes the formula for calculating SLD Obligations, to more generally describe how NSCC determines SLD Obligations on both an SOD and intraday basis. As proposed, Section 4.a. of Rule 4A would continue to describe the general formula used by NSCC to calculate SLD Obligations with minor drafting changes to simplify the rule text. In addition, Section 4.b. of Rule 4A would be revised to add new rule text to clarify that SLD Obligations are determined based on (i) observed Daily Liquidity Needs, to be collected on an SOD basis; and (ii) projected Daily Liquidity Needs, to be collected on an intraday basis. NSCC would also relocate the existing rules in Section 4.b. of Rule 4A concerning the allocation of SLD Obligations among Members, as described further below.</P>
                <P>Additionally, NSCC proposes to adopt new Section 4.c. of Rule 4A to describe adjustments that NSCC may make when determining SLD Obligations to ensure sufficient coverage of its liquidity risk tolerance. This proposed change is discussed in further detail below.</P>
                <P>
                    NSCC believes that the proposed changes to Section 4 of Rule 4A would improve a Member's understanding of the SLD rules by providing a clear and concise explanation of how NSCC calculates its Daily Liquidity Needs for both SOD and intraday purposes. NSCC notes that it does not propose to change the substance of the Daily Liquidity Need formula currently contained in Section 4.a. of Rule 4A (
                    <E T="03">i.e.,</E>
                     that Supplemental Liquidity Obligations shall be calculated as the difference between the Daily Liquidity Need of the Supplemental Liquidity Provider calculated for that Business Day and the sum of all Qualifying Liquid Resources available to NSCC on that Business Day assuming stressed market conditions).
                </P>
                <HD SOURCE="HD3">Proposed Changes To Standardize NSCC's Intraday SLD Methodology</HD>
                <P>NSCC proposes to enhance the NSCC Rules by standardizing the methodology and processes it uses to determine its projected Daily Liquidity Needs and intraday SLD Obligations, regardless of the point in time within or outside of any Options Expiration Activity Period. As discussed above, Section 7.a. of Rule 4A currently provides that for Intraday Supplemental Liquidity Calls on the first Business Day of an options expiry period, NSCC calculates a projection of its Daily Liquidity Need based on activity levels or projected settlement activity with respect to monthly expiration of stock options and adjusts the recalculated Daily Liquidity Needs using an estimated netting percentage that is based on that Supplemental Liquidity Provider's average percentage of netting observed over the prior 24 months. Section 7.b. of Rule 4A, however, does not specify netting assumptions for days other than the first Business Day of an options expiry period and allows for other netting assumptions, such as current-open positions.</P>
                <P>The proposed rule change would create one standard methodology and process, regardless of timing within or outside of the options expiry period, for calculating intraday SLD Obligations. Specifically, NSCC would eliminate the concept of the Options Expiration Activity Period from the NSCC Rules, discontinue its use of the estimated netting percentage based on a 24-month lookback period, and adopt one standard netting methodology based on current open positions regardless of the timing of any options expiry period, similar to SOD liquidity need calculations. To effectuate this change, NSCC would delete Section 7, entitled Determination of Intraday Supplemental Liquidity Calls, and the definition of Options Expiration Activity Period from Section 2 of Rule 4A. NSCC would replace these deleted items with new rules in a new Section 5 describing NSCC's methodology and process for projecting its Daily Liquidity Needs for purposes of determining intraday SLD Obligations, as described below.</P>
                <P>The proposed standardized netting approach would more closely reflect the actual netting against open NSCC positions that is done during the overnight process used for SOD liquidity need calculations, which NSCC believes is a more accurate representation of the actual liquidity exposures of each Member.</P>
                <HD SOURCE="HD3">Proposed Changes Related to Liquidity Need Projections for Intraday SLD</HD>
                <P>Under its existing authority in Section 7 of Rule 4A, NSCC may adjust its Daily Liquidity Needs for the purpose of determining Intraday Supplemental Liquidity Calls to account for increased activity levels and projected settlement activity of its Members. Accordingly, NSCC has continued to improve its process for projecting settlement activity to more accurately project its associated Daily Liquidity Needs. This includes refining the factors that NSCC considers and incorporates into its Daily Liquidity Need projections. NSCC proposes to adopt new Section 5 of Rule 4A to provide additional details regarding the various factors NSCC may take into consideration when projecting its Daily Liquidity Needs for intraday SLD Obligations.</P>
                <P>
                    Proposed Section 5 would provide that, when calculating and determining projected Daily Liquidity Needs to determine intraday SLD Obligations, NSCC may take into consideration factors including, but not limited to: (i) a Member's projected or anticipated trading or settlement activity as communicated by the Member, The Options Clearing Corporation, a Qualified Clearing Agency or Registered Clearing Agency offering trade matching services, an Index Receipt Agent, or any other person authorized to submit transaction information for such Member; (ii) projected netting activity using open positions for that Member; and (iii) anticipated deliveries from a Member's free inventory at the Member's Designated Depository into the next CNS 
                    <SU>16</SU>
                    <FTREF/>
                     night cycle, after consideration of applicable long allocation projection offsets and cross-account netting.
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         CNS is NSCC's core netting, allotting, and fail-control engine for securities transactions. 
                        <E T="03">See</E>
                         NSCC Rule 11 (CNS System) and Procedure VII (CNS Accounting Operation), 
                        <E T="03">supra</E>
                         note 3.
                    </P>
                </FTNT>
                <PRTPAGE P="41132"/>
                <P>The consideration of these factors is discussed in additional detail below.</P>
                <HD SOURCE="HD3">Consideration of Anticipated Trading and Settlement Activity</HD>
                <P>
                    Certain trading activity cleared by NSCC is not finalized and submitted to NSCC for clearing until later in the trading day and therefore is not typically received in time to be included in NSCC's intraday SLD calculation and collection process (which is generally completed prior to the close of the Federal Reserve's Fedwire Funds Service at 7:00 p.m. Eastern Time 
                    <SU>17</SU>
                    <FTREF/>
                    ). For example, the NSCC deadline for Index Receipt Agents to submit exchange-traded fund (“ETF”) creation/redemption instructions in the primary cycle is 8:45 p.m.,
                    <SU>18</SU>
                    <FTREF/>
                     the affirmation deadline for prime broker trades submitting by trade matching platforms (such as DTCC ITP Matching (US) LLC or “ITPM”) 
                    <SU>19</SU>
                    <FTREF/>
                     is currently 9:00 p.m., and final OCC E&amp;A Activity may be submitted to NSCC as late as 1:00 a.m. As a result, NSCC must incorporate projections of such activity into its Daily Liquidity Need calculations for purposes of determining intraday SLD Obligations.
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         All times discussed herein are Eastern Time unless otherwise indicated.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         ETFs (referred to as “index receipts” in the NSCC Rules) are marketable securities that track stock indices, commodities, bonds, or baskets of assets. Shares of ETFs are “created” and “redeemed” in the primary market and are traded on listed exchanges in the secondary market. NSCC facilitates clearing and settlement of the creation and redemption of ETF shares in the primary market as well as clearing of ETF trades in the secondary market. The participants in the ETF primary market typically consist of the issuers of ETFs (“ETF Sponsors”), custodian banks (“ETF Agents,” also referred to as “Index Receipt Agents” in the NSCC Rules, 
                        <E T="03">see</E>
                         Rule 1 (Definitions and Descriptions), 
                        <E T="03">supra</E>
                         note 3), and brokers/dealers that have agreements directly with ETF Sponsors to allow the brokers/dealers to place orders for the creation and redemption of ETF shares (“Authorized Participants” or “APs”). Both the ETF Agents and APs are Members of NSCC. APs create and redeem ETF shares from the ETF Sponsors in blocks called “creation units.” An AP that purchases a creation unit of ETF shares delivers a “basket” of securities and other assets to the ETF Agent, and then receives the creation unit of ETF shares in return for those assets. The redemption process is the reverse of the creation process: the AP redeems a creation unit of ETF shares for a basket of securities and other assets. 
                        <E T="03">See</E>
                         NSCC Rule 7 (Comparison and Trade Recording Operation (Including Special Representative/Index Receipt Agent)) and Procedure II. (Trade Comparison and Recording Service), Section F. concerning the ETF creation/redemption process, 
                        <E T="03">supra</E>
                         note 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         ITPM, which is a wholly owned subsidiary of DTCC ITP LLC, provides central trade matching and electronic trade confirmation services subject to the conditions of an exemptive order issued by the Commission. 
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 44188 (Apr. 17, 2001); 66 FR 20494 (Apr. 23, 2001) (600-32).
                    </P>
                </FTNT>
                <P>
                    Currently, in order to project its Daily Liquidity Needs, NSCC reaches out to those Members who are typically the top liquidity users (and also subject to SLD) during periods of elevated activity (
                    <E T="03">e.g.,</E>
                     the week leading up to standard option expirations) to solicit information concerning their projected OCC or ETF activity. With respect to OCC activity, NSCC receives E&amp;A Projection Files from OCC regarding projected OCC E&amp;A Activity for each activity date to inform NSCC's liquidity risk projections.
                    <SU>20</SU>
                    <FTREF/>
                     For ETF activity, this also includes outreach to Index Receipt Agents concerning their anticipated ETF activity, and NSCC has worked with Index Receipt Agents to develop an automated reporting process through which Index Receipt Agents can provide daily projected ETF activity reporting. Additionally, NSCC maintains information sharing arrangements with trade matching platforms concerning their anticipated clearance and settlement activity. All of this information is used by NSCC's Liquidity Risk Management team to inform the projection of NSCC's Daily Liquidity Need calculations for purposes of determining intraday SLD Obligations.
                </P>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         
                        <E T="03">See supra</E>
                         note 5.
                    </P>
                </FTNT>
                <P>The proposed rule change would provide additional clarity regarding NSCC's process for projecting Daily Liquidity Needs by describing in the NSCC Rules the various factors and information sources used to project or anticipate trading or settlement activity. This includes information communicated to NSCC by sources such as Members, OCC, trade matching platforms (such as ITPM), and Index Receipt Agents.</P>
                <P>Proposed Section 5 would also provide that NSCC shall assume the completeness and accuracy of all information concerning a Member's projected or anticipated trading or settlement activity that is provided to NSCC by the Member, OCC, a Qualified Clearing Agency or Registered Clearing Agency offering trade matching services, an Index Receipt Agent, or any other person authorized to submit transaction information for such Member, and that NSCC may directly incorporate such information into its Daily Liquidity Need calculations via automated processes. The proposed rule change would provide NSCC with explicit authority to automatically incorporate such data directly into its liquidity need calculations via automated processes rather than relying on manual processes and confirmations with Members.</P>
                <HD SOURCE="HD3">Consideration of Projected Netting Activity</HD>
                <P>The newly proposed Section 5 of Rule 4A would also reflect that NSCC would utilize a standard netting methodology based on current open positions for all intraday liquidity need projections, rather than using an estimated netting percentage based on the 24-month lookback period for the first Business Day of every options expiry period, as discussed above.</P>
                <HD SOURCE="HD3">Consideration of Anticipated Deliveries</HD>
                <P>
                    The proposed rule change would describe NSCC's ability to consider anticipated deliveries from a Member's free inventory at the Member's Designated Depository (
                    <E T="03">i.e.,</E>
                     DTC) into the next CNS night cycle as potential offsets to NSCC's projected liquidity needs. CNS is NSCC's automated accounting and securities settlement system that centralizes and nets the settlement of compared and recorded securities transactions and maintains an orderly flow of security and money balances. CNS relies on an interface with NSCC's affiliate clearing agency, DTC, for the book-entry movement of securities. CNS short positions are compared against each Member's DTC accounts to determine the availability of securities for delivery. If securities are available, they are automatically transferred from the Member's account at DTC to NSCC's account at DTC to cover the Member's short obligations to CNS.
                </P>
                <P>NSCC calculates its Daily Liquidity Need as the payment obligations of NSCC as central counterparty for all observed or projected same day, intraday and multiday settlement activity (where appropriate), assuming the default on that day of an Unaffiliated Member or Affiliated Family. This payment obligation is the net liquidity need after the application of all permitted long allocations, cross-account netting, and other applicable offsets.</P>
                <P>
                    Anticipated deliveries from free inventory at DTC may be used to further offset projected net liquidity needs after consideration of long allocation projection offsets and cross-account netting.
                    <SU>21</SU>
                    <FTREF/>
                     NSCC works with potential Supplemental Liquidity Providers to confirm their expected inventory value and obtain appropriate assurance that such Members manage and facilitate delivery of those securities into the CNS 
                    <PRTPAGE P="41133"/>
                    night cycle, which begins at approximately 11:30 p.m. each Business Day.
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         NSCC would use the actual DTC deliveries from the night cycle when determining net liquidity needs for its SOD liquidity reporting and determining whether additional SOD SLD Obligations are needed.
                    </P>
                </FTNT>
                <P>Proposed Section 5 would codify details concerning NSCC's process for incorporating anticipated deliveries from a Member's free inventory into NSCC's Daily Liquidity Need Projections. The proposed rule would provide that, in order for NSCC to appropriately consider anticipated deliveries from a Member's free inventory into its Daily Liquidity Need projections, the Member shall identify to NSCC in writing, and in such form, time and manner as required by NSCC, an aggregate value of its existing free inventory that is recorded in the subaccounts of the Member with delivery obligations into the CNS night cycle scheduled to run on that Business Day. The proposed rule would also stipulate that any Member identifying such anticipated deliveries for consideration in NSCC's Daily Liquidity Need projections represents to NSCC that (i) it shall make best efforts to manage such inventory such that it continues to be recorded within a specified subaccount of the Member through the start of the immediate next CNS night cycle; and (ii) it shall not take any action that would prohibit the delivery of such inventory into the immediate next CNS night cycle. The proposed rule would also clarify that NSCC may consider all or part of the identified inventory in its Daily Liquidity Need projections.</P>
                <P>The proposed rule change would provide additional clarity and transparency in NSCC's rules regarding the inventory projection process and codify the associated reporting, representations and assurances directly into the NSCC Rules. As noted above, a Member's available inventory is automatically transferred from the Member's account at DTC to NSCC's account at DTC to cover the Member's short obligations to CNS. NSCC therefore believes that applying inventory offsets when such inventory can be appropriately confirmed by NSCC and the Member and committed for delivery in the night cycle would result in more accurate projections of its Daily Liquidity Needs and resulting intraday SLD Obligations for its Members.</P>
                <HD SOURCE="HD3">Proposed Changes Related to Consideration of NSCC's Liquidity Risk Tolerance</HD>
                <P>As noted above, NSCC also proposes to adopt Section 4.c. of Rule 4A to describe how NSCC may adjust SLD Obligations to account for potential variations in NSCC's actual liquidity needs to facilitate the maintenance of sufficient liquidity resource coverage within NSCC's liquidity risk tolerance. Under the DTCC Corporate Risk Management Policy, NSCC maintains risk tolerance statements for certain core risks that (i) define the risk in question; (ii) describe the associated risk appetite and related thresholds; (iii) set forth supporting key risk indicators; and (iv) identify the escalation requirements when breaches occur. Risk tolerances are used to establish and communicate thresholds for risk, including the quantity and type of risk, that NSCC is willing to accept in pursuit of its business objectives. Pursuant to the DTCC Corporate Risk Management Policy, NSCC has established liquidity risk tolerances that include metrics and thresholds concerning its Cover 1 liquidity sufficiency. Currently, NSCC's liquidity risk tolerance targets liquidity resource levels sufficient to cover 110 percent of NSCC's actual liquidity needs. These liquidity risk tolerance targets allow NSCC to account for potential variations between NSCC's intraday liquidity projections, which are based on projections and estimates available to NSCC prior to Settlement Date, and NSCC's observed final simulated liquidity needs calculated on Settlement Date. Under the proposed rule change, NSCC would assess this liquidity risk tolerance threshold on at least an annual basis and will communicate any changes to such thresholds in advance to potential Supplemental Liquidity Providers.</P>
                <HD SOURCE="HD3">Proposed Changes to Allocation of Supplemental Liquidity Obligations</HD>
                <P>
                    As discussed above, Section 4.b. of Rule 4A currently provides that if two or more Supplemental Liquidity Providers have a Supplemental Liquidity Obligation of more than $2 billion, NSCC may determine the Supplemental Liquidity Obligation of each Supplemental Liquidity Provider as its pro rata share of the largest Supplemental Liquidity Obligation calculated for that Business Day. This rule provides NSCC with the option to determine, if it is appropriate, to collect the largest SLD calculated for that Business Day divided pro rata among the Supplemental Liquidity Providers rather than collect each of the individual Supplemental Liquidity Obligations of those firms. Collecting the largest SLD on a pro rata basis enables NSCC to collect sufficient funds to meet its Cover 1 regulatory requirement 
                    <SU>22</SU>
                    <FTREF/>
                     in circumstances when the aggregate Supplemental Liquidity Obligations on a particular day would significantly exceed that amount, thereby reducing liquidity and funding burdens on its Members.
                    <SU>23</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         
                        <E T="03">See supra</E>
                         note 7.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 92213 (June 21, 2021), 86 FR 33414, 33417-33419 (June 24, 2021) (SR-NSCC-2021-002).
                    </P>
                </FTNT>
                <P>
                    NSCC proposes to relocate its pro rata allocation rules into Section 6 of Rule 4A 
                    <SU>24</SU>
                    <FTREF/>
                     and clarify that it applies to all SLD Obligations (both SOD and intraday). NSCC also proposes to eliminate the $2 billion threshold for pro rata allocations. Specifically, Section 6 of Rule 4A would state that, if two or more Supplemental Liquidity Providers present a Daily Liquidity Need resulting in an SLD Obligation, NSCC would determine the SLD Obligation amount of each Supplemental Liquidity Provider as its pro rata share of the largest SLD Obligation calculated for the Business Day (whether start-of-day or intraday); provided that NSCC may collect the total amount of each Supplemental Liquidity Provider's individual SLD Obligations if NSCC determines that such action is necessary for the protection of NSCC, participants, investors or creditors.
                </P>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         The existing rules in Section 6 of Rule 4A concerning the notification of SLD Obligations would be relocated to Section 7 of Rule 4A, with certain modifications, as discussed below.
                    </P>
                </FTNT>
                <P>
                    NSCC intends to use pro rata allocation as the primary/default method for collecting SLD Obligations; however, NSCC would retain its existing discretion in the NSCC Rules to collect the total amount of a Member's SLD Obligation in exceptional circumstances (
                    <E T="03">i.e.,</E>
                     where the collection of the total obligation may be necessary for the protection of NSCC, participants, investors, or creditors). This may occur, for example, if NSCC has a reasonable basis to believe that one of the Supplemental Liquidity Providers may be unable to satisfy its pro rata portion of the SLD Obligation to NSCC. Any determination to collect each Member's total obligation would be made pursuant to NSCC's Liquidity Risk Management Procedures, which describe the process and approval authority required to make SLD calls based on the amount of any such call in relation to NSCC's Qualifying Liquid Resources (
                    <E T="03">i.e.,</E>
                     whether the amount of an SLD call would exceed certain percentage thresholds of Qualifying Liquid Resources).
                    <SU>25</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         NSCC notes that it does not intend to collect an amount between the Member's total obligation and a pro rata share of the largest obligation. NSCC would collect either the pro rata share of the largest obligation or the Member's total individual SLD Obligation.
                    </P>
                </FTNT>
                <PRTPAGE P="41134"/>
                <P>NSCC believes that providing one standardized approach in the NSCC Rules for allocating SOD and intraday SLD Obligations would provide greater clarity, transparency, and consistency for its Members. NSCC also believes that removing the $2 billion threshold established previously by NSCC would help to further reduce unnecessary liquidity and funding burdens on its Members while still allowing NSCC to collect sufficient funds to meet its regulatory requirements in circumstances when the aggregate SLD Obligations of all Supplemental Liquidity Providers on a particular day would exceed that amount.</P>
                <HD SOURCE="HD3">Proposed Changes To Return of SLD Obligations</HD>
                <P>
                    NSCC proposes to clarify its rules regarding the return of SLD in Section 9 of Rule 4A. Section 9 of Rule 4A currently provides that a Supplemental Liquidity Provider shall be entitled to the return of its SLD, payable on the Business Day following the Business Day on which the SLD was made, unless otherwise notified by NSCC.
                    <SU>26</SU>
                    <FTREF/>
                     Pursuant to this rule, NSCC may notify a Member that it has elected to retain all or part of its SLD if a liquidity need remains on the day(s) after the deposit was made. NSCC proposes to revise this rule to more clearly reflect NSCC's right to retain SLD, as needed, and to provide Members with the right to request the return of any excess SLD (rather than a default assumption regarding the automatic return of SLD).
                </P>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         
                        <E T="03">See</E>
                         NSCC Rule 4A, Section 9, 
                        <E T="03">supra</E>
                         note 3.
                    </P>
                </FTNT>
                <P>NSCC proposes to retitle this section of Rule 4A to “Return of Supplemental Liquidity Deposits” and restate this Rule to provide that, upon the request of a Member, NSCC will return its SLD, provided that NSCC may retain all or any amount of such SLD NSCC deems necessary to cover observed or projected liquidity obligations of such Member to NSCC, assuming the default on that day of such Member or Affiliated Family. NSCC believes the proposed rule change would more clearly reflect NSCC's right to retain all or part of a Member's SLD if a liquidity need remains beyond the initial day of deposit. NSCC also believes that making Members responsible for requesting the return of excess SLD will encourage Members to more actively monitor and manage their liquidity obligations at NSCC.</P>
                <HD SOURCE="HD3">Proposed Changes Concerning Member Reporting and Notification Requirements</HD>
                <P>NSCC also proposes to adopt new Section 14 of Rule 4A, titled “Member Reporting and Notification Requirements,” to provide additional clarity regarding expectations for Members to inform NSCC of anticipated trading and settlement activity that is not yet reflected in NSCC's clearing or risk systems. The proposed rule would require that each Member manage its liquidity needs to NSCC, specifically by tracking its settlement activities that generate liquidity needs across all trading desks, systems, and platforms and notifying NSCC of anticipated significant changes in such activity. The proposed rule would further require that each Member identify contact persons responsible for responding to NSCC's inquiries concerning settlement activity and liquidity management and confirm or update such contacts on at least an annual basis.</P>
                <P>
                    The proposed rule would also codify certain obligations for Members to provide reporting and information to NSCC concerning liquidity risk management. Pursuant to Section 2.A. of NSCC Rule 2B (Ongoing Membership Requirements and Monitoring), NSCC currently has the authority to require the submission of additional reports and other information as it may deem necessary or advisable, in the form and to the persons or departments as specified NSCC.
                    <SU>27</SU>
                    <FTREF/>
                     Under Section 2 of Rule 15 (Assurances of Financial Responsibility and Operational Capability), NSCC may also require Members to furnish such adequate assurances of its financial responsibility and operational capability as NSCC may at any time or from time to time deem necessary or advisable in order to protect NSCC, its participants, creditors or investors, to safeguard securities and funds in the custody or control of NSCC and for which NSCC is responsible, or to promote the prompt and accurate clearance, settlement and processing of securities transactions.
                    <SU>28</SU>
                    <FTREF/>
                     Pursuant to authority under these NSCC Rules, NSCC periodically requires Members to provide information and reporting on, for example, anticipated trading and settlement activity to inform NSCC's management of liquidity risk. NSCC now proposes to codify specific obligations for Members to provide regular reporting on anticipated trading and settlement activity. Specifically, the proposed rule change would state that NSCC may require Members to provide additional reports or information concerning their anticipated trading and settlement activity as NSCC may deem necessary or advisable to more accurately project its Daily Liquidity Needs. Furthermore, the proposed rule would require Members to provide such requested reports and information in the time, form and manner specified by NSCC and completely and accurately provide all requested information. With respect to Index Receipt Agents, the proposed rule change would further codify a requirement that such reporting shall include daily automated reporting of anticipated creation and redemption activity between such Index Receipt Agent and Authorized Participants, requiring all Index Receipt Agents to provide daily reporting through the automated reporting process discussed above.
                </P>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         
                        <E T="03">See</E>
                         NSCC Rule 2B, Section 2.A., 
                        <E T="03">supra</E>
                         note 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         
                        <E T="03">See</E>
                         NSCC Rule 15, Section 2.(a), 
                        <E T="03">supra</E>
                         note 3.
                    </P>
                </FTNT>
                <P>
                    NSCC believes that the provision of information concerning anticipated trading and settlement activity is necessary to accurately and appropriately project its Daily Liquidity Needs and intraday SLD Obligations under NSCC Rule 4A and meets its liquidity resource obligations under Rule 17ad-22(e)(7) under the Act.
                    <SU>29</SU>
                    <FTREF/>
                     Accordingly, NSCC proposes to explicitly codify these obligations with respect to liquidity risk reporting to provide additional clarity and transparency to Members and the public.
                </P>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         
                        <E T="03">See</E>
                         17 CFR 240.17ad-22(e)(7).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Other Clarifying Changes</HD>
                <P>NSCC proposes to make other clarifying and cleanup changes to Rule 4A. NSCC would revise Rule 4A to relocate the definitions of the terms Supplemental Liquidity Deposit and Supplemental Liquidity Provider to the definitions section in Section 2 to consolidate the majority of defined terms in Rule 4A and improve the clarity and readability of the NSCC Rules. NSCC would also add a new defined term, “SLD Obligation,” to mean, on any Business Day, the amount of SLD required to be provided by a Supplemental Liquidity Provider, on a start-of-day or intraday basis, as determined by NSCC in accordance with Rule 4A. NSCC would also update the definition of “Supplemental Liquidity Deposit” (or “SLD”) to mean a deposit made to the Clearing Fund by a Supplemental Liquidity Provider in an amount equal to its start-of-day or intraday SLD Obligations. In addition, NSCC would eliminate the defined term “Intraday Supplemental Liquidity Call” and instead use the new defined term SLD Obligation to apply to both SOD and intraday SLD obligations, as applicable, to provide for greater consistency across the NSCC Rules.</P>
                <P>
                    Additionally, NSCC would revise the definition of “Daily Liquidity Need” in 
                    <PRTPAGE P="41135"/>
                    Section 2 of Rule 4A to mean the payment obligations of NSCC as a central counterparty, as calculated and determined by NSCC, for all observed start-of-day, projected intraday and multiday settlement activity (where appropriate), assuming the default on that day of an Unaffiliated Member or Affiliated Family. The proposed rule change would clarify that NSCC's liquidity needs are calculated for payment obligations based on “observed start-of-day, projected intraday and multiday settlement activity” (rather than solely “projected” same day, intraday and multiday settlement activity). The proposed rule change would also clarify that such payment obligation is the anticipated net liquidity need after all permitted long allocations, cross-account netting and actual or anticipated deliveries into the CNS night cycle.
                </P>
                <P>NSCC would also revise the definition of “Qualifying Liquid Resources” in Section 2 of Rule 4A to remove a statement that “Qualifying Liquid Resources” would not include Supplemental Liquidity Deposits for purposes of this Rule 4(A).” This statement was intended to reflect the fact that SLD would be returned on the day following the date the deposit was made; however, as noted above, NSCC currently has the discretion to retain SLD if there is an ongoing liquidity need. Supplemental Liquidity Deposits that are currently deposited with NSCC, and which have not been returned, would in fact be included in NSCC's Qualifying Liquid Resources. NSCC therefore believes that removing this statement would improve the accuracy and clarity of the NSCC Rules.</P>
                <P>In addition, NSCC proposes to revise the description of its process for determining Supplemental Liquidity Providers in Section 3 of Rule 4A to streamline the rule and remove an unnecessary reference to “Members of an Affiliated Family,” which NSCC believes is already covered by the description used for “Affiliated Family.” NSCC would also remove the defined terms “Peak Liquidity Need” and “Lookback Period” from Sections 2 and 3 of Rule 4A but would retain the substance of these requirements within the newly revised Section 3 of Rule 4A by more directly stating that the 30 (or fewer) Unaffiliated Members or Affiliated Families with the largest Daily Liquidity Needs over a 24-month lookback period shall be Supplemental Liquidity Providers for that Business Day. The proposed change is meant to improve the drafting and clarity of the NSCC Rules and is not intended to change the manner in which NSCC determines which Members are Supplemental Liquidity Providers.</P>
                <P>
                    NSCC also proposes to revise Section 6 of Rule 4A, renumbered as Section 7, to provide additional clarity around the notices provided to Supplemental Liquidity Providers. Specifically, the proposed rule would note that on each Business Day, NSCC shall provide each Supplemental Liquidity Provider with the amount of its start-of-day and intraday SLD Obligation for that Business Day, “where applicable.” The proposed change is intended to clarify that a Member may be deemed a Supplemental Liquidity Provider pursuant to Section 3 of Rule 4A but not necessarily issued an SLD Obligation for that day. The proposed language would clarify that such notices would be provided for both SOD and intraday SLD Obligations. NSCC would also remove a statement in Section 6 of Rule 4A that SLD notices provided to Supplemental Liquidity Providers will specify if the Supplemental Liquidity Obligation was calculated pursuant to Section 4.b. of Rule 4A (
                    <E T="03">i.e.,</E>
                     that it was a pro rata allocated amount). NSCC performs outreach to Supplemental Liquidity Providers when issuing SLD Obligations to explain the reasons and drivers for the SLD Obligations but would not necessarily specify in the notice whether such an obligation was determined pursuant to Section 4.b. of Rule 4A. NSCC also proposes to delete the last sentence of Section 6 of Rule 4A, which requires Supplemental Liquidity Providers to make its SLD to the Clearing Fund within one hour of demand, unless otherwise determined by NSCC, and incorporate the timing requirements for meeting SLD calls generally into newly proposed Section 8 of Rule 4A, as discussed below.
                </P>
                <P>NSCC proposes to consolidate its rules concerning the satisfaction of SOD and intraday Supplemental Liquidity Obligations from Sections 5 and 8 into Section 8 of Rule 4A. As proposed, Section 8 of Rule 4A would provide that Members shall satisfy SLD Obligations by making a Supplemental Liquidity Deposit to NSCC within the time prescribed by NSCC or, in the absence thereof, within one hour of NSCC's issuance of notice of such obligation. The rule would also state that all Supplemental Liquidity Deposits shall be made in cash by wire transfer to an account designated by NSCC.</P>
                <P>The newly renumbered/proposed Sections 7-9 and existing Section 10 of Rule 4A would be included under a new subsection of Rule 4A titled “Satisfaction and Return of Supplemental Liquidity Deposits.</P>
                <P>Additionally, NSCC would update Section 13 of Rule 4A to include additional details concerning the information and reporting made available to Supplemental Liquidity Providers each Business Day. Specifically, NSCC would revise Section 13 of Rule 4A to clarify that, in addition to Daily Liquidity Needs for each Supplemental Liquidity Provider, NSCC also makes available the amount of Qualifying Liquid Resources on deposit for each Business Day.</P>
                <P>
                    Finally, NSCC would remove certain general explanatory statements from the introductory paragraph in Section 1 of Rule 4A, which do not describe material aspects of SLD, NSCC's SLD-related operations, or any rights or obligations related to SLD and therefore do not constitute “rules” as defined by Section 19(b)(1) of the Act 
                    <SU>30</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder.
                    <SU>31</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         Section 19(b)(1) of the Act requires a self-regulatory organization (“SRO”) such as NSCC to file with the Commission any proposed rule or any proposed change in, addition to, or deletion from the rules of such SRO. 
                        <E T="03">See</E>
                         15 U.S.C. 78s(b)(1). Section 3(a)(27) of the Act defines “rules of a clearing agency” to mean its (1) constitution, (2) articles of incorporation, (3) bylaws, (4) rules, (5) instruments corresponding to the foregoing and (6) such of the “stated policies, practices and interpretations” (“SPPI”) as the Commission may determine by rule. 
                        <E T="03">See</E>
                         15 U.S.C. 78c(a)(27). Rule 19b-4(a)(6) under the Act defines the term “SPPI” to include (i) any material aspect of the operation of the facilities of an SRO, or (ii) any statement made generally available to membership of, to all participants in, or to persons having or seeking access to facilities of an SRO that establishes or changes any standard, limit, or guideline. 
                        <E T="03">See</E>
                         17 CFR 240.19b-4(a)(6).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    NSCC believes that the proposed rule change is consistent with the requirements of the Act and the rules and regulations thereunder applicable to a registered clearing agency. Specifically, NSCC believes that the proposed changes are consistent with Section 17A(b)(3)(F) of the Act 
                    <SU>32</SU>
                    <FTREF/>
                     and Rule 17ad-22(e)(7) thereunder 
                    <SU>33</SU>
                    <FTREF/>
                     for the reasons set forth below.
                </P>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         15 U.S.C. 78q-1(b)(3)(F).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         
                        <E T="03">See</E>
                         17 CFR 240.17ad-22(e)(7).
                    </P>
                </FTNT>
                <P>
                    Section 17A(b)(3)(F) of Act 
                    <SU>34</SU>
                    <FTREF/>
                     requires, in part, that the rules of a clearing agency be designed to promote the prompt and accurate clearance and settlement of securities transactions, to assure the safeguarding of securities and funds which are in the custody or control of the clearing agency or for which it is responsible and, in general, to protect investors and the public interest. The proposed rule change would enhance the NSCC Rules for determining intraday SLD Obligations 
                    <PRTPAGE P="41136"/>
                    by standardizing the way NSCC calculates such obligations each day (regardless of the point in time within or outside of an options expiry period), which NSCC believes would result in more accurate estimations of the actual liquidity exposures of each Member and the SLD Obligations required to cover such exposures. The proposed rule change would also clearly describe the factors that NSCC may consider when projecting its Daily Liquidity Needs and adjusting SLD Obligations to remain within NSCC's liquidity risk tolerance. Specifically, the proposed rule change would clarify that NSCC may take into consideration factors including, but not limited to: (i) a Member's projected or anticipated trading or settlement activity as communicated to NSCC by the Member, OCC, trade matching platforms, Index Receipt Agents, or any other person authorized to submit transaction information for such Member; (ii) projected netting activity using open positions for that Member; and (iii) anticipated deliveries from a Member's free inventory at DTC into the next CNS night cycle. The proposed rule change would also clarify NSCC's authority to automatically incorporate such data directly into its liquidity need calculations (rather than relying on manual processes and confirmations). In addition, the proposed rule change would describe adjustments that NSCC may make to its intraday SLD Obligations to ensure coverage of NSCC's liquidity risk tolerance, which is designed to account for potential variations between NSCC's intraday liquidity projections and its final simulated liquidity needs on Settlement Date. Furthermore, the proposed rule change would codify existing obligations for Members to provide reporting and information to NSCC regarding anticipated trading and settlement activity that would impact NSCC's liquidity needs. This information is necessary for NSCC to accurately and appropriately project its Daily Liquidity Needs, which in turn informs how NSCC determines SLD Obligations needed to manage the liquidity risks presented by its Members.
                </P>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         15 U.S.C. 78q-1(b)(3)(F).
                    </P>
                </FTNT>
                <P>In addition, the proposed rule change would remove the $2 billion threshold for the pro rata allocation of SLD obligations and provide clear and transparent rules concerning the potential allocation of both SOD and intraday SLD Obligations. Collecting the largest SLD on a pro rata basis enables NSCC to collect sufficient funds to meet its Cover 1 regulatory requirements in circumstances when the aggregate Supplemental Liquidity Obligations on a particular day exceeds that amount, thereby limiting liquidity and funding burdens on its Members and reducing the possibility that Members would be unable to fund such amounts.</P>
                <P>
                    NSCC believes the proposed enhancements to NSCC's netting methodology and pro rata allocation rules would result in more accurate estimations of the actual liquidity exposures of its Members and would therefore result in more accurate and appropriate SLD Obligations for those Members. NSCC also believes that providing additional clarity in the NSCC Rules regarding the various factors considered by NSCC when projecting liquidity needs and determining SLD Obligations would improve understanding of NSCC's intraday SLD processes by NSCC's Members, market participants, and the public. This, in turn, would help Members understand their potential SLD Obligations so they are better equipped and able to satisfy such obligations when due. NSCC uses the SLD it collects to mitigate potential liquidity shortfalls that may arise when liquidating a defaulting Member's portfolio and to continue to effect the prompt and accurate clearance and settlement of securities transactions in the event NSCC ceases to act for a Member. As a result, NSCC believes the proposed rule change is designed to promote the prompt and accurate clearance and settlement of securities transactions, to assure the safeguarding of securities and funds which are in the custody or control of NSCC or for which it is responsible and, in general, to protect investors and the public interest in accordance with the requirements of Section 17A(b)(3)(F) of Act.
                    <SU>35</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    Rule 17ad-22(e)(7) under the Act requires generally that a covered clearing agency 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.
                    <SU>36</SU>
                    <FTREF/>
                     This includes by maintaining 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 plausible market conditions and holding qualifying liquid resources sufficient to meet this “Cover 1” requirement.
                    <SU>37</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>36</SU>
                         
                        <E T="03">See</E>
                         17 CFR 240.17ad-22(e)(7).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>37</SU>
                         
                        <E T="03">See</E>
                         17 CFR 240.17ad-22(e)(7)(i) and (ii).
                    </P>
                </FTNT>
                <P>As discussed above, the proposed rule change would enhance the NSCC rules for determining intraday SLD Obligations by standardizing the way it calculates such obligations each day and providing additional details regarding the factors that NSCC may consider when projecting and adjusting its Daily Liquidity Needs. This includes, for example, a Member's projected or anticipated trading or settlement activity as communicated to NSCC by various sources, projected netting activity using open positions for that Member, and anticipated deliveries from a Member's free inventory at DTC into the next CNS night cycle. In addition, the proposed rule change would describe adjustments that NSCC may make to its intraday SLD Obligations to ensure coverage of NSCC's liquidity risk tolerance, which is designed to account for potential variations between NSCC's intraday liquidity projections and its final observed simulated liquidity needs on Settlement Date. Furthermore, the proposed rule change would codify existing obligations for Members to provide reporting and information to NSCC regarding anticipated trading and settlement activity that would impact NSCC's liquidity needs. This information is necessary for NSCC to accurately and appropriately project its Daily Liquidity Needs, which in turn informs SLD Obligations needed to manage the liquidity risks presented by its Members. NSCC believes the proposed changes are reasonably designed to facilitate the collection of sufficient liquid resources to cover NSCC's liquidity exposures and complete end-of-day settlement in the event of the default of the Member that would generate the largest aggregate payment obligations for NSCC.</P>
                <P>
                    In addition, the proposed rule change would remove the $2 billion threshold for the pro rata allocation of SLD obligations and provide clear and transparent rules concerning the potential allocation of both SOD and intraday SLD Obligations. Collecting the largest SLD on a pro rata basis enables NSCC to collect sufficient funds to meet its Cover 1 regulatory requirements in circumstances when the aggregate SLD Obligations on a particular day exceeds 
                    <PRTPAGE P="41137"/>
                    that amount, thereby limiting liquidity and funding burdens on its Members and reducing the possibility that Members would be unable to fund such amounts.
                </P>
                <P>NSCC would also make changes throughout Rule 4A to improve the accuracy and clarity of the descriptions of key aspects of its liquidity risk management processes and its Members' responsibilities thereunder so that Members are better able to anticipate and comply with such requirements.</P>
                <P>
                    For the foregoing reasons, NSCC believes the proposed rule change is 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, and by maintaining sufficient qualifying liquid resources to effect the settlement of its payment obligations under a Cover 1 standard in accordance with the requirements of Rules 17ad-22(e)(7)(i) and (ii) under the Act.
                    <SU>38</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>38</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    For the reasons set forth above, NSCC believes the proposed rule change is consistent with Section 17A(b)(3)(F) of the Act 
                    <SU>39</SU>
                    <FTREF/>
                     and Rule 17ad-22(e)(7) thereunder.
                    <SU>40</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>39</SU>
                         15 U.S.C. 78q-1(b)(3)(F).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>40</SU>
                         
                        <E T="03">See</E>
                         17 CFR 240.17ad-22(e)(7).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">(B) Clearing Agency's Statement on Burden on Competition</HD>
                <P>
                    Section 17A(b)(3)(I) of Act 
                    <SU>41</SU>
                    <FTREF/>
                     requires that the rules of a clearing agency do not impose any burden on competition not necessary or appropriate in furtherance of the purposes of the Act. NSCC does not believe the proposed rule change would present any burden or have a material impact on competition. The proposed rule change is primarily intended to clarify and enhance the NSCC Rules for determining SLD requirements for its Supplemental Liquidity Providers; however, it would not change the NSCC Rules for selecting Supplemental Liquidity Providers on any given business day. As a result, NSCC does not expect the proposed rule change to impact the number of Members that would be designated Supplemental Liquidity Providers or the number of Members subject to SLD requirements. In addition, the proposed rule change would remove the threshold, and standardize the processes, for allocating SLD Obligations across Members on a pro rata basis, which should generally result in lower overall SLD Obligations for potential Supplemental Liquidity Providers, reducing unnecessary liquidity and funding burdens on NSCC's Members. This rule change would apply equally, and on a pro rata basis, to all Members determined to be Supplemental Liquidity Providers. NSCC therefore believes these proposed changes would not impose any burden on competition.
                </P>
                <FTNT>
                    <P>
                        <SU>41</SU>
                         15 U.S.C. 78q-1(b)(3)(I).
                    </P>
                </FTNT>
                <P>
                    The proposed rule change would also allow NSCC to use a more accurate estimate of potential netting activity, regardless of the point in time within or outside of any options expiry period, to determine its intraday SLD Obligations. In addition, the proposal would describe the various factors that NSCC may consider when projecting its intraday liquidity needs and how NSCC may consider its liquidity risk tolerance when determining the size of intraday SLD Obligations. While the proposed rule change could result in either increases or decreases to SLD Obligations on a given date for a given Member, the proposed changes are intended to result in more accurate estimations of the actual liquidity exposures of each Member and would therefore result in more accurate SLD Obligations for Members. The proposed changes are designed to enhance NSCC's ability to effectively measure, monitor, and manage its liquidity risk, specifically by maintaining sufficient qualifying liquid resources to effect the settlement of its payment obligations in compliance with its Cover 1 liquidity requirement 
                    <SU>42</SU>
                    <FTREF/>
                     and thereby promote the prompt and accurate clearance and settlement of securities transactions in furtherance of Section 17A(b)(3)(F) of the Act.
                    <SU>43</SU>
                    <FTREF/>
                     Accordingly, NSCC believes that any potential increases in SLD Obligations would be necessary and appropriate in furtherance of the purposes of the Act.
                </P>
                <FTNT>
                    <P>
                        <SU>42</SU>
                         
                        <E T="03">See supra</E>
                         note 7.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>43</SU>
                         15 U.S.C. 78q-1(b)(3)(F).
                    </P>
                </FTNT>
                <P>
                    Finally, the proposed rule change would codify existing obligations for Members to provide reporting and information to NSCC regarding anticipated trading and settlement activity that would impact NSCC's liquidity needs. This information is necessary for NSCC to accurately and appropriately project its Daily Liquidity Needs for intraday SLD purposes and to collect sufficient qualifying liquid resources to meet its Cover 1 regulatory obligation, as required by Rule 17ad-22(e)(7) under the Act.
                    <SU>44</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>44</SU>
                         
                        <E T="03">See</E>
                         17 CFR 240.17ad-22(e)(7).
                    </P>
                </FTNT>
                <P>For the foregoing reasons, NSCC does not believe that the proposed rule change would impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act.</P>
                <HD SOURCE="HD2">(C) Clearing Agency's Statement on Comments on the Proposed Rule Change Received From Members, Participants, or Others</HD>
                <P>NSCC has not received or solicited any written comments relating to this proposal. If any written comments are received, NSCC will amend this filing to publicly file such comments 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, 
                    <E T="03">available at 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 Commission's Division of Trading and Markets at 
                    <E T="03">tradingandmarkets@sec.gov</E>
                     or 202-551-5777.
                </P>
                <P>NSCC 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:
                    <PRTPAGE P="41138"/>
                </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-NSCC-2026-009 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-NSCC-2026-009. 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 NSCC 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-NSCC-2026-009 and should be submitted on or before July 27, 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-13523 Filed 7-2-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-105825; File No. SR-NYSETEX-2026-25]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; NYSE Texas, Inc.; Notice of Filing and Immediate Effectiveness of a Proposed Rule Change To Amend the Connectivity Fee Schedule</SUBJECT>
                <DATE>June 30, 2026.</DATE>
                <P>
                    Pursuant to Section 19(b)(1) 
                    <SU>1</SU>
                    <FTREF/>
                     of the Securities Exchange Act of 1934 (“Act”) 
                    <SU>2</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>3</SU>
                    <FTREF/>
                     notice is hereby given that, on June 18, 2026, the NYSE Texas, Inc. (“NYSE Texas” or “Exchange”) filed with the Securities and Exchange Commission (“Commission”) the proposed rule change as described in Items I and II below, which Items have been prepared by the self-regulatory organization. The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         15 U.S.C. 78a.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>
                <P>
                    The Exchange proposes to amend the Connectivity Fee Schedule to amend the list of third party data feeds to which Users can connect. The proposed rule change is available on the Exchange's website at 
                    <E T="03">www.nyse.com</E>
                     and at the principal office of the Exchange.
                </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <P>In its filing with the Commission, the self-regulatory organization included statements concerning the purpose of, and basis for, the proposed rule change and discussed any comments it received on the proposed rule change. The text of those statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in sections A, B, and C below, of the most significant parts of such statements.</P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and the Statutory Basis for, the Proposed Rule Change</HD>
                <HD SOURCE="HD3">1. Purpose</HD>
                <P>
                    The Exchange proposes to amend the Connectivity Fee Schedule to amend the list of third party data feeds to which Users 
                    <SU>4</SU>
                    <FTREF/>
                     can connect. Currently, Users are offered connectivity to data feeds from third party markets and other content service providers (“Third Party Data Feeds”) at the Mahwah, New Jersey data center (“MDC”).
                    <SU>5</SU>
                    <FTREF/>
                     The Exchange now proposes to amend the names of the Cboe Global Markets, Inc. Third Party Data Feeds (excluding Cboe Canada) (“Cboe Data Feeds”) and incorporate a new feed from Investors Exchange LLC (“IEX”).
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         For purposes of the Exchange's colocation services, a “User” means any market participant that requests to receive colocation services directly from the Exchange. 
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 87408 (October 28, 2019), 84 FR 58778 at n.6 (November 1, 2019) (SR-NYSECHX-2019-12). As specified in the Fee Schedule, a User that incurs colocation fees for a particular colocation service pursuant thereto would not be subject to colocation fees for the same colocation service charged by the New York Stock Exchange LLC, NYSE American LLC, NYSE Arca, Inc., and NYSE National, Inc. (together, the “Affiliate SROs”). Each Affiliate SRO has submitted substantially the same proposed rule change to propose the change described herein.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         Through its Fixed Income and Data Services (“FIDS”) business, Intercontinental Exchange, Inc. (“ICE”) operates the MDC. The Exchange and the Affiliate SROs are indirect subsidiaries of ICE.
                    </P>
                </FTNT>
                <P>The Exchange expects that the proposed rule change would become operative by August 31, 2026. The Exchange will announce the date through a customer notice.</P>
                <HD SOURCE="HD3">Proposed Change to the Cboe Data Feeds</HD>
                <P>
                    Currently, the Cboe Data Feeds are set forth in the list of Third Party Data Feeds by market. However, Users have requested that certain of the Cboe Data Feeds be broken out by asset class instead, so that if a User wanted all of the Cboe equities 
                    <SU>6</SU>
                    <FTREF/>
                     data, Cboe options 
                    <SU>7</SU>
                    <FTREF/>
                     data, or Cboe indices data 
                    <SU>8</SU>
                    <FTREF/>
                     it would not have to sign up for connectivity to more than one Third Party Data Feed.
                    <SU>9</SU>
                    <FTREF/>
                     The Exchange proposes to make the requested change and to indicate the exchanges from which data is included in the Cboe equities (“Cboe U.S. Equites”) and Cboe options (“Cboe Options”) data feeds.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         Cboe U.S. Equities | Cboe (representing the four U.S. equities exchanges that Cboe operates as BZX Equities, BYX Equities, EDGA Equities, and EDGX Equities).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         See Cboe U.S. Options | Trade Equity, Index &amp; ETF Options | Cboe (stating that the four U.S.-listed cash equity options markets that Cboe operates are the Cboe Options Exchange, the Cboe C2 Options Exchange, Cboe BZX Options Exchange, and Cboe EDGX Options Exchange).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         The Cboe indices data is set out in the Cboe Global Indices Feed. See Cboe Global Indices Feed (stating that the Cboe Global Indices Feed has more than 1,900 Index Values available).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         Currently, in order to connect to all of the Cboe U.S. Equity data feeds a User would have to connect to two Third Party Data Feeds, and to connect to all of the Cboe Options data feeds a User would have to connect to three Third Party Data Feeds. In order to connect to the Cboe indices data a User currently would have to connect to one Third Party Data Feed and the proposed change would ensure that remains true.
                    </P>
                </FTNT>
                <P>
                    The Exchange also proposes to change the name of “Cboe CFE Futures” to “Cboe Futures Exchange (CFE)” to mirror the name of Cboe Futures Exchange 
                    <SU>10</SU>
                    <FTREF/>
                     and to reorder the Cboe Data Feeds to maintain alphabetical order.
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See, e.g.,</E>
                         Exchange Act Release No. 104973 (March 11, 2026), 91 FR 12631 (March 16, 2026) (SR-CFE-2026-002) (presenting the name as “Cboe Futures Exchange, LLC,” abbreviated to “CFE”).
                    </P>
                </FTNT>
                <P>
                    Accordingly, the Exchange proposes to make the following changes to the Cboe Data Feeds listed under 
                    <PRTPAGE P="41139"/>
                    “Connectivity to Third Party Data Feeds” (proposed additions italicized, proposed deletions in brackets):
                </P>
                <GPOTABLE COLS="2" OPTS="L2,nj,tp0,i1" CDEF="s100,20">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Third party data feed</CHED>
                        <CHED H="1">
                            Monthly recurring
                            <LI>connectivity fee per</LI>
                            <LI>third party data feed</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">[Cboe BZX Exchange (CboeBZX) and Cboe BYX Exchange (CboeBYX)]</ENT>
                        <ENT>[$1,500]</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Cboe Canada</ENT>
                        <ENT>2,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Cboe [CFE] Futures 
                            <E T="03">Exchange (CFE)</E>
                        </ENT>
                        <ENT>1,500</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            <E T="03">Cboe Global Indices Feed</E>
                        </ENT>
                        <ENT>
                            <E T="03">1,500</E>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Cboe 
                            <E T="03">Options</E>
                            [EDGX] Exchange
                            <E T="03">s</E>
                             (
                            <E T="03">Cboe Options Exchange, Cboe C2 Options Exchange, Cboe BZX Options Exchange, and</E>
                             Cboe EDGX
                            <E T="03"> Options Exchange</E>
                            ) [and Cboe EDGA Exchange (CboeEDGA)]
                        </ENT>
                        <ENT>1,500</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Cboe 
                            <E T="03">U.S Equities</E>
                             Exchange
                            <E T="03">s</E>
                             (Cboe 
                            <E T="03">EDGA Equities, Cboe EDGX Equities, Cboe BYX Equities and Cboe BZX Equities</E>
                            ) [and C2 Exchange (C2)]
                        </ENT>
                        <ENT>1,500</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD3">Proposed Change to the IEX Third Party Data Feed</HD>
                <P>
                    IEX has announced that it will launch a new options exchange (“IEX Options”) 
                    <SU>11</SU>
                    <FTREF/>
                     and that it intends to launch IEX Options on October 2, 2026.
                    <SU>12</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See</E>
                         “IEX Announces Planned Launch of Options Exchange End of Q1 2026,” available at 
                        <E T="03">https://www.iex.io/article/iex-announces-planned-launch-of-options-exchange-end-of-q1-2026.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">See</E>
                         “IEX Options Frequently Asked Questions,” question 1, available at 
                        <E T="03">https://cdn.prod.website-files.com/696f8ac812dcabe749e3aa49/69d7ddd79256713d06405c46_IEX%20Options%20FAQs.pdf.</E>
                         The proposed rule change is proposed to become operative before IEX offers IEX Options in order to allow Users time to connect, and test their connection, to IEX Options. The Exchange does not plan to charge for the connection until the IEX Options Third Party Data Feed is available.
                    </P>
                </FTNT>
                <P>So that the Exchange may both offer connectivity to IEX Options and distinguish between IEX Options and the existing IEX equities exchange (“IEX Equities”), it proposes to make the following changes to the list of available Third Party Data Feeds (proposed additions italicized):</P>
                <GPOTABLE COLS="2" OPTS="L2,nj,tp0,i1" CDEF="s200,20">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Third party data feed</CHED>
                        <CHED H="1">
                            Monthly recurring
                            <LI>connectivity fee per</LI>
                            <LI>third party data feed</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">
                            Investors Exchange (IEX) 
                            <E T="03">Equities</E>
                        </ENT>
                        <ENT>$1,300</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            <E T="03">Investors Exchange (IEX) Options</E>
                        </ENT>
                        <ENT>
                            <E T="03">1,300</E>
                        </ENT>
                    </ROW>
                </GPOTABLE>
                <P>The Exchange would provide connectivity to IEX Options as a convenience to Users.</P>
                <P>As with the existing connections to Third Party Data Feeds, including the existing connections to Cboe Data Feeds and to the IEX Equities data feed, the Exchange would receive a connection to the IEX Options data feed (the “Proposed Third Party Data Feed”) from the content service provider at the relevant source. The Exchange would then provide connectivity to that data to Users for a fee. Users would connect to IEX Options over the internet protocol (“IP”) network, a local area network available in the MDC. The Proposed Third Party Data Feed would include trading and other information concerning the securities that are traded on IEX Options.</P>
                <P>As with the existing connections to Third Party Data Feeds, including the existing connection to Cboe Data Feeds and the IEX Equities data feed, in order to connect to a Proposed Third Party Data Feed, a User would enter into a contract with the third party content service provider, pursuant to which it may charge the User for the data feed. The Exchange would receive the Proposed Third Party Data Feed in remote locations and transport it over its fiber optic network to the MDC. After the content service provider and User entered into an agreement and the Exchange received authorization from the content service provider, the Exchange would retransmit the data to the User over the User's port. The Exchange would charge the User for connectivity to the Proposed Third Party Data Feed. A User would only receive, and would only be charged the fee for, connectivity to a Proposed Third Party Data Feed for which it entered into a contract.</P>
                <P>The Exchange has no affiliation with the seller of the Proposed Third Party Data Feed and would have no right to use the feed other than as a redistributor of the data. The Proposed Third Party Data Feed would not provide access or order entry to the Exchange's execution system. The Proposed Third Party Data Feed would not provide access or order entry service to the execution systems of any third party generating the feed. The Exchange would receive the Proposed Third Party Data Feed via arms-length agreements and would have no inherent advantage over any other distributor of such data.</P>
                <HD SOURCE="HD3">Application and Impact of the Proposed Changes</HD>
                <P>The proposed rule change would not apply differently to distinct types or sizes of market participants. Rather, it would apply to all Users equally. As is currently the case, the purchase of any colocation service is completely voluntary and the Connectivity Fee Schedule is applied uniformly to all Users.</P>
                <P>Users have requested that certain of the Cboe Data Feeds be broken out by asset class, instead of by market. The Exchange believes that one current User would benefit from the change. It does not expect to gain customers as a result of breaking out certain of the Cboe Data Feeds by asset class or the other proposed changes to the Cboe Data Feeds.</P>
                <P>Connectivity to the Proposed Third Party Data Feed was requested by Users, but the Exchange believes that it would gain at most a handful of new customers due to the proposed change to the IEX data feeds.</P>
                <HD SOURCE="HD3">Competitive Environment</HD>
                <P>
                    The Exchange operates in a highly competitive market in which other vendors offer colocation services as a means to facilitate the trading and other 
                    <PRTPAGE P="41140"/>
                    market activities of those market participants who believe that colocation enhances the efficiency of their operations. The Commission has repeatedly expressed its preference for competition over regulatory intervention in determining prices, products, and services in the securities markets. Specifically, in Regulation NMS, the Commission highlighted the importance of market forces in determining prices and SRO revenues and, also, recognized that current regulation of the market system “has been remarkably successful in promoting market competition in its broader forms that are most important to investors and listed companies.” 
                    <SU>13</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 51808 (June 9, 2005), 70 FR 37496, 37499 (June 29, 2005).
                    </P>
                </FTNT>
                <P>As explained below, the Exchange's provision of connectivity to the Proposed Third Party Data Feed (“Connectivity”) may compete with connectivity provided by other third parties. Third-party vendors are not at any competitive disadvantage created by the Exchange.</P>
                <P>The proposed change is not otherwise intended to address any other issues relating to colocation services or related fees, and the Exchange is not aware of any problems that Users would have in complying with the proposed change.</P>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    The Exchange believes that the proposed rule change is consistent with Section 6(b) of the Act,
                    <SU>14</SU>
                    <FTREF/>
                     in general, and furthers the objectives of Section 6(b)(5) of the Act,
                    <SU>15</SU>
                    <FTREF/>
                     in particular, because it is designed to prevent fraudulent and manipulative acts and practices, to promote just and equitable principles of trade, to foster cooperation and coordination with persons engaged in regulating, clearing, settling, processing information with respect to, and facilitating transactions in securities, to remove impediments to and perfect the mechanism of a free and open market and a national market system, and, in general, to protect investors and the public interest and because it is not designed to permit unfair discrimination between customers, issuers, brokers, or dealers. The Exchange further believes that the proposed rule change is consistent with Section 6(b)(4) of the Act,
                    <SU>16</SU>
                    <FTREF/>
                     because it provides for the equitable allocation of reasonable dues, fees, and other charges among its members and issuers and other persons using its facilities.
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         15 U.S.C. 78f(b).0 [sic].
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         15 U.S.C. 78f(b)(4).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">The Proposed Rule Change Is Reasonable</HD>
                <P>The Exchange believes that the proposed rule change is reasonable.</P>
                <P>
                    In considering the reasonableness of proposed services and fees, the Commission's market-based test considers “whether the exchange was subject to significant competitive forces in setting the terms of its proposal . . . , including the level of any fees.” 
                    <SU>17</SU>
                    <FTREF/>
                     If the Exchange meets that burden, “the Commission will find that its proposal is consistent with the Act unless `there is a substantial countervailing basis to find that the terms' of the proposal violate the Act or the rules thereunder.” 
                    <SU>18</SU>
                    <FTREF/>
                     Here, the Exchange is subject to significant competitive forces in setting the terms on which it offers its proposal, in particular because substantially similar substitutes are available and the Exchange has not placed present or future third party vendors at a competitive disadvantage created by the Exchange.
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 90209 (October 15, 2020), 85 FR 67044, 67049 (October 21, 2020) (Order Granting Accelerated Approval to Establish a Wireless Fee Schedule Setting Forth Available Wireless Bandwidth Connections and Wireless Market Data Connections) (SR-NYSE-2020-05, SR-NYSEAMER-2020-05, SR-NYSEARCA-2020-08, SR-NYSECHX-2020-02, SR-NYSENAT-2020-03, SR-NYSE-2020-11, SR-NYSEAMER-2020-10, SR-NYSEArca-2020-15, SR-NYSECHX-2020-05, SR-NYSENAT-2020-08) (“Wireless Approval Order”), citing Securities Exchange Act Release No. 59039 (December 2, 2008), 73 FR 74770, 74781 (December 9, 2008) (“2008 ArcaBook Approval Order”). 
                        <E T="03">See NetCoalition</E>
                         v. 
                        <E T="03">SEC,</E>
                         615 F.3d 525 (D.C. Cir. 2010).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         
                        <E T="03">See</E>
                         Wireless Approval Order, 
                        <E T="03">supra</E>
                         note 17, at 67049, citing 2008 ArcaBook Approval Order, 
                        <E T="03">supra</E>
                         note 17, at 74781.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Substantially Similar Substitutes Are Available</HD>
                <P>
                    As described above,
                    <SU>19</SU>
                    <FTREF/>
                     Users may connect to the Proposed Third Party Data Feed independent of the options provided by the Exchange, creating competition for the Exchange's proposed Connectivity. A User may connect to a Proposed Third Party Data Feed by, first, entering into an agreement with the relevant third party for connectivity, and second, connecting to the Proposed Third Party Data Feed through one of the Telecoms. Users that establish access or connectivity independent of the Connectivity offered by the Exchange are not at any competitive disadvantage created by the Exchange. As of April 30, 2026, more than 98% of the circuits for which Users contracted were supplied by the Telecoms. Although IEX Options does not currently offer the Proposed Third Party Data Feed, the Exchange believes that once it is available, Users may independently establish connectivity to the Proposed Third Party Data Feed through one of the Telecoms.
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         
                        <E T="03">See</E>
                         “Competitive Environment,” above.
                    </P>
                </FTNT>
                <P>
                    Because Users are third parties and are not required to make such information public, the Exchange does not have visibility into how many Users will connect to the Proposed Third Party Data Feed (once it becomes available) independently, as described above.
                    <SU>20</SU>
                    <FTREF/>
                     However, the market for connectivity to the Proposed Third Party Data Feed is competitive, and there is no reason to believe that other actual or potential Users would not obtain connectivity independently if they considered it to be in their commercial interest.
                </P>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         As they are third parties, the Exchange does not have visibility into whether Users intend to connect to the Proposed Third Party Data Feed (once it is available) for their own use, or if they intend to offer other Users such connectivity.
                    </P>
                </FTNT>
                <P>
                    Such Users compete, or would compete, with the Exchange's Connectivity and exert, or would exert, significant competitive forces on the Exchange in setting the terms of its proposal, including the level of the Exchange's proposed fees.
                    <SU>21</SU>
                    <FTREF/>
                     If the Exchange were to set its proposed fees too high, Users could respond by instead selecting other substantially similar access and connectivity by independently establishing access and connectivity as described above.
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         
                        <E T="03">See</E>
                         2008 ArcaBook Approval Order, 
                        <E T="03">supra</E>
                         note 17, at 74789 and n.295 (recognizing that products need not be identical to be substitutable).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Users Are Not at a Competitive Disadvantage Created by the Exchange</HD>
                <P>The Exchange does not believe that FIDS would have any competitive advantage over Users that establish independent connectivity to the Proposed Third Party Data Feed. The Exchange's proposed service for Connectivity does not have (a) any special access to the Proposed Third Party Data Feeds or (b) advantage within the MDC, as all distances in the MDC are normalized.</P>
                <P>Moreover, the Exchange does not believe that FIDS would have any competitive advantage because it would charge for connectivity only, not the Proposed Third Party Data Feed itself. All Users that connect to the Proposed Third Party Data Feed, whether they elect to connect using the Exchange's proposed service or not, would have to pay a third party for the Proposed Third Party Data Feed.</P>
                <P>
                    Nor does the Exchange believe that FIDS has a competitive advantage by virtue of the fact that ICE owns and 
                    <PRTPAGE P="41141"/>
                    operates the MDC's meet-me-rooms. Users purchasing Connectivity—like Users of any other colocation service—would require a circuit connecting out of the MDC, and in most cases, such circuits are provided by Telecoms.
                    <SU>22</SU>
                    <FTREF/>
                     Currently, 17 Telecoms operate in the meet-me-rooms and provide a variety of circuit choices. It is in the Exchange's best interest to set the fees that Telecoms pay to operate in the meet-me-rooms at a reasonable level 
                    <SU>23</SU>
                    <FTREF/>
                     so that market participants, including Telecoms, will maximize their use of the MDC. By setting the meet-me-room fees at a reasonable level, the Exchange encourages Telecoms to participate in the meet-me-rooms and to sell circuits to Users for connecting into and out of the MDC. These Telecoms then compete with each other by pricing such circuits at competitive rates. These competitive rates for circuits help draw in more Users and Hosted Customers to the MDC, which directly benefits the Exchange by increasing the customer base to whom the Exchange can sell its colocation services, which include cabinets, power, ports, and connectivity to many third-party data feeds, and because having more Users and Hosted Customers leads, in many cases, to greater participation on the Exchange. In this way, by setting the meet-me-room fees at a level attractive to telecommunications firms, the Exchange spurs demand for all of the services it sells at the MDC, while setting the meet-me-room fees too high would negatively affect the Exchange's ability to sell its services at the MDC.
                    <SU>24</SU>
                    <FTREF/>
                     Accordingly, there are real constraints on the meet-me-room fees the Exchange charges, such that the Exchange does not have an advantage in terms of costs when compared to third parties that enter the MDC through the meet-me-rooms to provide services to compete with the Exchange's services.
                </P>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         Note that in the case of wireless connectivity, a User in colocation still requires a fiber circuit to transport data. If a Telecom is used, the data is transmitted wirelessly to the relevant pole, and then from the pole to the meet-me-room using a fiber circuit.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 98001 (July 26, 2023), 88 FR 50196 (August 1, 2023) (SR-NYSECHX-2023-14) (“MMR Notice”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         
                        <E T="03">See id.</E>
                         at 50199. Importantly, the Exchange is prevented from making any alteration to its meet-me-room services or fees without filing a proposal for such changes with the Commission.
                    </P>
                </FTNT>
                <P>If anything, the Exchange would be subject to a competitive disadvantage vis-à-vis Users regarding connectivity to the Proposed Third Party Data Feed. Users that choose to independently establish connectivity may negotiate terms with the Telecoms through whom such connectivity is delivered, in response to competitive forces. Such prices are not required to be filed by any party with the Commission. In contrast, the Exchange's service and pricing would be standardized as set out in this filing, and the Exchange would be unable to respond to pricing pressure from its competitors without seeking a formal fee change in a filing before the Commission.</P>
                <P>
                    In sum, because the Exchange is subject to significant competitive forces in setting the terms on which it offers its proposal, in particular because the Exchange believes that a substantially similar substitute is available, and the Exchange has not placed actual or proposed Users that already have or establish connectivity at a competitive disadvantage created by the Exchange, the proposed fee for the Exchange's access to the Proposed Third Party Data Feed is reasonable.
                    <SU>25</SU>
                    <FTREF/>
                     If the Exchange were to set its prices for connectivity to the Proposed Third Party Data Feeds at a level that Users found to be too high, Users could easily choose to connect to the Proposed Third Party Data Feed through Telecoms, as detailed above.
                </P>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         
                        <E T="03">See</E>
                         Wireless Approval Order, 
                        <E T="03">supra</E>
                         note 17.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Additional Considerations</HD>
                <P>
                    The Exchange believes that the proposed changes to the Cboe Data Feeds are reasonable. Specifically, the Exchange believes that the proposed changes are a reasonable response to the request from Users that certain Cboe Data Feeds be broken out by asset class, instead of by market. Under the proposed change, if a User wanted all Cboe U.S. Equities data, Cboe Options data or Cboe indices data it would not have to sign up for connectivity to more than one Third Party Data Feed. The Exchange believes that changing the placement of the “CFE” in, and adding the word “Exchange” to, Cboe Futures Exchange would be reasonable, given that the resulting change would mirror the name of the Cboe Futures Exchange.
                    <SU>26</SU>
                    <FTREF/>
                     The monthly recurring connectivity fees for each Cboe Data Feed would remain the same as they are now.
                </P>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         
                        <E T="03">See supra</E>
                         note 10.
                    </P>
                </FTNT>
                <P>Additionally, as with the Proposed Third Party Data Feed, Users may connect to the Cboe Data Feeds independent of the options provided by the Exchange, creating competition for the Exchange's proposed Connectivity. A User may connect to a Cboe Data Feed by, first, entering into an agreement with the relevant third party for connectivity, and second, connecting to the Cboe Data Feed through one of the Telecoms.</P>
                <P>The Exchange believes that the proposed fee for the Proposed Third Party Data Feed is reasonable, as it is the same as the existing fee for connectivity to IEX, which encompasses IEX Equities only. The Exchange believes that adding “Equities” after the existing text for connectivity to the IEX feed is reasonable, as it would clarify which IEX data feed was referenced.</P>
                <HD SOURCE="HD3">The Proposed Rule Change Is Equitable</HD>
                <P>The Exchange believes that the proposed rule change is equitable.</P>
                <P>The Exchange believes that the proposed changes to the Cboe Data Feeds is equitable because the monthly recurring connectivity fee for each Cboe Data Feed would remain the same as it is now. However, under the proposed change, if a User wanted all Cboe U.S. Equities data, Cboe Options data or Cboe indices data it would not have to sign up for connectivity to more than one Third Party Data Feed.</P>
                <P>
                    The Exchange believes that changing the placement of the “CFE” in, and adding “Exchange” to, Cboe Futures Exchange would be equitable, given that the resulting change would mirror the name of the Cboe Futures Exchange.
                    <SU>27</SU>
                    <FTREF/>
                     The proposed changes would make the Fee Schedule easier to read and understand and alleviate any possible market participant confusion caused by the current text.
                </P>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <P>For the same reason, the Exchange believes that adding “Equities” after the existing text for connectivity to the IEX feed is equitable, as it would clarify which IEX data feed was referenced, therefore making the Fee Schedule easier to read and understand and alleviating any possible market participant confusion caused by the current text.</P>
                <P>The Exchange believes that the proposed fee for connectivity to the Proposed Third Party Data Feed is an equitable allocation of fees. The proposed fee is the same as the existing fee for connectivity to IEX Equities.</P>
                <P>
                    Without this proposed rule change, Users would have fewer options for connectivity to the Proposed Third Party Data Feed, once that feed becomes available. By offering Connectivity, the Exchange gives each User additional options for addressing its needs, responding to User demand for options. Offering these additional services would help each User tailor its data center operations to the requirements of its business operations by allowing it to select the form and latency of connectivity that best suits its needs. Users that do not opt to utilize the 
                    <PRTPAGE P="41142"/>
                    Exchange's proposed Connectivity would still be able to connect to the Proposed Third Party Data Feed using Telecoms.
                </P>
                <P>The Exchange believes that the proposed change is equitable because it will result in fees being charged only to Users that voluntarily select to receive the corresponding services and because those services will be available to all Users.</P>
                <P>
                    Furthermore, the Exchange believes that the services and fees proposed herein are equitably allocated because, in addition to the services being completely voluntary, they are available to all Users on an equal basis (
                    <E T="03">i.e.,</E>
                     the same products and services are available to all Users). All Users that voluntarily select the Exchange's Connectivity would be charged the same amount for the same services. Users who opt not to use Connectivity would not be charged. In this way, the proposed rule change equitably allocates the proposed fees only to Users who choose to use the Exchange's Connectivity.
                </P>
                <HD SOURCE="HD3">The Proposed Change Is Not Unfairly Discriminatory</HD>
                <P>The Exchange believes that the proposed rule change is not unfairly discriminatory, for the following reasons.</P>
                <P>The Exchange believes that the proposed changes to the Cboe Data Feeds are not unfairly discriminatory because the monthly recurring connectivity fee for each Cboe Data Feed would remain the same as they are now. However, under the proposed change, if a User wanted all Cboe U.S. Equities data, Cboe Options data or Cboe indices data it would not have to sign up for connectivity to more than one Third Party Data Feed.</P>
                <P>Without this proposed rule change, Users would have fewer options for connectivity to the Proposed Third Party Data Feed. The proposed change would provide Users with an additional choice with respect to the form and optimal latency of their connectivity to the Proposed Third Party Data Feed, allowing a User to select the connectivity that better suits its needs, helping it tailor its colocation operations to the requirements of its business operations. Users that do not opt to utilize the Exchange's proposed Connectivity would still be able to connect to the Proposed Third Party Data Feed using Telecoms.</P>
                <P>
                    The Exchange believes that the proposed change is not unfairly discriminatory because it will result in fees being charged only to Users that voluntarily select to receive the corresponding services and because those services will be available to all Users. Furthermore, the Exchange believes that the services and fees proposed herein are not unfairly discriminatory because, in addition to the services being completely voluntary, they are available to all Users on an equal basis (
                    <E T="03">i.e.,</E>
                     the same products and services are available to all Users). All Users that voluntarily select the Exchange's Connectivity would be charged the same amount for the same services.
                </P>
                <P>For all these reasons, the Exchange believes that the proposal is consistent with the Act.</P>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition</HD>
                <P>
                    In accordance with Section 6(b)(8) of the Act,
                    <SU>28</SU>
                    <FTREF/>
                     the Exchange believes that the proposed rule change will not impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. The proposed change would not affect competition among national securities exchanges or among members of the Exchange, but rather between FIDS and its commercial competitors.
                </P>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         15 U.S.C. 78f(b)(8).
                    </P>
                </FTNT>
                <P>The Exchange does not believe that the proposed rule change regarding Cboe Data Feeds will impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. The monthly recurring connectivity fee for each Cboe Data Feed would remain the same as it is now. However, under the proposed change, if a User wanted all Cboe U.S. Equities data, Cboe Options data or Cboe indices data it would not have to sign up for connectivity to more than one Third Party Data Feed. The other changes to the Cboe Data Feeds would not affect competition.</P>
                <P>By offering Connectivity, the Exchange would give each User additional options for addressing its needs, responding to User demand for options. Providing additional services would help each User tailor its data center operations to the requirements of its business operations by allowing it to select the form and latency of connectivity that best suits its needs. Users that do not opt to utilize the Exchange's proposed Connectivity would still be able to connect to the Proposed Third Party Data Feed using Telecoms.</P>
                <P>The Exchange does not believe that FIDS would have any competitive advantage over Users that establish independent connectivity to the Proposed Third Party Data Feed. The Exchange's proposed service for Connectivity does not have (a) any special access to the Proposed Third Party Data Feed or (b) advantage within the MDC, as all distances in the MDC are normalized.</P>
                <P>Moreover, the Exchange does not believe that FIDS would have any competitive advantage because it would charge for connectivity only, not the Proposed Third Party Data Feed itself. All Users that connect to the Proposed Third Party Data Feed, whether they elect to connect using the Exchange's proposed service or not, would have to pay a third party for the Proposed Third Party Data Feed.</P>
                <P>
                    Nor does the Exchange believe that FIDS has a competitive advantage over any third-party competitors offering connectivity by virtue of the fact that ICE owns and operates the MDC's meet-me-rooms. Users purchasing Connectivity—like Users of any other colocation service—would require a circuit connecting out of the MDC, and in most cases, such circuits are provided by third-party Telecoms. Currently, 17 Telecoms operate in the meet-me-rooms and provide a variety of circuit choices. It is in the Exchange's best interest to set the fees that Telecoms pay to operate in the meet-me-rooms at a reasonable level 
                    <SU>29</SU>
                    <FTREF/>
                     so that market participants, including Telecoms, will maximize their use of the MDC. By setting the meet-me-room fees at a reasonable level, the Exchange encourages Telecoms to participate in the meet-me-rooms and to sell circuits to Users for connecting into and out of the MDC. These Telecoms then compete with each other by pricing such circuits at competitive rates. These competitive rates for circuits help draw in more Users and Hosted Customers to the MDC, which directly benefits the Exchange by increasing the customer base to whom the Exchange can sell its colocation services, which include cabinets, power, ports, and connectivity to many third-party data feeds, and because having more Users and Hosted Customers leads, in many cases, to greater participation on the Exchange. In this way, by setting the meet-me-room fees at a level attractive to telecommunications firms, the Exchange spurs demand for all of the services it sells at the MDC, while setting the meet-me-room fees too high would negatively affect the Exchange's ability to sell its services at the MDC.
                    <SU>30</SU>
                    <FTREF/>
                     Accordingly, there are real constraints on the meet-me-room fees the Exchange charges, such that the Exchange does not have an advantage in terms of costs when compared to third parties that enter the 
                    <PRTPAGE P="41143"/>
                    MDC through the meet-me-rooms to provide services to compete with the Exchange's services.
                </P>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         
                        <E T="03">See</E>
                         MMR Notice, 
                        <E T="03">supra</E>
                         note 23.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         
                        <E T="03">See supra</E>
                         note 24.
                    </P>
                </FTNT>
                <P>If anything, the Exchange would be subject to a competitive disadvantage vis-à-vis Users regarding connectivity to the Proposed Third Party Data Feed. Users that choose to independently establish connectivity may negotiate terms with the Telecoms or other Users through whom such connectivity is delivered, in response to competitive forces. Such prices are not required to be filed by any party with the Commission. In contrast, the Exchange's service and pricing would be standardized as set out in this filing, and the Exchange would be unable to respond to pricing pressure from its competitors without seeking a formal fee change in a filing before the Commission.</P>
                <P>The changes would not put any market participants at a relative disadvantage compared to other market participants or penalize one or more categories of market participants in a manner that would impose an undue burden on competition.</P>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants, or Others</HD>
                <P>No written comments were solicited or received with respect to the proposed rule change.</P>
                <HD SOURCE="HD2">D. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants, or Others</HD>
                <P>No written comments were solicited or received with respect to the proposed rule change.</P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
                <P>
                    The Exchange has filed the proposed rule change pursuant to Section 19(b)(3)(A)(iii) of the Act 
                    <SU>31</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) thereunder.
                    <SU>32</SU>
                    <FTREF/>
                     Because the proposed rule change does not: (i) significantly affect the protection of investors or the public interest; (ii) impose any significant burden on competition; and (iii) become operative prior to 30 days from the date on which it was filed, or such shorter time as the Commission may designate, if consistent with the protection of investors and the public interest, the proposed rule change has become effective pursuant to Section 19(b)(3)(A) of the Act 
                    <SU>33</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) 
                    <SU>34</SU>
                    <FTREF/>
                     thereunder.
                </P>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         15 U.S.C. 78s(b)(3)(A)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         17 CFR 240.19b-4(f)(6).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         15 U.S.C. 78s(b)(3)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         17 CFR 240.19b-4(f)(6). In addition, Rule 19b-4(f)(6) requires a self-regulatory organization to give the Commission written notice of its intent to file the proposed rule change, along with a brief description and text of the proposed rule change, at least five business days prior to the date of filing of the proposed rule change, or such shorter time as designated by the Commission. The Exchange has satisfied this requirement.
                    </P>
                </FTNT>
                <P>
                    At any time within 60 days of the filing of such proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act. If the Commission takes such action, the Commission shall institute proceedings under Section 19(b)(2)(B) 
                    <SU>35</SU>
                    <FTREF/>
                     of the Act to determine whether the proposed rule change should be approved or disapproved.
                </P>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         15 U.S.C. 78s(b)(2)(B).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
                <P>Interested persons are invited to submit written data, views and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:</P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's internet comment form (
                    <E T="03">https://www.sec.gov/rules/sro.shtml</E>
                    ); or
                </P>
                <P>
                    • Send an email to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include file number SR-NYSETEX-2026-25 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-NYSETEX-2026-25. 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-NYSETEX-2026-25 and should be submitted on or before July 27, 2026.
                </FP>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>36</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>36</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-13531 Filed 7-2-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-105823; File No. SR-NYSENAT-2026-21]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; NYSE National, Inc.; Notice of Filing and Immediate Effectiveness of a Proposed Rule Change To Amend the Connectivity Fee Schedule</SUBJECT>
                <DATE>June 30, 2026.</DATE>
                <P>
                    Pursuant to Section 19(b)(1) 
                    <SU>1</SU>
                    <FTREF/>
                     of the Securities Exchange Act of 1934 (“Act”) 
                    <SU>2</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>3</SU>
                    <FTREF/>
                     notice is hereby given that on June 18, 2026, NYSE National, Inc. (“NYSE National” or “Exchange”) filed with the Securities and Exchange Commission (“Commission”) the proposed rule change as described in Items I and II below, which Items have been prepared by the self-regulatory organization. The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         15 U.S.C. 78a.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <PRTPAGE P="41144"/>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>
                <P>
                    The Exchange proposes to amend the Connectivity Fee Schedule to amend the list of third party data feeds to which Users can connect. The proposed rule change is available on the Exchange's website at 
                    <E T="03">www.nyse.com</E>
                     and at the principal office of the Exchange.
                </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <P>In its filing with the Commission, the self-regulatory organization included statements concerning the purpose of, and basis for, the proposed rule change and discussed any comments it received on the proposed rule change. The text of those statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in sections A, B, and C below, of the most significant parts of such statements.</P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and the Statutory Basis for, the Proposed Rule Change</HD>
                <HD SOURCE="HD3">1. Purpose</HD>
                <P>
                    The Exchange proposes to amend the Connectivity Fee Schedule to amend the list of third party data feeds to which Users 
                    <SU>4</SU>
                    <FTREF/>
                     can connect. Currently, Users are offered connectivity to data feeds from third party markets and other content service providers (“Third Party Data Feeds”) at the Mahwah, New Jersey data center (“MDC”).
                    <SU>5</SU>
                    <FTREF/>
                     The Exchange now proposes to amend the names of the Cboe Global Markets, Inc. Third Party Data Feeds (excluding Cboe Canada) (“Cboe Data Feeds”) and incorporate a new feed from Investors Exchange LLC (“IEX”).
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         For purposes of the Exchange's colocation services, a “User” means any market participant that requests to receive colocation services directly from the Exchange. 
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 83351 (May 31, 2018), 83 FR 26314 at n.9 (June 6, 2018) (SR-NYSENAT-2018-07). As specified in the Fee Schedule, a User that incurs colocation fees for a particular colocation service pursuant thereto would not be subject to colocation fees for the same colocation service charged by the New York Stock Exchange LLC, NYSE American LLC, NYSE Arca, Inc., and NYSE Texas, Inc. (together, the “Affiliate SROs”). Each Affiliate SRO has submitted substantially the same proposed rule change to propose the change described herein.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         Through its Fixed Income and Data Services (“FIDS”) business, Intercontinental Exchange, Inc. (“ICE”) operates the MDC. The Exchange and the Affiliate SROs are indirect subsidiaries of ICE.
                    </P>
                </FTNT>
                <P>The Exchange expects that the proposed rule change would become operative by August 31, 2026. The Exchange will announce the date through a customer notice.</P>
                <HD SOURCE="HD3">Proposed Change to the Cboe Data Feeds</HD>
                <P>
                    Currently, the Cboe Data Feeds are set forth in the list of Third Party Data Feeds by market. However, Users have requested that certain of the Cboe Data Feeds be broken out by asset class instead, so that if a User wanted all of the Cboe equities 
                    <SU>6</SU>
                    <FTREF/>
                     data, Cboe options 
                    <SU>7</SU>
                    <FTREF/>
                     data, or Cboe indices data 
                    <SU>8</SU>
                    <FTREF/>
                     it would not have to sign up for connectivity to more than one Third Party Data Feed.
                    <SU>9</SU>
                    <FTREF/>
                     The Exchange proposes to make the requested change and to indicate the exchanges from which data is included in the Cboe equities (“Cboe U.S. Equites”) and Cboe options (“Cboe Options”) data feeds.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         Cboe U.S. Equities | Cboe (representing the four U.S. equities exchanges that Cboe operates as BZX Equities, BYX Equities, EDGA Equities, and EDGX Equities).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         See Cboe U.S. Options | Trade Equity, Index &amp; ETF Options | Cboe (stating that the four U.S.-listed cash equity options markets that Cboe operates are the Cboe Options Exchange, the Cboe C2 Options Exchange, Cboe BZX Options Exchange, and Cboe EDGX Options Exchange).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         The Cboe indices data is set out in the Cboe Global Indices Feed. See Cboe Global Indices Feed (stating that the Cboe Global Indices Feed has more than 1,900 Index Values available).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         Currently, in order to connect to all of the Cboe U.S. Equity data feeds a User would have to connect to two Third Party Data Feeds, and to connect to all of the Cboe Options data feeds a User would have to connect to three Third Party Data Feeds. In order to connect to the Cboe indices data a User currently would have to connect to one Third Party Data Feed and the proposed change would ensure that remains true.
                    </P>
                </FTNT>
                <P>
                    The Exchange also proposes to change the name of “Cboe CFE Futures” to “Cboe Futures Exchange (CFE)” to mirror the name of Cboe Futures Exchange 
                    <SU>10</SU>
                    <FTREF/>
                     and to reorder the Cboe Data Feeds to maintain alphabetical order.
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See, e.g.,</E>
                         Exchange Act Release No. 104973 (March 11, 2026), 91 FR 12631 (March 16, 2026) (SR-CFE-2026-002) (presenting the name as “Cboe Futures Exchange, LLC,” abbreviated to “CFE”).
                    </P>
                </FTNT>
                <P>Accordingly, the Exchange proposes to make the following changes to the Cboe Data Feeds listed under “Connectivity to Third Party Data Feeds” (proposed additions italicized, proposed deletions in brackets):</P>
                <GPOTABLE COLS="2" OPTS="L2,nj,tp0,i1" CDEF="s100,17">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Third party data feed</CHED>
                        <CHED H="1">
                            Monthly recurring
                            <LI>connectivity fee</LI>
                            <LI>per third party</LI>
                            <LI>data feed</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">[Cboe BZX Exchange (CboeBZX) and Cboe BYX Exchange (CboeBYX)]</ENT>
                        <ENT>[$1,500]</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Cboe Canada</ENT>
                        <ENT>2,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Cboe [CFE] Futures 
                            <E T="03">Exchange (CFE)</E>
                        </ENT>
                        <ENT>1,500</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            <E T="03">Cboe Global Indices Feed</E>
                        </ENT>
                        <ENT>
                            <E T="03">1,500</E>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Cboe 
                            <E T="03">Options</E>
                            [EDGX] Exchange
                            <E T="03">s</E>
                             (
                            <E T="03">Cboe Options Exchange, Cboe C2 Options Exchange, Cboe BZX Options Exchange, and</E>
                             Cboe EDGX
                            <E T="03"> Options Exchange</E>
                            ) [and Cboe EDGA Exchange (CboeEDGA)]
                        </ENT>
                        <ENT>1,500</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Cboe 
                            <E T="03">U.S Equities</E>
                             Exchange
                            <E T="03">s</E>
                             (Cboe 
                            <E T="03">EDGA Equities, Cboe EDGX Equities, Cboe BYX Equities and Cboe BZX Equities</E>
                            ) [and C2 Exchange (C2)]
                        </ENT>
                        <ENT>1,500</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD3">Proposed Change to the IEX Third Party Data Feed</HD>
                <P>
                    IEX has announced that it will launch a new options exchange (“IEX Options”) 
                    <SU>11</SU>
                    <FTREF/>
                     and that it intends to launch IEX Options on October 2, 2026.
                    <SU>12</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See</E>
                         “IEX Announces Planned Launch of Options Exchange End of Q1 2026,” available at 
                        <E T="03">https://www.iex.io/article/iex-announces-planned-launch-of-options-exchange-end-of-q1-2026.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">See</E>
                         “IEX Options Frequently Asked Questions,” question 1, available at 
                        <E T="03">https://cdn.prod.website-files.com/696f8ac812dcabe749e3aa49/69d7ddd79256713d06405c46_IEX%20Options%20FAQs.pdf.</E>
                         The proposed rule change is proposed to become operative before IEX offers IEX Options in order to allow Users time to connect, and test their connection, to IEX Options. The Exchange does not plan to charge for the connection until the IEX Options Third Party Data Feed is available.
                    </P>
                </FTNT>
                <P>
                    So that the Exchange may both offer connectivity to IEX Options and distinguish between IEX Options and the existing IEX equities exchange (“IEX Equities”), it proposes to make the following changes to the list of available Third Party Data Feeds (proposed additions italicized):
                    <PRTPAGE P="41145"/>
                </P>
                <GPOTABLE COLS="2" OPTS="L2,nj,tp0,i1" CDEF="s100,17">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Third party data feed</CHED>
                        <CHED H="1">
                            Monthly recurring
                            <LI>connectivity fee</LI>
                            <LI>per third party</LI>
                            <LI>data feed</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">
                            Investors Exchange (IEX) 
                            <E T="03">Equities</E>
                        </ENT>
                        <ENT>$1,300</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            <E T="03">Investors Exchange (IEX) Options</E>
                        </ENT>
                        <ENT>
                            <E T="03">1,300</E>
                        </ENT>
                    </ROW>
                </GPOTABLE>
                <P>The Exchange would provide connectivity to IEX Options as a convenience to Users.</P>
                <P>As with the existing connections to Third Party Data Feeds, including the existing connections to Cboe Data Feeds and to the IEX Equities data feed, the Exchange would receive a connection to the IEX Options data feed (the “Proposed Third Party Data Feed”) from the content service provider at the relevant source. The Exchange would then provide connectivity to that data to Users for a fee. Users would connect to IEX Options over the internet protocol (“IP”) network, a local area network available in the MDC. The Proposed Third Party Data Feed would include trading and other information concerning the securities that are traded on IEX Options.</P>
                <P>As with the existing connections to Third Party Data Feeds, including the existing connection to Cboe Data Feeds and the IEX Equities data feed, in order to connect to a Proposed Third Party Data Feed, a User would enter into a contract with the third party content service provider, pursuant to which it may charge the User for the data feed. The Exchange would receive the Proposed Third Party Data Feed in remote locations and transport it over its fiber optic network to the MDC. After the content service provider and User entered into an agreement and the Exchange received authorization from the content service provider, the Exchange would retransmit the data to the User over the User's port. The Exchange would charge the User for connectivity to the Proposed Third Party Data Feed. A User would only receive, and would only be charged the fee for, connectivity to a Proposed Third Party Data Feed for which it entered into a contract.</P>
                <P>The Exchange has no affiliation with the seller of the Proposed Third Party Data Feed and would have no right to use the feed other than as a redistributor of the data. The Proposed Third Party Data Feed would not provide access or order entry to the Exchange's execution system. The Proposed Third Party Data Feed would not provide access or order entry service to the execution systems of any third party generating the feed. The Exchange would receive the Proposed Third Party Data Feed via arms-length agreements and would have no inherent advantage over any other distributor of such data.</P>
                <HD SOURCE="HD3">Application and Impact of the Proposed Changes</HD>
                <P>The proposed rule change would not apply differently to distinct types or sizes of market participants. Rather, it would apply to all Users equally. As is currently the case, the purchase of any colocation service is completely voluntary and the Connectivity Fee Schedule is applied uniformly to all Users.</P>
                <P>Users have requested that certain of the Cboe Data Feeds be broken out by asset class, instead of by market. The Exchange believes that one current User would benefit from the change. It does not expect to gain customers as a result of breaking out certain of the Cboe Data Feeds by asset class or the other proposed changes to the Cboe Data Feeds.</P>
                <P>Connectivity to the Proposed Third Party Data Feed was requested by Users, but the Exchange believes that it would gain at most a handful of new customers due to the proposed change to the IEX data feeds.</P>
                <HD SOURCE="HD3">Competitive Environment</HD>
                <P>
                    The Exchange operates in a highly competitive market in which other vendors offer colocation services as a means to facilitate the trading and other market activities of those market participants who believe that colocation enhances the efficiency of their operations. The Commission has repeatedly expressed its preference for competition over regulatory intervention in determining prices, products, and services in the securities markets. Specifically, in Regulation NMS, the Commission highlighted the importance of market forces in determining prices and SRO revenues and, also, recognized that current regulation of the market system “has been remarkably successful in promoting market competition in its broader forms that are most important to investors and listed companies.” 
                    <SU>13</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 51808 (June 9, 2005), 70 FR 37496, 37499 (June 29, 2005).
                    </P>
                </FTNT>
                <P>As explained below, the Exchange's provision of connectivity to the Proposed Third Party Data Feed (“Connectivity”) may compete with connectivity provided by other third parties. Third-party vendors are not at any competitive disadvantage created by the Exchange.</P>
                <P>The proposed change is not otherwise intended to address any other issues relating to colocation services or related fees, and the Exchange is not aware of any problems that Users would have in complying with the proposed change.</P>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    The Exchange believes that the proposed rule change is consistent with Section 6(b) of the Act,
                    <SU>14</SU>
                    <FTREF/>
                     in general, and furthers the objectives of Section 6(b)(5) of the Act,
                    <SU>15</SU>
                    <FTREF/>
                     in particular, because it is designed to prevent fraudulent and manipulative acts and practices, to promote just and equitable principles of trade, to foster cooperation and coordination with persons engaged in regulating, clearing, settling, processing information with respect to, and facilitating transactions in securities, to remove impediments to and perfect the mechanism of a free and open market and a national market system, and, in general, to protect investors and the public interest and because it is not designed to permit unfair discrimination between customers, issuers, brokers, or dealers. The Exchange further believes that the proposed rule change is consistent with Section 6(b)(4) of the Act,
                    <SU>16</SU>
                    <FTREF/>
                     because it provides for the equitable allocation of reasonable dues, fees, and other charges among its members and issuers and other persons using its facilities.
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         15 U.S.C. 78f(b).0 [sic]
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         15 U.S.C. 78f(b)(4).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">The Proposed Rule Change Is Reasonable</HD>
                <P>The Exchange believes that the proposed rule change is reasonable.</P>
                <P>
                    In considering the reasonableness of proposed services and fees, the Commission's market-based test considers “whether the exchange was subject to significant competitive forces in setting the terms of its proposal . . . , including the level of any fees.” 
                    <SU>17</SU>
                    <FTREF/>
                     If the Exchange meets that 
                    <PRTPAGE P="41146"/>
                    burden, “the Commission will find that its proposal is consistent with the Act unless `there is a substantial countervailing basis to find that the terms' of the proposal violate the Act or the rules thereunder.” 
                    <SU>18</SU>
                    <FTREF/>
                     Here, the Exchange is subject to significant competitive forces in setting the terms on which it offers its proposal, in particular because substantially similar substitutes are available and the Exchange has not placed present or future third party vendors at a competitive disadvantage created by the Exchange.
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 90209 (October 15, 2020), 85 FR 67044, 67049 (October 21, 
                        <PRTPAGE/>
                        2020) (Order Granting Accelerated Approval to Establish a Wireless Fee Schedule Setting Forth Available Wireless Bandwidth Connections and Wireless Market Data Connections) (SR-NYSE-2020-05, SR-NYSEAMER-2020-05, SR-NYSEARCA-2020-08, SR-NYSECHX-2020-02, SR-NYSENAT-2020-03, SR-NYSE-2020-11, SR-NYSEAMER-2020-10, SR-NYSEArca-2020-15, SR-NYSECHX-2020-05, SR-NYSENAT-2020-08) (“Wireless Approval Order”), citing Securities Exchange Act Release No. 59039 (December 2, 2008), 73 FR 74770, 74781 (December 9, 2008) (“2008 ArcaBook Approval Order”). 
                        <E T="03">See NetCoalition</E>
                         v. 
                        <E T="03">SEC,</E>
                         615 F.3d 525 (D.C. Cir. 2010).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         
                        <E T="03">See</E>
                         Wireless Approval Order, 
                        <E T="03">supra</E>
                         note 17, at 67049, citing 2008 ArcaBook Approval Order, 
                        <E T="03">supra</E>
                         note 17, at 74781.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Substantially Similar Substitutes Are Available</HD>
                <P>
                    As described above,
                    <SU>19</SU>
                    <FTREF/>
                     Users may connect to the Proposed Third Party Data Feed independent of the options provided by the Exchange, creating competition for the Exchange's proposed Connectivity. A User may connect to a Proposed Third Party Data Feed by, first, entering into an agreement with the relevant third party for connectivity, and second, connecting to the Proposed Third Party Data Feed through one of the Telecoms. Users that establish access or connectivity independent of the Connectivity offered by the Exchange are not at any competitive disadvantage created by the Exchange. As of April 30, 2026, more than 98% of the circuits for which Users contracted were supplied by the Telecoms. Although IEX Options does not currently offer the Proposed Third Party Data Feed, the Exchange believes that once it is available, Users may independently establish connectivity to the Proposed Third Party Data Feed through one of the Telecoms.
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         
                        <E T="03">See</E>
                         “Competitive Environment,” above.
                    </P>
                </FTNT>
                <P>
                    Because Users are third parties and are not required to make such information public, the Exchange does not have visibility into how many Users will connect to the Proposed Third Party Data Feed (once it becomes available) independently, as described above.
                    <SU>20</SU>
                    <FTREF/>
                     However, the market for connectivity to the Proposed Third Party Data Feed is competitive, and there is no reason to believe that other actual or potential Users would not obtain connectivity independently if they considered it to be in their commercial interest.
                </P>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         As they are third parties, the Exchange does not have visibility into whether Users intend to connect to the Proposed Third Party Data Feed (once it is available) for their own use, or if they intend to offer other Users such connectivity.
                    </P>
                </FTNT>
                <P>
                    Such Users compete, or would compete, with the Exchange's Connectivity and exert, or would exert, significant competitive forces on the Exchange in setting the terms of its proposal, including the level of the Exchange's proposed fees.
                    <SU>21</SU>
                    <FTREF/>
                     If the Exchange were to set its proposed fees too high, Users could respond by instead selecting other substantially similar access and connectivity by independently establishing access and connectivity as described above.
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         
                        <E T="03">See</E>
                         2008 ArcaBook Approval Order, 
                        <E T="03">supra</E>
                         note 17, at 74789 and n.295 (recognizing that products need not be identical to be substitutable).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Users Are Not at a Competitive Disadvantage Created by the Exchange</HD>
                <P>The Exchange does not believe that FIDS would have any competitive advantage over Users that establish independent connectivity to the Proposed Third Party Data Feed. The Exchange's proposed service for Connectivity does not have (a) any special access to the Proposed Third Party Data Feeds or (b) advantage within the MDC, as all distances in the MDC are normalized.</P>
                <P>Moreover, the Exchange does not believe that FIDS would have any competitive advantage because it would charge for connectivity only, not the Proposed Third Party Data Feed itself. All Users that connect to the Proposed Third Party Data Feed, whether they elect to connect using the Exchange's proposed service or not, would have to pay a third party for the Proposed Third Party Data Feed.</P>
                <P>
                    Nor does the Exchange believe that FIDS has a competitive advantage by virtue of the fact that ICE owns and operates the MDC's meet-me-rooms. Users purchasing Connectivity—like Users of any other colocation service—would require a circuit connecting out of the MDC, and in most cases, such circuits are provided by Telecoms.
                    <SU>22</SU>
                    <FTREF/>
                     Currently, 17 Telecoms operate in the meet-me-rooms and provide a variety of circuit choices. It is in the Exchange's best interest to set the fees that Telecoms pay to operate in the meet-me-rooms at a reasonable level 
                    <SU>23</SU>
                    <FTREF/>
                     so that market participants, including Telecoms, will maximize their use of the MDC. By setting the meet-me-room fees at a reasonable level, the Exchange encourages Telecoms to participate in the meet-me-rooms and to sell circuits to Users for connecting into and out of the MDC. These Telecoms then compete with each other by pricing such circuits at competitive rates. These competitive rates for circuits help draw in more Users and Hosted Customers to the MDC, which directly benefits the Exchange by increasing the customer base to whom the Exchange can sell its colocation services, which include cabinets, power, ports, and connectivity to many third-party data feeds, and because having more Users and Hosted Customers leads, in many cases, to greater participation on the Exchange. In this way, by setting the meet-me-room fees at a level attractive to telecommunications firms, the Exchange spurs demand for all of the services it sells at the MDC, while setting the meet-me-room fees too high would negatively affect the Exchange's ability to sell its services at the MDC.
                    <SU>24</SU>
                    <FTREF/>
                     Accordingly, there are real constraints on the meet-me-room fees the Exchange charges, such that the Exchange does not have an advantage in terms of costs when compared to third parties that enter the MDC through the meet-me-rooms to provide services to compete with the Exchange's services.
                </P>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         Note that in the case of wireless connectivity, a User in colocation still requires a fiber circuit to transport data. If a Telecom is used, the data is transmitted wirelessly to the relevant pole, and then from the pole to the meet-me-room using a fiber circuit.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 98002 (July 26, 2023), 88 FR 50232 (August 1, 2023) (SR-NYSENat-2023-12) (“MMR Notice”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         
                        <E T="03">See id.</E>
                         at 50235. Importantly, the Exchange is prevented from making any alteration to its meet-me-room services or fees without filing a proposal for such changes with the Commission.
                    </P>
                </FTNT>
                <P>If anything, the Exchange would be subject to a competitive disadvantage vis-à-vis Users regarding connectivity to the Proposed Third Party Data Feed. Users that choose to independently establish connectivity may negotiate terms with the Telecoms through whom such connectivity is delivered, in response to competitive forces. Such prices are not required to be filed by any party with the Commission. In contrast, the Exchange's service and pricing would be standardized as set out in this filing, and the Exchange would be unable to respond to pricing pressure from its competitors without seeking a formal fee change in a filing before the Commission.</P>
                <P>
                    In sum, because the Exchange is subject to significant competitive forces 
                    <PRTPAGE P="41147"/>
                    in setting the terms on which it offers its proposal, in particular because the Exchange believes that a substantially similar substitute is available, and the Exchange has not placed actual or proposed Users that already have or establish connectivity at a competitive disadvantage created by the Exchange, the proposed fee for the Exchange's access to the Proposed Third Party Data Feed is reasonable.
                    <SU>25</SU>
                    <FTREF/>
                     If the Exchange were to set its prices for connectivity to the Proposed Third Party Data Feeds at a level that Users found to be too high, Users could easily choose to connect to the Proposed Third Party Data Feed through Telecoms, as detailed above.
                </P>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         
                        <E T="03">See</E>
                         Wireless Approval Order, 
                        <E T="03">supra</E>
                         note 17.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Additional Considerations</HD>
                <P>
                    The Exchange believes that the proposed changes to the Cboe Data Feeds are reasonable. Specifically, the Exchange believes that the proposed changes are a reasonable response to the request from Users that certain Cboe Data Feeds be broken out by asset class, instead of by market. Under the proposed change, if a User wanted all Cboe U.S. Equities data, Cboe Options data or Cboe indices data it would not have to sign up for connectivity to more than one Third Party Data Feed. The Exchange believes that changing the placement of the “CFE” in, and adding the word “Exchange” to, Cboe Futures Exchange would be reasonable, given that the resulting change would mirror the name of the Cboe Futures Exchange.
                    <SU>26</SU>
                    <FTREF/>
                     The monthly recurring connectivity fees for each Cboe Data Feed would remain the same as they are now.
                </P>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         
                        <E T="03">See supra</E>
                         note 10.
                    </P>
                </FTNT>
                <P>Additionally, as with the Proposed Third Party Data Feed, Users may connect to the Cboe Data Feeds independent of the options provided by the Exchange, creating competition for the Exchange's proposed Connectivity. A User may connect to a Cboe Data Feed by, first, entering into an agreement with the relevant third party for connectivity, and second, connecting to the Cboe Data Feed through one of the Telecoms.</P>
                <P>The Exchange believes that the proposed fee for the Proposed Third Party Data Feed is reasonable, as it is the same as the existing fee for connectivity to IEX, which encompasses IEX Equities only. The Exchange believes that adding “Equities” after the existing text for connectivity to the IEX feed is reasonable, as it would clarify which IEX data feed was referenced.</P>
                <HD SOURCE="HD3">The Proposed Rule Change Is Equitable</HD>
                <P>The Exchange believes that the proposed rule change is equitable.</P>
                <P>The Exchange believes that the proposed changes to the Cboe Data Feeds is equitable because the monthly recurring connectivity fee for each Cboe Data Feed would remain the same as it is now. However, under the proposed change, if a User wanted all Cboe U.S. Equities data, Cboe Options data or Cboe indices data it would not have to sign up for connectivity to more than one Third Party Data Feed.</P>
                <P>
                    The Exchange believes that changing the placement of the “CFE” in, and adding “Exchange” to, Cboe Futures Exchange would be equitable, given that the resulting change would mirror the name of the Cboe Futures Exchange.
                    <SU>27</SU>
                    <FTREF/>
                     The proposed changes would make the Fee Schedule easier to read and understand and alleviate any possible market participant confusion caused by the current text.
                </P>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <P>For the same reason, the Exchange believes that adding “Equities” after the existing text for connectivity to the IEX feed is equitable, as it would clarify which IEX data feed was referenced, therefore making the Fee Schedule easier to read and understand and alleviating any possible market participant confusion caused by the current text.</P>
                <P>The Exchange believes that the proposed fee for connectivity to the Proposed Third Party Data Feed is an equitable allocation of fees. The proposed fee is the same as the existing fee for connectivity to IEX Equities.</P>
                <P>Without this proposed rule change, Users would have fewer options for connectivity to the Proposed Third Party Data Feed, once that feed becomes available. By offering Connectivity, the Exchange gives each User additional options for addressing its needs, responding to User demand for options. Offering these additional services would help each User tailor its data center operations to the requirements of its business operations by allowing it to select the form and latency of connectivity that best suits its needs. Users that do not opt to utilize the Exchange's proposed Connectivity would still be able to connect to the Proposed Third Party Data Feed using Telecoms.</P>
                <P>The Exchange believes that the proposed change is equitable because it will result in fees being charged only to Users that voluntarily select to receive the corresponding services and because those services will be available to all Users.</P>
                <P>
                    Furthermore, the Exchange believes that the services and fees proposed herein are equitably allocated because, in addition to the services being completely voluntary, they are available to all Users on an equal basis (
                    <E T="03">i.e.,</E>
                     the same products and services are available to all Users). All Users that voluntarily select the Exchange's Connectivity would be charged the same amount for the same services. Users who opt not to use Connectivity would not be charged. In this way, the proposed rule change equitably allocates the proposed fees only to Users who choose to use the Exchange's Connectivity.
                </P>
                <HD SOURCE="HD3">The Proposed Change Is Not Unfairly Discriminatory</HD>
                <P>The Exchange believes that the proposed rule change is not unfairly discriminatory, for the following reasons.</P>
                <P>The Exchange believes that the proposed changes to the Cboe Data Feeds are not unfairly discriminatory because the monthly recurring connectivity fee for each Cboe Data Feed would remain the same as they are now. However, under the proposed change, if a User wanted all Cboe U.S. Equities data, Cboe Options data or Cboe indices data it would not have to sign up for connectivity to more than one Third Party Data Feed.</P>
                <P>Without this proposed rule change, Users would have fewer options for connectivity to the Proposed Third Party Data Feed. The proposed change would provide Users with an additional choice with respect to the form and optimal latency of their connectivity to the Proposed Third Party Data Feed, allowing a User to select the connectivity that better suits its needs, helping it tailor its colocation operations to the requirements of its business operations. Users that do not opt to utilize the Exchange's proposed Connectivity would still be able to connect to the Proposed Third Party Data Feed using Telecoms.</P>
                <P>
                    The Exchange believes that the proposed change is not unfairly discriminatory because it will result in fees being charged only to Users that voluntarily select to receive the corresponding services and because those services will be available to all Users. Furthermore, the Exchange believes that the services and fees proposed herein are not unfairly discriminatory because, in addition to the services being completely voluntary, they are available to all Users on an equal basis (
                    <E T="03">i.e.,</E>
                     the same products and services are available to all Users). All Users that voluntarily select the Exchange's Connectivity would be 
                    <PRTPAGE P="41148"/>
                    charged the same amount for the same services.
                </P>
                <P>For all these reasons, the Exchange believes that the proposal is consistent with the Act.</P>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition</HD>
                <P>
                    In accordance with Section 6(b)(8) of the Act,
                    <SU>28</SU>
                    <FTREF/>
                     the Exchange believes that the proposed rule change will not impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. The proposed change would not affect competition among national securities exchanges or among members of the Exchange, but rather between FIDS and its commercial competitors.
                </P>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         15 U.S.C. 78f(b)(8).
                    </P>
                </FTNT>
                <P>The Exchange does not believe that the proposed rule change regarding Cboe Data Feeds will impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. The monthly recurring connectivity fee for each Cboe Data Feed would remain the same as it is now. However, under the proposed change, if a User wanted all Cboe U.S. Equities data, Cboe Options data or Cboe indices data it would not have to sign up for connectivity to more than one Third Party Data Feed. The other changes to the Cboe Data Feeds would not affect competition.</P>
                <P>By offering Connectivity, the Exchange would give each User additional options for addressing its needs, responding to User demand for options. Providing additional services would help each User tailor its data center operations to the requirements of its business operations by allowing it to select the form and latency of connectivity that best suits its needs. Users that do not opt to utilize the Exchange's proposed Connectivity would still be able to connect to the Proposed Third Party Data Feed using Telecoms.</P>
                <P>The Exchange does not believe that FIDS would have any competitive advantage over Users that establish independent connectivity to the Proposed Third Party Data Feed. The Exchange's proposed service for Connectivity does not have (a) any special access to the Proposed Third Party Data Feed or (b) advantage within the MDC, as all distances in the MDC are normalized.</P>
                <P>Moreover, the Exchange does not believe that FIDS would have any competitive advantage because it would charge for connectivity only, not the Proposed Third Party Data Feed itself. All Users that connect to the Proposed Third Party Data Feed, whether they elect to connect using the Exchange's proposed service or not, would have to pay a third party for the Proposed Third Party Data Feed.</P>
                <P>
                    Nor does the Exchange believe that FIDS has a competitive advantage over any third-party competitors offering connectivity by virtue of the fact that ICE owns and operates the MDC's meet-me-rooms. Users purchasing Connectivity—like Users of any other colocation service—would require a circuit connecting out of the MDC, and in most cases, such circuits are provided by third-party Telecoms. Currently, 17 Telecoms operate in the meet-me-rooms and provide a variety of circuit choices. It is in the Exchange's best interest to set the fees that Telecoms pay to operate in the meet-me-rooms at a reasonable level 
                    <SU>29</SU>
                    <FTREF/>
                     so that market participants, including Telecoms, will maximize their use of the MDC. By setting the meet-me-room fees at a reasonable level, the Exchange encourages Telecoms to participate in the meet-me-rooms and to sell circuits to Users for connecting into and out of the MDC. These Telecoms then compete with each other by pricing such circuits at competitive rates. These competitive rates for circuits help draw in more Users and Hosted Customers to the MDC, which directly benefits the Exchange by increasing the customer base to whom the Exchange can sell its colocation services, which include cabinets, power, ports, and connectivity to many third-party data feeds, and because having more Users and Hosted Customers leads, in many cases, to greater participation on the Exchange. In this way, by setting the meet-me-room fees at a level attractive to telecommunications firms, the Exchange spurs demand for all of the services it sells at the MDC, while setting the meet-me-room fees too high would negatively affect the Exchange's ability to sell its services at the MDC.
                    <SU>30</SU>
                    <FTREF/>
                     Accordingly, there are real constraints on the meet-me-room fees the Exchange charges, such that the Exchange does not have an advantage in terms of costs when compared to third parties that enter the MDC through the meet-me-rooms to provide services to compete with the Exchange's services.
                </P>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         
                        <E T="03">See</E>
                         MMR Notice, 
                        <E T="03">supra</E>
                         note 23.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         
                        <E T="03">See supra</E>
                         note 24.
                    </P>
                </FTNT>
                <P>If anything, the Exchange would be subject to a competitive disadvantage vis-à-vis Users regarding connectivity to the Proposed Third Party Data Feed. Users that choose to independently establish connectivity may negotiate terms with the Telecoms or other Users through whom such connectivity is delivered, in response to competitive forces. Such prices are not required to be filed by any party with the Commission. In contrast, the Exchange's service and pricing would be standardized as set out in this filing, and the Exchange would be unable to respond to pricing pressure from its competitors without seeking a formal fee change in a filing before the Commission.</P>
                <P>The changes would not put any market participants at a relative disadvantage compared to other market participants or penalize one or more categories of market participants in a manner that would impose an undue burden on competition.</P>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants, or Others</HD>
                <P>No written comments were solicited or received with respect to the proposed rule change.</P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
                <P>
                    The Exchange has filed the proposed rule change pursuant to Section 19(b)(3)(A)(iii) of the Act 
                    <SU>31</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) thereunder.
                    <SU>32</SU>
                    <FTREF/>
                     Because the proposed rule change does not: (i) significantly affect the protection of investors or the public interest; (ii) impose any significant burden on competition; and (iii) become operative prior to 30 days from the date on which it was filed, or such shorter time as the Commission may designate, if consistent with the protection of investors and the public interest, the proposed rule change has become effective pursuant to Section 19(b)(3)(A) of the Act 
                    <SU>33</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) 
                    <SU>34</SU>
                    <FTREF/>
                     thereunder.
                </P>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         15 U.S.C. 78s(b)(3)(A)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         17 CFR 240.19b-4(f)(6).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         15 U.S.C. 78s(b)(3)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         17 CFR 240.19b-4(f)(6). In addition, Rule 19b-4(f)(6) requires a self-regulatory organization to give the Commission written notice of its intent to file the proposed rule change, along with a brief description and text of the proposed rule change, at least five business days prior to the date of filing of the proposed rule change, or such shorter time as designated by the Commission. The Exchange has satisfied this requirement.
                    </P>
                </FTNT>
                <P>
                    At any time within 60 days of the filing of such proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act. If the Commission takes such action, the 
                    <PRTPAGE P="41149"/>
                    Commission shall institute proceedings under Section 19(b)(2)(B) 
                    <SU>35</SU>
                    <FTREF/>
                     of the Act to determine whether the proposed rule change should be approved or disapproved.
                </P>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         15 U.S.C. 78s(b)(2)(B).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
                <P>Interested persons are invited to submit written data, views and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:</P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's internet comment form (
                    <E T="03">https://www.sec.gov/rules/sro.shtml</E>
                    ); or
                </P>
                <P>
                    • Send an email to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include file number SR-NYSENAT-2026-21 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-NYSENAT-2026-21. 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-NYSENAT-2026-21 and should be submitted on or before July 27, 2026.
                </FP>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>36</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>36</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-13529 Filed 7-2-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-105827; File No. SR-NYSEAMER-2026-56]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; NYSE American LLC; Notice of Filing and Immediate Effectiveness of a Proposed Rule Change To Modify the NYSE American Options Fee Schedule Regarding Fees and Rebates Applicable to Manual Transactions</SUBJECT>
                <DATE>June 30, 2026.</DATE>
                <P>
                    Pursuant to Section 19(b)(1) 
                    <SU>1</SU>
                    <FTREF/>
                     of the Securities Exchange Act of 1934 (“Act”) 
                    <SU>2</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>3</SU>
                    <FTREF/>
                     notice is hereby given that, on June 22, 2026, NYSE American LLC (“NYSE American” or the “Exchange”) filed with the Securities and Exchange Commission (the “Commission”) the proposed rule change as described in Items I and II below, which Items have been prepared by the self-regulatory organization. The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         15 U.S.C. 78a.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>
                <P>
                    The Exchange proposes to modify the NYSE American Options Fee Schedule (“Fee Schedule”) regarding fees and rebates applicable to Manual transactions. The proposed rule change is available on the Exchange's website at 
                    <E T="03">www.nyse.com</E>
                     and at the principal office of the Exchange.
                </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <P>In its filing with the Commission, the self-regulatory organization included statements concerning the purpose of, and basis for, the proposed rule change and discussed any comments it received on the proposed rule change. The text of those statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in sections A, B, and C below, of the most significant parts of such statements.</P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and the Statutory Basis for, the Proposed Rule Change</HD>
                <HD SOURCE="HD3">1. Purpose</HD>
                <P>
                    The purpose of this filing is to amend the Fee Schedule to modify fees and rebates applicable to Manual transactions. Specifically, the Exchange proposes to (1) amend fees applicable to Manual transactions in non-Penny issues executed by e-Specialists, Market Makers, and Specialists (collectively, “Market Makers”), and (2) establish a rebate payable to Floor Broker orders that trade with a Market Maker order on the Trading Floor (“Trading Floor” or “Floor”). The Exchange proposes the fee change to be effective June 22, 2026.
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         The Exchange previously filed to amend the Fee Schedule several times beginning on January 2, 2026, all of which filings were withdrawn and replaced by another filing. Most recently, the Exchange amended the Fee Schedule on May 19, 2026 (SR-NYSEAMER-2026-44) which filing the Exchange withdrew on June 22, 2026. The Exchange notes that previous filing proposed changes to a complex order surcharge that are not included in this filing.
                    </P>
                </FTNT>
                <P>The Exchange proposes to amend Section I.A. of the Fee Schedule, which sets forth rates for Electronic and Manual transactions, in both Penny and non-Penny issues. Currently, a $0.50 per contract fee applies to Market Makers' Manual transactions in non-Penny issues (except for Manual transactions in MXEA, MXEF, MXUSA, MXWLD, and MXACW). The Exchange proposes to increase this fee to $1.00 per contract.</P>
                <P>The Exchange also proposes to establish a rebate of $0.20 per contract payable to Floor Broker orders that trade with Market Maker orders on the Trading Floor. For Floor Brokers that participate in the FB Prepay Program, the proposed rebate would apply in lieu of any rebates earned through the Manual Billable Rebate Program as provided in Section III. E. of the Fee Schedule. The Exchange proposes to add new text to Section III.E. of the Fee Schedule describing the proposed rebate.</P>
                <P>
                    The Exchange believes that the proposed rebate would continue to incentivize Floor Brokers to participate on the Trading Floor, including when the counterparty to such trading is a Market Maker. In addition, although the proposed change to the Market Maker fee for Manual transactions in non-Penny issues would increase the fee for such executions, the Exchange believes the proposed change, taken together with the proposed Floor Broker rebate would, on balance, not discourage Market Makers from continuing to participate in transactions on the 
                    <PRTPAGE P="41150"/>
                    Trading Floor, thereby promoting trading opportunities and competition on the Floor to the benefit of all market participants. The Exchange also notes that the amount of the proposed fee for Market Maker Manual transactions in non-Penny issues is within the range of fees currently in place for transactions by Market Makers (and other market participants) in non-Penny issues.
                    <SU>5</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See, e.g.,</E>
                         Fee Schedule, Section I.A., Rates for Options transactions (providing for $0.85 fee for Broker-Dealer, Firm, Non-NYSE American Options Market Maker, and Professional Customer electronic transactions in non-Penny issues and $0.95 fee for Market Maker electronic transactions in non-Penny issues (inclusive of Marketing Charges applicable to such transactions)).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    The Exchange believes that the proposed rule change is consistent with Section 6(b) of the Act,
                    <SU>6</SU>
                    <FTREF/>
                     in general, and furthers the objectives of Sections 6(b)(4) and (5) of the Act,
                    <SU>7</SU>
                    <FTREF/>
                     in particular, because it provides for the equitable allocation of reasonable dues, fees, and other charges among its members, issuers and other persons using its facilities and does not unfairly discriminate between customers, issuers, brokers or dealers.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         15 U.S.C. 78f(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         15 U.S.C. 78f(b)(4) and (5).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">The Proposed Rule Change Is Reasonable</HD>
                <P>
                    The Exchange operates in a highly competitive market. The Commission has repeatedly expressed its preference for competition over regulatory intervention in determining prices, products, and services in the securities markets. In Regulation NMS, the Commission highlighted the importance of market forces in determining prices and SRO revenues and, also, recognized that current regulation of the market system “has been remarkably successful in promoting market competition in its broader forms that are most important to investors and listed companies.” 
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 51808 (June 9, 2005), 70 FR 37496, 37499 (June 29, 2005) (S7-10-04) (“Reg NMS Adopting Release”).
                    </P>
                </FTNT>
                <P>
                    There are currently 18 registered options exchanges competing for order flow. Based on publicly-available information, and excluding index-based options, no single exchange has more than 16% of the market share of executed volume of multiply-listed equity and ETF options trades.
                    <SU>9</SU>
                    <FTREF/>
                     Therefore, currently no exchange possesses significant pricing power in the execution of multiply-listed equity and ETF options order flow. More specifically, in May 2026, the Exchange had 10.37% market share of executed volume of multiply-listed equity and ETF options trades.
                    <SU>10</SU>
                    <FTREF/>
                     In such a low-concentrated and highly competitive market, no single options exchange possesses significant pricing power in the execution of options order flow. Within this environment, market participants can freely and often do shift their order flow among the Exchange and competing venues in response to changes in their respective pricing schedules.
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         The OCC publishes options and futures volume in a variety of formats, including daily and monthly volume by exchange, available here: 
                        <E T="03">https://www.theocc.com/Market-Data/Market-Data-Reports/Volume-and-Open-Interest/Monthly-Weekly-Volume-Statistics.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         Based on a compilation of OCC data for monthly volume of equity-based options and monthly volume of equity-based ETF options, 
                        <E T="03">see id.,</E>
                         the Exchange's market share in equity-based options increased from 6.14% for the month of May 2025 to 10.37% for the month of May 2026.
                    </P>
                </FTNT>
                <P>The Exchange believes that the ever-shifting market share among the exchanges from month to month demonstrates that market participants can shift order flow or discontinue or reduce use of certain categories of products, in response to fee changes. Accordingly, competitive forces constrain options exchange transaction fees.</P>
                <P>The Exchange believes that the proposed rebate is reasonable because it would incentivize Floor Brokers to direct additional Manual orders to the Exchange, thereby creating more trading opportunities on the Trading Floor for all market participants, including Market Makers, who, therefore, would not be discouraged from continuing to quote and trade actively on the Exchange. The Exchange also believes that, in addition to benefitting all market participants, the amount of the proposed fee for Market Maker Manual transactions in non-Penny issues is reasonable, as it remains within the range of fees set forth in the Fee Schedule for transactions by Market Makers in non-Penny issues and more closely aligns with the fee applicable to electronic transactions by Market Makers in non-Penny issues.</P>
                <P>
                    Furthermore, the Exchange believes that assessing a higher fee for manual transactions on the Trading Floor is reasonable considering the distinct advantages afforded to Floor-based Market Makers. In May 2026, approximately 95% of Market Maker Manual volume in non-Penny issues was generated by Trading Floor-based Market Makers who, by virtue of their physical presence and participation model, are uniquely positioned to evaluate the full terms of a transaction, including size, pricing, and counterparty interest, immediately prior to execution. This capability enables Market Makers to exercise discretion in determining whether to engage in a trade under informed conditions that are not available to off-floor or fully electronic participants. In addition, the Exchange's rules provide Floor-based Market Makers with a guaranteed participation entitlement of up to 60% of the trade for both Solicitation and Facilitation Cross Transactions,
                    <SU>11</SU>
                    <FTREF/>
                     even in the absence of price improvement. This allocation represents a meaningful structural advantage as it ensures a substantial share of order flow once a Floor-based Market Maker elects to participate.
                    <SU>12</SU>
                    <FTREF/>
                     Together, these features—the ability to assess trading opportunities in real time before committing capital and the certainty of receiving a guaranteed, significant allocation—enhance the likelihood of favorable execution outcomes and revenue opportunities for Floor-based Market Makers. Accordingly, the Exchange believes it is reasonable to assess higher fees on Market Maker Manual transactions in non-Penny issues. The differential reflects the enhanced trading privileges, informational advantages, and allocation guarantees that are uniquely available to Trading Floor-based participants and serves to appropriately align fees with the relative value of these benefits as compared to other market participants operating without such advantages.
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See</E>
                         Rule 934.3NY and Rule 934.1NY(4)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         This is a significant benefit. While some Market Maker Manual volume derives from upstairs paired transactions, where these benefits are not present, such activity constitutes only a small percentage of overall Market Maker Manual activity
                    </P>
                </FTNT>
                <P>
                    The Exchange believes that the proposed changes are reasonably designed to incent Floor Brokers (and other participants on the Trading Floor) to increase the number of Manual orders sent to the Exchange. Any increase in trading volume would create more trading opportunities for all market participants and would in turn attract additional order flow to the Exchange, further contributing to a deeper, more liquid market to the benefit of all market participants. The Exchange also notes that the proposed rebate is similar in structure to incentive programs for Floor Brokers offered by competing options exchanges.
                    <SU>13</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See, e.g.,</E>
                         BOX Exchange Fee Schedule, Section V. Manual Transaction Fees, available at 
                        <E T="03">https://boxexchange.com/assets/BOX-Fee-Schedule-as-of-January-22-2026.pdf</E>
                         (offering Floor Brokers that submit QOO and FOO Orders a $0.20 per contract enhanced rebate for executions that trade with a Floor Market Maker, in lieu of lesser per contract rebates also available to Floor Brokers); MIAX Sapphire Options Exchange, Section 1) c) Trading 
                        <PRTPAGE/>
                        Floor Transactions, available at 
                        <E T="03">https://www.miaxglobal.com/sites/default/files/fee_schedule-files/MIAX_Sapphire_Fee_Schedule_01212026_b.pdf</E>
                         (providing for the “Floor Broker Breakup Credit,” a $0.20 credit applicable to Floor Brokers that submit a QFO or cQFO for executions that trade with a Floor Market Maker, instead of the $0.10 Floor Broker rebate otherwise available).
                    </P>
                </FTNT>
                <PRTPAGE P="41151"/>
                <P>The Exchange further believes the proposed change is reasonable because it is designed to offset costs associated with the proposed Floor Broker rebate, which, as noted above, is being proposed to create more trading opportunities on the Trading Floor for all market participants, including Market Makers. To the extent this purpose is achieved, the Exchange believes that the proposed change would not disincentivize Market Maker activity on the Trading Floor because increased order flow from Floor Brokers seeking to earn the proposed rebate would result in more opportunities to trade for all market participants. In addition, the Exchange notes that market participants are free to conduct transactions on competing venues instead if they believe other markets offer more favorable fees and credits.</P>
                <P>To the extent the proposed rule change continues to attract greater volume and liquidity by encouraging Floor Brokers to increase their options volume on the Exchange in an effort to earn the proposed rebate, the Exchange believes the proposed changes would improve the Exchange's overall competitiveness and strengthen its market quality for all market participants. Against the backdrop of the competitive environment in which the Exchange operates, the proposed rule change is a reasonable attempt by the Exchange to increase the depth of its market and improve its market share relative to its competitors.</P>
                <HD SOURCE="HD3">The Proposed Rule Change Is an Equitable Allocation of Credits and Fees</HD>
                <P>
                    The Exchange believes the proposed rule change is an equitable allocation of its fees and credits because the proposed rebate is based on the amount and type of business transacted on the Exchange, and Floor Brokers can try to earn the proposed rebate, or not. The Exchange also believes that the proposed change to the fee applicable to Market Maker Manual transactions in non-Penny issues is equitable because it is designed to balance costs associated with encouraging increased execution opportunities on the Trading Floor, and an increase in such orders would in turn enhance trading opportunities for all market participants. In addition, the proposed fee is within the range of fees currently applicable to transactions by Market Makers and other market participants in non-Penny issues. The Exchange further believes that assessing Market Makers a higher fee for Manual transactions in non-Penny issues is equitable because Floor-based Market Makers, who account for the majority of such volume, occupy a uniquely advantaged position relative to other market participants. Specifically, they benefit from the exclusive ability to evaluate the terms of a transaction immediately prior to execution as well as a guaranteed participation allocation of up to 60% of the trade under the Exchange's rules.
                    <SU>14</SU>
                    <FTREF/>
                     The Exchange also believes that the proposed rebate to Floor Brokers is an equitable allocation of fees and credits because it is intended to support Floor Brokers' role in facilitating the execution of Manual orders, which function benefits all market participants on the Trading Floor, including Market Makers.
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">See</E>
                         note 11, 
                        <E T="03">supra.</E>
                    </P>
                </FTNT>
                <P>Moreover, the proposal is designed to incent participation on the Trading Floor in an effort to make the Exchange a primary execution venue and to attract more Manual transactions to the Exchange. To the extent that the proposed change attracts more Floor Broker orders to the Exchange, this increased order flow would continue to make the Exchange a more competitive venue for, among other things, order execution. Thus, the Exchange believes the proposed rule change would improve market quality for all market participants on the Exchange and, as a consequence, attract more order flow to the Exchange thereby improving market-wide quality and price discovery.</P>
                <HD SOURCE="HD3">The Proposed Rule Change Is Not Unfairly Discriminatory</HD>
                <P>
                    The Exchange believes it is not unfairly discriminatory to modify the fee applicable to Market Maker Manual transactions in non-Penny issues because the proposed change would apply to all similarly-situated Market Maker orders equally, and as discussed above, the Exchange believes it is not unfairly discriminatory to incent order flow to the Exchange, which would enhance liquidity on the Exchange to the benefit of all market participants. The Exchange also believes that the proposed rebate payable to Floor Brokers for a Manual order that trades with a Market Maker order on the Trading Floor is not unfairly discriminatory because it would be available to all similarly situated market participants on an equal and non-discriminatory basis. The Exchange further believes that the proposed rebate available to Floor Brokers is not unfairly discriminatory to other market participants because it is intended to encourage the role performed by Floor Brokers in facilitating the execution of orders via open outcry, a function which the Exchange wishes to support for the benefit of all market participants. In addition, although the proposed change would increase the fee applicable to Market Maker Manual transactions in non-Penny issues, the Exchange notes that the amount of the proposed fee is within the range of fees currently applicable to transactions by Market Makers and other market participants in non-Penny issues and believes that Market Makers would not be discouraged from continuing to participate actively on the Trading Floor and would benefit from increased Manual order flow, including from Floor Brokers seeking to earn the proposed rebate, as a result of the proposed change. The Exchange also believes that the higher fee assessed to Market Makers for Manual transactions in non-Penny issues is not unfairly discriminatory because it reasonably reflects the uniquely advantaged position of Trading Floor-based Market Makers, who generate a significant portion of such volume, relative to other market participants. In particular, these Trading Floor-based Market Makers possess the exclusive ability to evaluate the full terms of a transaction immediately prior to execution and benefit from a guaranteed participation allocation of up to 60% of the trade under the Exchange's rules.
                    <SU>15</SU>
                    <FTREF/>
                     These features provide Floor-based Market Makers with meaningful informational and allocation advantages that are not available to off-floor or purely electronic participants. Accordingly, the Exchange believes that the differential in fees is appropriately calibrated to the distinct structural benefits available to Trading Floor-based Market Makers and therefore does not constitute unfair discrimination. Rather, the higher fee reflects a rational alignment between pricing and the value of the enhanced trading opportunities and execution certainty afforded to these participants. Moreover, to the extent that the exercise of these advantages contributes to increased Trading Floor activity and attracts additional order flow, the proposed fee would enhance overall market quality, deepen liquidity, and promote additional trading opportunities for all market participants on the Exchange.
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">See</E>
                         note 11, 
                        <E T="03">supra.</E>
                    </P>
                </FTNT>
                <P>
                    Finally, the Exchange believes that it is subject to significant competitive 
                    <PRTPAGE P="41152"/>
                    forces, as described below in the Exchange's statement regarding the burden on competition.
                </P>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition</HD>
                <P>
                    In accordance with Section 6(b)(8) of the Act, the Exchange does not believe that the proposed rule change would impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. Instead, as discussed above, the Exchange believes that the proposed changes would encourage the submission of additional liquidity to a public exchange, thereby promoting market depth, price discovery and transparency and enhancing order execution opportunities for all market participants. As a result, the Exchange believes that the proposed change furthers the Commission's goal in adopting Regulation NMS of fostering integrated competition among orders, which promotes “more efficient pricing of individual stocks for all types of orders, large and small.” 
                    <SU>16</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         
                        <E T="03">See</E>
                         Reg NMS Adopting Release, note 8 
                        <E T="03">supra,</E>
                         at 37499.
                    </P>
                </FTNT>
                <P>
                    <E T="03">Intramarket Competition.</E>
                     The proposed change is designed to attract additional order flow to the Exchange. The Exchange believes that the proposed change to Market Maker fees for Manual transactions in non-Penny issues, and the proposed rebate payable to the Floor Broker orders that trade against Market Maker orders on the Trading Floor would encourage Floor Broker Manual order flow and would not disincentivize Market Maker activity on the Trading Floor. Greater liquidity benefits all market participants on the Exchange and increased order flow would increase opportunities for execution of other trading interest. The proposed changes would apply and be available to all similarly situated market participants that execute Manual transactions on the Trading Floor, and, accordingly, the proposed changes would not impose a disparate burden on competition among market participants on the Exchange.
                </P>
                <P>
                    <E T="03">Intermarket Competition.</E>
                     The Exchange operates in a highly competitive market in which market participants can readily favor one of the other 18 competing options exchanges if they deem the Exchange's fee levels to be excessive. In such an environment, the Exchange must continually adjust its fees to remain competitive with other exchanges and to attract order flow to the Exchange. Based on publicly available information, and excluding index-based options, no single exchange has more than 16% of the market share of executed volume of multiply-listed equity and ETF options trades.
                    <SU>17</SU>
                    <FTREF/>
                     Therefore, currently no exchange possesses significant pricing power in the execution of multiply-listed equity and ETF options order flow. More specifically, in May 2026, the Exchange had 10.37% market share of executed volume of multiply-listed equity and ETF options trades.
                    <SU>18</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         The OCC publishes options and futures volume in a variety of formats, including daily and monthly volume by exchange, available here: 
                        <E T="03">https://www.theocc.com/Market-Data/Market-Data-Reports/Volume-and-Open-Interest/Monthly-Weekly-Volume-Statistics.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         Based on a compilation of OCC data for monthly volume of equity-based options and monthly volume of equity-based ETF options, 
                        <E T="03">see id.,</E>
                         the Exchange's market share in equity-based options increased from 6.14% for the month of May 2025 to 10.37% for the month of May 2026.
                    </P>
                </FTNT>
                <P>The Exchange believes that the proposed rule change reflects this competitive environment because it modifies the Exchange's fees in a manner designed to continue to incent participants on the Trading Floor to direct trading interest to the Exchange, to provide liquidity and to attract additional order flow. To the extent that Floor Brokers are encouraged to utilize the Exchange as a primary trading venue for all transactions, all Exchange market participants stand to benefit from the improved market quality and increased opportunities for price improvement. The Exchange notes that it operates in a highly competitive market in which market participants can readily favor competing venues. In such an environment, the Exchange must continually review, and consider adjusting, its fees and credits to remain competitive with other exchanges. For the reasons described above, the Exchange believes that the proposed rule change reflects this competitive environment.</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>No written comments were solicited or received with respect to the proposed rule change.</P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
                <P>
                    The foregoing rule change is effective upon filing pursuant to Section 19(b)(3)(A) 
                    <SU>19</SU>
                    <FTREF/>
                     of the Act and subparagraph (f)(2) of Rule 19b-4 
                    <SU>20</SU>
                    <FTREF/>
                     thereunder, because it establishes a due, fee, or other charge imposed by the Exchange.
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         15 U.S.C. 78s(b)(3)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         17 CFR 240.19b-4(f)(2).
                    </P>
                </FTNT>
                <P>
                    At any time within 60 days of the filing of such proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act. If the Commission takes such action, the Commission shall institute proceedings under Section 19(b)(2)(B) 
                    <SU>21</SU>
                    <FTREF/>
                     of the Act to determine whether the proposed rule change should be approved or disapproved.
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         15 U.S.C. 78s(b)(2)(B).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
                <P>Interested persons are invited to submit written data, views and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:</P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's internet comment form (
                    <E T="03">https://www.sec.gov/rules/sro.shtml</E>
                    ); or
                </P>
                <P>
                    • Send an email to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include file number SR-NYSEAMER-2026-56 on the subject line.
                </P>
                <HD SOURCE="HD2">Paper Comments</HD>
                <P>• Send paper comments in triplicate to Secretary, Securities and Exchange Commission, 100 F Street NE, Washington, DC 20549-1090.</P>
                <FP>
                    All submissions should refer to file number SR-NYSEAMER-2026-56. 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-NYSEAMER-2026-56 and should be submitted on or before July 27, 2026.
                </FP>
                <SIG>
                    <PRTPAGE P="41153"/>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>22</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>22</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-13532 Filed 7-2-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-105819; File No. SR-NYSETEX-2026-26]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; NYSE Texas, Inc.; Notice of Filing and Immediate Effectiveness of Proposed Rule Change To Amend Certain Initial and Continued Listing Standards</SUBJECT>
                <DATE>June 30, 2026.</DATE>
                <P>
                    Pursuant to Section 19(b)(1) 
                    <SU>1</SU>
                    <FTREF/>
                     of the Securities Exchange Act of 1934 (“Act”),
                    <SU>2</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>3</SU>
                    <FTREF/>
                     notice is hereby given that on June 23, 2026, the NYSE Texas, Inc. (“NYSE Texas” or the “Exchange”) filed with the Securities and Exchange Commission (“SEC” or “Commission”) the proposed rule change as described in Items I and II, below, which Items have been prepared by the Exchange. The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         15 U.S.C. 78a.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>
                <P>
                    The Exchange proposes to amend certain of its initial and continued listing standards contained in Article 22 of the NYSE Texas Rule Book (the “Rule Book'). The proposed rule change is available on the Exchange's website at 
                    <E T="03">www.nyse.com</E>
                     and at the principal office of the Exchange.
                </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <P>In its filing with the Commission, the self-regulatory organization included statements concerning the purpose of, and basis for, the proposed rule change and discussed any comments it received on the proposed rule change. The text of those statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in sections A, B, and C below, of the most significant parts of such statements.</P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and the Statutory Basis for, the Proposed Rule Change</HD>
                <HD SOURCE="HD3">1. Purpose</HD>
                <P>In 2018, a wholly-owned subsidiary of NYSE Group, Inc. merged with CHX Holdings, Inc., the parent of the Chicago Stock Exchange, Inc. (the “Predecessor Exchange”). Upon closing of the merger, the Predecessor Exchange was re-named NYSE Chicago, Inc. (“NYSE Chicago”). In 2025, NYSE Chicago reincorporated in the State of Texas and was re-named NYSE Texas, Inc. In order to facilitate new listings on NYSE Texas, the Exchange proposes to amend certain of its initial and continued listing standards to align them with the standards of other national securities exchanges on which issuers most often seek a primary listing.</P>
                <P>This Exchange's listing rules for common stock, preferred stock, stock warrants, contingent value rights (“CVRs”), and other securities are set forth in Article 22 of the Rule Book. In addition to proposing amendments to certain of the quantitative initial and continued listing standards, the Exchange also proposes certain other changes. The proposed changes are set forth below:</P>
                <HD SOURCE="HD3">Rule 1. General Provisions Regarding Listing</HD>
                <P>Under Rule 1(b)(4), the Exchange proposes to delete the definition of “net tangible assets” from the Rule Book. Current Exchange initial and continued listing rules require issuers to demonstrate compliance with a minimum net tangible asset metric. The Exchange notes that net tangible assets is not a line item typically reported on an issuer's financial statements, and it does not believe that net tangible assets is a metric used to demonstrate financial qualification for listing on any other national securities exchange. Instead, as discussed below, the Exchange proposes to adopt a stockholders' equity requirement for many of its initial and continued listing standards. The Exchange believes that stockholders' equity is comparable to net tangible assets, with the benefit that it is reported on an issuer's balance sheet and is more readily accessible to investors. Because the Exchange proposes to no longer require issuers to demonstrate a minimum level of net tangible assets, it proposes to delete this term from the list of definitions.</P>
                <P>
                    Under Rule 1(b)(5), the Exchange proposes to amend the definition of “publicly held shares” to exclude concentrated holdings of 10% or more. Currently, the Exchange's definition of “publicly held shares” excludes concentrated holdings of 5% or more. The Exchange notes that under the comparable definitions of publicly held shares on other national securities exchanges all establish the threshold for concentrated holdings at 10% or above.
                    <SU>4</SU>
                    <FTREF/>
                     To conform its definition of “publicly held shares” to the comparable definition in effect at other major listing exchanges, the Exchange proposes to amend the applicable threshold of concentrated holdings from 5% to 10%. The Exchange proposes to add clarifying language to the definition of “publicly held shares” that determinations of beneficial ownership for purposes of calculating publicly held shares will be made in accordance with Rule 13c-3 under the Act. The proposed clarifying language is consistent with the approach taken by other listing exchanges.
                    <SU>5</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See,</E>
                         for example, Section 102.01A(B) of the NYSE Listed Company Manual, Section 102 of the NYSE American Company Guide, and Nasdaq Rule 5005(a)(35).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See,</E>
                         for example, Nasdaq Stock Market Rule 5005(a)(35) and Section 101 of the NYSE American Company Guide.
                    </P>
                </FTNT>
                <P>Under Rule 1(b)(10), the Exchange proposes to change references to “Amex” and “American Stock Exchange” to “NYSE American” and “NYSE American LLC,” respectively, to reflect the current name of the NYSE American exchange.</P>
                <P>
                    The Exchange proposes to add new Rules 1(b)(13)—(15) to add definitions of “restricted securities,” “unrestricted securities,” and “unrestricted publicly held shares.” As discussed below, the Exchange is proposing to amend certain of its initial listing standards to conform to comparable standards in place on NYSE American which recently amended its initial listing standards to incorporate minimum requirements for unrestricted publicly held shares.
                    <SU>6</SU>
                    <FTREF/>
                     The definitions contained in proposed Rules 1(b)(13)—(15) are identical to the definitions contained in Section 101 of the NYSE American Company Guide.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 105105 (March 27, 2026), 91 FR 16262 (April 1, 2026).
                    </P>
                </FTNT>
                <P>
                    The Exchange proposes to delete Rule 1(c). Currently, the Exchange has a two-tier listing structure whereby issuers that meet one set of listing standards are designated as a Tier I issuer and other issuers that meet reduced listing standards are designated as a Tier II issuer. As discussed below, the Exchange proposes to adopt a single listing tier, with multiple initial listing standards, comparable to the initial listing standards of NYSE American and Nasdaq Capital Market. Therefore, the 
                    <PRTPAGE P="41154"/>
                    Exchange proposes to delete references to a “two-tier” listing structure and “Tier II” listing throughout Article 22 of the Rule Book. To reflect the proposed move to a single listing tier with multiple listing standards, the Exchange proposes to amend the language throughout Rule 1(d) and 1(e). As the Exchange proposes to adopt four alternative initial listing standards in Rule 8, a company can qualify for listing by meeting all of the applicable requirements of any one of the proposed standards.
                </P>
                <P>
                    Under Rule 1(f), the Exchange proposes to change outdated references to the National Association of Securities Dealers and related NASD rules to a more generic reference to a national securities association. The Exchange notes that the National Association of Securities Dealers no longer exists and its proposed revision conforms the language of Rule 1(f) to comparable language in the rules of other national securities exchanges.
                    <SU>7</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See,</E>
                         for example, Section 105.00 of the NYSE Listed Company Manual.
                    </P>
                </FTNT>
                <P>Under Rules 1(g)(1), 1(h)(1) and 1(h)(2) the Exchange proposed to delete references to dates that have passed and are no longer relevant.</P>
                <P>The Exchange proposes to update rule numbering and internal rule cross references throughout Rule 1 to reflect the amendments described herein.</P>
                <P>
                    Exchange Act Rule 3a51-1(a)(2) 
                    <SU>8</SU>
                    <FTREF/>
                     (the “Penny Stock Rule”) requires an Exchange to maintain quantitative listing standards that are substantially similar to or stricter than those listing standards that were in place on that exchange on January 8, 2004 or meet or exceed quantitative metrics described below. The Exchange's initial listing standards after adoption of the proposed amendments will exceed those established by the Penny Stock Rule. The Penny Stock Rule requires that initial listing standards require an issuer to have stockholders' equity of at least $5,000,000, market value of listed securities of $50,000,000, or income of $750,000 in the most recently completed fiscal year or in two of the three most recently completed fiscal years. Initial Listing Standard 1 requires income of $750,000 in an issuer's last fiscal year or two of the last three fiscal years. Initial Listing Standard 2 requires $5,000,000 in stockholders' equity. Initial Listing Standard 3 requires a market value of listed securities of at least $50,000,000. Initial Listing Standard 4 requires a market value of listed securities of at least $75,000,000.
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         17 CFR 240.3a51-1(a)(ii).
                    </P>
                </FTNT>
                <P>Under the Penny Stock Rule, initial listing standards must require that an issuer have an operating history of at least one year or a market value of listed securities of $50,000,000. Initial Listings Standards 1 and 2 both require at least one full fiscal year of operation and Initial Listing Standards 3 and 4 require at least $50,000,000 in market value of listed securities.</P>
                <P>Under the Penny Stock Rule, initial listing standards must require that issues of common or preferred stock have a minimum bid price of $4. Under the proposed initial listing standards, all issues of common stock must have a minimum bid price of $4 and issues of preferred stock must have a minimum bid price of $10.</P>
                <P>Under the Penny Stock Rule, initial listing standards shall require at least 300 round lot holders. The proposed listing standards satisfy this element of the Penny Stock Rule by requiring a minimum of 400 public holders. While the proposed shareholder requirement does not include a round lot component, the Exchange notes that requiring 400 public holders on an absolute basis is meaningfully higher than 300 round lot holders.</P>
                <P>Under the Penny Stock Rule, initial listing standards shall require 1,000,000 publicly held shares with a market value of at least $5,000,000. Each of the proposed initial listing standards requires an aggregate market value of publicly held shares of at least $15,000,000. Each initial listing standard also requires 1,000,000 publicly held shares.</P>
                <P>For the aforementioned reasons, the Exchange believes the proposed listing standards comply with the Penny Stock Rule.</P>
                <HD SOURCE="HD3">Rule 2. Admittance to Listing</HD>
                <P>
                    Under Interpretation and Policy .01(c), the Exchange proposes to remove the requirement that an applicant's (i) charter be certified by the Secretary of State of the applicant's state of incorporation, and (ii) by-laws be certified by the Secretary or Assistant Secretary of the applicant. The Exchange still plans to review an applicant's charter and by-laws as part of its initial listing qualification process, but does not believe it is necessary to require certified copies of such documents. The Exchange notes that issuers are also required to file with the Securities and Exchange Commission (the “Commission”) copies of their charter and by-laws as an exhibit to their registration statement.
                    <SU>9</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See</E>
                         Item 601 of Regulation S-K.
                    </P>
                </FTNT>
                <P>
                    The Exchange proposes to delete Interpretation and Policy .01(g) and .01(h). The Exchange expects most issuers to list in connection with an initial public offering and, therefore, would not have a certified schedule of distribution. Instead, the Exchange will obtain a representation letter from the issuer's underwriter to confirm that the securities to be listed will meet applicable distribution standards. The Exchange believes that a specimen stock certificate is not required to confirm that an issuer is qualified to list its securities on the Exchange and therefore proposes to remove this required submission. As amended, the proposed list of application materials is generally consistent with the materials required for listing on other exchanges.
                    <SU>10</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See,</E>
                         for example, Section 104.01 of the NYSE Listed Company Manual and Section 211 of the NYSE American Company Guide.
                    </P>
                </FTNT>
                <P>The Exchange's initial and annual listing fees will be filed in a separate fee schedule and made available on the Exchange's website. Therefore, the Exchange proposes to delete the paragraph entitled “Listing Fee” under Interpretation and Policy .01.</P>
                <P>Under Interpretation and Policy .02(c), the Exchange proposes to maintain the requirement that, when seeking a supplemental listing of additional shares, an issuer must submit an opinion of counsel as to legality of issuance and validity of the securities to be listed, including a statement of status under the Securities Act of 1933. However, the Exchange proposes to delete the requirement that if the opinion letter is furnished to another exchange, its submission to the Exchange must be accompanied by a manually signed letter of reliance. Even if not addressed specifically to NYSE Texas, the Exchange believes that a signed opinion of counsel opining on the legality of issuance and validity of securities is sufficient for Exchange purposes to determine that a security is qualified for listing.</P>
                <P>The Exchange proposes to delete Interpretation and Policy .02(g) as its supplemental listing fees will be filed in a separate fee schedule and made available on the Exchange's website.</P>
                <P>
                    Under Interpretation and Policy .03, the Exchange proposes to update reference to the NYSE American and Nasdaq Stock Market. The Exchange also proposes to delete references to “ECM” securities which refer to the Amex Emerging Company Marketplace which no longer exists. For the reasons stated above, the Exchange proposes to delete the requirement that an issuer submit a specimen stock certificate 
                    <PRTPAGE P="41155"/>
                    when it is applying to list on the Exchange concurrent with (or within twelve months of) seeking to list on the NYSE, NYSE American or Nasdaq Stock Market. The Exchange proposes to update section provisions to reflect the deletion.
                </P>
                <HD SOURCE="HD3">Rule 4. Removal of Securities</HD>
                <P>
                    Under Rule 4(c), the Exchange proposed to update references to NYSE Regulation which is the department of the Exchange that enforces Exchange rules and determines whether to issue a delisting notice. The Exchange also proposes to add electronic mail to the list of methods by which a delisting notice can be delivered to an issuer. The Exchange notes that most issuers prefer to communicate by electronic mail.
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         The rules of the New York Stock Exchange, NYSE American and Nasdaq Stock Market do not prescribe the manner in which the relevant exchange deliver written notice to an issuer of a potential delisting action. In contrast, Exchange rules set forth a variety of different means by which the Exchange can notify an issuer of a potential delisting action. Given that Exchange rules are more prescriptive in this regard than its peer exchanges, the Exchange believes it is reasonable to add electronic mail to the list of approved means of communication as it believes that is the preferred and most efficient method of communication for most listed companies.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Rule 8. Tier I Listing Requirements for Common Stock</HD>
                <P>Because the Exchange proposes to transition to a single listing tier, as described above, it proposes to delete the reference to “Tier I Listing Requirements” from the heading and title of Rule 8.</P>
                <P>Currently, the Exchange has a “basic” and “alternative” initial listing standard for its Tier I platform. The Exchange proposes to replace the basic and alternative listing standards with four initial listing standards to mirror the standards in place on the NYSE American exchange. The Exchange proposes to amend the language in the preamble of Rule 8(a) to specify that an issuer seeking to list common stock on the Exchange must meet one of the enumerated initial listing standards.</P>
                <P>
                    The quantitative requirements under proposed Initial Listing Standards 1-4 under Rule 8(a) would be substantially identical to Initial Listing Standards 1-4 under Section 101 and 102 of the NYSE American Company Guide. The only substantive difference between the proposed quantitative initial listing rules and existing Initial Listing Standards 1-4 on NYSE American is that the NYSE American rules include an alternative public distribution standard that allows an issuer to list if it has 800 public shareholders and between 500,000 and 1,000,000 publicly held shares. To satisfy the requirements of the Penny Stock Rule, the Exchange is proposing to require a minimum of 1,000,000 publicly held shares in all instances so it is not proposing to adopt this alternative. In addition, the Exchange is proposing to adopt a $4 minimum stock price and an aggregate market value of unrestricted publicly held shares of $15,000,000 (for Initial Listing Standards 1-3) and $20,000,000 (for Initial Listing Standard 4) to conform to the comparable NYSE American standards.
                    <SU>12</SU>
                    <FTREF/>
                     As discussed above, the Exchange is proposing to amend the list of required application materials to specify that when listing in connection with an initial public offering, a company's underwriter provide a letter representing that the company will meet applicable distribution standards, including with respect to shareholders and publicly held shares.
                    <SU>13</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">See, supra,</E>
                         Footnote 6.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         The Exchange's approach in this regard is consistent with how initial public offerings are evaluated for compliance with applicable listing standards on the New York Stock Exchange and NYSE American.
                    </P>
                </FTNT>
                <P>
                    The Exchange proposes to amend Rule 8(e) to delete the requirement that any initial public offering for equity securities must be underwritten on a firm commitment basis. While most initial public offerings are conducted in this manner, the Exchange notes that some issuers may elect to list on the Exchange pursuant an offering conducted under Regulation A. Accordingly, the Exchange proposes to delete this limiting requirement.
                    <SU>14</SU>
                    <FTREF/>
                     The Exchange proposes to further amend Rule 8(e) to clarify that every initial public offering of an equity issue must meet one of the proposed Initial Listing Standards and that there are no exceptions with respect to qualification for listing. Similarly, the Exchange proposes to delete Rule 8(e)(3) which permits issuers that do not meet applicable standards at the time of listing to qualify for listing based on meeting standards for a majority of the trading days for the period of 30 days immediately following the date the offering has been completed. The Exchange does not believe it is appropriate to permit an issuer to meet initial listing standards after it has already listed so it proposes to remove this exemption. Consistent with the rules of NYSE American, because the proposed listing rules will require that any company listing in connection with an initial public offering or other underwritten public offering must have a market value of unrestricted publicly held shares of at least $15,000,000 and that such requirement must be satisfied from the offering proceeds, the Exchange proposes to delete conflicting language from new Rule 8(e) stating that the initial listing standards are calculated without giving effect to proceeds of the initial public offering.
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         The Exchange notes that NYSE American does not have a similar requirement so the Exchange's proposed amendment in this regard conforms the Exchange's rules to that of NYSE American.
                    </P>
                </FTNT>
                <P>The Exchange proposes to conform numbering and rule references throughout Rule 8 to reflect the aforementioned changes.</P>
                <HD SOURCE="HD3">Rule 9. Tier I Listing Requirements for Preferred Stock</HD>
                <P>Similar to its proposed amendments for initial listing rules applicable to common stocks, the Exchange proposes to adopt a single tier for the listing of preferred stock. Accordingly, the Exchange proposes to remove references to Tier I from the heading and preamble to Rule 9.</P>
                <P>
                    The Exchange proposes to conform the initial listing requirements for preferred stock to the comparable initial listing requirements on NYSE American for preferred stock.
                    <SU>15</SU>
                    <FTREF/>
                     As amended, the Exchange's proposed quantitative initial listing requirements for preferred stock will be substantively identical to the initial listing standards on NYSE American. Like NYSE American's listing standards for preferred stock, the Exchange will require that an issuer of preferred stock (i) meet the size and earnings requirements applicable to issuers of common stock, and (ii) appear to be in financial position to service applicable dividend requirements for the class of preferred stock. With respect to distribution requirements, the Exchange—like NYSE American—will have alternate standards depending on whether an issuer of preferred stock has a class of common stock listed on the Exchange or another national securities exchange. The numerical standards included in those alternate requirements are comparable to those required on NYSE American.
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">See</E>
                         Sections 103 and 124 of the NYSE American Company Guide.
                    </P>
                </FTNT>
                <P>
                    The Exchange proposes to amend Rule 9(d) to specify the circumstances under which an issue of convertible preferred stock may contain a provision permitting its issuer to reduce the conversion price. As amended, Rule 9(d) will conform to the requirements of Section 103(d) of the NYSE American Company Guide. The Exchange proposes to adopt Rule 9(g) to set forth the required voting rights for issues of preferred stock listed on the Exchange. 
                    <PRTPAGE P="41156"/>
                    As adopted, the voting rights for preferred stock will be identical to the voting rights for issues of preferred stock on NYSE American.
                    <SU>16</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         
                        <E T="03">See</E>
                         Sections 103(c) and 124 of the NYSE American Company Guide.
                    </P>
                </FTNT>
                <P>The Exchange proposes other non-substantive changes to Rule 9 to remove references to Tier I and update references to the NYSE American exchange.</P>
                <HD SOURCE="HD3">Rule 10. Tier I Listing Requirements for Bonds and Debentures</HD>
                <P>The Exchange proposes to adopt a single tier for the listing of bonds and debentures. Accordingly, the Exchange proposes to remove references to Tier I from the heading and preamble to Rule 10 as well as within the provisions of Rule 10.</P>
                <P>
                    The Exchange proposes to amend Rule 10(a) to set forth the conditions that must be present for a debt security to qualify for listing. The conditions contained in proposed Rule 10(a)(1)-(5) are identical to the conditions contained in Section 104 of the NYSE American Company Guide. Exchange Rule 10(b) sets forth the same $5 million minimum market value requirement as is contained in the comparable NYSE American listing rule.
                    <SU>17</SU>
                    <FTREF/>
                     In Rule 10(b), the Exchange proposes to remove the requirement that a bond issue have at least 100 public beneficial holders. In this regard, the Exchange notes that it is conforming its bond listing requirements to the standards of the NYSE, NYSE American and Nasdaq Stock Market which do not have a minimum holder requirement.
                    <SU>18</SU>
                    <FTREF/>
                     The Exchange proposes to delete Rule 10(c) and 10(d) to eliminate separate listing requirements for (i) bonds issued by companies without common stock listed on the Exchange, New York Stock Exchange or NYSE American and (ii) municipal securities. In this regard, the Exchange notes that NYSE American does not have separate listing standards for these two categories of bond issuers and, as amended, the Exchange's rules will conform to NYSE American's comparable rules for bond listings. Lastly, with respect to convertible bonds, the Exchange proposes to amend Rule 10(e) to conform the circumstances under which an issuer may reduce the conversion price of such bond to the comparable requirements contained in the NYSE American rules.
                    <SU>19</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         
                        <E T="03">See</E>
                         Section 104 of the NYSE American Company Guide.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         
                        <E T="03">See,</E>
                         for example, Section 102.03 of the NYSE Listed Company Manual, Section 104 of the NYSE American Company Guide, and Nasdaq Stock Market Rule 5702.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         
                        <E T="03">See</E>
                         “Conversion Provisions” under Section 104 of the NYSE American Company Guide.
                    </P>
                </FTNT>
                <P>The Exchange proposes other non-substantive changes to Rule 10 to update numbering to account for the aforementioned changes.</P>
                <HD SOURCE="HD3">Rule 11. Tier I Listing Requirements for Stock Warrants</HD>
                <P>
                    The Exchange proposes to adopt a single tier for the listing of stock warrants. Accordingly, the Exchange proposes to remove references to Tier I from the heading and preamble to Rule 11 as well as within the provisions of Rule 11(b). The Exchange proposed to amend Rule 11(a) to require a minimum of 200,000 warrants publicly held by not less than 100 public warrantholders In addition, the Exchange proposes to amend Rule 11(b) to specify that it will not list an issue of stock warrants unless the issuer's common stock or security underlying the stock warrants is listed on the NYSE, NYSE American or Nasdaq Stock Market. Both of the aforementioned changes conform Rule 11 with the comparable NYSE American listing rule.
                    <SU>20</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         
                        <E T="03">See</E>
                         Section 105 of the NYSE American Company Guide.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Rule 12. Tier I Listing Requirements for Contingent Value Rights (“CVRs”)</HD>
                <P>The Exchange proposes to adopt a single tier for the listing of CVRs. Accordingly, the Exchange proposes to remove references to Tier I from the heading and preamble to Rule 12. Because the Exchange proposes to adopt new initial listing standards for common stock, the Exchange proposes to amend Rule 12(d) to specify that an issuer of CVRs must meet one of the initial listing standards applicable to common stock issuers. The Exchange notes that the proposed change mirrors the substance of the existing rule.</P>
                <HD SOURCE="HD3">Rule 13. Tier I Listing Requirements for Other Securities</HD>
                <P>The Exchange proposes to adopt a single tier for the listing of other securities. Accordingly, the Exchange proposes to remove references to Tier I from the heading of Rule 13. Within Rule 13(a), the Exchange proposes to replace references to “net worth” with references to “stockholders' equity.” In this regard, the Exchange notes that net worth and stockholders' equity are functionally the same metric, but that stockholders' equity is the line item most commonly reported on an issuer's balance sheet. Further, the Exchange notes that it is not proposing to change any of the minimum threshold requirements. Because the Exchange proposes to adopt new initial listing standards for common stock, the Exchange proposes to amend Rule 13(a) to specify that an issuer of other securities must meet one of the initial listing standards applicable to common stock issuers</P>
                <HD SOURCE="HD3">Rule 14. Tier I Maintenance Requirements for Common Stock</HD>
                <P>Rule 14 sets forth maintenance requirements for issues of common stock listed on the Exchange. Because the Exchange proposes to adopt a single listing tier, it proposes to delete references to Tier I throughout Rule 14.</P>
                <P>
                    Currently, Rule 14 specifies a minimum level of net tangible assets that must be maintained by any issuer with common stock listed on the Exchange. As discussed above, the Exchange is proposing to adopt initial listing standards that utilize stockholders' equity, rather than net tangible assets, as one of the financial requirements for determining listing qualification. Therefore, the Exchange is proposing to adopt a tiered schedule of stockholders' equity requirements in Rule 14(a)(1) for purposes of maintaining compliance with the Exchange's continued listing standards.
                    <SU>21</SU>
                    <FTREF/>
                     In addition to the two tiers currently in place, the Exchange proposes to adopt a third tier specifying that an issuer must have stockholders' equity of at least $6,000,000 if it has sustained losses from continuing operations and/or net losses in its five most recent fiscal years. In addition to the Exchange's general authority under Rule 17A to delist securities of any corporation whose assets have been depleted to the extent that the company can no longer operate as a going concern, the Exchange proposes to adopt Rule 14(a)(1)(D) specifying that an issuer must not have sustained losses which are so substantial in relation to its overall operations or financial resources as to raise questions about the issuer's ability to continue operations or meet its obligations as they mature.
                    <SU>22</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         
                        <E T="03">See</E>
                         Section 1003(a) of the NYSE American Company Guide for comparable continued listing standards for common stock on NYSE American.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         
                        <E T="03">See</E>
                         Section 1003(a)(iv) of the NYSE American Company Guide.
                    </P>
                </FTNT>
                <P>
                    The Exchange proposes to adopt language that an issuer will not be required to maintain the above-mentioned criteria if it has either (i) total market capitalization of at least $50,000,000; or total assets and revenue of $50,000,000 each in its last fiscal year, or in two of its last three fiscal years, and (ii) the issuer has at least 1,100,000 shares publicly held, a market 
                    <PRTPAGE P="41157"/>
                    value of publicly held shares of at least $15,000,000 and 400 round lot shareholders. This proposed exemption is comparable to the exemption contained in Section 1003 of the NYSE American Company Guide with respect to continued listing compliance.
                </P>
                <P>
                    The Exchange is proposing to amend Rule 14(a)(2) to require that an issuer of common stock to maintain at least 300 public shareholders to remain in compliance with Exchange listing rules. In combination with the existing requirement that an issue of common stock have at least 200,000 public shares outstanding, the Exchange believes that a standard of 300 public shareholders will provide an appropriate level of ongoing liquidity and notes that NYSE American has an identical continued listing standard for common stock.
                    <SU>23</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         
                        <E T="03">See</E>
                         Section 1003(b)(i)(B) of the NYSE American Company Guide.
                    </P>
                </FTNT>
                <P>
                    Rule 14(a)(3) currently states that a class of common stock must maintain a market value of publicly-held shares at least $1,000,000. The Exchange proposes to amend this requirement to specify that, in order to remain listed, a class of common stock may not have a market value of publicly-held shares of less than $1,000,000 for more than 90 consecutive days. Adding this time component is consistent with the NYSE American continued listing standards for common stock.
                    <SU>24</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         
                        <E T="03">See</E>
                         Section 1003(b)(i)(C) of the NYSE American Company Guide.
                    </P>
                </FTNT>
                <P>
                    Rule 14(a)(4) currently specifies that issues of common stock that trade at a low price per share for a substantial period of time must effect a reverse stock split within a reasonable period of time after being notified by the Exchange of the deficiency. The Exchange proposes to conform Rule 14(a)(4) to NYSE American's low selling price rule by adding new language detailing the circumstances under which the Exchange will not permit an issuer to conduct a reverse stock split to cure a low selling price. Specifically, if an issuer has effected one or more reverse stock splits over the prior two-year period with a cumulative ratio of 200 shares or more to one, then it will be subject to immediate suspension and delisting with no ability to submit a compliance plan. Additionally, an issuer will not be permitted to effectuate a reverse stock split if doing so would result in the issuer's securities falling below the continue listing standards contained in Rule 14. The proposed limitations on the ability to conduct a reverse stock split are substantively identical to the rules of NYSE American.
                    <SU>25</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         
                        <E T="03">See</E>
                         Section 1003(f)(vi)-(vii) of the NYSE American Company Guide.
                    </P>
                </FTNT>
                <P>The Exchange proposes to amend Rule 14(b) to update references to the New York Stock Exchange, NYSE American and Nasdaq Stock Market. Currently Rule 14(b) states that an issue shall not be required to meet the maintenance requirements contained in Rule 14(a) as long as the issue is also listed and has not been suspended from trading on one of these exchanges. The Exchange proposes to further refine Rule 14(b) to specify that an issue shall not be required to meet the maintenance requirements contained in Rule 14(a) provided the Exchange has made an independent determination that (i) the maintenance requirements for common stock on the other exchange are comparable or more stringent than the requirements set forth in Rule 14(a) and (ii) the issue is in compliance with the applicable maintenance requirements for common stock on the other exchange.</P>
                <P>As proposed, the Exchange's continued listing standards for common stock will be substantially identical to, if not more robust, than the continued listing standards for common stock on NYSE American.</P>
                <HD SOURCE="HD3">Rule 15. Tier I Maintenance Requirements for Preferred Shares</HD>
                <P>Rule 15 sets forth maintenance requirements for issues of preferred stock listed on the Exchange. Because the Exchange proposes to adopt a single listing tier, it proposes to delete references to Tier I throughout Rule 15.</P>
                <P>
                    For the reasons discussed above, the Exchange proposes to amend Rule 15(a)(1) to specify that issuers of preferred stock must be in compliance with the proposed stockholders' equity continued listing standard set forth in Rule 14(a). The Exchange proposes to amend Rule 15(a)(2) to remove the 150 public beneficial holder requirement and increase from 10,000 to 50,000 the publicly held shares requirement. The Exchange proposes to retain a $1,000,000 minimum market value of publicly held shares. In this regard, the Exchange's proposed continued listing requirements will conform with those applicable to preferred stock on NYSE American.
                    <SU>26</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         
                        <E T="03">See</E>
                         Section 1003(b)(iii) of the NYSE American Company Guide.
                    </P>
                </FTNT>
                <P>Because the Exchange is proposing to adopt maintenance standards consistent with those on NYSE American that permit an issuer with losses from continuing operations and/or net losses in its five most recent fiscal years provided it has at least $6,000,000 in stockholders' equity as described in Rule 14(a), the Exchange proposes to delete Rule 15(a)(4) (which states that an issuer of preferred shares must not have sustained losses from continuing operations and/or net losses in its five most recent fiscal years) and renumber Rule 15 accordingly. The Exchange's approach in this regard is consisted with that of NYSE American.</P>
                <P>The Exchange proposes to amend Rule 15(b) to update references to the New York Stock Exchange, NYSE American and Nasdaq Stock Market. Currently Rule 15(b) states that an issue shall not be required to meet the maintenance requirements contained in Rule 15(a) as long as the issue is also listed and has not been suspended from trading on one of these exchanges. The Exchange proposes to further refine Rule 15(b) to specify that an issue shall not be required to meet the maintenance requirements contained in Rule 15(a) provided the Exchange has made an independent determination that (i) the maintenance requirements for preferred stock on the other exchange are comparable or more stringent than the requirements set forth in Rule 15(a) and (ii) the issue is in compliance with the applicable maintenance requirements for preferred stock on the other exchange.</P>
                <P>
                    As proposed, the Exchange's continued listing standards for preferred stock will be substantially identical to, if not more robust, than the continued listing standards for preferred stock on NYSE American.
                    <SU>27</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         
                        <E T="03">See</E>
                         Section 1003(b)(iii) of the NYSE American Company Guide. For example, the Exchange will require 100,000 publicly held shares, whereas NYSE American requires 50,000 publicly held shares. Further, the Exchange will require at least 150 public beneficial shareholders whereas NYSE American has no comparable requirement.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Rule 16. Tier I Maintenance Requirements for Bonds and Debentures</HD>
                <P>Rule 16 sets forth maintenance requirements for bonds and debentures listed on the Exchange. Because the Exchange proposes to adopt a single listing tier, it proposes to delete references to Tier I throughout Rule 16.</P>
                <P>
                    For the reasons discussed above, the Exchange proposes to amend Rule 16(a)(1) to specify that issuers of bonds and debentures must be in compliance with the proposed stockholders' equity continued listing standard set forth in Rule 14(a). Because the Exchange is proposing to adopt maintenance standards consistent with those on NYSE American that permit an issuer with losses from continuing operations 
                    <PRTPAGE P="41158"/>
                    and/or net losses in its five most recent fiscal years provided it has at least $6,000,000 in stockholders' equity as described in Rule 14(a), the Exchange proposes to delete Rule 16(a)(4) (which states that an issuer of preferred shares must not have sustained losses from continuing operations and/or net losses in its five most recent fiscal years) and renumber Rule 16 accordingly.
                </P>
                <P>
                    The Exchange proposes to replace the public beneficial shareholder requirement in Rule 16(a)(2) with a requirement that an issuer must be able to meet its obligation on a listed debt security. Further, the Exchange proposes to amend the market value of shares publicly held requirement in Rule 16(a)(3) to $400,000. Both of these proposed changes conform the continued listing standards for bonds and debentures to the comparable standards on NYSE American.
                    <SU>28</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         See Section 1003(b)(iv) of the NYSE American Guide.
                    </P>
                </FTNT>
                <P>The Exchange proposes to delete Rule 16(a)(5) to eliminate the investment grade rating requirement of bonds and debentures of non-listed issuers as NYSE American does not have this requirement.</P>
                <P>The Exchange proposes to amend Rule 16(b) to update references to the New York Stock Exchange, NYSE American and Nasdaq Stock Market. Currently Rule 16(b) states that an issue shall not be required to meet the maintenance requirements contained in Rule 16(a) as long as the issue is also listed and has not been suspended from trading on one of these exchanges. The Exchange proposes to further refine Rule 16(b) to specify that an issue shall not be required to meet the maintenance requirements contained in Rule 16(a) provided the Exchange has made an independent determination that (i) the maintenance requirements for bonds and debentures on the other exchange are comparable or more stringent than the requirements set forth in Rule 16(a) and (ii) the issue is in compliance with the applicable maintenance requirements for bonds and debentures on the other exchange.</P>
                <HD SOURCE="HD3">Rule 17. Tier I Maintenance Requirements for Stock Warrants and Contingent Value Rights</HD>
                <P>Rule 17 sets forth maintenance requirements for stock warrants and contingent value rights. Because the Exchange proposes to adopt a single listing tier, it proposes to delete references to Tier I throughout Rule 17.</P>
                <P>The Exchange proposes to amend Rule 17(c) to update references to the New York Stock Exchange, NYSE American and Nasdaq Stock Market. Currently Rule 17(c) states that an issue shall not be required to meet the maintenance requirements contained in Rule 17(a) as long as the issue is also listed and has not been suspended from trading on one of these exchanges. The Exchange proposes to further refine Rule 17(c) to specify that an issue shall not be required to meet the maintenance requirements contained in Rule 17(a) provided the Exchange has made an independent determination that (i) the maintenance requirements for stock warrants and contingent value rights on the other exchange are comparable or more stringent than the requirements set forth in Rule 17(a) and (ii) the issue is in compliance with the applicable maintenance requirements for stock warrants and contingent value rights on the other exchange.</P>
                <HD SOURCE="HD3">Rule 17A. Maintenance Standards Applicable to All Tier I Issues</HD>
                <P>Rule 17A sets forth maintenance standards applicable to all issues listed on the Exchange. Because the Exchange proposes to adopt a single listing tier, it proposes to delete references to Tier I throughout Rule 17A. The Exchange also proposes to amend Rule 17A to update references to the New York Stock Exchange, NYSE American and Nasdaq Stock Market.</P>
                <P>
                    The Exchange proposes to adopt new Rule 17A(b) to detail the requirements around filing of periodic reports with the Securities and Exchange Commission and the process and timelines to regain compliance in the event that an issuer has a filing delinquency. In connection with adopting new Rule 17A(b), the Exchange will include the existing text of Rule 17A in a new Rule 17A(a). As proposed, Rule 17A(b) is substantively identical to the comparable rules on NYSE American.
                    <SU>29</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         
                        <E T="03">See</E>
                         Section 1007 of the NYSE American Company Guide.
                    </P>
                </FTNT>
                <P>The Exchange proposes to amend Interpretations and Policies paragraph .01 to specify that, when an issuer is operating under the terms of a plan to regain compliance with applicable Exchange rules, the Exchange can elect to truncate such plan and consider the issuer to have regained compliance if it has demonstrated that it has regained compliance for two consecutive quarters before the maximum plan period has expired. Current Rule 17A specifies that a plan can be so truncated if the issuer regains compliance before the plan has expired. By specifying that such compliance must be sustained for two consecutive quarters, the Exchange believes that it is making the requirements more stringent.</P>
                <HD SOURCE="HD3">Rule 18. Tier II Listing Requirements</HD>
                <P>Existing Rule 18 sets forth listing requirements for the listing of common stock, preferred stock, bonds and debentures and warrants on the Exchange's Tier II listing platform. Existing Rule 18 also authorizes the Exchange to list on Tier II a security that is already listed (or has been approved for listing) on the New York Stock Exchange, NYSE American or Nasdaq Stock Market.</P>
                <P>
                    As described above, the Exchange proposes to adopt a single listing tier so it proposes to delete the separate Tier II listing standards contained in Rule 18. The Exchange believes that issuers with a primary listing on the New York Stock Exchange, NYSE American or Nasdaq Stock Market may continue to seek a dual listing for their securities on the Exchange. Therefore, the Exchange proposes to amend the title of Rule 18 to Dual Listings and provide that if a security is already listed on the New York Stock Exchange, NYSE American or Nasdaq Stock Market, the security can be listed on the Exchange as a dual listing in reliance upon the listing requirements of the applicable other Exchange provided the Exchange has made an independent determination that the primary listing exchange's listing requirements for the class of securities to be dually listed are comparable or more stringent than the corresponding listing requirements of the Exchange. In this regard, the Exchange notes that the listing requirements for common stock, preferred stock, bonds and debentures, and warrants on these other exchanges are substantially similar to the proposed requirements on the Exchange.
                    <SU>30</SU>
                    <FTREF/>
                     As discussed herein, the Exchange's proposed listing standards for these categories of securities are substantively identical to those of NYSE American. The listing standards of the Nasdaq Capital Market, the lower tier of the Nasdaq Stock Market, are essentially identical to those of NYSE American and the Exchange's proposed listing standards. The NYSE and the Nasdaq Global and Global Select Markets have quantitative listing standards that are generally higher than those proposed by 
                    <PRTPAGE P="41159"/>
                    the Exchange. Because a security that is listed on the NYSE, NYSE American or Nasdaq Stock Market will be subject to listing standards that are substantively the same or more stringent, solely for purposes of a dual listing and consistent with the current rule, the Exchange believes it is reasonable to rely on the listing requirements of the applicable other exchange. Nonetheless, the Exchange proposes to add additional language to Rule 18 that the Exchange will make an independent determination that a security seeking a dual listing satisfies applicable listing requirements and shall require the issuer of any such security to enter into a listing agreement with the Exchange.
                    <SU>31</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         
                        <E T="03">See,</E>
                         Sections 102.01 (Common Stock), 102.03 (Debt Listings), 703.05 (Preferred Stock) and 703.12 (Warrants) of the NYSE Listed Company Manual; Sections 101 and 102 (Common Stock) 103 and 124 (Preferred Stock), 104 (Bonds and Debentures), and 105 (Warrants) of the NYSE American Company Guide; and Rules 5505 (Common Stock), 5510 (Preferred Stock), 5515 (Warrants) of the Nasdaq Stock Market.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         The Exchange believes its proposed approach with respect to dual listings is consistent with other dual listing venues. See, for example, Nasdaq Texas IM-5220 and Texas Stock Exchange Rule 16.205
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Rule 19. Corporate Governance</HD>
                <P>Because the Exchange proposes to adopt a single listing tier, it proposes to delete references to Tier I in the preamble to Rule 19. The Exchange proposes to update rule citations through newly numbered Rule 19 to reflect the correct references.</P>
                <P>
                    In Interpretations and Policies .03(b)((3) to Rule 19, the Exchange proposes to specify that open-end funds (including open-end funds that can be listed or traded as investment company units) are not required to comply with the annual meeting requirement of Rule 19(j). The Exchange notes that such category of open-end funds are exempt from exchange annual meeting requirements on the New York Stock Exchange and NYSE American.
                    <SU>32</SU>
                    <FTREF/>
                     Open-end funds, also known as exchange-traded funds (“ETFs”), receive regular disclosure documents describing the pricing mechanism for their securities and detailing how they can value their holdings. Moreover, the net asset value of an ETF is determined by the market price of each fund's underlying securities or other reference asset. Because shareholders can value their investments on an ongoing basis, the Exchange believes that there is less need for shareholders to engage management at an annual meeting. In addition, while holders of such securities may have the right to vote in certain limited circumstances, they do not have the right to vote on the annual election of a board of directors, further reducing the need for an annual meeting. Further, although the Exchange proposes to exclude issuers of such securities from holding an annual meeting consistent with the rules of other ETF listing venues, such issuers may still be required to hold special meetings as required by state law or their governing documents. The Exchange lists the categories of open-end funds discussed above pursuant to Exchange Rule 5 (Exchange Traded Products Listing Requirements) and Exchange Rule 8 (Trading of Certain Equity Derivatives). Accordingly, the Exchange proposes to amend Interpretations and Policies .03(b)((3) to Rule 19 to specify that open-end fund listed pursuant to Rule 5 and 8 are not required to comply with the annual meeting requirement of Rule 19(j).
                </P>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         
                        <E T="03">See</E>
                         Section 302.00 of the NYSE Listed Company Manual and Commentary .01 to Section 704 of the NYSE American Company Guide.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Rule 20. Tier I Voting Rights</HD>
                <P>Because the Exchange proposes to adopt a single listing tier, it proposes to delete references to Tier I in the heading and preamble to Rule 20. Rule 20(d) currently sets forth the required voting rights for issues of preferred stock. As discussed above, the Exchange proposes to amend Rule 9 to adopt preferred voting rights requirements consistent with those in effect on NYSE American. Because the voting rights required for issues of preferred stock will now be set forth in Rule 9, the Exchange proposes to delete the existing requirements contained in Rule 20(d).</P>
                <HD SOURCE="HD3">Rule 21. Tier II Corporate Governance, Disclosure, and Miscellaneous Requirements</HD>
                <P>As the Exchange plans to have a single tier for listed securities, it proposes to delete Rule 21 which sets forth corporate governance, disclosure and other requirements for Tier II issuers.</P>
                <HD SOURCE="HD3">Rule 22. Tier II Maintenance Standards</HD>
                <P>As the Exchange plans to have a single tier for listed securities, it proposes to delete Rule 22 which sets maintenance standards for Tier II issuers.</P>
                <HD SOURCE="HD3">Rule 23. Public Disclosure Requirements for Tier I and Tier II Issues</HD>
                <P>Existing Exchange Rule 23 sets forth public disclosure requirements for Tier I and Tier II issuers. The Exchange proposes to renumber Rule 23 to Rule 21 to reflect aforementioned rule deletions. The Exchange will update rule references throughout newly numbered Rule 21.</P>
                <P>
                    The Exchange will also delete reference to Tier I and Tier II throughout newly numbered Rule 21 as the Exchange is proposing to have a single listing tier and the public disclosure requirements will be applicable to all issuers. To reflect the Exchange's reincorporation in the State of Texas, the Exchange proposes to specify that certain times are applicable to the time in Dallas rather than the time in Chicago.
                    <SU>33</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         The Exchange notes that both Dallas and Chicago are located in the Central time zone so the proposed change is simply to avoid any confusion by referencing the time in Chicago for NYSE Texas rules.
                    </P>
                </FTNT>
                <P>The Exchange also proposes to update certain Exchange phone numbers and delete physical addresses for certain news and wire services. The Exchange believes that such physical addresses are outdated and notes that issuers are unlikely to need the physical mailing address of any news or wire services with which they communicate.</P>
                <HD SOURCE="HD3">Rule 24. Additional Requirements for Listed Securities Issued by Intercontinental Exchange, Inc. or Its Affiliates</HD>
                <P>Existing Rule 24 will be renumbered as Rule 22 to reflect aforementioned rule deletions. The Exchange proposes to update internal rule citations to reflect the correct numbering.</P>
                <HD SOURCE="HD3">Rule 25. Erroneously Awarded Compensation</HD>
                <P>
                    Existing Rule 25 will be renumbered as Rule 23 to reflect aforementioned rule deletions.
                    <SU>34</SU>
                    <FTREF/>
                     The Exchange proposes to update internal rule citations to reflect the correct numbering.
                </P>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         The Exchange notes that this rule was previously renumbered from Rule 29 to Rule 25. An internal reference was inadvertently not renumbered resulting in an extraneous reference to Rule 29 that the Exchange proposes to correct.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    The Exchange believes that the proposed rule change is consistent with Section 6(b) of the Act,
                    <SU>35</SU>
                    <FTREF/>
                     in general, and furthers the objectives of Section 6(b)(5) 
                    <SU>36</SU>
                    <FTREF/>
                     of the Act, in particular, because it is designed to prevent fraudulent and manipulative acts and practices, to promote just and equitable principles of trade, to foster cooperation and coordination with persons engaged in facilitating transactions in securities, to remove impediments to, and perfect the mechanism of, a free and open market and a national market system and, in general, to protect investors and the public interest. In addition, the Exchange believes that the proposed changes would promote just and equitable principles of trade, remove impediments to, and perfect the mechanism of, a free and open market and a national market system, and protect investors and the public interest 
                    <PRTPAGE P="41160"/>
                    because the proposed rules are based on rules of the Exchange's affiliated markets, the New York Stock Exchange and NYSE American, that have been approved by the Commission. The Exchange does not believe there is any material difference between the proposed quantitative listing rules and the current NYSE American listing rules. Accordingly, the proposed rule changes promote continuity across affiliated exchanges, permitting categories of securities to list and trade on the Exchange by meeting comparable listing standards as on the Exchange's affiliated markets. With respect to dual listings, the Exchange notes that its rules for the initial qualification and continued listing of dually-listed companies have been in effect for many years and the Exchange has continuously maintained an active roster of dually-listed companies for several decades. In addition, the Exchange notes that, with respect to companies that have a dual listing on the Exchange, it will make an independent determination that the initial and continued listing rules of the primary exchange are comparable or more stringent than those of the Exchange and that the issuer complies with such rules.
                </P>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         15 U.S.C. 78f(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>36</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <P>The Exchange believes that the proposed rule change is consistent with the above principles. The Exchange also believes that by enhancing the rules for the listing and trading of common stock, preferred stock, bonds and debentures, stock warrants and contingent value rights, the proposed rule change would encourage the additional utilization of, and interaction with, the exchange market, and provide issuers with additional choice for venues on which to list their securities.</P>
                <P>The proposal is also designed to promote just and equitable principles of trade by way of initial and continued listing standards which, if not maintained, would result in the discontinuation of trading in the affected products. These requirements, together with the applicable Exchange trading rules (which apply to the proposed products), ensure that no investor would have an unfair advantage over another respecting the trading of the subject products. On the contrary, all investors would have the same access to, and use of, information concerning the specific products and trading in the specific products, all to the benefit of public customers and the marketplace as a whole.</P>
                <P>Furthermore, the proposal is designed to remove impediments to and perfect the mechanism of a free and open market and a national market system by adopting rules that would lead ultimately to the listing and trading of new securities on the Exchange. The proposed changes do nothing more than enhance Exchange rules to align them with comparable rules on other listing exchanges. The Exchange believes that by aligning Exchange rules with the rules of other listing venues, the proposal would offer another option for the listing of securities and thereby promote broader competition among exchanges. The Exchange believes that issuers permitted to list securities on the Exchange should enhance competition within the mechanism of a free and open market and a national market system, and customers and other investors in the national market system should benefit from more depth and liquidity in the market.</P>
                <P>Additionally, the proposal is designed to prevent fraudulent and manipulative acts and practices, as trading would be subject to existing Exchange trading rules, together with specific requirements for registered market makers, books and record production, surveillance procedures, suitability and prospectus requirements, and requisite Exchange approvals, all set forth above. The proposed rule changes accomplish these objectives by enhancing Exchange continued listing standards. The Exchange believes that these proposed rules will enhance the Exchange's listing program, thereby serving to improve the national market system and protect investors and the public interest.</P>
                <P>With respect to the proposed adoption of a single listing tier and related deletion of listing rules applicable to Tier II securities, the Exchange believes that the proposed change is reasonable. The Exchange notes that existing Tier II listing rules are substantially lower than the rules on the New York Stock Exchange, NYSE American and Nasdaq Stock Market. By deleting existing Tier II listing standards and enhancing the initial and continued listing standards of the Exchange to align them with already approved listing standards on other venues, the Exchange believes its proposal helps ensure that the Exchange has a strong rules in place to ensure only qualified securities are listed on the Exchange which, in turn, supports the goals of protecting investors and the public interest. As amended, the Exchange's proposed initial and continued listing standards will be comparable to corresponding rules of the NYSE American and Nasdaq Capital Market tier of the Nasdaq Stock Market. The initial and continued listing standards of the NYSE and Nasdaq Global Select and Nasdaq Global tiers of the Nasdaq Stock Market generally have higher initial and continued listing standards. The Exchange believes it is consistent with the investor protection goals of Section 6(b) of the Act to admit for dual-listing on the Exchange a security that is listed on the NYSE, NYSE American or Nasdaq. In the event that a security with a primary listing on the NYSE, NYSE American or Nasdaq seeks a dual-listing on the Exchange, the Exchange will (i) make an independent determination at the time of listing that the listing standards of the primary exchange are at least as high as the Exchange's proposed standards, and (ii) determine whether such security is compliant with applicable listing standards. The Exchange will further require the issuer of any such security to enter into a listing agreement with the Exchange.</P>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition</HD>
                <P>The Exchange does not believe that the proposed rule change will impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. The proposed change is designed to conform the Exchange's listing rules to the listing rules of other major listing exchanges. With the exception of minor non-substantive and technical changes described above, the proposed rule amendments are identical to the rules in effect on the NYSE American and New York Stock Exchange.</P>
                <P>The proposed rules support competition by allowing for an additional listing venue for common stock, preferred stock, bonds and debentures, warrants and contingent value rights. The proposed rule change would promote competition by allowing the Exchange to compete with other national securities exchanges for the listing and trading of these categories on the basis of substantively comparable listing rules. The proposed rule changes would mitigate the risk that the Exchange could compete for listings on the basis of different or lesser listing standards. With respect to the proposed deletion of obsolete listing rules, the proposed changes would not have any impact on competition, because they are solely designed to eliminate obsolete text.</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>
                    No written comments were solicited or received with respect to the proposed rule change.
                    <PRTPAGE P="41161"/>
                </P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
                <P>
                    Because the foregoing proposed rule change does not: (i) significantly affect the protection of investors or the public interest; (ii) impose any significant burden on competition; and (iii) become operative for 30 days from the date on which it was filed, or such shorter time as the Commission may designate, it has become effective pursuant to Section 19(b)(3)(A) of the Act 
                    <SU>37</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) thereunder.
                    <SU>38</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>37</SU>
                         15 U.S.C. 78s(b)(3)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>38</SU>
                         17 CFR 240.19b-4(f)(6). In addition, Rule 19b-4(f)(6)(iii) requires a self-regulatory organization to give the Commission written notice of its intent to file the proposed rule change, along with a brief description and text of the proposed rule change, at least five business days prior to the date of filing of the proposed rule change, or such shorter time as designated by the Commission. The Exchange has satisfied this requirement.
                    </P>
                </FTNT>
                <P>At any time within 60 days of the filing of the proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act. If the Commission takes such action, the Commission shall institute proceedings to determine whether the proposed rule change should be approved or disapproved.</P>
                <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
                <P>Interested persons are invited to submit written data, views and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:</P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's internet comment form (
                    <E T="03">https://www.sec.gov/rules/sro.shtml</E>
                    ); or
                </P>
                <P>
                    • Send an email to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include file number SR-NYSETEX-2026-26 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-NYSETEX-2026-26. 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-NYSETEX-2026-26 and should be submitted on or before July 27, 2026.
                </FP>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>39</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>39</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-13525 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">SMALL BUSINESS ADMINISTRATION</AGENCY>
                <DEPDOC>[Disaster Declaration #21655 and #21656; NEW YORK Disaster Number NY-20039]</DEPDOC>
                <SUBJECT>Administrative Declaration of a Disaster for the State of New York</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 an Administrative declaration of a disaster for the state of New York dated June 30, 2026.</P>
                    <P>
                        <E T="03">Incident:</E>
                         Severe Storms 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 20, 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 Administrator's disaster declaration, 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:</E>
                     Queens.
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">Contiguous Counties:</E>
                </FP>
                <FP SOURCE="FP1-2">New York: Bronx, Kings, Nassau, New York, Richmond.</FP>
                <P>The Interest Rates are:</P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s30,8">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1"/>
                        <CHED H="1">Percent</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="22">
                            <E T="02">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="02">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="01">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 216556 and for economic injury is 216560.</P>
                <P>The state which received an SBA Administrative declaration is New York.</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-13570 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8026-09-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF STATE</AGENCY>
                <DEPDOC>[Public Notice: 13062]</DEPDOC>
                <SUBJECT>Notice of Determinations; Culturally Significant Object Being Imported for Exhibition—Determinations: “Maverick Kings: Three Visionary Pharaohs of Egypt's Golden Age” Exhibition</SUBJECT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        Notice is hereby given of the following determinations: I hereby determine that a certain object being imported from abroad pursuant to an agreement with its foreign owner or custodian for temporary display in the 
                        <PRTPAGE P="41162"/>
                        exhibition “Maverick Kings: Three Visionary Pharaohs of Egypt's Golden Age” at the Museum of Fine Arts, Boston, in Boston, Massachusetts, and at possible additional exhibitions or venues yet to be determined, is of cultural significance, and, further, that its temporary exhibition or display within the United States as aforementioned is in the national interest. I have ordered that Public Notice of these determinations be published in the 
                        <E T="04">Federal Register</E>
                        .
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Reed Liriano, Program Coordinator, Office of the Legal Adviser, U.S. Department of State (telephone: 202-632-6471; email: 
                        <E T="03">section2459@state.gov</E>
                        ). The mailing address is U.S. Department of State, L/PD, 2200 C Street NW (SA-5), Suite 5H03, Washington, DC 20522-0505.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The foregoing determinations were made pursuant to the authority vested in me by the Act of October 19, 1965 (79 Stat. 985; 22 U.S.C. 2459), Executive Order 12047 of March 27, 1978, the Foreign Affairs Reform and Restructuring Act of 1998 (112 Stat. 2681, 
                    <E T="03">et seq.;</E>
                     22 U.S.C. 6501 note, 
                    <E T="03">et seq.</E>
                    ), Delegation of Authority No. 234 of October 1, 1999, Delegation of Authority No. 236-3 of August 28, 2000, and Delegation of Authority No. 523 of December 22, 2021.
                </P>
                <SIG>
                    <NAME>Sherry C. Keneson-Hall,</NAME>
                    <TITLE>Principal Deputy Assistant Secretary for Educational and Cultural Affairs, Bureau of Educational and Cultural Affairs, Department of State.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13545 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4710-05-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Maritime Administration</SUBAGY>
                <DEPDOC>[Docket No. MARAD-2026-1060]</DEPDOC>
                <SUBJECT>Request Notice: Use of Foreign-Built Small Passenger Vessel in United States Coastwise Trade, S/V LADY SUSAN</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Maritime Administration (MARAD), U.S. Department of Transportation (DOT).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Secretary of Transportation, as represented by MARAD, is authorized to make determinations regarding the coastwise use of foreign built; certain U.S. built; and U.S. and foreign rebuilt vessels that solely carry no more than twelve passengers for hire. MARAD has received such a determination request and is publishing this notice to solicit comments to assist with determining whether the proposed use of the vessel set forth in the request would have an adverse effect on U.S. vessel builders or U.S. coastwise trade businesses that use U.S.-built vessels in those businesses. Information about the requestor's vessel, including a description of the proposed service, is in the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section below.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit comments on or before August 5, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments identified by DOT Docket Number MARAD-2026-1060 by any one of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">https://www.regulations.gov.</E>
                         Search the above DOT Docket Number and follow the instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail or Hand Delivery:</E>
                         Docket Management Facility is in the West Building, Ground Floor of the U.S. Department of Transportation. The Docket Management Facility location address is U.S. Department of Transportation, 1200 New Jersey Avenue SE, West Building, Room W12-140, Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except on Federal holidays.
                    </P>
                    <P>
                        <E T="03">Note:</E>
                         If you mail or hand-deliver your comments, we recommend that you include the DOT Docket Number, your name and a mailing address, an email address or a telephone number in the body of your document so that we can contact you if we have questions regarding your submission.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions received must include the agency name and specific DOT Docket Number. All comments received will be posted without change to the docket at 
                        <E T="03">www.regulations.gov,</E>
                         including any personal information provided. For detailed instructions on submitting comments, or to submit comments that are confidential in nature, see the section entitled Public Participation.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Patricia Hagerty, U.S. Department of Transportation, Maritime Administration, 1200 New Jersey Avenue SE, Mail Stop 2, MAR-620, Washington, DC 20590. Telephone: (202) 366-5400. Email: 
                        <E T="03">smallvessels@dot.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Pursuant to 46 U.S.C. 12121(b), the U.S. Coast Guard may issue a certificate of documentation with a coastwise trade endorsement for eligible, small passenger vessels authorized to carry no more than 12 passengers for hire if MARAD, after notice and an opportunity for public comment, determines the use of the small passenger vessel in the coastwise trade will not adversely affect United States vessel builders or the coastwise trade business of any person that employs vessels built in the United States in that business.
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         The U.S. Coast Guard and MARAD have authority under 46 U.S.C. 12121(b) through the Secretary of the Department of Homeland Security and the Secretary of the Department of Transportation, respectively.
                    </P>
                </FTNT>
                <P>
                    MARAD has received an eligibility determination request. Further details about the requester's vessel and its proposed operations may be found in the determination request posted in the DOT Docket Number listed in the 
                    <E T="02">ADDRESSES</E>
                     section above at 
                    <E T="03">https://www.regulations.gov.</E>
                     Interested parties may comment on the undue adverse effect this action may have on U.S. vessel builders or coastwise trade businesses in the U.S. that employ U.S.-built vessels in those businesses. Comments should refer to the vessel name, state the commenter's interest in the request, and demonstrate, with supporting documentation, the undue adverse effect on U.S. vessel builders and coastwise trade businesses.
                </P>
                <HD SOURCE="HD1">Public Participation</HD>
                <HD SOURCE="HD2">How do I submit comments?</HD>
                <P>
                    Please submit comments, including the attachments, following the instructions provided under the above heading entitled 
                    <E T="02">ADDRESSES</E>
                    . It may take a few hours or even days for comments to be reflected on the docket. Comments must be written in English. Provide concise comments and attach additional documents as necessary. There is no limit on the length of the attachments.
                </P>
                <HD SOURCE="HD2">Where do I go to read public comments, and find supporting information?</HD>
                <P>
                    The docket online is located at 
                    <E T="03">https://www.regulations.gov,</E>
                     keyword search the DOT Docket Number list in the 
                    <E T="02">ADDRESSES</E>
                     section above or visit the Docket Management Facility (see 
                    <E T="02">ADDRESSES</E>
                     for hours of operation). Please periodically check the Docket for new submissions and supporting material.
                </P>
                <HD SOURCE="HD2">Will my comments be made available to the public?</HD>
                <P>Yes. Your entire comment, including your personal identifying information, will be made publicly available.</P>
                <HD SOURCE="HD2">May I submit comments confidentially?</HD>
                <P>
                    You may request that MARAD treat your comments as commercially 
                    <PRTPAGE P="41163"/>
                    confidential by submitting them to 
                    <E T="03">SmallVessels@dot.gov.</E>
                     Include in the email subject heading “Contains Confidential Commercial Information” or “Contains CCI” and state in your submission, with specificity, the basis for any such confidential treatment highlighting the CCI portions. If possible, please provide a summary of your submission that can be made available to the public.
                </P>
                <P>If MARAD receives a Freedom of Information Act (FOIA) request for the information, procedures described in the Department's FOIA regulation at 49 CFR 7.29 will be followed. Only information that is ultimately determined to be confidential under those procedures will be exempt from disclosure under FOIA.</P>
                <HD SOURCE="HD1">Privacy Act</HD>
                <P>
                    Anyone can search the electronic form of all comments received into any of our dockets by the name of the individual submitting the comment (or signing the comment, if submitted on behalf of an association, business, labor union, etc.). For information on DOT's compliance with the Privacy Act, please visit 
                    <E T="03">https://www.transportation.gov/privacy.</E>
                </P>
                <EXTRACT>
                    <FP>(Authority: 46 U.S.C. 12121, 49 CFR 1.93(a))</FP>
                </EXTRACT>
                <SIG>
                    <P>By Order of the Maritime Administrator.</P>
                    <NAME>T. Mitchell Hudson, Jr.,</NAME>
                    <TITLE>Secretary, Maritime Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13499 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-81-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Maritime Administration</SUBAGY>
                <DEPDOC>[Docket No. MARAD-2026-1058]</DEPDOC>
                <SUBJECT>Request Notice: Use of Foreign-Built Small Passenger Vessel in United States Coastwise Trade, M/V DEUCE</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Maritime Administration (MARAD), U.S. Department of Transportation (DOT).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Secretary of Transportation, as represented by MARAD, is authorized to make determinations regarding the coastwise use of foreign built; certain U.S. built; and U.S. and foreign rebuilt vessels that solely carry no more than twelve passengers for hire. MARAD has received such a determination request and is publishing this notice to solicit comments to assist with determining whether the proposed use of the vessel set forth in the request would have an adverse effect on U.S. vessel builders or U.S. coastwise trade businesses that use U.S.-built vessels in those businesses. Information about the requestor's vessel, including a description of the proposed service, is in the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section below.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit comments on or before August 5, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments identified by DOT Docket Number MARAD-2026-1058 by any one of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">https://www.regulations.gov.</E>
                         Search the above DOT Docket Number and follow the instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail or Hand Delivery:</E>
                         Docket Management Facility is in the West Building, Ground Floor of the U.S. Department of Transportation. The Docket Management Facility location address is U.S. Department of Transportation, 1200 New Jersey Avenue SE, West Building, Room W12-140, Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except on Federal holidays.
                    </P>
                    <P>
                        <E T="03">Note:</E>
                         If you mail or hand-deliver your comments, we recommend that you include the DOT Docket Number, your name and a mailing address, an email address or a telephone number in the body of your document so that we can contact you if we have questions regarding your submission.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions received must include the agency name and specific DOT Docket Number. All comments received will be posted without change to the docket at 
                        <E T="03">www.regulations.gov,</E>
                         including any personal information provided. For detailed instructions on submitting comments, or to submit comments that are confidential in nature, see the section entitled Public Participation.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Patricia Hagerty, U.S. Department of Transportation, Maritime Administration, 1200 New Jersey Avenue SE, Mail Stop 2, MAR-620, Washington, DC 20590. Telephone: (202) 366-5400. Email: 
                        <E T="03">smallvessels@dot.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Pursuant to 46 U.S.C. 12121(b), the U.S. Coast Guard may issue a certificate of documentation with a coastwise trade endorsement for eligible, small passenger vessels authorized to carry no more than 12 passengers for hire if MARAD, after notice and an opportunity for public comment, determines the use of the small passenger vessel in the coastwise trade will not adversely affect United States vessel builders or the coastwise trade business of any person that employs vessels built in the United States in that business.
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         The U.S. Coast Guard and MARAD have authority under 46 U.S.C. 12121(b) through the Secretary of the Department of Homeland Security and the Secretary of the Department of Transportation, respectively.
                    </P>
                </FTNT>
                <P>
                    MARAD has received an eligibility determination request. Further details about the requester's vessel and its proposed operations may be found in the determination request posted in the DOT Docket Number listed in the 
                    <E T="02">ADDRESSES</E>
                     section above at 
                    <E T="03">https://www.regulations.gov.</E>
                     Interested parties may comment on the undue adverse effect this action may have on U.S. vessel builders or coastwise trade businesses in the U.S. that employ U.S.-built vessels in those businesses. Comments should refer to the vessel name, state the commenter's interest in the request, and demonstrate, with supporting documentation, the undue adverse effect on U.S. vessel builders and coastwise trade businesses.
                </P>
                <HD SOURCE="HD1">Public Participation</HD>
                <HD SOURCE="HD2">How do I submit comments?</HD>
                <P>
                    Please submit comments, including the attachments, following the instructions provided under the above heading entitled 
                    <E T="02">ADDRESSES</E>
                    . It may take a few hours or even days for comments to be reflected on the docket. Comments must be written in English. Provide concise comments and attach additional documents as necessary. There is no limit on the length of the attachments.
                </P>
                <HD SOURCE="HD2">Where do I go to read public comments, and find supporting information?</HD>
                <P>
                    The docket online is located at 
                    <E T="03">https://www.regulations.gov,</E>
                     keyword search the DOT Docket Number list in the 
                    <E T="02">ADDRESSES</E>
                     section above or visit the Docket Management Facility (see 
                    <E T="02">ADDRESSES</E>
                     for hours of operation). Please periodically check the Docket for new submissions and supporting material.
                </P>
                <HD SOURCE="HD2">Will my comments be made available to the public?</HD>
                <P>Yes. Your entire comment, including your personal identifying information, will be made publicly available.</P>
                <HD SOURCE="HD2">May I submit comments confidentially?</HD>
                <P>
                    You may request that MARAD treat your comments as commercially confidential by submitting them to 
                    <E T="03">SmallVessels@dot.gov.</E>
                     Include in the email subject heading “Contains Confidential Commercial Information” or “Contains CCI” and state in your 
                    <PRTPAGE P="41164"/>
                    submission, with specificity, the basis for any such confidential treatment highlighting the CCI portions. If possible, please provide a summary of your submission that can be made available to the public.
                </P>
                <P>If MARAD receives a Freedom of Information Act (FOIA) request for the information, procedures described in the Department's FOIA regulation at 49 CFR 7.29 will be followed. Only information that is ultimately determined to be confidential under those procedures will be exempt from disclosure under FOIA.</P>
                <HD SOURCE="HD1">Privacy Act</HD>
                <P>
                    Anyone can search the electronic form of all comments received into any of our dockets by the name of the individual submitting the comment (or signing the comment, if submitted on behalf of an association, business, labor union, etc.). For information on DOT's compliance with the Privacy Act, please visit 
                    <E T="03">https://www.transportation.gov/privacy.</E>
                </P>
                <EXTRACT>
                    <FP>(Authority: 46 U.S.C. 12121, 49 CFR 1.93(a))</FP>
                </EXTRACT>
                <SIG>
                    <P>By Order of the Maritime Administrator.</P>
                    <NAME>T. Mitchell Hudson, Jr.,</NAME>
                    <TITLE>Secretary, Maritime Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13502 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-81-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Maritime Administration</SUBAGY>
                <DEPDOC>[Docket No. MARAD-2026-1057]</DEPDOC>
                <SUBJECT>Request Notice: Use of Foreign-Built Small Passenger Vessel in United States Coastwise Trade, S/V GRACIE</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Maritime Administration (MARAD), U.S. Department of Transportation (DOT).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Secretary of Transportation, as represented by MARAD, is authorized to make determinations regarding the coastwise use of foreign built; certain U.S. built; and U.S. and foreign rebuilt vessels that solely carry no more than twelve passengers for hire. MARAD has received such a determination request and is publishing this notice to solicit comments to assist with determining whether the proposed use of the vessel set forth in the request would have an adverse effect on U.S. vessel builders or U.S. coastwise trade businesses that use U.S.-built vessels in those businesses. Information about the requestor's vessel, including a description of the proposed service, is in the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section below.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit comments on or before August 5, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments identified by DOT Docket Number MARAD-2026-1057 by any one of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">https://www.regulations.gov.</E>
                         Search the above DOT Docket Number and follow the instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail or Hand Delivery:</E>
                         Docket Management Facility is in the West Building, Ground Floor of the U.S. Department of Transportation. The Docket Management Facility location address is U.S. Department of Transportation, 1200 New Jersey Avenue SE, West Building, Room W12-140, Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except on Federal holidays.
                    </P>
                    <P>
                        <E T="03">Note:</E>
                         If you mail or hand-deliver your comments, we recommend that you include the DOT Docket Number, your name and a mailing address, an email address or a telephone number in the body of your document so that we can contact you if we have questions regarding your submission.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions received must include the agency name and specific DOT Docket Number. All comments received will be posted without change to the docket at 
                        <E T="03">www.regulations.gov,</E>
                         including any personal information provided. For detailed instructions on submitting comments, or to submit comments that are confidential in nature, see the section entitled Public Participation.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Patricia Hagerty, U.S. Department of Transportation, Maritime Administration, 1200 New Jersey Avenue SE, Mail Stop 2, MAR-620, Washington, DC 20590. Telephone: (202) 366-5400. Email: 
                        <E T="03">smallvessels@dot.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Pursuant to 46 U.S.C. 12121(b), the U.S. Coast Guard may issue a certificate of documentation with a coastwise trade endorsement for eligible, small passenger vessels authorized to carry no more than 12 passengers for hire if MARAD, after notice and an opportunity for public comment, determines the use of the small passenger vessel in the coastwise trade will not adversely affect United States vessel builders or the coastwise trade business of any person that employs vessels built in the United States in that business.
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         The U.S. Coast Guard and MARAD have authority under 46 U.S.C. 12121(b) through the Secretary of the Department of Homeland Security and the Secretary of the Department of Transportation, respectively.
                    </P>
                </FTNT>
                <P>
                    MARAD has received an eligibility determination request. Further details about the requester's vessel and its proposed operations may be found in the determination request posted in the DOT Docket Number listed in the 
                    <E T="02">ADDRESSES</E>
                     section above at 
                    <E T="03">https://www.regulations.gov.</E>
                     Interested parties may comment on the undue adverse effect this action may have on U.S. vessel builders or coastwise trade businesses in the U.S. that employ U.S.-built vessels in those businesses. Comments should refer to the vessel name, state the commenter's interest in the request, and demonstrate, with supporting documentation, the undue adverse effect on U.S. vessel builders and coastwise trade businesses.
                </P>
                <HD SOURCE="HD1">Public Participation</HD>
                <HD SOURCE="HD2">How do I submit comments?</HD>
                <P>
                    Please submit comments, including the attachments, following the instructions provided under the above heading entitled 
                    <E T="02">ADDRESSES</E>
                    . It may take a few hours or even days for comments to be reflected on the docket. Comments must be written in English. Provide concise comments and attach additional documents as necessary. There is no limit on the length of the attachments.
                </P>
                <HD SOURCE="HD2">Where do I go to read public comments, and find supporting information?</HD>
                <P>
                    The docket online is located at 
                    <E T="03">https://www.regulations.gov,</E>
                     keyword search the DOT Docket Number list in the 
                    <E T="02">ADDRESSES</E>
                     section above or visit the Docket Management Facility (see 
                    <E T="02">ADDRESSES</E>
                     for hours of operation). Please periodically check the Docket for new submissions and supporting material.
                </P>
                <HD SOURCE="HD2">Will my comments be made available to the public?</HD>
                <P>Yes. Your entire comment, including your personal identifying information, will be made publicly available.</P>
                <HD SOURCE="HD2">May I submit comments confidentially?</HD>
                <P>
                    You may request that MARAD treat your comments as commercially confidential by submitting them to 
                    <E T="03">SmallVessels@dot.gov.</E>
                     Include in the email subject heading “Contains Confidential Commercial Information” or “Contains CCI” and state in your submission, with specificity, the basis for any such confidential treatment 
                    <PRTPAGE P="41165"/>
                    highlighting the CCI portions. If possible, please provide a summary of your submission that can be made available to the public.
                </P>
                <P>If MARAD receives a Freedom of Information Act (FOIA) request for the information, procedures described in the Department's FOIA regulation at 49 CFR 7.29 will be followed. Only information that is ultimately determined to be confidential under those procedures will be exempt from disclosure under FOIA.</P>
                <HD SOURCE="HD1">Privacy Act</HD>
                <P>
                    Anyone can search the electronic form of all comments received into any of our dockets by the name of the individual submitting the comment (or signing the comment, if submitted on behalf of an association, business, labor union, etc.). For information on DOT's compliance with the Privacy Act, please visit 
                    <E T="03">https://www.transportation.gov/privacy.</E>
                </P>
                <EXTRACT>
                    <FP>(Authority: 46 U.S.C. 12121, 49 CFR 1.93(a))</FP>
                </EXTRACT>
                <SIG>
                    <P>By Order of the Maritime Administrator.</P>
                    <NAME>T. Mitchell Hudson, Jr.,</NAME>
                    <TITLE>Secretary, Maritime Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13501 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-81-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Maritime Administration</SUBAGY>
                <DEPDOC>[Docket No. MARAD-2026-1061]</DEPDOC>
                <SUBJECT>Request Notice: Use of Foreign-Built Small Passenger Vessel in United States Coastwise Trade, M/V MEAT WAGON 2</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Maritime Administration (MARAD), U.S. Department of Transportation (DOT).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Secretary of Transportation, as represented by MARAD, is authorized to make determinations regarding the coastwise use of foreign built; certain U.S. built; and U.S. and foreign rebuilt vessels that solely carry no more than twelve passengers for hire. MARAD has received such a determination request and is publishing this notice to solicit comments to assist with determining whether the proposed use of the vessel set forth in the request would have an adverse effect on U.S. vessel builders or U.S. coastwise trade businesses that use U.S.-built vessels in those businesses. Information about the requestor's vessel, including a description of the proposed service, is in the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section below.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit comments on or before August 5, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments identified by DOT Docket Number MARAD-2026-1061 by any one of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">https://www.regulations.gov.</E>
                         Search the above DOT Docket Number and follow the instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail or Hand Delivery:</E>
                         Docket Management Facility is in the West Building, Ground Floor of the U.S. Department of Transportation. The Docket Management Facility location address is U.S. Department of Transportation, 1200 New Jersey Avenue SE, West Building, Room W12-140, Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except on Federal holidays.
                    </P>
                    <P>
                        <E T="03">Note:</E>
                         If you mail or hand-deliver your comments, we recommend that you include the DOT Docket Number, your name and a mailing address, an email address or a telephone number in the body of your document so that we can contact you if we have questions regarding your submission.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions received must include the agency name and specific DOT Docket Number. All comments received will be posted without change to the docket at 
                        <E T="03">www.regulations.gov,</E>
                         including any personal information provided. For detailed instructions on submitting comments, or to submit comments that are confidential in nature, see the section entitled Public Participation.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Patricia Hagerty, U.S. Department of Transportation, Maritime Administration, 1200 New Jersey Avenue SE, Mail Stop 2, MAR-620, Washington, DC 20590. Telephone: (202) 366-5400. Email: 
                        <E T="03">smallvessels@dot.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Pursuant to 46 U.S.C. 12121(b), the U.S. Coast Guard may issue a certificate of documentation with a coastwise trade endorsement for eligible, small passenger vessels authorized to carry no more than 12 passengers for hire if MARAD, after notice and an opportunity for public comment, determines the use of the small passenger vessel in the coastwise trade will not adversely affect United States vessel builders or the coastwise trade business of any person that employs vessels built in the United States in that business.
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         The U.S. Coast Guard and MARAD have authority under 46 U.S.C. 12121(b) through the Secretary of the Department of Homeland Security and the Secretary of the Department of Transportation, respectively.
                    </P>
                </FTNT>
                <P>
                    MARAD has received an eligibility determination request. Further details about the requester's vessel and its proposed operations may be found in the determination request posted in the DOT Docket Number listed in the 
                    <E T="02">ADDRESSES</E>
                     section above at 
                    <E T="03">https://www.regulations.gov.</E>
                     Interested parties may comment on the undue adverse effect this action may have on U.S. vessel builders or coastwise trade businesses in the U.S. that employ U.S.-built vessels in those businesses. Comments should refer to the vessel name, state the commenter's interest in the request, and demonstrate, with supporting documentation, the undue adverse effect on U.S. vessel builders and coastwise trade businesses.
                </P>
                <HD SOURCE="HD1">Public Participation</HD>
                <HD SOURCE="HD2">How do I submit comments?</HD>
                <P>
                    Please submit comments, including the attachments, following the instructions provided under the above heading entitled 
                    <E T="02">ADDRESSES</E>
                    . It may take a few hours or even days for comments to be reflected on the docket. Comments must be written in English. Provide concise comments and attach additional documents as necessary. There is no limit on the length of the attachments.
                </P>
                <HD SOURCE="HD2">Where do I go to read public comments, and find supporting information?</HD>
                <P>
                    The docket online is located at 
                    <E T="03">https://www.regulations.gov,</E>
                     keyword search the DOT Docket Number list in the 
                    <E T="02">ADDRESSES</E>
                     section above or visit the Docket Management Facility (see 
                    <E T="02">ADDRESSES</E>
                     for hours of operation). Please periodically check the Docket for new submissions and supporting material.
                </P>
                <HD SOURCE="HD2">Will my comments be made available to the public?</HD>
                <P>Yes. Your entire comment, including your personal identifying information, will be made publicly available.</P>
                <HD SOURCE="HD2">May I submit comments confidentially?</HD>
                <P>
                    You may request that MARAD treat your comments as commercially confidential by submitting them to 
                    <E T="03">SmallVessels@dot.gov.</E>
                     Include in the email subject heading “Contains Confidential Commercial Information” or “Contains CCI” and state in your submission, with specificity, the basis for any such confidential treatment 
                    <PRTPAGE P="41166"/>
                    highlighting the CCI portions. If possible, please provide a summary of your submission that can be made available to the public.
                </P>
                <P>If MARAD receives a Freedom of Information Act (FOIA) request for the information, procedures described in the Department's FOIA regulation at 49 CFR 7.29 will be followed. Only information that is ultimately determined to be confidential under those procedures will be exempt from disclosure under FOIA.</P>
                <HD SOURCE="HD1">Privacy Act</HD>
                <P>
                    Anyone can search the electronic form of all comments received into any of our dockets by the name of the individual submitting the comment (or signing the comment, if submitted on behalf of an association, business, labor union, etc.). For information on DOT's compliance with the Privacy Act, please visit 
                    <E T="03">https://www.transportation.gov/privacy.</E>
                </P>
                <EXTRACT>
                    <FP>(Authority: 46 U.S.C. 12121, 49 CFR 1.93(a))</FP>
                </EXTRACT>
                <SIG>
                    <P>By Order of the Maritime Administrator.</P>
                    <NAME>T. Mitchell Hudson, Jr.,</NAME>
                    <TITLE>Secretary, Maritime Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13498 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-81-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Maritime Administration</SUBAGY>
                <DEPDOC>[Docket No. MARAD-2026-1059]</DEPDOC>
                <SUBJECT>Request Notice: Use of Foreign-Built Small Passenger Vessel in United States Coastwise Trade, S/V KINGSLEY</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Maritime Administration (MARAD), U.S. Department of Transportation (DOT).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Secretary of Transportation, as represented by MARAD, is authorized to make determinations regarding the coastwise use of foreign built; certain U.S. built; and U.S. and foreign rebuilt vessels that solely carry no more than twelve passengers for hire. MARAD has received such a determination request and is publishing this notice to solicit comments to assist with determining whether the proposed use of the vessel set forth in the request would have an adverse effect on U.S. vessel builders or U.S. coastwise trade businesses that use U.S.-built vessels in those businesses. Information about the requestor's vessel, including a description of the proposed service, is in the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section below.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit comments on or before August 5, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments identified by DOT Docket Number MARAD-2026-1059 by any one of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">https://www.regulations.gov.</E>
                         Search the above DOT Docket Number and follow the instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail or Hand Delivery:</E>
                         Docket Management Facility is in the West Building, Ground Floor of the U.S. Department of Transportation. The Docket Management Facility location address is U.S. Department of Transportation, 1200 New Jersey Avenue SE, West Building, Room W12-140, Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except on Federal holidays.
                    </P>
                    <P>
                        <E T="03">Note:</E>
                         If you mail or hand-deliver your comments, we recommend that you include the DOT Docket Number, your name and a mailing address, an email address or a telephone number in the body of your document so that we can contact you if we have questions regarding your submission.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions received must include the agency name and specific DOT Docket Number. All comments received will be posted without change to the docket at 
                        <E T="03">www.regulations.gov,</E>
                         including any personal information provided. For detailed instructions on submitting comments, or to submit comments that are confidential in nature, see the section entitled Public Participation.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Patricia Hagerty, U.S. Department of Transportation, Maritime Administration, 1200 New Jersey Avenue SE, Mail Stop 2, MAR-620, Washington, DC 20590. Telephone: (202) 366-5400. Email: 
                        <E T="03">smallvessels@dot.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Pursuant to 46 U.S.C. 12121(b), the U.S. Coast Guard may issue a certificate of documentation with a coastwise trade endorsement for eligible, small passenger vessels authorized to carry no more than 12 passengers for hire if MARAD, after notice and an opportunity for public comment, determines the use of the small passenger vessel in the coastwise trade will not adversely affect United States vessel builders or the coastwise trade business of any person that employs vessels built in the United States in that business.
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         The U.S. Coast Guard and MARAD have authority under 46 U.S.C. 12121(b) through the Secretary of the Department of Homeland Security and the Secretary of the Department of Transportation, respectively.
                    </P>
                </FTNT>
                <P>
                    MARAD has received an eligibility determination request. Further details about the requester's vessel and its proposed operations may be found in the determination request posted in the DOT Docket Number listed in the 
                    <E T="02">ADDRESSES</E>
                     section above at 
                    <E T="03">https://www.regulations.gov.</E>
                     Interested parties may comment on the undue adverse effect this action may have on U.S. vessel builders or coastwise trade businesses in the U.S. that employ U.S.-built vessels in those businesses. Comments should refer to the vessel name, state the commenter's interest in the request, and demonstrate, with supporting documentation, the undue adverse effect on U.S. vessel builders and coastwise trade businesses.
                </P>
                <HD SOURCE="HD1">Public Participation</HD>
                <HD SOURCE="HD2">How do I submit comments?</HD>
                <P>
                    Please submit comments, including the attachments, following the instructions provided under the above heading entitled 
                    <E T="02">ADDRESSES</E>
                    . It may take a few hours or even days for comments to be reflected on the docket. Comments must be written in English. Provide concise comments and attach additional documents as necessary. There is no limit on the length of the attachments.
                </P>
                <HD SOURCE="HD2">Where do I go to read public comments, and find supporting information?</HD>
                <P>
                    The docket online is located at 
                    <E T="03">https://www.regulations.gov,</E>
                     keyword search the DOT Docket Number list in the 
                    <E T="02">ADDRESSES</E>
                     section above or visit the Docket Management Facility (see 
                    <E T="02">ADDRESSES</E>
                     for hours of operation). Please periodically check the Docket for new submissions and supporting material.
                </P>
                <HD SOURCE="HD2">Will my comments be made available to the public?</HD>
                <P>Yes. Your entire comment, including your personal identifying information, will be made publicly available.</P>
                <HD SOURCE="HD2">May I submit comments confidentially?</HD>
                <P>
                    You may request that MARAD treat your comments as commercially confidential by submitting them to 
                    <E T="03">SmallVessels@dot.gov.</E>
                     Include in the email subject heading “Contains Confidential Commercial Information” or “Contains CCI” and state in your submission, with specificity, the basis for any such confidential treatment 
                    <PRTPAGE P="41167"/>
                    highlighting the CCI portions. If possible, please provide a summary of your submission that can be made available to the public.
                </P>
                <P>If MARAD receives a Freedom of Information Act (FOIA) request for the information, procedures described in the Department's FOIA regulation at 49 CFR 7.29 will be followed. Only information that is ultimately determined to be confidential under those procedures will be exempt from disclosure under FOIA.</P>
                <HD SOURCE="HD1">Privacy Act</HD>
                <P>
                    Anyone can search the electronic form of all comments received into any of our dockets by the name of the individual submitting the comment (or signing the comment, if submitted on behalf of an association, business, labor union, etc.). For information on DOT's compliance with the Privacy Act, please visit 
                    <E T="03">https://www.transportation.gov/privacy.</E>
                </P>
                <EXTRACT>
                    <FP>(Authority: 46 U.S.C. 12121, 49 CFR 1.93(a))</FP>
                </EXTRACT>
                <SIG>
                    <P>By Order of the Maritime Administrator.</P>
                    <NAME>T. Mitchell Hudson, Jr.,</NAME>
                    <TITLE>Secretary, Maritime Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13500 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-81-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Maritime Administration</SUBAGY>
                <DEPDOC>[Docket No. MARAD-2026-1062]</DEPDOC>
                <SUBJECT>Request Notice: Use of Foreign-Built Small Passenger Vessel in United States Coastwise Trade, S/V NAUTI DOG</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Maritime Administration (MARAD), U.S. Department of Transportation (DOT).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Secretary of Transportation, as represented by MARAD, is authorized to make determinations regarding the coastwise use of foreign built; certain U.S. built; and U.S. and foreign rebuilt vessels that solely carry no more than twelve passengers for hire. MARAD has received such a determination request and is publishing this notice to solicit comments to assist with determining whether the proposed use of the vessel set forth in the request would have an adverse effect on U.S. vessel builders or U.S. coastwise trade businesses that use U.S.-built vessels in those businesses. Information about the requestor's vessel, including a description of the proposed service, is in the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section below.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit comments on or before August 5, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments identified by DOT Docket Number MARAD-2026-1062 any one of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">https://www.regulations.gov.</E>
                         Search the above DOT Docket Number and follow the instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail or Hand Delivery</E>
                        : Docket Management Facility is in the West Building, Ground Floor of the U.S. Department of Transportation. The Docket Management Facility location address is U.S. Department of Transportation, 1200 New Jersey Avenue SE, West Building, Room W12-140, Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except on Federal holidays.
                    </P>
                </ADD>
                <NOTE>
                    <HD SOURCE="HED">Note:</HD>
                    <P>If you mail or hand-deliver your comments, we recommend that you include the DOT Docket Number, your name and a mailing address, an email address or a telephone number in the body of your document so that we can contact you if we have questions regarding your submission.</P>
                </NOTE>
                <P>
                    <E T="03">Instructions:</E>
                     All submissions received must include the agency name and specific DOT Docket Number. All comments received will be posted without change to the docket at 
                    <E T="03">www.regulations.gov,</E>
                     including any personal information provided. For detailed instructions on submitting comments, or to submit comments that are confidential in nature, see the section entitled Public Participation.
                </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Patricia Hagerty, U.S. Department of Transportation, Maritime Administration, 1200 New Jersey Avenue SE, Mail Stop 2, MAR-620, Washington, DC 20590. Telephone: (202) 366-5400. Email: 
                        <E T="03">smallvessels@dot.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Pursuant to 46 U.S.C. 12121(b), the U.S. Coast Guard may issue a certificate of documentation with a coastwise trade endorsement for eligible, small passenger vessels authorized to carry no more than 12 passengers for hire if MARAD, after notice and an opportunity for public comment, determines the use of the small passenger vessel in the coastwise trade will not adversely affect United States vessel builders or the coastwise trade business of any person that employs vessels built in the United States in that business.
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         The U.S. Coast Guard and MARAD have authority under 46 U.S.C. 12121(b) through the Secretary of the Department of Homeland Security and the Secretary of the Department of Transportation, respectively.
                    </P>
                </FTNT>
                <P>
                    MARAD has received an eligibility determination request. Further details about the requester's vessel and its proposed operations may be found in the determination request posted in the DOT Docket Number listed in the 
                    <E T="02">ADDRESSES</E>
                     section above at 
                    <E T="03">https://www.regulations.gov.</E>
                     Interested parties may comment on the undue adverse effect this action may have on U.S. vessel builders or coastwise trade businesses in the U.S. that employ U.S.-built vessels in those businesses. Comments should refer to the vessel name, state the commenter's interest in the request, and demonstrate, with supporting documentation, the undue adverse effect on U.S. vessel builders and coastwise trade businesses.
                </P>
                <HD SOURCE="HD1">Public Participation</HD>
                <HD SOURCE="HD2">How do I submit comments?</HD>
                <P>
                    Please submit comments, including the attachments, following the instructions provided under the above heading entitled 
                    <E T="02">ADDRESSES</E>
                    . It may take a few hours or even days for comments to be reflected on the docket. Comments must be written in English. Provide concise comments and attach additional documents as necessary. There is no limit on the length of the attachments.
                </P>
                <HD SOURCE="HD2">Where do I go to read public comments, and find supporting information?</HD>
                <P>
                    The docket online is located at 
                    <E T="03">https://www.regulations.gov,</E>
                     keyword search the DOT Docket Number list in the 
                    <E T="02">ADDRESSES</E>
                     section above or visit the Docket Management Facility (see 
                    <E T="02">ADDRESSES</E>
                     for hours of operation). Please periodically check the Docket for new submissions and supporting material.
                </P>
                <HD SOURCE="HD2">Will my comments be made available to the public?</HD>
                <P>Yes. Your entire comment, including your personal identifying information, will be made publicly available.</P>
                <HD SOURCE="HD2">May I submit comments confidentially?</HD>
                <P>
                    You may request that MARAD treat your comments as commercially confidential by submitting them to 
                    <E T="03">SmallVessels@dot.gov.</E>
                     Include in the email subject heading “Contains Confidential Commercial Information” or “Contains CCI” and state in your submission, with specificity, the basis for any such confidential treatment 
                    <PRTPAGE P="41168"/>
                    highlighting the CCI portions. If possible, please provide a summary of your submission that can be made available to the public.
                </P>
                <P>If MARAD receives a Freedom of Information Act (FOIA) request for the information, procedures described in the Department's FOIA regulation at 49 CFR 7.29 will be followed. Only information that is ultimately determined to be confidential under those procedures will be exempt from disclosure under FOIA.</P>
                <HD SOURCE="HD1">Privacy Act</HD>
                <P>
                    Anyone can search the electronic form of all comments received into any of our dockets by the name of the individual submitting the comment (or signing the comment, if submitted on behalf of an association, business, labor union, etc.). For information on DOT's compliance with the Privacy Act, please visit 
                    <E T="03">https://www.transportation.gov/privacy.</E>
                </P>
                <EXTRACT>
                    <FP>(Authority: 46 U.S.C. 12121, 49 CFR 1.93(a))</FP>
                </EXTRACT>
                <SIG>
                    <P>By Order of the Maritime Administrator.</P>
                    <NAME>T. Mitchell Hudson, Jr.,</NAME>
                    <TITLE>Secretary, Maritime Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13497 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-81-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>National Highway Traffic Safety Administration</SUBAGY>
                <DEPDOC>[Docket No. NHTSA-2022-0112; Notice 2]</DEPDOC>
                <SUBJECT>Rivian Automotive, LLC, Grant of Petition for Decision of Inconsequential Noncompliance</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Highway Traffic Safety Administration (NHTSA), Department of Transportation (DOT).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Grant of petition.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        Rivian Automotive, LLC (Rivian) has determined that certain model year (MY) 2022 Rivian Electric Delivery Van (EDV) motor vehicles do not fully comply with Federal Motor Vehicle Safety Standard (FMVSS) No. 208, 
                        <E T="03">Occupant Crash Protection.</E>
                         Rivian filed a noncompliance report dated October 24, 2022, and amended the report on November 14, 2022. Rivian subsequently petitioned NHTSA (the “Agency”) on November 15, 2022, for a decision that the subject noncompliance is inconsequential as it relates to motor vehicle safety. This document announces the grant of Rivian's petition.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Syed Rahaman, General Engineer, NHTSA, Office of Vehicle Safety Compliance, (202) 366-7018.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">I. Overview:</E>
                     Rivian determined that certain MY 2022 Rivian EDV motor vehicles do not fully comply with paragraph S4.5.1(b)(5)(i) of FMVSS No. 208, Occupant Crash Protection (49 CFR 571.208).
                </P>
                <P>
                    Rivian filed a noncompliance report dated October 24, 2022, and amended the report on November 14, 2022, pursuant to 49 CFR part 573, 
                    <E T="03">Defect and Noncompliance Responsibility and Reports.</E>
                     Rivian petitioned NHTSA on November 15, 2022, for an exemption from the notification and remedy requirements of 49 U.S.C. Chapter 301 on the basis that this noncompliance is inconsequential as it relates to motor vehicle safety, pursuant to 49 U.S.C. 30118(d) and 30120(h) and 49 CFR part 556, 
                    <E T="03">Exemption for Inconsequential Defect or Noncompliance.</E>
                </P>
                <P>
                    Notice of receipt of Rivian's petition was published with a 30-day public comment period, on May 19, 2023, in the 
                    <E T="04">Federal Register</E>
                     (88 FR 32275). No comments were received. To view the petition and all supporting documents log onto the Federal Docket Management System (FDMS) website at 
                    <E T="03">https://www.regulations.gov/.</E>
                     Then follow the online search instructions to locate docket number “NHTSA-2022-0112.”
                </P>
                <P>
                    <E T="03">II. Vehicles Involved:</E>
                     Approximately 1,278 MY 2022 Rivian EDV motor vehicles, manufactured between December 10, 2021, and September 27, 2022, were reported by the manufacturer.
                </P>
                <P>
                    <E T="03">III. Noncompliance:</E>
                     Rivian explains that a label displaying the subject vehicle's clearance height is affixed to the same side of the sun visor containing the air bag warning label, therefore, the subject vehicles do not comply with paragraph S4.5.1(b)(5)(i) of FMVSS No. 208.
                </P>
                <P>
                    <E T="03">IV. Rule Requirements:</E>
                     Paragraph S4.5.1(b)(5)(i) of FMVSS No. 208 includes the requirements relevant to this petition. S4.5.1(b)(5)(i) requires that except for the information on an air bag maintenance label placed on the sun visor pursuant to S4.5.1(a) of FMVSS No. 208, or on a utility vehicle warning label placed on the sun visor that conforms in content, form, and sequence to the label shown in Figure 1 of FMVSS No. 105, no other information shall appear on the same side of the sun visor to which the sun visor air bag warning label is affixed.
                </P>
                <P>
                    <E T="03">V. Summary of Rivian's Petition:</E>
                     The following views and arguments presented in this section, “V. Summary of Rivian's Petition,” are the views and arguments provided by Rivian. They do not reflect the views of the Agency. Rivian describes the subject noncompliance and contends that the noncompliance is inconsequential as it relates to motor vehicle safety.
                </P>
                <P>Rivian states that the air bag warning label that is affixed to the sun visor in the subject vehicles meets the FMVSS No. 208 content requirements and is displayed as intended by the standard. In addition to this compliant label, there is another label affixed to the sun visor that indicates the clearance height of the subject vehicle. Rivian believes that the vehicle clearance height label included on the sun visor is inconsequential to motor vehicle safety because the subject vehicles are exclusively used in a single fleet of delivery vehicles that are driven by professional drivers. Rivian explains that the subject vehicles are walk-in vans in which the driver's seat is the only designated seating position and drivers are required to wear their seat belts when operating the subject vehicle. Because of the vehicle's intended usage, Rivian believes that the subject noncompliance does not affect the efficacy of the information provided by the air bag warning label.</P>
                <P>Furthermore, Rivian contends that the purpose of the requirement that no other information be present with the air bag warning label is to mitigate “the potential for children to be placed at a seating position that is equipped with an air bag and also inform of the precautions the vehicle occupant may take to protect themselves from being injured by a deploying air bag” Rivian believes that this is not a risk because there is no expectation that a child would be present in or around the subject vehicle. Rivian states that if a child were to occupy the driver's seat, the brake transmission shift interlock that is required by FMVSS No. 114 would prevent the child from operating the vehicle, thus there would be no way for the air bags to be deployed.</P>
                <P>Additionally, Rivian says that the drivers of the subject vehicles are required to use the seat belt at all times and the information provided by the air bag warning label is visible, easy to read, and not positioned near the vehicle clearance height label. Therefore, Rivian believes that there is no indication that the addition of the noncompliant vehicle clearance height label would cause a driver of the subject vehicle to confuse the message of the air bag warning label.</P>
                <P>
                    Rivian believes that the reason NHTSA determined that no other types of information are allowed to be displayed on the same side of the sun visor as the air bag warning label was to maximize the effectiveness of the label's content by ensuring that there is 
                    <PRTPAGE P="41169"/>
                    consistent and uniform messaging to consumers. Rivian quotes NHTSA's decision on a similar petition from Maserati: “The purpose of [the air bag warning label in] FMVSS No. 208 is to reduce the adverse effects of air bags by attracting the attention of vehicle occupants to look for the air bag warning label on the sun visor.” 
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See</E>
                         Grant of Petition of Maserati, 87 FR 54749, September 7, 2022).
                    </P>
                </FTNT>
                <P>
                    Rivian contends that in past inconsequentiality petitions, NHTSA determined “that the manner in which a particular subset of vehicles is used bears upon the inconsequential nature of the air bag warning label noncompliance.” Further, Rivian says that NHTSA has previously granted inconsequentiality for a noncompliance involving the placement of the air bag warning label in a vocational vehicle and found that due to the nature and intended use of the affected vehicles, it would be unlikely for children to be placed in the front passenger seating area.
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See</E>
                         Grant of Petition of Spartan Motors, 81 FR 87654, December 5, 2016
                    </P>
                </FTNT>
                <P>
                    Rivian adds that NHTSA granted prior petitions in which the air bag warning label deviated from the exact language that is required by the standard.
                    <SU>3</SU>
                    <FTREF/>
                     Although those petitions related to the language that was used in the advanced air bag warning label, Rivian contends that NHTSA's rationale for those determinations still applies in the present case.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         Grant of Petition to Bentley Motors, 72 FR 71734, December 12, 2007; 
                        <E T="03">see also</E>
                         Grant of Petition to BMW, 71 FR 78511, December 29, 2006.
                    </P>
                </FTNT>
                <P>Rivian states that the subject noncompliance has been corrected for vehicles in production. Rivian says it is not aware of any crash, death, injury, field report, or claims related to the subject noncompliance.</P>
                <P>Rivian concludes by stating its belief that the subject noncompliance is inconsequential as it relates to motor vehicle safety and its petition to be exempted from providing notification of the noncompliance, as required by 49 U.S.C. 30118, and a remedy for the noncompliance, as required by 49 U.S.C. 30120, should be granted.</P>
                <P>
                    <E T="03">VI. NHTSA's Analysis:</E>
                </P>
                <P>
                    In determining inconsequentiality of a noncompliance, NHTSA focuses on the safety risk to individuals who experience the type of event against which a recall would otherwise protect.
                    <SU>4</SU>
                    <FTREF/>
                     In general, NHTSA does not consider the absence of complaints or injuries when determining if a noncompliance is inconsequential to safety. The absence of complaints does not mean vehicle occupants have not experienced a safety issue, nor does it mean that there will not be safety issues in the future.
                    <SU>5</SU>
                    <FTREF/>
                     Further, because each inconsequential noncompliance petition must be evaluated on its own facts and determinations are highly fact-dependent, NHTSA does not consider prior determinations as binding precedent. Petitioners are reminded that they have the burden of persuading NHTSA that the noncompliance is inconsequential to safety. FMVSS No. 208 S4.5.1(b)(5)(i) requires that except for the information on an air bag maintenance label placed on the sun visor pursuant to S4.5.1(a) of FMVSS No. 208, or on a utility vehicle warning label placed on the sun visor that conforms in content, form, and sequence to the label shown in Figure 1 of FMVSS No. 105, no other information shall appear on the same side of the sun visor to which the sun visor air bag warning label is affixed.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See Gen. Motors, LLC; Grant of Petition for Decision of Inconsequential Noncompliance,</E>
                         78 FR 35355 (June 12, 2013) (finding noncompliance had no effect on occupant safety because it had no effect on the proper operation of the occupant classification system and the correct deployment of an air bag); 
                        <E T="03">Osram Sylvania Prods. Inc.; Grant of Petition for Decision of Inconsequential Noncompliance,</E>
                         78 FR 46000 (July 30, 2013) (finding occupant using noncompliant light source would not be exposed to significantly greater risk than occupant using similar compliant light source).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See Morgan 3 Wheeler Limited; Denial of Petition for Decision of Inconsequential Noncompliance,</E>
                         81 FR 21663, 21666 (Apr. 12, 2016); 
                        <E T="03">see also United States</E>
                         v. 
                        <E T="03">Gen. Motors Corp.,</E>
                         565 F.2d 754, 759 (D.C. Cir. 1977) (finding defect poses an unreasonable risk when it “results in hazards as potentially dangerous as sudden engine fire, and where there is no dispute that at least some such hazards, in this case fires, can definitely be expected to occur in the future”).
                    </P>
                </FTNT>
                <P>The purpose of that labeling requirement is to reduce the adverse effects of air bags by attracting the attention of vehicle occupants to look for the air bag warning label on the sun visor. In its petition, Rivian explains that the subject vehicles are equipped with a label displaying the vehicle's clearance height that is affixed to the same side of the sun visor containing the air bag warning label. Rivian has provided evidence that even with the addition of the vehicle's clearance height information, the FMVSS No. 208 required Figure 1 label is present, unobstructed, and within clear view of the driver.</P>
                <P>Additionally, Rivian explains that in the subject vehicles, the driver's seat is the only designated seating position. With the understanding that these vehicles are delivery vans, the vehicle's clearance height could potentially be a frequently used piece of information for the driver.</P>
                <P>NHTSA has evaluated the merits of the inconsequential noncompliance petition submitted by Rivian and has determined that this particular noncompliance is inconsequential to motor vehicle safety. NHTSA agrees that given the nature and intended use of the subject vocational vehicles, it would be unlikely for children to be placed in the front passenger seating area.</P>
                <P>
                    <E T="03">VII. NHTSA's Decision:</E>
                     In consideration of the foregoing, NHTSA finds that Rivian has met its burden of persuasion that the subject FMVSS No. 208 noncompliance in the affected vehicles is inconsequential to motor vehicle safety. Accordingly, Rivian's petition is hereby granted and Rivian is consequently exempted from the obligation of providing notification of, and a free remedy for, that noncompliance under 49 U.S.C. 30118 and 30120.
                </P>
                <P>NHTSA notes that the statutory provisions (49 U.S.C. 30118(d) and 30120(h)) that permit manufacturers to file petitions for a determination of inconsequentiality allow NHTSA to exempt manufacturers only from the duties found in sections 30118 and 30120, respectively, to notify owners, purchasers, and dealers of a defect or noncompliance and to remedy the defect or noncompliance. Therefore, this decision only applies to the subject vehicles that Rivian no longer controlled at the time it determined that the noncompliance existed. However, the granting of this petition does not relieve vehicles distributors and dealers of the prohibitions on the sale, offer for sale, or introduction or delivery for introduction into interstate commerce of the noncompliant vehicles under their control after Rivian notified them that the subject noncompliance existed.</P>
                <EXTRACT>
                    <FP>(Authority: 49 U.S.C. 30118, 30120: delegations of authority at 49 CFR 1.95 and 501.8)</FP>
                </EXTRACT>
                <SIG>
                    <NAME>Otto G. Matheke III,</NAME>
                    <TITLE>Director, Office of Vehicle Safety Compliance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13544 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-59-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Bureau of the Fiscal Service</SUBAGY>
                <SUBJECT>Extension of a Currently Approved Information Collection: TreasuryDirect System</SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Department of the Treasury, as part of its continuing effort 
                        <PRTPAGE P="41170"/>
                        to reduce paperwork and respondent burden, invites the general public and other Federal agencies to take this opportunity to comment on proposed and/or continuing information collections, as required by the Paperwork Reduction Act of 1995. Currently the Bureau of the Fiscal Service within the Department of the Treasury is soliciting comments concerning the TreasuryDirect System.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be received on or before September 4, 2026 to be assured of consideration.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Direct all written comments and requests for additional information to Bureau of the Fiscal Service, Bruce A. Sharp, T1-G, P.O. Box 1328, Parkersburg, WV 26106-1328, or 
                        <E T="03">bruce.sharp@fiscal.treasury.gov.</E>
                    </P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Title:</E>
                     TreasuryDirect System.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1530-0071.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The information collected in the electronic system is requested to establish a new account and process any associated transactions.
                </P>
                <P>
                    <E T="03">Current Actions:</E>
                     Extension of a currently approved collection.
                </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>
                     3,549,700.
                </P>
                <P>
                    <E T="03">Estimated Time per Respondent:</E>
                     10 minutes.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     151,070.
                </P>
                <P>
                    <E T="03">Request for Comments:</E>
                     Comments submitted in response to this notice will be summarized and/or included in the request for OMB approval. All comments will become a matter of public record. Comments are invited on: 1. 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; 2. the accuracy of the agency's estimate of the burden of the collection of information; 3. ways to enhance the quality, utility, and clarity of the information to be collected; 4. 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 5. estimates of capital or start-up costs and costs of operation, maintenance, and purchase of services to provide information.
                </P>
                <SIG>
                    <DATED>Dated: June 30, 2026.</DATED>
                    <NAME>Bruce A. Sharp,</NAME>
                    <TITLE>Bureau PRA Clearance Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13505 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4810-AS-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Bureau of the Fiscal Service</SUBAGY>
                <SUBJECT>Extension of a Currently Approved Information Collection: Certificate of Identity</SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of the Treasury, as part of its continuing effort to reduce paperwork and respondent burden, invites the general public and other Federal agencies to take this opportunity to comment on proposed and/or continuing information collections, as required by the Paperwork Reduction Act of 1995. Currently the Bureau of the Fiscal Service within the Department of the Treasury is soliciting comments concerning the Certificate of Identity.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be received on or before September 4, 2026 to be assured of consideration.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Direct all written comments and requests for additional information to Bureau of the Fiscal Service, Bruce A. Sharp, T1-G, P.O. Box 1328, Parkersburg, WV 26106-1328, or 
                        <E T="03">bruce.sharp@fiscal.treasury.gov.</E>
                    </P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Title:</E>
                     Certificate of Identity.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1530-0026.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     FS Form 0385.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The information on the completed form is used to establish an individual's identity in a claim for payment of United States savings and retirement securities.
                </P>
                <P>
                    <E T="03">Current Actions:</E>
                     Extension of a currently approved collection.
                </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>
                     330.
                </P>
                <P>
                    <E T="03">Estimated Time per Respondent:</E>
                     10 minutes.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     55.
                </P>
                <P>
                    <E T="03">Request for Comments:</E>
                     Comments submitted in response to this notice will be summarized and/or included in the request for OMB approval. All comments will become a matter of public record. Comments are invited on: 1. 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; 2. the accuracy of the agency's estimate of the burden of the collection of information; 3. ways to enhance the quality, utility, and clarity of the information to be collected; 4. 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 5. estimates of capital or start-up costs and costs of operation, maintenance, and purchase of services to provide information.
                </P>
                <SIG>
                    <DATED>Dated: June 30, 2026.</DATED>
                    <NAME>Bruce A. Sharp,</NAME>
                    <TITLE>Bureau PRA Clearance Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13508 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4810-AS-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Bureau of the Fiscal Service</SUBAGY>
                <SUBJECT>Extension of a Currently Approved Information Collection: Pools and Associations—Annual Letter</SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of the Treasury, as part of its continuing effort to reduce paperwork and respondent burden, invites the general public and other Federal agencies to take this opportunity to comment on proposed and/or continuing information collections, as required by the Paperwork Reduction Act of 1995. Currently the Bureau of the Fiscal Service within the Department of the Treasury is soliciting comments concerning the Pools and Associations—Annual Letter.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be received on or before September 4, 2026 to be assured of consideration.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Direct all written comments and requests for additional information to Bureau of the Fiscal Service, Bruce A. Sharp, T1-G, P.O. Box 1328, Parkersburg, WV 26106-1328, or 
                        <E T="03">bruce.sharp@fiscal.treasury.gov.</E>
                    </P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Title:</E>
                     Pools and Associations—Annual Letter.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1530-0007.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The information is collected for the determinations of an acceptable percentage for each pool and association to allow Treasury certified companies credit on their Schedule F for authorized ceded reinsurance in determining the companies' underwriting limitations.
                </P>
                <P>
                    <E T="03">Current Actions:</E>
                     Extension of a currently approved collection.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Regular.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Business or other for-profit.
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     84.
                    <PRTPAGE P="41171"/>
                </P>
                <P>
                    <E T="03">Estimated Time per Respondent:</E>
                     1 hour 30 minutes.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     126.
                </P>
                <P>
                    <E T="03">Request for Comments:</E>
                     Comments submitted in response to this notice will be summarized and/or included in the request for OMB approval. All comments will become a matter of public record. Comments are invited on: 1. 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; 2. the accuracy of the agency's estimate of the burden of the collection of information; 3. ways to enhance the quality, utility, and clarity of the information to be collected; 4. 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 5. estimates of capital or start-up costs and costs of operation, maintenance, and purchase of services to provide information.
                </P>
                <SIG>
                    <DATED>Dated: June 30, 2026.</DATED>
                    <NAME>Bruce A. Sharp,</NAME>
                    <TITLE>Bureau PRA Clearance Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13507 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4810-AS-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Bureau of the Fiscal Service</SUBAGY>
                <SUBJECT>Extension of a Currently Approved Information Collection: Special Form of Request for Payment of US Savings and Retirement Securities Where Use of a Detached Request Is Authorized</SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of the Treasury, as part of its continuing effort to reduce paperwork and respondent burden, invites the general public and other Federal agencies to take this opportunity to comment on proposed and/or continuing information collections, as required by the Paperwork Reduction Act of 1995. Currently the Bureau of the Fiscal Service within the Department of the Treasury is soliciting comments concerning the Special Form of Request for Payment of US Savings and Retirement Securities Where Use of a Detached Request is Authorized.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be received on or before September 4, 2026 to be assured of consideration.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Direct all written comments and requests for additional information to Bureau of the Fiscal Service, Bruce A. Sharp, T1-G, PO Box 1328, Parkersburg, WV 26106-1328, or 
                        <E T="03">bruce.sharp@fiscal.treasury.gov.</E>
                    </P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Title:</E>
                     Special Form of Request for Payment of US Savings and Retirement Securities Where Use of a Detached Request is Authorized.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1530-0028.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     FS Form 1522.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The information on the completed form is submitted by the owner, co-owner, surviving beneficiary, or legal representative of the estate of a deceased or incompetent owner, persons entitled to the estate of a deceased registrant, or such other persons to request payment of United States Savings Bonds, Savings Notes, Retirement Plan Bonds, and Individual Retirement Bonds.
                </P>
                <P>
                    <E T="03">Current Actions:</E>
                     Extension of a currently approved collection.
                </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>
                     14,000.
                </P>
                <P>
                    <E T="03">Estimated Time per Respondent:</E>
                     15 minutes.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     3,500.
                </P>
                <P>
                    <E T="03">Request for Comments:</E>
                     Comments submitted in response to this notice will be summarized and/or included in the request for OMB approval. All comments will become a matter of public record. Comments are invited on: 1. 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; 2. the accuracy of the agency's estimate of the burden of the collection of information; 3. ways to enhance the quality, utility, and clarity of the information to be collected; 4. 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 5. estimates of capital or start-up costs and costs of operation, maintenance, and purchase of services to provide information.
                </P>
                <SIG>
                    <DATED>Dated: June 30, 2026.</DATED>
                    <NAME>Bruce A. Sharp,</NAME>
                    <TITLE>Bureau PRA Clearance Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13504 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4810-AS-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Office of Foreign Assets Control</SUBAGY>
                <SUBJECT>Notice of OFAC Sanctions Actions</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Foreign Assets Control, Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The U.S. Department of the Treasury's Office of Foreign Assets Control (OFAC) is publishing the names of one or more persons that have been placed on OFAC's Specially Designated Nationals and Blocked Persons List (SDN List) based on OFAC's determination that one or more applicable legal criteria were satisfied. All property and interests in property subject to U.S. jurisdiction of these persons are blocked, and U.S. persons are generally prohibited from engaging in transactions with them.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        This action was issued on June 30, 2026. See 
                        <E T="02">Supplementary Information</E>
                         for relevant dates.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        OFAC: Associate Director for Global Targeting, 202-622-2420; Assistant Director for Sanctions Compliance, 202-622-2490; or 
                        <E T="03">https://ofac.treasury.gov/contact-ofac.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Electronic Availability</HD>
                <P>
                    The SDN List and additional information concerning OFAC sanctions programs are available on OFAC's website: 
                    <E T="03">https://ofac.treasury.gov.</E>
                </P>
                <HD SOURCE="HD1">Notice of OFAC Actions</HD>
                <P>On June 30, 2026, OFAC determined that one or more persons identified below meet one or more of the criteria for the imposition of sanctions set forth in section 1(a)-(c) of Executive Order 14059 of December 15, 2021, “Imposing Sanctions on Foreign Persons Involved in the Global Illicit Drug Trade,” 86 FR 71549 (E.O. 14059). OFAC has selected to impose blocking sanctions pursuant to section 2(a)(i) of E.O. 14059 on the persons identified below.</P>
                <P>OFAC further determined that one or more persons identified below meet one or more of the criteria for sanctions pursuant to Executive Order 13224 of September 23, 2001, “Blocking Property and Prohibiting Transactions With Persons Who Commit, Threaten to Commit, or Support Terrorism,” 66 FR 49079, as amended by Executive Order 13886 of September 9, 2019, “Modernizing Sanctions To Combat Terrorism,” 84 FR 48041 (E.O. 13224, as amended).</P>
                <P>
                    As a result, the property and interests in property subject to U.S. jurisdiction 
                    <PRTPAGE P="41172"/>
                    of the following persons are blocked under the relevant sanctions authorities listed below.
                </P>
                <EXTRACT>
                    <HD SOURCE="HD1">Individuals</HD>
                    <P>1. JURAIDINI SILVA, Oscar Guillermo, Mexico; DOB 01 Sep 1984; POB Tamaulipas, Mexico; nationality Mexico; Gender Male; Secondary sanctions risk: section 1(b) of Executive Order 13224, as amended by Executive Order 13886; C.U.R.P. JUSO840901HTSRLS09 (Mexico) (individual) [SDGT] [ILLICIT-DRUGS-EO14059] (Linked To: CARTEL DE JALISCO NUEVA GENERACION).</P>
                    <P>Sanctioned pursuant to section 1(b)(iii) of E.O. 14059 for being owned, controlled, or directed by, or having acted or purported to act for or on behalf of, directly or indirectly, the Cartel de Jalisco Nueva Generacion (CJNG), a sanctioned person pursuant to E.O. 14059.</P>
                    <P>Designated pursuant to section 1(a)(iii)(A) of E.O. 13224, as amended, for being owned, controlled, or directed by, or having acted or purported to act for or on behalf of, directly or indirectly, CJNG, a person whose property and interests in property are blocked pursuant to E.O. 13224, as amended.</P>
                    <P>2. RUIZ VILLAGOMEZ, J. Refugio (a.k.a. RUIZ VILLAGOMEZ, Jose Refugio), Mexico; DOB 27 Aug 1961; POB Guanajuato, Mexico; nationality Mexico; Gender Male; Secondary sanctions risk: section 1(b) of Executive Order 13224, as amended by Executive Order 13886; C.U.R.P. RUVR610827HGTZLF02 (Mexico) (individual) [SDGT] [ILLICIT-DRUGS-EO14059] (Linked To: JOMADI LOGISTICS AND CARGO, S.A. DE C.V.; Linked To: AHAVAT LOGISTICS SOLUTION, S.A. DE C.V.).</P>
                    <P>Sanctioned pursuant to section 1(b)(iii) of E.O. 14059 for being owned, controlled, or directed by, or having acted or purported to act for or on behalf of, directly or indirectly, Ahavat Logistics Solution, S.A. de C.V. and Jomadi Logistics and Cargo, S.A. de C.V., sanctioned persons pursuant to E.O. 14059.</P>
                    <P>Designated pursuant to section 1(a)(iii)(A) of E.O. 13224, as amended, for being owned, controlled, or directed by, or having acted or purported to act for or on behalf of, directly or indirectly, Ahavat Logistics Solution, S.A. de C.V. and Jomadi Logistics and Cargo, S.A. de C.V., persons whose property and interests in property are blocked pursuant to E.O. 13224, as amended.</P>
                    <HD SOURCE="HD1">Entities</HD>
                    <P>1. CENTRO CAMBIARIO LA PESETA, S.A. DE C.V., Matamoros, Tamaulipas, Mexico; Secondary sanctions risk: section 1(b) of Executive Order 13224, as amended by Executive Order 13886; Organization Established Date 01 Feb 2012; Organization Type: Other financial service activities, except insurance and pension funding activities, n.e.c.; Folio Mercantil No. 1610 (Mexico) [SDGT] [ILLICIT-DRUGS-EO14059] (Linked To: JURAIDINI SILVA, Oscar Guillermo).</P>
                    <P>Sanctioned pursuant to section 1(b)(iii) of E.O. 14059 for being owned, controlled, or directed by, or having acted or purported to act for or on behalf of, directly or indirectly, Oscar Guillermo Juraidini Silva, a sanctioned person pursuant to E.O. 14059.</P>
                    <P>Designated pursuant to section 1(a)(iii)(A) of E.O. 13224, as amended, for being owned, controlled, or directed by, or having acted or purported to act for or on behalf of, directly or indirectly, Oscar Guillermo Juraidini Silva, a person whose property and interests in property are blocked pursuant to E.O. 13224, as amended.</P>
                    <P>2. CUCUMBER SWEET WAVES LTD, 27 Old Gloucester Street, London WC1N 3AX, United Kingdom; Secondary sanctions risk: section 1(b) of Executive Order 13224, as amended by Executive Order 13886; Organization Established Date 02 Sep 2024; Company Number 15928462 (United Kingdom) [SDGT] [ILLICIT-DRUGS-EO14059] (Linked To: JURAIDINI SILVA, Oscar Guillermo).</P>
                    <P>Sanctioned pursuant to section 1(b)(iii) of E.O. 14059 for being owned, controlled, or directed by, or having acted or purported to act for or on behalf of, directly or indirectly, Oscar Guillermo Juraidini Silva, a sanctioned person pursuant to E.O. 14059.</P>
                    <P>Designated pursuant to section 1(a)(iii)(A) of E.O. 13224, as amended, for being owned, controlled, or directed by, or having acted or purported to act for or on behalf of, directly or indirectly, Oscar Guillermo Juraidini Silva, a person whose property and interests in property are blocked pursuant to E.O. 13224, as amended.</P>
                    <P>3. OGUI FLETES, Matamoros, Tamaulipas, Mexico; Secondary sanctions risk: section 1(b) of Executive Order 13224, as amended by Executive Order 13886; Organization Type: Transportation and storage [SDGT] [ILLICIT-DRUGS-EO14059] (Linked To: JURAIDINI SILVA, Oscar Guillermo).</P>
                    <P>Sanctioned pursuant to section 1(b)(iii) of E.O. 14059 for being owned, controlled, or directed by, or having acted or purported to act for or on behalf of, directly or indirectly, Oscar Guillermo Juraidini Silva, a sanctioned person pursuant to E.O. 14059.</P>
                    <P>Designated pursuant to section 1(a)(iii)(A) of E.O. 13224, as amended, for being owned, controlled, or directed by, or having acted or purported to act for or on behalf of, directly or indirectly, Oscar Guillermo Juraidini Silva, a person whose property and interests in property are blocked pursuant to E.O. 13224, as amended.</P>
                    <P>4. OJ LIVING TRUST, S.A.P.I. DE C.V., Monterrey, Nuevo Leon, Mexico; Secondary sanctions risk: section 1(b) of Executive Order 13224, as amended by Executive Order 13886; Organization Established Date 28 Nov 2022; Organization Type: Real estate activities with own or leased property; Folio Mercantil No. N-2023006827 (Mexico) [SDGT] [ILLICIT-DRUGS-EO14059] (Linked To: JURAIDINI SILVA, Oscar Guillermo).</P>
                    <P>Sanctioned pursuant to section 1(b)(iii) of E.O. 14059 for being owned, controlled, or directed by, or having acted or purported to act for or on behalf of, directly or indirectly, Oscar Guillermo Juraidini Silva, a sanctioned person pursuant to E.O. 14059.</P>
                    <P>Designated pursuant to section 1(a)(iii)(A) of E.O. 13224, as amended, for being owned, controlled, or directed by, or having acted or purported to act for or on behalf of, directly or indirectly, Oscar Guillermo Juraidini Silva, a person whose property and interests in property are blocked pursuant to E.O. 13224, as amended.</P>
                    <P>5. RK REAL KING, S.A. DE C.V., Queretaro, Queretaro, Mexico; Secondary sanctions risk: section 1(b) of Executive Order 13224, as amended by Executive Order 13886; Organization Established Date 23 Nov 2018; Organization Type: Real estate activities with own or leased property; Folio Mercantil No. N-2018095907 (Mexico) [SDGT] [ILLICIT-DRUGS-EO14059] (Linked To: JURAIDINI SILVA, Oscar Guillermo).</P>
                    <P>Sanctioned pursuant to section 1(b)(iii) of E.O. 14059 for being owned, controlled, or directed by, or having acted or purported to act for or on behalf of, directly or indirectly, Oscar Guillermo Juraidini Silva, a sanctioned person pursuant to E.O. 14059.</P>
                    <P>Designated pursuant to section 1(a)(iii)(A) of E.O. 13224, as amended, for being owned, controlled, or directed by, or having acted or purported to act for or on behalf of, directly or indirectly, Oscar Guillermo Juraidini Silva, a person whose property and interests in property are blocked pursuant to E.O. 13224, as amended.</P>
                    <P>6. SOMA TRANSPORTE Y SERVICIOS, S.A. DE C.V., Matamoros, Tamaulipas, Mexico; Secondary sanctions risk: section 1(b) of Executive Order 13224, as amended by Executive Order 13886; Organization Established Date 10 Dec 2021; Organization Type: Transportation and storage; Folio Mercantil No. N-2022000577 (Mexico) [SDGT] [ILLICIT-DRUGS-EO14059] (Linked To: JURAIDINI SILVA, Oscar Guillermo).</P>
                    <P>Sanctioned pursuant to section 1(b)(iii) of E.O. 14059 for being owned, controlled, or directed by, or having acted or purported to act for or on behalf of, directly or indirectly, Oscar Guillermo Juraidini Silva, a sanctioned person pursuant to E.O. 14059.</P>
                    <P>Designated pursuant to section 1(a)(iii)(A) of E.O. 13224, as amended, for being owned, controlled, or directed by, or having acted or purported to act for or on behalf of, directly or indirectly, Oscar Guillermo Juraidini Silva, a person whose property and interests in property are blocked pursuant to E.O. 13224, as amended.</P>
                    <P>7. AHAVAT LOGISTICS SOLUTION, S.A. DE C.V., Metepec, Mexico, Mexico; Secondary sanctions risk: section 1(b) of Executive Order 13224, as amended by Executive Order 13886; Organization Established Date 13 Feb 2017; Folio Mercantil No. N-2019037707 (Mexico) [SDGT] [ILLICIT-DRUGS-EO14059] (Linked To: CARTEL DE JALISCO NUEVA GENERACION).</P>
                    <P>Sanctioned pursuant to section 1(b)(i) of E.O. 14059 for having provided, or attempted to provide, financial, material, or technological support of, or goods or services in support of, CJNG, a sanctioned person pursuant to E.O. 14059.</P>
                    <P>Designated pursuant to section 1(a)(iii)(C) of E.O. 13224, as amended, for having materially assisted, sponsored, or provided financial, material, or technological support for, or goods or services to or in support of, CJNG, a person whose property and interests in property are blocked pursuant to E.O. 13224, as amended.</P>
                    <P>
                        8. JOMADI LOGISTICS AND CARGO, S.A. DE C.V. (a.k.a. JOMADI LOGISTICS &amp; CARGO, S.A. DE C.V.; a.k.a. JOMADI LOGISTICS &amp; CARGO, SOCIEDAD 
                        <PRTPAGE P="41173"/>
                        ANONIMA DE CAPITAL VARIABLE), Metepec, Mexico, Mexico; Secondary sanctions risk: section 1(b) of Executive Order 13224, as amended by Executive Order 13886; Organization Established Date 03 May 2012; Folio Mercantil No. 46570 (Mexico) [SDGT] [ILLICIT-DRUGS-EO14059] (Linked To: CARTEL DE JALISCO NUEVA GENERACION).
                    </P>
                    <P>Sanctioned pursuant to section 1(b)(i) of E.O. 14059 for having provided, or attempted to provide, financial, material, or technological support of, or goods or services in support of, CJNG, a sanctioned person pursuant to E.O. 14059.</P>
                    <P>Designated pursuant to section 1(a)(iii)(C) of E.O. 13224, as amended, for having materially assisted, sponsored, or provided financial, material, or technological support for, or goods or services to or in support of, CJNG, a person whose property and interests in property are blocked pursuant to E.O. 13224, as amended.</P>
                    <P>9. OF TRANSPORTES, Matamoros, Tamaulipas, Mexico; Secondary sanctions risk: section 1(b) of Executive Order 13224, as amended by Executive Order 13886; Organization Type: Transportation and storage; R.F.C. JUSO8409010VA (Mexico) [SDGT] [ILLICIT-DRUGS-EO14059] (Linked To: JURAIDINI SILVA, Oscar Guillermo).</P>
                    <P>Sanctioned pursuant to section 1(b)(iii) of E.O. 14059 for being owned, controlled, or directed by, or having acted or purported to act for or on behalf of, directly or indirectly, Oscar Guillermo Juraidini Silva, a sanctioned person pursuant to E.O. 14059.</P>
                    <P>Designated pursuant to section 1(a)(iii)(A) of E.O. 13224, as amended, for being owned, controlled, or directed by, or having acted or purported to act for or on behalf of, directly or indirectly, Oscar Guillermo Juraidini Silva, a person whose property and interests in property are blocked pursuant to E.O. 13224, as amended.</P>
                    <FP>(Authority: E.O. 14059; E.O. 13224, as amended.)</FP>
                </EXTRACT>
                <SIG>
                    <NAME>Bradley T. Smith,</NAME>
                    <TITLE>Director, Office of Foreign Assets Control.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13494 Filed 7-2-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4810-AL-P</BILCOD>
        </NOTICE>
    </NOTICES>
    <VOL>91</VOL>
    <NO>127</NO>
    <DATE>Monday, July 6, 2026</DATE>
    <UNITNAME>Notices</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="41175"/>
            <PARTNO>Part II</PARTNO>
            <AGENCY TYPE="P">Department of Housing and Urban Development</AGENCY>
            <TITLE>Notice of Regulatory Waiver Requests Granted for the Fourth Quarter of Calendar Year 2025</TITLE>
        </PTITLE>
        <NOTICES>
            <NOTICE>
                <PREAMB>
                    <PRTPAGE P="41176"/>
                    <AGENCY TYPE="S">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT</AGENCY>
                    <DEPDOC>[Docket No. FR-6534-N-04]</DEPDOC>
                    <SUBJECT>Notice of Regulatory Waiver Requests Granted for the Fourth Quarter of Calendar Year 2025</SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Office of the General Counsel, HUD.</P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Notice.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>
                            Section 106 of the Department of Housing and Urban Development Reform Act of 1989 (the HUD Reform Act) requires HUD to publish quarterly 
                            <E T="04">Federal Register</E>
                             notices of all regulatory waivers that HUD has approved. Each notice covers the quarterly period since the previous 
                            <E T="04">Federal Register</E>
                             notice. The purpose of this notice is to comply with the requirements of section 106 of the HUD Reform Act. This notice contains a list of regulatory waivers granted by HUD during the period beginning on October 1, 2025, and ending on December 31, 2025.
                        </P>
                    </SUM>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>For general information about this notice, contact Amanda Wahlig, Acting Associate General Counsel for Legislation and Regulations, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, telephone 202-402-3743 (this is not a toll-free number). HUD welcomes and is prepared to receive calls from individuals who are deaf or hard of hearing, as well as individuals with speech and communication disabilities.</P>
                        <P>
                            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>
                        <P>For information concerning a particular waiver that was granted and for which public notice is provided in this document, contact the person whose name and address follow the description of the waiver granted in the accompanying list of waivers that have been granted in the fourth quarter of calendar year 2025.</P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P>Section 106 of the HUD Reform Act added a new section 7(q) to the Department of Housing and Urban Development Act (42 U.S.C. 3535(q)), which provides that:</P>
                    <P>1. Any waiver of a regulation must be in writing and must specify the grounds for approving the waiver;</P>
                    <P>2. Authority to approve a waiver of a regulation may be delegated by the Secretary only to an individual of Assistant Secretary or equivalent rank, and the person to whom authority to waive is delegated must also have authority to issue the particular regulation to be waived;</P>
                    <P>
                        3. Not less than quarterly, the Secretary must notify the public of all waivers of regulations that HUD has approved, by publishing a notice in the 
                        <E T="04">Federal Register</E>
                        . These notices (each covering the period since the most recent previous notification) shall:
                    </P>
                    <P>a. Identify the project, activity, or undertaking involved;</P>
                    <P>b. Describe the nature of the provision waived and the designation of the provision;</P>
                    <P>c. Indicate the name and title of the person who granted the waiver request;</P>
                    <P>d. Describe briefly the grounds for approval of the request; and</P>
                    <P>e. State how additional information about a particular waiver may be obtained.</P>
                    <P>Section 106 of the HUD Reform Act also contains requirements applicable to waivers of HUD handbook provisions that are not relevant to the purpose of this notice.</P>
                    <P>This notice follows procedures provided in HUD's Statement of Policy on Waiver of Regulations and Directives issued on April 22, 1991 (56 FR 16337). In accordance with those procedures and with the requirements of section 106 of the HUD Reform Act, waivers of regulations are granted by the Assistant Secretary with jurisdiction over the regulations for which a waiver was requested. In those cases in which a General Deputy Assistant Secretary granted the waiver, the General Deputy Assistant Secretary was serving in the absence of the Assistant Secretary in accordance with the office's Order of Succession.</P>
                    <P>This notice covers waivers of regulations granted by HUD from October 1, 2025 through December 31, 2025. For ease of reference, the waivers granted by HUD are listed by HUD program office (for example, the Office of Community Planning and Development, the Office of Fair Housing and Equal Opportunity, the Office of Housing, and the Office of Public and Indian Housing, etc.). Within each program office grouping, the waivers are listed sequentially by the regulatory section of title 24 of the Code of Federal Regulations (CFR) that is being waived. For example, a waiver of a provision in 24 CFR part 58 would be listed before a waiver of a provision in 24 CFR part 570.</P>
                    <P>Where more than one regulatory provision is involved in the grant of a particular waiver request, the action is listed under the section number of the first regulatory requirement that appears in 24 CFR and that is being waived. For example, a waiver of both § 58.73 and § 58.74 would appear sequentially in the listing under § 58.73.</P>
                    <P>Waiver of regulations that involve the same initial regulatory citation are in time sequence beginning with the earliest-dated regulatory waiver.</P>
                    <P>Should HUD receive additional information about waivers granted during the period covered by this report (the fourth quarter of calendar year 2025) before the next report is published (the first quarter of calendar year 2026), HUD will include any additional waivers granted for the fourth quarter in the next report.</P>
                    <P>Accordingly, information about approved waiver requests pertaining to HUD regulations is provided in the Appendix that follows this notice.</P>
                    <SIG>
                        <NAME>David C. Woll,</NAME>
                        <TITLE>General Counsel.</TITLE>
                    </SIG>
                    <HD SOURCE="HD1">APPENDIX</HD>
                    <HD SOURCE="HD1">Listing of Waivers of Regulatory Requirements Granted by Offices of the Department of Housing and Urban Development October 1, 2025 through December 31, 2025</HD>
                    <NOTE>
                        <HD SOURCE="HED">Note to Reader:</HD>
                        <P>More information about the granting of these waivers, including a copy of the waiver request and approval, may be obtained by contacting the person whose name is listed as the contact person directly after each set of regulatory waivers granted.</P>
                    </NOTE>
                    <P>The regulatory waivers granted appear in the following order:</P>
                    <FP SOURCE="FP-2">I. Regulatory waivers granted by the Office of Community Planning and Development</FP>
                    <FP SOURCE="FP-2">II. Regulatory waivers granted by the Office of Housing</FP>
                    <FP SOURCE="FP-2">III. Regulatory waivers granted by the Office of Public and Indian Housing</FP>
                    <HD SOURCE="HD1">I. Regulatory Waivers Granted by the Office of Community Planning and Development</HD>
                    <P>For further information about the following regulatory waivers, please see the name of the contact person that immediately follows the description of the waiver granted.</P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 92.300(a)(3).
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         The City of Santa Rosa, California requested a waiver of 24 CFR 92.300(a)(3) to permit a community housing development organization (CHDO) to transfer ownership of a HOME Investment Partnerships Program (HOME)-assisted rental project, Benton Veterans Village, to a nonprofit that will preserve the affordable housing for the remainder of the period of affordability.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         The HOME regulation at 24 CFR 92.300(a)(3) 
                        <PRTPAGE P="41177"/>
                        requires that rental housing developed with CHDO set-aside funds under 24 CFR 92.300(a) must be owned by the CHDO for a period at least equal to the period of affordability in 24 CFR 92.252.
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Bryan W. Horn, Acting Principal Deputy Assistant Secretary for Community Planning and Development.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 2, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         The City provided Community Housing Sonoma County (CHSC) with HOME CHDO set-aside funds for the development of Benton Veterans Village, a rental project for homeless veterans with seven HOME-assisted units. The project was completed in 2019 and has a period of affordability of 20 years. CHSC experienced financial hardship and no longer had the capacity to maintain the project for the remainder of the period of affordability. The City was not able to identify another eligible CHDO to assume ownership. To preserve the affordable units and avoid the repayment of HOME funds, the Department granted the waiver to permit the transfer of the Benton Veterans Village project to PEP Housing, a nonprofit with the capacity to own and operate the project in accordance with the HOME requirements for the duration of the HOME period of affordability. As a condition of the waiver, PEP Housing must assume the HOME written agreement and the City and PEP Housing must record amended deed restrictions in compliance with 24 CFR 92.252 for the remainder of the HOME period of affordability.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Peter Huber, Acting Director, Office of Affordable Housing Programs, Office of Community and Planning Development, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">peter.h.huber@hud.gov,</E>
                         telephone (202) 402-3941.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 570.200(a)(3), as modified by the 
                        <E T="04">Federal Register</E>
                         Notice published at 88 FR 32046 on May 18, 2023.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Community Development Block Grant Disaster Recovery (CDBG-DR) funds allocated to Lee County, Florida, pursuant to Public Law 117-328 (providing CDBG-DR funding for major disasters occurring in 2022), and subject to the requirements published in 88 FR 32046 (May 18, 2023), as modified by Memorandum 25-04 (May 7, 2025) (collectively, the “Prior Notices”). This waiver and alternative requirement apply to Lee County's infrastructure projects in which the service area contains less than 51 percent low- and moderate-income (LMI) residents.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         The Prior Notices, along with 24 CFR 570.200(a)(3), require grantees to meet the overall benefit requirement by ensuring that at least 70 percent of CDBG-DR funds benefit low- and moderate-income (LMI) persons. For infrastructure projects using the low- and moderate-income area (LMA) benefit national objective, the Prior Notices require that LMI residents comprise at least 51 percent of the project's service area.
                    </P>
                    <P>In response to a request from Lee County, this waiver and alternative requirement (1) permit the County to count proportional infrastructure costs toward meeting the LMI overall benefit threshold in service areas with less than 51 percent LMI residents, and (2) allow the County to multiply the total cost of an activity by the percentage of LMI persons in the service area, provided that the amount counted does not exceed the CDBG-DR funds invested. This flexibility enables the County to implement large-scale infrastructure projects, better reflect the benefits to LMI residents, and maintain compliance with the 70 percent overall benefit requirement for its 2022 CDBG-DR grant, while supporting critical disaster recovery and mitigation efforts.</P>
                    <P>
                        <E T="03">Granted By:</E>
                         Bryan W. Horn, Acting Principal Deputy Assistant Secretary for Community Planning and Development.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 8, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         Lee County demonstrated good cause that large-scale infrastructure projects funded under its 2022 CDBG-DR allocation provide significant benefits to mixed-income populations, including the County's LMI residents, but the County would face constraints on advancing its infrastructure projects that do not meet the LMA national objective. Without the requested waiver, the County would be unable to implement these critical activities and meet the 70 percent overall LMI benefit requirement, given that a substantial portion of its allocation is dedicated to addressing its significant infrastructure needs. HUD determined that the waiver and alternative requirement is not inconsistent with the overall purposes of Title I of the HCDA and will allow Lee County to calculate proportional LMI benefit for infrastructure activities by multiplying total project costs by the percentage of LMI persons in the service area, not to exceed the amount of CDBG-DR funds invested. This waiver and alternative requirement are applicable solely to the 2022 CDBG-DR funds awarded to Lee County under Public Law 117-328. It allows the County to calculate proportional LMI benefit for infrastructure projects in service areas with less than 51 percent LMI residents, for purposes of meeting the 70 percent overall LMI benefit requirement. The waiver and alternative requirement are effective as of December 8, 2025, and remain in effect for the duration of the County's 2022 CDBG-DR grant.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Gerilee W. Bennett, Acting Director, Office of Disaster Recovery, Office of Community Planning and Development, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">gerilee.w.bennett@hud.gov,</E>
                         telephone (202) 708-3587.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 570.200(a)(3), as modified by the 
                        <E T="04">Federal Register</E>
                         notice published at 88 FR 32046 on May 18, 2023.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Community Development Block Grant Disaster Recovery (CDBG-DR) funds allocated to Volusia County, Florida, pursuant to Public Law 117-328 (providing CDBG-DR funding for major disasters occurring in 2022), and subject to the requirements published in 88 FR 32046 (May 18, 2023), as modified by Memorandum 24-02 (August 8, 2024) and Memorandum 25-05 (May 23, 2025) (collectively, the “Prior Notices”). This waiver and alternative requirement apply to Volusia County's infrastructure projects in which the service area contains less than 51 percent low- and moderate-income (LMI) residents.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         The Prior Notices, along with 24 CFR 570.200(a)(3), require grantees to meet the overall benefit requirement by ensuring that at least 70 percent of CDBG-DR funds benefit low- and moderate-income (LMI) persons. For infrastructure projects using the low- and moderate-income area (LMA) benefit national objective, the Prior Notices require that LMI residents comprise at least 51 percent of the project's service area.
                    </P>
                    <P>
                        In response to a request from Volusia County, this waiver and alternative requirement (1) permits the County to count proportional infrastructure costs toward meeting the LMI overall benefit threshold in service areas with less than 51 percent LMI residents, and (2) allows the County to multiply the total cost of an activity by the percentage of LMI persons in the service area, provided that the amount counted does not exceed the CDBG-DR funds invested. This flexibility enables the County to implement large-scale infrastructure projects, better reflect the benefits to LMI residents, and maintain compliance with the 70 percent overall benefit 
                        <PRTPAGE P="41178"/>
                        requirement for its 2022 CDBG-DR grant, while supporting critical disaster recovery and mitigation efforts.
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Bryan W. Horn, Acting Principal Deputy Assistant Secretary for Community Planning and Development.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 28, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         Volusia County demonstrated good cause that large-scale infrastructure projects funded under its 2022 CDBG-DR allocation provide significant benefits to LMI persons, but due to broad service areas, the percentage of LMI residents falls below the 51 percent threshold required for the LMA national objective. Volusia County also requested this waiver and alternative requirement to align their infrastructure recovery program for Hurricane Ian (subject to the requirements of the Consolidated Notice and the basis for this waiver) with their infrastructure recovery program for Hurricane Milton (subject to the requirements of the Universal Notice). Without the requested waiver, the County would be unable to carry out these critical activities, meet the 70 percent overall LMI benefit requirement, and would face the added administrative burden of managing two concurrent infrastructure recovery programs with differing grant requirements. HUD determined that the waiver and alternative requirement is not inconsistent with the overall purposes of Title I of the HCDA and will allow Volusia County to calculate proportional LMI benefit for infrastructure activities by multiplying total project costs by the percentage of LMI persons in the service area, not to exceed the amount of CDBG-DR funds invested. This waiver and alternative requirement are applicable solely to the 2022 CDBG-DR funds awarded to Volusia County under Public Law 117-328. It allows the County to calculate proportional LMI benefit for infrastructure projects in service areas with less than 51 percent LMI residents, for purposes of meeting the 70 percent overall LMI benefit requirement. The waiver and alternative requirement are effective as of December 28, 2025, and remain in effect for the duration of the County's 2022 CDBG-DR grant.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Gerilee W. Bennett, Acting Director, Office of Disaster Recovery, Office of Community Planning and Development, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">gerilee.w.bennett@hud.gov,</E>
                         telephone (202) 708-3587.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         Section 102(a)(20)(A) and Section 105(c)(2)(A) of the Housing and Community Development Act of 1974 (42 U.S.C. 5302(a)(20)(A) and 42 U.S.C. 5305(c)(2)(A)).
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Community Development Block Grant Disaster Recovery (CDBG-DR) funds allocated to the State of Texas pursuant to Public Law 117-43 and Public Law 117-180 (for disasters occurring in 2021), and Public Law 118-158 (for disasters occurring in 2024), and subject to the requirements published in 87 FR 31636 (May 24, 2022), 88 FR 3198 (January 18, 2023), and Memorandum 22-01 (December 7, 2022) for the 2021 disasters, and 90 FR 4759 (January 16, 2025), 90 FR 1754 (January 8, 2025), Memorandum 2025-02 (March 19, 2025), and Memorandum 25-03 (March 31, 2025) for the 2024 disasters (collectively, the “Prior Notices”).
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         The State requested that HUD use its authority under 42 U.S.C. 5302(a)(20)(B) to establish alternative percentages of median income for areas when the Secretary determines such adjustments are necessary due to unusually high or low family incomes in those areas, rather than strictly applying the percentages set forth in 42 U.S.C. 5302(a)(20)(A). Pursuant to this request, HUD may grant a waiver to use state AMI as the minimum for disaster-impacted counties with an Area Median Income (AMI) below the state level, while maintaining county-level AMI for counties above the state level (as published by HUD).
                    </P>
                    <P>The State also requested a waiver from HUD to apply exception criteria in non-entitlement counties to determine that an activity qualifies as meeting the national objective of low- and moderate- income (LMI) area benefit based on the “upper quartile” data methodology outlined in 24 CFR 570.208(a)(1)(ii), when the area contains fewer than 51 percent of LMI persons. Section 105(c)(2)(A) of the Housing and Community Development Act (HCDA) allows for this exception when “the area served by such activity is within the highest quartile of all areas within the jurisdiction of such city or county in terms of the degree of concentration of persons of low and moderate income.” The State requested this waiver and alternative requirement for only those non-entitlement counties in which fewer than one quarter of the block groups within their jurisdiction have 51 percent or more LMI residents.</P>
                    <P>
                        <E T="03">Granted By:</E>
                         Bryan W. Horn, Acting Principal Deputy Assistant Secretary for Community Planning and Development.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 8, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         The State of Texas demonstrated good cause to set the minimum AMI requirement to the state's annual AMI in disaster-impacted counties that have an AMI below the statewide AMI. The State also demonstrated good cause to apply exception criteria in non-entitlement counties in which fewer than one quarter of the block groups within their jurisdiction have 51 percent or more LMI residents. Approving this waiver and alternative requirement will also allow the State to coordinate recovery efforts across their grant portfolio, as the standardized annual median income waiver and upper quartile exception criteria waiver was already approved for previous CDBG-DR and CDBG-Mitigation Funds allocations in the State of Texas, as published in 85 FR 60821 on September 28, 2020. This waiver and alternative requirement are applicable solely to CDBG-DR funds awarded to the State of Texas, for disasters occurring in 2021 under Public Law 117-43 and P.L. 117-180 and disasters occurring in 2024 under Public Law 118-158. The waiver and alternative requirement are effective as of December 8, 2025, and remain in effect for the duration of the State's 2021 and 2024 CDBG-DR grants.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Gerilee W. Bennett, Acting Director, Office of Disaster Recovery, Office of Community Planning and Development, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314 email: 
                        <E T="03">gerilee.w.bennett@hud.gov,</E>
                         telephone (202) 708-3587.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         Section III.A.1.a.(6)(d) of the Consolidated Notice (Appendix B to HUD's Community Development Block Grant Disaster Recovery (CDBG-DR) notices published in the 
                        <E T="04">Federal Register</E>
                         on May 18, 2023, at 88 FR 32046 (the “May 2023 Notice”).
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Community Development Block Grant Disaster Recovery (CDBG-DR) funds allocated to St. Louis County, Missouri, pursuant to Public Law 117-180 (providing CDBG-DR funding for major disasters occurring in 2021 or 2022), and subject to the requirements published in 88 FR 32046 (May 18, 2023). This waiver and alternative requirement applies to the internal auditor requirements at section III.A.1.a.(6)(d) of the Consolidated Notice, as set forth in Appendix B and amended by the May 2023 Notice, under which grantees must demonstrate they have an internal auditor responsible for both programmatic and financial oversight and have adopted policies outlining the auditor's role in detecting fraud, waste, and abuse. This waiver allows St. Louis County to not hire an internal auditor.
                        <PRTPAGE P="41179"/>
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         HUD allocated CDBG-DR funds to St. Louis County, Missouri under the May 18, 2023, Notice (88 FR 32046). This notice requires grantees to demonstrate they have an internal auditor responsible for both programmatic and financial oversight, and that the grantee has adopted policies outlining the auditor's role in detecting fraud, waste, and abuse.
                    </P>
                    <P>
                        In response to a request from St. Louis County, this waiver and alternative requirement (1) allows the County to apply the requirements established at section II.A.1.d.(iv). in the notice titled, 
                        <E T="03">Common Application, Waivers, and Alternative Requirements for Community Development Block Grant Disaster Recovery Grantees: The Universal Notice</E>
                         (the “Universal Notice”) (published at 90 FR 1754 on January 8, 2025, as amended) which requires only grants of $100 million or more to have or plan to employ an internal auditor, in lieu of the corresponding provisions in the May 2023 Notice and the Consolidated Notice, and (2) reminds the grantee that they must have adequate procedures in place to detect fraud, waste, and abuse. Additionally, the County must continue providing ongoing oversight and monitoring of subrecipients or developers, as applicable, to ensure compliance with all CDBG-DR requirements.
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Bryan W. Horn, Acting Principal Deputy Assistant Secretary for Community Planning and Development.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 8, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         St. Louis County, Missouri demonstrated good cause that appointing a county auditor would conserve financial resources, reduce administrative burden, and streamline recovery efforts. Without the requested waiver, the County would have to hire an internal auditor. HUD determined that the waiver and alternative requirement are not inconsistent with the overall purposes of Title I of the HCDA and will allow St. Louis County to appoint a county auditor that will be responsible for programmatic and financial oversight. This waiver and alternative requirement are applicable solely to the 2022 CDBG-DR funds awarded to St. Louis County, Missouri, under Public Law 117-180. The waiver and alternative requirement are effective as of December 8, 2025, and remain in effect for the duration of the County's 2022 CDBG-DR grant.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Gerilee W. Bennett, Acting Director, Office of Disaster Recovery, Office of Community Planning and Development, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">gerilee.w.bennett@hud.gov,</E>
                         telephone (202) 708-3587.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 576.203(b).
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         HUD granted a waiver of 24 CFR 576.203(b) to the State of Hawaii, extending the expenditure deadline for its Rapid Unsheltered Supportive Housing (RUSH) grant (E-24-DW-15-0001). The waiver permitted the State to continue expending funds for an additional month until December 31, 2025. HUD required the State to submit a spending plan on or before December 31, 2025, indicating that a full year extension would be considered based on HUD's review of the plan.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 576.203(b) provides that the recipient must draw down and expend funds from each year's grant not less than once during each quarter of the recipient's program year. All of the recipient's grant must be expended for eligible activity costs within 24 months after the date HUD signs the grant agreement with the recipient. For the purposes of this requirement, expenditure means either an actual cash disbursement for a direct charge for a good or service or an indirect cost; or the accrual of a direct charge for a good or service or an indirect cost.
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Bryan W. Horn, Acting Principal Deputy Assistant Secretary for Community Planning and Development.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         RUSH is intended to enable timely, local assistance by providing immediate funding to States or local governments capable of acting quickly to meet the unmet homeless assistance and homeless prevention needs in declared disaster areas. The Department's expenditure limit at 24 CFR 576.203(b) serves dually as a safeguard and benchmark for the expedient deployment of much needed funding to assist disaster survivors who are experiencing homelessness or at risk of experiencing homelessness and whose needs are not served or fully met by existing Federal disaster relief programs. In some cases, though, limiting recipients' use of RUSH funding within the 24-month expenditure period can impede, rather than promote, the efficient use of RUSH assistance.
                    </P>
                    <P>In this case, the State provided information showing that the 24-month period of performance ending on November 23, 2025, will cause undue hardship, negatively impacting the State's efforts to recover from the Maui Wildfires (DR-4724-HI). The State reports that its implementation timelines were compressed, particularly given the need to develop a new Policies and Procedures Manual, establish a prioritization framework for Coordinated Entry specific to RUSH, and initiate agreements with service providers. These preliminary steps were needed to ramp up the State's RUSH Program, accounting for the specialized use of this disaster funding and its differences from the State's ESG Program.</P>
                    <P>The State encountered additional challenges with the timing of RUSH expenditures in an effort to meet the local needs for rapid re-housing (RRH) and homelessness prevention (HP) assistance. Although funding for these component types takes longer to expend than other eligible activities, the State committed the majority of its RUSH funding to RRH and HP to best address the needs in areas affected by the wildfires. The State further explained that, while these strategies were identified as the most effective approach to reducing and preventing homelessness in disaster impacted communities, their complexity and limited implementation precedent posed additional challenges for timely execution of provider agreements. Finally, the infusion of other disaster response assistance during the first two years following the Maui Wildfires caused additional delays in the expenditure of RUSH funds due to the eligibility restriction limiting assistance to those whose needs are not served or fully met by existing Federal disaster relief programs. However, the State anticipates an increased demand for RUSH assistance and an increase in expenditures now that many of the federal disaster relief programs are beginning to phase out.</P>
                    <P>Due to these factors, the 24-month expenditure deadline would negatively impact the State in its ability to strategically use RUSH funding to meet the needs of those impacted by the Maui Wildfires. Requiring that expenditures for rental assistance be terminated at the current period of performance end date of November 23, 2025, will likely result in program participants returning to homeless situations in a community still recovering from the natural disaster.</P>
                    <P>
                        <E T="03">Contact:</E>
                         Norm Suchar, Director, Office of Special Needs Assistance Programs, Office of Community Planning and Development, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Norman.A.Suchar@hud.gov,</E>
                         telephone number (202) 708-4300.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 55.20(e)(1)(ii)(B).
                        <PRTPAGE P="41180"/>
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Sunflower Flats is a transfer and Rental Assistance Demonstration (RAD) program conversion in Manhattan, Kansas, sponsored by Oikos Development Corporation, a not-for-profit 501(c)(3) organization. The proposal includes a Housing Assistance Payments (HAP) contract transfer under the Section 8(bb) program and a RAD conversion to Project Rental Assistance Contracts (PRAC). The project involves new construction of one five-story residential building comprising a total of 62 units for senior households aged 62 and older; however, a waiver allows occupancy by seniors aged 55 and older who are individuals with disabilities. The development is intended to relocate tenants from the existing Garden Grove I and II Apartments, located at 1119 and 1115 Garden Way in Manhattan, Kansas, due to elevated flood risk at those sites. The proposed residential units located within the floodplain will be elevated above the FFRMS floodplain elevation; however, non-residential spaces may be located below the FFRMS floodplain elevation.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         New construction and substantial improvements of residential structures that are not critical actions, as defined at 24 CFR 55.2(b)(3), must be constructed with no dwelling units below the FFRMS floodplain and with all other spaces either elevated above the FFRMS floodplain or floodproofed, in accordance with FEMA regulations at 44 CFR 60.3(c)(3)(ii) and (c)(4)(i), or any subsequent standards issued by FEMA, at least to the elevation of the FFRMS floodplain.
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Bryan W. Horn, Principal Deputy Assistant Secretary for Community Planning and Development.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 4, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         Good cause for Sunflower Flats was determined based on the limited flood risk at the proposed project site, the flood risk minimization measures already incorporated into the project design, and the importance of the proposed Section 8(bb) transfer in advancing program goals. The site is located within Zone X (Area with Reduced Flood Risk Due to Levee) and the 0.2 percent annual chance floodplain, according to the effective Flood Insurance Rate Map (FIRM). The levee system, constructed in 1962, together with flood protection provided by a series of U.S. Army Corps of Engineers (USACE)-operated reservoirs on the Kansas River, significantly reduces flood risk relative to conditions that existed during the last major flood event in 1951. Since construction of the levee system, Manhattan has not experienced river flood damage within the downtown area. HUD's regulations at 24 CFR part 55, as updated in April 2024, do not specifically address Zone X (Levee) areas in the instructions for identifying the applicable floodplain. Multifamily has determined that a waiver of elevation and floodproofing requirements at this site is justified because current regulations and guidance would categorize a site closer to the river and at a lower elevation as sufficiently protected by the Kansas River levee. Notably, the Manhattan Levee is designed to provide protection from flooding on the Kansas River and the Big Blue River up to the 1-in-300 annual chance risk level. The proposed building is designed with all residential units located on the second floor and above, placing dwelling units above the 500-year flood elevation. Sunflower Flats presents a substantially lower flood risk than the existing Garden Grove Apartments, which is located within a Special Flood Hazard Area. The transfer of assistance will occur from Garden Grove Apartments to Sunflower Flats.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Lauren Hayes Knutson, Senior Policy Advisor, Office of Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, telephone (202) 402-4270.
                    </P>
                    <HD SOURCE="HD1">II. Regulatory Waivers Granted by the Office of Housing</HD>
                    <P>For further information about the following regulatory waivers, please see the name of the contact person that immediately follows the description of the waiver granted.</P>
                    <P>
                        <E T="03">Regulation:</E>
                         24 CFR 891.120(a).
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         South Oak Manor is an 82-unit, nonprofit-owned, high-rise property in North Platte, Nebraska, designed to serve elderly families. Originally developed under the Section 202/8 program, it is insured through HUD's 223(f) program, with a Section 202/8 Housing Assistance Payment (HAP) contract covering all units.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         Projects containing 20 units of housing for the elderly, Housing Handbook 4910.1 requires the installation of an emergency call system in each bathroom and one bedroom. The referenced Handbook applies through cross-reference in 24 CFR 891.120 to HUD's Minimum Property Standards in 24 CFR part 200, subpart S, which incorporate by reference the 1994 edition of Handbook 4910.1.
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Frank Cassidy, Principal Deputy Assistant Secretary for Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 18, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         Projects containing 20 or more units, the referenced Handbook requires the installation of an emergency call system in each bathroom and one bedroom. South Oak Manor is a 202/8 Direct Loan project that prepaid and completed the term of its Use Agreement. Although the project remains subject to 24 CFR part 891 under the terms of its Housing Assistance Payments contract, ongoing programmatic requirements relate only to the Section 8 Project-Based Rental Assistance program. Given that HUD found good cause to waive the elderly age restriction to draw working families in need of affordable housing to North Platte, HUD also found good cause to waive the emergency call system requirements applicable to housing for the elderly projects with 20 or more units. 
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer Larson, Director, Office of Asset Management, Office of Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, telephone (202) 402-7769.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 891.505.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         South Oak Manor is an 82-unit, nonprofit-owned, high-rise property in North Platte, Nebraska, designed to serve elderly families. Originally developed under the Section 202/8 program, it is insured through HUD's 223(f) program, with a Section 202/8 Housing Assistance Payment (HAP) contract covering all units.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         Specifies that the Borrower (
                        <E T="03">i.e.,</E>
                         Owner) must be a “private nonprofit corporation or a nonprofit consumer cooperative”.
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Frank Cassidy, Principal Deputy Assistant Secretary for Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 18, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         specifies that the Borrower (
                        <E T="03">i.e.,</E>
                         Owner) must be a “private nonprofit corporation or a nonprofit consumer cooperative.” South Oak Manor is a 202/8 Direct Loan project that prepaid and completed the term of its Use Agreement. Although the project remains subject to 24 CFR part 891 under the terms of its Housing Assistance Payments contract, ongoing programmatic requirements relate only to the Section 8 Project-Based Rental Assistance (PBRA) program. Given that the Section 8 PBRA program permits other ownership types, and based on the lack of prospective not-for-profit buyers and the need for the property to come under experienced ownership to avoid further financial and physical decline, HUD found good cause to waive the private nonprofit ownership requirements that apply to 202 Direct Loan projects.
                        <PRTPAGE P="41181"/>
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer Larson, Director, Office of Asset Management, Office of Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">jennifer.larson@hud.gov,</E>
                         telephone (202) 402-7769.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 891.520 and 24 CFR 5.403.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         South Oak Manor is an 82-unit, nonprofit-owned, high-rise property in North Platte, Nebraska, designed to serve elderly families. Originally developed under the Section 202/8 program, it is insured through HUD's 223(f) program, with a Section 202/8 Housing Assistance Payment (HAP) contract covering all units.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         Restrict occupancy to elderly families, defined as families where the head (including co-head), spouse, or sole member is a person who is at least 62 years of age.
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Frank Cassidy, Principal Deputy Assistant Secretary for Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 18, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         24 CFR 891.520 and 24 CFR 5.403—restrict occupancy to elderly families, defined as families where the head (including co-head), spouse, or sole member is a person who is at least 62 years of age. A new meatpacking plant is expected to draw working families in need of affordable housing to North Platte. South Oak Manor is a 202/8 Direct Loan project that prepaid and completed the term of its Use Agreement. Although the project remains subject to 24 CFR part 891 under the terms of its Housing Assistance Payments contract, ongoing programmatic requirements relate only to the Section 8 Project-Based Rental Assistance (PBRA) program. Given that Section 8 PBRA has a broader definition of “family,” and considering South Oak Manor's struggles to fill units and this anticipated demand for such units, HUD found good cause to waive the elderly restriction applicable to 202 Direct Loan Projects.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer Larson, Director, Office of Asset Management, Office of Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">jennifer.larson@hud.gov,</E>
                         telephone (202) 402-7769.
                    </P>
                    <HD SOURCE="HD1">III. Regulatory Waivers Granted by the Office of Public and Indian Housing</HD>
                    <P>For further information about the following regulatory waivers, please see the name of the contact person that immediately follows the description of the waiver granted.</P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 983.3.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 983.3 provides that a project can be a single building, multiple contiguous buildings, or multiple buildings on contiguous parcels of land, in which “contiguous” in this definition includes “adjacent to,” as well as touching along a boundary or a point.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         New York City Housing Authority (NYCHA) Jackie Robinson Houses and Harlem Scattered Sites.
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 5, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waivers on the basis of good cause, citing that NYCHA is particularly impacted by the application of the regulatory definition of “project” as applied to the sites and through this waiver request seeks to provide continuity by maintaining the current management and administration structure of these projects under the public housing program to the greatest extent feasible. Additionally, the consolidations have the potential to directly benefit residents (
                        <E T="03">e.g.,</E>
                         help facilitate and expedite transfers between buildings under the same Rental Assistance Demonstration-Project-Based Voucher (RAD-PBV) Housing Assistance Program (HAP) contract, noting the urgency of such transfer requests). Furthermore, the administrative efficiencies resulting from consolidating the RAD-PBV HAP contracts in the manner NYCHA has proposed for Redevelopment will significantly reduce the administrative burden on NYCHA staff, allowing more staff time to address the needs and concerns of residents.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Kristin Baugh, Portfolio Management Specialist, Office of Public Housing Voucher Programs, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">kristin.m.baugh@hud.gov,</E>
                         telephone (913) 551-5573.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 983.3.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 983.3 provides that a project can be a single building, multiple contiguous buildings, or multiple buildings on contiguous parcels of land, in which “contiguous” in this definition includes “adjacent to,” as well as touching along a boundary or a point.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         New York City Housing Authority (NYCHA) Ocean Hill-Stuyvesant Gardens.
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 5, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waivers on the basis of good cause, citing that NYCHA is particularly impacted by the application of the regulatory definition of “project” as applied to the sites and through this waiver request seeks to provide continuity by maintaining the current management and administration structure of these projects under the public housing program to the greatest extent feasible. Additionally, the consolidations have the potential to directly benefit residents (
                        <E T="03">e.g.</E>
                         help facilitate and expedite transfers between buildings under the same Rental Assistance Demonstration-Project-Based Voucher (RAD-PBV) Housing Assistance Program (HAP) contract, noting the urgency of such transfer requests). Furthermore, the administrative efficiencies resulting from consolidating the RAD-PBV HAP contracts in the manner NYCHA has proposed that Redevelopment will significantly reduce the administrative burden on NYCHA staff, allowing more staff time to address the needs and concerns of residents
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Kristin Baugh, Portfolio Management Specialist, Office of Public Housing Voucher Programs, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, telephone (913) 551-5573.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening of waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         City of Phoenix Housing Department.
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that the Housing Department has over 300 Emergency Housing Voucher (EHV) families. It is unlikely that the Housing Department would be able to effectively and efficiently provide correspondence to all EHV families to inform them that as a result of the EHV program sunsetting in 2026, they must apply for the HCV program and submit applications in order to be put on the waiting list. Without this waiver, EHV families could possibly lose assistance if they do not successfully apply to the Housing Choice Voucher (HCV) program. In addition, the Housing Department currently has the capacity and funding available in its HCV program for 2025 to successfully transition a large portion of EHV 
                        <PRTPAGE P="41182"/>
                        families into the HCV program. With funding for 2026 currently unknown, the more EHV families that can be transitioned into the HCV program in 2025, the better for the PHA and the EHV families. It also significantly reduces the chances of an EHV family being terminated due to the exhaustion of EHV funding in 2026.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         County of Sacramento Housing Authority (CSHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that CSHA currently is in shortfall and has about 460 active Emergency Housing Voucher (EHV) participants (representing 962 individuals, of which 398 are children). CSHA staff is unable to do the necessary individual outreach and follow up to ensure that each family, including those that have ported out, is informed of their opportunity to be placed on the waiting list and is able to submit an application. It is likely that all EHV families would lose the opportunity to apply for future assistance without this high level of support. A phased approach to converting families from EHV to the Housing Choice Voucher program, as vouchers become available, is necessary. When vouchers become available, the first priority should be to preserve the housing for homeless families currently housed and this waiver would help to make that happen.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Community Development Commission of Mendocino County (CDC).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that CDC currently serves a large volume of Emergency Housing Voucher (EHV) families. Without this waiver, requiring each family to complete a new Housing Choice Voucher application would overwhelm staff, detracting from core responsibilities such as inspections, reexaminations, and ongoing case management. The delay from requiring individual applications would also put families at risk of losing assistance. EHV families face barriers to completing the application process, such as limited internet access and mobility issues, which increases the likelihood that families may unintentionally lose rental assistance due to being unable to complete the application process.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Catalyst.
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that Housing Catalyst completed an Emergency Housing Voucher (EHV) Transition Impact Analysis and Outreach Summary, which found that the large number of families served under their EHV program makes individualized application processing logistically unfeasible within the limited timeframe, given their limited administrative capacity. Due to the time required to conduct individualized outreach, assist families with application completion and verify receipt, EHV families would be at risk of losing housing assistance before the transition can occur. Access to means of reliable resources are limited for some of their EHV families, some are without transportation, phone or email service. Geographic dispersion and rural areas add further barriers, making in-person outreach and support more time and resource intensive. These factors place EHV families at imminent risk of housing instability.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of the City of Daytona Beach (HACDB).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HACDB would like to request this waiver to expedite the process for the families we serve that may have limited access to technology and to eliminate the risk of families that may miss the opportunity to complete the online application. HACDB recently opened our public housing waiting list and received over 3000 applications in a period of 30 days. Our agency would have to send out denial letters to any applicant that applies during the time the waiting list is opened. This waiver will reduce the administrative burden of removing families that are not eligible to apply to the Housing Choice Voucher waiting list.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                        <PRTPAGE P="41183"/>
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         City of Pensacola Housing (CPH).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that requiring individual applications for Emergency Housing Voucher (EHV) participants to be placed on the Housing Choice Voucher (HCV) waiting list can create confusion and anxiety among vulnerable families and could result in EHV participants losing their housing assistance when the program ends. The complex application process may deter or delay some EHV families from completing the steps required to join the HCV waiting list, potentially leading to evictions and a return to homelessness or housing instability. Were this to occur, it would likely discourage property owners from participating in the HCV program and have a negative impact on the availability of affordable housing locally. Providing automatic placement with an EHV preference eliminates unnecessary steps, simplifies the transition, and ensures a clearer path to continue housing assistance for these families.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Augusta Housing Authority (AHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that Emergency Housing Voucher (EHV) families would be at risk of losing assistance due to the exhaustion of EHV funds if they had to go through the application process in order to be added to the Housing Choice Voucher (HCV) waiting list. Also, it is unlikely that the AHA would be able to do the necessary outreach and follow up to ensure that each family is informed of their opportunity to submit an application and be placed on the HCV waiting list, which would put families at risk of losing assistance.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of DeKalb County (HADC).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HADC is requesting a waiver in order to avoid putting families at risk of losing housing assistance, which the delay from requiring individual applications would cause. Due to the large number (96) of Emergency Housing Voucher (EHV) families that HADC serves, it is unlikely staff will have the capacity to do the necessary outreach and follow-up required to ensure that each family is informed and able to apply, jeopardizing their assistance. If HADC is not granted this waiver, it is very likely that EHV families will lose their housing.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Boise City Housing Authority (BCHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that BCHA currently has sufficient Housing Choice Voucher funding to absorb their Emergency Housing Voucher (EHV) families, however the ability to utilize this funding would be jeopardized were a waiver not granted. BCHA would experience an administrative burden, given that staff would need to conduct extensive individual outreach, collect and process separate applications from each household, and manually enter each applicant into the waiting list with the appropriate preference. For applicants, the individual application requirements introduce unnecessary barriers, particularly for vulnerable households who may face challenges with technology, paperwork or timely response. The extended processing timelines could significantly delay transitions, potentially resulting in eligible families missing the opportunity to apply under the preference, placing their housing stability at risk. This waiver would allow BCHA to act quickly to preserve housing stability for current EHV families while ensuring program efficiency and equity.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of Elgin (HAE).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that many of the current Emergency Housing Voucher (EHV) participants came to HAE under a Continuum of Care with connected agencies, many of whom had assistance completing the applications, verifications for income, 
                        <PRTPAGE P="41184"/>
                        and banking information. It is crucial for HAE to be able to manually add the EHV currently assisted families onto the Housing Choice Voucher (HCV) waitlist because it eliminates the potential confusion required of these households—many of whom face barriers such as disability, limited access to technology, or trauma—to reapply under standard HCV application procedures. Without the ability to automatically transfer the currently assisted EHV voucher residents to the current HCV waitlist, there is a severely heightened risk of housing loss once EHV assistance ends and significant administrative and operational burdens on HAE staff.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Johnson County Housing Authority (JCHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that JCHA would like to add the remaining 32 Emergency Housing Voucher (EHV) families to the regular Housing Choice Voucher waiting list because of the difficulty involved in contacting the families and the administrative burden on staff. As former homeless individuals and families, any additional requirements could potentially place their long-term stability in jeopardy. JCHA has added a local preference for EHV families to our draft 2026 Admin Plan changes for adoption on January 1, 2026. This waiver will prevent the EHV families from unintentionally losing their assistance.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Jefferson Parish Housing Services Development District (JPHSDD).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that JPHSDD currently has 41 families enrolled in Emergency Housing Vouchers (EHVs). Due to this large number of families and our limited staff, it will be difficult for us to do the necessary outreach and follow up to ensure that each family is informed of their opportunity to be placed on the waiting list and is able to submit an application, which would risk EHV families losing assistance due to the exhaustion of EHV funds. If this waiver is not provided, it could delay our opening of the Housing Choice Voucher waiting list as the same employees are involved in both processes.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Boston Housing Authority (BHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that current regulations require individuals to follow standard waiting list procedures for the Housing Choice Voucher (HCV) program, which can delay and/or terminate access to permanent housing for Emergency Housing Voucher (EHV) families once their temporary vouchers are terminated. EHV families are among the most vulnerable population, many face challenges, including trauma-related disorders, anxiety or cognitive imparements, which may impair their ability to navigate the complex administrative process of the HCV waiting list application. Delays in transitioning to the HCV program could result in housing instability, undermining the primary goal of the EHV program. Additionally, the manual processing required of EHV families through standard waiting list protocols creates a significant administrative burden, requiring additional staff time, resources and documentation. By granting this waiver, BHA can streamline the process by automatically placing EHV families on the HCV waiting list with a preference that reflects their urgent needs, ensuring continuity of housing assistance.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Lansing Housing Commission (LHC).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that with the impending conclusion of Emergency Housing Voucher (EHV) funding, all current EHV households face a high risk of losing their housing assistance. Many EHV families face complex barriers—such as limited literacy, technology access, or language proficiency—that make it difficult to complete an additional application process. Requiring individual applications at this stage may result in administrative delays, confusion, or lack of timely response by participants. Individually processing applications for every EHV participant during the EHV close-out period would strain our administrative capacity. Staff would be required to contact, assist, and process 
                        <PRTPAGE P="41185"/>
                        applications for every household, which may lead to delays, errors, or missed deadlines, and jeopardizing successful transitions. Automatically placing EHV families on the waiting list provides a safety net to prevent abrupt termination and potential homelessness.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Michigan State Housing Development Authority (MSHDA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that due to the large number of families in the Emergency Housing Voucher (EHV) program, MSHDA is unlikely to perform the necessary outreach and follow-up in a timely manner to ensure that each family is informed of their opportunity to be placed on the Housing Choice Voucher (HCV) waiting list, is able to submit an application, and is otherwise transitioned to the HCV program. Such administrative delay would create an unnecessary and unreasonable risk of EHV families losing assistance and/or housing due to the exhaustion of EHV funds.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing and Redevelopment Authority of Duluth (HRA of Duluth).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that the HRA of Duluth continues to experience high demand for rental assistance from extremely low-income and special-needs populations. Requiring vulnerable Emergency Housing Voucher (EHV) households to re-verify and re-apply after the EHV program ends would be a duplicative intake process, create potential delays and burden participating households and their landlords, potentially leading to a return to homelessness or unsafe housing conditions. Given HRA of Duluth's limited resources, requiring EHV households to re-apply would create an administrative strain on staff. Granting this waiver would allow for a smooth transition and reduce strain on participating households and ensure that they are not penalized for initially entering HUD programs through emergency resources rather than the standard Housing Choice Voucher route. Additionally, it would allow staff to transition EHV families to long-term housing solutions efficiently and humanely, consistent with HUD's mission and the intent of the EHV program.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Western Piedmont Council of Government (WPCOG).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that WPCOG currently has 19 Emergency Housing Voucher (EHV) families. These families represent a highly vulnerable population, including persons who are disabled and/or elderly and persons who were experiencing literal homelessness at the time of lease up. Without this waiver, these families would have to wait until the WPCOG publicly opens its Housing Choice Voucher (HCV) waiting list, which is currently closed with around 2,300 applicants on the list. Since WPCOG expects that it could be a year or longer before it opens its HCV waiting list, current EHV families would reach the end of their assistance before they are able to apply to the HCV waiting list. Approval of this waiver will support a more efficient and streamlined transition process from EHV to HCV, reducing administrative burdens and helping to safeguard against housing disruptions.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Atlantic City Housing Authority (ACHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that ACHA projects that it will exhaust Emergency Housing Voucher (EHV) funding in 2025 and that this will require termination of five EHV families this year. ACHA has analyzed the Two-Year Tool and determined that it would be able to absorb all EHV families into its Housing Choice Voucher (HCV) program in 2025, but this may not be the case again in 2026. Without this waiver, there will be a delay in transitioning EHV families into the HCV program, which means that ACHA would be able to transition fewer EHV families to HCV by the end of the year. Further, ACHA expects that some EHV families will not be able to complete the HCV application process and therefore risk losing their housing assistance due to the impending exhaustion of EHV funds.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations 
                        <PRTPAGE P="41186"/>
                        Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of the City of Reno (HACR).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HACR is requesting this waiver to allow us to place all current Emergency Housing Voucher (EHV) households onto their Housing Choice Voucher (HCV) waiting list without having to open it or requiring individual applications. Although HACR would be allowed to open the HCV list to just EHV households, HACR has found that their community will apply for any open waiting list, even if they know they do not qualify. This causes confusion in our community and requires our Admissions staff to spend months processing unnecessary applications and sending withdrawal letters, which then further upsets the applicants. In addition, these EHV households exited the trauma of homelessness when they received their voucher assistance and requiring them to reapply in order to avoid returning to homelessness, which may retraumatize them unnecessarily.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Nevada Rural Housing Authority (NRHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that without a waiver, NRHA would be required to formally reopen the waiting list solely to allow current Emergency Housing Voucher (EHV) families to apply, which would require significant administrative time and cost, cause confusion among the public and applicants not eligible for the EHV preference, and delay urgent transitions needed to preserve housing stability. Additionally, requiring EHV families to complete the Housing Choice Voucher application process would create unnecessary barriers since most EHV families would need case management support to navigate the application process, putting them at risk of losing assistance if they are not able to complete the process.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Hempstead Housing Authority (HHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HHA is requesting a waiver to allow the current seven EHV households, referred through the Nassau/Suffolk Coalition for the Homeless, to convert their Emergency Housing Vouchers (EHVs) directly to Housing Choice Vouchers without requiring them to complete the standard waitlist application process. These families are among the most vulnerable, facing mental health challenges, limited computer literacy, and risk of housing instability that would make navigating the open waitlist process burdensome and potentially prohibitive. Additionally, HHA has limited staffing that will face increased administrative burdens, as staff will need to provide individualized assistance to each EHV household to ensure proper submission and compliance with standard waitlist requirements. For EHV households, these delays could result in prolonged homelessness, instability, and heightened vulnerability, undermining the core intent of the EHV program to provide rapid rehousing. Granting this waiver will preserve housing stability, prevent a return to homelessness, and uphold HUD's commitment to serving the most vulnerable.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Trust Fund Corporation (HTFC).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HTFC currently administers assistance to over 1,400 families under the Emergency Housing Voucher (EHV) program. Due to the number of families currently receiving EHV assistance, HTFC anticipates a significant administrative burden on the Public Housing Agency to conduct individualized outreach and follow-up for each household, which may jeopardize the ability of some families to maintain continuous housing assistance. Additionally, without this waiver, it is possible that some eligible families could miss the opportunity to apply, putting them at risk of losing rental assistance.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be 
                        <PRTPAGE P="41187"/>
                        included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Cuyahoga Metropolitan Housing Authority (CMHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that the Emergency Housing Voucher (EHV) program provided 339 vouchers to assist individuals and families who are homeless, at risk of homelessness, fleeing domestic violence, or transitioning out of homelessness. With strong coordination with our partners at the Continuum of Care (CoC), CMHA was able to utilize these vouchers for the community. Two hundred sixty-seven EHV's remain utilized and requiring household to re-apply for housing would cause significant hardship since many of the EHV families had assistance to complete all housing related paperwork. Due to the limited funding available in EHV, CMHA estimates Housing Assistance Payments will cease in March 2026. Without this waiver families would likely not apply for housing on their own and a majority of the 267 EHV assisted households would return to homelessness, which will add to the large homeless population and potentially exceeding the capacity of our CoC and the shelter system.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314 email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Klamath Housing Authority (KHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that KHA's Emergency Housing Voucher (EHV) clients tend to be more high needs, and the reapplication process would be a hardship for them. The EHV families will fall through the cracks and lose housing assistance in the process, which negates the original goal of the program. As a result, KHA is requesting the waiver to move EHV families over to the Housing Choice Voucher waitlist without families having to individually apply.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Westmoreland County Housing Authority (WCHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that WCHA is requesting a waiver so current Emergency Housing Voucher (EHV) families can easily transition to the Housing Choice Voucher program. This will eliminate the chance that any of these households would experience delays or interruptions of housing due to the potential challenges they may have in successfully completing the application process. Without this waiver, EHV households would risk a return to homelessness. Additionally, the added administrative processing time required with the full application process will be much greater, creating additional strain on existing WCHA operations.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Delaware County Housing Authority (DCHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that due to the number (41) of Emergency Housing Voucher (EHV) families in the program, it is unlikely DCHA would be able to complete the necessary outreach required to provide the required assistance in a timely manner. This waiver is necessary to avoid a delay in completing the individual application process in a timely manner to avoid the risk of EHV families losing assistance due to the exhaustion of funds and potentially becoming homeless. If DCHA has funding available to transition EHV families into the Housing Choice Voucher program once EHV funding has been exhausted, this waiver will be necessary to assist with that transition. This waiver will prevent EHV participants from losing assistance prior to the exhaustion of the EHV funding.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Municipality of Aguadilla.
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that the current process of requiring individual applications from Emergency Housing Voucher (EHV) families introduces significant delays, which puts vulnerable families at risk of losing their housing, exacerbating their already precarious situations. Further, this requirement would place significant burden on staff; the increased workload can lead to processing delays, further jeopardizing the timely transition of 
                        <PRTPAGE P="41188"/>
                        EHV families to the Housing Choice Voucher program and could also divert resources away from other critical services. The uncertainty and delays associated with the individual application process can cause considerable emotional and financial stress for EHV families, many of whom are already facing challenging circumstances. The potential loss of assistance due to procedural delays can disrupt the stability that these families have started to achieve with the help of the EHV program. The streamlined process that the waiver would allow would ensure that no family is left without assistance due to the procedural delays.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Municipio de Camuy.
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that the Municipio de Camuy currently has 11 Emergency Housing Voucher (EHV) families. Subjecting these families to the process of applying for and obtaining assistance through the Housing Choice Voucher (HCV) program would take a lot of time and delay the transition of the families. This could lead to the funds being depleted and the families losing assistance. The Municipio de Camuy has space in its HCV program for these families and has updated its Administrative Plan to adopt a preference for EHV families. This waiver would facilitate the transition from EHV to HCV for these families and provide them with stability and continuity in their housing assistance.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Municipality of Lajas.
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that the Municipality of Lajas has 11 families in its Emergency Housing Voucher (EHV) program. The Municipality of Lajas projects that it will be able to transition all these families into its EHV program in calendar year 2025 and the delay caused by having to require individual applications from EHV families would put families at risk of not being able to transition to the Housing Choice Voucher (HCV) program. Further, the Municipality of Lajas will not be able to do the necessary outreach and follow up to ensure that each family is able to submit an application and be placed on the HCV waiting list, putting them at risk of losing assistance.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         North Charleston Housing Authority (NCHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that NCHA has 46 Emergency Housing Voucher (EHV) participants and many of them face significant barriers to completing the Housing Choice Voucher (HCV) application process. This is especially true for those who are elderly, have limited digital literacy, or have unstable or non-existent internet access. Without the ability to place EHV families directly onto the HCV waiting list, these vulnerable families face a high risk of losing assistance due to the complexity of the application process, staffing limitations, and lack of awareness of their need to reapply. Additionally, NCHA has only recently emerged from a multi-year shortfall period, and staffing for intake remains a challenge. NCHA does not currently have sufficient administrative capacity to support the reopening of the waiting list or intensive intake process. Granting this waiver will allow NCHA to prioritize existing EHV families without jeopardizing the integrity of our waiting list procedures.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         East Tennessee Human Resource Agency (ETHRA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that due to the wide geographical area and number of families involved, ETHRA may not be able to do an adequate amount of outreach and follow-up to ensure each family can submit an application in a timely manner, which could ultimately result in the loss of assistance when Emergency Housing Voucher (EHV) funds are discontinued. This waiver would ensure a smooth transition to the Housing Choice Voucher (HCV) Program with no gaps in assistance because we have HCV Housing Assistance Payments funds available for all remaining EHV families.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, 
                        <PRTPAGE P="41189"/>
                        Department of Housing and Urban Development, 451 Seventh Street, SW, Washington DC, 20410, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Houston Housing Authority (HHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that due to the scale of HHA's Emergency Housing Voucher (EHV) program (593 families), the administrative burden of requesting that each EHV family complete and submit an individual application would be considerable for both HHA and affected families. HHA expects that EHV families may require significant support from HHA staff in completing an application and would require notifying families, support in completing the application, and tracking progress throughout the application process. These barriers and challenges associated with a requirement for EHV families to submit individual applications may result in a loss or gap in housing assistance. HHA anticipates that this waiver will mitigate barriers related to applying to the Housing Choice Voucher (HCV) program and prevent a loss or gap in housing assistance for EHV families. Furthering efforts to support EHV families, HHA is in process of revising the HCV Administrative Plan to provide a local preference in the HCV program for currently assisted EHV families whose assistance is at risk of termination due to lack of program funding.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Dallas County Health and Human Services (DCHHS) .
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that requiring separate applications and standard selection would create significant administrative burden, extend the transition timelines, and increase the risk of funding gaps. This would further heighten the risk of assistance interruptions for households already experiencing housing instability and could lead to housing loss. DCHHS sought and received approval from the Dallas County Commissioners Court and has formally revised its FY2025 Housing Choice Voucher (HCV) program Administrative Plan to adopt a local preference specifically for transitioning Emergency Housing Voucher (EHV) families at risk of losing assistance. Granting a waiver would allow DCHHS to place all 87 EHV families directly onto the HCV waiting list, enabling a coordinated, equitable transition that protects vulnerable households, preserves uninterrupted assistance for those households and maintains program compliance.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Virginia Housing Development Authority (VHDA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that VHDA administers the Housing Choice Voucher program in partnership with 26 local housing agencies, managing separate waiting lists across a geographically vast and decentralized service area. Were a waiver not granted, waiting lists across the state would have to be opened to reach every region VHDA serves. This area would span urban centers, rural communities, and regions with limited local infrastructure. This influx would place a strain on VHDA's system, with more than 5,200 households across these waiting lists. Prior partnerships with 15 Continuums of Care across the State, who VHDA has historically relied on to support with outreach and housing support of the most vulnerable EHV households, have limited capacity due to recent funding cuts. It is unlikely that VHDA can conduct the level of individualized outreach and follow-up needed to ensure each EHV household is informed of the opportunity to apply to multiple waiting lists. Additionally, participants may be unable to complete the necessary applications timely due to lack of transportation, limited internet access, language barriers or other disabling conditions or needs. Without continued rental support, many of these families are at risk of returning to homelessness.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Worcester Housing Authority (WHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that WHA currently serves 58 families through the Emergency Housing Voucher (EHV) program. WHA faces significant operational challenges in conducting timely outreach, follow-up, and application intake for each EHV participant. Without a waiver, WHA would be required to request and process individual applications, a process that would substantially delay the ability to transfer EHV families to the Housing Choice Voucher waiting list
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                        <PRTPAGE P="41190"/>
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Missoula Housing Authority (MHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that MHA has many disabled adults with kids in its Emergency Housing Voucher (EHV) program and the requirement to go through the HCV application process would pose a barrier to transitioning to the Housing Choice Voucher (HCV) program before the exhaustion of EHV funds. The application process can be difficult for EHV families, and they could end up losing their housing if they are not able to transition to the HCV program in a timely manner.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         East Orange Housing Authority (EOHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that EOHA will endure delays in transitioning Emergency Housing Voucher (EHV) families to the Housing Choice Voucher program if we require them to submit individual applications, putting EHV families at risk of losing assistance due to the exhaustion of EHV funds.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         NYC Department of Housing Preservation and Development (HPD).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HPD has over 2,000 families in the Emergency Housing Voucher (EHV) program. EHV participants joined the program through a referral system established between HPD and community-based organizations (CBOs), which did not involve a paper-based application. Without the direct support from our partnering CBOs, HPD will not be able to engage households with the level of attention needed to ensure their applications are submitted properly and in a timely manner. This will result in EHV families failing to convert and lose assistance and potentially their overall housing stability.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Youngstown Metropolitan Housing Agency (YMHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that the process of applying for the Housing Choice Voucher (HCV) program would be confusing to Emergency Housing Voucher (EHV) families, and without their full understanding of what is occurring, homelessness is likely to occur for these families. In order to successfully transition EHV families to the HCV program, staff would need to follow up with all stakeholders in this subsidy process, families will suffer depression from not understanding the full process, and owners and social services agencies will be frustrated from the various phone calls that clients may be placing to agencies. This waiver will allow a smooth transition so that families will not lose assistance.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Akron Metropolitan Housing Authority (AMHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that the AMHA needs the waiver to streamline the process to add all Emergency Housing Voucher (EHV) families to the Housing Choice Voucher waiting list to avoid creating more of an administrative burden for our families and staff. AMHA is concerned that, based on the population served by EHV, these vulnerable families will not understand why they have to reapply when they already have housing and may not complete the required paperwork. If the families miss the required steps, the families would be forced back into homelessness rather than maintaining the stable housing they have already worked to achieve. Requiring EHV families to individually apply would also require additional AMHA staff time to process the applications, review them for accuracy, contact the EHV families, and answer questions
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and 
                        <PRTPAGE P="41191"/>
                        Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Linn-Benton Housing Authority (LBHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that the waiver is necessary because it is unlikely that Emergency Housing Voucher (EHV) families—particularly those with the greatest needs—will be able to complete the process of applying to the Housing Choice Voucher waiting list. This is compounded by the fact that LBHA serves a rural area that spans over 80 miles which makes it difficult for families to interact with the office. Many EHV families are no longer connected to services or coordinated care which puts them at risk of losing their assistance and becoming homeless. LBHA also does not have the staffing capacity to follow up with each family individually, increasing their risk of losing their assistance and becoming homeless.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of Washington County (HAWC).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HAWC has 80 families currently participating in its Emergency Housing Voucher (EHV) program and the capacity to absorb 20 EHV households into permanent voucher programs administered through the Housing Choice Voucher waiting list. Any delay in these program transfers will limit HAWC's capacity to extend the EHV timeline. The waiver is necessary for HAWC's ability to act quickly and efficiently to transition households from EHV to permanent rental assistance programs, while limiting the administrative burden for staff and participants.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Allentown Housing Authority (AHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that this waiver is needed to ensure continuity of housing assistance for this highly vulnerable population. This waiver would ensure that Emergency Housing Voucher (EHV) families are not excluded from housing assistance due to lack of capacity to complete paperwork or meet deadlines or due to delays and inefficiencies caused by the increased administrative burden on AHA.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 Seventh Street SW, Washington, DC 20410, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Municipality of San Germán (MSG).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that MSG has not been able to maintain 100% voucher utilization due to the limited availability of affordable housing units in our jurisdiction. Emergency Housing Voucher (EHV) families have already been determined eligible, are currently receiving rental assistance, and are residing in units that have passed HUD-required inspections. Their transition into the Housing Choice Voucher (HCV) program would not require the typical eligibility screening or initial Housing Quality Standards inspection processes, which not only reduces the administrative burden on our staff but also expedites the process of maintaining assistance for these households. Requiring each EHV household to reapply for HCV assistance would create unnecessary procedural barriers, which could delay or even jeopardize their continued housing stability. This waiver would allow us to maintain support for our most at-risk populations while maximizing voucher utilization and aligning with HUD's goals of reducing homelessness and improving program efficiency.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Tennessee Housing Development Agency (THDA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that THDA requests HUD approval to use the Emergency Housing Voucher (EHV) preference to protect vulnerable households from potential loss of assistance, reduce administrative workload, and support HUD's objective 
                        <PRTPAGE P="41192"/>
                        of streamlining agency processes. Given the volatility in our local housing market-marked by rising rents and limited availability-any disruption in assistance could lead to displacement or homelessness for families who are already rent-burdened. This waiver would allow THDA to provide a smooth and uninterrupted transition for the 207 families currently receiving EHV assistance. Without this waiver, these vulnerable families risk experiencing a lapse in rental assistance, which will create avoidable instability and hardship.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Prince William County Office of Housing and Community Development (OHCD).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that Emergency Housing Voucher (EHV) families face significant barriers to completing the Housing Choice Voucher (HCV) application process, such as limited knowledge in the usage of computers, difficulty maneuvering technological devices, and lack of access to transportation in order to obtain in-person assistance. Due to these limitations, EHV families would be at risk of losing their housing assistance if this waiver is not granted and they are required to go through the HCV application process.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Yakima Housing Authority (YHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that YHA projects that it will exhaust Emergency Housing Voucher (EHV) funding in 2025 and that this will require termination of 13 EHV families this year. YHA has analyzed the Two-Year Tool and determined that it would be able to absorb some EHV families into its Housing Choice Voucher (HCV) program in 2025, but this may not be the case again in 2026. Without this waiver, there will be a delay in transitioning EHV families into the HCV program, which means that YHA would be able to transition fewer EHV families to HCV by the end of the year. Further, YHA expects that some EHV families will not be able to complete the HCV application process and therefore risk losing their housing assistance due to the impending exhaustion of EHV funds.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Mesa Housing Authority (MHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that MHA currently has 82 families receiving assistance through the Emergency Housing Voucher (EHV) program. By granting this waiver, MHA will be able to place all EHV families on the Housing Choice Voucher (HCV) waiting list after establishing an EHV preference, without requiring each family to individually apply. This administrative flexibility would reduce barriers for families, prevent unnecessary gaps in assistance, and streamline the transition process, ensuring continuous housing support. Approval of this waiver request will allow MHA sufficient time to prepare to move EHV families to the regular HCV program, allowing us to avoid causing 82 EHV families to become homeless.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of the County of Kern (HACK).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HACK has 164 families assisted through the Emergency Housing Voucher (EHV) program and do not believe we have adequate staff capacity to complete the individual applications for the Housing Choice Voucher (HCV) program. Each family would need to be sent a letter, then followed by phone contact, and an in-person appointment to complete their application. This population has demonstrated that a more hands-on approach is needed than families in the regular HCV program, as evidenced by their need for additional assistance to complete annual and interim re-certifications. To ensure the continued housing stability of our EHV families, we respectfully request a waiver to add all EHV families to the HCV waiting list after establishing an EHV preference, without families having to individually apply for the HCV program.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <PRTPAGE P="41193"/>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of the County of San Joaquin (HACSJ)
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that Emergency Housing Voucher (EHV) families are some of the most vulnerable populations and reducing barriers to transitioning to the Housing Choice Voucher (HCV) program would reduce the risk of delays and housing interruptions. Without this waiver, HACSJ would have to contact each family individually, which would delay housing support and put EHV families at risk of not being able to transition to HCV due to error, lack of documentation, and significant administrative delays.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="04">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Marin Housing Authority (MHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that MHA has 97 families in its Emergency Housing Voucher (EHV) program. These families often face technology, mobility, and literacy barriers. When initially enrolled, EHV families received case management support through Coordinated Entry, but only 24 percent of EHV families currently have case managers. If this waiver is not granted, many EHV families may struggle to complete the application process, putting them at risk of losing assistance. Additionally, if MHA is required to publicly open its Housing Choice Voucher waiting list, it expects to receive a high volume of ineligible applications, which will require significant time to review and remove non-qualifying entries and create delays and administrative burden.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of the County of Humboldt (HACH).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HACH serves a rural population with extremely limited transportational options. Many participants are living with significant disabilities and mental health challenges. This is compounded by their requirement of intensive and specialized assistance, which creates challenges in their ability to timely and successfully complete basic paperwork, putting them at risk of losing their housing assistance if they must go through the application process to be added to the Housing Choice Voucher waiting list.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Santa Monica Housing Authority (SMHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that SMHA's Emergency Housing Voucher (EHV) program includes individuals and families who are homeless, fleeing domestic violence, or living with disabilities. Requiring them to submit a new application would create unnecessary barriers for people who are already facing significant challenges just to remain housed. When SMHA admitted participants to the EHV program, it did not make broad use of the flexibilities offered under the EHV program. In the few cases where families were admitted without full documentation, SMHA tracked those files and made sure to collect the required Social Security and citizenship documentation well within the 180-day window. All active EHV participants have provided full documentation and are eligible for continued assistance under the Housing Choice Voucher program. Housing in Santa Monica is extremely expensive, and the recent wildfires in the region have only made the rental market more difficult. Rents have gone up, affordable units are harder to find, and SMHA is seeing more displacement across the city. Without the waiver, SMHA risks unnecessary delays and disruptions that could harm families they have worked hard to stabilize.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Boulder County Housing Authority (BCHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that BCHA's Emergency Housing 
                        <PRTPAGE P="41194"/>
                        Voucher program currently supports 26 households, which include 26 children, four seniors over the age of 62, and three individuals with documented disabilities. All households experienced difficulty completing paperwork at initial intake due to barriers such as limited literacy, lack of internet access, and general instability. Requiring households to apply to the Housing Choice Voucher waiting list would create significant hardship and pose a risk to their housing stability.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Jefferson County Housing Authority (JCHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that if this waiver is not granted, JCHA would have to require individual applications from Emergency Housing Voucher (EHV) families and publicly open its Housing Choice Voucher (HCV) waiting list, which would cause the transition to HCV to become slower, less predictable, and more complex to manage administratively for JCHA. This would also pose barriers for EHV families, putting them at risk of losing assistance and becoming homeless.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Gary Housing Authority (GHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that GHA has enough Housing Choice Vouchers (HCVs) to be issued to all 21 Emergency Housing Voucher (EHV) families. However, it would be difficult for GHA to provide a reasonable amount of time for EHV families to apply for the HCV program and be selected from the waiting list before the exhaustion of EHV funds. Additionally, it is unlikely that GHA will be able to do the necessary outreach and follow up to ensure that each EHV family is able to submit an EHV application, which would put EHV families at risk of losing assistance.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Indiana Housing and Community Development Authority (IHCDA)
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 9, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that IHCDA has 239 Emergency Housing Voucher (EHV) participants. Having to individually apply will be time-consuming for this vulnerable population. Our staff will also have an increased workload and will not be able to complete the 239 application reviews for each tenant. Without this waiver, IHCDA's EHV families are at risk of returning to homelessness. Therefore, we are requesting this waiver to add all applicants to the waitlist at one time to prevent any burden on our operations and EHV families.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.201(e) and 983.251(a)(2).
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.201(e) and 983.251(a)(2) pertain to the verification of one's date of birth and disability status for the Housing Choice Voucher (HCV) and Project-Based Voucher programs.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Michigan State Housing Development Authority (MSHDA)
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 26, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing the following justifications from MSHDA:
                    </P>
                    <P>○ From July 2023 to June 2024, 53 percent of all new admissions to MSHDA's HCV program were individuals and families experiencing homelessness. Additionally, 47 percent of MSHDA's HCV program participants are disabled, and allowing self-certification of date of birth, disability status, and income verification requirements when other verification methods are not immediately available increases accessibility for families and individuals with disability.</P>
                    <P>○ In partnership with Continuums of Care and Housing Assessment and Resource Agencies statewide, MSHDA continues to offer a preference for individuals and families experiencing homelessness. The homeless preference is to ensure that critical, long-term housing subsidies are directed to those experiencing homelessness. It is incorporated as part of MSHDA's Emergency Solutions Grant (ESG) program to allow partners statewide to refer eligible households to the HCV waitlist under this preference, utilizing it as another tool to help end homelessness.</P>
                    <P>
                        ○ MSHDA adopted self-certification waivers for date of birth and income verifications for both Emergency Housing Vouchers and the Stability Vouchers. These waivers allowed MSHDA to relieve the burden of documentation collection on individuals and families 2 experiencing homelessness without experiencing any significant or measurable impact to Enterprise Income Verification identity verification errors or miscalculations of income, assets, and expenses. Individuals and families in these programs were able to provide self-
                        <PRTPAGE P="41195"/>
                        certification when documents were not immediately available. This has a proven track record of reducing the time it takes MSHDA to issue a family a voucher to search for housing with when these flexibilities are adopted.
                    </P>
                    <P>○ If these waivers are not approved, MSHDA will continue to experience delays in the lease-up process for families and individuals who are experiencing homelessness. The requirement to collect social security cards, birth certificates, and other verifications with no option to accept self-certification or allow lease up may present delays and even denial of assistance for homeless families. During this time the family remains unhoused in shelters and on the street. Additionally, families and individuals who have made requests for required documentation but are delayed in lease up continue to occupy shelters and require emergency funding that could be used for other families once they are permanently housed with an HCV.</P>
                    <P>
                        <E T="03">Contact:</E>
                         Waiver Processing Team at 
                        <E T="03">HomelessWaivers@hud.gov.</E>
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 905.314(l)(1); Section 9(g)(1) of the United States Housing Act of 1937
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         Section 9(g)(1) of the United States Housing Act of 1937, as implemented by regulation 24 CFR 905.314(l)(1), instructs public housing agencies (PHAs) that they may not use more than 20 percent of Capital Fund Formula grants for eligible Operating Fund activities as described in Section 9(e)(1)(C) of the Act.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of Kansas City (HAKC).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 26, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HAKC is experiencing high rates of violent crime and property crime, which pose a serious threat to the health and safety of the PHA's public housing residents at the following public housing developments: MO002000013: Brush Creek Towers, 1800 Emmanuel Cleaver II Blvd., Kansas City MO002000025: Pemberton Heights, 3710 East 51st Street, Kansas City. Also, HAKC provided recent local crime data and projections (within FFYs 2023 and FFY 2024) indicating crime rates in Kansas City, within which these projects are located. HAKC indicated the specific activities that it plans to undertake to address the crime problem identified, including using protective services. 2 HAKC provided a justification for the request based on the FFYs 2023 and 2024 Capital Fund Processing Guidance. HAKC requests authorization to allocate up to 34.06 percent of $4,779,630 of HAKC's FFY 2023 Capital Fund formula grant and up to 33.71 percent of $4,974,861 of HAKC's FFY 2024 Capital Fund formula grant, for above-baseline services for eligible antidrug and anticrime activities to be used for the current police contract. HAKC's letter provides good cause for a waiver to use Capital Funds in excess of 25 percent of its total grant award for its FFY 2023 Capital Funds in the amount of $433,095, approximately 9.06 percent of the total FFY 2023 Capital Fund grant. Additionally, HAKC provided good cause for a waiver to use Capital Funds in excess of 25 percent of its total grant award for its FFY 2024 Capital Funds in the amount of $433,095, approximately 8.71 percent of the total FFY 2024 Capital Fund grant. The security guard contract is for a period of two years with an option to renew. The annual contract cost is $433,095, totaling $866,190 for the two-year term. HAKC has certified that it has not exceeded 25 percent of its FFYs 2023 or 2024 Capital Funds for its contract with SK Security Services before the date of this waiver approval.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         David Fleischman, Director, Office of Capital Program Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">David.Fleischman@hud.gov,</E>
                         telephone (202) 402-2071.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.503(a)(2) and 24 CFR 982.503(b).
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.503(a)(2) and 24 CFR 982.503(b) provide that a Public Housing Agency (PHA) must adopt a payment standard schedule that establishes voucher payment standard amounts for each Fair Market Rent (FMR) area in a PHA's jurisdiction. And, for each payment standard area, a PHA must establish a payment standard amount for each unit size, measured by number of bedrooms. These payment standard amounts compose the PHA's payment standard schedule and are used to calculate the monthly housing assistance payment for a family.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Cuyahoga Metropolitan Housing Authority (CMHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         September 26, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that due to CMHA's current budget utilization for calendar year 2025, it cannot support higher subsidies for all Housing Choice Voucher (HCV) participants who move to an opportunity area. CMHA is projected to have a $11,913,345 HCV shortfall. CMHA has implemented several cost savings measures, such as ceasing issuance of new vouchers to applicants, restricting voucher extensions, stopping the absorption of incoming portability, and removing vacant PlaceBased Voucher units from existing contracts. However, to meet the requirements of their participation in the demonstration, CMHA must continue to offer payment standards that are adequate in opportunity areas in CMHA's local jurisdiction. As such, CMHA seeks to establish a separate payment schedule for the demonstration. In accordance with 85 FR 42890, a family's participation in the demonstration is defined as being enrolled in the demonstration at CMHA and assigned to a control or treatment group. This waiver will allow CMHA to balance its budget constraints with the requirements of the demonstration.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Carmen Chow, Housing Program Specialist, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Carmen.Chow@hud.gov,</E>
                         telephone 312-913-8523.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Montana Department of Commerce (MDOC).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 19, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that without this waiver, it is very possible that some MDOC tenants will lose their assistance and become homeless. MDOC covers the entirety of Montana and some of their tenants live in rural areas without access to a computer. This makes it very difficult for them to apply to the Housing Choice Voucher waiting list. Some also need a little extra help, which would force them to travel to get to the field offices. This is not always possible or safe in the winter.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing 
                        <PRTPAGE P="41196"/>
                        Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Works.
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 10, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that Housing Works successfully leased all 96 Emergency Housing Vouchers (EHVs) to participants from highly vulnerable populations, including individuals who have experienced homelessness and survivors of domestic violence and human trafficking. Housing Works is requesting this waiver so that it can seamlessly transition EHV participants on to the Housing Choice Voucher (HCV) program using a preference that Housing Works has already adopted. If this waiver were not granted, Housing Works would not be able to successfully transition EHV families to the HCV program and EHV families would be at risk of homelessness and re-traumatization.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Anaheim Housing Authority (AHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 10, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that AHA requests HUD approval of a waiver to stabilize households and prevent families from losing assistance and facing potential homelessness again. AHA's Emergency Housing Voucher (EHV) program has served individuals and families experiencing or at risk of homelessness, including children, elderly or disabled members, and survivors of domestic violence. With the end of EHV program funding, these families face a serious risk of returning to homelessness. This waiver will allow AHA to efficiently utilize HUD resources by reducing administrative burden, ensuring that public funds are applied effectively to stabilize households and prevent costly returns to emergency shelters or other crisis housing options. Should this waiver not be granted, requiring EHV families to submit a separate Housing Choice Voucher application would create barriers to timely housing assistance, lead to increased confusion and uncertainty, and increased likelihood of housing disruption and/or homelessness.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Boulder Housing Partners (BHP).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 10, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that BHP's Emergency Housing Voucher (EHV) program currently supports 22 households, including 30 adults and four children. The population includes nine elderly individuals over age 60 and 14 households headed by individuals with disabilities. Households are geographically dispersed across Boulder County, with 14 participants residing in the City of Boulder, four in Lafayette, and four in Longmont. Without this waiver, BHP would be required to allocate substantial staff time and resources to conduct individualized outreach, assist with application completion, and ensure timely receipt—all within a very limited timeframe. Opening a waiting list for vouchers, any type of voucher, is going to draw more than 2,000 applicants, and provide false hope to all of those who do not currently hold an EHV. For EHV households, particularly those lacking reliable internet and transportation access, the standard application process creates a substantial barrier. This may lead to missed deadlines and, ultimately, the loss of housing assistance.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         West Palm Beach Housing Authority (WPBHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 10, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that if this waiver is not granted, WPBHA would be required to formally reopen its Housing Choice Voucher waitlist to accept and process new applications from Emergency Housing Voucher (EHV) families. This process would place a significant administrative and operational burden on the agency, diverting staff time and system resources away from ongoing program management and participant services. Reopening the waitlist would also require additional public notifications, application screening, all of which would increase workload and delay the ability to assist EHV families in a timely manner. This delay could lead to disruptions in housing stability for EHV participants whose temporary assistance is ending, potentially resulting in housing insecurity or loss of housing.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <PRTPAGE P="41197"/>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Lakeland Housing Authority (LHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 10, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that LHA risks losing funding designated for our most vulnerable households. This could jeopardize ongoing assistance for these families and result in the discontinuation of their vouchers. Consequently, families may face difficulties in paying rent, increasing the likelihood of evictions and homelessness. Additionally, many landlords may choose to exit our voucher program. Reducing procedural burdens can mitigate significant stress and trauma for Emergency Housing Voucher (EHV) families, who are already experiencing anxiety related to funding uncertainties and their vulnerable circumstances. These waivers will facilitate a smoother transition for EHV participants and help prevent them from returning to homelessness.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Columbus Housing Authority (CHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 10, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that preventing housing instability for Emergency Housing Voucher (EHV) families is the main goal and this waiver will provide that opportunity by being able to bypass the need for each EHV family to individually apply to the HCV waiting list, reducing risks of delays or nonparticipation during the transition. The PHA can acknowledge that due to the delay caused by having to require individual applications from EHV families, EHV families would be at risk of losing assistance due to the exhaustion of EHV funds. Without this waiver, some EHV families may miss the opportunity to transition to the HCV program, especially those with barriers like disabilities, limited English proficiency, or low digital literacy leading to potential loss of assistance and increased risk of homelessness
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Lawrence-Douglas County Housing Authority (LDCHA).
                    </P>
                    <P>
                        <E T="03">Granted By:.</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 10, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that LDCHA is requesting a waiver to prevent housing instability and ensure continuity of assistance for highly vulnerable households. Many Emergency Housing Voucher (EHV) participants experience barriers such as disabilities, limited English proficiency, and low digital literacy. Requiring a new application process could result in confusion, missed deadlines, and loss of housing assistance, placing these households at high risk of homelessness once EHV funding expires. If the waiver is not granted, the additional workload of processing and verifying every individual application would create an unsustainable strain on staff capacity. Without this waiver, LDCHA risks increased homelessness among EHV participants, significant administrative inefficiencies, inequitable outcomes, and reduced program effectiveness.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of Baltimore City (HABC).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 10, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that as of October 28, 2025, 244 families are leased in HABC's Emergency Housing Voucher (EHV) program. Due to the scale of the EHV program, the administrative burden of requesting that each EHV family complete and submit an EHV application would be considerable for both HABC and affected families. HABC expects that EHV families may require significant support from HABC in order to complete an application, similar to the support that EHV families received from the Continuum of Care when they were initially admitted to the EHV program. Because of these barriers and challenges, requiring EHV families to submit an individual application may result in loss or gap in housing assistance. HABC anticipates that this waiver will mitigate barriers related to applying to the Housing Choice Voucher program and prevent a loss or gap in housing assistance for EHV families.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Northwest Minnesota Multi-County Housing and Redevelopment Authority (NWMNHRA).
                        <PRTPAGE P="41198"/>
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 10, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that NWMNHRA requests the waiver for the remaining Emergency Housing Voucher (EHV) participants so that these families do not lose their rent assistance, which would create immediate hardships and potential homelessness. If families had to apply individually, they may potentially get lost in the system, by not returning paperwork timely. If the waiver is not granted, landlords who already accepted the families to their rental units would not receive their payments, which could result in potential loss in landlords willing to work with the housing programs. Additionally, NWMNHRA staff would experience administrative burden with application processing, new briefings, inspections, and a loss of administrative fees.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Southern Nevada Regional Housing Authority (SNRHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 10, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that SNRHA requests a waiver to stabilize operations, uphold program integrity, and continue serving the Southern Nevada community effectively, ensuring that Emergency Housing Voucher (EHV) participants receive timely assistance and housing opportunities without disruption. This waiver would allow SNRHA to manage transferring 460 current EHV participants. If the waiver were not granted, SNRHA may be unable to meet critical program deadlines, including lease-ups, inspections and eligibility determinations. These delays would strain agency operations and jeopardize housing stability for 460 EHV participants, many of whom are from vulnerable populations. Families could lose housing opportunities, landlords may experience increased frustrations, and unit availability for future participants could be reduced.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Oklahoma Housing Finance Agency (OHFA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 10, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that Emergency Housing Voucher (EHV) households often include vulnerable populations, such as individuals with disabilities or those fleeing domestic violence. Without a waiver of 24 CFR 982.204 and 24 CFR 982.206, these households could face a loss of stable housing due to OHFA's inability to expedite transitions to the Housing Choice Voucher (HCV) program by opening its waiting list solely to these households and bulk adding them to the HCV waiting list with a targeted preference. Instead, OHFA would be required to open its waiting list to all applicants, potentially leading to a flood of non-EHV applications. EHV households would then be required to apply individually, along with non-EHV households, which could lead to prolonged processing times. Without this waiver, there could potentially be an increase in demand on homeless prevention services due to the high risk of EHV terminations
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Northwest Oregon Housing Authority (NOHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 10, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that NOHA is requesting a waiver to reduce the administrative burden for both the Authority itself and its families, preventing gaps in housing assistance, and ensuring compliance with HUD guidance to prioritize stability for Emergency Housing Voucher (EHV) households. Many EHV participants face circumstances such as homelessness, risk of homelessness, disability, or other challenges that could prevent timely submission of an application, leaving them at risk of being left off the waiting list. This waiver will enable NOHA to provide continuity of assistance, minimize disruptions for landlords, and support these vulnerable families.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Lancaster County Housing and Redevelopment Authority (LCHRA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 10, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that LCHRA is requesting the waiver to avoid undue stress and disruption for current Emergency Housing Voucher (EHV) families as they transition to the Housing Choice Voucher (HCV) program. Requiring EHV households to complete a new HCV application creates unnecessary administrative barriers and is likely to result in significant delays in the eligibility and leasing process. EHV households face complex challenges 
                        <PRTPAGE P="41199"/>
                        and barriers to engagement, including anxiety, trauma histories, and fear of program changes. Were the waiver not granted, the additional application steps will increase processing time and may result in disruptions to housing stability.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Knoxville Community Development Corporation (KCDC).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 10, 2025
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that KCDC is seeking this waiver to streamline the transition process and ensure continued assistance for Emergency Housing Voucher (EHV) families. This waiver will facilitate a smooth, efficient transition and help prevent housing instability for vulnerable households. Requiring separate applications from each EHV household would create unnecessary administrative burdens and delay the ability to provide uninterrupted housing support. If this waiver is not approved, EHV families will be required to submit individual applications to be placed on the Housing Choice Voucher waiting list. This additional step creates a significant risk that some households may lose rental assistance due to the exhaustion of EHV funding during the application processing period. It would also impose additional administrative burdens on KCDC staff, diverting resources from other critical housing activities.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of the City of Austin (HACA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 10, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HACA's Emergency Housing Voucher (EHV) clientele is overwhelmingly comprised of individuals with disabilities, many of whom would face significant physical and mental challenges when required to actively reapply for assistance. Granting this waiver would allow HACA staff to manually add families to the Housing Choice Voucher (HCV) waiting list, ensuring that all EHV households have equitable access to continued rental assistance—regardless of their ability to navigate the application process independently. Without the waiver, HACA would have to follow costly and time-consuming public notification procedures to open the HCV waiting list for EHV families. In addition to the financial cost and time delays, this process opens the door to confusion among the public (non-EHV participants) and whether they are eligible to apply for HCV assistance. This could lead to an influx of inquiries from low-income families, social service agencies, and media outlets, which would impair HACA's ability to provide quality customer service to our clients, and potentially damage the trust of our community.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Baytown Housing Authority (BHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 10, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that BHA administers 26 Emergency Housing Vouchers (EHVs) and may not have adequate time to perform the necessary outreach and follow up to ensure that each EHV family is fully informed of their opportunity to transition from the EHV program to the Housing Choice Voucher (HCV) program. Many do not have the capability or the means to submit any document forms electronically. Furthermore, many families lack transportation, placing these EHV families at risk of losing their opportunity to transition to the HCV program and ultimately, their housing assistance
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Eagle Pass Housing Authority (EPHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 10, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that through Notice PIH 2025-19, HUD strongly encouraged public housing authorities to transition Emergency Housing Voucher (EHV) participants to the regular Housing Choice Voucher (HCV) program and EPHA would like to follow such recommendation as soon as possible in order to prevent families from losing assistance and potentially facing homelessness. If EPHA requires individual applications from EHV families, this will delay the transition to the HCV program and place them at risk of losing assistance due to exhaustion of funds. Allowing EPHA to transition the EHV families without them having to re-apply will provide a smooth, quick transition and save time and effort which can be better used to attend to the program needs. This will also help the EHV families as they will not have to redo the entire application process.
                        <PRTPAGE P="41200"/>
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Grand Prairie Housing and Neighborhood Services (GPHNS).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 10, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that GPHNS's Housing Choice Voucher waiting list is currently closed. However, if we opened it for current Emergency Housing Choice (EHV) participants to apply, they may get confused and not apply at all thinking that the waiting list is closed to them as well. If we require separate individual applications from EHV families, we believe that it would be a challenge for them to complete the waiting list application. Although the EHV families currently have shelter, there are many barriers that they are still faced with. The families may lack several resources such as not possessing the necessary technological equipment to complete the online application, not having the transportation needed to get to the housing office, local library, or outreach center to utilize borrowed equipment, and for a few participants, the inability to understand the application process. Diligent efforts would be made to reach all EHV families, but it would be improbable for the GPHNS staff to do the required outreach and follow up to ensure that each EHV family applies to be placed on the waiting list. The only way that we can ensure that the EHV families have a fair, equitable chance at maintaining affordable housing is by placing them all on our now closed waiting list simultaneously.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Tacoma Housing Authority (THA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 10, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that if this waiver is not provided, THA staff would be required to train Emergency Housing Voucher (EHV) households on how to register for the application portal and assist them in submitting applications to the HCV waiting list. Given the large number of families in the EHV program, THA staff would be unable to effectively reach out and ensure that every household is informed and able to submit an application before available funds are exhausted. For EHV participants, the absence of the waiver would mean navigating another layer of paperwork and procedures, and could result in increased stress, confusion, and the possibility that vulnerable families might not complete the application process in time.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of the City of Bellingham (BHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 10, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that BHA requests the waiver in order to expedite the process of transitioning Emergency Housing Voucher (EHV) participants to the Housing Choice Voucher (HCV) program, allowing BHA to ensure all participants successfully get onto the HCV waitlist and no one loses their rental assistance. If the waiver is not granted, BHA will experience extensive delays in transitioning EHV participants to the HCV waitlist. Administrative burden would be unavoidable with the level of outreach that would be required to ensure all families are assisted with the application, leaving the potential for some participants to lose their housing assistance.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of Thurston County (HATC).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 10, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that if this waiver is not approved, HATC will be required to process individual Housing Choice Voucher (HCV) waiting list applications for each Emergency Housing Voucher (EHV) household. This would significantly increase administrative workload and delay transitions from EHV to HCV assistance. Staff would need to conduct duplicative data entry, verification, and eligibility reviews for each household, diverting limited resources from other core program functions. For participants, this would create additional procedural barriers, requiring families to complete separate applications and provide documentation that has already been verified under their EHV participation. Requiring each EHV household to separately apply to the HCV waiting list places additional administrative and logistical burden on families—many of whom may face barriers (lack of transportation, lack of stable mailing address, limited access to the internet, language or disability challenges). As a result, the transition process would be 
                        <PRTPAGE P="41201"/>
                        slower, more confusing for households, and could lead to gaps in housing assistance if an EHV participant loses eligibility before securing an HCV voucher.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Spokane Housing Authority (SHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 10, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that this waiver is necessary to ensure smooth program transitions, preserving housing stability for more than 160 vulnerable households currently assisted through the Emergency Housing Voucher (EHV) program, and to allow SHA to manage its voucher portfolio efficiency while EHV funding is being exhausted. If this waiver is not granted, EHV households will experience significant confusion and barriers associated with notice periods and new application processes. For many, this is likely to result in the abrupt and preventable loss of assistance, leading to homelessness. This outcome would also place additional strain on our community's public safety and emergency shelter systems and would damage SHA's relationships with private sector landlords. Internally, SHA will face significant operational and programmatic challenges including sharply increased inquiries and hardship requests from both EHV and non-EHV households, diverting staff capacity away from core Housing Choice Voucher program administration, lease-up targets, and essential program compliance reviews.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Dane County Housing Authority (DCHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 10, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that DCHA needs the waiver to place all Emergency Housing Voucher (EHV) households on our waiting list without each household needing to apply individually to ensure that none of these households falls back into homelessness due to the coming exhaustion of EHV funds. Requiring each household to apply individually for a new type of voucher would be challenging for these families to accomplish in a timely manner. During the initial lease up, many of the households had more social supports in the community through housing navigation services that they are no longer working with. Working only with the PHA on this transition to another voucher type is likely to be confusing and cumbersome for the families to accomplish. We also have a significant number of EHV households that are headed by a person with disabilities, which could also potentially present the need for reasonable accommodations or added steps to accomplish the reapplication process and create more delays and more risk that EHV funding runs out before some of the most vulnerable households have completed the process.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Flagstaff Housing Authority (FHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 10, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that FHA currently has 23 Emergency Housing Voucher (EHV) clients. If FHA has to reach out to all 23 EHV clients to have them apply for the Housing Choice Voucher (HCV) waiting list, there is a risk that FHA would run out of EHV funds before it is able to transition all EHV families to HCV. This waiver supports uninterrupted voucher assistance for those families and removes the clientfacing burden of applying. These clients were initially referred to FHA for EHVs through the Continuum of Care; therefore, the application process itself may be new to them. If this waiver is not granted, EHV clients risk housing instability, homelessness, health complications, and pressure to move from Flagstaff. As EHV clients were referred to FHA by the Continuum of Care for particular criteria, these populations are at greater risk of homelessness, sex trafficking, and domestic violence. Threats to housing stability only exacerbates these concerns.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity</E>
                        : Tempe Housing Authority (THA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 10, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that THA has 35 households in its Emergency Housing Voucher (EHV) program. Without this waiver, these households would be required to await the next Housing Choice Voucher waiting list opening, which is infrequent and unpredictable. They would be required to complete a new application process with no guarantee of selection or preference as THA practices a lottery. Vulnerable populations 
                        <PRTPAGE P="41202"/>
                        including those with limited literacy, language access needs, or disabilities may be effectively locked out of future housing assistance due to barriers in navigating new application procedures. THA will be required to create a duplicative outreach and application effort for a narrowly defined population that has already been fully vetted by HUD and THA staff. Approval of this waiver would not create an entitlement to HCV assistance or obligate THA to issue vouchers absent available funding. It would, however, preserve a formal pathway to long-term assistance for these 35 households and allow THA to administer an orderly, equitable, and efficient wind-down of the EHV program.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of San Luis Obispo (HASLO).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         December 10, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that several of HASLO's clients in this program struggle with disabilities and other barriers to self-sufficiency. Requiring clients to go through an application process without adequate case management support would increase their risk of losing assistance due to the exhaustion of Emergency Housing Voucher (EHV) funds. Additionally, our limited staffing would be stretched very thin if they had to follow up with all EHV households and help them with the application process. This waiver will allow HASLO to ensure the greatest number of clients retain their housing
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Pinal County Housing Authority (PCHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that manually processing individual applications for each Emergency Housing Voucher (EHV) family to transition to the Housing Choice Voucher (HCV) program may result in an administrative burden and delays for PCHA. The individual application process for transitioning to the HCV program presents additional challenges for EHV families such as: language barriers, filling out complex forms and navigating communication, and digital access limitations, as many families may lack reliable internet access or the necessary skills to navigate online applications. EHV families may need help to understand the requirements, gather necessary documents, and complete the application accurately, and such assistance might not be readily available. Waiving the requirement that EHV families individually apply allows for a more efficient and timely transition and minimizes the risk of disruption in assistance.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Gila County Housing Authority (GCHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that as Emergency Housing Voucher (EHV) funding approaches expiration, requiring individual applications from EHV households would introduce delays that risk loss of assistance. To ensure continuity of housing support, GCHA proposes to amend its Administrative Plan to include a targeted preference for EHV families at risk of termination due to lack of funding. To comply with waiting list regulations, GCHA will temporarily reopen the Housing Choice Voucher (HCV) waiting list exclusively for eligible EHV families under this new preference. GCHA's HCV waiting list is currently closed and contains 240 applicants. A broad reopening could exceed administrative capacity and result in over-leasing. Moreover, requiring individual applications from EHV families would create unnecessary delays and administrative burdens, potentially preventing timely placement on the HCV waiting list.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         San Francisco Housing Authority (SFHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that SFHA currently has over 950 families in its Emergency Housing Voucher (EHV) program. SFHA is also currently in shortfall and unable to issue regular Housing Choice Vouchers (HCVs), but is still allowed, and obligated, to fill Project-Based Voucher (PBV) vacancies. SFHA is requesting this waiver to allow it to place EHV families on the HCV and PBV waiting lists. This waiver is necessary to ensure that all currently subsidized EHV families will have the opportunity to remain housed without placing any undue burden on the families. Due to the number of EHV families, 
                        <PRTPAGE P="41203"/>
                        automatically adding participants will be crucial to ensuring timely processing and preventing EHV funding from running out prior to transferring families to HCV or PBV, since current projections show EHV funding being exhausted by June 2026.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of the County of Contra Costa (HACCC)
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HACCC is requesting this waiver to prevent housing instability for EHV families. HACCC can provide fair housing access to these families, in alignment with HUD objectives to ensure that no families are displaced as a result of the depletion of EHV funding. These families remain vulnerable, unable to afford market rents for their units in Contra Costa County and will certainly return to homelessness without this waiver. Furthermore, EHV families may miss the opportunity to transition to the HCV program, especially those with barriers like disabilities, limited English proficiency, or low digital literacy leading to potential loss of assistance and increased risk of homelessness.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of the City of San Buenaventura (HACSB).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HACSB requests a waiver to allow it to place all Emergency Housing Voucher (EHV) families directly onto its Housing Choice Voucher (HCV) waiting list. HACSB has determined that requiring individual applications from EHV families would cause a delay in processing, placing these families at risk of losing assistance and homelessness due to the exhaustion of available EHV funds. Transitioning EHV participants to the HCV waiting list will prevent this gap in assistance and ensure that vulnerable households maintain continuous access to housing support.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Yolo County Housing (YCH).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that YCH has not pulled applicants from its Housing Choice Voucher (HCV) waitlist for the past two years due to being in shortfall. Although YCH's HCV program is now out of shortfall, our Two-Year Tool projections only support minimal leasing for project-based vouchers. Opening our HCV waitlist only for Emergency Housing Voucher (EHV) families will cause confusion in the community and pose the risk that EHV families may not apply to the HCV waitlist and lose out on the opportunity to transition to HCV. Further, individually processing each EHV family's waiting list application creates unnecessary administrative burdens. The increased administrative time that staff takes to process, track, and manage individual waiting list applications can delay the EHV to HCV transition time, putting participants at risk of delays or gaps in assistance. The streamlined waiver minimizes risk of errors due to processing, delays, and staff workload.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Santa Clara County Housing Authority (SCCHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that SCCHA has one of the highest rental markets in the nation. Because of these extreme housing costs, families leased under the Emergency Housing Voucher (EHV) program are at especially high risk of instability if their assistance is disrupted or if they are unable to transition seamlessly into the Housing Choice Voucher (HCV) program. Many landlords are only willing to continue participation because of the consistency of subsidy support; any disruption will result in mass lease terminations, displacement and a return to homelessness for our families. If HUD does not approve the waiver, SCCHA would need to process each EHV household individually through the HCV waiting list. This would result in significant administrative delays, duplicative workload, and increased risk of errors given the size of SCCHA's EHV portfolio. Families may face gaps in assistance or termination from the EHV program before their HCV transition is complete.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                        <PRTPAGE P="41204"/>
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of the City of Madera (HACM).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HACM requests a waiver to transition eligible Emergency Housing Voucher (EHV) families to the Housing Choice Voucher (HCV) waitlist. While HACM is currently experiencing a funding shortfall in its HCV program, this waiver would not result in immediate issuance of vouchers. Instead, it would allow EHV families, who have already been screened and served under HUD's criteria, to be placed on the HCV waitlist for future consideration as funding becomes available. If EHV families are required to reapply through the general waitlist, both agency operations and vulnerable households will face significant disruption. There is a risk that EHV families, particularly those with limited access to technology, language barriers, or trauma-related challenges, may not successfully navigate the standard waitlist process and lose their connection to long-term housing support. Operationally, HACM would be required to close out EHV assistance without a mechanism to preserve eligibility for families who remain at high risk of homelessness. This would result in duplicative administrative burden, as staff would need to reprocess applications for households that have already been vetted, housed, and supported under HUD defined criteria. It would also strain limited resources during a period of HCV shortfall, diverting attention from critical shortfall mitigation and compliance efforts.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Compton Housing Authority (CHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that CHA is requesting approval to place all Emergency Housing Voucher (EHV) families on to the Housing Choice Voucher (HCV) waiting list after establishing the appropriate preference, without requiring individual applications. This waiver is necessary because CHA does not have an open HCV waiting list. Without approval, there would be no mechanism to transition these households into the HCV program, forcing them to wait until the waiting list opens—an unpredictable process that could take years. CHA's EHV families represent highly vulnerable populations, many at risk of homelessness. Requiring them to wait for a new HCV list or to individually apply increases the chance of gaps in assistance and housing instability. CHA also has limited staff capacity and processing new HCV applications for families already verified under the EHV program would create unnecessary administrative burden and duplicate work. Finally, many EHV participants face barriers, such as disabilities, limited mobility, or lack of access to technology. Requiring new applications could unfairly disadvantage these households.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of the City of Santa Barbara (HACSB)
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that requiring the manual collection and processing of Housing Choice Voucher applications for every Emergency Housing Voucher (EHV) household would impose an unsustainable administrative burden on staff. Even with staff support, the time required to manually collect and process 80 separate applications during the final months of the EHV program would overwhelm agency capacity, particularly amid staffing shortages and program wind-down activities. The administrative capacity simply does not exist to process each case individually without diverting resources away from other critical housing services. Without this waiver, these families would face the abrupt termination of assistance, leaving them with no viable pathway to remain housed. The likely outcome would be a return to homelessness for dozens of households who only recently achieved stability through the EHV program.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Hawthorne Housing Authority (HHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HHA is requesting this waiver to allow it to place its 38 Emergency Housing Voucher (EHV) families on its Housing Choice Voucher (HCV) waiting list as an alternative to only accepting individual applications from EHV families. Without this waiver, there would be a low probability that EHV families would be able to be placed on the HCV waiting list. HHA's Administrative Plan requires that a family submit an HCV application and be selected through a randomized lottery in order to be placed on the HCV waiting list. If EHV families are required to undergo lottery selection with other applicants to the HCV program, only a 
                        <PRTPAGE P="41205"/>
                        relatively small proportion can be expected to be placed on the HCV waiting list. Further, with the EHV service fee ending on August 19, 2025, there will not be enough time to do the necessary outreach to assist EHV families with this transition.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Sarasota Housing Authority (SHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that SHA requests a waiver to allow Emergency Housing Voucher (EHV) participants to be placed directly on the HCV waiting list without requiring individual applications. This waiver is essential to ensure continuity of housing assistance for this vulnerable population and to prevent unnecessary loss of support. Requiring individual applications from each EHV household presents significant challenges. SHA is already experiencing staffing shortages and elevated caseloads. Requiring individual applications from each EHV household would force the reallocation of staff from other critical duties to manage a time-sensitive and resource-intensive process. The delay caused by requiring individual applications may result in families losing assistance due to the exhaustion of EHV funds before they transition to the Housing Choice Voucher program
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Georgia Department of Community Affairs (GDCA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that GDCA requests to automatically place Emergency Housing Voucher (EHV) participants on to its Housing Choice Voucher (HCV) waiting list without requiring individual applications. This waiver is necessary to prevent the disruption of assistance for vulnerable EHV families as program funding is exhausted. GDCA has issued over 583 EHVs across 149 counties. Many EHV participants, particularly individuals who were formerly homeless, survivors of domestic violence, or those with disabilities, face barriers to navigating the application process. Due to the geographic scale and participant volume, requiring individual applications at this stage poses a serious risk of delays, loss of assistance, and administrative breakdown. Without this waiver, it is unlikely that GDCA can compete one-on-one outreach and application follow-up in time to transition these families before EHV funds run out. GDCA is also currently operating under a projected funding shortfall and cannot absorb these households into the regular HCV program. However, GDCA can support transitioning approximately 65-67 eligible EHV households into our Mainstream program. This waiver would allow GDCA to prioritize these families for continued assistance while maintaining federal compliance and continuity of services.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         City and County of Honolulu Department of Community Services (DCS).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that DCS is requesting this waiver to allow it to place its 276 Emergency Housing Voucher (EHV) families on its Housing Choice Voucher (HCV) waiting list as an alternative to only accepting individual applications from EHV families. Without this waiver, there would be a low probability that EHV families would be able to be placed on the HCV waiting list. DCS's Administrative Plan requires that a family submit an HCV application and be selected through a randomized lottery in order to be placed on the HCV waiting list. If EHV families are required to undergo lottery selection with other applicants to the HCV program, only a relatively small proportion can be expected to be placed on the HCV waiting list. Further, with the EHV service fee ending on August 19, 2025, there will not be enough time to do the necessary outreach to assist EHV families with this transition.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Hawaii Public Housing Authority (HPHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that due to the delay caused by having to require individual applications, Emergency Housing Voucher (EHV) families would be at risk of losing assistance due to the exhaustion of EHV funds. In addition, due to the large number of families in our EHV program, it's unlikely that HPHA will be able to do the necessary outreach and follow up 
                        <PRTPAGE P="41206"/>
                        to ensure that each family is informed of their opportunity to be placed on the waiting list and is able to submit an application. Without this waiver, some EHV families may miss the opportunity to transition to the Housing Choice Voucher program, especially those with barriers like disabilities, limited English proficiency, or low digital literacy leading to potential loss of assistance and increased risk of homelessness.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Iowa City Housing Authority (ICHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that many Emergency Housing Voucher (EHV) participants face significant barriers to navigating complex administrative processes, including limited literacy, lack of technology access, and difficulty meeting in-person documentation requirements. Requiring EHV families to submit a separate Housing Choice Voucher (HCV) application creates unnecessary barriers. Without this waiver, families risk falling out of the housing continuum simply because of procedural hurdles, despite being otherwise eligible for HCV assistance. Staff would need to conduct separate outreach campaigns, track multiple intake processes, and troubleshoot application issues for families who have already been screened and determined eligible under EHV requirements. This inefficiency diverts limited administrative resources from core program functions, including lease-up support and compliance monitoring. Granting this waiver reduces duplicative administrative work for both ICHA and families.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Fayetteville Metropolitan Housing Authority (FMHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that FMHA requests this streamlined waiver to prevent housing disruption to vulnerable Emergency Housing Voucher (EHV) families, who are exiting homelessness. Delays in placing these families onto the Housing Choice Voucher waiting list could lead to loss of housing opportunities, resulting in eviction, prolonged shelter stays, regression into literal homelessness, and adverse impacts on family stability and health. The waiver facilitates a seamless transition, preserving housing continuity and supporting family well-being. Without this waiver, FMHA would experience processing delays, having to divert resources limiting staff ability to provide housing counseling, landlord engagement and rapid re-housing support. If the waiver is not granted, FMHA's ability to implement a smooth transition for EHV families as intended may be limited, which could inadvertently affect the continuity efficiency, and family stability that HUD seeks to promote
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Fargo Housing and Redevelopment Authority (FHRA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that Emergency Housing Voucher (EHV) families would need to be transferred to either the Housing Choice Voucher (HCV) or Mainstream programs with FHRA. Currently, both the HCV and Mainstream waitlists are closed with no anticipated re-opening dates. The administrative burden of FHRA opening both of our HCV and Mainstream waitlists for 28 EHV families would cause a significant impact on our operations. Applications are currently only accepted through our online portal (unless otherwise requested), and our online portal cannot differentiate which applications would come from those EHV families or from new applicants not from our EHV program. Due to FHRA's history of opening the HCV and Mainstream waitlists and demand of housing assistance in our jurisdiction, FHRA would expect to receive a significant amount of applications to process. The administrative burden to review and process the entirety of these applications, along with the possibility of those new non-EHV applications requesting a HUD-mandated informal review, staff time would be taken away from normal operations and would cause workflow to be significantly altered. This waiver would allow FHRA to establish a streamlined process for the 28 EHV families to ensure there is not a lapse in housing assistance and that those families do not receive an undue burden of stress from the situation.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Rochester Housing Authority (RHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                        <PRTPAGE P="41207"/>
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that RHA currently administers 108 Emergency Housing Choice (EHV) households. Requiring each family to submit a separate HCV waiting list application will create delays at a critical point when EHV funding is projects to sunset. The additional administrative steps would place these households at serious risk of losing housing assistance due to the exhaustion of EHV funds before their Housing Choice Voucher (HCV) application could be processed. This waiver would allow RHA to ensure a fair and consistent transition for all EHV families by placing them directly on the HCV waiting list, thereby preserving their access to long-term rental assistance. Without the waiver, the likelihood of gaps in communication or delays in application processing could disproportionately impact the most vulnerable households.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Town of Brookhaven (TOB).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that requiring each family to complete a separate Housing Choice Voucher (HCV) application creates an unnecessary administrative hurdle and risks excluding households due to challenges such as limited access to technology, literacy barriers, mobility limitations, lack of transportation, difficulty navigating complex processes, or competing demands related to employment and family care. If this waiver is not granted, the PHA will be required to create, process, and manage approximately 25 individual HCV applications from Emergency Housing Voucher (EHV) households. This would place the issuance of new vouchers from the existing HCV waiting list on hold, delaying assistance for other eligible families. A streamlined approach, where caseworkers can transition EHV households to the HCV program seamlessly during an annual or interim recertification, reduces administrative workload, avoids duplicative steps, and ensures a smoother process for both TOB and participating families.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Cincinnati Metropolitan Housing Authority (CMHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that CMHA currently has 138 Emergency Housing Voucher (EHV) participants on the program. This waiver would allow CMHA to provide all EHV families with uninterrupted assistance, reducing the potential that these families would become homeless due to the loss of funding for the EHV program. CMHA has the capacity to transition all EHV participants to HCV prior to the funds being depleted. In addition, CMHA has adopted a preference to facilitate the transition of EHV participants to the HCV program. This waiver would eliminate the administration burden for the CMHA and the anxiety for the current participants in having to submit an individual application for the HCV program.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Lucas Metropolitan Housing Authority (LMHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that LMHA requests this waiver to ensure a streamlined and orderly transition of Emergency Housing Voucher (EHV) households into the Housing Choice Voucher (HCV) program as EHV funding phases out. Without this waiver, each household would be required to individually apply through the HCV waiting list. This process would create significant administrative burden, delay assistance, and risk housing instability for vulnerable families. This waiver would allow LMHA to place all EHV families directly onto the HCV waiting list under and adopted EHV preference, ensuring continuity of assistance and preventing gaps in subsidy.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Norman Housing Authority (NHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that this waiver would take the burden off of our current Emergency Housing Voucher (EHV) participants in having to come back in and start their process over. Many EHV participants do not have transportation or the funds available to get rides to the agency to complete the paperwork and appointments to keep their voucher 
                        <PRTPAGE P="41208"/>
                        assistance. It often takes weeks to months to get voucher holders to attend a scheduled appointment. Being able to streamline participants over to the Housing Choice Voucher program, once a preference is approved, would help relieve our staff of extra paperwork and appointments and ensure that vulnerable populations continue to receive assistance.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Mid-Columbia Housing Authority (MCHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that MCHA staff will need to devote significant time to sending letters, processing applications, and repeatedly following up with Emergency Housing Voucher (EHV) participants to explain why they must reapply for housing assistance. Given our current staffing shortage, this would create a substantial operational strain. We have observed that participants often do not distinguish between our various programs, referring to them collectively as “HUD.” As a result, EHV families may not fully understand the requirement to reapply for the Housing Choice Voucher program and could inadvertently disregard reapplication notices. The waiver would minimize this confusion, reduce the burden on participants, and help prevent unintended loss of housing assistance.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of the County of Dauphin (HACD).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that by automatically transferring all Emergency Housing Voucher (EHV) participants to the Housing Choice Voucher waitlist, HACD reduces the risk of disruption in housing assistance once EHV funding ends. This approach safeguards tenants from potential gaps in support that could lead to housing instability or loss of tenancy. Additionally, a bulk transfer process allows HACD to manage program records efficiently, reducing the administrative burden on both tenants and staff. Requiring each participant to individually reapply could create unnecessary barriers, duplicative paperwork, and delays in processing. Finally, many EHV participants face significant barriers to navigating complex application processes, including language, disability, or technology access challenges. By placing all participants onto the waitlist automatically, HACD ensures equitable access and prevents eligible households from being disadvantaged due to procedural hurdles.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Municipality of Juana Diaz (JDPHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that JDPHA requests the waiver to ensure that the eight Emergency Housing Voucher (EHV) families served can maintain housing stability and do not lose their housing or assistance. The waiver will help JDPHA maintain program efficiency efforts and avoid staffing and time restraints that would otherwise be required to provide effective outreach and support with an individual application process. If the waiver is not granted, JDPHA will experience significant administrative burden and vulnerable EHV households will be at risk of losing their housing assistance due to the exhaustion of EHV funds.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314 email: 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Metropolitan Development and Housing Agency (MDHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that due to the number of families that MDHA serves, MDHA runs the risk of not being able to adequately contact and follow up with families timely to ensure a smooth transition to the Housing Choice Voucher (HCV) program. The Emergency Housing Voucher (EHV) program serves a highly vulnerable population, many of whom faced challenges in completing and providing required documentation. This waiver will ensure that families under the EHV program have the opportunity to maintain housing by creating a smooth transition to the HCV program.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                        <PRTPAGE P="41209"/>
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         San Antonio Housing Authority (SAHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that SAHA requests the waiver in order to facilitate a smooth transition for Emergency Housing Voucher (EHV) families, all of whom are vulnerable and need extra care for assistance. Without the waiver, SAHA staff would be required to spend significant time and effort supporting EHV families with an individual application process, which would lead to confusion of participants and the possibility of not meeting the deadline, or not completing the process at all. This waiver would make it easier for EHV families' successful participation in the program and avoid a lapse in their assistance.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314 email: 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Harris County Housing Authority (HCHA.)
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HCHA is requesting the waiver to ensure that the current Emergency Housing Voucher (EHV) families continue with housing assistance as needed. Having to take EHV families through another admission process will cause hardship for most families as well as causing an administrative burden on the staff and agency. Additionally, if HCHA has to transition through normal new admission processes for EHV participants, the families that live outside of HCHA's jurisdiction would have to move, causing an additional burden to those families. Without this waiver, the EHV families HCHA serves will be at risk of becoming homeless or near homeless without the assistance of housing.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Jennifer LeGros, Management Analyst, Office of Housing Voucher Program Support Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Jennifer.L.Legros@hud.gov,</E>
                         telephone (212) 542-7833.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Brazos Valley Council of Governments (BVCOG).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that BVCOG currently administers assistance to 31 Emergency Housing Choice (EHV) households. While this caseload is not large, requiring each household to submit an individual Housing Choice Voucher application introduces unnecessary risks and delays that could result in the loss of assistance. EHV families are homeless, at risk of homelessness, or fleeing domestic violence or human trafficking. Any administrative delay could result in the immediate loss of stable housing, undermining the purpose of the program. Many EHV households face barriers such as unstable housing, limited technology access, or difficulty navigating complex application processes. As a result, some households may not submit applications in time, placing them at risk of losing assistance solely due to procedural requirements.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of Utah County (HAUC).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that allowing HAUC to place all Emergency Housing Voucher (EHV) families on the HCV waiting list to receive the preference will enable us to successfully transfer those participating in the EHV program to remain housed and continue to receive assistance through the Housing Choice Voucher program. The EHV participants currently in our program are among the most vulnerable and are likely to become homeless if they cannot continue to receive housing assistance. Allowing HAUC to complete the task of adding families to the waiting list and receiving the established preference for current EHV participants will allow for a seamless transition and allow for continued assistance. If this waiver is not provided, many of the families on the EHV program will likely become homeless. These families are among the most vulnerable of all our programs and cannot complete simple tasks without constant oversight. Allowing HAUC to complete this task will eliminate the risk of homelessness.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Columbia Housing Authority (CGHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that CGHA staff will need to devote significant time to sending letters, processing applications, and repeatedly 
                        <PRTPAGE P="41210"/>
                        following up with Emergency Housing Voucher (EHV) participants to explain why they must reapply for housing assistance. Given our current staffing shortage, this would create a substantial operational strain. We have observed that participants often do not distinguish between our various programs, referring to them collectively as “HUD.” As a result, EHV families may not fully understand the requirement to reapply for the Housing Choice Voucher program and could inadvertently disregard reapplication notices. The waiver would minimize this confusion, reduce the burden on participants, and help prevent unintended loss of housing assistance.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Sauk County Housing Authority (SCHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that SCHA currently administers 10 Emergency Housing Vouchers (EHVs). Requiring individual applications would create significant administrative burden, potentially delay transitions, and risk that EHV families lose assistance due to exhaustion of program funds. If this waiver is not granted, SCHA would face administrative delays and strain due to the need to contact each EHV family, process new applications, and reopen the waiting list. This would impede timely conversion of EHV families to the Housing Choice Voucher program, creating a risk that families lose rental assistance or experience gaps in housing support. This waiver ensures smooth transition, maintains continuity of assistance for vulnerable families, and reduces unnecessary administrative burdens on our limited staff.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Huntington Housing Authority (HHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that this waiver is necessary to prevent a gap in housing assistance for Emergency Housing Voucher (EHV) families. Without this waiver, we would be forcing families who have experienced homelessness or other trauma to navigate complex individual application processes that would be burdensome and could hinder their housing stability. Forcing every EHV family to apply individually, especially since our Housing Choice Voucher waiting list is closed, can create significant, unnecessary work for our staff and risk losing track of eligible families.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Cincinnati Metropolitan Housing Authority (CMHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that CMHA currently has 138 Emergency Housing Voucher (EHV) participants on the program. This waiver would allow CMHA to provide all EHV families with uninterrupted assistance, reducing the potential that these families would become homeless due to the loss of funding for the EHV program. CMHA has the capacity to transition all EHV participants to Housing Choice Voucher (HCV) prior to the funds being depleted. In addition, CMHA has adopted a preference to facilitate the transition of EHV participants to the HCV program. This waiver would eliminate the administration burden for the CMHA and the anxiety for the current participants in having to submit an individual application for the HCV program.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 451 Seventh Street SW, Washington, DC 20410, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of the City of Yuma (HACY).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HACY currently has eight families in its Emergency Housing Voucher (EHV) program. If this waiver is not approved, HACY would have to re-open the waiting list solely to transition eight EHV families to its Housing Choice Voucher (HCV) waiting list. This would create administrative burden not only on HACY staff but also our community. Although HACY may establish specific criteria and describe the tailored preference with great detail, the community consistently questions when will the HCV waiting list be re-opened. The community may not fully comprehend why such preference is being offered only to current recipients under the EHV program. Additionally, HACY currently does not have HCV vouchers available in order to transition families from the EHV program this current year. However, should the 
                        <PRTPAGE P="41211"/>
                        waiver be accepted, HACY would focus and align to house the EHV families with an HCV no later than June 2026, prior to EHV funds running out. This waiver is necessary to ensure that EHV participants who were originally identified as families experiencing or at risk of homelessness are not placed at risk of losing assistance due to the time limit of the EHV funding.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of the County of Riverside (HACR).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that this waiver is needed because there would be a delay by having to require individual applications from Emergency Housing Voucher (EHV) families and would place the EHV families at risk of losing assistance due to the exhaustion of EHV funds. With this waiver, HACR will be able to ensure that all eligible EHV assisted families will be properly registered on the Housing Choice Voucher (HCV) waiting list in order to be selected for the transition over to a regular HCV. Without this waiver, there can be the possibility that not all eligible EHV families are registered on our HCV waiting list and when the EHV funding is exhausted this can lead to homelessness for the EHV families that failed to register on our HCV waiting list.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of the City of Napa (HACN).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HACN is in shortfall and operating under leasing restrictions. Issuance of new vouchers is restricted, and every subsidy must be maximized to preserve tenancy for vulnerable families. Manually processing individual Emergency Housing Voucher (EHV)-to-Housing Choice Voucher applications during shortfall would divert limited staff capacity and delay critical decisions about voucher use. This waiver would help ensure that EHV families do not experience a break in assistance due to administrative processes, especially as service fees sunset and EHV funding draws down.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Garden Grove Housing Authority (GGHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that if this waiver is not granted, many Emergency Housing Voucher (EHV) families will face significant barriers in transitioning to the Housing Choice Voucher (HCV) program. The current process requires each household to complete an individual application, which creates obstacles for participants with disabilities, limited English proficiency, or low digital literacy. These households are more likely to experience delays or errors in the application process, which may prevent them from being placed on the HCV waiting list in time. Without streamlined access, some of the most vulnerable families risk losing critical housing assistance once EHV funding sunsets at the end of 2026. The consequences would be severe: families who lose assistance are at heightened risk of housing instability, displacement, or homelessness.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Roseville Housing Authority (RHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that RHA is currently assisting 38 Emergency Housing Voucher (EHV) families. Coordinating individual outreach and processing separate applications for each household would create delays that jeopardize housing stability. Many of these families are at risk of losing housing assistance due to the exhaustion of EHV funding, and the waiver would allow RHA to act swiftly and equitably by placing all eligible households directly on to the Housing Choice Voucher waiting list. This waiver would also allow RHA to transition eligible EHV families to the Mainstream waiting list without requiring individual applications. Requiring individual applications introduces barriers for vulnerable populations—including those with disabilities, limited English proficiency, or unstable living conditions. Families currently receiving EHV assistance may face gaps in support or complete loss of housing if they are unable to navigate the application process in time.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower 
                        <PRTPAGE P="41212"/>
                        Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Osceola County Housing Agency (OCHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that as Emergency Housing Voucher (EHV) funds are projected to run out by the end of 2026, time is critical. Delays caused by requiring individual applications may prevent vulnerable families from being successfully transitioned before funding ends. Without this waiver, some EHV families may miss the opportunity to transition to the Housing Choice Voucher program, especially those with barriers like disabilities, limited English proficiency, or low digital literacy leading to potential loss of assistance and increased risk of homelessness.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Atlanta Housing Authority (AHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that AHA's current waiting list has more than 20,000 households. Without a waiver, AHA will need to re-open the waiting list and alert the public about the opening process. This will create significant confusion among the public and uncertainty about the continuity of housing assistance for Emergency Housing Choice (EHV) families. Even the mentioning of the re-opening of the waiting list will create significant media and public attention in Atlanta. Moreover, EHV families would have to re-apply for assistance rather than being placed on the waiting list automatically, increasing the burden and possible stressful impact on EHV households.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Indianapolis Housing Agency (IHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that many Emergency Housing Voucher (EHV) households face significant challenges, including housing instability, limited access to technology, and difficulty obtaining required documentation. Requiring EHV families to reapply would be duplicative and unnecessarily burdensome for both the agency and the families. The lack of a streamlined transition would disrupt support, strain limited agency resources, and jeopardize the hard-earned stability of households who are already in good standing. Forcing these vulnerable families to restart the application process could result in loss of assistance due to procedural barriers—despite already being eligible. Vulnerable families who have already made progress toward stability could face renewed risk of homelessness due to avoidable administrative barriers. Granting this waiver ensures that no family falls through the cracks during the transition. If this waiver is not granted, the consequences could be especially damaging in Indianapolis, where housing insecurity remains a significant and ongoing challenge.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Stark Metropolitan Housing Authority (SMHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that SMHA currently administers 30 Emergency Housing Vouchers (EHVs). SMHA's Housing Choice Voucher (HCV) waiting list is currently closed with 556 applicants and must be fully exhausted before reopening. Opening the waiting list would require extensive planning and public notice, which would take considerable time and divert staff from critical operations, such as inspections, reexaminations, and HAP processing. Approval of this waiver will allow SMHA to seamlessly place EHV households on the HCV waiting list with a preference and process them for continued assistance without reopening the list. SMHA will ensure that its Administrative Plan reflects the Board-approved preference and applicable public notice procedures. If this waiver is not granted, EHV families could experience a lapse in assistance and potential eviction, disrupting housing stability and significantly risking the increase of homelessness.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Montgomery County Housing Authority (MCHA).
                        <PRTPAGE P="41213"/>
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HUD approval would benefit MCHA by eliminating administrative burden related to advertising, processing applications, computer entry of application, and confusion for participants. MCHA would like to move forward as soon as possible to potentially issue vouchers beginning in 2026. This waiver will assist MCHA with needed actions in 2026 to avoid any interruption of subsidy for our existing participants currently receiving Emergency Housing Voucher funding. Without this waiver, MCHA anticipates many participants will lose subsidy and become homeless again.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of the County of Chester (HACC).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that manually collecting and processing Housing Choice Voucher (HCV) applications from every Emergency Housing Voucher (EHV) household would place an unsustainable burden on staff, particularly at a time when the agency is winding down EHV, preparing for funding reductions, or operating under staff shortages. As EHV funds are projected to run out by the end of 2026, time is critical. Delays caused by requiring individual applications may prevent vulnerable families from being successfully transitioned before funding ends. Further, some EHV families may miss the opportunity to transition to the HCV program, especially those with barriers like disabilities, limited English proficiency, or low digital literacy, leading to potential loss of assistance and increased risk of homelessness.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of Indiana County (HAIC).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HAIC is requesting a waiver to place all Emergency Housing Voucher (EHV) families on the Housing Choice Voucher (HCV) waiting list so that each family does not have to individually apply for the HCV program, which could potentially result in the loss or interruption of their current housing. HAIC does not have the manpower to work with each household individually to make sure that they re-apply and complete all paperwork. If this waiver is not approved, it would put EHV families at risk of losing their housing.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Providence Housing Authority (PHA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that this waiver would enable the expedited selection of Emergency Housing Voucher (EHV) participants from the HCV waiting list, thereby minimizing interruptions in housing assistance and reducing the risk of homelessness. If this waiver is not provided, it will create a significant administrative burden by requiring PHA to contact each EHV participant individually. This could delay the selection process from the Housing Choice Voucher waiting list, increasing the risk of homelessness and disrupting the existing housing stability of the participants.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Municipality of Utuado.
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that this waiver would help prevent delays caused by having to require individual applications from Emergency Housing Voucher (EHV) families and help ensure that all EHV families receive assistance. EHV families face barriers, such as lack of cell phone service or email or mobile devices that would make it difficult to conduct the necessary outreach and follow-up to ensure that each family is informed of their opportunity to submit an application and be placed on the Housing Choice Voucher (HCV) waiting list. Without this waiver, EHV families who were unable to submit an application to be placed on the HCV waiting list would become homeless.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                        <PRTPAGE P="41214"/>
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         South Carolina State Housing and Finance Development Authority (SCSHFDA).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that SCSHFDA is currently servicing over 200 Emergency Housing Voucher (EHV) families. It would be an administrative burden for the agency to advertise and open the waitlist for currently assisted EHV families to apply as a preference. EHV families would be at risk of becoming homeless again if they fail to apply. We are currently understaffed, and it would be an administrative burden to pull staff away from other current daily duties to manage the waitlist requirements, for advertising, and accepting applications from current EHV families.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Michelle Daniels, Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Michelle.Daniels@hud.gov,</E>
                         telephone (202) 402-6051.
                    </P>
                    <P>
                        • 
                        <E T="03">Regulation:</E>
                         24 CFR 982.204, 24 CFR 982.206.
                    </P>
                    <P>
                        <E T="03">Nature of Requirement:</E>
                         24 CFR 982.204 provides criteria that must be included during the administration of a Public Housing Agency waiting list. 24 CFR 982.206 provides criteria for the opening and closing of said waiting lists.
                    </P>
                    <P>
                        <E T="03">Project/Activity:</E>
                         Housing Authority of the City of Brownsville (HACB).
                    </P>
                    <P>
                        <E T="03">Granted By:</E>
                         Benjamin Hobbs, Principal Deputy Assistant Secretary for Public and Indian Housing.
                    </P>
                    <P>
                        <E T="03">Date Granted:</E>
                         November 21, 2025.
                    </P>
                    <P>
                        <E T="03">Reason Waived:</E>
                         HUD grants the waiver on the basis of good cause, citing that HACB currently serves 47 Emergency Housing Voucher (EHV) families. Due to the delay caused by having to require individual applications from EHV families, EHV families would be at risk of losing assistance due to the exhaustion of EHV funds. It is unlikely that the HACB will be able to do the necessary outreach and follow up to ensure that each family is informed of their opportunity to be placed on the Housing Choice Voucher waiting list and is able to submit an application, which would risk EHV families losing assistance due to the exhaustion of EHV funds.
                    </P>
                    <P>
                        <E T="03">Contact:</E>
                         Celia Carpentier, Senior Housing Program Specialist, Housing Voucher Management and Operations Division, Office of Public and Indian Housing, Department of Housing and Urban Development, 2415 Eisenhower Avenue, Alexandria, VA 22314, email: 
                        <E T="03">Celia.Y.Carpentier@hud.gov,</E>
                         telephone (202) 402-7093.
                    </P>
                </SUPLINF>
                <FRDOC>[FR Doc. 2026-13539 Filed 7-2-26; 8:45 am]</FRDOC>
                <BILCOD>BILLING CODE 4210-67-P</BILCOD>
            </NOTICE>
        </NOTICES>
    </NEWPART>
    <VOL>91</VOL>
    <NO>127</NO>
    <DATE>Monday, July 6, 2026</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="41215"/>
            <PARTNO>Part III</PARTNO>
            <AGENCY TYPE="P"> Department of Health and Human Services</AGENCY>
            <SUBAGY> Centers for Medicare &amp; Medicaid Services</SUBAGY>
            <HRULE/>
            <CFR>42 CFR Parts 405, 410, 414, et al.</CFR>
            <TITLE>Calendar Year 2027 Home Health Prospective Payment System (HH PPS) Rate Update; Requirements for the HH Quality Reporting Program and the Expanded HH Value-Based Purchasing Model; Medicare Provider Enrollment, Durable Medical Equipment (DME), and DME, Prosthetics, Orthotics, and Supplies (DMEPOS) Policies; Proposed Rule</TITLE>
        </PTITLE>
        <PRORULES>
            <PRORULE>
                <PREAMB>
                    <PRTPAGE P="41216"/>
                    <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                    <SUBAGY>Centers for Medicare &amp; Medicaid Services</SUBAGY>
                    <CFR>42 CFR Parts 405, 410, 414, 422, 423, 424, 484, and 498</CFR>
                    <DEPDOC>[CMS-1844-P]</DEPDOC>
                    <RIN>RIN 0938-AV80</RIN>
                    <SUBJECT>Calendar Year 2027 Home Health Prospective Payment System (HH PPS) Rate Update; Requirements for the HH Quality Reporting Program and the Expanded HH Value-Based Purchasing Model; Medicare Provider Enrollment, Durable Medical Equipment (DME), and DME, Prosthetics, Orthotics, and Supplies (DMEPOS) Policies</SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Centers for Medicare &amp; Medicaid Services (CMS), Department of Health and Human Services (HHS).</P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Proposed rule.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>This proposed rule would set forth routine updates to the Medicare home health payment rates in accordance with existing statutory and regulatory requirements. In addition, this proposed rule discusses the behavior adjustment and proposes a temporary behavior adjustment and proposes to recalibrate the case-mix weights and update the functional impairment levels; comorbidity subgroups; and low-utilization payment adjustment (LUPA) thresholds for CY 2027. Additionally, this proposed rule discusses the provision of home health palliative care services and includes a request for information (RFI) on a home health specific wage index. This rule would also propose changes to the Home Health Quality Reporting Program (HH QRP) and summarizes potential initiatives to improve alignment between the HH QRP and expanded Home Health Value Based Purchasing (HHVBP) Model. Lastly, the rule would—clarify the application of the DMEPOS face-to-face encounter requirements for the replacement of DMEPOS items; make changes to the provider and supplier enrollment requirements; make changes regarding DME benefit expansion for infusion pumps and drugs; and discuss collection of information requirement changes regarding the DMEPOS Competitive Bidding Program (CBP) country of origin.</P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>
                            To be assured consideration, comments must be received at one of the addresses provided in the 
                            <E T="02">ADDRESSES</E>
                             section, no later than 5 p.m. EDT on August 31, 2026.
                        </P>
                    </EFFDATE>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P>In commenting, please refer to file code CMS-1844-P. Because of staff and resource limitations, we cannot accept comments by facsimile (FAX) transmission.</P>
                        <P>Comments, including mass comment submissions, must be submitted in one of the following three ways (please choose only one of the ways listed):</P>
                        <P>
                            1. 
                            <E T="03">Electronically.</E>
                             You may (and we encourage you to) submit electronic comments on this regulation to 
                            <E T="03">https://www.regulations.gov/docket/CMS-2026-XXXX.</E>
                             Follow the instructions under the “submit a comment” tab.
                        </P>
                        <P>
                            2. 
                            <E T="03">By regular mail.</E>
                             You may mail written comments to the following address ONLY: Centers for Medicare &amp; Medicaid Services, Department of Health and Human Services, Attention: CMS-1844-P, P.O. Box 8013, Baltimore, MD 21244-8013.
                        </P>
                        <P>Please allow sufficient time for mailed comments to be received before the close of the comment period.</P>
                        <P>
                            3. 
                            <E T="03">By express or overnight mail.</E>
                             You may send written comments via express or overnight mail to the following address ONLY: Centers for Medicare &amp; Medicaid Services, Department of Health and Human Services, Attention: CMS-1844-P, Mail Stop C4-26-05, 7500 Security Boulevard, Baltimore, MD 21244-1850.
                        </P>
                        <P>
                            For information on viewing public comments, we refer readers to the beginning of the 
                            <E T="02">SUPPLEMENTARY INFORMATION</E>
                             section.
                        </P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P/>
                        <P>
                            For general information about the Home Health Prospective Payment System (HH PPS), send your inquiry via email to 
                            <E T="03">HomeHealthPolicy@cms.hhs.gov.</E>
                        </P>
                        <P>
                            For information about the Home Health Quality Reporting Program (HH QRP), send your inquiry via email to 
                            <E T="03">homehealthqualityquestions@cms.hhs.gov.</E>
                        </P>
                        <P>
                            For more information about the expanded Home Health Value-Based Purchasing (HHVBP) Model, please visit the Expanded HHVBP Model web page at 
                            <E T="03">https://www.cms.gov/priorities/innovation/innovation-models/expanded-home-health-value-based-purchasing-model</E>
                             or send your inquiry via email to 
                            <E T="03">HHVBPquestions@cms.hhs.gov.</E>
                        </P>
                        <P>Nancy Allert (410) 786-4317, Jennifer Phillips (410) 786-1023, Olufemi Shodeke (410) 786-1649, Misty Whitaker (410) 786-4975, for Durable Medical Equipment, Prosthetics, Orthotics, and Supplies (DMEPOS) Encounter Requirements for Identical Replacement Items. Frank Whelan (410) 786-1302, for Medicare provider and supplier enrollment and DMEPOS accreditation.</P>
                        <P>
                            For more information about the DME Benefit Expansion for Infusion Pumps and Drugs, send your inquiry via email to 
                            <E T="03">DMEPOS@cms.hhs.gov.</E>
                        </P>
                        <P>Austin Gutowski, (410) 786-1643, for DME Competitive Bidding Program—Country of Origin.</P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P/>
                    <P>
                        <E T="03">Inspection of Public Comments:</E>
                         All comments received before the close of the comment period are available for viewing by the public, including any personally identifiable or confidential business information that is included in a comment. We post all comments received before the close of the comment period on the following website as soon as possible after they have been received: 
                        <E T="03">https://www.regulations.gov/.</E>
                         Follow the search instructions on that website to view public comments.
                    </P>
                    <P>
                        <E T="03">Plain Language Summary:</E>
                         In accordance with 5 U.S.C. 553(b)(4), a plain language summary of this rule may be found at 
                        <E T="03">https://www.regulations.gov/.</E>
                    </P>
                    <HD SOURCE="HD1">I. Executive Summary</HD>
                    <HD SOURCE="HD2">A. Purpose and Legal Authority</HD>
                    <HD SOURCE="HD3">1. Home Health Prospective Payment System (HH PPS)</HD>
                    <P>
                        As required under section 1895(b) of the Social Security Act (the Act), this proposed rule would update the CY 2027 Medicare payment rates for home health agencies (HHAs). In this proposed rule, we include an analysis of home health utilization, as well as analysis of the difference between assumed versus actual behavior change on estimated aggregate expenditures for home health payments as a result of the change in the unit of payment to 30 days and the implementation of the Patient Driven Groupings Model (PDGM) case-mix adjustment methodology. This proposed rule also discusses the permanent adjustments applied in previous years and proposes a temporary adjustment to the CY 2027 home health base payment rate. In addition, this rule proposes to recalibrate the PDGM case-mix weights and to update the low-utilization payment adjustment (LUPA) thresholds, functional impairment levels, and comorbidity adjustment subgroups under sections 1895(b)(4)(A)(i) and (b)(4)(B) of the Act for 30-day periods of care in CY 2027. This proposed rule proposes to update the CY 2027 fixed-dollar loss (FDL) ratio for outlier payments (so that outlier payments as a percentage of estimated total payments are projected not to exceed 2.5 percent, 
                        <PRTPAGE P="41217"/>
                        as required by section 1895(b)(5)(A) of the Act).
                    </P>
                    <P>Additionally, this rule discusses provision of palliative care services under the Medicare home health benefit and includes a request for information (RFI) regarding the construction of a home health specific wage index.</P>
                    <HD SOURCE="HD3">2. Home Health (HH) Quality Reporting Program (QRP)</HD>
                    <P>In accordance with the statutory authority at section 1895(b)(3)(B)(v) of the Act, we are proposing updated quality reporting policies. First, we summarize potential initiatives to improve alignment between the HH QRP and expanded HHVBP Model. We also propose to revise the HH QRP data submission deadlines beginning with the CY 2027 HH QRP. We also propose to revise the HH QRP OASIS and HHCAHPS Annual Payment Update (APU) reporting timeframe to report a calendar year of data (January 1 through December 31). We propose some revisions to regulatory text in support of rule proposals and to improve digital transfer of information during the reconsiderations process. Finally, we are soliciting public comments on one Request for Information (RFI) on future measure concepts for the HH QRP.</P>
                    <HD SOURCE="HD3">3. Expanded Home Health Value-Based Purchasing (HHVBP) Model</HD>
                    <P>We are not proposing any expanded HHVBP Model-specific policy changes in this proposed rule. We have included a brief summary of the Model with context relevant to potential alignment between the HH QRP and the expanded HHVBP Model.</P>
                    <HD SOURCE="HD3">4. Durable Medical Equipment, Prosthetics, Orthotics, and Supplies (DMEPOS) Encounter Requirements for Identical Replacement Items</HD>
                    <P>We propose clarifying the application of the DMEPOS face-to-face encounter requirements, as outlined in 42 CFR 410.38, and the related documentation necessary to support the replacement of DMEPOS items. We do not believe it necessary to require an additional in-depth beneficiary examination to “gather[ ] subjective and objective information associated with diagnosing, treating, or managing a clinical condition for which the DMEPOS is ordered” for replacement items. Such information should be recorded when the beneficiary is initially assessed and receives the item, and the practitioner should only write replacement orders for beneficiaries with ongoing medical need for the item(s). Therefore, we propose that an additional face-to-face encounter within the 6 months preceding an order/prescription for replacement of a DMEPOS item will not be required per 42 CFR 410.38. We clarify that for purposes of 42 CFR 410.38(d)(2), a “replacement” refers to the provision of an item that replaces an item falling under the same Healthcare Common Procedure Coding System (HCPCS) code; it does not include those situations involving the provision of a different item, for example, because of a change in medical condition.</P>
                    <HD SOURCE="HD3">5. Provider Enrollment and DMEPOS Accreditation</HD>
                    <P>Consistent with section 1866(j) of the Act, we are proposing a number of Medicare provider enrollment provisions to strengthen and clarify certain aspects of the provider enrollment process. These include but are not limited to: (1) adding grounds for denying or revoking a provider's or supplier's Medicare enrollment; and (2) expanding the reasons for which CMS can apply a retroactive effective date for provider and supplier revocations. These changes are necessary to help ensure that payments are made only to qualified providers and suppliers, which we believe would assist in protecting the Trust Funds and Medicare beneficiaries.</P>
                    <P>We are also proposing several minor revisions to our DMEPOS accreditation provisions in § 424.58, such as clarifying certain timeframes by which DMEPOS accreditation organizations must report data to CMS. We believe these revisions would help improve the efficiency of the DMEPOS accreditation process.</P>
                    <HD SOURCE="HD3">6. Durable Medical Equipment (DME) Benefit Expansion for Infusion Pumps and Drugs</HD>
                    <P>In section V.C. of this proposed rule, we propose to make changes to the Medicare Part B definition of DME at 42 CFR 414.202 to implement amendments made to the definition of DME at section 1861(n) of the Act by section 6222(a) of the Consolidated Appropriations Act, 2026 (CAA, 2026), expanding the scope of the benefit for DME to include certain external infusion pumps and associated home infusion drugs or other associated supplies. The legal authority for this proposed rule is provided by section 1861(n) of the Act, as amended by section 6222(a) of the CAA, 2026, and section 1871 of the Act.</P>
                    <HD SOURCE="HD3">7. DMEPOS Competitive Bidding Program—Country of Origin</HD>
                    <P>We discuss requesting to revise the DMEPOS Competitive Bidding Program (CBP) information collection under Office of Management and Budget (OMB) Control Number 0938-1408 (CMS-10744) to require DMEPOS CBP contract suppliers to report the country of origin for the lead items furnished during the contract's period of performance. This information will allow beneficiaries and interested parties to learn where the DMEPOS item originated, if interested.</P>
                    <HD SOURCE="HD2">B. Summary of the Provisions of This Proposed Rule</HD>
                    <HD SOURCE="HD3">1. Home Health Prospective Payment System (HH PPS)</HD>
                    <P>In section II.B.1. of this proposed rule, we provide monitoring and data analysis on the PDGM utilization.</P>
                    <P>In section II.C.1. of this proposed rule, we discuss the permanent behavior adjustment and propose a temporary adjustment to the base payment rate under the HH PPS.</P>
                    <P>In section II.D. of this proposed rule, we propose to recalibrate the CY 2027 PDGM case-mix weights and to update the low-utilization payment adjustment (LUPA) thresholds, functional impairment levels, and comorbidity adjustment subgroups.</P>
                    <P>In section II.E. of this proposed rule, we propose to update the home health wage index. We also propose to update the CY 2027 national, standardized 30-day period payment rates and the CY 2027 national per-visit payment amounts by the home health payment update percentage. Additionally, this rule proposes the CY 2027 fixed dollar loss (FDL) ratio to ensure that aggregate outlier payments are projected not to exceed 2.5 percent of the total aggregate payments, as required by section 1895(b)(5)(A) of the Act.</P>
                    <P>In section II.F. of this proposed rule, we discuss the provision of palliative care services under the Medicare home health benefit.</P>
                    <P>In section II.G. of this proposed rule, we include a request for information (RFI) on the construction of a home health specific wage index.</P>
                    <HD SOURCE="HD3">2. Home Health Quality Reporting Program (HH QRP)</HD>
                    <P>In section III.D. of this proposed rule, we summarize potential initiatives to improve alignment between the HH QRP and expanded HHVBP Model.</P>
                    <P>In section III.E. of this proposed rule, we are proposing to revise the HH QRP data submission deadlines beginning with the CY 2027 HH QRP.</P>
                    <P>
                        We are also proposing to revise the HH QRP OASIS and HHCAHPS Annual Payment Update (APU) reporting timeframe to report a calendar year of data (January 1 through December 31). Additionally, we propose some 
                        <PRTPAGE P="41218"/>
                        revisions to regulatory text in support of rule proposals or to improve digital transfer of information during the reconsiderations process.
                    </P>
                    <P>In section III.F. of this proposed rule, we are soliciting public comments on one Request for Information (RFI) on future measure concepts for the HH QRP.</P>
                    <HD SOURCE="HD3">3. Expanded Home Health Value Based Purchasing (HHVBP) Model</HD>
                    <P>In section IV. of this proposed rule, we summarize the expanded HHVBP Model. We are not proposing any expanded HHVBP Model-specific changes in this proposed rule. We have included a brief summary of the Model with context relevant to potential alignment between the HH QRP and expanded HHVBP Model.</P>
                    <HD SOURCE="HD3">4. DMEPOS Requirements for Identical Replacement Items</HD>
                    <P>In section V.A. of this proposed rule, we would clarify that while an order would continue to be required for replacement of DMEPOS items, a new face-to-face encounter would not need to occur to support payment for these DMEPOS items.</P>
                    <HD SOURCE="HD3">5. Provider Enrollment and DMEPOS Accreditation</HD>
                    <P>We are proposing a number of Medicare provider enrollment provisions to strengthen and clarify certain aspects of the provider enrollment process. These include, but are not limited to, the following:</P>
                    <P>• Adding grounds for denying or revoking a provider's or supplier's Medicare enrollment.</P>
                    <P>• Expanding the reasons for which CMS can apply a retroactive effective date for provider and supplier revocations.</P>
                    <P>• CMS can currently impose a reapplication bar of up to 10 years if the provider or supplier is denied enrollment for submitting false or misleading information on or with their enrollment application. (This means they cannot reapply to Medicare for up to 10 years.) We propose to expand this to permit a reapplication bar regardless of the denial reason.</P>
                    <P>We believe these revisions would help keep unqualified providers and suppliers out of the Medicare program, which, in turn would prevent improper Medicare payments to such parties.</P>
                    <P>We also propose several minor changes to our DMEPOS accreditation provisions in § 424.58, such as proposing a timeframe by which an accrediting organization must report suspected fraud, waste, or abuse to CMS. We believe these changes would help improve the DMEPOS accreditation program's efficiency.</P>
                    <HD SOURCE="HD3">6. DME Benefit Expansion for Infusion Pumps and Drugs</HD>
                    <P>In section V.C. of this proposed rule, we propose to revise the definition of DME at 42 CFR 414.202 to implement section 6222(a) of the CAA, 2026 by providing that certain external infusion pumps, associated home infusion drugs, or other associated supplies are treated as meeting the “appropriate for use in the home” requirement when specified statutory criteria are satisfied.</P>
                    <HD SOURCE="HD3">7. DMEPOS Competitive Bidding Program—Country of Origin</HD>
                    <P>In section VI. of this proposed rule, we discuss our request to revise the collection currently approved under OMB Control Number 0938-1408 (CMS-10744) to collect from DMEPOS CBP contract suppliers the country of origin for the lead items furnished during the DMEPOS CBP contract's period of performance.</P>
                    <P>As done historically with the product information reported on Form C by a DMEPOS CBP contract supplier, the reported country of origin information would be populated in the Medicare Supplier Directory for the contract supplier during the contract period of performance.</P>
                    <HD SOURCE="HD2">C. Summary of the Regulatory Impact Analysis</HD>
                    <BILCOD>BILLING CODE 4169-69-P</BILCOD>
                    <GPH SPAN="3" DEEP="341">
                        <PRTPAGE P="41219"/>
                        <GID>EP06JY26.021</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="147">
                        <GID>EP06JY26.022</GID>
                    </GPH>
                    <BILCOD>BILLING CODE 4169-69-C</BILCOD>
                    <HD SOURCE="HD1">II. Home Health Prospective Payment System</HD>
                    <HD SOURCE="HD2">A. Overview of the Home Health Prospective Payment System</HD>
                    <HD SOURCE="HD3">1. Statutory Background</HD>
                    <P>
                        Section 1895(b)(1) of the Act requires the Secretary to establish a Home Health Prospective Payment System (HH PPS) for all costs of home health services paid under Medicare. Section 1895(b)(2)(A) of the Act requires that, in defining a prospective payment amount, the Secretary shall consider an appropriate unit of service and the number, type, and duration of visits provided within that unit, potential changes in the mix of services provided within that unit and their cost, and a general system design that provides for continued access to quality services. In accordance with the statute, as amended by the Balanced Budget Act of 1997 (BBA) (Pub. L. 105-33), we issued a final rule which appeared in the July 3, 2000, 
                        <E T="04">Federal Register</E>
                         (65 FR 41128) to implement the HH PPS legislation.
                    </P>
                    <P>
                        Section 5201(c) of the Deficit Reduction Act of 2005 (DRA) (Pub. L. 109-171, enacted February 8, 2006) added new section 1895(b)(3)(B)(v) to the Act, requiring home health agencies (HHAs) to submit data for purposes of measuring health care quality, and linking the quality data submission to the annual applicable home health payment update percentage increase. This data submission requirement is applicable for CY 2007 and each subsequent year. Pursuant to section 1895(b)(3)(B)(v)(I) of the Act, if an HHA does not submit quality data, the home health market basket percentage increase is reduced by 2 percentage 
                        <PRTPAGE P="41220"/>
                        points. In the November 9, 2006, 
                        <E T="04">Federal Register</E>
                         (71 FR 65935), we issued a final rule to implement the pay-for-reporting requirement of the DRA, which was codified at § 484.225(h) and (i) in accordance with the statute. The pay-for-reporting requirement was implemented on January 1, 2007.
                    </P>
                    <P>Section 51001(a)(1)(B) of the Bipartisan Budget Act of 2018 (BBA of 2018) (Pub. L. 115-123) amended section 1895(b) of the Act to require a change to the home health unit of payment to 30-day periods beginning January 1, 2020. Section 51001(a)(2)(A) of the BBA of 2018 added a new subclause (iv) under section 1895(b)(3)(A) of the Act, requiring the Secretary to calculate a standard prospective payment amount (or amounts) for 30-day units of service furnished that end during the 12-month period beginning January 1, 2020, in a budget neutral manner, such that estimated aggregate expenditures under the HH PPS during CY 2020 are equal to the estimated aggregate expenditures that otherwise would have been made under the HH PPS during CY 2020 in the absence of the change to a 30-day unit of service. Section 1895(b)(3)(A)(iv) of the Act requires that the calculation of the standard prospective payment amount (or amounts) for CY 2020 be made before the application of the annual update to the standard prospective payment amount as required by section 1895(b)(3)(B) of the Act.</P>
                    <P>Additionally, section 1895(b)(3)(A)(iv) of the Act requires that in calculating the standard prospective payment amount (or amounts), the Secretary must make assumptions about behavior changes that could occur as a result of the implementation of the 30-day unit of service under section 1895(b)(2)(B) of the Act and case-mix adjustment factors established under section 1895(b)(4)(B) of the Act. Section 1895(b)(3)(A)(iv) of the Act further requires the Secretary to provide a description of the behavior assumptions made in notice and comment rulemaking. CMS finalized these behavior assumptions in the CY 2019 HH PPS final rule with comment period (83 FR 56461).</P>
                    <P>Section 51001(a)(2)(B) of the BBA of 2018 also added a new subparagraph (D) to section 1895(b)(3) of the Act. Section 1895(b)(3)(D)(i) of the Act requires the Secretary annually to determine the impact of differences between assumed behavior changes, as described in section 1895(b)(3)(A)(iv) of the Act, and actual behavior changes on estimated aggregate expenditures under the HH PPS with respect to years beginning with 2020 and ending with 2026. Section 1895(b)(3)(D)(ii) of the Act requires the Secretary, at a time and in a manner determined appropriate, through notice and comment rulemaking, to provide for one or more permanent increases or decreases to the standard prospective payment amount (or amounts) for applicable years, on a prospective basis, to offset for such increases or decreases in estimated aggregate expenditures, as determined under section 1895(b)(3)(D)(i) of the Act. Additionally, section 1895(b)(3)(D)(iii) of the Act requires the Secretary, at a time and in a manner determined appropriate, through notice and comment rulemaking, to provide for one or more temporary increases or decreases to the payment amount for a unit of home health services for applicable years, on a prospective basis, to offset for such increases or decreases in estimated aggregate expenditures, as determined under section 1895(b)(3)(D)(i) of the Act. Such a temporary increase or decrease shall apply only with respect to the year for which such temporary increase or decrease is made, and the Secretary shall not take into account such a temporary increase or decrease in computing the payment amount for a unit of home health services for a subsequent year. Finally, section 51001(a)(3) of the BBA of 2018 amends section 1895(b)(4)(B) of the Act by adding a new clause (ii) to require the Secretary to eliminate the use of therapy thresholds in the case-mix system for CY 2020 and subsequent years.</P>
                    <P>Division FF, section 4136 of the Consolidated Appropriations Act, 2023 (CAA, 2023) (Pub. L. 117-328) amended section 1834(s)(3)(A) of the Act to require that, beginning with 2024, the separate payment for furnishing negative pressure wound therapy (NPWT) be for just the device and not for nursing and therapy services. Payments for nursing and therapy services are to be included as part of payments under the HH PPS. The separate payment for 2024 was required to be equal to the supply price used to determine the relative value for the service under the Medicare Physician Fee Schedule (as of January 1, 2022) for the applicable disposable device updated by the percentage increase in the Consumer Price Index for All Urban Consumers (CPI-U). The separate payment for 2025 and each subsequent year is to be the payment amount for the previous year updated by the percentage increase in the CPI-U (United States city average) for the 12-month period ending in June of the previous year reduced by the productivity adjustment as described in section 1886(b)(3)(B)(xi)(II) of the Act for such year. The CAA, 2023 also added section 1834(s)(4) of the Act to require that beginning with 2024, as part of submitting claims for the separate payment, the Secretary shall accept, and process claims submitted using the type of bill that is most commonly used by home health agencies to bill services under a home health plan of care.</P>
                    <HD SOURCE="HD3">2. Current System for Payment of Home Health Services</HD>
                    <P>For home health periods of care beginning on or after January 1, 2020, Medicare makes payment under the HH PPS on the basis of a national, standardized 30-day period payment rate that is adjusted for case-mix and area wage differences in accordance with section 51001(a)(1)(B) of the BBA of 2018. The national, standardized 30-day period payment rate includes payment for the six home health disciplines (skilled nursing, home health aide, physical therapy, speech-language pathology, occupational therapy, and medical social services). Payment for non-routine supplies (NRS) is also part of the national, standardized 30-day period rate. Durable medical equipment (DME) provided as a home health service, as defined in section 1861(m)(5) of the Act, is paid the fee schedule amount or is paid through the competitive bidding program and such payment is not included in the national, standardized 30-day period payment amount. Additionally, the 30-day period payment rate does not include payment for certain injectable osteoporosis drugs and disposable negative pressure wound therapy (dNPWT) devices, but such drugs and devices must be billed by the HHA while a patient is under a home health plan of care, as the law requires separate consolidated billing of certain osteoporosis drugs and dNPWT devices.</P>
                    <P>
                        To better align payment with patient care needs and to better ensure that clinically complex and ill beneficiaries have adequate access to home health care, in the CY 2019 HH PPS final rule with comment period (83 FR 56406), we finalized case-mix methodology refinements, including the removal of therapy thresholds, through the Patient-Driven Groupings Model (PDGM) for home health periods of care beginning on or after January 1, 2020. The PDGM did not change eligibility or coverage criteria for Medicare home health services, and if the individual meets the criteria for home health services as described at 42 CFR 409.42, the individual can receive Medicare home health services, including therapy services. For more information about the 
                        <PRTPAGE P="41221"/>
                        role of therapy services under the PDGM, we refer readers to the Medicare Learning Network (MLN) Matters article SE20005 available at 
                        <E T="03">https://www.cms.gov/regulations-and-guidanceguidancetransmittals2020-transmittals/se20005.</E>
                         To adjust for case-mix for 30-day periods of care beginning on and after January 1, 2020, the HH PPS uses a 432-category case-mix classification system to assign patients to a home health resource group (HHRG) using patient characteristics and other clinical information from Medicare claims and the Outcome and Assessment Information Set (OASIS) instrument. These 432 HHRGs represent the different payment groups based on five main case-mix categories under the PDGM, as shown in figure B1. Each HHRG has an associated case-mix weight that is used in calculating the payment for a 30-day period of care. For periods of care with visits less than the low-utilization payment adjustment (LUPA) threshold for the HHRG, Medicare pays national per-visit rates based on the discipline(s) providing the services. Medicare also adjusts the national standardized 30-day period payment rate for certain intervening events that are subject to a partial payment adjustment. For certain cases that exceed a specific cost threshold, an outlier adjustment may also be available.
                    </P>
                    <P>Under this case-mix methodology, case-mix weights are generated for each of the different PDGM payment groups by regressing resource use for each of the five categories (admission source, timing, clinical grouping, functional impairment level, and comorbidity adjustment) using a fixed effects model. A detailed description of each of the case-mix variables under the PDGM have been described previously, and we refer readers to the CY 2021 HH PPS final rule (85 FR 70303 through 70305) for further information.</P>
                    <BILCOD>BILLING CODE 4169-69-P</BILCOD>
                      
                    <GPH SPAN="3" DEEP="516">
                          
                        <PRTPAGE P="41222"/>
                        <GID>EP06JY26.023</GID>
                    </GPH>
                      
                    <BILCOD>BILLING CODE 4169-69-C</BILCOD>
                    <HD SOURCE="HD2">B. Monitoring the Effects of the Implementation of the PDGM</HD>
                    <HD SOURCE="HD3">1. Routine PDGM Monitoring</HD>
                    <P>
                        CMS routinely analyzes Medicare home health benefit utilization, including but not limited to, overall total 30-day periods of care and average periods of care per HHA user; distribution of the type of visits in a 30-day period of care; the percentage of periods that receive the LUPA; estimated costs for 30-day period of care; the percentage of 30-day periods of care by clinical group, comorbidity adjustment, admission source, timing, and functional impairment level; the proportion of 30-day periods of care with and without any therapy visits, nursing visits, and/or aide/social worker visits; and number of home health visits using telecommunications technology and remote patient monitoring. For the monitoring included in this rule, we examine simulated data for CYs 2018 and 2019 and actual data for CYs 2020, 2021, 2022, 2023, 2024, and 2025 for 30-day periods of care. We refer readers to the CY 2022 HH PPS final rule (
                        <E T="03">86 FR 35881</E>
                        ) for discussion about simulated data for CYs 2018 and 2019.
                    </P>
                    <HD SOURCE="HD3">(a) Utilization</HD>
                    <P>
                        Table 2 shows the overall utilization of home health services. This data indicates the average number of 30-day periods of care per unique HHA beneficiary was higher in CY 2025 compared to CYs 2021, 2022, and 2023. The data also indicates that overall, the number of 30-day periods of care decreased between CY 2018 and CY 
                        <PRTPAGE P="41223"/>
                        2025. Table 3 shows the average utilization of visits per 30-day period of care by home health discipline. Table 4 shows the proportion of 30-day periods of care that are LUPAs and the average number of visits per discipline of those LUPA 30-day periods of care over time. The data show a decreasing trend in the average number of visits per 30-day period and average number of visits per discipline for LUPA 30-day periods of care between CY 2018 and CY 2025.
                    </P>
                    <BILCOD>BILLING CODE 4169-69-P</BILCOD>
                    <GPH SPAN="3" DEEP="309">
                        <GID>EP06JY26.024</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="325">
                        <PRTPAGE P="41224"/>
                        <GID>EP06JY26.025</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="360">
                        <PRTPAGE P="41225"/>
                        <GID>EP06JY26.026</GID>
                    </GPH>
                    <BILCOD>BILLING CODE 4169-69-C</BILCOD>
                    <HD SOURCE="HD3">(b) Analysis of 2024 Cost Report Data for 30-Day Periods of Care</HD>
                    <P>In the CY 2026 HH PPS proposed rule (90 FR 29120), we provided a summary of analysis on FY 2023 HHA cost report data, as this was the most recent and complete cost report data at the time of rulemaking, and CY 2024 claims to estimate 30-day period of care costs. Our analysis showed that the CY 2024 national, standardized 30-day period payment rate of $2,038.13, was approximately 32 percent more than the estimated CY 2024 estimated 30-day period cost of $1,548.39.</P>
                    <P>Using this same process in this proposed rule to compare home health payment to costs, we examined 2024 HHA Medicare cost reports (CMS Form 1728-20, OMB No. 0938-0222), as this is the most recent and complete cost report data at the time of rulemaking. We also examined CY 2025 home health claims to estimate 30-day period of care costs. We excluded LUPAs and partial payment adjustments when calculating the average number of visits. We used the 2024 average NRS costs per visit, which was $4.89. To update the estimated 30-day period of care costs, we begin with the 2024 average costs per visit with NRS for each discipline and multiply that amount by the CY 2025 home health payment update percentage of 2.7 percent (or a home health payment update factor of 1.027). We then multiplied that amount for each discipline by the 2025 average number of visits by discipline to determine the 2025 estimated 30-day period costs. Table 5 shows the estimated average costs for 30-day periods of care by discipline with NRS and the total 30-day period of care costs with NRS for CY 2025.  </P>
                    <GPH SPAN="3" DEEP="240">
                          
                        <PRTPAGE P="41226"/>
                        <GID>EP06JY26.027</GID>
                    </GPH>
                      
                    <P>The CY 2025 national standardized 30-day period payment rate was $2,057.35, which is approximately 34 percent more than the CY 2025 estimated 30-day period cost of $1,532.84. Moreover, as shown in table 3 in this proposed rule, HHAs have reduced visits under PDGM in CY 2025.</P>
                    <HD SOURCE="HD3">(c) Clinical Groupings and Comorbidities</HD>
                    <P>Each 30-day period of care is grouped into one of 12 clinical groups, which describes the primary reason for which a patient is receiving home health services under the Medicare home health benefit. The clinical grouping is based on the principal diagnosis reported on the home health claim. Table 6 shows the distribution of the 12 clinical groups over time.</P>
                    <GPH SPAN="3" DEEP="270">
                          
                        <GID>EP06JY26.028</GID>
                    </GPH>
                      
                    <P>
                        Thirty-day periods of care receive a comorbidity adjustment category based on certain secondary diagnoses reported on home health claims. These diagnoses are based on a home health specific list of clinically and statistically significant secondary diagnosis subgroups with similar resource use. We refer readers to section II.D. of this proposed rule and 
                        <PRTPAGE P="41227"/>
                        the CY 2020 HH PPS final rule with comment period (
                        <E T="03">84 FR 60493</E>
                        ) for further information on the comorbidity adjustment categories. Home health 30-day periods of care can receive a low or a high comorbidity adjustment, or no comorbidity adjustment. Table 7 shows the distribution of 30-day periods of care by comorbidity adjustment category for all 30-day periods.
                    </P>
                    <GPH SPAN="3" DEEP="228">
                        <GID>EP06JY26.029</GID>
                    </GPH>
                    <HD SOURCE="HD3">(d) Admission Source and Timing</HD>
                    <P>Each 30-day period of care is classified into one of two admission source categories—community or institutional, depending on what healthcare setting was utilized in the 14 days prior to receiving home health care. Thirty-day periods of care for beneficiaries with any inpatient acute care hospitalizations, inpatient psychiatric facility (IPF) stays, skilled nursing facility (SNF) stays, inpatient rehabilitation facility (IRF) stays, or long-term care hospital (LTCH) stays within 14-days prior to a home health admission are designated as institutional admissions. The institutional admission source category also includes patients that had an acute care hospital stay during a previous 30-day period of care and within 14 days prior to the subsequent, contiguous 30-day period of care and for which the patient was not discharged from home health and readmitted. All other 30-day periods of care would be designated as community admissions.</P>
                    <P>Thirty-day periods of care are classified as “early” or “late” depending on when they occur within a sequence of 30-day periods of care. The first 30-day period of care is classified as early and all subsequent 30-day periods of care in the sequence (second or later) are classified as late. A subsequent 30-day period of care would not be considered early unless there is a gap of more than 60 days between the end of one previous period of care and the start of another. Information regarding the timing of a 30-day period of care comes from Medicare home health claims data and not the OASIS assessment to determine if a 30-day period of care is “early” or “late”. Table 8 shows the distribution of 30-day periods of care by admission source and period timing.</P>
                    <GPH SPAN="3" DEEP="219">
                        <PRTPAGE P="41228"/>
                        <GID>EP06JY26.030</GID>
                    </GPH>
                    <HD SOURCE="HD3">(e) Functional Impairment Level</HD>
                    <P>
                        Each 30-day period of care is placed into one of three functional impairment levels (low, medium, or high) based on responses to certain OASIS functional items associated with grooming, bathing, dressing, ambulating, transferring, and risk for hospitalization. The specific OASIS items that are used for the functional impairment level are found in table 7 in the CY 2020 HH PPS final rule with comment period (
                        <E T="03">84 FR 60490</E>
                        ). Responses to these OASIS items are grouped together into response categories with similar resource use and each response category has associated points. A more detailed description as to how these response categories were established can be found in the technical report, “Overview of the Home Health Groupings Model” posted on the HHA web page 
                        <SU>1</SU>
                        <FTREF/>
                        . The sum of these points results in a functional impairment score used to group 30-day periods of care into a functional impairment level with similar resource use. The scores associated with the functional impairment levels vary by clinical group to account for differences in resource utilization. A patient's functional impairment level remains the same for the first and second 30-day periods of care unless there is a significant change in condition that warrants an “other follow-up” assessment prior to the second 30-day period of care. For each 30-day period of care, the Medicare claims processing system looks for occurrence code 50 on the claim to correspond to the M0090 date of the applicable assessment. Table 9 shows the distribution of 30-day periods by functional impairment level.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             
                            <E T="03">https://www.cms.gov/medicare/payment/prospective-payment-systems/home-health/home-health-patient-driven-groupings-model.</E>
                        </P>
                    </FTNT>
                    <GPH SPAN="3" DEEP="192">
                        <GID>EP06JY26.031</GID>
                    </GPH>
                    <PRTPAGE P="41229"/>
                    <HD SOURCE="HD3">(f) Therapy and Non-Therapy Visits</HD>
                    <P>Beginning in CY 2020, section 1895(b)(4)(B)(ii) of the Act eliminated the use of therapy thresholds in calculating payments for CY 2020 and subsequent years. Prior to implementation of the PDGM, HHAs could receive an adjustment to payment based on the number of therapy visits provided during a 60-day episode of care. We examined the proportion of actual 30-day periods of care with and without therapy visits. To be covered as skilled therapy, the services must require the skills of a qualified therapist (that is, PT, OT, or SLP) or qualified therapist assistant and must be reasonable and necessary for the treatment of the patient's illness or injury. As shown in table 4, we monitor the number of visits per 30-day period of care by each home health discipline. Any 30-day period of care can include both therapy and non-therapy visits. If any 30-day period of care consisted of only visits for PT, OT, or SLP, then this 30-day period of care is considered “therapy only”. If any 30-day period of care consisted of only visits for skilled nursing, home health aide, or social worker, then this 30-day period of care is considered “no therapy”. If any 30-day period of care consisted of at least one therapy visit and one non-therapy visit, then this 30-day period of care is considered “therapy + non-therapy”. Table10 shows the proportion of 30-day periods of care with only therapy visits, at least one therapy visit and one non-therapy visit, and no therapy visits. Figure 2 shows the proportion of 30-day periods of care by the number of therapy visits (excluding zero) provided during 30-day periods of care.</P>
                    <BILCOD>BILLING CODE 4169-69-P</BILCOD>
                    <GPH SPAN="3" DEEP="250">
                        <GID>EP06JY26.032</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="500">
                        <PRTPAGE P="41230"/>
                        <GID>EP06JY26.033</GID>
                    </GPH>
                    <P>Both figures 2 and 3 indicate there have been changes in the distribution of both therapy and non-therapy visits in CY 2025 compared to CY 2024. For example, the proportion of 30-day periods with one through five therapy visits during a 30-day period increased in CY 2025 compared to prior years. However, when comparing therapy utilization from before the PDGM (CYs 2018 and 2019) to after the implementation of the PDGM (CYs 2020-2025), we also see stabilization in overall therapy visits across all clinical groups, as shown in figure 3.</P>
                    <GPH SPAN="3" DEEP="445">
                        <PRTPAGE P="41231"/>
                        <GID>EP06JY26.034</GID>
                    </GPH>
                    <BILCOD>BILLING CODE 4169-69-C</BILCOD>
                    <P>We also examined the proportion of 30-day periods of care with and without skilled nursing, social work, or home health aide visits. Table 11 shows the number of 30-day periods of care with only skilled nursing visits, at least one skilled nursing visit and one other visit type (therapy or non-therapy), and no skilled nursing visits. Table 12 shows the number of 30-day periods of care with and without home health aide or social worker visits.</P>
                    <BILCOD>BILLING CODE 4169-69-P</BILCOD>
                    <GPH SPAN="3" DEEP="274">
                        <PRTPAGE P="41232"/>
                        <GID>EP06JY26.035</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="266">
                        <GID>EP06JY26.036</GID>
                    </GPH>
                    <BILCOD>BILLING CODE 4169-69-C</BILCOD>
                    <HD SOURCE="HD3">(g) Home Health Services Using Telecommunications Technology</HD>
                    <P>
                        As discussed in the CY 2023 final rule (
                        <E T="03">87 FR 66858</E>
                        ), we began collecting data on the use of telecommunications technology used during a home health period using three G-codes reported on home health claims. Collecting data on services furnished via telecommunications technology on claims allows CMS to analyze the characteristics of patients using services provided remotely. The monitoring illustrates which services are most frequently furnished via telecommunication technology and generally how long remote patient monitoring is utilized.
                    </P>
                    <P>
                        We began collecting this information from HHAs on a voluntary basis on January 1, 2023, and have required this information to be reported on claims starting on July 1, 2023 (
                        <E T="03">87 FR 66858</E>
                        ). The three G-codes help identify when home health services are furnished using synchronous telemedicine rendered via a real-time two-way audio and video telecommunications system 
                        <PRTPAGE P="41233"/>
                        (G0320); synchronous telemedicine rendered via telephone or other real-time interactive audio-only telecommunications systems (G0321); and the collection of physiologic data digitally stored and/or transmitted by the patient to the HHA, that is, remote patient monitoring (G0322). We capture the usage and length of remote patient monitoring using the start date of the remote patient monitoring and the number of days of monitoring indicated on the claim. We also looked at the disciplines most often providing remote patient monitoring. We examined the utilization of telecommunications technology devices during a home health period and remote patient monitoring by looking at home health claims that included the three G-codes. Tables 13 and 14 show that the use of telecommunications services and remote patient monitoring reported on CY 2025 home health claims have declined from prior year's monitoring (90 FR 29126 and 29127) and are mainly associated with skilled nursing.
                    </P>
                    <BILCOD>BILLING CODE 4169-69-P</BILCOD>
                    <GPH SPAN="3" DEEP="356">
                        <GID>EP06JY26.037</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="387">
                        <PRTPAGE P="41234"/>
                        <GID>EP06JY26.038</GID>
                    </GPH>
                    <BILCOD>BILLING CODE 4169-69-C</BILCOD>
                    <HD SOURCE="HD2">C. Proposed CY 2027 Payment Adjustments Under the HH PPS</HD>
                    <HD SOURCE="HD3">1. Proposed Behavior Adjustments Under the HH PPS</HD>
                    <HD SOURCE="HD3">a. Background</HD>
                    <P>As discussed in section II.A.1. of this proposed rule, starting in CY 2020, the Secretary was required by section 1895(b)(2)(B) of the Act to change the unit of payment under the HH PPS from a 60-day episode of care to a 30-day period of care. CMS was also required to make assumptions about behavior changes that could occur as a result of the implementation of the 30-day unit of payment and the case-mix adjustment factors that eliminated the use of therapy thresholds. In the CY 2019 HH PPS final rule with comment period (83 FR 56455), we finalized three behavior change assumptions which were also described in the CY 2022 and 2023 HH PPS rules (86 FR 35890, 87 FR 37614, and 87 FR 66795 through 66796). In the CY 2020 HH PPS final rule with comment period (84 FR 60519), we included these behavior change assumptions in the calculation of the 30-day budget neutral payment amount for CY 2020, finalizing a negative 4.36 percent behavior change assumption adjustment (“assumed behaviors”). We did not propose any changes for CYs 2021 and 2022 related to the behavior change assumptions finalized in the CY 2019 HH PPS final rule with comment period, or to the negative 4.36 percent behavior change assumption adjustment, finalized in the CY 2020 HH PPS final rule with comment period.</P>
                    <P>
                        In the CY 2023 HH PPS final rule (87 FR 66796), we stated that we had concluded, based on our annual monitoring at that time, that the three expected behavior changes did in fact occur as a result of the implementation of the PDGM and that other behaviors, such as changes in the provision of therapy and changes in functional impairment levels, had also occurred. We also reminded readers that in the CY 2020 HH PPS final rule with comment period (84 FR 60513), we stated we interpret actual behavior changes to encompass behavior changes that were previously outlined as assumed by CMS, and other behavior changes not identified at the time we established the budget-neutral 30-day payment rate for CY 2020. In the CY 2023 HH PPS final rule (87 FR 66796), we provided supporting evidence that indicated the number of therapy visits declined in CYs 2020 and 2021, as well as a slight decline in therapy visits beginning in CY 2019 after the finalization of the removal of therapy thresholds, but prior to implementation of the PDGM. In section II.B.1. of the CY 2025 HH PPS proposed rule (89 FR 55318), our analysis continued to show the actual 30-day periods are similar overall to the simulated 30-day periods as well as a continued decline in therapy visits, indicating that HHAs changed their behavior to reduce therapy visits. Although the analysis demonstrates evidence of individual behavior changes (for example, in the volume of visits for 
                        <PRTPAGE P="41235"/>
                        LUPAs, therapy sessions, etc.), we use the entirety of the behaviors to calculate estimated aggregate expenditures. The law instructs us to ensure that estimated aggregate expenditures under the PDGM are equal to the estimated aggregate expenditures that otherwise would have been made under the prior system.
                    </P>
                    <P>
                        Section 4142(a) of the CAA, 2023 required CMS to present, to the extent practicable, a description of the actual behavior changes occurring under the HH PPS from CYs 2020 through 2026. This subsection of the CAA, 2023 also required CMS to provide datasets underlying the simulated 60-day episodes and discuss and provide time for stakeholders to provide input on and ask questions about the payment rate development for CY 2023. CMS complied with these requirements by posting online both the supplemental limited data set (LDS) and descriptive files and the description of actual behavior changes that affected CY 2023 payment rate development. Additionally, on March 29, 2023, CMS conducted a webinar entitled “Medicare Home Health Prospective Payment System (HH PPS) Calendar Year (CY) 2023 Behavior Change Recap, 60-Day Episode Construction Overview, and Payment Rate Development.” The webinar was open to the public and discussed the actual behavior changes that occurred upon implementation of the PDGM; our approach used to construct simulated 60-day episodes using 30-day periods; payment rate development for CY 2023; and information on the supplemental data files containing information on the simulated 60-day episodes and actual 30-day periods used in calculating the permanent adjustment to the payment rate. Materials from the webinar, including the presentation and the CY 2023 descriptive statistics from the supplemental LDS files containing information on the number of simulated 60-day episodes and actual 30-day periods in CY 2021 that were used to construct the permanent adjustment to the payment rate, as well as information such as the number of episodes and periods by case-mix group, case-mix weights, and simulated payments, can be found on the Home Health Patient-Driven Groupings Model web page at 
                        <E T="03">https://www.cms.gov/medicare/payment/prospective-payment-systems/home-health/home-health-patient-driven-groupings-model.</E>
                    </P>
                    <HD SOURCE="HD3">b. Method to Annually Determine the Impact of Differences Between Assumed Behavior Changes and Actual Behavior Changes on Estimated Aggregate Expenditures</HD>
                    <P>In the CY 2023 HH PPS final rule (87 FR 66804), we finalized the methodology to evaluate the impact of the differences between assumed and actual behavior changes on estimated aggregate expenditures. In the CY 2024 HH PPS final rule (88 FR 77687 through 77688), we provided an overview of the methodology with detailed instructions for each step.</P>
                    <P>
                        Under the prior 153-group system (and the first three years for assessments associated with the PDGM completed prior to CY 2023), HHAs submitted the Outcome and Assessment Information Set (OASIS) instrument version D. However, OMB approved an updated version of the OASIS instrument, OASIS-E under OMB control number 0938-1279,
                        <SU>2</SU>
                        <FTREF/>
                         on November 30, 2022, effective January 1, 2023. Therefore, in the CY 2025 HH PPS final rule (89 FR 88364), we finalized two additional methodological assumptions related to mapping and imputation of OASIS-D responses from OASIS-E. We refer readers to the CY 2024 and CY 2025 HH PPS final rules for further information about the methodology.
                    </P>
                    <FTNT>
                        <P>
                            <SU>2</SU>
                             The current expiration date for this information collection request is December 31, 2027.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Calculating Permanent and Temporary Payment Adjustments</HD>
                    <P>To adjust the base payment rate based on increases or decreases in estimated aggregate expenditures that result from differences between assumed behavior changes and actual behavior changes for 2020 through 2026, we calculate one or more permanent prospective adjustments by calculating the percent change between the actual 30-day base payment rate and the recalculated 30-day base payment rate. This percent change is converted into an adjustment factor and applied in the annual rate update process.</P>
                    <P>To account for increases or decreases in estimated aggregate expenditures that result from differences between assumed behavior changes and actual behavior changes from 2020 through 2026, we calculate one or more temporary prospective adjustments by calculating the dollar amount difference between the estimated aggregate expenditures from all 30-day periods using the recalculated 30-day base payment rate, and the aggregate expenditures for all 30-day periods using the actual 30-day base payment rate for each of those years once data is available (87 FR 66804). In other words, when determining the dollar amount of aggregate expenditures in prior years that we must offset in future years, we use the full dataset of actual 30-day periods using both the actual and recalculated 30-day base payment rates to ensure that the utilization and distribution of claims are the same. In accordance with section 1895(b)(3)(D)(iii) of the Act, each temporary adjustment is applied prospectively but, as its name suggests, only with respect to the year for which such temporary increase or decrease is made. Therefore, after we determine the dollar amount we plan to reconcile in a given year, we calculate a temporary adjustment factor to be applied to the base payment rate for that year. The temporary adjustment factor is based on an estimated number of 30-day periods in the next year using historical data trends, and as applicable, controls for any permanent adjustment factor, case-mix weight recalibration neutrality factor, wage index budget neutrality factor, and the home health payment update. The temporary adjustment factor is applied last since the adjustment applies only to the respective year. That is, the temporary adjustment is not permanently fixed into future base payment rates. We refer readers to the CY 2024 HH PPS final rule (88 FR 77689 through 77694) for analysis of CYs 2020 through 2022 claims, the CY 2025 HH PPS final rule (89 FR 88366 through 88369) for analysis of CY 2023 claims, and the CY 2026 HH PPS final rule (90 FR 55365 through 55367) for analysis of CY 2024 claims.</P>
                    <HD SOURCE="HD3">d. CY 2025 Preliminary Claims Results</HD>
                    <P>
                        We stated in the CY 2026 HH PPS final rule (90 FR 55365) that we were exercising our authority expressly delegated under the statute to apply permanent adjustments “at a time and in a manner appropriate” not to apply any permanent adjustment for CY 2026 based on CY 2023 or 2024 data, as these years may contain data with behaviors attributable to factors beyond the implementation of the PDGM and a 30-day unit of payment. However, we also noted we will continue to annually analyze the data through CY 2026 claims, as required by law, to determine if any additional permanent adjustments would need to be made based on the impact of assumed versus actual behavior change on estimated aggregate expenditures resulting from the implementation of the PDGM and the 30-day unit of payment. While the law requires us to continue to evaluate the need for any additional permanent 
                        <PRTPAGE P="41236"/>
                        adjustments in future rulemaking, we reiterate that any additional permanent adjustment(s) would need to be related to actual behavior change resulting only from the implementation of the PDGM and the change in the unit of payment as required by law. Therefore, we will continue to compare estimated aggregate expenditures under the PDGM and the 153-group payment system, using the most recent complete home health claims data available at the time of rulemaking, as required by section 1895(b)(3)(D)(i) of the Act. While the CY 2025 analysis presented in this proposed rule uses the most complete data available at the time, it is considered preliminary and, as more data become available from the latter half of CY 2025, we will update our analysis in the final rule. The CY 2027 HH PPS final rule would use the complete CY 2025 data to determine any permanent and temporary adjustments needed to the CY 2027 payment rate. However, while the claims data and the permanent and temporary adjustments results would be considered complete for CY 2027, any adjustments to future payment rates may be subject to additional considerations such as permanent adjustments taken in previous years.
                    </P>
                    <P>The claims data used in rulemaking is released in the HH PPS LDS file twice each year, one with the proposed and one with the final rule. Accordingly, the HH PPS LDS file released with this proposed rule includes two files: the actual CY 2025 30-day periods and the CY 2025 simulated 60-day episodes.</P>
                    <P>
                        We remind readers that a data use agreement (DUA) is required to purchase the CY 2027 proposed HH PPS LDS file using the CMS-R-0235A form under OMB control number 0938-0734. Access would be granted for both the 30-day periods and the simulated 60-day episodes under one DUA. Visit the HH PPS LDS web page for more information.
                        <SU>3</SU>
                        <FTREF/>
                         In addition, the proposed CY 2027 Home Health Descriptive Statistics from the LDS Files spreadsheet is available on the HH PPS Regulations and Notices web page,
                        <SU>4</SU>
                        <FTREF/>
                         does not require a DUA, and is available at no cost to interested parties. The spreadsheet contains information on the number of simulated 60-day episodes and actual 30-day periods in CY 2025 that were used to determine the adjustments. The spreadsheet also provides information such as the number of episodes and periods by case-mix group, case-mix weights, and simulated payments.
                    </P>
                    <FTNT>
                        <P>
                            <SU>3</SU>
                             
                            <E T="03">https://www.cms.gov/research-statistics-data-and-systems/files-for-order/limiteddatasets/home_health_pps_lds.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>4</SU>
                             
                            <E T="03">https://www.cms.gov/Medicare/Medicare-Fee-for-Service-Payment/HomeHealthPPS/Home-Health-Prospective-Payment-System-Regulations-and-Notices.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">e. Applying the Methodology to CY 2025 Data To Determine the CY 2027 Permanent and Temporary Adjustments</HD>
                    <P>To comply with Section 1895(b)(3)(D)(ii) of the Act, we are required to annually analyze data from CY 2020 through CY 2026 and show the calculations to illustrate how the aggregate expenditures differ from actual and assumed behavior changes. We also continue to analyze differences in aggregate expenditures and calculate what the budget neutral rate would be to understand how the budget neutral rate differs from the actual finalized payment rate for CY 2025. We then determine whether the difference between the budget neutral rate and actual finalized payment rate can be directly attributed to behavior from PDGM implementation as discussed in CY 2026 final rule.</P>
                    <P>Using the methodology finalized in the CY 2023 HH PPS final rule to apply for all the years in which an adjustment is appropriate, we continue to use actual CY 2025 30-day periods to determine what the proposed permanent and temporary payment adjustments should be to offset for such increases or decreases in estimated aggregate expenditures as a result of the impact of differences between assumed behavior changes and actual behavior changes. We provide tables 15 and 16 to illustrate the same information displayed in prior rules to show the permanent adjustment that would need to be applied if the comparison of the aggregate expenditures were a result of behavior change due to the implementation of the PDGM. However, similar to what was finalized in the CY 2026 HH PPS final rule (90 FR 55364 through 55365), we believe any behavior changes reflected in preliminary CY 2025 claims for this CY 2027 proposed rule are not directly attributable to the PDGM but other confounding factors that began in CY 2023 (that is, continued recalibration of case-mix weights, a change to the OASIS-E, and previous reductions to the home health payment rate). The permanent adjustment calculated will be illustrative as part of our analysis of CY 2025 claims; however, we are not proposing to apply a permanent adjustment to the CY 2027 payment rate, as discussed previously. We show table 17 as another illustrative example showing a calculated permanent adjustment, using CY 2025 aggregate expenditures if we were to determine that the behavior changes that occurred could be directly attributed to the implementation of the PDGM.</P>
                    <P>Using the preliminary CY 2025 dataset, we began with 8,228,904 30-day periods of care and dropped 444,897 30-day periods of care that had a claim occurrence code 50 date after October 31, 2025. We also excluded 847,700 30-day periods of care that had a claim occurrence code 50 date before January 1, 2025, to ensure the 30-day period will not be part of a simulated 60-day episode that began in CY 2026. Applying the additional exclusions and assumptions as described in the finalized methodology (87 FR 66804), an additional 60,233 30-day periods were excluded.</P>
                    <P>The Company believes the proposed Observer provisions in the amended By-Laws are consistent with the Act because the Observer position will provide a means for individuals who are employed by, or otherwise affiliated with, an Exchange Member but may not be able, or willing, to serve as a Board member for one reason or another, to now be able to serve the Company in an advisory role and provide such valuable expertise and knowledge to help the Company carry out its business.</P>
                    <P>Using the preliminary dataset for CY 2025 (6,557,369 actual 30-day periods which made up the 3,860,954 simulated 60-day episodes) we determined the estimated aggregate expenditures using the finalized CY 2025 HH PPS payment rate were lower than the actual estimated aggregate expenditures under the PDGM HH PPS. As shown in table 15, aggregate expenditures under the PDGM were higher than if the 153-group payment system were still in place in CY 2025 and therefore, we determined the CY 2025 30-day base payment rate should have been $1,953.60 based on actual behavior changes.</P>
                    <P>We determined that for CYs 2020 through CY 2022 a total of −9.480 percent permanent adjustment was needed (after accounting for the −3.925 percent applied to the CY 2023 payment rate, the −2.890 percent applied to the CY 2024 payment rate, and the −1.975 percent applied to the CY 2025 payment rate). The CY 2026 permanent adjustment was calculated using the permanent adjustments already applied to CYs 2023, 2024, and 2025 finalized payment rates and to reach the payment rate reduction needed for CYs 2020 through 2022.</P>
                    <P>
                        In order to determine behavior changes only applicable to CY 2025, we simulated what the CY 2025 base payment rate would have been if the −1.023 percent adjustment that we determined using CY 2024 claims had been implemented and to compare 
                        <PRTPAGE P="41237"/>
                        PDGM claims with 153-group priced claims using 60-day simulated episodes.
                    </P>
                    <P>To do so, we started with the budget neutral CY 2024 base payment of $1,914.73 generated by CY 2024 simulated 60-day episodes (as published in the CY 2026 HH PPS final rule (90 FR 55366)) and applied the CY 2025 case-mix weights recalibration neutrality factor (1.0039), the CY 2025 wage index budget neutrality factor (0.9988), the CY 2024 labor-related share budget neutrality factor (1.0), and the CY 2025 home health payment update factor (1.027). We determined the CY 2025 base payment rate for assumed behavior would have been $1,971.73.</P>
                    <P>For the CY 2025 annual permanent adjustment, we calculated the percent change between the two payment rates for only CY 2025. For the CY 2025 annual temporary adjustment we calculated the difference in aggregate expenditures in dollars for all CY 2025 PDGM 30-day claims using the two payment rates. This difference is shown as the retrospective dollar amount we would need to offset payment using one or more temporary adjustments in future years. Our results for the CY 2025 annual (single year) permanent and temporary adjustment calculations using CY 2025 preliminary claims data are shown in table 15.</P>
                    <GPH SPAN="3" DEEP="274">
                        <GID>EP06JY26.039</GID>
                    </GPH>
                    <P>As shown in table 15, we illustrate that a permanent prospective adjustment of −0.919 percent to the CY 2027 30-day payment rate (assuming all adjustments from prior years were applied) for CY 2025 would be required to offset for such increases in estimated aggregate expenditures. Again, table 15 is illustrative because we are continuing to limit the calculation of the permanent adjustments to only include data from CYs 2020 through 2022 as finalized in the CY 2026 HH PPS final rule (90 FR 55365 through 55367) and the calculated permanent adjustment does not include implemented permanent adjustments from prior years. We reiterate that any additional permanent adjustment(s) must be determined to be related to actual behavior change resulting only from the implementation of the PDGM and the change in the unit of payment as required by law.</P>
                    <HD SOURCE="HD3">f. CY 2027 Permanent Adjustment and Proposed Temporary Adjustment Calculations</HD>
                    <P>In the preceding section we describe how we analyzed CY 2025 preliminary claims data to determine the effects of actual behavior change on estimated aggregate expenditures. Again, that illustrative analysis included simulations that assumed the full permanent adjustments were already taken. We note that CMS implemented a payment adjustment of −1.975 percent for the CY 2025 payment rate, rather than the −3.95 percent we calculated (89 FR 88373), so the calculations set forth later in this section reflect the remaining adjustments that still needed to be recognized.</P>
                    <P>Therefore, the calculation in this section includes any of the remaining adjustments not applied in previous years (that is, CYs 2020 through 2024 claims data), as well as the adjustment needed to account for CY 2025 claims. In calculating the full permanent adjustment needed to the CY 2027 30-day payment rate, we compare estimated aggregate expenditures under the PDGM and the prior system. Unlike the annual adjustments described in table 15, we do not assume we made the full adjustment from prior years. This section will also include calculation of a permanent adjustment using the actual CY 2025 payment rate and the budget neutral rate for CY 2025 using the method discussed in the CY 2026 final rule.</P>
                    <P>
                        As discussed in section II.C.1.d. of this proposed rule, using the preliminary dataset for CY 2025 (6,557,369 actual 30-day periods which made up the 3,860,954 simulated 60-day episodes) we determined the CY 2025 30-day base payment rate should have been $1,953.60 based on actual behavior. We then compared the repriced 30-day base payment rate based 
                        <PRTPAGE P="41238"/>
                        on actual behavior to the CY 2025 30-day base payment rate of $2,057.35 we paid based on assumed behaviors. The percent change, as summarized in table 16, between the actual CY 2025 base payment rate of $2,057.35 (based on assumed behaviors) and the CY 2025 recalculated base payment rate of $1,953.60 (based on actual behaviors) illustrates the total permanent adjustment that would reflect CY 2020 through CY 2025 claims. We conduct this calculation to satisfy the requirements described in section 1895(b)(3)(D)(ii) of the Act to illustrate what the permanent adjustment would be. We consider table 16 illustrative because we are proposing to limit the calculation of the permanent adjustments to only include data from CYs 2020 through 2022 as finalized in the CY 2026 final rule (90 FR 55365 through 55367).
                    </P>
                    <GPH SPAN="3" DEEP="152">
                        <GID>EP06JY26.040</GID>
                    </GPH>
                    <P>As shown in table 16, a permanent prospective adjustment of −5.043 percent to the CY 2027 30-day payment rate would be required to offset for such increases in estimated aggregate expenditures. To illustrate this calculation:</P>
                    <GPH SPAN="3" DEEP="28">
                        <GID>EP06JY26.041</GID>
                    </GPH>
                    <P>As we stated in the CY 2026 HH PPS final rule (90 FR 55357), applying a −1.975 percent (half of the proposed −3.95 percent) permanent adjustment to the CY 2025 30-day payment rate would not adjust the rate fully to account for differences in behavior changes on estimated aggregate expenditures in CYs 2020, 2021, 2022, and 2023. Using CY 2025 claims data, as shown in table 16, a permanent prospective adjustment of −5.043 percent to the CY 2027 30-day payment rate would offset for increases in estimated aggregate expenditures for CYs 2020 through 2025. We note that adjustment factors are multiplied in this payment system, and individual numbers (that is, percentages) cannot be added or subtracted together to determine the final adjustment. Therefore, we cannot determine the illustrative CY 2027 permanent adjustment, which would include estimated aggregate expenditures in CY 2025, by simply subtracting the −1.975 percent applied in CY 2025 and the −1.023 percent applied in CY 2026 from the total permanent adjustment of −5.043 percent as shown in table 16.</P>
                    <P>Instead, we account for the permanent adjustment applied in prior years when we calculate the CY 2027 permanent adjustment by solving the following equation  To illustrate this calculation we used the following approach.</P>
                    <GPH SPAN="3" DEEP="76">
                        <GID>EP06JY26.042</GID>
                    </GPH>
                    <P>We note that the −4.062 percent is calculated as a permanent adjustment for CY 2027 illustrating what we would need if we were to offset the difference in aggregate expenditures between CY 2025 claims priced under the PDGM and the 153-group system and adjusting for the permanent adjustments applied in prior years.</P>
                    <P>
                        We continue to apply the methodology finalized in the CY 2026 HH PPS final rule to determine what the permanent adjustment for CY 2025 claims would be even though we stopped comparing claims priced under PDGM and 153-group after CY 2022 claims for the purposes of applying a permanent adjustment in this proposed rule. As displayed in table 17, we calculate the permanent adjustment for CY 2025 by determining the percent change between the actual CY 2025 30-day payment rate ($2,057.35) and the budget neutral rate for CY 2025 
                        <PRTPAGE P="41239"/>
                        ($2,036.29). The budget neutral rate for CY 2025 is the finalized CY 2024 budget neutral rate discussed in CY 2026 final rule ($1,977.43) multiplied by the CY 2025 case-mix weights recalibration neutrality factor (1.0039), the CY 2025 wage index budget neutrality factor (0.9988), and the CY 2025 home health payment update factor (1.027).
                    </P>
                    <GPH SPAN="3" DEEP="235">
                        <GID>EP06JY26.043</GID>
                    </GPH>
                    <P>In section II.C.1.d of this proposed rule, we discussed various trends that are part of monitoring changes related to the PDGM using analysis of CY 2025 claims. The data continues to show minimal changes that could be attributed to the PDGM implementation after CY 2022 by a large proportion of home health providers. We also continue to acknowledge the difficulty in attributing any behavior change occurring from CYs 2023 through 2025 directly to the PDGM implementation and its effects on expenditures from the other changes occurring in those years. As discussed in the CY 2026 HH PPS final rule, CMS introduced several policy changes that make isolating the effect of implementing a permanent adjustment, with claims data from CYs 2023 through 2025, for the PDGM difficult. These changes include recalibration of case-mix weights and LUPA visit thresholds finalized in the CY 2023, 2024, 2025, and 2026 final rules; reassignment of certain ICD-10-CM codes related to the PDGM clinical groups and comorbidity groups in the CY 2023 HH PPS final rule; finalized permanent adjustments in the CY 2023, 2024, and 2025 HH PPS final rules; the introduction of OASIS-E in 2023 and finalized mapping of OASIS-E to OASIS-D in the CY 2025 HH PPS final rule for calculating functional points for functional impairment levels during repricing; and the expanded HHVBP Model. For these reasons, we maintain that limiting the application of the permanent adjustment to analysis of data from CYs 2020 through 2022 continues to be the most accurate application of the law. However, as required by law, we will continue to analyze data through CY 2026 claims to determine if any additional permanent adjustments are needed to account for the impact of assumed versus actual behavior change related to the implementation of the PDGM and the change to a 30-day unit of payment on estimated aggregate expenditures. As a result, we propose to not apply a permanent adjustment to the CY 2027 payment rate.</P>
                    <P>The dollar amount that needs to be collected through the temporary adjustment increased when examining home health claims from CY 2025 because those claims were paid using the actual 30-day payment rate ($2,057.35) instead of the calculated budget neutral payment rate for CY 2025 ($2,036.29). That is, had the payment rate in CY 2025 been $2,036.29, there would not be an increase in what needs to be collected through the temporary adjustment when examining home health claims from CY 2025. Because the 30-day payment rate was not budget neutral until the CY 2026 payment rate with the application of the −1.023 percent permanent adjustment, the temporary adjustment continued to accrue.</P>
                    <P>As described previously in this proposed rule, to account for such increases or decreases in estimated aggregate expenditures as a result of the impact of differences between assumed behavior changes and actual behavior changes in any given year from CY 2020 to CY 2026, we calculate the temporary prospective adjustment by calculating the dollar amount difference between the estimated aggregate expenditures from all 30-day periods using the recalculated 30-day base payment rate, and the aggregate expenditures for all 30-day periods using the actual 30-day base payment rate for that year. In other words, when determining the temporary retrospective dollar amount, we used the full dataset of actual 30-day periods using both the actual and recalculated 30-day base payment rates to ensure that the utilization and distribution of claims are the same. We refer readers to the CY 2024 HH PPS final rule (88 FR 77689 through 77694) for analysis of CYs 2020 through 2022 claims, the CY 2026 HH PPS final rule (90 FR 55366 through 55367) for analysis of CY 2023 and 2024 claims, and section II.C.1.d. of this proposed rule for the analysis of CY 2025 claims. Table 18 provides a summary of the temporary adjustment dollar amount for CYs 2020 through 2026.</P>
                    <GPH SPAN="3" DEEP="279">
                        <PRTPAGE P="41240"/>
                        <GID>EP06JY26.044</GID>
                    </GPH>
                    <P>Therefore, we exercise our authority under section 1895(b)(3)(D)(iii) of the Act to apply “one or more” temporary adjustments to continue recoupment of the retrospective overpayments for CYs 2020 through 2025. Specifically, we propose to implement a 3.0 percent reduction in CY 2027, that is equivalent to a 0.9700 temporary adjustment factor, to the CY 2027 national, standardized payment rate. Using historical trends, we estimated 7,680,775 30-day periods would occur in CY 2027. Using this estimated utilization, a 3.0 percent reduction to the CY 2027 30-day payment rate would begin to collect approximately $500 million of the total temporary adjustment dollar amount, equating to about 10 percent of the total $4.9 billion shown in table 18. In doing so; however, we would need to account for the remaining temporary adjustment dollar amount for CYs 2020 through 2026, plus any possible adjustments for CY 2027 and 2028, in future years. It is important to note that the estimated $500 million dollar amount anticipated to be collected by the implementation of the temporary adjustment factor is based on an estimate of the number of 30-day periods that would occur in CY 2027. It may not reflect the actual dollar amount to be collected if the actual number of 30-day periods and other utilization trends in CY 2027 differ from what was estimated. In other words, CMS will calculate the actual amount collected from the temporary adjustment in CY 2027 and credit it to the overall cumulative temporary dollar amount.</P>
                    <P>In accordance with section 1895(b)(3)(D)(iii) of the Act, the temporary adjustment is to be applied on a prospective basis and shall apply only with respect to the year for which such temporary increase or decrease is made. This means we would not include the −3.0 percent temporary adjustment applied for CY 2027 when calculating the CY 2028 base payment rates. However, to continue recoupment of the retrospective overpayments, we may propose additional temporary adjustments in future rulemaking and are not proposing that the −3.0 percent temporary adjustment would be applied each year after CY 2027. Rather, we will continue to analyze the data each year through CY 2026 claims as required by law, and in a time and manner deemed appropriate, we will propose one or more temporary adjustments to account for retrospective overpayments. We also note the $4.9 billion does not account for any monies recouped in CY 2026, as we do not have this dollar amount at the time of this CY 2027 rulemaking. In future rulemaking, we will show the remaining balance, accounting for the previous recoupment amount; however, there will be a lag. We refer readers to section II.E.3.b. for the CY 2027 base payment rates with and without the temporary adjustment.</P>
                    <P>We solicit comments on the proposals to not apply a permanent adjustment and to apply the −3.0 percent temporary adjustment to the CY 2027 home health base payment rate.</P>
                    <HD SOURCE="HD2">D. Proposed CY 2027 Home Health Low Utilization Payment Adjustment (LUPA) Thresholds, Functional Impairment Levels, Comorbidity Sub-Groups, and Case-Mix Weights</HD>
                    <HD SOURCE="HD3">1. Proposed CY 2027 PDGM LUPA Thresholds</HD>
                    <P>
                        Under the HH PPS, LUPAs are paid when a certain numerical minimum visit threshold for a payment group during a 30-day period of care is not met. In the CY 2019 HH PPS final rule with comment period (83 FR 56492), we finalized a policy setting the LUPA thresholds at the 10th percentile of visits or two visits, whichever is higher, for each payment group. This means the LUPA threshold for each 30-day period of care varies depending on the PDGM payment group to which it is assigned. If the LUPA threshold for the payment group is met under the PDGM, the 30-day period of care would be paid the full 30-day period case-mix adjusted payment amount (subject to any partial payment adjustment or outlier adjustments). If a 30-day period of care does not meet the PDGM LUPA visit threshold, then payment would be made using the per-visit payment amounts as described in section II.E.3.c. of this proposed rule. For example, if the LUPA visit threshold is four, and a 30-day period of care has four or more visits, 
                        <PRTPAGE P="41241"/>
                        it is paid the full 30-day period payment amount; if the period of care has three or fewer visits, payment is made using the per-visit payment amounts.
                    </P>
                    <P>In the CY 2019 HH PPS final rule with comment period (83 FR 56492), we finalized our policy that the LUPA thresholds for each PDGM payment group will be reevaluated every year based on the most current utilization data available at the time of rulemaking. However, as CY 2020 was the first year of the new case-mix adjustment methodology, we stated in the CY 2021 HH PPS final rule (85 FR 70305, 70306) that we would maintain the LUPA thresholds that were finalized and shown in table 18 of the CY 2020 HH PPS final rule with comment period (84 FR 60522) for CY 2021 payment purposes. We stated that at that time, we did not have sufficient CY 2020 data to reevaluate the LUPA thresholds for CY 2021.</P>
                    <P>In the CY 2022 HH PPS final rule with comment period (86 FR 62249), we finalized the proposal to recalibrate the PDGM case-mix weights, functional impairment levels, and comorbidity subgroups while maintaining the LUPA thresholds for CY 2022. We stated that because there are several factors that contribute to how the case-mix weight is set for a particular case-mix group (such as the number of visits, length of visits, types of disciplines providing visits, and non-routine supplies) and the case-mix weight is derived by comparing the average resource use for the case-mix group relative to the average resource use across all groups, we believe the COVID-19 public health emergency (PHE) will have impacted utilization within all case-mix groups similarly. Therefore, the impact of any reduction in resource use caused by the PHE on the calculation of the case-mix weight will be minimized since the impact will be accounted for both in the numerator and denominator of the formula used to calculate the case-mix weight. However, in contrast, the LUPA thresholds are based on the number of overall visits in a particular case-mix group (the threshold is the 10th percentile of visits or 2 visits, whichever is greater) instead of a relative value (like what is used to generate the case-mix weight) that will control for the impacts of the COVID-19 PHE. We noted that visit patterns and some of the decrease in overall visits in CY 2020 may not be representative of visit patterns in CY 2022. Therefore, to mitigate any potential future and significant short-term variability in the LUPA thresholds due to the COVID-19 PHE, we finalized the proposal to maintain the LUPA thresholds finalized and displayed in table 18 in the CY 2020 HH PPS final rule with comment period (84 FR 60522) for CY 2022 payment purposes.</P>
                    <P>For CY 2024, we proposed to update the LUPA thresholds using CY 2022 Medicare home health claims (as of March 17, 2023) linked to OASIS assessment data. We believed that CY 2022 data would be more indicative of visit patterns in CY 2024 rather than continuing to use the LUPA thresholds derived from the CY 2018 pre-PDGM data. Therefore, we finalized a policy to update the LUPA thresholds for CY 2024 using data from CY 2022.</P>
                    <P>For CY 2027, we are proposing to update the LUPA thresholds using CY 2025 home health claims utilization data (as of March 15, 2026), in accordance with our policy to annually recalibrate the case-mix weights and update the LUPA thresholds, functional impairment levels, and comorbidity subgroups. After reviewing the CY 2025 home health claims utilization data, we determined that LUPA visit patterns in 2025 were similar to visits in 2024 and a total of 18 case-mix groups have a decline in their LUPA threshold of a single visit and two case-mix groups have their LUPA threshold increase by a single visit. The proposed LUPA thresholds for the CY 2027 PDGM payment groups with the corresponding Health Insurance Prospective Payment System (HIPPS) codes and the case-mix weights are listed in table 24.</P>
                    <P>We are soliciting public comments on the proposed updates to the LUPA thresholds for CY 2027. The proposed LUPA thresholds will be updated based on more complete CY 2025 claims data in the final rule.</P>
                    <HD SOURCE="HD3">2. Proposed CY 2027 Functional Impairment Levels</HD>
                    <P>Under the PDGM, the functional impairment level is determined by responses to certain OASIS items associated with activities of daily living and risk of hospitalization; that is, responses to OASIS items M1800-M1860 and M1033. A home health period of care receives points based on each of the responses associated with these functional OASIS items, which are then converted into a table of points corresponding to increased resource use. The sum of all these points results in a functional impairment score which is used to group home health periods into a functional level with similar resource use. That is, the higher the points, the more the response is associated with increased resource use, or increased impairment. The three functional impairment levels of low, medium, and high were designed so that approximately one-third of home health periods from each clinical group falls within each level. This means home health periods in the low impairment level have responses for the functional OASIS items that are associated with the lowest resource use, on average. Home health periods in the high impairment level have responses for the functional OASIS items that are associated with the highest resource use on average.</P>
                    <P>
                        For CY 2027, we are proposing to use CY 2025 claims data to update the functional points and functional impairment levels by clinical group. The CY 2018 HH PPS proposed rule (82 FR 35320) and the technical report from December 2016, posted on the Home Health PPS Archive web page, located at 
                        <E T="03">https://www.cms.gov/medicare/home-health-pps/home-health-pps-archive,</E>
                         provides a more detailed explanation as to the construction of the functional impairment levels using the OASIS items. We are proposing to use the same methodology previously finalized to update the functional impairment levels for CY 2027. The proposed updated OASIS functional points table and the table of functional impairment levels by clinical group for CY 2027 are listed in tables 19 and 20, respectively.
                    </P>
                    <BILCOD>BILLING CODE 4169-69-P</BILCOD>
                    <GPH SPAN="3" DEEP="486">
                        <PRTPAGE P="41242"/>
                        <GID>EP06JY26.045</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="580">
                        <PRTPAGE P="41243"/>
                        <GID>EP06JY26.046</GID>
                    </GPH>
                    <BILCOD>BILLING CODE 4169-69-C</BILCOD>
                    <P>We are soliciting public comments on the proposed updates to the functional points and the functional impairment levels by clinical group.</P>
                    <HD SOURCE="HD3">3. Proposed CY 2027 Comorbidity Subgroups</HD>
                    <P>
                        Thirty-day periods of care are assigned to a comorbidity adjustment category based on the presence of certain secondary diagnoses reported on home health claims. These diagnoses are based on a home-health specific list of clinically and statistically significant secondary diagnosis subgroups with similar resource use, meaning the diagnoses have at least as high as the median resource use and are reported in more than 0.1 percent of 30-day periods of care. Home health 30-day periods of care can receive a comorbidity 
                        <PRTPAGE P="41244"/>
                        adjustment under the following circumstances:
                    </P>
                    <P>
                        • 
                        <E T="03">High comorbidity adjustment:</E>
                         There are two or more secondary diagnoses on the home health-specific comorbidity subgroup interaction list that are associated with higher resource use when both are reported together compared to when they are reported separately. That is, the two diagnoses may interact with one another, resulting in higher resource use.
                    </P>
                    <P>
                        • 
                        <E T="03">Low comorbidity adjustment:</E>
                         There is a reported secondary diagnosis on the home health-specific comorbidity subgroup list that is associated with higher resource use.
                    </P>
                    <P>
                        • 
                        <E T="03">No comorbidity adjustment:</E>
                         There is no secondary diagnosis or there is a secondary diagnosis that does not meet the criteria for a low or high comorbidity adjustment.
                    </P>
                    <P>In the CY 2019 HH PPS final rule with comment period (83 FR 56406), we stated that we will continue to examine the relationship of reported comorbidities on resource utilization and make the appropriate payment refinements to help ensure that payment is in alignment with the actual costs of providing care. For CY 2027, we are proposing to use the same methodology used to establish the comorbidity subgroups to update the comorbidity subgroups using CY 2025 home health data with linked OASIS data (as of March 15, 2026).</P>
                    <P>
                        For CY 2027, we are proposing to update the comorbidity subgroups to include 21 low comorbidity adjustment subgroups and 100 high comorbidity adjustment interaction subgroups. The proposed CY 2027 low comorbidity adjustment subgroups and the high comorbidity adjustment interaction subgroups including those diagnoses within each of these comorbidity adjustments are shown in tables 21 and 22. The proposed CY 2027 low comorbidity adjustment subgroups and the high comorbidity adjustment interaction subgroups including those diagnoses within each of these comorbidity adjustments will also be posted on the HHA Center web page at 
                        <E T="03">https://www.cms.gov/medicare/enrollment-renewal/providers-suppliers/home-health-agency-center.</E>
                    </P>
                    <P>We invite comments on the proposed updates to the low comorbidity adjustment subgroups and the high comorbidity adjustment interactions for CY 2027.</P>
                    <BILCOD>BILLING CODE 4169-69-P</BILCOD>
                    <GPH SPAN="3" DEEP="536">
                        <PRTPAGE P="41245"/>
                        <GID>EP06JY26.047</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41246"/>
                        <GID>EP06JY26.048</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41247"/>
                        <GID>EP06JY26.049</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41248"/>
                        <GID>EP06JY26.050</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41249"/>
                        <GID>EP06JY26.051</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41250"/>
                        <GID>EP06JY26.052</GID>
                    </GPH>
                    <GPH SPAN="1" DEEP="640">
                        <PRTPAGE P="41251"/>
                        <GID>EP06JY26.053</GID>
                    </GPH>
                    <BILCOD>BILLING CODE 4169-69-C</BILCOD>
                    <HD SOURCE="HD3">4. Proposed CY 2027 PDGM Case-Mix Weights</HD>
                    <P>As finalized in the CY 2019 HH PPS final rule with comment period (83 FR 56502), the PDGM places patients into meaningful payment categories based on patient and other characteristics, such as timing, admission source, clinical grouping using the reported principal diagnosis, functional impairment level, and comorbid conditions. The PDGM case-mix methodology results in 432 unique case-mix groups called home health resource groups (HHRGs). We also finalized a policy in the CY 2019 HH PPS final rule with comment period (83 FR 56515) to annually recalibrate the PDGM case-mix weights using a fixed effects model with the most recent and complete utilization data available at the time of annual rulemaking. Annual recalibration of the PDGM case-mix weights ensures that the case-mix weights reflect, as accurately as possible, current home health resource use and changes in utilization patterns. To generate the proposed recalibrated CY 2027 case-mix weights, we used CY 2025 home health claims data with linked OASIS data (as of March 15, 2026). These data are the most current and complete data available at the time of rulemaking. We believe that recalibrating the case-mix weights using data from CY 2025 would be reflective of PDGM utilization and patient resource use for CY 2027. The proposed recalibrated case-mix weights will be updated in the final rule based on more complete CY 2025 claims data.</P>
                    <P>The claims data provide visit-level data and data on whether non-routine supplies (NRS) were provided during the period and the total charges of NRS. We determine the case-mix weight for each of the 432 different PDGM payment groups by regressing resource use on a series of indicator variables for each of the categories using a fixed effects model as described in the following steps:</P>
                    <P>
                        <E T="03">Step 1:</E>
                         Estimate a regression model to assign a functional impairment level to each 30-day period. The regression model estimates the relationship between a 30-day period's resource use and the functional status and risk of hospitalization items included in the PDGM, which are obtained from certain OASIS items. We refer readers to table 19 for further information on the OASIS items used for the functional impairment level under the PDGM. We measure resource use with the cost-per-minute + NRS approach that uses information from 2023 home health cost reports. We use 2023 home health cost report data because it is the most complete cost report data available at the time of rulemaking. Other variables in the regression model include the 30-day period's admission source, clinical group, and 30-day period timing. We also include home health agency level fixed effects in the regression model. After estimating the regression model using 30-day periods, we divide the coefficients that correspond to the functional status and risk of hospitalization items by 10 and round to the nearest whole number. Those rounded numbers are used to compute a functional score for each 30-day period by summing together the rounded numbers for the functional status and risk of hospitalization items that are applicable to each 30-day period. Next, each 30-day period is assigned to a functional impairment level (low, medium, or high) depending on the 30-day period's total functional score. Each clinical group has a separate set of functional thresholds used to assign 30-day periods into a low, medium or high functional impairment level. We set those thresholds so that we assign roughly a third of 30-day periods within each clinical group to each functional impairment level (low, medium, or high).
                    </P>
                    <P>
                        <E T="03">Step 2:</E>
                         A second regression model estimates the relationship between a 30-day period's resource use and indicator variables for the presence of any of the comorbidities and comorbidity interactions that were originally examined for inclusion in the PDGM. Like the first regression model, this model also includes home health agency level fixed effects and includes control variables for each 30-day period's admission source, clinical group, timing, and functional impairment level. After we estimate the model, we assign comorbidities to the low comorbidity adjustment if any comorbidities have a coefficient that is statistically significant (p-value of 0.05 or less) and which have a coefficient that is larger than the 50th percentile of positive and statistically significant comorbidity coefficients. If two comorbidities in the model and their interaction term have coefficients that sum together to exceed $150 and the interaction term is statistically significant (p-value of 0.05 or less), we assign the two comorbidities together to the high comorbidity adjustment.
                    </P>
                    <P>
                        <E T="03">Step 3:</E>
                         After Step 2, each 30-day period is assigned to a clinical group, admission source category, episode timing category, functional impairment level, and comorbidity adjustment category. For each combination of those variables (which represent the 432 different payment groups that comprise 
                        <PRTPAGE P="41252"/>
                        the PDGM), we then calculate the 10th percentile of visits across all 30-day periods within a particular payment group. If a 30-day period's number of visits is less than the 10th percentile for their payment group, the 30-day period is classified as a Low Utilization Payment Adjustment (LUPA). If a payment group has a 10th percentile of visits that is less than two, we set the LUPA threshold for that payment group to be equal to two. That means if a 30-day period has one visit, it is classified as a LUPA and if it has two or more visits, it is not classified as a LUPA.
                    </P>
                    <P>
                        <E T="03">Step 4:</E>
                         Take all non-LUPA 30-day periods and regress resource use on the 30-day period's clinical group, admission source category, episode timing category, functional impairment level, and comorbidity adjustment category. The regression includes fixed effects at the level of the home health agency. After we estimate the model, the model coefficients are used to predict each 30-day period's resource use. To create the case-mix weight for each 30-day period, the predicted resource use is divided by the overall resource use of the 30-day periods used to estimate the regression.
                    </P>
                    <P>The case-mix weight is then used to adjust the base payment rate to determine each 30-day period's payment. Table 23 shows the coefficients of the payment regression used to generate the weights, and the coefficients divided by average resource use.</P>
                    <BILCOD>BILLING CODE 4169-69-P</BILCOD>
                    <GPH SPAN="3" DEEP="633">
                        <PRTPAGE P="41253"/>
                        <GID>EP06JY26.054</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="559">
                        <PRTPAGE P="41254"/>
                        <GID>EP06JY26.055</GID>
                    </GPH>
                    <BILCOD>BILLING CODE 4169-69-C</BILCOD>
                    <P>
                        The proposed case-mix weights for CY 2027 are listed in table 24 and will also be posted on the HHA Center web page at 
                        <E T="03">https://www.cms.gov/Center/Provider-Type/Home-Health-Agency-HHA-Center</E>
                         upon display of this proposed rule.
                    </P>
                    <BILCOD>BILLING CODE 4169-69-P</BILCOD>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41255"/>
                        <GID>EP06JY26.056</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41256"/>
                        <GID>EP06JY26.057</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41257"/>
                        <GID>EP06JY26.058</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41258"/>
                        <GID>EP06JY26.059</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41259"/>
                        <GID>EP06JY26.060</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41260"/>
                        <GID>EP06JY26.061</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41261"/>
                        <GID>EP06JY26.062</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41262"/>
                        <GID>EP06JY26.063</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41263"/>
                        <GID>EP06JY26.064</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41264"/>
                        <GID>EP06JY26.065</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41265"/>
                        <GID>EP06JY26.066</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41266"/>
                        <GID>EP06JY26.067</GID>
                    </GPH>
                    <BILCOD>BILLING CODE 4169-69-C</BILCOD>
                    <P>
                        Changes to the PDGM case-mix weights are implemented in a budget neutral manner by multiplying the CY 2027 national standardized 30-day 
                        <PRTPAGE P="41267"/>
                        period payment rate by a case-mix budget neutrality factor. Typically, the case-mix weight recalibration neutrality factor is also calculated using the most recent, complete home health claims data available. For CY 2027, we would continue the practice of using the most recent complete home health claims data at the time of rulemaking, which is currently CY 2025 data. The case-mix budget neutrality factor is calculated as the ratio of 30-day base payment rates such that total payments when the CY 2027 PDGM case-mix weights (developed using CY 2025 home health claims data) are applied to CY 2025 utilization (claims) data are equal to total payments when CY 2026 PDGM case-mix weights (developed using CY 2024 home health claims data) are applied to CY 2025 utilization data. This produces a case-mix budget neutrality factor for CY 2027 of 1.0045.
                    </P>
                    <P>We invite public comments on the CY 2027 proposed case-mix weights and proposed case-mix weight budget neutrality factor.</P>
                    <HD SOURCE="HD2">E. Proposed CY 2027 Home Health Payment Rate Updates</HD>
                    <HD SOURCE="HD3">1. Proposed CY 2027 Home Health Market Basket Update for HHAs</HD>
                    <P>Section 1895(b)(3)(B) of the Act requires that the standard prospective payment amounts for home health be increased by a factor equal to the applicable home health market basket update for those HHAs that submit quality data as required by the Secretary. In the CY 2024 HH PPS final rule (88 FR 77726), we finalized a rebasing of the home health market basket to reflect 2021 cost report data. We also finalized a policy for CY 2024 and subsequent years that the labor-related share is 74.9 percent, and the non-labor-related share is 25.1 percent. A detailed description of how we rebased the home health market basket and labor-related share is available in the CY 2024 HH PPS final rule (88 FR 77726 through 77742).</P>
                    <P>
                        In the CY 2015 HH PPS final rule (79 FR 38384), we finalized our methodology for calculating and applying the productivity adjustment. As we explained in that rule, section 1895(b)(3)(B)(vi) of the Act, requires that, in CY 2015 (and in subsequent calendar years, except CY 2018 (under section 411(c) of the Medicare Access and CHIP Reauthorization Act of 2015 (MACRA) (Pub. L. 114-10, enacted April 16, 2015)), the market basket percentage under the HH PPS as described in section 1895(b)(3)(B) of the Act be annually adjusted by changes in economy-wide productivity. Section 1886(b)(3)(B)(xi)(II) of the Act defines the productivity adjustment as equal to the 10-year moving average of change in annual economy-wide private nonfarm business multifactor productivity (as projected by the Secretary for the 10-year period ending with the applicable fiscal year, calendar year, cost reporting period, or other annual period). The Bureau of Labor Statistics (BLS) publishes the official measures of productivity for the United States economy. The productivity measure referenced in section 1886(b)(3)(B)(xi)(II) of the Act is published by BLS as private nonfarm business total factor productivity (TFP) (previously referred to as multifactor productivity).
                        <SU>5</SU>
                        <FTREF/>
                         We refer readers to 
                        <E T="03">https://www.bls.gov/productivity</E>
                         for the BLS historical published TFP data. A complete description of IHS Global Inc.'s (IGI) TFP projection methodology is available on the CMS website at 
                        <E T="03">https://www.cms.gov/data-research/statistics-trends-and-reports/medicare-program-rates-statistics/market-basket-research-and-information.</E>
                    </P>
                    <FTNT>
                        <P>
                            <SU>5</SU>
                             
                            <E T="03">https://www.bls.gov/productivity/notices/2021/mfp-to-tfp-term-change.htm.</E>
                        </P>
                    </FTNT>
                    <P>The proposed home health update percentage for CY 2027 is based on the estimated home health market basket percentage increase, specified at section 1895(b)(3)(B)(iii) of the Act of 3.1 percent (based on IHS Global Inc.'s first quarter 2026 forecast with historical data through fourth quarter 2025). The estimated CY 2027 proposed home health market basket percentage increase of 3.1 percent would then be reduced by a productivity adjustment, in accordance with section 1895(b)(3)(B)(vi) of the Act. Based on IGI's first quarter 2026 forecast, the proposed productivity adjustment is currently estimated to be 1.0 percentage point for CY 2027. Therefore, the proposed productivity-adjusted CY 2027 home health market basket update is 2.1 percent (3.1 percent market basket percentage increase, reduced by a 1.0 percentage point productivity adjustment). Furthermore, we are proposing that if more recent data become available (for example, a more recent estimate of the market basket percentage increase and/or productivity adjustment), we would use such data, if appropriate, to determine the CY 2027 market basket percentage increase and productivity adjustment in the final rule.</P>
                    <P>Section 1895(b)(3)(B)(v) of the Act requires that the home health percentage update be decreased by 2 percentage points for those HHAs that do not submit quality data as required by the Secretary. For HHAs that do not submit the required quality data for CY 2027, the proposed home health payment update percentage is 0.1 percent (2.1 percent minus 2 percentage points).</P>
                    <P>We invite public comments on the proposed CY 2027 home health market basket percentage increase and productivity adjustment.</P>
                    <HD SOURCE="HD3">2. Proposed CY 2027 Home Health Wage Index</HD>
                    <HD SOURCE="HD3">a. Background</HD>
                    <P>Sections 1895(b)(4)(A)(ii) and (b)(4)(C) of the Act require the Secretary to provide appropriate adjustments to the proportion of the payment amount under the HH PPS that account for area wage differences, using adjustment factors that reflect the relative level of wages and wage-related costs applicable to the furnishing of home health services. Since the inception of the HH PPS, we have used inpatient hospital wage data in developing a wage index to be applied to home health payments. We are proposing to continue this practice for CY 2027, as it is our belief that, in the absence of home health-specific wage data that accounts for area differences, using inpatient hospital wage data, including any changes made by the Office of Management and Budget (OMB) to Metropolitan Statistical Area (MSA) definitions, is appropriate and reasonable for the HH PPS.</P>
                    <P>
                        In general, OMB issues major revisions to statistical areas every 10 years, based on the results of the decennial census. However, OMB occasionally issues minor updates and revisions to statistical areas in the years between the decennial censuses. On April 10, 2018, OMB issued OMB Bulletin No. 18-03, which superseded the August 15, 2017, OMB Bulletin No. 17-01. On September 14, 2018, OMB issued OMB Bulletin No. 18-04 which superseded the April 10, 2018, OMB Bulletin No. 18-03. These bulletins established revised delineations for Metropolitan Statistical Areas, Micropolitan Statistical Areas, and Combined Statistical Areas, and provided guidance on the use of the delineations of these statistical areas. A copy of OMB Bulletin No. 18-04 may be obtained at 
                        <E T="03">https://www.whitehouse.gov/wp-content/uploads/2018/09/Bulletin-18-04.pdf.</E>
                         In the CY 2021 HH PPS final rule (85 FR 70298), we finalized our proposal to adopt the revised OMB delineations with a 5 percent cap on wage index decreases in CY 2021.
                        <PRTPAGE P="41268"/>
                    </P>
                    <P>
                        On July 21, 2023, OMB issued Bulletin No. 23-01, which updates and supersedes OMB Bulletin No. 20-01, issued on March 6, 2020. OMB Bulletin No. 23-01 establishes revised delineations for the MSAs, Micropolitan Statistical Areas, Combined Statistical Areas, and Metropolitan Divisions, collectively referred to as Core Based Statistical Areas (CBSAs). A copy of OMB Bulletin No. 23-01 is available online at 
                        <E T="03">https://www.whitehouse.gov/wp-content/uploads/2023/07/OMB-Bulletin-23-01.pdf.</E>
                    </P>
                    <P>
                        According to OMB, the delineations from OMB Bulletin 23-01 reflect the 2020 Standards for Delineating Core Based Statistical Areas (CBSAs) (the “2020 Standards”), which appeared in the 
                        <E T="04">Federal Register</E>
                         (86 FR 37770 through 37778) on July 16, 2021, and application of those standards to Census Bureau population and journey-to-work data (for example, 2020 Decennial Census, American Community Survey, and Census Population Estimates Program data). The OMB “2020 Standards” define a “Metropolitan Statistical Area” as being associated with at least one Urban Area that has a population of at least 50,000 and a “Micropolitan Statistical Area” as being associated with at least one Urban Area that has a population of at least 10,000, but less than 50,000 (86 FR 37778).
                    </P>
                    <P>In the CY 2025 HH PPS final rule (89 FR 88354), we finalized our proposal to adopt the revised OMB delineations from OMB Bulletin 23-01 with a 5 percent cap on wage index decreases at the CBSA level as well as at the county level. In that final rule we stated that we believe it is important for the HH PPS wage index to use the latest OMB delineations available in order to maintain a more accurate and up-to-date payment system that reflects the reality of population shifts and labor market conditions. We also stated that we believe using the most current OMB delineations will increase the integrity of the HH PPS wage index by creating a more accurate representation of geographic variation in wage levels. In conjunction with our implementation of the revised labor market delineations beginning in CY 2025, and consistent with the treatment of Micropolitan Statistical Areas under the Inpatient Prospective Payment System (IPPS), we also finalized continuing to treat Micropolitan Statistical Areas as “rural” and including Micropolitan Statistical Areas in the calculation of each state's statewide rural wage index. Therefore, the HH PPS statewide rural wage index is determined using IPPS hospital data from hospitals located in Micropolitan Statistical Areas and the HH PPS wage index for each CBSA is determined using IPPS hospital data from hospitals located in Metropolitan Statistical Areas.</P>
                    <HD SOURCE="HD3">b. Five Percent Cap on Wage Index Decreases</HD>
                    <P>In the CY 2023 HH PPS final rule (87 FR 66851 through 66853), we finalized a policy that the CY HH PPS wage index will include a permanent 5 percent cap on wage index decreases for CY 2023 and each subsequent year. Specifically, we finalized, for CY 2023 and subsequent years, the application of a permanent 5 percent cap on any decrease to a geographic area's wage index from its wage index in the prior year, regardless of the circumstances causing the decline. That is, we finalized a policy requiring that a geographic area's wage index for CY 2023 will not be less than 95 percent of its final wage index for CY 2022, regardless of whether the geographic area is part of an updated CBSA, and that for subsequent years, a geographic area's wage index will not be less than 95 percent of its wage index calculated in the prior CY.</P>
                    <P>Previously this methodology was applied to all counties that make up a CBSA or statewide rural area. However, in the CY 2025 HH PPS final rule (89 FR 88418 through 88421), because of the adoption of the revised OMB delineations from OMB Bulletin 23-01, we finalized a policy applying this methodology to individual counties. Specifically, we finalized a policy applying the 5 percent cap to counties that moved from a CBSA or statewide rural area with a higher wage index value into a new CBSA or statewide rural area with a lower wage index value, so that the county's CY 2025 wage index would not be less than 95 percent of the county's CY 2024 wage index value under the old delineation despite moving into a new delineation with a lower wage index.</P>
                    <P>Due to the way that we proposed calculating the 5 percent cap for counties that experienced an OMB designation change, some CBSAs and statewide rural areas could have had more than one wage index value. Specifically, some counties that changed OMB designations had a wage index value that was different than the wage index value assigned to the other constituent counties that made up that CBSA or statewide rural area that they moved into after the application of the 5 percent cap. However, for home health claims processing, each CBSA or statewide rural area can have only one wage index value assigned to that CBSA or statewide rural area. Therefore, we finalized a policy, beginning in CY 2025, that counties that have a different wage index value than the CBSA or rural area into which they are designated after the application of the 5 percent cap will use a wage index transition code. These special codes are five digits in length and begin with “50” and the remaining digits are unique for that code. The 50XXX wage index transition codes are used only in specific counties; counties located in CBSAs and rural areas that do not correspond to a different transition wage index value will still use the CBSA number.</P>
                    <P>We also finalized a policy applying the 5 percent cap to these specific counties that correspond to a different wage index value due to a delineation change until the county's new wage index is more than 95 percent of the wage index from the previous calendar year. In order to capture the correct wage index value, an HHA will continue to use the assigned 50XXX transition code on home health claims for services in these counties until the county's wage index value calculated for that calendar year using the new OMB delineations is not less than 95 percent of the county's capped wage index from the previous calendar year.</P>
                    <P>For CY 2027, the 5 percent cap on wage index decreases will continue to be calculated at the county level as well as the CBSA and statewide rural area level. While some counties that required a transition code for CY 2025 and CY 2026 will continue to use the same transition code for CY 2027, other counties that required a transition code in CY 2025 and CY 2026 will no longer require a transition code in CY 2027. The counties that will no longer require a transition code beginning in CY 2027 have a CY 2027 wage index value in the CBSA or rural area that the county was redesignated into that is higher than 95 percent of the county's CY 2026 wage index. Therefore, these counties will use the CBSA or rural county code of the area into which they were redesignated based on OMB Bulletin No. 23-01.</P>
                    <P>
                        The complete list of counties and corresponding transition codes can be found as a separate tab in the calendar year's wage index file located on the CMS website at 
                        <E T="03">https://www.cms.gov/medicare/payment/prospective-payment-systems/home-health-pps/home-health-pps-wage-index.</E>
                    </P>
                    <HD SOURCE="HD3">c. Proposed CY 2027 HH PPS Wage Index</HD>
                    <P>
                        The appropriate wage index value is applied to the labor portion of the HH PPS rates based on the site of service for the beneficiary (defined in section 
                        <PRTPAGE P="41269"/>
                        1861(m) of the Act as the beneficiary's place of residence). For CY 2027, we are proposing to base the HH PPS wage index on the FY 2027 hospital pre-floor, pre-reclassified wage index for hospital cost reporting periods beginning on or after October 1, 2022, and before October 1, 2023 (FY 2023 cost report data). The proposed CY 2027 HH PPS wage index would not take into account any geographic reclassification of hospitals, including those in accordance with sections 1886(d)(8)(B) or 1886(d)(10) of the Act but would include the 5 percent cap on wage index decreases as discussed previously.
                    </P>
                    <P>There exist some geographic areas where there are no hospitals, and thus, no hospital wage data on which to base the calculation of the HH PPS wage index. To address those geographic areas in which there are no inpatient hospitals, and thus, no hospital wage data on which to base the calculation of the CY 2027 HH PPS wage index, we are proposing to continue to use the same methodology discussed in the CY 2007 HH PPS final rule (71 FR 65884) to address those geographic areas in which there are no inpatient hospitals.</P>
                    <P>For urban areas without inpatient hospitals, we use the average wage index of all urban areas within the State as a reasonable proxy for the wage index for that CBSA. For CY 2027, the only urban area without inpatient hospital wage data is Hinesville, GA (CBSA 25980). Using the average wage index of all urban areas in Georgia as a proxy, we are proposing the CY 2027 wage index value for Hinesville, GA, would be 0.8797.</P>
                    <P>For rural areas that do not have inpatient hospitals, we use the average wage index from all contiguous Core Based Statistical Areas (CBSAs) as a reasonable proxy. The term “contiguous” means sharing a border (72 FR 49859). In the CY 2025 HH PPS final rule (89 FR 88422), we finalized a policy that rural North Dakota would become a rural area without a hospital from which hospital wage data can be derived. Therefore, in order to calculate the wage index for rural area 99935, North Dakota, we finalized using as a proxy, the average pre-floor, pre-reclassified hospital wage data from the contiguous CBSAs: CBSA 13900-Bismark, ND, CBSA 22020-Fargo, ND-MN, CBSA 24220-Grand Forks, ND-MN, and CBSA 33500, Minot, ND. Using this methodology, we are proposing that the CY 2027 HH PPS wage index for rural North Dakota would be 0.8210.</P>
                    <P>Previously, the only rural area without a hospital from which hospital wage data could be derived was rural Puerto Rico. However, for rural Puerto Rico, we did not apply this methodology due to the distinct economic circumstances that exist there (for example, due to the proximity of almost all of Puerto Rico's various urban and non-urban areas to one another, this methodology would produce a wage index for rural Puerto Rico that is higher than that in half of its urban areas). Instead, we used the most recent wage index previously available for that area, which was 0.4047. Beginning in CY 2025, due to the adoption of the revised OMB delineations, there is now a hospital in rural Puerto Rico from which hospital wage data can be derived. Therefore, we finalized a policy that the wage index for rural Puerto Rico would now be based on the hospital wage data for the area instead of the previously available wage index of 0.4047.</P>
                    <P>The unadjusted CY 2027 proposed wage index for rural Puerto Rico is 0.2577. However, because 0.2577 is more than a 5 percent decline in the CY 2026 wage index, we are proposing that the CY 2027 5 percent cap adjusted wage index for rural Puerto Rico be set equal to 95 percent of the CY 2026 wage index of 0.3653, which would result in a proposed wage index value of 0.3470.</P>
                    <P>Additionally, due to the adoption of the revised OMB delineations in the CY 2025 HH PPS final rule, Delaware, which was previously an all-urban state, now has one rural area with a hospital from which hospital wage data can be derived. As such, we are proposing that the CY 2026 wage index for rural Delaware would be 0.9590.</P>
                    <P>Finally, the Northern Mariana Islands and American Samoa are rural areas with no hospital data from which a wage index can be calculated. In the CY 2026 HH PPS Wage Index and Rate Update final rule (90 FR 55405), using our established methodology for rural areas with no hospitals, we finalized that for CY 2026 and subsequent years, HHAs that provide services in the Northern Mariana Islands and American Samoa would use CBSA 99965 (Guam) and receive the wage index assigned to CBSA 99965 (Guam) of 0.9611. While we appreciate that the islands of the Pacific Rim are not actually contiguous, we believe that same principle applies here, and that Guam is a reasonable proxy for American Samoa and the Northern Mariana Islands. We believe that CBSA 99965 (Guam) represents a reasonable proxy because the islands are located within the Pacific Rim and share a common status as United States Territories.</P>
                    <P>
                        The proposed HH PPS wage index file applicable for CY 2027 (January 1, 2027, through December 31, 2027) is available on the CMS website at 
                        <E T="03">https://www.cms.gov/medicare/enrollment-renewal/providers-suppliers/home-health-agency-center.</E>
                    </P>
                    <HD SOURCE="HD3">3. Proposed CY 2027 Home Health Payment Update</HD>
                    <HD SOURCE="HD3">a. Background</HD>
                    <P>The HH PPS has been in effect since October 1, 2000. As set forth in the July 3, 2000, HH PPS final rule (65 FR 41128), the base unit of payment under the HH PPS was a national, standardized 60-day episode payment rate. As finalized in the CY 2019 HH PPS final rule with comment period (83 FR 56406), and as described in the CY 2020 HH PPS final rule with comment period (84 FR 60478), the unit of home health payment changed from a 60-day episode to a 30-day period effective for those 30-day periods beginning on or after January 1, 2020.</P>
                    <P>As set forth in § 484.220, we adjust the national, standardized prospective payment rates by a case-mix relative weight and a wage index value based on the site of service for the beneficiary. To provide appropriate adjustments to the proportion of the payment amount under the HH PPS to account for area wage differences, we apply the appropriate wage index value to the labor portion of the HH PPS rates. In the CY 2024 HH PPS final rule (88 FR 77676), we finalized the rebasing of the home health market basket to reflect 2021 Medicare cost report data. We also finalized a policy that, for CY 2024 and subsequent years, the labor-related share is 74.9 percent, and the non-labor-related share is 25.1 percent. The following are the steps we take to compute the case-mix and wage-adjusted 30-day period payment amount for CY 2027:</P>
                    <P>• Multiply the national, standardized 30-day period rate by the patient's applicable case-mix weight.</P>
                    <P>• Divide the case-mix adjusted amount into a labor (74.9 percent) and a non-labor portion (25.1 percent).</P>
                    <P>• Multiply the labor portion by the applicable wage index based on the site of service of the beneficiary.</P>
                    <P>• Add the wage-adjusted portion to the non-labor portion, yielding the case-mix and wage adjusted 30-day period payment amount, subject to any additional applicable adjustments.</P>
                    <P>
                        We provide annual updates of the HH PPS rate in accordance with section 1895(b)(3)(B) of the Act. Section 484.225 sets forth the specific annual percentage update methodology. In accordance with section 1895(b)(3)(B)(v) of the Act and § 484.225(i), for an HHA that does not submit home health quality data, as specified by the Secretary, the 
                        <PRTPAGE P="41270"/>
                        unadjusted national prospective 30-day period rate is equal to the rate for the previous calendar year increased by the applicable home health payment update percentage, minus two percentage points. Any reduction of the percentage change will apply only to the calendar year involved and will not be considered in computing the prospective payment amount for a subsequent calendar year.
                    </P>
                    <P>The final claim that the HHA submits for payment determines the total payment amount for the period and whether we make an applicable adjustment to the 30-day case-mix and wage-adjusted payment amount. The end date of the 30-day period, as reported on the claim, determines which calendar year rates Medicare would use to pay the claim.</P>
                    <P>We may adjust a 30-day case-mix and wage-adjusted payment based on the information submitted on the claim to reflect the following:</P>
                    <P>• A LUPA is provided on a per-visit basis as set forth in §§ 484.205(d)(1) and 484.230.</P>
                    <P>• A partial payment adjustment as set forth in §§ 484.205(d)(2) and 484.235.</P>
                    <P>• An outlier payment as set forth in §§ 484.205(d)(3) and 484.240.</P>
                    <HD SOURCE="HD3">b. Proposed CY 2027 National, Standardized 30-Day Period Payment Amount</HD>
                    <P>Section 1895(b)(3)(A)(i) of the Act requires that the standard prospective payment rate and other applicable amounts be standardized in a manner that eliminates the effects of variations in relative case-mix and area wage adjustments among different home health agencies in a budget-neutral manner. To determine the CY 2027 national, standardized 30-day period payment rate, we would continue our practice of using the most recent, complete utilization data at the time of rulemaking; that is, we are using CY 2025 claims data for CY 2027 payment rate updates.</P>
                    <P>As discussed in section II.C.1. of the CY 2026 HH PPS final rule (90 FR 55406), we finalized the implementation of a temporary 3.0 percent reduction to the CY 2026 base payment rate that was equivalent to a final temporary adjustment factor of 0.97000. Per section 1895(b)(3)(D)(iii) of the Act, a temporary adjustment is to be applied for the applicable year and not included when computing a payment rate for a subsequent year. In other words, the temporary adjustment factor for CY 2026 will not be included in the starting payment rate for CY 2027. Therefore, we calculated the CY 2026 national, standardized 30-day period payment with and without the temporary adjustment factor.</P>
                    <P>To calculate the CY 2027 national, standardized 30-day period payment amount, we begin with the actual CY 2026 national standardized 30-day period payment amount (with the temporary adjustment factor included) and apply an adjustment factor of 1.03093 (which is equal to 1 divided by the CY 2026 temporary adjustment factor of 0.97000) to remove the temporary adjustment factor as shown in table 25.</P>
                    <GPH SPAN="3" DEEP="162">
                        <GID>EP06JY26.068</GID>
                    </GPH>
                    <P>We apply a case-mix weights recalibration budget neutrality factor, a wage index budget neutrality factor, the home health payment update percentage, and a temporary adjustment factor to update the CY 2027 payment rate. As discussed previously, to ensure the changes to the PDGM case-mix weights are implemented in a budget neutral manner, we apply a case-mix weight budget neutrality factor to the CY 2027 national, standardized 30-day period payment rate. The proposed case-mix weight budget neutrality factor for CY 2027 is 1.0045.</P>
                    <P>Additionally, we apply a wage index budget neutrality factor to ensure that wage index updates and revisions are implemented in a budget neutral manner. To calculate the wage index budget neutrality factor, we first determine the payment rate needed for non-LUPA 30-day periods using the CY 2027 wage index (with the 5 percent cap) so those total payments are equivalent to the total payments for non-LUPA 30-day periods using the CY 2026 wage index (with the 5 percent cap) and the CY 2026 national standardized 30-day period payment rate adjusted by the case-mix weights recalibration neutrality factor. Then, by dividing the payment rate for non-LUPA 30-day periods using the CY 2027 wage index with the 5 percent cap on wage index decreases) by the payment rate for non-LUPA 30-day periods using the CY 2026 wage index (with the 5 percent cap on wage index decreases), we obtain a wage index budget neutrality factor of 1.0009. We then apply the wage index budget neutrality factor of 1.0009 to the 30-day period payment rate.</P>
                    <P>
                        Next, we update the 30-day period payment rate by the proposed CY 2027 home health payment update percentage of 2.1 percent. As discussed in section II.C.1. of this proposed rule, we are also proposing to apply the temporary 3.0 percent reduction to the CY 2027 base payment rate. The proposed temporary adjustment factor is 0.97000. As discussed previously, per section 1895(b)(3)(D)(iii) of the Act, the temporary adjustment is to be applied for the applicable year and not included when computing a payment rate for a subsequent year. In other words, the temporary adjustment factor for CY 2027 should not be included in the starting payment rate for CY 2028. Therefore, we have calculated the CY 
                        <PRTPAGE P="41271"/>
                        2027 national, standardized 30-day period payment with and without the temporary adjustment factor. The CY 2027 national standardized 30-day period payment rate without a temporary adjustment is only for illustrative purposes. The actual CY 2027 national standardized 30-day period payment rate includes the proposed temporary adjustment and is calculated in table 26.
                    </P>
                    <GPH SPAN="3" DEEP="197">
                        <GID>EP06JY26.069</GID>
                    </GPH>
                    <P>The proposed CY 2027 national standardized 30-day period payment rate for an HHA that does not submit the required quality data would be updated by 0.1 percent (the proposed CY 2027 home health payment update percentage of 2.1 percent minus 2 percentage points) and is shown in table 27.</P>
                    <GPH SPAN="3" DEEP="187">
                        <GID>EP06JY26.070</GID>
                    </GPH>
                    <HD SOURCE="HD3">c. Proposed CY 2027 National Per-Visit Rates for 30-day Periods of Care</HD>
                    <P>The national per-visit rates are used to pay LUPAs and are also used to compute imputed costs in outlier calculations. The per-visit rates are paid by type of visit or home health discipline. The six home health disciplines are as follows:</P>
                    <FP SOURCE="FP-1">• Home health aide (HH aide).</FP>
                    <FP SOURCE="FP-1">• Medical Social Services (MSS).</FP>
                    <FP SOURCE="FP-1">• Occupational therapy (OT).</FP>
                    <FP SOURCE="FP-1">• Physical therapy (PT).</FP>
                    <FP SOURCE="FP-1">• Skilled nursing (SN).</FP>
                    <FP SOURCE="FP-1">• Speech-language pathology (SLP).</FP>
                    <P>
                        To calculate the proposed CY 2027 national per-visit rates, we start with the CY 2026 national per-visit rates. Then we apply a wage index budget neutrality factor to ensure budget neutrality for LUPA per-visit payments. We calculate the wage index budget neutrality factor by simulating total payments for LUPA 30-day periods of care using the CY 2027 wage index with the 5 percent cap on wage index decreases and comparing it to simulated total payments for LUPA 30-day periods of care using the CY 2026 wage index with the 5 percent cap. By dividing the total payments for LUPA 30-day periods of care using the CY 2027 wage index by the total payments for LUPA 30-day periods of care using the CY 2026 wage index, we obtain a wage index budget neutrality factor of 0.9997. As a reminder, the wage index budget neutrality factors for the national, standardized 30-day period amount and the national LUPA per-visit rates are not equal because they are calculated differently. The wage index budget neutrality factor for the LUPA per-visit payments is calculated by simulating total payments for LUPA 30-day periods while the 30-day period 
                        <PRTPAGE P="41272"/>
                        budget neutrality factor is calculated by simulating payments for non-LUPA 30-day periods.
                    </P>
                    <P>The LUPA per-visit rates are not calculated using case-mix weights. Therefore, no case-mix weight budget neutrality factor is needed to ensure budget neutrality for LUPA payments. Additionally, we are not applying the permanent adjustment or the temporary adjustment to the LUPA per-visit payment rates but only to the case-mix adjusted 30-day payment rate. Lastly, the per-visit rates for each discipline are updated by the proposed CY 2027 home health payment update percentage of 2.1 percent. The national per-visit rates are adjusted by the wage index based on the site of service of the beneficiary. The per-visit payments for LUPAs are separate from the LUPA add-on payment amount, which is paid for periods that occur as the only period or initial period in a sequence of adjacent periods. The proposed CY 2027 national per-visit rates for HHAs that submit the required quality data are updated by the proposed CY 2027 home health payment update percentage of 2.1 percent and are shown in table 28.</P>
                    <GPH SPAN="3" DEEP="180">
                        <GID>EP06JY26.071</GID>
                    </GPH>
                    <P>The CY 2027 per-visit payment rates for HHAs that do not submit the required quality data would be updated by 0.1 percent, which is the proposed CY 2027 home health payment update percentage of 2.1 percent minus 2 percentage points and are shown in table 29.</P>
                    <GPH SPAN="3" DEEP="245">
                        <GID>EP06JY26.072</GID>
                    </GPH>
                    <P>We are soliciting comments on the proposed CY 2027 30-day home health payment rates and the per-visit payment rates.</P>
                    <HD SOURCE="HD3">d. LUPA Add-On Factors</HD>
                    <P>
                        Prior to the implementation of the 30-day unit of payment, LUPA episodes were eligible for a LUPA add-on payment if the episode of care was the first or only episode in a sequence of adjacent episodes. As described in the CY 2008 HH PPS final rule, the average visit lengths in these initial LUPAs are 16 to 18 percent higher than the average 
                        <PRTPAGE P="41273"/>
                        visit lengths in initial non-LUPA episodes (72 FR 49848). LUPA episodes that occur as the only episode or as an initial episode in a sequence of adjacent episodes are adjusted by applying an additional amount to the LUPA payment before adjusting for area wage differences.
                    </P>
                    <P>In the CY 2014 HH PPS final rule (78 FR 72305), we changed the methodology for calculating the LUPA add-on amount, whereby we finalized the approach of multiplying the per-visit payment amount for the first skilled nursing (SN), physical therapy (PT), or speech language pathology (SLP) visit in LUPA episodes that occur as the only episode or an initial episode in a sequence of adjacent episodes by 1 + the proportional increase in minutes for an initial visit over non-initial visits. Specifically, we updated the analysis using 100 percent of LUPA episodes and a 20 percent sample of non-LUPA first episodes from CY 2012 claims data. At that time, we finalized add-on factors: 1.8451 for SN; 1.6700 for PT; and 1.6266 for SLP. In the CY 2019 HH PPS final rule with comment period (83 FR 56440), in addition to finalizing a 30-day unit of payment, we finalized our policy of continuing to multiply the per-visit payment amount for the first SN, PT, or SLP visit in LUPA periods that occur as the only period of care or the initial 30-day period of care in a sequence of adjacent 30-day periods of care by the appropriate add-on factor (using the already established LUPA add-on factors of 1.8451 for SN, 1.6700 for PT, and 1.6266 for SLP) to determine the LUPA add-on payment amount for 30-day periods of care under the PDGM.</P>
                    <P>In the CY 2025 HH PPS final rule (89 FR 88426 through 88427), in an effort to enhance the accuracy and relevance of LUPA add-on factors to reflect current healthcare practices and costs, we finalized updates to the LUPA add-on factors for PT, SN, and SLP, which had not been revised since the CY 2014 HH PPS final rule (using CY 2012 claims data). We finalized using the same methodology to establish the LUPA add-on amount as used for CY 2014, using updated claims data.</P>
                    <P>Specifically, in CY 2025, we updated the LUPA add-on factors by using 100 percent of LUPA periods and a 100 percent sample of non-LUPA first periods from CY 2023 claims data (as of September 11, 2024). Our analysis found that the average excess of minutes for the first visit in LUPA periods that were the only period or an initial LUPA in a sequence of adjacent periods are 29.91 minutes for the first visit if SN, 28.08 minutes for the first visit if PT, and 31.57 minutes for the first visit if SLP. The average minutes for all non-first visits in non-LUPA episodes are 41.54 minutes for SN, 45.11 minutes for PT, and 47.15 minutes for SLP. To determine the LUPA add-on factors for each discipline, we calculated the ratio of the average excess minutes for the first visits in LUPA claims to the average minutes for all non-first visits in non-LUPA claims. We then added one to these ratios to obtain the final add on factors. Therefore, beginning in CY 2025 the final LUPA add on factors for SN, PT, and SLP are 1.7200 for SN; 1.6225 for PT; and 1.6696 for SLP.</P>
                    <P>Additionally, as outlined in the CY 2025 HH PPS proposed rule (89 FR 55378), in order to implement Division CC, section 115, of the Consolidation Appropriations Act (CAA), 2021, CMS finalized changes to the regulations at §  484.55(a)(2) and (b)(3) that allowed occupational therapists to conduct initial and comprehensive assessments for all Medicare beneficiaries under the home health benefit when the plan of care does not initially include skilled nursing care, but included OT, as well as either PT or SLP (86 FR 62351). This change necessitated the establishment of a LUPA add-on factor for calculating the LUPA add-on payment amount for the first skilled OT visit in LUPA periods that occur as the only period of care or the initial 30-day period of care in a sequence of adjacent 30-day periods of care. However, at the time of the implementation, we stated in the CY 2022 HH PPS final rule (86 FR 62289), there was not sufficient data regarding the average excess minutes for the first visit in LUPA periods when the initial and comprehensive assessments are conducted by occupational therapists. Therefore, we finalized a policy using the PT LUPA add-on factor as a proxy. We also stated in the CY 2022 final rule that we will use the PT LUPA add-on factor as a proxy until we have CY 2022 data to establish a more accurate OT add-on factor for the LUPA add-on payment amounts (86 FR 62289). Ultimately, we refrained from using CY 2022 data (and instead utilized the PT LUPA add-on factor as a proxy for the OT LUPA add-on factor), as we marked the first year that occupational therapists were permitted to conduct the initial assessment. We wanted to extend our analysis to ensure we had sufficient data to reflect OT time spent conducting initial assessments to establish a discrete OT LUPA add-on factor (86 FR 62240).</P>
                    <P>In the CY 2025 HH PPS final rule (89 FR 88427), we finalized discontinuing the use of the PT LUPA add-on factor as a proxy and established a definitive LUPA add-on factor for OT. We used the same methodology used to establish the LUPA add-on amount for CY 2014, as described previously for the SN, PT, and SLP add-on factors. Specifically, we updated the analysis using 100 percent of LUPA periods and a 100 percent sample of non-LUPA first periods from CY 2023 claims data. Using updated analysis (as of September 11, 2024), we found that the average excess of minutes for the first OT visit in LUPA periods that were the only period or an initial LUPA in a sequence of adjacent periods is 33.28 minutes for the first visit. The average number of minutes for all non-first visits in non-LUPA periods is 45.98 minutes for OT. To determine the LUPA add-on factor for OT to account for the excess minutes during the first visit in a LUPA period, we finalized calculating the ratio of the average excess minutes for the first visits in LUPA claims to the average minutes for all non-first visits in non-LUPA claims. We then added one to this ratio to obtain the final add on factor of 1.7238 for OT. Therefore, the OT LUPA factor of 1.7238 is used when occupational therapy is the first skilled visit in a LUPA period that occurs as the only period or an initial period in a sequence of adjacent periods.</P>
                    <GPH SPAN="3" DEEP="95">
                        <GID>EP06JY26.073</GID>
                    </GPH>
                    <PRTPAGE P="41274"/>
                    <HD SOURCE="HD3">4. Payments for High-Cost Outliers Under the HH PPS</HD>
                    <HD SOURCE="HD3">a. Background</HD>
                    <P>Section 1895(b)(5) of the Act allows for the provision of an addition or adjustment to the home health payment amount otherwise made in the case of outliers because of unusual variations in the type or amount of medically necessary care. Under the HH PPS and the previous unit of payment (that is, 60-day episodes), outlier payments were made for 60-day episodes whose estimated costs exceed a threshold amount for each HHRG. The episode's estimated cost was established as the sum of the national wage-adjusted per-visit payment amounts delivered during the episode. The outlier threshold for each case-mix group or PEP adjustment is defined as the 60-day episode payment or PEP adjustment for that group plus a fixed-dollar loss (FDL) amount. For the purposes of the HH PPS, the FDL amount is calculated by multiplying the home health FDL ratio by a case's wage-adjusted national, standardized 60-day episode payment rate, which yields an FDL dollar amount for the case. The outlier threshold amount is the sum of the wage and case-mix adjusted PPS episode amount and wage-adjusted FDL amount. The outlier payment is defined as a proportion of the wage-adjusted estimated cost that surpasses the wage-adjusted threshold. The proportion of additional costs over the outlier threshold amount paid as outlier payments is referred to as the loss-sharing ratio.</P>
                    <P>As we noted in the CY 2011 HH PPS final rule (75 FR 70397 through 70399), section 3131(b)(1) of the Affordable Care Act amended section 1895(b)(3)(C) of the Act to require that the Secretary reduce the HH PPS payment rates such that aggregate HH PPS payments were reduced by 5 percent. In addition, section 3131(b)(2) of the Affordable Care Act amended section 1895(b)(5) of the Act by redesignating the existing language as section 1895(b)(5)(A) of the Act and revised the language to state that the total amount of the additional payments or payment adjustments for outlier episodes could not exceed 2.5 percent of the estimated total HH PPS payments for that year. Section 3131(b)(2)(C) of the Affordable Care Act also added section 1895(b)(5)(B) of the Act, which capped outlier payments as a percent of total payments for each HHA for each year at 10 percent.</P>
                    <P>As such, beginning in CY 2011, we reduced payment rates by 5 percent and targeted up to 2.5 percent of total estimated HH PPS payments to be paid as outliers. To do so, we first returned the 2.5 percent held for the target CY 2010 outlier pool to the national, standardized 60-day episode rates, the national per visit rates, the LUPA add-on payment amount, and the NRS conversion factor for CY 2010. We then reduced the rates by 5 percent as required by section 1895(b)(3)(C) of the Act, as amended by section 3131(b)(1) of the Affordable Care Act. For CY 2011 and subsequent calendar years we targeted up to 2.5 percent of estimated total payments to be paid as outlier payments, and apply a 10-percent agency-level outlier cap.</P>
                    <P>In the CY 2017 HH PPS proposed and final rules (81 FR 43737 through 43742 and 81 FR 76702), we described our concerns regarding patterns observed in home health outlier episodes. Specifically, we noted the methodology for calculating home health outlier payments may have created a financial incentive for providers to increase the number of visits during an episode of care in order to surpass the outlier threshold and simultaneously created a disincentive for providers to treat medically complex beneficiaries who require fewer but longer visits. Given these concerns, in the CY 2017 HH PPS final rule (81 FR 76702), we finalized changes to the methodology used to calculate outlier payments, using a cost-per-unit approach rather than a cost-per-visit approach. This change in methodology allows for more accurate payment for outlier episodes, accounting for both the number of visits during an episode of care and the length of the visits provided. Using this approach, we now convert the national per-visit rates into per 15-minute unit rates. These per 15-minute unit rates are used to calculate the estimated cost of an episode to determine whether the claim would receive an outlier payment and the amount of payment for an episode of care. In conjunction with our finalized policy to change to a cost-per-unit approach to estimate episode costs and determine whether an outlier episode should receive outlier payments, in the CY 2017 HH PPS final rule we also finalized the implementation of a cap on the amount of time per day that would be counted toward the estimation of an episode's costs for outlier calculation purposes (81 FR 76725). Specifically, we limit the amount of time per day (summed across the six disciplines of care) to 8 hours (32 units) per day when estimating the cost of an episode for outlier calculation purposes.</P>
                    <P>In the CY 2017 HH PPS final rule (81 FR 76724), we stated that we did not plan to re-estimate the average minutes per visit by discipline every year. Additionally, the per unit rates used to estimate an episode's cost were updated by the home health update percentage each year, meaning we would start with the national per visit amounts for the same calendar year when calculating the cost-per-unit used to determine the cost of an episode of care (81 FR 76727). We would continue to monitor the visit length by discipline as more recent data becomes available and may propose updating the rates as needed in the future.</P>
                    <P>In the CY 2019 HH PPS final rule with comment period (83 FR 56521), we finalized a policy to maintain the current methodology for payment of high-cost outliers upon implementation of PDGM beginning in CY 2020 and calculated payment for high-cost outliers based upon 30-day period of care. Upon implementation of the PDGM and 30-day unit of payment, we finalized the FDL ratio of 0.56 for 30-day periods of care in CY 2020.</P>
                    <P>In the CY 2021 HH PPS final rule (85 FR 70322), given that CY 2020 was the first year of the PDGM and the change to a 30-day unit of payment, we finalized maintaining the same FDL ratio of 0.56 in CY 2021 as we did not have sufficient CY 2020 data at the time of CY 2021 rulemaking to propose a change to the FDL ratio for CY 2021. In the CY 2022 HH PPS final rule with comment period (86 FR 62292), we estimated that outlier payments would be approximately 1.8 percent of total HH PPS payments in CY 2022 if we maintained an FDL of 0.56. Therefore, in order to pay up to, but no more than, 2.5 percent of total payments as outlier payments we finalized an FDL of 0.40 for CY 2022. In the CY 2023 HH PPS final rule (87 FR 66875), using CY 2021 claims utilization data, we finalized an FDL of 0.35 in order to pay up to, but no more than, 2.5 percent of the total payment as outlier payments in CY 2023. In the CY 2024 HH PPS final rule (88 FR 77749), using CY 2022 claims utilization data, we finalized an FDL of 0.27 for CY 2024. In the CY 2025 HH PPS final rule (89 FR 88354), using CY 2023 claims data (as of July 11, 2024) we finalized an FDL ratio of 0.35 for CY 2025. In the CY 2026 HH PPS final rule (90 FR 55411), using CY 2024 claims data (as of July 11, 2025) we finalized an FDL ratio of 0.37 for CY 2026.</P>
                    <HD SOURCE="HD3">b. Proposed FDL Ratio for CY 2027</HD>
                    <P>
                        For a given level of outlier payments, there is a trade-off between the values selected for the FDL ratio and the loss-sharing ratio. A high FDL ratio reduces the number of periods that can receive outlier payments but makes it possible to select a higher loss-sharing ratio, and 
                        <PRTPAGE P="41275"/>
                        therefore, increase outlier payments for qualifying outlier periods. Alternatively, a lower FDL ratio means that more periods can qualify for outlier payments, but outlier payments per period must be lower.
                    </P>
                    <P>The FDL ratio and the loss-sharing ratio are selected so that the estimated total outlier payments do not exceed the 2.5 percent aggregate level (as required by section 1895(b)(5)(A) of the Act). We use a value of 0.80 for the loss-sharing ratio, which we believe preserves incentives for agencies to attempt to provide care efficiently for outlier cases. With a loss-sharing ratio of 0.80, Medicare pays 80 percent of the additional estimated costs that exceed the outlier threshold amount.</P>
                    <P>Using CY 2025 claims data (as of March 12, 2026) and given the statutory requirement that total outlier payments do not exceed 2.5 percent of the total payments estimated to be made under the HH PPS, we are proposing an FDL ratio of 0.29 for CY 2027. We also propose to update the FDL ratio in the final rule based on more complete CY 2025 claims data.</P>
                    <HD SOURCE="HD2">F. Palliative Care Services as Home Health Services</HD>
                    <P>CMS is seeking to advance its broader goal of promoting access to and utilization of palliative care services, with a particular focus on expanding opportunities for beneficiaries to receive these services under the Medicare home health benefit. As part of this effort, CMS included a Request for Information (RFI) in the FY 2027 Hospice Wage Index and Payment Rate Update proposed rule (91 FR 17359) to solicit public input on potential policy, operational, and payment approaches to strengthen and enhance the delivery of palliative care services outside of the hospice benefit. We were especially interested in hearing more about how Medicare practitioners and post-acute care providers furnish community-based palliative care, well as opportunities for improvement. We stated we believe that, as palliative care is a method of care delivery that is provided throughout the continuum of illness, it can be furnished under various Medicare benefits. We also stated that the home is an ideal environment for individuals to receive palliative care services, as remaining in the home during a serious illness may help alleviate psychological and mental distress and allow for more intimate caregiving to be provided by family members. As such, we believe the Medicare home health benefit can be an important step in the care continuum when a patient needs palliative care, either during episodes of serious illness or near end of life, before choosing hospice care.</P>
                    <P>
                        In accordance with § 409.42(c), to qualify for Medicare coverage of home health services, a beneficiary must need skilled services as set out at § 409.32. Section 409.32(a) states that “[t]o be considered a skilled service, the service must be so inherently complex that it can be safely and effectively performed only by, or under the supervision of, professional or technical personnel.” Under the home health benefit, a beneficiary's unique condition and individual needs should be considered in deciding whether skilled nursing care is reasonable and necessary, without regard to whether the illness or injury is acute, chronic, terminal, or expected to extend over a long period of time. There are no expectations that life-prolonging therapies will be avoided or that the patient must be considered terminally ill, and the restoration potential of a patient is not the deciding factor in determining whether skilled services are needed. Even if full recovery or medical improvement is not possible, a patient may need skilled services to prevent further deterioration or preserve current capabilities. Further, as discussed in chapter seven of the Medicare Benefit Policy Manual (BPM),
                        <SU>6</SU>
                        <FTREF/>
                         it is an allowed practitioner, as defined at 
                        <E T="03">§ 484.2,</E>
                         who is familiar with the patient who determines whether a skilled service is reasonable and necessary based on the patient's individual care needs and goals, and accepted standards of medical and nursing practice. Therefore, if the beneficiary meets the qualifications for coverage of services as set out at § 409.42, he or she could receive palliative care services under the home health benefit, if ordered by an allowed practitioner.
                    </P>
                    <FTNT>
                        <P>
                            <SU>6</SU>
                             
                            <E T="03">https://www.cms.gov/Regulations-and-Guidance/Guidance/Manuals/Downloads/bp102c07.pdf.</E>
                        </P>
                    </FTNT>
                    <P>
                        Often skilled services are determined to be reasonable and necessary when a patient has multiple medications and comorbidities, with resultant functional impairments, that leave them homebound with a need for skilled observation of the patient's condition and medication management. A discussion on palliative care delivery in the home emphasizes the importance of home-based care for patients with multiple morbidities and limited mobility.
                        <SU>7</SU>
                        <FTREF/>
                         The structure of the PDGM allows, in general, for palliative care services to be most appropriately grouped into the medication, management, teaching, and assessment (MMTA) clinical group. As discussed in the CY 2019 HH PPS proposed rule (83 FR 32402), health teaching; guidance and counseling; case management, treatments and procedures; and surveillance are integral to the care of most home health patients. Palliative care is defined at § 418.3 to mean “patient and family-centered care that optimizes quality of life by anticipating, preventing, and treating suffering. Palliative care throughout the continuum of illness involves addressing physical, intellectual, emotional, social, and spiritual needs and to facilitate patient autonomy, access to information, and choice.” We believe that this definition encompasses all the services provided under the Medicare home health benefit. Additionally, these important interventions are often the primary reason for home health services. Section 1861(m) of the Act requires the 30-day period to include all covered home health services: skilled nursing; home health aide; physical therapy; speech-language pathology; occupational therapy; medical social services, and medical supplies. Skilled nursing services can address advanced symptom management, including specialized care to manage pain, nausea and vomiting, depression and anxiety, and respiratory distress. This may also include medication management to monitor therapeutic and adverse effects and review and adjust medications in coordination with allowed practitioners. Medical social services can help address advance care planning needs (including discussion on transition to hospice) as well as offer referrals for social and emotional support for families and caregivers. Physical therapists (PTs), occupational therapists (OTs), and speech language pathologists (SLPs) enhance patient quality of life, comfort, and dignity by maximizing functional independence and managing symptoms. PTs focus on mobility, pain management, and safe transfers, while OTs specialize in adapting activities of daily living (ADLs) and environments to maintain independence for as long as possible. SLPs support safe eating and drinking and help facilitate 
                        <PRTPAGE P="41276"/>
                        communication and decision making for those patients with deficits.
                    </P>
                    <FTNT>
                        <P>
                            <SU>7</SU>
                             National Academies of Sciences, Engineering, and Medicine; Health and Medicine Division; Board on Health Sciences Policy; Board on Health Care Services; Roundtable on Quality Care for People with Serious Illness. Models and Strategies to Integrate Palliative Care Principles into Care for People with Serious Illness: Proceedings of a Workshop. Washington (DC): National Academies Press (US); 2017 Oct 24. Proceedings of a Workshop. Available from: 
                            <E T="03">https://www.ncbi.nlm.nih.gov/books/NBK538355/.</E>
                        </P>
                    </FTNT>
                    <P>Like other skilled services, comprehensive home health clinical notes are expected to substantiate the need for palliative care necessitating medication management, teaching, and assessment through documentation of the patient's achievement of care needs and goals as outlined in the plan of care. Accordingly, chapter seven of the BPM includes an example of a patient with malignant melanoma who is terminally ill and requires skilled observation, assessment, teaching, and treatment, and who has not elected hospice care. This example explains that the documentation should describe the goal of the skilled nursing intervention, and at each visit the services provided should support that goal. The skilled nursing care that the patient requires would be covered, notwithstanding that the condition is terminal, because the documentation and description must support that the needed services required the skills of a nurse. A palliative care plan for this type of patient would likely include medication and symptom management, including expected treatment responses for pain, anxiety, constipation, nausea, or dyspnea; education and caregiver training on managing symptoms at home; assessing social risk factors including caregiver burden and emotional and psychosocial distress; and skilled therapy for non-pharmacologic pain management strategies and interventions to maximize functional status and independence.</P>
                    <P>We plan on adding additional palliative care examples of skilled care to the BPM following the publication of the CY 2027 HH PPS final rule to support our goal of encouraging community-based palliative care services, particularly under the Medicare home health benefit. We solicit comments on any concerns or suggestions regarding reaching this goal.</P>
                    <HD SOURCE="HD2">G. Request for Information on the Construction of a Home Health Specific Wage Index</HD>
                    <P>For CY 2027, we are proposing to continue to use the concurrent pre-floor, pre-reclassified IPPS hospital wage index as the basis for the HH PPS wage index. We continue to believe that this is the best available Medicare data to estimate costs per day, in accordance with our longstanding wage index policy at §  412.424(a)(2). The purpose of this comment solicitation is to gain information from the public regarding the appropriateness of alternative data sources consistent with our statutory authority and regulatory requirements. We note that other payment systems have explored and are exploring alternative wage index methodologies under their specific programmatic and statutory circumstances. For example, CMS finalized changes to the ESRD PPS wage index using Bureau of Labor Statistics (BLS) occupation-level wage data in the CY 2025 ESRD PPS final rule (89 FR 89116). While this approach was developed under the specific programmatic and statutory circumstances of the ESRD PPS and may not be directly transferable to the HH PPS, CMS is interested in exploring whether similar methodologies using publicly available wage data could be used to better reflect the geographic variation in labor costs for HHAs. In addition, we note that we are also considering the potential use of alternative data sources in other payment systems, including with respect to hospices (91 FR 17361 through 17363), the Inpatient Rehabilitation Facilities PPS (91 FR 17206 and 17207), and the Skilled Nursing Facilities PPS (91 FR 17692).</P>
                    <P>
                        Furthermore, in its 2023 Report to the Congress,
                        <SU>8</SU>
                        <FTREF/>
                         MedPAC discussed various conceptual approaches to Medicare wage indexes, including the use of county-level wage data from BLS with an occupational mix to construct wage indexes that are more specific to the payment setting. MedPAC has previously written about using all-employer, occupation-level wage data to establish different weights for setting-specific occupational labor mixes as one approach to geographic adjustments.
                    </P>
                    <FTNT>
                        <P>
                            <SU>8</SU>
                             
                            <E T="03">https://www.medpac.gov/document/chapter-9-reforming-medicares-wage-index-systems-june-2023-report/.</E>
                        </P>
                    </FTNT>
                    <P>We are soliciting comments on whether we should consider using alternative data sources to construct an HHA specific wage index for potential use in future years. CMS seeks feedback to understand the potential advantages and limitations of using alternative data sources, such as BLS data and home health Medicare cost reports, as well as other methodologies that stakeholders believe could appropriately reflect the geographic variation in labor costs for HHAs. We also seek feedback on the unique considerations applicable to HHAs that should inform how CMS considers the potential use of alternative data sources.</P>
                    <HD SOURCE="HD1">III. Home Health Quality Reporting Program (HH QRP)</HD>
                    <HD SOURCE="HD2">A. Background and Statutory Authority</HD>
                    <P>The HH QRP is authorized by section 1895(b)(3)(B)(v) of the Act. Section 1895(b)(3)(B)(v)(II) of the Act requires that, for 2007 and subsequent years, each home health agency (HHA) submit to the Secretary in a form and manner, and at a time, specified by the Secretary, such data that the Secretary determines are appropriate for the measurement of health care quality. To the extent that an HHA does not submit data in accordance with this clause, the Secretary shall reduce the home health market basket percentage increase applicable to the HHA for such year by 2 percentage points pursuant to section 1895(b)(3)(B)(v)(I) of the Act. As provided at section 1895(b)(3)(B)(vi) of the Act, depending on the market basket percentage increase applicable for a particular year, as further reduced by the productivity adjustment (except in 2018 and 2020) described in section 1886(b)(3)(B)(xi)(II) of the Act, the reduction of that increase by 2 percentage points for failure to comply with the requirements of the HH QRP may result in the home health market basket percentage increase being less than 0.0 percent for a year, and may result in payment rates under the HH PPS for a year being less than payment rates for the preceding year. Section 1890A of the Act requires that the Secretary establish and follow a pre-rulemaking process, in coordination with the consensus-based entity (CBE) with a contract under section 1890 of the Act, to solicit input from certain groups regarding the selection of quality and efficiency measures for the HH QRP. The HH QRP regulations can be found at 42 CFR 484.245 and 484.250.</P>
                    <HD SOURCE="HD2">B. Summary of the Provisions of This Proposed Rule</HD>
                    <P>In accordance with the statutory authority at section 1895(b)(3)(B)(v) of the Act, we are proposing the following policies in this proposed rule:</P>
                    <P>First, we summarize potential initiatives to improve alignment between the HH QRP and expanded HHVBP Model. We also propose to revise the HH QRP data submission deadlines beginning with the CY 2027 HH QRP. In addition, we are proposing to revise the HH QRP OASIS and HHCAHPs annual payment update (APU) reporting timeframe to report a calendar year of data (January 1 through December 31). We propose some revisions to regulatory text in support of rule proposals and to improve digital transfer of information during the reconsiderations process. Finally, we are soliciting public comments on one Request for Information (RFI) on future measure concepts for the HH QRP.</P>
                    <P>
                        For a detailed discussion of the considerations we historically use for measure selection for the HH QRP 
                        <PRTPAGE P="41277"/>
                        quality, resource use, and other measures, we refer readers to the CY 2016 HH PPS final rule (80 FR 68695 through 68696). In the CY 2019 HH PPS final rule with comment period (83 FR 56548 through 56550), we finalized the factors we consider for removing previously adopted HH QRP measures.
                    </P>
                    <HD SOURCE="HD2">C. Quality Measures Currently Adopted for the CY 2026 HH QRP</HD>
                    <P>The HH QRP currently includes 18 measures for the CY 2027 program year. As finalized in the CY 2026 HH PPS final rule, the HH QRP currently uses thirteen OASIS-based measures, four claims-based measures, and a HHCAHPS Survey-based composite measure (see table 31).</P>
                    <HD SOURCE="HD2">D. Opportunities for Potential Alignment Between the HH QRP and the Expanded HHVBP Model</HD>
                    <P>CMS has identified substantial opportunities to better align the HH QRP and the expanded HHVBP Model. While the HH QRP and expanded HHVBP Model share similar goals and measures, differences in measure sets, reporting periods, and performance assessment processes may create unnecessary complexity and administrative burden for HHAs. For example, misalignment between HH QRP APU reporting periods and the expanded HHVBP Model's annual performance period may contribute to confusion. Greater alignment would support more consistent evaluation of HHA quality performance and advance CMS quality priorities. Greater alignment is also consistent with CMS's priority of reducing provider burden and creating efficiencies across CMS programs. Opportunities for potential alignment between the HH QRP and expanded HHVBP Model include the following:</P>
                    <P>• Increasing alignment in expanded HHVBP Model and HH QRP Quality of Patient Care (QoPC) Star Ratings measure sets.</P>
                    <P>• Aligning HH QRP and expanded HHVBP Model measure reporting periods.</P>
                    <P>• Aligning HH QRP APU and expanded HHVBP Model annual payment reporting periods.</P>
                    <P>• Aligning expanded HHVBP Model Interim Performance and HH QRP QoPC Star Rating Reports.</P>
                    <P>• Aligning timeframe of appeals/suppression review processes for the expanded HHVBP Model and HH QRP.</P>
                    <P>• Updating scoring methodology to incorporate HH QRP APU penalties in expanded HHVBP Model payment adjustments and factoring HH QRP Quality Assessments Only (QAO) values into QoPC Star Ratings scoring.</P>
                    <P>We are not seeking comments on this list of opportunities for potential alignment between the HH QRP and expanded HHVBP Model and is providing this list for general awareness of potential areas of alignment that are being considered.</P>
                    <P>
                        We convened a Technical Expert Panel (TEP) meeting addressing HH QRP and expanded HHVBP Model alignment in December 2025. Please see the 2025 TEP Summary Report for more information (
                        <E T="03">www.cms.gov/priorities/innovation/files/hhvbp-tep-summary-report.pdf</E>
                        ).
                    </P>
                    <P>Table 31 reflects current and expected usage of measures for both the expanded HHVBP Model and the HH QRP.</P>
                    <GPH SPAN="3" DEEP="432">
                        <PRTPAGE P="41278"/>
                        <GID>EP06JY26.074</GID>
                    </GPH>
                    <HD SOURCE="HD2">E. Form, Manner, and Timing of Data Submission Under the HH QRP</HD>
                    <HD SOURCE="HD3">1. Proposal To Revise HH QRP Data Submission Deadlines Beginning With the CY 2027 HH QRP</HD>
                    <HD SOURCE="HD3">a. Background</HD>
                    <P>Section 1899B(f)(1) of the Act also requires the Secretary to provide confidential feedback reports to PAC providers on the performance of such PAC providers for quality, resource use, and other measures required under sections 1899B(c)(1) and (d)(1) of the Act beginning 1 year after the applicable specified application date. Further, section 1899B(g) of the Act requires the Secretary to establish procedures for making available to the public information regarding the performance of individual PAC providers for quality, resource use, and other measures required under sections 1899B(c)(1) and (d)(1) of the Act beginning not later than 2 years after the applicable specified application date. The procedures must ensure, including through a process consistent with the process applied under section 1886(b)(3)(B)(viii)(VII) of the Act for similar purposes, that each PAC provider has the opportunity to review and submit corrections to the data and information that are to be made public for the PAC provider prior to such data being made public.</P>
                    <P>Although assessment data submission, quarterly performance reports, and public reporting are required by statute, timing of data submission under the HH QRP was not initially specified. Thus, in the CY 2017 HHS PPS final rule (81 FR 76784) we finalized our proposal to comply with the requirements of section 1899B(g) of the Act, that HHAs would have approximately 4.5 months after the reporting quarter to correct any errors of their assessment-based data to calculate the measures. During the time of data submission for a given quarterly reporting period and up until the quarterly submission deadline, HHAs could review and perform corrections to errors in the assessment data used to calculate the measures.</P>
                    <P>
                        Public reporting of data collected under our quality reporting programs, such as the HH QRP, is designed to provide consumers and their families with the most current information to empower them to make quality-informed decisions about where to receive their care. We have identified that the time between when data on measures is submitted to us and when those data are publicly reported (approximately nine months) may be too long to provide the most accurate and up to date information for the public. 
                        <PRTPAGE P="41279"/>
                        We have received feedback from the provider community and TEPs that the aged data used in publicly reported quality measures diminishes their value to consumers. Furthermore, we have heard from HHAs that the HH QRP measure results they receive prior to public reporting are less useful for their quality improvement efforts due to the aged data and the delay in when they receive these reports.
                    </P>
                    <P>Currently, the largest contributing factor to the 9-month lag between the end of the data collection period and when measures are publicly reported is the 4.5-month timeframe for data submission. Reducing the data submission timeframe from 4.5 months to the 15th day of the second month after the end of the calendar quarter could reduce this lag by up to 3 months, resulting in more timely public reporting of data for consumers and increasing the value of publicly reported data. Additionally, this timeframe provides HHAs with more recent data in support of their quality improvement activities.</P>
                    <P>In the CY 2026 HH PPS proposed rule, we included a request for information (RFI) on reducing the OASIS assessment data submission deadline from 4.5 months to 45 days (90 FR 29182). We refer readers to the CY 2026 HH PPS final rule (90 FR 55429 and 55430) for a full summary of the public comments received.</P>
                    <HD SOURCE="HD3">b. Proposal To Revise the HH QRP Assessment Data Submission Deadline</HD>
                    <P>Beginning with the CY 2027 HH QRP, we are proposing that HHAs be required to complete their data submissions and make corrections to their OASIS assessment data where necessary no later than the 15th day of the second month after the end of the calendar quarter. However, if the 15th day of the second month falls on a Friday, weekend, or Federal holiday, the date is delayed until 11:59 p.m. EST on the next business day. We are proposing that HHAs would follow the deadlines presented in Table 32 for the CY 2027 HH QRP. We are also proposing that similar calendar year data submission deadlines would apply to future years' payment determinations.</P>
                    <GPH SPAN="3" DEEP="145">
                        <GID>EP06JY26.075</GID>
                    </GPH>
                    <P>We believe that requiring HHAs to submit OASIS assessment data by the 15th day of the second month after the end of the calendar quarter is reasonable. We conducted an analysis on the potential impact of reducing the timeframe by determining how many assessments are currently being submitted by this deadline, which is approximately within 45 days of the end of the quarter. Using 2024 data, we identified that 99.27 percent of all OASIS assessments were submitted to CMS within a 45-day timeframe. Of the remaining 0.63 percent submitted beyond 45 days, 0.24 percent were submitted after the current 4.5-month data submission deadline and would not be further impacted by a change in the data submission deadline. Therefore, only 0.49 percent of OASIS assessments would be impacted by changing the data submission deadline from 4.5 months to require data submission by the 15th day of the second month after the end of the calendar quarter.</P>
                    <P>We invite comment on this proposal to require that HHAs complete their data submissions and make corrections to their OASIS assessment data where necessary no later than the 15th day of the second month after the end of the calendar quarter beginning with the CY 2027 HH QRP.</P>
                    <HD SOURCE="HD3">2. Proposal To Revise the OASIS Annual Payment Update Reporting Timeframe</HD>
                    <HD SOURCE="HD3">a. Background</HD>
                    <P>HHAs are required to submit OASIS data in a timely manner as outlined under section 1895(b)(3)(B)(v) of the Act, as amended by the Deficit Reduction Act (Pub. L. 109-117). Failure to submit OASIS data in a timely manner with respect to a HH QRP year would result in the reduction of the annual home health market basket percentage increase otherwise applicable to an HHA for the corresponding calendar year by 2 percentage points. This annual payment update (APU) was initiated for the HH QRP on January 1, 2007. The HH QRP APU requirements were finalized in the CY 2007 HH PPS Final Rule (71 FR 44087 through 44088) outlining data collection of 12 months of data beginning July 1, 2005 and running through July 1, 2026. This timeframe allowed a full 12 months of data and provided CMS the time necessary to analyze and make any necessary payment adjustments to the CY 2007 payment rates (71 FR 44087 through 44088). The timing for APU reporting has remained on this data calculation cadence since this update.</P>
                    <P>
                        The current OASIS APU reporting timeframe differs from that used by other major CMS payment updates. Notably, the expanded HHVBP Model annual payment adjustment and the HH PPS updates are both based on a calendar year timeline. To improve alignment between HH payment policies and OASIS QRP reporting requirements, CMS is proposing to revise the OASIS APU data reporting timeframe to reflect a January 1 through December 31 reporting timeframe, or the calendar year. We believe this update would provide clarity to HH payment updates and facilitate the alignment of the HH pay-for-reporting policies with other HH payment policies.
                        <PRTPAGE P="41280"/>
                    </P>
                    <HD SOURCE="HD3">b. Proposal</HD>
                    <P>The proposed revision of the OASIS APU data reporting to a calendar year timeframe would require a transition year in which the current reporting timeframe is moved to the new proposed reporting timeframe. We propose the transition occur with the 2028 APU and further propose that the 6 months data collected from July 1, 2026 through December 31, 2026 would serve as the OASIS APU data reporting timeframe to determine the HH QRP 2028 OASIS APU. We also propose that the 2029 OASIS APU would be the first iteration in which the OASIS APU data reporting timeframe will be based on the calendar year, from January 1, 2027 through December 31, 2027. We would continue this new pattern for each subsequent OASIS APU with effective dates for data reporting of January 1 through December 31. OASIS assessments will be considered complete if they comply with the HH Conditions for Payment (COPs) that apply to the applicable year. Please see table 33 that outlines the current OASIS APU data reporting timeframe, the proposed transition reporting timeframe, and the revised OASIS APU timeframe used for the CY 2029 APU and later.</P>
                    <GPH SPAN="3" DEEP="81">
                        <GID>EP06JY26.076</GID>
                    </GPH>
                    <P>In the CY 2024 HH PPS final rule, CMS proposed adding the following language to the regulatory text at § 484.245(b)(2)(ii)(A): “A home health agency must meet or exceed the data submission threshold for each submission year (July 1-June 30) set at 90 percent of all required OASIS or successor instrument records and submitted through the CMS designated data submission systems ” (88 FR 77676). With the proposed change to a calendar year reporting timeframe, CMS proposes to revise the language in § 484.245(b)(2)(ii)(A) that currently states “(July 1-June 30)” to state “(January 1 through December 31)”.</P>
                    <HD SOURCE="HD3">3. Proposal To Revise the HHCAHPS Annual Payment Update Reporting Timeframe</HD>
                    <HD SOURCE="HD3">a. Background</HD>
                    <P>HHAs are required to submit quality data in a timely manner as outlined under section 1895(b)(3)(B)(v) of the Act. Failure to submit HHCAHPS data in a timely manner with respect to a HH QRP year could result in the reduction of the annual home health market basket percentage increase otherwise applicable to an HHA for the corresponding calendar year by 2 percentage points. HHCAHPS data inclusion in the HHQRP was finalized with the CY 2010 HH PPS Final Rule (FR 74 58098 through 58104). Adding a HHCAHPS annual payment update (APU) to the current HH QRP requirements was also finalized with the CY 2010 HH PPS Final Rule where CMS finalized the policy that HHCAHPS would be included in the APU reporting for the CY 2012 APU based on 6 months of data from October 2010 to March 2011 (FR 74 58103). In the CY 2011 HH PPS final rule, CMS finalized a policy that HHCAHPS APU calculations would require four quarters of data collection from April 1, 2011 to March 31, 2012 for the CY 2013 HH CAHPS APU (FR 75 70406). The timing for HHCAHPS APU reporting has remained on this cadence since this update.</P>
                    <P>The current HHCAHPS APU reporting timeframe differs from that used by other annual HH CMS payment updates. The expanded HHVBP Model payment adjustment percentage and the HH PPS updates are both based on a calendar year timeline. The OASIS APU data reporting timeframe is also different from a calendar year timeline and we are also proposing an update to a calendar year timeframe in a previous proposal. To improve alignment between home health payment policies and HH QRP pay-for-reporting requirements, we are proposing to revise the HHCAHPS APU data reporting timeframe to reflect a January 1 through December 31 reporting timeframe, or the calendar year. We believe this update would provide clarity related to HH payment updates and facilitate the alignment of CMS HH pay-for-reporting policies with other HH payment policies.</P>
                    <HD SOURCE="HD3">b. Proposal</HD>
                    <P>The proposed revision of the HHCAHPS APU data reporting to a calendar year timeframe would require a transition year in which the current reporting timeframe was moved to the new proposed reporting timeframe. We propose the transition occur with the 2028 HHCAHPS APU and further propose that the nine months of data collected from April 1, 2026 through December 31, 2026 would serve as the HHCAHPS APU data reporting timeframe to determine the HHQRP 2028 APU. We also propose that the 2029 HHCAHPS APU data reporting timeframe would be the first iteration in which the HHCAHPS APU data reporting timeframe would be for a calendar year, from January 1, 2027 through December 31, 2027. We would continue this new pattern for each subsequent HHCAHPS APU with effective dates for data reporting of January 1 through December 31. HHA OASIS assessments would be considered complete if they complied with the HH CoPs and Conditions for Payment that apply to the applicable year. Please see Table 34 that outlines the HHCAHPS current APU data reporting timeframe, the proposed transition reporting timeframe, and the revised APU timeframe used for the CY 2029 APU and later.</P>
                    <GPH SPAN="3" DEEP="89">
                        <PRTPAGE P="41281"/>
                        <GID>EP06JY26.077</GID>
                    </GPH>
                    <P>We invite comment on the proposals to revise the OASIS APU and HHCAHPS APU reporting timeframes to a calendar year period beginning with the CY 2027 HH QRP.</P>
                    <HD SOURCE="HD3">4. Proposed Updates to Regulation Text Related to Reconsiderations</HD>
                    <P>In the CY2026 HH PPS final rule, CMS updated regulation text language to codify how a provider may request an extension to file a reconsideration (90 FR 55342). We are proposing to further clarify aspects of the reconsideration process to facilitate more timely, digital transmission of information. Specifically, section 484.245(d)(1)(i) currently states, “HHAs that do not meet the quality reporting requirements under this section for a program year will receive a letter of noncompliance via the United States Postal Service and the CMS-designated data submission system”. We propose to revise this language to specify that HHAs that do not meet the quality reporting requirements under this section for a program year would receive a notification of noncompliance via the CMS-designated data submission system. Section 484.245(d)(1)(ii) currently states, an HHA may request reconsideration no later than 30 calendar days after the date identified on the letter of non-compliance. We propose to revise this language to state that an HHA may request reconsideration no later than 30 calendar days after the date identified on the notification of non-compliance. Section 484.245(d)(2)(v) currently states, CMS identified reason(s) for non-compliance as stated in the non-compliance letter. We propose to revise this language to state, CMS identified reason(s) for non-compliance as stated in the non-compliance notification.</P>
                    <P>Section 484.245(d)(4)(i) currently states that CMS notifies the HHA, in writing, of its final decision regarding any reconsideration request through at least one of the following methods:</P>
                    <P>• CMS designated data submission system.</P>
                    <P>• The United States Postal Service.</P>
                    <P>• Email from the CMS Medicare Administrative Contractor (MAC).</P>
                    <P>We propose to revise this language to state that CMS would notify the HHA of its final decision regarding any reconsideration request through a CMS designated data submission system.</P>
                    <P>We invite comments on these proposed updates to the regulations text related to the reconsideration process.</P>
                    <HD SOURCE="HD2">F. HH QRP Measure Concepts Under Consideration for Future Years—Request for Information (RFI)</HD>
                    <P>In the CY 2024 HH PPS proposed rule (88 FR 43738 through 43740), we included an RFI on a set of principles for selecting and prioritizing HH QRP measures, identifying measurement gaps, and suitable measures for filling these gaps. We refer readers to the CY 2024 HH PPS final rule (88 FR 77773 through 77774) for a summary of the public comments received in response to the RFI.</P>
                    <P>
                        We are seeking input on the importance, relevance, appropriateness, and applicability of the quality measure concepts related to advanced care planning. Advance care planning is a continuous process that supports people in understanding and communicating their goals, values, and preferences regarding future medical decisions.
                        <SU>9</SU>
                        <FTREF/>
                         The Patient Self Determination Act of 1990 
                        <SU>10</SU>
                        <FTREF/>
                         supports this process by requiring healthcare facilities to inform patients of their rights regarding medical decisions, including advance directives and end of life care.
                        <SU>11</SU>
                        <FTREF/>
                         In post-acute care (PAC) settings, where patients recover from acute illness, injury, or major procedures, their needs and goals may evolve as their condition changes. Factors such as clinical stability, functional status, therapy tolerance, cognition function, prognosis, and personal preferences can all shift during recovery. Regular reassessment and transparent communication are essential to maintaining person-centered care, while advance care planning facilitates shared decision-making by documenting patient preferences and ensuring goal-concordant care throughout care transitions.
                        <SU>12</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>9</SU>
                             McMahan, R.D., Tellez, I., &amp; Sudore, R.L. (2021). Deconstructing the Complexities of Advance Care Planning Outcomes: What Do We Know and Where Do We Go? A Scoping Review. Journal of the American Geriatrics Society, 69(1), 234-244. 
                            <E T="03">https://doi.org/10.1111/jgs.16801.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>10</SU>
                             Public Law 101-508, §§ 4206, 4751.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>11</SU>
                             
                            <E T="03">https://www.congress.gov/bill/101st-congress/house-bill/4449https://www.congress.gov/bill/101st-congress/house-bill/5835.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>12</SU>
                             McMahan RD, Tellez I, Sudore RL. Deconstructing the Complexities of Advance Care Planning Outcomes: What Do We Know and Where Do We Go? A Scoping Review. J Am Geriatr Soc. 2021 Jan;69(1):234-244. doi: 10.1111/jgs.16801. Epub 2020 Sep 7. PMID: 32894787; PMCID: PMC7856112.
                        </P>
                    </FTNT>
                    <P>As we review new measure concepts, we would prioritize evidence-based outcome measures that promote person-centered care practices. We are seeking input on the relevant aspects of advanced care planning and measures appropriate for the HH setting.</P>
                    <HD SOURCE="HD1">IV. The Expanded Home Health Value-Based Purchasing (HHVBP) Model</HD>
                    <P>As authorized by section 1115A of the Act and finalized in the CY 2016 HH PPS final rule (80 FR 68624), the Center for Medicare and Medicaid Innovation (Innovation Center) implemented the Home Health Value-Based Purchasing (HHVBP) Model (“original Model”) in nine states on January 1, 2016. The design of the original Model leveraged the successes and lessons learned from other CMS value-based purchasing programs and demonstrations to shift from volume-based payments to a model designed to promote the delivery of higher quality care to Medicare beneficiaries. The specific goals of the original Model were to—</P>
                    <P>• Provide higher incentives for better quality care with greater efficiency;</P>
                    <P>• Study new potential quality and efficiency measures for appropriateness in the home health setting; and</P>
                    <P>• Enhance the current public reporting process.</P>
                    <P>
                        On January 8, 2021, CMS announced the certification of the HHVBP Model for expansion nationwide, as well as the intent to expand the Model through notice and comment rulemaking.
                        <SU>13</SU>
                        <FTREF/>
                         In the CY 2022 HH PPS final rule (86 FR 62292 through 62336), we finalized the decision to expand the HHVBP Model to all Medicare certified HHAs in the 50 
                        <PRTPAGE P="41282"/>
                        States, territories, and District of Columbia beginning January 1, 2022. CY 2022 was a pre-implementation year. Payment adjustments under the Model are calculated in the year after each performance year and applied two years following each performance year. Therefore, payment adjustments for the first performance year of CY 2023 were implemented in CY 2025. Our codified policies for the expanded HHVBP Model can be found in our regulations at 42 CFR part 484, subpart F, §§ 484.300 through 484.375. The following description of existing HHVBP performance feedback reports is included for background and to provide context for the discussion of potential alignment between the HH QRP and the expanded HHVBP Model in section III of this proposed rule.
                    </P>
                    <FTNT>
                        <P>
                            <SU>13</SU>
                             
                            <E T="03">https://www.cms.gov/newsroom/press-releases/cms-takes-action-improve-home-health-care-seniors-announces-intent-expand-home-health-value-based.</E>
                        </P>
                    </FTNT>
                    <P>CMS publishes two types of routine performance feedback reports that provide HHAs with information on their measure performance:</P>
                    <P>• The first report type is the Interim Performance Report (IPR), which is issued quarterly. The information in the IPR reflects calculation of the TPS based on rolling data periods that are updated each quarter. CMS issues two versions of the IPR—a preliminary version and a final version that reflects any changes made as a result of the recalculation request process. The IPRs provide interim performance scores, achievement and improvement points, and TPS.</P>
                    <P>• The second report is the Annual Performance Report (APR). The APR provides HHAs with information on their measure performance using data from the prior calendar year. Like the IPR, the APR provides feedback to HHAs about performance relative to quality measure achievement thresholds, benchmarks, and improvement thresholds. Additionally, the APR includes the HHA's payment adjustment percentage for the upcoming CY, an explanation of when the adjustment will apply, and how CMS determined the adjustment.</P>
                    <P>We are not proposing any changes for the expanded HHVBP Model.</P>
                    <P>For more information on the policies we have adopted previously for the expanded HHVBP Model, we refer readers to the following:</P>
                    <FP SOURCE="FP-1">
                        • CY 2022 HH PPS final rule (
                        <E T="03">86 FR 62240</E>
                        ).
                    </FP>
                    <FP SOURCE="FP-1">
                        • CY 2023 HH PPS final rule (
                        <E T="03">87 FR 66790</E>
                        ).
                    </FP>
                    <FP SOURCE="FP-1">
                        • CY 2024 HH PPS final rule (
                        <E T="03">88 FR 77676</E>
                        ).
                    </FP>
                    <FP SOURCE="FP-1">
                        • CY 2025 HH PPS final rule (
                        <E T="03">89 FR 88354</E>
                        ).
                    </FP>
                    <FP SOURCE="FP-1">
                        • CY 2026 HH PPS final rule (
                        <E T="03">90 FR 55342</E>
                        ).
                    </FP>
                    <P>CY 2027 will be the fifth performance year for the expanded HHVBP Model. As finalized in the CY 2026 HH PPS final rule, the expanded HHVBP Model currently uses six OASIS-based measures, three claims-based measures, and two HHCAHPS Survey-based measures (see Table 31 in the HH QRP section (section III.) of this proposed rule). We continue to address the number of measures needed to maximize the number of HHAs in each cohort eligible for a payment adjustment.</P>
                    <P>CMS has identified substantial opportunities to better align the HH QRP and the expanded HHVBP Model, including measure-set alignment. Table 31 in section III. of this proposed rule reflects current and expected usage of measures for both the expanded HHVBP Model and the HH QRP. For more details on the potential alignment between the HH QRP and expanded HHVBP Model, see section III.D. of this proposed rule.</P>
                    <HD SOURCE="HD1">V. Durable Medical Equipment and Provider Enrollment Provisions</HD>
                    <HD SOURCE="HD2">A. Overview</HD>
                    <P>In this section of the proposed rule, we are proposing changes and seeking comment on the following DME and provide enrollment provisions:</P>
                    <P>• In section V.B. of the proposed rule, we would clarify the application of the DMEPOS face-to-face encounter requirements and the related documentation necessary to support the replacement of DMEPOS items.</P>
                    <P>• In section V.C. of the proposed rule, we are proposing a number of Medicare provider enrollment provisions to strengthen and clarify certain aspects of the provider enrollment process.</P>
                    <P>• In section V.D. of the proposed rule, we propose to make changes to the Medicare Part B definition of DME regulations in accordance with the statutory changes implemented via section 6222(a) of the CAA, 2026.</P>
                    <P>• In section V.E. of the proposed rule, we discuss requesting revisions to the information collection requirements that would require DMEPOS CBP contract suppliers to report the country of origin for the lead items furnished during the contract's period of performance.</P>
                    <HD SOURCE="HD2">B. DMEPOS Encounter Requirements for Identical Replacement Items</HD>
                    <HD SOURCE="HD3">1. Background</HD>
                    <P>Section 1834(a)(11)(B)(ii) of the Social Security Act, as amended by section 504 of MACRA and codified in the Code of Federal Regulation (CFR) at 42 CFR 410.38, outlines a condition of payment for certain items of durable medical equipment, prosthetics, orthotics, and supplies (DMEPOS). Specifically, it requires a physician, physician assistant (PA), nurse practitioner (NP), or clinical nurse specialist (CNS) (as these four terms are defined in section 1861 of the Act) to write an order that is communicated to the supplier prior to delivery and document that the physician, PA, practitioner, or specialist has had a face-to-face encounter (including through use of telehealth under section 1834(m) of the Act) with the individual involved, during the 6-month period preceding such written order.</P>
                    <P>
                        On November 8, 2019 (
                        <E T="03">84 FR 60648</E>
                        ), we published a process whereby items identified as potential vulnerabilities to the Trust Fund may be placed on the 
                        <E T="03">Master List of DMEPOS Items Potentially Subject to Face-to-Face Encounter and Written Orders Prior to Delivery and/or Prior Authorization Requirements</E>
                         (“Master List”). We analyze the Master List and select items from the Master List to be placed on the 
                        <E T="03">Required Face-to-Face Encounter and Written Orders Prior to Delivery List</E>
                         (“Required F2F/WOPD List”) via 
                        <E T="04">Federal Register</E>
                         notice. The face-to-face encounter requirements outlined in 42 CFR 410.38 are only applicable to items that are selected and placed on the Required F2F/WOPD List via 
                        <E T="04">Federal Register</E>
                         notice.
                    </P>
                    <P>For the identified items, the treating practitioner must document and communicate to the DMEPOS supplier that the treating practitioner has had a face-to-face encounter with the beneficiary within the 6 months preceding the date of the written order/prescription. The regulation requires the supporting documentation to include the subjective and objective beneficiary specific information used for diagnosing, treating, or managing a clinical condition for which the DMEPOS is ordered.</P>
                    <P>Separately, in our Medicare Benefit Policy Manual (100-02) (Chapter 15, Section 110.2—Repairs, Maintenance, Replacement, and Delivery), we define replacement as the provision of an identical or nearly identical item. Replacements may occur as a result of loss, theft, or irreparable damage, which may be due to a specific incident or event, or irreparable wear, in consideration of the reasonable useful lifetime of the equipment.</P>
                    <P>
                        Section 414.210(f) discusses payment for replacement of equipment. As specified at 
                        <E T="03">42 CFR 414.210(f)(1),</E>
                         the reasonable useful lifetime of durable medical equipment is generally determined through program instructions, or in the absence of 
                        <PRTPAGE P="41283"/>
                        program instructions, may be determined by the Medicare Administrative Contractors and be no less than 5 years. If the item of equipment has been in continuous use by the beneficiary for the equipment's useful lifetime or if the contractor determines that the item is lost, stolen, or irreparably damaged, the beneficiary may elect to obtain a new piece of equipment. Replacement may be paid when the practitioner reaffirms the medical necessity of the item through a new order.
                    </P>
                    <HD SOURCE="HD3">2. Proposed Provisions</HD>
                    <P>The proposed regulatory change would clarify that while an order would continue to be required for replacement DMEPOS items, a new face-to-face encounter would not need to occur to support payment for these DMEPOS items. We further clarify that, for purposes of proposed 42 CFR 410.38(d)(2)(iii), a “replacement” refers to the provision of an item that replaces an item falling under the same Healthcare Common Procedure Coding System (HCPCS) code; it does not include those situations involving the provision of a different item, for example, because of a change in medical condition. In other words, for paragraph(d) the replacement would be the same type of item (that is, the same HCPCS code as that originally ordered and rendered) with no change to the type of item ordered and rendered. When an order is written to replace an item falling under the same HCPCS code, requiring a new face-to-face examination to document subjective and objective beneficiary specific information regarding how the DMEPOS item will continue to be used in relation to the beneficiary's clinical condition seems burdensome and redundant. If the item is not a replacement item identified by the same HCPCS code, then a new face-to-face encounter would continue to be required, as described in existing 42 CFR 410.38. This clarification does not eliminate the need for a new order, nor does it supersede or eliminate any other coverage instruction—including those iterated in national or local coverage determinations.</P>
                    <HD SOURCE="HD2">C. Provider Enrollment</HD>
                    <HD SOURCE="HD3">1. Background and Applicability</HD>
                    <HD SOURCE="HD3">a. Enrollment Process</HD>
                    <P>Section 1866(j)(1)(A) of the Act requires the Secretary to establish a process for the enrollment of providers and suppliers into the Medicare program. The overarching purpose of the enrollment process is to help confirm that providers and suppliers (hereafter collectively “providers” unless otherwise noted) seeking to bill Medicare for services and items furnished to Medicare beneficiaries meet all applicable Federal and State requirements to do so. The process is, to an extent, a “gatekeeper” that prevents unqualified and potentially fraudulent individuals and entities from entering and inappropriately billing Medicare. Since 2006, we have undertaken rulemaking efforts to outline our enrollment procedures. These regulations are generally codified in 42 CFR part 424, subpart P (currently §§ 424.500 through 424.575 and hereafter occasionally referenced as subpart P). They address, among other things, requirements that providers must meet to obtain and maintain Medicare billing privileges.</P>
                    <P>As outlined in § 424.510, one such requirement is that the provider must complete, sign, and submit to its assigned Medicare Administrative Contractor (MAC) the appropriate enrollment form, typically the Form CMS-855 (OMB Control No.: 0938-0685). The Form CMS-855, which can be submitted via paper or electronically through the internet-based Provider Enrollment, Chain, and Ownership System (PECOS) process (SORN: 09-70-0532, PECOS), collects important information about the provider. Such data includes, but is not limited to, general identifying information (for example, legal business name), licensure and certification data, and practice locations. The application is used for a variety of provider enrollment transactions, including all of the following:</P>
                    <P>• Initial enrollment—The provider is—(1) enrolling in Medicare for the first time; (2) enrolling in another Medicare contractor's jurisdiction; or (3) seeking to enroll in Medicare after having previously been enrolled.</P>
                    <P>• Change of ownership—The provider is reporting a change in its ownership.</P>
                    <P>• Revalidation—The provider is revalidating its Medicare enrollment information in accordance with § 424.515. (Suppliers of durable medical equipment, prosthetics, orthotics, and supplies (DMEPOS) must revalidate their enrollment every 3 years; all other providers and suppliers must do so every 5 years.)</P>
                    <P>• Reactivation—The provider is seeking to reactivate its Medicare billing privileges after it was deactivated in accordance with § 424.540.</P>
                    <P>• Change of information—The provider is reporting a change in its existing enrollment information in accordance with § 424.516.</P>
                    <P>After receiving the provider's initial enrollment application, CMS or the MAC reviews and confirms the information thereon and determines whether the provider meets all applicable Medicare requirements. We believe this screening process has greatly assisted CMS in executing its responsibility to prevent Medicare fraud, waste, and abuse.</P>
                    <P>As previously mentioned, over the years we have issued various final rules pertaining to provider enrollment. These rules were intended not only to clarify or strengthen certain components of the enrollment process but also to enable us to take further action against providers: (1) engaging (or potentially engaging) in fraudulent or abusive behavior; (2) presenting a risk of harm to Medicare beneficiaries or the Medicare Trust Funds; or (3) that are otherwise unqualified to furnish Medicare services or items. Consistent with this, and as we discuss in this section V.C. of this proposed rule, we propose several changes to our existing Medicare provider enrollment regulations.</P>
                    <HD SOURCE="HD3">b. Legal Authorities</HD>
                    <P>There are two principal categories of legal authorities for our proposed Medicare provider enrollment provisions:</P>
                    <P>• Section 1866(j) of the Act furnishes specific authority regarding the enrollment process for providers and suppliers; and</P>
                    <P>• Sections 1102 and 1871 of the Act provide general authority for the Secretary to prescribe regulations for the efficient administration of the Medicare program.</P>
                    <HD SOURCE="HD3">c. Applicable Provider and Supplier Types</HD>
                    <P>The provisions in section V.C. of this proposed rule apply to all Medicare provider and supplier types except as specifically indicated otherwise. The most prominent proposed provisions that would apply only to certain types of providers or suppliers include the following:</P>
                    <P>• New § 424.530(a)(20), which would permit denial of a hospice's enrollment application for the reasons specified therein.</P>
                    <P>
                        • New §§ 424.530(a)(22) and 424.535(a)(25), which would allow denial or revocation of a hospice's, home health agency's, or DMEPOS supplier's enrollment for failing to comply with the change in majority ownership provisions in §§ 424.550(b) or 424.551.
                        <PRTPAGE P="41284"/>
                    </P>
                    <P>• Revised § 424.540(b)(3)(i), which would require reactivating hospices to undergo a State survey or accreditation prior to reactivation.</P>
                    <P>• Revisions to our DMEPOS accreditation requirements in § 424.58.</P>
                    <HD SOURCE="HD3">d. Comment Solicitation</HD>
                    <P>We solicit and welcome comments on all of the proposed provider enrollment provisions that follow.</P>
                    <HD SOURCE="HD3">2. Revocations and Denials of Enrollment</HD>
                    <P>Under § 424.535(a), CMS may revoke a Medicare provider's enrollment for any of the reasons specified in that paragraph. These reasons include, for instance, the provider's: (1) failure to adhere to Medicare enrollment requirements; (2) exclusion by the HHS Office of Inspector General (OIG); (3) felony conviction within the previous 10 years; (4) pattern of improper or abusive billing; and (5) termination by another Federal health care program. A revocation helps safeguard the Medicare program, the Trust Funds, and beneficiaries by removing from (and preventing payment to) Medicare providers that have engaged in problematic or otherwise non-compliant behavior. When a provider is revoked, it is generally barred from reenrolling in Medicare for a period of 1 to 10 years. The length of this “reenrollment bar” is determined based upon the severity of the basis of the revocation.</P>
                    <P>CMS also has numerous reasons in § 424.530(a) for which it can deny a provider's enrollment application, some of which duplicate our revocation grounds in § 424.535(a) (for instance, OIG exclusion). The general rationale for a denial is akin to that for a revocation: to protect the Medicare program and its beneficiaries from potentially fraudulent or abusive activity.</P>
                    <P>We have previously finalized a number of regulations adding or revising revocation and denial reasons in subpart P to address particular program integrity vulnerabilities and types of provider conduct. We have also used rulemaking to refine other revocation and denial policies, such as the effective dates of revocations. With our continuing obligation to establish strong payment safeguards, we believe that changes to our revocation and denial policies in subpart P are needed.</P>
                    <HD SOURCE="HD3">a. Modifications of Current Revocation Provisions</HD>
                    <HD SOURCE="HD3">(1) Abuse of Billing Privileges (§ 424.535(a)(8)(ii))</HD>
                    <P>Section 424.535(a)(8) permits revocation based on the provider's abuse of billing privileges. Per § 424.535(a)(8)(ii), this includes situations where CMS determines that the provider has a pattern or practice of submitting claims that fail to meet Medicare requirements. In making this determination, CMS considers, as appropriate or applicable, the following factors (outlined in § 424.535(a)(8)(ii)(A) through (D)):</P>
                    <P>• The percentage of submitted claims that were denied during the period under consideration (paragraph (a)(8)(ii)(A)).</P>
                    <P>• Whether the provider or supplier has any history of final adverse actions and the nature of any such actions (paragraph (a)(8)(ii)(B)).</P>
                    <P>• The type of billing non-compliance and the specific facts surrounding said non-compliance (to the extent this can be determined) (paragraph (a)(8)(ii)(C)).</P>
                    <P>• Any other information regarding the provider or supplier's specific circumstances that CMS deems relevant to its determination (paragraph (a)(8)(ii)(D)).</P>
                    <P>
                        As we noted in the December 5, 2014, final rule that promulgated § 424.535(a)(8)(ii), a provider “should be responsible for submitting valid claims at all times and that the provider or supplier's repeated failure to do so poses a risk to the Medicare Trust Funds.” 
                        <SU>14</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>14</SU>
                             “Medicare Program; Requirements for the Medicare Incentive Reward Program and Provider Enrollment” (79 FR 72500).
                        </P>
                    </FTNT>
                    <P>We propose the following two revisions to § 424.535(a)(8)(ii):</P>
                    <P>• Remove all the factors in § 424.535(a)(8)(ii)(A) through (D).</P>
                    <P>• Remove the second sentence of § 424.535(a)(8)(ii) that reads “In making this determination, CMS considers, as appropriate or applicable, the following”.</P>
                    <P>We have seen a wide variety of potential § 424.535(a)(8)(ii) cases over the years. However, our existing factors often constrain our ability to effectively address all these factual scenarios. To illustrate, we note the following:</P>
                    <P>• Final Adverse Actions—Most aberrant billing we have seen is done by providers with no history of adverse actions (for example, Medicare revocations or OIG exclusions). Yet the adverse action factor in § 424.535(a)(8)(ii) essentially requires us to weigh against a finding of improper billing for such providers. That is, this factor assists non-compliant providers so long as the provider lacks an adverse history, which it often will; this hinders our efforts to invoke § 424.535(a)(8)(ii) against the provider.</P>
                    <P>• Percentage of Claims Denied—This factor, too, is problematic. Non-compliant billing often occurs notwithstanding a low percentage of denied claims, especially with providers that submit many claims. Similar to the adverse history factor, the claim denial criterion thus makes it more difficult to use § 424.535(a)(8)(ii) even if a pattern of abusive billing exists. Moreover, the factor is limited to claim denials and does not consider other types of non-compliant claims (such as rejected claims). In our view, it is the lack of compliance itself, rather than the type of claim involved, that is pertinent.</P>
                    <P>In sum—and given our responsibility to protect the Trust Funds and taxpayers from improper billing—we must have the maximum flexibility to address all possible § 424.535(a)(8)(ii) scenarios without the rigid constraints of our existing factors. Even with the “as appropriate or applicable” qualifier in the opening paragraph of § 424.535(a)(8)(ii), there could still be an implication that we must consider all the factors in our determinations, which, as indicated, hampers the usefulness of § 424.535(a)(8)(ii). </P>
                    <P>Despite the proposed removal of the criteria in § 424.535(a)(8)(ii), a “pattern or practice” within the meaning of revised § 424.535(a)(8)(ii) might be established, for example, by a simple finding that several of the provider's claims do not meet Medicare requirements. In addition, and similar to what we have stated in past regulations when we have proposed new or revised revocation grounds, we would invoke revised § 424.535(a)(8)(ii) only when legitimately warranted under the facts and circumstances and not as a matter of course. Furthermore, interested parties should not conclude that our proposed example: (1) means we would always revoke in that situation; (2) is the only scenario in which we would revoke; and (3) establishes any kind of minimum threshold for CMS action.</P>
                    <HD SOURCE="HD3">(2) False or Misleading Information (§ 424.535(a)(4))</HD>
                    <P>
                        Section 424.535(a)(4) permits revocation if the provider or supplier certified as “true” misleading or false information on the enrollment application to be enrolled or maintain enrollment in the Medicare program. We propose to revise § 424.535(a)(4) to allow revocation based on the submission of false or misleading information on or associated with any CMS or Medicare enrollment-related form (including enrollment-related forms created by and/or submitted to CMS contractors). This would also include false or misleading documentation furnished as part of the completion or submission of the CMS or 
                        <PRTPAGE P="41285"/>
                        Medicare enrollment-related form. (The current parenthetical in § 424.535(a)(4) regarding potential penalties would remain.)
                    </P>
                    <P>This proposed expansion has three main components. One is that § 424.535(a)(4) would include certain documents other than Form CMS-855 or Form CMS-20134 (Medicare Enrollment Application: Medicare Diabetes Prevention Program (MDPP) Suppliers) provider enrollment forms. Providers and suppliers must always submit truthful enrollment and enrollment-related information to CMS and its contractors regardless of the form or document involved. Any false or misleading information could lead to improper payments based on inaccurately submitted data and generate doubts about the provider's/supplier's veracity. Additional documents that would fall within the purview of the proposed revisions to § 424.535(a)(4) include, but are not limited to the following:</P>
                    <P>• Form CMS-588 (Electronic Funds Transfer (EFT) Authorization Agreement; OMB Control Number 0938-0626), which must be submitted with the enrollment application.</P>
                    <P>• Documents required to demonstrate compliance with HHA capitalization requirements in § 489.28.</P>
                    <P>• Opt-out affidavits under 42 CFR part 405, subpart D.</P>
                    <P>• Letters from a provider demonstrating that a particular provider official qualifies as an authorized or delegated official under § 424.502.</P>
                    <P>• Any other required or requested enrollment-related documentation.</P>
                    <P>No less than false/misleading data submitted on the application itself, such information furnished via other documentation could result in a non-compliant provider being inadvertently enrolled in Medicare.</P>
                    <P>Another component is that the submission need not be intended to gain or maintain Medicare enrollment. For § 424.535(a)(4) purposes, the ultimate aim of the submission—be it to enroll, revalidate enrollment, reactivate enrollment, voluntarily terminate enrollment, report changed EFT data, etc.—is not, in our view, as crucial as the truthfulness of the submission. If we continued to limit § 424.535(a)(4) to “gain or maintain enrollment” situations, providers might believe they can submit false information on other enrollment-related documents without concern about possible revocation.</P>
                    <P>The third component is that the information need not have been certified as “true” for § 424.535(a)(4) to apply. The correctness of the information is the salient point and not whether it was certified as “true.”</P>
                    <P>We believe that our § 424.535(a)(4) expansion would help ensure that providers furnish truthful and accurate enrollment-related data to Medicare. As with current § 424.535(a)(4), though, we would invoke proposed § 424.535(a)(4) only when justified and necessary under the case's facts.</P>
                    <HD SOURCE="HD3">(3) Extension of Revocation (§ 424.535(i))</HD>
                    <P>Section 424.535(i) states that if a provider's enrollment is revoked under § 424.535(a), CMS may revoke any and all of the provider's other enrollments. This provision is designed to ensure that individuals and entities revoked for inappropriate behavior are not permitted to remain enrolled Medicare—and, hence, potentially able to continue their conduct via their other Medicare enrollments—in any capacity. We propose to expand § 424.535(i) such that we could also revoke a provider's other enrollments if the provider's triggering enrollment is denied under § 424.530(a). Some enrollment denials, in our experience, have been based on conduct as concerning to us as that leading to a revocation. Suppose Supplier X has three separate enrollments. It submits a fourth application for a new supplier site. The application is denied because CMS discovers that—(1) the new site is actually a false storefront; and (2) X furnished misleading information on its application. Although this conduct reflects on Supplier X as a whole, we could not take action against X's other enrollments under existing § 424.535(i), since the fourth enrollment was denied rather than revoked. This is disconcerting because X could repeat this behavior via its three remaining enrollments, hence placing the Trust Funds and Medicare beneficiaries at risk. Under our proposed § 424.535(i) revision, though, we would eliminate this vulnerability, for X's recent denial could result in its other enrollments being revoked.</P>
                    <P>We emphasize that § 424.535(i) would remain a discretionary authority. A denial would not automatically lead to the revocation of the provider's current enrollments.</P>
                    <HD SOURCE="HD3">(4) Expansion and Reorganization of Retroactive Revocation Grounds (§ 424.535(g))</HD>
                    <P>Section 424.535(g) addresses revocation effective dates. Paragraph (g)(1) states that except as described in paragraphs (g)(2) and (g)(3), a revocation becomes effective 30 days after CMS or the CMS contractor mails notice of its determination to the provider; the revocation is thus prospective. Paragraphs (g)(2)(i) through (xv) list situations where the revocation effective date is retroactive. This generally means that the revocation's effective date is retroactive back to the date on which the provider's non-adherence to Medicare requirements commenced.</P>
                    <P>The purpose of paragraph (g)(2) is to prevent payments to a provider while it is out of compliance. Assume a provider's medical license is revoked by the state on March 1. CMS learns of this and sends a revocation notice to the provider on March 15. If we applied the prospective “30 days after mailing” timeframe in paragraph (g)(1), the provider could bill and be paid for services furnished between March 1 and April 15 while unlicensed, resulting in potentially thousands of dollars in improper Medicare payments. Preventing improper payments is a cornerstone of provider enrollment, and retroactive revocation effective dates are crucial mechanisms for ensuring that taxpayer monies are paid only to compliant providers. As § 424.500 makes clear: “Providers and suppliers must meet and maintain [part 424, subpart P's] enrollment requirements to bill either the Medicare program or its beneficiaries for Medicare-covered services or supplies.” This means, by extension, that if said requirements are not met, the provider cannot bill—or, in turn, receive payment—for Medicare services or supplies.</P>
                    <P>
                        Our concerns about paying non-adherent providers are why we have increased the number of retroactive revocation grounds over the years. In the CY 2026 HH PPS final rule (90 FR 55342), we finalized numerous revisions to § 424.535(g) such that many of our existing revocation reasons are now retroactive.
                        <SU>15</SU>
                        <FTREF/>
                         So critical is it to make payments only to qualified providers and to comply with the aforementioned requirement in § 424.500 that we now propose to make the remainder of current prospective revocation grounds retroactive. We also believe that the prospect of a retroactive revocation no matter the § 424.535(a) reason could help spur providers to ensure constant 
                        <PRTPAGE P="41286"/>
                        compliance with Medicare requirements.
                    </P>
                    <FTNT>
                        <P>
                            <SU>15</SU>
                             “Medicare and Medicaid Programs; Calendar Year 2026 Home Health Prospective Payment System (HH PPS) Rate Update; Requirements for the HH Quality Reporting Program and the HH Value-Based Purchasing Expanded Model; Durable Medical Equipment, Prosthetics, Orthotics, and Supplies (DMEPOS) Competitive Bidding Program Updates; DMEPOS Accreditation Requirements; Provider Enrollment; and Other Medicare and Medicaid Policies”, published in the 
                            <E T="04">Federal Register</E>
                             on December 2, 2025 (90 FR 55342).
                        </P>
                    </FTNT>
                    <P>There would be two sets of changes to § 424.535(g). First, we would add new retroactive revocation bases. Second, we would restructure § 424.535(g) to remove current § 424.535(g)(1) (which addresses prospective revocations) and realign the existing retroactive grounds to correspond to the numerical order of our § 424.535(a) revocation reasons. To illustrate, current paragraph (g)(2)(i) (which addresses exclusions and debarments) would become paragraph (g)(1)(ii) to correspond to § 424.535(a)(2), which also addresses exclusions and debarments.</P>
                    <HD SOURCE="HD3">(a) General Non-Compliance, Licensure, and Provider Agreements</HD>
                    <P>CMS may revoke a provider under § 424.535(a)(1) if the provider is not in compliance with the enrollment requirements in Title 42 of the Act or in the enrollment application applicable to its provider type. We propose in new § 424.535(g)(1)(i)(A) that said revocation would be effective on the date the non-compliance began (per CMS' or the CMS contractor's determination). This is consistent with several other current retroactive grounds for which the commencement of non-compliance is the effective date; for said current grounds—as well as proposed § 424.535(g)(1)(i)(A)—the rationale is that payments should not be made to non-adherent providers.</P>
                    <P>State licensure revocations, suspensions, and surrenders (in lieu of further disciplinary action) are also grounds for revocation. As stated in existing § 424.535(g)(2)(iii) and (v), these revocation effective dates are the dates of the revocation, suspension, or surrender. We propose to consolidate paragraphs (g)(2)(iii) and (v) within new § 424.535(g)(1)(i)(B), retaining their current effective dates.</P>
                    <P>In addition, current § 424.535(g)(2)(vii) addresses effective dates for revocations based on a provider agreement termination under part 489. We propose to retain these dates and incorporate them into new § 424.535(g)(1)(i)(C).</P>
                    <HD SOURCE="HD3">(b) Exclusions/Debarments, Felony Convictions, False Information, and Non-Operational Status</HD>
                    <P>These revocation grounds are addressed in § 424.535(a)(2), (3), (4), and (5)(i), with their concomitant effective dates outlined in existing § 424.535(g)(2)(i), (ii), (ix), and (iv), respectively. With our proposed reorganization of § 424.535(g), § 424.535(g)(2)(i), (ii), (ix), and (iv) would become new § 424.535(g)(1)(ii), (iii), (iv), and (v)(A), respectively.</P>
                    <P>(We note that due to our proposed expansion of § 424.535(a)(4) (discussed previously), new § 424.535(g)(1)(iv) would include an additional effective date for paragraph (a)(4) revocations based on the submission of false or misleading data not involving the signature of a provider enrollment application certification statement. Specifically, these other false/misleading communications would trigger a revocation effective date of the date the false/misleading information was submitted.)</P>
                    <HD SOURCE="HD3">(c) Failure To Satisfy Enrollment Requirements</HD>
                    <P>Section 424.535(a)(5)(ii) permits revocation if the provider fails to satisfy any Medicare enrollment requirement. We propose in new § 424.535(g)(1)(v)(B) that a § 424.535(a)(5)(ii) revocation becomes effective on the date the Medicare enrollment requirement was not satisfied. This is somewhat akin to our proposed “date of non-compliance” effective date for § 424.535(a)(1), but we would instead use “not satisfied” to conform to the use of “satisfy” in existing § 424.535(a)(5)(ii).(d) Application Fee Payment.</P>
                    <P>CMS can revoke a provider's enrollment under § 424.535(a)(6) in any of the following four bulleted instances:</P>
                    <P>• Under § 424.535(a)(6)(i)(A) and (B)—</P>
                    <P>++ An institutional provider (as defined in § 424.502) fails to submit with its Medicare revalidation application an application fee or hardship exception request that complies with § 424.514; or</P>
                    <P>++ The hardship exception is not granted, and the institutional provider fails to submit the applicable application form or application fee within 30 days of being notified of the hardship exception request's denial.</P>
                    <P>
                        • Under § 424.535(a)(6)(ii)(A)
                        <E T="03">(1)</E>
                         and 
                        <E T="03">(2):</E>
                    </P>
                    <P>++ CMS is unable to deposit the full application fee amount into a government-owned account; or</P>
                    <P>++ The funds are unable to be credited to the United States Treasury.</P>
                    <P>• Under § 424.535(a)(6)(ii)(B), the provider lacks sufficient funds in the account at the banking institution whose name is imprinted on the check or other banking instrument to pay the application fee.</P>
                    <P>• Under § 424.535(a)(6)(ii)(C), there is any other reason why CMS or its Medicare contractor is unable to deposit the application fee into a government-owned account.</P>
                    <P>Unlike with most of our other revocation reasons, the variety and types of scenarios in § 424.535(a)(6) make it infeasible to establish a uniform revocation effective date based on provider non-compliance or other definitive point (for example, date on which license or state authority to prescribe drugs was revoked, date of felony conviction, etc.) For this reason, we propose in new § 424.535(g)(1)(vi) that a revocation under § 424.535(a)(6) is effective on the date on which CMS or its contractor determines that the provider or supplier should be revoked under this paragraph; the date, in other words, would be that of the CMS or contractor determination instead of, for instance, the date on which CMS could not deposit the funds. This would still allow for retroactivity because of the provider's non-compliance with § 424.514—that is, its failure to pay a full, depositable fee or have a hardship exception approved. Yet it would be flexible enough to address all the various § 424.535(a)(6) situations.</P>
                    <HD SOURCE="HD3">(e) Misuse of Billing Number</HD>
                    <P>CMS may revoke a provider's enrollment under § 424.535(a)(7) if the provider knowingly sells to or allows another individual or entity to use its billing number. (This excludes providers who enter into a valid reassignment of benefits under § 424.80 or a § 489.18 change of ownership.) Given the seriousness of this conduct—with its significant potential for fraud—we believe that the revocation effective date should be the date on which the conduct resulting in the revocation occurred. This would be included in new § 424.535(g)(1)(vii).</P>
                    <HD SOURCE="HD3">(f) Abuse of Billing Privileges</HD>
                    <P>The effective dates for revocations under § 424.535(a)(8)(i) and (ii) are addressed in § 424.535(a)(8)(iii). So that all revocation effective dates can be found in one paragraph, we propose to move and redesignate § 424.535(a)(8)(iii) as new § 424.535(g)(1)(viii). Paragraph (iii) would be deleted from § 424.535(a)(8).</P>
                    <HD SOURCE="HD3">(g) Reporting Enrollment Data Changes</HD>
                    <P>
                        Section 424.535(a)(9) permits revocation if the provider failed to comply with the change of information reporting requirements in §§ 424.516(d) or (e), 410.33(g)(2), or 424.57(c)(2). These four paragraphs collectively address all Medicare provider and supplier types (except Medicare Diabetes Prevention Programs (MDPPs), which are dealt with in § 424.205)) and all types of enrollment data changes. Current § 424.535(g)(2)(x) partially 
                        <PRTPAGE P="41287"/>
                        addresses the effective date of a § 424.535(a)(9) revocation. For revocations based on the provider's failure to timely report a change of ownership or adverse legal action, or a change, addition, or deletion of a practice location, the effective date under § 424.535(g)(2)(x) is day the after the date by which the provider was required to report the change, addition, or deletion. All other changes are prospective under current § 424.535(g)(1).
                    </P>
                    <P>We propose in new § 424.535(g)(1)(ix) to make all § 424.535(a)(9) revocations retroactive to the day following the due date for reporting the change. While ownership, adverse legal action, and practice location changes are important (hence their inclusion in existing § 424.535(g)(2)(x)), other data changes are as well. A failure to timely report a new managing employee or corporate officer, for example, could result in CMS unknowingly paying a provider with a high-level official who poses a program integrity risk based on past or current conduct. In addition, if we do not timely learn of a provider's new bank, billing agency, or correspondence address, CMS risks sending funds or information to—or receiving claims from—the wrong entity or individual; this could lead to incorrect payments or the inadvertent release of confidential data. The point is that outdated or erroneous enrollment information of any type—not simply ownership, adverse action, or location data—can threaten the Trust Funds, and any failure to timely report such changes means the provider is non-compliant with enrollment requirements. For these reasons—and because the prospect of a retroactive revocation could encourage providers to timely report all enrollment changes—we believe § 424.535(g)(1)(ix) is warranted.</P>
                    <P>Although the provider is ultimately responsible for ensuring that its enrollment data is timely updated and always accurate, we welcome stakeholder comment on any administrative difficulties in reporting changes in enrollment information and ideas on how they could be addressed.</P>
                    <HD SOURCE="HD3">(h) Failure To Document or Furnish Documentation</HD>
                    <P>CMS can revoke a provider under § 424.535(a)(10) if the provider fails to comply with the documentation or CMS access requirements in § 424.516(f). In general, § 424.516(f) requires providers (including physicians and eligible professionals) to: (1) retain for 7 years all documents regarding written orders, certifications, referrals, prescriptions and requests for payments for Part A or B services, items, or drugs; and (2) furnish access to that documentation upon CMS or CMS contractor request.</P>
                    <P>We propose in new § 424.535(g)(1)(x)(A) and (B) that a § 424.535(a)(10) effective date is as follows:</P>
                    <P>• For revocations based on a failure to retain documentation, the date on which CMS or the CMS contractor found that the provider has not complied with this retention requirement.</P>
                    <P>• For revocations based on a failure to provide access to that documentation, the day after the date by which the provider was required to give access.</P>
                    <P>We believe proposed § 424.535(g)(1)(x)(A) soundly balances the need for retroactivity—due to, for instance, the provider's non-compliance and our inability to make payment to non-adherent providers—and the need for a clear effective date. To illustrate, suppose CMS discovered several years after a particular service was ordered or certified that the provider lacks documentation thereof. CMS would have no means of knowing whether the documentation was never kept, discarded after 2 years or 4 years, etc. It is therefore difficult to establish an effective date in this scenario, hence the need to use the proposed—and much more precise—§ 424.535(g)(1)(x)(A) date. Regarding § 424.535(g)(1)(x)(B), the provider's failure to provide the documentation constitutes non-compliance, similar to a provider's failure to timely report changes in information. We thus believe that the day after the due date for furnishing access is an appropriate effective date.</P>
                    <HD SOURCE="HD3">(i) Initial Reserve Operating Funds (IROF)</HD>
                    <P>Under 42 CFR 489.28, HHAs must demonstrate that they have sufficient available funds upon application submission and for the 3-month period following the conveyance of Medicare billing privileges to operate the HHA for this 3-month period. CMS can revoke the HHA under § 424.535(a)(11) if, within 30 days of a CMS or Medicare contractor request, the HHA cannot furnish supporting documentation verifying that it meets the IROF requirement. For the same reasons behind proposed § 424.535(g)(1)(x)(B)—specifically, the provider's non-compliance with § 489.28 based on its failure to demonstrate adequate funds—we propose in new § 424.535(g)(1)(xi) that the § 424.535(a)(11) revocation effective date is the day after the date by which the HHA was required to submit the requested documentation.</P>
                    <HD SOURCE="HD3">(j) Other Program Termination</HD>
                    <P>CMS under § 424.535(a)(12) may revoke a provider's Medicare enrollment if the provider is terminated, revoked, or otherwise barred from participation in a State Medicaid program or any other federal health care program. The effective date of a § 424.535(a)(12) revocation is, consistent with existing § 424.535(g)(2)(vi), the date of the termination, revocation, or bar (from the other program). As part of our previously discussed restructuring of § 424.535(g), we propose to redesignate § 424.535(g)(2)(vi) as new § 424.535(g)(1)(xii); however, we would include the terms “revocation” and “bar” within the latter to correspond to § 424.535(a)(12). (Current § 424.535(g)(1)(vi) only references terminations.)</P>
                    <HD SOURCE="HD3">(k) Drug Enforcement Administration (DEA) Certificates</HD>
                    <P>Section 424.535(a)(13)(i) and (ii) permit revocation if—</P>
                    <P>• A physician or other eligible professional's DEA Certificate of Registration to dispense a controlled substance is currently suspended or revoked or is surrendered in response to a show cause order; or</P>
                    <P>• The applicable licensing or administrative body for any state in which the physician or eligible professional practices suspends or revokes the individual's ability to prescribe one or more drugs.</P>
                    <P>
                        Existing § 424.535(g)(2)(xi) permits retroactive revocation based on the surrender of the provider's DEA certificate of registration in response to a show cause order. (The revocation effective date is the date the certificate was surrendered.) We propose to include DEA certificate revocations and suspensions within this paragraph, with the date of the revocation or suspension as the effective date. It is the permanent or temporary loss of the certificate itself—rather than the form of loss (for example, revocation or surrender)—that is important for program integrity purposes; it would be illogical for certificate surrenders to be part of paragraph (g)(2)(xi) but not revocations or suspensions. As we stated in the CY 2026 HH PPS final rule that promulgated paragraph (g)(2)(xi), meeting all applicable federal and state requirements is necessary for enrollment.
                        <SU>16</SU>
                        <FTREF/>
                         If a provider is prescribing or dispensing drugs while non-compliant, we believe the risk this presents to beneficiaries after the 
                        <PRTPAGE P="41288"/>
                        certificate loss warrants a revocation back to the date said loss occurred.
                    </P>
                    <FTNT>
                        <P>
                            <SU>16</SU>
                             90 FR 55342.
                        </P>
                    </FTNT>
                    <P>Per current § 424.535(g)(2)(xii), the effective date of a revocation based on a State's suspension or revocation of the physician's or practitioner's ability to prescribe one or more drugs is the date of the suspension or revocation. We propose to redesignate this paragraph without change as new paragraph (g)(1)(xiii)(B), with existing (g)(2)(xi) redesignated as new paragraph (g)(1)(xiii)(A). This would better correspond numerically with (a)(13)(i) and (ii).</P>
                    <HD SOURCE="HD3">(l) Improper Prescribing Practices</HD>
                    <P>Section 424.535(a)(14) permits revocation if the physician or practitioner has a pattern or practice of prescribing Medicare-covered drugs that is abusive, represents a threat to the health and safety of Medicare beneficiaries, or fails to meet Medicare requirements. We propose in new § 424.535(g)(1)(xiv) that the effective date of a § 424.535(a)(14) revocation would be the last date of the prescription(s) in question; for instance, if there were three prescriptions dated March 1, March 15, and March 30, the last date—March 30 would be the revocation effective date. This approach mirrors that for § 424.535(a)(8)(ii)'s revocation effective date, which, as noted, is the last date of service on the claims in question.</P>
                    <P>We have in past enrollment rules expressed our concerns about abusive and improper prescribing. Such conduct could cause serious patient harm (for instance, the prescription of unnecessary but dangerous medications). Applying a prospective effective date to a § 424.535(a)(14) revocation would run counter to our obligation to help protect Medicare beneficiaries; we would essentially be allowing the individual to continue prescribing for at least another 30 days, during which time additional beneficiaries might be placed as risk. We thus believe a retroactive revocation in this circumstance is proper.</P>
                    <HD SOURCE="HD3">(m) False Claims Act (FCA)</HD>
                    <P>Revocation is permissible under § 424.535(a)(15) if the provider (or owner, managing employee or organization, officer, or director thereof) has had an FCA civil judgment against them within the previous 10 years. Considering the seriousness of false claims and the threat this poses to the Medicare program, we believe a retroactive revocation effective date back to the date of the judgment is necessary; this would be reflected in new paragraph (g)(1)(xv). Allowing the provider to remain enrolled for 30 or more days via a prospective effective date could result in the continuation of the provider's behavior, at potentially great cost to the Trust Funds.</P>
                    <P>(Proposed new § 424.535(g)(1)(xvi) is addressed later in this section V.C. of this proposed rule.)</P>
                    <HD SOURCE="HD3">(n) Debts Referred to Treasury</HD>
                    <P>Section 424.535(a)(17) permits revocation if the provider failed to repay a debt that CMS appropriately referred to the United States Department of Treasury. (Paragraph (a)(17) does not apply if: (1) the debt has been discharged by a bankruptcy court; or (2) the administrative appeals process regarding the debt has not been exhausted or the timeframe for filing the appeal (at the appropriate appeal level) has not expired.)</P>
                    <P>All providers are responsible for satisfying their financial obligations to Medicare. Consistent with our rationale for the original promulgation of § 424.535(a)(17), we believe that referral to the Department of Treasury may indicate the provider's unwillingness to repay a debt, which raises doubts regarding whether the provider is a reliable participant in the Medicare program.</P>
                    <P>With the need to protect the Medicare program's financial integrity, we propose in new § 424.535(g)(1)(xvii) that the effective date of § 424.535(a)(17) would be retroactive back to the date on which CMS referred the debt to Treasury. A prospective effective date, in our view, would give the provider more time to incur additional debts that it also might not repay, placing taxpayers at considerable financial risk. We also believe that the prospect of a retroactive revocation under § 424.535(g)(1)(xvii) could spur providers to ensure that it repays all debts before they are sent to Treasury.</P>
                    <HD SOURCE="HD3">(o) Revoked Under Different Name or Identity</HD>
                    <P>CMS under § 424.535(a)(18) may revoke a provider that is currently revoked under a different name, numerical identifier, or business identity, and the applicable reenrollment bar period under § 424.535(c) has not expired. The objective is to prevent situations where a revoked provider changes its identity in order to re-enter Medicare and thus circumvent its existing bar on reenrollment. Such conduct is not only dishonest but also threatens the Medicare program's integrity and beneficiaries, for the provider's activity that generated the prior revocation—such as abusive billing or prescribing, fraudulent behavior, etc.—could be repeated in its subsequent enrollment under the different name.</P>
                    <P>Accordingly, we believe that a retroactive revocation effective date is proper. This date in new § 424.535(g)(1)(xviii) would be the same as the effective date of the provider's current enrollment. Suppose Provider X was revoked effective February 1. It changes its name to Provider Y and re-enrolls in Medicare effective July 1. CMS becomes aware of the provider's current revocation under the Provider X name on September 1 and revokes Provider Y under § 424.535(a)(18). The revocation effective date would be July 1, the effective date of Y's enrollment. We do not believe Provider Y should effectively be rewarded for its circumvention with a revocation effective date that is later than its enrollment effective date. This is because it should not: (1) have attempted to reenroll under the new name to begin with (since it was prohibited from doing so under the original reenrollment bar); and (2) receive payment stemming from what amounts to an improper subsequent enrollment. We believe the severity of the provider's behavior warrants the earliest feasible retroactive revocation date, which could also deter revoked providers from attempting to maneuver around their re-enrollment bar.</P>
                    <HD SOURCE="HD3">(p) Undue Risk</HD>
                    <P>
                        Per § 424.535(a)(19), CMS may revoke a provider or supplier that has or has had an affiliation under § 424.519 that poses an undue risk of fraud, waste, or abuse to the Medicare program. There are many different scenarios that could fall within § 424.535(a)(19) in terms of, for example, the type, time, and length of the affiliation. As with § 424.535(a)(6), this makes it challenging to establish a uniform retroactive revocation effective date applicable to every factual situation. We hence propose in new § 424.535(g)(1)(xix) that a revocation under § 424.535(a)(19) is effective on the date on which CMS or its contractor determines that the provider or supplier should be revoked under this paragraph. This would still remove the risks posed by a prospective effective date—for instance, the continuation of a problematic affiliation that could threaten the Medicare program for another 30 or more days—while ensuring consistency in the application of § 424.535(a)(19) revocation effective dates.
                        <PRTPAGE P="41289"/>
                    </P>
                    <HD SOURCE="HD3">(q) Billing From Non-Compliant Location</HD>
                    <P>CMS may revoke enrollment under § 424.535(a)(20) if the provider billed for services performed at or items furnished from a location that it knew or should have known did not comply with Medicare enrollment requirements. This provision is partly analogous to § 424.535(a)(5)(i), which addresses non-operational locations; § 424.535(a)(5)(i)'s revocation effective date is the date on which the practice location was no longer operational. Yet it perhaps has more similarities to § 424.535(a)(8)(ii) because it references billing (that is, submission of claims) for services. In light of the previously noted importance of maintaining constant compliance with enrollment requirements, we believe a retroactive effective date for § 424.535(a)(20) aligning with that in § 424.535(a)(8)(ii) is needed. Per new § 424.535(g)(1)(xx), this date would be the earliest date on the claims for the non-compliant location that are triggering the revocation.</P>
                    <HD SOURCE="HD3">(r) Abusive Ordering, Certifying, Referring, or Prescribing</HD>
                    <P>Section 424.535(a)(21) permits revocation if the physician or eligible professional has a pattern or practice of ordering, certifying, referring, or prescribing Part A or B services, items, or drugs that is abusive, represents a threat to the health and safety of Medicare beneficiaries, or otherwise fails to meet Medicare requirements. As with proposed § 424.535(g)(1)(xiv) regarding § 424.535(a)(14), the seriousness of the conduct described in § 424.535(a)(21) and the threats it can present to Medicare patients and the Trust Funds (for instance, ordering unnecessary tests) warrants a retroactive effective date. This date under proposed § 424.535(g)(1)(xxi) would be the date of the last order, certification, referral, or prescription in the applicable pattern or practice, akin to the proposed § 424.535(a)(14) effective date.</P>
                    <HD SOURCE="HD3">(s) Patient Harm</HD>
                    <P>Revocation under § 424.535(a)(22) is permissible if the physician or other eligible professional has been subject to prior action from a State oversight board, Federal or State health care program, Independent Review Organization (IRO) determination(s), or any other equivalent governmental body or program that oversees, regulates, or administers the provision of health care with underlying facts reflecting improper conduct that led to patient harm. We believe a retroactive revocation effective date for § 424.535(a)(22) is appropriate due to the need to protect Medicare beneficiaries from potential harm. We propose that this effective date per new § 424.535(g)(1)(xxii) would be the date of the prior action that resulted in the revocation.</P>
                    <HD SOURCE="HD3">(t) Supplier Standard and Condition Violation</HD>
                    <P>Several provider and supplier types have certain standards and conditions they must meet in addition to all other enrollment requirements. These types—and their corresponding standard/condition regulatory sections—include independent diagnostic testing facilities (IDTFs) (§ 410.33(g)), DMEPOS suppliers (§ 424.57(b) and (c)), opioid treatment programs (OTP) (§ 424.67(b) and (e)), home infusion therapy suppliers (§ 424.68(c) and (e)), and MDPPs (§ 424.205(b) and (c)). Except for § 424.57(b) violations, CMS under § 424.535(a)(23) may revoke the provider or supplier for non-compliance with any of the standards or conditions applicable to their provider/supplier type. (Revocation is permissible for § 424.57(b) violations (as well as § 424.57(c) non-compliance) under § 424.57(e)(1).) The current § 424.535(a)(23) revocation effective dates (outlined in § 424.535(g)(2)(xv)(A) through (D), respectively) are as follows:</P>
                    <P>• For standard or condition violations involving the suspension, revocation, or termination (or surrender in lieu of further disciplinary action) of the provider's Federal or State license, certification, accreditation, or MDPP recognition, the date of the suspension, revocation, termination, or surrender.</P>
                    <P>• For standard or condition violations involving a non-operational practice location, the date the non-operational status began.</P>
                    <P>• For OTP standard violations involving a felony conviction of a party described in § 424.67(b)(6)(i), the date of the felony conviction.</P>
                    <P>• For all standard violations not addressed in existing paragraph (g)(2) (which, as discussed, would be incorporated within revised (g)(1)), the prospective effective date in current paragraph (g)(1) applies if the effective date in existing paragraph (g)(3) (discussed shortly) does not.</P>
                    <P>
                        We propose to retain the dates in § 424.535(g)(2)(xv)(A) through (C), though we would re-designate them as new § 424.535(g)(1)(xxiii)(A)(
                        <E T="03">1</E>
                        ) through (
                        <E T="03">3</E>
                        ). In new § 424.535(g)(1)(xxiii)(B)—and consistent with the foregoing concerns about paying non-compliant providers—we propose that the effective date of all other revocations based on a condition or standard violation would be the date of non-compliance with the condition or standard.
                    </P>
                    <P>We propose two other organizational changes. First, existing § 424.535(g)(2)(viii) states that the effective date of a revocation based on a lapse in the IDTF's comprehensive liability insurance under § 410.33(g)(6) is the date the insurance lapsed. We are not proposing to include a separate effective date for this revocation in revised § 424.535(g)(1) because we believe it would fall within new § 424.535(g)(1)(xxiii)(B), with the lapse date being the standard violation date. Second, existing § 424.535(g)(2)(xiv) states that the effective date of a revocation based on a DMEPOS supplier's non-compliance with a condition or standard in § 424.57(b) or (c) is the date on which the non-compliance began. This provision would not be included in revised § 424.535(g)(1), for new § 424.535(g)(1)(xxiii) would cover § 424.57(b) or (c) violations.</P>
                    <HD SOURCE="HD3">(u) Extension of Revocation</HD>
                    <P>As already noted, § 424.535(i) states that if a provider's Medicare enrollment is revoked, CMS may revoke any and all of the provider's Medicare enrollments, including those under different names, numerical identifiers or business identities and those under different types. The effective date of the revocation(s) of the other enrollment(s) is—per existing § 424.535(g)(2)(xiii)—the effective date of the revocation that triggered the other revocation(s). We propose to retain this effective date provision with two modifications. First, we would redesignate it as § 424.535(g)(2)(xxvi). Second, and consistent with our aforementioned proposed modification of § 424.535(i), the effective date of the other revocation(s) would be the date of the triggering revocation or denial.</P>
                    <P>(Proposed new § 424.535(g)(1)(xxiv) and (xxv) will be addressed later.)</P>
                    <P>In conclusion, existing § 424.535(g)(3) states that if the action that resulted in the revocation occurred prior to the effective date of the provider's enrollment, the revocation effective date is the same as the effective date of enrollment. To accommodate our restructuring of § 424.535(g), we propose to re-designate § 424.535(g)(3) as § 424.535(g)(2).</P>
                    <HD SOURCE="HD3">(5) Claim Submissions After Revocation (§ 424.535(h))</HD>
                    <P>
                        Under § 424.535(h)(1)(i) (and excluding HHAs), a revoked provider must—within 60 calendar days after the revocation's effective date—submit all claims for items and services furnished 
                        <PRTPAGE P="41290"/>
                        before the date of the revocation letter. For revoked HHAs, § 424.535(h)(1)(ii) states that claims must be submitted within 60 days after the later of the following: (1) the revocation effective date; and (2) the date that the HHA's last payable episode ends.
                    </P>
                    <P>
                        This general 60-day post-revocation policy was first established in the CY 2009 Physician Fee Schedule final rule (73 FR 69726), published in the 
                        <E T="04">Federal Register</E>
                         on November 19, 2008.
                        <SU>17</SU>
                        <FTREF/>
                         We noted therein that revoked physicians, non-physician practitioners (NPP), physician and NPP groups, and IDTFs had historically been allowed to continue billing for services furnished prior to revocation for up to 27 months after the revocation's effective date.
                        <SU>18</SU>
                        <FTREF/>
                         We explained in that rule that: (1) such a long, post-revocation billing period posed significant risk to the Medicare program; and (2) a 60-day post-revocation timeframe for these five general supplier categories (established in new § 424.535(h)) was necessary to limit the Medicare program's exposure to future vulnerabilities.
                        <SU>19</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>17</SU>
                             “Medicare Program; Payment Policies Under the Physician Fee Schedule and Other Revisions to Part B for CY 2009; E-Prescribing Exemption for Computer-Generated Facsimile Transmissions; and Payment for Certain Durable Medical Equipment, Prosthetics, Orthotics, and Supplies (DMEPOS).”
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>18</SU>
                             Ibid.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>19</SU>
                             Ibid.
                        </P>
                    </FTNT>
                    <P>Consistent with this theme, we later expanded § 424.535(h) to apply to all provider and supplier types in a December 5, 2014, final rule titled, “Medicare Program; Requirements for the Medicare Incentive Reward Program and Provider Enrollment” (79 FR 72500). In the proposed version of that rule, we:</P>
                    <P>• Cited the concerns we expressed in the CY 2009 PFS final rule regarding the 27-month period.</P>
                    <P>• Expressed our view that the longer the post-revocation claim submission timeframe, the more opportunity the provider or supplier would have to submit false claims.</P>
                    <P>
                        • Noted that under § 424.518(c)(3)(ii), a revoked provider falls within the “high” categorical risk level. This heightened risk posed by revoked providers threatened the Trust Funds, hence warranting a much shorter 60-day period for all provider and supplier types.
                        <SU>20</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>20</SU>
                             “Medicare Program; Requirements for the Medicare Incentive Reward Program and Provider Enrollment” Proposed Rule” (78 FR 25013), published in the 
                            <E T="04">Federal Register</E>
                             on April 29, 2013.
                        </P>
                    </FTNT>
                    <P>Despite this reduction to 60 days, we have remained concerned about possible fraudulent, improper, or other non-compliant activity by revoked providers. If a provider engaged in such conduct before the revocation, it may continue it afterwards—and 2 months is still an extensive timeframe in which to do so. Indeed, a revoked provider could submit hundreds of improper claims for hundreds of thousands of dollars during this period. If other providers did the same after their revocations, many millions of Trust Fund dollars would be threatened. With the need to protect taxpayer monies from such parties, we believe that further reducing the submission timeframe could correspondingly lessen the program integrity risk, for providers would have less time to engage in inappropriate billing. For these reasons, we propose to change the 60-day timeframe referenced in § 424.535(h) to 15 days. While we recognize that this would be a substantial time reduction, we believe the risk warrants it.</P>
                    <P>We propose an additional change to § 424.535(h). In 2014, many of our revocations were prospective, meaning they did not become effective until 30 days after the revocation letter was sent. This made § 424.535(h) easier to operationalize, for the revocation effective date in most cases would be in the future; the provider would have 60 days from the prospective effective date to submit its claims. Now, though, many revocation reasons have retroactive effective dates (and, as discussed previously, we are proposing that all revocation reasons be retroactive). Under existing § 424.535(h), therefore, if a provider had 60 days from the revocation effective date to submit its claims but the effective date was more than 60 days retroactive, the submission period might well have expired before the provider even received the revocation letter. To ensure that the provider actually has an opportunity to submit its claims, we propose to change:</P>
                    <P>• Section 424.535(h)(1)(i) to state that a revoked provider must—within 15 calendar days of the date of the revocation letter—submit all claims for items and services furnished before the revocation effective date.</P>
                    <P>• Section 424.535(h)(1)(ii) to state that a revoked HHA must—within 15 calendar days of the date of the revocation letter—submit all claims for items and services furnished before the later of the following:”.</P>
                    <P>Sections 424.535(h)(1)(i)(A) and (B) and (h)(2) (which references the timely filing requirements of § 424.44) need not be revised.</P>
                    <HD SOURCE="HD3">(6). New Revocation Reasons</HD>
                    <P>We also propose to add several new grounds for revocation in § 424.535(a).</P>
                    <HD SOURCE="HD3">(a) High-Risk Enrollments (§ 424.535(a)(24))</HD>
                    <P>
                        We have seen an alarming increase in situations where numerous providers and suppliers—sometimes of the same type—are simultaneously operating within a very small geographic area (for instance, a multi-block sector), the same complex or building, or even the same suite. Examples include: (1) several dozen hospices within a four-block area of Los Angeles County; (2) 18 HHAs within the same building in Columbus, Ohio; (3) at least nine cases in Ohio where at least five HHAs have the same practice location address, with four of these nine situations involving at least nine HHAs in one location; and (4) similar situations with several certified providers of the same type operating out of one building in Michigan, Nevada, North Carolina, and Texas. Los Angeles County has been a particularly serious concern. Per CMS data, the number of HHAs in the county between 2019 and 2023 rose over 45 percent, and at least 1,400 new HHAs have enrolled in the county since 2019. There was no medical need for such an increase, which was entirely out of proportion with any increase in the county's beneficiary population and can be a strong indicator of widespread fraud. Others share our concerns about this, including the Medicare Payment Advisory Commission,
                        <SU>21</SU>
                        <FTREF/>
                         members of Congress,
                        <SU>22</SU>
                        <FTREF/>
                         and even several national HHA and hospice organizations.
                        <SU>23</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>21</SU>
                             
                            <E T="03">https://www.medpac.gov/wp-content/uploads/2025/12/Tab-H-HHA-update-Dec-2025.pdf.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>22</SU>
                             Letter from United States House Representatives Brett Guthrie, John Joyce, M.D., Morgan Griffith, Jason Smith, David Schweikert, and Vern Buchanan to T. March Bell, Inspector General, HHS-OIG, January 9, 2026, 
                            <E T="03">https://energycommerce.house.gov/posts/chairmen-guthrie-joyce-griffith-smith-schweikert-and-buchanan-ask-hhs-oig-about-ongoing-hha-and-hospice-fraud-in-los-angeles-county-1.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>23</SU>
                             Letter from LeadingAge and the National Alliance for Care at Home Letter to Dr. Mehmet Oz, CMS Administrator, December 22, 2025, 
                            <E T="03">https://allianceforcareathome.org/wp-content/uploads/Final-Alliance-and-LeadingAge-Home-Health-and-Hospice-Program-Integrity-Recommendations.pdf.</E>
                        </P>
                    </FTNT>
                    <P>
                        We recognize that many medical facilities and complexes have large numbers of providers and suppliers located therein. To illustrate, a medical center comprising three adjacent buildings may have seven physician practices with different specialties, two laboratories, etc. Also, some areas may have several types of providers and suppliers within a particular neighborhood. The vast preponderance of these situations do not, in and of themselves, necessarily mean that fraud, waste, and abuse exists or that program integrity risks are otherwise present. Yet 
                        <PRTPAGE P="41291"/>
                        we believe those cases mentioned in the previous paragraph—as well as other situations—can and do. Fraud schemes can indeed involve problematic (or potentially problematic) providers operating in same general vicinity, as shown in the Los Angeles County and Columbus situations. Although having, for example, four organizational providers/suppliers of the same type (such as ambulance companies) in a seven-block area does not automatically signify fraud, waste, and abuse, it does—based on our experience—raise questions as to whether there is a patient need for all these providers or whether other considerations, such as fraud, are involved.
                    </P>
                    <P>With tens of millions of Medicare dollars at risk in any fraud scheme, our role in safeguarding the Trust Funds requires the ability to take revocation action—if circumstances warrant—to address such situations. This is especially important because we currently lack authority under § 424.535(a) to revoke providers/suppliers based on program integrity threats stemming from an excessive number of enrolled providers/suppliers within a particular area. We accordingly propose in new § 424.535(a)(24) that CMS may revoke a provider's or supplier's enrollment if it deems the enrollment as presenting a high risk of fraud, waste, or abuse due to the provider's or supplier's location within a limited geographic area that has an excessive number of providers and suppliers. We note the following concerning this proposal.</P>
                    <P>First, the term “high risk” for purposes of § 424.535(a)(24) does not mean the provider must be in: (1) the high screening level under § 424.518(c); or (2) a region that has traditionally posed a high risk of fraud, waste, and abuse, such as south Florida. To be sure, § 424.518(c) providers—as well as providers in known program integrity hotspots—pose elevated risks, a matter we may consider in § 424.535(a)(24) determinations. Yet other provider types in other areas can present threats as well. The risk that a particular provider poses based on its proximity to other providers—somewhat more so than the provider type and historic geographic risk—is the main consideration under proposed § 424.535(a)(24).</P>
                    <P>Second, and in a similar vein, a potential fraud scheme can involve multiple provider and supplier types; for instance, several HHAs, hospices, DMEPOS suppliers, physicians, etc., might be participating in a single operation. A § 424.535(a)(24) revocation therefore would not require the provider in question and the other providers/suppliers in the area to be of the same type.</P>
                    <P>Third, the terms “limited geographic area” or “excessive number” in the context of § 424.535(a)(24) will have their ordinary, plain-language meanings. This is due to the many factual situations that could arise and our need for flexibility in addressing them—something that thresholds such as minimum/maximum distance or numbers of providers would obstruct. Moreover, such thresholds would alert potentially problematic providers as to how to circumvent a § 424.535(a)(24) revocation. If, for example, we stated that § 424.535(a)(24) only applies if there are at least X number of providers within a radius of X miles, providers seeking to engage in fraud might enroll immediately outside said radius and/or within an area with fewer providers. This would defeat purpose of § 424.535(a)(24). That said, our primary focus is on providers in smaller areas—common buildings and complexes, city and town blocks, neighborhoods, etc. Although we reserve the right to apply § 424.535(a)(24) to providers in larger areas (especially if there is an abnormally high number of providers therein), the application of § 424.535(a)(24) would typically be more geographically limited.</P>
                    <P>Fourth, an actual finding of fraud, waste, or abuse by the provider or another provider in the area would not be required for a § 424.535(a)(24) revocation. This is akin to section 1866(j)(5) of the Act (codified in § 424.519), which permits denial or revocation if: (1) the provider has or has had a certain type of affiliation with another provider or supplier; and (2) the affiliation poses an undue risk of fraud, waste, or abuse; no determination of actual fraud, waste, or abuse is needed. Section 424.535(a)(24) revocations would be based on the assessed risk and not whether the provider or nearby providers have actually engaged in fraudulent conduct.</P>
                    <P>Fifth, while several existing revocation reasons in § 424.535(a) require CMS to consider specified factors in its revocation decisions, we are not proposing the same for § 424.535(a)(24). Consistent with our prior discussion regarding § 424.535(a)(8)(ii), we must be able to address all potential § 424.535(a)(24) scenarios without the rigid restrictions of required criteria and based solely on the unique facts and circumstances of each case.</P>
                    <P>Sixth, and notwithstanding the foregoing, we emphasize that proposed § 424.535(a)(24) is not designed to revoke good-faith providers who otherwise present no apparent risks even though they might, for example, be in an area with numerous other providers. We especially reiterate our understanding that many physicians and practitioners practice in the same building, complex, or other small area. Providers should not assume they would be revoked under § 424.535(a)(24) merely because they operate near other providers. Section 424.535(a)(24) would only be applied when the circumstances involved and the risk presented truly justify it.</P>
                    <P>Seventh, some interested parties may detect certain similarities between § 424.535(a)(24) and our authority under section 1866(j)(7) of the Act (codified in § 424.570) to impose a temporary enrollment moratorium. Although we address temporary moratoria in greater detail later in section V.C. of this proposed rule, we state here that a moratorium differs from § 424.535(a)(24) in many ways. The latter, for instance: (1) is a revocation reason rather than a prohibition on new enrollments; and (2) takes into account the provider's proximity to other providers of all types, not simply the number of (or risk posed by) providers of the same type.</P>
                    <HD SOURCE="HD3">(b) Certain Misdemeanor Convictions (§ 424.535(a)(16))</HD>
                    <P>In the CY 2024 PFS proposed rule (88 FR 52262), we proposed in new §§ 424.530(a)(16) and 424.535(a)(16) to deny or revoke enrollment if the provider—or any owner, managing employee or organization, officer, or director thereof—was convicted of a Federal or State misdemeanor within the past 10 years that CMS deems detrimental to the best interests of the Medicare program and its beneficiaries. We stated that offenses would include (but not be limited in scope or severity to):</P>
                    <P>• Fraud or other criminal misconduct involving the provider's participation in a Federal or State health care program or the delivery of services or items thereunder.</P>
                    <P>• Assault, battery, neglect, or abuse of a patient (including sexual offenses).</P>
                    <P>
                        • Any other misdemeanor that places the Medicare program or its beneficiaries at immediate risk, such as a malpractice suit that results in a conviction of criminal neglect or misconduct.
                        <SU>24</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>24</SU>
                             “Medicare and Medicaid Programs; CY 2024 Payment Policies Under the Physician Fee Schedule and Other Changes to Part B Payment and Coverage Policies; Medicare Shared Savings Program Requirements; Medicare Advantage; Medicare and Medicaid Provider and Supplier Enrollment Policies; and Basic Health Program”, published in the 
                            <E T="04">Federal Register</E>
                             on August 7, 2023.
                        </P>
                    </FTNT>
                    <PRTPAGE P="41292"/>
                    <P>We outlined in that CY 2024 proposed rule our increasing concern about providers convicted of misdemeanors for conduct that could endanger the Trust Funds and beneficiaries. We stated that our responsibility in overseeing the Medicare program requires that we be able to take protective action in such instances.</P>
                    <P>
                        We also noted that while some States may designate a particular crime as a misdemeanor while others deem it a felony, this does not lessen the risk that the former can pose to Medicare and its beneficiaries.
                        <SU>25</SU>
                        <FTREF/>
                         It is the conduct itself, not its classification under State law, that concerns us. This is particularly true since restricting our revocation authority for criminal convictions to felonies could leave us unable to address situations where a felony charge results in a misdemeanor plea.
                    </P>
                    <FTNT>
                        <P>
                            <SU>25</SU>
                             Ibid.
                        </P>
                    </FTNT>
                    <P>
                        As explained in the CY 2024 PFS final rule (88 FR 78818), we received numerous comments on this proposal. One of the commenters' concerns was that the proposal was too broad, potentially encompassing many types of misdemeanors involving comparatively modest conduct.
                        <SU>26</SU>
                        <FTREF/>
                         Based on the comments received, we did not finalize the proposal. We stated in the CY 2024 PFS final rule that: (1) we would continue to monitor cases of misdemeanor convictions involving significant misconduct; (2) we might pursue future rulemaking to address them; and (3) many misdemeanors—especially those involving assault, battery, neglect, or abuse of a patient (including sexual offenses)—could involve disturbing activity.
                        <SU>27</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>26</SU>
                             “Medicare and Medicaid Programs; CY 2024 Payment Policies Under the Physician Fee Schedule and Other Changes to Part B Payment and Coverage Policies; Medicare Shared Savings Program Requirements; Medicare Advantage; Medicare and Medicaid Provider and Supplier Enrollment Policies; and Basic Health Program”, published in the 
                            <E T="04">Federal Register</E>
                             on November 16, 2023.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>27</SU>
                             Ibid.
                        </P>
                    </FTNT>
                    <P>Two particularly disconcerting categories of misdemeanor convictions we have recently seen involve sexual assault and financial misconduct. The former can endanger Medicare beneficiaries while the latter can threaten the Trust Funds—both of which we must safeguard. In line with our aforementioned willingness to pursue future rulemaking if warranted, we propose in § 424.535(a)(16) (currently designated as “Reserved”) to revoke enrollment if the provider or supplier—or any owner, managing employee or organization, officer, or director thereof—was convicted of a Federal or State misdemeanor related to sexual assault or financial misconduct within the past 10 years that CMS deems detrimental to the best interests of the Medicare program and its beneficiaries.</P>
                    <P>While parts of this proposal duplicate those in the CY 2024 proposed rule (for example, the 10-year period, the applicability to owners, directors, etc.), there is one critical difference: it is much narrower in scope. Whereas the CY 2024 proposal was rather open-ended in terms of potential misdemeanors, the present one is limited to sexual assault and financial misconduct. We believe this would reduce interested parties' possible concerns that proposed § 424.535(a)(16) is too broad. In addition, we stress that: (1) terms such as financial misconduct would be based on their plain meanings; and (2) the misdemeanor convictions described in this paragraph must be detrimental to Medicare's (and Medicare beneficiaries') best interests, meaning that not every such conviction would result in revocation.</P>
                    <HD SOURCE="HD3">(c) Effective Dates of New Revocation Reasons</HD>
                    <P>Consistent with our proposed retroactive effective dates for all revocation reasons, we propose the following effective dates for proposed § 424.535(a)(16) and (24). The § 424.535(a)(16) effective date would be the date of the conviction, which mirrors the effective date for felony conviction revocations under § 424.535(a)(3); this date would be referenced in new § 424.535(g)(1)(xvi). For § 424.535(a)(24), we propose in new § 424.535(g)(1)(xxiv) an effective date that is the date on which CMS or its contractor determines that the provider should be revoked under § 424.535(a)(24). This aligns with our proposed effective date for our other risk-based revocation reason in § 424.535(a)(19) and is based on the difficulty in establishing a concrete date as to when the risk addressed in § 424.535(g)(1)(xxiv) commenced.</P>
                    <HD SOURCE="HD3">(7) Revised and New Denial Reasons (§ 424.530(a))</HD>
                    <P>We also propose a number of revised and new denial reasons in § 424.530(a).</P>
                    <HD SOURCE="HD3">(a) Changes to Existing Denial Reasons</HD>
                    <HD SOURCE="HD3">(i) Debt (§ 424.530(a)(6))</HD>
                    <P>Current § 424.530(a)(6)(i) and (ii) permit denial if the enrolling provider or owner (as defined in § 424.502) thereof—</P>
                    <P>• Has an existing Medicare debt; or</P>
                    <P>• Was previously the owner of a provider that had a Medicare debt when the latter provider's enrollment was voluntarily terminated, involuntarily terminated, or revoked (and additional criteria in § 424.530(a)(6)(ii)(A) through (C) are met).</P>
                    <P>We propose to include within the scope of § 424.530(a)(6) managing employees, managing organizations, and individuals and entities with any other form of business or financial relationship with the provider.</P>
                    <P>Section 424.530(a)(6)(i)'s purpose is to prevent providers (and owners thereof) from enrolling additional locations when they have debts to Medicare via their current enrollments that they have not paid. Indeed, if they have not fulfilled these financial obligations, we cannot be certain they will do so with their new enrollments, hence threatening the Trust Funds. The goal of § 424.530(a)(6)(ii), meanwhile, is to address situations where a party—often via their ownership of a provider—(1) incurs a substantial debt to Medicare; (2) exits the Medicare program, shuts down operations altogether, and attempts to re-enter Medicare through another vehicle or under a new business identity. The party's objective often is to avoid paying the prior debt while incurring additional debts through their ownership of the new provider. Section 424.530(a)(6)(ii) helps prevent this by blocking the new provider's enrollment.</P>
                    <P>Gaps remain, though. As noted in prior rulemaking efforts, managing employees and managing organizations (as defined in § 424.502) often have as much or more influence over a provider's day-to-day operations as an owner. Yet § 424.530(a)(6) only references the provider itself and its owners. Section 424.530(a)(6) thus cannot prevent enrollment if, for instance, a managing employee or organization of the prior provider ran its daily operations, was responsible for its accumulation of large debts, and now seeks to re-enter Medicare through their ownership of the new provider. Moreover, we have seen instances where parties other than owners and managing employees/organizations were substantially involved with the former provider in some capacity; as examples, this includes: (1) parties that furnished services or provided financing for the prior provider; and (2) closely associated health care providers. The core issue, therefore, is not the precise form or label of the relationship with the former provider—that is, whether it was ownership, financial, etc. It is instead the relationship itself and the party's effort to enroll new locations or reenter Medicare through the new provider.</P>
                    <P>
                        We emphasize that we do not intend to deny enrollment in all scenarios 
                        <PRTPAGE P="41293"/>
                        involving revised § 424.530(a)(6). Each case would be carefully judged on its own circumstances, and denial would only occur when warranted.
                    </P>
                    <HD SOURCE="HD3">(ii) Payment Suspension (§ 424.530(a)(7))</HD>
                    <P>Denial is permitted under § 424.530(a)(7) if the provider, or any owning or managing employee or organization of the provider, is currently under a Medicare or Medicaid payment suspension (as defined in §§ 405.370 through 405.372 or in § 455.23). For the same reasons behind our proposed addition to § 424.530(a)(6), we propose at § 424.530(a)(7) to include within scope individuals and entities with any form of business or financial relationship with the provider. A payment suspension is a serious matter and, as noted, parties other than owners and managing employees/organizations can have relationships with the provider. In addition, restricting § 424.530(a)(7) to owning/managing individuals and entities could encourage these parties to circumvent application of § 424.530(a)(7) by redefining, changing, or limiting their roles within the provider organization even though they would still influence or deal with the provider in some capacity; that is, they would purposely modify or eliminate their ownership or reduce their role in the organization to, they might believe, fall outside the managing employee/organization definitions. Given both this and our responsibility to protect the Trust Funds against problematic parties, we believe our proposed expansion to § 424.530(a)(7) is a prudent measure.</P>
                    <HD SOURCE="HD3">(iii) Program Terminations/Suspensions (§ 424.530(a)(14))</HD>
                    <P>CMS may deny enrollment under current § 424.530(a)(14)(i) if—</P>
                    <P>• The provider is currently terminated or suspended (or otherwise barred) from participation in a State Medicaid program or any other Federal health care program; or</P>
                    <P>• The provider's license is currently revoked or suspended in a State other than that in which the provider is enrolling.</P>
                    <P>We propose two changes to § 424.530(a)(14)(i). One would include the provider's owners, managing employees, and managing organizations within its purview. This aligns with several other denial reasons—such as existing § 424.530(a)(3) and (a)(7)—that include actions against owners and managing employees/organizations. Similar to these other denial grounds, revised § 424.530(a)(14)(i) would help prevent situations where the owning/managing party's conduct that led to the licensure action or the other program termination/suspension could be repeated with the prospective Medicare provider, especially considering (as noted) the significant influence such parties typically have over a provider's operations. Furthermore, it could keep such parties from entering Medicare via a new provider, hoping to shield themselves from application of § 424.530(a)(14)(i) due to the provision's current limitation to providers.</P>
                    <P>The other change would expand licenses to include those voluntarily surrendered in lieu of further disciplinary action. We have provisions in §§ 424.530 and 424.535 whose scope includes voluntary surrenders, and we believe the same approach for § 424.530(a)(14)(i) is needed because our overriding concern is the loss of the provider's license rather than the type of loss. Voluntary surrenders in lieu of further disciplinary action, in our view, are as much a threat to the Trust Funds and beneficiaries as revocations and suspensions, since they all involve problematic conduct.</P>
                    <HD SOURCE="HD3">(iv) False or Misleading Data (§ 424.530(a)(4))</HD>
                    <P>Section 424.530(a)(4) allows denial based on the provider's/supplier's submission of false or misleading information on the enrollment application to gain enrollment in the Medicare program. We propose to expand § 424.530(a)(4) in the same manner as with proposed § 424.535(a)(4) and for the same reasons. (The parenthetical concerning OIG referral would be retained in existing § 424.530(a)(4).)</P>
                    <HD SOURCE="HD3">(b) New Denial Reasons</HD>
                    <HD SOURCE="HD3">(i) Misdemeanor Convictions (§ 424.530(a)(16))</HD>
                    <HD SOURCE="HD3">(A) New § 424.530(a)(16)</HD>
                    <P>We propose to duplicate proposed § 424.535(a)(16) in § 424.530(a)(16) (also presently designated as “Reserved”) as a new denial ground. The same rationale is involved: the need to protect beneficiaries and the Trust Funds against parties convicted of sexual assault or financial misconduct misdemeanors.</P>
                    <HD SOURCE="HD3">(B) “Final Adverse Action” Definition</HD>
                    <P>Section 424.502 defines “final adverse action” as any of the following: (1) Medicare revocation; (2) State health care license suspension or revocation; (3) revocation or suspension by an accreditation organization; (4) felony conviction; or (5) exclusion or debarment. Given our proposed denial and revocation reasons based on a misdemeanor conviction for sexual assault or financial misconduct, we propose to add such misdemeanors as new paragraph (6) in the “final adverse action” definition. (As with felony convictions in paragraph (4), the 10-year period would be that preceding enrollment, revalidation, or reenrollment.)</P>
                    <HD SOURCE="HD3">(ii) Revocation or Denial in Same Suite (§ 424.530(a)(19))</HD>
                    <P>We propose a new denial ground in § 424.530(a)(19) based on the provider having its practice location in the same suite or office as another provider whose Medicare enrollment has been revoked or denied. Sharing a suite or office with a provider who has been deemed non-compliant with Medicare requirements could spur concerns about the newly enrolling provider's own willingness to retain compliance if enrolled. This is particularly true when—in situations we have seen—several providers in the same suite engage (or seek to engage) in a fraud scheme, have their Medicare enrollments revoked or denied, and another provider aims to enroll in that same office. Considering the risks posed by the revoked or denied provider, we maintain that we must have the authority to prevent the new enrollment if circumstances justify it.</P>
                    <P>Though they might appear similar, § 424.530(a)(19) would differ from proposed § 424.535(a)(24) in that the latter: (a) is a revocation reason and not a denial ground; and (b) is partly based on the number of nearby providers, whereas § 424.530(a)(19) is based on shared suites and offices. Sections 424.530(a)(19) and § 424.535(a)(24) thus complement but do not duplicate each other.</P>
                    <P>We recognize that, for example, physicians that are part of a group frequently share the same suite. If 10 physicians are in the group and one (Dr. X) has their enrollment revoked, this does not automatically mean that a prospective (and Medicare enrolling) 11th group member will be denied enrollment based on Dr X's revocation. Every situation is different, and CMS will only invoke § 424.530(a)(19) when proper.</P>
                    <HD SOURCE="HD3">(iii) Hospice Medical Directors and Administrators (§ 424.530(a)(20))</HD>
                    <P>
                        As previously discussed, we have seen serious program integrity issues involving hospices. Indeed, the Office of Inspector General (OIG) has included hospice care among the services posing 
                        <PRTPAGE P="41294"/>
                        a high risk of fraud.
                        <SU>28</SU>
                        <FTREF/>
                         It has also recently stated: “[T]here are significant problems with the [hospice] program. Our reports and investigations have revealed several concerning issues, including poor—sometimes harmful—quality of care, fraud schemes that involve enrolling beneficiaries without their consent, inappropriate billing practices, limited transparency for patients and their families, a payment system that creates incentives to minimize services, and a rapid growth in the number of new hospices, often to take advantage of these conditions.” 
                        <SU>29</SU>
                        <FTREF/>
                         In response to these concerns, CMS in recent years has taken numerous steps to address hospice fraud, waste, and abuse. Some have been directed towards persons who operate, control, or manage the hospice, such as the hospice's individual owners, medical directors, and administrators. These initiatives included, but were not limited to—
                    </P>
                    <FTNT>
                        <P>
                            <SU>28</SU>
                             HHS-OIG Fiscal Year 2025 Report, “Top Management &amp; Performance Challenges Facing HHS” (
                            <E T="03">https://oig.hhs.gov/reports/all/2025/2025-top-management-performance-challenges-facing-hhs/.</E>
                            )
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>29</SU>
                             
                            <E T="03">https://oig.hhs.gov/reports/featured/hospice/.</E>
                        </P>
                    </FTNT>
                    <P>• Under § 424.518(c), requiring persons who directly or indirectly own 5 percent or more of a newly enrolling hospice (or a hospice undergoing any ownership change) to submit fingerprints for a criminal background check.</P>
                    <P>• Requiring hospice medical directors who certify a patient's terminal illness under 418.22(c) to be enrolled in or opted out of Medicare, which enables CMS to screen the medical director.</P>
                    <P>• Clarifying that hospice medical directors and administrators are “managing employees” (as that term is defined in § 424.502) and thus must be reported on the hospice's Form CMS-855A enrollment application (OMB Control No. 0938-0685). This helps ensure that CMS knows the identities of these parties and can vet them for potential issues.</P>
                    <P>
                        In light of medical directors' and administrators' managing control over hospices, we believe that closer oversight of these individuals was necessary—especially considering: (1) the numerous criminal and False Claims Act cases we have seen involving hospice operators; 
                        <SU>30</SU>
                        <FTREF/>
                         and (2) reports of physicians falsely certifying patients' terminal status.
                        <SU>31</SU>
                        <FTREF/>
                         Despite the aforementioned steps, we continue to have program integrity concerns about hospice operators. We still see instances of false physician certifications, kickbacks to certifying physicians, criminal cases involving administrators, hospices billing Medicare while non-compliant with enrollment requirements, etc. On a more specific level, three problematic issues have arisen.
                    </P>
                    <FTNT>
                        <P>
                            <SU>30</SU>
                             See, for example, the proposed rule titled, “Medicare Program; Calendar Year (CY) 2024 Home Health (HH) Prospective Payment System Rate Update; HH Quality Reporting Program Requirements; HH Value-Based Purchasing Expanded Model Requirements; Home Intravenous Immune Globulin Items and Services; Hospice Informal Dispute Resolution and Special Focus Program Requirements, Certain Requirements for Durable Medical Equipment Prosthetics and Orthotics Supplies; and Provider and Supplier Enrollment Requirements” (88 FR 43654), published in the 
                            <E T="04">Federal Register</E>
                             on July, 10, 2023.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>31</SU>
                             See, for example, the proposed rule titled, “Medicare Program; FY 2024 Hospice Wage Index and Payment Rate Update, Hospice Conditions of Participation Updates, Hospice Quality Reporting Program Requirements, and Hospice Certifying Physician Provider Enrollment Requirements” (88 FR 20022), published in the 
                            <E T="04">Federal Register</E>
                             on April 4, 2023.
                        </P>
                    </FTNT>
                    <P>First, there are individuals who serve as medical director or administrator of numerous hospices. Ensuring (1) quality care to hospice patients, (2) the efficiency of the hospice's operations, (3) compliance with Medicare requirements, and (4) hospice program integrity requires the full attention and oversight of the medical director and administrator. We believe that having these roles at numerous facilities limits the time the individual can spend on each facility's operations and raises questions about the person's commitment to oversight; this, in our view, places hospice beneficiaries and program integrity at risk.</P>
                    <P>Second, we have seen cases where the medical director or administrator is very far from the physical hospice facility; several instances, in fact, involved the hospice and medical director being on opposite sides of the country (for instance, the medical director is in New York, and the hospice is in California). This, too, generates significant concerns about the individual's oversight of the hospice.</P>
                    <P>Third, certain hospices have been using medical directors with inactive licenses. Section 418.22(c), as noted, requires the medical director who initially certifies the beneficiary's terminal status to be enrolled in or opted-out of Medicare. However, if the medical director is not certifying Medicare beneficiaries' terminal status—and said physician is neither billing Medicare nor ordering/certifying the services/items outlined in § 424.507—enrollment is not required. CMS therefore might not know whether the medical director's license is active and only learn of the inactive status later. Since the medical director Conditions of Participation (CoPs) at § 418.102 and personnel requirements for physicians § 418.114(b)(1) require hospice medical directors to be physicians (and thus licensed), hospices with medical directors with inactive licenses are not compliant with the CoP Medicare requirements.</P>
                    <P>To address hospice program integrity and to protect beneficiaries, we thus propose new § 424.530(a)(20). This would permit denial of a hospice's enrollment application if any of the following apply:</P>
                    <P>• The enrolling hospice's medical director is—</P>
                    <P>++ The medical director of multiple other hospices, or</P>
                    <P>++ Practices at such a distance (for example, in a different state) from the enrolling hospice that the medical director cannot realistically perform all medical director functions required under 42 CFR part 418.</P>
                    <P>• The enrolling hospice's administrator is—</P>
                    <P>++ The administrator of multiple other hospices; or</P>
                    <P>++ Located at such a distance from the enrolling hospice that the administrator cannot realistically perform all administrator functions required under 42 CFR part 418.</P>
                    <P>• The hospice's medical director does not have an active physician medical license in the state in which they are practicing.</P>
                    <P>Section 424.530(a)(20) would not: (1) formally prohibit medical directors and administrators from serving at more than one hospice; or (2) change hospice CoPs or other hospice policies in 42 CFR part 418. It would simply help us address situations where the hospice's prospective enrollment raises the program integrity concerns outlined in this section V.C. of this proposed rule.</P>
                    <HD SOURCE="HD3">(iv) Misuse of Identity (§ 424.530(a)(21))</HD>
                    <P>
                        We noted previously that § 424.535(a)(7) permits revocation if the provider knowingly sells to or allows another individual or entity to use its billing number. (This does not include providers or suppliers who enter into a valid § 424.80 reassignment of benefits or a § 489.18 change of ownership.) Yet there is no denial reason that specifically addresses misuse of identifiers. This is problematic given situations we have recently seen where a party (X) steals the identity of another party (Y) (for example, another physician or practitioner) and enrolls Y without Y's knowledge and using Y's credentials and identifiers. X then bills and receives payment from Medicare under Y's name. To address this and other situations involving prospective enrollees using compromised identities, 
                        <PRTPAGE P="41295"/>
                        we propose in new § 424.530(a)(21) that CMS can deny enrollment if the prospective provider or supplier is attempting to enroll under another party's identity.
                    </P>
                    <HD SOURCE="HD3">(8) Reapplication Bar (§ 424.530(f))</HD>
                    <P>Under § 424.530(f), CMS may prohibit a prospective provider from enrolling in Medicare for up to 10 years if its enrollment application is denied because the provider submitted false or misleading information on or with (or omitted information from) its application to gain enrollment in Medicare. The goal is to prevent dishonest providers from submitting false information on their initial application and, after being denied enrollment on this ground under § 424.530(a)(4), simply submitting a new application with correct data.</P>
                    <P>We believe that restricting § 424.530(f) to instances involving false information limits its potential effectiveness, for there are other § 424.530(a) denial reasons that could involve similarly inappropriate provider behavior. Assume a prospective provider's enrollment is denied because the provider is: (1) unlicensed; (2) OIG excluded or has a recent felony conviction; (3) using a false storefront as its practice location; (4) under a current Medicare and Medicaid payment suspension based on a credible allegation of fraud; (5) terminated from another Federal health care program; or (6) revoked from Medicare and attempting to enroll under a different identity. This casts serious doubt as to the provider's honesty and trustworthiness, since the provider likely knows it cannot enroll but is nonetheless hoping to somehow “sneak into” the program; indeed, without a reapplication bar in these and similar situations, the provider might routinely submit more such applications with this nefarious objective in mind.</P>
                    <P>Accordingly, and to safeguard the Medicare program, we propose to revise the introductory text of § 424.530(f) to allow CMS to impose a reapplication bar for up to 10 years based on any § 424.530(a) denial reason (not merely § 424.530(a)(4)). We also propose to delete factors at § 424.530(f)(2) that CMS currently must consider in determining whether to impose a reapplication bar (and the length thereof) for a denial at § 424.530(a)(4). There are two related reasons for this. First, being tailored exclusively to § 424.530(a)(4) situations, these factors would be inapplicable to other denial grounds. Second, proposing different § 424.530(a)(4) criteria would essentially present the same problem mentioned in the previous sentence—specifically, a single set of § 424.530(f) factors could not possibly apply to all § 424.530(a) denial reasons considering the varying facts of each.</P>
                    <P>Unlike reenrollment bars under § 424.535(c), reapplication bars are discretionary. CMS need not impose them, and we are not proposing to change this. We recognize that less serious denial situations—such as, but not limited to, failure to pay an application fee—might not warrant a reapplication bar. Our focus is mostly on providers whose conduct raises significant program integrity concerns.</P>
                    <P>We would retain current § 424.530(f)(1) and (f)(3), which address, respectively, the bar's: (1) applicability to the provider's other names, identities, etc.; and (2) impact on the ordering, referral, certification, or prescription of services, items, or drugs. Paragraph (f)(3), though, would be redesignated as revised paragraph (f)(2).</P>
                    <HD SOURCE="HD3">(9) Changes in Majority Ownership (CIMOs)</HD>
                    <P>We previously mentioned § 424.550(b) and § 424.551, the former pertaining to HHAs and hospices and the latter to DMEPOS suppliers (hereafter collectively “providers”). Under these provisions, if the provider undergoes a CIMO within 36 months of its initial enrollment—or within 36 months of its most recent CIMO—and no exception applies, the provider's enrollment is terminated. (For HHAs and hospices, moreover, the provider agreement is terminated and does not transfer to the new owner.) The provider under its new majority ownership must enroll as a new provider and undergo a state survey or accreditation. (DMEPOS suppliers must obtain a new accreditation.)</P>
                    <P>There are two main purposes of this “36-month rule”. First, it enables CMS to undertake a complete screening and vetting of the provider under its new ownership. This is critical for ensuring that the provider is compliant with all Medicare requirements. Second, it helps prevent “flipping”. This involves a party enrolling a provider for the sole purpose of quickly selling it to another party without the latter having to newly enroll or undergo a survey/accreditation. This makes the provider more financially attractive to the prospective buyer and, in turn, helps the seller generate more revenue from the sale. In short, the seller's exclusive objective is profit, not patient care. This places beneficiaries at risk and allows parties to enter Medicare without the program safeguard of a survey or accreditation.</P>
                    <P>We have found the 36-month rule helpful in stemming flipping and facilitating greater scrutiny of new owners. Yet we have also seen provider efforts to circumvent or ignore the rule. These include, but are not limited to:</P>
                    <P>• Failing to notify CMS of the ownership change—meaning the sale occurs and the buyer assumes ownership under the existing enrollment without enrolling the entity as a new provider with a new survey/accreditation. Only later does CMS learn of the sale.</P>
                    <P>• Using a management (or similar) agreement in lieu of a formal sales agreement. Here, the management agreement states that: (1) managerial (and effectively all other) authority over the provider is transferred to Party X; and (2) X intends to later purchase the provider. Once the 36-month period expires, the sale occurs. In essence, Party X is purchasing the provider within the 36-month period but under the guise of a “management agreement”.</P>
                    <P>Such inappropriate attempts to avoid the 36-month rule undercut the latter's critical aim of protecting beneficiaries and the Trust Funds from unvetted and potentially problematic entities. To deter these efforts, we propose in new §§ 424.530(a)(22) and 424.535(a)(25) that we may deny or revoke enrollment if CMS determines that the HHA, hospice, or DMEPOS supplier failed to comply with the provisions and requirements of, as applicable, §§ 424.550(b) or 424.551. The § 424.535(a)(25) revocation effective date under new § 424.535(g)(1)(xxv) would be the date on which CMS or its contractor determined that the provider should be revoked.</P>
                    <HD SOURCE="HD3">3. Preclusion List (42 CFR 422.2 and 423.100)</HD>
                    <P>Addressed primarily in 42 CFR 422.222 and 423.120, the preclusion list is a compilation of providers and prescribers who are prohibited from receiving payment for furnished, ordered, or prescribed MA items/services and Part D drugs. The list's objective is to effectively bar from the MA and Part D programs various entities and persons that pose program integrity risks. Per the definition of “preclusion list in §§ 422.2 and 423.100, a party may be placed on the preclusion list if they fall into one of the following three categories:</P>
                    <P>
                        • Currently revoked under Medicare for a reason other than that in § 424.535(a)(3) (which addresses felony convictions), the reenrollment bar has not expired, and CMS determines that the underlying conduct that led to the 
                        <PRTPAGE P="41296"/>
                        revocation is detrimental to the Medicare program's best interests.
                    </P>
                    <P>• Engaged in behavior, other than that described in § 424.535(a)(3): (1) for which CMS could have revoked the provider/prescriber to the extent applicable had they been enrolled in Medicare; and (2) that CMS determines is detrimental to the Medicare program's best interests.</P>
                    <P>• Regardless of whether the provider/prescriber is or was enrolled in Medicare, has been convicted of a felony under Federal or State law within the previous 10 years that CMS deems detrimental to the Medicare program's best interests.</P>
                    <P>We propose to expand this third category to include felony convictions against the provider/prescriber's owner, managing employee, managing organization, corporate director, or corporate officer. As already stated, these parties typically exercise considerable influence over a provider/prescriber's operations, and a felony conviction against said party greatly concerns us; indeed, this is precisely why §§ 424.530(a)(3) and 424.535(a)(3) permit denial or revocation based on felony convictions against owners, managing employees/organizations, and corporate officers/directors. Our proposed change would not only ensure greater consistency with §§ 424.530(a)(3) and 424.535(a)(3) but also help protect the MA and Part D programs from program integrity risks.</P>
                    <P>The specific regulatory revisions would be to paragraph (3) of the “preclusion list” definitions in §§ 422.2 and 423.100. The language therein stating that the prescriber/provider, “regardless of whether they are or were enrolled in Medicare, has been convicted of a felony. . . .” would be changed to the prescriber/provider, “regardless of whether they are or were enrolled in Medicare—or an owner, managing employee, managing organization, director, or officer (as those terms are defined in § 424.502) thereof—has been convicted of a felony. . . . .”.</P>
                    <HD SOURCE="HD3">4. Temporary Moratoria (§ 424.570)</HD>
                    <P>
                        Pursuant to section 1866(j)(7) of the Act and § 424.570, we imposed several temporary enrollment moratoria between 2013 and 2019, and—as of May 13, 2026—there are national moratoria on the enrollment of new HHAs, hospices, and DMEPOS medical supply companies. All moratoria (including a moratorium extension) are announced via a notice published in the 
                        <E T="04">Federal Register</E>
                        . Also, under § 424.570(a)(1)(iii)(A) through (C) a temporary moratorium does not apply to any of the following:
                    </P>
                    <P>• Changes in practice location (except if the location is changing from a location outside the moratorium area to a location inside the moratorium area).</P>
                    <P>• Changes in provider or supplier information, such as phone number.</P>
                    <P>• Changes in ownership (except changes in ownership of HHAs that would require an initial enrollment).</P>
                    <P>Since restarting the moratorium process in 2026 after more than 6 years, we have seen several issues that we believe must be addressed in regulation.</P>
                    <HD SOURCE="HD3">a. Effective Date</HD>
                    <P>Per § 424.570(a)(1)(iv), a temporary moratorium does not apply to any enrollment application received by the Medicare contractor prior to the date the moratorium is imposed. We have received questions from interested parties regarding: (1) when the imposition date is; and (2) whether this is the same as the moratorium's effective date. We accordingly propose to revise § 424.570(a)(1)(iv) as follows:</P>
                    <P>• Existing § 424.570(a)(1)(iv) would be redesignated as new § 424.570(a)(1)(iv)(A).</P>
                    <P>• New § 424.570(a)(1)(iv)(B) would state that the date the moratorium is imposed is the moratorium's effective date, which is the date on which the moratorium notice was filed for public inspection at the Office of the Federal Register (OFR).</P>
                    <P>
                        There are often gaps between when a document (such as a proposed rule) is filed for OFR public inspection and when it is published in the 
                        <E T="04">Federal Register</E>
                        . If we used the latter as the moratorium's imposition/effective date, the affected providers/suppliers might have several days to submit their initial applications in order to “beat the deadline.” This would partly obstruct the moratorium's goal of halting all new enrollments and could lead to a rush of new applicants during this gap, some of whom may present program integrity problems. Using the OFR filing date would prevent this scenario, for the moratorium's imposition would be immediate.
                    </P>
                    <HD SOURCE="HD3">b. Ownership Changes</HD>
                    <P>We propose to change the aforementioned parenthetical in §  424.570(a)(1)(iii)(C) from “(except changes in ownership of home health agencies that would require an initial enrollment)” to “(except changes in ownership that require an initial enrollment, such as, but not limited to, an HHA, hospice, or DMEPOS supplier change in majority ownership under §§ 424.550(b) or 424.551)”. This update would conform to other regulations that address this topic and codify existing CMS policy that—like HHAs—hospices and DMEPOS suppliers that undergo a non-exempt CIMO under §§ 424.550(b) or 424.551 must enroll as a new provider/supplier and are thus subject to the moratorium.</P>
                    <HD SOURCE="HD3">c. Other Applicability</HD>
                    <P>Section 424.570(a)(1)(i) states CMS may impose a moratorium on the enrollment of new Medicare providers and suppliers of a particular type or the establishment of new practice locations of a particular type in a particular geographic area. Stakeholders have asked what qualifies as a “new” provider/supplier or practice location under the moratorium. To address these, we propose to outline in new § 424.570(a)(1)(i)(A) through (E) the application types that—solely for purposes of § 424.570(a)—are considered “new” and to which a moratorium applies:</P>
                    <FP SOURCE="FP-1">• Initial enrollment applications</FP>
                    <FP SOURCE="FP-1">• Change of ownership applications that require an initial enrollment per § 424.570(a)(1)(iii)(C)</FP>
                    <FP SOURCE="FP-1">• Enrollment applications from revoked providers/suppliers whose reenrollment bars under § 424.535(c) have expired and are seeking to re-enter the Medicare program</FP>
                    <FP SOURCE="FP-1">• Reactivation applications</FP>
                    <FP SOURCE="FP-1">• Enrollment applications from voluntarily terminated providers/suppliers seeking to enroll again in the Medicare program</FP>
                    <P>Initial and change of ownership applications are currently referenced in § 424.570. Revoked providers (proposed § 424.570(a)(1)(i)(C)) are removed from the Medicare program altogether; we have thus always considered their applications to reenroll in Medicare to be new enrollments.</P>
                    <P>
                        Reactivation involves the provider restoring their active enrollment status and Medicare billing privileges after being deactivated per § 424.540. Deactivation means the provider's billing privileges are stopped but can be restored (or “reactivated”) upon the submission of information required under § 424.540. Deactivation grounds include, but are not limited to, failure to submit a Medicare claim for 6 consecutive months, failure to timely report a change in enrollment information, non-compliance with enrollment requirements, and a non-operational practice location. Although a deactivated provider is not revoked from Medicare, the provider's: (1) ability to bill the program is halted pending its reactivation; (2) enrollment is effectively 
                        <PRTPAGE P="41297"/>
                        shut down; and (3) participation in Medicare is blocked in a manner akin to a revocation. (In fact, the only material differences between a revoked and a deactivated provider are that the former is subject to a reenrollment bar and a potentially more exhaustive reentry process (for instance, undergoing a state survey or accreditation)). Furthermore, the bases for both revocations and deactivations typically involve concerning provider behavior. Even if the deactivation was based on non-billing with no nefarious conduct, said conduct could have ensued if, for example, an unscrupulous party attempted to access the provider's billing number during the non-billing period. We hence believe that the significant similarities between deactivations and revocations warrant including reactivations within § 424.570(a)(1)(i).
                    </P>
                    <P>The same rationale applies to voluntary terminations, which involve a provider departing Medicare on their own volition. The provider is consciously severing their relationship with Medicare. While § 424.540(a)(7) permits CMS to deactivate a voluntarily terminating provider rather than outright terminating it, the provider in either case is essentially no longer in the program. It is considered a new provider should it seek to reenter Medicare. The incorporation of voluntary terminations within § 424.570(a)(1)(i) is therefore proper.</P>
                    <HD SOURCE="HD3">5. Hospice Reactivations (§ 424.540(b)(3))</HD>
                    <P>We mentioned earlier that hospices (like HHAs) that undergo a non-exempt CIMO within 36 months of their initial enrollment (or within 36 months of their previous CIMO) must initially enroll as a new hospice and have a state survey or accreditation. A new enrollment and survey/accreditation help confirm that the hospice under its new ownership is fully vetted, is committed to furnishing quality care, meets all enrollment requirements and CoPs, and does not pose program integrity risks. The substantial program integrity and quality of care benefits of a state survey/accreditation are why in 2009 we promulgated § 424.540(b)(3)(i), which requires a deactivated HHA to obtain an initial state survey/accreditation before it can be reactivated.</P>
                    <P>We believe the payment safeguard and patient care protections afforded by § 424.540(b)(3) should be extended to hospices. The previously noted hospice fraud we have seen requires, in our view, much closer scrutiny of reactivating hospices—especially since, as already noted, deactivated hospices are blocked from Medicare. We must ensure that the reentering hospice is compliant with all Medicare requirements. We thus propose to revise § 424.540(b)(3)(i) to include hospices.</P>
                    <HD SOURCE="HD3">6. Opt-Out (42 CFR Part 405, Subpart D)</HD>
                    <P>Section 1802(b)(1) of the Act permits certain physicians and practitioners to opt-out of Medicare. Under opt-out, neither the physician/practitioner nor the beneficiary submits a bill to Medicare for services performed. Instead, the beneficiary pays the physician/practitioner out-of-pocket and neither party is reimbursed by Medicare. A private contract is signed between the physician/practitioner and the beneficiary that states, in essence, that neither can receive payment from Medicare for the services performed. The physician/practitioner must also submit an affidavit to Medicare expressing a decision to opt-out of the program and confirming, as further described in § 405.420, compliance with opt-out requirements. Opt-out periods are for 2 years.</P>
                    <P>Provisions in 42 CFR part 405, subpart D, govern Medicare opt-out. We are proposing the following two regulatory clarifications, both of which reflect current policy.</P>
                    <P>First, opt-out periods are automatically renewed pursuant to section 1802(b)(3) of the Act unless the physician/practitioner—consistent with § 405.445(a)—notifies the appropriate MAC not later than 30 days before the end of the 2-year period indicating that the physician/practitioner does not want to extend the affidavit's extension for a subsequent 2-year period. In outlining the types of CMS opt-out determinations that are considered “initial” under § 498.3(b) (and thus appealable under 42 CFR part 498), § 405.450(a) includes the individual's failure to “timely renew opt-out”. Since opt-out is automatically extended absent the occurrence in § 405.445(a), we propose to change the quoted language in § 405.450(a) to “timely cancel automatic renewal”; a similar change would be made to § 498.3(b)(19), which lists various initial opt-out-related determinations.</P>
                    <P>Second, § 405.400 defines “opt-out period” as meaning, in part—with respect to an affidavit that meets the requirements of § 405.420—a 2-year period beginning on the date the affidavit is signed (as specified by § 405.410(c)(1) or (2)). There are instances where the MAC, in reviewing and processing the physician/practitioner's submitted affidavit, needs and requests additional information or clarification from the physician/practitioner. Interested parties have asked whether—if a new affidavit must be submitted per the MAC's request and it is subsequently approved—the opt-out period begins on the signature date of the second or the first submitted affidavit. In § 405.400, we propose to change the “opt-out period” definition that states “the date the affidavit is signed” to “the date the first submitted affidavit is signed.” This reflects our existing policy on this issue, and it aligns with our assignment of effective dates of Medicare billing privileges for most Medicare suppliers (including physicians/practitioners). Under § 424.520(d)(i) and (ii), this effective date for these suppliers is the later of the following: (1) the date of filing of a Medicare enrollment application that was subsequently approved by a Medicare contractor; or (2) the date that the provider or supplier first began furnishing services at a new practice location. With § 424.520(d)(i), even if the MAC needs the supplier to submit additional/clarifying information on the submitted enrollment application with a newly signed certification statement, the effective date is generally based on the initially submitted application rather than the date on which the additional data was submitted.</P>
                    <HD SOURCE="HD3">7. Private Equity Companies (PECs) and Real Estate Investment Trusts (REITs)</HD>
                    <P>
                        In a November 17, 2023, final rule published in the 
                        <E T="04">Federal Register</E>
                         titled, “Medicare and Medicaid Programs; Disclosures of Ownership and Additional Disclosable Parties Information for Skilled Nursing Facilities and Nursing Facilities; Medicare Providers' and Suppliers' Disclosure of Private Equity Companies and Real Estate Investment Trusts” (88 FR 80141), we implemented section 1124(c) of the Act. This provision—promulgated in § 424.516(g)—requires SNFs to report detailed information about their ownership, management, and associated parties. The regulation's purpose was to gain further insight into the SNF's operators and affiliates—a vital need given concerns about nursing home quality of care.
                    </P>
                    <P>
                        We expressed particular concern in the November 17, 2023, final rule about the prevalence of PEC and REIT ownership of SNFs. We cited reports indicating links between such ownership and substandard SNF care, primarily due to these entities' emphasis on maximizing profits.
                        <SU>32</SU>
                        <FTREF/>
                         One report stated, “Our estimates show that private equity (PE) ownership increases the short-term mortality of Medicare 
                        <PRTPAGE P="41298"/>
                        patients by 10 percent, implying 20,150 lives lost due to PE ownership over our twelve-year sample period. This is accompanied by declines in other measures of patient well-being, such as lower mobility, while taxpayer spending per patient episode increases by 11 percent.” 
                        <SU>33</SU>
                        <FTREF/>
                         We hence stated in the November 17, 2023, final rule our intention to revise the Form CMS-855A enrollment application 
                        <SU>34</SU>
                        <FTREF/>
                         to require all certified providers and certified suppliers (not simply SNFs) that complete said form to identify whether an entity they have disclosed thereon is a PEC or a REIT.
                        <SU>35</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>32</SU>
                             88 FR 80144.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>33</SU>
                             Ibid.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>34</SU>
                             Medicare Enrollment Application—Institutional Providers (OMB Control No. 0938-0635).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>35</SU>
                             88 FR 80146.
                        </P>
                    </FTNT>
                    <P>
                        The issue goes well beyond SNFs, though. PECs and REITs are involved in other health care sectors, too, including physician practices. The May 2025 edition of the American Medical Association's (AMA) Journal of Ethics (JOE) noted the continued increase in PEC ownership of providers and suppliers and the concerns associated therewith. The AMA JOE website (via which the May 2025 edition could be accessed) stated that private equity “aim(s) to maximize profitability while minimizing long-term holdings in such investments. . . . One reason private equity investment in the health sector deserves close ethical attention is that private equity firms are, generally, not interested in managing patient panels, clinician personnel, or making service delivery streams work for patients. Another reason is that influx of private equity investment in health care tends to consolidate markets for health services, undermining competition and driving up costs for patients”.
                        <SU>36</SU>
                        <FTREF/>
                         Various articles in the May 2025 edition expounded on this theme. Statements therein included:
                    </P>
                    <FTNT>
                        <P>
                            <SU>36</SU>
                             
                            <E T="03">https://journalofethics.ama-assn.org/issue/private-equity-health-care.</E>
                        </P>
                    </FTNT>
                    <P>
                        • “Physicians have fiduciary duties to respond with care to patient's clinical needs and vulnerabilities, whereas private equity companies have no such ethical or legal duties to patients and strive to maximize financial returns for their investors.” 
                        <SU>37</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>37</SU>
                             Lucy Xu, MD, and Matthew R. Naunheim, MD; “What Are Physicians' Duties to Patients When They Sell Their Practices?”; May 2025.
                        </P>
                    </FTNT>
                    <P>
                        • “Studies on the impact of PE investment in health care have increased in the last decade, with the preponderance of data suggesting that PE acquisitions are associated with reduced staffing levels and on-hand medical supplies. A 2023 systematic review concluded that PE ownership was associated with increased costs to payers and patients.
                        <SU>38</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>38</SU>
                             Ibid.
                        </P>
                    </FTNT>
                    <P>
                        • “Private equity firms' acquisition and management of health service delivery entities, such as specialty physicians' practices, have been associated with increased cost and diminished quality of care.” 
                        <SU>39</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>39</SU>
                             Cheryl Erwin and Sheryl Tatar Dacso; “When and How Should Patients Be Informed About Clinicians' or Organizations' Sale of a Clinical Practice to a Private Equity Buyer?” May 2025.
                        </P>
                    </FTNT>
                    <P>
                        • “Private equity margin maximization and profit-making strategies focus on acquisition, short-term ownership, and sale of health care entities, including residency program opportunities. PE ownership durations generally have 3 purposes: reduce staff, sell assets, and refinance debt.” 
                        <SU>40</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>40</SU>
                             Mark Varvares, MD, et al.; “Should Private Equity Firms Own Residency Slots?” May 2025.
                        </P>
                    </FTNT>
                    <P>In light of the foregoing, we believe CMS should ascertain the prevalence of PEC and REIT involvement with Medicare Part B suppliers no less than with Part A providers such as SNFs. This is a Medicare-wide issue. Consequently—and like our approach in the November 17, 2023, final rule—we announce our intention to revise the following provider enrollment applications to require all suppliers completing these forms to identify whether any organizations disclosed thereon are PECs or REITs:</P>
                    <P>• Form CMS-855B (Medicare Enrollment Application—Clinics/Group Practices and Certain Other Suppliers; OMB Control No. 0938-1377).</P>
                    <P>• Form CMS-855S (Medicare Enrollment Application—Durable Medical Equipment, Prosthetics, Orthotics, and Supplies (DMEPOS) Suppliers; OMB Control No. 0938-1056).</P>
                    <P>• Form CMS-20134 (Medicare Diabetes Prevention Program (MDPP) Suppliers).</P>
                    <P>We note that we are relying upon sections 1102, 1866(j), and 1871 of the Act (rather than section 1124(c)) as authority for this proposal.</P>
                    <P>As with the November 17, 2023, final rule, our intended form revisions would not involve regulatory changes.</P>
                    <HD SOURCE="HD3">8. Definition of “Operational” (§ 424.502)</HD>
                    <HD SOURCE="HD3">a. Background and Provisions</HD>
                    <P>Per § 424.510(d)(6), a provider must be “operational” to obtain Medicare billing privileges. “Operational” is defined in § 424.502 as meaning the provider meets all of the following:</P>
                    <P>• Has a qualified physical practice location.</P>
                    <P>• Is open to the public for the purpose of providing health care related services.</P>
                    <P>• Is prepared to submit valid Medicare claims.</P>
                    <P>• Is properly staffed, equipped, and stocked (as applicable, based on the type of facility or organization, provider or supplier specialty, or the services or items being rendered) to furnish these items or services.</P>
                    <P>Over the years, we have received numerous queries about the meaning and scope of these requirements, such as “properly staffed”, “properly stocked”, and “open to the public”. For instance, assume a provider has an adequate number of personnel at its site. This could appear to meet the “properly staffed” requirement, but perhaps many of these employees are unqualified for their positions (such as being unlicensed). The question thus becomes whether “properly staffed” refers to the number of employees, the employees' credentials, both, or something else entirely. The term “open to the public,” meanwhile, does not address (1) timeframes in which the provider must be open or (2) physical accessibility to the location. Indeed, it is possible that a provider might, on the surface, meet the letter of the existing “open to the public” criterion by being briefly “open” to the public but not the definition's intent if it is only open 1 hour per day. These issues are important, for the “operational” definition's core purpose is to help confirm that the provider is bona fide. We have, in fact, seen situations where a provider appears to meet the definition but turns out to be a fraudulent operation.</P>
                    <P>Our concerns about the definition are therefore twofold: that it lacks clarity and is too narrow. We believe additional criteria in the definition would better ensure the provider's operational status and legitimacy and assist us in preventing sham providers from entering Medicare. Therefore, we propose the following changes to our definition.</P>
                    <P>
                        First, we propose an opening sentence to the definition that would read “
                        <E T="03">Operational</E>
                         means (as applicable, based on the type of facility or organization, provider or supplier specialty, or the services or items being rendered) the provider or supplier meets all of the following:”. The parenthetical—which is in the current definition—would clarify for stakeholders that: (1) certain components of our revised definition may not apply to all provider types; and (2) CMS would account for this in applying the definition.
                        <PRTPAGE P="41299"/>
                    </P>
                    <P>Second, the previously referenced four bulleted components of the existing definition would be designated as new paragraphs (1) through (4) therein. This would improve the definition's readability. (We are not proposing changes to the first requirement concerning a qualified practice location.)</P>
                    <P>Third, proposed paragraph (2) would explain that the requirement that the provider “[i]s open to the public for the purpose of providing health care related services” includes, but is not limited to, all of the following:</P>
                    <P>• The provider's location is fully accessible to all patients and lacks safety hazards.</P>
                    <P>• The provider's hours of business are sufficient to regularly serve patients.</P>
                    <P>• Medicare beneficiaries can contact and locate the provider's location based on publicly available information (for example, the internet).</P>
                    <P>We believe these three requirements would help verify the provider's compliance with this criterion. In our view, a provider whose location threatens patient safety, is inaccessible to beneficiaries, or cannot be found via public means raises doubts as to whether the location is truly “open.”</P>
                    <P>To assist interested parties in understanding the term “accessible” for purposes of the “operational” definition, proposed paragraph (2)(i) would define it as meaning both of the following:</P>
                    <P>• The provider is located in an area and a building that patients can enter with reasonable ease.</P>
                    <P>• The location is compliant with all Federal Americans with Disabilities Act regulations and all applicable and equivalent State and local laws.</P>
                    <P>These requirements would make clear that providers must—from an accessibility standpoint—accommodate beneficiaries with disabilities and those without. We note that the phrase “located in an area” does not mean the provider's location must be, for instance, within a short drive or a mere 5-mile radius of the beneficiary's home. “Area” in this context would mean the location's immediate vicinity, such as the parking lot or a larger, multi-building complex in which the provider has its office. Also, nothing in the first bullet would prevent the provider from having security locks or security personnel between its office(s) and the building entrance. It instead references the beneficiary's ability to enter the building once access is granted (for instance, security staff signs in the beneficiary and directs the beneficiary to the provider's office).</P>
                    <P>Third, we propose in new paragraph (3) to change “prepared” to “prepared and able”. If the provider lacks the administrative or logistical ability to submit valid claims—even if it may be “prepared” to do so—we do not believe the provider can be considered operational for purposes of Medicare enrollment.</P>
                    <P>Fourth, and similar to proposed paragraph (2), proposed paragraph (4) would include the following additional requirements concerning the “properly staffed, properly equipped. . . .” criterion:</P>
                    <P>• Provider staff must be qualified (such as licensed or certified if required under state law) to perform their health care-related functions.</P>
                    <P>• Equipment must be functional, appropriate for the services and items the provider intends to furnish, and in sufficient quantity to provide these items and services.</P>
                    <P>• Appropriate medications for the services and items the provider intends to furnish and in sufficient quantity to provide these items and services.</P>
                    <P>Each of these three requirements, to some extent, already fall within the existing “properly staffed, properly equipped. . . .” category. To illustrate, we do not believe that a provider with little to no working equipment that is needed to treat beneficiaries—or whose medical equipment has nothing to do with the services the provider plans to furnish—can be considered “properly” equipped under the current “operational” definition. We believe that specifying these three requirements in regulation would help interested parties understand the purview of this criterion.</P>
                    <P>We also maintain, though, that operationality should require more than proposed paragraphs (1) through (4), particularly with respect to administration, safety, and patient care. If, for instance, a provider lacks any written procedures or policies for these and related activities, this can indicate an inefficient, unprepared provider that is not ready to safely treat Medicare patients or to accurately bill Medicare—in short, one that is not genuinely “operational”. Again, we believe the current “operational” definition's narrowness can enable questionable providers to meet it. To thus further strengthen it, we propose in new paragraph (5) that operationality requires the provider to have adequate written policies and records regarding its operations, such as, but not limited to, procedures for patient care, patient safety, medical and patient recordkeeping, and general administration.</P>
                    <HD SOURCE="HD3">b. Additional Considerations</HD>
                    <P>We understand that our clarified and expanded definition may raise concerns about its breadth, applicability, and relationship to other CMS requirements. We wish to address these in advance. As already noted, there are numerous types of providers and suppliers, practice locations, and factual scenarios. Again, therefore, not every requirement in our revised definition would be applicable to every provider or situation. We seek to assure providers that while they must be operational under our proposed definition to enroll in Medicare, we would continue to account for situations where a particular requirement cannot realistically apply to the provider based on its type or circumstances. On the other hand, the reverse could also occur—specifically, the wide variety of provider types and scenarios might at times require us to consider information not addressed in our revised definition in order to determine the provider's operationality. Suppose a case arises where most of the definition's requirements are inapplicable to the provider, but this leaves insufficient remaining criteria for us to determine operational status. We believe we must have the ability to contemplate other information in this and other cases. We hence propose an additional (though un-numerated) paragraph at the end of our revised definition stating that CMS may consider any information in determining whether the provider is operational.</P>
                    <P>Proposed paragraph (2)—including the term “regularly” therein—does not establish an across-the-board, minimum hour requirement for providers to be open for business (for example, Provider X must be open 50 hours a week to be considered “operational”). Our determination as to whether the provider meets paragraph (2) would, as presently, be made on a case-by-case basis.</P>
                    <P>
                        Perhaps most importantly, our expanded definition would not—and is not intended to—supplant or supersede existing conditions of participation, conditions for coverage, certified provider or supplier survey or accreditation procedures, DMEPOS supplier and quality standards, and other provider or supplier-specific requirements (such as IDTF standards in § 410.33(g) and OTP conditions in § 424.67(b) and (e)). “Operational” status for purposes of provider enrollment is, and has always been, an entirely separate and distinct requirement, which the provider must meet along with all others needed for enrollment.
                        <PRTPAGE P="41300"/>
                    </P>
                    <HD SOURCE="HD3">9. Signage (§ 424.510(f))</HD>
                    <P>Sections 424.57(c)(7)(i)(D) and 410.33(g)(14)(ii) require DMEPOS suppliers and IDTFs, respectively, to maintain a visible sign posting its normal business hours. The former adds that if the supplier's place of business is located within a building complex, the sign must be visible at the main entrance of the building (or the hours can be posted at the entrance of the supplier). We propose in new § 424.510(f) to expand this requirement to include all providers and suppliers; § 424.510(f) would mirror the current language of § 424.57(c)(7)(i)(D). This would assist beneficiaries and site visit personnel in locating the provider's business, something that has occasionally proven difficult because the location contains no signage. To ensure consistency, we would also revise § 410.33(g)(14)(ii) to duplicate the language in proposed § 424.510(f).</P>
                    <P>Consistent with our proposed revisions to the definition of “operational” definition; however, § 424.510(f) is not intended to supersede any other Medicare requirements regarding signage. Section 424.510(f) is strictly an enrollment requirement. In addition, we recognize that our proposed signage requirement may not be practicable in all circumstances. This could be due to, for instance, the type of provider involved, its particular business circumstances, etc. Thus, we propose the following exceptions to the signage requirement:</P>
                    <P>• The provider shares office space with another provider (for example, physicians in a group practice sharing a common suite, though the group itself must have signage).</P>
                    <P>• The provider treats patients in the patients' homes.</P>
                    <P>• The provider treats patients in the provider's home and only uses the provider's address for administrative purposes.</P>
                    <P>• The provider performs telehealth services from home.</P>
                    <HD SOURCE="HD3">10. Retention and Furnishing of Documentation (§ 424.516)</HD>
                    <P>We explained previously that under § 424.516(f)(1), providers and suppliers that furnish covered ordered, certified, referred, or prescribed Part A or B services, items or drugs are required to:</P>
                    <P>• Maintain the documentation described in § 424.516(f)(1)(ii) for 7 years from the date of service; and</P>
                    <P>• Upon CMS' or a Medicare contractor's request, provide access to that documentation.</P>
                    <P>The documentation described in § 424.516(f)(1)(ii) includes written and electronic documents (including the NPI of the physician or, when permitted, other eligible professional who ordered, certified, referred, or prescribed the Part A or B service, item, or drug) relating to written orders, certifications, referrals, prescriptions, and requests for payments for Part A or B services, items or drugs.</P>
                    <P>Section 424.516(f)(2) contains a similar documentation retention and submission requirement for physicians (or, when permitted, eligible professionals) who order, certify, refer, or prescribe Part A or B services, items or drugs. In addition, § 424.516(a)(10) permits revocation if the provider or supplier fails to comply with § 424.516(f) documentation and CMS access requirements. Section 424.516(f) helps CMS determine, for instance, whether the service was reasonable and necessary, whether fraud, waste, or abuse is involved, and whether the provider is compliant with Medicare requirements.</P>
                    <P>We propose to add new § 424.516(f)(3) clarifying that all documentation required to be retained and furnished under § 424.516(f) must be accurate, complete, and compliant with all CMS requirements. In our documentation reviews, we have seen: (1) patient charts missing medical director signatures; (2) hospice certifications signed before the face-to-face encounter; (3) certification end dates preceding the certification start dates; and (4) other types of inaccurate records. This makes it difficult for CMS and its contractors to verify the provider's adherence and the service's necessity; the program integrity benefits of § 424.516(f) are greatly reduced if the documentation is inaccurate or non-compliant. We accordingly believe § 424.516(f)(3) is necessary. However, we emphasize that our proposal is not intended to establish any new condition of payment. It would be restricted to the scope of the documents addressed in § 424.516(f).</P>
                    <HD SOURCE="HD3">11. Managing Employees (§ 424.502)</HD>
                    <P>The term “managing employee” is defined in § 424.502. It means, in part, a general manager, business manager, administrator, director, or other individual who exercises operational or managerial control over, or who directly or indirectly conducts, the day-to-day operation of the provider. Managing employees have long been required to be disclosed on the provider's Medicare enrollment application. Since, as stated, managing employees sometimes have as much or more influence over a provider's daily operations as an owner, we must know whether such persons present risks to the Trust Funds.</P>
                    <P>Yet the risks are not merely financial. We have repeatedly noted over the years our obligation to protect the health and safety of Medicare beneficiaries. The provider enrollment process has assisted in this regard by collecting information on certain medical professionals within a provider organization. This includes, for example: (1) IDTF supervising physicians, interpreting physicians, and technicians; (2) ordering OTP personnel; and (3) hospice and SNF medical directors. The purpose is to ensure that such persons not only pose no payment safeguard threats but also are qualified for their roles (such as meeting State licensure requirements). Unqualified or unvetted medical personnel can harm Medicare patients.</P>
                    <P>So great is our concern about this matter that we believe additional clinical parties should be disclosed on the provider enrollment application. We hence propose to expand upon our aforementioned inclusion of hospice and SNF medical directors within the “managing employee” definition. The following persons would be added:</P>
                    <FP SOURCE="FP-1">• Medical directors (not merely those at SNFs and hospices)</FP>
                    <FP SOURCE="FP-1">• Clinical directors</FP>
                    <FP SOURCE="FP-1">• Departmental heads (for example, a hospital's chief of cardiology)</FP>
                    <FP SOURCE="FP-1">• Supervising physicians (not simply those at IDTFs)</FP>
                    <FP SOURCE="FP-1">• Nursing directors</FP>
                    <FP SOURCE="FP-1">• Alternate administrators</FP>
                    <FP SOURCE="FP-1">• All other clinical personnel that meet the “managing employee” definition.</FP>
                    <P>
                        We note four things. First, these categories apply to all provider and supplier types, including SNFs and hospices. Second, we believe the persons in these categories already qualify as “managing employees” and should have always been reported. They clearly have direct or indirect control of the provider's day-to-day operations, and the fact that they are clinical personnel (rather than administrative) is irrelevant for purposes of determining whether a person is a managing employee. Our inclusion of them within the “managing employee” definition is, in large part, a reminder to stakeholders that clinical staff must be disclosed if the definition is met. Third, these seven new bulleted categories do not establish any minimum threshold for disclosure; for example, even if an individual has less influence than a departmental head, the person must still be reported as long as the managing employee definition is met. Fourth, and on the other hand, this does not mean that every clinical employee regardless of influence must be reported. Disclosure is only required if the person is a managing employee.
                        <PRTPAGE P="41301"/>
                    </P>
                    <HD SOURCE="HD3">12. Corrective Action Plans (CAPs), Rebuttals, and Appeals</HD>
                    <P>In certain situations, a provider or supplier may have an opportunity to correct a deficiency or contest a CMS finding regarding its enrollment by submitting, as applicable: (1) a CAP in response to a §§ 424.530(a)(1) or 424.535(a)(1) denial or revocation, respectively; (2) a rebuttal to a stay or deactivation of enrollment under §§ 424.541 or 424.546, respectively; or (3) an appeal of an initial determination under 42 CFR 498.3. We propose several revisions to these processes.</P>
                    <HD SOURCE="HD3">a. CAPs (§ 405.809)</HD>
                    <P>Sections 424.530(a)(1) and 424.535(a)(1) permit CMS to deny or revoke enrollment, respectively, if the provider is not compliant with the enrollment requirements in Title 42 or in the enrollment application applicable for its provider type. The provider may submit a CAP in response to this denial or revocation, which allows the provider to remedy the deficiency or deficiencies in question and achieve compliance. As has long been CMS practice, though, §§ 424.530(a)(1) and 424.535(a)(1) are the only denial or revocation reasons under §§ 424.530 and 424.535 for which the provider may submit a CAP. While § 405.809(a)(1) makes this clear with respect to § 424.535(a)(1), it is silent as to § 424.530(a)(1). To incorporate this CAP policy into regulation, we propose to add § 424.530(a)(1) denials to § 405.809's purview. This would involve the following revisions:</P>
                    <P>• Section 405.809's title would change from “Reinstatement of provider or supplier billing privileges following corrective action” to “Granting or reinstatement of provider or supplier billing privileges following corrective action.”</P>
                    <P>• In paragraph (a)(1), the language “revocation for noncompliance under § 424.530(a)(1)” would change to “denial or revocation for non-compliance under § 424.530(a)(1) or § 424.535(a)(1)”.</P>
                    <P>• In paragraph (a)(2), “revocation” would change to “denial or revocation”.</P>
                    <P>• In paragraph (b)(1), “Reinstates” would change to “Approves or reinstates”.</P>
                    <P>• Paragraph (b)(1)(i) would be redesignated as paragraph (b)(1)(i)(B).</P>
                    <P>• Under new paragraph (b)(1)(i)(A), the effective date of the approval is based on the applicable timeframes described in §§ 424.520 and 424.521. This is consistent with existing practice.</P>
                    <P>• In paragraph (b)(1)(ii), “reinstatement” would change to “approval or reinstatement”.</P>
                    <P>• In paragraph (b)(2), “reinstate” would change to “approve or reinstate”.</P>
                    <HD SOURCE="HD3">b. Notification of Determinations</HD>
                    <P>Section 498.3(b) lists several CMS or MAC provider enrollment decisions that are considered “initial determinations”. These include, for example, enrollment denials, enrollment revocations, and inclusion of a provider on the preclusion list. The affected provider under § 498.5 may request a reconsideration of the initial determination, for which CMS or, if applicable, the MAC issues a reconsideration determination. Under §§ 498.20(a)(1) and 498.25(a)(1), CMS mails notice of the initial determination or reconsidered determination, respectively, to the provider. Furthermore, §§ 405.800 requires that denial and revocation notices (as well as notice regarding the addition of years to a reenrollment bar) be sent by certified mail. We propose to revise §§ 405.800(a), (b)(1), and (c)(1), 498.20(a)(1) and 498.25(a)(1) to include email as an acceptable form of notice. We believe this would facilitate faster notice to the provider without the expense of paper mailing.</P>
                    <HD SOURCE="HD3">c. Appeals of Reactivation Effective Dates</HD>
                    <P>Along with listing types of initial determinations, paragraph (d) of § 498.3 outlines administrative actions that are not initial determinations and thus not appealable under part 498. One type of provider enrollment finding that is not mentioned in either § 498.3(b) or (d) is the effective date of a reactivation under § 424.540(b). Under § 424.540(d)(2), a reactivation effective date is the date on which the Medicare contractor received the provider's reactivation submission that the Medicare contractor processed to approval. Due to lack of clarity among some stakeholders as to whether an assigned reactivation effective date may be appealed or rebutted, we propose several regulatory changes.</P>
                    <P>First, we propose to add new paragraph (3) to § 424.540(d) stating that a provider or supplier may rebut their assigned reactivation effective date via the general deactivation rebuttal procedures in § 424.546. As deactivations are not considered initial determinations—and to ensure consistent approaches—we do not believe reactivation effective dates should, either. Yet we also believe the provider should have an opportunity to be heard on the matter, and a rebuttal would provide that.</P>
                    <P>To accommodate reactivation effective date rebuttals within § 424.546, we also propose to revise the latter as follows:</P>
                    <P>• Change the title from “Deactivation rebuttals” to “Rebuttals of deactivations and of reactivation effective dates”.</P>
                    <P>• In paragraph (a)(1), insert the following between “under § 424.540,” and “the provider or supplier has 15 calendar days”: “or is assigned a reactivation effective date by CMS or its contractor under § 424.540(d)(2),”.</P>
                    <P>• In paragraph (b)(2), insert the following between “effective date,” and “and the reasons”: “(or with the assigned reactivation effective date)”.</P>
                    <P>• In paragraph (b)(3), insert the following after “deactivation”: “or the reactivation effective date”.</P>
                    <P>• Delete existing paragraph (d) and replace with the following: “Upon receipt of a timely and compliant deactivation (or reactivation effective date) rebuttal, CMS reviews the rebuttal to determine whether the imposition of the deactivation and/or the designated effective date (or the assigned reactivation effective date) are correct.”</P>
                    <P>In this vein, we would also revise § 424.545(b) to include assignments of reactivation effective dates as a ground for rebuttal.</P>
                    <HD SOURCE="HD3">13. Fingerprinting (§ 424.518(c))</HD>
                    <P>Section 424.518(c)(2)(ii)(A) states that 5 percent or greater individual owners of providers and suppliers in the “high” screening category must submit fingerprints for a national criminal background check. We propose to revise this paragraph to clarify that individuals subject to fingerprinting must use the CMS-designated fingerprinting contractor for this task. This would: (1) facilitate consistency in the fingerprinting process; and (2) inform individuals as to which fingerprinting entity to use, a matter that has caused some uncertainty in the provider community.</P>
                    <HD SOURCE="HD3">14. DMEPOS Accreditation (§ 424.58)</HD>
                    <P>
                        Consistent with §§ 424.57(c)(22) and 424.58, DMEPOS suppliers must be accredited by a CMS-approved accrediting organization (AO) to enroll and remained enrolled in Medicare. Section 424.58 details the general procedures and policies associated with DMEPOS accreditation. Many of these were added to § 424.58 in the CY 2026 HH PPS final rule (90 FR 55342) in an effort to strengthen CMS' oversight of the DMEPOS accreditation program in general and the DMEPOS AOs in particular. This included requirements regarding information and agreements that AOs must submit to CMS as part of their application/reapplication process. 
                        <PRTPAGE P="41302"/>
                        Three of these requirements are as follows:
                    </P>
                    <P>• Per § 424.58(c)(1)(xxiii)(D), agreeing to notify CMS in writing of any decision to terminate, revoke, withdraw, or amend the accreditation status of a specific DMEPOS supplier within 3 business days of the date the AO took action.</P>
                    <P>• Per § 424.58(c)(1)(xxii), describing the AO's processes for—</P>
                    <P>++ Detecting and addressing DMEPOS supplier fraud, waste, and abuse (including identifying the AO's definitions of fraud, waste, and abuse); and</P>
                    <P>++ Reporting this activity to CMS and, as applicable, law enforcement.</P>
                    <P>• Per § 424.58(c)(1)(vii)(D), outlining the AO's policies and procedures for avoiding conflicts of interest and the appearance thereof involving individuals who conduct surveys or participate in accreditation decisions.</P>
                    <P>Upon further reflection since these three provisions were promulgated, we propose the following changes.</P>
                    <P>One revision would change the 3-business day period in § 424.58(c)(1)(xxiii)(D) to 5 calendar days. This would better align with § 424.58(e)(5)(i), which requires approved AOs to report the same information to CMS within 5 calendar days. Having two different timeframes for reporting similar data has led to some confusion.</P>
                    <P>In addition, there currently is no timeframe in § 424.58 for reporting the fraud, waste, and abuse described § 424.58(c)(1)(xxii). We propose in new § 424.58(c)(1)(xxiii)(N) that the AO must agree to notify CMS in writing (and, if applicable, law enforcement) of suspected fraud, waste, and abuse—consistent with the AO's CMS-approved definitions of those terms—within 3 calendar days of the date on which the AO determines that fraud, waste, or abuse may have occurred. (Current § 424.58(c)(1)(xxiii)(N) would be redesigned as new § 424.58(c)(1)(xxiii)(O)). Given the seriousness of such conduct and the current lack of a reporting timeframe § 424.58, we believe a 3-calendar day requirement is warranted.</P>
                    <P>
                        Notwithstanding the provisions of § 424.58(c)(1)(vii)(D) regarding conflicts of interest, none of them actually require the AO to report in its application/reapplication whether it has such conflicts. To help ensure that CMS makes fully informed AO approval decisions, we propose to revise § 424.58(c)(1)(vii)(D)(
                        <E T="03">4</E>
                        ) to require the AO to also disclose to CMS all conflicts of interest (as described in § 424.58(c)(1)(vii)(D)(
                        <E T="03">3</E>
                        )) it currently has and explain how and when it will terminate them.
                    </P>
                    <HD SOURCE="HD3">15. Affiliations</HD>
                    <P>As indicated previously, and consistent with section 1866(j)(5) of the Act, § 424.519 states that upon a CMS request, an initially enrolling or revalidating provider or supplier (hereafter collectively “provider” unless otherwise noted) must disclose any and all affiliations that it or any of its owning or managing employees or organizations (per § 424.502's definitions of “owner” and “managing employee”) has or, within the previous 5 years, had with a currently or formerly enrolled Medicare, Medicaid, or CHIP provider that has a disclosable event (as defined in § 424.502). If CMS determines that the affiliation poses an undue risk of fraud, waste, or abuse, CMS may deny or revoke the provider's enrollment under §§ 424.530(a)(13) or § 424.535(a)(19), respectively.</P>
                    <P>Section 424.502 describes a disclosable event as any of the following: (1) a current uncollected debt to Medicare, Medicaid, or CHIP; (2) a payment suspension under a federal health care program; (3) an OIG exclusion; or (4) a denial, revocation or termination of a Medicare, Medicaid, or Children's Health Insurance Program enrollment.</P>
                    <P>For purposes of § 424.519, an “affiliation” under § 424.502 includes any of the following (outlined in paragraphs (1) through (5) of the “affiliation” definition, respectively):</P>
                    <P>• A 5 percent or greater direct or indirect ownership interest that an individual or entity has in another organization.</P>
                    <P>• A general or limited partnership interest (regardless of the percentage) that an individual or entity has in another organization.</P>
                    <P>• An interest in which an individual or entity exercises operational or managerial control over, or directly or indirectly conducts, the day-to-day operations of another organization (including sole proprietorships)—either under contract or through some other arrangement, regardless of whether or not the managing individual or entity is a W-2 employee of the organization.</P>
                    <P>• An interest in which an individual is acting as an officer or director of a corporation.</P>
                    <P>• Any reassignment relationship under § 424.80.</P>
                    <P>
                        These provisions were established via regulation in a final rule published in the 
                        <E T="04">Federal Register</E>
                         on September 10, 2019 (84 FR 47794).
                        <SU>41</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>41</SU>
                             “Medicare, Medicaid, and Children's Health Insurance Programs; Program Integrity Enhancements to the Provider Enrollment Process.”
                        </P>
                    </FTNT>
                    <P>Since establishing the affiliation regulations, CMS has emphasized identifying current and past relationships between and among different providers and suppliers and, if an undue risk exists, denying or revoking the applicable provider(s). This helps protect the Trust Funds and beneficiaries from threats that certain provider associations can pose. Nevertheless, we have found three issues in § 424.519 that we believe hinder the provision's effectiveness.</P>
                    <P>One involves the aforementioned 5-year lookback period. We have seen situations where a relationship from more than 5 years ago still presents an undue risk of fraud, waste, abuse. In not requiring disclosure of these affiliations—and, in turn, being unable to deny or revoke enrollment under §§ 424.530(a)(13) or 424.535(a)(19)—we are effectively permitting a potentially significant fraud, waste, or abuse risk to remain. This is antithetical to our duty to protect the Medicare program.</P>
                    <P>The second pertains to the “affiliation” definition in § 424.502. While it covers several types of associations, there are other conceivably problematic relationships we have encountered in our program integrity efforts. Consider these hypotheticals:</P>
                    <P>• An individual or entity operates a small building with over 30 HHAs and hospices that list the building address as their practice location. Considering our earlier discussion of the high payment safeguard risk in such situations, the building operator might be involved with these providers in some type of fraud scheme.</P>
                    <P>• Based on CMS data, five physicians in a known geographic hotspot for fraud appear to be the primary physician for the same beneficiary, raising questions as to whether these doctors are sharing patients for improper purposes.</P>
                    <P>• A provider had a relationship with a financial services company that had several high-level officials convicted of fraudulent activity.</P>
                    <P>• A provider hired Marketing Firm X. X had solicited beneficiaries for four DMEPOS suppliers, all of which were later revoked with a 10-year reenrollment bar.</P>
                    <P>
                        These and other scenarios demonstrate that numerous associations beyond those listed in the “affiliation” definition can endanger the Medicare program, for nefarious parties of all types constantly seek new means of perpetuating Medicare fraud.
                        <PRTPAGE P="41303"/>
                    </P>
                    <P>The third issue also involves the “affiliation” definition, though on a narrower level—specifically, paragraph (3) thereof. As noted, paragraph (3) addresses relationships where an individual or entity has operational or managerial control over (or directly or indirectly conducts) the day-to-day operations of another organization. (This mirrors our current definitions of “managing employee” and “managing organization in § 424.502.) A recent situation arose where an individual was a medical director (Dr. A) of two providers—B and C. C was revoked from Medicare. Since a medical director is a managing employee under § 424.502, B was revoked under § 424.535(a)(19) consistent with paragraph (3) of the affiliation definition; that is, Dr. X was an individual with operational or managerial control over another entity—Providers B and C. This established the affiliation between B and C, with Dr. X as the clear link—a view that aligns not only with our longstanding interpretation of paragraph (3) but also with section 1866(j)(5) of the Act. Moreover, we believe our position helps ensure the usefulness of section 1866(j)(5) of the Act. A provider generally acts through its owners, managers, and other personnel. If we applied paragraph (3) only to situations where a provider operates or manages another provider, we would be unable to address other cases where the real fraud, waste, and abuse risk is posed by parties affiliated with both providers. In other words, we need the ability to go within the provider organization to the operators and managers to address threats they present.</P>
                    <P>With all three issues, we believe the fraud, waste, and abuse risk itself is much more important than when the relationship triggering the risk occurred, whether the provider entity poses the risk or, instead, the managing employee, etc. Accordingly, we propose the following revisions to our affiliation provisions in part 424, subpart P:</P>
                    <P>• We propose to remove the 5-year period from § 424.519(b). So long as the requirements for disclosure are otherwise met, the affiliation would have to be reported regardless of how long ago it occurred or ended.</P>
                    <P>• We propose to add new paragraph (6) to the “affiliation” definition. Consistent with the second issue, this paragraph would include any marketing, business, fulfillment, financial, managerial, or beneficiary relationship. (The “managerial” relationships in paragraph (6) would be those not otherwise falling within paragraph (3) of the “affiliation” definition.)</P>
                    <P>• To reiterate the scope of our affiliation provisions (per our interpretation of the aforementioned paragraph (3)), we propose to do the following:</P>
                    <P>++ In paragraph (3), insert the following language between “individual or entity,” and “exercises operational”: “or any of its owning or managing employees or organizations,”.</P>
                    <P>++ In §§ 424.530(a)(13) and § 424.535(a)(19), insert the following language between “provider or supplier” and “has or has had”: “or any of its owning or managing employees or organizations,”.</P>
                    <HD SOURCE="HD3">16. Savings, Costs, and Other Impacts Concerning the Provider Enrollment Provisions</HD>
                    <HD SOURCE="HD3">a. Monetary Effects</HD>
                    <P>As explained in the RIA section of this proposed rule, we project annual savings from our proposed enrollment provisions of approximately $82 million. This would stem from our expansion of retroactive revocation grounds. Additional savings could accrue from several proposed new and expanded revocation reasons; however, we are unable to devise an estimate because we cannot predict how frequently these authorities would be utilized.</P>
                    <P>Per our discussion in the ICR section of this proposed rule, we do not anticipate any ICR costs stemming from our proposed provisions. Yet we project approximately $1.4 million in annual survey or accreditation costs due to our revision to § 424.540(b)(3).</P>
                    <HD SOURCE="HD3">b. Additional Impacts</HD>
                    <P>The following discusses other possible impacts of our most prominent proposals.</P>
                    <HD SOURCE="HD3">(1) New and Expanded Grounds for Revocation or Denial</HD>
                    <P>We do not anticipate a significant impact on providers, suppliers, or beneficiaries resulting from our proposed denial and revocation grounds. We have in numerous past rules proposed and finalized new denial/revocation reasons with no real effect on the universe of enrolled providers or on the availability of health care. Only a very small percentage of providers (roughly 3 percent, though this can vary somewhat) are revoked at least once during their Medicare enrollment, leaving well over 2 million enrolled providers able to continue furnishing services. Too, we do not anticipate a substantial increase in the number of denials and revocations stemming from our proposals; as we have repeatedly stated in prior rules, we only take denial/revocation action when appropriate and not as a matter of course.</P>
                    <HD SOURCE="HD3">(2) Retroactive Revocation Reasons</HD>
                    <P>We recognize that some revoked providers and suppliers would be impacted by our expansion of retroactive revocation effective date provisions. The $82 million in aforementioned savings might otherwise be paid to these providers if the prospective effective date were retained. Again, though, revocations are infrequent, and the annual number of affected providers would—as explained in this proposed rule's RIA—be estimated at a mere 337 out of the 2 million-plus provider universe. The overall impact would therefore be quite limited, and health care availability would remain robust. Indeed, we also expanded the number of retroactive revocation effective dates in the CY 2026 HH PPS final rule (90 FR 55342), projecting savings of nearly $2.2 billion resulting from 1,442 annual revocations that would have new retroactive effective dates. However, this did not cause a material impact on the provider community or beneficiaries.</P>
                    <P>Perhaps the largest impact of our denial, revocation, and retroactive revocation proposals would be on the Trust Funds and, by extension, the American taxpayers via the saving of monies that should not have been paid to these providers due to their non-compliance with enrollment requirements.</P>
                    <HD SOURCE="HD3">(3) Reapplication Bar</HD>
                    <P>While we are proposing to expand our bases for a reapplication bar to include any denial reason, reapplication bars would remain discretionary, meaning that not every denial would necessarily invoke said bar. Moreover, many providers would remain ineligible to enroll in Medicare long after the denial with or without a reapplication bar; this is because they would still not meet Medicare requirements. We hence do not foresee an appreciable impact on providers, suppliers, or beneficiaries from this proposal, as there would be little change in the number of enrolled and qualified providers.</P>
                    <HD SOURCE="HD3">(4) Temporary Moratoria</HD>
                    <P>
                        We do not expect a notable impact on providers and beneficiaries from our temporary moratoria modifications. Moratoria are rare (even with our three aforementioned current moratoria) and typically limited to certain provider types and, between 2013 and 2019, geographic regions. They also do not apply to currently enrolled providers 
                        <PRTPAGE P="41304"/>
                        and suppliers but only to new enrollments. In addition, our changes to § 424.570 would be very restricted in scope. Healthcare access should thus remain unaffected.
                    </P>
                    <HD SOURCE="HD3">(5) Hospice Reactivations</HD>
                    <P>As discussed in more detail in the RIA, we project that only 226 hospices would be affected by our proposal that they must undergo a State survey or accreditation prior to reactivation. Given this very small number, we do not foresee this proposal having a substantial impact on hospices or beneficiaries.</P>
                    <HD SOURCE="HD3">(6) Expansion of “Operational” and “Managing Employee” Definitions, Signage, and Documentation Accuracy</HD>
                    <P>We do not believe these proposals would have a material impact on providers or beneficiaries. In our experience, many providers likely: (1) meet the parameters of our proposed expanded “operational” definition and signage requirements; and (2) retain documentation under § 424.516(f) that is accurate and complete. We also previously noted that providers and suppliers should already be reporting the seven categories of individuals in our proposed “managing employee” definition expansion. Health care access should thus remain strong notwithstanding these proposals.</P>
                    <HD SOURCE="HD2">E. DME Benefit Expansion for Infusion Pumps and Drugs</HD>
                    <HD SOURCE="HD3">1. Background</HD>
                    <HD SOURCE="HD3">a. Home Infusion Therapy Benefit</HD>
                    <P>
                        In section 5012 of the 21st Century Cures Act (Pub. L. 114-255), Congress amended section 1861(s)(2) of the Act and added sections 1834(u) and 1861(iii) of the Act to establish a new Medicare home infusion therapy benefit effective January 1, 2021. This benefit covers certain professional services associated with the provision of home infusion therapy to a beneficiary who is under the care of a physician, nurse practitioner, or physician assistant. Home infusion therapy involves the intravenous or subcutaneous administration of drugs or biologicals to an individual at home through an external infusion pump. As indicated in a final rule, we published in the 
                        <E T="04">Federal Register</E>
                         on November 8, 2019, titled “Medicare and Medicaid Programs; CY 2020 Home Health Prospective Payment System Rate Update; Home Health Value-Based Purchasing Model; Home Health Quality Reporting Requirements; and Home Infusion Therapy Requirements,” the external infusion pump and other supplies, including home infusion drugs, necessary for the effective use of the pump are covered under the Part B DME benefit rather than the home infusion therapy benefit (84 FR 60612). Pursuant to section 1861(iii) of the Act, we published a final rule in the 
                        <E T="04">Federal Register</E>
                         on November 13, 2018, titled “Medicare and Medicaid Programs; CY 2019 Home Health Prospective Payment System Rate Update and CY 2020 Case-Mix Adjustment Methodology Refinements; Home Health Value-Based Purchasing Model; Home Health Quality Reporting Requirements; Home Infusion Therapy Requirements; and Training Requirements for Surveyors of National Accrediting Organizations” (83 FR 56406) to define the scope of “home infusion therapy,” “home,” “qualified home infusion therapy supplier,” and “home infusion drug” at 42 CFR 486 Subpart I.
                    </P>
                    <P>Section 486.525(a) implements the definition of “home infusion therapy” set forth at section 1861(iii)(1) of the Act, defining the term to include professional services, including nursing services, furnished in accordance with the plan of care described under 42 CFR 486.520, patient training and education (not otherwise paid for as DME), remote monitoring and monitoring services for the provision of home infusion therapy services and home infusion drugs furnished by a qualified home infusion therapy supplier in the individual's home. Section 486.505 implements the definition of “home” set forth at section 1861(iii)(3)(B) of the Act, defining the term as a place of residence used as the home of an individual, including an institution that is used as a home. An institution that is used as a home may not be a hospital, critical access hospital (CAH), or skilled nursing facility (SNF) as defined in section 1861(e)(1), 1861(mm)(1), or 1819(a)(1) of the Act, respectively.</P>
                    <P>Section 486.505 implements the definition of “qualified home infusion therapy supplier” set forth at section 1861(iii)(3)(D)(i) of the Act, defining the term to mean a supplier of home infusion therapy that meets all of the following criteria which are set forth at section 1861(iii)(3)(D)(i) of the Act: (1) furnishes infusion therapy to individuals with acute or chronic conditions requiring administration of home infusion drugs; (2) ensures the safe and effective provision and administration of home infusion therapy on a 7-day-a-week, 24-hour-a-day basis; (3) is accredited by an organization designated by the Secretary in accordance with section 1834(u)(5) of the Act; and (4) meets such other requirements as the Secretary determines appropriate. A qualified home infusion therapy supplier may subcontract with a pharmacy, physician, provider of services, or supplier to meet these requirements.</P>
                    <P>Section 486.505 implements the definition of “home infusion drug” set forth at section 1861(iii)(3)(C) of the Act, currently defining the term as a parenteral drug or biological administered intravenously, or subcutaneously for an administration period of 15 minutes or more, in the home of an individual through a pump that is an item of DME, excluding insulin pump systems and self-administered drugs or biologicals on a self-administered drug exclusion list.</P>
                    <HD SOURCE="HD3">b. Durable Medical Equipment Benefit</HD>
                    <P>Under the Medicare Part B benefit for DME, a limited number of home infusion drugs (as defined under 42 CFR 486.505) are covered if it is determined that it is medically necessary to use an external infusion pump classified as DME for administration of the home infusion drug, and the home infusion drug being used with the pump is, itself, reasonable and necessary for the treatment of an illness or injury (84 FR 60612).</P>
                    <P>For an external infusion pump and associated supplies to be covered under the Part B DME benefit, the pump must, among other statutory and regulatory requirements, be “appropriate for use in the home” (see 42 CFR 414.202). This requirement means that the equipment must be capable of being safely and effectively used by the beneficiary or caregiver in the home without the assistance of a healthcare professional (84 FR 60628). As noted previously, section 1861(iii)(3)(C) of the Act limits the home infusion therapy benefit to drugs administered in the patient's home through a pump covered under the DME benefit as defined under section 1861(n) of the Act. Therefore, historically, external infusion pumps and associated home infusion drugs that do not meet the “appropriate for use in the home” requirement have not been eligible for coverage under the DME benefit and services associated with administering the home infusion have not been covered under the Part B home infusion therapy benefit.</P>
                    <HD SOURCE="HD3">2. Current Issues</HD>
                    <P>
                        Section 6222(a) of the Consolidated Appropriations Act, 2026 (CAA, 2026) (Pub. L. 119-75) amended section 1861(n) of the Act to expand the scope of the Medicare Part B benefit for DME to include certain external infusion pumps and associated home infusion drugs (as defined in section 
                        <PRTPAGE P="41305"/>
                        1861(iii)(3)(C) of the Act) or other associated supplies that would not otherwise qualify as DME because the use of such device would not meet the “appropriate for use in the home” requirement applied to the DME definition at 42 CFR 414.202. As stated in section V.E.1. of this proposed rule, CMS has historically interpreted the requirement that DMEPOS must be “appropriate for use in the home” to mean that the equipment must be capable of being safely and effectively used by the beneficiary or caregiver in the home without the assistance of a healthcare professional.
                    </P>
                    <P>Effective for items furnished on or after April 1, 2027, section 6222(a) of the CAA, 2026, states an external infusion pump and associated home infusion drug (as defined in section 1861 (iii)(3)(C) of the Act) or other associated supplies that do not meet the appropriate for use in the home requirement applied to the definition of DME under 42 CFR 414.202 (or any successor to such regulation) shall be treated as meeting such requirement if each of the following criteria is satisfied:—</P>
                    <P>• The prescribing information approved by the FDA for the home infusion drug associated with the pump instructs that the drug should be administered by or under the supervision of a health care professional;</P>
                    <P>• A qualified home infusion therapy supplier, as defined in section 1861(iii)(3)(D) of the Act, administers or supervises the administration of the drug or biological in a safe and effective manner in the patient's home, as defined in section 1861(iii)(3)(B) of the Act; and</P>
                    <P>• The FDA-approved prescribing information instructs that the home infusion drug be infused at least 12 times per year:</P>
                    <P>++ Intravenously or subcutaneously; or</P>
                    <P>++ Infusion rates that the Secretary determines would require the use of an external infusion pump.</P>
                    <P>Section 6222(a) of the CAA, 2026 does not define the term “health care professional”. We propose that the term “health care professional” would refer to any of the following clinicians, provided that such clinician is permitted to administer or supervise the administration of a home infusion drug in accordance with Federal and State law: physician (as defined in section 1861(r) of the Act); a clinical nurse specialist, nurse practitioner, or a physician assistant (as such terms are defined in section 1861(aa)(5) of the Act and regulations at 42 CFR 410.74 through 410.76); or a registered nurse otherwise licensed to practice nursing in the State in which the home infusion drug is administered. To ensure consistency across the Medicare program, we propose to define physician, clinical nurse specialist, nurse practitioner, and physician assistant as such terms are defined under the Medicare home health benefit. Given that sections 1861(r) and (aa)(5) of the Act (as codified at 42 CFR 410.74 through 410.76) do not define “registered nurse”, we propose to define “registered nurse” as a clinician licensed to practice nursing in the State in which the home infusion drug is administered.</P>
                    <P>Because of the risks associated with administering certain home infusion drugs in the home under the expanded DME benefit, we propose limiting the definition of “health care professional” to these practitioners. We are aware of at least one drug, patisiran, that presents heighted safety risks and that may meet the new criteria and definition of home infusion drug under the revised definition of DME at section 1861(n) of the Act. In accordance with the prescribing information for the drug patisiran, adverse reactions during clinical trials included upper respiratory tract infections as well as infusion-related reaction symptoms including dizziness, headaches, chest pain, and other symptoms. Four serious adverse reactions of atrioventricular (AV) heart block (2.7 percent) occurred in patients treated with patisiran, including three cases of complete AV block. Warnings and precautions regarding infusion-related reactions under the highlights of prescribing information include the need to monitor for signs and symptoms of reactions during infusion, slow or interrupt the infusion if clinically indicated, and discontinue the infusion if a serious or life-threatening infusion-related reaction occurs. Infusion-related reactions for other home infusion drugs that may be covered under the expansion of the DME benefit could be even more serious and require emergency medical assistance in certain situations. Based on our review, we believe that such safety concerns may be adequately monitored and mitigated if either a physician, clinical nurse specialist, nurse practitioner, physician assistant, or registered nurse administers or supervises the administration of the home infusion drug. We believe any of these clinicians, if available on hand, could address any emergency medical events that occur during the course of the infusion of the drug. We are soliciting comments on this proposal, including whether there are other clinicians that may be equally qualified to administer or supervise the infusions of the drugs in the home and also address any emergency medical events that occur during the course of the infusion of the drug.</P>
                    <P>Note, we are not proposing that the term “health care professional” be defined to include a licensed practical nurse (LPN) or licensed vocational nurse (LVN) under the supervision of a registered nurse or physician. State law varies in terms of whether an LPN or LVN can perform certain emergency services such as delivering emergency medications. Thus, it is not clear that addressing the adverse affects associated with the administration of certain home infusion drugs would consistently fall under an LPN's or LVN's scope of practice. Additionally, as LPNs and LVNs practice under supervision without the same level of independent clinical authority as the professionals identified above, we believe they are less suited to serve as a health care professional for administering complex home infusion drugs under the expanded Medicare DME benefit. In addition, we do not believe that supervising the administration of the drug in the home should be done remotely as this could violate state laws and compromise the safety of the home infusion therapy as a health care professional would not be present to perform any necessary emergency services. In order to be present and able to perform emergency services in the home setting if necessary for the safety and health of the beneficiary, we are proposing that the health care professional be on site at the home to administer or directly supervise the administration of a home infusion drug covered under the expanded DME benefit. We are soliciting comments on this proposal.</P>
                    <P>
                        As stated previously, section 6222(a) of the CAA, 2026 expands the DME benefit category to include external infusion pumps and associated home infusion drugs to include home infusion drugs that: (1) are infused at least 12 times per year intravenously or subcutaneously (section 1861(n)(3)(A) of the Act); or (2) infused at infusion rates that the Secretary determines would require the use of an external infusion pump (section 1861(n)(3)(B) of the Act). Based on our review, there do not currently appear to be any home infusion drugs that must be infused at rates that would require the use of an external infusion pump that do not otherwise already fall under the criterion set forth under section 
                        <PRTPAGE P="41306"/>
                        1861(n)(3)(A) of the Act. Therefore, we are not proposing at this time to include additional drugs under the scope of this DME benefit category expansion that do not already meet the criterion set forth under section 1861(n)(3)(A) of the Act. The criterion specified in section 1861(n)(3) of the Act is that the drug must be infused at least 12 times per year. Because of the way dosing information is typically framed in the prescribing information, we propose that to meet this requirement, the drug must be infused at least once per month. We believe such limitation would be appropriate given that it is aligned with how home infusion drugs are typically framed in the prescribing information. We therefore propose that home infusion drugs covered under this expanded DME benefit must be infused at least once a month. We are soliciting comments on this proposal.
                    </P>
                    <P>Note, we are not proposing a minimum or maximum number of times a drug must be infused to qualify as a “home infusion drug”. The duration of treatment is not always clear and is often patient-dependent. Prescribing information for infusion drugs will often call for infusions to continue indefinitely, until toxicity, or until adverse reactions preclude further treatment.</P>
                    <P>Finally, section 6222(b) of the CAA, 2026 requires the Secretary to ensure that patients are notified of the cost sharing for electing home infusion therapy compared to other applicable settings of care for the furnishing of infusion drugs under the Medicare program. We plan to implement this provision through sub regulatory guidance.</P>
                    <HD SOURCE="HD3">3. Provisions of the Proposed Regulation</HD>
                    <P>We propose to revise the definition of DME under 42 CFR 414.202 to incorporate the amendments to section 1861(n) of the Act for implementation of section 6222(a) of the CAA, 2026, effective April 1, 2027. Specifically, we propose to provide that certain external infusion pumps, associated home infusion drugs, and related supplies will be treated as meeting the “appropriate for use in the home” requirement when the following three criteria under paragraphs (1) through (3) of section 1861(n) of the Act are satisfied:</P>
                    <P>• The prescribing information approved by the FDA for the home infusion drug (as defined in § 486.505) associated with the pump instructs that the drug should be administered by or under the supervision of a health care professional. The health care professional must be a clinical nurse specialist (as defined § 410.76), nurse practitioner (as defined § 410.75), physician assistant (as defined § 410.74), physician as defined in section 1861(r) of the Act, or a registered nurse otherwise licensed to practice nursing in the State in which the home infusion drug is administered. The health care professional must be on site at the home to administer or supervise the administration of the home infusion drug.</P>
                    <P>• A qualified home infusion therapy supplier (as defined in § 486.505) administers or supervises the administration of the home infusion drug in a safe and effective manner in the patient's home (as defined in § 486.505)</P>
                    <P>
                        • The prescribing information instructs that the home infusion drug be infused at least 12 times per year (at least once a month), either intravenously or subcutaneously
                        <E T="03">,</E>
                         or at infusion rates that the Secretary determines would require the use of an external infusion pump. We are soliciting comments on this proposal.
                    </P>
                    <HD SOURCE="HD2">D. DMEPOS Competitive Bidding Program—Country of Origin</HD>
                    <P>CMS is planning to request to revise the information collection for the Durable Medical Equipment, Prosthetics, Orthotics, and Supplies (DMEPOS) Competitive Bidding Program (CBP), under OMB Control Number 0938-1408 (CMS-10744), to collect from DMEPOS CBP contract suppliers the country of origin for the lead items furnished during the DMEPOS CBP contract's period of performance.</P>
                    <P>
                        DMEPOS CBP contract suppliers are required to use a reporting form, known as Form C, to provide product information (manufacturer name, model name, and model number) for the lead item they furnish. During an active round of the DMEOPS CBP, the information provided in the form is included in the Supplier Directory on the 
                        <E T="03">Medicare.gov</E>
                         website with the products the supplier plans to provide during the next 6-month period. Contract suppliers are required, as a term of their contracts, to maintain the accuracy of their product information for the lead item they furnish using Form C. Form C includes an attestation that all the reported information is accurate and up to date. This attestation needs to be completed to fulfill a Form C submission requirement.
                    </P>
                    <P>We plan to request to revise the information collection to include the country of origin for each lead item they report on a new “country of origin” field on Form C. As done historically with the product information reported on Form C by a contract supplier, the reported country of origin information would be populated on the Medicare Supplier Directory for the contract supplier during the contract period of performance. This information would allow beneficiaries and interested parties to have access to the information on the country from which the DMEPOS item originated, if interested.</P>
                    <P>Contract suppliers would identify the country of origin based on the markings on the product for the lead item, or where an exemption to marking applies, obtain documentation from the manufacturer or distributor. Under U.S. Customs and Border Protections rules, imported goods must be properly marked with: “Made in [Country],” unless an exemption applies (for example, an item that is incapable of being marked, like a catheter), as explained at 19 CFR 134.32.</P>
                    <P>To correctly identify the country of origin for a product in the absence of a marking or to verify a marking, contract suppliers may need to obtain documentation from the manufacturer or distributor indicating the country of origin for its product, which could include one or a combination of the following: manufacturer certifications, bills of materials, manufacturing process descriptions, commercial invoices, U.S. Customs and Border Protection entry documentation, or a Harmonized Tariff Schedule classification.</P>
                    <P>The details for this update to Form C will be included under OMB Control Number 0938-1408 (CMS-10744).</P>
                    <HD SOURCE="HD1">VI. Collection of Information Requirements</HD>
                    <HD SOURCE="HD2">A. Statutory Requirement for Solicitation of Comments</HD>
                    <P>
                        Under the Paperwork Reduction Act of 1995, we are required to provide a notice in the 
                        <E T="04">Federal Register</E>
                         and solicit public comment before a collection of information requirement is submitted to the Office of Management and Budget (OMB) for review and approval. In order to fairly evaluate whether an information collection should be approved by OMB, section 3506(c)(2)(A) of the Paperwork Reduction Act of 1995 requires that we solicit comment on the following issues:
                    </P>
                    <P>• The need for the information collection and its usefulness in carrying out the proper functions of our agency.</P>
                    <P>• The accuracy of our estimate of the information collection burden.</P>
                    <P>• The quality, utility, and clarity of the information to be collected.</P>
                    <P>
                        • Recommendations to minimize the information collection burden on the affected public, including automated collection techniques.
                        <PRTPAGE P="41307"/>
                    </P>
                    <HD SOURCE="HD2">B. Information Collection Requirements (ICRs)</HD>
                    <P>In this HH PPS proposed rule, we are soliciting public comment on each of these issues for the following sections of this document that contain information collection requirements (ICRs). Failure to submit HH QRP data required under section 1895(b)(3)(B)(v) of the Act with respect to a program year would result in the reduction of the annual home health market basket percentage increase otherwise applicable to an HHA for the corresponding calendar year by 2 percentage points.</P>
                    <HD SOURCE="HD3">1. ICRs for HH QRP</HD>
                    <P>As discussed in section III of this proposed rule, we are proposing to revise the HH QRP data submission deadlines beginning with the CY 2027 HH QRP. CMS is also proposing to revise the HH QRP OASIS and HHCAHPS Annual Payment Update (APU) reporting timeframe to report a calendar year of data (January 1 through December 31). CMS proposes some revisions to regulatory text in support of rule proposals or to improve digital transfer of information during the reconsiderations process. Finally, we are soliciting public comments on one Request for Information (RFI) on future measure concepts for the HH QRP.</P>
                    <P>The net effect of these proposals is no changes to expected burden associated with OASIS data collection.</P>
                    <HD SOURCE="HD3">2. ICRs for the Expanded HHVBP Model</HD>
                    <P>There are no proposals for the expanded HHVBP Model.</P>
                    <HD SOURCE="HD3">3. ICRs for DMEPOS Requirements for Identical Replacement Items</HD>
                    <P>This proposed clarification neither imposes new information collection requirements nor eliminates existing ones. Rather, it further explains and reinforces the intent of this section when the item furnished is a replacement item. The PRA package for Medicare Fee-for-Service Prepayment Review of Medical Records is CMS-10417 and approved under OMB control number 0938-0969. In section V.B. of this proposed rule, we clarify that a new face-to-face encounter and related documentation are not required to support payment for replacement durable medical equipment, prosthetic, orthotic and supply (DMEPOS) items. Under existing Medicare requirements, suppliers and providers are already obligated to maintain documentation sufficient to demonstrate compliance with coverage requirements under 42 CFR 410.38 at the time the item is furnished. This rule clarifies that CMS does not consider an additional comprehensive beneficiary examination necessary to “gather[ ] subjective and objective information associated with diagnosing, treating, or managing a clinical condition for which the DMEPOS is ordered” when the item being furnished is a replacement item. If a claim for a replacement DMEPOS item is subject to audit, the provider must nevertheless submit documentation from the original face-to-face encounter to demonstrate that medical necessity, billing and coverage requirements have been satisfied. Accordingly, the intent of 42 CFR 410.38, which requires a face-to-face encounter for certain DMEPOS items, would continue to apply when the item is initially furnished; however, the requirement would not need to be repeated solely for replacement items. Therefore, we assume this clarification would have a negligible monetary impact.</P>
                    <HD SOURCE="HD3">4. ICRs for Provider Enrollment</HD>
                    <P>We do not believe that any of our proposed provider enrollment regulatory revisions would impose an information collection burden on interested parties. However, there are several provisions about which clarification on this matter is needed.</P>
                    <HD SOURCE="HD3">a. Signage</HD>
                    <P>Proposed § 424.510(f) would require all providers and suppliers (regardless of type) to maintain a permanent visible sign in plain view and post their hours of operation. We believe the vast majority of providers and suppliers already do so; in accordance with the implementing regulations of the PRA at 5 CFR 1320.3(b)(2), providers and suppliers typically maintain such policies and records as a usual and customary business practice. Therefore, we have not assigned any burden to this requirement.</P>
                    <HD SOURCE="HD3">b. Clarification of “Managing Employee” Definition</HD>
                    <P>All providers and suppliers must report their managing employees (and any changes in their managing employees) to CMS. This reporting requirement falls within the overall OMB-approved ICR burden for the following forms:</P>
                    <P>• Form CMS-855A (Medicare Enrollment Application for Institutional Providers; OMB Control No. 0938-0685).</P>
                    <P>• Form CMS-855B (Medicare Enrollment Application—Clinics/Group Practices and Certain Other Suppliers; OMB Control No. 0938-1377).</P>
                    <P>• Form CMS-855I (Medicare Enrollment Application—Physicians and Non-Physician Practitioners; Clinics/Group Practices and Certain Other Suppliers; OMB Control No. 0938-1355).</P>
                    <P>• Form CMS-855S (Medicare Enrollment Application—Durable Medical Equipment, Prosthetics, Orthotics, and Supplies (DMEPOS) Suppliers; OMB Control No. 0938-1056).</P>
                    <P>We are proposing to revise the definition of “managing employee” in § 424.502 to identify certain individuals who fall within this definition. This would not impose an additional ICR burden, though, because these persons have always qualified as managing employees and thus must be reported. We are simply identifying them in § 424.502 to reiterate this point.</P>
                    <HD SOURCE="HD3">c. Documentation</HD>
                    <HD SOURCE="HD3">(1) “Operational”</HD>
                    <P>Proposed paragraph (5) of our proposed revised definition of “operational” in § 424.502 would require, in part, that the provider or supplier have adequate written policies and records regarding its operations. We do not believe this would impose an additional information collection burden on providers and suppliers. In accordance with the implementing regulations of the PRA at 5 CFR 1320.3(b)(2), providers and suppliers typically maintain such policies and records as a usual and customary business practice. Therefore, we have not assigned any burden to this requirement.</P>
                    <HD SOURCE="HD3">(2) Section 424.516(f)</HD>
                    <P>Section 424.516(f) requires providers and suppliers to maintain certain types of documentation. We are proposing to revise this paragraph to make clear that said documentation must be accurate, complete, and consistent with CMS requirements. We do not believe this would impose an additional information collection burden on providers and suppliers. In accordance with the implementing regulations of the PRA at 5 CFR 1320.3(b)(2), providers and suppliers typically maintain such policies and records as a usual and customary business practice. Therefore, we have not assigned any burden to this requirement.</P>
                    <HD SOURCE="HD3">d. Private Equity Companies (PECs) and Real Estate Investment Trusts (REITs)</HD>
                    <P>
                        The Form CMS-855A enrollment application for certified providers and certain certified suppliers (Medicare Enrollment Application for Institutional Providers OMB Control No. 0938-0685) requires providers and suppliers to report whether any party listed on the 
                        <PRTPAGE P="41308"/>
                        application is a PEC or a REIT. We are announcing in this proposed rule our intention to expand this requirement to the following Medicare provider and supplier enrollment forms:
                    </P>
                    <P>• Form CMS-855B (Medicare Enrollment Application—Clinics/Group Practices and Certain Other Suppliers; OMB Control No. 0938-1377).</P>
                    <P>• Form CMS-855S (Medicare Enrollment Application—Durable Medical Equipment, Prosthetics, Orthotics, and Supplies (DMEPOS) Suppliers; OMB Control No. 0938-1056).</P>
                    <P>• Form CMS-20134 (Medicare Diabetes Prevention Program (MDPP) Suppliers).</P>
                    <P>Although this announcement would not, in and of itself, impose an information collection burden, the revisions of the Forms CMS-855B and CMS-855S, to collect PEC and REIT data would do so. The Forms CMS-855B and CMS-855S burdens will be addressed in the information collection requests that CMS will submit to the Office of Management and Budget to request revisions to these two forms. However, the Form CMS-20134 is exempt under section 1115(a) of the Affordable Care Act.</P>
                    <HD SOURCE="HD3">e. Disclosure of Affiliations</HD>
                    <P>As discussed in section V.C. of this proposed rule, we are proposing to revise our affiliation provisions in §§ 424.502 and 424.519. We solicit comment from interested parties as to whether any additional ICR burden would ensue from these changes.</P>
                    <HD SOURCE="HD3">f. Reactivation Effective Dates</HD>
                    <P>We are proposing to permit providers that have been assigned an effective date for their reactivation to submit a rebuttal if they disagree with said date. We believe the rebuttal and the associated burden would be incurred subsequent to an administrative action. In accordance with the implementing regulations for the PRA (5 CFR 1320.4(a)(2) and (c)), the burden associated with any information collected subsequent to the administrative action is exempt from the requirements of the PRA (that is, the rebuttal submitted subsequent to the assignment of the reactivation effective date).</P>
                    <HD SOURCE="HD3">5. ICRs for Country of Origin</HD>
                    <P>
                        When ready, the following changes will be submitted to OMB for review under control number 0938-1408 (CMS-10744) using the standard, non-rule related PRA process (which includes the publication of 60- and 30-day 
                        <E T="04">Federal Register</E>
                         notices) to facilitate the change.
                    </P>
                    <P>As discussed in section V.E. of this proposed rule, we plan to revise Form C (Semi-Annual Report) to collect the country of origin information for the lead items furnished during the DMEPOS CBP contract's period of performance. Because contract suppliers are required to submit Form C once every 6 months during January and July throughout the DMEPOS Competitive Bidding Program contract's period of performance, contract suppliers would be required to report this information twice a year. A DMEPOS CBP contract supplier would continue to be required as a term of its contract to maintain the accuracy of its product information (manufacturer name, model name, and model number) for the lead item it furnishes on Form C, and they would now be required to also maintain the accuracy of the country of origin for each product it reports in a newly added “country of origin” field on Form C. Form C would continue to require an attestation that all the reported information is accurate and up to date.</P>
                    <P>Contract suppliers should be able to identify the country of origin based on the markings on the product for the lead item. For example, under U.S. Customs and Border Protections rules, imported goods must be properly marked with: “Made in [Country],” unless an exemption applies (for example an item that is incapable of being marked, like a catheter), as explained at 19 CFR 134.32. To correctly identify the country of origin for a product in the absence of a marking or to verify a marking, contract suppliers may need to refer to readily available documentation from the manufacturer or distributor indicating the country of origin for its product, which could include a combination of the following: manufacturer certifications, bills of materials, manufacturing process descriptions, commercial invoices, U.S. Customs and Border Protection entry documentation, or a Harmonized Tariff Schedule classification.</P>
                    <P>
                        At this time, we estimate that each annual response would take 0.2 hours (1 bidder/year × 0.1 hr/response × 2 responses/year) at a cost of $20.84 (0.2 hr × $104.22/hr). Given that the number of suppliers that will be awarded a Round 2028 DMEPOS CBP contract is not yet finalized, we are providing an estimated annual response time as opposed to an aggregate figure that considers the total number of awarded suppliers. Our proposed number of respondents and other burden estimates will be revised once the number of DMEPOS CBP contracts for Round 2028 is finalized, and will be restated when we publish our 60- and 30-day 
                        <E T="04">Federal Register</E>
                         notices. This information will be updated when the final rule is published.
                    </P>
                    <GPH SPAN="3" DEEP="99">
                        <GID>EP06JY26.078</GID>
                    </GPH>
                    <HD SOURCE="HD1">VII. Regulatory Impact Analysis</HD>
                    <HD SOURCE="HD2">A. Statement of Need</HD>
                    <HD SOURCE="HD3">1. HH PPS</HD>
                    <P>
                        Section 1895(b)(1) of the Act requires the Secretary to establish an HH PPS for all costs of home health services paid under Medicare. In addition, section 1895(b) of the Act requires: (1) the computation of a standard prospective payment amount include all costs for home health services covered and paid for on a reasonable cost basis and that such amount be initially based on the most recent audited cost report data available to the Secretary; (2) the prospective payment amount under the HH PPS to be an appropriate unit of service based on the number, type, and duration of visits provided within that unit; and (3) the standard prospective 
                        <PRTPAGE P="41309"/>
                        payment amount be adjusted to account for the effects of case-mix and wage levels among HHAs. Section 1895(b)(3)(B) of the Act addresses the annual update to the standard prospective payment amounts by the home health applicable percentage increase. Section 1895(b)(4) of the Act governs the payment computation. Sections 1895(b)(4)(A)(i) and (b)(4)(A)(ii) of the Act require the standard prospective payment amount be adjusted for case-mix and geographic differences in wage levels. Section 1895(b)(4)(B) of the Act requires the establishment of appropriate case-mix adjustment factors for significant variation in costs among different units of services. Lastly, section 1895(b)(4)(C) of the Act requires the establishment of wage adjustment factors that reflect the relative level of wages, and wage-related costs applicable to home health services furnished in a geographic area compared to the applicable national average level.
                    </P>
                    <P>Section 1895(b)(3)(B)(iv) of the Act provides the Secretary with the authority to implement adjustments to the standard prospective payment amount (or amounts) for subsequent years to eliminate the effect of changes in aggregate payments during a previous year or years that were the result of changes in the coding or classification of different units of services that do not reflect real changes in case-mix. Section 1895(b)(5) of the Act provides the Secretary with the option to make changes to the payment amount otherwise paid in the case of outliers because of unusual variations in the type or amount of medically necessary care. Section 1895(b)(3)(B)(v) of the Act requires HHAs to submit data for purposes of measuring health care quality and links the quality data submission to the annual applicable percentage increase.</P>
                    <P>Sections 1895(b)(2) and 1895(b)(3)(A) of the Act, as amended by sections 51001(a)(1) and 51001(a)(2) of the BBA of 2018 respectively, required the Secretary to implement a 30-day unit of payment, for 30-day periods beginning on and after January 1, 2020. Section 1895(b)(3)(D)(i) of the Act, as added by section 51001(a)(2)(B) of the BBA of 2018, requires the Secretary to annually determine the impact of differences between assumed behavior changes, as described in section 1895(b)(3)(A)(iv) of the Act, and actual behavior changes on estimated aggregate expenditures under the HH PPS with respect to years beginning with 2020 and ending with 2026. Section 1895(b)(3)(D)(ii) of the Act requires the Secretary, at a time and in a manner determined appropriate, through notice and comment rulemaking, to provide for one or more permanent increases or decreases to the standard prospective payment amount (or amounts) for applicable years, on a prospective basis, to offset for such increases or decreases in estimated aggregate expenditures, as determined under section 1895(b)(3)(D)(i) of the Act. Additionally, 1895(b)(3)(D)(iii) of the Act requires the Secretary, at a time and in a manner determined appropriate, through notice and comment rulemaking, to provide for one or more temporary increases or decreases to the payment amount for a unit of home health services for applicable years, on a prospective basis, to offset for such increases or decreases in estimated aggregate expenditures, as determined under section 1895(b)(3)(D)(i) of the Act. The HH PPS wage index utilizes the wage adjustment factors used by the Secretary for purposes of sections 1895(b)(4)(A)(ii) and (b)(4)(C) of the Act for hospital wage adjustments.</P>
                    <HD SOURCE="HD3">2. HH QRP</HD>
                    <P>Section 1895(b)(3)(B)(v) of the Act authorizes the HH QRP, which requires HHAs to submit data in accordance with the requirements specified by CMS. Failure to submit data required under section 1895(b)(3)(B)(v) of the Act with respect to a program year will result in the reduction of the annual home health market basket percentage increase otherwise applicable to an HHA for the corresponding calendar year by 2 percentage points.</P>
                    <HD SOURCE="HD3">3. Expanded HHVBP Model</HD>
                    <P>In the CY 2022 HH PPS final rule (86 FR 62292 through 62336) and codified at 42 CFR part 484, subpart F, we finalized our policy to expand the HHVBP Model to all Medicare certified HHAs in the 50 States, territories, and District of Columbia beginning January 1, 2022. CY 2022 was a pre-implementation year. CY 2023 was the first performance year in which HHAs individual performance on the applicable measures affects their Medicare payments in CY 2025. We are not proposing any expanded HHVBP Model-specific changes in this proposed rule.</P>
                    <HD SOURCE="HD3">4. DMEPOS Requirements for Identical Replacement Items</HD>
                    <P>In this proposed rule, we would clarify that a new face-to-face encounter and related documentation, as described in 42 CFR 410.38, is not necessary to support the payment of replacement DMEPOS items.</P>
                    <HD SOURCE="HD3">5. Provider Enrollment</HD>
                    <P>Consistent with section 1866(j) of the Act, we are proposing a number of Medicare provider enrollment provisions to strengthen and clarify certain aspects of the provider enrollment process. These include but are not limited to: (1) adding and modifying grounds for denying or revoking a provider's or supplier's Medicare enrollment; and (2) expanding the reasons for which CMS can apply a retroactive effective date for provider and supplier revocations. These changes are necessary to help ensure that payments are made only to qualified providers and suppliers, which we believe would assist in protecting the Trust Funds and Medicare beneficiaries.</P>
                    <HD SOURCE="HD3">6. DMEPOS Coverage of External Infusion Pumps</HD>
                    <P>With section 6222 of the Consolidated Appropriations Act, 2026, Congress modified section 1861(n) of the Act to expand the scope of the DME benefit to enable coverage for home infusion of drugs that: (1) must be administered by or under the supervision of a health care professional; (2) are administered by a qualified home infusion therapy supplier; and (3) have prescribing information that requires infusion at least 12 times per year. This regulatory action implements the changes made by section 6222 of the CAA, 2026 to the definition of DME.</P>
                    <HD SOURCE="HD3">7. DMEPOS Competitive Bidding—Country of Origin</HD>
                    <P>For the DMEPOS CBP, we discuss requesting to revise the information collection under OMB Control Number 0938-1408 (CMS-10744) to collect from DMEPOS Competitive Bidding contract suppliers the country of origin for the lead items furnished during the DMEPOS CBP contract's period of performance.</P>
                    <P>The reported country of origin information would be populated on the Medicare Supplier Directory for the contract supplier during the contract period of performance so beneficiaries and interested parties may learn where the DMEPOS item originated, if interested.</P>
                    <HD SOURCE="HD2">B. Overall Impact</HD>
                    <P>
                        We have examined the impacts of this proposed rule as required by Executive Order 12866, “Regulatory Planning and Review”; Executive Order 13132, “Federalism”; Executive Order 13563, “Improving Regulation and Regulatory Review”; Executive Order 14192, “Unleashing Prosperity Through Deregulation”; the Regulatory Flexibility Act (RFA) (Pub. L. 96 354); 
                        <PRTPAGE P="41310"/>
                        section 1102(b) of the Social Security Act; and section 202 of the Unfunded Mandates Reform Act of 1995.
                    </P>
                    <P>Executive Orders 12866 and 13563 direct agencies to assess all costs and benefits of available regulatory alternatives and, if regulation is necessary, to select those regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety, and other advantages; and distributive impacts). Section 3(f) of Executive Order 12866 defines a “significant regulatory action” as any regulatory action that is likely to result in a rule that may: (1) have an annual effect on the economy of $100 million or more or adversely affect in a material way the economy, a sector of the economy, productivity, competition, jobs, the environment, public health or safety, or State, local, or tribal governments or communities; (2) create a serious inconsistency or otherwise interfere with an action taken or planned by another agency; (3) materially alter the budgetary impact of entitlements, grants, user fees, or loan programs or the rights and obligations of recipients thereof; or (4) raise novel legal or policy issues arising out of legal mandates, or the President's priorities.</P>
                    <P>A regulatory impact analysis (RIA) must be prepared for a regulatory action that is significant under section 3(f)(1) of Executive Order 12866. Based on our estimates, OMB's Office of Information and Regulatory Affairs has determined this rulemaking is significant per section 3(f)(1) of Executive Order 12866. Accordingly, we have prepared a regulatory impact analysis that presents the cost and benefit of the rulemaking to the best of our ability.</P>
                    <HD SOURCE="HD2">C. Detailed Economic Analysis</HD>
                    <HD SOURCE="HD3">1. Effects of the Proposed Changes for the CY 2027 HH PPS</HD>
                    <P>This rule proposes to update Medicare payments under the HH PPS for CY 2027. The net transfer impact related to the changes in payments under the HH PPS for CY 2027 is estimated to be $420 million (2.4 percent) above the current projected CY 2026 baseline of $17.575 billion, leading to total projected spending of approximately $18 billion for 2027. The $420 million increase in estimated payments for CY 2027 reflects the effects of the proposed CY 2027 home health payment update percentage of 2.1 percent ($370 million increase), and an estimated 0.3 percent increase that reflects the updated FDL ($50 million increase).</P>
                    <P>We use the latest data and analysis available. However, we do not adjust for future changes in such variables as number of visits or case-mix. This analysis incorporates the latest estimates of growth in service use and payments under the Medicare home health benefit, based primarily on Medicare claims data for periods that ended on or before December 31, 2025. We note that certain events may combine to limit the scope or accuracy of our impact analysis, because such an analysis is future-oriented and, thus, susceptible to errors resulting from other changes in the impact time period assessed. Some examples of such possible events are newly legislated general Medicare program funding changes made by the Congress or changes specifically related to HHAs. In addition, changes to the Medicare program may continue to be made as a result of new statutory provisions. Although these changes may not be specific to the HH PPS, the nature of the Medicare program is such that overall changes may interact, and the complexity of the interaction of these changes could make it difficult to predict accurately the full scope of the impact upon HHAs.</P>
                    <P>Table 36 represents how HHA revenues are likely to be affected by the proposed policy changes for CY 2027. For this analysis, we used an analytic file with linked CY 2025 OASIS assessments and home health claims data for dates of service that ended on or before December 31, 2025. The first column of table 36 classifies HHAs according to a number of characteristics including provider type, geographic region, and urban and rural locations. The second column shows the number of facilities in the impact analysis. The third column shows the payment effects of the recalibration of the case-mix weights offset by the case-mix weight budget neutrality factor. The fourth column shows the payment effects of updating the CY 2027 wage index (that is, the FY 2027 hospital pre-floor, pre-reclassified wage index for hospital cost reporting periods beginning on or after October 1, 2022, and before October 1, 2023 (FY 2023 cost report data) with a 5-percent cap on wage index decreases. The aggregate impact of the changes in the fourth column is zero percent, due to the wage index budget neutrality factor. The fifth column shows the payment effects of the proposed CY 2027 home health payment update percentage. The sixth column shows the payment effects of the proposed FDL. The seventh column shows the payment effects of the proposed temporary adjustment on all payments. The aggregate impact of the proposed temporary adjustment reflected in the seventh column equals zero percent because both the CY 2026 and CY 2027 payment rates would include a 3.0 percent temporary adjustment. The last column shows the combined effects of all the proposed provisions.</P>
                    <P>Overall, it is projected that aggregate payments in CY 2027 would increase by 2.4 percent, which reflects the proposed 2.1 percent increase to the home health payment update percentage and the 0.3 percent increase from the updated FDL. As illustrated in table 36, the combined effects of all changes vary by specific types of providers and by location. We note that some individual HHAs within the same group may experience different impacts on payments than others due to the distributional impact of the CY 2027 wage index, the percentage of total HH PPS payments that were subject to the LUPA or paid as outlier payments, and the degree of Medicare utilization.</P>
                    <BILCOD>BILLING CODE 4169-69-P</BILCOD>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41311"/>
                        <GID>EP06JY26.079</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41312"/>
                        <GID>EP06JY26.080</GID>
                    </GPH>
                    <PRTPAGE P="41313"/>
                    <BILCOD>BILLING CODE 4169-69-C</BILCOD>
                    <HD SOURCE="HD3">2. Effects of the Proposed Changes for the HH QRP for CY 2027</HD>
                    <P>Failure to submit HH QRP data required under section 1895(b)(3)(B)(v) of the Act with respect to a program year will result in the reduction of the annual home health market basket percentage increase otherwise applicable to an HHA for the corresponding calendar year by 2 percentage points. For the CY 2023 program year, 820 of the 11,549 active Medicare-certified HHAs, or approximately 7.1 percent, did not receive the full annual percentage increase because they did not meet assessment submission requirements. The 820 HHAs that did not satisfy the reporting requirements of the HH QRP for the CY 2023 program year represent $149 million in home health claims payment dollars during the reporting period out of a total $16.4 billion for all HHAs.</P>
                    <P>This proposed rule proposes to revise the HH QRP data submission deadlines beginning with the CY 2027 HH QRP. We also propose to revise the HH QRP OASIS and HHCAHPs annual payment update (APU) reporting timeframe to report a calendar year of data (January 1 through December 31). We propose revisions to regulatory text in support of rule proposals to improve digital transfer of information during the reconsiderations process. Finally, we are soliciting public comments on one Request for Information (RFI) on future measure concepts for the HH QRP. The net effect of these proposals is no change in burden for OASIS data collection.</P>
                    <HD SOURCE="HD3">3. Effects of the Expanded HHVBP Model</HD>
                    <P>In the CY 2022 HH PPS final rule (88 FR 77676), we estimated that the expanded HHVBP Model would generate a total projected 5-year gross FFS savings of $3,376,000,000. Given that we are not proposing any expanded HHVBP Model specific changes in this proposed rule, these estimates are unchanged.</P>
                    <HD SOURCE="HD3">4. DMEPOS Requirements for Identical Replacement Items</HD>
                    <P>This proposed provision would clarify that a face-to-face encounter and related documentation, as described in 42 CFR 410.38, is not necessary to support the payment of replacement DMEPOS items. The fiscal impact of this clarification cannot be estimated as this rule only identifies whether a face-to-face encounter is required for payment for replacement of DMEPOS items. Given the volume of Medicare beneficiaries and associated claims for payment, we do not audit all claim submissions for compliance with Medicare conditions of payment—including the face-to-face encounter. In addition, for those claims audited, it is one of many Medicare coverage requirements, and therefore delineating its compliance rate is not operationally feasible. This situation can only be identified upon medical record review, and replacements were not the sole focus of a medical review audit. Rather, varied medical review decision-making and the need for this clarification was identified anecdotally. As such, we cannot reliably forecast any cost for this limited subset of claims for replacement items</P>
                    <HD SOURCE="HD3">5. Provider Enrollment</HD>
                    <P>As previously noted, we are proposing a number of provider enrollment provisions to strengthen and clarify certain aspects of the provider enrollment process. This RIA addresses provisions that: (1) we believe would have a financial impact; and (2) would not, in our view, have such an impact but which require explanation.</P>
                    <HD SOURCE="HD3">a. Revocation Effective Dates</HD>
                    <P>Existing § 424.535(g)(1) states that except as described in § 424.535(g)(2) and (3), a revocation becomes effective 30 days after CMS or its contractor mails notice of its determination to the provider or supplier (hereafter occasionally and collectively “providers”). Under current § 424.535(g)(2)(i) through (xv), there are grounds for which CMS can revoke a provider's enrollment retroactively to the date the provider's non-compliance commenced. Retroactive revocation allows CMS to collect monies that have been paid to the provider since the beginning of its non-compliance. We explained in section V.C. of this proposed rule that we are proposing to make the effective dates of all of our revocation reasons in § 424.535 retroactive. Existing revocation grounds that are currently applied prospectively but would become retroactive are listed as follows (along with their proposed retroactive effective dates):</P>
                    <P>
                        • 
                        <E T="03">§ 424.535(a)(1) (Noncompliance with enrollment requirements):</E>
                         The date the non-compliance began (per CMS' or the CMS contractor's determination).
                    </P>
                    <P>
                        • 
                        <E T="03">§ 424.535(a)(5)(b)(ii) (Noncompliance with enrollment requirements):</E>
                         The date the Medicare enrollment requirement was not satisfied.
                    </P>
                    <P>
                        • 
                        <E T="03">§ 424.535(a)(7):</E>
                         The date on which the conduct resulting the revocation occurred.
                    </P>
                    <P>
                        • 
                        <E T="03">§ 424.535(a)(6) (Application fee noncompliance):</E>
                         The date on which CMS or its contractor determines that the provider should be revoked under paragraph (a)(6).
                    </P>
                    <P>
                        • 
                        <E T="03">§ 424.535(a)(10)(i) (Document retention):</E>
                         The date on which CMS or the CMS contractor determines that the provider has not complied with this retention requirement.
                    </P>
                    <P>
                        • 
                        <E T="03">§ 424.535(a)(10)(ii) (Document access to CMS):</E>
                         The day after the date by which the provider was required to furnish access.
                    </P>
                    <P>
                        • 
                        <E T="03">§ 424.535(a)(11) (Capitalization):</E>
                         The day after the date by which the provider was required to furnish the requested documentation.
                    </P>
                    <P>
                        • 
                        <E T="03">§ 424.535(a)(14) (Abusive prescribing):</E>
                         The date of the last prescription in the applicable pattern or practice.
                    </P>
                    <P>
                        • 
                        <E T="03">§ 424.535(a)(15) (False Claims Act judgments):</E>
                         The date of the judgment.
                    </P>
                    <P>
                        • 
                        <E T="03">§ 424.535(a)(17) (Referral of debt to Treasury):</E>
                         The date on which CMS referred the debt to the Department of Treasury.
                    </P>
                    <P>
                        • 
                        <E T="03">§ 424.535(a)(18) (Revoked under different name or identifier):</E>
                         The effective date of the provider's current enrollment.
                    </P>
                    <P>
                        • 
                        <E T="03">§ 424.535(a)(19) (Undue risk):</E>
                         The date on which CMS or its contractor determines that the provider should be revoked under paragraph (a)(19).
                    </P>
                    <P>
                        • 
                        <E T="03">§ 424.535(a)(20) (Billing from non-compliant location):</E>
                         The earliest date on the claims for the non-compliant location that are triggering the revocation.
                    </P>
                    <P>
                        • 
                        <E T="03">§ 424.535(a)(21) (Abusive ordering, certifying, etc.):</E>
                         The date of the last order, certification, referral, or prescription in the applicable pattern or practice.
                    </P>
                    <P>
                        • 
                        <E T="03">§ 424.535(a)(22) (Patient harm):</E>
                         The date of the prior action resulting in the revocation.
                    </P>
                    <P>
                        • 
                        <E T="03">§ 424.535(a)(23) (Condition or standard noncompliance):</E>
                         Under § 424.535(g)(xv)(D), the current paragraph (a)(23) revocation effective date for all standard orcondition violations other than those listed in § 424.535(g)(xv)(A) through (C) is prospective; that is, it is 30 days after the date that CMS or the CMS contractor mails the revocation letter to the provider or supplier. We are proposing to make these (a)(23) prospective effective dates retroactive back to the date of the violation or non-compliance (per CMS' or the CMS contractor's determination).
                        <PRTPAGE P="41314"/>
                    </P>
                    <P>Table 37 contains several data categories. The first identifies those new retroactive revocation grounds for which we are able to calculate savings to the Medicare program. The second is the average annual number of revocations that occur for each of these revocation grounds. The third is the average length of time between when the non-compliance begins in these situations and 30 days after the revocation letter is sent to the provider in question. For instance, suppose a provider undergoes a change in its billing agency's address effective May 1 but fails to report it to CMS within 90 days. The provider is revoked under § 424.535(a)(9). The revocation letter is mailed to the provider on August 15, meaning the effective date under existing § 424.535(g)(1) is September 15. The period between the date of non-compliance and the effective date under current paragraph (g)(1) is thus 45 days (that is, the period between July 31 (the day after the 90-day reporting deadline) and September 15). Under our proposal, though, the provider would be ineligible for payments for services furnished during this 45-day period because its revocation would now be retroactive back to the date of non-compliance (July 31).</P>
                    <P>The last two categories address the savings that would accrue to Medicare from the proposed retroactive grounds listed in the first column. Based on internal CMS data, we calculated in the fourth column of table 37 the average amount of actual payments made to the providers in each of the table's proposed retroactive revocation reasons during the time period in the table's third column. To illustrate, table 37 indicates that 17 providers per year are revoked under § 424.535(a)(22), with the third column identifying a 95-day period. The fourth column reflects the average annual payments each of these 17 providers receive during their respective 95-day periods (or $20,586).</P>
                    <P>The fifth column estimates the total savings for each of our proposed retroactive revocation reasons—specifically, we multiplied the figures in the second column by those in the fourth. Using our § 424.535(a)(22) example, the total annual savings figure is $349,962 (or 17 × $20,586).</P>
                    <P>We used this same approach when calculating projected savings for the new retroactive revocation grounds we finalized in the CY 2026 HH PPS final rule (90 FR 55342).</P>
                    <GPH SPAN="3" DEEP="266">
                        <GID>EP06JY26.081</GID>
                    </GPH>
                    <P>Accordingly, we project annual savings of $81,963,430 stemming from our retroactive revocation proposals.</P>
                    <HD SOURCE="HD3">b. Expanded and New Revocation Reasons</HD>
                    <P>As discussed in section V.B. of this proposed rule, we are proposing the following expanded and new revocation grounds:</P>
                    <P>• We would expand existing § 424.535(a)(4) to permit revocation if the provider submits false or misleading information on or associated with any provider enrollment-related CMS or Medicare form (including forms created by and/or submitted to CMS contractors). Section 424.535(a)(4) would no longer be limited to false or misleading information on the enrollment application.</P>
                    <P>• Revised § 424.535(a)(16) would include a new revocation ground permitting enrollment if the provider—or any owner, managing employee, managing organization, officer, or director thereof—was convicted of a Federal or State misdemeanor related to sexual assault or financial misconduct within the past 10 years that CMS deems detrimental to the best interests of the Medicare program and its beneficiaries.</P>
                    <P>• New § 424.535(a)(24) would permit revocation if CMS determines that the provider's enrollment presents a high risk of fraud, waste, or abuse due to the provider's location within a limited geographic area that has an excessive number of providers and suppliers.</P>
                    <P>
                        • New § 424.535(a)(25) would permit revocation if CMS determines that the HHA, hospice, or DMEPOS supplier did not comply with the provisions and requirements of, as applicable, § 424.550(b) or § 424.551.
                        <PRTPAGE P="41315"/>
                    </P>
                    <P>As we cannot predict the number of instances in which we would utilize these new and expanded, we are unable to establish a savings estimate.</P>
                    <HD SOURCE="HD3">c. Preclusion List</HD>
                    <P>The preclusion list is a compilation of providers that are prohibited from receiving Medicare Advantage or Part D payments. One ground for which a provider can be placed on the preclusion list if it has a felony conviction with the past 10 years. We are proposing to expand this to include felony convictions of the provider's owner, managing employee/organization, or corporate officer/director. As with our proposed revocation provisions, though, we are unable to establish a savings estimate for this expansion. This is because we cannot predict the number of instances where we would place a provider on the preclusion based on an owner's, managing employee's, etc., felony conviction.</P>
                    <HD SOURCE="HD3">d. Hospice Reactivations</HD>
                    <P>Section 424.540(b)(3)(i) states that an HHA whose Medicare billing privileges are deactivated under § 424.540 must obtain an initial State survey or accreditation before its Medicare billing privileges can be reactivated. We are proposing to expand § 424.540(b)(3)(i) to include hospices.</P>
                    <P>An average of roughly 226 hospices each year seek to reactivate their enrollments. Although hospice surveys and accreditation costs vary widely, we project—solely for purposes of this estimate—that the average cost would be $6,000. This results in an annual cost of our proposed § 424.540(b)(3)(i) expansion of $1,356,000. We welcome comments on this projection.</P>
                    <HD SOURCE="HD3">e. Conclusion</HD>
                    <P>We do not believe our proposals would negatively impact access to care, including in rural areas. We have promulgated numerous denial and revocation provisions in prior CMS provider enrollment regulations with no such impact, and we do not anticipate that our new denial and revocation grounds (and expansions of existing ones) would result in large numbers of denial and revocations.</P>
                    <P>We solicit comment from interested parties regarding any additional costs that may arise from our proposed enrollment provisions.</P>
                    <HD SOURCE="HD3">6. DMEPOS Coverage of External Infusion Pumps</HD>
                    <P>This proposed rule would expand the scope of the Medicare Part B benefit for DME by revising the interpretation of the “appropriate for use in the home” requirement in the definition of DME at 42 CFR 414.202 for certain drugs or biologicals infused in the home that fulfill specific requirements outlined in the statute. Since drugs or biologicals administered through an external infusion pump that is classified as DME can be covered under the Medicare Part B benefit as supplies necessary for the effective use of the external infusion pump, expanding the scope of the DME benefit has the effect of expanding coverage to drugs or biologicals that were not previously covered through home infusion. At this time, we expect that there is only one drug that did not previously meet the requirements for coverage through home infusion but does meet the requirements as modified by section 6222 of the Consolidated Appropriations Act, 2026, and will be used by a sufficient number of Medicare beneficiaries to warrant consideration: patisiran. While there may be other drugs that meet the basic requirements for coverage, we believe that use through home infusion would be negligible. In addition, it is possible that pharmaceutical makers may introduce new drugs or biologicals, or reformulate existing products, that will qualify for coverage under this expanded scope, but we cannot predict or estimate what impact this may have.</P>
                    <P>This expanded scope mirrors changes that had been proposed in 2020 rulemaking, “Durable Medical Equipment, Prosthetics, Orthotics, and Supplies (DMEPOS) Policy Issues and Level II of the Healthcare Common Procedure Coding System (HCPCS)” (85 FR 70358). At that time, we had estimated Medicare savings of roughly $3 million per year. Since then, claims data show that significantly fewer beneficiaries have been receiving patisiran infusions. Claims data for 2025 show that only 69 beneficiaries received patisiran infusions. As we noted in the previous proposed rule, the primary impact of this expanded scope relates to the difference in beneficiary cost sharing between infusion therapy received in an outpatient clinic setting and home infusion therapy: cost sharing for each outpatient infusion is the normal 20 percent Part B coinsurance limited to the Part A deductible ($1,736 in 2026), while cost sharing for home infusion therapy is not limited.</P>
                    <P>Claims data show that the annual cost of patisiran for each beneficiary receiving it in 2025 was approximately $313,000. Based on the typical infusion every three weeks, these patients likely received 17 infusions each year. When received in an outpatient setting, the capped cost sharing would apply, so each beneficiary would pay $1,736 per infusion or approximately $29,500 for the year. If, instead, patisiran were received as home infusion, cost sharing for the patisiran alone would be approximately $3,700 per infusion, or $62,900 per year. There would also be additional charges for home infusion (for example, home infusion services, pump rental, other supplies) that exceed the charges for outpatient infusion, and CMS believes these would cost Medicare approximately $7,000 per beneficiary per year, and the beneficiary approximately $2,000 in cost sharing (additional charges for outpatient infusion would cost Medicare approximately $4,000). Taken together, a beneficiary that receives patisiran through home infusion instead of outpatient infusion would save Medicare approximately $31,000 per year because of the higher cost sharing (the beneficiary would pay an additional $34,000) offset by the higher total cost of home infusion (additional $3,000 net cost to Medicare).</P>
                    <P>
                        Given this substantial cost sharing difference, we believe it is unlikely that beneficiaries would consider home infusion for patisiran unless they are either enrolled in Medicaid or have purchased Medicare supplement insurance (Medigap). While CMS does not directly track how many beneficiaries have enrolled in private Medigap plans, a recent report from the Kaiser Family Foundation (“Key Facts About Medigap Enrollment and Premiums for Medicare Beneficiaries,” 2024. Retrieved from 
                        <E T="03">https://www.kff.org/medicare/key-facts-about-medigap-enrollment-and-premiums-for-medicare-beneficiaries/</E>
                        ) suggests that approximately 40 percent of original Medicare beneficiaries have Medigap plans. CMS data show that approximately 17 percent of Medicare beneficiaries are also enrolled in Medicaid. CMS has no practical way of knowing, specifically, whether beneficiaries receiving infusion therapy are more or less likely than the overall Medicare population to have non-Medicare insurance that limits the impact of Medicare cost sharing. For purposes of estimating regulatory impact, we assume that approximately one-third of beneficiaries receiving patisiran would not consider home infusion because of the higher cost sharing. Of the remainder, we estimate that approximately 50 percent may not switch to home infusion, either because they prefer to receive it in an outpatient setting or because, in consultation with their medical providers, they have concluded that home infusion is not 
                        <PRTPAGE P="41316"/>
                        appropriate for them. Therefore, we estimate that roughly one-third of beneficiaries receiving patisiran would switch to home infusion therapy, although there is substantial uncertainty associated with this estimate. Based on this estimate of the number who might switch, and the savings to Medicare of $31,000 per beneficiary who switches, we estimate initial aggregate savings to the Medicare program would be approximately $800 thousand per year.
                    </P>
                    <P>We note that many Medicare beneficiaries have chosen to receive their Medicare benefits through Part C (Medicare Advantage). The differences in cost sharing discussed here apply strictly to those who have chosen original Medicare (Parts A and B). Medicare Advantage plans set their own cost sharing policies, and we have no way to estimate whether and how these changes in coverage for home infusion therapy would lead Medicare Advantage plans to change their policies and the cost sharing beneficiaries may face in different settings.</P>
                    <P>We also note that, by definition, infusion drugs that were not previously covered by Part B in the home infusion setting would have been covered by Part D. However, the drugs that are covered by this new benefit require infusion under the supervision of a medical professional, and the service charges related to such supervised infusion, together with rental of the infusion equipment, would not have previously been payable under Part B or Part D. Therefore, we do not believe that a significant number of beneficiaries would be switching from Part D coverage to this new benefit under Part B, given the significant out of pocket payments that would have been required.</P>
                    <HD SOURCE="HD3">7. DMEPOS Competitive Bidding—Country of Origin</HD>
                    <P>As explained earlier, for the DMEPOS CBP, we are proposing to revise the collection currently approved under OMB Control Number 0938-1408 (CMS-10744) to collect from DMEPOS Competitive Bidding contract suppliers the country of origin for the lead items furnished during the DMEPOS CBP contract's period of performance.</P>
                    <P>Specifically, contract suppliers under a DMEPOS CBP contract will continue to be required as a term of their contracts to maintain the accuracy of the product information (manufacturer name, model name, and model number) for the lead item the supplier furnishes on Form C, and would now be required to also include the country of origin for each product it reports on a new “country of origin” field on Form C. Contract suppliers are required to submit Form C once every 6 months during January and July throughout the DMEPOS Competitive Bidding Program Contract's period of performance, and Form C includes an attestation that all the reported information is accurate and up to date. This attestation would need to be completed to fulfill a Form C submission requirement. The details for this update to Form C would be included in advance of the required reporting through an updated CMS-1074.</P>
                    <P>As done historically with the product information reported on Form C by a contract supplier, the reported country of origin information would be populated on the Medicare Supplier Directory for the contract supplier during the contract period of performance. This information would allow beneficiaries and interested parties to learn the country from which the DMEPOS item originated, if interested.</P>
                    <P>Contract suppliers should be able to identify the country of origin based on the markings on the product for the lead item. Under US Customs and Border Protections rules, imported goods must be properly marked with: “Made in [Country],” unless an exemption applies (for example, an item that is incapable of being marked, like a catheter), as explained at 19 CFR 134.32. To correctly identify the country of origin for a product in the absence of a marking or to verify a marking, contract suppliers may need to refer to available documentation from the manufacturer or distributor indicating the country of origin for its product, which could include a combination of the following: manufacturer certifications, bills of materials, manufacturing process descriptions, commercial invoices, U.S. Customs and Border Protection entry documentation, or a Harmonized Tariff Schedule classification.</P>
                    <HD SOURCE="HD2">D. Regulatory Review Cost Estimation</HD>
                    <P>If regulations impose administrative costs on private entities, such as the time needed to read and interpret this rule, we should estimate the cost associated with regulatory review. Due to the uncertainty involved with accurately quantifying the number of entities that will review the rule, we assume that the total number of unique commenters on last year's proposed rule will be the number of reviewers of this proposed rule. We acknowledge that this assumption may understate or overstate the costs of reviewing this rule. It is possible that not all commenters reviewed last year's rule in detail, and it is also possible that some reviewers chose not to comment on the proposed rule. For these reasons we thought that the number of past commenters would be a fair estimate of the number of reviewers of this rule. We welcome any comments on the approach used in estimating the number of entities reviewing this proposed rule.</P>
                    <P>
                        We recognize that different types of entities are in many cases affected by mutually exclusive sections of this proposed rule. Therefore, for the purposes of our estimate we assume that each reviewer reads approximately 50 percent of the rule. Finally, in our estimates, we have used the 347 number of timely pieces of correspondence on the CY 2026 HH PPS proposed rule as our estimate for the number of reviewers of this rule. We continue to acknowledge the uncertainty involved with using this number, but we believe it is a fair estimate due to the variety of entities affected and the likelihood that some of them choose to rely (in full or in part) on press releases, newsletters, fact sheets, or other sources rather than the comprehensive review of preamble and regulatory text. We seek comments on this assumption. Using the median hourly wage information from the BLS for medical and health service managers (Code 11-9111), we estimate that the cost of reviewing the proposed rule is $96.36 per hour, including overhead and fringe benefits (
                        <E T="03">https://www.bls.gov/oes/current/oes_nat.htm</E>
                        ). Assuming an average reading speed, we estimate that it would take approximately 2.77 hours for the staff to review half of this proposed rule. For each entity that reviews this proposed rule, the estimated cost is $266.92 (2.77 hours × $96.36). Therefore, we estimate that the total cost of reviewing this proposed rule is $92,621 ($266.92 × 347 reviewers).
                    </P>
                    <HD SOURCE="HD2">E. Alternatives Considered</HD>
                    <HD SOURCE="HD3">1. HH PPS</HD>
                    <P>
                        In section II.C.1.e. of this proposed rule, we describe that to achieve budget neutrality as required by law, we calculated an illustrative permanent adjustment by determining what the 30-day base payment amount should have been in CYs 2020, 2021, 2022, 2023, 2024, and 2025 in order to achieve the same estimated aggregate expenditures as obtained from the simulated 60-day episodes as required by statute. We proposed not implementing a permanent adjustment to the CY 2027 30-day base payment rate. One alternative to not proposing a permanent adjustment included proposing a −1.024 percent permanent adjustment for CY 2027 if we could 
                        <PRTPAGE P="41317"/>
                        show that the observed behavior changes in CY 2025 claims could be directly attributed to the implementation of the PDGM as we discussed in the CY 2026 final rule (90 FR 55366 through 55367). However, we continue to believe that implementing a permanent adjustment would not be appropriate because our analysis suggests that the majority of the behavior change related to the implementation of the PDGM occurred in CYs 2020 through 2022 and that the behavior change observed in CYs 2023 through 2025 is related to factors other than the implementation of the PDGM.
                    </P>
                    <P>We are proposing to implement a temporary adjustment to continue reconciling retrospective overpayments from CYs 2020, 2021, 2022, 2023, 2024 and 2025, as discussed in section II.C.1.f. of this proposed rule. Section 1895(b)(3)(D)(iii) of the Act gives CMS the authority to make a temporary adjustment in a time and manner appropriate through notice and comment rulemaking.</P>
                    <P>We considered not proposing implementing a temporary adjustment. However, due to the growing temporary adjustment amount calculated from CYs 2020 through 2025, to delay the implementation of a temporary adjustment would lead to many more years of reductions to the payment rate to reach budget neutrality. Another alternative would be to apply a temporary adjustment factor to the CY 2027 payment rate that would recoup the full calculated temporary adjustment dollar amount, to date, of $4.9 billion. However, we believe that applying a temporary adjustment factor accounting for the temporary adjustment dollar amount of $4.9 billion to the CY 2027 payment rate may adversely affect HHAs given the magnitude of this adjustment to the payment rate in a single year. Although we are not establishing a timeframe to recoup the calculated temporary adjustment dollar amount of $4.9 billion (to date), we believe it is prudent to continue implementing an adjustment to account for some of this amount to slow its continued growth. Postponing any collection of this large dollar amount would lead to an extended duration of temporary adjustments or larger reductions to the payment rates in future years to reach budget neutrality sooner.</P>
                    <P>Therefore, we believe it is best to propose implementing a temporary adjustment decrease of 3.0 percent to the CY 2027 base payment rate.</P>
                    <HD SOURCE="HD3">2. HH QRP</HD>
                    <P>With regard to the proposal to revise the HH QRP assessment data submission deadline from 4.5 months to no later than the 15th day of the second month after the end of each quarter, we considered keeping the deadline unchanged. We determined that the revised timeframe is a reasonable amount of time for HHAs to submit data and make any necessary corrections, and that the benefits of this shortened timeframe include making the data timelier and more actionable which increases the value of publicly reported data both for consumers and their families and for HHAs to use in their quality improvement activities.</P>
                    <P>With regard to the proposal to revise the HH QRP OASIS and HHCAHPs annual payment update (APU) reporting timeframe to report a calendar year of data (January 1 through December 31), we believe this update will provide clarity to HH payment updates and facilitate the alignment of the HH QRP pay-for-reporting policies with other HH payment policies without adding burden to providers.</P>
                    <HD SOURCE="HD3">3. Provider Enrollment</HD>
                    <P>There were two principal alternatives we considered. First, we considered retaining the existing prospective effective dates for some of our revocation grounds. However, as explained in section V.C. of this proposed rule, we do not believe that providers are entitled to payment for services and items furnished while non-compliant. Second, and in a similar vein, we contemplated adding no more than a few denial grounds as bases for a reapplication bar. Yet because of the concerning provider conduct behind some denials, we believe we must have the discretion to bar such providers from repeatedly attempting to enter Medicare by submitting multiple applications.</P>
                    <HD SOURCE="HD3">4. DMEPOS Competitive Bidding—Country of Origin</HD>
                    <P>We considered having all DMEPOS suppliers submit the country of information for their product at the time they submit a bid for the DMEPOS CBP, instead of first submitting it on day one of their DMEPOS CBP contract, if awarded. However, this would have presented two issues. First, because the purpose is to make the country of origin available to beneficiaries and interested parties on the Supplier Directory, it would be unnecessary to require all bidders to submit this information at the time they submit a bid when only a subset of bidders will ultimately receive a DMEPOS CBP contract (and have its information available on the Supplier Directory). Secondly, we believe it would be unnecessary to require this information at the time of bid submission, approximately 1 year before contracts are awarded, as it would not be used in the bid evaluation process. As a result, we believe it is most appropriate that only contract suppliers be required on a routine basis to submit accurate and up-to-date country of origin information for its products on Form C.</P>
                    <HD SOURCE="HD2">F. Accounting Statement and Table</HD>
                    <P>
                        Consistent with OMB Circular A-4 (available at 
                        <E T="03">https://www.whitehouse.gov/wp-content/uploads/2025/08/CircularA-4.pdf</E>
                        ) in table 38, we have prepared an accounting statement showing the classification of the impacts associated with the provisions of this proposed rule.
                    </P>
                    <GPH SPAN="3" DEEP="226">
                        <PRTPAGE P="41318"/>
                        <GID>EP06JY26.082</GID>
                    </GPH>
                    <HD SOURCE="HD2">G. Regulatory Flexibility Act (RFA)</HD>
                    <P>The RFA requires agencies to analyze options for regulatory relief of small entities, if a rule has a significant impact on a substantial number of small entities. For purposes of the RFA, small entities include small businesses, nonprofit organizations, and small governmental jurisdictions. In addition, HHAs are small entities, as that is the term used in the RFA. Individuals and States are not included in the definition of a small entity.</P>
                    <P>
                        The North American Industry Classification System (NAICS) was adopted in 1997 and is the current standard used by the Federal statistical agencies related to the U.S. business economy. We utilized the NAICS U.S. industry title “Home Health Care Services” and corresponding NAICS code 621610 in determining impacts for small entities. The NAICS code 621610 has a size standard of 19 million 
                        <SU>42</SU>
                        <FTREF/>
                         and approximately 96 percent of HHAs are considered small entities. We estimate that almost all home infusion therapy suppliers are, similarly, small entities. Table 39 shows the number of firms, revenue, and average revenue per firm for the home health care services category (NAICS 621610). Table 40 shows the number of nonemployer establishments, total, and average revenue per nonemployer establishment.
                    </P>
                    <FTNT>
                        <P>
                            <SU>42</SU>
                             
                            <E T="03">https://www.sba.gov/sites/sbagov/files/2023-03/Table%20of%20Size%20Standards_Effective%20March%2017%2C%202023.xlsx</E>
                            .
                        </P>
                    </FTNT>
                    <GPH SPAN="3" DEEP="262">
                        <PRTPAGE P="41319"/>
                        <GID>EP06JY26.083</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="156">
                        <GID>EP06JY26.084</GID>
                    </GPH>
                    <P>The economic impact assessment is based on estimated Medicare payments (revenues) and HHS's practice in interpreting the RFA is to consider effects economically “significant” only if greater than 5 percent of providers reach a threshold of 3 to 5 percent or more of total revenue or total costs. The majority of HHAs' visits are Medicare paid visits and therefore the majority of HHAs' revenue consists of Medicare payments. Based on our analysis, we conclude that the policies proposed in this rule would result in an estimated total impact of 3 to 5 percent or more on Medicare revenue for greater than 5 percent of HHAs. Therefore, the Secretary has determined that the payment policies in this proposed HH PPS rule would have a significant positive economic impact on a substantial number of small entities.</P>
                    <P>
                        Specifically, we estimate that the net impact of the payment policies in this proposed rule would be a positive 2.4 percent impact in the aggregate for CY 2027 or approximately $420 million. As discussed in the preamble, the net increase in CY 2027 is mostly driven by the impact of the proposed CY 2027 home health payment update percentage and proposed updated FDL. Table 36 details the total percentage payment increase by number of 30-day periods and impact by facility type, size, and location. As shown in table 36, when examining the distribution of projected payment impacts across individual agency groups, a substantial share of HHAs are projected to receive a payment increase of 3 percent or more. For example, agencies in the New England (299 agencies, 3.0 percent), Mid-Atlantic (360 agencies, 3.6 percent), Pacific (2,880 agencies, 3.0 percent), and outlying (44 agencies, 3.6 percent) census regions alone account for approximately 3,583 agencies. This represents roughly 36 percent of all 9,975 HHAs which are each projected to receive a total payment impact of at least 3.0 percent. Additional groups projected to receive impacts of 3 percent or more include free-standing/other government (97 agencies, 3.4 percent), facility-based proprietary (20 agencies, 3.4 percent), facility-based government (159 agencies, 3.7 percent), and several rural and urban facility subcategories. Collectively, these groups confirm that more than 5 percent of HHAs are projected to experience a payment impact of 3 percent or more. We estimate that smaller HHAs (those with less than 100 periods of care and thereby lower overall revenues) would 
                        <PRTPAGE P="41320"/>
                        receive a 2.9 percent payment impact in CY 2027. Also, we estimate that larger HHAs (those with more than 1,000 periods of care and thereby higher overall revenues) would receive a 2.3 percent payment impact in CY 2027. We estimate that HHAs located in the Mid-Atlantic and outlying regions would receive the largest impact reflecting a 3.6 percent payment impact. The East South Central and West South Central region would receive the lowest impact reflecting a 1.7 percent increase.
                    </P>
                    <P>In summary, the payment policies in this proposed rule would increase Medicare payments to home health agencies, with small agencies receiving a slightly larger percentage increase than large ones. We solicit comments on this RFA analysis on small entities.</P>
                    <P>Regarding options for regulatory relief, we note that section 1895(b)(3)(D)(i) of the Act requires CMS to annually determine the impact of differences between the assumed behavior changes finalized in the CY 2019 HH PPS final rule with comment period (83 FR 56455) and actual behavior changes on estimated aggregate expenditures under the HH PPS with respect to years beginning with 2020 and ending with 2026. Additionally, section 1895(b)(3)(D)(ii) and (iii) of the Act requires us to make permanent and temporary adjustments to the payment rate to offset for such increases or decreases in estimated aggregate expenditures through notice and comment rulemaking.While our analysis of claims suggests that the majority of the behavior change related to the implementation of the PDGM occurred in CYs 2020 through 2022 and that the behavior change observed in CYs 2023 through 2025 is related to factors other than the implementation of the PDGM, we determined that it was not necessary to propose implementing a permanent adjustment because we do not consider behavior changes directly attributed to the implementation of PDGM We include the calculations described in section II.C.1.f. of this proposed rule to illustrate the impact of differences between the assumed behavior changes and actual behavior changes if such behaviors were attributable to the implementation of the PDGM. We note that the law requires us to annually calculate the impact of differences between the assumed behavior changes and actual behavior changes through 2026 claims. We will also continue to reprice claims, per the finalized methodology, and make any additional adjustments at a time and manner deemed appropriate in future rulemaking.</P>
                    <P>As discussed previously in the Alternatives Considered section of this proposed rule, we explored alternatives to the proposed 3.0 percent temporary adjustment including proposing a temporary adjustment factor to the CY 2027 payment rate that would recoup the full calculated temporary adjustment dollar amount, to date, of $4.9 billion. However, we believe that applying a temporary adjustment factor accounting for the temporary adjustment dollar amount of $4.9 billion to the CY 2027 payment rate may adversely affect HHAs given the magnitude of this adjustment to the payment rate in a single year. We solicit comments on the overall HH PPS RFA analysis.</P>
                    <P>This rule does not affect health care enterprises operated by small government entities such as counties or towns with populations 50,000 or less. HHS generally uses a revenue impact of 3 to 5 percent as a significance threshold under the RFA. The RFA threshold analysis, therefore, indicates that there is not a significant economic impact on a substantial number of small entities. Furthermore, the regulation review costs mentioned previously, is de minimis and will not impose any additional burden on these small businesses. The statement of need for the various proposed policies in this rule is discussed in section VII.A. of the proposed rule. Additionally, the alternatives considered for the various proposed policies in this rule are discussed in section VII.E. of the proposed rule. We considered potential alternatives for the policies proposed in this rule, including routine technical rate-setting updates and temporary adjustment. The home health payment update percentage is established annually in accordance with existing statutory requirements of section 1895(b) of the Act. We maintain that limiting the application of the permanent adjustment to analysis of data from CYs 2020 through 2022 continues to be the most accurate application of the law. The data continues to show minimal changes that could be attributed to the PDGM implementation after CY 2022 by a large proportion of home health providers. We also continue to acknowledge the difficulty in attributing any behavior change occurring from CYs 2023 through 2025 directly to the PDGM implementation and its effects on expenditures from the other changes occurring in those years. After completing the analysis required by law, we determined that it was not necessary to apply a permanent adjustment. For the temporary adjustment, we explored alternatives to delay, reduce, or increase the temporary adjustments; however, this would delay progress on the BBA of 2018 requirement and may adversely affect HHAs if reductions to the payment rate are too high in a single year. The proposed policy is expected to increase revenue for small HHAs. Therefore, the Secretary has determined that this proposed HH PPS rule would have a significant positive economic impact on a substantial number of small entities.</P>
                    <P>In addition, section 1102(b) of the Act requires us to prepare an RIA if a rule may have a significant impact on the operations of a substantial number of small rural hospitals. This analysis must conform to the provisions of section 603 of the RFA. For purposes of section 1102(b) of the Act, we define a small rural hospital as a hospital that is located outside of a Metropolitan Statistical Area for Medicare payment regulations and has fewer than 100 beds. We are not preparing an analysis for section 1102(b) of the Act because we have determined, and the Secretary certifies, that this proposed rule will not have a significant impact on the operations of a substantial number of small rural hospitals.</P>
                    <P>Executive Order 13132 establishes certain requirements that an agency must meet when it promulgates a proposed rule (and subsequent final rule) that imposes substantial direct requirement costs on State and local governments, preempts State law, or otherwise has Federalism implications. Since this regulation does not impose any costs on State or local governments, the requirements of Executive Order 13132 are not applicable.</P>
                    <HD SOURCE="HD2">H. Unfunded Mandates Reform Act (UMRA)</HD>
                    <P>Section 202 of UMRA of 1995 UMRA also requires that agencies assess anticipated costs and benefits before issuing any rule whose mandates require spending in any 1 year of $100 million in 1995 dollars, updated annually for inflation. In 2026, that threshold is approximately $193 million. This proposed rule would not impose a mandate that will result in the expenditure by State, local, and Tribal governments, in the aggregate, or by the private sector, of more than $193 million in any 1 year.</P>
                    <HD SOURCE="HD2">I. Federalism</HD>
                    <P>
                        Executive Order 13132 establishes certain requirements that an agency must meet when it promulgates a proposed rule (and subsequent final rule) that imposes substantial direct 
                        <PRTPAGE P="41321"/>
                        requirement costs on State and local governments, preempts State law, or otherwise has Federalism implications. We have reviewed this proposed rule under these criteria of Executive Order 13132 and have determined that it would not impose substantial direct costs on State or local governments.
                    </P>
                    <HD SOURCE="HD2">J. Unleashing Prosperity Through Deregulation</HD>
                    <P>Executive Order 14192, titled “Unleashing Prosperity Through Deregulation” was issued on January 31, 2025, and requires that “any 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”</P>
                    <HD SOURCE="HD2">K. Conclusion</HD>
                    <P>In conclusion, we estimate that the provisions in this proposed rule would result in an estimated net increase in home health payments of 2.4 percent for CY 2027 ($420 million). The $420 million increase in estimated payments for CY 2027 reflects the effects of the proposed CY 2027 home health payment update percentage increase of 2.1 percent ($370 million increase), and an estimated 0.3 percent increase that reflects the effects of an updated FDL ($50 million).</P>
                    <HD SOURCE="HD1">VII. Response to Comments</HD>
                    <P>
                        Because of the large number of public comments we normally receive on 
                        <E T="04">Federal Register</E>
                         documents, we are not able to acknowledge or respond to them individually. We will consider all comments we receive by the date and time specified in the 
                        <E T="02">DATES</E>
                         section of this preamble, and, when we proceed with a subsequent document, we will respond to the comments in the preamble to that document.
                    </P>
                    <P>Mehmet Oz, Administrator of the Centers for Medicare &amp; Medicaid Services, approved this document on July 1, 2026.</P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects</HD>
                        <CFR>42 CFR Part 405</CFR>
                        <P>Administrative practice and procedure, Diseases, Health facilities, Health professions, Medical devices, Medicare, Reporting and recordkeeping requirements, Rural areas, X-rays.</P>
                        <CFR>42 CFR Part 410</CFR>
                        <P>Diseases, Health facilities, Health professions, Laboratories, Medicare, Reporting and recordkeeping requirements, Rural areas, X-rays.</P>
                        <CFR>42 CFR Part 414</CFR>
                        <P>Administrative practice and procedure, Biologics, Diseases, Drugs, Health facilities, Health professions, Medicare, Reporting and recordkeeping requirements.</P>
                        <CFR>42 CFR Part 422</CFR>
                        <P>Administrative practice and procedure, Health facilities, Health maintenance organizations (HMO), Medicare, Penalties, Privacy, Reporting and recordkeeping requirements.</P>
                        <CFR>42 CFR Part 423</CFR>
                        <P>Administrative practice and procedure, Emergency medical services, Health facilities, Health maintenance organizations (HMO), Health professionals, Incorporation by reference, Medicare, Penalties, Privacy, Reporting and recordkeeping requirements.</P>
                        <CFR>42 CFR Part 424</CFR>
                        <P>Emergency medical services, Health facilities, Health professions, Medicare, Reporting and recordkeeping requirements.</P>
                        <CFR>42 CFR Part 484</CFR>
                        <P>Health facilities, Health professions, Medicare, Reporting and recordkeeping requirements.</P>
                        <CFR>42 CFR Part 498</CFR>
                        <P>Administrative practice and procedure, Health facilities, Health professions, Medicare, Reporting and recordkeeping requirements.</P>
                    </LSTSUB>
                    <P>For the reasons set forth in the preamble, the Centers for Medicare &amp; Medicaid Services proposes to amend 42 CFR parts 405, 410, 414, 422, 423, 424, 484, and 498 as set forth below:</P>
                    <PART>
                        <HD SOURCE="HED">PART 405—FEDERAL HEALTH INSURANCE FOR THE AGED AND DISABLED</HD>
                    </PART>
                    <AMDPAR>X. The authority for part 405 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>42 U.S.C. 263a, 405(a), 1302, 1320b-12, 1395x, 1395y(a), 1395ff, 1395hh, 1395kk, 1395rr, and 1395ww(k).</P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 405.400 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>X. Section 405.400 is amended in the definition of “opt-out period” by removing the phrase “the date the affidavit is signed” and adding in its place the phrase “the date the first submitted affidavit is signed”.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 405.450 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>X. Section 405.450 is amended in paragraph (a) by removing the phrase “renew opt-out” and adding in its place the phrase “cancel automatic renewal”.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 405.800 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>X. Section 405.800 is amended by removing the term “certified mail” and adding in its place the phrase “certified mail or email” in paragraphs (a), (b)(1), and (c)(1).</AMDPAR>
                    <AMDPAR>X. Section 405.809 is amended as follows:</AMDPAR>
                    <AMDPAR>a. Revising the section heading and paragraph (a)(1);</AMDPAR>
                    <AMDPAR>b. In paragraph (a)(2), removing the term “revocation” and adding in its place the phrase “denial or revocation”;</AMDPAR>
                    <AMDPAR>c. In paragraph (b)(1) introductory text, removing the term “Reinstates” and adding in its place the phrase “Approves or reinstates”;</AMDPAR>
                    <AMDPAR>d. Revising paragraph (b)(1)(i);</AMDPAR>
                    <AMDPAR>e. In paragraph (b)(1)(ii), removing the term “reinstatement” and adding in its place the phrase “approval or reinstatement”;</AMDPAR>
                    <AMDPAR>f. In paragraph (b)(2), removing the term “reinstate” and adding in its place the phrase “approve or reinstate”.</AMDPAR>
                    <P>The revisions are as follows:</P>
                    <SECTION>
                        <SECTNO>§ 405.809 </SECTNO>
                        <SUBJECT> Granting or reinstatement of provider or supplier billing privileges following corrective action.</SUBJECT>
                        <P>(a)(1) May only submit a corrective action plan for a denial or revocation for non-compliance under §§ 424.530(a)(1) or 424.535(a)(1) of this chapter; and</P>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>(1) * * *</P>
                        <P>(i) The effective date of the—</P>
                        <P>(A) Approval is based on the applicable timeframes described in §§ 424.520 and 424.521; and</P>
                        <P>(B) Reinstatement is based on the date the provider or supplier is in compliance with all Medicare requirements.</P>
                        <STARS/>
                    </SECTION>
                    <PART>
                        <HD SOURCE="HED">PART 410—SUPPLEMENTARY MEDICAL INSURANCE (SMI) BENEFITS</HD>
                        <AUTH>
                            <HD SOURCE="HED">Authority: </HD>
                            <P>42 U.S.C. 1302, 1395m, 1395hh, 1395rr, and 1395ddd.</P>
                        </AUTH>
                    </PART>
                    <AMDPAR>X. Section 410.33 is amended by revising paragraph (g)(14)(ii) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 410.33 </SECTNO>
                        <SUBJECT>Independent diagnostic testing facility.</SUBJECT>
                        <STARS/>
                        <P>(g) * * *</P>
                        <P>(14) * * *</P>
                        <P>
                            (ii) Maintain a permanent visible sign in plain view and posts hours of operation. If the IDTF's place of business is located within a building complex, the sign must be visible at the main entrance of the building or the 
                            <PRTPAGE P="41322"/>
                            hours can be posted at the entrance of the IDTF.
                        </P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>X. Section 410.38 is amended by adding paragraph (d)(2)(iii) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 410.38 </SECTNO>
                        <SUBJECT>Durable medical equipment, prosthetics, orthotics and supplies (DMEPOS): Scope and conditions.</SUBJECT>
                        <STARS/>
                        <P>(d) * * *</P>
                        <P>(2) * * *</P>
                        <P>(iii)(A) For purposes of § 410.38(d), replacement item means an item identified by the same Healthcare Common Procedure Coding System (HCPCS) code as the original item, that has been—</P>
                        <P>
                            (
                            <E T="03">1</E>
                            ) In continuous use by the same beneficiary and is at the end of its reasonable useful lifetime; or
                        </P>
                        <P>
                            (
                            <E T="03">2</E>
                            ) Lost, stolen, or irreparably damaged.
                        </P>
                        <P>(B) Items ordered as replacement items do not require a new face-to-face encounter. All other requirements specified in § 410.38 continue to apply.</P>
                        <STARS/>
                    </SECTION>
                    <PART>
                        <HD SOURCE="HED">PART 414—PAYMENT FOR PART B MEDICAL AND OTHER HEALTH SERVICES</HD>
                    </PART>
                    <AMDPAR>X. The authority citation for part 414 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P> 42 U.S.C. 1302, 1395hh, and 1395rr(b)(l).</P>
                    </AUTH>
                    <AMDPAR>X. Section 414.202 is amended by revising the definition of “Durable medical equipment” to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 414.202 </SECTNO>
                        <SUBJECT> Definitions.</SUBJECT>
                        <STARS/>
                        <P>
                            <E T="03">Durable medical equipment</E>
                             means:
                        </P>
                        <P>(1) Equipment, furnished by a supplier or a home health agency that meets the following conditions:</P>
                        <P>(i) Can withstand repeated use.</P>
                        <P>(ii) Effective with respect to items classified as DME after January 1, 2012, has an expected life of at least 3 years.</P>
                        <P>(iii) Is primarily and customarily used to serve a medical purpose.</P>
                        <P>(iv) Generally is not useful to an individual in the absence of an illness or injury.</P>
                        <P>(v) Is appropriate for use in the home except as provided in paragraph (2) of this definition.</P>
                        <P>(2) On or after April 1, 2027, an external infusion pump that meets all conditions in paragraphs (1)(i) through (iv) of this definition provided that the following criteria are satisfied:</P>
                        <P>(i) The prescribing information approved by the FDA for the home infusion drug (as defined in § 486.505) associated with the pump instructs that the drug should be administered by or under the supervision of a health care professional.</P>
                        <P>(A) The health care professional must be one of the following:</P>
                        <P>
                            (
                            <E T="03">1</E>
                            ) A registered nurse licensed to practice nursing in the State in which the home infusion drug is administered.
                        </P>
                        <P>
                            (
                            <E T="03">2</E>
                            ) A clinical nurse specialist as defined in section 1861(aa)(5) of the Act.
                        </P>
                        <P>
                            (
                            <E T="03">3</E>
                            ) Nurse practitioner as defined in section 1861(aa)(5) of the Act.
                        </P>
                        <P>
                            (
                            <E T="03">4</E>
                            ) Physician assistant as defined in section 1861(aa)(5) of the Act.
                        </P>
                        <P>
                            (
                            <E T="03">5</E>
                            ) A physician as defined in section 1861(r) of the Act; and
                        </P>
                        <P>(B) The health care professional must be on site at the home to administer or supervise the administration of the home infusion drug.</P>
                        <P>(ii) A qualified home infusion therapy supplier (as defined in § 486.505) administers or supervises the administration of the home infusion drug in a safe and effective manner in the patient's home (as defined in § 486.505).</P>
                        <P>(iii) The prescribing information instructs that the home infusion drug be infused at least 12 times per year (at least once a month)—</P>
                        <P>(A) Either intravenously or subcutaneously; or</P>
                        <P>(B) At infusion rates that the Secretary determines would require the use of an external infusion pump.</P>
                        <STARS/>
                    </SECTION>
                    <PART>
                        <HD SOURCE="HED">PART 422—MEDICARE ADVANTAGE PROGRAM</HD>
                    </PART>
                    <AMDPAR>X. The authority continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>42 U.S.C. 1302, 1306, 1395w-21 through 1395w-28, and 1395hh.</P>
                    </AUTH>
                    <AMDPAR>X. Section 422.2 is amended by revising paragraph (3) introductory text for the definition of “Preclusion list” to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 422.2 </SECTNO>
                        <SUBJECT> Definitions.</SUBJECT>
                        <STARS/>
                        <P>
                            <E T="03">Preclusion list</E>
                             * * *
                        </P>
                        <P>(3) The individual or entity—or any owner, managing employee, managing organization, officer, or director thereof (as those terms are defined in § 424.502)—regardless of whether they are or were enrolled in Medicare, has been convicted of a felony under Federal or State law within the previous 10 years that CMS deems detrimental to the best interests of the Medicare program. Factors that CMS considers in making such a determination under this paragraph (3) are—</P>
                        <STARS/>
                    </SECTION>
                    <PART>
                        <HD SOURCE="HED">PART 423—VOLUNTARY MEDICARE PRESCRIPTION DRUG BENEFIT</HD>
                    </PART>
                    <AMDPAR>X. The authority citation continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P> 42 U.S.C. 1302, 1306, 1395w-101 through 1395w-152, and 1395hh.</P>
                    </AUTH>
                    <AMDPAR>X. Section 423.100 is amended by revising paragraph (3) introductory text for the definition of “Preclusion list” to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 423.100 </SECTNO>
                        <SUBJECT> Definitions.</SUBJECT>
                        <STARS/>
                        <P>
                            <E T="03">Preclusion list</E>
                             * * *
                        </P>
                        <P>(3) The prescriber—or any owner, managing employee, managing organization, officer, or director thereof (as those terms are defined in § 424.502)—regardless of whether they are or were enrolled in Medicare, has been convicted of a felony under Federal or State law within the previous 10 years that CMS deems detrimental to the best interests of the Medicare program. Factors that CMS considers in making such a determination under this paragraph (3) are—</P>
                        <STARS/>
                    </SECTION>
                    <PART>
                        <HD SOURCE="HED">PART 424—CONDITIONS FOR MEDICARE PAYMENT</HD>
                    </PART>
                    <AMDPAR>X. The authority for part 424 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>42 U.S.C. 1302 and 1395hh.</P>
                    </AUTH>
                    <AMDPAR>X. Section 424.58 is amended by—</AMDPAR>
                    <AMDPAR>
                        a. Revising paragraph (c)(1)(vii)(D)(
                        <E T="03">4</E>
                        );
                    </AMDPAR>
                    <AMDPAR>b. In paragraph (c)(1)(xxiii)(D), removing the phrase “3 business days” and adding in its place the phrase “5 calendar days”;</AMDPAR>
                    <AMDPAR>c. Redesignating paragraph (c)(1)(xxiii)(N) as paragraph (c)(1)(xxiii)(O); and</AMDPAR>
                    <AMDPAR>d. Adding new paragraph (c)(1)(xxiii)(N).</AMDPAR>
                    <P>The revision and addition read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 424.58 </SECTNO>
                        <SUBJECT> Accreditation.</SUBJECT>
                        <STARS/>
                        <P>(c) * * *</P>
                        <P>(1) * * *</P>
                        <P>(vii) * * *</P>
                        <P>(D) * * *</P>
                        <P>
                            <E T="03">(4)</E>
                             For notifying CMS when a conflict of interest is discovered. This includes disclosing to CMS all conflicts of interest (as defined in § 424.58(c)(1)(vii)(D)(
                            <E T="03">5</E>
                            )) it currently has and explaining how and when it will terminate them.
                        </P>
                        <STARS/>
                        <P>(xxiii) * * *</P>
                        <P>
                            (N) Agrees to notify CMS in writing (and, if applicable, notify other law enforcement) of suspected fraud, waste, 
                            <PRTPAGE P="41323"/>
                            or abuse—consistent with the accrediting organization's CMS-approved definitions of those terms per paragraph (c)(1)(xxii) of this section—within 3 calendar days of the date on which the accrediting organization determines that fraud, waste, or abuse may have occurred.
                        </P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>X. Section 424.502 is amended by—</AMDPAR>
                    <AMDPAR>a. In the definition of “Affiliation”—</AMDPAR>
                    <AMDPAR>i. Republishing the introductory text;</AMDPAR>
                    <AMDPAR>ii. Revising paragraph (3); and</AMDPAR>
                    <AMDPAR>iii. Adding new paragraph (6);</AMDPAR>
                    <AMDPAR>b. In the definition of “Final adverse action”;</AMDPAR>
                    <AMDPAR>i. Republishing the introductory text; and</AMDPAR>
                    <AMDPAR>ii. Adding new paragraph (6);</AMDPAR>
                    <AMDPAR>c. Revising paragraph (1) of the definition of “Managing employee”; and</AMDPAR>
                    <AMDPAR>d. Revising the definition of “Operational”</AMDPAR>
                    <P>The additions and revisions are as follows:</P>
                    <SECTION>
                        <SECTNO>§ 424.502 </SECTNO>
                        <SUBJECT>Definitions.</SUBJECT>
                        <STARS/>
                        <P>
                            <E T="03">Affiliation</E>
                             means, for purposes of applying § 424.519, any of the following:
                        </P>
                        <STARS/>
                        <P>(3) An interest in which an individual or entity—or any of its owning or managing employees or organizations—exercises operational or managerial control over, or directly or indirectly conducts, the day-to-day operations of another organization (including, for purposes of this paragraph (3), sole proprietorships), either under contract or through some other arrangement, regardless of whether or not the managing individual or entity is a W-2 employee of the organization.</P>
                        <STARS/>
                        <P>(6) Any marketing, business, fulfillment, financial, managerial, or beneficiary relationship</P>
                        <STARS/>
                        <P>
                            <E T="03">Final adverse action</E>
                             means one or more of the following actions—
                        </P>
                        <STARS/>
                        <P>
                            (6) 
                            <E T="03">Misdemeanor conviction.</E>
                             A conviction of a Federal or State misdemeanor related to sexual assault or financial misconduct within the past 10 years preceding enrollment, revalidation or reenrollment.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Managing employee</E>
                             means—
                        </P>
                        <P>(1) A general manager, business manager, administrator, director, or other individual that exercises operational or managerial control over, or who directly or indirectly conducts, the day-to-day operation of the provider or supplier, either under contract or through some other arrangement, whether or not the individual is a W-2 employee of the provider or supplier. For purposes of this definition, this includes not only a hospice or skilled nursing facility administrator and a hospice or skilled nursing facility medical director but also any of the following:</P>
                        <P>(i) Medical directors other than skilled nursing facility and hospice medical directors.</P>
                        <P>(ii) Clinical directors.</P>
                        <P>(iii) Departmental heads (for example, a hospital's chief of cardiology).</P>
                        <P>(iv) Supervising physicians (not simply those at independent diagnostic testing facilities).</P>
                        <P>(v) Nursing directors.</P>
                        <P>(vi) Alternate administrators.</P>
                        <P>(vii) All other clinical personnel not listed in paragraphs (1)(i) through (vi) of this definition who meet the “managing employee” definition.</P>
                        <STARS/>
                        <P>
                            <E T="03">Operational</E>
                             means (as applicable, based on the type of facility or organization, provider or supplier specialty, or the services or items being rendered) the provider or supplier meets all of following requirements:
                        </P>
                        <P>(1) Has a qualified practice location.</P>
                        <P>(2) Is open to the public for the purpose of providing health care related services, which includes, but is not limited to, all of the following:</P>
                        <P>(i) The provider's or supplier's location is fully accessible to all patients and lacks safety hazards. For purposes of this paragraph (2)(i), accessible means—</P>
                        <P>(A) The provider or supplier is located in an area and a building that patients can enter with reasonable ease; and</P>
                        <P>(B) The location is compliant with all federal Americans with Disabilities Act regulations and all applicable and equivalent state and local laws.</P>
                        <P>(ii) The provider's or supplier's hours of business are sufficient to regularly serve patients.</P>
                        <P>(iii) Medicare beneficiaries can contact and locate the provider's or supplier's location based on publicly available information (for example, the internet).</P>
                        <P>(3) Is prepared and able to submit valid Medicare claims.</P>
                        <P>(4) Is properly staffed, equipped, and stocked (as applicable, based on the type of facility or organization, provider or supplier specialty, or the services or items being rendered, to furnish these items or services. This includes, but is not limited to, the following:</P>
                        <P>(i) Provider or supplier staff must be qualified (such as licensed or certified if required under state law) to perform their health care-related functions.</P>
                        <P>(ii) Equipment must be functional, appropriate for the services and items the provider or supplier intends to furnish, and in sufficient quantity to provide these items and services.</P>
                        <P>(iii) Appropriate medications for the services and items the provider or supplier intends to furnish and in sufficient quantity to provide these items and services.</P>
                        <P>(5) Has adequate written policies and records regarding its operations, such as, but not limited to, procedures for patient care, patient safety, medical and patient recordkeeping, and general administration.</P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>X. Section 424.510 is amended by adding paragraph (f) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 424.510 </SECTNO>
                        <SUBJECT>Requirements for enrolling in the Medicare program.</SUBJECT>
                        <STARS/>
                        <P>
                            (f) 
                            <E T="03">Signage.</E>
                             (1) The provider or supplier must maintain a permanent visible sign in plain view and post hours of operation. If the provider's or supplier's place of business is located within a building complex, the sign must be visible at the main entrance of the building or the hours can be posted at the entrance of the provider or supplier.
                        </P>
                        <P>(2) The requirement in paragraph (f)(1) of this section does not apply if the provider or supplier—</P>
                        <P>(i) Shares office space with another provider or supplier (for example, physicians in a group practice sharing a common suite, though the group itself must have signage);</P>
                        <P>(ii) Treats patients in the patients' homes;</P>
                        <P>(iii) Treats patients in the provider's or supplier's home and only uses the provider's or supplier's address for administrative purposes.</P>
                        <P>(iv) Performs telehealth services from home.</P>
                    </SECTION>
                    <AMDPAR>X. Section 424.516 is amended by adding paragraph (f)(3) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 424.516 </SECTNO>
                        <SUBJECT>Additional provider and supplier requirements for enrolling and maintaining active enrollment status in the Medicare program.</SUBJECT>
                        <STARS/>
                        <P>(f) * * *</P>
                        <P>(3) All documentation required to be retained and furnished under this paragraph (f) must be accurate, complete, and compliant with all CMS requirements.</P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>X. Section 424.518 is amended by revising paragraph (c)(2)(ii)(A) to read as follows:</AMDPAR>
                    <SECTION>
                        <PRTPAGE P="41324"/>
                        <SECTNO>§ 424.518 </SECTNO>
                        <SUBJECT>Screening levels for Medicare providers and suppliers</SUBJECT>
                        <STARS/>
                        <P>(c) * * *</P>
                        <P>(2) * * *</P>
                        <P>(ii)(A) Using the CMS-designated fingerprinting contractor, requires the submission of a set of fingerprints for a national background check from all individuals who maintain a 5 percent or greater direct or indirect ownership interest in the provider or supplier; and</P>
                        <STARS/>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 424.519 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>X. Section 424.519 is amended in paragraph (b) by removing the phrase “has or, within the previous 5 years, had” and adding in its place the phrase “has or had”.</AMDPAR>
                    <AMDPAR>X. Section 424.530 is amended by—</AMDPAR>
                    <AMDPAR>a. Revising paragraph (a)(4); (6)(i), (ii) introductory text, (ii)(A), and (iii) introductory text; (7)(i) and (ii); (13); (14); and (16);</AMDPAR>
                    <AMDPAR>b. Adding paragraphs (a)(19) through (22);</AMDPAR>
                    <AMDPAR>c. Revising paragraph (f) introductory text;</AMDPAR>
                    <AMDPAR>d. Removing paragraphs (f)(2)(i) through (iv); and</AMDPAR>
                    <AMDPAR>e. Redesignating paragraphs (f)(3)(i) and (ii) as revised paragraphs (f)(2)(i) and (ii).</AMDPAR>
                    <P>The revisions and additions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 424.530 </SECTNO>
                        <SUBJECT>Denial of enrollment in the Medicare program.</SUBJECT>
                        <P>(a) * * *</P>
                        <P>
                            (4) 
                            <E T="03">False or misleading information.</E>
                             The provider or supplier submits false or misleading information on or associated with any CMS or Medicare provider enrollment-related form. (Offenders may be referred to the Office of Inspector General for investigation and possible criminal, civil, or administrative sanctions.) This includes but is not limited to:
                        </P>
                        <P>(i) Enrollment-related forms created by or submitted to CMS contractors;</P>
                        <P>(ii) Documentation furnished as part of the completion or submission of the CMS or Medicare enrollment-related form.</P>
                        <P>(iii) Form CMS-588 (Electronic Funds Transfer (EFT) Authorization Agreement; OMB Control Number 0938-0626).</P>
                        <P>(iv) Documents required to demonstrate compliance with HHA capitalization requirements in § 489.28.</P>
                        <P>(v) Opt-out affidavits under 42 CFR part 405, subpart D.</P>
                        <P>(vi) Letters from a provider demonstrating that a particular provider official qualifies as an authorized or delegated official under § 424.502.</P>
                        <P>(vii) Any other required or requested enrollment-related documentation.</P>
                        <STARS/>
                        <P>
                            (6) 
                            <E T="03">Medicare debt.</E>
                             (i) The enrolling provider or supplier—or any owner, managing employee, managing organization, or individual or entity with any other form of business or financial relationship with the provider or supplier (hereafter collectively “associated party” for purposes of paragraph (a)(6) of this section)—has an existing Medicare debt.
                        </P>
                        <P>(ii) The enrolling provider or supplier or associated party thereof was previously an associated party of a provider or supplier that had a Medicare debt that existed when the latter's enrollment was voluntarily terminated, involuntarily terminated, or revoked, and all of the following criteria are met:</P>
                        <P>(A) The associated party left the provider or supplier with the Medicare debt within 1 year before or after that provider or supplier's voluntary termination, involuntary termination or revocation.</P>
                        <STARS/>
                        <P>(iii) A denial of Medicare enrollment under this paragraph (a)(6) of this section can be avoided if the enrolling provider or supplier (or associated party thereof) does either of the following:</P>
                        <STARS/>
                        <P>
                            (7) 
                            <E T="03">Payment suspension.</E>
                             (i) The provider or supplier—or any owner, managing employee, managing organization, or individual or entity with any other form of business or financial relationship with the provider or supplier (hereafter collectively “associated party” for purposes of paragraph (a)(7) of this section)—is currently under a Medicare or Medicaid payment suspension as defined in §§ 405.370 through 405.372 or in § 455.23 of this chapter.
                        </P>
                        <P>(ii) CMS may apply this paragraph (a)(7) of this section to the provider or supplier under any of the provider's, supplier's, or associated party's current or former names, numerical identifiers, or business identities or to any of its existing enrollments.</P>
                        <STARS/>
                        <P>
                            (13) 
                            <E T="03">Affiliation that poses undue risk.</E>
                             CMS determines that the provider or supplier—or any of its owning or managing employees or organizations—has or has had an affiliation under § 424.519 that poses an undue risk of fraud, waste, or abuse to the Medicare program.
                        </P>
                        <STARS/>
                        <P>
                            (14) 
                            <E T="03">Other program termination or suspension.</E>
                             (i) The provider or supplier—or any owner, managing employee, or managing organization thereof—is currently terminated or suspended (or otherwise barred) from participation in a State Medicaid program or any other federal health care program, or the provider's or supplier's license is currently revoked or suspended (or voluntarily surrendered in lieu of further action) in a State other than that in which the provider or supplier is enrolling. In determining whether a denial under this paragraph (a)(14) is appropriate, CMS considers the following factors:
                        </P>
                        <P>(A) The reason(s) for the termination, suspension, revocation, or surrender.</P>
                        <P>(B) Whether, as applicable, the provider or supplier—or owner, managing employee, or managing organization thereof—is currently terminated or suspended (or otherwise barred) from more than one program (for example, more than one State's Medicaid program), or has been subject to any other sanctions during its participation in other programs or by any other State licensing boards.</P>
                        <P>(C) Any other information that CMS deems relevant to its determination.</P>
                        <P>(ii) CMS may apply paragraph (a)(14)(i) of this section to the provider or supplier under any of the provider's or supplier's—or owner's, managing employee's, or managing organization's—current or former names, numerical identifiers or business identities, and regardless of whether any appeals are pending.</P>
                        <STARS/>
                        <P>
                            (16) 
                            <E T="03">Misdemeanor conviction.</E>
                             The provider or supplier—or any owner, managing employee, managing organization, officer, or director thereof—was convicted of a Federal or State misdemeanor related to sexual assault or financial misconduct within the past 10 years that CMS deems detrimental to the best interests of the Medicare program and its beneficiaries.
                        </P>
                        <STARS/>
                        <P>
                            (19) 
                            <E T="03">Same suite.</E>
                             The provider's or supplier's practice location is in the same suite or office as another provider or supplier whose Medicare enrollment has been revoked or denied under § 424.535 or § 424.530.
                        </P>
                        <P>
                            (20) 
                            <E T="03">Hospice medical director or administrator.</E>
                             A hospice's enrollment may be denied if any of the following apply:
                        </P>
                        <P>(i) The hospice's medical director is either of the following:</P>
                        <P>(A) The medical director of multiple other hospices.</P>
                        <P>
                            (B) Practices at such a distance (for example, in a different state) from the enrolling hospice that the medical director cannot realistically perform all medical director functions required under 42 CFR 418.
                            <PRTPAGE P="41325"/>
                        </P>
                        <P>(ii) The hospice's administrator is either of the following:</P>
                        <P>(A) The administrator of multiple other hospices.</P>
                        <P>(B) Located at such a distance from the enrolling hospice that the administrator cannot realistically perform all administrator functions required under 42 CFR 418.</P>
                        <P>(ii) The hospice's medical director does not have an active physician medical license in the State in which they are practicing.</P>
                        <P>
                            (21) 
                            <E T="03">Misuse of identity.</E>
                             The provider or supplier is attempting to enroll under another party's identity.
                        </P>
                        <P>
                            (22) 
                            <E T="03">Change in majority ownership non-compliance.</E>
                             CMS determines that the HHA, hospice, or DMEPOS supplier has failed to comply with the provisions and requirements of, as applicable, § 424.550(b) or § 424.551.
                        </P>
                        <STARS/>
                        <P>
                            (f) 
                            <E T="03">Reapplication bar.</E>
                             CMS may prohibit a prospective provider or supplier from enrolling in Medicare for up to 10 years if their enrollment application is denied for any reason under § 424.530.
                        </P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>X. Section 424.535 is amended by—</AMDPAR>
                    <AMDPAR>a. Revising paragraph (a)(4);</AMDPAR>
                    <AMDPAR>b. Revising paragraph (a)(8)(ii) introductory text;</AMDPAR>
                    <AMDPAR>c. Removing paragraphs (a)(8)(ii)(A) through (D) and (a)(8)(iii);</AMDPAR>
                    <AMDPAR>d. Revising paragraph (a)(16);</AMDPAR>
                    <AMDPAR>e. Revising paragraph (a)(19);</AMDPAR>
                    <AMDPAR>f. Adding paragraphs (a)(24) and (25).</AMDPAR>
                    <AMDPAR>g. Revising paragraph (g)(1);</AMDPAR>
                    <AMDPAR>h. Removing paragraph (g)(3);</AMDPAR>
                    <AMDPAR>i. Redesignating paragraph (g)(3) as (g)(2);</AMDPAR>
                    <AMDPAR>j. Revising paragraphs (h)(1)(i) and (ii).</AMDPAR>
                    <AMDPAR>k. Revising paragraph (i)(1).</AMDPAR>
                    <P>The revisions and additions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 424.535 </SECTNO>
                        <SUBJECT>Revocation of enrollment in the Medicare program.</SUBJECT>
                        <STARS/>
                        <P>(a) * * *</P>
                        <P>
                            (4) 
                            <E T="03">False or misleading information.</E>
                             The provider or supplier submits false or misleading information on or associated with any CMS or Medicare provider enrollment-related form. (Offenders may be referred to the Office of Inspector General for investigation and possible criminal, civil, or administrative sanctions.) This includes but is not limited to—
                        </P>
                        <P>(i) Forms created by and/or submitted to CMS contractors.</P>
                        <P>(ii) Documentation furnished as part of the completion or submission of the CMS or Medicare enrollment-related form.</P>
                        <P>(iii) Form CMS-588 (Electronic Funds Transfer (EFT) Authorization Agreement; OMB Control Number 0938-0626), which must be submitted with the enrollment application.</P>
                        <P>(iv) Documents required to demonstrate compliance with HHA capitalization requirements in § 489.28.</P>
                        <P>(v) Opt-out affidavits under 42 CFR part 405, subpart D.</P>
                        <P>(vi) Letters from a provider demonstrating that a particular provider official qualifies as an authorized or delegated official under § 424.502.</P>
                        <P>(vii) Any other required or requested enrollment-related documentation.</P>
                        <STARS/>
                        <P>(8) * * *</P>
                        <P>(ii) CMS determines that the provider or supplier has a pattern or practice of submitting claims that fail to meet Medicare requirements.</P>
                        <STARS/>
                        <P>
                            (16) 
                            <E T="03">Misdemeanor conviction.</E>
                             The provider or supplier—or any owner, managing employee, managing organization, officer, or director thereof—was convicted of a Federal or State misdemeanor related to sexual assault or financial misconduct within the past 10 years that CMS deems detrimental to the best interests of the Medicare program and its beneficiaries.
                        </P>
                        <STARS/>
                        <P>
                            (19) 
                            <E T="03">Affiliation that poses undue risk.</E>
                             CMS determines that the provider or supplier—or any of its owning or managing employees or organizations—has or has had an affiliation under § 424.519 that poses an undue risk of fraud, waste, or abuse to the Medicare program.
                        </P>
                        <STARS/>
                        <P>
                            (24) 
                            <E T="03">High-risk based on excess providers in area.</E>
                             CMS determines that the provider's or supplier's enrollment presents a high risk of fraud, waste, or abuse due to the provider's or supplier's location within a limited geographic area that has an excessive number of providers and suppliers.
                        </P>
                        <P>
                            (25) 
                            <E T="03">Change in majority ownership non-compliance.</E>
                            —CMS determines that the HHA, hospice, or DMEPOS supplier did not comply with the provisions and requirements of, as applicable, § 424.550(b) or § 424.551.
                        </P>
                        <STARS/>
                        <P>(g)(1) Except as described in paragraph (g)(2) of this section, the effective dates of the revocations identified in this section are as follows:</P>
                        <P>(i) For revocations under paragraph (a)(1) of this section:</P>
                        <P>(A) If the revocation is based on non-compliance with the enrollment requirements in Title 42 or in the enrollment application applicable to the provider or supplier type, the date the non-compliance began (per CMS' or the CMS contractor's determination).</P>
                        <P>(B) If the revocation is based on a State license revocation, suspension, or surrender in lieu of further disciplinary action, the date of the license revocation, suspension, or surrender.</P>
                        <P>(C) For revocations based on termination of a provider agreement under part 489 of this chapter, and as applicable to the type of provider involved, the later of—</P>
                        <P>
                            (
                            <E T="03">1</E>
                            ) The date of the provider agreement termination; or
                        </P>
                        <P>
                            (
                            <E T="03">2</E>
                            ) The date that CMS establishes under § 489.55.
                        </P>
                        <P>(ii) For revocations under paragraph (a)(2) of this section, the date of the exclusion or debarment.</P>
                        <P>(iii) For revocations under paragraph (a)(3) of this section, the date of the felony conviction.</P>
                        <P>(iv) For revocations under paragraph (a)(4) of this section, and as applicable to the situation, the date the certification statement was signed or the false or misleading information was submitted.</P>
                        <P>(v)(A) For revocations under paragraph (a)(5)(i) of this section, the date on which the provider's or supplier's practice location was no longer operational (per CMS' or the CMS contractor's determination).</P>
                        <P>(B) For revocations under paragraph (a)(5)(ii) of this section, the date the Medicare enrollment requirement was not satisfied.</P>
                        <P>(vi) For revocations under paragraph (a)(6) of this section, the date on which CMS or its contractor determines that the provider or supplier should be revoked under paragraph (a)(6).</P>
                        <P>(vii) For revocations under paragraph (a)(7) of this section, the date on which the conduct resulting in the revocation occurred.</P>
                        <P>(viii)(A) For revocations under paragraph (a)(8)(i) of this section, the earliest date of service on the claim or claims that is or are triggering the revocation.</P>
                        <P>(B) For revocations under paragraph (a)(8)(ii) of this section, the last date of service on the claims in the applicable pattern or practice.</P>
                        <P>(ix) For revocations under paragraph (a)(9) of this section, the day following the date by which the provider or supplier was required to report the applicable change, addition, or deletion.</P>
                        <P>
                            (x)(A) For revocations under paragraph (a)(10) of this section based on a failure to retain documentation, the date on which CMS or the CMS contractor determines that the provider or supplier has not complied with this retention requirement.
                            <PRTPAGE P="41326"/>
                        </P>
                        <P>(B) For revocations under paragraph (a)(10) of this section based on a failure to provide access to the documentation, the day after the date by which the provider or supplier was required to furnish access.</P>
                        <P>(xi) For revocations under paragraph (a)(11) of this section, the day after the date by which the HHA was required to submit the requested documentation.</P>
                        <P>(xii) For revocations under paragraph (a)(12) of this section, the date of the termination, revocation, or bar.</P>
                        <P>(xiii)(A) For revocations under paragraph (a)(13)(i) of this section, the date of the certificate revocation, suspension, or surrender.</P>
                        <P>(B) For revocations under paragraph (a)(13)(ii) of this section, the date of the revocation or suspension of the ability to prescribe.</P>
                        <P>(xiv) For revocations under paragraph (a)(14) of this section, the date of the last prescription in the applicable pattern or practice.</P>
                        <P>(xv) For revocations under paragraph (a)(15) of this section, the date of the judgment.</P>
                        <P>(xvi) For revocations under paragraph (a)(16) of this section, the date of the conviction.</P>
                        <P>(xvii) For revocations under paragraph (a)(17) of this section, the date on which CMS referred the debt to the Department of Treasury.</P>
                        <P>(xviii) For revocations under paragraph (a)(18) of this section, the effective date of the provider's or supplier's current enrollment.</P>
                        <P>(xix) For revocations under paragraph (a)(19) of this section, the date on which CMS or its contractor determines that the provider or supplier should be revoked under this paragraph.</P>
                        <P>(xx) For revocations under paragraph (a)(20) of this section, the earliest date on the claims for the non-compliant location that are triggering the revocation.</P>
                        <P>(xxi) For revocations under paragraph (a)(21) of this section, the date of the last order, certification, referral, or prescription in the applicable pattern or practice.</P>
                        <P>(xxii) For revocations under paragraph (a)(22) of this section, the date of the prior action resulting in the revocation.</P>
                        <P>(xxiii)(A) For revocations under paragraph (a)(23) of this section—</P>
                        <P>
                            (
                            <E T="03">1</E>
                            ) If the standard or condition violation involves the suspension, revocation, or termination (or surrender in lieu of further disciplinary action) of the provider's or supplier's Federal or State license, certification, accreditation, or MDPP recognition, the effective date is the date of the license, certification, accreditation, or MDPP recognition suspension, revocation, termination, or surrender.
                        </P>
                        <P>
                            (
                            <E T="03">2</E>
                            ) If the standard or condition violation involves a non-operational practice location, the effective date is the date the non-operational status began (per CMS' or the CMS contractor's determination).
                        </P>
                        <P>
                            (
                            <E T="03">3</E>
                            ) If the standard violation involves a felony conviction of an individual or entity described in § 424.67(b)(6)(i), the effective date is the date of the felony conviction.
                        </P>
                        <P>(B) For all other revocations under paragraph (a)(23) of this section based on a condition or standard violation, the effective date is the date of non-compliance with the condition or standard.</P>
                        <P>(xxiv) For revocations under paragraph (a)(24) of this section, the date on which CMS or its contractor determines that the provider or supplier should be revoked under paragraph (a)(24).</P>
                        <P>(xxv) For revocations under paragraph (a)(25) of this section, the date on which CMS or its contractor determines that the provider or supplier should be revoked under paragraph (a)(25).</P>
                        <P>(xxvi) For revocations under paragraph (i) of this section, the effective date of the revocation (or date of the denial) that triggered the revocation(s) of the other enrollment(s).</P>
                        <STARS/>
                        <P>(h)(1)(i) Except for HHAs as described in paragraph (h)(1)(ii) of this section, a revoked provider or supplier must, within 15 calendar days of the date of the revocation letter, submit all claims for items and services furnished before the date of the effective date of the revocation.</P>
                        <P>(ii) A revoked HHA must, within 15 calendar days of the date of the revocation letter, submit all claims for items and services furnished before the later of the following:</P>
                        <STARS/>
                        <P>(i) * * *</P>
                        <P>(1) If a provider's or supplier's Medicare enrollment is revoked under paragraph (a) of this section or denied under § 424.530, CMS may revoke any and all of the provider's or supplier's Medicare enrollments, including those under different names, numerical identifiers or business identities and those under different types.</P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>X. Section 424.540 is amended by—</AMDPAR>
                    <AMDPAR>a. In paragraph (b)(3)(i), removing the term “HHA” and adding in its place the phrase “HHA or hospice”; and</AMDPAR>
                    <AMDPAR>b. Adding paragraph (d)(3).</AMDPAR>
                    <P>The addition reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 424.540</SECTNO>
                        <SUBJECT>Deactivation of Medicare billing privileges.</SUBJECT>
                        <STARS/>
                        <P>(d) * * *</P>
                        <P>(3) A provider or supplier may rebut their assigned reactivation effective date via the procedures in § 424.546.</P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>X. Section 424.545 is amended by revising paragraph (b) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 424.545</SECTNO>
                        <SUBJECT>Provider and supplier appeal rights</SUBJECT>
                        <STARS/>
                        <P>(b) A provider or supplier whose billing privileges are deactivated or has been assigned a reactivation effective date may file a rebuttal in accordance with § 424.546 of this chapter.</P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>X. Section 424.546 would be amended as follows:</AMDPAR>
                    <AMDPAR>a. Revising the section heading, and paragraphs (a)(1) and (b)(2);</AMDPAR>
                    <AMDPAR>d. In paragraph (b)(3), removing the term “deactivation” and adding in its place the phrase “deactivation or reactivation effective date”; and</AMDPAR>
                    <AMDPAR>e. Revising paragraph (d).</AMDPAR>
                    <P>The revisions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 424.546</SECTNO>
                        <SUBJECT> Rebuttals of deactivations and of reactivation effective dates.</SUBJECT>
                        <P>(a)(1) If a provider or supplier receives written notice from CMS or its contractor that the provider's or supplier's billing privileges are to be or have been deactivated under § 424.540 or is assigned a reactivation effective date by CMS or its contractor under § 424.540(d)(2), the provider or supplier has 15 calendar days from the date of the written notice to submit a rebuttal to CMS as permitted under § 424.545(b).</P>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>(2) Specify the facts or issues about which the provider or supplier disagrees with the deactivation's imposition and/or the effective date (or with the assigned reactivation effective date), and the reasons for disagreement.</P>
                        <STARS/>
                        <P>(d) Upon receipt of a timely and compliant deactivation (or reactivation effective date) rebuttal, CMS reviews the rebuttal to determine whether the imposition of the deactivation and/or the designated effective date (or the assigned reactivation effective date) are correct.</P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>X. Section 424.570 is amended as follows:</AMDPAR>
                    <AMDPAR>a. Revising paragraphs (a)(1)(i) and(1)(iii)(C);</AMDPAR>
                    <AMDPAR>
                        b. Redesignating paragraph (a)(1)(iv) as paragraph (a)(1)(iv)(A).
                        <PRTPAGE P="41327"/>
                    </AMDPAR>
                    <AMDPAR>c. Adding paragraph (a)(1)(iv)(B).</AMDPAR>
                    <P>The revisions and addition read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 424.570</SECTNO>
                        <SUBJECT>Moratoria on newly enrolling Medicare providers and suppliers.</SUBJECT>
                        <P>(a) * * *</P>
                        <P>(1) * * *</P>
                        <P>(i) CMS may impose a moratorium on the enrollment of new Medicare providers and suppliers of a particular type or the establishment of new practice locations of a particular type in a particular geographic area. Solely for purposes of this section, the term “new” means any of the following application types:</P>
                        <P>(A) Initial enrollment applications.</P>
                        <P>(B) Change of ownership applications that require an initial enrollment per § 424.570(a)(1)(iii)(C).</P>
                        <P>(C) Enrollment applications from revoked providers or suppliers whose reenrollment bars under § 424.535(c) have expired and are seeking to enroll again in the Medicare program.</P>
                        <P>(D) Reactivation applications.</P>
                        <P>(E) Enrollment applications from voluntarily terminated providers/suppliers seeking to enroll again in the Medicare program.</P>
                        <STARS/>
                        <P>(iii) * * *</P>
                        <P>(C) Changes in ownership (except changes in ownership that require an initial enrollment, such as, but not limited to, an HHA, hospice, or DMEPOS supplier change in majority ownership under § 424.550(b) or § 424.551).</P>
                        <P>(iv)(A) A temporary moratorium does not apply to any enrollment application that has been received by the Medicare contractor prior to the date the moratorium is imposed.</P>
                        <P>(B) The date the moratorium is imposed is the moratorium's effective date, which is the date on which the moratorium notice is filed for public inspection at the Office of the Federal Register (OFR).</P>
                        <STARS/>
                    </SECTION>
                    <PART>
                        <HD SOURCE="HED">PART 484—HOME HEALTH SERVICES</HD>
                    </PART>
                    <AMDPAR>X. The authority citation for part 484 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>42 U.S.C. 1302 and 1395hh.</P>
                    </AUTH>
                    <AMDPAR>X. Section 484.245 is amended by—</AMDPAR>
                    <AMDPAR>a. In paragraph (b)(2)(ii)(A), removing the parenthetical phrase “(July 1 through June 30)” and adding in its place the parenthetical phrase “(January 1 through December 31)”;</AMDPAR>
                    <AMDPAR>b. In paragraph (d)(1)(i), removing the phrase “a letter of noncompliance” and adding in its place the phrase “receive notification of non-compliance”;</AMDPAR>
                    <AMDPAR>
                        c. In paragraph (d)(2) introductory text, removing the hyperlink “
                        <E T="03">HHAPureConsiderations@cms.hhs.gov</E>
                         ” and adding in its place the hyperlink “
                        <E T="03">HHAPUReconsiderations@cms.hhs.gov”;</E>
                    </AMDPAR>
                    <AMDPAR>d. In paragraph (d)(2)(v), removing the phrase “non-compliance letter” and adding in its place the phrase “non-compliance notification”; and</AMDPAR>
                    <AMDPAR>e. Revising paragraph (d)(4)(i);</AMDPAR>
                    <P>The revision reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 484.245</SECTNO>
                        <SUBJECT>Requirements under the Home Health Quality Reporting Program (HH QRP).</SUBJECT>
                        <STARS/>
                        <P>(d) * * *</P>
                        <P>(4)(i) CMS notifies the HHA of its final decision regarding any reconsideration request through a CMS designated data submission system.</P>
                        <STARS/>
                    </SECTION>
                    <PART>
                        <HD SOURCE="HED">PART 498—APPEALS PROCEDURES FOR DETERMINATIONS THAT AFFECT PARTICIPATION IN THE MEDICARE PROGRAM AND FOR DETERMINATIONS THAT AFFECT THE PARTICIPATION OF ICFs/IID AND CERTAIN NFs IN THE MEDICAID PROGRAM</HD>
                    </PART>
                    <AMDPAR>X. The authority for part 498 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>42 U.S.C. 1302, 1320a-7j, and 1395hh.</P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 498.3</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>X. Section 498.3 is amended in paragraph (b)(19) by removing the term “renew opt-out” and add in its place the phrase “cancel automatic renewal”.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 498.20</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>X. Section 498.20 is amended in paragraph (a)(1) by removing the term “mails” and add in its place the phrase “mails or emails”.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 498.25</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>X. Section 498.25 is amended by revising paragraph (a)(1) to remove the term “mails” and add in its place the phrase “mails or emails”.</AMDPAR>
                    <SIG>
                        <NAME>Robert F. Kennedy, Jr.,</NAME>
                        <TITLE>
                            Secretary, 
                            <E T="03">Department of Health and Human Services.</E>
                        </TITLE>
                    </SIG>
                </SUPLINF>
                <FRDOC>[FR Doc. 2026-13602 Filed 7-1-26; 4:15 pm]</FRDOC>
                <BILCOD>BILLING CODE 4169-69-P</BILCOD>
            </PRORULE>
        </PRORULES>
    </NEWPART>
    <VOL>91</VOL>
    <NO>127</NO>
    <DATE>Monday, July 6, 2026</DATE>
    <UNITNAME>Notices</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="41329"/>
            <PARTNO>Part IV </PARTNO>
            <AGENCY TYPE="P">Department of Justice</AGENCY>
            <SUBAGY>Antitrust Division</SUBAGY>
            <HRULE/>
            <TITLE>United States et al. v. Live Nation Entertainment, Inc.; Proposed Final Judgment and Competitive Impact Statement; Notice</TITLE>
        </PTITLE>
        <NOTICES>
            <NOTICE>
                <PREAMB>
                    <PRTPAGE P="41330"/>
                    <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                    <SUBAGY>Antitrust Division</SUBAGY>
                    <SUBJECT>
                        <E T="7462">United States et al.</E>
                          
                        <E T="01">v.</E>
                          
                        <E T="7462">Live Nation Entertainment, Inc.;</E>
                         Proposed Final Judgment and Competitive Impact Statement
                    </SUBJECT>
                    <P>
                        Notice is hereby given pursuant to the Antitrust Procedures and Penalties Act, 15 U.S.C. 16(b)-(h), that a proposed Final Judgment, Stipulation, and Competitive Impact Statement have been filed with the United States District Court for the Southern District of New York in 
                        <E T="03">United States of America et al.</E>
                         v. 
                        <E T="03">Live Nation Entertainment, Inc,</E>
                         Civil Action No. 1:24-cv-3973-AS. On August 30, 2024, the United States filed an Amended Complaint (the “Complaint”) alleging that Live Nation Entertainment, Inc. and Ticketmaster L.L.C. (“Defendants”) violated Sections 1 and 2 of the Sherman Act, 15 U.S.C. 1-2, as well as several State laws by engaging in anticompetitive conduct in certain ticketing, promotions, and amphitheater markets. The proposed Final Judgment filed on June 12, 2026 requires Defendants to: (1) develop technology to allow Major Concert Venues utilizing Ticketmaster's back-end software to sell and distribute primary tickets through third-party marketplaces; (2) loosen exclusivity provisions in their existing primary ticketing contracts and abide by new restrictions on exclusive contracting for future ticketing contracts; (3) allow promoters and artists to use alternative sellers of tickets at Defendants' amphitheaters; (4) cap ticket service fees at Defendants' amphitheaters; (5) divest control over certain amphitheaters; (6) allow artists who choose to work with other promoters to perform at Defendants' amphitheaters; (7) waive exclusive and preferred booking rights at Major Concert Venues; (8) refrain from engaging in conditioning, retaliation, or content-steering that impairs competition; (9) maintain firewalls that limit disclosure of information between Ticketmaster and Live Nation; (10) terminate their ticketing agreement with the Oak View Group and refrain from entering into similar agreements in the future; (11) share certain data with artists; and (12) notify the United States of certain future acquisitions. It also requires Defendants to submit to oversight by a monitor who will have the power to monitor Defendants' compliance with the Stipulation and Order and proposed Final Judgment.
                    </P>
                    <P>
                        Copies of the Complaint, proposed Final Judgment, and Competitive Impact Statement are available for inspection on the Antitrust Division's website at 
                        <E T="03">http://www.justice.gov/atr</E>
                         and at the Office of the Clerk of the United States District Court for the Southern District of New York. Copies of these materials may be obtained from the Antitrust Division upon request and payment of the copying fee set by Department of Justice regulations.
                    </P>
                    <P>
                        Public comment is invited within 60 days of the date of this notice. Such comments, including the name of the submitter, and responses thereto, will be posted on the Antitrust Division's website, filed with the Court, and, under certain circumstances, published in the 
                        <E T="04">Federal Register</E>
                        . Comments should be submitted in English and directed to David Teslicko, Acting Chief, Financial Services, Fintech, and Banking Section, Antitrust Division, Department of Justice, 450 Fifth Street NW, Suite 4000, Washington, DC 20530 (email address: 
                        <E T="03">LiveNationPublicComment@usdoj.gov</E>
                        ).
                    </P>
                    <SIG>
                        <NAME>Suzanne Morris,</NAME>
                        <TITLE>Deputy Director Civil Enforcement Operations, Antitrust Division.</TITLE>
                    </SIG>
                    <HD SOURCE="HD1">UNITED STATES DISTRICT COURT SOUTHERN DISTRICT OF NEW YORK</HD>
                    <P>
                        <E T="03">UNITED STATES OF AMERICA, U.S. Department of Justice, Antitrust Division, 450 Fifth Street N.W., Suite 4000, Washington, DC 20530; STATE OF ARIZONA, 2005 N. Central Avenue, Phoenix, AZ 85004; STATE OF ARKANSAS, 323 Center Street, Suite 200, Little Rock, AR 72201; STATE OF CALIFORNIA, 300 South Spring Street, Suite 1702, Los Angeles, CA 90013; STATE OF COLORADO, 1300 Broadway, 7th Floor, Denver, CO 80203; STATE OF CONNECTICUT, 165 Capitol Avenue, Hartford, CT 06106; DISTRICT OF COLUMBIA, 400 Sixth Street, N.W., Washington, DC 20001; STATE OF FLORIDA, PL-01 The Capitol, Tallahassee, FL 32399-1050; STATE OF ILLINOIS, 115 S. LaSalle Street, Floor #23, Chicago, IL 60603; STATE OF INDIANA, 302 West Washington Street, Fifth Floor, Indianapolis, IN 46204; STATE OF IOWA, 1305 E. Walnut St., Des Moines, IA 50319; STATE OF KANSAS, 120 S.W. 10th Avenue, 2nd Floor, Topeka, KS 66612-1597; STATE OF LOUISIANA, 1885 North Third Street, Baton Rouge, LA 70802; STATE OF MARYLAND, 200 St. Paul Place, 19th Floor, Baltimore, MD 21202; COMMONWEALTH OF MASSACHUSETTS, One Ashburton Place, 18th Floor, Boston, MA 02108; STATE OF MICHIGAN, 525 W Ottawa St., Lansing, MI 48933; STATE OF MINNESOTA, 445 Minnesota Street, Saint Paul, MN 55101; STATE OF MISSISSIPPI, 550 High Street, Jackson, MS 39201; STATE OF NEBRASKA, 2115 State Capitol, Lincoln, NE 68509; STATE OF NEVADA, 8945 West Russell Road., Suite 204, Las Vegas, Nevada 89148; STATE OF NEW HAMPSHIRE, 1 Granite Place South, Concord, NH 03301; STATE OF NEW JERSEY, 124 Halsey Street, 5th Floor, Newark, NJ 07101; STATE OF NEW MEXICO, 408 Galisteo St., Santa Fe, NM 87501; STATE OF NEW YORK, 28 Liberty Street, New York, NY 10005; STATE OF NORTH CAROLINA, P.O. Box 629, Raleigh, NC 27602; STATE OF OHIO, 30 E. Broad Street, 26th Floor, Columbus, OH 43215; STATE OF OKLAHOMA, 313 NE 21st Street, Oklahoma City, OK 73105; STATE OF OREGON, 1162 Court Street, N.E., Salem, OR 97301; COMMONWEALTH OF PENNSYLVANIA, Strawberry Square, 14th Floor, Harrisburg, PA 17120; STATE OF RHODE ISLAND, 150 South Main Street, Providence, RI 02903; STATE OF SOUTH CAROLINA, P.O. Box 11549, Columbia, South Carolina 29211; STATE OF SOUTH DAKOTA, 1302 E. Hwy 14, Suite 1, Pierre SD 57501; STATE OF TENNESSEE, P.O. Box 20207, Nashville, TN 37202; STATE OF TEXAS, P.O. Box 12548, Austin, TX 78711-2548; STATE OF UTAH, 160 East 300 South, 5th Floor, Salt Lake City, UT 84114; STATE OF VERMONT, 109 State Street, Montpelier, VT 05609; COMMONWEALTH OF VIRGINIA, 202 N. 9th Street, Richmond, VA 23219; STATE OF WASHINGTON, 800 Fifth Avenue, Suite 2000, Seattle, WA 98104-3188; STATE OF WEST VIRGINIA, 1900 Kanawha Boulevard East, Capitol Complex, Building 6, Suite 401, Charleston, WV 25305; STATE OF WISCONSIN, P.O. Box 7857, Madison, Wisconsin 53707,</E>
                         and; 
                        <E T="03">STATE OF WYOMING, 109 State Capitol, Cheyenne, WY 82002,</E>
                    </P>
                    <P>Plaintiffs,</P>
                    <P>v.</P>
                    <P>
                        <E T="03">LIVE NATION ENTERTAINMENT, INC., 9348 Civic Center Drive, Beverly Hills, CA 90210,</E>
                    </P>
                    <P>and</P>
                    <P>
                        <E T="03">TICKETMASTER L.L.C., 9348 Civic Center Drive, Beverly Hills, CA 90210,</E>
                    </P>
                    <P>Defendants.</P>
                    <FP>
                        <E T="03">AMENDED COMPLAINT, 1:24-cv-3973, JURY TRIAL DEMANDED</E>
                    </FP>
                    <HD SOURCE="HD1">Table of Contents</HD>
                    <FP SOURCE="FP-2">I. Introduction </FP>
                    <FP SOURCE="FP-2">II. Defendants Live Nation and Ticketmaster </FP>
                    <FP SOURCE="FP-2">III. Industry Background </FP>
                    <FP SOURCE="FP1-2">A. How Live Concerts Work </FP>
                    <FP SOURCE="FP1-2">B. Money Flows Across the Live Entertainment Industry </FP>
                    <FP SOURCE="FP1-2">
                        C. Live Nation's “Flywheel” 
                        <PRTPAGE P="41331"/>
                    </FP>
                    <FP SOURCE="FP1-2">D. History of Live Nation and Ticketmaster </FP>
                    <FP SOURCE="FP-2">IV. Live Nation Maintains Monopolies and Market Power Across the Live Concert Ecosystem Through an Anticompetitive and Exclusionary Course of Conduct </FP>
                    <FP SOURCE="FP1-2">A. Oak View Group: Nascent competitor to a self-described “hammer” for Live Nation. </FP>
                    <FP SOURCE="FP1-2">B. Live Nation threatens rivals to blunt expansion into U.S. concert promotions. </FP>
                    <FP SOURCE="FP1-2">C. Using “carrots” and “sticks,” Live Nation locks venues into exclusive, long-term ticketing agreements with Ticketmaster that shut out competition. </FP>
                    <FP SOURCE="FP1-2">D. Ticketmaster's long-term exclusive agreements with venues are designed to lock up share and lock out competition, which forecloses a substantial share of primary ticketing markets. </FP>
                    <FP SOURCE="FP1-2">E. Live Nation restricts access to its venues unless Live Nation is paid to be the promoter. </FP>
                    <FP SOURCE="FP1-2">F. Live Nation strategically acquires promoters, venues, and festivals to eliminate rivals, expand its network, and grow its “moat.” </FP>
                    <FP SOURCE="FP-2">V. Anticompetitive Effects and Competitive Harm </FP>
                    <FP SOURCE="FP-2">VI. Continuing Violations </FP>
                    <FP SOURCE="FP-2">VII. Relevant Markets and Monopoly Power </FP>
                    <FP SOURCE="FP1-2">A. Primary Ticketing Services Markets </FP>
                    <FP SOURCE="FP1-2">i. Primary Ticketing Services to Major Concert Venues </FP>
                    <FP SOURCE="FP1-2">ii. Primary Concert Ticketing Offerings to Fans at Major Concert Venues </FP>
                    <FP SOURCE="FP1-2">B. Concert Promotions Services Markets</FP>
                    <FP SOURCE="FP1-2">i. Concert Booking and Promotion Services to Major Concert Venues </FP>
                    <FP SOURCE="FP1-2">ii. Promotion Services to Artists </FP>
                    <FP SOURCE="FP1-2">C. Artist Use of Large Amphitheaters </FP>
                    <FP SOURCE="FP-2">VII. Jurisdiction, Venue, and Commerce </FP>
                    <FP SOURCE="FP-2">VIII. Antitrust Injury </FP>
                    <FP SOURCE="FP-2">IX. Violations Alleged </FP>
                    <FP SOURCE="FP-2">X. Request for Relief </FP>
                    <FP SOURCE="FP-2">XI. Demand for a Jury Trial </FP>
                    <HD SOURCE="HD1">I. Introduction</HD>
                    <P>1. One monopolist serves as the gatekeeper for the delivery of nearly all live music in America today: Live Nation, including its wholly owned subsidiary Ticketmaster. In Live Nation's words, it is the “largest live entertainment company in the world,” the “largest producer of live music concerts in the world,” and “the world's leading live entertainment ticketing sales and marketing company.” Indeed, Live Nation is all these things, to the detriment of fans, artists, venues, and competition.</P>
                    <P>2. Today, musical artists must rely on promoters, venues, and ticketers to organize the business of playing live music. These service providers should work to serve the interests of artists and fans. Genuine competition for and among these service providers would generate the best, most cost-effective, and fan-friendly experience. But the world live music fans live in today is far from that.</P>
                    <P>3. Live Nation directly manages more than 400 musical artists and, in total, controls around 60% of concert promotions at major concert venues across the country. Live Nation also owns or controls more than 265 concert venues in North America, including more than 60 of the top 100 amphitheaters in the United States. For comparison, its closest rival owns no more than a handful of top amphitheaters. And, of course, through Ticketmaster, Live Nation controls roughly 80% or more of major concert venues' primary ticketing for concerts and a growing share of ticket resales in the secondary market.</P>
                    <P>4. The live music industry, like other heavily concentrated industries, is largely controlled by a well-known group of insiders who lead multiple interconnected companies with numerous conflicts of interest. These insiders have spent decades amassing, fortifying, and exercising power, particularly against anyone who seeks to disrupt the now-standard industry business practices and conduct. These business practices can, and often do, work against the interests of those with relatively little power and influence, especially working musicians and fans. These insiders often speak to each other, and work together, as allies and partners rather than as vigorous competitors.</P>
                    <P>5. With this vast scope of power comes influence. Live Nation and its wholly owned subsidiary, Ticketmaster, have used that power and influence to insert themselves at the center and the edges of virtually every aspect of the live music ecosystem. This has given Live Nation and Ticketmaster the opportunity to freeze innovation and bend the industry to their own benefit. While this may be a boon to Live Nation's bottom line, there is a real cost to Americans. As described in detail below, today Live Nation possesses and routinely exercises control over which artists perform on what dates at which venues. Through Ticketmaster, Live Nation also possesses and exercises control over how fans are able to purchase tickets to see their favorite artists in concert and what fees those fans will pay to do so. Artists and fans as well as the countless people and other services that support them suffer from the loss of dynamism and growth that competition would inevitably usher in.</P>
                    <P>6. As this Complaint describes in detail, through a self-reinforcing “flywheel” that Live Nation-Ticketmaster created to connect their multiple interconnected businesses and interests, Live Nation and Ticketmaster have engaged in numerous forms of anticompetitive conduct. That anticompetitive conduct includes the following:</P>
                    <P>
                        a. 
                        <E T="03">Relationship with Oak View Group.</E>
                         Live Nation-Ticketmaster exploits its longtime relationship with Oak View Group, a potential competitor-turned-partner that has described itself as a “hammer” and “protect[or]” for Live Nation. In recent years, Oak View Group has avoided bidding against Live Nation for artist talent and influenced venues to sign exclusive agreements with Ticketmaster. For example, Live Nation has scolded Oak View Group multiple times for trying to compete. In one instance, Live Nation asked, “who would be so stupid to . . . play into [an artist agent's] arms,” and on another occasion, Live Nation stated, “let's make sure we don't let [the artist agency] now start playing us off.”
                    </P>
                    <P>
                        b. 
                        <E T="03">Retaliating Against Potential Entrants.</E>
                         Live Nation-Ticketmaster successfully threatened financial retaliation against a firm unless it stopped one of its subsidiaries from competing to gain a foothold in the U.S. concert promotions market.
                    </P>
                    <P>
                        c. 
                        <E T="03">Acquiring Competitors and Competitive Threats.</E>
                         Live Nation-Ticketmaster strategically acquired a number of smaller and regional promoters that it had internally identified as threats. This has undermined competition and impacted artist compensation.
                    </P>
                    <P>
                        d. 
                        <E T="03">Threatening and Retaliating Against Venues that Work with Rivals.</E>
                         Live Nation-Ticketmaster's power in concert promotions means that every live concert venue knows choosing another promoter or ticketer comes with a risk of drawing an adverse reaction from Live Nation-Ticketmaster that would result in losing concerts, revenue, and fans.
                    </P>
                    <P>
                        e. 
                        <E T="03">Locking Out Competition with Exclusionary Contracts.</E>
                         Live Nation-Ticketmaster locks concert venues into long-term exclusive contracts so that venues cannot consider or choose rival ticketers or switch to better, more, or cost-effective ticketing technology. These contracts allow Live Nation-Ticketmaster to reduce competitive pressure to improve its own ticketing technology and customer service.
                        <PRTPAGE P="41332"/>
                    </P>
                    <P>
                        f. 
                        <E T="03">Blocking Venues from Using Multiple Ticketers.</E>
                         Live Nation-Ticketmaster's conduct and exclusive contracts prevent new and different promotions and ticketing competitors and business models from emerging. They block venues from being able to use multiple ticketers, who would compete by offering the best mix of prices, fees, quality, and innovation to fans.
                    </P>
                    <P>
                        g. 
                        <E T="03">Restricting Artists' Access to Venues.</E>
                         Live Nation-Ticketmaster has increasingly gained control of key venues, including amphitheaters, through acquisitions, partnerships, and agreements. Live Nation-Ticketmaster restricts artists' use of those venues unless those artists also agree to use their promotion services.
                    </P>
                    <P>7. Taken individually and considered together, Live Nation's and Ticketmaster's conduct allows them to exploit their conflicts of interest—as a promoter, ticketer, venue owner, and artist manager—across the live music industry and further entrench their dominant positions. Because Live Nation and Ticketmaster control so much of the concert-going experience, would-be rivals must compete at scale across different levels of the concert ecosystem, raising barriers to competition even further and requiring multi-level entry by existing and would-be competitors.</P>
                    <P>8. The real world, practical costs of Live Nation's strategy are well-known. Public frustration with concert ticket pricing and sales is a constant drumbeat. The fees that must be paid to attend a live concert in America far exceed fees in comparable parts of the world. Any fan who has logged onto Ticketmaster's website to buy a concert ticket knows the feeling of shock and frustration as the base cost of the ticket increases dramatically with the addition of fees to include:</P>
                    <P>a. “service” or “convenience” fees,</P>
                    <P>b. “Platinum” fees,</P>
                    <P>c. “VIP” fees,</P>
                    <P>d. “per order” or “handling” fees,</P>
                    <P>e. “payment processing” fees,</P>
                    <P>f. “facility” fees, and/or</P>
                    <P>g. any other fee or tax Ticketmaster collects from the fan, often with a cut of that fee going back to Ticketmaster.</P>
                    <P>9. Whatever the name of the fee and however the fees are packaged and collected, they are essentially a “Ticketmaster Tax” that ultimately raise the price fans pay.</P>
                    <P>10. Live Nation's anticompetitive conduct has not only harmed fans in the form of more and higher fees, but also undermines innovation. Competition increases the array and quality of services available and makes it easier for fans to find and see artists they love. Unburdened by competition on the merits, Ticketmaster does not need to invest as much to improve the fan experience.</P>
                    <P>11. Live Nation and Ticketmaster understand the benefits a more open and competitive ticketing ecosystem would bring to fans and others. For example, in 2022, Ticketmaster evaluated and recognized that a more open, non-exclusive ticketing system—in essence, ending its preferred exclusive primary ticketing relationships—could lead to more competition and threats to its dominance. Instead, Ticketmaster has focused on adding new restrictions to its ticketing systems to force fans to interact with Ticketmaster and thereby facilitate Ticketmaster's ability to increase the amount of data it collects from fans. This, of course, benefits not only Ticketmaster but also the vast array of related Live Nation businesses and feeds the Live Nation-Ticketmaster flywheel. According to Live Nation's CEO, Ticketmaster “now not only know[s] the person that bought the ticket, but [also] those three people that you are taking to the show, which we [Live Nation] have not known historically.” Its data supremacy over rivals has only accelerated.</P>
                    <P>12. The impact of the diminished incentive to innovate can manifest in real ways. Without competitive pressure to spur investment and innovation, customer service, website and app design, and product quality and stability suffer. These harms are the natural and predictable consequence of an industry suffocating under monopoly.</P>
                    <P>13. The United States and certain States previously tried to protect what should be a dynamic, thriving industry through a Clayton Act Section 7 case and resulting consent decree in 2010, followed by an amended consent decree in 2020. Notwithstanding the prior case under Section 7 of the Clayton Act, Live Nation and Ticketmaster have violated other antitrust laws, namely the Sherman Act, through additional, different, and more expansive forms of anticompetitive conduct and exclusionary practices.</P>
                    <P>14. Live Nation's monopoly, and the anticompetitive conduct that protects and maintains its monopoly, strikes a chord precisely because the industry at stake is one that has for generations inspired, entertained, and challenged Americans. Conduct that subverts competition here not only harms the structure of the live music industry and the countless people that work in that industry, but also damages the foundation of creative expression and art that lies at the heart of our personal, social, and political lives.</P>
                    <P>15. It is often said that music requires little more than “three chords and the truth.” In our modern economy, the live music industry requires that plus competition. Restoring competition protects the ability of working artists and fans to meaningfully access, afford, and engage with music and each other. Addressing and stopping anticompetitive conduct is also essential to ensure the vibrancy of live music. The United States and the Attorneys General of Arizona, Arkansas, California, Colorado, Connecticut, the District of Columbia, Florida, Illinois, Indiana, Iowa, Kansas, Louisiana, Maryland, Massachusetts, Michigan, Minnesota, Mississippi, Nebraska, Nevada, New Hampshire, New Jersey, New Mexico, New York, North Carolina, Ohio, Oklahoma, Oregon, Pennsylvania, Rhode Island, South Carolina, South Dakota, Tennessee, Texas, Utah, Vermont, Virginia, Washington, West Virginia, Wisconsin, and Wyoming hereby seek relief from this Court, including structural relief, to stop the anticompetitive conduct arising from Live Nation's monopoly power.</P>
                    <HD SOURCE="HD1">II. Defendants Live Nation and Ticketmaster</HD>
                    <P>16. According to its 2023 securities filings, Defendant Live Nation Entertainment, Inc. is the “largest live entertainment company in the world,” the “largest producer of live music concerts in the world,” and “the world's leading live entertainment ticketing sales and marketing company,” and it owns, operates, leases, has equity interest in, or has exclusive booking rights for or significant influence over 373 venues globally and more than 265 in North America. This includes more than 60 of the top 100 amphitheaters in the United States that Live Nation either owns or controls through long-term leases or for which it has the exclusive right to determine who performs at the venue. Control over a venue not only confers on Live Nation the ability to dictate whether fans can see a particular artist they love, but in many cases also provides Live Nation control over many aspects of the concert experience and a host of additional revenue streams ranging from sponsorships to food and beverage sales.</P>
                    <P>
                        17. Live Nation's business brings in over $22 billion dollars in revenue a year globally. Live Nation divides its business into three segments: Concerts (
                        <E T="03">e.g.,</E>
                         promotions, venue management, and music festival production), Ticketing (
                        <E T="03">e.g.,</E>
                         Ticketmaster business), and Sponsorship and Advertising. In 
                        <PRTPAGE P="41333"/>
                        2023, Live Nation generated $18.8 billion in Concerts revenue, $2.9 billion for Ticketing, and $1.1 billion for Sponsorship &amp; Advertising.
                    </P>
                    <P>18. Defendant Ticketmaster L.L.C. is a wholly owned subsidiary of Live Nation (collectively referred to as “Live Nation” herein). Ticketmaster provides primary and secondary ticketing services, which are responsible, respectively, for selling tickets to fans in the first instance for a show and allowing fans to resell those tickets at a later time. Ticketmaster is by far the largest concert ticketing company in the United States for major concert venues, at least eight times the size of its closest competitor.</P>
                    <HD SOURCE="HD1">III. Industry Background</HD>
                    <HD SOURCE="HD2">A. How Live Concerts Work</HD>
                    <P>19. Today's live music concerts are complex productions involving thousands of choices to bring together artists and their fans on a particular date and time. Staging a single concert at a major concert venue—let alone an entire tour—involves months of preparation and requires the orchestrated support of many intermediaries in multiple roles. Among the decisions that will most impact the overall experience of fans include what venue will host a particular live music experience, who will promote the event, and who will ticket the event.</P>
                    <GPH SPAN="3" DEEP="199">
                        <GID>EN06JY26.085</GID>
                    </GPH>
                    <P>
                        20. The planning of a concert predictably begins with an artist 
                        <SU>1</SU>
                        <FTREF/>
                         who decides to share her music and the artistic vision for the presentation of that music with the world and, specifically, with her fans. For artists, the decision to perform live and share music in this medium is an important opportunity to publicly display their art, but also to generate and continue to cultivate enduring relationships with their fans who appreciate and patronize that art. The overall experience associated with what music to present and, critically, how to present it, allows artists to express their artistic vision in a way that will resonate with fans. While artists strive to ensure fans at a single show appreciate their art, they also work to cultivate that fan base over the long run. This allows artists to maximize their ability to earn money over the arc of their career as compensation for their creative labor, whether it is through more concerts, the sale of more tickets at larger concerts, or the sale of merchandise and other related products and services. As is often publicly reported, the income earned from concerts generally represents a substantial part of artists' compensation for their creative and performance labor.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             As used in this Complaint, “artist” refers to both musicians and comedians, who make similar choices in planning their performances and face similar competitive conditions.
                        </P>
                    </FTNT>
                    <P>21. Managers and/or agents typically assist artists to achieve these goals. Managers and agents guide artists' professional lives, including touring, and are often compensated based on a share of the artist's revenues or profit streams. Live Nation manages more than 400 artists in the United States, and in that capacity works with artists, along with other industry intermediaries, to shape their tours and price tickets. One of the founders of Oak View Group, a leading venue development company that partners with Live Nation, also owns a company that is a major manager of artists in the United States music industry.</P>
                    <P>22. In the modern era, once an artist decides to perform a concert or go on tour, the first major decision they must make, alongside their manager or agent, is to contract with one or more promoters. Promoters are primarily responsible for arranging the concert or tour and promoting the event to the public. Promoters provide a variety of services, including working with artists and their managers and/or agents to help choose the venue(s) to host the concert or tour and determine ticket prices, promoting the concert to the public, and shouldering the financial risk and potential upside if the show or tour underperforms/overperforms in terms of profitability. Promoters are also generally responsible for facilitating payments to the artist, venue, and other vendors associated with the concert or tour.</P>
                    <P>
                        23. Artists historically used different promoters for each show in a new city or region of the country. Today, while local promoters may book one or a handful of shows in a local market, touring artists typically use national promoters—principally Live Nation and AEG Presents (a subsidiary of Anschutz Entertainment Group Inc. (“AEG”))—as they can offer a single packaged tour deal. These deals often include a larger, upfront guaranteed payment to the artist for a national tour with multiple shows across many markets as compared to one-off shows in a single city or region. Through tour deals, national promoters reduce their own risk of not generating enough revenue to cover the artist's guarantee by, in effect, using the profits of successful shows to mitigate the 
                        <PRTPAGE P="41334"/>
                        losses of unsuccessful shows within an artist's tour.
                    </P>
                    <P>24. Live Nation and its much smaller rival (less than half the size, although even that overstates its competitive significance), AEG, are the two largest concert promoters in the United States. Both Live Nation and AEG also separately provide and are compensated for providing primary ticketing services to venues. No other promoter in the United States can rival their venue networks, scale, reach, and connections to compete to promote national tours for major artists on a regular basis.</P>
                    <P>25. The second major decision an artist—supported by their manager and/or agent—must make is which concert venues to use at various stops on a national tour. Concert venues are the physical spaces or facilities that host live music. Venues compete to attract artists to perform at their facility, and artists may choose where to perform based on a variety of characteristics, including the venue's ambiance, capacity, location, and acoustics. Sometimes a venue owner separately contracts with a promoter, like Live Nation, to provide that promoter with financial incentives for booking and promotions services over an extended period of time, which predictably can lead a promoter to steer artists it promotes to perform at the venue. Other times venues provide these incentives on a show-by-show basis.</P>
                    <P>26. Venue owners can either operate the facility themselves or hire a management company to operate it. Venue operators provide and maintain the facilities where concerts are held and oversee the venue's services, such as concessions, parking, security, and artist merchandising. Venue operators usually charge the artist and their promoter rent to use the facility to perform a concert, and the venue operator often works directly with the artist in providing related ancillary services, such as the staging and lighting of a show.</P>
                    <P>27. Most artists start their careers performing at smaller venues like clubs or theaters, which offer limited capacities, but at generally lower costs. These venues allow newer artists to develop and grow a relationship with their fans in more intimate settings before moving on to larger venues as their “draw” of fans increases. As artists grow their fan base, they graduate to larger venues. Major concert venues include large amphitheaters and arenas that are particularly suited to hosting live concerts for popular artists due to their capacity, infrastructure, and amenities. Concerts are a vital source of revenue for these venues.</P>
                    <P>28. Live Nation owns, operates, or otherwise controls more than 265 venues across North America. For many years, Live Nation has been the single largest—and growing—owner of American clubs and theaters, which gives it the unique ability to capture artists early in their careers. As artists grow their popularity, this early access enhances Live Nation's ability to funnel artists through the vast array of Live Nation products and services in the modern live music ecosystem. Live Nation's control over access to so many popular venues across the country gives it outsized power and control in this industry.</P>
                    <P>29. Large amphitheaters, in particular, are attractive venues for certain popular artists. Amphitheaters are outdoor venues, which allow artists to take advantage of warm weather in the summer months when many artists prefer to tour. Many touring artists like amphitheaters because they generally offer a balance between more seating than clubs and theaters at a more lucrative compensation and more affordable prices for fans, and a more curated and intimate artistic experience than arenas or large festivals. Large amphitheaters are especially attractive to artists who have graduated from clubs and theaters, but are not yet able to fill higher-capacity arenas on a consistent basis. They also may be attractive to artists who once played in arenas or stadiums but are no longer able to attract the same audience size.</P>
                    <P>30. Live Nation controls more than 60% of large amphitheaters in the United States. Live Nation owns, operates, or exclusively books at least 40 of the top 50 and 60 of the top 100 amphitheaters in the United States. No other company in the United States owns more than a handful of amphitheaters, even those with an otherwise sizeable portfolio of arenas.</P>
                    <P>31. Today, almost all major concert venues contract with a primary ticketer to handle the sale of tickets. Primary ticketers orchestrate the sale of tickets to fans. In the past, tickets for major concert venues were sold through call centers, retail outlets, and box offices, all of which could be operated or offered by different parties. Today, most tickets are sold through the internet and mobile applications and the most common delivery method is electronic delivery to fans' mobile phones. The vast majority of major concert venues have an exclusive arrangement with a primary ticketer, most often Ticketmaster, who is entitled to manage and sell tickets on behalf of the initial rights holder—for concerts, this is typically the artist—for all events at that venue. The primary ticketer manages ticketing inventory and provides the technology for online ticketing, accounting, payment processing, and other administrative capabilities.</P>
                    <P>32. Live Nation's subsidiary, Ticketmaster, is the largest primary ticketer in the United States. AEG operates AXS, the second largest primary ticketer in the United States, although it is much smaller than—less than a fifth of the size of—Ticketmaster. Ticketmaster's dominance is especially apparent among major concert venues. In 2022, Ticketmaster's share of primary ticketing for NBA and NHL arenas exceeded 70%, with AXS and SeatGeek trailing. In the past ten years, AXS has not moved a single arena away from Ticketmaster. Live Nation's conduct, including its financial and commercial relationship with venue manager Oak View Group and the conditioning of access to artists on a venue's selection of primary ticketer, vitiates many venues' ability to select a primary ticketer on the merits of its ticketing service, significantly disadvantaging Live Nation's rivals when they compete for primary ticketing contracts.</P>
                    <P>33. In light of existing market dynamics and Live Nation's conduct, it has been and remains rare for venues in the United States to be “open,” which would mean that the dynamism of competition would decide what primary ticketer wins the contract for a particular concert at a particular venue. Instead, primary ticketers, notably Ticketmaster, typically contract to be the exclusive ticketer for a major concert venue for a period of many years, offering venues up-front payments in the form of signing bonuses and sponsorships. Indeed, Ticketmaster's exclusive contracts cover more than 60% of ticket sales to major concert venues and more than 75% of concert ticket sales to major concert venues. These exclusive agreements contractually bar any option of having more than one ticketing company offering differentiated services to fans at such venues for a single show or even across shows, with very limited exceptions. This model that locks in the certainty of exclusivity over the dynamism of open competition is an intentional business strategy found in the Ticketmaster-dominated primary ticketing market in the United States, but does not burden competition for such services in many other parts of the world not dominated by Ticketmaster.</P>
                    <P>
                        34. In other countries, many venues are “open.” For instance, in France, concert tickets are often held in a central inventory management system that is accessible by multiple ticketing 
                        <PRTPAGE P="41335"/>
                        companies. And in the United Kingdom, a promoter often allocates bundles of tickets to multiple ticketing providers. No matter the form it takes, an “open” system means that artists, whose incentives for a lower-cost, higher-quality concert experience are more closely aligned with fans, are more likely to play a role in choosing the ticketing company of their choice.
                    </P>
                    <P>35. In addition to the primary ticketer, fans can buy tickets through a secondary ticketing platform, where individual ticket holders, season ticket holders, or businesses can re-sell tickets to other fans. Secondary ticketing platforms earn revenue through fees paid by the seller of the ticket and, usually, fees paid by the buyer of the ticket as well.</P>
                    <P>36. Ticketmaster's ticketing agreements with a venue sometimes entitle Ticketmaster to control secondary ticketing services in addition to primary ticketing services. Ticketmaster's overall share of resale tickets in North America has grown rapidly since 2019, accounting for nearly one third of ticket resales in 2022. Ticketmaster's rapid increase in secondary market share coincided with its launch of SafeTix technology in or about 2019. SafeTix technology requires that all transfers occur within the Ticketmaster platform. This technology makes it harder for fans to use rivals' secondary ticketing platforms to resell tickets, pushing them instead to the Ticketmaster resale platform.</P>
                    <HD SOURCE="HD2">B. Money Flows Across the Live Entertainment Industry</HD>
                    <P>37. Today, artists who perform at a live concert must navigate a complex web of contracts, business relationships, and money flows across numerous intermediaries and participants. These arrangements often result in fees and charges being split among various industry participants in ways that are not always visible to artists, let alone to fans. Importantly, many of these contracts are interdependent, such that increases to one incentivize or directly influence increases in other areas. And at times, the convoluted web of agreements results in one entity paying on behalf of another, only to then recoup portions of those funds for its own benefit.</P>
                    <P>38. Today, fans pay more in fees associated with live music concert tickets in America than other parts of the world.</P>
                    <P>39. An intermediary, like Live Nation, makes money through a series of interconnected agreements it enters into with artists, venues, rival promoters, and fans by virtue of the many “hats” it wears across the industry. Through these agreements, Live Nation has constructed a live entertainment ecosystem in which Live Nation can not only extract revenues at every stage as an intermediary, but on many occasions, also double-dip across multiple business lines—for example, as both a ticketer and a promoter—creating a feedback loop that inflates its fees and revenue, all at the expense of fans.</P>
                    <P>40. Promoters like Live Nation generate revenue primarily through a pre-agreed split of the gross ticket sales of a show or tour with the artist as well as through payments made by venues to incentivize the promoter to route its artists to perform at a particular venue.</P>
                    <P>41. When trying to secure the right to promote an artist's tour, a promoter and artist often negotiate over the artist's guaranteed payment and the profit split of certain additional concert revenues. For example, Live Nation typically pays an artist the higher of either (1) a percentage of the gross ticket sales less expenses or (2) the artist's guaranteed payment. Guaranteed payments are typically based on the number of performances in the tour, length of the promotion contract, and projected ticket sales, while the percentage of the gross ticket sales less expenses is a set percentage. Live Nation will also enter into some multi-tour deals where the artist will earn even larger cash advances today in exchange for the right to promote the artist exclusively for a certain number of performances or a specific amount of time. While Live Nation sweetens the upfront incentives for certain artists by offering these larger cash advances, they extract recompense in other parts of the ecosystem by, for example, routing their promoted artists through Live Nation's owned and controlled venues or venues exclusively ticketed by Ticketmaster. For other artists, Live Nation typically conditions use of its owned or controlled venues (especially large amphitheaters) on an artist signing with Live Nation as promoter.</P>
                    <P>
                        42. In addition to contracting with artists for promotion services, Live Nation, as a promoter, also frequently and separately contracts with venues to provide booking and promotions services, in exchange for a cut of the venue's revenues associated with the shows it brings to the venue and, occasionally, even a cut from shows that rival promoters bring to the venue. These agreements can come in a variety of forms and are known as “rebate deals,” “co-promotion deals,” or “drawbacks.” These revenues generally are not added to the pool of money Live Nation splits with artists. In fact, some of these payments functionally remit money back to Live Nation that Live Nation initially paid to venues on behalf of its artists (
                        <E T="03">e.g.,</E>
                         facility rental fee rebates). These deals—through which Live Nation can essentially claw back a show's expenditures—reflect Live Nation's power over venues, derived from its influence over artists' decisions about what venues to play and when. Over the past few years, Live Nation has continued to increase its concert promotions fees imposed on venues, which are passed through to fans.
                    </P>
                    <P>43. Ticketmaster, as primary ticketer, collects both the face value of the ticket as well as a host of fees tacked on top of the face value (“primary ticketing fees”). Ticketmaster, owned by Live Nation, retains a portion of the fees. The remaining fees are remitted to other intermediaries like the venue and promoter, which are often Live Nation-owned entities, amounting to paying several of these fees (or portions thereof) to itself.</P>
                    <P>44. “Ticketing” Fees. Americans are well-acquainted with the numerous and different fees appended to the cost of a single ticket to attend a concert today. The numerous fees that are added on top of each other—often with little visibility offered to the fan buying the ticket—contribute to Live Nation's nearly 40% adjusted operating margin in 2023 for its global ticketing business. In addition to charging those fees, Ticketmaster often offers consumers the ability to purchase ticket insurance and “upsells” (such as the option to add parking) at checkout, and it retains a “cut” of these revenues as well. The fees can include, for example:</P>
                    <P>
                        • 
                        <E T="03">“Service” or “Convenience” Fees.</E>
                         Service fees, sometimes called convenience fees, are negotiated between the venue and the ticketer and can be set in a variety of ways. Sometimes the ticketer will receive an agreed-upon dollar amount and/or an agreed-upon percentage of the service fee. Alternatively, the venue and ticketer might agree in advance as to the actual fee that the fan will pay for any event and how to split that. Sometimes, the ticketer will receive a fee based on the face value of the ticket. Under any of those models, the ultimate fee that the consumer pays results from the negotiation between the ticketer and the venue. Generally, under these models, the higher the ticket price, the higher the ticketing fee. As a result, the fee has no meaningful relation to the actual cost of providing the ticketing service, which would not vary ticket by ticket or show by show.
                    </P>
                    <P>
                        • “
                        <E T="03">Platinum” and “Pricemaster” Fees.</E>
                         Not all primary tickets, however, are subject to the typical “service” fees. 
                        <PRTPAGE P="41336"/>
                        Ticketmaster has two dynamic pricing tools, Platinum and Pricemaster. For tickets that are dynamically priced by Ticketmaster, consumers often pay higher ticketing fees. Ticketmaster additionally receives an “inside fee” from the promoter amounting to a double dip by Ticketmaster.
                    </P>
                    <P>
                        • 
                        <E T="03">“Per Order” (or “Handling”) Fees,</E>
                         which are additional ticketing service fees charged on top of each order, separate and apart from the ticketing fees embedded in the service charge. These are often split between the ticketer and the venue.
                    </P>
                    <P>
                        • 
                        <E T="03">“Payment Processing” Fees,</E>
                         which are additional fees charged on certain transactions for processing the electronic payment inherently necessary to purchase any electronically delivered ticket.
                    </P>
                    <P>
                        • 
                        <E T="03">“Facility” Fees,</E>
                         which are fees charged by some venues and typically remitted in full to the venue.
                    </P>
                    <FP>Although venues retain some proportion of ticketing fees described above, a significant proportion of the venue's share is often passed onto promoters, like Live Nation, to incentivize them to steer content to their venue.</FP>
                    <P>45. The face values of tickets are typically set or approved by artists, although promoters' offers also influence face values. Artists, in consultation with their manager and the promoter (either or both of which might be Live Nation employees), can also decide to enable dynamic pricing through Ticketmaster's two dynamic pricing tools, Pricemaster and Platinum, which allow face values to increase based upon the level of demand for a given concert. Promoters and venues use Ticketmaster's Pricemaster tool for “bulk” dynamic pricing of groups of seats, while Platinum tickets, on the other hand, are used to dynamically price at the seat level. For tickets that are dynamically priced by Ticketmaster, whether as bulk or at the seat level, consumers often pay much higher face values. Ticketmaster has a pricing team that makes pricing recommendations—including recommendations as to average and minimum face value of tickets. And typically, it is Ticketmaster's own pricing team that adjusts the face value of tickets based on demand for a particular show.</P>
                    <P>46. Venues earn revenue by renting their facilities to the artist and promoter, selling food, beverages, and merchandise to patrons, collecting ticketing and parking fees, and—sometimes—by sharing in the profit from concerts through co-promotion agreements with promoters such as Live Nation. When venues set aspects of ticket fees, they must not only account for their own operating costs, but also ensure the fees are sufficient to cover all the payments the venues must make to intermediaries like promoters and ticketers. For example, venues must ensure the additional ticket fees cover the fee charged by the primary ticketing service (generally Ticketmaster) and offset the various payments they must make to the promoter (often Live Nation). Because of the interrelated nature of contracts in the industry, money often flows in multiple directions to and from various intermediaries, sometimes in both directions for a single show.</P>
                    <P>47. Live Nation tells the public that the service fees are decided by the venue. While it is nominally true that “[t]he venue decides on the service fees,” in reality, these decisions are predicated upon the portion of those fees that Live Nation (via Ticketmaster) will retain in the first instance—an amount Live Nation negotiates with each venue in advance of the venue setting the amount of the fee. This arrangement is consistent with the many other fees extracted at various stages; those fees may superficially be set by a market participant other than Live Nation or Ticketmaster, but Live Nation and Ticketmaster nonetheless have a hand in setting nearly all these fees and often benefit financially from a significant portion of these fees.</P>
                    <P>48. In other words, Live Nation's various contracts operate together to drive up the overall number and size of fees paid by fans. For example, under many Ticketmaster contracts, when venues increase their own fees to offset Live Nation's concert promotion charges, Ticketmaster is entitled to receive a “ticketing” fee. This double-dip by Live Nation (as promoter) and Ticketmaster (as ticketer) means venues have to raise fan-paid fees just to offset Live Nation's promotions charges. For example, a venue forced to pay Live Nation a $5 promotions rebate and Ticketmaster a portion of any increased fees would need to raise fees on fans by significantly more than $5 to break even.</P>
                    <P>49. Secondary ticketing providers earn revenue through fees paid by the seller of the ticket and, usually, the buyer of the ticket as well. Ticketmaster provides secondary ticketing services via “TM+” to venues when it provides primary ticketing services to the venue hosting the event. Typically, Ticketmaster has sole discretion to set the “buyer” and “seller” fees on TM+ transactions. Ticketmaster also sells secondary tickets via its “3PE” tool when it does not provide primary ticketing services to the venue hosting the event. For those events, Ticketmaster sets the buyer and seller fees, and Ticketmaster rarely if ever shares fee revenue of those secondary sales with a venue, promoter, or artist.</P>
                    <P>50. In addition to the fees Live Nation extracts under its ticketing and promotions contracts, Live Nation also generates significant revenues from its sponsorship and advertising business. Live Nation takes advantage of its vast network of venues and high volume of tickets to secure substantial sponsorship and advertising revenue—further deepening its pool of profits. It sells signage rights, online advertising, beverage pouring rights, venue-naming rights, and more. Live Nation considers its sponsorship and advertising business to be one of its high-margin businesses.</P>
                    <P>51. Live Nation is able to extract significant revenues through its sponsorship and advertising business in part by controlling access to fans at performances where advertisers want to reach them. By controlling the vast majority of large amphitheaters in the United States—pushing concerts to venues it owns, operates, and/or exclusively tickets; locking in key artist talent; and growing the massive data trove it has accumulated as a ticketer—Live Nation is able to drive substantial advertising revenue that feeds the rest of its business.</P>
                    <HD SOURCE="HD2">C. Live Nation's “Flywheel”</HD>
                    <P>52. Founded in 1996, Live Nation began as a live events promoter. Over the following three decades, Live Nation expanded its reach across nearly the entire live entertainment industry—live events promotions, primary ticketing, secondary ticketing, venue ownership and operations, music festivals, artist management, sponsorships, and more. Live Nation controls wide swaths of live music in the United States because of its multidimensional power.</P>
                    <P>53. Live Nation uses its concert promotion business—the core of its “flywheel”—to feed its other high margin businesses, including Ticketmaster's ticketing business, Live Nation's network of venues, as well as Live Nation's sponsorship and advertising business.</P>
                    <P>54. As Live Nation's CEO put it, concert promotion is the business that gives the company control over content that feeds Live Nation's three high margin businesses:</P>
                    <EXTRACT>
                        <FP>
                            At the core is our flywheel. It's the concert business . . . It's the lower margin part of our business. But in order to get into these three high margin businesses and be competitive, we have to have that scale [in concerts] . . . [Our] leadership position [in 
                            <PRTPAGE P="41337"/>
                            concerts] drives the three high margin businesses that are driving our true cash flow and EBITDA.
                        </FP>
                    </EXTRACT>
                    <P>55. The graphic below, based upon Live Nation documents, demonstrates how the flywheel entrenches Live Nation's profits and power.</P>
                    <P>56. The modified graphic below, based upon Live Nation's public filings, demonstrates how this flywheel generates substantial revenues and profits across Live Nation's businesses.</P>
                    <GPH SPAN="3" DEEP="207">
                        <GID>EN06JY26.086</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="228">
                        <GID>EN06JY26.087</GID>
                    </GPH>
                    <P>57. Live Nation wields its power in concert promotions to fuel and drive its primary ticketing business. This presents a Hobson's choice for major concert venues that Live Nation does not already own or otherwise control: either choose Ticketmaster as their exclusive provider of primary ticketing services and benefit from access to Live Nation concerts, or choose a rival ticketing company and risk losing access to Live Nation concerts. Losing access to even a portion of Live Nation's tours can seriously harm venues that rely on highly profitable concerts.</P>
                    <P>58. Live Nation does not have to threaten individual venues explicitly (although it does) to discourage them from signing ticketing contracts with competitors. The risks are well-known in the industry, and Live Nation's topmost executives remain outspoken that Live Nation likely will steer concerts away from independent venues that do not select Ticketmaster as their ticketer. Live Nation's CEO publicly acknowledged as much in not-so-subtle terms:</P>
                    <EXTRACT>
                        <FP>
                            <E T="03">We can't say to a Ticketmaster venue that says they want to use a different ticketing platform, “If you do that, we won't put shows in your building.” . . . [But] we have to put the show where we make the most economics, and maybe that venue [that wants to use a different ticketing platform] won't be the best economic place anymore because we don't hold the revenue.</E>
                        </FP>
                    </EXTRACT>
                    <P>
                        59. The power and profits from Live Nation's high-margin businesses (including Ticketmaster and 
                        <PRTPAGE P="41338"/>
                        Sponsorship &amp; Advertising) help keep the flywheel spinning by financially fueling (what may appear on paper to be) Live Nation's less profitable promotions business. Live Nation can do this in a number of ways. For example, for top artists, Live Nation can use profits from other business lines to fund break-even or even unprofitable exclusive promotion contracts on a standalone basis to keep feeding the flywheel. Rival promoters often find themselves unable to match Live Nation's offers to artists because Live Nation can subsidize artist offers with profits from ticketing and other higher margin businesses. (Of course, some of Live Nation's exclusionary conduct also is aimed at weakening or eliminating rivals, and reducing the amount Live Nation needs to bid to win artists' business). At the same time, artists who do not choose Live Nation to promote their shows or tours can find themselves locked out of Live Nation-owned and controlled venues, including Live Nation's large stable of amphitheaters that are more accessible for fans.
                    </P>
                    <P>60. Live Nation also uses consumer data—acquired through primary and secondary ticketing sales—to augment its ability to feed its flywheel. As Live Nation's CEO put it: “No one has 80 million customers segmented in a database as rich as ours . . . that audience and that platform is really the key, unique part of our business.”</P>
                    <P>61. As described below, Live Nation's conduct and anticompetitive scheme further create and enhance barriers for rivals and nascent threats while cementing Live Nation's grip on nearly every corner of this ecosystem. Industry participants recognize that rivals must participate at scale and at multiple points of the concert ecosystem to compete effectively with Live Nation. For example:</P>
                    <P>• Live Nation's self-reinforcing conduct and power in promotions, ticketing, and venue access disadvantages rivals that do not have a similar portfolio of intertwined assets, increasing barriers for those that do not enter and expand in multiple markets simultaneously.</P>
                    <P>• Ticketing rivals must invest in and develop ticketing systems robust enough to handle high-demand on-sale events for popular artists, fraud/protection and credit card access for fans, and back-office support. Rival ticketers must also accumulate sufficient data to target, market, and advertise shows to fans, as well as sufficient working capital to secure business, all at a time when there are limited opportunities to even compete to dislodge Ticketmaster's monopoly that is maintained by long-term, exclusive ticketing contracts and the content threat and thereby recoup this investment.</P>
                    <P>• Promotions rivals face similar obstacles. They need significant capital to fund tour payments (often millions of dollars), enough scale to hedge against the risk of any single tour failing, extensive relationships with artists, artist managers, agents, and venue operators (and, on the flip side, willingness of those market participants to use a competitor without the fear of retaliation by Live Nation or its surrogates), and enough experience and data from previous tours to make effective routing and pricing recommendations to artists.</P>
                    <HD SOURCE="HD2">D. History of Live Nation and Ticketmaster</HD>
                    <P>62. SFX Entertainment, which later became Live Nation, was founded in 1996 and rapidly began rolling up smaller entertainment companies to consolidate power in concert promotions. That strategy continues today. As Live Nation's current CEO has explained, this strategy of consolidation “from day one” is part of the company's DNA: “we want to continually be the largest promoter in the world, have as many boots on the ground in as many cities and countries in the world as possible . . . .”</P>
                    <P>63. Ticketmaster, Inc. was founded in 1976 as an independent ticketing company. It has been the largest primary ticketer for major concert venues for decades. Like Live Nation, Ticketmaster initially rose to power in part through a series of acquisitions that consolidated the company's dominant position in primary ticketing. Ticketmaster also expanded and cemented its dominance by pushing through changes to the structure of ticketing contracts that reduced competitive pressures to lower ticketing fees that are ultimately borne by fans.</P>
                    <P>64. Ticketmaster restructured how ticketing companies get paid for their services. Venues used to pay ticketing service companies to ticket events. But in the early 1980s, Ticketmaster started passing more ticketing costs onto consumers (who effectively have no choice in selecting the ticketer) in the form of fees, and then sharing some of the additional revenue with venues. Second, Ticketmaster began paying venues large upfront advances in exchange for the exclusive, multi-year right to sell and distribute their tickets.</P>
                    <P>
                        65. On February 10, 2009, Live Nation (then known as Live Nation, Inc.) and Ticketmaster (then known as Ticketmaster Entertainment, Inc.), agreed to merge. At the time, Live Nation was an emerging direct competitor to Ticketmaster in primary ticketing services: after spending nearly two years evaluating, licensing, and developing its own ticketing platform, Live Nation had rapidly become America's second-largest primary ticketer at major concert venues.
                        <SU>2</SU>
                        <FTREF/>
                         Alleging the merger would likely substantially lessen competition in the provision and sale of primary ticketing services for major concert venues, the United States and nineteen states and commonwealths 
                        <SU>3</SU>
                        <FTREF/>
                         filed a case challenging the merger under Section 7 of the Clayton Act, 15 U.S.C. 18.
                        <SU>4</SU>
                        <FTREF/>
                         The parties agreed to a consent decree, entered as a final judgment in the Section 7 case on July 30, 2010, allowing the merger to proceed subject to certain conditions.
                        <SU>5</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>2</SU>
                             Amended Complaint at 5-6 ¶ 3, 13-14 ¶ 34, 
                            <E T="03">United States et al.</E>
                             v. 
                            <E T="03">Ticketmaster Ent., Inc., et al.,</E>
                             No. 1:10-cv-00139, (D.D.C. Jan. 29, 2010), ECF No. 5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>3</SU>
                             Specifically, the States of Arizona, Arkansas, California, Florida, Illinois, Iowa, Louisiana, Nebraska, Nevada, New Jersey, Ohio, Oregon, Rhode Island, Tennessee, Texas, Washington, and Wisconsin, and the Commonwealths of Massachusetts and Pennsylvania. 
                            <E T="03">Id.</E>
                             at 1.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>4</SU>
                             
                            <E T="03">Id.</E>
                             at 17 ¶ 46.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>5</SU>
                             Final Judgment, 
                            <E T="03">United States et al.</E>
                             v. 
                            <E T="03">Ticketmaster Ent., Inc., et al.,</E>
                             No. 1:10-cv-00139 (D.D.C. July 30, 2010), ECF No. 15.
                        </P>
                    </FTNT>
                    <P>
                        66. In January 2020, the United States filed a motion to modify the consent decree in the Section 7 case.
                        <SU>6</SU>
                        <FTREF/>
                         Ticketmaster and Live Nation denied the allegations but ultimately agreed to the United States' and some state co-plaintiffs' proposed amendments to the consent decree.
                        <SU>7</SU>
                        <FTREF/>
                         The court entered the amended consent decree as an amended final judgment that, among other things, partially extended the decree's effective date through December 31, 2025.
                        <SU>8</SU>
                        <FTREF/>
                         The court then closed the Section 7 case on February 29, 2020.
                        <SU>9</SU>
                        <FTREF/>
                         Several of the Plaintiff States here were not parties to the 2010 or 2020 decrees.
                    </P>
                    <FTNT>
                        <P>
                            <SU>6</SU>
                             Motion to Modify Final Judgment and Enter Amended Final Judgment, 
                            <E T="03">United States et al.</E>
                             v. 
                            <E T="03">Ticketmaster Ent., Inc., et al.,</E>
                             No. 1:10-cv-00139 (D.D.C. January 8, 2020), ECF No. 22.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>7</SU>
                             Memorandum in Support of Motion to Modify Final Judgment and Enter Amended Final Judgment at 2, 
                            <E T="03">United States et al.</E>
                             v. 
                            <E T="03">Ticketmaster Ent., Inc., et al.,</E>
                             No. 1:10-cv-00139 (D.D.C. January 8, 2020), ECF No. 22.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>8</SU>
                             Amended Final Judgment, 
                            <E T="03">United States et al.</E>
                             v. 
                            <E T="03">Ticketmaster Ent., Inc., et al.,</E>
                             No. 1:10-cv-00139 (D.D.C. Jan. 28, 2020), ECF No. 29.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>9</SU>
                             Minute Order, 
                            <E T="03">United States et al.</E>
                             v. 
                            <E T="03">Ticketmaster Ent., Inc., et al.,</E>
                             No. 1:10-cv-00139 (D.D.C. Feb. 19, 2020).
                        </P>
                    </FTNT>
                    <P>
                        67. In the years since, Live Nation and Ticketmaster have committed additional, different, and more expansive violations of the antitrust laws compared to the narrower scope of the Section 7 case. As detailed below, Live Nation and Ticketmaster have 
                        <PRTPAGE P="41339"/>
                        engaged in ongoing unlawful monopolization of markets across the concert industry in violation of Section 2 of the Sherman Act and state analogues. For example, since 2020, Live Nation and Ticketmaster have unlawfully coopted actual and potential rivals to remove competitive threats and cement Live Nation's and Ticketmaster's dominance of the concert industry. In addition, as also detailed below, Live Nation and Ticketmaster have violated Section 1 of the Sherman Act and state analogues. For example, since 2020, Ticketmaster has entered into long-term exclusive ticketing agreements with venues. The Section 7 consent decree—which addressed a claim different from those at issue here—has failed to restrain Live Nation and Ticketmaster from violating other antitrust laws in increasingly serious ways.
                    </P>
                    <HD SOURCE="HD1">IV. Live Nation Maintains Monopolies and Market Power Across the Live Concert Ecosystem Through an Anticompetitive and Exclusionary Course of Conduct</HD>
                    <P>68. Live Nation maintains and exercises its power through a coordinated pattern of anticompetitive conduct that serves a variety of ends: expanding its scope and reach into every crevice of an increasingly more complex and interconnected ecosystem, eliminating rivals, continuing to increase barriers to entry, and inhibiting competition on the merits. Each act is exclusionary on its own. But the acts also work together across the ecosystem, enhanced by the flywheel and scale effects, to magnify the anticompetitive force of the scheme.</P>
                    <P>69. Live Nation's strategy includes several forms of anticompetitive conduct across its various intermediary roles that work in harmony to protect Live Nation's power and keep rivals at bay. For example:</P>
                    <P>• Live Nation enters into agreements with rivals not only to remove them, but also to cement and expand its dominance.</P>
                    <P>• Live Nation engages in threats (directly or through intermediaries) and pressure campaigns to nullify rivals or nascent threats.</P>
                    <P>• Live Nation relies on “carrots and sticks” to induce venues to sign long-term exclusive ticketing contracts that offer durable protection for Ticketmaster's dominance. Venues have seen that if they sign with a Ticketmaster competitor, they risk losing lucrative Live Nation concerts and may suffer other harmful retaliation.</P>
                    <P>• Live Nation conditions artists' access to its vast and desirable network of amphitheaters and other venues on choosing Live Nation as the promoter, which enables the company to expand its control over artists and third-party venues alike.</P>
                    <P>• Live Nation removes and neutralizes potential competitors and nascent threats via acquisitions, joint ventures, and other contractual agreements.</P>
                    <HD SOURCE="HD2">A. Oak View Group: Nascent Competitor to a Self-described “Hammer” for Live Nation</HD>
                    <P>70. Live Nation and Oak View Group have colluded and established a partnership to allocate business lines, avoid competing with each other, and chart a mutually beneficial plan to cement Live Nation's dominance. Oak View Group is a leading American venue development and management company uniquely positioned to compete against Live Nation. Oak View Group has a portfolio of over 200 venues in the United States, including more than 100 venues that it manages but does not own. It was founded in 2015 by two industry giants whose combined résumés include roles as the former CEO of AEG, the former CEO of Ticketmaster, the former chairman of Live Nation, and the owner of The Azoff Company, whose portfolio includes one of the world's leading artist management companies: Full Stop Management.</P>
                    <P>71. Oak View Group's experience and relationships with venues and artists make it particularly well-suited to be a real competitor to Live Nation in the United States concert promotion business. Oak View Group's ownership structure also gives it a key asset any would-be promotions rival needs to compete against Live Nation: access to capital. In 2018, private equity firm Silver Lake invested $100 million in Oak View Group, in which it now holds a controlling stake.</P>
                    <P>72. Unsurprisingly, then, Live Nation recognized Oak View Group's promotion capability by categorizing Oak View Group as one of its “Biggest Competitor Threats” shortly after Oak View Group was founded. Over time though, Oak View Group and Live Nation morphed from competitors into partners who found it easier and mutually beneficial to work together rather than compete. Oak View Group now operates as an agent and a self-described “pimp” and “hammer” for Live Nation, often influencing venues and artists for the benefit of Live Nation. As Oak View Group's CEO recently emphasized to Live Nation's CEO, “[j]ust like I tell our folks we 100% always protect you and LN on your lanes,” and “I always protect you on rebates, promotor position, ticketing.” The cozy relationship between Live Nation and Oak View Group covers several areas that ultimately impact fans.</P>
                    <P>73. First, Live Nation and Oak View Group have agreed to a competitive détente in concert promotions to avoid competition between the two companies over artists and tours. In 2016, for example, after learning that Oak View Group offered to promote an artist Live Nation had previously promoted, Live Nation's CEO immediately emailed Oak View Group, warning that such competition would only lead to artists demanding more compensation. He wrote: “whats up? We have done his [touring] and vegas[.] Let's make sure we don't let [the artist agency] now start playing us off.” Oak View Group's CEO backed down: “Our guys got a bit ahead. All know we don't promote and we only do tours with Live Nation.” Oak View Group's other co-founder followed up: “Growing pains,” later noting that Oak View Group's executives “should never discuss comp [for artists],” and Oak View Group's talent buyers would work for Live Nation.</P>
                    <P>74. This was not a one-off episode. In 2022, Live Nation's CEO again challenged the CEO of Oak View Group after learning that Oak View Group made another direct promotions offer: “who would be so stupid to do this and play into [the artist agent's] arms”? Oak View Group's CEO again backed down: “We have never promoted without you. Won't.” Oak View Group's CEO later added that he was “[m]ore than happy to do these deals thru LN as I have always been aligned,” and that “I never want to be competitors.”</P>
                    <P>75. As a Senior Vice President at Oak View Group explained to a colleague in 2019 when approached about potentially bidding on a tour: “It has been our policy to stay on the sidelines when it comes to buying and specifically promoting tour dates as we are cognizant not to compete with our partner Live Nation in this side of the business.”</P>
                    <P>
                        76. Second, just as Oak View Group effectively ceded the concert promotions space to Live Nation, Live Nation effectively ceded its arena consulting business to Oak View Group.
                        <SU>10</SU>
                        <FTREF/>
                         Shortly after its founding, Oak View Group formed an alliance with venues to provide “insights and access to premier sports and live entertainment content,” a venture that encroached on 
                        <PRTPAGE P="41340"/>
                        Live Nation's own consulting business, Live Nation Arenas. To relieve this competitive friction, Oak View Group's CEO proposed that Live Nation Arenas combine with Oak View Group and that the head of Live Nation Arenas join Oak View Group's alliance board of advisors, which he did. In his proposal, Oak View Group's CEO warned the head of Live Nation Arenas, “[w]e are experiencing Arena's that want to play us off one another.”
                    </P>
                    <FTNT>
                        <P>
                            <SU>10</SU>
                             Arena consulting services are advisory services for venues that may include assistance with booking shows, selecting and working with promotors and ticketers, and getting sponsorship deals.
                        </P>
                    </FTNT>
                    <P>77. Live Nation identified three paths forward with regard to Oak View Group: “1) Lead 2) Follow 3) or get out of the way.” Live Nation ultimately decided to “get out of the way” in deference to Oak View Group, just as Oak View Group agreed to get out of the way of Live Nation for promotions. In some instances, Live Nation Arenas and Oak View Group decided to partner with one another for agreements with venues, sharing the profits instead of competing for the contracts. The relationship between Live Nation and Oak View Group is so cozy that these venue partnerships were entered into on nothing more than verbal agreements. Through its venue development deals, venue management deals, and venue alliances, Oak View Group can help direct Live Nation content to venues across the country and demand or influence the use of Ticketmaster at these venues.</P>
                    <P>78. Third, Live Nation exploits its long-term relationship with Oak View Group to flip venues to Ticketmaster, further cementing Ticketmaster's power. In 2022, Live Nation and Oak View Group entered into a long-term ticketing services agreement. This agreement makes Ticketmaster the exclusive primary ticketer for the five venues owned by Oak View Group and obligates Oak View Group to “advocate for” exclusive agreements with Ticketmaster for more than 100 venues Oak View Group manages. The agreement also applies to all future venues owned or managed by Oak View Group, essentially locking those venues into long-term exclusive Ticketmaster agreements.</P>
                    <P>79. For Oak View Group-managed venues currently under exclusive ticketing agreements with Ticketmaster, the agreement obligates Oak View Group to advocate to the venues for extensions of those agreements on the existing terms, with an annual increase to Ticketmaster's portion of the per-ticket service fee for primary tickets. For venues not currently utilizing Ticketmaster, the agreement obligates Oak View Group to advocate that the venues enter into exclusive Ticketmaster agreements with predetermined standard financial terms. These terms include fee splits for primary ticket sales that are generally less favorable for the venues than their current ticketing contracts. Nonetheless, Live Nation has enlisted Oak View Group to push these new contracts, subverting the ticketer selection process Oak View Group runs on behalf of its clients. As Oak View Group's CEO explained to Live Nation's CEO, the deal “allows us to tie up all Owned and Operated facilities to 10 year deals, develop a standard A and B market deal for all future projects and to convert all OVG 360 deals to TM now or as they expire for 10 years. . . Appreciate the consideration and partnership and all of us will work diligently on this so we are always aligned with TM.”</P>
                    <P>80. Oak View Group's compensation for its “advocacy” includes a substantial “incentive payment” from Live Nation plus significant annual payments. Through these payments, Oak View Group is able to share in the Ticketmaster monopoly profits it helps protect. Oak View Group projected that the deal would flip at least 22 venues to Ticketmaster over the next four years; Live Nation likewise recognized that this deal was a “win” for Ticketmaster because it “incentiviz[ed]” Oak View Group “to convert all the [Paciolan] buildings to [Ticketmaster].” As venue manager, Oak View Group is able to control which non-incumbent ticketing services are invited to submit bids for ticketing service proposals and often only invites Ticketmaster. The agreement between Live Nation and Oak View Group takes off the table several of the limited opportunities rival ticketers have to compete against Ticketmaster. So far, Oak View Group is on pace to hit its goal: in 2023 Oak View Group converted six venues to Ticketmaster.</P>
                    <HD SOURCE="HD2">B. Live Nation threatens rivals to blunt expansion into U.S. concert promotions</HD>
                    <P>81. Live Nation also wields its power to keep other rivals from expanding in the concert promotions market in the United States. For example, in 2021, Live Nation threatened commercial retaliation against private equity firm Silver Lake, unless one of its portfolio companies, TEG, stopped competing with Live Nation for artist promotion contracts in the United States. These threats ultimately succeeded, and Silver Lake has tried to sell TEG altogether.</P>
                    <P>82. Prior to the TEG incident, Live Nation and Silver Lake had a relationship through Silver Lake's ownership of Oak View Group, which, as discussed above, became a functionary for aspects of Live Nation's anticompetitive scheme. But TEG's attempt to expand its role in the live music industry in the United States—a clear direct threat to Live Nation—quickly threatened to sour that relationship.</P>
                    <P>83. Live Nation's campaign to squash competition with TEG took place at the highest levels. In 2021, Live Nation's CEO complained to Oak View Group's co-founder that TEG was “[f]ull on competitors.” Oak View Group, in turn, conveyed to Silver Lake that Live Nation was “not happy.” Live Nation's CEO then escalated his complaints to Silver Lake directly, conveying: “I am all in on [Oak View Group] where the big play lies with venues—why insult me with this investment in ticketing/promotions etc.”</P>
                    <P>84. Later in 2021, after learning that TEG made offers to prominent artists in the United States, Live Nation executives discussed how “[TEG] will be everywhere” and “will hunt big names.” After learning that TEG succeeded in securing a prominent artist for a concert at the Los Angeles Coliseum, Live Nation used its exclusive ticketing deal with the venue to frustrate TEG's concert. For this concert, TEG had reached an agreement with StubHub where TEG would sell a certain number of tickets on StubHub's platform. In response, Live Nation, through its subsidiary Ticketmaster, which was the exclusive ticketer for all shows at the venue, “threat[ened] not to honor any of those tickets” and demanded that TEG either “unwind” its deal with StubHub or transfer the ticketing proceeds to Ticketmaster. A Ticketmaster executive noted, “if TEG [thinks] they can come into [North America] and take whatever they want off our platform we will have a massive problem.” Ultimately, StubHub stopped selling tickets and attempted to work with Ticketmaster to fulfill the tickets that it had already sold. But Ticketmaster failed to fulfill many of those tickets to StubHub's customers, and hundreds of StubHub's customers were refused entry to the event.</P>
                    <P>85. After learning about the TEG concert, Live Nation's CEO again threatened Silver Lake, TEG, and Oak View Group. As Live Nation's CEO put it, he “fail[ed] to understand” why Silver Lake “continue[d] to invest in a business that competes with LN/OVG. . . .” Live Nation threatened to pull its support from Oak View Group and instead back an Oak View Group competitor unless TEG stopped competing with Live Nation in the United States:</P>
                    <EXTRACT>
                        <PRTPAGE P="41341"/>
                        <P>I can assure you the OVG investment is a much bigger win then T[E]G . . . . LN declared to back OVG vs other developers or going solo and it's been a huge win for both sides—we have over 20 global arenas in development that neither could do without the other . . . do you really want LN backing [AEG's venue development and management company]. . .? Seems like a dumb trade off??</P>
                    </EXTRACT>
                    <P>
                        86. The co-founder of Oak View Group, who refused to allow TEG to promote any of his large roster of artist clients,
                        <SU>11</SU>
                        <FTREF/>
                         thereafter informed Live Nation that he was going to demand that Silver Lake sell TEG. Live Nation's CEO replied, “Love ya.”
                    </P>
                    <FTNT>
                        <P>
                            <SU>11</SU>
                             Oak View's co-founder also owns a large artist management company, Full Stop Management.
                        </P>
                    </FTNT>
                    <P>87. TEG soon stopped competing for concert promotions in the United States. Silver Lake now seems “intent on dumping teg” and has asked, through the founder of Oak View Group, whether Live Nation would be interested in purchasing TEG.</P>
                    <HD SOURCE="HD2">C. Using “carrots” and “sticks,” Live Nation locks venues into exclusive, long-term ticketing agreements with Ticketmaster that shut out competition</HD>
                    <P>88. Live Nation puts a “choice” to venues: use Ticketmaster and potentially receive a significant payment for long-term exclusivity or use another ticketer and risk losing access to the vast array of Live Nation assets, including lucrative concerts. Sometimes Live Nation is bold and communicates this threat directly. Other times, the expression of the threat may be implicit, but the meaning is self-evident. And in some circumstances, Live Nation deploys its extensive network of intermediaries to communicate this “choice.” Sometimes, the “choice” does not have to be communicated at all. It is well understood across the live concert industry, as a result of Live Nation's historical conduct and exactly as Live Nation intended, that choosing ticketers other than Ticketmaster carries enormous risk and financial pain.</P>
                    <P>89. Live Nation's reputation and history of retaliation are so well known in the industry that Live Nation does not have to (although it still does) explicitly threaten individual venues. Instead, its threats have become more public and generalized. As Live Nation's CEO told the industry in 2019, Live Nation's concert promotions business decides to host concerts “where we make the most economics,” which usually means venues where Ticketmaster holds the primary ticketing contract. Venues considering primary ticketing options understand all too well the risks of switching to another ticketer, and some even model the loss they would suffer if they switched and lost access to some of Live Nation's concerts. The threat of steering shows away from venues allows Live Nation to exercise its monopoly power to get better promotions deals and impose Ticketmaster on venues.</P>
                    <P>90. Live Nation has a number of punitive tools it can use to retaliate against venues, even without making good on the catastrophic threat of pulling or moving concerts completely. In addition to reducing the number of concerts it places at a venue, Live Nation has the power to move shows to less desirable and less lucrative dates, curtail promotional efforts, and force venues to disable secondary ticketing on non-Ticketmaster platforms (potentially making unsure fans less likely to commit to tickets in the first place and frustrating fans who do buy tickets but change plans).</P>
                    <P>91. These kinds of threats and punishments are not just how Live Nation acquired its outsized power in every corner of this industry. In fact, Live Nation has continued to use this playbook in recent years. For example, in 2021, Live Nation threatened retaliation against a venue that had decided to switch from Ticketmaster to SeatGeek for primary ticketing. That venue had decided to switch, in part, because SeatGeek offered to share a greater percentage of the fees associated with secondary ticketing.</P>
                    <P>92. Upon learning about the potential switch, a senior Live Nation executive texted a not-so-subtle warning to the venue's CEO: “Apparently seatgeek are telling [nearby venue] and others that they have a contract deal with you guys already?? Anyways should think about bigger relationship with LN not just who is writing a bigger sponsorship check.” A few days later, Live Nation's CEO emailed the venue's owner that Live Nation “will be very concerned that seatgeek a secondary provider will be selling our LN artist tickets when not authorized by the artist.”</P>
                    <P>93. Once the venue switched to SeatGeek, Live Nation followed through on its threats, re-routing concerts to other venues. Live Nation's promotions business also demanded that the venue disable secondary ticketing on SeatGeek's platform for all Live Nation-promoted concerts, depriving the venue and SeatGeek of secondary fee revenue.</P>
                    <P>94. Live Nation eventually relented and allowed the venue to enable secondary ticket sales—but only after (a) the venue agreed to split its share of secondary fee revenue (sourced through SeatGeek) with Live Nation, and (b) SeatGeek agreed to change its ticket-buying interface to make it conform, in some respects, to Ticketmaster's without regard to whether that was what fans or the venue preferred. In particular, Live Nation demanded that SeatGeek change the way it distinguished primary and secondary tickets (to make it more like Ticketmaster) and limit the use of its fan-friendly tool called “DealScore.” Given all of Live Nation's complaints, which it directed to the venue, it is unsurprising that within about a year, that venue returned to Ticketmaster.</P>
                    <P>95. The knowledge and awareness in the industry—that Live Nation will route shows away from venues that do not choose Ticketmaster—is so widespread that other intermediaries deliver threats and warnings to venues for Live Nation's benefit. For example, Oak View Group, Live Nation's self-described “hammer,” has made such threats to at least one venue. And at least one other venue has been warned by a rival CEO that Live Nation would move shows away from the venue if it selected SeatGeek for primary ticketing services.</P>
                    <P>96. Even Live Nation's biggest competitors fear losing concerts if they do not use Ticketmaster. Live Nation's principal competitor, AEG, has an approximately 30% ownership stake in Anschutz Spectacor Management (“ASM Global”), a venue management company that manages more than 30 arenas in the United States. ASM Global resulted from a 2019 merger between AEG Facilities and Spectacor Management Group (“SMG”). Before the merger, SMG's legacy venues had used Ticketmaster as their exclusive primary ticketer, and AEG Facilities' legacy venues had used AXS as their exclusive primary ticketer. Through its minority interest in ASM Global, AEG advocated for AXS to serve as the exclusive primary ticketer for the ASM Global venues AEG now partially owned. But ASM Global's majority shareholder Onex worried that Live Nation would retaliate by withholding shows from ASM Global venues if ASM Global entirely switched away from using Ticketmaster.</P>
                    <P>97. To avoid losing access to concerts at ASM Global venues by “alienating” Live Nation, AEG was forced to accept that Ticketmaster would remain the dominant provider at ASM Global venues despite AEG's partial ownership of ASM Global and AEG's ability to provide an alternative primary ticketer, AXS. AEG agreed Ticketmaster would remain the default primary ticketer for most ASM Global venues, with AEG reserving the right to use AXS for events promoted by AEG.</P>
                    <P>
                        98. These threats—whether direct or indirect, explicit or implicit— coupled 
                        <PRTPAGE P="41342"/>
                        with Live Nation's multi-pronged strategy of long-term exclusive agreements, a history of retaliation, and other exclusionary conduct—means neither venues nor artists are free to choose ticketers based on their own assessment of price, quality, or value. They are not free to choose a ticketer based on the best technology, or most favorable contract terms, or simply what works best for them or—importantly—what works best for the fans that fill venues to see their favorite artists. Instead, venues, artists, fans, rivals, and others throughout the live concert industry must navigate an ecosystem created by Live Nation, defined by its dominance in promotions 
                        <E T="03">and</E>
                         ticketing, together with its extensive network of venues (especially amphitheaters), and limited by Live Nation's restrictions and restraints.
                    </P>
                    <HD SOURCE="HD2">D. Ticketmaster's long-term exclusive agreements with venues are designed to lock up share and lock out competition, which forecloses a substantial share of primary ticketing markets</HD>
                    <P>99. Ticketmaster's long-term, exclusive agreements with venues are a key tool to protect Live Nation's stranglehold on the live concert industry, and on primary ticketing in particular. These agreements make Ticketmaster the sole provider of primary ticketing services for all or nearly all events held at a venue for multiple years, sometimes as long as 14 years.</P>
                    <P>100. Ticketmaster's exclusive agreements cover more than 75% of concert ticket sales at major concert venues, foreclosing a substantial share of the primary ticketing market from rival ticketers. In 2022 alone, for example, Ticketmaster signed several lengthy deals with major concert venues.</P>
                    <P>101. Ticketmaster is quite clear about why it focuses on these deals: they are, in Ticketmaster's own words, a “[h]edge against significant improvements by the competition or even a new competitor” because the “client is under contract for longer and not able to leave [Ticketmaster] or price the competition's offer into our new deal for an extended time.” In other words, even if a rival ticketer were to offer a better price, a better product, or simply a better ticketing experience, a Ticketmaster-exclusive venue would not be able to choose the rival for a long time, often a decade.</P>
                    <P>102. Before its long-term exclusive agreements expire, Ticketmaster also works defensively to deny rivals the opportunity to compete at all, by, for example “[m]itigat[ing] competitor growth.” Ticketmaster often renews or extends these ticketing agreements before they expire, thus preventing rivals like SeatGeek and AXS from being able to bid at all. This not only eliminates the chance Ticketmaster will lose the contract but also mitigates competitive pressure on Ticketmaster to improve the terms of the contract. As one internal Ticketmaster presentation from 2021 recognized: “When We Compete with [SeatGeek] on an Open Bid, We Can Lose . . . GM [Gross Margin]/Ticket.” To prevent competition, Ticketmaster analyzed top sports leagues and venues to identify “key clients to renew early and ensure continued concert revenue and block SeatGeek.”</P>
                    <P>103. To ensure their existing locked-in venues agree to early renewals and thereby block competition from a rival for the contract, Ticketmaster used COVID-19 as an opportunity to extend the terms of its existing long-term venue ticketing agreements by one year. After one venue resisted, telling Ticketmaster that it disagreed and intended to sign with a rival, Ticketmaster's counsel wrote: “Any effort by [the venue] to switch ticketing service providers before [the extension date] would be a breach of contract, and any announced intention to do so would be an anticipatory breach.” In a conversation between that venue's CEO and Live Nation executives, Live Nation's CFO indicated Live Nation would “drop” the contractual dispute if the venue agreed to enter into a new ticketing contract with Ticketmaster, but not if the venue went with a rival.</P>
                    <P>104. Ticketmaster's renewal strategy not only blocks potential rivals but also creates friction—legal costs and otherwise—to ensure venues do not even try to pursue a competitive bidding process. These tactics have worked: Ticketmaster has publicly touted its “incredible high renewal rate,” which, historically, is virtually 100%.</P>
                    <P>
                        105. These strategies are part of a deliberate and defensive series of actions and decisions designed to lock up venues, lock out competitors, and hold the industry hostage from innovation and evolution. For example, Ticketmaster considered the pros and cons of “opening” venues in the United States, that is, eliminating its exclusivity to permit multiple primary ticketers to service a venue or a particular concert. It recognized that fans could benefit from open venues because it would be “easy to find &amp; purchase tickets anywhere (
                        <E T="03">e.g.,</E>
                         [StubHub, SeatGeek], Groupon)” and fans could find “competitively priced tickets across various touch points.” Venues too could benefit, because having multiple ticketers would enable venues to “limit risk of unsold inventory, `pack the house,' ” “maximize revenue among primary inventory (reduce resale),” “limit bad PR from resale arbitrage attributed to sell-outs,” and “reach new audiences/better know their fans.” When venues have proposed non-exclusive ticketing contracts, Ticketmaster has almost invariably rejected the request, even outside the live concerts space. For example, after one NHL team requested a non-exclusive ticketing deal, a Ticketmaster executive forwarded that request internally, stating his reaction, “Protect our Exclusivity for primary of course.” That Ticketmaster contract remains exclusive.
                    </P>
                    <P>
                        106. And even though Live Nation agreed to limited non-exclusivity for AEG-promoted shows at certain ASM Global venues as part of its recent contract negotiation—to dislodge its largest ticketing rival (AEG's AXS) from the very venues that its largest promotions rival (AEG) partially owns—one Ticketmaster executive stated internally: “[i]t's not something we would do for another client.” If even AEG must acquiesce to Live Nation's demands that Ticketmaster exclusively ticket every show at AEG's own affiliated venues—save those shows promoted by AEG—no other major concert venue owner stands a chance. And when other clients—none of which owns a sizable ticketer or promoter—
                        <E T="03">have</E>
                         asked for a similar arrangement, Ticketmaster has “shot it down as a non-starter.”
                    </P>
                    <P>107. While the industry and fans would benefit from “opening,” Ticketmaster and its parent company, Live Nation—as the incumbent monopolists—would not. As one Ticketmaster executive has recognized: “Open is WAY more attractive as a competitor strategy, not as an incumbent.” For Ticketmaster, the success of exclusivity combined with Ticketmaster's already high market share in the United States are fool-proof ways to maintain its empire, the benefits of which are reflected in Ticketmaster's bottom line. Primary ticketing fees are far higher in the United States than in other countries around the world:</P>
                    <GPH SPAN="3" DEEP="261">
                        <PRTPAGE P="41343"/>
                        <GID>EN06JY26.088</GID>
                    </GPH>
                    <P>108. Ticketmaster's exclusive agreements also inhibit the growth of more specialized ticketing services and different business models. For example, Ticketmaster's exclusivity provisions deny most artists the ability to sell tickets directly to their most passionate fans and “fan clubs” through pre-sale windows. Since third parties often charge less than Ticketmaster, when selling to fan clubs through non-Ticketmaster ticketing systems, artists are better able to control ticketing fees. Through fan clubs or other alternative ticket distribution methods, artists can also offer tickets alongside other experiences and opportunities that can improve the concert experience or increase value for fans. Alternative distribution methods can also provide artists greater control over how, when, and to whom tickets are made available. Ticketmaster previously allowed tickets to be sold through third parties to fan clubs in accordance with its Fan Club Policy. But after acquiring one such third-party provider of tickets to fan clubs in 2018, Ticketmaster has used its exclusive ticketing contracts with venues to curtail artists' ability to use third-party providers for fan club sales—at the expense of artists' choice and their relationships with fans.</P>
                    <P>109. Ticketmaster further uses its extensive network of long-term exclusive ticketing contracts to raise the costs of rival ticketers and further heighten barriers to entry. For example, in the areas where despite Ticketmaster's best efforts, competitors still persist, Ticketmaster deploys its vast power and network to protect its monopoly. One example of this is Ticketmaster's encrypted mobile ticket program, SafeTix. Ticketmaster has added SafeTix to its suite of products and services in a manner that protects its position in primary ticketing, expands its position in secondary ticketing, and undercuts the ability of rival ticketers to compete in either aspect of ticketing.</P>
                    <P>110. Pursuant to this program, Ticketmaster replaced the static barcodes on PDF—or other types of electronic tickets—with a constantly refreshing and encrypted barcode. Ticketmaster's SafeTix marketed this change as reducing the risk of ticket fraud from stolen or illegal counterfeit tickets. But there were less restrictive ways to reduce fraud. Ticketmaster's own documents show that a primary motivation behind its push for a non-transferable digital ticket was to make it more difficult for a fan who wishes to buy or sell a SafeTix-encrypted ticket through a secondary platform to use a rival platform like StubHub or SeatGeek. One document from a Ticketmaster executive meeting in 2014, for example, describes the “non-transferrable digital ticket” as “a game-changer.” Another document from 2017 describes the rotating barcode as a “product enhancement[ ] for market share” and an opportunity to “REDUCE TM'S ECONOMIC RISK.”</P>
                    <P>111. Further, SafeTix introduces uncertainty as to when, or even whether, that ticket can even be transferred. If a ticketholder wants to sell or otherwise transfer a SafeTix-encrypted ticket, both the ticketholder and the purchaser must create Ticketmaster accounts (thereby providing Ticketmaster with their data), download the Ticketmaster app, and wait for Ticketmaster to determine when or whether the transfer can be completed. By reducing the incentives to enter secondary ticketing altogether, SafeTix not only reduces competition from existing rivals but also disincentivizes prospective innovators from considering secondary ticketing as a viable foothold for entering primary ticketing.</P>
                    <P>
                        112. In addition to inserting Ticketmaster as an intermediary into secondary ticket transfers and transactions, SafeTix has also fortified Live Nation's data advantages over its rivals. According to internal documents, SafeTix was expected to grow the “size/value of the TM database,” already by far the largest of any ticketer, by as much as 30 to 40%. As Live Nation's CEO put it, “[o]ne of the advantages we've launched under the transfer strategy is we now not only know the person that bought the ticket, but we're going to know those three people that you are taking to the show, which we have not known historically.” Live Nation can monetize this unique trove of data in its various businesses to both increase its bottom line and further entrench its positions across the live entertainment industry.
                        <PRTPAGE P="41344"/>
                    </P>
                    <HD SOURCE="HD2">E. Live Nation restricts access to its venues unless Live Nation is paid to be the promoter</HD>
                    <P>113. Live Nation's control over a significant number of concert venues not only facilitates maintenance of Ticketmaster's monopoly in ticketing but also serves to limit artists' options and exclude rival promoters. Live Nation has a longstanding policy going back more than a decade of preventing artists who prefer and choose third-party promoters from using its venues. In other words, if an artist wants to use a Live Nation venue as part of a tour, he or she almost always must contract with Live Nation as the tour's concert promoter.</P>
                    <P>114. Live Nation's policy of restricting the use of its venues is particularly problematic for artists seeking to tour in large amphitheaters where Live Nation enjoys monopoly power. These artists—many of whom have well-established, dedicated fan bases but have not yet matured their fan base to play larger stadiums—are effectively forced to hire Live Nation as their promoter or risk being locked out of dozens of desirable Live Nation-controlled large amphitheaters in the United States. Live Nation's amphitheater portfolio includes at least 40 of the top 50, and more than 60 of the top 100 amphitheaters in the United States. No other entity owns more than a handful of amphitheaters in either set. This network of large amphitheaters has allowed Live Nation to attain a greater than 70% market share in large amphitheater promotions and become by far the largest promoter of national amphitheater tours. Put differently, it is nearly impossible for an artist to create a tour that includes stops at amphitheaters without Live Nation. As one Live Nation executive explained, “if [artists] want to do an extensive amphitheater tour with a lot of shows, they would typically be coming to us for that, and they do.”</P>
                    <P>115. Live Nation senior executives know the company has restricted the use of its amphitheaters and other venues for years and often make the choice to sacrifice additional profits the company could be earning as a venue owner by opening its venues to non-Live Nation promoted shows that are available to play at those venues. A 2018 internal Live Nation analysis found that its top 10 amphitheaters are “dark,” or without shows, “on nearly 50% of their Saturdays in the summer,” the highest performing day of the week during the primary performance season. Relatedly, a 2022 analysis found that Live Nation's top 15 amphitheaters are, on average, dark on eight Saturdays between June and September.</P>
                    <P>116. Live Nation also recognizes its amphitheater portfolio gives it control over artists pursuing an amphitheater tour. For example, a senior Live Nation executive directed his employees not to increase guaranteed payments offered to artists they know are looking for “True Amp Tours.” This is because Live Nation recognizes these artists almost certainly will need to play several shows at Live Nation's stable of top amphitheaters, and to do so, they will need to sign with Live Nation as their promoter: “we know [artists] are likely playing amphitheaters and we are going to get those in most cases.” Because many artists sign with Live Nation to promote their entire tour—both amphitheater and non-amphitheater shows alike—Live Nation's restrictive amphitheater policies help the company extend its reach to promoting artists in other venues as well. Further, because relationships are so important in the promotions business, once Live Nation uses its exclusionary amphitheater policy to lock in emerging artists early in their careers, they are able to keep some of those artists as they graduate to higher capacity venues, such as arenas and stadiums.</P>
                    <HD SOURCE="HD2">F. Live Nation strategically acquires promoters, venues, and festivals to eliminate rivals, expand its network, and grow its “moat.”</HD>
                    <P>117. To protect and expand its positions across the live entertainment industry, Live Nation has pursued a strategy of acquiring nascent threats and neutralizing rivals. This strategy has included acquiring promoters, amphitheaters, festivals, other venues, and even small ticketers, as well as entering into long-term exclusive booking contracts with many venues. Although many of these rivals were relatively small at the time of their acquisitions, Live Nation's internal documents show that the company viewed them as some of its “biggest” threats. This is unsurprising given the lack of sizeable, scaled, national competitors in the markets in which Live Nation operates. Live Nation's conduct has thwarted growth of its rivals and disincentivized investment that might have led to entry. Nonetheless, Live Nation viewed many of these acquisitions of competitors on the “edge” as necessary to protect its “moat” around the live concert ecosystem.</P>
                    <P>118. In its own words: “Live Nation is a company founded on acquisition. At its inception, Live Nation began rolling up the regional world of promoters and venues and has not stopped since.” Over the past decade, Live Nation has acquired dozens of companies across the industry to expand its reach and entrench its positions. Live Nation presentations like the one below describe Live Nation's “Decade of Growth” and acquisitions:</P>
                    <GPH SPAN="3" DEEP="239">
                        <PRTPAGE P="41345"/>
                        <GID>EN06JY26.089</GID>
                    </GPH>
                    <P>119. Live Nation has recognized that one of its “Biggest Competitor Threats” is smaller and regional independent promoters that have the ability to “com[e] in from the edges creating events, opening venues, and purchasing artist inventory.” To address this disruptive potential, Live Nation pursued an aggressive plan to acquire or co-opt key independent promoters, even when the economics of a particular deal did not make sense for its promotions business. Live Nation personnel justified the counterintuitive economics for these transactions by looking at the long-term benefits: reducing competition for artists, including by “keeping the [artist] guarantees down” and stopping competitors from “driving the price up” for artists.</P>
                    <P>120. Live Nation's acquisitions have, over time, constrained artists' choice of promoters. This is especially true for nationwide tours and has the effect of further increasing venues' dependence on Live Nation for content. As a major venue in New York City recognized, Live Nation has made significant acquisitions of top independent promoters over the past decade, eliminating most mid-tier promoters and leaving primarily small, concert promotion companies with little market share.</P>
                    <P>121. Below are some specific examples of Live Nation's acquisition strategy in practice.</P>
                    <P>
                        122. 
                        <E T="03">United Concerts.</E>
                         In 2017, Live Nation acquired United Concerts, a promoter and venue owner in Utah, whose venues included the most popular large amphitheater in the state. Live Nation acquired United Concerts in part to eliminate a potential competitive promotions threat and to starve a competing primary ticketer of customers.
                    </P>
                    <P>
                        123. Before Live Nation bought United Concerts, many venues in Utah, including United Concerts' venues, used a regional ticketing company called SmithsTix.
                        <SU>12</SU>
                        <FTREF/>
                         Internally, Live Nation noted that SmithsTix had taken Ticketmaster's “last client in Utah” and left a “barren landscape[ ]” for Ticketmaster there. Live Nation chose not to acquire SmithsTix directly because doing so would “require us to go to the DOJ [to notify them as required under the 2010 consent decree that it planned to acquire a primary ticketing company] and that's something we wouldn't necessarily want to do.” Instead, Live Nation went bigger while sidestepping the notification requirements of the consent decree: it acquired United Concerts and its venues, and 
                        <E T="03">then</E>
                         converted those venues to Ticketmaster. Left “with only a few small clients,” SmithsTix ultimately went out of business.
                    </P>
                    <FTNT>
                        <P>
                            <SU>12</SU>
                             The prior owner of United Concerts also owned DATATIXS, a regional ticketing company that operated under the SmithsTix brand. SmithsTix provided ticketing services to more than 40 venues throughout Utah, including the arena that the home of the Utah Jazz.
                        </P>
                    </FTNT>
                    <P>124. AC Entertainment. In 2016, Live Nation acquired a controlling stake in AC Entertainment—a regional independent promoter in the Southeast and one of Live Nation's internally designated “Biggest Competitor Threats.” AC Entertainment promoted over 1,000 shows a year, including arena and amphitheater shows. AC Entertainment also controlled the venue booking decisions at 14 historic theaters and clubs throughout Tennessee and the Carolinas and promoted major music festivals, including Bonnaroo.</P>
                    <P>125. Live Nation pursued the acquisition even though it had doubts about the standalone economics of the deal. Live Nation's Chief Strategy Officer explained to Live Nation executives: “The numbers are not super exciting and this feels like more of a defensive move to (I) Keep [rival] AEG out of the region especially creating situation where [a well-known artist manager] can play both sides in Nashville.” Live Nation's Chief Strategy Officer also recognized that the acquisition helped “grow[] our moat in the [Nashville] market,” while another internal document touted the benefit of “lower competition in the Region and specifically in Nashville.”</P>
                    <P>126. Frank Productions and National Shows 2. In 2018, Live Nation acquired yet another “Biggest Competitor Threat” in rival promoter, Frank Productions. Frank Productions owned four theaters and clubs in Wisconsin—one of which competed with a Live Nation-operated venue. When its owners looked to transition the business to new ownership as they stepped back, Live Nation jumped at the opportunity to take another edge competitor off the board, and out of the hands of any other potential buyer.</P>
                    <P>
                        127. Live Nation used this acquisition, in part, to convert Frank Productions' venues to Ticketmaster. Frank Productions previously selected other primary ticketing service providers over Ticketmaster because it 
                        <PRTPAGE P="41346"/>
                        had “a difficult time wrapping their head around why they would do business with a company [Live Nation/Ticketmaster] who will be in direct competition with them in their home market.” In a presentation to its Board of Directors, Live Nation executives explained: “[c]urrent ticketing arrangements for certain venues with Ticketfly and Etix set to expire within 2 years” and that, after the acquisition, “[Ticketmaster] to become exclusive ticketing provider for all live events booked or promoted following the expiration of current agreements.” Recognizing that Frank Productions venues' ticketing contracts were set to expire not long after the acquisition, Live Nation acquired the company and then flipped the venues to exclusive Ticketmaster contracts.
                    </P>
                    <P>
                        128. Live Nation also acquired Frank Productions' subsidiary, National Shows 2—yet another firm listed as a “Competitor Threat.” National Shows 2, which promoted over 350 shows per year in the United States, was one of a small number of competitors to Live Nation in the Nashville region after Live Nation bought AC Entertainment, the acquisition described 
                        <E T="03">infra</E>
                         ¶ 122, in 2016.
                    </P>
                    <P>
                        129. 
                        <E T="03">Red Mountain Entertainment.</E>
                         In 2018, Live Nation acquired Red Mountain Entertainment, a regional promoter that promoted shows in Alabama and Mississippi, including several music festivals throughout the Southeast. At the time of the acquisition, Red Mountain also operated and/or exclusively booked concerts at Wharf Amphitheater in Orange Beach Alabama, Brandon Amphitheater in Brandon, Mississippi, and Tuscaloosa Amphitheater in Tuscaloosa, Alabama. Red Mountain had been on Live Nation's radar since at least 2016 when a Live Nation executive indicated it had an “active plan to mitigate further expansion” by Red Mountain because Live Nation “[c]an't get complacent and let small guys encroach from the edges.” Live Nation recognized that Red Mountain's control of the Tuscaloosa Amphitheater was driving up compensation to artists, and so it wanted control of the Tuscaloosa Amphitheater to “keep[] the guarantees down” to artists.
                    </P>
                    <P>130. As Red Mountain grew, Live Nation unleashed what it called a “velvet hammer” by warning that it would cut off “the content flow on artist[s]” to Red Mountain venues if Red Mountain continued to compete as a promoter. A Live Nation executive described the message he communicated to Red Mountain: “Either we are together or we are competitors. Seemed to work, as they had 3 venues, 2 festivals and another venue coming online in [20]18, and wanted the content flow on artists where we had touring rights to in the U.S. Velvet Hammer.” Red Mountain ultimately agreed to sell its business to Live Nation.</P>
                    <P>
                        131. 
                        <E T="03">313 Presents (“313”)</E>
                        . In 2018, Live Nation co-opted a Detroit-based competitor, 313, by entering into a multi-faceted non-compete agreement. Prior to the agreement, Live Nation recognized 313 predecessor organizations, Palace Sports and Olympia Entertainment, as “competitors” since they “make direct offers to artists.” As such, Live Nation and the co-founder of Oak View Group concocted a “scheme” to “put [Olympia] out of the promoting side.” Under the agreement, Live Nation agreed not to compete in the development, operation, or ownership of venues in the Detroit market, while 313 promised “not [to] bid against Live Nation” for artist talent. 313 recognized that “absent all parties coming together, we would be forced into a competition that would only benefit artists.”
                    </P>
                    <P>132. Live Nation and 313 also agreed on other terms. For example, they agreed: (1) to pool certain revenues across aspects of the Detroit market; (2) Live Nation would serve as the exclusive promoter for all three amphitheaters controlled by 313, which are the three largest amphitheaters in the Detroit market; (3) 313 would provide Live Nation the opportunity to co-promote any shows purchased by 313 for Little Caesars Arena or Comerica Park in Detroit; and (4) that Live Nation will not build, develop, own, or operate any music or comedy venue in the Detroit market.</P>
                    <P>133. The agreement worked to suppress competition to the benefit of both parties. 313 Presents saw reduced talent costs and avoided competition from an expanding venue operator. Live Nation, meanwhile, disarmed another promotions competitor, secured exclusive deals at three amphitheaters, and locked-up several venues with Ticketmaster for years to come. Today, 313 controls several of the most popular concert venues in the Detroit live music hub.</P>
                    <P>
                        134. 
                        <E T="03">ScoreMore Shows.</E>
                         ScoreMore Shows was a regional promoter in Texas that Live Nation identified as a “Competitor Threat.” Around 2017, Live Nation agreed with ScoreMore not to compete to sign artists in Dallas and to pool their collective revenues to co-promote artists. After that agreement was in place, in 2018, Live Nation acquired a majority stake in ScoreMore Shows. Internal Live Nation documents celebrated that ScoreMore and Live Nation were “no longer competing” or “driving the price up” for booking artists. Live Nation replaced rivalrous competition with cooperation. As the CEO of ScoreMore Shows stated to Live Nation:
                    </P>
                    <EXTRACT>
                        <P>[Y]ou are forgetting that in pooling these revenues it also meant that we were no longer competing. We weren't driving the price up, either. We haven't been sending offers or telling agents anything but “yes, that's good, we work with LN, we will copro[mote] there.” [S]o if we were on our own (without the pool), sending our own offers, putting in indie rooms, driving the price up . . . do you think the [contribution margin] would be the same? [W]ould you still think we don't provide the value?</P>
                    </EXTRACT>
                    <P>135. For Live Nation, the value of no longer competing with ScoreMore meant that it could book more shows while paying less to artists. Live Nation's CEO wrote to ScoreMore's CEO, “I agree that measurement is what you book and what you stand down for overall win. . . .”</P>
                    <P>
                        136. 
                        <E T="03">Logjam Presents.</E>
                         In 2023, Live Nation acquired a majority stake in Logjam Presents, the leading promoter and venue operator in Montana. Prior to the acquisition, the Logjam Presents venues used a competing primary ticketing service provider. As with previous acquisitions, Live Nation switched Logjam venues from the competing primary ticketing service provider to Ticketmaster once its ticketing agreement expired.
                    </P>
                    <P>137. At the same time Live Nation was acquiring the businesses identified above, Live Nation was also building a “top tier festival portfolio through acquisitions.” Live Nation recognized that the “Proliferation of Festivals” was one of its “Biggest Competitor Threats” because these outdoor shows threatened to “cannibaliz[e] high margin amp shows.” In executing this strategy, and to help protect its power and position in amphitheaters, Live Nation acquired several popular and widely attended festivals, including, Austin City Limits, Lollapalooza, Electric Daisy Carnival, Bottlerock, Mountain Jam, Shaky Knees, Houston Free Press Summer, Governor's Ball, and others.</P>
                    <P>
                        138. Beyond its outright acquisition of venues, some of which are described above, Live Nation has entered into long-term exclusive booking contracts to augment its control of venues, particularly large amphitheaters. In recent years, Live Nation has entered into long-term exclusive booking agreements with more than a dozen large amphitheaters and long-term leases with several additional 
                        <PRTPAGE P="41347"/>
                        amphitheaters as well. While the specific terms vary from agreement to agreement, these exclusive booking agreements generally provide Live Nation the exclusive right to control which artists may use the venue, cementing Live Nation's ability to reward artists it promotes while locking out artists promoted by third-party competitors. Some agreements also provide Live Nation with some degree of control over other aspects of the venue's operations such as concessions and ticketing.
                    </P>
                    <HD SOURCE="HD1">V. Anticompetitive Effects and Competitive Harm</HD>
                    <P>139. Live Nation has engaged in individual anticompetitive acts that have themselves harmed competition. But those individual acts have also had the desired effect of working together in a mutually reinforcing manner to enhance Live Nation's flywheel, suffocate competition, and inhibit the evolution of the live music industry that competition could and should usher in. Live Nation (and its subsidiaries like Ticketmaster) has inserted itself into nearly every corner of the live music industry, which inures to the benefit of Live Nation, but comes at a real cost to fans, artists, venues, and to the competitive process more broadly. Live Nation's conduct, taken individually and collectively, has complicated and exploited the relationship between artists and fans for the delivery of live entertainment and increased its bottom line.</P>
                    <P>140. The anticompetitive effects of Live Nation's distortion of the competitive process cascade through a number of interrelated relevant antitrust markets and fall upon the various entities within those markets. Live Nation's anticompetitive actions allow Live Nation to impose costs and take more for itself, obstruct innovation, impede competitors and nascent threats, and maintain its monopolies and power.</P>
                    <P>141. Because the competitive process has systematically and intentionally been corrupted, there has been less competition than there otherwise would have been in the live music industry over a variety of dimensions, including, ticketing fees, contractual terms, output, quality, and innovation across the United States, including in every Plaintiff State.</P>
                    <P>
                        142. Due to Live Nation's unlawful conduct, fans across the United States, including fans in every Plaintiff State, have paid more in fees that are not negotiable and cannot be comparison shopped because there are no other options. Fans are forced to pay service and convenience fees, Pricemaster and Platinum fees, payment processing fees, handling fees, and facility fees, often with little visibility into how these fees are assessed. The overcharges stemming from these fees are known as the “Ticketmaster Tax,” and Live Nation, acting as both a ticketer and promoter, has routinely double dipped into the pockets of venues, fans, and artists, taking an outsized cut of what fans pay for live entertainment. Whether the fee is one technically charged by Ticketmaster or someone else (
                        <E T="03">e.g.,</E>
                         the venue), it is the fans who ultimately pay unlawfully inflated prices for concert tickets.
                    </P>
                    <P>143. Fans have also been denied access to the benefits that a competitive process would deliver, such as quality, innovation, and more fan-friendly ticketing options. For example, SeatGeek's refundable ticket program, Swaps, offers refundable tickets that can be returned for 100% credit on a future purchase, for any reason, up to 72 hours before the event. Ticketmaster, on the other hand, has a more restrictive refund policy, and fans are typically confined to a complicated ticket insurance process that costs extra and can only be used in limited circumstances. Flexibility is important to fans, and Live Nation's unlawful stranglehold on the primary ticketing market stifles competition and prevents or impedes more fan-friendly options.</P>
                    <P>144. Lack of competition also restricts opportunities and access for artists, venues, and fans. Live Nation controls nearly every aspect of the live events industry, which results in artists having fewer opportunities to play concerts, and fewer real choices for promoting their concerts, selling tickets to their own shows, and performing at certain venues. Likewise, venues have fewer real choices for obtaining concerts and ticketing services, and many are reluctant to disrupt the status quo due to the financial risk and barriers to entry Live Nation's conduct, as described above, has created, perpetuated, or exacerbated.</P>
                    <P>145. Live Nation's conduct has harmed fans because they have been left with fewer concerts, have had more limited choices among touring artists, have paid higher ticketing fees, and have experienced a lower-quality ticketing experience than they otherwise would have but for Live Nation's anticompetitive conduct.</P>
                    <P>146. Defendants' exclusive ticketing arrangements have allowed them to limit venues' and artists' options and impose supra-competitive fees on fans because there are no meaningful alternatives. This lack of competitive pressure has also disincentivized Defendants from investing in quality and innovation in ticketing. The result is a worse experience for fans than they would have in a competitive marketplace. What fans pay at Ticketmaster-ticketed events therefore does not simply represent the cost of providing ticketing services—it arises from Defendants' unlawful conduct in the live events industry in each Plaintiff State, harming not only the fans, but also the artists and venues.</P>
                    <P>147. As a result of Defendants' unlawful conduct, Plaintiff States and their residents and general economies have suffered damages.</P>
                    <P>148. Live Nation has used its unlawfully maintained power in promotions, large amphitheaters, and ticketing to siphon an inflated portion of the money flows from the concert ecosystems and impose additional costs through a web of overlapping agreements with other industry participants. For example, Live Nation's “take rate”—the sum of the various cuts of fees and payments it takes through contracts across the concert industry—as the dominant intermediary is higher than it would be in a marketplace without Live Nation's anticompetitive scheme. Through interconnected agreements associated with Live Nation's various roles as ticketer, promoter, artist manager, and venue owner, Live Nation has created a feedback loop that pushes ticketing and ancillary fees higher while allowing Live Nation to be on all sides of numerous transactions and thereby double-dip from the pockets of fans, artists, and venues.</P>
                    <P>
                        149. Likewise, Live Nation's role as gatekeeper for the venues it owns or controls, especially large amphitheaters, means that touring artists who intend to play several concerts in large amphitheaters are effectively forced to hire Live Nation, or face reduced compensation and access to fans. Rival promoters are unable to promote artists at many in-demand venues, hampering their ability to compete against Live Nation. And fans attending concerts at Live Nation-controlled amphitheaters get access to fewer shows and see fewer artists than they otherwise would because only Live Nation-promoted artists are allowed to perform there. In many instances, these same fans also face higher prices for ticketing and ancillary services, because Live Nation, acting as the primary ticketer, promoter, and venue owner, faces little competition in each of these interconnected markets. On the other hand, fans who live near the few remaining amphitheaters owned and booked by third parties may not have 
                        <PRTPAGE P="41348"/>
                        access to Live Nation's stable of artists, who are instead routed disproportionately through Live Nation's venues.
                    </P>
                    <P>150. Live Nation has created and now protects a system that inhibits artists, fans, and venues from making choices that should exist in a free market, whether that is choosing a concert promoter or a primary ticketer. And by locking venues into its business model, Live Nation has also dampened competition that otherwise would push fees down for fans. As a result, market forces that ordinarily would constrain the fees borne by fans are absent.</P>
                    <P>151. Each aspect of Live Nation's scheme erects barriers for rivals and nascent threats to compete on the merits in the alleged markets with better, lower-priced, or different services. This scheme also cements an industry structure that requires would-be competitors to enter multiple markets simultaneously and at scale to compete effectively, further increasing entry barriers. Without Live Nation's exclusionary conduct, rivals and nascent threats could bring more innovations to the marketplace, develop important scale to improve offerings, further enhance their competitive reputation, increase investments, create disruptive business models, or expand. If those rivals and nascent threats were able to compete on a level playing field, the entire ecosystem, including artists, venues, fans, and others, would realize the many benefits of competition.</P>
                    <P>152. Based on Live Nation's conduct, venues reasonably fear the disruption, retaliation, and complications of partnering with anyone other than Live Nation lest they lose access to culturally significant and lucrative concerts. That has predictably raised rivals' costs. For example, it has forced at least one ticketing rival to agree to a venue's “make good” or “lost event guarantee” clauses in some of its ticketing contracts if those venues choose that rival and Live Nation, as predicted, retaliates. These clauses obligate the rival ticketer to compensate its venue customer if Live Nation diverts or pulls concerts in response to a venue choosing a rival ticketer over Ticketmaster. In other words, Live Nation's conduct not only constrains which ticketer venues may choose, but also inhibits and raises costs for rival ticketers who try to compete with Ticketmaster.</P>
                    <P>153. Competition on the merits would enable more innovation and better products. For example, rivals might bring fan-focused innovations to the marketplace, such as a more streamlined user interface and purchase flow, insightful presentation of ticket inventory, enhanced buying options, or more flexible refund policies. Instead, those would-be rivals face artificial barriers obstructing their ability to gain traction in the marketplace, which in turn dampens incentives to innovate.</P>
                    <P>154. Live Nation's conduct and power also lessens the competitive pressure to innovate to improve its own products, platforms, and services. Concerns about Ticketmaster's ticketing technology are widespread and have made national news. Facing limited competitive pressure, Ticketmaster has no incentive to invest more into proactively improving its ticketing products, but rather patches holes as problems surface and fans are harmed. Live Nation instead uses the capital it might otherwise spend on technological improvements to sweeten ticketing contracts for venues to keep them locked into long-term exclusive agreements and out of the hands of rivals. During a series of meetings between Ticketmaster's Chief Operating Officer and other Ticketmaster employees, Ticketmaster staff acknowledged in 2021 that Ticketmaster has “historically had [a] duct tape product strategy” and that its assets only “push [the] ball sideways.” Rather than concluding that it needed to innovate different products to accommodate its clients' needs, Ticketmaster concluded that it could “ `over' pay” venue clients “if needed.”</P>
                    <HD SOURCE="HD1">VI. Continuing Violations</HD>
                    <P>155. From at least four years prior to the filing of this Complaint and continuing to the present day, Live Nation has unlawfully maintained its dominance in the primary ticketing industry through a course of exclusionary conduct, causing fans continuing and accumulating harm.</P>
                    <P>156. From at least four years prior to the filing of this Complaint and continuing to the present day, Live Nation has stifled fee competition and suppressed quality and innovation in the primary ticketing services market by entering into long-term, exclusive contracts. Fans have experienced and continue to experience the effects of this reduced competition when purchasing a primary concert ticket to a show ticketed by Live Nation in a major concert venue.</P>
                    <P>157. From at least four years prior to the filing of this Complaint and continuing to the present day, Live Nation has used its power in concert promotions to threaten, retaliate against, and otherwise block venues from working with Ticketmaster rivals. Fans have experienced and continue to experience the effects of this reduced competition when purchasing a primary concert ticket to a show ticketed by Ticketmaster in a major concert venue.</P>
                    <P>158. From at least four years prior to the filing of this Complaint and continuing to the present day, fans throughout the United States have overpaid for primary concert tickets purchased from Ticketmaster.</P>
                    <HD SOURCE="HD1">VII. Relevant Markets and Monopoly Power</HD>
                    <P>159. Courts define a relevant product and geographic market to help identify the lines of commerce and areas of competition impacted by alleged anticompetitive conduct. There can be multiple relevant markets covering the same or similar products and services, and markets need not have precise metes and bounds. A relevant market also may include distinct groups or clusters of customers or sellers, where those customers or sellers are identifiable and particularly susceptible to anticompetitive conduct by a monopolist or others.</P>
                    <P>160. Additionally, there may exist within a relevant product market a nested sub-market that itself constitutes a relevant antitrust market. Such a market may be defined based on differences in products or services within the broader market or differences in the competitive conditions faced by various customer groups within the broader market. Where such a submarket exists, it may be helpful to also examine the effects of anticompetitive conduct within these relevant markets, as the effects may be particularly acute or significant. Additionally, there may be related markets adjacent to each other within an industry that offer distinct products and services, potentially to distinct customers, where competitive dynamics within one market impact competition within the other.</P>
                    <P>161. Live Nation has its tentacles in virtually every aspect of the live entertainment industry. As a result, Live Nation's conduct has harmed artists, venues, and fans through the loss of competition in several relevant antitrust markets related to ticketing and promotions. Practical indicia in the industry, the structure of the industry and behavior of market participants, along with substantial evidence that includes ordinary course documents, economic analysis, and other evidence support the relevant markets identified below:</P>
                    <P>
                        • 
                        <E T="03">Primary Ticketing Services Markets</E>
                        —Primary ticketing providers offer a variety of services to two distinct sets of customers: major concert venues and fans. The particular products and 
                        <PRTPAGE P="41349"/>
                        services offered to and the competitive conditions faced by these two customer groups are distinct but related.
                    </P>
                    <P>
                        ○ First, with respect to venues, there is a relevant market for the provision of primary ticketing services to major concert venues in the United States (“primary ticketing services market”). This market includes within it a relevant submarket, which is in and of itself a relevant market, for the provision of primary 
                        <E T="03">concert</E>
                         ticketing services to major concert venues in the United States (“primary concert ticketing services market”).
                    </P>
                    <P>○ Second, with respect to fans, there is a relevant market for primary concert ticketing offerings to fans at major concert venues in the United States (“fan-facing primary ticketing market”), and there is a relevant market that includes both primary concert ticketing offerings and services that offer resale of concert tickets (“fan-facing ticketing market”).</P>
                    <P>
                        • 
                        <E T="03">Concert Promotions Services Markets</E>
                        —Concert promoters similarly offer a variety of services to two distinct sets of customers: major concert venues and artists. The particular products and services offered to and the competitive conditions faced by these two customer groups are distinct but related.
                    </P>
                    <P>○ First, with respect to venues, there is a relevant market for the provision of concert booking and promotional services to major concert venues in the United States (“venue booking and promotion services”).</P>
                    <P>○ Second, with respect to artists, there is a relevant market for the provision of promotional services to artists performing in major concert venues in the United States (“artists promotions market”).</P>
                    <P>
                        • 
                        <E T="03">Artist Use of Large Amphitheaters</E>
                        —Owners, operators, and exclusive bookers of large amphitheaters offer artists use of large amphitheaters for their shows. The provision of the use of large amphitheaters and ancillary services to artists for large amphitheater tours is a relevant market (“use of amphitheaters market”).
                    </P>
                    <P>162. Even where Live Nation's anticompetitive conduct appears to affect a single relevant market, its effects on fans, artists, venues, and others directly reverberate across the live entertainment industry. Likewise, due to the anticompetitive scheme's overall effect of maintaining Live Nation's market power and monopolies and the self-reinforcing aspects of Live Nation's flywheel, effects are felt across the ecosystem regardless of the market in which any particular anticompetitive act has the most direct impact.</P>
                    <HD SOURCE="HD2">A. Primary Ticketing Services Markets</HD>
                    <P>163. Primary ticketing providers offer venues and fans a variety of related but distinct services. Primary ticketing services allow a venue to sell, track, and distribute some or all of the tickets for a show. From the fan perspective, primary ticketing services allow fans to purchase tickets for a show when it first goes on sale to the public and provide a bundle of services that handle payment processing and customer service. Often in today's market, contracts between primary ticketing services and venues dictate the terms and conditions on which primary ticketers are able to offer tickets to fans, directly impacting (and often limiting) competition for these services from the fan perspective.</P>
                    <HD SOURCE="HD3">i. Primary Ticketing Services to Major Concert Venues</HD>
                    <P>164. The provision of primary ticketing services to major concert venues is a relevant product market. Primary ticketing services are sold to venues, the customers for these services. Primary ticketers contract with venues to provide an array of services. This array of services includes the initial (or primary) sale and distribution of tickets for events at the operative venue, underlying technology, and various business support functions. Primary ticketers for major concert venues require, among other things, sophisticated software capable of handling complex ticketing arrangements and high-demand on-sales, back-office support functions, and consumer data for marketing. In addition, primary ticketers for major concert venues that also host sporting events often must provide support for distributing a team's season tickets. The choice of primary ticketer is a key decision for major concert venues because ticketing operations can materially impact the fan experience at, and reputation of, the venue.</P>
                    <P>165. The venues most directly impacted by Live Nation's scheme are major concert venues. These are venues big enough to host major concerts and able to provide a suitable environment and infrastructure for widely attended concerts, like large arenas and amphitheaters. As a result, major concert venues are popular locations for concerts and generate a substantial portion of their revenue from them. Because primary ticketers individually negotiate with venues over pricing and other terms, primary ticketers take into account venue size and how important concert ticketing is to a given venue when submitting a bid. Because major concert venues are particularly susceptible to the effects of Live Nation's conduct, and can be targeted, they are appropriately considered together in evaluating that conduct. Internal documents indicate that Ticketmaster monitors different categories of venues to inform its business decisions and individual negotiations, including size of venue and importance of concert revenues to the venue.</P>
                    <P>166. The United States is a relevant geographic market for the provision of primary ticketing services to major concert venues. Major concert venues in the United States require providers of primary ticketing services capable of fulfilling contractual requirements within the United States. Internal Ticketmaster documents support the United States as a relevant geographic market. For example, Live Nation evaluates the business and competitive conditions in segments within the United States separately from Canada.</P>
                    <P>
                        167. There are no reasonable substitutes for primary ticketing services to major concert venues, nor is arbitrage reasonably possible. Given the significant investment and technology required to build and maintain a primary ticketing service, self-supply is a not a reasonable substitute for most major concert venues. Additionally, secondary ticketing services are not reasonable substitutes. 
                        <E T="03">First,</E>
                         the intended purpose of secondary ticketing services is different than for primary ticketing services. Whereas primary ticketing services are meant to facilitate and run ticket sales on a venue's behalf, secondary ticketing services are meant to facilitate ticket purchasers' resale of their ticket(s). 
                        <E T="03">Second,</E>
                         ticketholders and fans—not venues—are ticketers' typical customers on the secondary ticketing platform. 
                        <E T="03">Third,</E>
                         the platforms for primary and secondary ticketing services are functionally very different. Internal Ticketmaster documents recognize these kinds of differences by, for example, analyzing the performance and competitive conditions of primary ticketing separately from secondary ticketing.
                    </P>
                    <P>168. For these and other reasons, a monopolist in primary ticketing services to major concert venues in the United States would be able to maintain prices above competitive levels and/or maintain quality below the level that would prevail in a competitive market.</P>
                    <P>
                        169. Live Nation—through Ticketmaster—has a durable monopoly in primary ticketing services for major concert venues in the United States. For example, in 2022, Ticketmaster accounted for at least 70% of the total 
                        <PRTPAGE P="41350"/>
                        face value associated with all tickets sold at large arenas and amphitheaters. An internal Live Nation document indicates Ticketmaster is the primary ticketer for about 80% of the U.S. arenas that host NBA or NHL teams; no other rival ticketed more than 14%.
                    </P>
                    <P>170. Live Nation's monopoly power in primary ticketing for major concert venues in the United States also is demonstrated by its ability to control prices and/or exclude competition. For example, in the United States, where Ticketmaster has a higher market share relative to other markets, Ticketmaster is able to charge higher prices and impose higher fees not tied to higher costs. In addition, Live Nation has the ability to exclude competition. Some examples of its power and scheme are described above, such as successfully threatening and retaliating against venues that consider a rival primary ticketer and imposing various other restrictive contractual terms.</P>
                    <P>171. Live Nation's primary ticketing services monopoly for major concert venues in the United States is also protected by significant barriers to entry and expansion. Successfully building primary ticketing capabilities requires substantial investment and access to scale. Live Nation touts its enormous scale as an advantage. Live Nation's scale and its flywheel exacerbate the barriers to entry and expansion in primary ticketing. Live Nation uses its monopoly power in concert promotions to foreclose competition in primary ticketing and erects additional barriers to entry, which prevent ticketers who are not vertically integrated from competing on a level playing field. Live Nation's agreements and exclusionary conduct act as further barriers to entry because they impede rivals' ability and incentives to compete.</P>
                    <P>
                        172. Within this market exists a narrower relevant product market for the provision of primary ticketing services for concerts and comedy events (“concerts”) 
                        <SU>13</SU>
                        <FTREF/>
                         to major concert venues. There are some unique attributes to providing primary ticketing services for 
                        <E T="03">concerts</E>
                         to major concert venues such that there are no reasonable substitutes, nor is arbitrage possible. For example, some primary ticketing features are particularly important for concerts, including the ability to handle complex on-sale processes, surge traffic, and specific types of marketing initiatives. In addition, financial arrangements contracting, and fees charged to fans for primary ticketing services can differ for concerts as compared to other event types like sports. This is due, at least in part, to how lucrative hosting concerts can be for major concert venues. Thus, viable competitive alternatives for primary ticketing services for concerts at major concert venues can be, and are, different than for other live events. Internal Live Nation documents analyze concert ticketing separately from ticketing for other events and identify venues for which concert revenues are particularly important.
                    </P>
                    <FTNT>
                        <P>
                            <SU>13</SU>
                             Live music concerts and comedy shows (as well as musical artists and comedians) have competitive similarities in terms of tour planning, on-sale events, and venue suitability. Ordinary course evidence suggests that concerts and comedy events are assessed and treated similarly as a matter of industry practice.
                        </P>
                    </FTNT>
                    <P>173. Live Nation—through Ticketmaster—has a durable monopoly in primary concert ticketing services for major concert venues in the United States. For example, Ticketmaster accounts for at least 80% of the total face value associated with all concert tickets sold at major concert venues.</P>
                    <P>174. For the same reasons as stated above, there are substantial barriers to entry and expansion within this narrower market. A monopolist in primary concert ticketing services at major concert venues in the United States would be able to maintain prices above competitive levels and/or maintain quality below the level that would prevail in a competitive market.</P>
                    <HD SOURCE="HD3">ii. Primary Concert Ticketing Offerings to Fans at Major Concert Venues</HD>
                    <P>175. The provision of primary concert ticketing offerings to fans at major concert venues is a relevant product market. Fans rely upon primary concert ticketing offerings to purchase tickets to concerts. Primary ticketers typically provide an online interface to purchase tickets to a concert during an initial on-sale and continue to offer tickets for sale until the show is sold out. In addition to facilitating the purchase of tickets, primary concert ticketing offerings typically also provide customer service to fans, employ mechanisms to detect and prevent fraudulent purchases, store credit card information, keep track of fan purchases, and provide fans other related services. Primary concert ticketing offerings to fans at major concert venues require, among other things, sophisticated software capable of handling complex ticketing arrangements and high-demand on-sales and databases. Currently in the United States, except in rare cases, only a single primary ticketing service is offered to fans to purchase tickets to a given concert, and typically, only one primary ticketing service is offered to fans to purchase tickets during all on-sales for a given venue.</P>
                    <P>176. Resale services offer a different service: the resale of previously purchased tickets. Thus, in order for a ticket to be available for resale on a secondary ticketing marketplace, the ticket must have already been purchased from a primary ticketing offering, with the purchaser having already paid the fees associated with the primary ticketing offering. Accordingly, the fees (and often ticket prices) associated with resale marketplaces are not closely related to the fees associated with primary ticketing offerings, because primary ticketing fees are baked into the price of tickets being resold on these marketplaces.</P>
                    <P>177. Likewise, other means of obtaining tickets during an initial on-sale are limited and not available to all fans. Ticketmaster makes available a limited number of tickets to ticket brokers but charges fees for the initial transfer of tickets to these brokers before those tickets can be resold to fans. Ticketmaster also allows for the limited ticket sales to artist fan clubs in some circumstances, but such ticket sales are limited in number and not all fans are eligible to purchase tickets through these channels. As a result, they do not represent reasonably close substitutes for most fans today, although they could in the future but for Ticketmaster's anticompetitive conduct.</P>
                    <P>178. In addition, fans may not view primary and resale tickets as close substitutes due to a perception that a primary ticket purchase is more “secure” or “guaranteed” as compared to a resale purchase.</P>
                    <P>179. Internal documents indicate that Live Nation tracks its share of primary concert ticketing separately from its share of resale ticketing and identifies a distinct set of competitors in each segment. Live Nation also monitors its share of concert ticketing separate from its share of ticketing for other types of shows.</P>
                    <P>180. The United States is a relevant geographic market for primary concert ticketing offerings for fans. Fans seeking to attend shows in the United States must use primary concert ticketing services that offer tickets for those shows. Internal Live Nation documents support the United States as a relevant geographic market. For example, Live Nation evaluates the business and competitive conditions in segments within the United States separately from Canada.</P>
                    <P>
                        181. For these and other reasons, and consistent with industry information, a monopolist in primary concert ticketing offerings to fans at major concert venues in the United States would be able to maintain prices above competitive 
                        <PRTPAGE P="41351"/>
                        levels and/or maintain quality below the level that would prevail in a competitive market.
                    </P>
                    <P>182. Live Nation—through Ticketmaster—has a durable monopoly in primary concert ticketing offerings to fans at major concert venues in the United States. For example, in 2022 Ticketmaster accounted for at least 80% of the total face value associated with all concert tickets sold at major concert venues.</P>
                    <P>183. Ticketmaster's monopoly power in primary concert ticketing offerings to fans at major concert venues in the United States is further demonstrated by its ability to control prices and/or exclude competition. In the United States, where Live Nation maintains a high market share in arenas and amphitheaters through its exclusive contracts and owned and operated venues, Ticketmaster has much higher fees relative to other countries notwithstanding comparable costs. In addition, Live Nation has the ability to exclude competition by insisting that venues utilize only Ticketmaster for all shows and for all tickets sold for a given show.</P>
                    <P>184. Live Nation's monopoly in primary concert ticketing offering to fans is also protected by significant barriers to entry and expansion. To successfully build primary concert ticketing capabilities requires substantial investment and access to scale. Live Nation touts its enormous scale as an advantage. Live Nation's scale and its flywheel exacerbate the barriers to entry and expansion in primary ticketing. Live Nation uses its market power in concert promotions to foreclose competition for primary ticketing service for fans, while also erecting additional barriers to entry that prevent, by preventing ticketers who are not vertically integrated from competing on a level playing field. Live Nation's agreements and exclusionary conduct act as further barriers to entry because they impede rivals' ability and incentives to compete.</P>
                    <P>185. Although the provision of primary concert ticketing services to fans is a relevant product market, in the alternative, there is also a broader relevant product market that includes both primary concert ticketing offerings and services that provide resale for concert tickets to fans at major concert venues. For the reasons above, primary concert ticketing offerings to fans offer distinct services from resale service providers, and resale marketplaces necessarily rely upon an initial sale of a ticket via a primary concert ticketing service (inclusive of the primary ticketing fees) in order for the resale marketplace to exist. Nonetheless, a fan looking to purchase a concert ticket may be able to purchase such a ticket from a primary ticketing offering or resale service provider. To the extent the two markets are combined into a larger market, internal documents show that Live Nation has substantial market power or monopoly power in this broader market as well.</P>
                    <P>186. The United States is a relevant geographic market for concert ticketing offerings and resale services for fans. Fans seeking to attend concerts in the United States must use ticketing services that offer tickets for those shows. Internal Live Nation documents support the United States as a relevant geographic market. For example, Live Nation evaluates the business and competitive conditions in segments within the United States separately from Canada.</P>
                    <P>187. For these and other reasons, and consistent with industry information, a monopolist in a combined market of primary concert ticketing offerings and services that provide resale of concert tickets to fans for shows in the United States would be able to maintain prices above competitive levels and/or maintain quality below the level that would prevail in a competitive market.</P>
                    <P>188. Live Nation—through Ticketmaster—has a monopoly in this market. For example, in 2022, Ticketmaster accounted for more than 70% of the total transactions associated with all tickets sold or resold for concerts at major concert venues in the United States. Transaction volume is an economically relevant measure of power in this market. Importantly, these numbers capture only transactions handled principally by Ticketmaster. But, as discussed above, because of Ticketmaster's use of technology like SafeTix, Ticketmaster necessitates its involvement in the resale of tickets that take place entirely on rivals' secondary ticketing platforms. In doing so, Ticketmaster is able to exert some degree of control over these transactions as well as obtain valuable fan data related to ticket transfers. As a result, Ticketmaster's share understates its competitive significance in this market.</P>
                    <P>189. Ticketmaster's monopoly power in this market also is demonstrated by its ability to control prices and/or exclude competition. For example, Ticketmaster is able to charge higher prices in areas where its power is greatest (notwithstanding comparable costs), as evidenced by the much higher fees charged in the United States, where Ticketmaster has a high market share, relative to elsewhere where its shares are much lower. In addition, Live Nation has the ability to exclude competition. Some examples of its power and scheme are described above, such as successfully threatening and retaliating against venues that consider a rival primary ticketers and imposing various other restrictive contractual terms.</P>
                    <P>190. Live Nation's monopoly over primary concert ticketing offerings and services that provide resale of concert tickets is also protected by significant barriers to entry and expansion. To successfully build primary ticketing capabilities requires substantial investment and access to scale. Live Nation touts its enormous scale as an advantage. Live Nation's scale and its flywheel exacerbate the barriers to entry and expansion in primary ticketing. Live Nation uses its market power in concert promotions to foreclose competition to become a primary ticketing offering for fans and erects additional barriers to entry, by preventing ticketers who are not vertically integrated from competing on a level playing field. Additionally, Live Nation has taken steps to impede resale providers from efficiently facilitating the resale of tickets, including by hindering the transfer of tickets originally sold by Ticketmaster. Live Nation's agreements and exclusionary conduct act as a further barrier to entry because they impede rivals' ability and incentives to compete.</P>
                    <HD SOURCE="HD2">B. Concert Promotions Services Markets</HD>
                    <P>191. Concert promoters offer a variety of related products and services to two distinct sets of customers: major concert venues and artists. For major concert venues, promoters arrange for, book, and market shows with artists to fill available dates at the venues. These services can take the form of booking one-off performances of an artist or long-term booking agreements where the promoter promises to bring multiple artists to a venue over a period of time. For artists, concert promoters work to plan, finance, and market an artist's show or—as is more often the case—a tour of multiple shows. In this way, although concert promoters are responsible for bringing together an artist and venue to perform a show, the particular form and nature of services they offer venues and artists differ considerably.</P>
                    <HD SOURCE="HD3">i. Concert Booking and Promotion Services to Major Concert Venues</HD>
                    <P>
                        192. The provision of concert booking and promotion services to major concert venues is a relevant antitrust product market. In general, promoters arrange and coordinate artist performances at 
                        <PRTPAGE P="41352"/>
                        venues and help to promote those shows to the public once they are booked. Promoters have significant influence over which venues an artist chooses to play. Typically, venues enter into individualized agreements with promoters (either on a show-by-show or long-term basis), which dictate the payments between venues and promoters in exchange for the performance(s). Concert booking and promotion services are essential to major concert venues because they help ensure the venues receive a steady stream of concert content.
                    </P>
                    <P>193. The venues most directly impacted by Live Nation's scheme are major concert venues. As discussed above, major concert venues have unique characteristics that make it appropriate to include them in this product market. In particular, major concert venues rely on live entertainment for a significant portion of their revenues and thus are unlikely to forego promotion services. Revenue from live entertainment is important to offset substantial fixed costs at these venues, and more events allow venues to allocate those costs across a greater number of shows.</P>
                    <P>194. There are no reasonable substitutes for the purchase of concert booking and promotion services for major concert venues. Booking and promotional services for non-concert events at major concert venues are not adequate substitutes because the venues' average revenue per show from concerts is often higher than from non-concert events. Neither self-promotion nor self-supply is a significant constraint because most venues will be unable to incentivize a sufficient number of artists to choose to perform at their venue without the support of a promoter. Most venues cannot successfully promote concerts at scale because they lack the necessary expertise and relationships and are unwilling to assume the financial risk of a show selling poorly. Industry participants, including Live Nation and venues, recognize that providing concert promotions is a unique business and separately analyze the business and competitive conditions.</P>
                    <P>195. The relevant geographic market for the provision of concert booking and promotion services to major concert venues is no broader than the United States, and there may also be smaller, regional relevant geographic markets. When procuring booking and promotion services, major concert venues in the United States require providers that can service their requirements in the United States. Further, many artists who perform at major concert venues do so as a part of regional or national tours that include venues across the United States. Internal Live Nation documents also support the United States as a relevant geographic market. For example, Live Nation considers the United States to be a distinct reporting segment and separately evaluates the business and competitive conditions in the United States.</P>
                    <P>196. For these and other reasons, a monopolist in the provision of concert booking and promotion services to major concert venues in the United States would be able to maintain prices above competitive levels and/or maintain quality below the level that would prevail in a competitive market.</P>
                    <P>198. Live Nation's monopoly power in concert booking and promotion services for major concert venues in the United States is also demonstrated by its ability to control prices and exclude competition. For example, as described above, Live Nation extracts supracompetitive payments from venues, including large promoter rebates, and otherwise imposes onerous, restrictive contractual terms on venues in exchange for supplying them with content. In addition, Live Nation has the ability to exclude competition in concert promotions through, for example, exclusivity agreements with venues. Some examples of its power and scheme are described above, including using its power to stop rivals or nascent threats from competition in concert promotions.</P>
                    <P>199. Live Nation's power over concert booking and promotion services is protected by barriers to entry and expansion. Promotion contracts with artists, the key input in this market, requires capital, expertise, connections, data, and a demonstrated level of success in the industry. There are also indirect network effects that sustain high barriers to entry in concert promotions. Venues naturally prefer to work with a promoter who is successful in promoting many popular artists, and artists naturally prefer to work with a promoter who is successful in promoting many high-demand shows at popular venues. As described above, in addition to Live Nation's scheme, Live Nation's self-described flywheel and scale-related factors enhance substantial barriers for entry and expansion in this market as well.</P>
                    <HD SOURCE="HD3">ii. Promotion Services to Artists</HD>
                    <P>200. The provision of promotion services to artists performing in major concert venues is also a relevant product market. Artists seek to contract with promoters for their help in arranging individual concerts and tours. Typically, artists enter into contracts with a promoter for a single show, multiple shows, including a tour. Promoters work with artists, and their managers and/or agents, to help the artist choose the venue(s) where they will play, work with venues on behalf of the artist to arrange aspects of the show(s), and then ultimately promote each show in local areas where the artist will perform. Promoters take on the financial risk associated with a show or tour, and in exchange they are compensated with a portion of the revenue generated by successful shows. For artists seeking to perform in major concert venues, promoters are an essential component to ensuring the show or tour is successful.</P>
                    <P>201. Artists who seek to perform all or parts of their tour in large amphitheaters are uniquely impacted by Live Nation's anticompetitive conduct. Because of Live Nation's control over a vast network of large amphitheaters and its policy to only work with artists that it promotes, artists seeking to perform a tour in large amphitheaters are denied the ability to work with the promoter of their choice if they want to play a Live Nation-owned or controlled venue. These artists are forced either to work with Live Nation or forgo an amphitheater tour altogether.</P>
                    <P>202. There are no reasonable substitutes for promotion services for artists seeking to perform in major concert venues. Artist performances in major concert venues are complicated events whose success requires significant industry experience and relationships with different vendors. Self-promotion is not a reasonable substitute for artists because they generally lack the expertise, relationships, and financial resources to promote a show or tour on their own at major concert venues.</P>
                    <P>203. The relevant geographic market for the artist promotions market is no broader than the United States, and there may also be smaller, regional relevant geographic markets as well. When procuring promotion services for performances in major concert venues in the United States, artists require promoters who can service their requirements in the United States. Internal Live Nation documents also support the United States as a relevant geographic market. For example, Live Nation considers the United States to be a distinct reporting segment and evaluates the business and competitive conditions in the United States separately.</P>
                    <P>
                        204. For these and other reasons, and consistent with industry information, a monopolist in the artist promotions 
                        <PRTPAGE P="41353"/>
                        market in the United States would be able to maintain prices above competitive levels and/or maintain quality below the level that would prevail in a competitive market.
                    </P>
                    <P>205. Live Nation currently has monopoly power in the market for the provision of promotion services to artists performing in major concert venues in the United States. Live Nation's policy of blocking third-party promoted artists from using its amphitheaters has enabled the company to grow its share in the artists promotions market, above and beyond what it would have been able to achieve through fair competition. Industry participants, including venue owners, recognize Live Nation's dominance in this market. As one prior venue manager explained, “If you don't do a deal with these guys, you're going to lose shows.” Live Nation as a promoter accounts for around 60% of the total face value associated with all primary tickets sold at major concert venues and more than 70% of the total face value associated with large amphitheater shows in the United States.</P>
                    <P>206. Live Nation's power over the artist promotion services market is protected by barriers to entry and expansion.</P>
                    <HD SOURCE="HD2">C. Artist Use of Large Amphitheaters</HD>
                    <P>207. The provision of the use of large amphitheaters and ancillary services to musicians and comedians (“artists”) for large amphitheater tours is also a relevant product market. “Large” amphitheaters (also known as “non-boutique amphitheaters”) are recognized as a distinct type of venue in Live Nation's ordinary course documents and regular reporting and by industry participants. Large amphitheaters have unique characteristics—including capacity, sight lines, acoustics, seating, and staging—that differentiate them both from smaller amphitheaters and other venues. These unique characteristics make large amphitheaters attractive to both artists and fans in the summer months when most touring takes place, and as a result, there are artists who seek to perform several shows or even entire tours at large amphitheaters in given year. They also are attractive to artists who are not yet able to—or no longer able to—fill a larger venue, like an arena, but have outgrown smaller clubs and theaters. In a similar vein, industry participants, including Live Nation and venues, recognize that large amphitheater concerts constitute a unique business and separately analyze the business and competitive conditions. Large amphitheaters provide artists the use of their venue plus related services, such as staging and lighting, and in exchange, the artist pays rent and performs a show that enables the venue to collect additional revenue from fans, including from food, beverage and parking.</P>
                    <P>208. Artists either work directly with their agent, or through their chosen promoter, to communicate with venues about availability and ultimately choose the amphitheaters where they will perform. When promoters reach out to venues to inquire about availability and pricing, they do so on behalf of a particular artist. Similarly, when promoters contract with amphitheaters owned and/or operated by a third party, they typically do so for a specific artist on a particular day. Put another way, when promoters communicate and contract directly with venues, they are acting on behalf of their artist clients. Those artists are the customers for the provision of use of large amphitheaters who ultimately decide where, when, and under what terms they will perform. The fact that promoters enter into contracts for access to amphitheaters on behalf of specific artist clients does not change the reality that it is ultimately artists who utilize the amphitheaters.</P>
                    <P>209. The artists most impacted by Live Nation's anticompetitive conduct are those interested in performing a tour of large amphitheaters in a particular year. This includes artists seeking to perform exclusively at large amphitheaters as well as artists seeking to construct a tour that includes both a significant number of shows at large amphitheaters as well as shows at other venues. As a practical matter, artists seeking to perform a tour of large amphitheaters typically do not contract directly with individual venues, as artists work with promoters who take on the financial risk of shows or entire tours, arrange shows on their behalf, and promote their shows to their fans.</P>
                    <P>210. Artists seeking to perform a tour of large amphitheaters will not view a tour that excludes large amphitheaters as a reasonable substitute. As described above, large amphitheaters have unique characteristics that distinguish them from other venues, and artists seeking a tour of large amphitheaters will generally not consider a tour wholly excluding large amphitheaters as a reasonable alternative. Industry participants, including Live Nation, recognize that there are artists with a specific interest in touring large amphitheaters.</P>
                    <P>211. The relevant geographic market for the use of large amphitheaters market is no broader than the United States, and there may also be smaller, regional relevant geographic markets. Artists seeking to do a large amphitheater tour often do so as part of regional or national tours across the United States. Internal Live Nation documents also support the United States as a relevant geographic market. For example, Live Nation considers the United States to be a distinct reporting segment and evaluates the business and competitive conditions in the United States separately.</P>
                    <P>212. For these and other reasons, a monopolist who controls the use of large amphitheaters in the United States would be able to maintain prices above competitive levels and/or maintain quality below the level that would prevail in a competitive market.</P>
                    <P>213. Live Nation has monopoly power in the use of large amphitheaters market. Live Nation owns, operates, or exclusively books concerts in more than 55 large amphitheaters in the United States. Live Nation's controlled venues account for at least 65% of the total number of primary tickets and face value associated with all concert tickets sold at large amphitheaters. These measures are economically relevant measures of power in this market. Internal documents from 2022 indicate that Live Nation promoted events account for approximately 70% of all amphitheater shows in the United States.</P>
                    <P>214. Live Nation's monopoly power in the use of large amphitheaters market is protected by barriers to entry and expansion. Entering this market requires significant time, capital and expertise to either build a new amphitheater or sign a contract with an existing amphitheater to operate it. Building a new large amphitheater is particularly burdensome and uncertain, as it requires a potential new entrant to identify a specific location for the facility, acquire the land, secure the necessary permitting, and contract with the many vendors necessary to put on successful shows. Large amphitheaters also require access to artists to ensure financial viability. Because Live Nation routes the artists it promotes to its own existing network of amphitheaters, that makes it more difficult for a new amphitheater to attract the talent necessary to be financially viable.</P>
                    <HD SOURCE="HD1">VII. Jurisdiction, Venue, and Commerce</HD>
                    <P>
                        215. The United States brings this action against Live Nation and Ticketmaster pursuant to Section 4 of the Sherman Act, 15 U.S.C. 4, to prevent and restrain Defendants' violations of Section 1 and Section 2 of the Sherman Act, 15 U.S.C. 1-2.
                        <PRTPAGE P="41354"/>
                    </P>
                    <P>216. The Attorneys General of the Plaintiff States, as the chief legal officers of their respective states, bring this action under their respective and independent statutory, common law, and equitable powers, and in their quasi-sovereign capacities, to prevent anticompetitive conduct that harms competition and the economies of the Plaintiff States and the economic welfare of consumers in and from the Plaintiff States. Plaintiff States have quasi-sovereign interests in protecting consumers—from economic harm resulting from illegal anticompetitive conduct and in ensuring their economies are not suppressed by unjustified restraints of trade.</P>
                    <P>217. The Attorneys General assert these claims based on their independent authority to bring this action pursuant to Sections 4c and 16 of the Clayton Act, 15 U.S.C. 15c and 26, and common law, to prevent and restrain Live Nation's violations of Section 1 and Section 2 of the Sherman Act, 15 U.S.C. 1-2. State attorneys general are specifically authorized to bring suits to obtain treble damages on behalf of natural persons pursuant to 15 U.S.C. 15c and to secure injunctive relief pursuant to 15 U.S.C. 26, for violations of the Sherman Act.</P>
                    <P>218. This Court has subject matter jurisdiction over this action under Section 4 of the Sherman Act, 15 U.S.C. 4, Sections 4c and 16 of the Clayton Act, 15 U.S.C. 15c and 26, and 28 U.S.C. 1331, 1337(a), and 1345(d), and has supplemental jurisdiction under 28 U.S.C. 1367(a).</P>
                    <P>219. The Court has personal jurisdiction over the Defendants, and venue is proper in this District under Section 12 of the Clayton Act, 15 U.S.C. 22, and under 28 U.S.C. 1391, because all Defendants transact business and are found within this District.</P>
                    <P>220. Defendant Live Nation is a Delaware corporation with its principal place of business at 9348 Civic Center Drive, Beverly Hills, CA 90210, and an office at 430 W 15th Street, New York, NY 10011. Defendant Ticketmaster is a Virginia limited liability company with its principal place of business at 9348 Civic Center Drive, Beverly Hills, CA 90210. Ticketmaster operates from offices in various locations, including at 430 W 15th Street, New York, NY 10011.</P>
                    <P>221. Each Defendant engages in, and its activities substantially affect, interstate trade and commerce. Each Defendant provides a range of products and services that are marketed, distributed, and offered to consumers throughout the United States, in the Plaintiff States, across state lines, and internationally. Defendants' actions and course of conduct are ongoing and are likely to continue or recur, including through other practices with the same purpose or effect.</P>
                    <P>222. Defendants' conduct had and continues to have substantial interstate and intrastate effects because major concert venues and artists within each Plaintiff State have been coerced by Live Nation's long-term, exclusive contracts and monopoly power. As a result, fans residing in each Plaintiff State have been forced to continue paying supracompetitive fees for concert tickets, which, in the absence of Live Nation's anticompetitive scheme, would have been reduced as a result of competition from other primary ticketing providers and promoters.</P>
                    <HD SOURCE="HD1">VIII. Antitrust Injury</HD>
                    <P>
                        223. As a direct and proximate result of the unlawful conduct alleged above, consumers in the Plaintiff States were not and are not able to purchase tickets to live events at prices determined by free and open competition, and consequently have been injured in their property in that, 
                        <E T="03">inter alia,</E>
                         they have paid more and continue to pay more for fees relating to tickets to live events than they would have paid in a free and open competitive market. The Plaintiff States cannot quantify at this time the precise amount of monetary harm which their consumers have sustained, but allege that such harm is substantial. A precise determination of this amount will require discovery from the books and records of the Defendants and third parties. As a direct and proximate result of the unlawful conduct alleged above, the general economies of the Plaintiff States have sustained injury, and are threatened with further injury to their property unless the Defendants are enjoined from their unlawful conduct.
                    </P>
                    <HD SOURCE="HD1">IX. Violations Alleged</HD>
                    <HD SOURCE="HD2">First Claim for Relief: Monopolization of Primary Ticketing Services Markets in Violation of Sherman Act § 2</HD>
                    <P>224. Plaintiffs incorporate the allegations of Paragraphs 1 through 223 above.</P>
                    <P>225. Live Nation has monopolized several relevant markets related to primary ticketing services in the United States. These include the provision of primary ticketing services to major concert venues, the provision of primary concert ticketing services to major concert venues, and the provision of primary concert ticketing offerings to fans at major concert venues (even if combined with services that offer resale of concert tickets).</P>
                    <P>226. Each constitutes a relevant antitrust market, and Live Nation has monopoly power in each market.</P>
                    <P>227. Live Nation has unlawfully maintained its monopoly in each market through a course of exclusionary conduct, including:</P>
                    <P>• Directly threatening venues that Live Nation will divert live music shows to other venues if they do not sign with Ticketmaster;</P>
                    <P>• Indirectly threatening venues that Live Nation will divert live music shows to other venues if they do not sign with Ticketmaster by, for example, co-opting business partner Oak View Group into warning venues that they will lose Live Nation content if they contract with a ticketer other than Ticketmaster;</P>
                    <P>• Retaliating against venues that contract with rival ticketers by:</P>
                    <P>○ Diverting concerts on Live Nation-promoted tours to other venues;</P>
                    <P>○ Disabling or delaying the sale of secondary tickets through the rival ticketer's platform;</P>
                    <P>○ Refusing to publicize shows hosted by a venue that uses a competing ticketer;</P>
                    <P>○ Diverting content away from venues ticketed by companies other than Ticketmaster, making it risky for any venue to contract with a rival ticketer; and</P>
                    <P>○ Lodging complaints against rival ticketers when Live Nation promotes a show at a venue where Ticketmaster is not the primary ticketer;</P>
                    <P>• Foreclosing rival ticketing companies from the market by:</P>
                    <P>○ Imposing long-term exclusive contracts covering a significant proportion of tickets sold;</P>
                    <P>○ Engaging in strategic purchases of rival promoters and venues to enhance its market power in content and to convert ticketing to Ticketmaster, further foreclosing the primary ticketing market; and</P>
                    <P>○ Deterring entry and expansion by rivals into primary ticketing by using its monopoly to expand its control over secondary ticketing, which previously had been an entry point for primary ticketing.</P>
                    <P>228. Although each of these acts is anticompetitive when considered alongside Live Nation's associated conduct, each act occurs in concert with and against the backdrop of allegations and facts outlined throughout this Complaint. These acts have synergistic anticompetitive effects that have harmed competition and the competitive process.</P>
                    <P>
                        229. Live Nation's exclusionary conduct has foreclosed a substantial share of each of these markets.
                        <PRTPAGE P="41355"/>
                    </P>
                    <P>230. Live Nation's anticompetitive acts have had harmful effects on competition and consumers.</P>
                    <P>231. Live Nation's exclusionary conduct lacks a non-pretextual procompetitive justification that offsets the harm caused by Live Nation's anticompetitive and unlawful conduct.</P>
                    <P>232. Live Nation's anticompetitive and exclusionary practices violate Section 2 of the Sherman Act, 15 U.S.C. 2.</P>
                    <HD SOURCE="HD2">Second Claim for Relief: Unlawful Exclusive Dealing in Violation of Sherman Act § 1</HD>
                    <P>233. Plaintiffs incorporate the allegations of Paragraphs 1 through 223 above.</P>
                    <P>234. The provision of primary ticketing services to major concert venues in the United States is a relevant antitrust market, and the provision of primary concert ticketing services to major concert venues in the United States is a relevant antitrust market.</P>
                    <P>235. Ticketmaster's long-term exclusive agreements to provide primary ticketing services to major concert venues in the United States unreasonably restrain competition, in violation of Section 1 of the Sherman Act, 15 U.S.C. 1.</P>
                    <P>236. These contracts exclude all competitors, are terminable only for cause, and have terms ranging from three to 14 years.</P>
                    <P>237. Ticketmaster's long-term exclusive primary ticketing contracts restrict the access of Ticketmaster's competitors to the only significant channel of distribution for primary ticketing services to major concert venues.</P>
                    <P>238. Through its long-term exclusive primary ticketing contracts, Ticketmaster has foreclosed a substantial share of the market for the provision of primary ticketing services to major concert venues in the United States.</P>
                    <P>239. Live Nation's anticompetitive acts have had harmful effects on fans of major concerts, the venues that host them, and competition for primary ticketing.</P>
                    <P>240. Live Nation's exclusionary conduct lacks a non-pretextual procompetitive justification that offsets the harm caused by Live Nation's anticompetitive and unlawful conduct.</P>
                    <HD SOURCE="HD2">Third Claim for Relief: Unlawful Tying Arrangement Concerning the Use of Large Amphitheaters and Artist Promotions Markets in Violation of Sherman Act § 1</HD>
                    <P>241. Plaintiffs incorporate the allegations of Paragraphs 1 through 223 above.</P>
                    <P>242. The provision of the use of large amphitheaters and ancillary services to artists for large amphitheater tours in the United States is a relevant antitrust market, and Live Nation has monopoly power in that market.</P>
                    <P>243. The provision of promotion services to artists performing in major concert venues in the United States is a relevant market, and Live Nation has market power in that market.</P>
                    <P>244. The provision of the use of large amphitheaters to artists and the provision of promotion services to artists are separate services sold to artists. The services are provided in different markets, with distinct demand for each, and they are treated by industry participants as separate products. There are some industry participants, such as third-party operated amphitheaters, that only offer access to amphitheaters, and there are promoters who only offer artists promotion services. Live Nation has unlawfully required artists seeking to use its large amphitheaters for shows as part of a tour to also purchase promotion services from Live Nation.</P>
                    <P>245. The purpose and effect of this tying policy is to prevent artists from choosing a promoter on the merits and instead force artists who wish to play in Live Nation amphitheaters to contract with the company for promotions services.</P>
                    <P>246. This anticompetitive conduct has significantly foreclosed competition in promotion services to artists. Artists who would otherwise choose rival promoters on the merits of those promoters must refrain from doing so to maintain use of Live Nation's amphitheaters on their tours.</P>
                    <P>247. This conduct lacks a non-pretextual procompetitive justification that offsets the harm caused by Live Nation's anticompetitive and unlawful conduct.</P>
                    <P>248. Live Nation's anticompetitive and exclusionary practices violate Section 1 of the Sherman Act, 15 U.S.C. 1.</P>
                    <HD SOURCE="HD2">Fourth Claim for Relief: Monopolization of the Market for the Use of  Large Amphitheaters in Violation of Sherman Act § 2</HD>
                    <P>249. Plaintiffs incorporate the allegations of Paragraphs 1 through 223 above.</P>
                    <P>250. The provision of the use of large amphitheaters and ancillary services to artists for large amphitheater tours in the United States is a relevant antitrust market, and Live Nation has monopoly power in that market.</P>
                    <P>251. Live Nation has unlawfully maintained its monopoly in this market through a course of anticompetitive exclusionary conduct, including:</P>
                    <P>• Entering into exclusive booking arrangements with venues, enabling Live Nation to extend its control of this market beyond the significant share it controls through its owned, operated, and leased amphitheaters;</P>
                    <P>• Acquiring control over several amphitheaters, enabling Live Nation to extend its control of this market through its portfolio of owned and operated amphitheaters;</P>
                    <P>• Acquiring several competing promotion companies that either owned amphitheaters or had exclusive booking contracts with amphitheaters; and</P>
                    <P>• Acquiring numerous large festivals, further reducing the ability of artists on large amphitheater tours to seek alternatives to Live Nation. These exclusionary acts have harmed artists, rival promoters, and fans.</P>
                    <P>252. Although each of these acts is anticompetitive when considered alongside Live Nation's associated conduct, each act occurs in concert with and against the backdrop of allegations and facts outlined throughout this Complaint. These acts have synergistic anticompetitive effects that have harmed competition and the competitive process.</P>
                    <P>253. Live Nation's exclusionary conduct has foreclosed a substantial share of the market.</P>
                    <P>254. Live Nation's anticompetitive acts have had harmful effects on competition and consumers.</P>
                    <P>255. Live Nation's conduct lacks any procompetitive benefits or justification that offsets the significant anticompetitive harm that flows from the exclusionary conduct.</P>
                    <P>256. Live Nation's anticompetitive and exclusionary practices violate Section 2 of the Sherman Act, 15 U.S.C. 2.</P>
                    <HD SOURCE="HD2">Fifth Claim for Relief: Monopolization of the Markets for Concert Promotion Services in Violation of Sherman Act § 2</HD>
                    <P>257. Plaintiffs incorporate the allegations of Paragraphs 1 through 223 above.</P>
                    <P>
                        258. The provision of concert booking and promotion services to major concert venues and the provision of promotion services to artists performing in major concert venues in the United States are related, relevant antitrust markets, and 
                        <PRTPAGE P="41356"/>
                        Live Nation has monopoly power in each market.
                    </P>
                    <P>259. Live Nation has unlawfully maintained its monopoly in each market through a course of exclusionary conduct described herein, including:</P>
                    <P>• Engaging in strategic purchases of rival promoters (actual or potential) and venues to enhance and entrench its monopoly power;</P>
                    <P>• Tying artists' use of Live Nation owned, controlled and exclusively-booked large amphitheaters to their purchase of promotional services from Live Nation;</P>
                    <P>• Deterring entry and expansion by rivals by threatening potential rivals and their investors; and</P>
                    <P>• Imposing restrictive terms in contracts with major concert venues that undermine and foreclose competition from actual and potential rival promoters.</P>
                    <P>260. Although each of these acts is anticompetitive when considered alongside Live Nation's associated conduct, each act occurs in concert with and against the backdrop of allegations and facts outlined throughout this Complaint. These acts have synergistic anticompetitive effects that have harmed competition and the competitive process.</P>
                    <P>261. Live Nation's exclusionary conduct has foreclosed a substantial share of each market.</P>
                    <P>262. Live Nation's anticompetitive acts have had harmful effects on competition and consumers.</P>
                    <P>263. Live Nation's exclusionary conduct lacks a non-pretextual procompetitive justification that offsets the harm caused by Live Nation's anticompetitive and unlawful conduct.</P>
                    <P>264. Live Nation's anticompetitive and exclusionary practices violate Section 2 of the Sherman Act, 15 U.S.C. 2.</P>
                    <HD SOURCE="HD2">Sixth Claim for Relief: Violation of Arizona Law</HD>
                    <P>265. The State of Arizona incorporates the allegations of Paragraphs 1 through 264 above.</P>
                    <P>
                        266. In addition to violating federal law, Defendants' acts as alleged herein also constitute violations of Arizona's Uniform State Antitrust Act, Arizona Revised Statutes (“A.R.S.”) § 44-1401 
                        <E T="03">et seq.,</E>
                         as follows:
                    </P>
                    <P>a. Live Nation, as described in Paragraphs 224 through 232, has unlawfully established, maintained, and used its monopoly power in several markets, which constitutes a violation of A.R.S. § 44-1403. These markets include the provision of primary ticketing services to major concert venues, the provision of primary concert ticketing services to major concert venues, and the provision of primary concert ticketing to fans at major concert venues.</P>
                    <P>b. Ticketmaster's long-term exclusive agreements to provide primary ticketing services to major concert venues, as described in Paragraphs 233 through 240, are contracts, combinations, or conspiracies between two or more persons that restrain or monopolize trade, which constitutes a violation of A.R.S. § 44-1402.</P>
                    <P>c. Live Nation, as described in Paragraphs 241 through 248, has required artists to purchase substantial promotional services from Live Nation in order for artists to use its large amphitheaters for shows as part of a tour, which constitutes an unlawful tying arrangement in violation of A.R.S. § 44-1402.</P>
                    <P>d. Live Nation, as described in Paragraphs 249 through 256, has unlawfully established, maintained, and used its monopoly power in the market for the provision of the use of large amphitheaters and ancillary services to artists on large-amphitheater tours, which constitutes a violation of A.R.S. § 44-1403.</P>
                    <P>e. Live Nation, as described in Paragraphs 257 through 264, has unlawfully established, maintained, and used its monopoly power in the markets for the provision of concert booking and promotion services to major concert venues and the provision of promotion services to artists performing in major concert venues, which constitutes a violation of A.R.S. § 44-1403.</P>
                    <P>267. Defendants committed these violations while selling tickets, promoting events, and operating venues within the State of Arizona. These violations ultimately harm fans, venues, promoters, and artists across Arizona by increasing costs and prices, and reducing choice, innovation, and quality.</P>
                    <P>268. In addition to its federal law remedies, the State of Arizona seeks all remedies available under A.R.S. § 44-1407, including, without limitation, the following:</P>
                    <P>a. Injunctive relief, other equitable relief (including but not limited to disgorgement), fees and costs, and other relief as this Court deems just and equitable pursuant to A.R.S. § 44-1407;</P>
                    <P>b. Civil penalties pursuant to A.R.S. § 44-1407 which provides that: “The court may assess for the benefit of the state a civil penalty of not more than one hundred fifty thousand dollars for each violation of this article”; and</P>
                    <P>269. Other remedies as the Court may deem appropriate under the facts and circumstances of this case.</P>
                    <HD SOURCE="HD2">Seventh Claim for Relief: Violation of Arkansas Law</HD>
                    <P>270. Plaintiff State of Arkansas incorporates the allegations of Paragraphs 1 through 264 above.</P>
                    <P>
                        271. Plaintiff State of Arkansas brings this action in its sovereign capacity pursuant to Ark. Code Ann. § 4-75-212(a) and Ark. Code Ann. § 4-75-315(a) and its 
                        <E T="03">parens patriae</E>
                         capacity pursuant to Ark. Code Ann. § 4-75-212(b) and Ark. Code Ann. § 4-75-315(b).
                    </P>
                    <P>272. Defendants' acts as alleged herein constitute an unlawful monopoly in violation of Ark. Code Ann. §§ 4-75-301-302.</P>
                    <P>273. Defendants' acts as alleged herein further violate Arkansas's prohibition of secret rebates or privileges tending to destroy competition. Unfair Practices Act, Ark. Code Ann. § 4-75-208.</P>
                    <P>274. Plaintiff State of Arkansas is entitled to and seeks all remedies available at law or in equity, including, without limitation, the following:</P>
                    <P>a. A declaratory judgment, pursuant to Ark. Code Ann. § 4-75-212(a)(1) and Ark. Code Ann. § 4-75-315(a)(1), that Defendants' acts and practices as described in this Complaint violate Arkansas's Unfair Practices Act and its prohibition on monopolies;</P>
                    <P>b. Permanent injunctions against Defendants, pursuant to Ark. Code Ann. § 4-75-212(a)(2) and Ark. Code Ann. § 4-75-315(a)(2), enjoining Defendants from engaging in any act that violates Arkansas's Unfair Practices Act and its prohibition on monopolies, including but not limited to the unfair methods of competition alleged herein;</P>
                    <P>c. Damages for injuries sustained or restitution for loss as a result of violations of Arkansas's antitrust statutes pursuant to Ark. Code Ann. § 4-75-212(b)(1)(A) and Ark. Code Ann. § 4-75-315(b)(1);</P>
                    <P>d. Civil penalties pursuant to Ark. Code Ann. § 4-75-212(a)(4) and Ark. Code Ann. § 4-75-315(a)(4);</P>
                    <P>e. Costs and attorneys' fees pursuant to Ark. Code Ann. § 4-75-212(a)(4) and Ark. Code Ann. § 4-75-315(a)(4); and</P>
                    <P>f. All other just and equitable relief that this Court may deem appropriate.</P>
                    <HD SOURCE="HD2">Eighth Claim for Relief: Violation of California Law</HD>
                    <P>275. The State of California incorporates the allegations of Paragraphs 1 through 264 above.</P>
                    <P>
                        276. Defendants' acts and practices detailed above also violate California's Unfair Competition Law (“UCL”), Cal. Bus. &amp; Prof. Code § 17200, 
                        <E T="03">et seq.,</E>
                         which prohibits any unlawful, unfair, or fraudulent business act or practice.
                        <PRTPAGE P="41357"/>
                    </P>
                    <P>277. In bringing its state claims, Plaintiff State of California is entitled to, without limitation, the following relief:</P>
                    <P>a. Injunctive, restitution and other equitable relief under the UCL (Cal. Bus. &amp; Prof. Code § 17203); and</P>
                    <P>b. Civil penalties assessed at up to $2,500 for each violation of the UCL (Cal. Bus. &amp; Prof. Code § 17206).</P>
                    <HD SOURCE="HD2">Ninth Claim for Relief: Violations of Colorado Law</HD>
                    <P>278. Plaintiff State of Colorado repeats and re-alleges and incorporates by reference Paragraphs 1 through 264 in this Complaint as if fully set forth herein.</P>
                    <P>279. Defendants' acts as alleged herein violate the Colorado Antitrust Act of 2023, § 6-4-101, et. seq., Colo. Rev. Stat. These violations substantially affect the people of Colorado and have impacts within the State of Colorado.</P>
                    <P>280. The markets for primary ticketing services to major concert venues, provision of primary concert ticketing services to major concert venues and provision of primary concert ticketing offerings to fans at major concert venues in the United States, as alleged in Paragraphs 163 through 190, each constitute a separate relevant antitrust market. The provision of concert booking and promotion services to major concert venues, provision of the use of large amphitheaters and ancillary services to artists, and provision of promotion services to artists performing in major concert venues in the United States or in smaller regional geographic markets, as alleged in Paragraphs 191 through 214, each constitute separate, relevant antitrust markets.</P>
                    <P>281. Defendants' acts alleged in Paragraphs 224 through 232 to unlawfully maintain monopoly power in the markets for primary ticketing services violate § 6-4-105, Colo. Rev. Stat. Defendants have monopoly power in the relevant markets for provision of primary ticketing services and have engaged in an unlawful course of conduct to maintain that monopoly power.</P>
                    <P>282. Defendants' acts alleged in Paragraphs 233 through 240 constitute unlawful exclusive dealing in violation of § 6-4-104, Colo. Rev. Stat. Ticketmaster's long-term exclusive agreements to provide primary ticketing services to major concert venues unreasonably restrain competition, foreclosing a substantial share of the market for provision of primary ticketing services to major concert venues in the United States.</P>
                    <P>283. Defendants' acts alleged in Paragraphs 241 through 248 constitute unlawful tying arrangements in violation of § 6-4-104, Colo. Rev. Stat. Live Nation's acts to require artists to purchase concert promotion services from Live Nation in order to access large amphitheaters coerce artists and significantly foreclose the market for concert promotion services to artists.</P>
                    <P>284. Defendants' acts alleged in Paragraphs 249 through 256 to monopolize the market for provision of use of large amphitheaters and ancillary services to artists violate § 6-4-105, Colo. Rev. Stat. Defendants have monopoly power in the market for provision of use of large amphitheaters and ancillary services to artists, and have engaged in an unlawful course of conduct to maintain that monopoly power.</P>
                    <P>285. Defendants' acts alleged in Paragraphs 257 through 264 to monopolize the markets for concert promotion services violate § 6-4-105, Colo. Rev. Stat. Defendants have monopoly power in the market for provision of concert booking and promotion services to major concert venues and the market for provision of concert promotion services to artists performing at major concert venues, and have engaged in an unlawful course of conduct to maintain that monopoly power.</P>
                    <P>286. Defendants engaged in a wide-ranging anticompetitive and exclusionary course of the conduct described above while selling tickets, booking and promoting concerts, and operating venues within Colorado. As alleged in Paragraphs 70 through 158 and 223, and on information and belief, this anticompetitive conduct has harmed competition, fans, venues, promoters, and artists across Colorado by resulting in:</P>
                    <P>a. Supracompetitive prices in Colorado;</P>
                    <P>b. Reduction in the quality and quantity of live events available in Colorado;</P>
                    <P>c. Loss of innovation in the relevant markets; and</P>
                    <P>d. Other harms resulting from lack of competition in the relevant markets.</P>
                    <P>287. Each of Defendants' unlawful agreements, arrangements, or acts alleged herein constitute at least one distinct violation of the Colorado Antitrust Act within the meaning of § 6-4-113, Colo. Rev. Stat.</P>
                    <P>288. Defendants' acts alleged herein were willful within the meaning of § 6-4-113(2), Colo. Rev. Stat.</P>
                    <P>289. Defendants' acts alleged herein constitute a continuous pattern and practice of behavior within the meaning of § 6-4-113(2), Colo. Rev. Stat.</P>
                    <P>290. The State of Colorado seeks all available remedies under the Colorado Antitrust Act, including, without limitation.</P>
                    <P>a. Injunctive and other equitable relief pursuant to § 6-4-112, Colo. Rev. Stat.;</P>
                    <P>b. Civil penalties pursuant to § 6-4-113, Colo. Rev. Stat. for each violation of the Colorado Antitrust Act, including but not limited to:</P>
                    <P>i. Each exclusive agreement in violation of § 6-4-104, Colo. Rev. Stat.;</P>
                    <P>ii. Each unlawful tying arrangement in violation of § 6-4-104, Colo. Rev. Stat.; and</P>
                    <P>iii. Each act to unlawfully maintain monopoly power in any relevant market in violation of § 6-4-105, Colo. Rev. Stat.</P>
                    <P>
                        c. Treble damages for injuries sustained, directly or indirectly, by individuals residing in Colorado to their property through the purchase of tickets for live events from Ticketmaster, pursuant to the State of Colorado's 
                        <E T="03">parens patriae</E>
                         authority under § 6-4-112(3), Colo. Rev. Stat.;
                    </P>
                    <P>d. Costs and attorneys' fees, pursuant to § 6-4-112(5), Colo. Rev. Stat.; and</P>
                    <P>e. Other remedies as the Court may deem appropriate on the basis of the facts properly alleged and proven.</P>
                    <P>291. The State of Colorado does not seek damages on behalf of any governmental or public entity.</P>
                    <HD SOURCE="HD2">Tenth Claim for Relief: Violation of Connecticut Law</HD>
                    <P>292. The State of Connecticut incorporates the allegations of Paragraphs 1 through 264 above.</P>
                    <P>293. Defendants engaged in the conduct described while selling tickets, promoting shows, and operating venues in Connecticut. This anticompetitive conduct harmed fans, venues, promoters, and artists across the State and affected commerce therein.</P>
                    <P>
                        294. Defendants' actions alleged in the Complaint violate the Connecticut Antitrust Act (“CAA”), General Statutes § 35-24 
                        <E T="03">et seq.</E>
                    </P>
                    <P>295. Defendants' actions alleged in the Complaint constitute restraint of a part of trade or commerce within the state in violation of Conn. Gen. Stat. § 35-26.</P>
                    <P>296. Defendants' actions alleged in the Complaint constitute monopolization of a part of trade or commerce within the state in violation of Conn. Gen. Stat. § 35-27.</P>
                    <P>297. The State of Connecticut seeks all remedies available under the CAA, including, without limitation, the following:</P>
                    <P>a. Injunctive and other equitable relief, pursuant to Conn. Gen. Stat. § 35-34;</P>
                    <P>
                        b. Civil penalties of $1,000,000 against each Defendant pursuant to Conn. Gen. Stat. § 35-38;
                        <PRTPAGE P="41358"/>
                    </P>
                    <P>c. Costs and attorneys' fees, pursuant to Conn. Gen. Stat. § 35-34; and</P>
                    <P>d. Other remedies as the Court may deem appropriate under the facts and circumstances of the case.</P>
                    <HD SOURCE="HD2">Eleventh Claim for Relief: Violation of District of Columbia Law</HD>
                    <P>298. The District of Columbia incorporates the allegations of Paragraphs 1 through 264 above.</P>
                    <P>
                        <E T="03">299.</E>
                         The Attorney General for the District of Columbia brings this action pursuant to DC Code § 28-4501, 
                        <E T="03">et seq.</E>
                    </P>
                    <P>300. Defendants' conduct alleged in paragraphs 224-232 and 249-264 constitutes unlawful monopolization within the District of Columbia under DC Code § 28-4503.</P>
                    <P>301. Defendants' conduct alleged in paragraphs 233-248 constitutes unlawful combination in restraint of trade within the District of Columbia under DC Code § 28-4502.</P>
                    <P>
                        302. The District of Columbia, pursuant to its 
                        <E T="03">parens patriae</E>
                         authority in the District of Columbia Antitrust Act, DC Code § 28-4507(b)(1) seeks all remedies available under DC Code § 28-4507. The District of Columbia is also entitled to recover its costs and attorney's fees under DC Code § 28-4507(a)(2)(B).
                    </P>
                    <HD SOURCE="HD2">Twelfth Claim for Relief: Violation of Florida Law</HD>
                    <P>303. Plaintiff State of Florida incorporates the allegations of Paragraphs 1 through 264 above.</P>
                    <HD SOURCE="HD3">Florida Antitrust Act</HD>
                    <P>304. In addition to violating federal law, Defendants' acts described above violate the Florida Antitrust Act, Sections 542.18 and 542.19, Florida Statutes.</P>
                    <P>305. The State of Florida seeks damages under Section 542.22, Florida Statutes, for each violation of the Florida Antitrust Act, Sections 542.18 and 542.19, Florida Statutes.</P>
                    <P>306. The State of Florida seeks the maximum civil penalties under Section 542.21, for each violation of the Florida Antitrust Act, Sections 542.18 and 542.19, Florida Statutes.</P>
                    <P>307. The State of Florida seeks to recover its reasonable attorneys' fees and costs, pursuant to Section 542.23, Florida Statutes.</P>
                    <P>308. The State of Florida seeks injunctive relief pursuant to Section 542.23, Florida Statutes.</P>
                    <P>309. Defendants' conduct alleged herein constitutes unlawful monopolization within Florida under Section 542.19, Florida Statutes.</P>
                    <P>310. Defendants' conduct alleged herein constitutes unlawful combination in restraint of trade within Florida under Section 542.18, Florida Statutes.</P>
                    <P>311. Defendants engaged in the conduct described above while selling tickets, promoting concerts, and operating venues in Florida. This anticompetitive conduct harmed fans, venues, promoters, and artists across Florida and affected commerce therein.</P>
                    <P>312. Defendants' anticompetitive acts alleged herein, or the effects thereof, are continuing and will continue and are likely to recur unless permanently restrained and enjoined.</P>
                    <HD SOURCE="HD3">Florida Deceptive and Unfair Trade Practices Act</HD>
                    <P>313. In addition to violating federal law, Defendants' acts described above constitute unfair methods of competition which violate the Florida Deceptive and Unfair Trade Practices Act, Section 501.204, Florida Statutes.</P>
                    <P>314. Defendants engaged in the conduct described above while selling tickets, promoting concerts, and operating venues in Florida. This anticompetitive conduct harmed fans, venues, promoters, and artists across Florida and affected commerce therein.</P>
                    <P>315. The State of Florida seeks damages under Section 501.207(c), Florida Statutes, for each violation of the Florida Deceptive and Unfair Trade Practices Act, Section 501.204, Florida Statutes.</P>
                    <P>316. The State of Florida seeks the maximum civil penalties under Sections 501.2075 and 501.2077, Florida Statutes, for each violation of the Florida Deceptive and Unfair Trade Practices Act, Section 501.204, Florida Statutes.</P>
                    <P>317. The State of Florida seeks to recover its reasonable attorneys' fees and costs, pursuant to Section 501.2105, Florida Statutes.</P>
                    <P>318. The State of Florida seeks injunctive relief pursuant to Section 501.207(1)(b), Florida Statutes.</P>
                    <P>319. Defendants' unfair methods of competition alleged herein, or the effects thereof, are continuing and will continue and are likely to recur unless permanently restrained and enjoined.</P>
                    <HD SOURCE="HD3">Florida's Prayer for Relief</HD>
                    <P>320. Award to the State of Florida damages under Section 542.22, Florida Statutes, for each violation of the Florida Antitrust Act, Sections 542.18 and 542.19, Florida Statutes;</P>
                    <P>321. Award to the State of Florida the maximum civil penalties under Section 542.21, for each violation of the Florida Antitrust Act, Sections 542.18 and 542.19, Florida Statutes;</P>
                    <P>322. Award to the State of Florida its reasonable attorneys' fees and costs, pursuant to Section 542.23, Florida Statutes;</P>
                    <P>323. Adjudge and decree that Defendants violated Sections 542.18, and 542.19, Florida Statutes;</P>
                    <P>324. Award to the State of Florida damages under Section 501.207(c), Florida Statutes, for each violation of the Florida Deceptive and Unfair Trade Practices Act, Section 501.204, Florida Statutes;</P>
                    <P>325. Award to the State of Florida the maximum civil penalties under Sections 501.2075 and 501.2077, Florida Statutes, for each violation of the Florida Deceptive and Unfair Trade Practices Act, Section 501.204, Florida Statutes;</P>
                    <P>326. Award to the State of Florida its reasonable attorneys' fees and costs, pursuant to Section 501.2105, Florida Statutes;</P>
                    <P>327. Adjudge and decree that Defendants violated Section 501.204, Florida Statutes;</P>
                    <P>328. Enjoin and restrain, pursuant to Florida law, Defendants, their affiliates, assignees, subsidiaries, successors, and transferees, and their officers, directors, partners, agents and employees, and all other persons acting or claiming to act on their behalf or in concert with them, from continuing to engage in any anticompetitive conduct, and from adopting in the future any practice, plan, program, or device having a similar purpose or effect to the anticompetitive actions set forth above.</P>
                    <HD SOURCE="HD3">Thirteenth Claim for Relief: Violation of Illinois Law</HD>
                    <P>329. Plaintiff State of Illinois incorporates the allegations of Paragraphs 1 through 264 above.</P>
                    <P>330. Defendants' acts alleged herein, which all lack any non-pretextual procompetitive justifications that offset the substantial harmful effects on competition and consumers, violate Section 3 of the Illinois Antitrust Act, 740 ILCS 10/3, as follows:</P>
                    <P>a. Live Nation has unlawfully maintained its monopoly power in the provision of primary ticketing services to major concert venues through a course of exclusionary conduct described in Paragraphs 224 through 232 above, in violation of Section 3(3) of the Illinois Antitrust Act, 740 ILCS 10/3(3);</P>
                    <P>
                        b. Ticketmaster's long-term exclusive agreements to provide primary ticketing services to major concert venues, which exclude all competitors, as described in Paragraphs 233 through 240 above, unreasonably restrain competition in violation of Sections 3(1)(a) &amp; 3(1)(b) of 
                        <PRTPAGE P="41359"/>
                        the Illinois Antitrust Act, 740 ILCS 10/3(1)(a) &amp; 10/3(1)(b);
                    </P>
                    <P>c. Live Nation has engaged in unlawful, anticompetitive and exclusionary tying arrangements by requiring artists seeking to perform at large amphitheaters in Illinois as part of a tour to purchase promotion services from Live Nation, as described in Paragraphs 241 through 248 above, in violation of Section 3(4) of the Illinois Antitrust Act, 740 ILCS 10/3(4);</P>
                    <P>d. Live Nation has unlawfully maintained its monopoly power in the provision of large amphitheaters and ancillary services for large amphitheater tours through a course of anticompetitive exclusionary conduct described in Paragraphs 249 through 256 above in violation of Sections 3(2) &amp; 3(3) of the Illinois Antitrust Act, 740 ILCS 10/3(2) &amp; 10/3(3); and</P>
                    <P>e. Live Nation has unlawfully maintained its monopoly power in the provision of concert booking and promotion services to major concert venues and the provision of promotion services to artists performing in major concert venues through a course of anticompetitive exclusionary practices described in Paragraphs 257 through 264 above, in violation of Sections 3(1)(b), 3(2) &amp; 3(3) of the Illinois Antitrust Act, 740 ILCS 10/3(1)(b), 10/3(2) &amp; 10/3(3).</P>
                    <P>331. These violations substantially affect the people who reside in Illinois and companies that conduct business in Illinois and have impacts within the State of Illinois.</P>
                    <P>
                        332. Plaintiff State of Illinois, through its Attorney General, seeks all available injunctive and monetary relief, including as 
                        <E T="03">parens patriae</E>
                         on behalf of persons residing in Illinois to recover treble damages under 740 ILCS 10/7(2) and including civil penalties under 740 ILCS 10/7(4).
                    </P>
                    <P>333. Plaintiff State of Illinois, through its Attorney General, also seeks to recover its costs and attorneys' fees under 740 ILCS 10/7(2).</P>
                    <HD SOURCE="HD2">Fourteenth Claim for Relief: Violation of Indiana Law</HD>
                    <P>334. Plaintiff State of Indiana incorporate the allegations of Paragraphs 1 through 264 above.</P>
                    <HD SOURCE="HD3">Indiana Antitrust Act</HD>
                    <P>335. The aforementioned practices by Live Nation and Ticketmaster were and are in violation of the Indiana Antitrust Act, Ind. Code §§ 24-1-2-1 and 24-1-2-2.</P>
                    <P>1. The aforementioned practices by Live Nation and Ticketmaster were and are in violation of the Indiana Antitrust Act, Ind. Code §§ 24-1-2-1 and 24-1-2-2.</P>
                    <P>336. The acts alleged in the Complaint constitute schemes, contracts, or combinations in restraint of trade or commerce or are otherwise illegal under Ind. Code § 24-1-2-1.</P>
                    <P>337. The acts alleged in the Complaint constitute monopolization as a part of trade or commerce within the state under Ind. Code § 24-1-2-2.</P>
                    <P>
                        338. Plaintiff State of Indiana, through its Attorney General, seeks all available relief as 
                        <E T="03">parens patriae</E>
                         on behalf of natural persons residing in Indiana under the Indiana Antitrust Act, including, without limitation, the following:
                    </P>
                    <P>a. Appropriate injunctive or other equitable relief pursuant to Ind. Code § 24-1-2-5.1;</P>
                    <P>b. A civil penalty pursuant to Ind. Code § 24-1-2-5.1;</P>
                    <P>c. Injuries or damages sustained directly or indirectly by natural persons pursuant to Ind. Code § 24-1-2-5.1;</P>
                    <P>d. Costs and fees pursuant to Ind. Code § 24-1-2-5.1;</P>
                    <P>e. Other remedies the Court finds necessary to redress and prevent recurrence of each Defendant's violations.</P>
                    <HD SOURCE="HD2">Fifteenth Claim for Relief: Violation of Iowa Law</HD>
                    <P>339. Plaintiff State of Iowa incorporates Paragraphs 1 through 264 above. Defendants engaged in the conduct alleged above while they sold tickets and promoted concerts in Iowa. That conduct substantially affects the people of Iowa and the State of Iowa.</P>
                    <P>340. As a result of this conduct, Iowa consumers have suffered anticompetitive harm by paying increased prices, paying additional costs, and suffering reduced quality.</P>
                    <P>341. Plaintiff State of Iowa seeks all remedies available under Federal law.</P>
                    <P>342. Defendants' conduct also violates the Iowa Competition Law, Iowa Code Chapter 553, including Iowa Code §§ 553.4 and 553.5.</P>
                    <P>343. For violations of the Iowa Competition Law, Plaintiff State of Iowa seeks all available relief under Iowa Code Chapter 553, including but not limited to:</P>
                    <P>a. Injunctive and equitable relief under Iowa Code § 553.12(1);</P>
                    <P>b. Damages under Iowa Code § 553.12(2);</P>
                    <P>c. Civil penalties under Iowa Code § 553.13; and</P>
                    <P>d. All other remedies the court may deem appropriate.</P>
                    <P>344. Defendants' conduct also constitutes unfair practices in violation of the Iowa Consumer Fraud Act, Iowa Code § 714.16.</P>
                    <P>345. For violations of the Iowa Consumer Fraud Act, Plaintiff State of Iowa seeks all available relief under Iowa Code § 714.16, including but not limited to:</P>
                    <P>a. Injunctive relief, equitable relief, and civil penalties under Iowa Code § 714.16(7);</P>
                    <P>b. Costs and attorneys' fees under Iowa Code § 714.16(11); and</P>
                    <P>c. All other remedies the court may deem appropriate.</P>
                    <HD SOURCE="HD2">Sixteenth Claim for Relief: Violation of Kansas Law</HD>
                    <P>346. The State of Kansas incorporates the allegations of Paragraphs 1 through 264 above.</P>
                    <P>
                        347. In addition to violating federal law, Defendants' acts as alleged herein also constitute violations of the Kansas Restraint of Trade Act (“KRTA”), Kansas Statutes Annotated (“Kan. Stat. Ann.”) § 50-101, 
                        <E T="03">et seq.,</E>
                         as follows:
                    </P>
                    <P>a. Live Nation and Ticketmaster have entered into combinations of capital, skill, or acts which restrict trade or commerce, increase the price of merchandise or commodities, and prevent competition in the sale or purchase of merchandise or commodities in the markets for concert promotion, venues, artists, and the related sale of tickets for performances in entertainment in Kansas, in violation of Kan. Stat. Ann. § 50-101.</P>
                    <P>b. Live Nation and Ticketmaster have entered into, executed and carried out contracts, obligations or agreements which bind venues, promotors and artists to preclude free and unrestricted competition in these markets, in violation of Kan. Stat. Ann. § 50-101.</P>
                    <P>c. Live Nation and Ticketmaster have entered into arrangements, contracts, agreements, trusts, or combinations with a view to or which tend to prevent full and free competition and advance the price of products and services for entertainment in Kansas, in violation of Kan. Stat. Ann. § 50-112.</P>
                    <P>348. Defendants committed these violations while selling tickets, promoting events, and operating venues within the State of Kansas. These violations caused harm to the State of Kansas and ultimately harm fans, venues, promoters, and artists across Kansas by increasing costs and prices, and reducing choice, innovation, and quality.</P>
                    <P>349. In addition to federal remedies, the State of Kansas seeks the following remedies under state law:</P>
                    <P>a. A declaration that the above acts and practices violate the KRTA pursuant to Kan. Stat. Ann. § 50-103;</P>
                    <P>
                        b. Injunctive relief, voiding of any contract or agreement in violation of the 
                        <PRTPAGE P="41360"/>
                        KRTA, other equitable relief, fees and costs, including attorneys' fees, pursuant to Kan. Stat. Ann. §§ 50-103 and 50-161;
                    </P>
                    <P>c. Civil penalties, pursuant to Kan. Stat. Ann. § 50-103, as specified by Kan. Stat. Ann. § 50-160 which provides that: “The commission of any act or practice declared to be a violation of the Kansas restraint of trade act shall render the violator liable to the state for the payment of a civil penalty in a sum set by the court of not less than $100 nor more than $5,000 for each day such violation shall have occurred”; and</P>
                    <P>d. Other relief as this Court deems appropriate.</P>
                    <HD SOURCE="HD2">Seventeenth Claim for Relief: Violation of Louisiana Law</HD>
                    <P>350. Plaintiff State of Louisiana repeats and re-alleges each and every preceding allegation through Paragraph 264 as if fully set forth herein.</P>
                    <P>
                        351. The Attorney General of the State of Louisiana is authorized to bring this action pursuant to the Louisiana Unfair Trade Practices Act, LSA-R.S. 51:1401, 
                        <E T="03">et seq.</E>
                         (“LUTPA”).
                    </P>
                    <P>352. LSA-R.S. 51:1405(A) of LUTPA makes unlawful “unfair and deceptive acts or practices in the conduct of any trade or commerce.”</P>
                    <P>353. Defendants' acts as alleged herein violates Louisiana's prohibition on unfair and deceptive acts or practices in LUTPA.</P>
                    <P>354. Plaintiff State of Louisiana seeks the following remedies:</P>
                    <P>a. Injunctive relief enjoining Defendants from violating LUTPA, including but not limited to conduct alleged herein pursuant to LSA-R.S. 51:1407(A);</P>
                    <P>b. Restitution to any person harmed by Defendants conduct pursuant to LSA-R.S. 51:1408(A)(5);</P>
                    <P>c. Civil penalties pursuant to LSA-R.S. 51:1407(B); and</P>
                    <P>d. Costs and attorneys' fees; and</P>
                    <P>e. Any other relief the court may grant.</P>
                    <HD SOURCE="HD2">Eighteenth Claim for Relief: Violation of Maryland Law</HD>
                    <P>355. Plaintiff State of Maryland incorporates the allegations of Paragraphs 1 through 264 above.</P>
                    <P>356. The Defendants engaged in the conduct alleged above while selling tickets, promoting shows, and operating venues in Maryland. The anticompetitive conduct in Maryland harmed thousands of Maryland fans, venues, promoters, and artists, among others.</P>
                    <P>357. As a result of Defendants' conduct and the related reduction of competition in the relevant markets, Maryland consumers and businesses have suffered anticompetitive harms, including increased prices, increased costs, and reduced quality.</P>
                    <P>
                        358. The Defendants' acts violate the Maryland Antitrust Act, MD Commercial Law Code Ann. § 11-201 
                        <E T="03">et seq.</E>
                         Defendants' conduct alleged herein constitutes unlawful monopolization under MD Commercial Law Code Ann. § 11-204(a).
                    </P>
                    <P>359. The Defendants' conduct alleged herein constitutes an unlawful combination in restraint of trade in violation of MD Commercial Law Code Ann. § 11-204(a). Defendants' conduct has substantially lessened competition and produced anticompetitive effects within the State of Maryland.</P>
                    <P>360. Plaintiff State of Maryland is entitled to all remedies available at law or in equity under Maryland Commercial Law Code Ann. § 11-209 and federal law. Maryland seeks the following remedies available under the Maryland Antitrust Act:</P>
                    <P>a. That the Court adjudge and decree the conduct alleged in the complaint to be unlawful and in violation of the Maryland Antitrust Act;</P>
                    <P>b. Injunctive and other equitable relief pursuant to MD Commercial Law Code Ann. § 11-209;</P>
                    <P>c. Civil penalties pursuant to MD Commercial Law Code Ann. § 11-209;</P>
                    <P>d. Costs and attorney's fees pursuant to MD Commercial Law Code Ann. § 11-209;</P>
                    <P>e. Other remedies, including pre-judgment interest, as the court may deem appropriate under the facts and circumstances of the case.</P>
                    <HD SOURCE="HD2">Nineteenth Claim for Relief: Violation of Michigan Law</HD>
                    <P>361. Plaintiff State of Michigan re-alleges and incorporates the allegations of Paragraphs 1 through 264 above.</P>
                    <P>
                        362. In addition to violating federal law, Defendants' acts constitute violations of the Michigan Antitrust Reform Act (“MARA”; MCL 445.771 
                        <E T="03">et seq.</E>
                        ). MARA shall be applied and harmonized to effectuate its general purpose with deference to “interpretations given by the federal courts to comparable antitrust statutes, including, without limitation, the doctrine of per se violations and the rule of reason.” MCL 445.784.
                    </P>
                    <P>363. Section Two of MARA, MCL 445.772, makes unlawful a contract, combination, or conspiracy between two or more persons in restraint of, or to monopolize, trade or commerce in a relevant market.</P>
                    <P>364. Section Three of MARA, MCL 445.773, makes unlawful the establishment, maintenance, or use of a monopoly, or any attempt to establish a monopoly, of trade or commerce in a relevant market by any person, for the purpose of excluding or limiting competition or controlling, fixing, or maintaining prices.</P>
                    <P>365. Live Nation has established and unlawfully maintained a monopoly in each of the markets alleged in Section VI of this Complaint.</P>
                    <P>366. Through unlawful monopolization of the relevant markets, unlawful exclusive dealing, unlawful tying or some combination thereof, the Defendants have inflicted antitrust injuries on consumers, artists, venue operators and live music promoters in Michigan in violation of Sections Two and Three of MARA.</P>
                    <P>
                        367. The Attorney General brings this suit in the name of the State of Michigan and on behalf of the people of the State of Michigan in her 
                        <E T="03">parens patriae</E>
                         capacity.
                    </P>
                    <P>368. Michigan seeks all legal and equitable relief under Federal law as well as the legal and equitable relief authorized by MCL 445.777 and MCL 445.778, including civil penalties, disgorgement, damages, injunctive relief, and costs and attorney's fees.</P>
                    <HD SOURCE="HD2">Twentieth Claim for Relief: Violation of Minnesota Law</HD>
                    <P>369. Plaintiff State of Minnesota re-alleges and incorporates by reference the allegations of Paragraphs 1 through 264 above.</P>
                    <P>370. In addition to violating federal law, Defendants' acts as alleged herein violate the Minnesota Antitrust Law of 1971, Minnesota Statutes sections 325D.49 to 325D.66.</P>
                    <P>371. Live Nation has unlawfully maintained its monopoly power, as described in Paragraphs 224 through 232 above, over markets related to primary ticketing, including the provision of primary ticketing services to major concert venues, the provision of primary concert ticketing services to major concert venues, and the provision of primary concert ticketing offerings to fans at major concert venues (even if combined with services that offer resale of concert tickets), in violation of Minnesota Statutes section 325D.52. Each of these markets constitute trade or commerce. Defendants have done so for the purpose of affecting competition.</P>
                    <P>
                        372. Ticketmaster's long-term exclusive primary ticketing contracts constitute contracts, combinations, or conspiracies between two or more persons in unreasonable restraint of trade, as described in Paragraphs 233 through 240 above, in violation of Minnesota Statutes section 325D.51.
                        <PRTPAGE P="41361"/>
                    </P>
                    <P>373. Live Nation's requirement that artists seeking to use its large amphitheaters for shows as part of a tour also purchase promotion services from Live Nation constitutes contracts, combinations, or conspiracies between two or more persons in unreasonable restraint of trade, as described in Paragraphs 241 through 248 above, in violation of Minnesota Statutes section 325D.51.</P>
                    <P>374. Live Nation has maintained or used monopoly power over the market for the provision of the use of large amphitheaters and ancillary services to artists on large-amphitheater tours, as described in Paragraphs 249 through 256 above, in violation of Minnesota Statutes section 325D.52. This market constitutes trade or commerce. Live Nation has done so for the purpose of affecting competition.</P>
                    <P>375. Live Nation has maintained or used its monopoly power in the markets for the provision of concert booking and promotion services to major concert venues and the provision of promotion services to artists performing in major concert venues, as described in Paragraphs 257 through 264 above, in violation of Minnesota Statutes section 325D.52. The markets constitute trade or commerce. Live Nation has done so for the purpose of affecting competition.</P>
                    <P>376. Defendants engaged in the conduct described herein while selling tickets, promoting concerts, and operating venues within Minnesota. These violations substantially affect trade and commerce within the State of Minnesota and cause anticompetitive harms to the people of Minnesota and the general economy of Minnesota, such as increased prices, increased costs, reduced choice, reduced innovation, and reduced quality.</P>
                    <P>377. Plaintiff State of Minnesota seeks relief, including but not limited to the following:</P>
                    <P>a. Enjoining Defendants and their employees, officers, directors, agents, successors, assignees, affiliates, merged or acquired predecessors, parents, or controlling entities, subsidiaries, and all other persons acting in concert or participation with them from engaging in conduct in violation of Minnesota Statutes sections 325D.49 to 325D.66;</P>
                    <P>b. Awarding judgment against Defendants for civil penalties pursuant to Minnesota Statutes sections 8.31, subd. 3, and 325D.56; and</P>
                    <P>c. Costs and reasonable attorneys' fees under Minnesota Statutes sections 325D.57 and 8.31, subd. 3a.</P>
                    <HD SOURCE="HD2">Twenty-first Claim for Relief: Violation of Mississippi Law</HD>
                    <P>378. Plaintiff State of Mississippi incorporates the allegations of Paragraphs 1 through 264 above.</P>
                    <P>
                        379. In addition to violating federal law, Defendants' acts as alleged herein also violate the Mississippi Antitrust Act (MAA), Miss. Code Ann § 75-21-1 
                        <E T="03">et seq.</E>
                         These acts have substantially lessened competition and have anticompetitive effects within the State of Mississippi.
                    </P>
                    <P>380. Specifically, Defendants' acts as described above constitute illegal monopolization under Miss. Code Ann. § 75-21-3(b) and restraint of trade under Miss. Code Ann. § 75-21-1(a).</P>
                    <P>381. Plaintiff State of Mississippi is entitled to and seeks all remedies available at law or in equity, including, but without limitation, civil penalties in the amount of $ 2,000.00 for every willful violation of the MAA, pursuant to Miss. Code Ann. § 75-21-7.</P>
                    <HD SOURCE="HD2">Twenty-second Claim for Relief: Violation of Nebraska Law</HD>
                    <P>382. Plaintiff State of Nebraska incorporates the allegations of Paragraphs 1 through 264 above.</P>
                    <P>
                        383. Plaintiff State of Nebraska brings this action pursuant to the Nebraska Unlawful Restraint of Trade Act, Neb. Rev. Stat. § 59-801 
                        <E T="03">et seq.,</E>
                         the Nebraska Consumer Protection Act, § 59-1601 
                        <E T="03">et seq.,</E>
                         and the Nebraska Attorney General's duty to enforce the Nebraska antitrust laws. Neb Rev. Stat. § 84-211 
                        <E T="03">et seq.</E>
                    </P>
                    <P>384. In addition to violating federal law, Defendants' conduct, as alleged herein, constitutes unreasonable restraints of trade, unlawful monopoly maintenance, and unfair methods of competition under the Nebraska Unlawful Restraint of Trade Act and the Nebraska Consumer Protection Act.</P>
                    <P>385. Defendants' violations of the Nebraska antitrust laws arise from their sale of goods, services, and commerce alleged herein.</P>
                    <P>386. Defendants' anticompetitive conduct has occurred within or impacted trade or commerce in Nebraska.</P>
                    <P>387. Defendants' anticompetitive conduct has and will continue to directly and indirectly affect the people of the State of Nebraska by causing increased prices, increased costs, and reduced quality.</P>
                    <P>388. Plaintiff State of Nebraska requests the Court enter a judgment finding Defendants violated Neb. Rev. Stat. §§ 59-801, 59-802, 59-1602, 59-1603, and 59-1604.</P>
                    <P>389. Plaintiff State of Nebraska is entitled to relief including, but not limited to, civil penalties, injunctive relief, and its costs and attorney's fees under Neb. Rev. Stat. §§ 59-1608 and 59-1614.</P>
                    <HD SOURCE="HD2">Twenty-third Claim for Relief: Violation of Nevada Law</HD>
                    <HD SOURCE="HD3">Violations of Nevada Unfair Trade Practices Act</HD>
                    <P>390. The State of Nevada incorporates the allegations of Paragraphs 1 through 264 above.</P>
                    <P>391. The Defendants' conduct in the course of selling tickets, booking and promoting live entertainment shows, and operating concert venues in the State of Nevada has been unlawful, exclusionary and anticompetitive, as described in detail above. This alleged conduct, while national in scope, has harmed fans, venues, promoters and artists throughout, or doing business in, the State of Nevada.</P>
                    <P>
                        392. Live Nation's unlawful maintenance of its monopoly power in each of the various antitrust markets identified in Section VI through anticompetitive and exclusionary conduct, also constitute violations of Nevada law pursuant to the Nevada Unfair Trade Practices Act, Nev. Rev. Stat. § 598A.010, 
                        <E T="03">et seq. See</E>
                         specifically Nev. Rev. Stat. § 598A.060—Prohibited Acts.
                    </P>
                    <P>393. The State of Nevada seeks all remedies available under federal law and the Nevada Unfair Trade Practices Act including, without limitation, the following:</P>
                    <P>a. Civil penalties pursuant to Nev. Rev. Stat. § 598A.170, which provides for “an amount not to exceed 5 percent of the gross income realized by the sale of commodities or services sold by such persons in this state in each year in which the prohibited activities occurred”;</P>
                    <P>b. Damages for natural persons residing in Nevada that were damaged directly or indirectly by the defendants' conduct, pursuant to Nev. Rev. Stat. § 598A.160;</P>
                    <P>c. Injunctive relief pursuant to Nev. Rev. Stat. § 598A.070(c)(1);</P>
                    <P>d. Disgorgement, restitution and other equitable relief as provided by Nev. Rev. Stat. § 598A.070(c)(4);</P>
                    <P>e. Costs and attorney's fees pursuant to Nev. Rev. Stat. § 598A.200; and</P>
                    <P>f. Any other remedies the court may deem appropriate under the facts and circumstances of the case.</P>
                    <HD SOURCE="HD2">Twenty-fourth Claim for Relief: Violation of New Hampshire Law</HD>
                    <P>
                        394. The State of New Hampshire incorporates the allegations of Paragraphs 1 through 264 above.
                        <PRTPAGE P="41362"/>
                    </P>
                    <P>
                        395. The Attorney General for the State of New Hampshire brings this action pursuant to NH RSA 356 
                        <E T="03">et seq.</E>
                         and 15 U.S.C. 12 
                        <E T="03">et seq.</E>
                    </P>
                    <P>396. Defendants' conduct as alleged herein constitutes unlawful contract, combination, or conspiracy in restraint of trade under NH RSA 356:2.</P>
                    <P>397. Defendants' conduct as alleged herein constitutes unlawful establishment, maintenance or use of monopoly power, or an attempt to establish, maintain or use monopoly power over trade or commerce for the purpose of affecting competition or controlling, fixing or maintaining prices under NH RSA 356:3.</P>
                    <P>
                        398. The State of New Hampshire seeks all remedies available under federal law and NH RSA 356:4 
                        <E T="03">et seq.,</E>
                         including, without limitation:
                    </P>
                    <P>
                        a. Damages for natural persons under 
                        <E T="03">parens patriae</E>
                         authority under NH RSA 356:4-a, II;
                    </P>
                    <P>b. Injunctive and other equitable relief under NH RSA 356:4-a;</P>
                    <P>c. Civil penalties under NH RSA 356:4-a;</P>
                    <P>d. Costs and attorney's fees under NH RSA 356:4-b and/or 356:10; and</P>
                    <P>e. Other remedies as the Court may deem appropriate under the facts and circumstances of the case.</P>
                    <P>f.</P>
                    <HD SOURCE="HD2">Twenty-fifth Claim for Relief: Violation of New Jersey Law</HD>
                    <P>399. Plaintiff State of New Jersey repeats and realleges and incorporates by reference Paragraphs 1 through 264 of this Complaint as if fully set forth herein.</P>
                    <P>400. The New Jersey Antitrust Act, N.J.S.A. 56:9-3, states: “Every contract, combination in the form of trust or otherwise, or conspiracy in restraint of trade or commerce, in this State, shall be unlawful.”</P>
                    <P>401. The New Jersey Antitrust Act, N.J.S.A. 56:9-4(a), further states: “It shall be unlawful for any person to monopolize, or attempt to monopolize, or to combine or conspire with any person or persons, to monopolize trade or commerce in any relevant market within this State.”</P>
                    <P>402. Defendants engaged in numerous commercial practices in the operation of their business that violate N.J.S.A. 56:9-3 and N.J.S.A. 56:9-4(a), including but not limited to the following:</P>
                    <P>403. Utilizing Ticketmaster's long-term exclusive agreements to provide primary ticketing services to major concert venues in the State of New Jersey to unreasonably restrain competition;</P>
                    <P>404. Utilizing Ticketmaster's contracts of adhesion to exclude competitors and restrict competitors' access to the only significant distribution channel for primary ticketing services to major concert venues across the State of New Jersey;</P>
                    <P>405. Utilizing Ticketmaster's long-term exclusive primary ticketing contracts to restrict from competition a substantial share of the market for the provision of primary ticketing services to major concert venues in the State of New Jersey; and</P>
                    <P>406. Selling tickets, booking and promoting live shows, and operating concert venues in an unlawful, exclusionary, and anti-competitive manner that lacks a valid procompetitive justification sufficient to offset the harm caused by that unlawful behavior.</P>
                    <P>407. Defendants' violations of the New Jersey Antitrust Act, N.J.S.A. 56: 9-1 to -19, and Section 16 of the Clayton Act, have resulted in the following harm to the citizens of New Jersey and to citizens of other states that have attended events or purchased tickets to events in the State of New Jersey, as well as to venues, promoters, and artists who are located in or do business in the State of New Jersey:</P>
                    <P>408. Causing those who attend live events to pay more in non-transparent, non-negotiable fees without other options;</P>
                    <P>409. Denying consumers the benefits of competition, such as more concert choices and innovative, fan-friendly ticketing options; and</P>
                    <P>410. Restricting the provision of primary ticketing services to major concert venues to fans at major concert venues (even if combined with services that offer resale of concert tickets).</P>
                    <P>411. To restore competition to the affected markets, New Jersey seeks all remedies available under the New Jersey Antitrust Act, N.J.S.A. 56:9-1 to -19, and/or Section 16 of the Clayton Act including, without limitation, the following:</P>
                    <P>a. Divestiture of Ticketmaster and/or venues owned or operated by Live Nation Entertainment, pursuant to N.J.S.A. 56:9-7 and/or Section 16 of the Clayton Act;</P>
                    <P>b. Injunctive and other equitable relief prohibiting Defendants' wrongful conduct, in accordance with N.J.S.A. 56:9-10(a);</P>
                    <P>c. Equitable monetary relief to remedy Defendants' unlawful conduct, pursuant to N.J.S.A. 56:9-10(b);</P>
                    <P>d. Civil penalties of not more than the greater of $100,000 or $500 per day for each and every day of said violation against Defendants, pursuant to N.J.S.A. 56:9-10(c);</P>
                    <P>e. Costs and attorney's fees, pursuant to N.J.S.A. 56:9-12; and</P>
                    <P>f. Other remedies as the Court may deem appropriate and the interests of justice may require.</P>
                    <HD SOURCE="HD2">Twenty-sixth Claim for Relief: Violation of New Mexico Law</HD>
                    <P>412. The State of New Mexico incorporates the allegations of Paragraphs 1 through 264 above.</P>
                    <P>413. Pursuant to Section 15 of the New Mexico Antitrust Act, N.M. Stat. Ann. § 57-1-15, a violation of Sections 1 and 2 of the federal Sherman Antitrust Act also constitutes a violation of Sections 1 and 2 of the New Mexico Antitrust Act, N.M. Stat. Ann. §§ 57-1-1 and -2.</P>
                    <P>414. The Attorney General brings this enforcement action on behalf of the State of New Mexico in its sovereign capacity pursuant to Section 3 of the New Mexico Antitrust Act, N.M. Stat. Ann. § 57-1-3.</P>
                    <P>415. Live Nation has unlawfully maintained its monopoly power in the provision of primary ticketing services to major concert venues through a course of exclusionary conduct described in Paragraphs 224 through 232 above, in violation of Section 2 of the New Mexico Antitrust Act, N.M. Stat. Ann. § 57-1-2.</P>
                    <P>416. Ticketmaster's long-term exclusive agreements to provide primary ticketing services to major concert venues, which exclude all competitors, as described in Paragraphs 233 through 240 above, unreasonably restrain competition in violation of Section 1 of the New Mexico Antitrust Act, N.M. Stat. Ann. § 57-1-1.</P>
                    <P>417. Live Nation has engaged in unlawful, anticompetitive, and exclusionary tying arrangements by requiring artists seeking to perform at large amphitheaters in New Mexico as part of a tour to purchase promotion services from Live Nation, as described in Paragraphs 241 through 248 above, in violation of Section 1 of the New Mexico Antitrust Act, N.M. Stat. Ann. § 57-1-1.</P>
                    <P>418. Live Nation has unlawfully maintained its monopoly power in the provision of large amphitheaters and ancillary services for large amphitheater tours through a course of anticompetitive exclusionary conduct described in Paragraphs 249 through 256 above, in violation of Section 2 of the New Mexico Antitrust Act, N.M. Stat. Ann. § 57-1-2.</P>
                    <P>
                        419. Live Nation has unlawfully maintained its monopoly power in the provision of concert booking and promotion services to major concert venues and the provision of promotion 
                        <PRTPAGE P="41363"/>
                        services to artists performing in major concert venues through a course of anticompetitive exclusionary practices described in Paragraphs 257 through 264 above, in violation of Section 2 of the New Mexico Antitrust Act, N.M. Stat. Ann. § 57-1-2.
                    </P>
                    <P>420. Defendants' acts substantially affect the people who reside in the State of New Mexico and companies that conduct business in New Mexico and have impacts within the State of New Mexico.</P>
                    <P>421. Plaintiff State of New Mexico seeks civil monetary penalties and injunctive relief pursuant to Sections 7 and 8 of the New Mexico Antitrust Act, N.M. Stat. Ann. §§ 57-1-7 and -8.</P>
                    <P>422. Plaintiff State of New Mexico is entitled to costs and reasonable attorney fees pursuant to Section 3 of the New Mexico Antitrust Act, N.M. Stat. Ann. § 57-1-3(A).</P>
                    <HD SOURCE="HD2">Twenty-Seventh Claim for Relief: Violation of New York Law</HD>
                    <P>423. Plaintiff State of New York incorporates the allegations of Paragraphs 1 through 264 above.</P>
                    <P>
                        424. Defendants' acts as alleged in this Complaint violate New York's Donnelly Act, New York General Business Law §§ 340 
                        <E T="03">et seq.,</E>
                         by contracts, agreements, arrangements or combinations that result in the establishment or maintenance of a monopoly and/or by restraining competition.
                    </P>
                    <P>425. Defendants' acts alleged in this Complaint also violate Section 63(12) of New York's Executive Law, in that Defendants have engaged in repeated and/or persistent illegal acts, including violations of Sections 1 and 2 of the Sherman Act, as well as violations of the Donnelly Act.</P>
                    <P>
                        426. To restore competition to the affected markets, New York seeks equitable relief, including an injunction prohibiting Defendants' wrongful conduct, as well as, 
                        <E T="03">inter alia,</E>
                         divestitures of Ticketmaster and venues owned or operated by Live Nation Entertainment, pursuant to Section 16 of the Clayton Act, New York General Business Law § 342 and/or Section 63(12) of the New York Executive Law.
                    </P>
                    <P>427. New York also seeks equitable monetary relief to deter and remedy Defendants' unlawful conduct pursuant to Section 63(12) of the New York Executive Law.</P>
                    <P>428. New York seeks also civil penalties of $1,000,000 per violation against each defendant, pursuant to New York Business Law § 342-a, as well as fees and costs pursuant to federal and state law.</P>
                    <HD SOURCE="HD2">Twenty-Eighth Claim for Relief: Violation of North Carolina Law</HD>
                    <P>429. Plaintiff State of North Carolina incorporates the allegations of Paragraphs 1 through 264 above.</P>
                    <P>430. Defendants engaged in the conduct alleged above while selling tickets and promoting concerts in North Carolina. This anticompetitive conduct in North Carolina harmed fans, venues, promoters, and artists across the State.</P>
                    <P>431. As a result of this conduct, and the concomitant reduction of competition in the relevant markets, North Carolina consumers have suffered anticompetitive harm, including increased prices, increased costs, and reduced quality.</P>
                    <P>432. This conduct has affected North Carolina commerce to a substantial degree.</P>
                    <P>
                        433. Defendants' acts as alleged in the First, Fourth, and Fifth causes of action stated above violate the North Carolina Unfair or Deceptive Trade Practices Act, N.C.G.S. § 75-1 
                        <E T="03">et seq.,</E>
                         in that they constitute unlawful monopolization of a part of trade or commerce in North Carolina. N.C.G.S. § 75-2.1.
                    </P>
                    <P>434. Defendants' acts as alleged in the Second and Third causes of action stated above violate the North Carolina Unfair or Deceptive Trade Practices Act in that they constitute contracts in restraint of trade or commerce in North Carolina, and/or acts and contracts in restraint of trade or commerce which violate the principles of the common law. N.C.G.S. §§ 75-1, 75-2.</P>
                    <P>435. Plaintiff State of North Carolina seeks all remedies available for claims under federal law and claims under N.C.G.S. §§ 75-1, 75-2, and 75-2.1, including, without limitation, the following:</P>
                    <P>a. Disgorgement and restitution pursuant to N.C.G.S. § 75-15.1 and the common law of North Carolina;</P>
                    <P>b. Injunctive and other equitable relief pursuant to N.C.G.S. § 75-14 and the common law of North Carolina;</P>
                    <P>c. Civil penalties pursuant to N.C.G.S. § 75-15.2, which provides a penalty of up to $5,000 per violation;</P>
                    <P>d. Costs and attorneys' fees pursuant to N.C.G.S. § 75-16.1; and</P>
                    <P>e. Other remedies as the court may deem appropriate under the facts and circumstances of the case.</P>
                    <HD SOURCE="HD2">Twenty-Ninth Claim for Relief: Violation of Ohio Law</HD>
                    <P>436. Plaintiff State of Ohio incorporates the allegations of Paragraphs 1 through 264 above.</P>
                    <P>437. Defendants Live Nation Entertainment, Inc. and Ticketmaster L.L.C. contract with and provide live entertainment services and commodities to Ohio businesses and consumers.</P>
                    <P>438. Plaintiff brings this action pursuant to Ohio Rev. Code § 109.81 and Ohio Rev. Code Chapter 1331.</P>
                    <P>439. Plaintiff, having reasonable cause to believe that violations of Ohio's antitrust laws have occurred, brings this action in his sovereign capacity to enforce Ohio law and quasi-sovereign capacity for natural persons residing in the State of Ohio, pursuant to Ohio Rev. Code § 109.81.</P>
                    <P>440. Defendants, by and through their officers, directors, employees, agents, or other representatives, have engaged in a combination of capital, skill, or acts to create or carry out restrictions in trade or commerce in violation of Ohio's Valentine Act. Ohio Rev. Code § 1331.01 and 1331.04.</P>
                    <P>441. Defendants' collective and individual activities as alleged herein, including the vertical arrangements, constitute Trusts under Ohio Rev. Code § 1331.01(C)(1)(a), (b), and (e) and are thus illegal under Ohio's Valentine Act.</P>
                    <P>442. Defendants' collective and individual activities as alleged herein, including the vertical arrangements, are ongoing, and these violations continue at the present time.</P>
                    <P>443. Defendants are members of these Trusts, and the purposes or effects of Defendants' Trusts are to decrease competition, raise prices, and/or stifle innovation in all of the alleged relevant markets. Ohio Rev. Code § 1331.09.</P>
                    <P>444. Defendants' anticompetitive conduct has harmed Ohio fans by causing them to pay more in fees that are not transparent, not negotiable, and cannot be comparison-shopped because there are no other options.</P>
                    <P>445. Defendants' anticompetitive conduct has harmed Ohio fans by denying them access to the benefits a competitive process would deliver, such as more choices in concerts and innovative fan-friendly ticketing options.</P>
                    <P>446. Defendants' anticompetitive conduct has harmed Ohio's general economy.</P>
                    <P>447. This complaint constitutes due notice of these violations under Ohio Rev. Code § 1331.03.</P>
                    <P>448. Plaintiff seeks the following remedies pursuant to Ohio Rev. Code § 109.81 and Chapter 1331:</P>
                    <P>a. Civil forfeiture pursuant to Ohio Rev. Code § 1331.03;</P>
                    <P>b. Relief permanently enjoining Defendants Live Nation Entertainment, Inc. and Ticketmaster L.L.C. from engaging in any acts that violate Ohio's Valentine Act;</P>
                    <P>
                        c. Costs, attorneys' fees, and interest; and
                        <PRTPAGE P="41364"/>
                    </P>
                    <P>d. Other remedies the court may deem appropriate according to the facts and circumstances of the case.</P>
                    <HD SOURCE="HD2">Thirtieth Claim for Relief: Violation of Rhode Island Law</HD>
                    <P>449. The state of Rhode Island incorporates the allegations of Paragraphs 1 through 264 above.</P>
                    <P>450. Defendants engaged in the conduct described above while selling tickets and promoting shows in Rhode Island. This anticompetitive conduct in Rhode Island harmed fans, venues, promoters, and artists across the state.</P>
                    <P>451. As a result of this conduct, and the concomitant reduction in competition in the relevant markets, Rhode Island businesses and residents have suffered anticompetitive harms, including increased prices, increased costs, and reduced quality.</P>
                    <P>452. This conduct has affected Rhode Island commerce to a substantial degree.</P>
                    <P>453. The above conduct constitutes unlawful monopolization within Rhode Island in violation of the Rhode Island Antitrust Law, R.I. Gen. L. § 6-36-5.</P>
                    <P>454. The above conduct constitutes unlawful combination in restraint of trade within Rhode Island in violation of the Rhode Island Antitrust Law, R.I. Gen. L. § 6-36-4.</P>
                    <P>455. The Attorney General of Rhode Island brings this action in the name of the State of Rhode Island and on behalf of the people of the State of Rhode Island pursuant to the authority granted by R.I. Gen. Laws §§ 6-36-11 and 12.</P>
                    <P>456. Rhode Island seeks all remedies available under federal law or the Rhode Island Antitrust Act including, without limitation, the following:</P>
                    <P>a. Civil penalties pursuant to R.I. Gen. L. 6-36-10(c), which provides that “any person who violates this chapter may be liable for a civil penalty of not more than fifty thousand dollars ($50,000) for each violation;”</P>
                    <P>b. Damages for Rhode Island residents pursuant to R.I. Gen. L. § 6-36-12(a);</P>
                    <P>c. Threefold the damages sustained by Rhode Island residents as monetary relief for the State pursuant to § 6-36-12(b);</P>
                    <P>d. Injunctive and other equitable relief pursuant to R.I. Gen. L. § 6-36-10;</P>
                    <P>e. Costs and attorney's fees pursuant to § 6-36-11(a) and 12(b); and</P>
                    <P>f. Other remedies as the court may deem appropriate under the facts and circumstances of the case.</P>
                    <HD SOURCE="HD2">Thirty-First Claim for Relief: Violation of South Carolina Law</HD>
                    <P>457. Plaintiff State of South Carolina incorporates the allegations of Paragraphs 1 through 264 above. Each allegation is brought separately against each Defendant.</P>
                    <P>458. The Attorney General of South Carolina is bringing this action in the name of the State pursuant to S.C. Code § 39-5-50.</P>
                    <P>459. At all times described herein, the Defendants were engaged in conduct which constitutes “trade” and “commerce” as defined in S.C. Code § 39-5-10(b).</P>
                    <P>460. In addition to the Defendants' national presence described above, Defendants' collective and individual business operations, constituting “trade” and “commerce” in South Carolina, comprise a significant percentage of all major live events in South Carolina.</P>
                    <P>461. Through the conduct discussed above and by leveraging large market share in South Carolina, therefore improperly exercising market power, Defendants have constrained, restrained, and improperly and unfairly affected trade and commerce in South Carolina, affecting South Carolinians and the state's commercial environment.</P>
                    <P>462. Upon information and belief, Defendants' collective and individual monopolistic activities have resulted and continue to result in higher prices in South Carolina than a competitive market would bear.</P>
                    <P>463. Similarly, upon information and belief, Defendants' improper exercise of market power in South Carolina enables them to manipulate the quality and quantity of live events, diminishing what would otherwise be available in a competitive market. Defendants' acts or practices regarding South Carolina consumers as alleged herein are capable of repetition and affect the public interest.</P>
                    <P>464. Defendants' acts or practices alleged herein constitute “unfair methods of competition” under S.C. Code § 39-5-20. Every unfair act or practice by each Defendant constitutes a separate and distinct violation of S.C. Code § 39-5-20.</P>
                    <P>465. Defendants' acts or practices alleged herein are offensive to established public policy, immoral, unethical, or oppressive.</P>
                    <P>466. At all times Defendants knew or should have known their conduct violated S.C. Code § 39-5-20 and, therefore, the conduct is willful for purposes of S.C. Code § 39-5-110, justifying civil penalties.</P>
                    <P>467. Plaintiff State of South Carolina seeks all remedies available under the South Carolina Unfair Trade Practices Act (SCUTPA) including, without limitation, the following:</P>
                    <P>a. Permanently enjoin Defendants pursuant to S.C. Code § 39-5-50(a) from engaging in any acts that violate SCUTPA, including, but not limited to, the unfair methods of competition and unfair or deceptive acts or practices alleged herein;</P>
                    <P>b. Civil penalties in the amount of $5,000, pursuant to S.C. Code § 39-5-110(a), for every willful violation of SCUTPA;</P>
                    <P>c. Ascertainable loss as determined by the Court under S.C. Code § 39-5-50(b);</P>
                    <P>d. Costs and attorneys' fees pursuant to S.C. Code § 39-5-50(a) and S.C. Code § 1-7-85; and</P>
                    <P>e. All other legal and equitable relief as the court may deem appropriate under the facts and circumstances of the case.</P>
                    <HD SOURCE="HD2">Thirty-Second Claim for Relief: Violation of Tennessee Law</HD>
                    <P>468. Plaintiff State of Tennessee incorporates the allegations of Paragraphs 1 through 264 above.</P>
                    <P>469. Defendants engaged in the conduct described above while selling tickets, promoting shows, and operating venues in Tennessee. This anticompetitive conduct in Tennessee harmed thousands of fans, venues, promoters, and artists across the state.</P>
                    <P>470. As a result of this conduct, and the concomitant reduction in competition in the relevant markets, Tennesseans and Tennessee businesses have suffered anticompetitive harms, including increased prices, increased costs, and reduced quality.</P>
                    <P>471. This conduct has affected Tennessee commerce to a substantial degree.</P>
                    <P>472. Accordingly, Defendants' actions violate the Tennessee Trade Practices Act, Tenn. Code Ann. §§ 47-25-101 and 102, as amended.</P>
                    <P>
                        473. To remedy this anticompetitive conduct, the Tennessee Attorney General and Reporter seeks all legal and equitable relief to which it is entitled under Tenn. Code Ann. § 47-25-106, including treble damages in its 
                        <E T="03">parens patriae</E>
                         capacity, civil penalties, and injunctive relief.
                    </P>
                    <HD SOURCE="HD2">Thirty-Third Claim for Relief: Violation of Texas Law</HD>
                    <P>474. Plaintiff State of Texas repeats and realleges the allegations of Paragraphs 1 through 264 above. Each allegation is brought separately against each Defendant.</P>
                    <P>
                        475. The aforementioned practices by Defendants Live Nation Entertainment, Inc. and Ticketmaster L.L.C. were and are in violation of Texas Business and Commerce Code § 15.01 
                        <E T="03">et seq.</E>
                    </P>
                    <P>
                        476. Plaintiff State of Texas has reason to believe that Defendants have engaged in, and will continue to engage in, the anticompetitive and exclusionary course of conduct set forth herein, has 
                        <PRTPAGE P="41365"/>
                        caused and will cause adverse effects to consumers and harm to economic competition in trade and commerce in this State, and will cause damage to the State of Texas and to persons in the State of Texas. Therefore, the Antitrust Division of the Office of the Attorney General of the State of Texas believes and is of the opinion that this matter is in the public interest.
                    </P>
                    <P>
                        477. The State of Texas requests a judgment that the Defendants engaged in conduct in violation of Texas Business and Commerce Code § 15.01 
                        <E T="03">et seq.</E>
                    </P>
                    <P>478. The State of Texas requests a civil fine up to the maximum amount allowed pursuant to Texas Business and Commerce Code § 15.20(a).</P>
                    <P>479. The State of Texas requests the issuance of a permanent injunction to enjoin any activity or contemplated activity that violates or threatens to violate any of the prohibitions in § 15.05 pursuant to the Texas Business and Commerce Code § 15.20(b).</P>
                    <P>480. The State of Texas requests its costs of this suit, including attorneys' fees, pursuant to § 15.20(b) of the Texas Business and Commerce Code and § 402.006 of the Texas Government Code.</P>
                    <HD SOURCE="HD2">Thirty-Fourth Claim for Relief: Violation of Utah Law</HD>
                    <P>481. The state of Utah incorporates the allegations of Paragraphs 1 through 264 above.</P>
                    <P>482. Defendants engaged in the conduct described above while selling tickets and promoting shows in Utah. This anticompetitive conduct in Utah harmed fans, venues, promoters, and artists across the state.</P>
                    <P>483. As a result of this conduct, and the concomitant reduction in competition in the relevant markets, Utah businesses and residents have suffered anticompetitive harms, including increased prices, increased costs, and reduced quality.</P>
                    <P>484. This conduct has affected Utah commerce to a substantial degree.</P>
                    <P>485. The above conduct violated the Utah Antitrust Act, Utah Code § 76-10-3104(1) and (2).</P>
                    <P>486. The Attorney General of Utah brings this action in the name of the State of Utah and on behalf of the people of the State of Utah pursuant to the authority granted by Utah Code § 76-10-3106.</P>
                    <P>487. Utah seeks all remedies available under federal law or the Utah Antitrust Act including, without limitation, the following:</P>
                    <P>
                        a. Damages for Utah residents as 
                        <E T="03">parens patriae</E>
                         pursuant to Utah Code § 76-10-3108(1);
                    </P>
                    <P>b. Threefold the damages sustained by Utah residents as monetary relief for the State pursuant to Utah Code § 76-10-3109(1)(b);</P>
                    <P>c. Civil penalties pursuant to Utah Code § 76-10-3108(2), which provides that “Any individual who violates this act is subject to a civil penalty of not more than $100,000 for each violation. Any person, other than an individual, who violates this act is subject to a civil penalty of not more than $500,000 for each violation.”</P>
                    <P>d. Injunctive and other equitable relief pursuant to Utah Code § 76-10-3108(1);</P>
                    <P>e. Costs and attorney's fees pursuant to Utah Code § 76-10-3109(1)(b); and</P>
                    <P>f. Other remedies as the court may deem appropriate under the facts and circumstances of the case.</P>
                    <HD SOURCE="HD2">Thirty-fifth Claim for Relief: Violation of Vermont Law</HD>
                    <P>
                        488. Plaintiff State of Vermont repeats and realleges the allegations of paragraphs 1 through 232 above.
                        <SU>14</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>14</SU>
                             The State of Vermont does not allege claims for relief 2, 3, 4, and 5.
                        </P>
                    </FTNT>
                    <P>
                        489. In addition to violating the federal law as set forth in Count 1, Defendants' acts as alleged herein also constitute violations of Vermont's Consumer Protection Act, 9 Vermont Statutes Annotated (“V.S.A.”) § 2451 
                        <E T="03">et seq.,</E>
                         as follows:
                    </P>
                    <P>a. Live Nation as described in paragraphs 1 through 232, has unlawfully established, maintained, and used its monopoly power in several markets in violation of 9 V.S.A. § 2453. These markets include the provision of primary ticketing services to major concert venues, the provision of primary concert ticketing services to major concert venues, and the provision of primary concert ticketing to fans at major concert venues.</P>
                    <P>b. Live Nation committed these violations while selling tickets to Vermont consumers and promoting events within the State of Vermont. These violations ultimately harm fans across Vermont by increasing costs and prices, and reducing choice, innovation, and quality.</P>
                    <P>490. In addition to its federal law remedies, the State of Vermont seeks all remedies available under 9 V.S.A. § 2458, including, without limitation, the following:</P>
                    <P>a. Civil penalties, injunctive relief, other equitable relief (including but not limited to disgorgement), fees and costs, and other relief as this Court deems just and equitable pursuant to 9 V.S.A. § 2458; and</P>
                    <P>b. Other remedies as the Court may deem appropriate under the facts and circumstances of this case.</P>
                    <HD SOURCE="HD2">Thirty-Sixth Claim for Relief: Violation of Virginia Law</HD>
                    <P>491. Plaintiff Commonwealth of Virginia incorporates the allegations of Paragraphs 1 through 264 above.</P>
                    <P>
                        <E T="03">492.</E>
                         Defendants' acts described above violate the Virginia Antitrust Act, Va. Code § 59.1-9.1 
                        <E T="03">et seq.,</E>
                         which “shall be applied and construed to effectuate its general purposes in harmony with judicial interpretation of comparable federal statutory provisions.” Va. Code § 59.1-9.17. Conduct that violates Sections 1 and 2 of the Sherman Act, 15 U.S.C. 1-2, when falling under the Commonwealth's jurisdiction, also violates Va. Code §§ 59.1-9.5-9.6.
                    </P>
                    <P>493. Defendants engaged in the conduct described above while selling tickets to Virginia residents and citizens and from concerts operated at Virginia venues, promoting concerts in Virginia, and operating venues in Virginia. This anticompetitive conduct harmed fans, venues, promoters, and artists across the Commonwealth and affected commerce therein.</P>
                    <P>494. Plaintiff Commonwealth of Virginia is entitled to remedies for the claims alleged above, including but not limited to civil penalties and injunctive relief under Va. Code § 59.1-9.11 and other remedies (including recovery of costs and attorney's fees) under Va. Code § 59.1-9.15. The Commonwealth of Virginia also demands remedies available to it under federal law, including equitable relief as alleged above.</P>
                    <HD SOURCE="HD2">Thirty-Seventh Claim for Relief: Violation of Washington Law</HD>
                    <P>495. The state of Washington incorporates the allegations of Paragraphs 1 through 264 above.</P>
                    <P>496. The acts alleged in the claims for relief also constitute antitrust violations pursuant to the Washington Consumer Protection Act under Wash. Rev. Code § 19.86.030 (2024) and § 19.86.040 (2024), which declares unlawful every contract, combination, or conspiracy in restraint of trade or commerce.</P>
                    <P>497. Defendants engaged in the conduct described above while selling tickets, promoting shows, and operating venues in Washington. The anticompetitive conduct in Washington harmed thousands of Washington fans as well as venues, promoters, and artists across the state.</P>
                    <P>
                        498. The acts alleged in the claims for relief also constitute antitrust violations pursuant to the Washington Consumer Protection Act under Wash. Rev. Code § 19.86.040 (2024), which declares it unlawful for any person to monopolize or attempt to monopolize any part of trade or commerce.
                        <PRTPAGE P="41366"/>
                    </P>
                    <P>499. Upon information and belief, Defendants' collective and individual monopolistic activities have resulted and continue to result in higher prices in Washington than a competitive market would bear.</P>
                    <P>500. Similarly, upon information and belief, Defendants' improper exercise of market power in Washington enables Defendants to manipulate the quality and quantity of live events, diminishing what would otherwise be available in a competitive market.</P>
                    <P>501. Washington seeks the following remedies available under the Washington Consumer Protection Act including, without limitation, the following:</P>
                    <P>a. That the Court adjudge and decree the conduct alleged in the complaint to be unlawful and in violation of the Washington Consumer Protection Act, Wash. Rev. Code § 19.86.030 (2024) and § 19.86.040 (2024);</P>
                    <P>b. Injunctive and other equitable relief pursuant to Wash. Rev. Code § 19.86.080 (2024);</P>
                    <P>c. Disgorgement and restitution pursuant to Wash. Rev. Code § 19.86.080 (2024);</P>
                    <P>d. Civil penalties pursuant to Wash. Rev. Code § 19.86.140 (2024);</P>
                    <P>e. Costs and attorney's fees pursuant to Wash. Rev. Code § 19.86.080 (2024); and</P>
                    <P>f. Other remedies, including pre-judgment interest, as the court may deem appropriate under the facts and circumstances of the case.</P>
                    <HD SOURCE="HD2">Thirty-Eighth Claim for Relief: Violation of West Virginia Law</HD>
                    <P>502. Plaintiff State of West Virginia incorporates the allegations of Paragraphs 1 through 264 above.</P>
                    <P>503. Defendants engaged in the conduct described above while selling tickets, promoting shows, and operating venues in West Virginia. The anticompetitive conduct in West Virginia harmed thousands of West Viriginia fans as well as venues, promoters, and artists across the state.</P>
                    <P>
                        504. Defendants' acts described above generally violate the West Virginia Antitrust Act, W. Va. Code § 47-18-1 
                        <E T="03">et seq.,</E>
                         and specifically the prohibition from establishing, maintaining or using a monopoly of trade or commerce to exclude competition or control, fix or maintain prices. W.Va. Code § 47-18-4.
                    </P>
                    <P>505. Defendants' acts described above further violate the West Virginia Antitrust Act through their exclusionary, long term contracts. W.Va. Code § 47-18-3(b)(1) and (3).</P>
                    <P>506. Defendants' acts described above substantially affected the State of West Virginia and had and have impacts within the State of West Virginia.</P>
                    <P>507. As a result of the Defendants' conduct described above, West Virginia consumers have suffered anticompetitive harms, including increased prices, increased costs, and reduced quality of services.</P>
                    <P>
                        508. Plaintiff State of West Virginia, in its 
                        <E T="03">parens patriae</E>
                         capacity, is entitled to all remedies available at law or in equity (including damages, injunctive relief, disgorgement, restitution, and reimbursement), W. Va. Code §§ 47-18-8, -9, and -17, as well as civil penalties under West Virginia Code § 47-18-8.
                    </P>
                    <P>509. Plaintiff State of West Virginia also is entitled to recover its costs and attorneys' fees under West Virginia Code §§ 47-18-8, -9, and -17.</P>
                    <HD SOURCE="HD2">Thirty-Ninth Claim for Relief: Violation of Wisconsin Law</HD>
                    <P>510. Plaintiff State of Wisconsin repeats and re-alleges and incorporates by reference the allegations of Paragraphs 1 through 264 above as if fully set forth herein.</P>
                    <P>511. Defendants' acts as alleged in the First, Fourth, and Fifth causes of action stated above violate Wis. Stat. § 133.03(2) in that they constitute unlawful monopolization of a part of trade or commerce in Wisconsin.</P>
                    <P>512. Defendants' acts as alleged in the Second and Third causes of action stated above violate Wis. Stat. § 133.03(1) in that they constitute unlawful restraints of trade or commerce in Wisconsin.</P>
                    <P>513. Defendants engaged in the conduct described above while selling tickets, promoting shows, and operating venues in Wisconsin. The anticompetitive conduct in Wisconsin harmed thousands of Wisconsin fans as well as venues, promoters, and artists across the state.</P>
                    <P>514. As a result of this conduct, and the concomitant reduction in competition in the relevant markets, Wisconsin consumers and Wisconsin businesses have suffered anticompetitive harms, including increased prices, increased costs, and reduced quality.</P>
                    <P>515. This conduct has affected Wisconsin commerce to a substantial degree.</P>
                    <P>516. In addition to its federal law remedies, Plaintiff State of Wisconsin, through its Attorney General and under its antitrust enforcement authority in Wis. Stat. Ch. 133, is entitled to all remedies available under Wis. Stat. §§ 133.03, 133.16, 133.17, and 133.18, including, without limitation, the following:</P>
                    <P>a. Civil penalties pursuant to Wis. Stat. § 133.03;</P>
                    <P>b. Injunctive and other equitable relief pursuant to Wis. Stat. § 133.16;</P>
                    <P>c. Costs and attorneys' fees pursuant to Wis. Stat. § 133.16; and;</P>
                    <P>d. Other remedies as the Court may deem appropriate under the facts and circumstances of this case.</P>
                    <HD SOURCE="HD1">X. Request for Relief</HD>
                    <P>517. To remedy these illegal acts, Plaintiffs request that the Court:</P>
                    <P>a. Adjudge and decree that Live Nation has acted unlawfully to maintain its monopoly in the markets for the provision of primary ticketing services to major concert venues, the provision of primary concert ticketing services to major concert venues, and the provision of primary concert ticketing offerings to fans at major concert venues (even if combined with services that offer resale of concert tickets), in violation of Section 2 of the Sherman Act, 15 U.S.C. 2 and the state laws cited in paragraphs 265 through 516 above;</P>
                    <P>b. Adjudge and decree that Live Nation has acted unlawfully by entering into long-term exclusive primary ticketing contracts with major concert venues that unreasonably restrain trade in the United States in violation of Section 1 of the Sherman Act, 15 U.S.C. 1 and the state laws cited in paragraphs 265 through 516 above;</P>
                    <P>c. Adjudge and decree that Live Nation has acted unlawfully by tying artists' use of Live Nation owned, controlled and exclusively-booked large amphitheaters to their purchase of promotional services from Live Nation in violation of Section 1 of the Sherman Act, 15 U.S.C. 1 and the state laws cited in paragraphs 265 through 516 above;</P>
                    <P>d. Adjudge and decree that Live Nation has acted unlawfully to maintain its monopoly in the market for the provision of the use of large amphitheaters and ancillary services to artists on large amphitheater tours, in violation of Section 2 of the Sherman Act, 15 U.S.C. 2 and the state laws cited in paragraphs 265 through 516 above;</P>
                    <P>e. Adjudge and decree that Live Nation has acted unlawfully to maintain its monopoly in the markets for the provision of concert booking and promotion services to major concert venues and the provision of promotion services to artists performing in major concert venues, in violation of Section 2 of the Sherman Act, 15 U.S.C. 2 and the state laws cited in paragraphs 265 through 516 above;</P>
                    <P>
                        f. Order the divestiture of, at minimum, Ticketmaster, along with any additional relief as needed to cure any anticompetitive harm;
                        <PRTPAGE P="41367"/>
                    </P>
                    <P>g. Order the termination of Live Nation's ticketing agreement with Oak View Group;</P>
                    <P>h. Enjoin Live Nation from continuing to engage in anticompetitive practices described herein and from engaging in other practices with the same purpose and effect as the challenged practices;</P>
                    <P>i. Enter any other preliminary or permanent relief necessary and appropriate to restore competitive conditions in the markets affected by Live Nation's unlawful conduct;</P>
                    <P>
                        j. Award the States of Arizona, Arkansas, Colorado, Connecticut, Florida, Illinois, Indiana, Iowa, Michigan, Minnesota, Nevada, New Hampshire, New Jersey, New York, North Carolina, Ohio, Oklahoma, Oregon, Rhode Island, South Carolina, Tennessee, Utah, Washington, West Virginia, and Wisconsin, the Commonwealth of Pennsylvania and the District of Columbia, pursuant to their 
                        <E T="03">parens patriae</E>
                         authority on behalf of natural persons residing in their respective states, commonwealths and district, treble damages for injury sustained by such natural persons to their property through the purchase of tickets for live events from Live Nation and Ticketmaster, and the cost of suit, including reasonable attorneys' fees, pursuant to Section 4c of the Clayton Act, 15 U.S.C. 15c;
                    </P>
                    <P>k. Award the States of Arizona, Arkansas, California, Colorado, Connecticut, Florida, Illinois, Indiana, Iowa, Kansas, Louisiana, Maryland, Michigan, Minnesota, Mississippi, Nebraska, Nevada, New Hampshire, New Jersey, New Mexico, New York, North Carolina, Ohio, Rhode Island, South Carolina, Tennessee, Texas, Utah, Vermont, Washington, West Virginia, and Wisconsin, the Commonwealth of Virginia, and the District of Columbia civil penalties or civil forfeiture, under their respective state laws, for the violations cited herein;</P>
                    <P>l. Award any additional relief in law or equity the Court finds just and proper; and</P>
                    <P>m. Award each Plaintiff, as applicable, an amount equal to its costs, including reasonable attorneys' fees, incurred in bringing this action.</P>
                    <HD SOURCE="HD1">XI. Demand for a Jury Trial</HD>
                    <P>518. Pursuant to Federal Rule of Civil Procedure 38(b), Plaintiffs demand a trial by jury of all issues properly triable to a jury in this case.</P>
                    <BILCOD>BILLING CODE 4410-11-P</BILCOD>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41368"/>
                        <GID>EN06JY26.090</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41369"/>
                        <GID>EN06JY26.091</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41370"/>
                        <GID>EN06JY26.092</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41371"/>
                        <GID>EN06JY26.093</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41372"/>
                        <GID>EN06JY26.094</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41373"/>
                        <GID>EN06JY26.095</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41374"/>
                        <GID>EN06JY26.096</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41375"/>
                        <GID>EN06JY26.097</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41376"/>
                        <GID>EN06JY26.098</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41377"/>
                        <GID>EN06JY26.099</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41378"/>
                        <GID>EN06JY26.100</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41379"/>
                        <GID>EN06JY26.101</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41380"/>
                        <GID>EN06JY26.102</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41381"/>
                        <GID>EN06JY26.103</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41382"/>
                        <GID>EN06JY26.104</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41383"/>
                        <GID>EN06JY26.105</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41384"/>
                        <GID>EN06JY26.106</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41385"/>
                        <GID>EN06JY26.107</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="632">
                        <PRTPAGE P="41386"/>
                        <GID>EN06JY26.108</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="41387"/>
                        <GID>EN06JY26.109</GID>
                    </GPH>
                    <PRTPAGE P="41388"/>
                    <HD SOURCE="HD1">UNITED STATES DISTRICT COURT SOUTHERN DISTRICT OF NEW YORK</HD>
                    <P>
                        UNITED STATES OF AMERICA, 
                        <E T="03">et al., Plaintiffs,</E>
                         v. 
                        <E T="03">LIVE NATION ENTERTAINMENT, INC. and TICKETMASTER L.L.C., Defendants.</E>
                    </P>
                    <HD SOURCE="HD3">Case No. 1:24-cv-3973-AS</HD>
                    <HD SOURCE="HD1">PROPOSED FINAL JUDGMENT</HD>
                    <P>
                        <E T="03">Whereas,</E>
                         Plaintiff, United States of America, along with the Attorneys General of Arkansas, Iowa, Mississippi, Nebraska, Oklahoma, and South Dakota (collectively, the “Settling States”), filed their Amended Complaint on August 30, 2024 (“Amended Complaint”);
                    </P>
                    <P>
                        <E T="03">And whereas,</E>
                         the United States, the Settling States, and Defendants, Live Nation Entertainment, Inc. and Ticketmaster L.L.C., consent to entry of this Final Judgment;
                    </P>
                    <P>
                        <E T="03">And whereas,</E>
                         Defendants agree to undertake the obligations and obey the prohibitions described in this Final Judgment to remedy the loss of competition alleged in the Amended Complaint;
                    </P>
                    <P>
                        <E T="03">And whereas,</E>
                         Defendants represent that the relief required by this Final Judgment can and will be made and that Defendants will not later raise a claim of hardship or difficulty as grounds for asking the Court to modify any provision of this Final Judgment;
                    </P>
                    <P>
                        <E T="03">Now Therefore, it is ordered, adjudged, and decreed:</E>
                    </P>
                    <HD SOURCE="HD1">I. Jurisdiction</HD>
                    <P>The Court has jurisdiction over the subject matter of, and each of the parties to, this action. The Amended Complaint states a claim upon which relief may be granted against Defendants under Sections 1 and 2 of the Sherman Act (15 U.S.C. 1-2) and the state laws identified in the Amended Complaint that correspond to claims brought by the Settling States.</P>
                    <HD SOURCE="HD1">II. Definitions</HD>
                    <P>As used in this Final Judgment:</P>
                    <P>A. “Live Nation” means Defendant Live Nation Entertainment Inc., a Delaware corporation with its headquarters in Beverly Hills, California, its successors and assigns, and its subsidiaries, divisions, groups, affiliates, partnerships, and joint ventures, in each instance if controlled by Live Nation Entertainment, Inc., and their directors, officers, managers, agents, and employees, except for those entities listed on Schedule A attached hereto, so long as Defendants lack operational and management control over those entities and do not exercise their influence over, or otherwise use, those entities to engage in conduct prohibited by this Final Judgment.</P>
                    <P>B. “Ticketmaster” means Defendant Ticketmaster L.L.C., a Virginia limited liability company with its headquarters in Beverly Hills, CA, its successors and assigns, and its subsidiaries, divisions, groups, affiliates, partnerships, and joint ventures, in each instance if controlled by Ticketmaster L.L.C., and their directors, officers, managers, agents, and employees.</P>
                    <P>C. “Amphitheater” means an outdoor Venue that typically has a lawn with general admission seating, and is (1) a Major Concert Venue that is identified as an “amphitheater” on Schedule B attached hereto (but solely for so long as such Venue remains a “Major Concert Venue” as defined herein), or (2) a Venue not listed on Schedule B but that is or becomes a Major Concert Venue as defined in Section II.N.</P>
                    <P>D. “API” means an application programming interface.</P>
                    <P>E. “Artist” means any creator or performer of live entertainment content, including concert, comedy, theatrical, or family entertainment content.</P>
                    <P>
                        F. “Client Ticketing Data” means the following data relating to a ticketing client's events: on-sale dates for a client's events, the number of tickets sold, location or type of tickets sold, ticket prices (including all fees charged and the amount of such fees), sales proceeds, marketing and promotions results, ticket purchaser/ticket holder information, and inventory status of any particular ticket. “Client Ticketing Data” does not include data that: (1) is collected through other means (
                        <E T="03">e.g.,</E>
                         website visitor tracking, user group surveys, public sources); or (2) is made public by someone other than Defendants and Defendants' agents.
                    </P>
                    <P>G. “Condition” or “Conditioning” means to explicitly or practically require buyers to purchase or use one product or service if they want to purchase or use a second product or service. In addition to explicit Conditioning, Conditioning can also occur if, due to the seller's pricing, policies, or other conduct, it is unreasonably difficult, costly, or economically infeasible to purchase the desired product or service alone.</P>
                    <P>H. “Content Steering” means, with respect to concert promotion or booking, any decision, conduct, or action that requires, encourages, prohibits, or discourages an Artist to perform at a particular Venue based on the identity of a Primary Ticketing Services provider of such Venue or the revenue that Defendants receive by virtue of being a Primary Ticketing Services provider of such Venue. For clarity, “Content Steering” does not include (1) truthful and non-misleading discussions with an Artist about the capabilities of the Primary Ticketing Services provider(s) of such Venue and how that might affect the Artist's interests, or (2) decisions made in the ordinary course of business based on commercial considerations other than the identity of the Primary Ticketing Services provider(s) or the revenue Defendants receive by virtue of being the Primary Ticketing Services provider, including scheduling, demand, production requirements, or other non-prohibited economic factors.</P>
                    <P>I. “Eligible Primary Ticketing Services Provider” means a Person that either (1) is engaged in the sale of primary tickets for Live Entertainment Events at Venues in the United States through a Primary Marketplace as an established ongoing business (independent of any primary tickets received as part of Ticketmaster's non-exclusivity under this Final Judgment), or (2) has demonstrated or can demonstrate the ability to fully provide Primary Ticketing Services for Major Concert Venues in the United States by offering both a Primary Marketplace and a Primary Ticketing Back-End. Any Person that qualifies under Clause (1) of this definition and also operates a secondary ticket sales business can remain qualified under Clause (1) only if it (a) maintains and reasonably enforces a policy prohibiting speculative ticket sales (including but not limited to the listing, offering for sale, or sale of tickets that the seller does not own, control, or have been contractually allocated at the time of listing, and including a firmly enforced prohibition on the sale of any tickets prior to a material pre-sale or on-sale); (b) follows bona fide artist, team, or other content owner requests to limit resale to face value (or other pricing restrictions), geofence sales, or otherwise adhere to content owner requests for secondary ticket sales on designated events; (c) requires ticket sellers to disclose their identities to the marketplace operator; and (d) prohibits ticket listings without specific section, row and seat quantity, or other indicia that the tickets are genuine. Any disputes as to whether a Primary Ticketing Services provider qualifies as an Eligible Primary Ticketing Services Provider will be resolved by the process set forth in Section IV.E.</P>
                    <P>
                        J. “Exempted Employee” means any employee of Defendants who is not a Firewall Employee, including: (1) any senior corporate officer, director, or manager with responsibilities that include oversight of Defendants' provision of Primary Ticketing Services; and (2) any employee whose primary 
                        <PRTPAGE P="41389"/>
                        responsibilities solely include accounting, human resources, legal, information systems, and/or finance.
                    </P>
                    <P>K. “Firewall Employee” means any employee of Defendants whose principal job responsibility involves the operation or day-to-day management of Defendants' Venues, concert promotions, or Artist management services.</P>
                    <P>L. “Including” means including, but not limited to.</P>
                    <P>M. “Live Entertainment Event” means an event (other than a multi-day multi-Artist festival or similar event) where an Artist performs in a Venue and for which tickets are sold to the public. References herein to the “provision of” or “providing” Live Entertainment Events means to supply one or more Live Entertainment Events and/or the services reasonably necessary to plan, promote, market, and settle one or more Live Entertainment Events, such as concert promotion services, but specifically excludes the provision of Primary Ticketing Services, Venue management services, and/or tour stage/set design and construction services.</P>
                    <P>N. “Major Concert Venue” means (1) each of the Venues set forth on Schedule B attached hereto, and (2) any other Amphitheater or arena located in the United States that has a Live Entertainment Event sellable capacity of 8,000 or more and (a) hosted ten or more Live Entertainment Events in any calendar year from 2024 through the term of this Final Judgment or (b) is new and forecasts hosting ten or more Live Entertainment Events in an upcoming calendar year. Any Venue added to this definition pursuant to subclause (2) of this Section will be deemed a “Major Concert Venue” solely on a prospective basis in connection with new contracts entered into after the end of the immediately preceding calendar year. Notwithstanding the foregoing or anything to the contrary in this Final Judgment, if a particular Venue undergoes a structural or systemic operational change that reduces its Live Entertainment Event sellable capacity to fewer than 8,000 people or no longer regularly operates as an Amphitheater or arena that hosts Live Entertainment Events on a consistent basis, then such Venue will not be considered a “Major Concert Venue” for purposes of the next calendar year.</P>
                    <P>O. “Management” means all directors and officers of Defendants, or any other employee with management or supervisory responsibilities for Defendants' business or operations related to negotiating the provision of Primary Ticketing Services or the provision of Live Entertainment Events.</P>
                    <P>
                        P. “Nondiscriminatory Calendar Procedures” means the procedures that govern requesting, holding, and challenging dates for Live Entertainment Events on the Venue's booking calendar that apply generally to Promoters on a nondiscriminatory basis (
                        <E T="03">i.e.,</E>
                         without regard to whether any given Promoter is owned or operated by, or otherwise affiliated with, Defendants) and include, at minimum, the following principles: (1) equal application to all Promoters, including Live Nation and third-party Promoters; (2) assignment of hold positions based on the order in which complete booking requests are received; (3) a challenge process by which any date holder may require priority-position holders to either confirm their booking with a binding commitment or release the date; and (4) standardized confirmation requirements, including execution of a license agreement, receipt of the required deposit, and written confirmation.
                    </P>
                    <P>Q. “Oak View Group” means Oak View Group LLC, a Delaware limited liability company with its headquarters in Denver, Colorado, its successors and assigns, and its subsidiaries, divisions, groups, affiliates, partnerships, and joint ventures, and their directors, officers, managers, agents, and employees.</P>
                    <P>R. “Person” or “Persons” means any natural person, corporate entity, partnership, association, joint venture, or trust, including corporations and associations existing under or authorized by the laws of the United States, the laws of any State, or the laws of any foreign country.</P>
                    <P>S. “Preferred Booking Agreement” means an agreement or understanding between a Venue and Live Nation that grants Live Nation any Preferred Booking Rights. “Preferred Booking Agreement” does not include: (1) agreements or understandings between a Venue and Live Nation that engage Live Nation to book such Venue and to administer, but not control, such Venue's booking calendar so long as the agreement does not include any Preferred Booking Rights; (2) operating leases, subleases, or similar agreements between a Venue and Live Nation that grant Live Nation the right to operate the Venue; or (3) agreements between Live Nation and a third-party Promoter pursuant to which the third-party Promoter sublicenses or otherwise grants to Live Nation the right to book and/or promote only a portion of the Live Entertainment Events at the Venue, so long as Live Nation promotes less than 50% of the total number of Live Entertainment Events that are held at the applicable Venue in a calendar year.</P>
                    <P>T. “Preferred Booking Rights” means rights that grant: (1) preferred access to certain dates for booking and/or promotion of Live Entertainment Events at the Venue not otherwise generally available to Promoters, other than in accordance with Nondiscriminatory Calendar Procedures; (2) the exclusive right to book and/or promote all, or a specified number of, Live Entertainment Events at the Venue; (3) co-promotion rights that require third party Promoters to co-promote Live Entertainment Events at the Venue with Live Nation; (4) booking rights of first refusal for dates at the Venue; (5) most-favored nation booking or promotion rights at the Venue; and (6) rebates to Live Nation for shows promoted by third parties. For clarity, “Preferred Booking Rights” do not include incentives by a Venue to encourage the achievement of financial thresholds or show volume from a Promoter or to re-coup prepayments or other guaranteed financial commitments made by the Promoter to the Venue.</P>
                    <P>U. “Primary Marketplace” means a technology or distribution platform for making the initial distribution of tickets. For clarity, “Primary Marketplace” does not include technology or distribution platforms that lack the ability to fulfill the responsibilities of a merchant of record, as described in Section IV.A.</P>
                    <P>V. “Primary Ticketing Back-End” means the collection of software, technology, and/or platform services provided to, and used by or on behalf of, Major Concert Venues for the following functions related to the ticketing of Live Entertainment Events: (1) event and inventory configuration; (2) manifest, seat map, inventory, holds, and exclusive allocation controls; (3) barcode/token generation; (4) secure rendering support; (5) ticket-validity and entry-control validation; (6) entry scan validation; (7) maintenance of operational/audit logs necessary to support allocation, token issuance, and scanning; and (8) providing data feeds, APIs, and reporting related to event details, inventory status, entry scans, and other relevant and applicable data points.</P>
                    <P>W. Primary Ticketing Services means the provision of a Primary Ticketing Back-End, or a Primary Marketplace, or both.</P>
                    <P>
                        X. “Promoter” means a Person (other than an Artist and its managers and/or agents) that generally bears the potential financial risk and gain of presenting Live Entertainment Events and assists with the planning and production of Live Entertainment Events, such as by working with Artists (and the Artist's managers and/or agents) to construct a 
                        <PRTPAGE P="41390"/>
                        tour, negotiate with and select Venue(s) at which to perform, determine ticket prices and distribution strategy, advertise or publicize the show or tour to the public, and/or organize staffing or logistics for the Artist's team.
                    </P>
                    <P>Y. “Relevant Employees” means Defendants' employees with responsibility for Primary Ticketing Services or Live Entertainment Events.</P>
                    <P>Z. “Retaliate” or “Retaliating” means refusing to provide Live Entertainment Events to a Venue, or providing Live Entertainment Events to a Venue on less favorable terms, because the Venue has contracted or is contemplating contracting with a company other than Defendants for Primary Ticketing Services. “Retaliate” does not mean: (1) truthful and non-misleading discussions with an Artist about the capabilities of the Primary Ticketing Services provider(s) of such Venue and how that might affect the Artist's interests, (2) actions taken at the independent direction of an Artist or an Artist's managers or agents, or (3) other decisions made in the ordinary course of business based on commercial considerations other than the identity of the Primary Ticketing Services provider(s) or the revenue Defendants receive by virtue of being the Primary Ticketing Services provider, including scheduling, demand, production requirements, or other non-prohibited economic factors.</P>
                    <P>
                        AA. “Ticket Service Fees” means all service charges retained (in whole or part) by the Primary Ticketing Services provider, shipping and handling fees, and order processing fees. “Ticket Service Fees” do not include Venue or facility fees, credit card fees and other payment processing fees, and fees charged in connection with any optional add-ons (
                        <E T="03">e.g.,</E>
                         insurance, payment installment plan fees, merchandise, and any other service or product not required for the purchase of a primary ticket).
                    </P>
                    <P>BB. “Ticketmaster Back-End” means the full suite of Ticketmaster software, technology, and/or platform services used by or on behalf of Venues for functions related to the ticketing of Live Entertainment Events such as: (1) event and inventory configuration; (2) manifest, seat map, inventory, holds, and exclusive allocation controls; (3) third-party Primary Ticketing Services provider authorization and credentialing; (4) APIs, feeds, queues, or other mechanisms for third-party Primary Ticketing Services providers to retrieve allocated inventory; (5) validation of third-party ticketing service provider sale requests; (6) barcode/token generation; (7) secure rendering support; (8) ticket-validity and entry-control validation; (9) entry scan validation; (10) maintenance of operational/audit logs necessary to support allocation, token issuance, and scanning; and (11) providing data feeds, APIs, and reporting related to event details, inventory status, entry scans, and other relevant and applicable data points. For clarity, Ticketmaster Marketplace is distinct from and not included in Ticketmaster Back-End, and together, Ticketmaster Marketplace and Ticketmaster Back-End make up Ticketmaster's Primary Ticketing Services business.</P>
                    <P>CC. “Ticketmaster Marketplace” means all products, services, features, and capabilities of Ticketmaster that are not part of Ticketmaster Back-End, including Ticketmaster's technology and distribution platform used to market and sell primary tickets to Live Entertainment Events to consumers.</P>
                    <P>DD. “Venue” means any building or physical space located in the United States that hosts Live Entertainment Events and any owner, operator, or manager of that building or physical space.</P>
                    <HD SOURCE="HD1">III. Applicability</HD>
                    <P>This Final Judgment applies to Live Nation and Ticketmaster, as defined above, and all other Persons in active concert or participation with any Defendant who receive actual notice of this Final Judgment.</P>
                    <HD SOURCE="HD1">IV. Ticketing</HD>
                    <P>A. Ticketmaster must develop and provide an open distribution and ticket authentication system that enables any Major Concert Venue using Ticketmaster Back-End to distribute primary tickets using any Eligible Primary Ticketing Services Provider(s) chosen by such Major Concert Venue. Such open distribution and ticket authentication system must have Ticketmaster remain responsible for the various functions that constitute the Ticketmaster Back-End. Such system must permit Eligible Primary Ticketing Services Providers to be sufficiently integrated into the Ticketmaster Back-End so that, once a Major Concert Venue has allocated tickets to an Eligible Primary Ticketing Services Provider, such Eligible Primary Ticketing Services Provider is able to utilize its own technologies to assume the customary responsibilities of a merchant of record, both before and after a Major Concert Venue has allocated tickets to it. The customary responsibilities of a merchant of record to be assumed by such Eligible Primary Ticketing Services Provider include the following:</P>
                    <P>1. storing and supporting discovery for event listings and providing details thereof;</P>
                    <P>2. ingesting event and allocated inventory data;</P>
                    <P>3. configuring the event and allocated seats in such Eligible Primary Ticketing Services Provider's own systems and/or ingesting such information from another Primary Ticketing Services provider for the Venue;</P>
                    <P>4. listing allocated tickets in Primary Marketplace(s), managing checkout flows and payment processing, maintaining related order records and customer accounts or sessions, and processing refunds, cancellations, exchanges, chargebacks, and taxes;</P>
                    <P>5. sales reporting and settlement;</P>
                    <P>6. requesting, receiving, and rendering barcodes/tokens issued by Ticketmaster Back-End;</P>
                    <P>7. supporting refunds, cancellations, exchanges, transfer/resale features, and fan support; and</P>
                    <P>8. collecting and (as appropriate) remitting ticket sales proceeds to the Promoter and/or Venue concerned.</P>
                    <P>B. The open distribution and ticket authentication system required by Section IV.A must:</P>
                    <P>1. facilitate the automated transfer of tickets/ticket barcodes for all primary tickets sold using third-party Primary Marketplaces and may not, in connection with any transfer and/or re-sale of tickets purchased through third-party Primary Marketplaces, require ticket purchasers to pay any additional fees or otherwise take materially burdensome or unnecessary additional actions, such as use of a Ticketmaster website, app, or account (provided that Ticketmaster may require Eligible Primary Ticketing Services Providers to pay fees in connection with such transfer and/or re-sale intended to cover the costs of Ticketmaster Back-End, as verified by the monitor);</P>
                    <P>2. be fully operational, implemented, and made available as a standalone product to Major Concert Venues within 275 days of entry of this Final Judgment (the “Ticketing Transition Deadline”); and</P>
                    <P>3. be maintained by Ticketmaster such that it addresses any reasonable deficiencies identified by Defendants, Major Concert Venues, third-party Primary Marketplaces, the monitor, or the United States as necessary to accomplish the purposes of this Final Judgment.</P>
                    <P>
                        C. Ticketmaster must timely publish and update any documentation or other information necessary for Major Concert Venues or Eligible Primary Ticketing Services Providers to utilize the system described in Section IV.A.
                        <PRTPAGE P="41391"/>
                    </P>
                    <P>D. Ticketmaster must not use any contractual, pricing, technological, or other means to restrict Major Concert Venues' choice of Eligible Primary Ticketing Services Providers. Ticketmaster must allow Major Concert Venues to choose to use (1) solely Ticketmaster Back-End (and not any other product or service offered by Defendants, including Ticketmaster Marketplace) or (2) multiple Primary Ticketing Back-End systems.</P>
                    <P>E. Ticketmaster is not required to integrate with any third-party marketplace that is not an Eligible Primary Ticketing Services Provider. Should Ticketmaster believe that a Major Concert Venue has asked it to integrate with a third-party marketplace that is not an Eligible Primary Ticketing Services Provider, it must immediately inform the monitor, who will promptly determine whether the third-party marketplace is an Eligible Primary Ticketing Services Provider. The monitor's determination as to whether the third-party marketplace is or is not an Eligible Primary Ticketing Services Provider will be conclusive, subject to an application by the United States to the Court for a determination that the third-party marketplace is an Eligible Primary Ticketing Services Provider.</P>
                    <P>F. Ticketmaster must not use any Client Ticketing Data collected via Ticketmaster Back-End from the transfer of tickets on third-party Primary Marketplaces for any purpose, other than in connection with the performance of services by Ticketmaster Back-End.</P>
                    <P>G. For all Primary Ticketing Services contracts between Ticketmaster and a Major Concert Venue in effect as of the date of the entry of this Final Judgment, any and all contract terms that renew the contract or extend its term automatically are hereby waived and unenforceable. Ticketmaster must provide written notice of this provision to every Major Concert Venue to which it applies, in a form to be approved by the United States in its sole discretion, within 30 calendar days of entry of this Final Judgment. The United States may, in its sole discretion, grant Defendants additional time.</P>
                    <P>H. No later than the Ticketing Transition Deadline, Ticketmaster must waive any exclusive Primary Marketplace ticketing requirements of any contract then in effect between a Major Concert Venue and Ticketmaster to allow the Major Concert Venue to use the Primary Marketplace of any other Eligible Primary Ticketing Services Provider for one Live Entertainment Event per year during each year remaining in its contract with Ticketmaster. The Major Concert Venue has the sole discretion to choose the events. Ticketmaster may not seek payment from any Major Concert Venue in connection with the Major Concert Venue's exercise of this provision. Ticketmaster must provide notice of this provision to every Major Concert Venue to which it is applicable in a form to be approved by the United States in its sole discretion.</P>
                    <P>I. For any contract between Ticketmaster and any Major Concert Venue that, as of the entry of this Final Judgment, has at least four years remaining on its term (excluding any renewal or automatic extension terms that are waived in accordance with Section IV.G), Ticketmaster must, no later than the Ticketing Transition Deadline and on each one-year anniversary of the entry of the Final Judgment (until such point that fewer than four years remain on any such contract), provide that Venue the option to sell or distribute up to 20% of fee-bearing primary ticket inventory for Live Entertainment Events otherwise sellable by Ticketmaster through Eligible Primary Ticketing Services Providers for the remainder of the contract term, notwithstanding any exclusivity commitments made to Ticketmaster, provided that:</P>
                    <P>1. Ticketmaster may require the Venue to agree to a pro rata adjustment to any economic arrangements under such contract or related contract that were associated with exclusivity of Primary Ticketing Services. In the event of irreconcilable disagreements between Ticketmaster and a Venue as to whether particular economic arrangements were associated with exclusivity of Primary Ticketing Services, such dispute will be submitted to the monitor for resolution, and the monitor's resolution will be binding on Defendants. For the avoidance of doubt, such adjustments may be implemented through reductions or offsets to ongoing or future payments or consideration under the contract.</P>
                    <P>2. Any 20% allocation under this provision must be: (a) 20% of each section or tier, as determined by the Major Concert Venue equitably and in good faith; (b) 20% of Live Entertainment Events each year, with the events selected by the Major Concert Venue equitably and in good faith; or (c) a combination of (a) and (b) totaling up to 20% of fee-bearing primary ticket inventory for Live Entertainment Events otherwise sellable by Ticketmaster at the applicable Major Concert Venue in that year.</P>
                    <P>3. Ticketmaster must provide notice of this provision to every Major Concert Venue to which it applies in a form to be approved by the United States in its sole discretion.</P>
                    <P>J. Upon entry of this Final Judgment, for any Live Entertainment Event at any Amphitheater that Live Nation owns, operates, or controls: (1) the Venue must allow any Promoter or Artist contracting after such date to present a Live Entertainment Event in such Venue to sell and distribute up to 50% of the fee-bearing primary ticket inventory for each section or tier in the Venue through the Primary Marketplace of any Eligible Primary Ticketing Services Provider that the Promoter or Artist chooses, without Ticketmaster charging any Ticket Service Fees on such tickets when sold through third-party Eligible Primary Ticketing Services Providers; and (2) on tickets it sells, Ticketmaster must not charge Ticket Service Fees that exceed 15% of the ticket face value. Ticketmaster may require third-party ticketing services providers to pay fees in connection with the distribution of tickets under this Section intended to cover the costs of Ticketmaster Back-End, as verified by the monitor.</P>
                    <P>K. Upon entry of this Final Judgment, Ticketmaster must not negotiate nor enter into any Primary Ticketing Services contracts with a Major Concert Venue inconsistent with the following requirements:</P>
                    <P>1. If Ticketmaster negotiates a Primary Ticketing Services contract with a Major Concert Venue, Ticketmaster must offer such Major Concert Venue the option to choose a fully or partially non-exclusive contract under which all or a portion of the primary tickets (at the Major Concert Venue's election) are not exclusive to Ticketmaster. Such non-exclusive contracts may not use pricing schemes, pricing tiers, or other provisions that have the practical effect of Primary Ticketing Services exclusivity.</P>
                    <P>2. If Ticketmaster seeks to offer a fully exclusive contract, such contract may not have a term longer than four years. Any partial-exclusive contract with at least 20% of tickets not exclusive to Ticketmaster is not subject to the four-year maximum term applicable to fully exclusive agreements if (a) the Major Concert Venue, in writing, requests a longer term and/or (b) a competitor submits an offer for a longer term.</P>
                    <P>
                        3. Ticketmaster will provide notice and a copy of this Final Judgment, in a form to be proposed by Defendants and approved by the United States in its sole discretion, to every Major Concert Venue with whom Ticketmaster discusses or negotiates the provision of any Primary Ticketing Services at the beginning of any such negotiation. The notice will include an explanation of 
                        <PRTPAGE P="41392"/>
                        the requirements of Section IV of this Final Judgment, a statement encouraging the Major Concert Venue to contact the Department of Justice and the monitor if they are or become aware of any potential violations of this Final Judgment, and a statement waiving any contractual limitation on what the Major Concert Venue may disclose to the monitor or a government agency as well as any obligation to provide notice to Defendants about any such contacts.
                    </P>
                    <P>L. Primary Ticketing Services contracts entered into during the term of this Final Judgment between Ticketmaster and a Major Concert Venue (including any renewals or extensions of existing contracts) must not: (a) contain any auto-renewal provisions; or (b) condition any terms on a Venue forgoing a Request for Proposals (“RFP”) process or other competitive bidding process for Primary Ticketing Services.</P>
                    <HD SOURCE="HD1">V. Venue and Promotions</HD>
                    <P>A. Within 30 days of entry of this Final Judgment, unless the United States, in its sole discretion, grants Defendants additional time, Defendants must provide notice to the Venues listed in Table 1 (the “Divestiture Venues”), in a form approved by the United States in its sole discretion, that Defendants are required to, at the Divestiture Venues' election, do one of the following with respect to any and all contracts that relate to the provision of booking or promotion services and/or control or ownership interests at the Divestiture Venues: (1) terminate such contracts or (2) modify such existing contracts to bring them into compliance with all aspects of Section V.B.1 below on terms agreeable to Defendants and the Divestiture Venue. For avoidance of doubt, nothing herein prevents Defendants from terminating such contracts based on any doctrines excusing or discharging contractual obligations available at law or in equity.</P>
                    <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s150,r50,xs16">
                        <TTITLE>Table 1—Divestiture Venues</TTITLE>
                        <BOXHD>
                            <CHED H="1"> </CHED>
                            <CHED H="1"> </CHED>
                            <CHED H="1"> </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Wharf Amphitheater</ENT>
                            <ENT>Orange Beach</ENT>
                            <ENT>AL</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Walmart AMP</ENT>
                            <ENT>Rogers</ENT>
                            <ENT>AR</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Ford Idaho Center</ENT>
                            <ENT>Nampa</ENT>
                            <ENT>ID</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Maine Savings Amphitheater</ENT>
                            <ENT>Bangor</ENT>
                            <ENT>ME</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Pine Knob Music Theatre</ENT>
                            <ENT>Clarkston</ENT>
                            <ENT>MI</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Brandon Amphitheater</ENT>
                            <ENT>Brandon</ENT>
                            <ENT>MS</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Bethel Woods Center for the Arts</ENT>
                            <ENT>Bethel</ENT>
                            <ENT>NY</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Empower FCU Amphitheater at Lakeview</ENT>
                            <ENT>Syracuse</ENT>
                            <ENT>NY</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Riverbend Music Center</ENT>
                            <ENT>Cincinnati</ENT>
                            <ENT>OH</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Germania Insurance Amphitheater</ENT>
                            <ENT>Austin</ENT>
                            <ENT>TX</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Cynthia Woods Mitchell Pavilion</ENT>
                            <ENT>Woodlands</ENT>
                            <ENT>TX</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BMO Pavilion</ENT>
                            <ENT>Milwaukee</ENT>
                            <ENT>WI</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">American Family Insurance Amphitheater</ENT>
                            <ENT>Milwaukee</ENT>
                            <ENT>WI</ENT>
                        </ROW>
                    </GPOTABLE>
                    <P>B. Following termination or modification of all applicable rights under any and all contracts pursuant to Section V.A:</P>
                    <P>1. Defendants must not enter into any Preferred Booking Agreement with the Divestiture Venues, or otherwise acquire or exercise any form of ownership or control over the Divestiture Venues in any way (including control, but excluding administration without control, of the Divestiture Venues' booking calendar). For the avoidance of doubt, Defendants may not engage in Content Steering with respect to the Divestiture Venues.</P>
                    <P>2. The owner or operator of any Divestiture Venue will be free to conduct a new ticketing RFP. Any Primary Ticketing Services contract offered by Defendants must conform to the requirements set forth in Section IV.K.</P>
                    <P>C. Within 30 days of entry of this Final Judgment, at any Amphitheater owned, operated, or controlled by Defendants: (1) Defendants must abide by the Nondiscriminatory Calendar Procedures; (2) Defendants must not refuse an Artist access to such Amphitheater because the Artist has engaged a Promoter other than Defendants; and (3) Defendants must offer rental terms to Artists using a third-party Promoter for such Amphitheater that are, when taken as a whole and accounting for Venue-driven economic considerations (such as day of week, time of year, number of shows, popularity of the Artist, expected onsite revenue from concessions and VIP hospitality, historical performance of the Artist in similar Venues, etc.), at least as favorable as those offered to Artists that use Defendants as their Promoter for such Amphitheater to the extent Defendants control setting such terms at the Amphitheater.</P>
                    <P>D. Upon entry of this Final Judgment, Defendants must not enter into any Preferred Booking Agreement with a Major Concert Venue.</P>
                    <P>E. Within 30 days of entry of this Final Judgment, unless the United States, in its sole discretion, grants Defendants additional time, Defendants must provide notice, approved by the United States in its sole discretion, to all Major Concert Venues for which Defendants have a Preferred Booking Agreement that Defendants are required to, at the Venue's election, (1) terminate such Preferred Booking Agreement or (2) modify such Preferred Booking Agreement in a manner that renders the agreement no longer a Preferred Booking Agreement on terms agreeable to Defendants and the Venue.</P>
                    <P>F. Defendants' Nondiscriminatory Calendar Procedures must be implemented by Live Nation in good faith and set forth in Live Nation's official, published, generally applicable booking calendar management policies, and may be updated by Live Nation provided such updates are consistent with the foregoing principles and other requirements of this Final Judgment and provided to the monitor.</P>
                    <HD SOURCE="HD1">VI. Anti-Conditioning, Anti-Retaliation, Anti-Content Steering, and other Provisions Designed To Promote Competition</HD>
                    <P>A. Defendants must not:</P>
                    <P>1. Retaliate, in any way, against a Venue because it is known to Defendants that the Venue has contracted or is contemplating contracting with a company other than Defendants for Primary Ticketing Services;</P>
                    <P>
                        2. Condition or threaten to Condition (including via intermediaries) the provision of Live Entertainment Events to a Venue based on that Venue refraining from contracting with a company other than Defendants for Primary Ticketing Services;
                        <PRTPAGE P="41393"/>
                    </P>
                    <P>3. Condition or threaten to Condition the provision of Primary Ticketing Services to a Venue based on that Venue refraining from contracting with a company other than Defendants for the provision of Live Entertainment Events; or</P>
                    <P>4. Engage in Content Steering with respect to Venues.</P>
                    <P>B. For the avoidance of doubt, the prohibitions set forth in Section VI.A apply to the provision of one or more Live Entertainment Events at Venues. Defendants have waived any argument that the prohibitions set forth in Section VI.A only apply to all Live Entertainment Events at Venues. For clarity, Plaintiffs need not identify particular Live Entertainment Events that have been withheld in order to prevail on a claim of Retaliation.</P>
                    <P>C. Prior to opening or obtaining control over any Amphitheater, Defendants must report that fact to the monitor and state whether Defendants believe the Amphitheater is a Major Concert Venue.</P>
                    <P>D. Defendants must not (1) engage in any conduct materially the same as conduct prohibited by another Section of this Final Judgment or designed to evade any obligation imposed by this Final Judgment; or (2) engage in any conduct that evades or frustrates the purposes of this Final Judgment.</P>
                    <HD SOURCE="HD1">VII. Firewalls</HD>
                    <P>A. Defendants must implement and maintain effective procedures to prevent any Client Ticketing Data from being shared with, disclosed to, or accessible by any Firewall Employee, except as expressly permitted by this Section VII.</P>
                    <P>B. Defendants may disclose to a Firewall Employee only the Client Ticketing Data that concerns a specific event for which the Firewall Employee is involved in promotion or management of the Artist who will perform or did perform at the event, and only if Defendants do so on the same terms as generally provided to other Promoters or Artist managers not affiliated with Defendants. Defendants may disclose to an Exempted Employee only the Client Ticketing Data required for the Exempted Employee to perform his or her job function(s), provided, however, that such Exempted Employee may not use Client Ticketing Data to perform any job function(s) that primarily involve(s) the day-to-day operation or management of Defendants' businesses related to Venues, concert promotions, or Artist management services. Defendants may disclose Client Ticketing Data to any Defendant employee where so required by law, government regulation, legal process, or court order, so long as such disclosure is limited to fulfillment of that purpose.</P>
                    <P>C. Defendants must, within 30 calendar days of the entry of the Stipulation and Order, submit to the United States a compliance plan setting forth in detail the procedures Defendants propose to implement to effect compliance with this Section VII. The United States will inform Defendants within 15 business days of receipt whether, in its sole discretion, the United States approves or rejects Defendants' compliance plan. Within 15 business days of receiving a notice of rejection, Defendants must submit a revised compliance plan. The United States may request that the Court determine whether Defendants' proposed compliance plan fulfills the requirements of this Section VII.</P>
                    <P>D. At minimum, an effective compliance plan must include, for all Firewall Employees: (1) initial written notice followed by quarterly written reminders; (2) training within 30 days of the date the compliance plan is approved, followed by training on a yearly basis; and (3) provision of written acknowledgment of the obligations of this Section VII within 30 days of the date the compliance plan is approved, followed by acknowledgment on a yearly basis. The form of all written notifications must be approved by the United States in its sole discretion.</P>
                    <P>E. Defendants must maintain complete records of all written notices, training, employee acknowledgments, and all other efforts made to comply with this Section VII until one year after the expiration of this decree or any enforcement efforts or litigation brought by the United States or any Settling States that implicates this firewall, whichever is later.</P>
                    <HD SOURCE="HD1">VIII. Termination of Agreement with Oak View Group</HD>
                    <P>A. Within 30 calendar days after the Court's entry of the Stipulation and Order, Defendants must terminate the Ticketing Services Incentive Agreement with Oak View Group dated July 1, 2022 (“Oak View Agreement”).</P>
                    <P>B. Within 60 calendar days of entry of this Final Judgment, for any Venue managed by Oak View Group that entered into a contract with Defendants on or after July 1, 2022 (excluding, for clarity, Venues that are owned in whole or part by Oak View Group), Defendants must: (1) disclose the existence and nature of the Oak View Agreement and all payments made to Oak View Group associated with the Oak View Agreement, including the $20 million payment of July 2022; and (2) at the option of the Venue, allow the Venue to conduct a new RFP process for any contract between the Venue and Defendants, including for Primary Ticketing Services, without penalty. Defendants must provide notice to Venues of the disclosure required by VIII.B.1 and the option to conduct a new RFP process under VIII.B.2 in a form approved by the United States in its sole discretion.</P>
                    <P>C. To the extent Defendants are required under Section VIII.A to terminate rights to upfront payments or other financial considerations, nothing herein prevents Defendants from asserting any contract law or other claims or remedies to seek a pro rata adjustment to any ongoing or future payments or consideration to reflect the reduced scope of such rights or obligations.</P>
                    <P>D. Defendants must not enter into any agreement with a Major Concert Venue's agent (including a third-party facility manager or other agent with authority, influence, or involvement regarding decisions to enter into Primary Ticketing Services contracts) that compensates or rewards the agent for converting any of the Major Concert Venue's existing Primary Ticketing Services contracts into a new Primary Ticketing Services contract with Ticketmaster.</P>
                    <HD SOURCE="HD1">IX. Artist Transparency</HD>
                    <P>
                        A. Upon entry of this Final Judgment, at an Artist's request, Defendants must provide the Artist with all data and information in Defendants' possession, custody, or control about purchasers of tickets for Live Entertainment Events performed by that Artist sold by Ticketmaster (
                        <E T="03">e.g.,</E>
                         ticket purchasers, number of tickets sold, location or type of tickets sold, ticket prices, sales proceeds) for such Artist's sole interests, subject to any restrictions, prohibitions, obligations, or other requirements arising under privacy laws applicable to Defendants and any commitments to purchasers of tickets with respect to the use of their data (collectively, “Privacy Obligations”). Defendants must not modify their privacy policies and/or practices in a manner that circumvents or frustrates their obligation described in this Section IX.A. Defendants may provide this information subject to standard privacy protection and a non-disclosure agreement, subject to approval by the United States in its sole discretion. Such non-disclosure agreement will not restrict the Artist's use of this data more than necessary, in the United States' sole discretion, to comply with Defendant's Privacy Obligations and reasonably protect any competitively sensitive information 
                        <PRTPAGE P="41394"/>
                        belonging to Defendants, which includes not directly sharing such information with Defendants' competitors or transferring the rights to the information, including to data aggregators.
                    </P>
                    <P>B. Defendants must provide notice to all Artists for which it maintains data or information covered by Section IX.A, that the information and data described in Section IX.A is available to them upon request, subject to the limitations in Section IX.A. Such notice must be in a form acceptable to the United States in its sole discretion and must be transmitted to the Artist's manager, counsel, or representative (including of the estate of any deceased Artist).</P>
                    <HD SOURCE="HD1">X. Affidavits</HD>
                    <P>A. Within 30 calendar days of entry of this Final Judgment and every 60 calendar days thereafter until (1) the ticketing distribution enablement required by Section IV of this Final Judgment has been made available to Venues, and (2) the divestiture of the Divestiture Venues required by Section V of this Final Judgment is complete, Defendants must deliver to the United States an affidavit, signed by Live Nation's Chief Financial Officer and Executive Vice President for Corporate and Regulatory Affairs, that describes in reasonable detail all actions that Defendants have taken and all steps that Defendants have implemented to comply with Sections IV and V of this Final Judgment. The United States, in its sole discretion, may approve different signatories for the affidavits.</P>
                    <P>B. If a Defendant makes any changes to actions and steps described in affidavits provided pursuant to Section X.A, the Defendant must, within 15 calendar days after any change is implemented, deliver to the United States an affidavit describing those changes.</P>
                    <P>C. Defendants must keep all records of any efforts made to comply with Section IV until one year after the ticketing distribution enablement required by Section IV has been made available to Venues. Defendants must keep all records of any efforts made to comply with Section V until one year after the Venue divestitures required by Section V of this Final Judgment have been completed.</P>
                    <HD SOURCE="HD1">XI. Appointment of Monitor</HD>
                    <P>
                        A. Upon application of the United States, which Defendants may not oppose, the Court will appoint a monitor selected by the United States in its sole discretion, after consultation with the Settling States, and approved by the Court. The United States will select the same Person appointed by the Court as monitor pursuant to the Amended Final Judgment in 
                        <E T="03">United States</E>
                         v. 
                        <E T="03">Ticketmaster Entertainment Inc. and Live Nation Entertainment Inc.,</E>
                         No. 10-cv-139 (D.D.C.), unless that Person is unavailable or unable to accomplish the monitor's duties. If that Person is or becomes unavailable or unable to accomplish the monitor's duties, the United States will select and recommend a different monitor in its sole discretion, after consultation with the Settling States, for the Court's approval. Once approved, the court-appointed monitor should be considered by the United States and Defendants to be an arm and representative of the Court.
                    </P>
                    <P>B. The monitor will have the power and authority to monitor Defendants' compliance with the terms of this Final Judgment and the Stipulation and Order entered by the Court and will have other powers as the Court deems appropriate. The monitor will have no responsibility or obligation for the operation of Defendants' businesses. No attorney-client relationship will be formed between Defendants and the monitor.</P>
                    <P>C. The monitor will have the authority to take such steps as, in the judgment of the monitor and the United States, may be necessary to accomplish the monitor's responsibilities. The monitor may seek information from Defendants' personnel, including in-house counsel, compliance personnel, and internal auditors. The monitor may require Defendants to produce documents, to submit signed affidavits, and to make employees available to sit for interviews. The monitor may require that such interviews be conducted under oath in the format of a deposition with a court reporter. Defendants must establish a policy, annually communicated to all employees, that employees may disclose any information to the monitor without reprisal for such disclosure. Defendants must not punish or take any adverse action against any employee or third party for disclosing information to the monitor.</P>
                    <P>D. Defendants may not object to actions taken by the monitor in fulfillment of the monitor's responsibilities under any Order of the Court on any ground other than malfeasance by the monitor. Disagreements between the monitor and Defendants related to the scope of the monitor's responsibilities do not constitute malfeasance. Objections by Defendants must be conveyed in writing to the United States and the monitor within 20 calendar days of the monitor's action that gives rise to Defendants' objection, or the objection is waived.</P>
                    <P>E. The monitor will serve at the cost and expense of Defendants pursuant to a written agreement, on terms and conditions, including confidentiality requirements and conflict of interest certifications, approved by the United States in its sole discretion. If the monitor and Defendants are unable to reach such a written agreement within 14 calendar days of the Court's appointment of the monitor, or if the United States, in its sole discretion, declines to approve the proposed written agreement, the United States, in its sole discretion, may take appropriate action, including making a recommendation to the Court, which may set the terms and conditions for the monitor's work, including compensation, costs, and expenses.</P>
                    <P>F. The monitor may hire, at the cost and expense of Defendants, any agents and consultants, including investment bankers, attorneys, technical experts, and accountants, that are reasonably necessary in the monitor's judgment to assist with the monitor's duties. These agents or consultants will be directed by and solely accountable to the monitor and will serve on terms and conditions, including confidentiality requirements and conflict-of-interest certifications, approved by the United States in its sole discretion. Within three business days of hiring any agents or consultants, the monitor must provide written notice of the hiring and the rate of compensation to Defendants and the United States.</P>
                    <P>G. The compensation of the monitor and agents or consultants retained by the monitor must be on reasonable and customary terms commensurate with the individuals' experience and responsibilities.</P>
                    <P>H. The monitor must account for all costs and expenses incurred.</P>
                    <P>I. Defendants' failure to promptly pay the monitor's accounted-for costs and expenses, including for agents and consultants, will constitute a violation of this Final Judgment and may result in sanctions. If Defendants make a timely objection in writing to the United States to any part of the monitor's accounted-for costs and expenses, Defendants must establish an escrow account into which Defendants must pay the disputed costs and expenses until the dispute is resolved.</P>
                    <P>
                        J. Defendants must use best efforts to cooperate fully with the monitor and to assist the monitor in monitoring Defendants' compliance with their obligations under this Final Judgment and the Stipulation and Order. Subject to reasonable protection for trade secrets, other confidential research, 
                        <PRTPAGE P="41395"/>
                        development, or commercial information (
                        <E T="03">e.g.,</E>
                         through use of a non-disclosure or confidentiality agreement), or any applicable privileges (
                        <E T="03">e.g.,</E>
                         privilege log), Defendants must provide the monitor and agents or consultants retained by the monitor with full and complete access to all personnel (current and former), agents, consultants, books, records, and facilities.
                    </P>
                    <P>K. Any disputes between Defendants and the monitor with respect to reasonable protection for trade secrets, other confidential research, development, or commercial information, or any applicable privileges will be decided by the United States in its sole discretion. Defendants may not take any action to interfere with or to impede accomplishment of the monitor's responsibilities.</P>
                    <P>L. The monitor must investigate and report on Defendants' compliance with every provision of this Final Judgment and the Stipulation and Order, including by taking all actions necessary to monitor Defendants' compliance with the remedies set forth in Sections IV, V, and VI. The monitor must provide reports to the United States and Settling States, on a quarterly basis and as requested, setting forth Defendants' efforts to comply with their obligations under this Final Judgment and under the Stipulation and Order. In any proceeding in which the United States or a Settling State is a party, Defendants waive any argument that statements by the monitor are a public record or are statements of the United States or of any Settling State.</P>
                    <P>M. Within 30 calendar days after appointment of the monitor by the Court, and on a yearly basis thereafter, the monitor must provide to the United States and Defendants a proposed written work plan. Defendants may provide comments on the proposed written work plan to the United States and the monitor within 14 calendar days after receipt, after which the monitor must produce a final work plan to the United States and Defendants, for approval by the United States in its sole discretion. Any disputes between Defendants and the monitor with respect to any written work plan will be decided by the United States in its sole discretion. The United States retains the right, in its sole discretion, to move the Court to require changes or additions to a work plan at any time.</P>
                    <P>
                        N. The monitor may communicate 
                        <E T="03">ex parte</E>
                         with the Court when, in the monitor's judgment, such communication is reasonably necessary to the monitor's duties under this Final Judgment, including if Defendants fail to pay the monitor's costs and expenses in a timely manner or otherwise violate this Final Judgment.
                    </P>
                    <P>O. The monitor will serve until this Final Judgment expires.</P>
                    <P>P. If the United States determines that the monitor is not acting diligently or in a reasonably cost-effective manner, or if the monitor resigns or becomes unable to accomplish the monitor's duties, the United States may recommend that the Court appoint a substitute.</P>
                    <HD SOURCE="HD1">XII. Compliance Obligations</HD>
                    <P>
                        A. 
                        <E T="03">Antitrust Compliance Officer.</E>
                         Defendants must appoint an Antitrust Compliance Officer, who must be an internal employee or officer of Defendants, subject to the following responsibilities and obligations:
                    </P>
                    <P>1. Defendants must appoint an Antitrust Compliance Officer within 21 days of entry of this Final Judgment and must identify to the United States the Antitrust Compliance Officer's name, business address, telephone number, and email address. Within 45 days of a vacancy in the Antitrust Compliance Officer position, Defendants must appoint a replacement and must identify to the United States the replacement Antitrust Compliance Officer's name, business address, telephone number, and email address. In all events, Defendants' appointment of any Antitrust Compliance Officer is subject to the approval of the United States in its sole discretion.</P>
                    <P>2. The Antitrust Compliance Officer must be an active member in good standing of the bar in any U.S. jurisdiction and must have at least five years' experience in legal practice, including experience with antitrust, regulatory, or compliance matters.</P>
                    <P>3. The Antitrust Compliance Officer must, directly or through the employees or counsel working under the Antitrust Compliance Officer's authority and direction: (a) within 21 days after the Antitrust Compliance Officer's appointment, furnish to all of Defendants' Management and Relevant Employees a copy of this Final Judgment; (b) within 30 days after the Antitrust Compliance Officer's appointment, in a manner to be devised by Defendants and approved by the United States, provide Defendants' Management and Relevant Employees reasonable notice of the meaning and requirements of this Final Judgment.</P>
                    <P>4. Twice during the first year, then annually thereafter, the Antitrust Compliance Officer must brief Defendants' Management and Relevant Employees on the meaning and requirements of this Final Judgment, with written materials for each briefing to be approved by the United States in its sole discretion.</P>
                    <P>5. The Antitrust Compliance Officer must brief any person who becomes part of Management or a Relevant Employee within 60 days of such transition.</P>
                    <P>6. The Antitrust Compliance Officer must obtain from each Person designated as Management or a Relevant Employee, within 30 days of that Person's receipt of this Final Judgment, a certification that the Person (a) has read and understands and agrees to abide by the terms of this Final Judgment; (b) is not aware of any violation of this Final Judgment that has not been reported to Defendants; and (c) understands that failure to comply with this Final Judgment may result in an enforcement action for civil or criminal contempt of court.</P>
                    <P>7. The Antitrust Compliance Officer must communicate annually to Defendants' Management and Relevant Employees that they may disclose to the Antitrust Compliance Officer or monitor, without reprisal or adverse consequence for such disclosure, information concerning any violation or potential violation of this Final Judgment or the U.S. antitrust laws by Defendants.</P>
                    <P>
                        B. 
                        <E T="03">Reporting and Investigation Requirements.</E>
                         Upon Management or the Antitrust Compliance Officer learning of any violation or potential violation of any provision of this Final Judgment, Defendants must:
                    </P>
                    <P>1. promptly notify the monitor and take appropriate action to investigate, and in the event of a violation, terminate or modify the activity so as to comply with this Final Judgment;</P>
                    <P>2. within seven days, notify the United States of the violation or potential violation;</P>
                    <P>3. maintain all documents related to any violation or potential violation of this Final Judgment for a period of five years or the duration of this Final Judgment, whichever is longer;</P>
                    <P>4. maintain, and furnish to Plaintiffs upon request, a log of (a) all such documents for which Defendants claim protection under the attorney-client privilege or the attorney work product doctrine, and (b) all potential and actual violations, even if no documentary evidence regarding the violations exist;</P>
                    <P>
                        5. within thirty days, provide to the United States and the monitor a statement describing the violation or potential violation, which must include a description of any communications constituting the violation or potential violation, including the date and place of the communication, the Persons involved, and the subject matter of the communication, as well as a description 
                        <PRTPAGE P="41396"/>
                        of the steps taken to mitigate or remediate any violation or potential violation.
                    </P>
                    <P>C. Defendants must establish a whistleblower protection policy, which must provide that any employee may disclose, without reprisal or adverse consequence for such disclosure, to the Antitrust Compliance Officer or the monitor information concerning any violation or potential violation by the Defendants of this Final Judgment or the U.S. antitrust laws.</P>
                    <P>D. Defendants' CEO must certify in writing to the United States and the Settling States, 180 days after entry of this Final Judgment and thereafter annually on the anniversary date of the entry of this Final Judgment, that Defendants have complied with all provisions of this Final Judgment or that any violations or potential violations known to Management or the Antitrust Compliance Officer have been disclosed to the monitor and the United States.</P>
                    <P>E. Defendants must maintain and produce to the United States upon request: (1) a list identifying all employees having received the compliance training required under Sections XII.A.4 and XII.A.5 of this Final Judgment and the dates on which the employees received the training; and (2) copies of all materials distributed as part of the annual antitrust compliance training required under Sections XII.A.4 and XII.A.5 of this Final Judgment. For all materials requested to be produced pursuant to this Section for which Defendants claim protection under the attorney-client privilege or the attorney work product doctrine, Defendants must furnish to the United States a privilege log.</P>
                    <HD SOURCE="HD1">XIII. Compliance Inspection</HD>
                    <P>A. For the purposes of determining or securing compliance with this Final Judgment or related orders such as the Stipulation and Order, or for purposes of determining whether this Final Judgment should be modified or vacated, upon the written request of an authorized representative of the Assistant Attorney General for the Antitrust Division and reasonable notice to Defendants, Defendants must permit, from time to time and subject to legally recognized privileges, authorized representatives, including agents retained by the United States:</P>
                    <P>1. to have access during Defendants' business hours to inspect and copy, or at the option of the United States, to require Defendants to provide electronic copies (without redactions or limitations of any kind except for attorney-client privilege or attorney work product) of, all books, ledgers, accounts, records, data, and documents, wherever located, in the possession, custody, or control of Defendants relating to any matters contained in this Final Judgment; and</P>
                    <P>2. to interview, either informally or on the record, Defendants' officers, employees, or agents, wherever located, who may have their individual counsel present, relating to any matters contained in this Final Judgment. The interviews must be subject to the reasonable convenience of the interviewee and without restraint or interference by Defendants.</P>
                    <P>B. Upon the written request of an authorized representative of the Assistant Attorney General for the Antitrust Division, Defendants must submit written reports or respond to written interrogatories, under oath if requested, relating to any matters contained in this Final Judgment.</P>
                    <P>C. Each Settling State will have the same abilities provided by Sections XIII.A and XIII.B to investigate violations or potential violations involving a Venue or Live Entertainment Event located within 125 miles of that Settling State.</P>
                    <HD SOURCE="HD1">XIV. Notification</HD>
                    <P>A. Starting 60 days after entry of the Stipulation and Order, unless a transaction is otherwise subject to the reporting and waiting period requirements of the Hart-Scott-Rodino Antitrust Improvements Act of 1976, as amended, 15 U.S.C. 18a (the “HSR Act”), Defendants may not, without first providing at least 30 calendar days advance notification to the United States and each of the Settling States (an “Acquisition Notice”), directly or indirectly acquire all (or substantially all) of the assets located in the United States of, or any 20% or greater interest in, any Person engaged in providing ticketing services in the United States, any Promoter operating in the United States, and/or any Major Concert Venue located in the United States. Notwithstanding the foregoing, Defendants will not be required to provide to the United States or the Settling States any Acquisition Notice for: (1) acquisitions of additional interests in Persons in which Defendants already own a controlling interest; (2) acquisitions of real estate and ground and/or operating leases in connection with new Venue development projects; (3) the performance of purchase obligations that are included in existing contracts as of the entry of this Final Judgment; or (4) acquisitions of assets or interests in Persons located outside the United States that generated less than $15 million in annual revenue in the United States in each of the last two years.</P>
                    <P>B. Defendants must provide the notification required by this Section XIV in the same format as, and in accordance with the instructions relating to, the Notification and Report Form set forth in the Appendix to Part 803 of Title 16 of the Code of Federal Regulations, as amended, except Defendants will not be required to provide the information requested in the Additional Information section.</P>
                    <P>C. Notification must include, beyond the information required by the instructions, the names of the principal representatives who negotiated the transaction on behalf of each party, and all management or strategic plans discussing the proposed transaction. If, within the 30 calendar days following notification, representatives of the United States make a written request for additional information, Defendants may not consummate the proposed transaction until 20 calendar days after submitting all requested information.</P>
                    <P>D. Early termination of the waiting periods set forth in this Section may be requested and, where appropriate, granted in the same manner as is applicable under the requirements and provisions of the HSR Act and rules promulgated thereunder. This Section must be broadly construed, and any ambiguity or uncertainty relating to whether to file a notice under this Section must be resolved in favor of providing notice.</P>
                    <P>E. For any merger, acquisition, or other transaction that is subject to the HSR Act and is of a Person that engaged in providing ticketing services in the United States, is a Promoter in the United States, and/or owns, operates, or controls a Major Concert Venue in the United States, Defendants must provide a copy of the HSR notification to the United States and to each of the Settling States at the same time Defendants make their required notification under the HSR Act.</P>
                    <P>F. For purposes of this Final Judgment, any notice or other communication required to be provided to Plaintiffs will be sent to the Person at the address and emails set forth below (or such other addresses as a Plaintiff may specify in writing to Defendants):</P>
                    <FP SOURCE="FP-1">
                        <E T="03">United States</E>
                         David Teslicko, Financial Services, Fintech, and Banking Section, U.S. Department of Justice, Antitrust Division, 450 Fifth Street NW, Suite 4000, Washington, DC 20530, 
                        <E T="03">David.Teslicko@usdoj.gov</E>
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Arkansas</E>
                         Amanda Wentz, Senior Assistant Attorney General, Consumer Protection Division, Office of the 
                        <PRTPAGE P="41397"/>
                        Arkansas Attorney General, Bob R. Brooks Jr. Justice Building, 101 West Capitol Avenue, Little Rock, Arkansas 72201, 
                        <E T="03">amanda.wentz@arkansasag.gov</E>
                        , 
                        <E T="03">consumer@arkansasag.gov.</E>
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Iowa</E>
                         Noah Goerlitz, Assistant Attorney General, Office of the Iowa Attorney General 1305 E. Walnut St., Des Moines, IA 50319, 
                        <E T="03">noah.goerlitz@ag.iowa.gov</E>
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Mississippi</E>
                         Crystal Utley Secoy, Director &amp; Assistant Attorney General, Consumer Protection Division, Mississippi Attorney General's Office, Post Office Box 220, Jackson, Mississippi 39205, 
                        <E T="03">crystal.utley@ago.ms.gov.</E>
                    </FP>
                    <FP SOURCE="FP-1">
                        Lee Morris Special Assistant Attorney General, Consumer Protection Division, Mississippi Attorney General's Office, Post Office Box 220, Jackson, Mississippi 39205, 
                        <E T="03">Lee.Morris@ago.ms.gov</E>
                    </FP>
                    <FP SOURCE="FP-1">
                        Nebraska Justin C. McCully, Assistant Attorney General, Consumer Protection Bureau, Office of the Nebraska Attorney General, 1445 K St. Rm. 2115, Lincoln, Nebraska 68508, 
                        <E T="03">Justin.mccully@nebraska.gov.</E>
                    </FP>
                    <FP SOURCE="FP-1">
                        Oklahoma Cameron Capps OBA No. 32742, Deputy Attorney General, Consumer Protection, Office of the Oklahoma Attorney General, 313 NE 21st Street, Oklahoma City, Oklahoma 73105, Telephone: (405) 522-0858, Fax: (405) 522-0085, 
                        <E T="03">Cameron.Capps@oag.ok.gov.</E>
                    </FP>
                    <FP SOURCE="FP-1">
                        South Dakota Jacob R. Dempsey, Assistant Attorney General, South Dakota Office of Attorney General, 1302 East SD Highway 1889, Suite 1 Pierre SD, 57501, 605-773-4425 (Direct Line), 
                        <E T="03">Jacob.Dempsey@state.sd.us.</E>
                    </FP>
                    <HD SOURCE="HD1">XV. No Reacquisition</HD>
                    <P>During the term of this Final Judgment, Defendants may not acquire or reacquire any part of, any interest in, or any form of control over any Divestiture Venue (including any control over event booking at any Divestiture Venue) without prior written authorization of the United States; provided, however, that this Section XV will not prohibit Defendants from booking or administering the calendar for Live Entertainment Events at such Divestiture Venues so long as control over event booking at such Divestiture Venue is not held by Defendants.</P>
                    <HD SOURCE="HD1">XVI. Public Disclosure</HD>
                    <P>A. No information or documents obtained pursuant to any provision in this Final Judgment, including reports the monitor provides to the United States or any Settling States pursuant to Section XI.L and any notifications or other information provided pursuant to Section XIV, may be divulged by the United States or by any Settling State to any person other than an authorized representative of the executive branch of the United States or an authorized representative of the Settling States, except in the course of legal proceedings to which the United States or a Settling State is a party, including grand-jury proceedings, for the purpose of securing compliance with this Final Judgment, or as otherwise required by law.</P>
                    <P>B. In the event that the monitor receives a subpoena, court order, or other court process seeking or requiring production of information or documents obtained pursuant to any provision in this Final Judgment, including reports the monitor provides to the United States or any Settling States pursuant to Section XI.L or any notifications or other information provided pursuant to Section XIV, the monitor must notify the United States, Settling States, and Defendants immediately and prior to any disclosure, so that any of the parties may address such potential disclosure and, if necessary, pursue alternative legal remedies, including if deemed appropriate by Defendants, intervention in the relevant proceedings.</P>
                    <P>
                        C. In the event of a request by a third party, pursuant to the Freedom of Information Act, 5 U.S.C. 552, or similar state disclosure laws for disclosure of information obtained pursuant to any provision of this Final Judgment, the United States will act in accordance with that statute and the Department of Justice regulations at 28 CFR part 16, including the provision on confidential commercial information at 28 CFR 16.7, and the Settling States will act in accordance with their applicable disclosure laws. Defendants submitting information to the Antitrust Division should designate the confidential commercial information portions of all applicable documents and information under 28 CFR 16.7. Designations of confidentiality expire 10 years after submission, “unless the submitter requests and provides justification for a longer designation period.” 
                        <E T="03">See</E>
                         28 CFR 16.7(b).
                    </P>
                    <P>D. If at the time that Defendants furnish information or documents to the United States and Settling States pursuant to any provision of this Final Judgment, Defendants represent and identify in writing information or documents for which a claim of protection may be asserted under Rule 26(c)(1)(G) of the Federal Rules of Civil Procedure, and Defendants mark each pertinent page of such material, “Subject to claim of protection under Rule 26(c)(1)(G) of the Federal Rules of Civil Procedure,” the United States and the Settling States must give Defendants 10 calendar days' notice before divulging the material in any legal proceeding (other than a grand jury proceeding).</P>
                    <HD SOURCE="HD1">XVII. Retention of Jurisdiction</HD>
                    <P>The Court retains jurisdiction to enable any party to this Final Judgment to apply to the Court at any time for further orders and directions as may be necessary or appropriate to carry out or construe this Final Judgment, to modify any of its provisions, to enforce compliance, and to punish violations of its provisions.</P>
                    <HD SOURCE="HD1">XVIII. Enforcement of Final Judgment</HD>
                    <P>A. If at any time during the term of this Final Judgment, the United States or any Settling State determines in its sole discretion that Defendants have violated this Final Judgment, then the United States may re-open this proceeding to seek additional relief. Such additional relief may be ordered by this Court upon a finding by a preponderance of the evidence that this Final Judgment did not redress the violations alleged in the Amended Complaint and restore competition.</P>
                    <P>B. The United States and each Settling State retains and reserves all rights to enforce the provisions of this Final Judgment, including the right to seek an order of contempt from the Court. In a civil contempt action, a motion to show cause, or a similar action brought by the United States or any Settling State relating to an alleged violation of this Final Judgment, the United States or any Settling State may establish a violation of this Final Judgment and the appropriateness of a remedy therefor by a preponderance of the evidence, and Defendants waive any argument that a different standard of proof should apply.</P>
                    <P>
                        C. This Final Judgment should be interpreted to give full effect to the procompetitive purposes of the antitrust laws and to restore the competition the Amended Complaint alleges was harmed by the challenged conduct. Defendants may be held in contempt of, and the Court may enforce, any provision of this Final Judgment that, as interpreted by the Court in light of these procompetitive principles and applying ordinary tools of interpretation, is stated specifically and in reasonable detail, whether or not it is clear and unambiguous on its face. In any such interpretation, the terms of this Final Judgment should not be construed against either party as the drafter.
                        <PRTPAGE P="41398"/>
                    </P>
                    <P>D. In an enforcement proceeding in which the Court finds that Defendants have violated this Final Judgment, the United States, together with any Settling States, may apply to the Court for an extension of this Final Judgment, together with other relief that may be appropriate. In connection with a successful effort by the United States or any Settling State to enforce this Final Judgment against a Defendant, whether litigated or resolved before litigation, that Defendant must reimburse the United States, and any Settling State that brought or joined said enforcement proceeding, for the fees and expenses of its attorneys, as well as all other costs including experts' fees, incurred in connection with that effort to enforce this Final Judgment, including in connection with the investigation of the potential violation.</P>
                    <P>E. For violations involving Major Concert Venues, Defendants will pay a penalty of $5,000,000 per violation of this Final Judgment, payable to the United States of America. For the avoidance of doubt, for conduct in violation of Section VI, multiple threats to Condition content directed to the same Venue during the same contracting cycle would amount to a single violation, but any of the following will amount to independent violations: acts directed toward different Venues; acts occurring in different contracting cycles; conduct concerning different Artists.</P>
                    <P>F. For a period of four years following the expiration of this Final Judgment, if the United States has evidence that Defendants violated this Final Judgment before it expired, the United States may file an action against Defendants in this Court requesting that the Court order: (1) Defendants to comply with the terms of this Final Judgment for an additional term of at least four years following the filing of the enforcement action; (2) all appropriate contempt remedies; (3) additional relief needed to ensure the Defendants comply with the terms of this Final Judgment; and (4) fees or expenses as called for by this Section XVIII.</P>
                    <HD SOURCE="HD1">XIX. State-Specific Provisions</HD>
                    <P>
                        A. Defendants must pay to the Settling States the corresponding amounts set forth in the table below (“Settlement Payments”). These payments are to resolve claims for monetary relief and/or civil penalties alleged in the Amended Complaint by certain states, including but not limited to claims brought by states in their 
                        <E T="03">parens patriae</E>
                         capacities on behalf of natural persons in their respective states. Notice and claims administration costs, taxes, any award of attorneys' fees and expenses to such states, or other payments authorized by the Court directly related to consumer redress in such states, must also be paid by the Defendants and will not thereby reduce any Settling State's Settlement Payment. More specifically, Defendants agree to make the following payments to the following Settling States:
                    </P>
                    <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s50,14">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1">State</CHED>
                            <CHED H="1">Amount</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Arkansas</ENT>
                            <ENT>$3,548,637.22</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Iowa</ENT>
                            <ENT>$3,000,000.00</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Mississippi</ENT>
                            <ENT>$2,780,037.76</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Nebraska</ENT>
                            <ENT>$3,588,759.96</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Oklahoma</ENT>
                            <ENT>$4,967,661.87</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">South Dakota</ENT>
                            <ENT>$677,920.00</ENT>
                        </ROW>
                    </GPOTABLE>
                    <P>B. In consideration of the monetary provisions and commitments contained in Section XIX.A, to the extent allowable by law and as of the date this Final Judgment is entered by the Court, the Settling States agree to fully, finally, and forever release Defendants from all claims that were expressly stated in the Amended Complaint.</P>
                    <P>C. The Settlement Payment may be used for any one or more of the following purposes, by the Settling States as they, in their sole discretion, see fit:</P>
                    <P>1. For payment of attorneys' fees and expenses, including, without limitation, reimbursement of grants received;</P>
                    <P>2. For the enforcement of antitrust or consumer protection law;</P>
                    <P>
                        3. For deposit into a state antitrust or consumer protection account (
                        <E T="03">e.g.,</E>
                         revolving account, trust account), for use in accordance with the state laws governing that account;
                    </P>
                    <P>4. For deposit into a fund exclusively dedicated to assisting state attorneys general enforce the antitrust and consumer protection laws by defraying the costs of (a) experts, economists, and consultants in multistate antitrust investigations and litigation, (b) training or continuing education in antitrust for attorneys in state attorney general offices, or (c) information management systems used in multistate antitrust investigations and litigation; or</P>
                    <P>5. For any other purpose as the Attorney General of each Settling State deems appropriate and consistent with or required by, the various states' laws.</P>
                    <HD SOURCE="HD1">XX. Expiration of Final Judgment</HD>
                    <P>Unless the Court grants an extension, this Final Judgment will expire on the date that is eight years from the date of its entry. Notwithstanding the foregoing or anything to the contrary in this Final Judgment, upon the closing of a sale or divestiture by Live Nation Entertainment, Inc. of the Ticketmaster business or substantially all of the assets thereof, Sections VI.A, VI.B, and VII will be deemed to have expired, while all other provisions will continue in full force and effect.</P>
                    <HD SOURCE="HD1">XXI. Reservation of Rights</HD>
                    <P>This Final Judgment terminates only the claims by the United States and the Settling States expressly stated in the Amended Complaint against Defendants and does not affect other charges or claims the United States or Settling States have filed or may file. The United States and the Settling States retain all rights to investigate and prosecute, under all applicable laws, any federal, state, or local claims against Defendants, whether civil or criminal, other than the claims expressly stated in the Amended Complaint. The claims of State Plaintiffs that are not Settling States are unaffected by this Final Judgment.</P>
                    <HD SOURCE="HD1">XXII. Public Interest Determination</HD>
                    <P>The parties have complied with the requirements of the Antitrust Procedures and Penalties Act, 15 U.S.C. 16, including by making available to the public copies of this Final Judgment and the Competitive Impact Statement, public comments thereon, and any response to comments by the United States. Based upon the record before the Court, which includes the Competitive Impact Statement and, if applicable, any comments and response to comments filed with the Court, entry of this Final Judgment is in the public interest.</P>
                    <EXTRACT>
                        <P>Date: _</P>
                        <FP>[Court approval subject to procedures of Antitrust Procedures and Penalties Act, 15 U.S.C. 16]</FP>
                        <FP SOURCE="FP-DASH"/>
                        <FP>Hon. Arun Subramanian</FP>
                        <FP>United States District Judge</FP>
                    </EXTRACT>
                    <HD SOURCE="HD1">Schedule A</HD>
                    <HD SOURCE="HD2">Excluded Entities</HD>
                    <P>1. Roc Nation LLC, and all of its subsidiaries.</P>
                    <P>2. VEEPS Inc., and all of its subsidiaries.</P>
                    <HD SOURCE="HD1">
                        Schedule B
                        <PRTPAGE P="41399"/>
                    </HD>
                    <GPOTABLE COLS="4" OPTS="L2,nj,i1" CDEF="s100,r50,xs30,r50">
                        <TTITLE>Initial List of Major Concert Venues</TTITLE>
                        <BOXHD>
                            <CHED H="1">Venue name</CHED>
                            <CHED H="1">City</CHED>
                            <CHED H="1">State</CHED>
                            <CHED H="1">Venue type</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">ALPINE VALLEY MUSIC THEATRE</ENT>
                            <ENT>EAST TROY</ENT>
                            <ENT>WI</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">AMERICAN FAMILY INSURANCE AMPHITHEATER</ENT>
                            <ENT>MILWAUKEE</ENT>
                            <ENT>WI</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">AMERIS BANK AMPHITHEATRE</ENT>
                            <ENT>ALPHARETTA</ENT>
                            <ENT>GA</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">ARTPARK OUTDOOR AMPHITHEATER</ENT>
                            <ENT>LEWISTON</ENT>
                            <ENT>NY</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">ATRIUM HEALTH AMPHITHEATER</ENT>
                            <ENT>MACON</ENT>
                            <ENT>GA</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">AZURA AMPHITHEATER</ENT>
                            <ENT>BONNER SPRINGS</ENT>
                            <ENT>KS</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BACK WATERS STAGE</ENT>
                            <ENT>DUBUQUE</ENT>
                            <ENT>IA</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BANKNH PAVILION</ENT>
                            <ENT>GILFORD</ENT>
                            <ENT>NH</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BANKPLUS AMPHITHEATER AT SNOWDEN GROVE</ENT>
                            <ENT>SOUTHAVEN</ENT>
                            <ENT>MS</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BETHEL WOODS CENTER FOR THE ARTS</ENT>
                            <ENT>BETHEL</ENT>
                            <ENT>NY</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BLACK OAK MOUNTAIN AMPHITHEATER</ENT>
                            <ENT>LAMPE</ENT>
                            <ENT>MO</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BLOSSOM MUSIC CENTER</ENT>
                            <ENT>CUYAHOGA FALLS</ENT>
                            <ENT>OH</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BMO PAVILION</ENT>
                            <ENT>MILWAUKEE</ENT>
                            <ENT>WI</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BRANDON AMPHITHEATER</ENT>
                            <ENT>BRANDON</ENT>
                            <ENT>MS</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">CASCADES AMPHITHEATER</ENT>
                            <ENT>RIDGEFIELD</ENT>
                            <ENT>WA</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">CCNB AMPHITHEATRE AT HERITAGE PARK</ENT>
                            <ENT>SIMPSONVILLE</ENT>
                            <ENT>SC</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">COASTAL CREDIT UNION MUSIC PARK</ENT>
                            <ENT>RALEIGH</ENT>
                            <ENT>NC</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">CONCRETE STREET AMPHITHEATER</ENT>
                            <ENT>CORPUS CHRISTI</ENT>
                            <ENT>TX</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">CONSTELLATION BRANDS MARVIN SANDS PERFORMING ARTS CENTER (CMAC)</ENT>
                            <ENT>CANANDAIGUA</ENT>
                            <ENT>NY</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">CREDIT ONE STADIUM</ENT>
                            <ENT>CHARLESTON</ENT>
                            <ENT>SC</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">CREDIT UNION 1 AMPHITHEATRE</ENT>
                            <ENT>TINLEY PARK</ENT>
                            <ENT>IL</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">CYNTHIA WOODS MITCHELL PAVILION</ENT>
                            <ENT>THE WOODLANDS</ENT>
                            <ENT>TX</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">DARIEN LAKE AMPHITHEATER</ENT>
                            <ENT>DARIEN CENTER</ENT>
                            <ENT>NY</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">DOS EQUIS PAVILION</ENT>
                            <ENT>DALLAS</ENT>
                            <ENT>TX</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">EMPOWER FCU AMPHITHEATER AT LAKEVIEW</ENT>
                            <ENT>SYRACUSE</ENT>
                            <ENT>NY</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">FIDDLER'S GREEN AMPHITHEATRE</ENT>
                            <ENT>GREENWOOD VILLAGE</ENT>
                            <ENT>CO</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">FIVEPOINT AMPHITHEATRE</ENT>
                            <ENT>IRVINE</ENT>
                            <ENT>CA</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">FORD AMPHITHEATER</ENT>
                            <ENT>COLORADO SPRINGS</ENT>
                            <ENT>CO</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">FORD IDAHO CENTER AMPHITHEATER</ENT>
                            <ENT>NAMPA</ENT>
                            <ENT>ID</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">FOREST HILLS STADIUM</ENT>
                            <ENT>NEW YORK</ENT>
                            <ENT>NY</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">FPL SOLAR AMPHITHEATER AT BAYFRONT PARK</ENT>
                            <ENT>MIAMI</ENT>
                            <ENT>FL</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">FREEDOM MORTGAGE PAVILION</ENT>
                            <ENT>CAMDEN</ENT>
                            <ENT>NJ</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">FROST AMPHITHEATER</ENT>
                            <ENT>STANFORD</ENT>
                            <ENT>CA</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">GERMANIA INSURANCE AMPHITHEATER</ENT>
                            <ENT>AUSTIN</ENT>
                            <ENT>TX</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">GLEN HELEN AMPHITHEATER</ENT>
                            <ENT>SAN BERNARDINO</ENT>
                            <ENT>CA</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">GORGE AMPHITHEATRE</ENT>
                            <ENT>QUINCY</ENT>
                            <ENT>WA</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">HAYDEN HOMES AMPHITHEATER</ENT>
                            <ENT>BEND</ENT>
                            <ENT>OR</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">HERSHEYPARK STADIUM</ENT>
                            <ENT>HERSHEY</ENT>
                            <ENT>PA</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">HOLLYWOOD BOWL</ENT>
                            <ENT>LOS ANGELES</ENT>
                            <ENT>CA</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">HOLLYWOOD CASINO AMPHITHEATRE</ENT>
                            <ENT>MARYLAND HEIGHTS</ENT>
                            <ENT>MO</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">HUNTINGTON BANK PAVILION AT NORTHERLY ISLAND</ENT>
                            <ENT>CHICAGO</ENT>
                            <ENT>IL</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">ISLETA AMPHITHEATER</ENT>
                            <ENT>ALBUQUERQUE</ENT>
                            <ENT>NM</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">ITHINK FINANCIAL AMPHITHEATRE</ENT>
                            <ENT>WEST PALM BEACH</ENT>
                            <ENT>FL</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">JIFFY LUBE LIVE</ENT>
                            <ENT>BRISTOW</ENT>
                            <ENT>VA</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">LAKE TAHOE OUTDOOR ARENA</ENT>
                            <ENT>STATELINE</ENT>
                            <ENT>NV</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">LAKEWOOD AMPHITHEATER</ENT>
                            <ENT>ATLANTA</ENT>
                            <ENT>GA</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">LAURIDSEN AMPHITHEATER</ENT>
                            <ENT>DES MOINES</ENT>
                            <ENT>IA</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">MAINE SAVINGS AMPHITHEATER</ENT>
                            <ENT>BANGOR</ENT>
                            <ENT>ME</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">MAINE SAVINGS PAVILION AT ROCK ROW</ENT>
                            <ENT>WESTBROOK</ENT>
                            <ENT>ME</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">MERCEDES-BENZ AMPHITHEATER</ENT>
                            <ENT>TUSCALOOSA</ENT>
                            <ENT>AL</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">MERRIWEATHER POST PAVILION</ENT>
                            <ENT>COLUMBIA</ENT>
                            <ENT>MD</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">MIDFLORIDA CREDIT UNION AMPHITHEATRE</ENT>
                            <ENT>TAMPA</ENT>
                            <ENT>FL</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">NORTH ISLAND CREDIT UNION AMPHITHEATRE</ENT>
                            <ENT>CHULA VISTA</ENT>
                            <ENT>CA</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">NORTHWELL AT JONES BEACH THEATER</ENT>
                            <ENT>WANTAGH</ENT>
                            <ENT>NY</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">OAK MOUNTAIN AMPHITHEATRE</ENT>
                            <ENT>PELHAM</ENT>
                            <ENT>AL</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">OZARKS AMPHITHEATER</ENT>
                            <ENT>CAMDENTON</ENT>
                            <ENT>MO</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PACIFIC AMPHITHEATRE</ENT>
                            <ENT>COSTA MESA</ENT>
                            <ENT>CA</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PINE KNOB MUSIC THEATRE</ENT>
                            <ENT>CLARKSTON</ENT>
                            <ENT>MI</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PNC BANK ARTS CENTER</ENT>
                            <ENT>HOLMDEL</ENT>
                            <ENT>NJ</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PNC MUSIC PAVILION</ENT>
                            <ENT>CHARLOTTE</ENT>
                            <ENT>NC</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">RED ROCKS AMPHITHEATRE</ENT>
                            <ENT>MORRISON</ENT>
                            <ENT>CO</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">RIVERBEND MUSIC CENTER</ENT>
                            <ENT>CINCINNATI</ENT>
                            <ENT>OH</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">RUOFF MUSIC CENTER</ENT>
                            <ENT>NOBLESVILLE</ENT>
                            <ENT>IN</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">SARATOGA PERFORMING ARTS CENTER</ENT>
                            <ENT>SARATOGA SPRINGS</ENT>
                            <ENT>NY</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">SHORELINE AMPHITHEATRE</ENT>
                            <ENT>MOUNTAIN VIEW</ENT>
                            <ENT>CA</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">TALKING STICK RESORT AMPHITHEATRE</ENT>
                            <ENT>PHOENIX</ENT>
                            <ENT>AZ</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">TD PAVILION AT THE MANN</ENT>
                            <ENT>PHILADELPHIA</ENT>
                            <ENT>PA</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">THE BAYCARE SOUND</ENT>
                            <ENT>CLEARWATER</ENT>
                            <ENT>FL</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">THE MILL TERRE HAUTE</ENT>
                            <ENT>TERRE HAUTE</ENT>
                            <ENT>IN</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">THE ORION AMPHITHEATER</ENT>
                            <ENT>HUNTSVILLE</ENT>
                            <ENT>AL</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">THE PAVILION AT MONTAGE MOUNTAIN</ENT>
                            <ENT>SCRANTON</ENT>
                            <ENT>PA</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="41400"/>
                            <ENT I="01">THE PAVILION AT STAR LAKE</ENT>
                            <ENT>BURGETTSTOWN</ENT>
                            <ENT>PA</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">THE PAVILION AT TOYOTA MUSIC FACTORY</ENT>
                            <ENT>IRVING</ENT>
                            <ENT>TX</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">THE RADY SHELL AT JACOBS PARK</ENT>
                            <ENT>SAN DIEGO</ENT>
                            <ENT>CA</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">THE SOUND AMPHITHEATER</ENT>
                            <ENT>GAUTIER</ENT>
                            <ENT>MS</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">THE WALMART AMP</ENT>
                            <ENT>ROGERS</ENT>
                            <ENT>AR</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">THE WHARF AMPHITHEATER</ENT>
                            <ENT>ORANGE BEACH</ENT>
                            <ENT>AL</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">THE XFINITY CENTER</ENT>
                            <ENT>MANSFIELD</ENT>
                            <ENT>MA</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">TOM MOFFATT WAIKIKI SHELL</ENT>
                            <ENT>HONOLULU</ENT>
                            <ENT>HI</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">TOYOTA AMPHITHEATRE</ENT>
                            <ENT>WHEATLAND</ENT>
                            <ENT>CA</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">TOYOTA PAVILION AT CONCORD</ENT>
                            <ENT>CONCORD</ENT>
                            <ENT>CA</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">UTAH FIRST CREDIT UNION AMPHITHEATRE</ENT>
                            <ENT>WEST VALLEY CITY</ENT>
                            <ENT>UT</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">VETERANS UNITED HOME LOANS AMPHITHEATER</ENT>
                            <ENT>VIRGINIA BEACH</ENT>
                            <ENT>VA</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">WESTVILLE MUSIC BOWL</ENT>
                            <ENT>NEW HAVEN</ENT>
                            <ENT>CT</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">WHITE RIVER AMPHITHEATRE</ENT>
                            <ENT>AUBURN</ENT>
                            <ENT>WA</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">WILLIAM RANDOLPH HEARST GREEK THEATRE</ENT>
                            <ENT>BERKELEY</ENT>
                            <ENT>CA</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">XFINITY THEATRE</ENT>
                            <ENT>HARTFORD</ENT>
                            <ENT>CT</ENT>
                            <ENT>AMPHITHEATER</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">ACRISURE ARENA</ENT>
                            <ENT>THOUSAND PALMS</ENT>
                            <ENT>CA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">ADDITION FINANCIAL ARENA</ENT>
                            <ENT>ORLANDO</ENT>
                            <ENT>FL</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">ALERUS CENTER</ENT>
                            <ENT>GRAND FORKS</ENT>
                            <ENT>ND</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">ALLEN COUNTY WAR MEMORIAL COLISEUM</ENT>
                            <ENT>FORT WAYNE</ENT>
                            <ENT>IN</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">ALLIANT ENERGY POWERHOUSE</ENT>
                            <ENT>CEDAR RAPIDS</ENT>
                            <ENT>IA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">ALLSTATE ARENA</ENT>
                            <ENT>ROSEMONT</ENT>
                            <ENT>IL</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">AMALIE ARENA</ENT>
                            <ENT>TAMPA</ENT>
                            <ENT>FL</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">AMERANT BANK ARENA</ENT>
                            <ENT>SUNRISE</ENT>
                            <ENT>FL</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">AMERICAN AIRLINES CENTER</ENT>
                            <ENT>DALLAS</ENT>
                            <ENT>TX</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">AMERICAN BANK CENTER</ENT>
                            <ENT>CORPUS CHRISTI</ENT>
                            <ENT>TX</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">AMICA MUTUAL PAVILION</ENT>
                            <ENT>PROVIDENCE</ENT>
                            <ENT>RI</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">ANGEL OF THE WINDS ARENA</ENT>
                            <ENT>EVERETT</ENT>
                            <ENT>WA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BALL ARENA</ENT>
                            <ENT>DENVER</ENT>
                            <ENT>CO</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BARCLAYS CENTER</ENT>
                            <ENT>NEW YORK</ENT>
                            <ENT>NY</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BERT OGDEN ARENA</ENT>
                            <ENT>EDINBURG</ENT>
                            <ENT>TX</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BILL GRAHAM CIVIC AUDITORIUM</ENT>
                            <ENT>SAN FRANCISCO</ENT>
                            <ENT>CA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BLUE CROSS ARENA</ENT>
                            <ENT>ROCHESTER</ENT>
                            <ENT>NY</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BMO HARRIS BRADLEY CENTER</ENT>
                            <ENT>MILWAUKEE</ENT>
                            <ENT>WI</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BOJANGLES COLISEUM</ENT>
                            <ENT>CHARLOTTE</ENT>
                            <ENT>NC</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BOK CENTER</ENT>
                            <ENT>TULSA</ENT>
                            <ENT>OK</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BON SECOURS WELLNESS ARENA</ENT>
                            <ENT>GREENVILLE</ENT>
                            <ENT>SC</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BRIDGESTONE ARENA</ENT>
                            <ENT>NASHVILLE</ENT>
                            <ENT>TN</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BROADMOOR WORLD ARENA</ENT>
                            <ENT>COLORADO SPRINGS</ENT>
                            <ENT>CO</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BROOKSHIRE GROCERY ARENA</ENT>
                            <ENT>BOSSIER CITY</ENT>
                            <ENT>LA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BRYCE JORDAN CENTER</ENT>
                            <ENT>STATE COLLEGE</ENT>
                            <ENT>PA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">CADENCE BANK ARENA</ENT>
                            <ENT>TUPELO</ENT>
                            <ENT>MS</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">CAJUNDOME</ENT>
                            <ENT>LAFAYETTE</ENT>
                            <ENT>LA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">CAPITAL ONE ARENA</ENT>
                            <ENT>WASHINGTON</ENT>
                            <ENT>DC</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">CFG BANK ARENA</ENT>
                            <ENT>BALTIMORE</ENT>
                            <ENT>MD</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">CHAIFETZ ARENA</ENT>
                            <ENT>ST LOUIS</ENT>
                            <ENT>MO</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">CHARLESTON COLISEUM &amp; CONVENTION CENTER</ENT>
                            <ENT>CHARLESTON</ENT>
                            <ENT>WV</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">CHARTWAY ARENA</ENT>
                            <ENT>NORFOLK</ENT>
                            <ENT>VA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">CHASE CENTER</ENT>
                            <ENT>SAN FRANCISCO</ENT>
                            <ENT>CA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">CHI HEALTH CENTER OMAHA</ENT>
                            <ENT>OMAHA</ENT>
                            <ENT>NE</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">CLIMATE PLEDGE ARENA</ENT>
                            <ENT>SEATTLE</ENT>
                            <ENT>WA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">COLISEO DE PUERTO RICO JOSÉ MIGUEL AGRELOT</ENT>
                            <ENT>SAN JUAN</ENT>
                            <ENT>PR</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">COLONIAL LIFE ARENA</ENT>
                            <ENT>COLUMBIA</ENT>
                            <ENT>SC</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">COLUMBUS CIVIC CENTER</ENT>
                            <ENT>COLUMBUS</ENT>
                            <ENT>GA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">CREDIT UNION 1 ARENA</ENT>
                            <ENT>CHICAGO</ENT>
                            <ENT>IL</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">CROSS INSURANCE ARENA</ENT>
                            <ENT>PORTLAND</ENT>
                            <ENT>ME</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">CROSS INSURANCE CENTER</ENT>
                            <ENT>BANGOR</ENT>
                            <ENT>ME</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">CRYPTO.COM ARENA</ENT>
                            <ENT>LOS ANGELES</ENT>
                            <ENT>CA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">DCU CENTER</ENT>
                            <ENT>WORCESTER</ENT>
                            <ENT>MA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">DELTA CENTER</ENT>
                            <ENT>SALT LAKE CITY</ENT>
                            <ENT>UT</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">DENNY SANFORD PREMIER CENTER</ENT>
                            <ENT>SIOUX FALLS</ENT>
                            <ENT>SD</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">DESERT DIAMOND ARENA</ENT>
                            <ENT>GLENDALE</ENT>
                            <ENT>AZ</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">DICKIES ARENA</ENT>
                            <ENT>FORT WORTH</ENT>
                            <ENT>TX</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">DIGNITY HEALTH ARENA</ENT>
                            <ENT>BAKERSFIELD</ENT>
                            <ENT>CA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">DON HASKINS CENTER</ENT>
                            <ENT>EL PASO</ENT>
                            <ENT>TX</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">DONALD L. TUCKER CIVIC CENTER</ENT>
                            <ENT>TALLAHASSEE</ENT>
                            <ENT>FL</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">EAGLEBANK ARENA</ENT>
                            <ENT>FAIRFAX</ENT>
                            <ENT>VA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">ENMARKET ARENA</ENT>
                            <ENT>SAVANNAH</ENT>
                            <ENT>GA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">ENTERPRISE CENTER</ENT>
                            <ENT>ST LOUIS</ENT>
                            <ENT>MO</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">EXTRAMILE ARENA</ENT>
                            <ENT>BOISE</ENT>
                            <ENT>ID</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">FAMILY ARENA</ENT>
                            <ENT>ST CHARLES</ENT>
                            <ENT>MO</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">FEDEXFORUM</ENT>
                            <ENT>MEMPHIS</ENT>
                            <ENT>TN</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="41401"/>
                            <ENT I="01">FIRST HORIZON COLISEUM</ENT>
                            <ENT>GREENSBORO</ENT>
                            <ENT>NC</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">FIRST INTERSTATE ARENA</ENT>
                            <ENT>BILLINGS</ENT>
                            <ENT>MT</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">FISERV FORUM</ENT>
                            <ENT>MILWAUKEE</ENT>
                            <ENT>WI</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">FORD CENTER</ENT>
                            <ENT>EVANSVILLE</ENT>
                            <ENT>IN</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">FORD IDAHO CENTER ARENA</ENT>
                            <ENT>NAMPA</ENT>
                            <ENT>ID</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">FRANK ERWIN CENTER</ENT>
                            <ENT>AUSTIN</ENT>
                            <ENT>TX</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">FREEMAN COLISEUM</ENT>
                            <ENT>SAN ANTONIO</ENT>
                            <ENT>TX</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">FROST BANK CENTER</ENT>
                            <ENT>SAN ANTONIO</ENT>
                            <ENT>TX</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">GAINBRIDGE FIELDHOUSE</ENT>
                            <ENT>INDIANAPOLIS</ENT>
                            <ENT>IN</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">GAS SOUTH ARENA</ENT>
                            <ENT>DULUTH</ENT>
                            <ENT>GA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">GIANT CENTER</ENT>
                            <ENT>HERSHEY</ENT>
                            <ENT>PA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">GOLDEN 1 CENTER</ENT>
                            <ENT>SACRAMENTO</ENT>
                            <ENT>CA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">GREAT SOUTHERN BANK ARENA</ENT>
                            <ENT>SPRINGFIELD</ENT>
                            <ENT>MO</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">H-E-B CENTER AT CEDAR PARK</ENT>
                            <ENT>CEDAR PARK</ENT>
                            <ENT>TX</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">HAMPTON COLISEUM</ENT>
                            <ENT>HAMPTON</ENT>
                            <ENT>VA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">HERITAGE BANK CENTER</ENT>
                            <ENT>CINCINNATI</ENT>
                            <ENT>OH</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">HERTZ ARENA</ENT>
                            <ENT>ESTERO</ENT>
                            <ENT>FL</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">HONDA CENTER</ENT>
                            <ENT>ANAHEIM</ENT>
                            <ENT>CA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">HUNTINGTON CENTER</ENT>
                            <ENT>TOLEDO</ENT>
                            <ENT>OH</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">INTRUST BANK ARENA</ENT>
                            <ENT>WICHITA</ENT>
                            <ENT>KS</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">INTUIT DOME</ENT>
                            <ENT>INGLEWOOD</ENT>
                            <ENT>CA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">JIM WHELAN BOARDWALK HALL</ENT>
                            <ENT>ATLANTIC CITY</ENT>
                            <ENT>NJ</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">JOE LOUIS ARENA</ENT>
                            <ENT>DETROIT</ENT>
                            <ENT>MI</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">JOHN PAUL JONES ARENA</ENT>
                            <ENT>CHARLOTTESVILLE</ENT>
                            <ENT>VA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">KASEYA CENTER</ENT>
                            <ENT>MIAMI</ENT>
                            <ENT>FL</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">KEYBANK CENTER</ENT>
                            <ENT>BUFFALO</ENT>
                            <ENT>NY</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">KFC YUM! CENTER</ENT>
                            <ENT>LOUISVILLE</ENT>
                            <ENT>KY</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">KIA CENTER</ENT>
                            <ENT>ORLANDO</ENT>
                            <ENT>FL</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">LA CROSSE CENTER</ENT>
                            <ENT>LA CROSSE</ENT>
                            <ENT>WI</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">LANDERS CENTER</ENT>
                            <ENT>SOUTHAVEN</ENT>
                            <ENT>MS</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">LEGACY ARENA</ENT>
                            <ENT>BIRMINGHAM</ENT>
                            <ENT>AL</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">LENOVO CENTER</ENT>
                            <ENT>RALEIGH</ENT>
                            <ENT>NC</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">LITTLE CAESARS ARENA</ENT>
                            <ENT>DETROIT</ENT>
                            <ENT>MI</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">MABEE CENTER</ENT>
                            <ENT>TULSA</ENT>
                            <ENT>OK</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">MADISON SQUARE GARDEN</ENT>
                            <ENT>NEW YORK</ENT>
                            <ENT>NY</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">MASSMUTUAL CENTER</ENT>
                            <ENT>SPRINGFIELD</ENT>
                            <ENT>MA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">MAVERIK CENTER</ENT>
                            <ENT>WEST VALLEY CITY</ENT>
                            <ENT>UT</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">MGM GRAND GARDEN ARENA</ENT>
                            <ENT>LAS VEGAS</ENT>
                            <ENT>NV</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">MICHELOB ULTRA ARENA</ENT>
                            <ENT>LAS VEGAS</ENT>
                            <ENT>NV</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">MISSISSIPPI COAST COLISEUM</ENT>
                            <ENT>BILOXI</ENT>
                            <ENT>MS</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">MISSISSIPPI COLISEUM</ENT>
                            <ENT>JACKSON</ENT>
                            <ENT>MS</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">MODA CENTER</ENT>
                            <ENT>PORTLAND</ENT>
                            <ENT>OR</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">MOHEGAN ARENA AT CASEY PLAZA</ENT>
                            <ENT>WILKES BARRE</ENT>
                            <ENT>PA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">MOHEGAN SUN ARENA</ENT>
                            <ENT>UNCASVILLE</ENT>
                            <ENT>CT</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">MOODY CENTER</ENT>
                            <ENT>AUSTIN</ENT>
                            <ENT>TX</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">MVP ARENA</ENT>
                            <ENT>ALBANY</ENT>
                            <ENT>NY</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">NASHVILLE MUNICIPAL AUDITORIUM</ENT>
                            <ENT>NASHVILLE</ENT>
                            <ENT>TN</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">NASSAU VETERANS MEMORIAL COLISEUM</ENT>
                            <ENT>UNIONDALE</ENT>
                            <ENT>NY</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">NATIONWIDE ARENA</ENT>
                            <ENT>COLUMBUS</ENT>
                            <ENT>OH</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">NEAL S BLAISDELL ARENA</ENT>
                            <ENT>HONOLULU</ENT>
                            <ENT>HI</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">NORTH CHARLESTON COLISEUM</ENT>
                            <ENT>NORTH CHARLESTON</ENT>
                            <ENT>SC</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">NRG ARENA</ENT>
                            <ENT>HOUSTON</ENT>
                            <ENT>TX</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">NUTTER CENTER</ENT>
                            <ENT>DAYTON</ENT>
                            <ENT>OH</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">OAKLAND ARENA</ENT>
                            <ENT>OAKLAND</ENT>
                            <ENT>CA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">ORLEANS ARENA</ENT>
                            <ENT>LAS VEGAS</ENT>
                            <ENT>NV</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PAYCOM CENTER</ENT>
                            <ENT>OKLAHOMA CITY</ENT>
                            <ENT>OK</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PECHANGA ARENA</ENT>
                            <ENT>SAN DIEGO</ENT>
                            <ENT>CA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PENSACOLA BAY CENTER</ENT>
                            <ENT>PENSACOLA</ENT>
                            <ENT>FL</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PEORIA CIVIC CENTER ARENA</ENT>
                            <ENT>PEORIA</ENT>
                            <ENT>IL</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PETERSEN EVENTS CENTER</ENT>
                            <ENT>PITTSBURGH</ENT>
                            <ENT>PA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PHX ARENA</ENT>
                            <ENT>PHOENIX</ENT>
                            <ENT>AZ</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PINNACLE BANK ARENA</ENT>
                            <ENT>LINCOLN</ENT>
                            <ENT>NE</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PPG PAINTS ARENA</ENT>
                            <ENT>PITTSBURGH</ENT>
                            <ENT>PA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PPL CENTER</ENT>
                            <ENT>ALLENTOWN</ENT>
                            <ENT>PA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PROPST ARENA</ENT>
                            <ENT>HUNTSVILLE</ENT>
                            <ENT>AL</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PRUDENTIAL CENTER</ENT>
                            <ENT>NEWARK</ENT>
                            <ENT>NJ</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">RAISING CANE'S RIVER CENTER ARENA</ENT>
                            <ENT>BATON ROUGE</ENT>
                            <ENT>LA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">RESCH CENTER</ENT>
                            <ENT>GREEN BAY</ENT>
                            <ENT>WI</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">RICHMOND COLISEUM</ENT>
                            <ENT>RICHMOND</ENT>
                            <ENT>VA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">ROCKET ARENA</ENT>
                            <ENT>CLEVELAND</ENT>
                            <ENT>OH</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">RUPP ARENA</ENT>
                            <ENT>LEXINGTON</ENT>
                            <ENT>KY</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">SAMES AUTO ARENA</ENT>
                            <ENT>LAREDO</ENT>
                            <ENT>TX</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="41402"/>
                            <ENT I="01">SAP CENTER AT SAN JOSE</ENT>
                            <ENT>SAN JOSE</ENT>
                            <ENT>CA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">SAVE MART CENTER</ENT>
                            <ENT>FRESNO</ENT>
                            <ENT>CA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">SCHOTTENSTEIN CENTER</ENT>
                            <ENT>COLUMBUS</ENT>
                            <ENT>OH</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">SIMMONS BANK ARENA</ENT>
                            <ENT>NORTH LITTLE ROCK</ENT>
                            <ENT>AR</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">SMOOTHIE KING CENTER</ENT>
                            <ENT>NEW ORLEANS</ENT>
                            <ENT>LA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">SNHU ARENA</ENT>
                            <ENT>MANCHESTER</ENT>
                            <ENT>NH</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">SPECTRUM CENTER</ENT>
                            <ENT>CHARLOTTE</ENT>
                            <ENT>NC</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">SPHERE</ENT>
                            <ENT>LAS VEGAS</ENT>
                            <ENT>NV</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">SPOKANE ARENA</ENT>
                            <ENT>SPOKANE</ENT>
                            <ENT>WA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">STATE FARM ARENA</ENT>
                            <ENT>ATLANTA</ENT>
                            <ENT>GA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">STATE FARM CENTER</ENT>
                            <ENT>CHAMPAIGN</ENT>
                            <ENT>IL</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">T-MOBILE ARENA</ENT>
                            <ENT>LAS VEGAS</ENT>
                            <ENT>NV</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">T-MOBILE CENTER</ENT>
                            <ENT>KANSAS CITY</ENT>
                            <ENT>MO</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">TACOMA DOME</ENT>
                            <ENT>TACOMA</ENT>
                            <ENT>WA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">TARGET CENTER</ENT>
                            <ENT>MINNEAPOLIS</ENT>
                            <ENT>MN</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">TD GARDEN</ENT>
                            <ENT>BOSTON</ENT>
                            <ENT>MA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">THE ARMORY</ENT>
                            <ENT>MINNEAPOLIS</ENT>
                            <ENT>MN</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">THE FORD WYOMING CENTER</ENT>
                            <ENT>CASPER</ENT>
                            <ENT>WY</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">THE KIA FORUM</ENT>
                            <ENT>INGLEWOOD</ENT>
                            <ENT>CA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">THE LIACOURAS CENTER</ENT>
                            <ENT>PHILADELPHIA</ENT>
                            <ENT>PA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">THE PALACE OF AUBURN HILLS</ENT>
                            <ENT>AUBURN HILLS</ENT>
                            <ENT>MI</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">THE SANTANDER ARENA</ENT>
                            <ENT>READING</ENT>
                            <ENT>PA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">THOMPSON-BOLING ARENA AT FOOD CITY CENTER</ENT>
                            <ENT>
                                KNO
                                <E T="0732">X</E>
                                VILLE
                            </ENT>
                            <ENT>TN</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">TOYOTA ARENA</ENT>
                            <ENT>ONTARIO</ENT>
                            <ENT>CA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">TOYOTA CENTER</ENT>
                            <ENT>HOUSTON</ENT>
                            <ENT>TX</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">UBS ARENA</ENT>
                            <ENT>ELMONT</ENT>
                            <ENT>NY</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">UNITED CENTER</ENT>
                            <ENT>CHICAGO</ENT>
                            <ENT>IL</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">UNITED SUPERMARKETS ARENA</ENT>
                            <ENT>LUBBOCK</ENT>
                            <ENT>TX</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">UNO LAKEFRONT ARENA</ENT>
                            <ENT>NEW ORLEANS</ENT>
                            <ENT>LA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">VAN ANDEL ARENA</ENT>
                            <ENT>GRAND RAPIDS</ENT>
                            <ENT>MI</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">VETERANS MEMORIAL COLISEUM</ENT>
                            <ENT>PORTLAND</ENT>
                            <ENT>OR</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">VETERANS MEMORIAL COLISEUM</ENT>
                            <ENT>MADISON</ENT>
                            <ENT>WI</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">VIBRANT ARENA AT THE MARK</ENT>
                            <ENT>MOLINE</ENT>
                            <ENT>IL</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">VIEJAS ARENA</ENT>
                            <ENT>SAN DIEGO</ENT>
                            <ENT>CA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">VYSTAR VETERANS MEMORIAL ARENA</ENT>
                            <ENT>JACKSONVILLE</ENT>
                            <ENT>FL</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">WELLS FARGO ARENA</ENT>
                            <ENT>DES MOINES</ENT>
                            <ENT>IA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">WELLS FARGO CENTER</ENT>
                            <ENT>PHILADELPHIA</ENT>
                            <ENT>PA</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">WINTRUST ARENA</ENT>
                            <ENT>CHICAGO</ENT>
                            <ENT>IL</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">WOLSTEIN CENTER</ENT>
                            <ENT>CLEVELAND</ENT>
                            <ENT>OH</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">XCEL ENERGY CENTER</ENT>
                            <ENT>ST PAUL</ENT>
                            <ENT>MN</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">XL CENTER</ENT>
                            <ENT>HARTFORD</ENT>
                            <ENT>CT</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">YUENGLING CENTER</ENT>
                            <ENT>TAMPA</ENT>
                            <ENT>FL</ENT>
                            <ENT>ARENA</ENT>
                        </ROW>
                    </GPOTABLE>
                    <HD SOURCE="HD1">United States District Court Southern District of New York</HD>
                    <EXTRACT>
                        <FP SOURCE="FP-1">
                            <E T="03">United States of America, et al.,</E>
                             Plaintiffs, v. 
                            <E T="03">Live Nation Entertainment, Inc.</E>
                             and 
                            <E T="03">Ticketmaster L.L.C.</E>
                            , Defendants.
                        </FP>
                        <FP>Case No. 1:24-cv-3973-AS</FP>
                    </EXTRACT>
                    <HD SOURCE="HD1">Competitive Impact Statement</HD>
                    <P>
                        In accordance with the Antitrust Procedures and Penalties Act, 15 U.S.C. 16(b)-(h) (the “APPA” or “Tunney Act”), the United States of America 
                        <SU>1</SU>
                        <FTREF/>
                         files this Competitive Impact Statement related to its proposed Final Judgment filed in this civil antitrust proceeding.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             This Competitive Impact Statement addresses only the effects of the proposed Final Judgment on the claims brought by the United States. It does not address any effects of the proposed Final Judgement on the claims pursued by the Settling States or the State-Specific Provisions contained in Section XIX of the proposed Final Judgment.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">I. Nature and Purpose of the Proceeding</HD>
                    <P>On May 23, 2024, the United States and several States (collectively “Plaintiffs”) filed a civil antitrust complaint against Defendants Live Nation Entertainment, Inc. and Ticketmaster L.L.C. Plaintiffs subsequently filed an amended complaint (the “Complaint”) on August 30, 2024. The Complaint alleges Defendants violated Sections 1 and 2 of the Sherman Act, 15 U.S.C. 1-2, as well as several State laws by engaging in anticompetitive conduct in certain ticketing, promotions, and amphitheater markets.</P>
                    <P>On March 5, 2026, Defendants and the United States executed a term sheet (ECF No. 1171-1) memorializing the material terms of a settlement of the pending litigation. Subsequently, the States of Arkansas, Iowa, Mississippi, Nebraska, Oklahoma, and South Dakota (the “Settling States”) joined the settlement with additional terms applicable only to the Settling States. The United States and the Settling States have now filed a proposed Final Judgment and Stipulation and Order (“Stipulation and Order”) to which Defendants have agreed and that is designed to remedy the loss of competition alleged in the Complaint.</P>
                    <P>
                        Under the proposed Final Judgment, which is explained more fully below, Defendants are required to: (1) develop technology to allow Major Concert Venues 
                        <SU>2</SU>
                        <FTREF/>
                         utilizing Ticketmaster's back-end software to sell and distribute primary tickets through third-party marketplaces; (2) loosen exclusivity provisions in their existing primary ticketing contracts and abide by new restrictions on exclusive contracting for 
                        <PRTPAGE P="41403"/>
                        future ticketing contracts; (3) allow promoters and artists to use alternative sellers of tickets (“ticketers”) at Defendants' amphitheaters; (4) cap ticket service fees at Defendants' amphitheaters; (5) divest control over certain amphitheaters; (6) allow artists who choose to work with other promoters to perform at Defendants' amphitheaters; (7) waive exclusive and preferred booking rights at Major Concert Venues; (8) refrain from engaging in conditioning, retaliation, or content-steering that impairs competition; (9) maintain firewalls that limit disclosure of information between Ticketmaster and Live Nation; (10) terminate their ticketing agreement with the Oak View Group (“OVG”) and refrain from entering into similar agreements in the future; (11) share certain data with artists; and (12) notify the United States of certain future acquisitions. Additionally, the proposed Final Judgment provides for the appointment of a monitor to oversee Defendants' compliance, and it imposes substantial penalties and other consequences should Defendants violate these or other provisions of the Final Judgment in the future. The decree will last for eight years, unless the Court grants an extension.
                    </P>
                    <FTNT>
                        <P>
                            <SU>2</SU>
                             “Major Concert Venues” generally refers to arenas and amphitheaters with a seating capacity of 8,000 or more. 
                            <E T="03">See</E>
                             Proposed Final Judgment, ECF No. 1523-2, Paragraph II(N).
                        </P>
                    </FTNT>
                    <P>Under the terms of the Stipulation and Order, Defendants must comply with the proposed Final Judgment, including all timeframes specified in its provisions, pending entry by the Court or until the time for all appeals of any Court ruling declining entry of the proposed Final Judgment has expired. On June 15, 2026, the Court entered the Stipulation and Order.</P>
                    <P>The United States and Defendants have stipulated that the proposed Final Judgment may be entered after compliance with the APPA. Entry of the proposed Final Judgment will terminate this action with respect to the United States, except that the Court will retain jurisdiction to construe, modify, or enforce the provisions of the proposed Final Judgment and to punish violations thereof.</P>
                    <HD SOURCE="HD1">II. Description of Events Giving Rise to the Alleged Violations</HD>
                    <HD SOURCE="HD2">A. The Defendants and Their Anticompetitive Conduct</HD>
                    <P>
                        Defendants are the “largest live entertainment company in the world,” the “largest producer of live music concerts in the world,” and “the world's leading live entertainment ticketing sales and marketing company.” 
                        <SU>3</SU>
                        <FTREF/>
                         Live Nation Entertainment was formed in 2010 as a result of the merger between Live Nation and Ticketmaster. At that time, to resolve competitive concerns the United States alleged would result from the merger, Live Nation entered into the 2010 Final Judgment 
                        <SU>4</SU>
                        <FTREF/>
                         with the United States in which Live Nation agreed not to condition live entertainment content on a venue's use of Ticketmaster or retaliate against a venue that chose or considered a primary ticketing provider other than Ticketmaster, among other relief. In the years following the 2010 Final Judgment, Live Nation engaged in conduct that, in the United States' view, violated the 2010 Final Judgment. More specifically, the United States alleged that Live Nation had repeatedly conditioned and threatened to condition its provision of live entertainment content on a venue's using Ticketmaster's primary ticketing service. As a result, in 2020, Live Nation and the United States agreed to modify and extend the 2010 Final Judgment into what became the 2020 Amended Final Judgment.
                        <SU>5</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>3</SU>
                             Am. Compl. ¶ 16.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>4</SU>
                             
                            <E T="03">United States, et. al</E>
                             v. 
                            <E T="03">Ticketmaster Ent.,</E>
                             ECF No. 15, No. 10-cv-00139 (D.D.C. July 30, 2010).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>5</SU>
                             
                            <E T="03">United States, et. al</E>
                             v. 
                            <E T="03">Ticketmaster Ent.,</E>
                             ECF No. 29, No. 10-cv-00139 (D.D.C. Jan. 28, 2020).
                        </P>
                    </FTNT>
                    <P>As alleged in the Complaint, Defendants have maintained monopolies and/or restrained competition in certain markets for primary ticketing, promotion services for artists, promotion and booking services for venues, and the use of large amphitheaters through a wide range of anticompetitive acts. For example, Defendants entered into exclusive primary ticketing contracts with Major Concert Venues, threatened and/or retaliated against venues that chose to or considered working with competing ticketers, entered into exclusive and preferred booking agreements with venues, acquired venues and promoters, entered into an anticompetitive agreement with OVG related to ticketing, and tied artists' access to Defendants' amphitheaters to the use of Defendants' promotion services.</P>
                    <HD SOURCE="HD2">B. Industry Background</HD>
                    <P>
                        The performance of a concert requires multiple steps and multiple actors. First, the artist decides—often in consultation with the artist's representatives and potential promoters—where and when they want to perform. This decision is largely focused on the desired geographical areas and the type of venue (
                        <E T="03">e.g.,</E>
                         amphitheaters, arenas, etc.). Next, typically through an agent, the artist solicits offers from promoters who bid to promote a concert or tour. Promoting a concert generally involves taking on the financial risk of the show by guaranteeing an artist a set amount of money, marketing the show, negotiating with venues on behalf of the artist, and other logistical tasks.
                    </P>
                    <P>Some promoters enter into exclusive booking agreements with venues whereby if the artist wants to perform at a specific venue, then that artist must use the venue's exclusive promoter. Under an exclusive booking agreement, artists cannot benefit from competition that might otherwise occur between promoters who are competing to book concerts at that specific venue. Additionally, some promoters enter into preferred booking agreements with venues that provide the promoter with preferential rights to book dates or promote shows at a venue. Live Nation has numerous exclusive and preferred booking arrangements with Major Concert Venues, including large amphitheaters. Live Nation also owns and operates a significant number of large amphitheaters in the United States and serves as the exclusive booker of those venues. As such, Live Nation is typically the only promoter that promotes concerts in its owned and operated amphitheaters and in venues it does not own and operate but with which it has exclusive or preferred booking arrangements. Live Nation has acquired and leased amphitheaters across the country, sometimes even when Live Nation projected that it would incur a financial loss as a result of these decisions.</P>
                    <P>After the artist has chosen the venue and promoter, the next step is selling tickets to consumers. Ticketers include primary ticketers and secondary ticketers. Primary ticketers typically make their sales to consumers under a contract with a venue. Under an exclusive primary ticketing arrangement, the venue typically chooses the primary ticketing company. Under non-exclusive primary ticketing arrangements, promoters and artists may choose the primary ticketing company in conjunction with the venue.</P>
                    <P>
                        The event ticketing services that primary ticketers provide include two major types of services: (1) “back-end” services and (2) distribution (“marketplace”) services. First, the primary ticketing back-end is a collection of software, technology, and/or platform services used by venues to manage the inventory of tickets, generate barcodes, control and manage the entry of ticket holders into the venue, report data related to the event, and perform other similar functions related to managing the event. Second, 
                        <PRTPAGE P="41404"/>
                        the primary ticketing marketplace is a technology or distribution platform for making the initial distribution of tickets to the consumers who purchase them from the primary ticketers. After the initial sale of a ticket from a primary ticketer to a consumer (including fans, brokers, and other stakeholders), the purchaser typically can sell their tickets through secondary ticketing platforms. Artists and promoters generally do not receive revenue from secondary ticketing sales.
                    </P>
                    <HD SOURCE="HD2">C. The Competitive Effects of the Conduct</HD>
                    <P>Defendants' conduct had anticompetitive effects in the markets alleged in the Complaint. Defendants' anticompetitive acts distorted the competitive process, impeded competitors, deterred entry, reduced customer choice, increased prices, and reduced output.</P>
                    <P>For example, Defendants' exclusive ticketing agreements limited venues', artists', and fans' options with respect to primary ticketers and enabled Defendants to impose supra-competitive ticketing fees, borne by fans. Similarly, Defendants' threats to venues and their conditioning of live entertainment content on a venue's use of Ticketmaster impeded the ability of existing ticketing companies to compete and deterred or impeded entry by new or nascent rivals. Defendants also entered into a secret agreement with OVG that rewarded OVG for converting its venue clients' ticketing contracts to Ticketmaster, which subverted the competitive bidding process for those ticketing contracts.</P>
                    <P>With respect to artists, Defendants' policy of restricting artists' access to large amphitheaters unless those artists also used Defendants' promotions services distorted and reduced competition for promotion services and limited the shows performed at Defendants' venues. Similarly, Defendants used exclusive or preferred booking agreements with Major Concert Venues to impede competition by other promoters, to the detriment of artists, venues, and fans.</P>
                    <HD SOURCE="HD1">III. Explanation of the Proposed Final Judgment</HD>
                    <P>The relief required by the proposed Final Judgment will remedy the harm to competition alleged in the Complaint.</P>
                    <HD SOURCE="HD2">A. Ticketing Provisions</HD>
                    <P>Section IV of the proposed Final Judgment requires Defendants to develop, within 275 days, a new open distribution and ticket authentication technology to allow Major Concert Venues that use Ticketmaster's back-end system to sell and distribute primary tickets through eligible third-party primary ticketing marketplaces of the venue's choosing. Additionally, this section requires Defendants to modify certain existing ticketing agreements with venues to provide greater flexibility for venues to partner with third-party ticketing service providers, and it prohibits Defendants from engaging in certain exclusive ticketing practices in the future.</P>
                    <P>
                        More specifically, Paragraphs IV(A-D) of the proposed Final Judgment obligate Ticketmaster to develop and launch an open distribution and ticket authentication system that provides venues with a means to sell primary tickets through any eligible primary ticketing marketplace 
                        <SU>6</SU>
                        <FTREF/>
                         of the venue's choosing, without disadvantaging or encumbering any third-party marketplace. Specifically, Ticketmaster may not use any contractual, pricing, technological, or other means to restrict a Major Concert Venue's choice of primary ticketing service providers. Additionally, Ticketmaster must also facilitate the transfer and resale of tickets, regardless of the primary marketplace through which the ticket was initially purchased, without requiring the ticket purchaser to take any additional steps on the Ticketmaster website or pay any additional fees to Ticketmaster. Ticketmaster is limited to collecting from the third-party marketplace a transfer fee that covers Ticketmaster's cost of providing the back-end services necessary to facilitate the ticket transfer. These amounts will be verified by the monitor.
                    </P>
                    <FTNT>
                        <P>
                            <SU>6</SU>
                             An “Eligible Primary Ticketing Services Provider” is defined in Paragraph II(I) of the proposed Final Judgment. In general, a primary marketplace is eligible to receive a ticketing allocation under the new open distribution system if it (1) is engaged in the sale of primary tickets to live entertainment events in the United States through a primary marketplace as an established ongoing business or (2) can demonstrate the ability to fully provide primary ticketing services for Major Concert Venues by offering both a primary ticketing marketplace and a primary ticketing back-end technology. A ticketer that also operates a secondary ticketing marketplace remains qualified under (1) so long as it has reasonable policies and practices in place to limit speculative ticketing (
                            <E T="03">i.e.</E>
                             offering for sale tickets that the seller does not own, control, or have a contractual right to at the time of listing) and other ticketing practices that harm consumers and/or violate the directions of artists and venues. Any disputes as to whether a primary marketplace is eligible to receive a ticketing allocation will be resolved by the monitor, subject to a potential appeal by the United States to the Court.
                        </P>
                    </FTNT>
                    <P>
                        Ticketmaster also is required to address any reasonable deficiencies in this new system that are identified by venues, third-party marketplaces, the United States,
                        <SU>7</SU>
                        <FTREF/>
                         or the monitor. Once this new technology is launched, Ticketmaster must offer Ticketmaster's back-end software as a standalone product and allow venues to use it with any eligible primary ticketing marketplace(s) or other back-end systems of the venue's choosing, subject to the eligibility criteria noted above. These provisions collectively are designed to allow new and existing primary ticketing marketplaces to compete more effectively to sell and distribute primary tickets, regardless of whether a venue currently uses Ticketmaster or in the future chooses to use Ticketmaster's back-end system.
                    </P>
                    <FTNT>
                        <P>
                            <SU>7</SU>
                             Any interested person is invited to raise any identified deficiencies with the United States.
                        </P>
                    </FTNT>
                    <P>
                        Section IV also requires Defendants to modify certain existing Ticketmaster contracts and to follow new restrictions in future contracts. First, Defendants must waive any auto-renewal provisions and may not induce or penalize Major Concert Venues to forgo a Request for Proposal (“RFP”) when a ticketing contract is nearing expiration. Defendants also must waive exclusivity provisions in existing ticketing contracts with Major Concert Venues to allow those venues the opportunity to use, without penalty, alternative primary ticketing marketplaces for at least one event during each year remaining on their Ticketmaster contract. Additionally, Defendants must provide certain Major Concert Venues the option to sell or distribute up to 20% of primary tickets via eligible third-party primary marketplaces in exchange for a pro-rata adjustment to any amounts previously paid by Defendants to obtain primary ticketing exclusivity under the venue's existing primary ticketing contract. In future contract negotiations with Major Concert Venues, Defendants must offer fully and partially non-exclusive contracts under which all or a portion of the primary tickets (at the Major Concert Venue's election) are not exclusive to Ticketmaster. Ticketmaster may not use any pricing schemes, pricing tiers, or other contract provisions that have the practical effect of exclusivity for primary ticketing services. Finally, any fully exclusive primary ticketing agreements with Major Concert Venues are capped at four years. Partially-exclusive primary ticketing contracts may be longer than four years, but only if the venue specifically requests, in writing, a longer term or a competing ticketer submits an offer to that venue for a longer term. These provisions are designed to facilitate entry of new primary ticketing service providers and increase 
                        <PRTPAGE P="41405"/>
                        competition among existing ticketing service providers.
                    </P>
                    <P>The relief secured by Section IV will further improve competition by changing the structure of the primary ticketing markets at issue in the case. By separating the “back-end” and “marketplace” functions of primary ticketing, competitors will face lower barriers to entry. Competition among marketplaces can happen more dynamically because Major Concert Venues can use multiple marketplaces and can shift their usage more frequently than they change primary ticketing back-ends. Marketplaces can compete for ticketing sales without needing to compete to provide back-end services. Additionally, by empowering venues to use multiple ticketing marketplaces in a single concert season and/or for individual shows, Defendants' promotions business will have less incentive and ability to steer content away from venues that use rival ticketers.</P>
                    <P>
                        This section of the proposed Final Judgment has additional ticketing provisions designed specifically to foster ticketing competition at amphitheaters and ameliorate the harm to consumers stemming from Defendants' monopolies. Specifically, this section requires Defendants to allow any promoter or artist performing a show at a large amphitheater 
                        <SU>8</SU>
                        <FTREF/>
                         owned, operated, or controlled by Defendants to sell and distribute up to 50% of their tickets through an eligible third-party primary marketplace. Additionally, Defendants may not charge service fees in excess of 15% for any tickets sold via Ticketmaster for events at those amphitheaters.
                    </P>
                    <FTNT>
                        <P>
                            <SU>8</SU>
                             These provisions extend to large amphitheaters that qualify as a Major Concert Venue.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">B. Venue and Promotions Provisions</HD>
                    <P>Section V of the proposed Final Judgment requires Defendants to terminate or modify certain venue and promotions contracts with thirteen Divestiture Venues, which are large amphitheaters over which Defendants currently exercise control. Under the terms of the proposed Final Judgment, Defendants may no longer exert control over these venues and must allow the venues to conduct a new RFP process for ticketing services if they wish to do so. Moreover, Defendants may not engage in any form of content steering with respect to Divestiture Venues. At both these venues and other Major Concert Venues, Defendants may no longer enter into, and must either terminate or modify, any exclusive or preferred booking agreements. Additionally, Defendants must allow artists to rent large amphitheaters owned or controlled by Defendants regardless of which promoter artists select; Defendants must rent these venues on the same terms as other artists promoted by Defendants, accounting for the nature of the particular show. This section is designed to foster increased competition among promoters by allowing artists to partner with their promoter of choice without fear of being locked out of Major Concert Venues controlled by Live Nation where fans wish to see them perform.</P>
                    <HD SOURCE="HD2">C. Anti-Conditioning, Anti-Retaliation, and Anti-Steering</HD>
                    <P>Section VI of the proposed Final Judgment contains prohibitions against Defendants engaging in any form of conditioning, steering, or retaliation based on a venue's choice of or consideration of primary ticketer. This section specifically forbids Defendants from retaliating “in any way” against a venue because Defendants know or believe that venue is considering contracting with another primary ticketer. It also prohibits Defendants from steering artists to venues based on the identity of the primary ticketer or based on the ticketing revenues Defendants receive from events at a venue, while allowing Defendants to share truthful and non-misleading information about the capabilities of ticketers engaged by the venue. These provisions are designed to expand, clarify, and strengthen similar provisions contained in the 2020 Amended Final Judgment. Additionally, Paragraph VI(D) of the proposed Final Judgment bars Defendants from engaging in conduct that is materially the same as conduct prohibited by the proposed Final Judgment, conduct designed to evade any obligation imposed by the proposed Final Judgment, and conduct that evades or frustrates the purposes of the proposed Final Judgment.</P>
                    <P>These provisions are intended to foster increased competition for primary ticketing by prohibiting Defendants from using their monopoly power in artist promotion and venue booking markets to distort the competitive process or inhibit customer choice.</P>
                    <HD SOURCE="HD2">D. Firewalls</HD>
                    <P>Section VII of the proposed Final Judgment requires Defendants to maintain firewalls between their ticketing and promotions businesses, similar to those Defendants were required to implement pursuant to the 2020 Amended Final Judgment.</P>
                    <HD SOURCE="HD2">E. Oak View Group Agreement</HD>
                    <P>Section VIII of the proposed Final Judgment requires Defendants to terminate their 2022 ticketing agreement with Oak View Group (“OVG”), under which Defendants paid OVG millions of dollars to “advocate” to flip venues managed by OVG to use Ticketmaster rather than their existing primary ticketer. This section also requires Ticketmaster to allow affected venues to conduct a new ticketing RFP after being made aware of the terms of Defendants' agreement with OVG. Defendants are prohibited from entering into similar agreements with venue managers in the future.</P>
                    <HD SOURCE="HD2">F. Artist Transparency</HD>
                    <P>Section IX of the proposed Final Judgment requires Defendants to provide artists with ticketing data and information for those artists' shows, both retrospectively and on an ongoing basis. This provision is designed to allow artists to use that data to build their fan base and promote future shows, regardless of which promoters or ticketers they partner with going forward.</P>
                    <HD SOURCE="HD2">G. Reporting Obligations for Future Acquisitions</HD>
                    <P>
                        Section XIV of the proposed Final Judgment requires Defendants to notify the United States in advance of acquiring, directly or indirectly, in a transaction that would not otherwise be reportable under the Hart-Scott-Rodino Antitrust Improvements Act of 1976, as amended, 15 U.S.C. 18a (the “HSR Act”), any assets of or any 20% or greater interest in any entity related to ticketing, promotions services, or Major Concert Venues in the United States. Pursuant to the proposed Final Judgment, Defendants must notify the United States of such acquisitions as it would for a required HSR Act filing, as specified in the Appendix to Part 803 of Title 16 of the Code of Federal Regulations. The proposed Final Judgment further provides for waiting periods and opportunities for the United States to obtain additional information, analogous to the corresponding provisions of the HSR Act, before such acquisitions can be consummated. Requiring notification before Defendants' acquisition of an entity involved in ticketing, promotions services, or venues will permit the United States to assess the competitive effects of that acquisition before it is consummated and, if necessary, seek to enjoin the transaction.
                        <PRTPAGE P="41406"/>
                    </P>
                    <HD SOURCE="HD2">H. Monitor</HD>
                    <P>Section XI of the proposed Final Judgment provides that the United States may appoint a monitor who will have the power and authority to investigate and report on Defendants' compliance with the terms of the Final Judgment and the Stipulation and Order. These powers include the ability to require Defendants to produce documents, to submit signed affidavits, and to make employees available to sit for interviews, including interviews conducted under oath. The monitor will not have any responsibility or obligation for the operation of Defendants' businesses. The monitor will serve at Defendants' expense, on such terms and conditions as the United States approves, and Defendants must assist the monitor in fulfilling his or her obligations. The monitor will provide periodic reports to the United States and will serve until the Final Judgement expires.</P>
                    <HD SOURCE="HD2">I. Compliance and Inspection</HD>
                    <P>The proposed Final Judgment also contains provisions designed to promote compliance with and make enforcement of the Final Judgment as effective as possible.</P>
                    <P>Paragraph XVIII(A) allows the United States to re-open the case in the future if it believes that Defendants have violated the Final Judgment. If this occurs, the United States may seek additional relief by showing by a preponderance of the evidence that the Final Judgment did not redress the violations alleged in the Complaint and restore competition.</P>
                    <P>Paragraph XVIII(B) provides that the United States retains and reserves all rights to enforce the Final Judgment, including the right to seek an order of contempt from the Court. Under the terms of this section, Defendants have agreed that in any civil contempt action, any motion to show cause, or any similar action brought by the United States regarding an alleged violation of the Final Judgment, the United States may establish the violation and the appropriateness of any remedy by a preponderance of the evidence and that Defendants have waived any argument that a different standard of proof should apply. This provision aligns the standard for compliance with the Final Judgment with the standard of proof that applies to the underlying offenses that the Final Judgment addresses.</P>
                    <P>Paragraph XVIII(C) provides additional clarification regarding the interpretation of the provisions of the proposed Final Judgment. The proposed Final Judgment is intended to remedy the loss of competition the United States alleges in the Complaint occurred due to Defendants' conduct. Defendants agree that they will abide by the proposed Final Judgment and that they may be held in contempt of the Court for failing to comply with any provision of the proposed Final Judgment that is stated specifically and in reasonable detail, as interpreted in light of this procompetitive purpose.</P>
                    <P>Paragraph XVIII(D) provides that if the Court finds in an enforcement proceeding that a Defendant has violated the Final Judgment, the United States may apply to the Court for an extension of the Final Judgment, together with such other relief as may be appropriate. In addition, to compensate American taxpayers for any costs associated with investigating and enforcing violations of the Final Judgment, Paragraph XVIII(D) provides that, in any successful effort by the United States to enforce the Final Judgment against a Defendant, whether litigated or resolved before litigation, the Defendant must reimburse the United States for attorneys' fees, experts' fees, and other costs incurred in connection with that effort to enforce this Final Judgment, including the investigation of the potential violation.</P>
                    <P>Paragraph XVIII(E) requires Defendants to pay to the United States a penalty of $5,000,000 for each violation of the Final Judgment involving a Major Concert Venue. Acts directed toward different venues, acts occurring in different contracting cycles, and conduct concerning different artists each count as a separate violation of the Final Judgment.</P>
                    <P>Paragraph XVIII(F) states that the United States may file an action against a Defendant for violating the Final Judgment for up to four years after the Final Judgment has expired or been terminated. This provision is meant to address circumstances such as when evidence that a violation of the Final Judgment occurred during the term of the Final Judgment is discovered after the Final Judgment has expired or been terminated or when there is not sufficient time for the United States to complete an investigation of an alleged violation prior to expiration or termination of the Final Judgment. This provision, therefore, makes clear that, for four years after the Final Judgment has expired or been terminated, the United States may still challenge a violation that occurred during the term of the Final Judgment.</P>
                    <P>Finally, Section XX of the proposed Final Judgment provides that the Final Judgment will expire eight years from the date of its entry, except that certain provisions concerning conditioning and firewalls will expire earlier upon a sale or divestiture of Ticketmaster.</P>
                    <HD SOURCE="HD1">IV. Remedies Available To Potential Private Plaintiffs</HD>
                    <P>Section 4 of the Clayton Act, 15 U.S.C. 15, provides that any person who has been injured as a result of conduct prohibited by the antitrust laws may bring suit in federal court to recover three times the damages the person has suffered, as well as costs and reasonable attorneys' fees. Entry of the proposed Final Judgment as to the United States does not impair the bringing of any private antitrust damage action.</P>
                    <HD SOURCE="HD1">V. Procedures Available for Modificationof the Proposed Final Judgment</HD>
                    <P>The United States, Settling States, and Defendants have stipulated that the proposed Final Judgment may be entered by the Court after compliance with the provisions of the APPA, provided that the United States has not withdrawn its consent. The APPA conditions entry upon the Court's determination that the proposed Final Judgment is in the public interest.</P>
                    <P>
                        The APPA provides a period of at least 60 days preceding the effective date of the proposed Final Judgment within which any person may submit to the United States written comments regarding the proposed Final Judgment. Any person who wishes to comment should do so within 60 days of the date of publication of this Competitive Impact Statement in the 
                        <E T="04">Federal Register</E>
                        , or within 60 days of the first date of publication in a newspaper of the summary of this Competitive Impact Statement, whichever is later. All comments received during this period will be considered by the U.S. Department of Justice, which remains free to withdraw its consent to the proposed Final Judgment at any time before the Court's entry of the Final Judgment. The comments and the response of the United States will be filed with the Court. In addition, the comments and the United States' response will be published in the 
                        <E T="04">Federal Register</E>
                         unless the Court agrees that the United States instead may publish them on the U.S. Department of Justice, Antitrust Division's internet website.
                    </P>
                    <P>Written comments should be submitted in English to:</P>
                    <P>
                        David Teslicko, Acting Chief, Financial Services, Fintech, and Banking Section, Antitrust Division, United States Department of Justice, 450 Fifth St. NW, Suite 4000, Washington, 
                        <PRTPAGE P="41407"/>
                        DC 20530, 
                        <E T="03">LiveNationPublicComment@usdoj.gov</E>
                        .
                    </P>
                    <P>
                        The proposed Final Judgment provides that the Court retains jurisdiction over this action, and the parties may apply to the Court for any order necessary or appropriate for the modification, interpretation, or enforcement of the Final Judgment.
                        <SU>9</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>9</SU>
                             
                            <E T="03">See</E>
                             Proposed Final Judgment, ECF No. 1523-2, Section XVII.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">VI. Alternatives to the Proposed Final Judgment</HD>
                    <P>
                        As an alternative to the proposed Final Judgment, the United States considered completing the liability trial on the merits against Defendants. The United States could have continued the litigation and, upon a finding of liability, sought injunctive relief through additional remedy proceedings. This proposed Final Judgment provides relief designed to improve competition in markets, such as the artist promotion and venue booking markets, for which the Court previously granted Defendants' motion for summary judgment, over the United States' objections. 
                        <E T="03">See</E>
                         ECF No. 1037. It also brings benefits to competition sooner than would be expected after a full trial and appeals. Based on the totality of circumstances, including the time, expense, uncertainty, and risks associated with completing trial on the merits and completing any possible appeals, and the benefits to competition secured in the proposed Final Judgment, the United States chose not to complete the full trial on the merits and ensuing remedies proceeding and potential appeals.
                    </P>
                    <HD SOURCE="HD1">VII. Standard of Review Under the Appa for the Proposed Final Judgment</HD>
                    <P>
                        Under the APPA, proposed Final Judgments, or “consent decrees,” in antitrust cases brought by the United States are subject to a 60-day comment period, after which the Court shall determine whether entry of the proposed Final Judgment “is in the public interest.” 15 U.S.C. 16(e)(1); 
                        <E T="03">see also United States</E>
                         v. 
                        <E T="03">Int'l Bus. Mach. Corp.,</E>
                         163 F.3d 737, 740 (2d Cir. 1998). In making that determination, the Court, in accordance with the statute as amended in 2004, is required to consider:
                    </P>
                    <EXTRACT>
                        <P>(A) the competitive impact of such judgment, including termination of alleged violations, provisions for enforcement and modification, duration of relief sought, anticipated effects of alternative remedies actually considered, whether its terms are ambiguous, and any other competitive considerations bearing upon the adequacy of such judgment that the court deems necessary to a determination of whether the consent judgment is in the public interest; and</P>
                        <P>(B) the impact of entry of such judgment upon competition in the relevant market or markets, upon the public generally and individuals alleging specific injury from the violations set forth in the complaint including consideration of the public benefit, if any, to be derived from a determination of the issues at trial.</P>
                    </EXTRACT>
                    <FP>
                        15 U.S.C. 16(e)(1)(A) &amp; (B); 
                        <E T="03">see generally United States</E>
                         v. 
                        <E T="03">Keyspan,</E>
                         763 F. Supp. 2d 633, 637-38 (S.D.N.Y. 2011) (discussing Tunney Act standards). In considering these statutory factors, the Court's inquiry is necessarily a limited one as the government is entitled to “broad discretion to settle with the defendant within the reaches of the public interest.” 
                        <E T="03">United States</E>
                         v. 
                        <E T="03">Microsoft Corp.,</E>
                         56 F.3d 1448, 1461 (D.C. Cir. 1995); 
                        <E T="03">accord United States</E>
                         v. 
                        <E T="03">Alex. Brown &amp; Sons, Inc.,</E>
                         963 F. Supp. 235, 238 (S.D.N.Y. 1997), 
                        <E T="03">aff'd sub nom. United States</E>
                         v. 
                        <E T="03">Bleznak,</E>
                         153 F.3d 16 (2d Cir. 1998) (citing 
                        <E T="03">Microsoft,</E>
                         56 F.3d at 1460); 
                        <E T="03">Keyspan,</E>
                         763 F. Supp. 2d at 637 (same).
                    </FP>
                    <P>
                        As the United States Court of Appeals for the District of Columbia Circuit has held, under the APPA a court considers, among other things, the relationship between the remedy secured and the specific allegations in the government's Complaint, whether the proposed Final Judgment is sufficiently clear, whether its enforcement mechanisms are sufficient, and whether it may positively harm third parties. 
                        <E T="03">See Microsoft,</E>
                         56 F.3d at 1458-62. With respect to the adequacy of the relief secured by the decree, “` [t]he Court's function is not to determine whether the proposed [d]ecree results in the balance of rights and liabilities that is the one that will 
                        <E T="03">best</E>
                         serve society, but only to ensure that the resulting settlement is `within the 
                        <E T="03">reaches</E>
                         of the public interest.'” 
                        <E T="03">United States</E>
                         v. 
                        <E T="03">Morgan Stanley,</E>
                         881 F. Supp. 2d 563, 567 (S.D.N.Y. 2012) (quoting 
                        <E T="03">Alex. Brown &amp; Sons,</E>
                         963 F. Supp. at 238) (internal quotation marks omitted) (emphasis in original). In making this determination, “` [t]he [c]ourt is not permitted to reject the proposed remedies merely because the [c]ourt believes other remedies are preferable. [Rather], the relevant inquiry is whether there is a factual foundation for the government's decisions such that its conclusions regarding the proposed settlement are reasonable.' ” 
                        <E T="03">Morgan Stanley,</E>
                         881 F. Supp. 2d at 567 (citing 
                        <E T="03">United States</E>
                         v. 
                        <E T="03">Abitibi-Consolidated Inc.,</E>
                         584 F. Supp. 2d 162, 165 (D.D.C. 2008)); 
                        <E T="03">see also United States</E>
                         v. 
                        <E T="03">Apple, Inc.,</E>
                         889 F. Supp. 2d 623, 631 (S.D.N.Y. 2012); 
                        <E T="03">Alex. Brown &amp; Sons,</E>
                         963 F. Supp. at 238.
                        <SU>10</SU>
                        <FTREF/>
                         The United States' predictions about the efficacy of the remedy are to be afforded deference by the Court. 
                        <E T="03">Apple,</E>
                         889 F. Supp. 2d at 631; 
                        <E T="03">Microsoft,</E>
                         56 F.3d at 1461 (noting the need for courts to be “deferential to the government's predictions as to the effect of the proposed remedies”); 
                        <E T="03">United States</E>
                         v. 
                        <E T="03">ArcherDaniels-Midland Co.,</E>
                         272 F. Supp. 2d 1, 6 (D.D.C. 2003) (noting that the court should grant due respect to the United States' prediction as to the effect of proposed remedies, its perception of the market structure, and its views of the nature of the case); 
                        <E T="03">United States</E>
                         v. 
                        <E T="03">Iron Mountain, Inc.,</E>
                         217 F. Supp. 3d 146, 152-53 (D.D.C. 2016) (“In evaluating objections to settlement agreements under the Tunney Act, a court must be mindful that [t]he government need not prove that the settlements will perfectly remedy the alleged antitrust harms[;] it need only provide a factual basis for concluding that the settlements are reasonably adequate remedies for the alleged harms.”) (internal quotations omitted).
                    </P>
                    <FTNT>
                        <P>
                            <SU>10</SU>
                             
                            <E T="03">See also United States</E>
                             v. 
                            <E T="03">Bechtel Corp.,</E>
                             648 F.2d 660, 666 (9th Cir. 1981) (“The balancing of competing social and political interests affected by a proposed antitrust consent decree must be left, in the first instance, to the discretion of the Attorney General.”); 
                            <E T="03">see generally Microsoft,</E>
                             56 F.3d at 1461 (discussing whether “the remedies [obtained in the decree are] so inconsonant with the allegations charged as to fall outside of the `reaches of the public interest'”).
                        </P>
                    </FTNT>
                    <P>
                        “[A] proposed decree must be approved even if it falls short of the remedy the court would impose on its own, as long as it falls within the range of acceptability or is `within the reaches of public interest.'” 
                        <E T="03">United States</E>
                         v. 
                        <E T="03">Am. Tel. &amp; Tel. Co.,</E>
                         552 F. Supp. 131, 151 (D.D.C. 1982); 
                        <E T="03">Apple,</E>
                         889 F. Supp. 2d at 637 n.10; 
                        <E T="03">see also United States</E>
                         v. 
                        <E T="03">U.S. Airways Grp., Inc.,</E>
                         38 F. Supp. 3d 69, 74 (D.D.C. 2014) (noting that room must be made for the government to grant concessions in the negotiation process for settlements) (citing 
                        <E T="03">Microsoft,</E>
                         56 F.3d at 1461); 
                        <E T="03">Morgan Stanley,</E>
                         881 F. Supp. 2d at 568 (approving the consent decree even though the court may have imposed a greater remedy). To meet this standard, “it is necessary only that the submissions provide an ample `factual foundation for the government's decisions such that its conclusions regarding the proposed settlement are reasonable.' ” 
                        <E T="03">Apple,</E>
                         889 F. Supp. 2d at 639 (citing 
                        <E T="03">Keyspan,</E>
                         763 F. Supp. 2d at 637-38).
                    </P>
                    <P>
                        Moreover, the Court's role under the APPA is limited to reviewing the remedy in relationship to the violations that the United States has alleged in its Complaint, and does not authorize the 
                        <PRTPAGE P="41408"/>
                        Court to “construct [its] own hypothetical case and then evaluate the decree against that case.” 
                        <E T="03">Microsoft,</E>
                         56 F.3d at 1459; 
                        <E T="03">see also Morgan Stanley,</E>
                         881 F. Supp. 2d at 567 (“A court must limit its review to the issues in the complaint and give `due respect to the [Government's] perception of  . . . its case.' ”) (citing 
                        <E T="03">Microsoft,</E>
                         56 F.3d at 1461); 
                        <E T="03">United States</E>
                         v. 
                        <E T="03">InBev,</E>
                         2009 U.S. Dist. LEXIS 84787, at *20 (D.D.C. Aug. 11, 2009) (“[T]he `public interest' is not to be measured by comparing the violations alleged in the complaint against those the court believes could have, or even should have, been alleged”). Because the “court's authority to review the decree depends entirely on the government's exercising its prosecutorial discretion by bringing a case in the first place,” it follows that “the court is only authorized to review the decree itself,” and not to “effectively redraft the complaint” to inquire into other matters that the United States did not pursue. 
                        <E T="03">Microsoft,</E>
                         56 F.3d at 1459-60.
                    </P>
                    <P>
                        In its 2004 amendments to the APPA, Congress made clear its intent to preserve the practical benefits of using judgments proposed by the United States in antitrust enforcement, Public Law 108-237 § 221, and added the unambiguous instruction that “[n]othing in this section shall be construed to require the court to conduct an evidentiary hearing or to require the court to permit anyone to intervene.” 15 U.S.C. 16(e)(2); 
                        <E T="03">see also Apple,</E>
                         889 F. Supp. 2d at 633 (declining to hold evidentiary hearing and finding “[a] hearing would serve only to delay the proceedings unnecessarily.”); 
                        <E T="03">U.S. Airways,</E>
                         38 F. Supp. 3d at 76 (stating that “[a] court is not required to hold an evidentiary hearing or to permit intervenors as part of its review under the Tunney Act”). This language explicitly wrote into the statute what Congress intended when it first enacted the Tunney Act in 1974. As Senator Tunney explained: “[t]he court is nowhere compelled to go to trial or to engage in extended proceedings which might have the effect of vitiating the benefits of prompt and less costly settlement through the consent decree process.” 119 Cong. Rec. 24,598 (1973) (statement of Sen. John V. Tunney). Rather, the procedure for the public interest determination is left to the discretion of the court, with the recognition that the court's “scope of review remains sharply proscribed by precedent and the nature of Tunney Act proceedings.” 
                        <E T="03">SBC Commc'ns,</E>
                         489 F. Supp. 2d at 11; 
                        <E T="03">see also Apple,</E>
                         889 F. Supp. 2d at 632 (“[P]rosecutorial functions vested solely in the executive branch could be undermined by the improper use of the APPA as an antitrust oversight provision or anti-takeover statute.” (quoting 
                        <E T="03">United States</E>
                         v. 
                        <E T="03">BNS Inc.,</E>
                         858 F.2d 456, 466 (9th Cir. 1988)). A court can make its public interest determination based on the detailed allegations in the Complaint, competitive impact statement, and response to public comments alone. 
                        <E T="03">Apple,</E>
                         889 F. Supp. 2d at 633; 
                        <E T="03">U.S. Airways,</E>
                         38 F. Supp. 3d at 76.
                    </P>
                    <HD SOURCE="HD1">VIII. Determinative Documents</HD>
                    <P>There are no determinative materials or documents within the meaning of the APPA that were considered by the United States in formulating the proposed Final Judgment.</P>
                    <EXTRACT>
                        <P>Dated: June 29, 2026</P>
                        <P>Respectfully submitted,</P>
                        <FP>FOR PLAINTIFF</FP>
                        <FP>UNITED STATES OF AMERICA:</FP>
                        <FP SOURCE="FP-DASH"/>
                        <FP>Andrew L. Kline</FP>
                        <FP>David M. Teslicko</FP>
                        <FP>
                            United States Department of Justice, Antitrust Division, 450 Fifth St. NW, Suite 4000, Washington, DC 20530, Telephone: (202) 549-6655, Email: 
                            <E T="03">Andrew.Kline@usdoj.gov</E>
                            .
                        </FP>
                    </EXTRACT>
                </PREAMB>
                <FRDOC>[FR Doc. 2026-13623 Filed 7-2-26; 8:45 am]</FRDOC>
                <BILCOD>BILLING CODE 4410-11-P</BILCOD>
            </NOTICE>
        </NOTICES>
    </NEWPART>
    <VOL>91</VOL>
    <NO>127</NO>
    <DATE>Monday, July 6, 2026</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="41409"/>
            <PARTNO>Part V</PARTNO>
            <AGENCY TYPE="P"> Environmental Protection Agency</AGENCY>
            <CFR>40 CFR Part 63</CFR>
            <TITLE>National Emission Standards for Hazardous Air Pollutants: Plywood and Composite Wood Products; Final Rule</TITLE>
        </PTITLE>
        <RULES>
            <RULE>
                <PREAMB>
                    <PRTPAGE P="41410"/>
                    <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                    <CFR>40 CFR Part 63</CFR>
                    <DEPDOC>[EPA-HQ-OAR-2016-0243; FRL-5185.1-02-OAR]</DEPDOC>
                    <RIN>RIN 2060-AV56</RIN>
                    <SUBJECT>National Emission Standards for Hazardous Air Pollutants: Plywood and Composite Wood Products</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 U.S. Environmental Protection Agency (EPA) is finalizing amendments to the national emissions standards for hazardous air pollutants (NESHAP) for the Plywood and Composite Wood Products (PCWP) source category. Specifically, the EPA is finalizing maximum achievable control technology (MACT) standards in the form of emission limitations and work practices as appropriate for total hazardous air pollutants (HAP) (including acetaldehyde, acrolein, formaldehyde, methanol, phenol, propionaldehyde), non-mercury (non-Hg) HAP metals, mercury (Hg), hydrogen chloride (HCl), polycyclic aromatic hydrocarbons (PAH), dioxin/furan (D/F), and methylene diphenyl diisocyanate (MDI). Sources affected by the amendments include PCWP process units and lumber kilns located at facilities that are major sources of HAP emissions. These final amendments address the 2007 partial remand and vacatur of the 2004 final rule that promulgated the PCWP NESHAP (“2004 rule”). The final amendments also respond to issues raised in a petition for reconsideration regarding the 2020 residual risk and technology review (RTR) and other amendments to the 2020 PCWP NESHAP.</P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>This final rule is effective on July 6, 2026. The incorporation by reference of certain publications listed in the rule is approved by the Director of the Federal Register as of July 6, 2026.</P>
                    </EFFDATE>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P>
                            The EPA has established a docket for this action under Docket ID No. EPA-HQ-OAR-2016-0243. All documents in the docket are listed on the 
                            <E T="03">https://www.regulations.gov/</E>
                             website. Although listed, some information is not publicly available, 
                            <E T="03">e.g.,</E>
                             Confidential Business Information (CBI) or other information whose disclosure is restricted by statute. Certain other material, such as copyrighted material, is not placed on the internet and will be publicly available only as portable document format (PDF) versions that can only be accessed on the EPA computers in the docket office reading room. Certain databases and physical items cannot be downloaded from the docket but may be requested by contacting the docket office at (202) 566-1744. The docket office has up to 10 business days to respond to these requests. Except for these items, publicly available docket materials are available electronically at 
                            <E T="03">https://www.regulations.gov/</E>
                             or on EPA computers in the docket office reading room at the EPA Docket Center, WJC West Building, Room Number 3334, 1301 Constitution Ave. NW, Washington, DC. The Public Reading Room hours of operation are 8:30 a.m. to 4:30 p.m. Eastern Time (ET), Monday through Friday. The telephone number for the Public Reading Room is (202) 566-1744, and the telephone number for the EPA Docket Center is (202) 566-1742.
                        </P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>
                            For information about this final rule, contact U.S. EPA, Attn: Matthew Kollman, Mail Drop: E143-03, 109 T.W. Alexander Drive, P.O. Box 12055, Research Triangle Park, North Carolina 27711; telephone number: (919) 541-1920; and email address: 
                            <E T="03">Kollman.Matthew@epa.gov.</E>
                             Individuals who are deaf or hard of hearing, as well as individuals who have speech or communication disabilities, may use a telecommunications relay service. To learn more about how to make an accessible telephone call to any of the telephone numbers shown in this preamble, please visit 
                            <E T="03">https://www.fcc.gov/trs</E>
                             for the relay service of the Federal Communications Commission, and a list of relay services is available on their directory page at 
                            <E T="03">https://www.fcc.gov/general/trs-state-and-territories.</E>
                        </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P/>
                    <P>
                        <E T="03">Preamble acronyms and abbreviations.</E>
                         Throughout this document the use of “we,” “us,” or “our” is intended to refer to the EPA. We use multiple acronyms and terms in this preamble. While this list may not be exhaustive, to ease the reading of this preamble and for reference purposes, the EPA defines the following terms and acronyms here:
                    </P>
                    <EXTRACT>
                        <FP SOURCE="FP-1">APCD air pollution control device</FP>
                        <FP SOURCE="FP-1">CAA Clean Air Act</FP>
                        <FP SOURCE="FP-1">CBI Confidential Business Information</FP>
                        <FP SOURCE="FP-1">CEDRI Compliance and Emissions Data Reporting Interface</FP>
                        <FP SOURCE="FP-1">CEMS continuous emission monitoring system</FP>
                        <FP SOURCE="FP-1">CFR Code of Federal Regulations</FP>
                        <FP SOURCE="FP-1">CPMS continuous parameter monitoring system</FP>
                        <FP SOURCE="FP-1">
                            CO
                            <E T="52">2</E>
                            e carbon dioxide equivalent
                        </FP>
                        <FP SOURCE="FP-1">
                            D/F dioxin/furan (
                            <E T="03">i.e.,</E>
                             polychlorinated dibenzo-p-dioxins and polychlorinated dibenzofurans)
                        </FP>
                        <FP SOURCE="FP-1">dscm dry standard cubic meter</FP>
                        <FP SOURCE="FP-1">EDL estimated detection limit</FP>
                        <FP SOURCE="FP-1">EFB electrified filter bed</FP>
                        <FP SOURCE="FP-1">EPA Environmental Protection Agency</FP>
                        <FP SOURCE="FP-1">ESP electrostatic precipitator</FP>
                        <FP SOURCE="FP-1">°F degrees Fahrenheit</FP>
                        <FP SOURCE="FP-1">FR Federal Register</FP>
                        <FP SOURCE="FP-1">gr/dscf grains per dry standard cubic foot</FP>
                        <FP SOURCE="FP-1">HAP hazardous air pollutant(s)</FP>
                        <FP SOURCE="FP-1">HCl hydrogen chloride</FP>
                        <FP SOURCE="FP-1">Hg mercury</FP>
                        <FP SOURCE="FP-1">IBR incorporation by reference</FP>
                        <FP SOURCE="FP-1">ICR information collection request</FP>
                        <FP SOURCE="FP-1">kPa kilopascals</FP>
                        <FP SOURCE="FP-1">
                            lb/MSF 
                            <FR>3/4</FR>
                            ” pounds of pollutant per thousand square feet of 
                            <FR>3/4</FR>
                            -inch thick board
                        </FP>
                        <FP SOURCE="FP-1">
                            lb/MSF 
                            <FR>3/8</FR>
                            ” pounds of pollutant per thousand square feet of 
                            <FR>3/8</FR>
                            -inch thick board
                        </FP>
                        <FP SOURCE="FP-1">lb/ODT pounds of pollutant per oven-dried ton of wood</FP>
                        <FP SOURCE="FP-1">LVL laminated veneer lumber</FP>
                        <FP SOURCE="FP-1">MACT maximum achievable control technology</FP>
                        <FP SOURCE="FP-1">MDF medium density fiberboard</FP>
                        <FP SOURCE="FP-1">MDI methylene diphenyl diisocyanate</FP>
                        <FP SOURCE="FP-1">MDL method detection limit</FP>
                        <FP SOURCE="FP-1">mg/dscm milligrams of pollutant per dry standard cubic meter of air</FP>
                        <FP SOURCE="FP-1">NAICS North American Industry Classification System</FP>
                        <FP SOURCE="FP-1">NESHAP national emission standards for hazardous air pollutants</FP>
                        <FP SOURCE="FP-1">ng/dscm nanograms of pollutant per dry standard cubic meter of air</FP>
                        <FP SOURCE="FP-1">Non-Hg non-mercury</FP>
                        <FP SOURCE="FP-1">NRDC Natural Resources Defense Council</FP>
                        <FP SOURCE="FP-1">NTTAA National Technology Transfer and Advancement Act</FP>
                        <FP SOURCE="FP-1">O&amp;M operation and maintenance</FP>
                        <FP SOURCE="FP-1">OCAP Office of Clean Air Programs</FP>
                        <FP SOURCE="FP-1">OMB Office of Management and Budget</FP>
                        <FP SOURCE="FP-1">OSB oriented strandboard</FP>
                        <FP SOURCE="FP-1">PAH polycyclic aromatic hydrocarbons</FP>
                        <FP SOURCE="FP-1">PBCO production-based compliance option</FP>
                        <FP SOURCE="FP-1">PCWP plywood and composite wood products</FP>
                        <FP SOURCE="FP-1">PDF portable document format</FP>
                        <FP SOURCE="FP-1">PM particulate matter</FP>
                        <FP SOURCE="FP-1">PRA Paperwork Reduction Act</FP>
                        <FP SOURCE="FP-1">ppmvd parts per million by volume, dry</FP>
                        <FP SOURCE="FP-1">psia pounds per square inch absolute</FP>
                        <FP SOURCE="FP-1">RATA relative accuracy test audit</FP>
                        <FP SOURCE="FP-1">RCO regenerative catalytic oxidizer</FP>
                        <FP SOURCE="FP-1">RDL representative detection limit</FP>
                        <FP SOURCE="FP-1">RFA Regulatory Flexibility Act</FP>
                        <FP SOURCE="FP-1">RMH resinated material handling</FP>
                        <FP SOURCE="FP-1">RTC Response to Comments</FP>
                        <FP SOURCE="FP-1">RTO regenerative thermal oxidizer</FP>
                        <FP SOURCE="FP-1">RTR residual risk and technology review</FP>
                        <FP SOURCE="FP-1">SBA Small Business Administration</FP>
                        <FP SOURCE="FP-1">SSM startup, shutdown, and malfunction</FP>
                        <FP SOURCE="FP-1">TEQ toxic equivalency (relative the toxicity of 2,3,7,8-tetrachlordibenzo dioxin)</FP>
                        <FP SOURCE="FP-1">THC total hydrocarbon</FP>
                        <FP SOURCE="FP-1">tpy tons per year</FP>
                        <FP SOURCE="FP-1">UMRA Unfunded Mandates Reform Act</FP>
                        <FP SOURCE="FP-1">VCS voluntary consensus standards</FP>
                        <FP SOURCE="FP-1">WESP wet electrostatic precipitator</FP>
                        <FP SOURCE="FP-1">3xRDL three times the representative detection limit</FP>
                    </EXTRACT>
                    <HD SOURCE="HD1">Table of Contents </HD>
                    <EXTRACT>
                        <FP SOURCE="FP-2">
                            I. General Information
                            <PRTPAGE P="41411"/>
                        </FP>
                        <FP SOURCE="FP1-2">A. Executive Summary</FP>
                        <FP SOURCE="FP1-2">B. Does this action apply to me?</FP>
                        <FP SOURCE="FP1-2">C. Where can I get a copy of this document and other related information?</FP>
                        <FP SOURCE="FP1-2">D. Judicial Review and Administrative Reconsideration</FP>
                        <FP SOURCE="FP1-2">E. Severability</FP>
                        <FP SOURCE="FP-2">II. Background</FP>
                        <FP SOURCE="FP1-2">A. What is the statutory authority for this action?</FP>
                        <FP SOURCE="FP1-2">B. What is the PCWP source category and how does the current NESHAP regulate its HAP emissions?</FP>
                        <FP SOURCE="FP1-2">C. What changes did we propose for the PCWP source category in our May 18, 2023, proposal?</FP>
                        <FP SOURCE="FP-2">III. What is the rationale for our final decisions and amendments to the PCWP NESHAP?</FP>
                        <FP SOURCE="FP1-2">A. Analytical Procedures</FP>
                        <FP SOURCE="FP1-2">B. MACT Standards for Direct-Fired PCWP Dryers</FP>
                        <FP SOURCE="FP1-2">C. MACT Standards for Lumber Kilns</FP>
                        <FP SOURCE="FP1-2">D. MACT Standards for Process Units With Organic HAP Emissions</FP>
                        <FP SOURCE="FP1-2">E. MACT Standards for Process Units With MDI Emissions</FP>
                        <FP SOURCE="FP1-2">F. Requirements for Performance Testing, Monitoring, and Recordkeeping and Reporting</FP>
                        <FP SOURCE="FP1-2">G. Other Actions</FP>
                        <FP SOURCE="FP1-2">H. What are the effective and compliance dates of the standards?</FP>
                        <FP SOURCE="FP-2">IV. Summary of Cost, Environmental, and Economic Impacts and Additional Analyses Conducted</FP>
                        <FP SOURCE="FP1-2">A. What are the affected sources?</FP>
                        <FP SOURCE="FP1-2">B. What are the air quality impacts?</FP>
                        <FP SOURCE="FP1-2">C. What are the cost impacts?</FP>
                        <FP SOURCE="FP1-2">D. What are the economic impacts?</FP>
                        <FP SOURCE="FP1-2">E. What are the benefits?</FP>
                        <FP SOURCE="FP-2">V. Statutory and Executive Order Reviews</FP>
                        <FP SOURCE="FP1-2">A. Executive Order 12866: Regulatory Planning and Review and Executive Order 13563: Improving Regulation and Regulatory Review</FP>
                        <FP SOURCE="FP1-2">B. Executive Order 14192: Unleashing Prosperity Through Deregulation</FP>
                        <FP SOURCE="FP1-2">C. Paperwork Reduction Act (PRA)</FP>
                        <FP SOURCE="FP1-2">D. Regulatory Flexibility Act (RFA)</FP>
                        <FP SOURCE="FP1-2">E. Unfunded Mandates Reform Act (UMRA)</FP>
                        <FP SOURCE="FP1-2">F. Executive Order 13132: Federalism</FP>
                        <FP SOURCE="FP1-2">G. Executive Order 13175: Consultation and Coordination With Indian Tribal Governments</FP>
                        <FP SOURCE="FP1-2">H. Executive Order 13045: Protection of Children From Environmental Health Risks and Safety Risks</FP>
                        <FP SOURCE="FP1-2">I. Executive Order 13211: Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use</FP>
                        <FP SOURCE="FP1-2">J. National Technology Transfer and Advancement Act (NTTAA) and 1 CFR part 51</FP>
                        <FP SOURCE="FP1-2">K. Congressional Review Act (CRA)</FP>
                    </EXTRACT>
                    <HD SOURCE="HD1">I. General Information</HD>
                    <HD SOURCE="HD2">A. Executive Summary</HD>
                    <P>
                        In this final rule, the EPA is amending the PCWP NESHAP in response to multiple actions: the partial remand and vacatur of the 2004 final rule that promulgated the “2004 rule”, the petition for reconsideration of the 2020 RTR, and to address previously unregulated HAP in the PCWP source category.
                        <E T="51">1 2</E>
                        <FTREF/>
                         This final rule establishes new emission limitations and work practices as appropriate that reflect MACT for HAP emitted by process units that are part of the PCWP source category. This action is an amendment to the previous technology review, not a new technology review as required under CAA section 112(d)(6).
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             69 FR 45944 (July 30, 2004).
                        </P>
                        <P>
                            <SU>2</SU>
                             85 FR 49434 (Aug. 13, 2020).
                        </P>
                    </FTNT>
                    <P>
                        The EPA promulgated the PCWP NESHAP on July 30, 2004. In the 2004 rule, for several process units, the EPA concluded that the MACT floors were represented by no emission reduction (or “no-control” emission floors). In 2007, the U.S. Court of Appeals for the D.C. Circuit vacated and remanded those portions of the 2004 rule.
                        <SU>3</SU>
                        <FTREF/>
                         On August 13, 2020, the EPA took final action on the RTR of the PCWP NESHAP as required by Clean Air Act (CAA) sections 112(d)(6) and (f)(2). The EPA acknowledged in the preamble to the proposed RTR that there were unregulated sources with “no-control” MACT determinations in the PCWP source category, and we stated our plans to address those units in a separate action subsequent to the RTR.
                        <SU>4</SU>
                        <FTREF/>
                         The EPA also received a petition for reconsideration following promulgation of the 2020 RTR, which argued that the EPA failed to set limits for unregulated HAP, among other issues.
                    </P>
                    <FTNT>
                        <P>
                            <SU>3</SU>
                             
                            <E T="03">NRDC</E>
                             v. 
                            <E T="03">EPA,</E>
                             489 F.3d 1364 (D.C. Cir. 2007).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>4</SU>
                             84 FR 47077-78 (Sept. 6, 2019).
                        </P>
                    </FTNT>
                    <P>
                        On May 18, 2023, the EPA proposed revisions to the PCWP NESHAP (“May 2023 proposal”) to set MACT standards for total HAP (including acetaldehyde, acrolein, formaldehyde, methanol, phenol, propionaldehyde), MDI, and combustion-related HAP. The proposed standards for combustion related HAP include non-Hg HAP metals, mercury, HCl, PAH, and D/F).
                        <SU>5</SU>
                        <FTREF/>
                         We proposed setting total HAP and MDI standards for sources with previously vacated no-control floor determinations, MDI standards for processes that use MDI resins and coatings, and standards to limit combustion-related HAP from direct wood- and other fuel-fired dryers. 
                        <E T="03">See</E>
                         section II.C of this preamble for additional details and other proposed changes that were included in the May 2023 proposal.
                    </P>
                    <FTNT>
                        <P>
                            <SU>5</SU>
                             88 FR 31856 (May 18, 2023).
                        </P>
                    </FTNT>
                    <P>
                        The public comment period for the May 2023 proposal closed on July 18, 2023. We summarize some of the more significant comments we timely received regarding the proposed rule and provide our responses in section III of this preamble. A summary of all other public comments on the proposal and the EPA's responses to those comments is available in the docket for this rulemaking along with a redline strikeout version of the regulatory language that incorporates the changes.
                        <E T="51">6 7</E>
                        <FTREF/>
                         The EPA is finalizing MACT standards largely as proposed to address sources with previously vacated no-control floor determinations and unregulated HAP in the PCWP source category. Changes from the proposed rule are listed in Table 1 and include setting D/F emission limitations for direct wood-fired green rotary dryers, adding a definition for PAH, technical corrections to emissions data analyses, refinement to work practice standards for sources including lumber kilns, fiber washers, log vats, and wastewater operations to address comments on technical feasibility or clarity, and other changes to improve clarity such as revising the definition for non-HAP resin. Section III.G.4 of this preamble contains our responses to the issues raised by the petition for reconsideration that the EPA received on the 2020 RTR final rule.
                    </P>
                    <FTNT>
                        <P>
                            <SU>6</SU>
                             
                            <E T="03">National Emission Standards for Hazardous Air Pollutants: Plywood and Composite Wood Products (40 CFR part 63, subpart DDDD), Response to Public Comments on May 18, 2023 Proposed Amendments,</E>
                             available in the docket for this rulemaking.
                        </P>
                        <P>
                            <SU>7</SU>
                             
                            <E T="03">Final Regulation Edits for 40 CFR part 63 Subpart DDDD National Emission Standards for Hazardous Air Pollutants: Plywood and Composite Wood Products,</E>
                             available in the docket for this rulemaking.
                        </P>
                    </FTNT>
                    <P>
                        The EPA estimates that this final rule will result in the reduction of approximately 720 tons per year (tpy) HAP and 8,500 tpy volatile organic compounds (VOC) at a total annualized cost of $53 million (2024 dollars) to 219 affected major source facilities. Section IV of this preamble describes in more detail the final costs, emissions reductions, and economic impacts of this final rule.
                        <PRTPAGE P="41412"/>
                    </P>
                    <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s75,r150">
                        <TTITLE>Table 1—Summary of Final Amendments</TTITLE>
                        <BOXHD>
                            <CHED H="1">Action</CHED>
                            <CHED H="1">Summary</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Finalize standards for lumber kilns</ENT>
                            <ENT>Establishes work practice standards to limit emissions of organic HAP, combustion-related HAP, and VOCs from lumber kilns.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Finalize standards for organic HAP emitted by process units with previous “no-control” MACT determinations</ENT>
                            <ENT>Establishes numeric standards for organic HAP for new and existing atmospheric refiners and heated zones of existing fiberboard mat dryers and press predryers; establishes work practice standards for new and existing resinated material handling process units, stand-alone digesters, fiber washers, and log vats; and defines mixed PCWP process emissions streams subject to the NESHAP.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Finalize standards for previously unregulated resin-related HAP</ENT>
                            <ENT>Establishes numeric standards for MDI emissions for reconstituted wood products presses, tube dryers that blow-line blend MDI resin, and miscellaneous coating operations.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Finalize standards for previously unregulated combustion-related HAP</ENT>
                            <ENT>Establishes numeric standards for emissions of combustion-related HAP for new and existing direct wood-fired dryers; establishes work practice standards to limit emissions of combustion-related HAP, including D/F, by requiring burner tune-ups for burners associated with direct wood-fired and direct natural gas-fired dryers and by requiring continuous monitoring of an indicator of combustion unit bypass stack usage associated with PCWP dryers and lumber kilns.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Other updates and revisions</ENT>
                            <ENT>Establishes performance testing requirements for new and existing source emission limits; establishes monitoring, recordkeeping, and reporting requirements; removes obsolete rule language including the emissions averaging compliance option for existing affected sources, dates, and startup/shutdown provisions that are no longer in effect; and updates and clarifies electronic reporting requirements.</ENT>
                        </ROW>
                    </GPOTABLE>
                    <HD SOURCE="HD2">B. Does this action apply to me?</HD>
                    <P>
                        <E T="03">Regulated entities.</E>
                         Table 2 of this preamble presents categories and entities that this action potentially regulates.
                    </P>
                    <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s100,r100">
                        <TTITLE>Table 2—NESHAP and Industrial Source Categories Affected by This Final Action</TTITLE>
                        <BOXHD>
                            <CHED H="1">NESHAP and source category</CHED>
                            <CHED H="1">
                                NAICS 
                                <SU>1</SU>
                                 code
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Plywood and Composite Wood Products (40 CFR part 63, subpart DDDD)</ENT>
                            <ENT>321113, 321211, 321212, 321215, 321219, and 321999.</ENT>
                        </ROW>
                        <TNOTE>
                            <SU>1</SU>
                             North American Industry Classification System.
                        </TNOTE>
                    </GPOTABLE>
                    <P>
                        The EPA does not intend table 2 of this preamble to be exhaustive but rather to provide a guide for readers regarding the entities that this final action is likely to affect. To determine if this action affects your facility, you should examine the applicability criteria in title 40 of the Code of Federal Regulations (CFR), part 63, subpart DDDD. If you have any questions regarding the applicability of any aspect of this NESHAP, please contact the appropriate person listed in the preceding 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section of this preamble.
                    </P>
                    <HD SOURCE="HD2">C. Where can I get a copy of this document and other related information?</HD>
                    <P>
                        In addition to being available in the docket, an electronic copy of this action is available on the internet. In accordance with 5 U.S.C. 553(b)(4), a brief summary of this rulemaking may be found at 
                        <E T="03">www.regulations.gov,</E>
                         Docket ID No. EPA-HQ-OAR-2016-0243. Following signature by the EPA Administrator, the EPA will post a copy of this final action at 
                        <E T="03">https://www.epa.gov/stationary-sources-air-pollution/plywood-and-composite-wood-products-manufacture-national-emission.</E>
                         Following publication in the 
                        <E T="04">Federal Register</E>
                        , the EPA will post the 
                        <E T="04">Federal Register</E>
                         version of the final rule and key technical documents at this same website.
                    </P>
                    <HD SOURCE="HD2">D. Judicial Review and Administrative Reconsideration</HD>
                    <P>Under CAA section 307(b)(1), judicial review of this final action is available only by filing a petition for review in the United States Court of Appeals for the District of Columbia Circuit (D.C. Circuit) by September 4, 2026. CAA section 307(b)(2) prohibits a party from challenging this final rule separately in any civil or criminal proceedings brought by the EPA for enforcement.</P>
                    <P>
                        CAA section 307(d)(7)(B) further provides that only an objection to a rule or procedure that was raised with reasonable specificity during the period for public comment (including any public hearing) may be raised during judicial review. This section also requires the EPA to reconsider the rule if the person raising an objection can demonstrate to the Administrator that it was impracticable to raise such objection within the period for public comment or if the grounds for such objection arose after the period for public comment (but within the time specified for judicial review) and if such objection is of central relevance to the outcome of the rule. Any person seeking to make such a demonstration should submit a Petition for Reconsideration to the Office of the Administrator, U.S. EPA, Room 3000, WJC South Building, 1200 Pennsylvania Ave. NW, Washington, DC 20460, with a copy to both the person(s) listed in the preceding 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section, and the Associate General Counsel for the Air and Radiation Law Office, Office of General Counsel (Mail Code 2344A), U.S. EPA, 1200 Pennsylvania Ave. NW, Washington, DC 20460.
                    </P>
                    <HD SOURCE="HD2">E. Severability</HD>
                    <P>
                        This final rule contains several discrete components, which the EPA views as severable as a practical matter (
                        <E T="03">i.e.,</E>
                         they are functionally independent and will operate in practice independently of the other components). These discrete components are detailed in sections III.A through III.G of this preamble and 
                        <PRTPAGE P="41413"/>
                        the technical memoranda available in the docket. For example, the final requirements for direct-fired PCWP dryers, lumber kilns, process units that use MDI resins or coatings, monitoring of process unit bypass stacks, and performance testing generally function independently of one another and would not be impacted if a reviewing court were to vacate one or more of the other final provisions. In addition, as this final rule revises an existing NESHAP, the EPA notes that if a reviewing court were to vacate one or more of the standards finalized here, the affected standards will revert to those present in the 2020 RTR final rule.
                    </P>
                    <HD SOURCE="HD1">II. Background</HD>
                    <HD SOURCE="HD2">A. What is the statutory authority for this action?</HD>
                    <P>
                        CAA section 112, as amended (42 U.S.C. 7412) provides the statutory authority for this action. CAA section 112 establishes a two-stage regulatory process to develop standards for emissions of HAP from stationary sources. Generally, the first stage involves establishing technology-based standards that reflect MACT or an appropriate alternative.
                        <SU>8</SU>
                        <FTREF/>
                         The second stage involves evaluating those standards within eight years to determine whether additional standards are needed to address any remaining risk associated with HAP emissions.
                        <SU>9</SU>
                        <FTREF/>
                         The EPA commonly refers to this second stage as the “residual risk review.” In addition to the residual risk review, CAA section 112 also requires the EPA to review the standards at least every eight years and “revise as necessary” taking into account “developments in practices, processes, or control technologies.” 
                        <SU>10</SU>
                        <FTREF/>
                         This review, commonly referred to as the “technology review,” is the subject of this final rule. The discussion that follows identifies the most relevant CAA section 112 statutory sections and briefly explains the contours of the methodology used to implement these statutory requirements.
                    </P>
                    <FTNT>
                        <P>
                            <SU>8</SU>
                             42 U.S.C. 7412(d)(1)-(4).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>9</SU>
                             
                            <E T="03">Id.</E>
                             7412(f)(2).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>10</SU>
                             
                            <E T="03">Id.</E>
                             7412(d)(6).
                        </P>
                    </FTNT>
                    <P>
                        In the first stage, the EPA promulgates technology-based standards under CAA section 112(d) for categories of sources identified as emitting one or more of the HAP listed in CAA section 112(b). “Major sources” are those that emit, or have the potential to emit, any single HAP at a rate of 10 tpy or more, or 25 tpy or more of any combination of HAP.
                        <SU>11</SU>
                        <FTREF/>
                         For major sources, these standards are commonly referred to as MACT standards; CAA section 112(d)(2) provides that these must reflect the maximum degree of emission reductions of HAP achievable (after considering cost, energy requirements, and non-air quality health and environmental impacts). In developing MACT standards, CAA section 112(d)(2) directs the EPA to consider the application of measures, processes, methods, systems, or techniques, including, but not limited to, those that reduce the volume of or eliminate HAP emissions through process changes, substitution of materials, or other modifications; enclose systems or processes to eliminate emissions; collect, capture, or treat HAP when released from a process, stack, storage, or fugitive emissions point; are design, equipment, work practice, or operational standards; or any combination of the above.
                    </P>
                    <FTNT>
                        <P>
                            <SU>11</SU>
                             
                            <E T="03">Id.</E>
                             7412(a)(1).
                        </P>
                    </FTNT>
                    <P>CAA section 112(d)(3) establishes a minimum control level for MACT standards, known as the MACT “floor,” based on emission controls achieved in practice by the best performing sources. For new sources, the MACT floor cannot be less stringent than the emission control achieved in practice by the best-controlled similar source. The MACT standards for existing sources can be less stringent than floors for new sources, but they cannot be less stringent than the average emission limitation achieved by the best-performing 12 percent of existing sources in the category or subcategory (or the best-performing five sources for categories or subcategories with fewer than 30 sources).</P>
                    <P>
                        In certain instances, as provided in CAA section 112(h), the EPA may set work practice standards in lieu of numerical emission standards. Under CAA section 112(h), the EPA may adopt a work practice standard in lieu of a numerical emission standard if it is “not feasible in the judgment of the Administrator to prescribe or enforce an emission standard for control of a hazardous air pollutant or pollutants.” 
                        <SU>12</SU>
                        <FTREF/>
                         CAA section 112(h)(2) defines the phrase “not feasible to prescribe or enforce an emission standard” to mean any situation where the Administrator either determines that a HAP or HAPs “cannot be emitted through a conveyance designed and constructed to emit or capture such pollutant, or that any requirement for, or use of such a conveyance would be inconsistent with any Federal, State or local law” 
                        <SU>13</SU>
                        <FTREF/>
                         or determines that “the application of measurement methodology to a particular class of sources is not practicable due to technological and economic limitations.” 
                        <SU>14</SU>
                        <FTREF/>
                         The EPA considers a measurement to be not technologically practicable within the meaning of CAA section 112(h)(2)(B) if the majority of the measurements are below the detection limit. Such measurements raise issues of questionable reliability, feasibility, and enforceability.
                    </P>
                    <FTNT>
                        <P>
                            <SU>12</SU>
                             
                            <E T="03">Id.</E>
                             7412(h)(1).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>13</SU>
                             
                            <E T="03">Id.</E>
                             7412(h)(2)(A).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>14</SU>
                             
                            <E T="03">Id.</E>
                             7412(h)(2)(B).
                        </P>
                    </FTNT>
                    <P>
                        The EPA also considers control options that are more stringent than the floor and may establish standards more stringent than the floor, based on the consideration of the cost of achieving the emissions reductions, any non-air quality health and environmental impacts, and energy requirements.
                        <SU>15</SU>
                        <FTREF/>
                         Standards more stringent than the floor are commonly referred to as “beyond-the-floor” standards. In the second stage of the regulatory process, the CAA section 112(d)(6) requires the EPA to undertake a technology review no less frequently than every eight years. Under the technology review, the EPA must review the technology-based standards and revise them “as necessary (taking into account developments in practices, processes, and control technologies).” 
                        <SU>16</SU>
                        <FTREF/>
                         In conducting this review, the EPA is not required to recalculate the MACT floors that were established in earlier rulemakings.
                        <SU>17</SU>
                        <FTREF/>
                         The EPA may consider cost in deciding whether to revise the standards pursuant to CAA section 112(d)(6).
                        <SU>18</SU>
                        <FTREF/>
                         Following the D.C. Circuit's decision in 
                        <E T="03">Louisiana Environmental Action Network (LEAN)</E>
                         v. 
                        <E T="03">EPA,</E>
                        <SU>19</SU>
                        <FTREF/>
                         the EPA also reviews available data to determine if there are unregulated HAP within the source category and evaluate these data for use in developing new emission standards. The D.C. Circuit held in 
                        <E T="03">LEAN</E>
                         that the EPA is required to address unregulated HAP from a major source category when the Agency conducts a technology review of a NESHAP that previously left such HAP unregulated.
                        <SU>20</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>15</SU>
                             
                            <E T="03">Id.</E>
                             7412(d)(2).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>16</SU>
                             CAA section 112(d)(6). CAA section 112 is codified at 42 U.S.C. 7412.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>17</SU>
                             
                            <E T="03">Ass'n of Battery Recyclers, Inc.</E>
                             v. 
                            <E T="03">EPA,</E>
                             716 F.3d 667 (D.C. Cir. 2013); 
                            <E T="03">NRDC</E>
                             v. 
                            <E T="03">EPA,</E>
                             529 F.3d 1077, 1084 (D.C. Cir. 2008).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>18</SU>
                             42 U.S.C. 7412(d)(2), (6); 
                            <E T="03">Ass'n of Battery Recyclers,</E>
                             716 F.3d at 673-74.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>19</SU>
                             955 F.3d 1088 (D.C. Cir. 2020).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>20</SU>
                             The Agency is proposing elsewhere, 
                            <E T="03">see e.g.,</E>
                             91 FR 21672 (Apr. 22, 2026), that the D.C. Circuit's decision in 
                            <E T="03">LEAN</E>
                             did not address the separate question whether the statute is best read as mandating that the EPA address any unregulated emission points during the next available technology review. Rather, as proposed, the EPA retains discretion to evaluate whether and at what time to expand the regulatory scope of the NESHAP to include additional emission points, including 
                            <PRTPAGE/>
                            whether it is appropriate to regulate such additional emission points in the NESHAP for the particular source category at issue or instead as part of a different or new source category. In this final rule, the EPA is regulating emission points excluded from the 2004 rule in response to the D.C. Circuit's 2007 remand in 
                            <E T="03">NRDC,</E>
                             which held that the Agency had wrongfully excluded these emission points in the first instance from the 2004 rule that established standards for the PCWP source category. Doing so at this time is consistent with the EPA's obligations on remand from NRDC and with the EPA's discretion to address unregulated emission points when appropriate and in an appropriate manner.
                        </P>
                    </FTNT>
                    <PRTPAGE P="41414"/>
                    <P>
                        In the 2004 rule, the EPA concluded that the MACT floors for several process units were represented by no emission reduction (or “no control” emission floors) and declined to set standards for those units. In 2007, the D.C. Circuit held that the EPA's use of “no-control” emission floors to avoid setting emissions standards in another source category was unlawful.
                        <SU>21</SU>
                        <FTREF/>
                         In response, the EPA requested a voluntary remand and vacatur of the portions of the 2004 rule that included these “no-control” emission floor determinations.
                        <SU>22</SU>
                        <FTREF/>
                         The D.C. Circuit remanded and vacated those portions of the 2004 rule to the EPA to set emission standards for those units to replace the unlawful “no-control” floor determinations.
                        <SU>23</SU>
                        <FTREF/>
                         On August 13, 2020, the EPA took final action on the RTR of the PCWP NESHAP as required by CAA sections 112(d)(6) and (f)(2). The EPA acknowledged in the preamble to the proposed RTR that there are unregulated sources with “no-control” MACT determinations in the PCWP source category, and we stated our plans to address those units in a separate action subsequent to the RTR.
                        <SU>24</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>21</SU>
                             
                            <E T="03">Sierra Club</E>
                             v. 
                            <E T="03">EPA,</E>
                             479 F.3d 875, 883 (D.C. Cir. 2007).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>22</SU>
                             
                            <E T="03">NRDC,</E>
                             489 F.3d at 1371.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>23</SU>
                             
                            <E T="03">See id.</E>
                             at 1375. .
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>24</SU>
                             84 FR 47077-78 (Sept. 6, 2019).
                        </P>
                    </FTNT>
                    <P>This final rule responds to the partial remand and vacatur of the 2004 rule, the petition for reconsideration of the 2020 RTR, and addresses previously unregulated HAP in the PCWP source category. This final rule establishes new standards that reflect MACT for HAP emitted by process units that are part of the PCWP source category, pursuant to CAA sections 112(d)(2) and (3) and, where appropriate, CAA section 112(h). The EPA is setting “total HAP” standards (defined in the PCWP NESHAP as acetaldehyde, acrolein, formaldehyde, methanol, phenol, and propionaldehyde) for sources with previously vacated “no-control” MACT determinations. In addition to total HAP, the EPA is setting standards for previously unregulated HAP present in the PCWP source category, including non-Hg HAP metals, Hg, HCl, PAH, and D/F as a result of combustion in direct-fired dryers and MDI from processes that use MDI resins and coatings.</P>
                    <HD SOURCE="HD2">B. What is the PCWP source category and how does the current NESHAP regulate its HAP emissions?</HD>
                    <P>
                        The EPA originally promulgated the PCWP NESHAP on July 30, 2004.
                        <SU>25</SU>
                        <FTREF/>
                         The standards are codified at 40 CFR part 63, subpart DDDD. The PCWP industry consists of facilities engaged in the production of PCWP or kiln-dried lumber. PCWP are manufactured by bonding wood material (fibers, particles, strands, etc.) or agricultural fiber, generally with resin under heat and pressure, to form a structural panel or engineered wood product. PCWP manufacturing facilities also include facilities that manufacture dry veneer and lumber kilns located at any facility. PCWP includes (but are not limited to) plywood, veneer, particleboard, oriented strand board (OSB), hardboard, fiberboard, medium density fiberboard (MDF), laminated strand lumber, laminated veneer lumber (LVL), wood I-joists, kiln-dried lumber, and glue-laminated beams. There are currently 219 major source facilities that are subject to the PCWP NESHAP, including 93 facilities manufacturing PCWP and 126 facilities producing kiln-dried lumber. A major source of HAP is a plant site that emits or has the potential to emit any single HAP at a rate of 9.07 megagrams (10 tons) or more, or any combination of HAP at a rate of 22.68 megagrams (25 tons) or more per year from all emission sources at the plant site.
                    </P>
                    <FTNT>
                        <P>
                            <SU>25</SU>
                             69 FR 45944 (July 30, 2004).
                        </P>
                    </FTNT>
                    <P>The affected source under the PCWP NESHAP is the collection of dryers, refiners, blenders, formers, presses, board coolers, and other process units associated with the manufacturing of PCWP. The affected source includes, but is not limited to, green end operations, refining, drying operations (including any combustion unit exhaust stream routinely used to direct fire process unit(s)), resin preparation, blending and forming operations, pressing and board cooling operations, and miscellaneous finishing operations (such as sanding, sawing, patching, edge sealing, and other finishing operations not subject to other NESHAP). The affected source also includes onsite storage and preparation of raw materials used in the manufacturing of PCWP, such as resins; onsite wastewater treatment operations specifically associated with PCWP manufacturing; and miscellaneous coating operations. The affected source includes lumber kilns at PCWP manufacturing facilities and at any other kind of facility.</P>
                    <P>The PCWP NESHAP contains several compliance options for process units subject to the standards: (1) installation and use of emissions control systems with an efficiency of at least 90 percent; (2) production-based limits that restrict HAP emissions per unit of product produced; and (3) emissions averaging that allows control of emissions from a group of sources collectively (only at existing affected sources). These compliance options apply for the following process units: fiberboard mat dryer heated zones (at new affected sources); green rotary dryers; hardboard ovens; press predryers (at new affected sources); pressurized refiners; primary tube dryers; secondary tube dryers; reconstituted wood product board coolers (at new affected sources); reconstituted wood product presses; softwood veneer dryer heated zones; rotary strand dryers; and conveyor strand dryers (zone one at existing affected sources, and zones one and two at new affected sources). In addition, the PCWP NESHAP includes work practice standards for dry rotary dryers, hardwood veneer dryers, softwood veneer dryers, veneer redryers, and group 1 miscellaneous coating operations (defined in 40 CFR 63.2292).</P>
                    <P>
                        The 2020 RTR found that the risk associated with air emissions from the PCWP manufacturing industry (including those from lumber kilns and other process units and HAP for which we had not yet responded to the 2007 partial remand and vacatur) are acceptable and that the current PCWP NESHAP provides an ample margin of safety to protect public health. In the 2020 RTR, the EPA concluded that there were no developments in practices, processes, or control technologies that would warrant revisions to the specific standards already promulgated in 2004. In addition to conclusions with respect to the RTR, the 2020 action contained amendments to remove exemptions from the standards during periods of startup, shutdown, and malfunction (SSM). The 2020 RTR amendments added work practices so there would be standards in place of the former startup and shutdown exemptions for three specific events that occur during PCWP production: safety-related shutdowns, pressurized refiner startup/shutdown, and softwood veneer dryer gas-burner relights. Lastly, the 2020 RTR amendments included provisions requiring electronic reporting and repeat emissions testing. In the 2020 RTR, the EPA did not address and reached no conclusions regarding unregulated HAP. The 2020 RTR did not address 
                        <PRTPAGE P="41415"/>
                        establishing MACT emissions limits or work practices for the process units or HAP that were the subject of the 2007 D.C. Circuit's partial remand and vacatur of the 2004 rule's “no-control” MACT determinations. Consequently, this is the first rulemaking in which the EPA has addressed emission limits and work practices for these process units and HAP, since the 2007 ruling.
                    </P>
                    <HD SOURCE="HD2">C. What changes did we propose for the PCWP source category in our May 18, 2023, proposal?</HD>
                    <P>
                        On May 18, 2023, the EPA published a proposal in the 
                        <E T="04">Federal Register</E>
                         for the PCWP NESHAP, 40 CFR part 63, subpart DDDD to set MACT standards for total HAP, MDI, and combustion-related HAP including non-Hg HAP metals, Hg, HCl, PAH, D/F. Total HAP limits were proposed for fiberboard mat dryers at existing sources, hardboard press predryers at existing sources, and atmospheric refiners at existing and new sources. Limits for non-Hg HAP metals in the form of particulate matter (PM), Hg, HCl, and PAH were proposed for direct wood- and other fuel-fired dryers at existing and new sources. MDI limits were proposed for reconstituted wood product presses using MDI, tube dryers blow-line blending MDI, and miscellaneous coating operations. The proposed rule also included the addition of burner tune-up requirements for all direct-fired PCWP dryers, direct-fired lumber kilns, and associated combustion unit bypass stacks. Work practice standards were also proposed for lumber kilns, stand-alone digesters, fiber washers, log vats, wastewater operations, and resinated material handling (RMH) units, including resin tanks, blenders, formers, reconstituted wood products board coolers at existing sources, plywood presses, engineered wood product presses and curing chambers, finishing sanders, finishing saws, panel trim chippers, humidifiers, and wastewater operations.
                    </P>
                    <P>The proposed rule included the removal of the emissions averaging compliance option for existing affected sources (not available for new affected sources). The proposed rule also included a requirement for mixed PCWP process streams at existing sources currently meeting the compliance options present in Table 1B of this subpart to continue doing so. Additionally, the proposed rule included a requirement to monitor process unit bypass stack usage at all times; plus, the proposal added emissions testing; monitoring, reporting, and recordkeeping requirements relevant to the standards being added. The proposal incorporated a revised definition of “pressurized refiner” to clearly distinguish between stand-alone digesters and pressurized refiners. Lastly, the proposed rule included the removal of obsolete date language associated with amendments finalized on August 13, 2020, that are now implemented.</P>
                    <HD SOURCE="HD1">III. What is the rationale for our final decisions and amendments to the PCWP NESHAP?</HD>
                    <P>This action finalizes the EPA's determinations pursuant to the technology review provisions of CAA section 112 for the PCWP source category and amends the PCWP NESHAP based on those determinations. This action also reflects several changes to the May 2023 proposal in consideration of comments received during the public comment period described in section III of this preamble.</P>
                    <P>
                        Section III.A describes the analytical procedures used to develop the MACT standards we are finalizing. Section III.B discusses the MACT standards we are finalizing for combustion-related HAP from direct-fired PCWP dryers, including rotary strand dryers, green rotary dryers, dry rotary dryers, tube dryers, and softwood veneer dryers. Section III.C discusses the MACT standards we are finalizing for all HAP emitted from lumber kilns. Section III.D discusses the MACT standards we are finalizing for total HAP from various process units other than lumber kilns that also had “no-control” MACT determinations in the 2004 rule that were vacated and remanded. Section III.E discusses the MACT standards we are finalizing for process units with MDI emissions, including reconstituted wood product presses, blow-line blend tube dryers, and miscellaneous coating operations. Section III.F discusses the final requirements for performance testing, monitoring, and recordkeeping and reporting. Section III.G discusses other actions we are finalizing. Section III.H discusses the effective and compliance dates of the amendments we are finalizing. Each of these discussions include a summary of what we proposed, a summary of key comments we received on what we proposed and our responses, and a summary of our final decisions and rationale. Comment summaries for all other comments and the EPA's specific responses can be found in the response to comments (RTC) document.
                        <SU>26</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>26</SU>
                             
                            <E T="03">National Emission Standards for Hazardous Air Pollutants: Plywood and Composite Wood Products (40 CFR part 63, subpart DDDD), Response to Public Comments on May 18, 2023 Proposed Amendments,</E>
                             available in the docket for this rulemaking.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">A. Analytical Procedures</HD>
                    <P>
                        The MACT standards finalized in this action were developed pursuant to CAA sections 112(d)(2) and (3) or, when appropriate, CAA section 112(h). When developing MACT standards, the “MACT floor” for existing sources is calculated based on the average performance of the best performing units in each category or subcategory and on a consideration of the variability of HAP emissions from these units. The MACT floor for new sources is based on the emissions levels that are achieved by the best performing similar source, with a similar consideration of variability. For existing sources, the MACT floor is based on the average emission limitation achieved by the best performing 12 percent of sources (for which the EPA has emissions information) for source categories or subcategories with 30 or more sources, or the average emission limitation achieved by the best performing five sources (for which the EPA has or could reasonably obtain emissions information) for categories or subcategories with fewer than 30 sources. The EPA does not consider costs when determining the MACT floor. To account for variability in PCWP manufacturing operations and resulting emissions, we calculated the MACT floors using the 99 percent Upper Prediction Limit (UPL) using performance data collected from two CAA section 114 surveys of PCWP facilities in 2017 and 2022.
                        <SU>27</SU>
                        <FTREF/>
                         We note that the MACT floors for certain existing and new units are based on limited data sets.
                        <SU>28</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>27</SU>
                             For more information regarding the general use of the UPL and why it is appropriate for calculating MACT floors, see 
                            <E T="03">Use of Upper Prediction Limit for Calculating MACT Floors</E>
                             (UPL Memo), available in the docket for this rulemaking.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>28</SU>
                             
                            <E T="03">See</E>
                             the memorandum entitled 
                            <E T="03">Revised Approach for Applying the Upper Prediction Limit to Limited Datasets,</E>
                             available in the docket for this rulemaking.
                        </P>
                    </FTNT>
                    <P>
                        Once the UPL is calculated for a pollutant, the representative detection limit (RDL) for the pollutant measurement method is considered, if necessary. The RDL is representative of the laboratory instrument sensitivity and lowest industry-standard method detection limits (MDL) achieved when analyzing air pollutant samples. Consideration of the RDL is necessary when pollutants are measured near or below the detection limit of the analysis method, which was the case for some HAP measured in the 2022 survey. The EPA compares a value of three times the RDL (3xRDL) of the pollutant to UPL 
                        <PRTPAGE P="41416"/>
                        values to ensure that the calculated MACT floors account for measurement variability.
                        <SU>29</SU>
                        <FTREF/>
                         If the 3xRDL value exceeds the MACT floor UPL, the 3xRDL value is substituted as the MACT floor emission limit to ensure that the standard is set no lower than the minimum level at which emissions can reliably be measured. We applied an established procedure for cases where we had low detection data to handle below detection level (BDL) data and develop RDL data when setting MACT emission limits.
                        <SU>30</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>29</SU>
                             The factor of three used in the 3xRDL calculation is based on a scientifically accepted definition of level of quantitation—simply stated, the level where a test method performs with acceptable precision. The level of quantitation has been defined as 10 times the standard deviation of seven replicate analyses of a sample at a concentration level close to the MDL units of the emission standard. That level is then compared to the MACT floor value to ensure that the resulting emission limit is in a range that can be measured with reasonable precision. In other words, if the 3xRDL value were less than the calculated floor (
                            <E T="03">e.g.,</E>
                             calculated from the UPL), we would conclude that measurement variability has been adequately addressed by the calculated floor; if it were greater than the calculated floor, we would adjust the emissions limit to comport with the 3xRDL value to address measurement variability.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>30</SU>
                             Westlin, P. &amp; Merrill, R. (2012). 
                            <E T="03">Data and procedure for handling below detection level data in analyzing various pollutant emissions databases for MACT and RTR emissions limits,</E>
                             available in the docket for this rulemaking.
                        </P>
                    </FTNT>
                    <P>In addition, under CAA section 112(d)(2), the EPA must examine more stringent “beyond-the-floor” regulatory options to determine MACT. Unlike the floor minimum stringency requirements, the EPA must consider various impacts of the more stringent regulatory options in determining whether MACT standards are to reflect beyond-the-floor requirements. These impacts include the cost of achieving additional emissions reduction beyond that achieved by the MACT floor, any non-air quality health and environmental impacts that would result from imposing controls beyond the floor, and energy requirements of such beyond floor measures. If the EPA concludes that the more stringent regulatory options have unreasonable impacts, the EPA selects the MACT floor as MACT. However, if the EPA concludes that impacts associated with beyond-the-floor levels of control are reasonable considering additional HAP emissions reductions achieved, the EPA selects those beyond-the-floor levels as MACT.</P>
                    <P>For some process types, it is not feasible to prescribe or enforce a numerical emission standard using the MACT floor and MACT determination approach described in CAA sections 112(d)(2) and (3). According to CAA section 112(h)(1), MACT standards may take the form of design, equipment, work practice, or operational standards if it is not feasible in the judgment of the Administrator to prescribe or enforce an emission standard for control of HAP. To support a determination that it is not feasible to prescribe or enforce an emission standard for control of HAP, CAA sections 112(h)(2)(A) and (B) require the EPA to determine that either: (A) a HAP or pollutants cannot be emitted through a conveyance designed and constructed to emit or capture such pollutant, or that any requirement for, or use of, such a conveyance would be inconsistent with any Federal, State or local law, or (B) the application of measurement methodology to a particular class of sources is not practicable due to technological and economic limitations.</P>
                    <HD SOURCE="HD2">B. MACT Standards for Direct-Fired PCWP Dryers</HD>
                    <P>
                        As proposed, the EPA is finalizing standards for two subcategories of PCWP direct-fired dryers: (1) wood and other fuel-fired dryers; and (2) natural gas fuel-fired dryers. We subcategorized PCWP direct-fired dryers by fuel type because wood and other fuel-fired dryers have different design and combustion-related HAP emissions profiles from those firing natural gas (or propane). We are finalizing the addition of the following definitions to the PCWP NESHAP to delineate the different types of direct-fired PCWP dryers: 
                        <E T="03">PCWP dryer, Direct wood-fired PCWP dryer, and Direct natural gas-fired PCWP dryer.</E>
                         In addition, we are finalizing the same definition of natural gas used in the NESHAP codified at 40 CFR part 63, subpart DDDDD (“Boiler MACT”).
                    </P>
                    <P>As proposed, the EPA is finalizing a work practice standard requiring annual burner tune-ups for the combustion unit(s) that fire new and existing direct-fired PCWP dryers. The purpose of the annual burner tune-ups is to control all combustion-related HAP that may be emitted from direct natural gas-fired PCWP dryers and control D/F emissions from direct wood-fired dryers. In addition to requiring annual burner tune-ups for all direct-fired dryers, we are also finalizing the proposed requirement for new and existing direct-fired PCWP dryers to continuously monitor an indicator of their combustion unit bypass stack usage such as flow damper position or temperature to address any HAP emitted from combustion bypass stacks associated with direct-fired PCWP dryers. As explained in the preamble, work practice standards for direct-fired dryer bypass stacks are justified because emissions are not technically and feasibly measurable.</P>
                    <HD SOURCE="HD3">1. What combustion HAP standards did we propose for direct wood-fired dryers?</HD>
                    <P>For direct wood-fired PCWP dryers, emission limits for combustion HAP were developed following the approach described in section III.A. The MACT emission limits were developed in mass per production and concentration units to provide compliance options for the various dryer configurations subject to the standards. Mass per production units are pounds of pollutant per thousand square feet (lb/MSF) for softwood veneer dryers and pounds per oven dried ton (lb/ODT) for all other dryer types. Concentration units include grains per dry standard cubic foot (gr/dscf) for PM and milligrams per dry standard cubic meter (mg/dscm) for non-PM pollutants.</P>
                    <P>
                        The EPA proposed MACT standards for combustion-related HAP (non-Hg metals, Hg, HCl, PAH, and D/F) from direct wood-fired PCWP dryers, which include rotary strand dryers, green rotary dryers, dry rotary dryers, tube dryers, softwood veneer dryers (heated zones), fiberboard mat dryers (heated zones), and hardboard ovens. The EPA proposed PM numerical limits to serve as a surrogate to control non-Hg metals and proposed numerical limits for both mercury and HCl. Additionally, the EPA proposed PAH numerical limits for all direct wood-fired dryers based on an aggregate of 19 PAH compounds which serve as a surrogate for all PAHs in the PCWP source category. Lastly, the EPA proposed a D/F work practice to address D/F emissions from direct wood-fired dryers in the PCWP source category. Some, but not all, changes to the direct-fired standards from the May 2023 proposal are discussed in the remainder of this section.
                        <SU>31</SU>
                        <FTREF/>
                         A complete discussion of changes is provided in the RTC document and a docketed memorandum.
                        <SU>32</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>31</SU>
                             88 FR 31861-67 (May 18, 2023).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>32</SU>
                             
                            <E T="03">Revised Regulatory Options for Combustion-related HAP from Plywood and Composite Wood Products Direct-Fired Dryers,</E>
                             available in the docket for this rulemaking.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2. What comments did we receive on combustion HAP standards for direct wood-fired dryers?</HD>
                    <P>
                        <E T="03">Comment:</E>
                         The EPA received comments on specific data and production values used in our calculations of the proposed PM emission limit for green rotary dryers.
                    </P>
                    <P>
                        <E T="03">EPA Response:</E>
                         After reevaluating the production values used in the PM UPL calculations for green rotary dryers, and 
                        <PRTPAGE P="41417"/>
                        reviewing the technical errors raised by commenters, the EPA agreed with commenters and found that the new and existing source limits for PM required correction due to technical errors. 
                        <E T="03">See</E>
                         section 3 of the RTC document located in the docket for this rulemaking for these specific comments and our responses regarding revisions.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         With regards to the proposed PAH limits for wood-fired dryers, commenters argued that data quality issues with the PAH data collected in the 2022 survey render the data unsuitable for setting these limits. The commenters requested that the EPA remove the PAH limits based on the collected data and instead rely on the annual burner tune-up work practice to control PAH emissions. The commenters noted the annual burner tune-up work practice to reduce D/F formation would also reduce the formation of PAH.
                    </P>
                    <P>
                        <E T="03">EPA Response:</E>
                         The EPA agrees, in part, with the commenter's concern over data quality. The EPA has reevaluated the PAH data and concluded the data were acceptable for setting MACT limits after two adjustments. First, we removed one 3-run test with excessive contamination from the final MACT analysis (in addition to a single test run with lab analysis problems we had already removed from the proposed MACT analysis). Second, we removed naphthalene from the MACT floor analysis and from the rule specific definition of PAH at 40 CFR 63.2292 to preemptively address naphthalene contamination issues in future compliance demonstrations.
                        <SU>33</SU>
                        <FTREF/>
                         The EPA received sufficient data in the 2022 survey to demonstrate that the remaining 18 PAH congeners serve as an appropriate surrogate for polycyclic organic matter and naphthalene, the listed HAP that PAH standards are intended to regulate.
                    </P>
                    <FTNT>
                        <P>
                            <SU>33</SU>
                             
                            <E T="03">See</E>
                             the RTC document and memorandum entitled 
                            <E T="03">Revised Regulatory Options for Combustion-related HAP from Plywood and Composite Wood Products Direct-Fired Dryers,</E>
                             available in the docket for this rulemaking.
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters argued that our proposal to use the 3xRDL value of 3.3E-05 mg/dscm as the PAH limit for wood-fired softwood veneer dryers in the absence of PAH test data was arbitrary and capricious.
                    </P>
                    <P>
                        <E T="03">EPA Response:</E>
                         The EPA agrees that we lacked adequate data to establish a numerical MACT limit for softwood veneer dryers. Performance data were not collected from direct-wood fired softwood veneer dryers in the CAA section 114 survey because softwood veneer dryers were not expected to have the same potential for formation of detectable PAH emissions as direct wood-fired rotary and tube dryers, which operate at higher temperatures under more turbulent conditions. Upon further consideration in response to these comments, we are not finalizing the proposed 3xRDL limit for wood-fired softwood veneer dryers and instead are relying on the burner tune-up standards included in the rule to limit the potential for PAH emissions from wood-fired softwood veneer dryers. However, we require that wood-fired softwood veneer dryers conduct performance testing for PAH emissions along with the compliance tests required for other combustion-related HAPs. Although we do not expect to find detectable PAH emissions, if PAH are detected, these test results could be used during the next eight-year technology review to determine if revision to a numerical standard is warranted.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter questioned our analysis of D/F toxic equivalency (TEQ) emissions data and proposed that a work practice is justified for D/F from wood-fired dryers because emissions cannot reliably be measured due to the prevalence of non-detects in more than 55 percent of TEQ runs.
                        <SU>34</SU>
                        <FTREF/>
                         The commenter suggested that the EPA reevaluate the RDL as a result of D/F test method improvements in recent years and questioned if the EPA should have compared detected TEQ to the 3xRDL value as was done for the proposal.
                    </P>
                    <FTNT>
                        <P>
                            <SU>34</SU>
                             TEQ of dioxin and furan congeners is relative to the toxicity of 2,3,7,8-tetrachlordibenzo-p-dioxin.
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">EPA Response:</E>
                         We maintain that use of the current RDL is appropriate for this rulemaking. The EPA may consider updating the RDL as additional lab experience and data sets become available for a broader set of emission sources using the revised EPA Method 23, which was not finalized at the time of the PCWP CAA section 114 data collection. However, the EPA agrees with commenters that the RDL is not the appropriate detection value when determining the number of non-detect TEQ runs. We updated our analysis of the detected TEQ to compare to the estimated detection limit (EDL) of 1.8E-02 nanograms per dry standard cubic meter (ng/dscm) instead of 3xRDL to adhere to guidance for evaluating when to establish numerical MACT limits versus establishing work practices.
                        <SU>35</SU>
                        <FTREF/>
                         Upon reanalysis, the percentage of non-detect TEQ runs remained the same as proposed for wood-fired rotary strand dryers (100 percent non-detect), dry rotary dryers (100 percent non-detect), and tube dryers (80 percent non-detect). We no longer found that a substantial majority of green rotary dryer TEQ runs were non-detect upon comparison with the EDL. As a result, we are revising the rule to add a numerical limit for D/F from direct wood-fired green rotary dryers based on the emissions data sets available at proposal.
                    </P>
                    <FTNT>
                        <P>
                            <SU>35</SU>
                             
                            <E T="03">See</E>
                             the June 5, 2014 memorandum entitled 
                            <E T="03">Determination of “non-detect” from EPA Method 29 (multi-metals) and EPA Method 23 (dioxin/furan) test data when evaluating the setting of MACT floors versus establishing work practice standards,</E>
                             available in the docket for this rulemaking.
                        </P>
                    </FTNT>
                    <P>Emissions data for D/F (in terms of TEQ) are available for three out of six direct wood-fired green rotary dryer systems. The UPL MACT floor calculations for existing sources were based on all three systems because fewer than 30 direct wood-fired green rotary dryer systems exist. The UPL MACT floor calculation for new sources was based on the best performing system. The TEQ MACT floor for existing direct wood-fired green rotary dryer systems is 1.3E-09 lb/ODT or 1.7E-01 ng/dscm based on the UPL. The TEQ MACT floor for new direct wood-fired green rotary dryers is 4.4E-10 lb/ODT or 3.7E-02 ng/dscm based on 3xRDL. The 3xRDL value was substituted for the UPL in the new source MACT floor to ensure that the standards are established at the minimum level at which emissions can be measured reliably. The TEQ MACT floors are based on dryers that already have PM and organic HAP controls in series. The burner tune-up requirements required for all direct-fired PCWP dryers are expected to help with meeting the TEQ MACT floors. No options more stringent than the MACT floors were identified for existing or new sources. No reductions in TEQ emissions were estimated for existing or new wood-fired green rotary dryer systems because they are expected to meet the MACT floor with baseline controls and proper tuning.</P>
                    <HD SOURCE="HD3">3. What Combustion HAP Standards Are We Finalizing for Direct Wood-Fired Dryers</HD>
                    <P>
                        Table 3 of this preamble summarizes the MACT emission limits being finalized for direct wood-fired PCWP dryers.
                        <PRTPAGE P="41418"/>
                    </P>
                    <GPOTABLE COLS="5" OPTS="L2,nj,p7,7/8,i1" CDEF="s100,r50,r50,r50,r50">
                        <TTITLE>
                            Table 3—Final Emission Limits for Combustion-Related HAP for Direct Wood-Fired PCWP Dryers 
                            <E T="01">
                                <SU>e</SU>
                            </E>
                        </TTITLE>
                        <BOXHD>
                            <CHED H="1">PCWP Dryer</CHED>
                            <CHED H="1">
                                PM (non-Hg HAP metal) limit 
                                <SU>a</SU>
                            </CHED>
                            <CHED H="1">
                                Hg limit 
                                <SU>a</SU>
                            </CHED>
                            <CHED H="1">
                                HCl limit 
                                <SU>a</SU>
                            </CHED>
                            <CHED H="1">
                                PAH limit 
                                <SU>a</SU>
                                 
                                <SU>b</SU>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Rotary strand dryer—existing</ENT>
                            <ENT>9.9E-02 lb/ODT or 3.6E-03 gr/dscf</ENT>
                            <ENT>1.7E-05 lb/ODT or 8.4E-04 mg/dscm</ENT>
                            <ENT>5.8E-03 lb/ODT or 1.5E-01 mg/dscm</ENT>
                            <ENT>1.1E-04 lb/ODT or 9.9E-03 mg/dscm.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Rotary strand dryer—new</ENT>
                            <ENT>5.6E-02 lb/ODT or 1.3E-03 gr/dscf</ENT>
                            <ENT>1.7E-05 lb/ODT or 8.4E-04 mg/dscm</ENT>
                            <ENT>1.7E-03 lb/ODT or 9.0E-02 mg/dscm</ENT>
                            <ENT>1.8E-05 lb/ODT or 1.5E-03 mg/dscm.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Green rotary dryer—existing</ENT>
                            <ENT>
                                2.9E-01 lb/ODT or
                                <LI>5.2E-03 gr/dscf</LI>
                            </ENT>
                            <ENT>1.5E-05 lb/ODT or 1.3E-03 mg/dscm</ENT>
                            <ENT>1.1E-02 lb/ODT or 1.7 mg/dscm</ENT>
                            <ENT>3.2E-04 lb/ODT or 4.2E-02 mg/dscm.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Green rotary dryer—new</ENT>
                            <ENT>3.7E-02 lb/ODT or 1.3E-03 gr/dscf</ENT>
                            <ENT>1.1E-05 lb/ODT or 8.4E-04 mg/dscm</ENT>
                            <ENT>2.9E-03 lb/ODT or 9.0E-02 mg/dscm</ENT>
                            <ENT>6.2E-05 lb/ODT or 2.9E-03 mg/dscm.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Dry rotary dryer—existing</ENT>
                            <ENT>
                                6.5E-01 lb/ODT or
                                <LI>9.8E-02 gr/dscf</LI>
                            </ENT>
                            <ENT>1.0E-05 lb/ODT or 8.4E-04 mg/dscm</ENT>
                            <ENT>1.1E-03 lb/ODT or 9.0E-02 mg/dscm</ENT>
                            <ENT>4.6E-05 lb/ODT or 4.1E-03 mg/dscm.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Dry rotary dryer—new</ENT>
                            <ENT>6.0E-01 lb/ODT or 4.6E-02 gr/dscf</ENT>
                            <ENT>1.0E-05 lb/ODT or 8.4E-04 mg/dscm</ENT>
                            <ENT>1.1E-03 lb/ODT or 9.0E-02 mg/dscm</ENT>
                            <ENT>2.2E-05 lb/ODT or 2.1E-03 mg/dscm.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Primary tube dryer or secondary tube dryer—existing</ENT>
                            <ENT>
                                3.1E-01 lb/ODT or
                                <LI>3.1E-03 gr/dscf</LI>
                            </ENT>
                            <ENT>3.9E-05 lb/ODT or 1.6E-03 mg/dscm</ENT>
                            <ENT>6.4E-03 lb/ODT or 7.4E-01 mg/dscm</ENT>
                            <ENT>3.0E-04 lb/ODT or 1.6E-03 mg/dscm.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Primary tube dryer or secondary tube dryer—new</ENT>
                            <ENT>9.1E-02 lb/ODT or 1.3E-03 gr/dscf</ENT>
                            <ENT>3.9E-05 lb/ODT or 8.4E-04 mg/dscm</ENT>
                            <ENT>4.3E-03 lb/ODT or 9.0E-02 mg/dscm</ENT>
                            <ENT>3.4E-06 lb/ODT or 1.8E-06 mg/dscm.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Softwood veneer dryer heated zones—existing</ENT>
                            <ENT>
                                7.2E-02 lb/MSF 
                                <FR>3/8</FR>
                                ″ or 1.5E-02 gr/dscf
                            </ENT>
                            <ENT>
                                5.8E-05 lb/MSF 
                                <FR>3/8</FR>
                                ″ or 4.1E-02 mg/dscm
                            </ENT>
                            <ENT>
                                (
                                <SU>c</SU>
                                )
                            </ENT>
                            <ENT>
                                (
                                <SU>d</SU>
                                )
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Softwood veneer dryer heated zones—new</ENT>
                            <ENT>
                                7.2E-02 lb/MSF 
                                <FR>3/8</FR>
                                ″ or 1.5E-02 gr/dscf
                            </ENT>
                            <ENT>
                                5.8E-05 lb/MSF 
                                <FR>3/8</FR>
                                ″ or 4.1E-02 mg/dscm
                            </ENT>
                            <ENT>
                                (
                                <SU>c</SU>
                                )
                            </ENT>
                            <ENT>
                                (
                                <SU>d</SU>
                                )
                            </ENT>
                        </ROW>
                        <TNOTE>
                            <SU>a</SU>
                             lb/ODT = pounds per oven dried ton, gr/dscf = grains per dry standard cubic foot, mg/dscm = milligrams per dry standard cubic meter
                        </TNOTE>
                        <TNOTE>
                            <SU>b</SU>
                             Naphthalene was not included in the final PAH limits.
                        </TNOTE>
                        <TNOTE>
                            <SU>c</SU>
                             HCl was not detected.
                        </TNOTE>
                        <TNOTE>
                            <SU>d</SU>
                             A burner-tune up standard applies. See section III.B of this preamble for details.
                        </TNOTE>
                        <TNOTE>
                            <SU>e</SU>
                             A burner-tune up standard applies for D/F emissions for all wood-fired PCWP dryers except green rotary dryers which have a numerical D/F limit discussed in section III.B of this preamble.
                        </TNOTE>
                    </GPOTABLE>
                    <P>We are modifying the proposed PAH limits to not include naphthalene. We are not finalizing the proposed PAH limits from softwood veneer dryers and instead are requiring PAH testing to be included in the performance tests of these dryers in addition to the burner tune-up standard. In addition to the limits presented in Table 3 of this preamble, we are revising the rule to add D/F limits for direct wood-fired green rotary dryers based on reanalysis of the D/F data. In addition to adjustments stemming from public comments, we removed data from MACT floor calculations if they were collected from systems that ceased operations since the pre-proposal analysis was completed. This adjustment affected some limits and some mass per production based 3xRDL values. We also updated PM 3xRDL values to reflect the most recent revision to these values.</P>
                    <HD SOURCE="HD2">C. MACT Standards for Lumber Kilns</HD>
                    <P>
                        As explained in the May 2023 proposal, the EPA did not identify any lumber kilns with add-on air pollution controls.
                        <SU>36</SU>
                        <FTREF/>
                         We explained that the EPA, as well as State permitting authorities, have evaluated the possibility of capturing and controlling emissions from lumber kilns and in each case concluded that capture and control of lumber kiln emissions is not technically feasible or cost effective for VOC emissions from batch or continuous kilns, and that these previous conclusions are equally relevant for capture and control of HAP. The EPA proposed a work practice standard for lumber kilns based on the criteria in CAA section 112(h), which states that if it is not feasible in the judgment of the Administrator to prescribe or enforce an emission standard for control of a HAP, the Administrator may, in lieu thereof, promulgate a design, equipment, work practice, or operational standard, or combination thereof, which in the Administrator's judgment is consistent with the provisions of CAA section 112(d).
                    </P>
                    <FTNT>
                        <P>
                            <SU>36</SU>
                             88 FR 31867-71 (May 18, 2023).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">1. What lumber kilns standards did we propose?</HD>
                    <P>
                        To reduce HAP from lumber kilns, we proposed a work practice consisting of four elements: (1) operation and maintenance (O&amp;M) plan for all kilns to maintain the integrity of lumber kiln internal air flow and heat distribution components (
                        <E T="03">e.g.,</E>
                         baffles, fans, vents, heating coils, temperature sensors) to provide as uniform a temperature and air flow as reasonably possible; (2) annual burner tune-up for direct-fired kilns to reduce the potential for combustion-related HAP emissions beyond the reduction in these emissions that results from minimizing lumber over-drying; (3) a work practice option in which all kilns limit over-drying by operating below a temperature set point, conducting in-kiln moisture monitoring, or following a site-specific plan (for temperature and lumber moisture monitoring); and (4) minimum kiln-dried lumber moisture content limits below which lumber is considered to be over-dried lumber for all kilns for purposes of the PCWP NESHAP. The May 2023 proposal described each of these elements in detail.
                        <SU>37</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>37</SU>
                             
                            <E T="03">See</E>
                             the June 1, 2026 memorandum entitled 
                            <E T="03">Revised Development of National Emission Standards for Hazardous Air Pollutant Emission Standards for Lumber Drying Kilns,</E>
                             available in the docket for this rulemaking.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2. What comments did we receive on the proposed lumber kiln standards?</HD>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter argued that the EPA has not shown infeasibility to justify work practice standards over numeric standards for limiting over-drying of lumber at lumber kilns. Other commenters agreed with the EPA's determination that it is not feasible to prescribe or enforce emissions standards for lumber kilns.
                    </P>
                    <P>
                        <E T="03">EPA response:</E>
                         The EPA determined work practice standards are appropriate because the total volume of emissions cannot be emitted through a conveyance that is designed and constructed to emit or capture HAP emissions. Furthermore, direct measurement of flow rate from batch kilns is not technically feasible because of the numerous vents and changing flow direction. Similarly, continuous dry kilns (CDKs) have fugitive emissions from their openings that cannot be eliminated while allowing for lumber to enter and exit the kiln. Therefore, the EPA maintains work practice standards for kilns are justified and establishing numerical limits for kilns is not feasible. The work practices included in the final rule are justified under CAA section 112(h) and reflect the maximum degree of emission reduction achieved by existing lumber 
                        <PRTPAGE P="41419"/>
                        kilns and the degree of reduction that is achievable based on the EPA's review and analysis of available information.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Commenters supported the inclusion of O&amp;M plans for kilns but suggested edits to plan requirements. Commenters noted components covered by the O&amp;M plan should not be limited to those listed in the May 2023 proposal; objected to the proposed charge optimization practices to promote uniformity in lumber charged into the kiln (
                        <E T="03">e.g.,</E>
                         sizing, sorting, stickering, conditioning); requested to be allowed additional time to complete corrective actions; and requested that the annual kiln inspection be conducted within 13 months of the previous inspection.
                    </P>
                    <P>Similarly, a commenter requested that the EPA allow burner tune-ups to be performed every 13 months instead of every 12 months to help with process operation or personnel scheduling issues. The commenter also requested that additional language be added to 40 CFR 63.2271(c)(2) to specify that any cleaning, repairs, or replacements must be initiated within 30 days, to remove any interpretation that corrective action must be initiated immediately. This timeframe is consistent with 40 CFR 63.2253(a)(3)(ii) for initiation of the corrective actions identified during the annual lumber kiln integrity inspection in the O&amp;M plan. The commenter did not propose a specific completion timeframe.</P>
                    <P>
                        <E T="03">EPA response:</E>
                         The EPA agrees that facilities may need an additional month to perform corrective action and in the burner tune-up compliance schedule to accommodate process operations and personnel scheduling issues. In response to these comments, the EPA revised the O&amp;M plan language. We also revised the rule to allow inspections to occur no later than 13 months after the previous inspection and added language for allowing submittal of a written request to the delegated authority for completing corrective actions after 180 days In response to the commenter's requests, the EPA revised the final rule to allow annual tune-ups and burner/grate inspections to be performed no more than 13 months after the previous tune-up, instead of every 12 months. To address the commenter's concerns regarding the current rule language being silent on the required timeframe of corrective actions and potential delays due to availability of parts, the EPA revised 40 CFR 63.2271(c)(2) to clarify that any corrective action taken as part of the tune-up/inspection must be initiated within 30 days and completed within 180 days following the annual tune-up/inspection identifying the need for the corrective action. The EPA also added language specifying if additional time is necessary to complete corrective actions, an extension request may be submitted through the delegated authority consistent with the O&amp;M requirements.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Commenters stated that the “temperature set point” option under the proposed work practices should be referred to as the “temperature limit” option. According to the commenter, the EPA has proposed these temperature limits as “temperature set points” but compliance with the proposed temperature set point option would be based on the actual kiln dry bulb temperature readings according to 40 CFR 63.2269(m) and 40 CFR 63.2270(h)(1).
                    </P>
                    <P>Commenters also requested that compliance with the maximum dry bulb temperatures under this work practice option be demonstrated with a longer averaging period of at least 24 hours, daily or batch to accommodate temperature variation instead of with a three-hour block average as proposed. The commenters noted that shorter averaging periods are impacted by routine temperature fluctuations in the kiln, such as temperature increases during fan reversals, which are a normal part of kiln operation and not indicative of over-drying. They also noted that facilities hold title V operating permits with 24-hour averaging periods for temperature monitoring.</P>
                    <P>
                        Commenters requested that the EPA replace the “in-kiln moisture measurement” option with a hybrid option involving both temperature and moisture measurement. The commenters stated that most facilities monitor lumber moisture content after the lumber exits the kiln and cools, per industry guidance. The commenters suggested a hybrid option could apply to most lumber kilns conducting higher temperature drying such as those in the U.S. Southeast. The commenters recommended maximum dry bulb temperature limits of 240 degrees Fahrenheit (°F) for batch indirect-fired kilns, 250 °F for batch direct-fired kilns, and 260 °F for indirect- and direct-fired continuous kilns. Because the hybrid work practice option would include higher temperature limits, commenters suggested that facilities could also monitor moisture content to meet the minimum moisture content limits in the rule. However, under the hybrid option, the moisture content could be measured either in the kiln or after the lumber has exited the kiln (
                        <E T="03">e.g.,</E>
                         at the planer).
                    </P>
                    <P>
                        <E T="03">EPA response:</E>
                         As a result of these comments, to avoid confusion and clarify intent of the proposed standard, the EPA modified the name of this option in the final rule to refer to a “temperature limit” rather than a “temperature set point”. The EPA is revising the final rule to require a batch cycle average for batch kilns and a daily (24-hour) block average for continuous kilns for the maximum dry bulb temperature to demonstrate compliance with the work practice standard.
                    </P>
                    <P>The EPA also agrees with the commentator's request for a hybrid compliance option involving both temperature and moisture measurement. Using the large amount of monitoring data generated at the planer, along with kiln dry bulb temperature is a robust approach to reduce over-drying and is consistent with practices in place at lumber mills. Therefore, we revised the final rule to replace the in-kiln moisture measurement option with the requested hybrid option.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Relative to the “site-specific plan” work practice option, commenters requested that the EPA extend the deadline to submit site-specific plans from the 180 days (as proposed) to 18 months to allow time for facilities to properly develop an effective site-specific plan and gather data to support the elements of the plan. One commenter noted that developing a site-specific plan for lumber kilns could reasonably take more than 12 months.
                    </P>
                    <P>
                        <E T="03">EPA response:</E>
                         The EPA agrees with the commenter that 18 months will allow facilities to properly develop a site-specific plan, therefore, the deadline is being extended to 18 months versus the proposed 180 days (6 months) in the final rule. The EPA acknowledges this extension will shorten the period for delegated authorities to review and approve the plans for over 140 lumber kilns in operation.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter supported the EPA's general methodology of defining over-dried lumber through the proposed lumber minimum moisture content limits of the proposed Table 11 to Subpart DDDD of Part 63 (“Table 11”). The commenter also agreed with the EPA's description of maximum lumber moisture grade in principle but requested that the term “moisture specification” be used throughout the rule rather than “moisture grade.”
                    </P>
                    <P>
                        <E T="03">EPA response:</E>
                         The EPA agreed and changed the term “moisture grade” to “moisture specification” to eliminate potential confusion.
                        <PRTPAGE P="41420"/>
                    </P>
                    <HD SOURCE="HD3">3. What lumber kiln standards are we finalizing?</HD>
                    <P>
                        After considering comments,
                        <SU>38</SU>
                        <FTREF/>
                         we are finalizing work practice standards for lumber kilns in 40 CFR 63.2241(e) to reduce HAP emissions by minimizing lumber over-drying. The final work practice consists of four elements: (1) O&amp;M plan for all kilns; (2) annual burner tune-up for direct-fired kilns; (3) a choice of three work practice options including a temperature limit option, hybrid option involving higher temperature limit and lumber moisture monitoring, or site-specific plan for temperature and lumber moisture monitoring; and (4) minimum kiln-dried lumber moisture content limits below which lumber is considered to be over-dried lumber for all kilns for purposes of the PCWP NESHAP.
                    </P>
                    <FTNT>
                        <P>
                            <SU>38</SU>
                             
                            <E T="03">See National Emission Standards for Hazardous Air Pollutants: Plywood and Composite Wood Products (40 CFR part 63, subpart DDDD), Response to Public Comments on May 18, 2023 Proposed Amendments,</E>
                             available in the docket for this rulemaking for a complete list of comments and responses.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">D. MACT Standards for Process Units With Organic HAP Emissions</HD>
                    <P>
                        The EPA is finalizing MACT standards for organic HAP emissions from process units that had “no-control” MACT determinations in the 2004 rule that were vacated in 2007. In addition to lumber kilns, these process units include various RMH process units, atmospheric refiners, stand-alone digesters, fiber washers, fiberboard mat dryers at existing sources, hardboard press predryers at existing sources, and log vats. Some of these process units are already subject to new source HAP standards in the PCWP NESHAP, including fiberboard mat dryers, hardboard press predryers, and reconstituted wood product board coolers (which are a type of RMH unit) at new and reconstructed sources. Therefore, limits for these new and reconstructed sources do not need to be established in response to the partial remand and vacatur. Mixed PCWP process streams routed to HAP control devices subject to the current HAP emission limits in Table 1B are also already subject to the PCWP NESHAP. Sections III.D.1 through 6 summarize the final standards for process units with unregulated organic HAP emissions that were subject to the partial remand and vacatur, the key comments received and our responses, and our final decisions and rationale on the standards for this final action.
                        <SU>39</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>39</SU>
                             
                            <E T="03">See</E>
                             the RTC document and the June 1, 2026 memorandum entitled 
                            <E T="03">Revised Development of Emission Standards for Remanded Process Units Under the Plywood and Composite Wood Products NESHAP,</E>
                             available in the docket for this rulemaking.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">1. RMH Process Units</HD>
                    <P>
                        RMH process units within the PCWP affected source include resin tanks, softwood and hardwood plywood presses, engineered wood product presses and curing chambers, blenders, formers, finishing saws, finishing sanders, panel trim chippers, reconstituted wood product board coolers (at existing affected sources), hardboard humidifiers, and onsite wastewater treatment operations specifically associated with PCWP manufacturing. These process units handle resin or resinated wood material downstream of the point in the PCWP process where resin is applied. The potential for HAP emissions from RMH process units relates to the material being processed (
                        <E T="03">i.e.,</E>
                         resin and wood).
                    </P>
                    <HD SOURCE="HD3">a. What RMH standards did we propose?</HD>
                    <P>As explained in the proposal, RMH process units are not designed and constructed in a way that allows for HAP emissions capture or measurement. Therefore, the EPA proposed work practice standards for RMH process units under CAA section 112(h) to address their resin-related emissions and wood-related emissions.</P>
                    <P>
                        We proposed work practice standards to require new and existing facilities with RMH process units to (i) use only a non-HAP resin,
                        <SU>40</SU>
                        <FTREF/>
                         or (ii) use a resin with a maximum true vapor pressure of less than or equal to 5.2 kilopascals (kPa), which is equal to 0.75 pounds per square inch absolute (psia),
                        <SU>41</SU>
                        <FTREF/>
                         or (iii) use a combination of resins meeting either (i) or (ii). Facilities with RMH process units would also be required to process wood material that was purchased pre-dried to a moisture content of no more than 30 percent (weight percent, dry basis) or that has been dried in a dryer located at the PCWP facility. The proposed requirement to process dried wood did not apply for wet formers and wastewater operations.
                    </P>
                    <FTNT>
                        <P>
                            <SU>40</SU>
                             Defined in 40 CFR 63.2292.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>41</SU>
                             Defined in 40 CFR 63.2292.
                        </P>
                    </FTNT>
                    <P>No options more stringent than the RMH process unit work practices were identified for resin tanks, softwood and hardwood plywood presses, engineered wood product presses and curing chambers, blenders, formers, finishing saws, finishing sanders, panel trim chippers, or hardboard humidifiers at new or existing affected sources, or for reconstituted wood product board coolers at existing affected sources. Reconstituted wood product board coolers at new affected sources are already subject to standards under the PCWP NESHAP, so were not addressed by our proposal.</P>
                    <P>For RMH wastewater operations, the EPA proposed a work practice in addition to the process unit work practice standards that would require facilities with wastewater operations to implement one of the following measures:</P>
                    <P>• Follow the plan required in 40 CFR 63.2268 for wet control devices used as the sole means of reducing HAP emissions from PCWP process units; or</P>
                    <P>• Reduce the volume of wastewater to be processed by reusing or recirculating wastewater in the PCWP process or air pollution control system; or</P>
                    <P>• Store wastewater in a closed system; or</P>
                    <P>• Treat the wastewater by using an onsite biological treatment system, or by routing the wastewater to an offsite POTW or industrial wastewater treatment facility.</P>
                    <HD SOURCE="HD3">b. What comments on our proposed RMH standards did we receive?</HD>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter questioned the justification of work practice standards for RMH process units.
                    </P>
                    <P>
                        <E T="03">EPA response:</E>
                         We maintain that work practices developed under CAA section 112(h) are legally justified and are the appropriate format of standard for RMH process units, because it is not feasible to prescribe or enforce an emission standard for RMH process units.
                        <E T="51">42 43</E>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>42</SU>
                             
                            <E T="03">See</E>
                             the June 1, 2026 memorandum entitled 
                            <E T="03">Revised Development of Emission Standards for Remanded Process Units Under the Plywood and Composite Wood Products NESHAP,</E>
                             available in the docket for this rulemaking.
                        </P>
                        <P>
                            <SU>43</SU>
                             88 FR 31871-76 (May 18, 2023).
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Comment:</E>
                         Other commenters agreed that work practices are justified under CAA section 112(h) but expressed significant concern about the proposed definition of “non-HAP resin.” To reduce implementation uncertainty, the commenters stated that the EPA should focus application of the weight percent limits (0.1 percent for carcinogens and 1 percent for non-carcinogens) on known resin-related HAP and clarify that the limits, which are based on OSHA hazard communication thresholds for reporting, are not cumulative. One commenter also requested that the EPA apply the tiered approach from the amino/phenolic resin NESHAP (based on storage tank capacity) for purposes of setting the vapor pressure limits in the PCWP NESHAP. The commenters asserted that these changes are needed to properly scope the standards to avoid unintended consequences and unaccounted for 
                        <PRTPAGE P="41421"/>
                        market impacts to upstream suppliers of resins. Commenters also requested whether the process under 40 CFR 63.6(g) for approval of an alternative non-opacity emission standard could be used in specific situations where it is not feasible to use a non-HAP resin or a resin that meets the vapor pressure standards.
                        <SU>44</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>44</SU>
                             For a complete list of comments and responses on this subject 
                            <E T="03">see National Emission Standards for Hazardous Air Pollutants: Plywood and Composite Wood Products (40 CFR part 63, subpart DDDD), Response to Public Comments on May 18, 2023 Proposed Amendments,</E>
                             available in the docket for this rulemaking.
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">EPA response:</E>
                         The EPA agrees that the definitions around non-HAP resin and the resin requirements require further clarification. The EPA also agrees that the vapor pressure requirements should account for different tank sizes, as suggested by commenters. In this final action we are clarifying the definition of “non-HAP resin” and “maximum true vapor pressure” and incorporating a tiered limits for vapor pressure based on resin tank size.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         We received numerous comments opposing the proposed wastewater work practice options. Among other issues, commenters asserted that the definition of “wastewater operations” as proposed goes beyond the PCWP affected source, the EPA did not account for the costs associated with this overly broad definition, and the EPA lacked emissions information to justify the wastewater work practice.
                    </P>
                    <P>
                        <E T="03">EPA response:</E>
                         The EPA also agrees that, given the broad set of operations included under the proposed wastewater work practice, most of which are not part of the affected source as defined in the current rule, we lacked the authority to impose requirements beyond the defined affected source.
                    </P>
                    <HD SOURCE="HD3">c. What RMH standards are we finalizing?</HD>
                    <P>
                        As a result of the comments, we are updating the proposed definition of “non-HAP resin” in the final rule to focus on the known resin-related HAP and to clarify how the weight percent limits are to be applied. In the final rule, non-HAP resin is defined as “a resin that contains less than 0.1 percent by mass of formaldehyde and less than 1.0 percent by mass each of phenol, methanol, and MDI.” Using this definition and following the intent of the May 2023 proposal for the weight percentages to be applied for each HAP, an example resin with 0.5 weight percent phenol and 0.7 weight percent methanol would be considered a non-HAP resin because the 1.0 weight percent threshold is applied to each HAP. Under the vapor pressure option, the final standard contains tiered limits for vapor pressure based on resin tank size consistent with the amino/phenolic resin NESHAP and updating the definition of “maximum true vapor pressure” for the final rule.
                        <SU>45</SU>
                        <FTREF/>
                         The final vapor pressure limits for resins received at the PCWP facility are 5.2 kPa (0.75 psia) for resins stored in resin tanks with capacity greater than or equal to 40,000 gallons and 13.1 kPa (1.9 psia) for resins stored in one or more resin tanks with capacity less than 40,000 gallons. Finally, we note that under the PCWP NESHAP facilities can already request approval of an alternative standard following the process set forth under 40 CFR 63.6(g).
                        <SU>46</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>45</SU>
                             40 CFR part 63, subpart OOO.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>46</SU>
                             
                            <E T="03">See</E>
                             40 CFR part 63, subpart DDDD, table 10.
                        </P>
                    </FTNT>
                    <P>Considering the EPA's proposed overly broad definition of wastewater operations that extends beyond the affected source and that no HAP emission reductions are estimated to be achieved with the wastewater work practices, the EPA is not finalizing the four work practice options for “wastewater operations” that were proposed in addition to the work practice standards for RMH process units. For the final rule, the term “wastewater operations” is being replaced with the wording from the definition of affected source “onsite wastewater treatment operations specifically associated with PCWP manufacturing,” in the definition of RMH process units. The resin-related RMH process unit standards apply for “onsite wastewater treatment operations specifically associated with PCWP manufacturing.”</P>
                    <HD SOURCE="HD3">2. Atmospheric Refiners</HD>
                    <P>
                        Atmospheric refiners operate with continuous infeed and outfeed of wood material and under atmospheric pressure for refining (rubbing, grinding, or milling) wood material into fibers or particles used in particleboard or dry formed hardboard production. Atmospheric refiners are further characterized based on their placement before or after dryers in the PCWP production process. In addition to a definition of “atmospheric refiner,” we proposed definitions of “dried wood atmospheric refiner” and “green wood atmospheric refiner” to distinguish atmospheric refiners following dryers in the PCWP process (
                        <E T="03">e.g.,</E>
                         dried wood atmospheric refiners) from other atmospheric refiners (
                        <E T="03">e.g.,</E>
                         green wood atmospheric refiners).
                    </P>
                    <HD SOURCE="HD3">a. What atmospheric refiner standards did we propose?</HD>
                    <P>We proposed numerical emission limits for existing and new atmospheric refiners of each type developed pursuant to CAA sections 112(d)(2) and (3) using performance data collected from the CAA section 114 survey of PCWP facilities in 2022. The proposed standards were based on the MACT floor. More-stringent beyond-the-floor options were analyzed and rejected due to the high costs relative to the emission reductions that would be achieved, energy usage, and other non-air quality environmental impacts. Although the more stringent beyond-the-floor options were not proposed, we proposed to include a provision in 40 CFR 63.2240(d)(6) to give facilities the option of complying with the more stringent limits in Table 1B in place of the proposed limits in the proposed Table 1C to Subpart DDDD of Part 63 (“Table 1C”) if they choose to meet the more stringent option.</P>
                    <HD SOURCE="HD3">b. What comments on the proposed atmospheric refiner standards did we receive?</HD>
                    <P>
                        <E T="03">Comment:</E>
                         We received several comments noting that the numerical standards were not necessary and suggested using a work practice. Commenters also requested a concentration-based compliance option as well as revisions to the proposed definitions and classifications for atmospheric refiners.
                    </P>
                    <P>
                        <E T="03">EPA response:</E>
                         The EPA maintains that work practice standards cannot be established for atmospheric refiners under CAA section 112(h) because emissions can be captured, conveyed, and measured. However, the EPA agrees that an additional concentration-based compliance option and clarifying language is needed to reduce uncertainty and confusion with the proposed atmospheric refiner standards.
                    </P>
                    <HD SOURCE="HD3">c. What atmospheric refiner standards are we finalizing?</HD>
                    <P>
                        Due to the requirement for EPA to establish emission standards for atmospheric refiners under CAA sections 112(d)(2) and (3), we are finalizing the numerical standards for atmospheric refiners as proposed. In response to comments received, we are adding concentration-based standards, in addition to the lb/ODT standards. We are modifying the proposed definition for atmospheric refiners to remove reference to wet-formed hardboard and fiberboard. We are also redefining the proposed “green wood atmospheric” and “dried wood atmospheric refiner,” 
                        <PRTPAGE P="41422"/>
                        terms as “multipurpose atmospheric refiner” and “post-dryer atmospheric refiner,” respectively, to eliminate confusion surrounding references to “green” and “dried” wood when the distinction to be made hinges on placement of a subset of refiners after dryers in the PCWP process. In the revised rule, all atmospheric refiners that are not “post-dryer atmospheric refiners” are defined as “multipurpose atmospheric refiners.” These definitional changes do not alter the proposed MACT floors for green and dried wood atmospheric refiners because they are consistent with how the MACT floors and MACT were determined.
                    </P>
                    <P>
                        The final total HAP standards for multipurpose atmospheric refiners are 1.2E-01 lb/ODT or 15 parts per million volume, dry (ppmvd) for existing units and 2.4E-03 lb/ODT or 3.3 ppmvd for new units. The final standards for existing post-dryer atmospheric refiners are 4.1E-03 lb/ODT or 8.5E-01 ppmvd, and 3.3E-03 lb/ODT or 6.5E-01 ppmvd for new units.
                        <SU>47</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>47</SU>
                             More information on development of these standards can be found in the memorandum entitled 
                            <E T="03">Revised Development of Emission Standards for Remanded Process Units Under the Plywood and Composite Wood Products NESHAP,</E>
                             available in the docket for this rulemaking, and in our responses to comments in the RTC document, also available in the docket for this rulemaking.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">3. Stand-Alone Digesters and Fiber Washers</HD>
                    <P>Stand-alone digesters are used to steam or water soak wood chips so that they may be easily rubbed apart or ground into fibers in atmospheric separate refiners that operate downstream from the digesters. Stand-alone digesters have batch operating cycles that differ from pressurized refiner steaming vessels (sometimes called “digesters”) used to preheat wood chips prior to pressurized refining. Pressurized refiner steaming vessels have continuous infeed and outfeed without pressure release between the steaming vessel and refiner part of the pressurized refiner.</P>
                    <P>Fiber washers are units in which water-soluble components of wood (hemicellulose and sugars) that have been produced during digesting and refining are removed from the wood fiber before the fiber is used in fiberboard or hardboard production. In a fiber washer, wet fiber leaving a refiner is further diluted with water and then passed over a filter, leaving the cleaned fiber on the surface.</P>
                    <P>One wet/dry process hardboard facility operated a batch stand-alone digester and a fiber washer at the time of the May 2023 proposal. This facility has since ceased operations. No PCWP affected sources are expected to operate stand-alone digesters or fiber washers, but the possibility cannot be entirely ruled out. Thus, standards for these process units are being finalized in this action. Both process units meet the criteria under CAA section 112(h)(2)(B) for establishing a work practice standard because there are technological and economic limitations to measuring emissions.</P>
                    <HD SOURCE="HD3">a. What standards for stand-alone digesters and fiber washers were proposed?</HD>
                    <P>
                        The potential for HAP emissions from stand-alone digesters is reduced when: (1) clean steam from the boiler is used for the digestion process (as opposed to steam potentially contaminated with HAP being reused from another process); and (2) HAP-containing or wood pulping chemicals 
                        <SU>48</SU>
                        <FTREF/>
                         are not added to the digestion process. Thus, we proposed a work practice requiring clean steam to be used in the digesters and prohibiting addition of HAP-containing or wood pulping chemicals to the digestion process. No regulatory options more stringent than the work practice were identified for further consideration for existing or new stand-alone digesters.
                    </P>
                    <FTNT>
                        <P>
                            <SU>48</SU>
                             Wood pulping chemicals added to dissolve lignin in wood include sodium sulfide (Na
                            <E T="52">2</E>
                            S) in combination with sodium hydroxide (NaOH), sulfurous acid (H
                            <E T="52">2</E>
                            SO
                            <E T="52">3</E>
                            ) compounds, or sodium sulfite (Na
                            <E T="52">2</E>
                            SO
                            <E T="52">3</E>
                            ) in combination with sodium carbonate (Na
                            <E T="52">2</E>
                            CO
                            <E T="52">3</E>
                            ). Lignin removal is not necessary in the hardboard industry where natural lignin helps bind wood fibers in processes where synthetic resins are not used.
                        </P>
                    </FTNT>
                    <P>We proposed a work practice for PCWP fiber washers to use fresh water for washing and processing fiber without addition of wood pulping or HAP-containing chemicals.</P>
                    <HD SOURCE="HD3">b. What comments on the proposed stand-alone digester and fiber washer standards did we receive?</HD>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter explained their wet end process uses a large amount of water, which is recycled to optimize the volume of water discharged from the process and balance pH. The commenter requested the EPA eliminate the requirement to use only fresh water for washing because it is technically infeasible.
                    </P>
                    <P>
                        <E T="03">EPA response:</E>
                         The EPA agrees with the commentator's argument that using fresh water is infeasible due to process design and the increase in volume of wastewater that would result. Therefore, we are not finalizing the requirement to use only fresh water for washing in the work practice standards for fiber washers.
                    </P>
                    <HD SOURCE="HD3">c. What standards for stand-alone digesters and fiber washers are we finalizing?</HD>
                    <P>We are finalizing the proposed definition of “stand-alone digester” and an amendment to the definition of “pressurized refiner” in 40 CFR 63.2292 to distinguish between these two process units. Pressurized refiners are already subject to emission standards in the PCWP NESHAP. We are amending the current definition of pressurized refiner to state that: “Pressurized refiners include steaming vessels that operate under pressure to continuously feed and vent through the pressurized refiner.” We are finalizing the stand-alone digester work practice requiring clean steam to be used in the digesters and prohibiting addition of HAP-containing or wood pulping chemicals to the digestion process. Initial and continuous compliance with the stand-alone digester work practice must be demonstrated through recordkeeping.</P>
                    <P>We are finalizing the work practice requirement to process fiber without addition of HAP-containing or wood pulping chemicals. Initial and continuous compliance with the fiber washer work practice must be demonstrated through recordkeeping. No regulatory options more stringent than the work practice were identified for further consideration for existing or new fiber washers. No new fiberboard or hardboard mills are projected. Therefore, no new PCWP affected sources are expected to use fiber washers.</P>
                    <HD SOURCE="HD3">4. Fiberboard Mat Dryers and Press Predryers at Existing Sources</HD>
                    <P>Fiberboard mat dryers are conveyor-type dryers used to dry wet-formed fiber mats. Press predryers are used in the wet/dry hardboard process to remove additional moisture from the hardboard mat after it exits the fiberboard mat dryer before the mat enters the hardboard press. The PCWP NESHAP already contains standards for fiberboard mat dryers (heated zones) and hardboard press predryers at new sources.</P>
                    <HD SOURCE="HD3">a. What Fiberboard mat dryers and press predryers did we propose for existing sources?</HD>
                    <P>
                        The EPA proposed standards for the heated zones of existing fiberboard mat dryers and hardboard press predryers. For the fiberboard mat dryer (heated zones), the proposed MACT floor is 4.9E-02 lb total HAP per MSF on a 1/8-inch thickness basis. The MACT floor 
                        <PRTPAGE P="41423"/>
                        for the press predryer is 8.0E-02 lb total HAP per MSF on a 1/8-inch thickness basis. The emission limit for each dryer was calculated using HAP test data collected in 2022 through a CAA section 114 survey. These MACT floor calculations were based on limited data sets.
                        <SU>49</SU>
                        <FTREF/>
                         The units that were tested in the 2022 survey were at the same wet/dry hardboard facility discussed in section III.D.3, which has ceased operations since the May 2023 proposal was published. The EPA considered beyond-the-floor regulatory options for both dryers, but these options were rejected because of the high costs relative to the HAP emission reduction that could be achieved, energy usage, and other non-air quality environmental impacts.
                    </P>
                    <FTNT>
                        <P>
                            <SU>49</SU>
                             
                            <E T="03">See</E>
                             the memorandum entitled 
                            <E T="03">Approach for Applying the Upper Prediction Limit to Limited Datasets,</E>
                             available in the docket for this rulemaking, for details on the EPA's review of the data sets and conclusions regarding appropriateness of the proposed MACT floors.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. What comments did the EPA receive on the proposed standards for Fiberboard mat dryers and press predryers?</HD>
                    <P>
                        <E T="03">Comment:</E>
                         The EPA received comments supporting and opposing the proposed emission limits for fiberboard mat dryers and press predryers. One commenter recommended that the EPA rely on data from sources with controls that have ceased operation to set MACT standards instead of data from the only remaining units in operation at the time of proposal, which were uncontrolled. The commenter argued that the EPA contravenes the CAA by setting weaker standards using data from this single source when previously existing sources were better performing. A different commenter supported the proposed MACT analysis and emission limits and requested a change to the definition of fiberboard mat dryer to clarify applicability for units producing wet/dry hardboard. Another commenter asked the EPA to specify the emission standards for existing fiberboard mat dryers and press predryers in Table 1C on both a 1/8-inch and 1/2-inch basis for consistency with Table 1A to Subpart DDDD of Part 63 (“Table 1A”) and asked the Agency to clarify the dates in Table 1C.
                    </P>
                    <P>
                        <E T="03">EPA Response:</E>
                         We disagree with the commenter's statement that development of these limits contravenes the CAA. According to CAA section 112(d)(3)(B), the MACT floor for existing sources is the average emission limitation achieved by the best performing five sources (for which the Administrator has or could reasonably obtain emissions information) in a category or subcategory with fewer than 30 sources. The D.C. Circuit has affirmed that CAA section 112 “says nothing about what data the Agency should use to calculate emission standards.” 
                        <SU>50</SU>
                        <FTREF/>
                         The EPA followed the law when developing the MACT floors for fiberboard mat dryers and hardboard press predryers based on the emission data from the source remaining in operation at the time of the 2022 section 114 survey.
                        <SU>51</SU>
                        <FTREF/>
                         The most complete and relevant data on fiberboard mat dryer and press predryer emissions were collected during this survey. As noted in this section, the EPA did consider beyond-the-floor measures for both the fiberboard mat dryer and press predryer based on control technology and rejected these options for both dryers because of the high costs relative to the HAP emission reduction that could be achieved, energy usage, and other non-air quality environmental impacts.
                    </P>
                    <FTNT>
                        <P>
                            <SU>50</SU>
                             
                            <E T="03">Nat'l Lime Ass'n</E>
                             v. 
                            <E T="03">EPA,</E>
                             233 F.3d 625, 632-33 (D.C. Cir. 2000).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>51</SU>
                             The Agency is proposing elsewhere to rely on information from the time of the original NESHAP rulemaking to avoid unfairly subjecting previously unregulated emission points to more stringent standards than would have been adopted if the EPA had set MACT floors in the 2004 rule. 
                            <E T="03">See</E>
                             91 FR 21672 (Apr. 22, 2026). This rulemaking does not raise the same equity concerns because sources are not subject to more stringent standards than would have been adopted in 2004.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. What standards for Fiberboard mat dryers and press predryers are we finalizing?</HD>
                    <P>After considering comments, we are finalizing the proposed standards for existing source fiberboard mat dryers and press predryers as proposed. We modified the proposed Table 1C to include the 1/8-inch limits converted to equivalent values in terms of 1/2-inch. We added a footnote to the table to clarify that the existing source limits are not applicable to new sources, which have their own limits from the 2004 rule in Tables 1A or 1B to Subpart DDDD of Part 63. Regarding the other changes requested by commenters, we clarified the definition fiberboard mat dryer applies to dryers in the wet/dry hardboard process.</P>
                    <HD SOURCE="HD3">5. Log Vats</HD>
                    <P>Log vats are used to condition logs before they are cut into veneer or wood strands. Hot water vats in which logs are immersed are often open to the atmosphere. In log steaming or “chest” vats, logs are placed in the vat in batches, the door is closed, and steam (which condenses in the vat) along with hot water sprays are used to condition the logs for a specified time before the logs are removed for veneer production. The EPA is finalizing the proposed definition for “log vat” in 40 CFR 63.2292 that applies to both hot water and log steaming vats.</P>
                    <HD SOURCE="HD3">a. What log vat standards did the EPA propose?</HD>
                    <P>We proposed a work practice standard based on CAA section 112(h)(2)(A) and (B) for log vats at existing or new sources because log vats have neither the proper emissions capture and conveyance ductwork nor stacks where emissions testing could be conducted. The proposed work practice standard would require facilities to: (a) operate each vat using a site-specific target log temperature that does not exceed 212 °F, measured in the water used to soak the logs or in the wood cut at the lathe or stranders; and (b) operate each vat to reduce the potential for fugitive emissions by either: (1) covering at least 80 percent of the vat hot water surface area for soaking vats in which logs are submerged; or (2) keeping doors closed while steam or hot water showers are being applied inside log steaming vats.</P>
                    <HD SOURCE="HD3">b. What comments on the proposed log vat standards did we receive?</HD>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter opposed distinguishing between hot water vats and log steaming vats and questioned the EPA's justification for using work practice standards over numeric standards for log vats. Other commenters agreed log vats are eligible for work practice standards but recommended changes in the proposed work practice standards pertaining to the potential for fugitive emissions. The commenters stated that covering logs in log vats can create health and safety concerns and hinder operations. They noted operators with steam vats already close the doors during steaming/spraying as standard procedures, making this requirement redundant.
                    </P>
                    <P>
                        <E T="03">EPA Response:</E>
                         As discussed in a docketed memorandum, the EPA has concluded that work practice standards for log vats are justified given the technical limitations and measurement infeasibilities.
                        <SU>52</SU>
                        <FTREF/>
                         The EPA has also noted the safety concerns raised by commenters, and agrees that requiring an 80 percent log vat cover would interfere with operations and potentially lead to health and safety concerns.
                    </P>
                    <FTNT>
                        <P>
                            <SU>52</SU>
                             
                            <E T="03">See</E>
                             the June 1, 2026 memorandum entitled 
                            <E T="03">Revised Development of Emission Standards for Remanded Process Units Under the Plywood and Composite Wood Products NESHAP,</E>
                             available in the docket for this rulemaking.
                        </P>
                    </FTNT>
                    <PRTPAGE P="41424"/>
                    <HD SOURCE="HD3">c. What log vat standards are we finalizing?</HD>
                    <P>As a result of the concerns raised by commenters on the proposed work practice standards, we are finalizing the temperature limitation work practice but not the requirement to cover at least 80 percent of the hot water surface or keep doors of log steaming vats closed. This change also eliminates the distinction in hot water and steaming vats.</P>
                    <HD SOURCE="HD3">6. Mixed PCWP Process Streams Regulated at Existing Sources</HD>
                    <P>Some PCWP facilities route emission streams from multiple process units of the same or different types into one shared HAP control system such as a regenerative thermal oxidizer (RTO), regenerative catalytic oxidizer (RCO), biofilter, or process incineration system to meet the compliance options in Table 1B. In a few mixed process arrangements, an emissions stream from a remanded unit was mixed at the inlet to a HAP control device and co-controlled with other process units listed in Table 1B such that the combined emission stream became subject to the Table 1B limits when the control system was initially installed to meet the PCWP NESHAP or as part of the PCWP plant design. Due to the mixing of emissions from each individual type of process unit, the PCWP process stream cannot be distinguished at the inlet or outlet of the control device.  </P>
                    <HD SOURCE="HD3">a. What standards did we propose for mixed process streams?</HD>
                    <P>We proposed a requirement that mixed PCWP process streams from remanded units meeting the compliance options in Table 1B be treated as a separate type of emission stream that remains subject to the Table 1B limits. Mixed PCWP process streams are defined in 40 CFR 63.2292 as an emission stream from a process unit subject to the final amendments that was commingled with emissions stream(s) from process unit(s) subject to the compliance options in Table 1B before July 6, 2026 at an affected source that commenced construction (or reconstruction) on or before May 18, 2023. The definition of “mixed PCWP process stream” refers specifically to a “stream” as opposed to a whole process unit because there can be uncaptured or uncontrolled emissions from a remanded process unit in addition to the captured emission stream from the remanded unit that is routed to the HAP control device as part of a mixed PCWP process stream.</P>
                    <HD SOURCE="HD3">b. What comments on the proposed mixed PCWP process stream limits did we receive?</HD>
                    <P>
                        <E T="03">Comment:</E>
                         Two commenters agreed with the EPA's proposal that mixed PCWP process streams continue to meet compliance options in Table 1B. One commenter requested the Notice of Compliance Status (NOCS) for mixed PCWP process streams be due within a short timeframe after publication in the 
                        <E T="04">Federal Register</E>
                         (
                        <E T="03">e.g.,</E>
                         30 or 60 days) rather than on the date of publication.
                    </P>
                    <P>
                        <E T="03">EPA Response:</E>
                         We acknowledge commenters support for the proposed requirement that mixed PCWP process streams comply with options in Table 1B. We agree that 30 days would allow facilities the necessary time to create and submit their NOCS.
                    </P>
                    <HD SOURCE="HD3">c. What mixed PCWP process stream limits are we finalizing?</HD>
                    <P>In response to these comments, we are finalizing requirements for the mixed PCWP process streams as proposed with the exception that the NOCS shall be due no later than 30 days after the date of publication.</P>
                    <HD SOURCE="HD2">E. MACT Standards for Process Units With MDI Emissions</HD>
                    <P>
                        The EPA is finalizing standards to regulate MDI emissions from reconstituted wood product presses using MDI, tube dryers that blow-line blend MDI resin, and miscellaneous coating operations. Sections III.E.1 through 3 summarize the final standards, the key comments received and our responses, and our final decisions and rationale on the standards for this final action. A complete discussion of changes from the May 2023 proposal can be found in the RTC document and a docketed memorandum.
                        <SU>53</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>53</SU>
                             
                            <E T="03">See</E>
                             the June 1, 2026 memorandum entitled 
                            <E T="03">Revised Regulatory Options for MDI Emissions from Plywood and Composite Wood Products Reconstituted Wood Products Presses, Tube Dryers, and Miscellaneous Coating Operations,</E>
                             available in the docket for this rulemaking.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">1. Reconstituted Wood Product Presses</HD>
                    <HD SOURCE="HD3">a. What reconstituted wood product press MDI standards did we propose?</HD>
                    <P>The EPA proposed MDI emission standards for reconstituted wood product presses that produce OSB and for reconstituted wood product presses that produce particleboard or MDF (PB/MDF). We developed separate standards because product differences affect MDI emissions.</P>
                    <P>For OSB presses, the proposed MACT standards for both new and existing sources are based on 3xRDL for MDI, which exceeded the calculated MACT floor. The 3xRDL values were substituted for the calculated MACT floor to ensure that the standards are established at the minimum level at which emissions can be measured reliably. The proposed MACT standards for new and existing OSB presses are 2.5E-04 lb MDI/MSF 3/4” (1.3E-04 lb/MSF 3/8”) or 2.7E-02 mg MDI/dscm.</P>
                    <P>The proposed MACT floor for existing PB/MDF presses using MDI is 8.4E-04 lb/MSF 3/4” or 2.0E-01 mg MDI/dscm. For new sources, the 3xRDL values exceeded the calculated MACT floor concentration and emission rate. Therefore, the 3xRDL values were used in place of the calculated MACT floor for new source PB/MDF presses using MDI to ensure that the standards are established at the minimum level at which emissions can be measured reliably. For new PB/MDF presses the MDI proposed MACT limit based on the 3xRDL values is 2.3E-04 lb MDI/MSF 3/4” or 2.7E-02 mg MDI/dscm.</P>
                    <P>Considering the low levels of MDI emitted and that reconstituted wood product presses already meet HAP limits in the PCWP NESHAP using robust HAP controls, no regulatory options more stringent than the existing or new source MACT floors for MDI were identified for OSB or PB/MDF reconstituted wood product presses.</P>
                    <HD SOURCE="HD3">b. What comments on the proposed MDI reconstituted wood product press standards did we receive?</HD>
                    <P>
                        <E T="03">Comment:</E>
                         The EPA received comments supporting and opposing subcategorization of reconstituted wood product presses for purposes of limiting MDI.
                    </P>
                    <P>
                        <E T="03">EPA response:</E>
                         The EPA maintains subcategorizing reconstituted wood product presses using MDI by product is within the EPA's authority in CAA section 112(d)(1), which states, “The Administrator may distinguish among classes, types, and sizes of sources within a category or subcategory in establishing standards.” The manner and type of press operation are distinct between products. Depending on the product type (
                        <E T="03">i.e.,</E>
                         OSB, or PB/MDF), presses require different operating temperatures (
                        <E T="03">e.g.,</E>
                         OSB is pressed at higher temperature) and feed stocks (
                        <E T="03">e.g.,</E>
                         OSB are created with larger wood strands), which affect emission rates. Therefore, subcategorizing by product is appropriate.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The EPA also received a comment stating that it is unnecessary for the EPA to set numerical standards for MDI, and that MDI emissions would be more appropriately regulated under 
                        <PRTPAGE P="41425"/>
                        the work practice for RMH process units.
                    </P>
                    <P>
                        <E T="03">EPA response:</E>
                         We maintain that the EPA is required to set standards for HAP such as MDI that are known to be emitted from reconstituted wood products presses. Reconstituted wood products presses do not meet the criteria under CAA section 112(h) for establishing work practices.
                    </P>
                    <HD SOURCE="HD3">c. What MDI reconstituted wood product press standards are we finalizing?</HD>
                    <P>
                        The EPA is finalizing the proposed MDI MACT limits for reconstituted wood product presses. The EPA is maintaining the designated subcategorization based on the product type, as described above. Reconstituted wood product presses operating HAP controls are expected to meet the MACT floor for existing and new sources. However, it is currently unknown whether presses at two particleboard facilities that meet the PCWP production-based compliance option (PBCO) using pollution prevention measures would meet the MDI MACT floor.
                        <E T="51">54 55</E>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>54</SU>
                             Table 1A to subpart DDDD of 40 CFR part 63 contains the PBCO total HAP limits.
                        </P>
                        <P>
                            <SU>55</SU>
                             
                            <E T="03">See</E>
                             the June 1, 2026 memorandum entitled 
                            <E T="03">Revised Cost, Environmental, and Energy Impacts of Subpart DDDD Regulatory Options,</E>
                             available in the docket for this rulemaking, for additional discussion the on impact of this action.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2. Tube Dryers</HD>
                    <P>Primary tube dryers often incorporate blow-line blending in which resin is added to wood fibers as they enter the primary tube dryer. The resin and wood fibers mix with the turbulent conditions in the primary tube dryer as the wood fiber is dried. Primary and secondary tube dryers are often co-controlled. Primary tube dryers may also be co-controlled with a reconstituted wood product press.</P>
                    <HD SOURCE="HD3">a. What MDI standards did the EPA propose for tube dryers?</HD>
                    <P>The proposed MACT standard for MDI from new and existing tube dryers is 1.7E-02 lb/ODT or 0.68 mg MDI/dscm. This standard is based on the MACT floor. No regulatory options more stringent than the MACT floor were identified for tube dryers that blow-line blend MDI.</P>
                    <P>b. What comments on the proposed MDI standard for tube dryers did we receive?</P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter indicated MDI standards for tube dryers are not necessary because all tube dryers with blow-line blending MDI resin are equipped with HAP emissions controls and the standard will only serve to incur an additional cost of emissions testing every five years with no environmental benefit.
                    </P>
                    <P>
                        <E T="03">EPA response:</E>
                         The EPA disagrees with the commenters claim that MDI standards for tube dryers are not necessary. Tube dryers blow-line blending MDI were identified as one of the primary sources of MDI emissions in the PCWP source category in the 2020 RTR.
                        <SU>56</SU>
                        <FTREF/>
                         Further, source testing in 2022 identified MDI emissions from an RTO-controlled tube dryer to be above the detection limit. For these reasons, establishing standards for tube dryers is appropriate.
                    </P>
                    <FTNT>
                        <P>
                            <SU>56</SU>
                             85 FR 49434 (Aug. 13, 2020).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. What MDI standards are we finalizing for tube dryers?</HD>
                    <P>The EPA is finalizing the proposed MACT standard for MDI from new and existing tube dryers. The MACT standard for tube dryers is 1.7E-02 lb/ODT or 0.68 mg MDI/dscm.</P>
                    <HD SOURCE="HD3">3. Miscellaneous Coatings Operations</HD>
                    <HD SOURCE="HD3">a. What MDI standards did we propose for miscellaneous coatings operations?</HD>
                    <P>The EPA proposed MDI emission standards for miscellaneous coating operations in which MDI moisture sealants are applied to engineered wood products such as parallel strand lumber or LVL.</P>
                    <HD SOURCE="HD3">b. What comments did the EPA receive on the proposed MDI standards for miscellaneous coatings operations?</HD>
                    <P>
                        <E T="03">Comment:</E>
                         Commenters questioned the necessity of the MDI numerical limit and requested reduced testing frequency for the MDI coating operation.
                    </P>
                    <P>
                        <E T="03">EPA response:</E>
                         The EPA maintains the standard is required to ensure MDI is properly regulated across miscellaneous coatings operations. Emissions from this source are measurable and capturable; therefore, they do not meet the criteria under CAA section 112(h) for establishing a work practice. See section III.F for an explanation of EPA's performance testing, monitoring, and recordkeeping and reporting requirements
                    </P>
                    <HD SOURCE="HD3">c. What MDI standards did we finalize for miscellaneous coatings operations?</HD>
                    <P>
                        The final MACT limit for existing and new sources is 1.9E-03 lb MDI emitted/lb sealant applied, or 1.4E-05 lb MDI/ft
                        <SU>2</SU>
                         surface area coated based on coating HAP content. The limit is based on the MACT floor. No options more stringent than the MACT floor emission level were identified for further analysis. The EPA is finalizing the five-year testing frequency, as proposed.
                    </P>
                    <HD SOURCE="HD2">F. Requirements for Performance Testing, Monitoring, and Recordkeeping and Reporting</HD>
                    <HD SOURCE="HD3">1. Performance Testing</HD>
                    <P>
                        No comments were received on the proposed emission test methods included in Table 4 to Subpart DDDD of Part 63 (“Table 4”). We are finalizing the proposed methods without change. The final emissions test methods for total HAP include EPA Method 320,
                        <SU>57</SU>
                        <FTREF/>
                         NCASI Method IM/CAN/WP-99.02,
                        <SU>58</SU>
                        <FTREF/>
                         NCASI Method ISS/FP-A105.0,
                        <SU>59</SU>
                        <FTREF/>
                         or ASTM D6348-12e1 
                        <SU>60</SU>
                        <FTREF/>
                         with the conditions discussed in section V.J of this preamble. EPA Method 326 
                        <SU>61</SU>
                        <FTREF/>
                         is required for MDI emissions measurement, in which a minimum sample of 1 dscm must be collected. For PM as a surrogate to HAP metals, either EPA Method 5 
                        <SU>62</SU>
                        <FTREF/>
                         or EPA Method 29 
                        <SU>63</SU>
                        <FTREF/>
                         is required with a minimum sample volume of 2 dscm. For Hg, EPA Method 29 or EPA Method 30B 
                        <SU>64</SU>
                        <FTREF/>
                         are required, with a minimum sample volume of 2 dscm for EPA Method 29. EPA Method 26A 
                        <SU>65</SU>
                        <FTREF/>
                         was proposed for HCl emissions measurement with a minimum sample volume of 2 dscm. The recently updated EPA Method 23 
                        <SU>66</SU>
                        <FTREF/>
                         is required for PAH and D/F emission measurement with a minimum sample volume of 3 dscm. Consistent with the treatment of non-detect data used to establish the emission standards, we are finalizing a requirement that non-detect data be treated as the MDL in test averages used to demonstrate compliance with the standards in Table 1C, Table 1D to Subpart DDDD of Part 63 (“Table 1D”), or Table 1E to Subpart DDDD of Part 63 (“Table 1E”). We are revising the rule to add Table 12 to Subpart DDDD of Part 63 (“Table 12”) to provide the toxic equivalence factors (TEFs) to multiply by the individual D/F congener test results to determine TEQ.
                        <SU>67</SU>
                        <FTREF/>
                         In addition, we are adding EPA Method 9 
                        <SU>68</SU>
                        <FTREF/>
                         to the 
                        <PRTPAGE P="41426"/>
                        rule for use in conjunction with pressure drop monitoring across mechanical collectors and other dry control devices.
                    </P>
                    <FTNT>
                        <P>
                            <SU>57</SU>
                             Appendix A to 40 CFR part 63.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>58</SU>
                             IBR in 40 CFR 63.14.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>59</SU>
                             IBR in 40 CFR 63.14.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>60</SU>
                             IBR in 40 CFR 63.14.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>61</SU>
                             Appendix A to 40 CFR part 63.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>62</SU>
                             Appendix A-3 to 40 CFR part 60.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>63</SU>
                             Appendix A-8 to 40 CFR part 60.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>64</SU>
                             Appendix A-8 to 40 CFR part 60.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>65</SU>
                             Appendix A-8 to 40 CFR part 60.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>66</SU>
                             Appendix A-8 to 40 CFR part 60.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>67</SU>
                             U.S. Environmental Protection Agency. (2010). 
                            <E T="03">Recommended Toxicity Equivalence Factors (TEFs) for Human Health Risk Assessments of 2,3,7,8-Tetrachlorodibenzo-p-dioxin and Dioxin-Like Compounds: https://www.epa.gov/sites/default/files/2013-09/documents/tefs-for-dioxin-epa-00-r-10-005-final.pdf.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>68</SU>
                             Appendix A-4 to 40 CFR part 60.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">a. What performance testing frequency did we propose?</HD>
                    <P>For the new and existing source emission limits being added to the PCWP NESHAP, we proposed that performance testing would be required every 5 years (60 months).</P>
                    <HD SOURCE="HD3">b. What comments did we receive on the proposed performance testing frequency?</HD>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters expressed concern about the proposed five-year frequency of emissions testing. One commenter argued that testing every five years is too infrequent to ensure compliance and recommended semiannual testing or a continuous emission monitoring system (CEMS). Other commenters requested the EPA allow performance testing of PAH, HCl, and Hg be one time sampling events rather than repeated every five years considering the high costs of testing, complexity of test methods, and lack of laboratory availability for these trace compounds.
                    </P>
                    <P>
                        <E T="03">EPA response:</E>
                         Regarding the assertion that stack testing every five years cannot ensure compliance, we note that demonstration of compliance is not accomplished by performance testing alone but is paired with ongoing parametric monitoring established during performance testing to show compliance with the emission limits. Routine performance testing is necessary to provide periodic verification of the operation of control devices and to ensure the parametric monitoring remains relatable to actual emissions. We maintain that the proposed testing frequency, in combination with required parametric monitoring, is sufficient to ensure compliance and that CEMS are unnecessary for PCWP standards being finalized.
                    </P>
                    <HD SOURCE="HD3">c. What performance testing requirements are we finalizing?</HD>
                    <P>The final rule requires initial performance tests to be completed within 180 days after the compliance date for the new standards and subsequent performance testing every five years (60 months), thereafter.</P>
                    <HD SOURCE="HD3">2. Parameter Monitoring</HD>
                    <P>
                        The preamble for the May 2023 proposal described the proposed parametric monitoring requirements in detail.
                        <SU>69</SU>
                        <FTREF/>
                         After reviewing public comments, we are finalizing the parametric monitoring requirements substantially as proposed with the following key changes:
                    </P>
                    <FTNT>
                        <P>
                            <SU>69</SU>
                             88 FR 31878-79 (May 18, 2023).
                        </P>
                    </FTNT>
                    <P>• We are allowing the owner or operator to monitor pressure drop weekly opacity observations in lieu of continuous opacity monitoring system (COMS) for mechanical collectors (or other dry control devices not otherwise mentioned in Table 2 to Subpart DDDD of Part 63 [“Table 2”]) to demonstrate continuous compliance with PM limits.</P>
                    <P>• We are clarifying language in Table 10 to Subpart DDDD of Part 63 “Table 10” to require the notification and reporting requirements for performance evaluations for only COMs and CEMS, although we are retaining the requirement to perform performance evaluations on other continuous parameter monitoring systems (CPMS).</P>
                    <P>• We have corrected typographical errors related to electrified filter bed (EFB) monitoring by clarifying that only voltage monitoring is required for EFB.</P>
                    <P>• We changed the semiannual flow sensor calibration to an annual calibration, which is consistent with other calibration requirements throughout the rule.</P>
                    <P>• We are amending the rule to include language specifying when pressure drop is to be monitored.</P>
                    <P>For more details and our rationale surrounding these changes and other minor changes to the monitoring requirements, please see the RTC document in the docket for this action. The final monitoring requirements are summarized in this section.</P>
                    <P>Continuous compliance with the standards proposed in Tables 1C, 1D, or 1E must be demonstrated through control device parameter monitoring coupled with the proposed periodic emissions testing described in section III.F.1. The parametric monitoring already required in Table 2 for thermal oxidizers, catalytic oxidizers, or biofilters to demonstrate continuous compliance with the compliance options in Table 1B is also required to demonstrate ongoing compliance with the standards in Tables 1C, 1D, or 1E. In addition to the parametric monitoring currently specified for thermal oxidizers, catalytic oxidizers, or biofilters, the amendments to Table 2 as revised by this final action include the following parameter monitoring requirements for the types of air pollution control devices (APCDs) that we expect to be used to comply with the standards in Tables 1D or 1E:</P>
                    <P>• For wet electrostatic precipitator (WESP), secondary electric power input and liquid flow rate;</P>
                    <P>• For dry electrostatic precipitator (ESP), secondary electric power input or opacity;</P>
                    <P>• For wet PM scrubbers, liquid flow rate and pressure drop;</P>
                    <P>• For wet acid gas scrubbers, liquid flow rate and effluent pH;</P>
                    <P>• For EFBs, ionizer voltage or current and pressure drop; and</P>
                    <P>
                        • For mechanical collectors (
                        <E T="03">e.g.,</E>
                         cyclone or multiclone) or other dry control devices, a choice of opacity monitored using a COMS or pressure drop with weekly opacity observations.
                    </P>
                    <P>The operating limits for these parameters must be established consistently with the existing provisions of 40 CFR 63.2262, as the average of the three test run averages during the performance test. Continuous compliance with the parameters for WESP, dry ESP, wet scrubbers, and EFB must be determined by comparing the three-hour block average parameter average to the limit established during the performance test.</P>
                    <P>Consistent with existing provisions in Table 2, the rule is amended to require that a source owner choosing to rely on a control device other than a thermal oxidizer, catalytic oxidizer, or biofilter used to meet a compliance option in Table 1C petition the Administrator for site-specific operating parameters to be monitored or to maintain the three-hour block average total hydrocarbon (THC) concentration within the limits established during the performance test. The source owner of process units that meet a compliance option in Tables 1C, 1D, or 1E without using a control device must maintain on a daily basis the process unit controlling operating parameter(s) within the ranges established during the performance test or maintain the three-hour block average THC concentration within the limits established during the performance test.</P>
                    <P>For control devices where opacity is used as an operating parameter, a COMS is required, and the 24-hour block average opacity must not exceed 10 percent (or the highest hourly average measured during the performance test). Table 10 indicates that the requirements for opacity standards in 40 CFR 63.6(h)(2) through (9) do not apply because opacity is an operating limit and not an emission standard.</P>
                    <P>
                        Continuous monitoring requirements associated with the work practices in Table 3 to Subpart DDDD of Part 63 (“Table 3”) include combustion unit bypass stack usage monitoring (
                        <E T="03">e.g.,</E>
                         temperature or bypass damper position), lumber kiln dry bulb temperature 
                        <PRTPAGE P="41427"/>
                        monitoring for comparison with the batch average or daily block average dry bulb temperature limit, monitoring of lumber moisture (with semiannual averaging) for comparison to lumber minimum moisture content limits in Table 11, or monitoring of lumber kiln temperature (with 3-hour block averaging) and lumber moisture (with semiannual averaging) for comparison to limits in an approved site-specific plan.
                    </P>
                    <P>We are finalizing as proposed a requirement to continuously monitor process unit bypass stack usage at all times while the process units are operating, including times when the process unit is undergoing startup or shutdown, and during the operating conditions as specified in 40 CFR 63.2250(f)(2) through (4). This requirement is included to ensure that reliable data are available to evaluate continuous compliance with the PCWP NESHAP requirements.</P>
                    <P>Consistent with NESHAP general provisions at 40 CFR part 63, subpart A, a source owner is required to operate and maintain the source, its air pollution control equipment, and its monitoring equipment in a manner consistent with safety and good air pollution control practices for minimizing emissions, to include operating and maintaining equipment in accordance with the manufacturer's recommendations. Owners are required to prepare and keep records of calibration and accuracy checks of the continuous monitoring system (CMS) to document proper operation and maintenance of the monitoring system.</P>
                    <HD SOURCE="HD3">3. Recordkeeping and Reporting</HD>
                    <P>
                        The EPA received no significant comments on the recordkeeping requirements, so they are being finalized as proposed. A source owner is required to submit semi-annual compliance summary reports that document both compliance with the requirements of the PCWP NESHAP and any deviations from compliance with any of those requirements, consistent with existing requirements in the PCWP NESHAP. Owners and operators are required to maintain the records specified by 40 CFR 63.10 and, in addition, are required to maintain records of all monitoring data, in accordance with the PCWP NESHAP.
                        <SU>70</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>70</SU>
                             40 CFR 63.2282.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">G. Other Actions</HD>
                    <P>We are finalizing revisions to the PCWP NESHAP to remove obsolete rule language including the emissions averaging compliance option for existing affected sources, dates, and startup/shutdown provisions that are no longer in effect. Removing the outdated language from the PCWP NESHAP streamlines the rule and makes it easier to read. We are also finalizing updates and clarifications of the electronic reporting requirements. In addition, we reviewed issues raised by reconsideration petitioners following the 2020 RTR. The final revisions and rationale are presented in this section.</P>
                    <HD SOURCE="HD3">1. Emissions Averaging</HD>
                    <P>Emissions averaging was included in the 2004 rule as a compliance option for use at existing affected sources. We proposed to remove the emissions averaging compliance option in the May 2023 proposal because no existing facilities are using it, and emissions averaging is not an option for new affected facilities. The only facility to use the option has now ceased PCWP production. Also, the new emission standards being added for process units and HAP subject to the 2007 partial remand and vacatur with this action further diminish opportunities for emissions averaging, and removing the emission averaging language simplifies the rule. Two commenters agreed with removing the emissions averaging option and no commenters objected. Therefore, we are removing the emissions averaging option from the PCWP NESHAP in this final action.</P>
                    <HD SOURCE="HD3">2. Obsolete Dates and Provisions</HD>
                    <P>
                        On August 13, 2020, the EPA published several amendments to the PCWP NESHAP with corresponding compliance dates for transitioning from obsolete provisions that have since passed.
                        <SU>71</SU>
                        <FTREF/>
                         This final rule contains additional amendments with multiple associated dates discussed in section III.H of this preamble. We proposed in the May 2023 proposal to remove the obsolete dates and provisions that are no longer in effect to improve clarity of the PCWP NESHAP, including:
                    </P>
                    <FTNT>
                        <P>
                            <SU>71</SU>
                             85 FR 49434 (Aug. 13, 2020).
                        </P>
                    </FTNT>
                    <P>• In 40 CFR 63.2233(1) through (3), cross-references to specific paragraphs needed to implement the 2020 RTR amendments were proposed to be removed and replaced with a reference to the proposed 40 CFR 63.2233(e), which provides compliance dates for the rule requirements proposed in this action.</P>
                    <P>• Paragraphs 40 CFR 63.2250(a) through (c) were proposed to be removed and reserved because their requirements no longer apply.</P>
                    <P>• Date language was proposed to be removed in paragraphs 40 CFR 63.2250(f) and (g), which are paragraphs that replaced the obsolete paragraphs 40 CFR 63.2250(a) through (c) in the 2020 RTR amendments.</P>
                    <P>• Paragraphs 40 CFR 63.2280(b) and (d) contained dates for when electronic submittal of initial notifications and performance test results became effective. 40 CFR 63.2281(b)(6) contained dates for when electronic submittal of semiannual reports became effective. These dates have passed, and the electronic reporting requirements are in full effect, so we proposed to remove dates to make the rule easier to read.</P>
                    <P>• The first part of paragraph 40 CFR 63.2281(c)(4) contains dates for language that was phased out as well as dates for when electronic reporting requirements were phased in. Similarly, 40 CFR 63.2282(a)(2) contains obsolete dates and language intended to phase out some records and phase in other records. We proposed to remove the obsolete language to simplify the rule because the dates have now passed.</P>
                    <P>• Row 2 in Table 9 to Subpart DDDD of Part 63 was proposed to be removed and reserved because the requirement for an SSM report is no longer in effect.</P>
                    <P>• The 2020 RTR amendments added a column to Table 10 to clarify which general provisions in 40 CFR part 63, subpart A applied before and after August 13, 2021, for existing sources. The now obsolete column pertaining to requirements before August 13, 2021, was proposed to be removed. Those amendments pertain to SSM provisions that were removed and to reporting provisions that were added on August 13, 2020.</P>
                    <P>
                        For clarity, we are retaining date language from the 2020 RTR that specified compliance dates for standards and electronic reporting provisions added with that rulemaking. We have also taken care to insert compliance date language for the new standards finalized in this action as discussed further in section III.H of this preamble.
                        <SU>72</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>72</SU>
                             40 CFR 63.2240(d) and (e), tables 1C, 1D, 1E to subpart DDDD of 40 CFR part 63, 40 CFR 63.2241(d) through (g), and table 3 to subpart DDDD of 40 CFR part 63.
                        </P>
                    </FTNT>
                    <P>We received no substantial comments on removal of the obsolete dates and provisions. Therefore, we are finalizing the changes as proposed.</P>
                    <HD SOURCE="HD3">3. Electronic Reporting Updates and Clarifications</HD>
                    <P>
                        On November 19, 2020, the EPA published a final rule incorporating standard electronic reporting language into the general provisions at 40 CFR 
                        <PRTPAGE P="41428"/>
                        63.9(k). We proposed to update the electronic reporting language in 40 CFR part 63, subpart DDDD, to refer to the provisions in 40 CFR 63.9(k) in addition to other revisions. The proposed revisions are as follows:
                    </P>
                    <P>• We proposed to require that initial notifications and notifications of compliance status be submitted in a user-specified format such as PDF in 40 CFR 63.2280(b) and (d) instead of 40 CFR 63.2281(h).</P>
                    <P>• General provisions pertaining to submittal of CBI were proposed to be removed from 40 CFR 63.2281(h), (i)(3), and (j)(3).</P>
                    <P>
                        • In 40 CFR 63.2281(k), we proposed to replace language pertaining to Compliance and Emissions Data Reporting Interface (CEDRI) outageswith additional detailed procedures for submitting CBI in electronic format.
                        <SU>73</SU>
                        <FTREF/>
                         The update provides an email address that source owners and operators can use to electronically mail CBI to the Office of Clean Air Programs (OCAP) CBI Office when submitting compliance reports.
                    </P>
                    <FTNT>
                        <P>
                            <SU>73</SU>
                             Now in 40 CFR 63.9(k).
                        </P>
                    </FTNT>
                    <P>• In 40 CFR 63.2281(l), we proposed to remove the provisions related to force majeure claims which are now in 40 CFR 63.9(k).</P>
                    <P>• We proposed to remove the provision in 40 CFR 63.2283(d) that states that records submitted to CEDRI may be maintained in electronic format, because 40 CFR 63.10(b)(1) already allows the retention of all records electronically.</P>
                    <P>• In Table 10, we proposed to indicate that all of the provisions in 40 CFR 63.9(k) apply to 40 CFR part 63, subpart DDDD.</P>
                    <P>In addition, we proposed to amend 40 CFR 63.2281(c)(4) to clarify the compliance reporting requirements for the work practices in Table 3 (rows 6, 7, or 8). The EPA proposed to clarify that the requirement to report the date, time, and duration of every instance in which one of the work practices is used applies only if that individual work practice is used for more than 100 hours during the reporting period. The EPA's original intent was for the 100-hour reporting threshold to be compared to the semiannual usage of each of the three work practices individually, not for the total usage of all three work practices combined. As stated in 40 CFR 63.2281(c)(4), when one of the work practices is used for less than 100 hours per semiannual reporting period, a summary of the number of instances and total amount of time that work practice was used is required to be reported. As noted in section III.F.2 of this preamble, we also proposed to require continuous monitoring and recording of process unit bypass stack usage at all times including during the operating conditions specified in 40 CFR 63.2250(f)(2) through (4) and Table 3 (rows 6, 7, or 8) to ensure that reliable data are available to evaluate continuous compliance with the PCWP NESHAP requirements.</P>
                    <P>
                        One commenter offered comments on the updated CEDRI reporting template provided with the May 2023 proposal and requested an additional opportunity to review the template before it is finalized.
                        <SU>74</SU>
                        <FTREF/>
                         The commenter's recommendations and the EPA's responses are provided in the RTC located in the docket. The EPA's revised CEDRI reporting template for this final rule is available in the docket but will not be required until implemented in CEDRI.
                        <SU>75</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>74</SU>
                             40 CFR part 63, subpart DDDD—Plywood and Composite Wood Products Semiannual Compliance Reporting Spreadsheet Template. Document ID No. EPA-HQ-OAR-2016-0243-0417.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>75</SU>
                             40 CFR part 63, subpart DDDD—Plywood and Composite Wood Products Semiannual Compliance Reporting Spreadsheet Template (Final ICR Draft, 2026), available in the docket for this rulemaking.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">4. Issues Raised by Petitioners Following the RTR</HD>
                    <P>
                        Following publication of the 2020 RTR,
                        <SU>76</SU>
                        <FTREF/>
                         the EPA received a petition for reconsideration (Petition) from Earthjustice on behalf of Greater Birmingham Alliance to Stop Pollution, Louisiana Environmental Action Network, and Sierra Club (“Petitioners”). The Petitioners asked the EPA to reconsider certain aspects of the 2020 RTR and other amendments under the authority of CAA section 307(d)(7)(B), arguing that the EPA's rationale for four decisions all appeared for the first time in the 2020 RTR and RTC document accompanying the final rule.
                        <SU>77</SU>
                        <FTREF/>
                         This section summarizes the four issues raised by the Petitioners, the EPA's proposed revisions to the PCWP NESHAP to address some of these issues, comments received on the proposed revisions and our responses, and our final decisions and rationale on the issues for this rulemaking.
                    </P>
                    <FTNT>
                        <P>
                            <SU>76</SU>
                             85 FR 49434 (Aug. 13, 2020).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>77</SU>
                             
                            <E T="03">National Emission Standards for Hazardous Air Pollutants: Plywood and Composite Wood Products (40 CFR part 63, subpart DDDD) Residual Risk and Technology Review, Final Amendments, Responses to Public Comments on September 6, 2019, Proposal.</E>
                             Document ID No. EPA-HQ-OAR-2016-0243-0244, available in the docket for this rulemaking.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">a. What were the issues raised by the Petitioners and what were our proposed revisions?</HD>
                    <P>In the first issue raised, the Petitioners alleged that the EPA failed to set limits for unregulated HAP. Although we do not agree that the Petitioners met their burden under CAA section 307(d)(7)(B) to show that it was impracticable to raise this objection during the public comment period for the proposed 2020 RTR, and thereby compel reconsideration of this issue, the May 2023 proposal contained new standards for unregulated HAP that are being finalized in response to the 2007 partial remand and vacatur of the 2004 rule and to address unregulated HAP, such that the Petitioners' concern regarding this issue is resolved with this final action.</P>
                    <P>
                        In the second and third issues raised by the Petitioners, they disagreed with two work practices the EPA finalized on August 13, 2020, for safety-related shutdowns and pressurized refiner startup and shutdowns, and objected to what they perceived to be the EPA's changed or new rationale for these work practices between proposal and finalization of the 2020 RTR, claiming that they did not have an opportunity to raise their objections during the public comment period. The Petitioners disagreed with the EPA's use of CAA section 112(h) to develop work practice standards for safety-related shutdowns and pressurized refiner startup and shutdown events. For safety-related shutdowns, the Petitioners took issue with the EPA's rationale that facilities cannot capture and convey HAP emissions 
                        <E T="03">to a control device</E>
                         during these periods for safety reasons, saying that whether emissions can be conveyed 
                        <E T="03">to a control device</E>
                         is irrelevant under CAA section 112(h)(2)(A).
                        <SU>78</SU>
                        <FTREF/>
                         In response to this critique, and to ensure that there is a full opportunity for all stakeholders to comment on the EPA's rationale for these work practices, the EPA requested comment in the May 2023 proposal on the relevance of the ability of facilities to capture and convey emissions to a control device to CAA section 112(h)(2)(A), given that CAA section 112(h)(2)(A) explicates CAA section 112(h)(1), which explicitly refers to the EPA's judgment as to when it is not feasible to prescribe or enforce an emission standard 
                        <E T="03">for control of</E>
                         a HAP.
                    </P>
                    <FTNT>
                        <P>
                            <SU>78</SU>
                             
                            <E T="03">National Emission Standards for Hazardous Air Pollutants: Plywood and Composite Wood Products (40 CFR part 63, subpart DDDD) Residual Risk and Technology Review, Final Amendments: Response to Public Comments on September 6, 2019 Proposal.</E>
                             Docket ID No. EPA-HQ-OAR-2016-0243-0244 Available in the docket for this rulemaking.
                        </P>
                    </FTNT>
                    <PRTPAGE P="41429"/>
                    <P>
                        Regarding the EPA's rationale under CAA section 112(h)(2)(B) for the safety-related shutdown and pressurized refiner startup and shutdown work practices, the Petitioners expressed discontent with the EPA's conclusion that stack tests (which typically take one to three hours) cannot be conducted for events lasting only minutes. The Petitioners asserted that the EPA should have considered the practicability of other measurement methodologies including CEMS or continuous parameter monitoring. In response to the Petitioners' concerns, in the May 2023 proposal we maintained that stack testing is not feasible for safety-related shutdown events lasting only minutes or for pressurized refiner startup/shutdown events lasting less than 15 minutes. We requested comment in the May 2023 proposal on how the EPA could feasibly prescribe or enforce a numeric emission limit for such short-term events without the ability to conduct stack testing. Further, continuous operation of CEMS on bypass stacks that are unused for the majority of process operating time is not technically (
                        <E T="03">e.g.,</E>
                         because of the calibration drift likely to occur while the CEMS goes unused) or economically practicable. The source testing required for conducting a relative accuracy test audit (RATA) of CEMS would not be possible without requiring the use of the bypass during the RATA. Obtaining emissions data to correlate with parameters to establish continuously monitored parameter limits also necessitates stack testing. Although CEMS or specific continuously monitored parameter limits are not an appropriate measurement methodology for safety-related shutdowns and pressurized refiner startups and shutdowns themselves because of technical and economic limitations, in 2023 we proposed additional continuous parameter monitoring of bypass stack usage in addition to the work practices for safety-related shutdowns and pressurized refiner startup/shutdown events to address the Petitioners' concern. As discussed in section III.B of this preamble, we proposed to require continuous monitoring of combustion unit bypass stacks and to require annual tune-ups of combustion units used to direct-fire dryers. As discussed in section III.F of this preamble, we also proposed to require continuous monitoring of process unit bypass stack usage at all times while the process units are operating, including times when the process unit is undergoing startup or shutdown, and during safety-related shutdowns and pressurized refiner startup/shutdown events to ensure that reliable data are available to evaluate continuous compliance with the PCWP NESHAP requirements.
                    </P>
                    <P>The Petitioners also took issue with inclusion of measures that facilities have developed to protect workers and equipment in the safety-related shutdown work practice. The Petitioners argued that the steps an operator takes to protect workers and equipment are not necessarily the steps needed to prevent excess emissions or to remove raw materials and the heat source from the process as expeditiously as possible. We disagree with the Petitioners that the phrase “to protect workers and equipment” detracts from the safety-related shutdown work practice requirements to ensure that the flow of raw materials (such as furnish or resin) and fuel or process heat (as applicable) ceases, and that material is removed from the process unit(s) as expeditiously as possible given the system design to reduce air emissions. However, we requested comment in the May 2023 proposal on inclusion of measures facilities developed to protect workers and equipment from the safety-related shutdown provision. We also requested comment on all aspects of the work practice provisions (which appear in Table 3, rows 6 and 7) based on operational experience now that these narrowly defined provisions have been implemented in place of the broader SSM exemptions that were removed from the PCWP NESHAP.</P>
                    <P>In their fourth issue raised, the Petitioners disagreed with the EPA's statement in the September 6, 2019, proposed technology review and 2020 RTR that use of low-HAP resins is a development under CAA section 112(d)(6), claiming the EPA must revise standards for any development identified to require the maximum degree of reduction that is achievable through its application. In the 2019 proposed and 2020 final technology reviews, when noting that low-HAP resins may be a development, the EPA also explained that the EPA did not identify information to suggest that the resin system changes have significantly altered the type of process units or HAP pollution control technologies used in the PCWP industry to date or have led to processes or practices that have not been accounted for in the promulgated PCWP NESHAP compliance options. The Petitioners dismissed as irrelevant the EPA's explanation that there are many types of resin systems used in the manufacture of the various PCWP and that the resin-system solution for one facility's product may not be applicable for another product produced at a different facility. The Petitioners also argued that it is irrelevant the EPA noted in 2020 plans for additional action for the PCWP NESHAP source category with respect to remanded PCWP process units in which the EPA would further consider the effects of resin system changes.</P>
                    <P>
                        Given the Petitioners' objections, we rearticulated in the May 2023 proposal our conclusion from the 2020 RTR. Specifically, we retracted our characterization of low-HAP resins as a “development” under CAA section 112(d)(6) with respect to the standards established for the PCWP source category in 2004. As noted in 2020, the EPA did not identify information suggesting that the resin system changes have significantly altered the type of process units or HAP pollution control technologies used in the PCWP industry or have led to processes or practices that were not accounted for in the 2004 rule compliance options. Therefore, we agree with the Petitioners that it may have been inappropriate to describe resin changes as a “development” under CAA section 112(d)(6) that occurred after the PCWP NESHAP was promulgated in 2004. Moreover, we disagree with the Petitioners' claim that if resin changes were in fact such a “development,” the EPA would be required to establish MACT standards under CAA sections 112(d)(2) and (3) as a consequence of that development. CAA section 112(d)(6) does not require the EPA to reconduct MACT determinations, as the D.C. Circuit made clear in 
                        <E T="03">Natural Resources Defense Council (NRDC)</E>
                         v. 
                        <E T="03">EPA,</E>
                         529 F.3d 1077 (D.C. Cir. 2008). Instead, CAA section 112(d)(6) provides the EPA with the ability to exercise its judgment to determine what revisions to preexisting standards are necessary, after considering such developments. The mere presence of a development does not alone compel the EPA to determine that revising a promulgated MACT standard is necessary. Rather, the EPA is required to review the standard and determine whether to revise the standard after taking into account the development. This preserves the EPA's ability to exercise judgment regarding whether a change to a promulgated standard is necessary. In any event, as discussed in section III.D of this preamble, we proposed work practice standards under CAA section 112(h) for RMH process units for which no emission standards were in place to respond to the 2007 partial remand and vacatur of the 2004 rule. These work practices were based on the use of non-HAP resins or resins with low vapor 
                        <PRTPAGE P="41430"/>
                        pressure, which have a low potential for HAP emissions, including resin types that were available at the time of the 2004 rule.
                    </P>
                    <HD SOURCE="HD3">b. What comments did we receive on our proposed revisions to address the issues and what were our responses and final decisions?</HD>
                    <P>
                        We received comments on the safety-related shutdown and pressurized refiner work practices. One commenter opposed these work practices while another commenter supported them. Upon review of the comments provided, the EPA has reconsidered the work practices for safety-related shutdown and pressurized refiner startup and shutdown events, and the Agency is retaining these work practice standards as promulgated in the 2020 RTR.
                        <SU>79</SU>
                        <FTREF/>
                         The specific comments related to the work practices and our detailed response are in the RTC located in the docket.
                        <SU>80</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>79</SU>
                             85 FR 49434 (Aug. 13, 2020).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>80</SU>
                             
                            <E T="03">see National Emission Standards for Hazardous Air Pollutants: Plywood and Composite Wood Products (40 CFR part 63, subpart DDDD), Response to Public Comments on May 18, 2023 Proposed Amendments,</E>
                             Docket ID No. EPA-HQ-OAR-2016-0243, available in the docket for this rulemaking
                        </P>
                    </FTNT>
                    <P>
                        We also received a comment concerning the EPA's proposed retraction of a finding published in the 2019 proposed technology review.
                        <SU>81</SU>
                        <FTREF/>
                         The EPA stated in the 2019 review that the increased availability of low-HAP resins constituted a “development” that must be considered pursuant to CAA section 112(d)(6).
                        <SU>82</SU>
                        <FTREF/>
                         Commenters asserted that the EPA's proposed retraction of this finding in the May 2023 proposal is arbitrary. The commenter noted that pursuant to CAA section 112(d)(6), the EPA must evaluate whether this development warrants strengthening the MACT standard. A different commenter indicated the EPA correctly determined that the option for facilities to reformulate resins was already contemplated during the development of the 2004 rule. The commenter stated that as an alternative to installing controls to reduce emissions, facilities can utilize the PBCO and meet HAP emission limits for each process unit. Upon review of the comments provided, we are reaffirming our conclusion from the 2020 RTR that no change to the preexisting PCWP NESHAP standards is warranted as a result of resin system changes. The specific comments and our detailed response are in the RTC located in the docket.
                    </P>
                    <FTNT>
                        <P>
                            <SU>81</SU>
                             84 FR 47074 (Sept. 6, 2019).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>82</SU>
                             
                            <E T="03">Id.</E>
                             at 47092.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">H. What are the effective and compliance dates of the standards?</HD>
                    <P>
                        As proposed, the final rule requires affected sources that commence construction or reconstruction on or before May 18, 2023, to comply with the new emission standards within three years after the effective date (
                        <E T="03">i.e.,</E>
                         by July 6, 2029). For affected sources that commenced construction or reconstruction after May 18, 2023, owners and operators must comply with the new provisions by July 6, 2026 or upon startup, whichever is later. An affected source is the collection of process units at a PCWP facility. Examples of new affected sources are new greenfield PCWP or lumber facilities, existing facilities constructing new PCWP manufacturing process lines in addition to (or as a replacement for) existing process lines, and existing lumber facilities adding (or replacing) lumber kilns in projects that meet the definition of reconstruction.
                    </P>
                    <P>Commenters offered differing opinions on our proposal to provide three years after the effective date of the new provisions for existing affected sources to comply. One commenter argued that three years was too long, while another commenter argued that the three-year compliance period was too short to implement all new requirements.</P>
                    <P>Amendments to the PCWP NESHAP finalized in this rulemaking for adoption under CAA section 112(d)(2) and (3) are subject to the compliance deadlines outlined in the CAA under CAA section 112(i). For existing sources, CAA section 112(i)(3) provides that there shall be compliance “as expeditiously as practicable, but in no event later than 3 years after the effective date of such standard” subject to certain exemptions further detailed in the statute. In determining what compliance period is as “expeditious as practicable,” we consider the amount of time needed to plan and construct projects and change operating procedures. As provided in CAA section 112(i), all new affected sources would comply with these provisions by the effective date of the final amendments to the PCWP NESHAP or upon startup, whichever is later.</P>
                    <P>
                        The EPA projects that many existing sources will need to make changes (
                        <E T="03">e.g.,</E>
                         review operations, assemble documentation, install add-on controls and monitoring equipment) to comply with the finalized limits for various process units in their facility. These sources will require time to develop plans, construct, conduct performance testing, and implement monitoring to comply with the revised provisions. Therefore, the final rule allows three years for existing sources to become compliant with the applicable emission standards finalized in this action.
                    </P>
                    <HD SOURCE="HD1">IV. Summary of Cost, Environmental, and Economic Impacts and Additional Analyses Conducted</HD>
                    <HD SOURCE="HD2">A. What are the affected sources?</HD>
                    <P>
                        There are currently 219 major source facilities subject to the PCWP NESHAP. We estimated that six new PCWP facilities will be constructed and become subject to the NESHAP in the five years following the May 2023 proposal. A memorandum documenting the revised changes to the facility list since the 2023 proposed rule can be found in the docket for this rulemaking.
                        <SU>83</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>83</SU>
                             
                            <E T="03">See</E>
                             the June 1, 2026 memorandum entitled “Revised Updates to List of Plywood and Composite Wood Products Facilities”, available in the docket for this rulemaking.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">B. What are the air quality impacts?</HD>
                    <P>This final action is expected to reduce 721 tpy of directly-regulated HAPs compared to baseline emissions of 7,250 tpy.</P>
                    <P>
                        Additionally, the final rule will result in a decrease of other air emissions that are not regulated by this rule. In comparison to baseline emissions of 58,036 tpy VOC, the EPA estimates VOC emission reductions of approximately 8,504 tpy.
                        <SU>84</SU>
                        <FTREF/>
                         We also estimate that the final action would result in additional reductions of 202 tpy of PM, 144 tpy of PM &lt;2.5 µm in diameter (PM
                        <E T="52">2.5</E>
                        ), 132 tpy of NOx, 719 tpy of CO, 12 tpy of SO
                        <E T="52">2</E>
                        .
                        <SU>85</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>84</SU>
                             Baseline emissions estimates include only those process units for which new standards are being finalized in this action.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>85</SU>
                             More information about the estimated emission reductions and secondary impacts of this final action can be found in the document entitled 
                            <E T="03">Revised Cost, Environmental, and Energy Impacts of Subpart DDDD Regulatory Options,</E>
                             available in the docket for this rulemaking.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">C. What are the cost impacts?</HD>
                    <P>
                        The EPA estimates that this final action would cost approximately $121 million in total capital costs (distributed across multiple years) and $53 million per year (in 2024 dollars) in total annualized costs.
                        <SU>86</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>86</SU>
                             More information about the estimated cost of this final action can be found in the document entitled 
                            <E T="03">Revised Cost, Environmental, and Energy Impacts of Subpart DDDD Regulatory Options,</E>
                             available in the docket for this rulemaking.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">D. What are the economic impacts?</HD>
                    <P>
                        For the final rule, the EPA estimated the cost of compliance with the final emission limits. This includes the capital costs of installation, subsequent maintenance and operation of the 
                        <PRTPAGE P="41431"/>
                        controls, and other one-time and annual costs. To assess the potential economic impacts, the EPA prepared a partial equilibrium analysis modeling impacts to prices, production, and imports and exports. The EPA additionally performed a screening analysis that compared the expected annualized cost of compliance to the total sales revenue for the ultimate owners of affected facilities.
                    </P>
                    <P>For this final rule, the partial equilibrium analysis estimated an expected economic cost to both producers and consumers and accounting for changes to prices and quantities caused by the final amendments equal to $53 million. The expected annualized compliance cost from the screening analysis is $237,680 (on average) for each facility, including 219 existing and six projected new facilities, with an estimated nationwide annualized cost of $53,500,000. The 219 existing affected facilities are owned by 64 parent companies, and the compliance costs associated with the final amendments are expected to be on average about 0.27 percent of annual sales revenue per ultimate owner.</P>
                    <P>
                        Information on our cost and economic impact estimates for the PCWP manufacturing source category is contained in 
                        <E T="03">Economic Impact Analysis for the Final National Emissions Standards for Hazardous Air Pollutants: Plywood and Composite Wood Products Amendments,</E>
                         available in the docket for this rulemaking.
                        <SU>87</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>87</SU>
                             Docket ID No. EPA-HQ-OAR-2016-0243.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">E. What are the benefits?</HD>
                    <P>
                        The EPA is obligated to present the Agency's best scientific understanding and the implications of that science when developing policies and regulations. However, the EPA's analytical practices often provided the public with false precision and confidence regarding the monetized impacts of fine PM
                        <E T="52">2.5</E>
                         and ozone due to changes in emissions of PM
                        <E T="52">2.5</E>
                         as well as PM
                        <E T="52">2.5</E>
                         and ozone precursors. In addition, the science regarding the exposure, health effects from exposure, and valuation of reduction in health effect are evolving with better data and methods, especially at low concentrations of PM and ozone. Some of the sources of uncertainties include the set of assumptions used in projecting the health impact of reducing PM. These projections are based on a series of models that take into account emissions changes, resulting distributions of changes in ambient air quality, the estimated reductions in health effects from changes in exposure, and the composition of the population that will benefit from the reduced exposure. Each component includes assumptions, each with varying degrees of uncertainty.
                    </P>
                    <P>
                        In addition, the EPA historically provided point estimates rather than just ranges or only quantifying emissions, which leads the public to believe the Agency has a better understanding of the monetized impacts of exposure to PM
                        <E T="52">2.5</E>
                         and ozone than it does in reality. Therefore, to address these concerns, the EPA is no longer monetizing benefits from PM
                        <E T="52">2.5</E>
                         and ozone but will continue to quantify the emissions until the Agency is confident enough in the modeling to properly monetize those impacts. Implementing the final amendments is expected to reduce emissions of HAP and non-HAP pollutants, such as VOC. We estimate that the final amendments would reduce HAP emissions from the source category by approximately 721 tpy. The amendments would regulate emissions of acetaldehyde, acrolein, formaldehyde, methanol, phenol, propionaldehyde, non-Hg HAP metals, Hg, HCl, PAH, D/F and MDI. Information regarding the health effects of these compounds can be found in 
                        <E T="03">Health Effects Notebook for Hazardous Air Pollutants</E>
                         
                        <SU>88</SU>
                        <FTREF/>
                         and in the EPA Integrated Risk Information System database.
                        <SU>89</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>88</SU>
                             U.S. Environmental Protection Agency. (Last updated Nov. 24, 2025). 
                            <E T="03">Health Effects Notebook for Hazardous Air Pollutants: https://www.epa.gov/haps/health-effects-notebook-hazardous-air-pollutants.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>89</SU>
                             U.S. Environmental Protection Agency. (2026). 
                            <E T="03">List of Substances on IRIS: https://iris.epa.gov/AtoZ/?list_type=alpha.</E>
                        </P>
                    </FTNT>
                    <P>
                        The final amendments would reduce emissions of VOC which, in conjunction with NOx and in the presence of sunlight, form ground-level ozone. There are health benefits of reducing VOC emissions in terms of the number and value of avoided ozone-attributable deaths and illnesses. The 
                        <E T="03">Integrated Science Assessment for Ozone</E>
                          
                        <SU>90</SU>
                        <FTREF/>
                         found short-term (less than one month) exposures to ozone to be causally related to respiratory effects, a “likely to be causal” relationship with metabolic effects, and a “suggestive of, but not sufficient to infer, a causal relationship” for central nervous system effects, cardiovascular effects, and total mortality. The ISA reported that long-term exposures (one month or longer) to ozone are “likely to be causal” for respiratory effects including respiratory mortality, and a “suggestive of, but not sufficient to infer, a causal relationship” for cardiovascular effects, reproductive effects, central nervous system effects, metabolic effects, and total mortality.
                    </P>
                    <FTNT>
                        <P>
                            <SU>90</SU>
                             U.S. Environmental Protection Agency. (2020). 
                            <E T="03">Integrated Science Assessment for Ozone and Related Photochemical Oxidants.</E>
                             EPA/600/R-20/012: 
                            <E T="03">https://www.epa.gov/isa/integrated-science-assessment-isa-ozone-and-related-photochemical-oxidants.</E>
                        </P>
                    </FTNT>
                    <P>
                        The human health risk estimated for this source category for the 2020 RTR was determined to be acceptable, and the standards were determined to provide an ample margin of safety to protect public health. Specifically, the maximum individual cancer risk was 30-in-1 million for actual and allowable emissions and the noncancer hazard indices for chronic exposure were below 1 (
                        <E T="03">i.e.,</E>
                         0.8 for actual and allowable emissions). The maximum noncancer hazard quotient for acute exposure was 4. These health risk estimates were based on HAP emissions from the source category after addition of air pollution controls used to meet the MACT standards promulgated in 2004, as well as the baseline HAP emissions from process units for which standards are being promulgated in this action. While the 2020 RTR final amendments reduced emissions by an unquantified amount by removing the SSM exemption and adding repeat testing requirements, the changes to the PCWP NESHAP in this final action will reduce emissions by an additional 721 tons of HAP per year and will further improve human health exposures for populations in all demographic groups.
                    </P>
                    <HD SOURCE="HD1">V. Statutory and Executive Order Reviews</HD>
                    <P>
                        Additional information about these statutes and Executive Orders can be found at 
                        <E T="03">https://www.epa.gov/laws-regulations/laws-and-executive-orders.</E>
                    </P>
                    <HD SOURCE="HD2">A. Executive Order 12866: Regulatory Planning and Review and Executive Order 13563: Improving Regulation and Regulatory Review</HD>
                    <P>This action is not a significant regulatory action and was therefore not submitted to the Office of Management and Budget (OMB) for review.</P>
                    <HD SOURCE="HD2">B. Executive Order 14192: Unleashing Prosperity Through Deregulation</HD>
                    <P>This action is not an Executive Order 14192 regulatory action because this action is not significant under Executive Order 12866.</P>
                    <HD SOURCE="HD2">C. Paperwork Reduction Act (PRA)</HD>
                    <P>
                        The information collection activities in this final rule have been submitted for approval to OMB under the PRA. The information collection request (ICR) document that the EPA prepared has been assigned EPA ICR number 1984.12. You can find a copy of the ICR in the 
                        <PRTPAGE P="41432"/>
                        docket for this rule, and it is briefly summarized here.
                    </P>
                    <P>The final changes to the reporting and recordkeeping requirements for the PCWP NESHAP incorporate the reporting and recordkeeping requirements associated with the MACT standards being added to the rule for multiple HAP from new and existing process units.</P>
                    <P>
                        <E T="03">Respondents/affected entities:</E>
                         Owners or operators of PCWP or kiln-dried lumber manufacturing plants that are major sources, or that are located at, or are part of, major sources of HAP emissions.
                    </P>
                    <P>
                        <E T="03">Respondent's obligation to respond:</E>
                         Mandatory.
                        <SU>91</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>91</SU>
                             40 CFR part 63, subpart DDDD.
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Estimated number of respondents:</E>
                         On average over the next three years, approximately 219 existing major sources would be subject to these standards. It is also estimated that six additional respondents would become subject to the emission standards over the three-year period.
                    </P>
                    <P>
                        <E T="03">Frequency of response:</E>
                         The frequency of responses varies depending on the burden item (
                        <E T="03">e.g.,</E>
                         one-time, semiannual, annual, every five years).
                    </P>
                    <P>
                        <E T="03">Total estimated burden:</E>
                         The average annual burden to industry over the next three years from the final recordkeeping and reporting requirements is estimated to be 44,400 hours per year. Burden is defined at 5 CFR 1320.3(b).
                    </P>
                    <P>
                        <E T="03">Total estimated cost:</E>
                         The total annual recordkeeping and reporting cost for all facilities to comply with all the requirements in the NESHAP, including the requirements in this final rule, is estimated to be $10,290,000 per year including $3,870,000 in annualized capital and O&amp;M costs.
                    </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. The OMB control numbers for the EPA's regulations in 40 CFR are listed in 40 CFR part 9. When OMB approves this ICR, the Agency will announce that approval in the 
                        <E T="04">Federal Register</E>
                         and publish a technical amendment to 40 CFR part 9 to display the OMB control number for the approved information collection activities contained in this rule.
                    </P>
                    <HD SOURCE="HD2">D. Regulatory Flexibility Act (RFA)</HD>
                    <P>I certify that this action will not have a significant economic impact on a substantial number of small entities under the RFA. The small entities subject to the requirements of this action are small businesses as defined by the U.S. Small Business Administration (SBA). The EPA prepared a small business screening analysis to determine if any of the identified affected entities are small entities, as defined by the SBA. This analysis is available in the docket for this rulemaking (Docket ID No. EPA-HQ-OAR-2016-0243). The Agency has determined that 18 out of 64 small ultimate PCWP manufacturing parent companies may experience an impact ranging from approximately 0.03 percent to approximately 1.09 percent of annual sales, with three of the 18 ultimate parent companies experiencing an impact of more than one percent of annual sales. The 18 parent companies own 22 affected PCWP facilities. The EPA does not expect a substantial economic impact from these final amendments because only three out of 18 small business ultimate parent owners in the PCWP manufacturing source category face incremental total annualized compliance costs more than one percent but less than three percent of annual sales revenue.</P>
                    <P>
                        Details of this analysis are presented in 
                        <E T="03">Economic Impact Analysis for the Final National Emissions Standards for Hazardous Air Pollutants: Plywood and Composite Wood Products Amendments,</E>
                         located in the docket for this action.
                        <SU>92</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>92</SU>
                             Docket ID No. EPA-HQ-OAR-2016-0243.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">E. Unfunded Mandates Reform Act (UMRA)</HD>
                    <P>This action does not contain an unfunded mandate of $100 million or more as described in UMRA, 2 U.S.C. 1531-1538, and does not significantly or uniquely affect small governments. While this action creates an enforceable duty on the private sector and one facility owned by a Tribal government, the cost does not exceed $100 million or more.</P>
                    <HD SOURCE="HD2">F. Executive Order 13132: Federalism</HD>
                    <P>This action does not have federalism implications. It will not have substantial direct effects on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
                    <HD SOURCE="HD2">G. Executive Order 13175: Consultation and Coordination With Indian Tribal Governments</HD>
                    <P>This action does not have Tribal implications as specified in Executive Order 13175. It will not have substantial direct effects on Tribal governments, 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, as specified in Executive Order 13175. There are facilities subject to this rule located on the lands of the Coeur D'Alene Tribe, the Confederated Tribes and Bands of the Yakima Nation, and the Choctaw Nation. Consistent with the EPA Policy on Consultation and Coordination with Indian Tribes, the EPA offered consultation opportunities for Tribal officials early in the process of developing this rule to permit them to have meaningful and timely input into its development. The Choctaw Nation requested and received a pre-proposal meeting, a summary of which is available in the docket for this rulemaking. The EPA also offered consultation opportunities to all federally recognized Tribes during the comment period from May 18, 2023, to July 18, 2023, but received no request for consultation.</P>
                    <HD SOURCE="HD2">H. Executive Order 13045: Protection of Children From Environmental Health Risks and Safety Risks</HD>
                    <P>This action is not subject to Executive Order 13045 because the EPA does not believe the environmental health or safety risks addressed by this action present a disproportionate risk to children.</P>
                    <HD SOURCE="HD2">I. Executive Order 13211: Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use</HD>
                    <P>This action is not a “significant energy action” because it is not likely to have a significant adverse effect on the supply, distribution, or use of energy. In this final action, the EPA is setting emission standards for the PCWP source category. This does not impact energy supply, distribution, or use.</P>
                    <HD SOURCE="HD2">J. National Technology Transfer and Advancement Act (NTTAA) and 1 CFR Part 51</HD>
                    <P>
                        This action involves technical standards. Therefore, the EPA conducted searches for the PCWP NESHAP through the Enhanced National Standards Systems Network (NSSN) Database managed by the American National Standards Institute (ANSI). We also conducted a review of voluntary consensus standards (VCS) organizations and accessed and searched their databases. We conducted searches for EPA Methods 1, 1A, 2, 2A, 2C, 2D, 2F of appendix A-1 to part 60 of this chapter; EPA Test Methods 2G, 3, 3A, 3B of appendix A-2 to part 60 of this chapter; EPA Test Methods 4, 5 of appendix A-3 to part 60 of this chapter; 
                        <PRTPAGE P="41433"/>
                        EPA Test Method 10 of appendix A-4 to part 60 of this chapter; EPA Test Method 18 of appendix A-6 to part 60 of this chapter; EPA Test Methods 23, 25A of appendix A-7 to part 60 of this chapter; EPA Test Methods 26A, 29 of appendix A-8 to part 60 of this chapter; EPA Test Methods 204, 204A, 204B, 204C, 204D, 204E, 204F, 205 of appendix M to part 51 of this chapter; EPA Test Methods 308, 316, 320, 326 of appendix A to part 63 of this chapter; and EPA Test Method 0011 (incorporated by reference at 40 CFR 260.11(c)(4)). During the EPA's VCS search, if the title or abstract (if provided) of the VCS described technical sampling and analytical procedures that are similar to the EPA's referenced method, the EPA ordered a copy of the standard and reviewed it as a potential equivalent method. We reviewed all potential standards to determine the practicality of the VCS for this rule. This review requires significant method validation data that meet the requirements of EPA Method 301 for accepting alternative methods or scientific, engineering, and policy equivalence to procedures in the EPA referenced methods. The EPA may reconsider determinations of impracticality when additional information is available for any particular VCS.
                    </P>
                    <P>
                        Detailed information on the VCS search and determination can be found in the memorandum, 
                        <E T="03">Voluntary Consensus Standard Results for NEHSAP: Plywood and Composite Wood Products,</E>
                         which is available in the docket for this action.
                        <SU>93</SU>
                        <FTREF/>
                         Two VCS were identified as acceptable alternatives to the EPA test methods for this final rule.
                    </P>
                    <FTNT>
                        <P>
                            <SU>93</SU>
                             Document ID No. EPA-HQ-OAR-2016-0243-0415.
                        </P>
                    </FTNT>
                    <P>
                        The VCS ANSI/ASME PTC 19.10-1981 Part 10, “Flue and Exhaust Gas Analyses,” is an acceptable alternative to EPA Method 3B manual portions only and not the instrumental portion. This method determines quantitatively the gaseous constituents of exhausts resulting from stationary combustion sources. The manual procedures (but not instrumental procedures) of ASME/ANSI PTC 19.10-1981 Part 10 may be used as an alternative to EPA Method 3B for measuring the oxygen or carbon dioxide content of the exhaust gas. The gases covered in ASME/ANSI PTC 19.10-1981 are oxygen, carbon dioxide, carbon monoxide, nitrogen, sulfur dioxide, sulfur trioxide, nitric oxide, nitrogen dioxide, hydrogen sulfide, and hydrocarbons. However, the use in this rule is only applicable to oxygen and carbon dioxide. This VCS may be obtained from American Society of Mechanical Engineers (ASME), Three Park Avenue, New York, NY 10016-5990, telephone (800) 843-2763, 
                        <E T="03">https://www.asme.org.</E>
                         The EPA is finalizing our proposal to incorporate by reference (IBR) the VCS ANSI/ASME PTC 19.10-1981 Part 10, “Flue and Exhaust Gas Analyses,” as an acceptable alternative to EPA Method 3B manual portions only and not the instrumental portion.
                    </P>
                    <P>
                        The VCS ASTM D6348-12e1, “Determination of Gaseous Compounds by Extractive Direct Interface Fourier Transform (FTIR) Spectroscopy,” is an acceptable alternative to EPA Method 320 with certain conditions. The VCS ASTM D6348-12e1 employs an extractive sampling system to direct stationary source effluent to an FTIR spectrometer for the identification and quantification of gaseous compounds. Concentration results are provided. This test method is potentially applicable for the determination of compounds that (1) have sufficient vapor pressure to be transported to the FTIR spectrometer; and (2) absorb a sufficient amount of infrared radiation to be detected. The VCS ASTM D6348-12e1 may be obtained from 
                        <E T="03">https://www.astm.org</E>
                         or from the ASTM Headquarters at 100 Barr Harbor Drive, P.O. Box C700, West Conshohocken, Pennsylvania, 19428-2959. The EPA is finalizing our proposal to IBR the VCS ASTM D6348-12e1, “Determination of Gaseous Compounds by Extractive Direct Interface Fourier Transform (FTIR) Spectroscopy,” as an acceptable alternative to EPA Method 320 in place of ASTM D6348-03. ASTM D6348-03(2010) was determined to be equivalent to EPA Method 320 with caveats. ASTM D6348-12e1 is a revised version of ASTM D6348-03(2010) and includes a new section on accepting the results from the direct measurement of a certified spike gas cylinder but lacks the caveats placed on the ASTM D6348-03(2010) version. ASTM D6348-12e1 is an extractive FTIR field test method used to quantify gas phase concentrations of multiple analytes from stationary source effluent and is an acceptable alternative to EPA Method 320 at this time with caveats requiring inclusion of selected annexes to the standard as mandatory. When using ASTM D6348-12e1, the following conditions must be met:
                    </P>
                    <P>• The test plan preparation and implementation in the Annexes to ASTM D6348-03, sections A1 through A8 are mandatory; and</P>
                    <P>
                        • In ASTM D6348-03, Annex A5 (Analyte Spiking Technique), the percent (%) R must be determined for each target analyte.
                        <SU>94</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>94</SU>
                             Equation A5.5.
                        </P>
                    </FTNT>
                    <P>
                        In order for the test data to be acceptable for a compound, percent R must be 70 percent ≤ R ≤ 130 percent. If the percent R value does not meet this criterion for a target compound, the test data is not acceptable for that compound and the test must be repeated for that analyte (
                        <E T="03">i.e.,</E>
                         the sampling and/or analytical procedure should be adjusted before a retest). The percent R value for each compound must be reported in the test report, and all field measurements must be corrected with the calculated percent R value for that compound by using the following equation: Reported Results = (Measured Concentration in Stack)/(percent R) × 100.
                    </P>
                    <P>
                        In addition to the VCS mentioned earlier in this section, we are finalizing our proposal to IBR ASTM D1835-05, “Standard Specification for Liquefied Petroleum (LP) Gases,” for use in the definition of natural gas in 40 CFR 63.2292. The VCS ASTM D-1835-05 covers those products commonly referred to as liquefied petroleum gases, consisting of propane, propene (propylene), butane, and mixtures of these materials. This specification is designed to properly define acceptable LP products for domestic, commercial, or industrial uses. This VCS may be obtained from 
                        <E T="03">https://www.astm.org</E>
                         or from the ASTM Headquarters at 100 Barr Harbor Drive, P.O. Box C700, West Conshohocken, Pennsylvania, 19428-2959.
                    </P>
                    <HD SOURCE="HD2">K. Congressional Review Act (CRA)</HD>
                    <P>This action is subject to the CRA, 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>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects in 40 CFR Part 63</HD>
                        <P>Environmental protection, Administrative practice and procedures, Air pollution control, Hazardous substances, Incorporation by reference, Intergovernmental relations, Reporting and recordkeeping requirements.</P>
                    </LSTSUB>
                    <SIG>
                        <NAME>Lee Zeldin,</NAME>
                        <TITLE>Administrator.</TITLE>
                    </SIG>
                    <P>For the reasons stated in the preamble, the Environmental Protection Agency amends part 63 of title 40, chapter I, of the Code of Federal Regulations as follows:</P>
                    <PART>
                        <PRTPAGE P="41434"/>
                        <HD SOURCE="HED">PART 63—NATIONAL EMISSION STANDARDS FOR HAZARDOUS AIR POLLUTANTS FOR SOURCE CATEGORIES</HD>
                    </PART>
                    <REGTEXT TITLE="40" PART="63">
                        <AMDPAR>1. The authority citation for part 63 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>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart A—General Provisions</HD>
                    </SUBPART>
                    <REGTEXT TITLE="40" PART="63">
                        <AMDPAR>2. Amend § 63.14 by revising paragraphs (f)(1) and (i)(13), (86), and (88) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 63.14 </SECTNO>
                            <SUBJECT>Incorporations by reference.</SUBJECT>
                            <STARS/>
                            <P>(f) * * *</P>
                            <P>(1) ANSI/ASME PTC 19.10-1981, Flue and Exhaust Gas Analyses [Part 10, Instruments and Apparatus], issued August 31, 1981; §§ 63.116(c) and (h); 63.128(a); 63.145(i); 63.309(k); 63.365(b); 63.457(k); 63.490(g); 63.772(e) and (h); 63.865(b); 63.997(e); 63.1282(d) and (g); 63.1426(c); 63.1450(a), (b), (d), (e), (f), and (g); 63.1625(b); table 5 to subpart EEEE; §§ 63.3166(a); 63.3360(e); 63.3545(a); 63.3555(a); 63.4166(a); 63.4362(a); 63.4766(a); 63.4965(a); 63.5160(d); table 4 to subpart UUUU; table 3 to subpart YYYY; table 5 to subpart AAAAA; § 63.7322(b); table 5 to subpart DDDDD; §§ 63.7822(b); 63.7824(e); 63.7825(b); 63.8000(d); table 4 to subpart JJJJJ; table 4 to subpart KKKKK; §§ 63.9307(c); 63.9323(a); 63.9621(b) and (c); table 4 to subpart SSSSS; table 5 of subpart UUUUU; table 1 to subpart ZZZZZ; §§ 63.11148(e); 63.11155(e); 63.11162(f); 63.11163(g); table 4 to subpart JJJJJJ; §§ 63.11410(j); 63.11551(c); 63.11646(a); 63.11945(d).</P>
                            <STARS/>
                            <P>(i) * * *</P>
                            <P>(13) ASTM Method D1835-05, Standard Specification for Liquefied Petroleum (LP) Gases, approved April 1, 2005, IBR approved for §§ 63.2292, 63.7575, and 63.11237.</P>
                            <STARS/>
                            <P>(86) ASTM D6348-03, Standard Test Method for Determination of Gaseous Compounds by Extractive Direct Interface Fourier Transform Infrared (FTIR) Spectroscopy, including Annexes A1 through A8, Approved October 1, 2003, IBR approved for §§ 63.457(b), 63.997(e), and 63.1349, table 5 to subpart EEEE, table 4 to subpart UUUU, table 4 subpart ZZZZ, and table 8 to subpart HHHHHHH.</P>
                            <STARS/>
                            <P>(88) ASTM D6348-12e1, Standard Test Method for Determination of Gaseous Compounds by Extractive Direct Interface Fourier Transform Infrared (FTIR) Spectroscopy, Approved February 1, 2012, IBR approved for §§ 63.997(e), 63.1571(a), and 63.2354(b), table 4 to subpart DDDD, table 5 to subpart EEEE, table 4 to subpart UUUU, §§ 63.7142(a) and (b) and 63.8000(d), and table 4 to subpart SSSSS.</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <SUBPART>
                        <HD SOURCE="HED">SUBPART DDDD—NATIONAL EMISSION STANDARDS FOR HAZARDOUS AIR POLLUTANTS: PLYWOOD AND COMPOSITE WOOD PRODUCTS</HD>
                    </SUBPART>
                    <REGTEXT TITLE="40" PART="63">
                        <AMDPAR>3. Amend § 63.2233 by revising paragraphs (a)(1) and (2) and (b) and adding paragraph (e) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 63.2233 </SECTNO>
                            <SUBJECT>When do I have to comply with this subpart?</SUBJECT>
                            <P>(a) * * *</P>
                            <P>(1) If the initial startup of your affected source is before September 28, 2004, then you must comply with the compliance options, operating requirements, and work practice requirements for new and reconstructed sources in this subpart no later than September 28, 2004, except as otherwise specified in paragraph (e) of this section or elsewhere in this subpart.</P>
                            <P>(2) If the initial startup of your affected source is after September 28, 2004, then you must comply with the compliance options, operating requirements, and work practice requirements for new and reconstructed sources in this subpart upon initial startup of your affected source, except as otherwise specified in paragraph (e) of this section or elsewhere in this subpart.</P>
                            <P>(b) If you have an existing affected source, you must comply with the compliance options, operating requirements, and work practice requirements for existing sources no later than October 1, 2007, except as otherwise specified in paragraph (e) of this section or elsewhere in this subpart.</P>
                            <STARS/>
                            <P>(e) The compliance dates in paragraphs (e)(1) and (2) of this section apply for the compliance options, operating requirements, and work practice requirements that became effective on July 6, 2026. The compliance options, operating requirements, and work practice requirements that became effective on July 6, 2026, are listed in paragraph (e)(3) of this section.</P>
                            <P>(1) If construction or reconstruction of your affected source is commenced after May 18, 2023, you must comply with the compliance options, operating requirements, and work practice requirements listed in paragraph (e)(3) of this section beginning on July 6, 2026, or upon initial startup, whichever is later.</P>
                            <P>(2) If construction or reconstruction of your affected source is commenced on or before May 18, 2023, you must comply with the compliance options, operating requirements, and work practice requirements listed in paragraph (e)(3) of this section beginning on July 6, 2029, except as otherwise specified for mixed PCWP process streams in § 63.2240(d)(5).</P>
                            <P>(3) The compliance options, operating requirements, and work practice requirements that became effective on July 6, 2026, include the compliance options and operating requirements in § 63.2240(d) and (e) and tables 2 (rows 6 to 12), 1C, 1D, 1E, 4 (rows 12 to 19), 5 (rows 9 to 12), and 7 (rows 8 to 14) to this subpart; and the work practice requirements § 63.2241(d) through (g) and tables 3 (rows 9 to 14), 6 (rows 9 to 14), 8 (rows 9 to 17) and 11 to this subpart.</P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="40" PART="63">
                        <AMDPAR>4. Amend § 63.2240 by:</AMDPAR>
                        <AMDPAR>a. Revising the introductory text;</AMDPAR>
                        <AMDPAR>b. Removing and reserving paragraph (c); and</AMDPAR>
                        <AMDPAR>c. Adding paragraphs (d) and (e).</AMDPAR>
                        <P>The revision and additions read as follows:</P>
                        <SECTION>
                            <SECTNO>§ 63.2240 </SECTNO>
                            <SUBJECT>What are the compliance options and operating requirements and how must I meet them?</SUBJECT>
                            <P>You must meet the compliance options and operating requirements described in tables 1A, 1B, and 2 to this subpart by using one or more of the compliance options listed in paragraphs (a) and (b) of this section. You must meet the compliance options in tables 1C through 1E to this subpart according to paragraph (d) of this section. The process units subject to the compliance options are listed in tables 1A through 1E to this subpart and are defined in § 63.2292. You need only to meet one of the compliance options outlined in paragraph (a) or (b) of this section for each process unit. You cannot combine compliance options in paragraphs (a) and (b) of this section for a single process unit. (For example, you cannot use a production-based compliance option in paragraph (a) of this section for one vent of a veneer dryer and an add-on control system compliance option in paragraph (b) of this section for another vent on the same veneer dryer. You must use either the production-based compliance option or an add-on control system compliance option for the entire dryer.)</P>
                            <STARS/>
                            <P>
                                (d) 
                                <E T="03">Additional compliance requirements.</E>
                                 After July 6, 2026, you must comply with the compliance 
                                <PRTPAGE P="41435"/>
                                options in tables 1C through 1E to this subpart and associated operating limits in table 2 to this subpart as specified in paragraphs (d)(1) through (6) of this section.
                            </P>
                            <P>(1) Process units at an affected source that commenced construction or reconstruction on or before May 18, 2023, must comply with the compliance options in table 1C to this subpart on and after July 6, 2029.</P>
                            <P>(2) Process units at an affected source that commenced construction or reconstruction after May 18, 2023, must comply with the compliance options in table 1C to this subpart beginning on July 6, 2026, or upon initial startup, whichever is later.</P>
                            <P>(3) Direct-wood fired PCWP dryers at an affected source that commenced construction or reconstruction on or before May 18, 2023, must comply with the compliance options in table 1D to this subpart on and after July 6, 2029. In addition to the limits in table 1D to this subpart, direct wood-fired green rotary dryers that commenced construction or reconstruction on or before May 18, 2023, must limit emissions of dioxins and furans toxic equivalency (TEQ) to no more than 1.3E-09 pounds per oven dried ton (lb/ODT) or 1.7E-01 nanogram per dry standards cubic meter (ng/dscm) on and after July 6, 2029.</P>
                            <P>(4) Direct-wood fired PCWP dryers at an affected source that commenced construction or reconstruction after May 18, 2023, must comply with the compliance options in table 1E to this subpart beginning on July 6, 2026, or upon initial startup, whichever is later. In addition to the limits in table 1E to this subpart, direct wood-fired green rotary dryers that commenced construction or reconstruction after May 18, 2023, must limit emissions of dioxins and furans TEQ to no more than 4.4E-10 lb/ODT or 3.7E-02 ng/dscm on and after July 6, 2029.</P>
                            <P>(5) Mixed PCWP process streams (defined in § 63.2292) complying with the compliance options for add-on control systems in table 1B to this subpart according to paragraph (b) of this section before July 6, 2026, must continue to comply with the compliance options in table 1B to this subpart after July 6, 2026.</P>
                            <P>(6) Affected facilities may choose to comply with the add-on control system compliance options in table 1B to this subpart (and associated operating limits in table 2 to this subpart) instead of the compliance options in table 1C to this subpart for fiberboard mat dryer heated zones, press predryers, post-dryer atmospheric refiners, or multipurpose atmospheric refiners.</P>
                            <P>
                                (e) 
                                <E T="03">Process unit bypass stack operating requirement.</E>
                                 After July 6, 2026, you must comply with the operating requirement in table 2 to this subpart for process unit bypass stacks (defined in § 63.2292) by the compliance dates specified in § 63.2233(e).
                            </P>
                        </SECTION>
                        <AMDPAR>5. Amend § 63.2241 by adding paragraphs (d) through (g) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 63.2241 </SECTNO>
                            <SUBJECT>What are the work practice requirements and how must I meet them?</SUBJECT>
                            <STARS/>
                            <P>(d) The following combustion unit tune-up and bypass stack monitoring requirements must be conducted for all direct-fired dryers (including direct wood-fired PCWP dryers, direct natural gas-fired PCWP dryers, and direct-fired lumber kilns) by the dates specified in § 63.2233(e) and table 3 to this subpart. You must conduct an annual tune-up of each combustion unit used to directly-fire the PCWP dryer or lumber kiln following the procedures in § 63.2271(c) as specified in paragraphs (d)(1) through (3) of this section. You must monitor usage of combustion unit bypass stacks (defined in § 63.2292) following the procedures specified in § 63.2269(k) by the compliance date specified in § 63.2233(e).</P>
                            <P>(1) The initial tune-up must be completed by the compliance date specified in § 63.2233(e). After the initial tune-up, each annual tune-up is required to be completed no more than 13 months after the previous tune-up.</P>
                            <P>(2) If a combustion unit that direct-fires a PCWP dryer or lumber kiln is not operating on the required date for a tune-up, the tune-up must be conducted within 30 calendar days of startup of the combustion unit for the purpose of direct-firing a PCWP dryer or lumber kiln.</P>
                            <P>(3) For combustion units with tune-up requirements in this subpart, you may use documentation (required in § 63.7550(c)(1)) of the tune-up conducted according to §§ 63.7515(d) and 63.7540(a)(10), in place of the annual combustion unit tune-up requirements in this paragraph (d) and § 63.2271(c), provided the documentation required in § 63.7550(c)(1) is provided according to the schedule in paragraphs (d)(1) and (2) of this section.</P>
                            <P>(e) For each lumber kiln, you must minimize lumber over-drying to reduce HAP emissions by meeting the requirements in paragraphs (e)(1) through (4) of this section by the dates specified in § 63.2233(e) and table 3 to this subpart.</P>
                            <P>
                                (1) 
                                <E T="03">Lumber kiln operation and maintenance (O&amp;M).</E>
                                 Develop and maintain onsite an O&amp;M plan for the lumber kilns at the facility. The O&amp;M plan must include the kiln maintenance, charge optimization, inspection, and corrective action elements specified in § 63.2253(a).
                            </P>
                            <P>
                                (2) 
                                <E T="03">Lumber kiln burner tune-up.</E>
                                 For direct-fired lumber kilns, conduct annual burner tune-ups according to paragraph (d) of this section and § 63.2271(c).
                            </P>
                            <P>
                                (3) 
                                <E T="03">Lumber kiln work practice.</E>
                                 Minimize lumber over-drying by operating according to one of the work practice options in paragraph (e)(3)(i), (ii), or (iii) of this section.
                            </P>
                            <P>
                                (i) 
                                <E T="03">Temperature limit option.</E>
                                 Operate the lumber kiln with a maximum dry bulb temperature limit of no more than 210 °F for batch indirect fired (IF) kilns, 235 °F for batch direct-fired (DF) kilns, 245 °F for continuous IF kilns, or 245 °F for continuous DF kilns. You must continuously monitor and record the dry bulb temperature during the kiln drying cycle according to § 63.2269(m) and maintain the batch cycle average dry bulb temperature (for batch kilns) or daily block average dry bulb temperature (for continuous kilns) below the maximum limit specified in this paragraph (e)(3)(i) according to § 63.2270(h)(1).
                            </P>
                            <P>
                                (ii) 
                                <E T="03">Hybrid option.</E>
                                 Operate the lumber kiln according to paragraphs (e)(3)(ii)(A) and (B) of this section.
                            </P>
                            <P>(A) Operate the lumber kiln with a maximum dry bulb temperature limit of no more than 240 °F for batch indirect fired (IF) kilns, 250 °F for batch direct-fired (DF) kilns, 260 °F for continuous IF kilns, or 260 °F for continuous DF kilns. You must continuously monitor and record the dry bulb temperature during the kiln drying cycle according to § 63.2269(m) and maintain the batch cycle average dry bulb temperature (for batch kilns) or daily block average dry bulb temperature (for continuous kilns) below the maximum limit specified in this paragraph (e)(3)(ii)(A) according to § 63.2270(h)(1).</P>
                            <P>(B) Operate the kiln to dry to a semiannual average lumber moisture content (weight percent, dry basis) at or above the minimum limit of moisture content considered to be over-dried lumber as specified in paragraph (e)(4) of this section and table 11 of this subpart. Lumber moisture must be monitored and recorded according to § 63.2269(n). The semiannual average must be determined according to § 63.2270(i).</P>
                            <P>
                                (iii) 
                                <E T="03">Site-specific plan option.</E>
                                 Develop and operate according to a site-specific plan to minimize lumber over-drying 
                                <PRTPAGE P="41436"/>
                                through temperature and lumber moisture monitoring as required in paragraphs (e)(3)(iii)(A) and (B) of this section. The site-specific plan must be submitted to the delegated authority for approval and the site-specific limits from the plan must be incorporated into the facility's operating permit as specified in § 63.2253(b).
                            </P>
                            <P>(A) The site-specific plan must identify one temperature parameter (such as wet or dry bulb temperature, wet bulb depression, or temperature drop across the load) to be continuously monitored during the kiln drying cycle; include a description of how the temperature parameter is measured and used to minimize over-drying of lumber; and include a site-specific limit for the temperature parameter that minimizes over-drying. You must continuously monitor and record the temperature parameter according to § 63.2269(m) and calculate the 3-hour block average for comparison to the site-specific temperature limit according to § 63.2270(h)(2).</P>
                            <P>(B) The site-specific plan must include a method for monitoring lumber moisture content (weight percent, dry basis); specify the location of such monitoring within the lumber manufacturing process (for example, at the kiln unloading track, in lumber storage, or at the planer); specify the minimum kiln-dried lumber moisture content limit based on the lumber moisture specifications produced at the facility based on paragraph (e)(4) of this section and table 11 of subpart DDDD; and adhere to the minimum data and lumber moisture content averaging requirements in §§ 63.2269(o) and 63.2270(j).</P>
                            <P>
                                (4) 
                                <E T="03">Over-dried lumber.</E>
                                 As used in this subpart, the “maximum lumber moisture specification” means the upper limit of lumber moisture content (weight percent on a dry basis) that meets the relevant lumber grade standard for a lumber product. For each maximum lumber moisture specification, table 11 to this subpart provides the corresponding minimum kiln-dried lumber moisture content limits below which lumber is considered to be over-dried for purposes of this subpart.
                            </P>
                            <P>(f) By the dates specified in § 63.2233(e) and table 3 to this subpart, you must operate each log vat using a site-specific target log temperature that does not exceed 212 °F measured in the water used to soak the logs or in the wood as it is cut from the log.</P>
                            <P>(g) By the dates specified in § 63.2233(e) and table 3 to this subpart, you must meet the work practice standards in paragraphs (g)(1) and (2) of this section for resinated material handling process units, including resin tanks, softwood and hardwood plywood presses, engineered wood product presses and curing chambers, blenders, formers, finishing saws, finishing sanders, panel trim chippers, and reconstituted wood products board coolers (at existing affected sources), hardboard humidifiers, and onsite wastewater treatment operations specifically associated with PCWP manufacturing.</P>
                            <P>(1) You must meet one of the resin-related requirements in paragraphs (g)(1)(i) through (iii) of this section.</P>
                            <P>(i) Use only a non-HAP resin as defined in § 63.2292; or</P>
                            <P>(ii) Use only a resin with maximum true vapor pressure (defined in § 63.2292) of less than or equal to 13.1 kPa (1.9 psia) if the resin is stored in resin tanks with capacity of less than 40,000 gallons, or use only a resin with maximum true vapor pressure (defined in § 63.2292) of less than 5.2 kPa (0.75 psia) if the resin is stored in one or more resin tanks with capacity of 40,000 gallons or more; or</P>
                            <P>(iii) Use a combination of resins meeting either paragraph (g)(1)(i) or (ii) of this section.</P>
                            <P>(2) Process wood material that was purchased pre-dried to a moisture content of no more than 30 percent (weight percent, dry basis), or has been dried in a dryer located at the PCWP facility. This paragraph (g)(2) does not apply for wet formers and onsite wastewater treatment operations specifically associated with PCWP manufacturing.</P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="40" PART="63">
                        <AMDPAR>6. Amend § 63.2250 by:</AMDPAR>
                        <AMDPAR>a. Removing and reserving paragraphs (a) through (c);</AMDPAR>
                        <AMDPAR>b. Revising paragraph (f) introductory text and paragraph (f)(6);</AMDPAR>
                        <AMDPAR>c. Adding paragraph (f)(7); and</AMDPAR>
                        <AMDPAR>d. Revising paragraph (g).</AMDPAR>
                        <P>The revisions and addition read as follows:</P>
                        <SECTION>
                            <SECTNO>§ 63.2250 </SECTNO>
                            <SUBJECT>What are the general requirements?</SUBJECT>
                            <STARS/>
                            <P>(f) You must be in compliance with the compliance options, operating requirements, and the work practice requirements in this subpart when the process unit(s) subject to the compliance options, operating requirements, and work practice requirements are operating, except as specified in paragraphs (f)(1) through (7) of this section.</P>
                            <STARS/>
                            <P>(6) The applicable standard during each of the operating conditions specified in paragraphs (f)(2) through (4) of this section are the work practice requirements in table 3 to this subpart for safety-related shutdowns (row 6), pressurized refiner startup and shutdown (row 7), and direct-fired softwood veneer dryers undergoing startup or shutdown of gas-fired burners (row 8). The otherwise applicable compliance options, operating requirements, and work practice requirements (in rows 1 through 5 of table 3 to this subpart) do not apply during the operating conditions specified in paragraphs (f)(2) through (4) of this section, with the exception of the operating requirement in § 63.2240(e) which applies at all times.</P>
                            <P>(7) When using a wet scrubber, electrified filter bed, or mechanical collector (or other dry control device not mentioned elsewhere in table 2 to this subpart), you are not required to meet the minimum limit for pressure drop across the control device during startup or shutdown. Parameter limits other than pressure drop continue to apply during startup and shutdown.</P>
                            <P>(g) You must always operate and maintain your affected source, including air pollution control and monitoring equipment in a manner consistent with good air pollution control practices for minimizing emissions at least to the levels required by this subpart. The general duty to minimize emissions does not require you to make any further efforts to reduce emissions if levels required by the applicable standard have been achieved. Determination of whether a source is operating in compliance with operation and maintenance requirements will be based on information available to the Administrator which may include, but is not limited to, monitoring results, review of operation and maintenance procedures, review of operation and maintenance records, and inspection of the source.</P>
                        </SECTION>
                    </REGTEXT>
                    <SECTION>
                        <SECTNO>§ 63.2252 </SECTNO>
                        <SUBJECT>[Removed and Reserved]</SUBJECT>
                    </SECTION>
                    <REGTEXT TITLE="40" PART="63">
                        <AMDPAR>7. Remove and reserve § 63.2252.</AMDPAR>
                    </REGTEXT>
                    <REGTEXT TITLE="40" PART="63">
                        <AMDPAR>8. Under the undesignated center heading “General Compliance Requirements” add § 63.2253 to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 63.2253 </SECTNO>
                            <SUBJECT>What are the general requirements for lumber kilns?</SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Lumber kiln O&amp;M plan.</E>
                                 The lumber kiln O&amp;M plan must include the elements specified in paragraphs (a)(1) through (3) of this section and be maintained according to paragraph (a)(4) of this section.
                            </P>
                            <P>
                                (1) Procedures for maintaining the integrity of lumber kiln internal air flow and heat distribution components (such as, baffles, fans, vents, heating coils, or 
                                <PRTPAGE P="41437"/>
                                temperature sensors) to provide as uniform a temperature and air flow as reasonably possible.
                            </P>
                            <P>(2) Charge optimization practices to reduce over drying.</P>
                            <P>(3) At least annually, you must inspect lumber kiln integrity and review the charge optimization practices used. You must implement corrective actions as needed and maintain records of the inspections and corrective actions taken.</P>
                            <P>(i) The initial inspection of kiln integrity must be completed by the compliance date specified in § 63.2233(e). After the initial inspection, each annual inspection is required to be completed no more than 13 months after the previous inspection.</P>
                            <P>(ii) Corrective actions must be initiated within 30 days after the inspection and completed within 180 days following the inspection identifying the need for the corrective action. If the corrective action cannot be completed within 180 days, a written request for an extension may be submitted to the delegated authority, who may grant an extension if they determine additional time is necessary.</P>
                            <P>(4) After the compliance date in § 63.2233(e), any updates made to the O&amp;M plan maintained onsite must be described in the semiannual compliance report. Delegated authorities may require modification of the O&amp;M plan, as needed, upon review.</P>
                            <P>
                                (b) 
                                <E T="03">Lumber kiln site-specific plan approval.</E>
                                 If you choose to comply with the work practice option in § 63.2241(e)(3)(iii) using a site-specific plan for temperature and lumber moisture monitoring, the requirements in paragraphs (b)(1) through (5) of this section apply.
                            </P>
                            <P>(1) The site-specific plan must be developed and submitted to the delegated authority by January 6, 2028.</P>
                            <P>(2) The written site-specific plan must be maintained onsite at the facility and is enforceable upon the compliance date specified in § 63.2233.</P>
                            <P>(3) After the compliance date, you must report deviations from the site-specific plan according to § 63.2281.</P>
                            <P>(4) Once the site-specific plan is approved by the delegated authority, the site-specific limits from the plan must be incorporated into the facility's title V permit when the title V permit is next reopened for cause or renewed, as applicable.</P>
                            <P>(5) After the compliance date in § 63.2233(e), any updates made to the site-specific plan must be approved by the delegated authority, and any updates to the site-specific limits from the plan must be incorporated into the facility's title V permit when the title V permit is next reopened for cause or renewed, as applicable. </P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="40" PART="63">
                        <AMDPAR>9. Amend § 63.2260 by revising paragraph (a) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 63.2260 </SECTNO>
                            <SUBJECT>How do I demonstrate initial compliance with the compliance options, operating requirements, and work practice requirements?</SUBJECT>
                            <P>(a) To demonstrate initial compliance with the compliance options and operating requirements, you must conduct performance tests and establish each site-specific operating requirement in table 2 to this subpart according to the requirements in § 63.2262 and table 4 to this subpart. Combustion units that accept process exhausts into the flame zone are exempt from the performance testing to show compliance with the compliance options in table 1B or 1C to this subpart and the operating requirements for thermal oxidizers.</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="40" PART="63">
                        <AMDPAR>10. Revise § 63.2262 to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 63.2262 </SECTNO>
                            <SUBJECT>How do I conduct performance tests and establish operating requirements?</SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Testing procedures.</E>
                                 You must conduct each performance test according to the requirements in paragraphs (b) through (o) of this section and according to the methods specified in table 4 to this subpart.
                            </P>
                            <P>
                                (b) 
                                <E T="03">Periods when performance tests must be conducted.</E>
                                 You must conduct each performance test based on representative performance (
                                <E T="03">i.e.,</E>
                                 performance based on representative operating conditions as defined in § 63.2292) of the affected source for the period being tested. Representative conditions exclude periods of startup and shutdown. You may not conduct performance tests during periods of malfunction. You must describe representative operating conditions in your performance test report for the process and control systems and explain why they are representative. You must record the process information that is necessary to document operating conditions during the test and include in such record an explanation to support that such conditions are representative. Upon request, you shall make available to the Administrator such records as may be necessary to determine the conditions of performance tests.
                            </P>
                            <P>
                                (c) 
                                <E T="03">Number and duration of test runs.</E>
                                 You must conduct three separate test runs for each performance test required in this section as specified in § 63.7(e)(3). Each test run must last at least 1 hour except as specified in paragraphs (c)(1) and (2) of this section.
                            </P>
                            <P>(1) Testing of a temporary total enclosure (TTE) conducted using EPA Methods 204A through 204F of appendix M of part 51 of this chapter, which require three separate test runs of at least 3 hours each; and testing of an enclosure conducted using the alternative tracer gas method in appendix A to this subpart, which requires a minimum of three separate runs of at least 20 minutes each.</P>
                            <P>(2) Test runs longer than 1 hour may be required to meet minimum sample volume requirements specified in table 4 to this subpart.</P>
                            <P>
                                (d) 
                                <E T="03">Location of sampling sites.</E>
                                 (1) Sampling sites must be located at the inlet (if emission reduction testing or documentation of inlet methanol or formaldehyde concentration is required) and outlet of the control device (defined in § 63.2292) and prior to any releases to the atmosphere. For control sequences with wet control devices (defined in § 63.2292) followed by control devices (defined in § 63.2292), sampling sites may be located at the inlet and outlet of the control sequence and prior to any releases to the atmosphere.
                            </P>
                            <P>(2) Sampling sites for process units meeting compliance options without a control device must be located prior to any releases to the atmosphere. Facilities demonstrating compliance with a production-based compliance option for a process unit equipped with a wet control device must locate sampling sites prior to the wet control device.</P>
                            <P>(3) Sampling sites must be located at the outlet of the control device (defined in § 63.2292), if a control device is used, and prior to any releases to the atmosphere to demonstrate compliance with the compliance options in table 1C, 1D, or 1E to this subpart and for compliance with the dioxin and furan limits in § 63.2240(d)(2) and (3).</P>
                            <P>
                                (e) 
                                <E T="03">Collection of monitoring data.</E>
                                 You must collect operating parameter monitoring system or continuous emissions monitoring system (CEMS) data at least every 15 minutes during the entire performance test and determine the parameter or concentration value for the operating requirement during the performance test using the methods specified in paragraphs (k) through (o) of this section.
                            </P>
                            <P>
                                (f) 
                                <E T="03">Collection of production data.</E>
                                 To comply with any of the production-based compliance options in table 1A to this subpart, or compliance options in terms of mass per unit production in table 1C, 1D, or 1E to this subpart, you must measure and record the process unit throughput during each performance test.
                                <PRTPAGE P="41438"/>
                            </P>
                            <P>
                                (g) 
                                <E T="03">Nondetect data.</E>
                                 (1) Except as specified in paragraphs (g)(2) and (3) of this section, all nondetect data (defined in § 63.2292) must be treated as one-half of the method detection limit when determining total HAP, formaldehyde, methanol, or total hydrocarbon (THC) emission rates.
                            </P>
                            <P>(2) When showing compliance with the production-based compliance options in table 1A to this subpart, you may treat emissions of an individual HAP as zero if all three of the performance test runs result in a nondetect measurement, and the method detection limit is less than or equal to 1 parts per million by volume, dry basis (ppmvd). Otherwise, nondetect data for individual HAP must be treated as one-half of the method detection limit.</P>
                            <P>(3) Nondetect data must be treated as the method detection limit when showing compliance with § 63.2240(d)(3) or (4) and the compliance options in table 1C, 1D, or 1E to this subpart. When determining 2,3,7,8-Tetrachlorodibenzo-p-dioxin toxicity equivalency (TEQ), the value of zero may be used for nondetect results.</P>
                            <P>
                                (h) 
                                <E T="03">Calculation of percent reduction across a control system.</E>
                                 When determining the control system efficiency for any control system when complying with any of the compliance options based on percent reduction across a control system in table 1B to this subpart, as part of the performance test, you must calculate the percent reduction using the following equation:
                            </P>
                            <HD SOURCE="HD3">Equation 1 to Paragraph (h)</HD>
                            <GPH SPAN="3" DEEP="42">
                                <GID>ER06JY26.003</GID>
                            </GPH>
                            <EXTRACT>
                                <FP SOURCE="FP-2">Where:</FP>
                                <FP SOURCE="FP-2">PR = Percent reduction, percent.</FP>
                                <FP SOURCE="FP-2">CE = Capture efficiency, percent (determined for reconstituted wood product presses and board coolers as required in table 4 to this subpart).</FP>
                                <FP SOURCE="FP-2">
                                    ER
                                    <E T="52">in</E>
                                     = Emission rate of total HAP (calculated as the sum of the emission rates of acetaldehyde, acrolein, formaldehyde, methanol, phenol, and propionaldehyde), THC, formaldehyde, or methanol in the inlet vent stream of the control device, pounds per hour.
                                </FP>
                                <FP SOURCE="FP-2">
                                    ER
                                    <E T="52">out</E>
                                     = Emission rate of total HAP (calculated as the sum of the emission rates of acetaldehyde, acrolein, formaldehyde, methanol, phenol, and propionaldehyde), THC, formaldehyde, or methanol in the outlet vent stream of the control device, pounds per hour.
                                </FP>
                            </EXTRACT>
                            <P>
                                (i) 
                                <E T="03">Calculation of mass per unit production.</E>
                                 To comply with any of the production-based compliance options in table 1A to this subpart, or compliance options in terms of mass per unit production in table 1C, 1D, or 1E to this subpart, you must calculate your mass per unit production emissions for each performance test run using the following equation:
                            </P>
                            <HD SOURCE="HD3">Equation 2 to Paragraph (i)</HD>
                            <GPH SPAN="1" DEEP="46">
                                <GID>ER06JY26.004</GID>
                            </GPH>
                            <EXTRACT>
                                <FP SOURCE="FP-2">Where:</FP>
                                <FP SOURCE="FP-2">MP = Mass per unit production, pounds per oven dried ton OR pounds per thousand square feet on a specified thickness basis (see paragraph (j) of this section if you need to convert from one thickness basis to another).</FP>
                                <FP SOURCE="FP-2">
                                    ER
                                    <E T="52">HAP</E>
                                     = Emission rate of total HAP (calculated as the sum of the emission rates of acetaldehyde, acrolein, formaldehyde, methanol, phenol, and propionaldehyde) or other pollutant in table 1C, 1D, or 1E to this subpart being measured in the stack, pounds per hour.
                                </FP>
                                <FP SOURCE="FP-2">P = Process unit production rate (throughput), oven dried tons per hour OR thousand square feet per hour on a specified thickness basis;</FP>
                                <FP SOURCE="FP-2">CE = Capture efficiency, percent (determined for reconstituted wood product presses and board coolers as required in table 4 to this subpart).</FP>
                            </EXTRACT>
                            <P>
                                (j) 
                                <E T="03">Thickness basis conversion.</E>
                                 Use the following equation to convert from one thickness basis to another:
                            </P>
                            <HD SOURCE="HD3">Equation 3 to Paragraph (j)</HD>
                            <GPH SPAN="1" DEEP="29">
                                <GID>ER06JY26.005</GID>
                            </GPH>
                            <EXTRACT>
                                <FP SOURCE="FP-2">Where:</FP>
                                <FP SOURCE="FP-2">
                                    MSF
                                    <E T="52">A</E>
                                     = Thousand square feet on an A-inch basis.
                                </FP>
                                <FP SOURCE="FP-2">
                                    MSF
                                    <E T="52">B</E>
                                     = Thousand square feet on a B-inch basis.
                                </FP>
                                <FP SOURCE="FP-2">A = Old thickness you are converting from, inches.</FP>
                                <FP SOURCE="FP-2">B = New thickness you are converting to, inches.</FP>
                            </EXTRACT>
                            <P>
                                (k) 
                                <E T="03">Establishing thermal oxidizer operating requirements.</E>
                                 If you operate a thermal oxidizer, you must establish your thermal oxidizer operating parameters according to paragraphs (k)(1) through (3) of this section.
                            </P>
                            <P>
                                (1) During the performance test to meet a compliance option in table 1B or 1C to this subpart (or a PAH limit in table 1D or 1E to this subpart), you must continuously monitor the firebox temperature during each of the required 1-hour test runs. For regenerative thermal oxidizers, you may measure the temperature in multiple locations (
                                <E T="03">e.g.,</E>
                                 one location per burner) in the combustion chamber and calculate the average of the temperature measurements prior to reducing the temperature data to 15-minute averages for purposes of establishing your minimum firebox temperature. The minimum firebox temperature must then be established as the average of the three minimum 15-minute firebox temperatures monitored during the three test runs demonstrating compliance with the applicable standards. Multiple three-run performance tests may be conducted to establish a range of parameter values under different operating conditions.
                            </P>
                            <P>(2) You may establish a different minimum firebox temperature for your thermal oxidizer by submitting the notification specified in § 63.2280(g) and conducting a repeat performance test as specified in paragraph (k)(1) of this section that demonstrates compliance with the applicable compliance options of this subpart.</P>
                            <P>(3) If your thermal oxidizer is a combustion unit that accepts process exhaust into the flame zone, then you are exempt from the performance testing and monitoring requirements specified in paragraphs (k)(1) and (2) of this section. To demonstrate initial compliance, you must submit documentation with your Notification of Compliance Status showing that process exhausts controlled by the combustion unit enter into the flame zone.</P>
                            <P>
                                (l) 
                                <E T="03">Establishing catalytic oxidizer operating requirements.</E>
                                 If you operate a catalytic oxidizer, you must establish your catalytic oxidizer operating parameters according to paragraphs (l)(1) and (2) of this section.
                            </P>
                            <P>
                                (1) During the performance test to meet a compliance option in table 1B or 1C to this subpart (or a PAH limit in table 1D or 1E to this subpart), you must continuously monitor during the required 1-hour test runs either the temperature at the inlet to each catalyst bed or the temperature in the 
                                <PRTPAGE P="41439"/>
                                combustion chamber. For regenerative catalytic oxidizers, you must calculate the average of the temperature measurements from each catalyst bed inlet or within the combustion chamber prior to reducing the temperature data to 15-minute averages for purposes of establishing your minimum catalytic oxidizer temperature. The minimum catalytic oxidizer temperature must then be established as the average of the three minimum 15-minute temperatures monitored during the three test runs demonstrating compliance with the applicable standards. Multiple three-run performance tests may be conducted to establish a range of parameter values under different operating conditions.
                            </P>
                            <P>(2) You may establish a different minimum catalytic oxidizer temperature by submitting the notification specified in § 63.2280(g) and conducting a repeat performance test as specified in this paragraph (l) that demonstrates compliance with the applicable compliance options of this subpart.</P>
                            <P>
                                (m) 
                                <E T="03">Establishing biofilter operating requirements.</E>
                                 If you operate a biofilter, you must establish your biofilter operating requirements according to paragraphs (m)(1) through (3) of this section.
                            </P>
                            <P>(1) During the performance test to meet a compliance option in tables 1B through 1E to this subpart, you must continuously monitor the biofilter bed temperature during each of the required 1-hour test runs. To monitor biofilter bed temperature, you may use multiple thermocouples in representative locations throughout the biofilter bed and calculate the average biofilter bed temperature across these thermocouples prior to reducing the temperature data to 15-minute averages for purposes of establishing biofilter bed temperature limits. The biofilter bed temperature range must be established as the temperature values 10 percent below the minimum and 10 percent (not to exceed 8 °F) above the maximum 15-minute biofilter bed temperatures monitored during the three test runs demonstrating compliance with the applicable standards. You may base your biofilter bed temperature range on values recorded during previous performance tests provided that the data used to establish the temperature ranges have been obtained using the test methods required in this subpart. If you use data from previous performance tests, you must certify that the biofilter and associated process unit(s) have not been modified subsequent to the date of the performance tests. Replacement of the biofilter media with the same type of material is not considered a modification of the biofilter for purposes of this section.</P>
                            <P>(2) For a new biofilter installation, you will be allowed up to 180 days following the compliance date or 180 days following initial startup of the biofilter to complete the requirements in paragraph (m)(1) of this section.</P>
                            <P>(3) You may expand your biofilter bed temperature operating range by submitting the notification specified in § 63.2280(g) and conducting a repeat performance test as specified in paragraph (m)(1) of this section that demonstrates compliance with the applicable compliance options of this subpart.</P>
                            <P>
                                (n) 
                                <E T="03">Establishing operating requirements for process units meeting compliance options without a control device.</E>
                                 If you operate a process unit that meets a compliance option in table 1A, 1C, 1D, or 1E to this subpart without the use of a control device, you must establish your process unit operating parameters according to paragraphs (n)(1) and (2) of this section.
                            </P>
                            <P>(1) During the performance test, you must identify and document the process unit controlling parameter(s) that affect HAP emissions during the three-run performance test. The controlling parameters you identify must coincide with the representative operating conditions you describe according to paragraph (b) of this section. For each parameter, you must specify appropriate monitoring methods, monitoring frequencies, and for continuously monitored parameters, averaging times not to exceed 24 hours. The operating limit for each controlling parameter must then be established as the minimum, maximum, range, or average (as appropriate depending on the parameter) recorded during the performance test. Multiple three-run performance tests may be conducted to establish a range of parameter values under different operating conditions.</P>
                            <P>(2) You may establish different controlling parameter limits for your process unit by submitting the notification specified in § 63.2280(g) and conducting a repeat performance test as specified in paragraph (n)(1) of this section that demonstrates compliance with the compliance options in table 1A, 1C, 1D, or 1E to this subpart for an uncontrolled process unit.</P>
                            <P>
                                (o) 
                                <E T="03">Establishing operating requirements using THC CEMS.</E>
                                 If you choose to meet the operating requirements by monitoring THC concentration instead of monitoring control device or process operating parameters, you must establish your THC concentration operating requirement according to paragraphs (o)(1) and (2) of this section.
                            </P>
                            <P>(1) During the performance test, you must continuously monitor THC concentration using your CEMS during each of the required 1-hour test runs. The maximum THC concentration must then be established as the average of the three maximum 15-minute THC concentrations monitored during the three test runs demonstrating compliance with the applicable standards. Multiple three-run performance tests may be conducted to establish a range of THC concentration values under different operating conditions.</P>
                            <P>(2) You may establish a different maximum THC concentration by submitting the notification specified in § 63.2280(g) and conducting a repeat performance test as specified in paragraph (o)(1) of this section that demonstrates compliance with the compliance options in tables 1A and 1B to this subpart.</P>
                            <P>
                                (p) 
                                <E T="03">Establishing wet electrostatic precipitator operating requirements.</E>
                                 If you use a wet electrostatic precipitator to meet a compliance option in table 1D or 1E to this subpart, you must establish your wet electrostatic precipitator operating requirements according to paragraphs (p)(1) through (3) of this section except as specified in paragraph (p)(4) of this section if you are using a COMS.
                            </P>
                            <P>(1) During the PM or Hg performance test, you must continuously monitor the total secondary electric power during each of the required test runs. The minimum total secondary electric power must then be established as the average of the three minimum 15-minute total secondary electric power values monitored during the three test runs demonstrating compliance with the applicable emission limits in this subpart.</P>
                            <P>(2) During the PM, Hg, or HCl performance test, you must continuously monitor the liquid flow rate to the wet electrostatic precipitator during each of the required test runs. The minimum liquid flow rate must then be established as the average of the three minimum 15-minute liquid flow rate values monitored during the three test runs demonstrating compliance with the applicable emission limits in this subpart.</P>
                            <P>
                                (3) You may establish a different minimum total secondary power or liquid flow rate limits for your wet electrostatic precipitator by submitting the notification specified in § 63.2280(g) and conducting a repeat performance test as specified in paragraphs (p)(1) and (2) of this section that demonstrates 
                                <PRTPAGE P="41440"/>
                                compliance with the applicable emission limits in this subpart. Multiple three-run performance tests may be conducted to establish a range of parameter values under different operating conditions.
                            </P>
                            <P>(4) For a WESP followed by a control device with a dry exhaust for which you choose to use a COMS instead of WESP parameter monitoring, you must follow the procedures in paragraph (t) of this section for establishing the opacity operating limit.</P>
                            <P>
                                (q) 
                                <E T="03">Establishing dry electrostatic precipitator operating requirements.</E>
                                 If you use a dry electrostatic precipitator to meet a compliance option in table 1D or 1E to this subpart, you must establish your dry electrostatic precipitator operating requirements according to paragraphs (q)(1) and (2) of this section.
                            </P>
                            <P>(1) During the PM or Hg performance test, you must continuously monitor the total secondary electric power during each of the required test runs. The minimum total secondary electric power must then be established as the average of the three minimum 15-minute total secondary electric power values monitored during the three test runs demonstrating compliance with the emission limits in this subpart.</P>
                            <P>(2) You may establish a different minimum total secondary power limits for your dry electrostatic precipitator by submitting the notification specified in § 63.2280(g) and conducting a repeat performance test as specified in paragraph (q)(1) of this section that demonstrates compliance with the applicable emission limits in this subpart. Multiple three-run performance tests may be conducted to establish a range of parameter values under different operating conditions.</P>
                            <P>
                                (r) 
                                <E T="03">Establishing wet scrubber operating requirements.</E>
                                 If you use a wet scrubber to meet a compliance option in table 1D or 1E to this subpart, you must establish your wet scrubber operating requirements according to paragraphs (r)(1) through (4) of this section.
                            </P>
                            <P>(1) During the performance test, you must continuously monitor the scrubber liquid flow rate during each of the required test runs. The minimum liquid flow rate must then be established as the average of the three minimum 15-minute liquid flow rate values monitored during the three test runs demonstrating compliance with the compliance options in table 1D or 1E to this subpart.</P>
                            <P>(2) For a wet PM scrubber, during the PM performance test, you must continuously monitor pressure drop across the scrubber during each of the required test runs. The minimum pressure drop must then be established as the average of the three minimum 15-minute pressure drop values monitored during the three test runs demonstrating compliance with the PM limit.</P>
                            <P>(3) For wet acid gas scrubber, during the HCl performance test, you must continuously monitor the scrubber effluent pH during each of the required test runs. The minimum effluent pH must then be established as the average of the three minimum 15-minute pH values monitored during the three test runs demonstrating compliance with the HCl limit.</P>
                            <P>(4) You may establish different minimum liquid flow rate, pressure drop, or pH values for your wet scrubber by submitting the notification specified in § 63.2280(g) and conducting a repeat performance test as specified in paragraphs (r)(1) through (3) of this section that demonstrates compliance with the applicable emission limits in this subpart. Multiple three-run performance tests may be conducted to establish a range of parameter values under different operating conditions.</P>
                            <P>
                                (s) 
                                <E T="03">Establishing electrified filter bed operating requirements.</E>
                                 If you use an electrified filter bed to meet a compliance option in table 1D or 1E to this subpart, you must establish your electrified filter bed operating requirements according to paragraphs (s)(1) through (3) of this section.
                            </P>
                            <P>(1) During the PM or Hg performance test, you must continuously monitor the bed voltage and ionizer voltage during each of the required test runs. The minimum bed voltage limit and ionizer voltage limit must then be established as the average of the three minimum 15-minute bed voltage values and ionizer voltage values monitored during the three test runs demonstrating compliance.</P>
                            <P>(2) During the PM or Hg performance test, you must continuously monitor the pressure drop across the electrified filter bed during each of the required test runs. The pressure drop range limits must then be established as the average of the three minimum and three maximum 15-minute pressure drop values monitored during the three test runs demonstrating compliance with the applicable emission limits in this subpart.</P>
                            <P>(3) You may establish different bed voltage and ionizer voltage limits or pressure drop range limits for your electrified filter bed by submitting the notification specified in § 63.2280(g) and conducting a repeat performance test as specified in paragraph (s)(1) and (2) of this section that demonstrates compliance with the applicable emission limits in this subpart. Multiple three-run performance tests may be conducted to establish a range of parameter values under different operating conditions.</P>
                            <P>
                                (t) 
                                <E T="03">Establishing operating requirements using opacity measured with a COMS.</E>
                                 If you use a mechanical collector (or other dry control device not listed elsewhere in table 2 to the subpart) or WESP followed by a control device with a dry exhaust (for which you choose to use a COMS) to meet a compliance option in table 1D or 1E to this subpart, you must establish your operating requirements according to paragraphs (t)(1) and (2) of this section.
                            </P>
                            <P>(1) During the PM performance test, you must continuously monitor opacity during each of the required test runs. The maximum opacity limit must then be established as either 10 percent opacity, or the highest hourly average computed from the 6-minute opacity values monitored during the three test runs demonstrating compliance with the PM limit.</P>
                            <P>(2) You may establish different opacity limits by submitting the notification specified in § 63.2280(g) and conducting a repeat performance test as specified in paragraph (t)(1) of this section that demonstrates compliance with the applicable emission limits in this subpart. Multiple three-run performance tests may be conducted to establish a range of opacity values under different operating conditions.</P>
                            <P>
                                (u) 
                                <E T="03">Establishing operating requirements based on pressure drop with opacity observations.</E>
                                 If you use a mechanical collector (or other dry control device not listed elsewhere in table 2 to this subpart) to meet a compliance option in table 1D or 1E to this subpart, and you choose to use a combination of pressure drop and opacity observations instead of a COMS to demonstrate continuous compliance, you must establish your operating requirements according to paragraphs (u)(1) through (3) of this section.
                            </P>
                            <P>(1) During the PM performance test, you must continuously monitor pressure drop across the mechanical collector (or other dry control device) during each of the required test runs. The minimum pressure drop limit must then be established as the average of the three minimum 15-minute pressure drop values monitored during the three test runs demonstrating compliance with the PM limit.</P>
                            <P>
                                (2) During the PM performance test, you must conduct opacity observations of the control device outlet emissions to the atmosphere using EPA Method 9 of appendix A-4 to part 60 of this chapter. You must establish the maximum opacity operating limit as the average of 
                                <PRTPAGE P="41441"/>
                                the 6-minute opacity observations during the three test runs demonstrating compliance with the PM limit, or 10 percent opacity, whichever is greater.
                            </P>
                            <P>(3) You may establish a different pressure drop limit or opacity observation limit by submitting the notification specified in § 63.2280(g) and conducting a repeat performance test as specified in paragraph (u)(1) or (2) of this section that demonstrates compliance with the applicable emission limits in this subpart. Multiple three-run performance tests may be conducted to establish a range of parameter values under different operating conditions.</P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="40" PART="63">
                        <AMDPAR>11. Revise § 63.2268 to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 63.2268 </SECTNO>
                            <SUBJECT>Initial compliance demonstration for a wet control device.</SUBJECT>
                            <P>If you use a wet control device as the sole means of reducing HAP emissions (including total HAP, methanol, or formaldehyde), you must develop and implement a plan for review and approval to address how organic HAP captured in the wastewater from the wet control device is contained or destroyed to minimize re-release to the atmosphere such that the desired emissions reductions are obtained. You must submit the plan with your Notification of Compliance Status.</P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="40" PART="63">
                        <AMDPAR>12. Amend § 63.2269 by revising paragraph (c) introductory text and adding paragraphs (e) through (o) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 63.2269 </SECTNO>
                            <SUBJECT>What are my monitoring installation, operation, and maintenance requirements?</SUBJECT>
                            <STARS/>
                            <P>
                                (c) 
                                <E T="03">Wood moisture monitoring.</E>
                                 For each furnish or veneer moisture meter, you must meet the requirements in paragraphs (a)(1) through (3) and (c)(1) through (5) of this section. This paragraph (c) does not apply for lumber moisture monitoring (covered in paragraphs (n) and (o) of this section) to show compliance with the lumber kilns standards in § 63.2241(e).
                            </P>
                            <STARS/>
                            <P>
                                (e) 
                                <E T="03">Continuous opacity monitoring systems (COMS).</E>
                                 You must install, operate, certify and maintain each COMS according to the procedures in paragraphs (e)(1) through (7) of this section by the compliance date specified in § 63.2233.
                            </P>
                            <P>(1) Each COMS must be installed, operated, and maintained according to Performance Specification 1 at appendix B to part 60 of this chapter.</P>
                            <P>(2) You must conduct a performance evaluation of each COMS according to the requirements in § 63.8(e) and according to Performance Specification 1 at appendix B to part 60 of this chapter.</P>
                            <P>(3) As specified in § 63.8(c)(4)(i), each COMS must complete a minimum of one cycle of sampling and analyzing for each successive 10-second period and one cycle of data recording for each successive 6-minute period.</P>
                            <P>(4) The COMS data must be reduced as specified in §§ 63.8(g)(2) and 63.2270(e).</P>
                            <P>(5) You must document procedures and acceptance criteria for operating and maintaining each COMS according to the requirements in § 63.8(d). At a minimum, the documentation must include a daily calibration drift assessment, a quarterly performance audit, and an annual zero alignment audit of each COMS.</P>
                            <P>(6) You must operate and maintain each COMS according to the requirements of § 63.8(e). You must identify periods the COMS is out of control including any periods that the COMS fails to pass a daily calibration drift assessment, a quarterly performance audit, or an annual zero alignment audit. Any 6-minute period for which the monitoring system is out of control and data are not available for a required calculation constitutes a deviation from the monitoring requirements.</P>
                            <P>(7) You must determine and record all the 6-minute averages (and 24-hour block averages as applicable) collected for periods during which the COMS is not out of control.</P>
                            <P>
                                (f) 
                                <E T="03">Pressure monitoring.</E>
                                 If you have an operating requirement that requires the use of a pressure monitoring system, you must meet the requirements in paragraphs (a) and (f)(1) through (6) of this section.
                            </P>
                            <P>
                                (1) Install the pressure sensor(s) in a position that provides a representative measurement of the pressure (
                                <E T="03">e.g.,</E>
                                 PM scrubber pressure drop).
                            </P>
                            <P>(2) Minimize or eliminate pulsating pressure, vibration, and internal and external corrosion consistent with good engineering practices.</P>
                            <P>(3) Use a pressure sensor with a minimum tolerance of 1.27 centimeters of water or a minimum tolerance of 1 percent of the pressure monitoring system operating range, whichever is less.</P>
                            <P>
                                (4) Perform checks at least once each process operating day to ensure pressure measurements are not obstructed (
                                <E T="03">e.g.,</E>
                                 check for pressure tap pluggage daily).
                            </P>
                            <P>(5) Conduct a performance evaluation of the pressure monitoring system at the time of each performance test but no less frequently than annually.</P>
                            <P>(6) If at any time the measured pressure exceeds the manufacturer's specified maximum operating pressure range, conduct a performance evaluation of the pressure monitoring system and confirm that the pressure monitoring system continues to meet the performance requirements. Alternatively, install and verify the operation of a new pressure sensor.</P>
                            <P>
                                (g) 
                                <E T="03">pH monitoring.</E>
                                 If you have an operating limit that requires a pH monitoring system, you must meet the requirements in paragraphs (a) and (g)(1) through (4) of this section.
                            </P>
                            <P>(1) Install the pH sensor in a position that provides a representative measurement of scrubber effluent pH.</P>
                            <P>(2) Ensure the sample is properly mixed and representative of the fluid to be measured.</P>
                            <P>(3) Calibrate the pH monitoring system according to the manufacturer's instructions. Clean the pH probe at least once each process operating day. Maintain on-site documentation that your calibration frequency is sufficient to maintain the specified accuracy of your device.</P>
                            <P>(4) Conduct a performance evaluation (including a two-point calibration with one of the two buffer solutions having a pH within 1 of the pH of the operating limit) of the pH monitoring system at the time of each performance test but no less frequently than annually.</P>
                            <P>
                                (h) 
                                <E T="03">Liquid flow rate monitoring.</E>
                                 If you have an operating limit that requires the use of a flow measurement device, you must meet the requirements in paragraphs (h)(1) through (4) of this section.
                            </P>
                            <P>(1) Locate the flow sensor and other necessary equipment in a position that provides a representative flow.</P>
                            <P>(2) Use a flow sensor with a measurement sensitivity of 2 percent of the flow rate.</P>
                            <P>(3) Reduce swirling flow or abnormal velocity distributions due to upstream and downstream disturbances.</P>
                            <P>(4) Conduct a flow sensor calibration check at least annually.</P>
                            <P>
                                (i) 
                                <E T="03">Secondary electric power input monitoring.</E>
                                 If you have an operating requirement that requires a secondary electric power monitoring system, you must meet the requirements in paragraphs (a) and (i)(1) and (2) of this section.
                            </P>
                            <P>(1) Install sensors to measure (secondary) voltage and current to the precipitator collection plates.</P>
                            <P>(2) Conduct a performance evaluation of the electric power monitoring at the time of each performance test but no less frequently than annually.</P>
                            <P>
                                (j) 
                                <E T="03">Electrified filter bed voltage monitoring.</E>
                                 If you have an operating 
                                <PRTPAGE P="41442"/>
                                requirement that requires a voltage monitoring system, you must meet the requirements in paragraphs (a) and (j)(1) and (2) of this section.
                            </P>
                            <P>(1) Install sensors to measure voltage to the electrified filter bed.</P>
                            <P>(2) Conduct a performance evaluation of the voltage monitoring at the time of each performance test but no less frequently than annually.</P>
                            <P>
                                (k) 
                                <E T="03">Combustion unit bypass stack monitoring.</E>
                                 If you have a bypass stack in which combustion unit exhaust streams routinely used to direct-fire a PCWP dryer or lumber kiln are temporarily vented to the atmosphere without passing through the direct-fired PCWP dryer or lumber kiln, you must meet the requirements in paragraphs (a) and (k)(1) and (2) of this section.
                            </P>
                            <P>(1) Install a sensor to continuously monitor an indicator of bypass stack usage such as flow damper position or temperature.</P>
                            <P>(2) Conduct a performance evaluation of the bypass stack monitor at the time of each performance test but no less frequently than annually.</P>
                            <P>
                                (l) 
                                <E T="03">Process unit bypass stack monitoring.</E>
                                 If you have a bypass stack that allows a process unit exhaust stream to temporarily vent to the atmosphere while bypassing a control device routinely used to meet the compliance options in table 1B, 1C, 1D, or 1E to this subpart, you must meet the requirements in paragraphs (a) and (l)(1) and (2) of this section.
                            </P>
                            <P>(1) Install a sensor to continuously monitor an indicator of bypass stack usage such as flow damper position or temperature.</P>
                            <P>(2) Conduct a performance evaluation of the bypass stack monitor at the time of each performance test but no less frequently than annually.</P>
                            <P>
                                (m) 
                                <E T="03">Lumber kiln temperature monitoring.</E>
                                 Temperature monitors used in lumber kilns must meet the requirements in paragraphs (a), (b), and (m)(1) and (2) of this section.
                            </P>
                            <P>(1) For purposes of complying with dry bulb temperature limits in § 63.2241(e)(3)(i) or (ii), dry bulb temperature monitor(s) must be located in a position to determine the dry bulb temperature of the heated air that exits the lumber.</P>
                            <P>(2) Facilities complying with the site-specific plan in § 63.2241(e)(3)(iii) must describe the number and location of temperature monitors in the site-specific plan.</P>
                            <P>
                                (n) 
                                <E T="03">Lumber moisture monitoring under hybrid option.</E>
                                 The requirements in paragraphs (a), (b), and (n)(1) and (2) of this section apply for lumber kilns using the hybrid temperature and lumber moisture monitoring work practice option in § 63.2241(e)(3)(ii). The lumber moisture content (weight percent, dry basis) must be monitored either within the kiln or at a location after the lumber exits the kiln.
                            </P>
                            <P>(1) For lumber moisture content measured after the lumber exits the kiln, you must obtain at least one lumber moisture content measurement per either twenty thousand board feet (20 MBF or 20,000 BF) of board lumber produced or per 2,000 cubic feet (2,000 CF) of round lumber produced.</P>
                            <P>(2) For lumber moisture content measured in the kiln, lumber moisture measurements must be obtained as follows for each kiln type:</P>
                            <P>(i) For batch kilns with in-kiln moisture monitoring, lumber moisture measurements must be distributed in different areas of the kiln. At least one lumber moisture reading per crib must be obtained.</P>
                            <P>(ii) For continuous kilns with in-kiln moisture monitoring, lumber moisture measurements must be obtained for each crib of lumber dried.</P>
                            <P>
                                (o) 
                                <E T="03">Lumber moisture monitoring under site-specific plan.</E>
                                 The requirements in paragraphs (a) and (o)(1) and (2) of this section apply for lumber facilities monitoring lumber moisture under the site-specific plan work practice option § 63.2241(e)(3)(iii).
                            </P>
                            <P>(1) The site-specific plan must include a method for monitoring lumber moisture content (weight percent, dry basis) and specify the location of such monitoring within the lumber manufacturing process (for example, at the kiln unloading track, in lumber storage, or at the planer).</P>
                            <P>(2) You must obtain at least one lumber moisture content measurement per twenty thousand board feet (20 MBF or 20,000 BF) of board lumber produced or per 2,000 cubic feet (2,000 CF) of round lumber produced.</P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="40" PART="63">
                        <AMDPAR>13. Amend § 63.2270 by revising paragraph (e) and adding paragraphs (g) through (k) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 63.2270 </SECTNO>
                            <SUBJECT> How do I monitor and collect data to demonstrate continuous compliance?</SUBJECT>
                            <STARS/>
                            <P>(e) For dry rotary dryer and veneer predryer wood moisture monitoring, dry rotary dryer temperature monitoring, biofilter bed temperature monitoring, biofilter outlet THC monitoring, and continuous opacity monitoring, determine the 24-hour block average of all recorded readings, calculated after every 24 hours of operation as the average of the evenly spaced recorded readings in the previous 24 operating hours (excluding periods described in paragraphs (b) and (c) of this section).</P>
                            <STARS/>
                            <P>(g) The requirements in paragraphs (c) through (f) of this section do not apply for monitoring the usage of process unit bypass stacks or combustion unit bypass stacks as such monitoring must be conducted continuously at all times that the process unit or combustion unit (that routinely direct-fires a PCWP dryer or lumber kiln) is operating. You must record the dates and times when each bypass stack is used and use the recording readings (excluding invalid data described in paragraph (b) of this section) to calculate and report the total duration of bypass stack usage during the semiannual reporting period.</P>
                            <P>(h) For lumber kilns, the following temperature data averaging requirements apply:</P>
                            <P>
                                (1) 
                                <E T="03">Temperature limit and hybrid options.</E>
                                 You must continuously monitor and record the dry bulb temperature during the kiln drying cycle and record the dry bulb temperature at least once every 15 minutes as specified in § 63.2269(m). The readings from multiple dry bulb temperature monitors positioned to determine the temperature of the heated air that exits the lumber may be averaged together to determine the kiln-wide, dry bulb temperature.
                            </P>
                            <P>(i) For batch kilns, calculate the average from the recorded readings during each batch cycle, and maintain the batch cycle average dry bulb temperature at or below the maximum temperature limits specified in either § 63.2241(e)(3)(i) or (ii), whichever applies.</P>
                            <P>(ii) For continuous dry kilns, calculate the daily block average from the recorded readings and maintain the daily block average dry bulb temperature at or below the maximum temperature limits specified in either § 63.2241(e)(3)(i) or (ii), whichever applies.</P>
                            <P>
                                (2) 
                                <E T="03">Site specific plan option.</E>
                                 You must continuously monitor the temperature parameter (such as wet or dry bulb temperature, wet bulb depression, or temperature drop across the load) specified in your site-specific plan. You must record the temperature parameter at least every 15 minutes and calculate the 3-hour block average for comparison to the site-specific temperature limit.
                            </P>
                            <P>(i) For lumber kilns using the hybrid option, the following lumber moisture data averaging requirements must be followed:</P>
                            <P>
                                (1) Using the lumber moisture content measurement data collected according to § 63.2269(n), calculate and record the semiannual average kiln-dried lumber 
                                <PRTPAGE P="41443"/>
                                moisture content for lumber with a given moisture specification produced at the facility.
                            </P>
                            <P>(2) Compare the semiannual average lumber moisture content for each moisture specification produced at the facility to the applicable minimum kiln-dried moisture content limits included in table 11 to this subpart to determine compliance.</P>
                            <P>(j) For lumber kilns using the site-specific option, the following lumber moisture data averaging requirements must be followed:</P>
                            <P>(1) Using the lumber moisture content measurement data collected, calculate and record the monthly and semiannual average kiln-dried lumber moisture content.</P>
                            <P>(2) Compare the monthly average lumber moisture content to the minimum kiln-dried lumber moisture content limit included in the site-specific plan based on § 63.2241(e)(4) and table 11 to this subpart. You must take corrective action if the monthly average lumber moisture content determined in paragraph (j)(1) of this section is below the minimum lumber moisture content limit in the site-specific plan. You must maintain records of corrective actions taken and report corrective actions in the semiannual report.</P>
                            <P>(3) Compare the semiannual average kiln-dried lumber moisture content to the minimum lumber moisture content limit included in the site-specific plan based on § 63.2241(e)(4) of this section and table 11 to this subpart to determine compliance.</P>
                            <P>(k) If you observe opacity using EPA Method 9 of appendix A-4 to part 60 of this chapter (in conjunction with pressure drop monitoring) instead of using a COMS for mechanical collectors (or other dry control device not listed elsewhere in table 2 to this subpart) to meet a compliance option in table 1D or 1E to this subpart, you must follow the procedure for demonstrating continuous compliance with the opacity observation limit in paragraphs (k)(1) and (2) of this section.</P>
                            <P>(1) A qualified observer must conduct two weekly 6-minute opacity observations of the mechanical collector (or other dry control device) exhaust to the atmosphere according to EPA Method 9 of appendix A-4 in part 60 of this chapter and 40 CFR 60.11 to demonstrate the opacity remains below the maximum limit established according to § 63.2262(u).</P>
                            <P>(2) If the average of the two weekly 6-minute opacity observations exceeds the maximum opacity limit established in paragraph (k)(1) of this section, you must take appropriate corrective action to correct the above normal emissions as soon as practicable and within the monitoring period and record the action taken.</P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="40" PART="63">
                        <AMDPAR>14. Amend § 63.2271 by revising paragraph (b)(4) and adding paragraph (c) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 63.2271 </SECTNO>
                            <SUBJECT>How do I demonstrate continuous compliance with the compliance options, operating requirements, and work practice requirements?</SUBJECT>
                            <STARS/>
                            <P>(b) * * *</P>
                            <P>(4) Instances of safety-related shutdown, pressurized refiner startup and shutdown, and startup and shutdown of direct-fired softwood veneer dryer gas-fired burners subject to the work practice requirements in table 3 to this subpart (rows 6 through 8) must be reported as required in § 63.2281(c)(4). Instances when the work practice requirements in table 3 to this subpart (rows 6 through 8) are used are not considered to be deviations from (or violations of) the otherwise applicable compliance options, operating requirements and work practice requirements (in rows 1 through 5 of table 3 to this subpart) as long as you do not exceed the minimum amount of time necessary for these events and continuously monitor process unit bypass stack usage during the events as required in § 63.2240(e) and table 2 to this subpart.</P>
                            <P>(c) For direct-fired PCWP dryers (including direct wood-fired PCWP dryers and direct natural gas-fired PCWP dryers) and direct-fired lumber kilns, demonstrate compliance with the annual tune-up requirement in § 63.2241(d) and table 3 to this subpart as specified in paragraphs (c)(1) through (8) of this section.</P>
                            <P>(1) You must conduct the tune-up while burning the type of fuel (or fuels in case of units that routinely burn a mixture) that provided the majority of the heat input to PCWP dryer or lumber kiln over the 12 months prior to the tune-up.</P>
                            <P>(2) Inspect the burner and (if applicable) grates. Clean, repair, or replace any components of the burner and grates as necessary. This work must be initiated within 30 days after the inspection and completed within 180 days following the inspection identifying the need for the corrective action. If the corrective action cannot be completed within 180 days, a written request for an extension may be submitted to the delegated authority, who may grant an extension if they determine additional time is necessary.</P>
                            <P>(3) For direct-fired PCWP dryers with burners in the dryer or separate combustion unit(s), inspect the flame pattern (as applicable) and adjust the burner as necessary to optimize the flame pattern. The adjustment should be consistent with the manufacturer's specifications, if available.</P>
                            <P>(4) For each direct-fired PCWP dryer with a burner in the dryer, cycle the burner through its firing range to ensure the burner functions satisfactorily throughout the operating range.</P>
                            <P>(5) Inspect the combustion air system and system that controls the air-to-fuel ratio to make sure it is functioning properly (according to the manufacturer's guidelines, if available).</P>
                            <P>(6) Inspect the fuel delivery system and, if applicable, the ash removal system to make sure each system is functioning properly (according to the manufacturer's guidelines, if available).</P>
                            <P>(7) Record the results of each inspection and corrective action taken, as required in § 63.2282.</P>
                            <P>(8) The required inspections and any necessary maintenance must be performed annually (no more than 13 months after previous inspection). If inspections are performed more frequently than annually, required equipment maintenance and replacement may be delayed until the next scheduled shutdown of the combustion unit firing a PCWP dryer or lumber kiln.</P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="40" PART="63">
                        <AMDPAR>15. Amend § 63.2280 by:</AMDPAR>
                        <AMDPAR>a. Revising paragraphs (a) and (b) and paragraph (d) introductory text;</AMDPAR>
                        <AMDPAR>b. Removing and reserving paragraph (f);</AMDPAR>
                        <AMDPAR>c. Revising paragraph (g) introductory text; and</AMDPAR>
                        <AMDPAR>d. Removing and reserving paragraph (g)(2).</AMDPAR>
                        <P>The revisions read as follows:</P>
                        <SECTION>
                            <SECTNO>§ 63.2280 </SECTNO>
                            <SUBJECT> What notifications must I submit and when?</SUBJECT>
                            <P>(a) You must submit all of the notifications in §§ 63.7(b) and (c), 63.8(e) and (f)(4) and (6), 63.9(b) through (e) and (g) and (h) by the dates specified.</P>
                            <P>(b) You must submit an Initial Notification no later than 120 calendar days after September 28, 2004, 120 calendar days after initial startup, or no later than 120 days after the source becomes subject to this subpart, or after initial startup, whichever is later, as specified in § 63.9(b)(2). Initial notifications required in § 63.9(b) must be submitted in a user-specified format such as portable document format (PDF) following the procedure specified in § 63.9(k) except the Confidential Business Information (CBI) should be submitted according to § 63.2281(k).</P>
                            <STARS/>
                            <PRTPAGE P="41444"/>
                            <P>(d) If you are required to conduct a performance test, design evaluation, or other compliance demonstration as specified in tables 4 through 6 to this subpart, or a repeat performance test as specified in table 7 to this subpart, you must submit a Notification of Compliance Status as specified in § 63.9(h)(2)(ii). Notifications of Compliance Status must be submitted in a user-specified format such as portable document format (PDF) following the procedure specified in § 63.9(k) except the CBI should be submitted according to § 63.2281(k).</P>
                            <STARS/>
                            <P>(g) You must notify the EPA Administrator within 30 days before you take any of the actions specified in paragraphs (g)(1) and (3) of this section.</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="40" PART="63">
                        <AMDPAR>16. Revise § 63.2281 to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 63.2281 </SECTNO>
                            <SUBJECT>What reports must I submit and when?</SUBJECT>
                            <P>(a) You must submit each report in table 9 to this subpart that applies to you.</P>
                            <P>(b) Unless the EPA Administrator has approved a different schedule for submission of reports under § 63.10(a), you must submit each report by the date in table 9 to this subpart and as specified in paragraphs (b)(1) through (6) of this section.</P>
                            <P>(1) The first compliance report must cover the period beginning on the compliance date that is specified for your affected source in § 63.2233 ending on June 30 or December 31, and lasting at least 6 months, but less than 12 months. For example, if your compliance date is March 1, then the first semiannual reporting period would begin on March 1 and end on December 31.</P>
                            <P>(2) The first compliance report must be postmarked or delivered no later than July 31 or January 31 for compliance periods ending on June 30 and December 31, respectively.</P>
                            <P>(3) Each subsequent compliance report must cover the semiannual reporting period from January 1 through June 30 or the semiannual reporting period from July 1 through December 31.</P>
                            <P>(4) Each subsequent compliance report must be postmarked or delivered no later than July 31 or January 31 for the semiannual reporting period ending on June 30 and December 31, respectively.</P>
                            <P>(5) For each affected source that is subject to permitting regulations pursuant to 40 CFR part 70 or 71, and if the permitting authority has established dates for submitting semiannual reports pursuant to § 70.6(a)(3)(iii)(A) or § 71.6(a)(3)(iii)(A), you may submit the first and subsequent compliance reports according to the dates the permitting authority has established instead of according to the dates in paragraphs (b)(1) through (4) of this section.</P>
                            <P>(6) Submit all reports following the procedure specified in § 63.9(k) except the CBI should be submitted according to paragraph (k) of this section.</P>
                            <P>(c) The compliance report must contain the information in paragraphs (c)(1) through (11) of this section.</P>
                            <P>(1) Company name and address.</P>
                            <P>(2) Statement by a responsible official with that official's name, title, and signature, certifying the truth, accuracy, and completeness of the content of the report.</P>
                            <P>(3) Date of report and beginning and ending dates of the reporting period.</P>
                            <P>(4) The compliance report must include the number of instances and total amount of time during the reporting period in which each of the work practice requirements in table 3 to this subpart (row 6, 7, or 8) is used in place of the otherwise applicable compliance options, operating requirements, and work practice requirements (in table 3 to this subpart rows 1 through 5). If a work practice in table 3 to this subpart (row 6, 7, or 8) is used for more than a total of 100 hours during the semiannual reporting period, you must report the date, time and duration of each instance when that one work practice exceeding 100 hours was used.</P>
                            <P>(5) A description of control device maintenance performed while the control device was offline and one or more of the process units controlled by the control device was operating, including the information specified in paragraphs (c)(5)(i) through (iii) of this section.</P>
                            <P>(i) The date and time when the control device was shut down and restarted.</P>
                            <P>(ii) Identification of the process units that were operating and the number of hours that each process unit operated while the control device was offline.</P>
                            <P>(iii) A statement of whether or not the control device maintenance was included in your approved routine control device maintenance exemption developed pursuant to § 63.2251. If the control device maintenance was included in your approved routine control device maintenance exemption, then you must report the information in paragraphs (c)(5)(iii)(A) through (C) of this section.</P>
                            <P>(A) The total amount of time that each process unit controlled by the control device operated during the semiannual compliance period and during the previous semiannual compliance period.</P>
                            <P>(B) The amount of time that each process unit controlled by the control device operated while the control device was down for maintenance covered under the routine control device maintenance exemption during the semiannual compliance period and during the previous semiannual compliance period.</P>
                            <P>(C) Based on the information recorded under paragraphs (c)(5)(iii)(A) and (B) of this section for each process unit, compute the annual percent of process unit operating uptime during which the control device was offline for routine maintenance using the following equation.</P>
                            <HD SOURCE="HD3">Equation 1 to Paragraph (c)(5)(iii)(C)</HD>
                            <GPH SPAN="1" DEEP="48">
                                <GID>ER06JY26.006</GID>
                            </GPH>
                            <EXTRACT>
                                <FP SOURCE="FP-2">Where:</FP>
                                <FP SOURCE="FP-2">RM = Annual percentage of process unit uptime during which control device is down for routine control device maintenance.</FP>
                                <FP SOURCE="FP-2">
                                    PU
                                    <E T="52">p</E>
                                     = Process unit uptime for the previous semiannual compliance period.
                                </FP>
                                <FP SOURCE="FP-2">
                                    PU
                                    <E T="52">c</E>
                                     = Process unit uptime for the current semiannual compliance period.
                                </FP>
                                <FP SOURCE="FP-2">
                                    DT
                                    <E T="52">p</E>
                                     = Control device downtime claimed under the routine control device maintenance exemption for the previous semiannual compliance period.
                                </FP>
                                <FP SOURCE="FP-2">
                                    DT
                                    <E T="52">c</E>
                                     = Control device downtime claimed under the routine control device maintenance exemption for the current semiannual compliance period.
                                </FP>
                            </EXTRACT>
                            <P>(6) [Reserved]</P>
                            <P>(7) If there are no deviations from any applicable compliance option or operating requirement, and there are no deviations from the requirements for work practice requirements in table 8 to this subpart, a statement that there were no deviations from the compliance options, operating requirements, or work practice requirements during the reporting period.</P>
                            <P>(8) If there were no periods during which the continuous monitoring system (CMS), including CEMS, COMS, and CPMS, was out-of-control as specified in § 63.8(c)(7), a statement that there were no periods during which the CMS was out-of-control during the reporting period.</P>
                            <P>
                                (9) For each combustion unit subject to tune-up requirements, include the date of the most recent burner tune-up 
                                <PRTPAGE P="41445"/>
                                and a summary of corrective actions taken.
                            </P>
                            <P>(10) The total time (hours) during the semiannual reporting period that each combustion unit bypass stack or each process unit bypass stack was used.</P>
                            <P>(11) For each lumber kiln, the information specified in paragraphs (c)(11)(i) though (v) of this section.</P>
                            <P>(i) A description of updates to the O&amp;M plan made during the reporting period, as required under § 63.2253(a)(4).</P>
                            <P>(ii) If complying with the dry bulb temperature limit option in § 63.2241(e)(3)(i), note the applicable maximum dry bulb temperature limit according to kiln type, and report deviations from the dry bulb temperature limit batch cycle average (for batch kilns) or daily block average (for continuous kilns) calculated according to § 63.2270(h)(1).</P>
                            <P>(iii) If complying with a site-specific temperature limit under a site-specific plan in § 63.2241(e)(3)(iii)(A), note the site-specific temperature parameter limit, and report deviations from the 3-hour block average temperature parameter limit included in the site-specific plan calculated according to § 63.2270(h)(2).</P>
                            <P>(iv) If complying with the hybrid option in § 63.2241(e)(3)(ii), note the applicable maximum dry bulb temperature limit according to kiln type, report deviations from the dry bulb temperature limit batch cycle average (for batch kilns) or daily block average (for continuous kilns) calculated according to § 63.2270(h)(1), and report the semiannual average lumber moisture content determined according to § 63.2270(i).</P>
                            <P>(v) If complying with a site-specific approach for monitoring kiln-dried lumber moisture content under a site-specific plan in § 63.2241(e)(3)(iii)(B), describe the lumber moisture monitoring method and location and note the site-specific minimum kiln-dried lumber moisture content limit included in the site-specific plan. Report corrective actions taken as a result of monthly lumber moisture content averages (determined according to § 63.2270(g)) that are below the minimum lumber moisture content limit in the site-specific plan. Report the semiannual average kiln-dried lumber moisture content value determined according to § 63.2270(g).</P>
                            <P>(d) For each deviation from a compliance option or operating requirement and for each deviation from the work practice requirements in table 8 to this subpart that occurs at an affected source where you are not using a CMS to comply with the compliance options, operating requirements, or work practice requirements in this subpart, the compliance report must contain the information in paragraphs (c)(1) through (5) of this section and in paragraphs (d)(1) and (2) of this section. This includes periods of startup, shutdown, and malfunction and routine control device maintenance.</P>
                            <P>(1) The total operating time of each affected source during the reporting period.</P>
                            <P>(2) Information on the date, time, duration, and cause of deviations (including unknown cause, if applicable), as applicable, and the corrective action taken.</P>
                            <P>(e) For each deviation from a compliance option, operating requirement, or work practice requirement occurring at an affected source where you are using a CMS to comply with the compliance options, operating requirements, or work practice requirements in this subpart, you must include the information in paragraphs (c)(1) through (5) and (e)(2) through (13) of this section. This includes periods of startup, shutdown, and malfunction and routine control device maintenance.</P>
                            <P>(1) [Reserved]</P>
                            <P>(2) The date, time, and duration that each CMS was inoperative, except for zero (low-level) and high-level checks.</P>
                            <P>(3) The date, time, and duration that each CMS was out-of-control, including the information in § 63.8(c)(8).</P>
                            <P>(4) The date and time that each deviation started and stopped, and whether each deviation occurred during a period of startup, shutdown, or malfunction; during a period of control device maintenance covered in your approved routine control device maintenance exemption; or during another period.</P>
                            <P>(5) A summary of the total duration of the deviation during the reporting period and the total duration as a percent of the total source operating time during that reporting period.</P>
                            <P>(6) A breakdown of the total duration of the deviations during the reporting period into those that are due to startup, shutdown, control system problems, control device maintenance, process problems, other known causes, and other unknown causes.</P>
                            <P>(7) A summary of the total duration of CMS downtime during the reporting period and the total duration of CMS downtime as a percent of the total source operating time during that reporting period.</P>
                            <P>(8) A brief description of the process units.</P>
                            <P>(9) A brief description of the CMS.</P>
                            <P>(10) The date of the latest CMS certification or audit.</P>
                            <P>(11) A description of any changes in CMS, processes, or controls since the last reporting period.</P>
                            <P>(12) For any failure to meet a compliance option in § 63.2240, including the compliance options in table 1A through 1E to this subpart, provide an estimate of the quantity of each regulated pollutant emitted over any emission limit, and a description of the method used to estimate the emissions.</P>
                            <P>(13) The total operating time of each affected source during the reporting period. </P>
                            <P>(f) [Reserved]</P>
                            <P>(g) Each affected source that has obtained a title V operating permit pursuant to 40 CFR part 70 or 71 must report all deviations as defined in this subpart in the semiannual monitoring report required by § 70.6(a)(3)(iii)(A) or § 71.6(a)(3)(iii)(A). If an affected source submits a compliance report pursuant to table 9 to this subpart along with, or as part of, the semiannual monitoring report required by § 70.6(a)(3)(iii)(A) or § 71.6(a)(3)(iii)(A), and the compliance report includes all required information concerning deviations from any compliance option, operating requirement, or work practice requirement in this subpart, submission of the compliance report shall be deemed to satisfy any obligation to report the same deviations in the semiannual monitoring report. However, submission of a compliance report shall not otherwise affect any obligation the affected source may have to report deviations from permit requirements to the permitting authority.</P>
                            <P>
                                (h) If you are required to submit reports following the procedure specified in this paragraph (h), you must submit reports to the EPA via the Compliance and Emissions Data Reporting Interface (CEDRI), which can be accessed through the EPA's Central Data Exchange (CDX) (
                                <E T="03">https://cdx.epa.gov/</E>
                                ). For semiannual compliance reports required in this section and table 9 (row 1) to this subpart, you must use the appropriate electronic report template on the CEDRI website (
                                <E T="03">https://www.epa.gov/electronic-reporting-air-emissions/compliance-and-emissions-data-reporting-interface-cedri</E>
                                ) for this subpart. The date report templates become available will be listed on the CEDRI website. If the reporting form for the semiannual compliance report specific to this subpart is not available in CEDRI at the time that the report is due, you must submit the report to the 
                                <PRTPAGE P="41446"/>
                                Administrator at the appropriate addresses listed in § 63.13. You must begin submitting all subsequent reports via CEDRI in the first full reporting period after the report template for this subpart has been available in CEDRI for 1 year. The report must be submitted by the deadline specified in this subpart, regardless of the method in which the report is submitted.
                            </P>
                            <P>(i) Within 60 days after the date of completing each performance test required by this subpart, you must submit the results of the performance test following the procedures specified in paragraphs (i)(1) through (3) of this section.</P>
                            <P>
                                (1) 
                                <E T="03">Data collected using test methods supported by the EPA's Electronic Reporting Tool (ERT) as listed on the EPA's ERT website (https://www.epa.gov/electronic-reporting-air-emissions/electronic-reporting-tool-ert) at the time of the test.</E>
                                 Submit the results of the performance test to the EPA via CEDRI, which can be accessed through the EPA's CDX (
                                <E T="03">https://cdx.epa.gov/</E>
                                ). The data must be submitted in a file format generated through the use of the EPA's ERT. Alternatively, you may submit an electronic file consistent with the extensible markup language (XML) schema listed on the EPA's ERT website.
                            </P>
                            <P>
                                (2) 
                                <E T="03">Data collected using test methods that are not supported by the EPA's ERT as listed on the EPA's ERT website at the time of the test.</E>
                                 The results of the performance test must be included as an attachment in the ERT or an alternate electronic file consistent with the XML schema listed on the EPA's ERT website. Submit the ERT generated package or alternative file to the EPA via CEDRI.
                            </P>
                            <P>
                                (3) 
                                <E T="03">Confidential Business Information (CBI).</E>
                                 If you claim some of the information submitted under this paragraph (i) is CBI, you must submit a complete file, including information claimed to be CBI, to the EPA. The file must be generated through the use of the EPA's ERT or an alternate electronic file consistent with the XML schema listed on the EPA's ERT website. Submit the file according to paragraph (k) of this section except it should be sent to the attention of the Branch Supervisor in the Measurement Strategy Branch.
                            </P>
                            <P>(j) Within 60 days after the date of completing each continuous monitoring system (CMS) performance evaluation (as defined in § 63.2), you must submit the results of the performance evaluation following the procedures specified in paragraphs (j)(1) through (3) of this section.</P>
                            <P>
                                (1) 
                                <E T="03">Performance evaluations of CMS measuring relative accuracy test audit (RATA) pollutants that are supported by the EPA's ERT as listed on the EPA's ERT website at the time of the evaluation.</E>
                                 Submit the results of the performance evaluation to the EPA via CEDRI, which can be accessed through the EPA's CDX. The data must be submitted in a file format generated through the use of the EPA's ERT. Alternatively, you may submit an electronic file consistent with the XML schema listed on the EPA's ERT website.
                            </P>
                            <P>
                                (2) 
                                <E T="03">Performance evaluations of CMS measuring RATA pollutants that are not supported by the EPA's ERT as listed on the EPA's ERT website at the time of the evaluation.</E>
                                 The results of the performance evaluation must be included as an attachment in the ERT or an alternate electronic file consistent with the XML schema listed on the EPA's ERT website. Submit the ERT generated package or alternative file to the EPA via CEDRI.
                            </P>
                            <P>
                                (3) 
                                <E T="03">Confidential Business Information (CBI).</E>
                                 If you claim some of the information submitted under this paragraph (j) is CBI, you must submit a complete file, including information claimed to be CBI, to the EPA. The file must be generated through the use of the EPA's ERT or an alternate electronic file consistent with the XML schema listed on the EPA's ERT website. Submit the file according to paragraph (k) of this section except it should be sent to the attention of the Branch Supervisor in the Measurement Strategy Branch.
                            </P>
                            <P>(k) For Confidential Business Information (CBI):</P>
                            <P>
                                (1) The preferred method to receive CBI is for it to be transmitted electronically using email attachments, File Transfer Protocol, or other online file sharing services. Electronic submissions must be transmitted directly to the OCAP CBI Office at the email address 
                                <E T="03">ocapcbi@epa.gov,</E>
                                 and as described in the preceding sentence, should include clear CBI markings and be flagged to the attention of the Sector Lead, Plywood and Composite Wood Products. If assistance is needed with submitting large electronic files that exceed the file size limit for email attachments, and if you do not have your own file sharing service, please email 
                                <E T="03">ocapcbi@epa.gov</E>
                                 to request a file transfer link.
                            </P>
                            <P>(2) If you cannot transmit the file electronically, you may send CBI information through the postal service to the following address: OCAP Document Control Officer (C404-02), OCAP, U.S. Environmental Protection Agency, 109 T.W. Alexander Drive, P.O. Box 12055, Research Triangle Park, North Carolina 27711, Attention Sector Lead—Plywood and Composite Wood Products. The mailed CBI material should be double wrapped and clearly marked. Any CBI markings should not show through the outer envelope.</P>
                            <P>(3) All CBI claims must be asserted at the time of submission. Anything submitted using CEDRI cannot later be claimed CBI. Furthermore, under CAA section 114(c), emissions data is not entitled to confidential treatment, and the EPA is required to make emissions data available to the public. Thus, emissions data will not be protected as CBI and will be made publicly available.</P>
                            <P>(4) You must submit the same file submitted to the CBI office with the CBI omitted to the EPA via the EPA's CDX as described in § 63.9(k).</P>
                            <P>(l) [Reserved] </P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="40" PART="63">
                        <AMDPAR>17. Amend § 63.2282 by:</AMDPAR>
                        <AMDPAR>a. Revising paragraphs (a)(2) introductory text, (a)(2)(iii)(A), and (c) introductory text; and</AMDPAR>
                        <AMDPAR>b. Removing and reserving paragraph (d).</AMDPAR>
                        <P>The revisions read as follows:</P>
                        <SECTION>
                            <SECTNO>§ 63.2282 </SECTNO>
                            <SUBJECT>What records must I keep?</SUBJECT>
                            <P>(a) * * *</P>
                            <P>(2) Records related to startup and shutdown, failures to meet the standard, and actions taken to minimize emissions, specified in paragraphs (a)(2)(i) through (iv) of this section.</P>
                            <STARS/>
                            <P>(iii) * * *</P>
                            <P>(A) For any failure to meet a compliance option in § 63.2240, including the compliance options in tables 1A through 1E to this subpart, record an estimate of the quantity of each regulated pollutant emitted over any emission limit and a description of the method used to estimate the emissions.</P>
                            <STARS/>
                            <P>(c) For each CMS, you must keep the following records:</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <SECTION>
                        <SECTNO>§ 63.2283 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <REGTEXT TITLE="40" PART="63">
                        <AMDPAR>18. Amend § 63.2283 by removing and reserving paragraph (d).</AMDPAR>
                    </REGTEXT>
                    <REGTEXT TITLE="40" PART="63">
                        <AMDPAR>19. Revise § 63.2292 to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 63.2292 </SECTNO>
                            <SUBJECT>What definitions apply to this subpart?</SUBJECT>
                            <P>Terms used in this subpart are defined in the Clean Air Act (CAA), in § 63.2, and in this section as follows:</P>
                            <P>
                                <E T="03">1-hour period</E>
                                 means a 60-minute period.
                            </P>
                            <P>
                                <E T="03">Affected source</E>
                                 means the collection of dryers, refiners, blenders, formers, presses, board coolers, and other process units associated with the 
                                <PRTPAGE P="41447"/>
                                manufacturing of plywood and composite wood products. The affected source includes, but is not limited to, green end operations, refining, drying operations (including any combustion unit exhaust stream routinely used to direct fire process unit(s)), resin preparation, blending and forming operations, pressing and board cooling operations, and miscellaneous finishing operations (such as sanding, sawing, patching, edge sealing, and other finishing operations not subject to other NESHAP). The affected source also includes onsite storage of raw materials used in the manufacture of plywood and/or composite wood products, such as resins; onsite wastewater treatment operations specifically associated with plywood and composite wood products manufacturing; and miscellaneous coating operations (defined elsewhere in this section). The affected source includes lumber kilns at PCWP manufacturing facilities and at any other kind of facility.
                            </P>
                            <P>
                                <E T="03">Agricultural fiber</E>
                                 means the fiber of an annual agricultural crop. Examples of agricultural fibers include, but are not limited to, wheat straw, rice straw, and bagasse.
                            </P>
                            <P>
                                <E T="03">Atmospheric refiner</E>
                                 means a piece of equipment operated under atmospheric pressure for refining (rubbing, grinding, or milling) wood material into fibers or particles for use in particleboard, MDF or dry-process hardboard production. Atmospheric refiners are operated with continuous infeed and outfeed of wood material and atmospheric pressures throughout the refining process. An atmospheric refiner is a process unit.
                            </P>
                            <P>
                                <E T="03">Biofilter</E>
                                 means an enclosed control system such as a tank or series of tanks with a fixed roof that contact emissions with a solid media (such as bark) and use microbiological activity to transform organic pollutants in a process exhaust stream to innocuous compounds such as carbon dioxide, water, and inorganic salts. Wastewater treatment systems such as aeration lagoons or activated sludge systems are not considered to be biofilters.
                            </P>
                            <P>
                                <E T="03">Blender</E>
                                 means rotary drum or other vessel in which resin and other additives are mixed with wood or agricultural fiber furnish prior to forming into a composite wood product. Blenders do not include mix chests in wet formed fiberboard or hardboard manufacturing. A blender is a process unit.
                            </P>
                            <P>
                                <E T="03">Capture device</E>
                                 means a hood, enclosure, or other means of collecting emissions into a duct so that the emissions can be measured.
                            </P>
                            <P>
                                <E T="03">Capture efficiency</E>
                                 means the fraction (expressed as a percentage) of the pollutants from an emission source that are collected by a capture device.
                            </P>
                            <P>
                                <E T="03">Catalytic oxidizer</E>
                                 means a control system that combusts or oxidizes, in the presence of a catalyst, exhaust gas from a process unit. Catalytic oxidizers include regenerative catalytic oxidizers and thermal catalytic oxidizers.
                            </P>
                            <P>
                                <E T="03">Combustion unit</E>
                                 means a dryer burner, process heater, or boiler. Combustion units may be used for combustion of organic HAP emissions.
                            </P>
                            <P>
                                <E T="03">Combustion unit bypass stack</E>
                                 means a bypass or abort stack in which a combustion unit exhaust stream routinely used to direct-fire a PCWP dryer or lumber kiln is vented to the atmosphere without first passing through the PCWP dryer or lumber kiln.
                            </P>
                            <P>
                                <E T="03">Control device</E>
                                 means any equipment that reduces the quantity of HAP emitted to the air. The device may destroy the HAP or secure the HAP for subsequent recovery. Control devices include, but are not limited to, thermal or catalytic oxidizers, combustion units that incinerate process exhausts, biofilters, and condensers.
                            </P>
                            <P>
                                <E T="03">Control system or add-on control system</E>
                                 means the combination of capture and control devices used to reduce HAP emissions to the atmosphere.
                            </P>
                            <P>
                                <E T="03">Conveyor strand dryer</E>
                                 means a conveyor dryer used to reduce the moisture of wood strands used in the manufacture of oriented strandboard, laminated strand lumber, or other wood strand-based products. A 
                                <E T="03">conveyor strand dryer</E>
                                 is a process unit.
                            </P>
                            <P>
                                <E T="03">Conveyor strand dryer zone</E>
                                 means each portion of a conveyor strand dryer with a separate heat exchange system and exhaust vent(s). Conveyor strand dryers contain multiple zones (
                                <E T="03">e.g.,</E>
                                 three zones), which may be divided into multiple sections.
                            </P>
                            <P>
                                <E T="03">Curing chamber</E>
                                 means an oven or room surrounded by a wall or heavy plastic flaps that uses heat, infrared, or radio-frequency techniques to cure the resin used to bond the web and flange components of I-joists. A curing chamber is a process unit.
                            </P>
                            <P>
                                <E T="03">Deviation</E>
                                 means any instance in which an affected source subject to this subpart, or an owner or operator of such a source:
                            </P>
                            <P>(1) Fails to meet any requirement or obligation established by this subpart including, but not limited to, any compliance option, operating requirement, or work practice requirement;</P>
                            <P>(2) Fails to meet any term or condition that is adopted to implement an applicable requirement in this subpart, and that is included in the operating permit for any affected source required to obtain such a permit; or</P>
                            <P>(3) Fails to meet any compliance option, operating requirement, or work practice requirement in this subpart during startup, shutdown, or malfunction, regardless of whether or not such failure is permitted by this subpart. A deviation is not always a violation. The determination of whether a deviation constitutes a violation of the standard is up to the discretion of the entity responsible for enforcement of the standards.</P>
                            <P>
                                <E T="03">Direct-fired process unit</E>
                                 means a process unit that is heated by the passing of combustion exhaust through the process unit such that the process material is contacted by the combustion exhaust.
                            </P>
                            <P>
                                <E T="03">Direct natural gas-fired PCWP dryer</E>
                                 means a direct-fired PCWP dryer (including each dry rotary dryer, green rotary dryer, tube dryer, rotary strand dryer, hardboard oven, press predryer or heated zones from a softwood or hardwood veneer dryer, conveyor strand dryer, or fiberboard mat dryer) in which greater than 90 percent of the direct-fired annual heat input results from natural gas (or propane) combustion.
                            </P>
                            <P>
                                <E T="03">Direct wood-fired PCWP dryer</E>
                                 means a direct-fired PCWP dryer in which 10 percent or more of the direct-fired annual heat input results from combustion of wood-derived fuel such as bark, wood residuals, or wood-derived syngas or any other fuel except for natural gas (or propane).
                            </P>
                            <P>
                                <E T="03">Dry forming</E>
                                 means the process of making a mat of resinated fiber to be compressed into a reconstituted wood product such as particleboard, oriented strandboard, medium density fiberboard, or hardboard.
                            </P>
                            <P>
                                <E T="03">Dry rotary dryer</E>
                                 means a rotary dryer that dries wood particles or fibers with a maximum inlet moisture content of less than or equal to 30 percent (by weight, dry basis) and operates with a maximum inlet temperature of less than or equal to 600 °F. A dry rotary dryer is a process unit.
                            </P>
                            <P>
                                <E T="03">Dryer heated zones</E>
                                 means the zones of a softwood veneer dryer or fiberboard mat dryer that are equipped with heating and hot air circulation units. The cooling zone(s) of the dryer through which ambient air is blown are not part of the dryer heated zones.
                            </P>
                            <P>
                                <E T="03">Engineered wood product</E>
                                 means a structural wood product made with lumber, veneers, strands of wood, or from other small wood elements that are bound together with resin. Engineered wood products include, but are not limited to, laminated strand lumber, laminated veneer lumber, parallel 
                                <PRTPAGE P="41448"/>
                                strand lumber, wood I-joists, and glue-laminated beams.
                            </P>
                            <P>
                                <E T="03">Engineered wood product press</E>
                                 means a press that applies heat and/or pressure to resinated veneer, wood strands, or lumber to bond the resinated wood material into an engineered wood product. An engineered wood product press is a process unit.
                            </P>
                            <P>
                                <E T="03">Fiber</E>
                                 means the discrete elements of wood or similar cellulosic material, which are separated by mechanical means, as in refining, that can be formed into boards.
                            </P>
                            <P>
                                <E T="03">Fiber washer</E>
                                 means a unit in which water-soluble components of wood (hemicellulose and sugars) that have been produced during digesting are removed from the wood fiber. Typically, wet fiber leaving a refiner is further diluted with water and then passed over a filter, leaving the cleaned fiber on the surface. A fiber washer is a process unit.
                            </P>
                            <P>
                                <E T="03">Fiberboard</E>
                                 means a composite panel composed of cellulosic fibers (usually wood or agricultural material) made by wet forming and compacting a mat of fibers. Fiberboard density generally is less than 0.50 grams per cubic centimeter (31.5 pounds per cubic foot).
                            </P>
                            <P>
                                <E T="03">Fiberboard mat dryer</E>
                                 means a dryer used to reduce the moisture of wet-formed wood fiber mats used to produce fiberboard or hardboard by applying heat. A 
                                <E T="03">fiberboard mat dryer</E>
                                 is a process unit.
                            </P>
                            <P>
                                <E T="03">Finishing sander</E>
                                 means a piece of equipment that uses an abrasive drum, belt, or pad to impart smoothness to the surface of a plywood or composite wood product panel and to reduce the panel to the prescribed thickness. A finishing sander is a process unit.
                            </P>
                            <P>
                                <E T="03">Finishing saw</E>
                                 means a piece of equipment used to trim or cut finished plywood and composite wood products panels to a certain size. A finishing saw is a process unit.
                            </P>
                            <P>
                                <E T="03">Flame zone</E>
                                 means the portion of the combustion chamber in a combustion unit that is occupied by the flame envelope.
                            </P>
                            <P>
                                <E T="03">Former or forming system</E>
                                 means a series of bins (or forming headers) that distribute resinated furnish into layers onto a conveyor to form a loose mat to be compressed into a reconstituted wood product such as particleboard, oriented strandboard, or medium density fiberboard. Each forming bin (or forming header) adds a layer to the mat beginning with a face furnish layer, then one or more core furnish layers, and ending with a face furnish layer. The forming system includes each of the forming bins (headers) in series, flying cutoff saw (in facilities with batch presses), and pneumatic furnish pick-up points up prior to the press loader or continuous press.
                            </P>
                            <P>
                                <E T="03">Furnish</E>
                                 means the fibers, particles, or strands used for making boards.
                            </P>
                            <P>
                                <E T="03">Glue-laminated beam</E>
                                 means a structural wood beam made by bonding lumber together along its faces with resin.
                            </P>
                            <P>
                                <E T="03">Glue-laminated beam press</E>
                                 means an engineered wood product press that presses resinated stacks of lumber into a beam by application of heat and/or pressure.
                            </P>
                            <P>
                                <E T="03">Green rotary dryer</E>
                                 means a rotary dryer that dries wood particles or fibers with an inlet moisture content of greater than 30 percent (by weight, dry basis) at any dryer inlet temperature or operates with an inlet temperature of greater than 600 °F with any inlet moisture content. A 
                                <E T="03">green rotary dryer</E>
                                 is a process unit.
                            </P>
                            <P>
                                <E T="03">Group 1 miscellaneous coating operations</E>
                                 means application of edge seals, nail lines, logo (or other information) paint, shelving edge fillers, trademark/grade stamp inks, and wood putty patches to plywood and composite wood products (except kiln-dried lumber) on the same site where the plywood and composite wood products are manufactured. Group 1 miscellaneous coating operations also include application of synthetic patches to plywood at new affected sources.
                            </P>
                            <P>
                                <E T="03">Hardboard</E>
                                 means a composite panel composed of inter-felted cellulosic fibers made by dry or wet forming and pressing of a resinated fiber mat. Hardboard generally has a density of 0.50 grams per cubic centimeter (31.5 pounds per cubic foot) or greater.
                            </P>
                            <P>
                                <E T="03">Hardboard oven</E>
                                 means an oven used to heat treat or temper hardboard after hot pressing. Humidification chambers are not considered as part of hardboard ovens. A 
                                <E T="03">hardboard oven</E>
                                 is a process unit.
                            </P>
                            <P>
                                <E T="03">Hardwood</E>
                                 means the wood of a broad-leafed tree, either deciduous or evergreen. Examples of hardwoods include, but are not limited to, aspen, birch, poplar, and oak.
                            </P>
                            <P>
                                <E T="03">Hardwood plywood press</E>
                                 means a hot press which, through heat and pressure, bonds assembled hardwood veneers (including multiple plies of veneer and/or a substrate) and resin into a hardwood plywood panel. A hardwood plywood press is a process unit.
                            </P>
                            <P>
                                <E T="03">Hardwood veneer dryer</E>
                                 means a dryer that removes excess moisture from veneer by conveying the veneer through a heated medium on rollers, belts, cables, or wire mesh. Hardwood veneer dryers are used to dry veneer with less than 30 percent softwood species on an annual volume basis. Veneer kilns that operate as batch units, veneer dryers heated by radio frequency or microwaves that are used to redry veneer, and veneer redryers (defined elsewhere in this section) that are heated by conventional means are not considered to be hardwood veneer dryers. A 
                                <E T="03">hardwood veneer dryer</E>
                                 is a process unit.
                            </P>
                            <P>
                                <E T="03">Humidifier or humidification chamber</E>
                                 means a process unit used to increase the moisture content of hardboard following pressing or baking in a hardboard oven. Typically, water vapor saturated air is blown over the hardboard surfaces in a cabinet. A humidifier is a process unit.
                            </P>
                            <P>
                                <E T="03">Kiln-dried lumber</E>
                                 means solid wood lumber that has been dried in a lumber kiln.
                            </P>
                            <P>
                                <E T="03">Laminated strand lumber (LSL)</E>
                                 means a composite product formed into a billet made of thin wood strands cut from whole logs, resinated, and pressed together with the grain of each strand oriented parallel to the length of the finished product.
                            </P>
                            <P>
                                <E T="03">Laminated veneer lumber (LVL)</E>
                                 means a composite product formed into a billet made from layers of resinated wood veneer sheets or pieces pressed together with the grain of each veneer aligned primarily along the length of the finished product. 
                                <E T="03">Laminated veneer lumber</E>
                                 is also known as parallel strand lumber (PSL).
                            </P>
                            <P>
                                <E T="03">Log vat</E>
                                 means a process unit that raises the temperature of the logs inside by applying a heated substance, usually hot water or steam, to the outside of the logs by spraying or soaking. A log vat is a process unit.
                            </P>
                            <P>
                                <E T="03">Lumber</E>
                                 means boards or planks sawed or split from logs or timber, including logs or timber processed for use as utility poles or other wood components. Lumber can be either green (non-dried) or dried. Lumber is typically either air-dried or kiln-dried.
                            </P>
                            <P>
                                <E T="03">Lumber kiln</E>
                                 means an enclosed dryer operated by applying heat to reduce the moisture content of lumber.
                            </P>
                            <P>
                                <E T="03">LVL or PSL press</E>
                                 means an engineered wood product press that presses resinated stacks of veneers into a solid billet by application of heat and/or pressure. The billet is cut into laminated veneer lumber or parallel strand lumber after exiting the press. An LVL or PSL press is a process unit.
                            </P>
                            <P>
                                <E T="03">Maximum lumber moisture specification</E>
                                 means (for purposes of this subpart) the upper limit of lumber moisture content (weight percent on a dry basis) that meets the relevant lumber grade standard for a lumber product.
                            </P>
                            <P>
                                <E T="03">Maximum true vapor pressure</E>
                                 means the equilibrium partial pressure exerted by each HAP that is present in the stored resin in a concentration above the 
                                <PRTPAGE P="41449"/>
                                thresholds defining non-HAP resins at the temperature equal to the highest calendar-month average of the liquid storage temperature for liquids stored above or below the ambient temperature, or at the local maximum monthly average temperature as reported by the National Weather Service for liquids stored at the ambient temperature, as determined:
                            </P>
                            <P>(1) From safety data sheets or other technical information provided by the PCWP resin supplier; or</P>
                            <P>(2) Standard reference texts; or</P>
                            <P>(3) Any other method approved by the Administrator.</P>
                            <P>
                                <E T="03">Medium density fiberboard (MDF)</E>
                                 means a composite panel composed of cellulosic fibers (usually wood or agricultural fiber) made by dry forming and pressing of a resinated fiber mat.
                            </P>
                            <P>
                                <E T="03">Method detection limit</E>
                                 means the minimum concentration of an analyte that can be determined with 99 percent confidence that the true value is greater than zero.
                            </P>
                            <P>
                                <E T="03">Miscellaneous coating operations</E>
                                 means application of any of the following to plywood or composite wood products: edge seals, moisture sealants, anti-skid coatings, company logos, trademark or grade stamps, nail lines, synthetic patches, wood patches, wood putty, concrete forming oils, glues for veneer composing, and shelving edge fillers. Miscellaneous coating operations also include the application of primer to oriented strandboard siding that occurs at the same site as oriented strandboard manufacture and application of asphalt, clay slurry, or titanium dioxide coatings to fiberboard at the same site of fiberboard manufacture.
                            </P>
                            <P>
                                <E T="03">Mixed PCWP process stream</E>
                                 means an emission stream from a process unit subject to standards effective on July 6, 2026, that was co-mingled with an emissions stream or streams from one or more process units subject to the compliance options in table 1B to this subpart before July 6, 2026, at an affected source that commenced construction (or reconstruction) on or before May 18, 2023.
                            </P>
                            <P>
                                <E T="03">Molded particleboard</E>
                                 means a shaped composite product (other than a composite panel) composed primarily of cellulosic materials (usually wood or agricultural fiber) generally in the form of discrete pieces or particles, as distinguished from fibers, which are pressed together with resin.
                            </P>
                            <P>
                                <E T="03">MSF</E>
                                 means thousand square feet (92.9 square meters). Square footage of panels is usually measured on a thickness basis, such as 
                                <FR>3/8</FR>
                                -inch, to define the total volume of panels. Equation 3 of § 63.2262(j) shows how to convert from one thickness basis to another.
                            </P>
                            <P>
                                <E T="03">Multipurpose atmospheric refiner</E>
                                 means an atmospheric refiner that processes wood for use in PCWP and is not a “post-dryer atmospheric refiner” as defined in this section. A 
                                <E T="03">multipurpose atmospheric refiner</E>
                                 is a process unit.
                            </P>
                            <P>
                                <E T="03">Natural gas</E>
                                 means:
                            </P>
                            <P>(1) A naturally occurring mixture of hydrocarbon and nonhydrocarbon gases found in geologic formations beneath the earth's surface, of which the principal constituent is methane; or</P>
                            <P>(2) Liquefied petroleum gas, as defined in ASTM D1835-05 (incorporated by reference, see § 63.14); or</P>
                            <P>(3) A mixture of hydrocarbons that maintains a gaseous state at ISO conditions. Additionally, natural gas must either be composed of at least 70 percent methane by volume or have a gross calorific value between 35 and 41 megajoules (MJ) per dry standard cubic meter (950 and 1,100 Btu per dry standard cubic foot); or</P>
                            <P>
                                (4) Propane or propane derived synthetic natural gas. Propane means a colorless gas derived from petroleum and natural gas, with the molecular structure C
                                <E T="52">3</E>
                                H
                                <E T="52">8</E>
                                .
                            </P>
                            <P>
                                <E T="03">Nondetect data</E>
                                 means, for the purposes of this subpart, any value that is below the method detection limit.
                            </P>
                            <P>
                                <E T="03">Non-HAP coating</E>
                                 means a coating with HAP contents below 0.1 percent by mass for Occupational Safety and Health Administration-defined carcinogens as specified in section A.6.4 of appendix A to 29 CFR 1910.1200, and below 1.0 percent by mass for other HAP compounds.
                            </P>
                            <P>
                                <E T="03">Non-HAP resin</E>
                                 means a resin that contains less than 0.1 percent by mass of formaldehyde and less than 1.0 percent by mass each of phenol, methanol, and MDI.
                            </P>
                            <P>
                                <E T="03">Oriented strandboard (OSB)</E>
                                 means a composite panel produced from thin wood strands cut from whole logs, formed into resinated layers (with the grain of strands in one layer oriented perpendicular to the strands in adjacent layers), and pressed.
                            </P>
                            <P>
                                <E T="03">Oven-dried ton(s) (ODT)</E>
                                 means tons of wood dried until all of the moisture in the wood is removed. One oven-dried ton equals 907 oven-dried kilograms.
                            </P>
                            <P>
                                <E T="03">Panel-trim chipper</E>
                                 means a piece of equipment that accepts the discarded pieces of veneer or pressed plywood and composite wood products panels that are removed by finishing saws and reduces these pieces to small elements. A panel-trim chipper is a process unit.
                            </P>
                            <P>
                                <E T="03">Parallel strand lumber (PSL)</E>
                                 means a composite product formed into a billet made from layers of resinated wood veneer sheets or pieces pressed together with the grain of each veneer aligned primarily along the length of the finished product. 
                                <E T="03">Parallel strand lumber</E>
                                 is also known as laminated veneer lumber (LVL).
                            </P>
                            <P>
                                <E T="03">Partial wood products enclosure</E>
                                 means an enclosure that does not meet the design criteria for a wood products enclosure as defined in this subpart.
                            </P>
                            <P>
                                <E T="03">Particle</E>
                                 means a discrete, small piece of cellulosic material (usually wood or agricultural fiber) produced mechanically and used as the aggregate for a particleboard.
                            </P>
                            <P>
                                <E T="03">Particleboard</E>
                                 means a composite panel composed primarily of cellulosic materials (usually wood or agricultural fiber) generally in the form of discrete pieces or particles, as distinguished from fibers, which are pressed together with resin.
                            </P>
                            <P>
                                <E T="03">PCWP dryer</E>
                                 means each dry rotary dryer, green rotary dryer, tube dryer, rotary strand dryer, hardboard oven, or press predryer; or the heated zones from a softwood or hardwood veneer dryer, conveyor strand dryer, or fiberboard mat dryer.
                            </P>
                            <P>
                                <E T="03">Plywood</E>
                                 means a panel product consisting of layers of wood veneers hot pressed together with resin. Plywood includes panel products made by hot pressing (with resin) veneers to a substrate such as particleboard, medium density fiberboard, or lumber. Plywood products may be flat or curved.
                            </P>
                            <P>
                                <E T="03">Plywood and composite wood products (PCWP) manufacturing facility</E>
                                 means a facility that manufactures plywood and/or composite wood products by bonding wood material (fibers, particles, strands, veneers, etc.) or agricultural fiber, generally with resin under heat and pressure, to form a panel, engineered wood product, or other product defined in this section. Plywood and composite wood products manufacturing facilities also include facilities that manufacture dry veneer and lumber kilns located at any facility. Plywood and composite wood products include, but are not limited to, plywood, veneer, particleboard, molded particleboard, oriented strandboard, hardboard, fiberboard, medium density fiberboard, laminated strand lumber, laminated veneer lumber, wood I-joists, kiln-dried lumber, and glue-laminated beams.
                            </P>
                            <P>
                                <E T="03">Polycyclic aromatic hydrocarbons (PAH)</E>
                                 means the sum of 2-methylnaphthalene, acenaphthylene, acenaphthene, fluorene, phenanthrene, anthracene, fluoranthene, pyrene, benz(a)anthracene, chrysene, benzo(b)fluoranthene, benzo(k)fluoranthene, benzo(e)pyrene, 
                                <PRTPAGE P="41450"/>
                                benzo(a)pyrene, perylene, indeno(1,2,3-c,d)pyrene, benzo(g,h,i)perylene, dibenz(a,h)anthracene.
                            </P>
                            <P>
                                <E T="03">Post-dryer atmospheric refiner</E>
                                 means an atmospheric refiner used to process wood for use in PCWP in which 90 percent or more (by weight) of the annual throughput has been previously dried onsite in a dryer at the PCWP affected facility. A 
                                <E T="03">post-dryer atmospheric refiner</E>
                                 is a process unit.
                            </P>
                            <P>
                                <E T="03">Press predryer</E>
                                 means a dryer used to reduce the moisture and elevate the temperature by applying heat to a wet-formed fiber mat before the mat enters a hot press. A 
                                <E T="03">press predryer</E>
                                 is a process unit.
                            </P>
                            <P>
                                <E T="03">Pressurized refiner</E>
                                 means a piece of equipment operated under pressure for preheating (usually by steaming) wood material and refining (rubbing or grinding) the wood material into fibers. Pressurized refiners are operated with continuous infeed and outfeed of wood material and maintain elevated internal pressures (
                                <E T="03">i.e.,</E>
                                 there is no pressure release) throughout the preheating and refining process. Pressurized refiners include steaming vessels that operate under pressure to continuously feed and vent through the pressurized refiner. A 
                                <E T="03">pressurized refiner</E>
                                 is a process unit.
                            </P>
                            <P>
                                <E T="03">Primary tube dryer</E>
                                 means a single-stage tube dryer or the first stage of a multi-stage tube dryer. Tube dryer stages are separated by vents for removal of moist gases between stages (
                                <E T="03">e.g.,</E>
                                 a product cyclone at the end of a single-stage dryer or between the first and second stages of a multi-stage tube dryer). The first stage of a multi-stage tube dryer is used to remove the majority of the moisture from the wood furnish (compared to the moisture reduction in subsequent stages of the tube dryer). Blow-lines used to apply resin are considered part of the primary tube dryer. A 
                                <E T="03">primary tube dryer</E>
                                 is a process unit.
                            </P>
                            <P>
                                <E T="03">Process unit</E>
                                 means equipment classified according to its function such as a blender, dryer, press, former, or board cooler.
                            </P>
                            <P>
                                <E T="03">Process unit bypass stack</E>
                                 means a bypass or abort stack that allows a process unit exhaust stream to temporarily vent to the atmosphere while bypassing a control device routinely used to meet the compliance options in table 1B, 1C, 1D, or 1E to this subpart.
                            </P>
                            <P>
                                <E T="03">Process unit(s) subject to standards effective on July 6, 2026,</E>
                                 means a softwood plywood press, hardwood plywood press, engineered wood product press, humidifier, atmospheric refiner, stand-alone digester, fiber washer, blender, former, finishing sander, finishing saw, panel trim chipper, log vat, resin tank, onsite wastewater treatment operation specifically associated with PCWP manufacturing, lumber kiln, press predryer (at an existing affected source), fiberboard mat dryer heated zones (at an existing affected source), or reconstituted wood products board cooler (at an existing affected source).
                            </P>
                            <P>
                                <E T="03">Reconstituted wood product board cooler</E>
                                 means a piece of equipment designed to reduce the temperature of a board by means of forced air or convection within a controlled time period after the board exits the reconstituted wood product press unloader. Board coolers include wicket and star type coolers commonly found at medium density fiberboard and particleboard plants. Board coolers do not include cooling sections of dryers (
                                <E T="03">e.g.,</E>
                                 veneer dryers or fiberboard mat dryers) or coolers integrated into or following hardboard bake ovens or humidifiers. A 
                                <E T="03">reconstituted wood product board cooler</E>
                                 is a process unit.
                            </P>
                            <P>
                                <E T="03">Reconstituted wood product press</E>
                                 means a press, including (if applicable) the press unloader, that presses a resinated mat of wood fibers, particles, or strands between hot platens or hot rollers to compact and set the mat into a panel by simultaneous application of heat and pressure. Reconstituted wood product presses are used in the manufacture of hardboard, medium density fiberboard, particleboard, and oriented strandboard. Extruders are not considered to be reconstituted wood product presses. A 
                                <E T="03">reconstituted wood product press</E>
                                 is a process unit.
                            </P>
                            <P>
                                <E T="03">Representative operating conditions</E>
                                 means operation of a process unit during performance testing under the conditions that the process unit will typically be operating in the future, including use of a representative range of materials (
                                <E T="03">e.g.,</E>
                                 wood material of a typical species mix and moisture content or typical resin formulation) and representative operating temperature range. Representative operating conditions exclude periods of startup and shutdown.
                            </P>
                            <P>
                                <E T="03">Resin</E>
                                 means the synthetic adhesive (including glue) or natural binder, including additives, used to bond wood or other cellulosic materials together to produce plywood and composite wood products.
                            </P>
                            <P>
                                <E T="03">Resin tank</E>
                                 means a storage tank, container, or vessel connected to plywood and composite wood product production that holds resin. A resin tank is a process unit.
                            </P>
                            <P>
                                <E T="03">Resinated material handling (RMH) process unit</E>
                                 means each resin tank, softwood plywood press, hardwood plywood press, engineered wood product press or curing chamber, blender, former, finishing saw, finishing sander, panel trim chipper, hardboard humidifier, and onsite wastewater treatment operations specifically associated with PCWP manufacturing at a new or existing affected source; and each reconstituted wood products board cooler at an existing affected source.
                            </P>
                            <P>
                                <E T="03">Responsible official</E>
                                 means responsible official as defined in 40 CFR 70.2 and 71.2.
                            </P>
                            <P>
                                <E T="03">Rotary strand dryer</E>
                                 means a rotary dryer operated by applying heat and used to reduce the moisture of wood strands used in the manufacture of oriented strandboard, laminated strand lumber, or other wood strand-based products. A rotary strand dryer is a process unit.
                            </P>
                            <P>
                                <E T="03">Safety-related shutdown</E>
                                 means an unscheduled shutdown of a process unit subject to a compliance option in table 1B to this subpart during which time emissions from the process unit cannot be safely routed to the control system in place to meet the compliance options or operating requirements in this subpart without imminent danger to the process, control system, or system operator.
                            </P>
                            <P>
                                <E T="03">Secondary tube dryer</E>
                                 means the second stage and subsequent stages following the primary stage of a multi-stage tube dryer. Secondary tube dryers, also referred to as relay dryers, operate at lower temperatures than the primary tube dryer they follow. Secondary tube dryers are used to remove only a small amount of the furnish moisture compared to the furnish moisture reduction across the primary tube dryer. A 
                                <E T="03">secondary tube dryer</E>
                                 is a process unit.
                            </P>
                            <P>
                                <E T="03">Softwood</E>
                                 means the wood of a coniferous tree. Examples of softwoods include, but are not limited to, Southern yellow pine, Douglas fir, and White spruce.
                            </P>
                            <P>
                                <E T="03">Softwood plywood press</E>
                                 means a hot press which, through heat and pressure, bonds assembled softwood veneer plies and resin into a softwood plywood panel. A softwood plywood press is a process unit.
                            </P>
                            <P>
                                <E T="03">Softwood veneer dryer</E>
                                 means a dryer that removes excess moisture from veneer by conveying the veneer through a heated medium, generally on rollers, belts, cables, or wire mesh. Softwood veneer dryers are used to dry veneer with greater than or equal to 30 percent softwood species on an annual volume basis. Veneer kilns that operate as batch units, veneer dryers heated by radio frequency or microwaves that are used to redry veneer, and veneer redryers (defined elsewhere in this section) that are heated by conventional means are not considered to be softwood veneer 
                                <PRTPAGE P="41451"/>
                                dryers. A 
                                <E T="03">softwood veneer dryer</E>
                                 is a process unit.
                            </P>
                            <P>
                                <E T="03">Stand-alone digester</E>
                                 means a pressure vessel used to heat and soften wood chips (usually by steaming) before the chips are sent to a separate process unit for refining into fiber. Stand-alone digesters operate in batch cycles that include filling with wood chips, pressurization, cooking of wood chips under pressure, pressure release (purge) venting, and chip discharge (blow) from the pressure vessel. Venting of emissions from stand-alone digesters is separate from any downstream refining process. A stand-alone digester is a process unit.
                            </P>
                            <P>
                                <E T="03">Startup</E>
                                 means bringing equipment online and starting the production process.
                            </P>
                            <P>
                                <E T="03">Startup, initial</E>
                                 means the first time equipment is put into operation. Initial startup does not include operation solely for testing equipment. Initial startup does not include subsequent startups (as defined in this section) following malfunction or shutdowns or following changes in product or between batch operations. Initial startup does not include startup of equipment that occurred when the source was an area source.
                            </P>
                            <P>
                                <E T="03">Strand</E>
                                 means a long (with respect to thickness and width), flat wood piece specially cut from a log for use in oriented strandboard, laminated strand lumber, or other wood strand-based product.
                            </P>
                            <P>
                                <E T="03">Temporary total enclosure (TTE)</E>
                                 means an enclosure constructed for the purpose of measuring the capture efficiency of pollutants emitted from a given source, as defined in EPA Method 204 of appendix M to part 51 of this chapter.
                            </P>
                            <P>
                                <E T="03">Thermal oxidizer</E>
                                 means a control system that combusts or oxidizes exhaust gas from a process unit. Thermal oxidizers include regenerative thermal oxidizers and combustion units.
                            </P>
                            <P>
                                <E T="03">Total hazardous air pollutant emissions</E>
                                 means, for purposes of this subpart, the sum of the emissions of the following six compounds: acetaldehyde, acrolein, formaldehyde, methanol, phenol, and propionaldehyde.
                            </P>
                            <P>
                                <E T="03">Tube dryer</E>
                                 means a single-stage or multi-stage dryer operated by applying heat to reduce the moisture of wood fibers or particles as they are conveyed (usually pneumatically) through the dryer. Resin may or may not be applied to the wood material before it enters the tube dryer. Tube dryers do not include pneumatic fiber transport systems that use temperature and humidity conditioned pneumatic system supply air in order to prevent cooling of the wood fiber as it is moved through the process. A 
                                <E T="03">tube dryer</E>
                                 is a process unit.
                            </P>
                            <P>
                                <E T="03">Veneer</E>
                                 means thin sheets of wood peeled or sliced from logs for use in the manufacture of wood products such as plywood, laminated veneer lumber, or other products.
                            </P>
                            <P>
                                <E T="03">Veneer redryer</E>
                                 means a dryer heated by conventional means, such as direct wood-fired, direct-gas-fired, or steam heated, that is used to redry veneer that has been previously dried. Because the veneer dried in a veneer redryer has been previously dried, the inlet moisture content of the veneer entering the redryer is less than 25 percent (by weight, dry basis). Batch units used to redry veneer (such as redry cookers) are not considered to be veneer redryers. A 
                                <E T="03">veneer redryer</E>
                                 is a process unit.
                            </P>
                            <P>
                                <E T="03">Wet control device</E>
                                 means any equipment that uses water as a means of collecting an air pollutant. Wet control devices include scrubbers, wet electrostatic precipitators, and electrified filter beds. Wet control devices do not include biofilters or other equipment that destroys or degrades HAP.
                            </P>
                            <P>
                                <E T="03">Wet forming</E>
                                 means the process of making a slurry of water, fiber, and additives into a mat of fibers to be compressed into a fiberboard or hardboard product.
                            </P>
                            <P>
                                <E T="03">Wood I-joists</E>
                                 means a structural wood beam with an I-shaped cross section formed by bonding (with resin) wood or laminated veneer lumber flanges onto a web cut from a panel such as plywood or oriented strandboard.
                            </P>
                            <P>
                                <E T="03">Wood products enclosure</E>
                                 means a permanently installed containment that was designed to meet the following physical design criteria:
                            </P>
                            <P>(1) Any natural draft opening shall be at least four equivalent opening diameters from each HAP-emitting point, except for where board enters and exits the enclosure, unless otherwise specified by the EPA Administrator.</P>
                            <P>(2) The total area of all natural draft openings shall not exceed 5 percent of the surface area of the enclosure's four walls, floor, and ceiling.</P>
                            <P>(3) The average facial velocity of air through all natural draft openings shall be at least 3,600 meters per hour (200 feet per minute). The direction of airflow through all natural draft openings shall be into the enclosure.</P>
                            <P>(4) All access doors and windows whose areas are not included in item 2 of this definition and are not included in the calculation of facial velocity in item 3 of this definition shall be closed during routine operation of the process.</P>
                            <P>(5) The enclosure is designed and maintained to capture all emissions for discharge through a control device.</P>
                            <P>
                                <E T="03">Work practice requirement</E>
                                 means any design, equipment, work practice, or operational standard, or combination thereof, that is promulgated pursuant to CAA section 112(h).
                            </P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="40" PART="63">
                        <AMDPAR>20. Add tables 1C through 1E to subpart DDDD of part 63 to read as follows:</AMDPAR>
                        <GPOTABLE COLS="3" OPTS="L2,nj,p7,7/8,i1" CDEF="s75,r75,r75">
                            <TTITLE>Table 1C to Subpart DDDD of Part 63—Compliance Options Applicable On and After July 6, 2026</TTITLE>
                            <BOXHD>
                                <CHED H="1" O="L">If you operate a(n) . . .</CHED>
                                <CHED H="1" O="L">
                                    For process units at an affected source that commenced construction or reconstruction on or before May 18, 2023, you must comply with the following compliance options 
                                    <SU>1</SU>
                                     on and after July 6, 2029 . . .
                                </CHED>
                                <CHED H="1" O="L">
                                    For process units at an affected source that commenced construction or reconstruction after May 18, 2023, you must comply with the following compliance options 
                                    <SU>1</SU>
                                     beginning on July 6, 2026, or upon initial startup, whichever is later . . .
                                </CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">
                                    Fiberboard mat dryer heated zones at an affected source that commenced construction or reconstruction on or before January 9, 2003 
                                    <SU>2</SU>
                                </ENT>
                                <ENT>
                                    4.9E-02 lb total HAP/MSF 
                                    <FR>1/8</FR>
                                    ″ or 2.0E-01 lb total HAP/MSF 
                                    <FR>1/2</FR>
                                    ″
                                </ENT>
                                <ENT>See footnote “2”.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">
                                    Press predryer at an affected source that commenced construction or reconstruction on or before January 9, 2003
                                    <SU>2</SU>
                                </ENT>
                                <ENT>
                                    8.0E-02 lb total HAP/MSF 
                                    <FR>1/8</FR>
                                    ″ or 3.2E-01 lb total HAP/MSF 
                                    <FR>1/2</FR>
                                    ″
                                </ENT>
                                <ENT>See footnote “2”.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Post-dryer atmospheric refiner</ENT>
                                <ENT>4.1E-03 lb total HAP/ODT or 8.5E-01 ppmvd total HAP</ENT>
                                <ENT>3.3E-03 lb total HAP/ODT or 6.5E-01 ppmvd total HAP.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Multipurpose atmospheric refiner</ENT>
                                <ENT>1.2E-01 lb total HAP/ODT or 15 ppmvd total HAP</ENT>
                                <ENT>2.4E-03 lb total HAP/ODT or 3.3 ppmvd total HAP.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Reconstituted wood product press producing OSB using MDI resin</ENT>
                                <ENT>
                                    2.5E-04 lb MDI/MSF 
                                    <FR>3/4</FR>
                                    ″ (1.3E-04 lb/MSF 
                                    <FR>3/8</FR>
                                    ″) or 2.7E-02 mg MDI/dscm
                                </ENT>
                                <ENT>
                                    2.5E-04 lb MDI/MSF 
                                    <FR>3/4</FR>
                                    ″ (1.3E-04 lb/MSF 
                                    <FR>3/8</FR>
                                    ″) or 2.7E-02 mg MDI/dscm.
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Reconstituted wood product press producing particleboard or MDF using MDI resin</ENT>
                                <ENT>
                                    8.4E-04 lb MDI/MSF 
                                    <FR>3/4</FR>
                                    ″ or 2.0E-01 mg MDI/dscm
                                </ENT>
                                <ENT>
                                    2.3E-04 lb MDI/MSF 
                                    <FR>3/4</FR>
                                    ″ or 2.7E-02 mg MDI/dscm.
                                </ENT>
                            </ROW>
                            <ROW>
                                <PRTPAGE P="41452"/>
                                <ENT I="01">Primary tube dryer blow-line blending MDI resin, or primary tube dryer blow-line blending MDI resin co-controlled with a reconstituted wood products press using MDI resin</ENT>
                                <ENT>1.7E-02 lb MDI/ODT or 6.8E-01 mg MDI/dscm</ENT>
                                <ENT>1.7E-02 lb MDI/ODT or 6.8E-01 mg MDI/dscm.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Miscellaneous coating operation for applying MDI moisture sealant to the surface of an engineered wood product</ENT>
                                <ENT>1.9E-03 lb MDI emitted/lb sealant applied or 1.4E-05 lb MDI per square foot of surface area coated</ENT>
                                <ENT>1.9E-03 lb MDI emitted/lb sealant applied or 1.4E-05 lb MDI per square foot of surface area coated.</ENT>
                            </ROW>
                            <TNOTE>
                                <SU>1</SU>
                                 Total HAP, as defined in § 63.2292, includes acetaldehyde, acrolein, formaldehyde, methanol, phenol, and propionaldehyde. MDI is 4,4′-Diphenylmethane Diisocyanate (CAS 101-68-8). ug = micrograms; mg = milligrams; dscm = micrograms per dry standard meter; kPa = kilopascals; psia = pounds per square inch absolute; lb/ODT = pounds per oven-dried ton; lb/MSF = pounds per thousand square feet with a specified thickness basis (inches). Section 63.2262(j) shows how to convert from one thickness basis to another.
                            </TNOTE>
                            <TNOTE>
                                <SU>2</SU>
                                 Fiberboard mat dryer (heated zones) or press predryers at an affected source that commenced construction or reconstruction after January 9, 2003, must be in compliance with the compliance options in table 1A or 1B to this subpart beginning on September 28, 2004, or upon initial startup, whichever is later.
                            </TNOTE>
                        </GPOTABLE>
                        <GPOTABLE COLS="5" OPTS="L2,nj,p7,7/8,i1" CDEF="s50,r50,r50,r50,r50">
                            <TTITLE>Table 1D to Subpart DDDD of Part 63—Compliance Options Applicable On and After July 6, 2029, for Direct Wood-Fired PCWP Dryers at Affected Sources That Commenced Construction or Reconstruction On or Before May 18, 2023</TTITLE>
                            <BOXHD>
                                <CHED H="1" O="L">For the following types of direct wood-fired PCWP dryers . . .</CHED>
                                <CHED H="1">
                                    You must meet the PM 
                                    <LI>(HAP metal) limit</LI>
                                </CHED>
                                <CHED H="1">You must meet the Hg limit</CHED>
                                <CHED H="1">You must meet the HCl limit</CHED>
                                <CHED H="1">You must meet the PAH limit</CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">Rotary strand dryer</ENT>
                                <ENT>9.9E-02 lb/ODT or 3.6E-03 gr/dscf</ENT>
                                <ENT>1.7E-05 lb/ODT or 8.4E-04 mg/dscm</ENT>
                                <ENT>5.8E-03 lb/ODT or 1.5E-01 mg/dscm</ENT>
                                <ENT>1.1E-04 lb/ODT or 9.9E-03 mg/dscm.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Green rotary dryer</ENT>
                                <ENT>2.9E-01 lb/ODT or 5.2E-03 gr/dscf</ENT>
                                <ENT>1.5E-05 lb/ODT or 1.3E-03 mg/dscm</ENT>
                                <ENT>1.1E-02 lb/ODT or 1.7 mg/dscm</ENT>
                                <ENT>3.2E-04 lb/ODT or 4.2E-02 mg/dscm.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Dry rotary dryer</ENT>
                                <ENT>6.5E-01 lb/ODT or 9.8E-02 gr/dscf</ENT>
                                <ENT>1.0E-05 lb/ODT or 8.4E-04 mg/dscm</ENT>
                                <ENT>1.1E-03 lb/ODT or 9.0E-02 mg/dscm</ENT>
                                <ENT>4.6E-05 lb/ODT or 4.1E-03 mg/dscm.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Primary tube dryer or secondary tube dryer</ENT>
                                <ENT>3.1E-01 lb/ODT or 3.1E-03 gr/dscf</ENT>
                                <ENT>3.9E-05 lb/ODT or 1.6E-03 mg/dscm</ENT>
                                <ENT>6.4E-03 lb/ODT or 7.4E-01 mg/dscm</ENT>
                                <ENT>3.0E-04 lb/ODT or 1.6E-03 mg/dscm.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Softwood veneer dryer heated zones</ENT>
                                <ENT>7.2E-02 lb/MSF 3/8″ or 1.5E-02 gr/dscf</ENT>
                                <ENT>5.8E-05 lb/MSF 3/8″ or 4.1E-02 mg/dscm</ENT>
                                <ENT>NA</ENT>
                                <ENT>NA.</ENT>
                            </ROW>
                            <TNOTE>
                                <E T="02">Notes:</E>
                                 lb/ODT = pounds per oven dried ton, gr/dscf = grains per dry standard cubic foot, mg/dscm = milligrams per dry standard cubic meter. See § 63.2240(d)(3) for dioxin and furan TEQ limit for direct wood-fired green rotary dryers.
                            </TNOTE>
                        </GPOTABLE>
                        <GPOTABLE COLS="5" OPTS="L2,nj,p7,7/8,i1" CDEF="s50,r50,r50,r50,r50">
                            <TTITLE>Table 1E to Subpart DDDD of Part 63—Compliance Options Applicable On and After July 6, 2026, for Direct Wood-Fired PCWP Dryers at Affected Sources That Commenced Construction or Reconstruction After May 18, 2023</TTITLE>
                            <BOXHD>
                                <CHED H="1" O="L">For the following types of direct wood-fired PCWP dryers . . .</CHED>
                                <CHED H="1">
                                    You must meet the PM 
                                    <LI>(HAP metal) limit</LI>
                                </CHED>
                                <CHED H="1">You must meet the Hg limit</CHED>
                                <CHED H="1">You must meet the HCl limit</CHED>
                                <CHED H="1">You must meet the PAH limit</CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">Rotary strand dryer</ENT>
                                <ENT>5.6E-02lb/ODT or 1.3E-03 gr/dscf</ENT>
                                <ENT>1.7E-05 lb/ODT or 8.4E-04 mg/dscm</ENT>
                                <ENT>1.7E-03 lb/ODT or 9.0E-02 mg/dscm</ENT>
                                <ENT>1.8E-05 lb/ODT or 1.5E-03 mg/dscm.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Green rotary dryer</ENT>
                                <ENT>3.7E-02 lb/ODT or 1.3E-03 gr/dscf</ENT>
                                <ENT>1.1E-05 lb/ODT or 8.4E-04 mg/dscm</ENT>
                                <ENT>2.9E-03 lb/ODT or 9.0E-02 mg/dscm</ENT>
                                <ENT>6.2E-05 lb/ODT or 2.9E-03 mg/dscm.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Dry rotary dryer</ENT>
                                <ENT>6.0E-01 lb/ODT or 4.6E-02 gr/dscf</ENT>
                                <ENT>1.0E-05 lb/ODT or 8.4E-04 mg/dscm</ENT>
                                <ENT>1.1E-03 lb/ODT or 9.0E-02 mg/dscm</ENT>
                                <ENT>2.2E-05 lb/ODT or 2.1E-03 mg/dscm.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Primary tube dryer or secondary tube dryer</ENT>
                                <ENT>9.1E-02 lb/ODT or 1.3E-03 gr/dscf</ENT>
                                <ENT>3.9E-05 lb/ODT or 8.4E-04 mg/dscm</ENT>
                                <ENT>4.3E-03 lb/ODT or 9.0E-02 mg/dscm</ENT>
                                <ENT>3.4E-06 lb/ODT or 1.8E-06 mg/dscm.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Softwood veneer dryer heated zones</ENT>
                                <ENT>7.2E-02 lb/MSF 3/8″ or 1.5E-02 gr/dscf</ENT>
                                <ENT>5.8E-05 lb/MSF 3/8″ or 4.1E-02 mg/dscm</ENT>
                                <ENT>NA</ENT>
                                <ENT>NA.</ENT>
                            </ROW>
                            <TNOTE>
                                <E T="02">Notes:</E>
                                 lb/ODT = pounds per oven dried ton, gr/dscf = grains per dry standard cubic foot, mg/dscm = milligrams per dry standard cubic meter. See § 63.2240(d)(4) for dioxin and furan TEQ limit for direct wood-fired green rotary dryers.
                            </TNOTE>
                        </GPOTABLE>
                    </REGTEXT>
                    <REGTEXT TITLE="40" PART="63">
                        <AMDPAR>21. Revise tables 2 through 10 to subpart DDDD of part 63 to read as follows:</AMDPAR>
                        <GPOTABLE COLS="3" OPTS="L2,nj,p7,7/8,i1" CDEF="s75,r75,r75">
                            <TTITLE>Table 2 to Subpart DDDD of Part 63—Operating Requirements</TTITLE>
                            <BOXHD>
                                <CHED H="1" O="L">If you operate a(n) . . .</CHED>
                                <CHED H="1" O="L">You must . . .</CHED>
                                <CHED H="1" O="L">Or you must . . .</CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">(1) Thermal oxidizer</ENT>
                                <ENT>Maintain the 3-hour block average firebox temperature above the minimum temperature established during the performance test</ENT>
                                <ENT>
                                    Maintain the 3-hour block average THC concentration 
                                    <SU>1</SU>
                                     in the thermal oxidizer exhaust below the maximum concentration established during the performance test.
                                </ENT>
                            </ROW>
                            <ROW>
                                <PRTPAGE P="41453"/>
                                <ENT I="01">(2) Catalytic oxidizer</ENT>
                                <ENT>Maintain the 3-hour block average catalytic oxidizer temperature above the minimum temperature established during the performance test; and check the activity level of a representative sample of the catalyst annually except as specified in footnote “2” to this table</ENT>
                                <ENT>
                                    Maintain the 3-hour block average THC concentration 
                                    <SU>1</SU>
                                     in the catalytic oxidizer exhaust below the maximum concentration established during the performance test.
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(3) Biofilter</ENT>
                                <ENT>Maintain the 24-hour block biofilter bed temperature within the range established according to § 63.2262(m)</ENT>
                                <ENT>
                                    Maintain the 24-hour block average THC concentration 
                                    <SU>1</SU>
                                     in the biofilter exhaust below the maximum concentration established during the performance test.
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(4) Control device other than a thermal oxidizer, catalytic oxidizer, or biofilter used to meet the compliance options in table 1B or 1C to this subpart</ENT>
                                <ENT>Petition the EPA Administrator for site-specific operating parameter(s) to be established during the performance test and maintain the average operating parameter(s) within the range(s) established during the performance test</ENT>
                                <ENT>
                                    Maintain the 3-hour block average THC concentration 
                                    <SU>1</SU>
                                     in the control device exhaust below the maximum concentration established during the performance test.
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(5) Process unit that meets a compliance option in table 1A, 1C, 1D, or 1E to this subpart without the use of a control device</ENT>
                                <ENT>Maintain on a daily basis the process unit controlling operating parameter(s) within the ranges established during the performance test according to § 63.2262(n)</ENT>
                                <ENT>
                                    Maintain the 3-hour block average THC concentration 
                                    <SU>1</SU>
                                     in the process unit exhaust below the maximum concentration established during the performance test.
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(6) Wet electrostatic precipitator used to meet the compliance options in § 63.2240(d)(2) and (3) and table 1D or 1E to this subpart</ENT>
                                <ENT>Maintain the 3-hour block average total secondary electric power input and liquid flow rate above the minimum limits established during the performance test.</ENT>
                                <ENT>For a WESP followed by a control device with a dry exhaust, maintain the 24-hour block average opacity of no more than 10 percent (or the highest hourly average measured during the performance test).</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(7) Dry electrostatic precipitator used to meet the compliance options in § 63.2240(d)(2) and (3) and table 1D or 1E to this subpart</ENT>
                                <ENT>Maintain the 3-hour block average total secondary electric power input above the minimum limit established during the performance test</ENT>
                                <ENT>Maintain the 24-hour block average opacity of no more than 10 percent (or the highest hourly average measured during the performance test).</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(8) Wet PM scrubber used to meet the compliance options in § 63.2240(d)(2) and (3) and table 1D or 1E to this subpart</ENT>
                                <ENT>Maintain the 3-hour block average liquid flow rate and pressure drop above the minimum limits established during the performance test</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(9) Wet acid gas scrubber used to meet the compliance options in table 1D or 1E to this subpart</ENT>
                                <ENT>Maintain the 3-hour block average liquid flow rate and effluent pH above the minimum limits established during the performance test</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(10) Electrified filter bed used to meet the compliance options in § 63.2240(d)(2) and (3) and table 1D or 1E to this subpart</ENT>
                                <ENT>Maintain the 3-hour block average ionizer voltage and the bed voltage above the minimum limits established during the performance test; AND maintain the pressure drop within the range established during the performance test</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(11) Mechanical collector or other dry control device (not listed elsewhere in this table) used to meet the compliance options in § 63.2240(d)(2) and (3) and table 1D or 1E to this subpart</ENT>
                                <ENT>Maintain the 24-hour block average opacity of no more than 10 percent (or the highest hourly average measured during the performance test)</ENT>
                                <ENT>Maintain the 3-hour block average pressure drop across the control device above the minimum limit established during the performance test AND maintain average weekly 6-minute opacity readings below the maximum limit established according to § 63.2262(u).</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(12) Process unit bypass stack (defined in § 63.2292) on and after July 6, 2029, except as noted in footnote “3” to this table</ENT>
                                <ENT>Continuously monitor usage of the process unit bypass stack at all times while the process units are operating</ENT>
                            </ROW>
                            <TNOTE>
                                <SU>1</SU>
                                 You may choose to subtract methane from THC measurements.
                            </TNOTE>
                            <TNOTE>
                                <SU>2</SU>
                                 You may forego the annual catalyst activity check during the calendar year when a performance test is conducted according to table 4 to this subpart.
                            </TNOTE>
                            <TNOTE>
                                <SU>3</SU>
                                 New or reconstructed affected sources that commenced construction or reconstruction after May 18, 2023, must comply with this requirement beginning on July 6, 2026, or upon initial startup, whichever is later.
                            </TNOTE>
                        </GPOTABLE>
                        <GPOTABLE COLS="2" OPTS="L2,nj,p7,7/8,i1" CDEF="s75,r100">
                            <TTITLE>Table 3 to Subpart DDDD of Part 63—Work Practice Requirements</TTITLE>
                            <BOXHD>
                                <CHED H="1" O="L">
                                    For the following process units at existing or 
                                    <LI>new affected sources . . .</LI>
                                </CHED>
                                <CHED H="1" O="L">You must . . .</CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">(1) Dry rotary dryers</ENT>
                                <ENT>Process furnish with a 24-hour block average inlet moisture content of less than or equal to 30 percent (by weight, dry basis); AND operate with a 24-hour block average inlet dryer temperature of less than or equal to 600 °F.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(2) Hardwood veneer dryers</ENT>
                                <ENT>Process less than 30 volume percent softwood species on an annual basis.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(3) Softwood veneer dryers</ENT>
                                <ENT>Minimize fugitive emissions from the dryer doors through (proper maintenance procedures) and the green end of the dryers (through proper balancing of the heated zone exhausts).</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(4) Veneer redryers</ENT>
                                <ENT>Process veneer that has been previously dried, such that the 24-hour block average inlet moisture content of the veneer is less than or equal to 25 percent (by weight, dry basis).</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(5) Group 1 miscellaneous coating operations</ENT>
                                <ENT>Use non-HAP coatings as defined in § 63.2292.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(6) Process units and control systems undergoing safety-related shutdown on and after August 13, 2021, except as noted in footnote “1” to this table</ENT>
                                <ENT>Follow documented site-specific procedures such as use of automated controls or other measures that you have developed to protect workers and equipment to ensure that the flow of raw materials (such as furnish or resin) and fuel or process heat (as applicable) ceases and that material is removed from the process unit(s) as expeditiously as possible given the system design to reduce air emissions.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(7) Pressurized refiners undergoing startup or shutdown on and after August 13, 2021, except as noted in footnote “1” to this table</ENT>
                                <ENT>Route exhaust gases from the pressurized refiner to its dryer control system no later than 15 minutes after wood is fed to the pressurized refiner during startup. Stop wood flow into the pressurized refiner no more than 15 minutes after wood fiber and exhaust gases from the pressurized refiner stop being routed to the dryer during shutdown.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(8) Direct-fired softwood veneer dryers undergoing startup or shutdown of gas-fired burners on and after August 13, 2021, except as noted in footnote “1” to this table</ENT>
                                <ENT>Cease feeding green veneer into the softwood veneer dryer and minimize the amount of time direct gas-fired softwood veneer dryers are vented to the atmosphere due to the conditions described in § 63.2250(d).</ENT>
                            </ROW>
                            <ROW>
                                <PRTPAGE P="41454"/>
                                <ENT I="01">(9) Direct wood-fired PCWP dryers, direct natural gas-fired PCWP dryers, direct-fired lumber kilns, and associated combustion unit bypass stacks on and after July 6, 2029, except as noted in footnote “2” to this table</ENT>
                                <ENT>Conduct an annual tune-up of the combustion unit(s) used to directly fire each PCWP dryer or lumber kiln as specified in §§ 63.2241(d) and 63.2271(c); and continuously monitor an indicator of combustion unit bypass stack usage such as flow damper position or temperature according to § 63.2269(l)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(10) Lumber kilns on and after July 6, 2029, except as noted in footnote “2” to this table</ENT>
                                <ENT>Minimize lumber over-drying to reduce HAP emissions according to § 63.2241(e) by developing and operating according to the O&amp;M plan in § 63.2241(e)(1) and complying with one of the work practice requirements in § 63.2241(e)(3).</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(11) Stand-alone digesters on and after July 6, 2029, except as noted in footnote “2” to this table</ENT>
                                <ENT>Use clean steam for injection into digestion process; AND process fiber without addition of HAP-containing or wood pulping chemicals.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(12) Fiber washers on and after July 6, 2029, except as noted in footnote “2” to this table</ENT>
                                <ENT>Process fiber without addition of HAP-containing or wood pulping chemicals.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(13) Log vats on and after July 6, 2029, except as noted in footnote “2” to this table</ENT>
                                <ENT>Meet the work practice requirements specified in § 63.2241(f).</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(14) Resinated material handling (RMH) process units on and after July 6, 2029, except as noted in footnote “2” to this table, as applicable</ENT>
                                <ENT>Meet the work practice requirements specified in § 63.2241(g).</ENT>
                            </ROW>
                            <TNOTE>
                                <SU>1</SU>
                                 New or reconstructed affected sources that commenced construction or reconstruction after September 6, 2019, must comply with this requirement beginning on August 13, 2020, or upon initial startup, whichever is later.
                            </TNOTE>
                            <TNOTE>
                                <SU>2</SU>
                                 New or reconstructed affected sources that commenced construction or reconstruction after May 18, 2023, must comply with this requirement beginning on July 6, 2026, or upon initial startup, whichever is later.
                            </TNOTE>
                        </GPOTABLE>
                        <GPOTABLE COLS="3" OPTS="L2,nj,p7,7/8,i1" CDEF="s75,r50,r100">
                            <TTITLE>Table 4 to Subpart DDDD of Part 63—Requirements for Performance Tests</TTITLE>
                            <BOXHD>
                                <CHED H="1" O="L">For . . .</CHED>
                                <CHED H="1" O="L">You must . . .</CHED>
                                <CHED H="1" O="L">Using . . .</CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">(1) Each process unit subject to a compliance option in tables 1A through 1E to this subpart</ENT>
                                <ENT>select sampling port's location and the number of traverse ports</ENT>
                                <ENT>EPA Method 1 or 1A of appendix A-1 to part 60 of this chapter (as appropriate).</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(2) Each process unit subject to a compliance option in tables 1A through 1E to this subpart</ENT>
                                <ENT>determine velocity and volumetric flow rate</ENT>
                                <ENT>EPA Method 2 in addition to Methods 2A, 2C, 2D, 2F, or 2G of appendices A-1 and A-2 to part 60 of this chapter (as appropriate).</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(3) Each process unit subject to a compliance option in tables 1A through 1E to this subpart</ENT>
                                <ENT>conduct gas molecular weight analysis</ENT>
                                <ENT>EPA Method 3, 3A, or 3B of appendix A-2 to part 60 of this chapter (as appropriate). As an alternative to EPA Method 3B for the manual procedures only and not the instrumental procedures, you may use ANSI/ASME PTC 19-10-1981 Part 10 (IBR, see § 63.14).</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(4) Each process unit subject to a compliance option in tables 1A through 1E to this subpart</ENT>
                                <ENT>measure moisture content of the stack gas</ENT>
                                <ENT>EPA Method 4 of appendix A-3 to part 60 of this chapter; OR EPA Method 320 of appendix A to this part; OR ASTM D6348-12e1 (IBR, see § 63.14).</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(5) Each process unit subject to a compliance option in table 1B to this subpart for which you choose to demonstrate compliance using a total HAP as THC compliance option</ENT>
                                <ENT>measure emissions of total HAP as THC</ENT>
                                <ENT>EPA Method 25A in appendix A-7 to part 60 of this chapter. You may measure emissions of methane using EPA Method 18 in appendix A-6 to part 60 of this chapter and subtract the methane emissions from the emissions of total HAP as THC.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(6) Each process unit subject to a compliance option in table 1A to this subpart</ENT>
                                <ENT>measure emissions of total HAP (as defined in § 63.2292)</ENT>
                                <ENT>EPA Method 320 of appendix A to this part; OR the NCASI Method IM/CAN/WP-99.02 (IBR, see § 63.14); OR the NCASI Method ISS/FP-A105.01 (IBR, see § 63.14); OR ASTM D6348-12e1 (IBR, see § 63.14) provided that the conditions in footnote “1” are met.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(7) Each process unit subject to a compliance option in table 1B to this subpart for which you choose to demonstrate compliance using a methanol compliance option</ENT>
                                <ENT>measure emissions of methanol</ENT>
                                <ENT>EPA Method 308 of appendix A to this part; OR EPA Method 320 of appendix A to this part; OR the NCASI Method CI/WP-98.01 (IBR, see § 63.14); OR the NCASI Method IM/CAN/WP-99.02 (IBR, see § 63.14); OR the NCASI Method ISS/FP-A105.01 (IBR, see § 63.14).</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(8) Each process unit subject to a compliance option in table 1B to this subpart for which you choose to demonstrate compliance using a formaldehyde compliance option</ENT>
                                <ENT>measure emissions of formaldehyde</ENT>
                                <ENT>EPA Method 316 of appendix A to this part; OR EPA Method 320 of appendix A to this part; OR EPA Method 0011 in “Test Methods for Evaluating Solid Waste, Physical/Chemical Methods” (EPA Publication No. SW-846) for formaldehyde (IBR, see § 63.14); OR the NCASI Method CI/WP-98.01 (IBR, see § 63.14); OR the NCASI Method IM/CAN/WP-99.02 (IBR, see § 63.14); OR the NCASI Method ISS/FP-A105.01 (IBR, see § 63.14).</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(9) Each reconstituted wood product press at a new or existing affected source or reconstituted wood product board cooler at a new affected source subject to a compliance option in table 1B to this subpart</ENT>
                                <ENT>
                                    meet the design specifications included in the definition of wood products enclosure in § 63.2292; or
                                    <LI>determine the percent capture efficiency of the enclosure directing emissions to an add-on control device</LI>
                                </ENT>
                                <ENT>EPA Methods 204 and 204A through 204F of appendix M to part 51 of this chapter, to determine capture efficiency (except for wood products enclosures as defined in § 63.2292). Enclosures that meet the definition of wood products enclosure or that meet Method 204 requirements for a permanent total enclosure (PTE) are assumed to have a capture efficiency of 100 percent. Enclosures that do not meet either the PTE requirements or design criteria for a wood products enclosure must determine the capture efficiency by constructing a TTE according to the requirements of EPA Method 204 and applying EPA Methods 204A through 204F (as appropriate). As an alternative to EPA Methods 204 and 204A through 204F, you may use the tracer gas method contained in appendix A to this subpart.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(10) Each reconstituted wood product press at a new or existing affected source or reconstituted wood product board cooler at a new affected source subject to a compliance option in table 1A to this subpart</ENT>
                                <ENT>determine the percent capture efficiency</ENT>
                                <ENT>A TTE and EPA Methods 204 and 204A through 204F (as appropriate) of appendix M to part 51 of this chapter. As an alternative to installing a TTE and using EPA Methods 204 and 204A through 204F, you may use the tracer gas method contained in appendix A to this subpart. Enclosures that meet the design criteria (1) through (4) in the definition of wood products enclosure, or that meet EPA Method 204 requirements for a PTE (except for the criteria specified in section 6.2 of EPA Method 204) are assumed to have a capture efficiency of 100 percent. Measured emissions divided by the capture efficiency provides the emission rate.</ENT>
                            </ROW>
                            <ROW>
                                <PRTPAGE P="41455"/>
                                <ENT I="01">(11) Each process unit subject to a compliance option in tables 1A and 1B to this subpart</ENT>
                                <ENT>establish the site-specific operating requirements (including the parameter limits or THC concentration limits) in table 2 to this subpart</ENT>
                                <ENT>Data from the parameter monitoring system or THC CEMS and the applicable performance test method(s).</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(12) Each process unit subject to total HAP limit in table 1C to this subpart</ENT>
                                <ENT>measure emissions of total HAP (as defined in § 63.2292)</ENT>
                                <ENT>EPA Method 320 of appendix A to this part; OR the NCASI Method IM/CAN/WP-99.02 (IBR, see § 63.14); OR the NCASI Method ISS/FP-A105.01 (IBR, see § 63.14); OR ASTM D6348-12e1 (IBR, see § 63.14) provided that the conditions in footnote “1” are met. Nondetect data must be treated according to § 63.2262(g)(3).</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(13) Each process unit subject to an MDI limit in table 1C to this subpart</ENT>
                                <ENT>measure emissions of MDI</ENT>
                                <ENT>EPA Method 326 of appendix A to this part. Nondetect data must be treated according to § 63.2262(g)(3). A minimum sample volume of 1 dscm must be collected.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(14) Each process unit subject to a PM HAP metals limit in table 1D or 1E to this subpart</ENT>
                                <ENT>measure emissions of PM</ENT>
                                <ENT>EPA Method 5 in appendix A-3 to part 60 of this chapter; or EPA Method 29 in appendix A-8 to part 60 of this chapter. Nondetect data must be treated according to § 63.2262(g)(3). A minimum sample volume of 2 dscm must be collected.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(15) Each process unit subject to a mercury limit in table 1D or 1E to this subpart</ENT>
                                <ENT>measure emissions of mercury</ENT>
                                <ENT>EPA Method 29 or 30B in appendix A-8 to part 60 of this chapter. Nondetect data must be treated according to § 63.2262(g)(3). For EPA Method 29 a minimum sample volume of 2 dscm must be collected.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(16) Each process unit subject to an HCl limit in table 1D or 1E to this subpart</ENT>
                                <ENT>measure emissions of HCl</ENT>
                                <ENT>EPA Method 26A in appendix A-8 to part 60 of this chapter. Nondetect data must be treated according to § 63.2262(g)(3). A minimum sample volume of 2 dscm must be collected.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(17) Each process unit subject to a PAH limit in table 1D or 1E to this subpart and each direct wood-fired softwood veneer dryer subject to this subpart</ENT>
                                <ENT>measure emissions of PAH</ENT>
                                <ENT>EPA Method 23 of appendix A-8 to part 60 of this chapter. Nondetect data must be treated according to § 63.2262(g)(3). A minimum sample volume of 3 dscm must be collected.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(18) Each process unit subject to a PM limit in table 1D or table 1E to this subpart controlled by mechanical collector or other dry control device for which pressure drop and opacity observations are used to demonstrate compliance</ENT>
                                <ENT>observe opacity</ENT>
                                <ENT>Method 9 of appendix A-4 to part 60 of this chapter. Opacity observations must be conducted during the duration of the PM performance test. For weekly observations, two 6-minute readings are required.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(19) Each direct wood-fired green rotary dryer subject to a dioxin/furan TEQ limit in § 63.2240(d)(3) or (4)</ENT>
                                <ENT>Measure emissions of dioxins and furans</ENT>
                                <ENT>EPA Method 23 of appendix A-8 to part 60 of this chapter. Nondetect and estimated maximum possible concentration (EMPC) data must be treated according to § 63.2262(g)(3) and section 9.1.7.2 of EPA Method 23 procedures for standards promulgated after March 20, 2023. A minimum sample volume of 3 dscm must be collected. For each dioxin and furan congener, multiply the congener concentration by its corresponding toxic equivalency factor specified in table 12 to this subpart to determine the TEQ concentration for each congener. Sum the TEQ concentrations of each congener to obtain the total concentration of dioxins and furans emitted in terms of TEQ.</ENT>
                            </ROW>
                            <TNOTE>dscm = dry standard cubic meters.</TNOTE>
                            <TNOTE>
                                <SU>1</SU>
                                 As an alternative to EPA Method 320 of appendix A to this part, you may use ASTM Method D6348-12e1 (incorporated by reference, see § 63.14), with the caveats that the test plan preparation and implementation in the Annexes to ASTM Method D6348-12el, Sections Al through A8 are mandatory; and in ASTM Method D6348-12e1 Annex A5 (Analyte Spiking Technique), the percent (%) R must be determined for each target analyte (Equation A5.5). In order for the test data to be acceptable for a compound, %R must be 70% ≤ R ≤ 130%. If the %R value does not meet this criterion for a target compound, the test data is not acceptable for that compound and the test must be repeated for that analyte (
                                <E T="03">i.e.,</E>
                                 the sampling and/or analytical procedure should be adjusted before a retest). The %R value for each compound must be reported in the test report, and all field measurements must be corrected with the calculated %R value for that compound by using the following equation:
                            </TNOTE>
                            <TNOTE>Reported Results = (Measured Concentration in the Stack × 100)/% R.</TNOTE>
                        </GPOTABLE>
                        <GPOTABLE COLS="3" OPTS="L2,nj,p7,7/8,i1" CDEF="s75,r75,r100">
                            <TTITLE>Table 5 to Subpart DDDD of Part 63—Performance Testing and Initial Compliance Demonstrations for the Compliance Options and Operating Requirements</TTITLE>
                            <BOXHD>
                                <CHED H="1" O="L">For each . . .</CHED>
                                <CHED H="1" O="L">
                                    For the following compliance options 
                                    <LI>and operating requirements . . .</LI>
                                </CHED>
                                <CHED H="1" O="L">You have demonstrated initial compliance if . . .</CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">(1) Process unit listed in table 1A to this subpart</ENT>
                                <ENT>Meet the production-based compliance options listed in table 1A to this subpart</ENT>
                                <ENT>The average total HAP emissions measured using the methods in table 4 to this subpart over the 3-hour performance test are no greater than the compliance option in table 1A to this subpart; AND you have a record of the operating requirement(s) listed in table 2 to this subpart for the process unit over the performance test during which emissions did not exceed the compliance option value.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(2) Process unit listed in table 1B to this subpart</ENT>
                                <ENT>Reduce emissions of total HAP, measured as THC, by 90 percent</ENT>
                                <ENT>Total HAP emissions, measured using the methods in table 4 to this subpart over the 3-hour performance test, are reduced by at least 90 percent, as calculated using the procedures in § 63.2262; AND you have a record of the operating requirement(s) listed in table 2 to this subpart for the process unit over the performance test during which emissions were reduced by at least 90 percent.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(3) Process unit listed in table 1B to this subpart</ENT>
                                <ENT>Limit emissions of total HAP, measured as THC, to 20 ppmvd</ENT>
                                <ENT>The average total HAP emissions, measured using the methods in table 4 to this subpart over the 3-hour performance test, do not exceed 20 ppmvd; and you have a record of the operating requirement(s) listed in table 2 to this subpart for the process unit over the performance test during which emissions did not exceed 20 ppmvd.</ENT>
                            </ROW>
                            <ROW>
                                <PRTPAGE P="41456"/>
                                <ENT I="01">(4) Process unit listed in table 1B to this subpart</ENT>
                                <ENT>Reduce methanol or formaldehyde emissions by 90 percent</ENT>
                                <ENT>The methanol or formaldehyde emissions measured using the methods in table 4 to this subpart over the 3-hour performance test, are reduced by at least 90 percent, as calculated using the procedures in § 63.2262; AND you have a record of the operating requirement(s) listed in table 2 to this subpart for the process unit over the performance test during which emissions were reduced by at least 90 percent.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(5) Process unit listed in table 1B to this subpart</ENT>
                                <ENT>Limit methanol or formaldehyde emissions to less than or equal to 1 ppmvd (if uncontrolled emissions are greater than or equal to 10 ppmvd)</ENT>
                                <ENT>The average methanol or formaldehyde emissions, measured using the methods in table 4 to this subpart over the 3-hour performance test, do not exceed 1 ppmvd; AND you have a record of the operating requirement(s) listed in table 2 to this subpart for the process unit over the performance test during which emissions did not exceed 1 ppmvd. If the process unit is a reconstituted wood product press or a reconstituted wood product board cooler, your capture device either meets the EPA Method 204 criteria for a PTE or achieves a capture efficiency of greater than or equal to 95 percent.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(6) Reconstituted wood product press at a new or existing affected source, or reconstituted wood product board cooler at a new affected source</ENT>
                                <ENT>Compliance options in tables 1A and 1B to this subpart</ENT>
                                <ENT>You submit the results of capture efficiency verification using the methods in table 4 to this subpart with your Notification of Compliance Status.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(7) Process unit listed in table 1B to this subpart controlled by routing exhaust to a combustion unit</ENT>
                                <ENT>Compliance options in table 1B to this subpart</ENT>
                                <ENT>You submit with your Notification of Compliance Status documentation showing that the process exhausts controlled enter into the flame zone of your combustion unit.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(8) Process unit listed in table 1B to this subpart using a wet control device as the sole means of reducing HAP emissions</ENT>
                                <ENT>Compliance options in table 1B to this subpart</ENT>
                                <ENT>You submit with your Notification of Compliance Status your plan to address how organic HAP captured in the wastewater from the wet control device is contained or destroyed to minimize re-release to the atmosphere.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(9) Process unit listed in table 1C to this subpart</ENT>
                                <ENT>Total HAP compliance options in table 1C to this subpart</ENT>
                                <ENT>The average total HAP emissions measured using the methods in table 4 to this subpart over the 3-hour performance test are no greater than the compliance option in table 1C to this subpart; AND you have a record of the operating requirement(s) listed in table 2 to this subpart for the process unit over the performance test during which emissions did not exceed the compliance option value.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(10) Process unit listed in table 1C to this subpart</ENT>
                                <ENT>MDI compliance options in table 1C to this subpart</ENT>
                                <ENT>The average total HAP emissions measured using the methods in table 4 to this subpart over the 3-hour performance test are no greater than the compliance option in table 1C to this subpart; AND you have a record of the operating requirement(s) listed in table 2 to this subpart for the process unit over the performance test during which emissions did not exceed the compliance option value.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(11) Direct wood-fired PCWP dryer listed in table 1D or 1E to this subpart</ENT>
                                <ENT>PM (HAP metal), Hg, HCl, and PAH compliance options in table 1D or 1E to this subpart and dioxin/furan TEQ options in § 63.2240(d)(3) and (4)</ENT>
                                <ENT>The average emissions measured using the methods in table 4 to this subpart over the 3-hour performance test are no greater than the compliance option in tables 1D and 1E to this subpart; AND you have a record of the operating requirement(s) listed in table 2 to this subpart for the process unit over the performance test during which emissions did not exceed the compliance option value.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(12) Mixed PCWP process stream as defined in § 63.2292</ENT>
                                <ENT>Compliance options in table 1B to this subpart</ENT>
                                <ENT>You identify the mixed PCWP process stream in your Notification of Compliance Status and submit documentation showing that the mixed PCWP process stream met a compliance option in table 1B to this subpart on or before the close of business on the 30th calendar day after July 6, 2026.</ENT>
                            </ROW>
                        </GPOTABLE>
                        <GPOTABLE COLS="3" OPTS="L2,nj,p7,7/8,i1" CDEF="s75,r75,r100">
                            <TTITLE>Table 6 to Subpart DDDD of Part 63—Initial Compliance Demonstrations for Work Practice Requirements</TTITLE>
                            <BOXHD>
                                <CHED H="1" O="L">For each . . .</CHED>
                                <CHED H="1" O="L">
                                    For the following work practice 
                                    <LI>requirements . . .</LI>
                                </CHED>
                                <CHED H="1" O="L">You have demonstrated initial compliance if . . .</CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">(1) Dry rotary dryer</ENT>
                                <ENT>Process furnish with an inlet moisture content less than or equal to 30 percent (by weight, dry basis) and operate with an inlet dryer temperature of less than or equal to 600 °F</ENT>
                                <ENT>You meet the work practice requirement and you submit a signed statement with the Notification of Compliance Status that the dryer meets the criteria of a “dry rotary dryer” and you have a record of the inlet moisture content and inlet dryer temperature (as required in § 63.2263).</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(2) Hardwood veneer dryer</ENT>
                                <ENT>Process less than 30 volume percent softwood species</ENT>
                                <ENT>You meet the work practice requirement and you submit a signed statement with the Notification of Compliance Status that the dryer meets the criteria of a “hardwood veneer dryer” and you have a record of the percentage of softwoods processed in the dryer (as required in § 63.2264).</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(3) Softwood veneer dryer</ENT>
                                <ENT>Minimize fugitive emissions from the dryer doors and the green end</ENT>
                                <ENT>You meet the work practice requirement and you submit with the Notification of Compliance Status a copy of your plan for minimizing fugitive emissions from the veneer dryer heated zones (as required in § 63.2265).</ENT>
                            </ROW>
                            <ROW>
                                <PRTPAGE P="41457"/>
                                <ENT I="01">(4) Veneer redryers</ENT>
                                <ENT>Process veneer with an inlet moisture content of less than or equal to 25 percent (by weight, dry basis)</ENT>
                                <ENT>You meet the work practice requirement and you submit a signed statement with the Notification of Compliance Status that the dryer operates only as a redryer and you have a record of the veneer inlet moisture content of the veneer processed in the redryer (as required in § 63.2266).</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(5) Group 1 miscellaneous coating operations</ENT>
                                <ENT>Use non-HAP coatings as defined in § 63.2292</ENT>
                                <ENT>You meet the work practice requirement and you submit a signed statement with the Notification of Compliance Status that you are using non-HAP coatings and you have a record showing that you are using non-HAP coatings.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(6) Process units and control systems undergoing safety-related shutdown on and after August 13, 2021, except as noted in footnote “1” to this table</ENT>
                                <ENT>Follow documented site-specific procedures to ensure the flow of raw materials and fuel or process heat ceases and that material is removed from the process unit(s) as expeditiously as possible given the system design to reduce air emissions</ENT>
                                <ENT>You meet the work practice requirement and you have a record of safety-related shutdown procedures available for inspection by the delegated authority upon request.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(7) Pressurized refiners undergoing startup or shutdown on and after August 13, 2021, except as noted in footnote “1” to this table</ENT>
                                <ENT>Route exhaust gases from the pressurized refiner to its dryer control system no later than 15 minutes after wood is fed to the pressurized refiner during startup. Stop wood flow into the pressurized refiner no more than 15 minutes after wood fiber and exhaust gases from the pressurized refiner stop being routed to the dryer during shutdown</ENT>
                                <ENT>You meet the work practice requirement and you have a record of pressurized refiner startup and shutdown procedures available for inspection by the delegated authority upon request.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(8) Direct-fired softwood veneer dryers undergoing startup or shutdown of gas-fired burners on and after August 13, 2021, except as noted in footnote “1” to this table</ENT>
                                <ENT>Cease feeding green veneer into the softwood veneer dryer and minimize the amount of time direct gas-fired softwood veneer dryers are vented to the atmosphere due to the conditions described in § 63.2250(d)</ENT>
                                <ENT>You meet the work practice requirement and you have a record of the procedures for startup and shutdown of softwood veneer dryer gas-fired burners available for inspection by the delegated authority upon request.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(9) Direct wood-fired PCWP dryers, direct natural gas-fired PCWP dryers, direct-fired lumber kilns, and associated bypass stacks for combustion unit exhaust streams routinely used to direct-fire a PCWP dryer or lumber kiln on and after July 6, 2029, except as noted in footnote “2” to this table</ENT>
                                <ENT>Conduct an annual tune-up of combustion unit(s) used to directly fire each PCWP dryer or lumber kiln as specified in § 63.2241(d) AND continuously monitor an indicator of bypass stack usage</ENT>
                                <ENT>You submit with your Notification of Compliance Status documentation of the initial burner tune up conducted according to § 63.2241(d); and you identify in your Notification of Compliance Status the method used to continuously monitor and record the duration of bypass stack usage.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(10) Lumber kilns on and after July 6, 2029, except as noted in footnote “2” to this table</ENT>
                                <ENT>Minimize lumber over-drying to reduce HAP emissions according to the work practice requirements in § 63.2241(e)</ENT>
                                <ENT>You submit with your Notification of Compliance Status the O&amp;M plan developed according to §§ 63.2241(e)(1) and 63.2250(a) and a description of the work practice option you will comply with according to § 63.2241(e)(3); and if using the site-specific plan option under § 63.2241(e)(3)(iii) you must submit your site-specific plan to the delegated authority for approval according to § 63.2253(b) by the date specified in § 63.2253(b)(1).</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(11) Stand-alone digesters on and after July 6, 2029, except as noted in footnote “2” to this table</ENT>
                                <ENT>Use clean steam for injection into digestion process; and process fiber without addition of HAP-containing or wood pulping chemicals</ENT>
                                <ENT>You meet the work practice requirement and you submit a signed statement with the Notification of Compliance Status that the stand-alone digester operates according to the work practice.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(12) Fiber washers on and after July 6, 2029, except as noted in footnote “2” to this table</ENT>
                                <ENT>Process fiber without addition of HAP-containing or wood pulping chemicals</ENT>
                                <ENT>You meet the work practice requirement and you submit a signed statement with the Notification of Compliance Status that the fiber washer operates according to the work practice.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(13) Log vats on and after July 6, 2029, except as noted in footnote “2” to this table</ENT>
                                <ENT>Operate the log vat with a target log temperature at or below 212 °F as specified in § 63.2241(f)</ENT>
                                <ENT>You meet the work practice requirements and you submit a signed statement with the Notification of Compliance Status with a record showing that the target log temperature is at or below 212 °F.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(14) Resinated material handling (RMH) process units on and after July 6, 2029, except as noted in footnote “2” to this table</ENT>
                                <ENT>Work practice requirements specified in § 63.2241(g)</ENT>
                                <ENT>You meet the work practice requirements and you submit a signed statement with the Notification of Compliance Status that resin(s) used are non-HAP resin(s) or have maximum true vapor pressure of less than or equal to the applicable limit in § 63.2241(g)(1)(ii) and that wood material processes meets the requirements in 63.2241(g)(2).</ENT>
                            </ROW>
                            <TNOTE>
                                <SU>1</SU>
                                 New or reconstructed affected sources that commenced construction or reconstruction after September 6, 2019, must comply with this requirement beginning on August 13, 2020, or upon initial startup, whichever is later.
                            </TNOTE>
                            <TNOTE>
                                <SU>2</SU>
                                 New or reconstructed affected sources that commenced construction or reconstruction after May 18, 2023, must comply with this requirement beginning on July 6, 2026, or upon initial startup, whichever is later.
                            </TNOTE>
                        </GPOTABLE>
                        <PRTPAGE P="41458"/>
                        <GPOTABLE COLS="3" OPTS="L2,nj,p7,7/8,i1" CDEF="s75,r75,r100">
                            <TTITLE>Table 7 to Subpart DDDD of Part 63—Continuous Compliance With the Compliance Options and Operating Requirements</TTITLE>
                            <BOXHD>
                                <CHED H="1" O="L">For . . .</CHED>
                                <CHED H="1" O="L">
                                    For the following compliance options 
                                    <LI>and operating requirements . . .</LI>
                                </CHED>
                                <CHED H="1" O="L">You must demonstrate continuous compliance by . . .</CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">(1) Each process unit listed in table 1B to this subpart or mixed PCWP process unit (defined in § 63.2292)</ENT>
                                <ENT>Compliance options in table 1B to this subpart and the operating requirements in table 2 to this subpart based on monitoring of operating parameters</ENT>
                                <ENT>Collecting and recording the operating parameter monitoring system data listed in table 2 to this subpart for the process unit according to §§ 63.2269(a) and (b) and 63.2270; and reducing the operating parameter monitoring system data to the specified averages in units of the applicable requirement according to calculations in § 63.2270; and maintaining the average operating parameter at or above the minimum, at or below the maximum, or within the range (whichever applies) established according to § 63.2262.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(2) Each process unit listed in tables 1A and 1B to this subpart</ENT>
                                <ENT>Compliance options in tables 1A and 1B to this subpart and the operating requirements in table 2 to this subpart based on THC CEMS data</ENT>
                                <ENT>Collecting and recording the THC monitoring data listed in table 2 to this subpart for the process unit according to § 63.2269(d); and reducing the CEMS data to 3-hour block averages according to calculations in § 63.2269(d); and maintaining the 3-hour block average THC concentration in the exhaust gases less than or equal to the THC concentration established according to § 63.2262.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(3) Each process unit using a biofilter</ENT>
                                <ENT>Compliance options in tables 1B to this subpart</ENT>
                                <ENT>
                                    Conducting a repeat performance test using the applicable method(s) specified in table 4 to this subpart 
                                    <SU>1</SU>
                                     within 2 years following the previous performance test and within 180 days after each replacement of any portion of the biofilter bed media with a different type of media or each replacement of more than 50 percent (by volume) of the biofilter bed media with the same type of media.
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(4) Each process unit using a catalytic oxidizer</ENT>
                                <ENT>Compliance options in table 1B to this subpart</ENT>
                                <ENT>
                                    Checking the activity level of a representative sample of the catalyst at least annually 
                                    <SU>2</SU>
                                     and taking any necessary corrective action to ensure that the catalyst is performing within its design range.
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(5) Each process unit listed in table 1A to this subpart</ENT>
                                <ENT>Compliance options in table 1A to this subpart and the operating requirements in table 2 to this subpart based on monitoring of process unit controlling operating parameters</ENT>
                                <ENT>Collecting and recording on a daily basis process unit controlling operating parameter data; and maintaining the operating parameter at or above the minimum, at or below the maximum, or within the range (whichever applies) established according to § 63.2262.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(6) Each Process unit listed in table 1B to this subpart using a wet control device as the sole means of reducing HAP emissions</ENT>
                                <ENT>Compliance options in table 1B to this subpart</ENT>
                                <ENT>Implementing your plan to address how organic HAP captured in the wastewater from the wet control device is contained or destroyed to minimize re-release to the atmosphere.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(7) Each process unit listed in table 1B to this subpart using a control device other than a biofilter</ENT>
                                <ENT>Compliance options in tables 1B to this subpart</ENT>
                                <ENT>
                                    Conducting a repeat performance test using the applicable method(s) specified in table 4 to this subpart 
                                    <SU>1</SU>
                                     by August 13, 2023, or within 60 months following the previous performance test, whichever is later, and thereafter within 60 months following the previous performance test.
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(8) Process unit listed in table 1C to this subpart</ENT>
                                <ENT>Total HAP compliance options in table 1C to this subpart and the operating requirements in table 2 to this subpart based on monitoring of operating parameters</ENT>
                                <ENT>The average total HAP emissions measured using the methods in table 4 to this subpart over the 3-hour performance test are no greater than the compliance option in table 1C to this subpart; and you have a record of the operating requirement(s) listed in table 2 to this subpart for the process unit over the performance test during which emissions did not exceed the compliance option value.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(9) Process unit listed in table 1C to this subpart</ENT>
                                <ENT>MDI compliance options in table 1C to this subpart and the operating requirements in table 2 to this subpart based on monitoring of operating parameters</ENT>
                                <ENT>The average MDI emissions measured using the methods in table 4 to this subpart over the 3-hour performance test are no greater than the compliance option in table 1C to this subpart; AND you have a record of the operating requirement(s) listed in table 2 to this subpart for the process unit over the performance test during which emissions did not exceed the compliance option value.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(10) Direct wood-fired PCWP dryer using a wet or dry electrostatic precipitator, wet scrubber, electrified filter bed, thermal oxidizer, catalytic oxidizer, or biofilter to meet the standards in table 1D or 1E to this subpart</ENT>
                                <ENT>Compliance options in § 63.2240(d)(2) and (3) and table 1D or 1E to this subpart and the operating requirements in table 2 to this subpart based on monitoring of operating parameters</ENT>
                                <ENT>Collecting and recording the operating parameter monitoring system data listed in table 2 to this subpart for the process unit according to §§ 63.2269(a) and (b) and 63.2270; and reducing the operating parameter monitoring system data to the specified averages in units of the applicable requirement according to calculations in § 63.2270; and maintaining the average operating parameter at or above the minimum, at or below the maximum, or within the range (whichever applies) established according to § 63.2262.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(11) Direct wood-fired PCWP dryer using a mechanical collector or other dry control device (not elsewhere listed in this table) or a WESP followed by a control device with a dry exhaust to meet the standards in table 1D or 1E to this subpart</ENT>
                                <ENT>Compliance options in § 63.2240(d)(2) and (3) and table 1D or 1E to this subpart and the operating requirements in table 2 to this subpart based on continuous opacity monitoring</ENT>
                                <ENT>Collecting and recording opacity data according to §§ 63.2269(e) and 63.2270; and reducing the opacity data to a 24-hour block average according to § 63.2270; and maintaining the average opacity at or below the maximum established according to § 63.2262.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(12) Process unit bypass stack (defined in § 63.2292)</ENT>
                                <ENT>Continuously monitor usage of the process unit bypass stack at all times while the process units are operating, undergoing startup or shutdown, and during the operating conditions specified in § 63.2250(f)(2) through (4)</ENT>
                                <ENT>Continuously monitoring and recording the duration of bypass stack usage according to §§ 63.2269(a) and (l) and 63.2270.</ENT>
                            </ROW>
                            <ROW>
                                <PRTPAGE P="41459"/>
                                <ENT I="01">(13) Each process unit listed in table 1C, 1D, or 1E to this subpart</ENT>
                                <ENT>Total HAP and MDI limits in table 1C to this subpart (as applicable), and the PM, Hg, HCl, and PAH limits in table 1D or 1E to this subpart (as applicable), and the dioxin/furan TEQ limits in § 63.2240(d)(2) and (3)</ENT>
                                <ENT>
                                    Conducting a repeat performance test using the applicable method(s) specified in table 4 to this subpart
                                    <SU>1</SU>
                                     within 60 months following the previous performance test.
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(14) Direct wood-fired PCWP dryer using a mechanical collector or other dry control device (not elsewhere listed in this table) to meet the standards in table 1D or 1E to this subpart</ENT>
                                <ENT>Compliance options in § 63.2240(d)(2) and (3) and table 1D or 1E to this subpart and the operating requirements in table 2 to this subpart based on pressure drop monitoring and opacity observations</ENT>
                                <ENT>Collecting and recording pressure drop and opacity observations listed in table 2 to this subpart according to §§ 63.2269(a) and (f) and 63.2270; and reducing the pressure drop monitoring system data to the specified averages in units of the applicable requirement according to calculations in § 63.2270; and maintaining the average pressure drop above the minimum established according to § 63.2262; and maintaining the weekly opacity observations at or below the maximum established according to § 63.2262.</ENT>
                            </ROW>
                            <TNOTE>
                                <SU>1</SU>
                                 When conducting a repeat performance test, the capture efficiency demonstration required in table 4 to this subpart, row 9 is not required to be repeated with the repeat emissions test if the capture device is maintained and operated consistent with its design as well as its operation during the previous capture efficiency demonstration conducted according to table 4 to this subpart, row 9 as specified in § 63.2267.
                            </TNOTE>
                            <TNOTE>
                                <SU>2</SU>
                                 You may forego the annual catalyst activity check during the calendar year when a performance test is conducted according to table 4 to this subpart.
                            </TNOTE>
                        </GPOTABLE>
                        <GPOTABLE COLS="3" OPTS="L2,nj,p7,7/8,i1" CDEF="s75,r75,r100">
                            <TTITLE>Table 8 to Subpart DDDD of Part 63—Continuous Compliance With the Work Practice Requirements</TTITLE>
                            <BOXHD>
                                <CHED H="1" O="L">For . . .</CHED>
                                <CHED H="1" O="L">
                                    For the following work practice 
                                    <LI>requirements . . .</LI>
                                </CHED>
                                <CHED H="1" O="L">You must demonstrate continuous compliance by . . .</CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">(1) Dry rotary dryer</ENT>
                                <ENT>Process furnish with an inlet moisture content less than or equal to 30 percent (by weight, dry basis) and operate with an inlet dryer temperature of less than or equal to 600 °F</ENT>
                                <ENT>Maintaining the 24-hour block average inlet furnish moisture content at less than or equal to 30 percent (by weight, dry basis) and maintaining the 24-hour block average inlet dryer temperature at less than or equal to 600 °F; and keeping records of the inlet temperature of furnish moisture content and inlet dryer temperature.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(2) Hardwood veneer dryer</ENT>
                                <ENT>Process less than 30 volume percent softwood species</ENT>
                                <ENT>Maintaining the volume percent softwood species processed below 30 percent and keeping records of the volume percent softwood species processed.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(3) Softwood veneer dryer</ENT>
                                <ENT>Minimize fugitive emissions from the dryer doors and the green end</ENT>
                                <ENT>Following (and documenting that you are following) your plan for minimizing fugitive emissions.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(4) Veneer redryers</ENT>
                                <ENT>Process veneer with an inlet moisture content of less than or equal to 25 percent (by weight, dry basis)</ENT>
                                <ENT>Maintaining the 24-hour block average inlet moisture content of the veneer processed at or below of less than or 25 percent and keeping records of the inlet moisture content of the veneer processed.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(5) Group 1 miscellaneous coating operations</ENT>
                                <ENT>Use non-HAP coatings as defined in § 63.2292</ENT>
                                <ENT>Continuing to use non-HAP coatings and keeping records showing that you are using non-HAP coatings.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(6) Process units and control systems undergoing safety-related shutdown on and after August 13, 2021, except as noted in footnote “1” to this table</ENT>
                                <ENT>Follow documented site-specific procedures to ensure the flow of raw materials and fuel or process heat ceases and that material is removed from the process unit(s) as expeditiously as possible given the system design to reduce air emissions</ENT>
                                <ENT>Keeping records showing that you are following the work practice requirements during safety-related shutdowns.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(7) Pressurized refiners undergoing startup or shutdown on and after August 13, 2021, except as noted in footnote “1” to this table</ENT>
                                <ENT>Route exhaust gases from the pressurized refiner to its dryer control system no later than 15 minutes after wood is fed to the pressurized refiner during startup. Stop wood flow into the pressurized refiner no more than 15 minutes after wood fiber and exhaust gases from the pressurized refiner stop being routed to the dryer during shutdown</ENT>
                                <ENT>Keeping records showing that you are following the work practice requirements during pressurized refiner startup and shutdown events.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(8) Direct-fired softwood veneer dryers undergoing startup or shutdown of gas-fired burners on and after August 13, 2021, except as noted in footnote “1” to this table</ENT>
                                <ENT>Cease feeding green veneer into the softwood veneer dryer and minimize the amount of time direct gas-fired softwood veneer dryers are vented to the atmosphere due to the conditions described in § 63.2250(d)</ENT>
                                <ENT>Keeping records showing that you are following the work practice requirements while undergoing startup or shutdown of softwood veneer dryer direct gas-fired burners.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(9) Direct wood-fired PCWP dryers, direct natural gas-fired PCWP dryers, direct-fired lumber kilns, and associated combustion unit bypass stacks on and after July 6, 2029, except as noted in footnote “2” to this table</ENT>
                                <ENT>Conduct an annual tune-up of combustion unit(s) used to directly fire each PCWP dryer or lumber kiln as specified in § 63.2271(c); AND continuously monitor an indicator of bypass stack usage</ENT>
                                <ENT>Conducting and maintaining records of annual burner inspections and corrective actions taken; and continuously monitoring and recording the duration of combustion unit bypass stack usage according to §§ 63.2269(a) and (k) and 63.2270.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(10) Lumber kilns on and after July 6, 2029, except as noted in footnote “2” to this table</ENT>
                                <ENT>O&amp;M plan developed under § 63.2241(e)(1) involving annual inspection of lumber kiln integrity and review of charge optimization practices and corrective actions</ENT>
                                <ENT>Operating according to your O&amp;M plan developed under § 63.2241(e)(1); and conducting annual inspection of the integrity of the lumber kiln internal air flow and heat distribution components, reviewing charge optimization practices, implementing corrective actions, and maintaining records of corrective actions according to § 63.2241(e)(1)(c).</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(11) Lumber kilns on and after July 6, 2029, except as noted in footnote “2” to this table</ENT>
                                <ENT>Temperature limit option under § 63.2241(e)(3)(i)</ENT>
                                <ENT>Operating the kiln with a dry bulb temperature limit no higher than the maximum limit specified in § 63.2241(e)(3)(i); and continuously monitoring dry bulb temperature; and maintaining records of the batch average or daily block average dry bulb temperature.</ENT>
                            </ROW>
                            <ROW>
                                <PRTPAGE P="41460"/>
                                <ENT I="01">(12) Lumber kilns on and after July 6, 2029, except as noted in footnote “2” to this table</ENT>
                                <ENT>Hybrid option under § 63.2241(e)(3)(ii)</ENT>
                                <ENT>Operating the kiln with a dry bulb temperature limit no higher than the maximum limit specified in § 63.2241(e)(3)(ii)(A); and continuously monitoring dry bulb temperature; and maintaining records of the batch average or daily block average dry bulb temperature and continuously monitoring lumber moisture while drying lumber; and keeping records of the kiln-dried lumber moisture content for determination of the semiannual average according to § 63.2241(e)(3)(ii)(B)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(13) Lumber kilns on and after July 6, 2029, except as noted in footnote “2” to this table</ENT>
                                <ENT>Site-specific plan option for temperature and lumber moisture monitoring under § 63.2241(e)(3)(iii)</ENT>
                                <ENT>Operating the kiln using the approved site specific temperature limit and site-specific method for lumber moisture monitoring under § 63.2241(e)(3)(iii); continuously monitoring, recording, and calculating the 3-hour block average temperature under § 63.2241(e)(3)(iii)(A); continuously monitoring, recording, and calculating the monthly and semiannual average kiln-dried lumber moisture content under § 63.2241(e)(3)(iii)(B); and maintaining records and reporting corrective action as required in § 63.2241(e)(3)(iii)(B).</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(14) Stand-alone digesters on and after July 6, 2029, except as noted in footnote “2” to this table</ENT>
                                <ENT>Use clean steam for injection into digestion process; and process fiber without addition of HAP-containing or wood pulping chemicals</ENT>
                                <ENT>Continuing to meet the work practice by using clean steam and processing fiber without addition of HAP-containing or wood pulping chemicals and keeping records showing that you continue to meet the work practice.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(15) Fiber washers on and after July 6, 2029, except as noted in footnote “2” to this table</ENT>
                                <ENT>Process fiber without addition of HAP-containing or wood pulping chemicals</ENT>
                                <ENT>Continuing to meet the work practice by processing fiber without addition of HAP-containing or wood pulping chemicals AND keeping records showing that you continue to meet the work practice.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(16) Log vats on and after July 6, 2029, except as noted in footnote “2” to this table</ENT>
                                <ENT>Operate the log vat with a target log temperature at or below 212 °F as specified in § 63.2241(f)</ENT>
                                <ENT>Continuing to meet the work practice by operating the log vat as specified in § 63.2241(f) and keeping records showing that you continue to meet the work practice.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(17) Resinated material handling (RMH) process units on and after July 6, 2029, except as noted in footnote “2” to this table</ENT>
                                <ENT>Work practice requirements specified in § 63.2241(g)</ENT>
                                <ENT>Continuing to meet the work practice requirements in § 63.2241(g) and keeping records showing that you continue to meet the work practice.</ENT>
                            </ROW>
                            <TNOTE>
                                <SU>1</SU>
                                 New or reconstructed affected sources that commenced construction or reconstruction after September 6, 2019, must comply with this requirement beginning on August 13, 2020, or upon initial startup, whichever is later.
                            </TNOTE>
                            <TNOTE>
                                <SU>2</SU>
                                 New or reconstructed affected sources that commenced construction or reconstruction after May 18, 2023, must comply with this requirement beginning on July 6, 2026, or upon initial startup, whichever is later.
                            </TNOTE>
                        </GPOTABLE>
                        <GPOTABLE COLS="3" OPTS="L2,nj,p7,7/8,i1" CDEF="s70,r50,r50">
                            <TTITLE>Table 9 to Subpart DDDD of Part 63—Requirements for Reports</TTITLE>
                            <BOXHD>
                                <CHED H="1" O="L">You must submit a(n) . . .</CHED>
                                <CHED H="1" O="L">The report must contain . . .</CHED>
                                <CHED H="1" O="L">You must submit the report . . .</CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">(1) Compliance report</ENT>
                                <ENT>The information in § 63.2281(c) through (g)</ENT>
                                <ENT>Semiannually according to the requirements in § 63.2281(b).</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(2) [Reserved]</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(3) Performance test report</ENT>
                                <ENT>The information required in § 63.7(g)</ENT>
                                <ENT>According to the requirements of § 63.2281(i).</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(4) CMS performance evaluation, as required for CEMS under § 63.2269(d)(2) and COMS under § 63.2269(e)(2)</ENT>
                                <ENT>The information required in § 63.7(g)</ENT>
                                <ENT>According to the requirements of § 63.2281(j).</ENT>
                            </ROW>
                        </GPOTABLE>
                        <GPOTABLE COLS="4" OPTS="L2,nj,p7,7/8,i1" CDEF="xs80,r50,r100,xs120">
                            <TTITLE>Table 10 to Subpart DDDD of Part 63—Applicability of General Provisions to This Subpart</TTITLE>
                            <BOXHD>
                                <CHED H="1">Citation</CHED>
                                <CHED H="1">Subject</CHED>
                                <CHED H="1">Brief description</CHED>
                                <CHED H="1">Applies to this subpart</CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">§ 63.1</ENT>
                                <ENT>Applicability</ENT>
                                <ENT>Initial applicability determination; applicability after standard established; permit requirements; extensions, notifications</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.2</ENT>
                                <ENT>Definitions</ENT>
                                <ENT>Definitions for standards in this part</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.3</ENT>
                                <ENT>Units and Abbreviations</ENT>
                                <ENT>Units and abbreviations for standards in this part</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.4</ENT>
                                <ENT>Prohibited Activities and Circumvention</ENT>
                                <ENT>Prohibited activities; compliance date; circumvention, fragmentation</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.5</ENT>
                                <ENT>Preconstruction Review and Notification Requirements</ENT>
                                <ENT>Preconstruction review requirements of section 112(i)(1)</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.6(a)</ENT>
                                <ENT>Applicability</ENT>
                                <ENT>GP apply unless compliance extension; GP apply to area sources that become major</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.6(b)(1) through (4)</ENT>
                                <ENT>Compliance Dates for New and Reconstructed Sources</ENT>
                                <ENT>Standards apply at effective date; 3 years after effective date; upon startup; 10 years after construction or reconstruction commences for section 112(f)</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.6(b)(5)</ENT>
                                <ENT>Notification</ENT>
                                <ENT>Must notify if commenced construction or reconstruction after proposal</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.6(b)(6)</ENT>
                                <ENT>[Reserved]</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.6(b)(7)</ENT>
                                <ENT>Compliance Dates for New and Reconstructed Area Sources that Become Major</ENT>
                                <ENT>Area sources that become major must comply with major source standards immediately upon becoming major, regardless of whether required to comply when they were an area source</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.6(c)(1) and (2)</ENT>
                                <ENT>Compliance Dates for Existing Sources</ENT>
                                <ENT>Comply according to date in subpart, which must be no later than 3 years after effective date; for section 112(f) standards, comply within 90 days of effective date unless compliance extension</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.6(c)(3) and (4)</ENT>
                                <ENT>[Reserved]</ENT>
                            </ROW>
                            <ROW>
                                <PRTPAGE P="41461"/>
                                <ENT I="01">§ 63.6(c)(5)</ENT>
                                <ENT>Compliance Dates for Existing Area Sources that Become Major</ENT>
                                <ENT>
                                    Area sources that become major must comply with major source standards by date indicated in subpart or by equivalent time period (e.g
                                    <E T="03">.,</E>
                                     3 years)
                                </ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.6(d)</ENT>
                                <ENT>[Reserved]</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.6(e)(1)(i)</ENT>
                                <ENT>General Duty to Minimize Emissions</ENT>
                                <ENT>You must operate and maintain affected source in a manner consistent with safety and good air pollution control practices for minimizing emissions</ENT>
                                <ENT>No, see § 63.2250 for general duty requirement.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.6(e)(1)(ii)</ENT>
                                <ENT>Requirement to Correct Malfunctions ASAP</ENT>
                                <ENT>You must correct malfunctions as soon as practicable after their occurrence</ENT>
                                <ENT>No.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.6(e)(1)(iii)</ENT>
                                <ENT>Operation and Maintenance Requirements</ENT>
                                <ENT>Operation and maintenance requirements are enforceable independent of emissions limitations or other requirements in relevant standards</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.6(e)(2)</ENT>
                                <ENT>[Reserved]</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.6(e)(3)</ENT>
                                <ENT>Startup, Shutdown, and Malfunction Plan (SSMP)</ENT>
                                <ENT>Requirement for SSM and SSMP; content of SSMP</ENT>
                                <ENT>No.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.6(f)(1)</ENT>
                                <ENT>SSM Exemption</ENT>
                                <ENT>You must comply with emission standards at all times except during SSM</ENT>
                                <ENT>No.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.6(f)(2) and (3)</ENT>
                                <ENT>Methods for Determining Compliance/Finding of Compliance</ENT>
                                <ENT>Compliance based on performance test, operation and maintenance plans, records, inspection</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.6(g)(1) through (3)</ENT>
                                <ENT>Alternative Standard</ENT>
                                <ENT>Procedures for getting an alternative standard</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.6(h)(1)</ENT>
                                <ENT>SSM Exemption</ENT>
                                <ENT>You must comply with opacity and visible emission standards at all times except during SSM</ENT>
                                <ENT>No.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.6(h)(2) through (9)</ENT>
                                <ENT>Opacity/Visible Emission (VE) Standards</ENT>
                                <ENT>Requirements for opacity and visible emission standards</ENT>
                                <ENT>No. This subpart specifies opacity as an operating limit not an emission standard.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.6(i)(1)-(14)</ENT>
                                <ENT>Compliance Extension</ENT>
                                <ENT>Procedures and criteria for Administrator to grant compliance extension</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.6(i)(15)</ENT>
                                <ENT>[Reserved]</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.6(i)(16)</ENT>
                                <ENT>Compliance Extension</ENT>
                                <ENT>Compliance extension and Administrator's authority</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.6(j)</ENT>
                                <ENT>Presidential Compliance Exemption</ENT>
                                <ENT>President may exempt source category from requirement to comply with rule</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.7(a)(1) and (2)</ENT>
                                <ENT>Performance Test Dates</ENT>
                                <ENT>Dates for conducting initial performance testing and other compliance demonstrations; must conduct within 180 days after first subject to rule</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.7(a)(3)</ENT>
                                <ENT>Section 114 Authority</ENT>
                                <ENT>Administrator may require a performance test under CAA section 114 at any time</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.7(b)(1)</ENT>
                                <ENT>Notification of Performance Test</ENT>
                                <ENT>Must notify Administrator 60 days before the test</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.7(b)(2)</ENT>
                                <ENT>Notification of Rescheduling</ENT>
                                <ENT>If have to reschedule performance test, must notify Administrator as soon as practicable</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.7(c)</ENT>
                                <ENT>Quality Assurance/Test Plan</ENT>
                                <ENT>Requirement to submit site-specific test plan 60 days before the test or on date Administrator agrees with; test plan approval procedures; performance audit requirements; internal and external QA procedures for testing</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.7(d)</ENT>
                                <ENT>Testing Facilities</ENT>
                                <ENT>Requirements for testing facilities</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.7(e)(1)</ENT>
                                <ENT>Performance Testing</ENT>
                                <ENT>Performance tests must be conducted under representative conditions; cannot conduct performance tests during SSM; not a violation to exceed standard during SSM</ENT>
                                <ENT>No, see § 63.2262(a) and (b).</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.7(e)(2)</ENT>
                                <ENT>Conditions for Conducting Performance Tests</ENT>
                                <ENT>Must conduct according to rule and EPA test methods unless Administrator approves alternative</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.7(e)(3)</ENT>
                                <ENT>Test Run Duration</ENT>
                                <ENT>Must have three test runs for at least the time specified in the relevant standard; compliance is based on arithmetic mean of three runs; specifies conditions when data from an additional test run can be used</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.7(f)</ENT>
                                <ENT>Alternative Test Method</ENT>
                                <ENT>Procedures by which Administrator can grant approval to use an alternative test method</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.7(g)</ENT>
                                <ENT>Performance Test Data Analysis</ENT>
                                <ENT>Must include raw data in performance test report; must submit performance test data 60 days after end of test with the notification of compliance status; keep data for 5 years</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.7(h)</ENT>
                                <ENT>Waiver of Tests</ENT>
                                <ENT>Procedures for Administrator to waive performance test</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.8(a)(1)</ENT>
                                <ENT>Applicability of Monitoring Requirements</ENT>
                                <ENT>Subject to all monitoring requirements in standard</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.8(a)(2)</ENT>
                                <ENT>Performance Specifications</ENT>
                                <ENT>Performance specifications in appendix B of part 60 of this chapter</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.8(a)(3)</ENT>
                                <ENT>[Reserved]</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.8(a)(4)</ENT>
                                <ENT>Monitoring with Flares</ENT>
                                <ENT>Requirements for flares in § 63.11 apply</ENT>
                                <ENT>NA.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.8(b)(1)</ENT>
                                <ENT>Monitoring</ENT>
                                <ENT>Must conduct monitoring according to standard unless Administrator approves alternative</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.8(b)(2) and (3)</ENT>
                                <ENT>Multiple Effluents and Multiple Monitoring Systems</ENT>
                                <ENT>Specific requirements for installing monitoring systems; must install on each effluent before it is combined and before it is released to the atmosphere unless Administrator approves otherwise; if more than one monitoring system on an emission point, must report all monitoring system results, unless one monitoring system is a backup</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.8(c)(1)</ENT>
                                <ENT>Monitoring System Operation and Maintenance</ENT>
                                <ENT>Maintain monitoring system in a manner consistent with good air pollution control practices</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.8(c)(1)(i)</ENT>
                                <ENT>Operation and Maintenance of CMS</ENT>
                                <ENT>Must maintain and operate CMS in accordance with § 63.6(e)(1)</ENT>
                                <ENT>No.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.8(c)(1)(ii)</ENT>
                                <ENT>Spare Parts for CMS</ENT>
                                <ENT>Must maintain spare parts for routine CMS repairs</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <PRTPAGE P="41462"/>
                                <ENT I="01">§ 63.8(c)(1)(iii)</ENT>
                                <ENT>Requirements to Develop SSMP for CMS</ENT>
                                <ENT>Must develop and implement SSMP for CMS</ENT>
                                <ENT>No.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.8(c)(2)-(3)</ENT>
                                <ENT>Monitoring System Installation</ENT>
                                <ENT>Must install to get representative emission of parameter measurements; must verify operational status before or at performance test</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.8(c)(4)</ENT>
                                <ENT>CMS Requirements</ENT>
                                <ENT>CMS must be operating except during breakdown, out-of-control, repair, maintenance, and high-level calibration drifts; COMS must have a minimum of one cycle of sampling and analysis for each successive 10-second period and one cycle of data recording for each successive 6-minute period; CEMS must have a minimum of one cycle of operation for each successive 15-minute period</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.8(c)(5)</ENT>
                                <ENT>Continuous Opacity Monitoring System (COMS) Minimum Procedures</ENT>
                                <ENT>COMS minimum procedures</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.8(c)(6) through (8)</ENT>
                                <ENT>CMS Requirements</ENT>
                                <ENT>Zero and high-level calibration check requirements; out-of-control periods</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.8(d)(1) and (2)</ENT>
                                <ENT>CMS Quality Control</ENT>
                                <ENT>Requirements for CMS quality control, including calibration, etc.</ENT>
                                <ENT>Yes. Refer to § 63.2269(a) through (c) and (f) through (o) for CPMS quality control procedures to be included in the quality control program.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.8(d)(3)</ENT>
                                <ENT>Written Procedures for CMS</ENT>
                                <ENT>Must keep quality control plan on record for 5 years. Keep old versions for 5 years after revisions. May incorporate as part of SSMP to avoid duplication.</ENT>
                                <ENT>No, see § 63.2282(f).</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.8(e)(1)</ENT>
                                <ENT>CMS Performance Evaluation</ENT>
                                <ENT>Performance evaluation</ENT>
                                <ENT>Yes, for CEMS, COMS, and for the CMS in § 63.2269(f) and (g) and (i) through (l)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.8(e)(2) through (5)</ENT>
                                <ENT>CMS Performance Evaluation</ENT>
                                <ENT>Notification, performance evaluation test plan, reports</ENT>
                                <ENT>Yes, for CEMS and COMS.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.8(f)(1) through (5)</ENT>
                                <ENT>Alternative Monitoring Method</ENT>
                                <ENT>Procedures for Administrator to approve alternative monitoring</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.8(f)(6)</ENT>
                                <ENT>Alternative to Relative Accuracy Test</ENT>
                                <ENT>Procedures for Administrator to approve alternative relative accuracy tests for CEMS</ENT>
                                <ENT>Yes, for CEMS.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.8(g)</ENT>
                                <ENT>Data Reduction</ENT>
                                <ENT>COMS 6-minute averages calculated over at least 36 evenly spaced data points; CEMS 1 hour averages computed over at least 4 equally spaced data points; data that can't be used in average; rounding of data</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.9(a)</ENT>
                                <ENT>Notification Requirements</ENT>
                                <ENT>Applicability and State delegation</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.9(b)(1) and (2)</ENT>
                                <ENT>Initial Notifications</ENT>
                                <ENT>Submit notification 120 days after effective date; contents of notification</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.9(b)(3)</ENT>
                                <ENT>[Reserved]</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.9(b)(4) and (5)</ENT>
                                <ENT>Initial Notifications</ENT>
                                <ENT>Submit notification 120 days after effective date; notification of intent to construct/reconstruct; notification of commencement of construct/reconstruct; notification of startup; contents of each</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.9(c)</ENT>
                                <ENT>Request for Compliance Extension</ENT>
                                <ENT>Can request if cannot comply by date or if installed best available control technology/lowest achievable emission rate</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.9(d)</ENT>
                                <ENT>Notification of Special Compliance Requirements for New Source</ENT>
                                <ENT>For sources that commence construction between proposal and promulgation and want to comply 3 years after effective date</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.9(e)</ENT>
                                <ENT>Notification of Performance Test</ENT>
                                <ENT>Notify the EPA Administrator 60 days prior</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.9(f)</ENT>
                                <ENT>Notification of Visible Emissions/Opacity Test</ENT>
                                <ENT>Notify the EPA Administrator 30 days prior</ENT>
                                <ENT>Yes, except notifications are not required for opacity observations in § 63.2270(k).</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.9(g)</ENT>
                                <ENT>Additional Notifications When Using CMS</ENT>
                                <ENT>Notification of performance evaluation; notification using COMS data; notification that exceeded criterion for relative accuracy</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.9(h)(1) through (6)</ENT>
                                <ENT>Notification of Compliance Status</ENT>
                                <ENT>Contents; due 60 days after end of performance test or other compliance demonstration, except for opacity/VE, which are due 30 days after; when to submit to Federal vs. State authority</ENT>
                                <ENT>Yes, except notifications are not required for opacity observations in § 63.2270(k).</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.9(i)</ENT>
                                <ENT>Adjustment of Submittal Deadlines</ENT>
                                <ENT>Procedures for Administrator to approve change in when notifications must be submitted</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.9(j)</ENT>
                                <ENT>Change in Previous Information</ENT>
                                <ENT>Must submit within 15 days after the change</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.9(k)</ENT>
                                <ENT>Electronic reporting procedures</ENT>
                                <ENT>Electronic reporting procedures</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.10(a)</ENT>
                                <ENT>Recordkeeping/Reporting</ENT>
                                <ENT>Applies to all, unless compliance extension; when to submit to Federal vs. State authority; procedures for owners of more than one source</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.10(b)(1)</ENT>
                                <ENT>Recordkeeping/Reporting</ENT>
                                <ENT>General Requirements; keep all records readily available; keep for 5 years</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.10(b)(2)(i)</ENT>
                                <ENT>Recordkeeping of Occurrence and Duration of Startups and Shutdowns</ENT>
                                <ENT>Records of occurrence and duration of each startup or shutdown that causes source to exceed emission limitation</ENT>
                                <ENT>No, see § 63.2282(a).</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.10(b)(2)(ii)</ENT>
                                <ENT>Recordkeeping of Failures to Meet a Standard</ENT>
                                <ENT>Records of occurrence and duration of each malfunction of operation or air pollution control and monitoring equipment</ENT>
                                <ENT>No, see § 63.2282(a) for recordkeeping of (1) date, time and duration; (2) listing of affected source or equipment, and an estimate of the quantity of each regulated pollutant emitted over the standard; and (3) actions to minimize emissions and correct the failure.</ENT>
                            </ROW>
                            <ROW>
                                <PRTPAGE P="41463"/>
                                <ENT I="01">§ 63.10(b)(2)(iii)</ENT>
                                <ENT>Maintenance Records</ENT>
                                <ENT>Records of maintenance performed on air pollution control and monitoring equipment</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.10(b)(2)(iv) and (v)</ENT>
                                <ENT>Actions Taken to Minimize Emissions During SSM</ENT>
                                <ENT>Records of actions taken during SSM to minimize emissions</ENT>
                                <ENT>No.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.10(b)(2)(vi), (x), and (xi)</ENT>
                                <ENT>CMS Records</ENT>
                                <ENT>Malfunctions, inoperative, out-of-control</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.10(b)(2)(vii) through (ix)</ENT>
                                <ENT>Records</ENT>
                                <ENT>Measurements to demonstrate compliance with compliance options and operating requirements; performance test, performance evaluation, and visible emission observation results; measurements to determine conditions of performance tests and performance evaluations</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.10(b)(2)(xii)</ENT>
                                <ENT>Records</ENT>
                                <ENT>Records when under waiver</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.10(b)(2)(xiii)</ENT>
                                <ENT>Records</ENT>
                                <ENT>Records when using alternative to relative accuracy test</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.10(b)(2)(xiv)</ENT>
                                <ENT>Records</ENT>
                                <ENT>All documentation supporting initial notification and notification of compliance status</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.10(b)(3)</ENT>
                                <ENT>Records</ENT>
                                <ENT>Applicability determinations</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.10(c)(1) through (6) and (9) through (14)</ENT>
                                <ENT>Records</ENT>
                                <ENT>Additional records for CMS</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.10(c)(7) and (8)</ENT>
                                <ENT>Records</ENT>
                                <ENT>Records of excess emissions and parameter monitoring exceedances for CMS</ENT>
                                <ENT>No.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.10(c)(15)</ENT>
                                <ENT>Use of SSMP</ENT>
                                <ENT>Use SSMP to satisfy recordkeeping requirements for identification of malfunction, correction action taken, and nature of repairs to CMS</ENT>
                                <ENT>No.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.10(d)(1)</ENT>
                                <ENT>General Reporting Requirements</ENT>
                                <ENT>Requirement to report</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.10(d)(2)</ENT>
                                <ENT>Report of Performance Test Results</ENT>
                                <ENT>When to submit to Federal or State authority</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.10(d)(3)</ENT>
                                <ENT>Reporting Opacity or VE Observations</ENT>
                                <ENT>What to report and when</ENT>
                                <ENT>NA.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.10(d)(4)</ENT>
                                <ENT>Progress Reports</ENT>
                                <ENT>Must submit progress reports on schedule if under compliance extension</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.10(d)(5)(i)</ENT>
                                <ENT>Periodic SSM Reports</ENT>
                                <ENT>Contents and submission of periodic SSM reports</ENT>
                                <ENT>No, see § 63.2281(d) and (e) for malfunction reporting requirements.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.10(d)(5)(ii)</ENT>
                                <ENT>Immediate SSM Reports</ENT>
                                <ENT>Contents and submission of immediate SSM reports</ENT>
                                <ENT>No.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.10(e)(1) and (2)</ENT>
                                <ENT>Additional CMS Reports</ENT>
                                <ENT>Must report results for each CEM on a unit; written copy of performance evaluation; 3 copies of COMS performance evaluation</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.10(e)(3)</ENT>
                                <ENT>Reports</ENT>
                                <ENT>Excess emission reports</ENT>
                                <ENT>No.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.10(e)(4)</ENT>
                                <ENT>Reporting COMS Data</ENT>
                                <ENT>Must submit COMS data with performance test data</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.10(f)</ENT>
                                <ENT>Waiver for Recordkeeping/Reporting</ENT>
                                <ENT>Procedures for the EPA Administrator to waive</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.11</ENT>
                                <ENT>Control Device and Work Practice Requirements</ENT>
                                <ENT>Requirements for flares and alternative work practice for equipment leaks</ENT>
                                <ENT>NA.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.12</ENT>
                                <ENT>State Authority and Delegations</ENT>
                                <ENT>State authority to enforce standards</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.13</ENT>
                                <ENT>Addresses</ENT>
                                <ENT>Addresses where reports, notifications, and requests are sent</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.14</ENT>
                                <ENT>Incorporations by Reference</ENT>
                                <ENT>Test methods incorporated by reference</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.15</ENT>
                                <ENT>Availability of Information and Confidentiality</ENT>
                                <ENT>Public and confidential information</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.16</ENT>
                                <ENT>Performance Track Provisions</ENT>
                                <ENT>Requirements for Performance Track member facilities</ENT>
                                <ENT>Yes.</ENT>
                            </ROW>
                        </GPOTABLE>
                    </REGTEXT>
                    <REGTEXT TITLE="40" PART="63">
                        <AMDPAR>22. Add tables 11 and 12 to subpart DDDD of part 63 to read as follows:</AMDPAR>
                        <GPOTABLE COLS="2" OPTS="L2,nj,i1" CDEF="s150,30">
                            <TTITLE>Table 11 to Subpart DDDD of Part 63—Lumber Minimum Moisture Content Limits</TTITLE>
                            <BOXHD>
                                <CHED H="1" O="L">
                                    If the maximum lumber 
                                    <LI>moisture specification (weight percent, dry basis) is . . .</LI>
                                </CHED>
                                <CHED H="1" O="L">
                                    The minimum kiln-dried lumber moisture content (weight percent, 
                                    <LI>dry basis) is . . .</LI>
                                </CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">22 or more</ENT>
                                <ENT>15</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">19-21</ENT>
                                <ENT>12</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">18</ENT>
                                <ENT>11</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">17</ENT>
                                <ENT>10</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">16</ENT>
                                <ENT>9</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">15</ENT>
                                <ENT>8</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">14</ENT>
                                <ENT>7</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">13</ENT>
                                <ENT>6</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">10-12</ENT>
                                <ENT>5</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">9</ENT>
                                <ENT>4.5</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">8</ENT>
                                <ENT>4</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">7</ENT>
                                <ENT>3.5</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">6</ENT>
                                <ENT>3</ENT>
                            </ROW>
                        </GPOTABLE>
                        <PRTPAGE P="41464"/>
                        <GPOTABLE COLS="2" OPTS="L2,nj,i1" CDEF="s150,30">
                            <TTITLE>Table 12 to Subpart DDDD of Part 63—Toxic Equivalency Factors</TTITLE>
                            <BOXHD>
                                <CHED H="1">Dioxin/furan congener</CHED>
                                <CHED H="1">Toxic equivalency factor</CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">2,3,7,8-tetrachlorinated dibenzo-p-dioxin</ENT>
                                <ENT>1</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">1,2,3,7,8-pentachlorinated dibenzo-p-dioxin</ENT>
                                <ENT>1</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">1,2,3,4,7,8-hexachlorinated dibenzo-p-dioxin</ENT>
                                <ENT>0.1</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">1,2,3,7,8,9-hexachlorinated dibenzo-p-dioxin</ENT>
                                <ENT>0.1</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">1,2,3,6,7,8-hexachlorinated dibenzo-p-dioxin</ENT>
                                <ENT>0.1</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">1,2,3,4,6,7,8-heptachlorinated dibenzo-p-dioxin</ENT>
                                <ENT>0.01</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">octachlorinated dibenzo-p-dioxin</ENT>
                                <ENT>0.0003</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">2,3,7,8-tetrachlorinated dibenzofuran</ENT>
                                <ENT>0.1</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">2,3,4,7,8-pentachlorinated dibenzofuran</ENT>
                                <ENT>0.3</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">1,2,3,7,8-pentachlorinated dibenzofuran</ENT>
                                <ENT>0.03</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">1,2,3,4,7,8-hexachlorinated dibenzofuran</ENT>
                                <ENT>0.1</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">1,2,3,6,7,8-hexachlorinated dibenzofuran</ENT>
                                <ENT>0.1</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">1,2,3,7,8,9-hexachlorinated dibenzofuran</ENT>
                                <ENT>0.1</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">2,3,4,6,7,8-hexachlorinated dibenzofuran</ENT>
                                <ENT>0.1</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">1,2,3,4,6,7,8-heptachlorinated dibenzofuran</ENT>
                                <ENT>0.01</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">1,2,3,4,7,8,9-heptachlorinated dibenzofuran</ENT>
                                <ENT>0.01</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">octachlorinated dibenzofuran</ENT>
                                <ENT>0.0003</ENT>
                            </ROW>
                        </GPOTABLE>
                    </REGTEXT>
                </SUPLINF>
                <FRDOC>[FR Doc. 2026-13550 Filed 7-2-26; 8:45 am]</FRDOC>
                <BILCOD>BILLING CODE 6560-50-P</BILCOD>
            </RULE>
        </RULES>
    </NEWPART>
    <VOL>91</VOL>
    <NO>127</NO>
    <DATE>Monday, July 6, 2026</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="41465"/>
            <PARTNO>Part VI</PARTNO>
            <AGENCY TYPE="P">Department of Homeland Security</AGENCY>
            <CFR>6 CFR Part 124</CFR>
            <AGENCY TYPE="P">Department of Justice</AGENCY>
            <CFR>28 CFR Part 124</CFR>
            <TITLE>Counter-UAS Authority for State, Local, Tribal, and Territorial Law Enforcement and Correctional Agencies; Interim Final Rule</TITLE>
        </PTITLE>
        <RULES>
            <RULE>
                <PREAMB>
                    <PRTPAGE P="41466"/>
                    <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                    <CFR>6 CFR Part 124</CFR>
                    <RIN>RIN 1601-AB25</RIN>
                    <AGENCY TYPE="O">DEPARTMENT OF JUSTICE</AGENCY>
                    <CFR>28 CFR Part 124</CFR>
                    <DEPDOC>[Docket No. FBI-2026-0001]</DEPDOC>
                    <RIN>RIN 1110-AA39</RIN>
                    <SUBJECT>Counter-UAS Authority for State, Local, Tribal, and Territorial Law Enforcement and Correctional Agencies</SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCIES:</HD>
                        <P>Department of Homeland Security; Department of Justice.</P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Interim final rule; request for comment.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>In this interim final rule (“IFR”), the Department of Justice (“DOJ”) and the Department of Homeland Security (“DHS”) (collectively, “the Departments”) codify the framework for implementing the SAFER SKIES Act, which authorizes State, local, Tribal, and territorial law enforcement or correctional (“SLTT”) agencies to conduct counter-unmanned aircraft system (“C-UAS”) operations. This framework governs training and certification (including a two-tiered structure for detection and warning operations and for mitigation operations), authorized technologies, spectrum coordination, airspace approval, real-time air traffic control notification, mitigation reporting, privacy protections, and compliance requirements for SLTT agencies in relation to the exercise of C-UAS authority.</P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P/>
                        <P>
                            <E T="03">Effective date:</E>
                             This interim final rule is effective July 1, 2026.
                        </P>
                        <P>
                            <E T="03">Comment due date:</E>
                             Comments must be received on or before September 4, 2026. The electronic Federal Docket Management System (“FDMS”) at 
                            <E T="03">https://www.regulations.gov</E>
                             will accept electronic comments until 11:59 p.m. Eastern Time on that date.
                        </P>
                    </EFFDATE>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P>
                            You may submit comments on the entirety of this IFR, identified by FDMS Docket No. FBI-2026-0001, through the Federal eRulemaking Portal: 
                            <E T="03">https://www.regulations.gov.</E>
                             Follow the website instructions for submitting comments. The Departments are not accepting mailed, couriered, or hand-delivered comments at this time. If you cannot submit your comment by using 
                            <E T="03">https://www.regulations.gov,</E>
                             please use the contact information in the 
                            <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                             section for alternate instructions.
                        </P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P/>
                        <P>
                            <E T="03">For DHS:</E>
                             Steven A. Willoughby, Acting Executive Director, Program Executive Office for Drones and Counter-Unmanned Aircraft Systems, U.S. Department of Homeland Security, 
                            <E T="03">drones@dhs.gov.</E>
                        </P>
                        <P>
                            <E T="03">For DOJ:</E>
                             Micheal J. Torphy, Assistant Section Chief, Unmanned Aviation Section, Critical Incident Response Group, Federal Bureau of Investigation, 
                            <E T="03">ncutc@fbi.gov.</E>
                        </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <HD SOURCE="HD1">I. Public Participation</HD>
                    <P>The Departments invite all interested parties to participate in this rulemaking by submitting written data, views, comments, and arguments on all aspects of this rule. The Departments also invite comments that relate to the economic, environmental, or federalism effects that might result from this rule. Comments must be submitted in English, or an English translation must be provided. Comments that will provide the most assistance to the Departments in implementing these changes will reference a specific portion of the rule, explain the reason for any recommended change, and include data, information, or authority that supports such recommended change. Comments submitted in a manner other than the one listed above, including emails or letters sent to Department officials, will not be considered comments on the rule and may not receive a response from the Departments.</P>
                    <P>
                        <E T="03">Instructions:</E>
                         If you submit a comment, you must include the agency name (Federal Bureau of Investigation) and the FDMS Docket No. FBI-2026-0001 for this rulemaking. All submissions will be posted, without change, to the Federal eRulemaking Portal at 
                        <E T="03">https://www.regulations.gov,</E>
                         and will include any personal information you provide. Therefore, submitting this information makes it public. You may wish to consider limiting the amount of personal information that you provide in any voluntary public comment submission you make to the Departments. The Departments may withhold information provided in comments from public viewing that they determine may impact the privacy of an individual or is offensive. For additional information, please read the Privacy and Security Notice available at 
                        <E T="03">https://www.regulations.gov.</E>
                    </P>
                    <P>
                        <E T="03">Docket:</E>
                         For access to the docket and to read background documents or comments received, go to 
                        <E T="03">https://www.regulations.gov,</E>
                         referencing FDMS Docket No. FBI-2026-0001. You may also sign up for email alerts on the online docket to be notified when comments are posted or a final rule is published.
                    </P>
                    <HD SOURCE="HD1">II. Executive Summary</HD>
                    <P>
                        In 2018, Congress recognized the growing threat of drones (unmanned aircraft) and unmanned aircraft systems (“UAS”) to public safety and national security, including their use by extremists, terrorists, and criminals. 
                        <E T="03">See</E>
                         S. Rep. No. 115-332, at 2-3 (2018). Congress recognized that “[t]errorist organizations promote the use of UAS to conduct attacks in the U.S. and surveillance on potential targets.” 
                        <E T="03">Id.</E>
                         at 2. In one notable instance, “Al-Qaeda in the Arabian Peninsula used their Inspire magazine in May 2016 to encourage individuals to use UAS to collect information about potential assassination attempts and killings.” 
                        <E T="03">Id.</E>
                         And “[i]n September 2011, Rezwan Ferdaus, a U.S. citizen, was arrested for planning to attach explosives to a UAS and attack the Pentagon and U.S. Capitol.” 
                        <E T="03">Id.</E>
                         “Another potentially dangerous incident occurred in 2017 when a UAS flew over the San Francisco 49ers and Oakland Raiders National Football League stadiums dropping leaflets and causing panic.” 
                        <E T="03">Id.</E>
                    </P>
                    <P>
                        Congress also recognized that Federal law hampered the ability of law enforcement to respond to these threats. Congress noted that Federal law enforcement agencies were “prohibited from taking actions against UAS due to decades-old statutes,” such as “the Wiretap Act of 1968 and the Computer Fraud and Abuse Act of 1986,” that “were enacted long before UAS were widely available.” 
                        <E T="03">Id.</E>
                         Such laws make “it illegal to intercept any wire, oral, or electronic communication, or to access a computer without authorization, respectively, making it imposing to use the electronic transmission to track down the operator of the drone.” 
                        <E T="03">Id.</E>
                         Congress also noted that “DHS and DOJ are prevented from taking action against a rogue UAS due to the FAA Modernization and Reform Act of 2012 that define[d] UAS as aircraft” and as a result subjected UAS to “aircraft piracy laws [that] ma[de] it illegal to seize or exercise control of an aircraft.” 
                        <E T="03">Id.</E>
                         (citing 49 U.S.C. 331).
                    </P>
                    <P>
                        In order to remedy this problem, as part of the FAA Reauthorization Act of 2018, Congress passed the Preventing Emerging Threats Act of 2018, which authorized the Secretary of Homeland Security and the Attorney General to designate certain facilities or assets as 
                        <PRTPAGE P="41467"/>
                        “covered facilities or assets” and take certain measures necessary to mitigate a credible threat that an unmanned aircraft or UAS poses to the safety or security of a covered facility or asset, notwithstanding certain provisions of Federal criminal law, including prohibitions against aircraft piracy, destruction of an aircraft, computer fraud, interference with the operation of a satellite, the Wiretap Act, and the prohibition on pen register and trap and trace device use. Public Law 115-254, sec. 1602(a), 132 Stat. 3186, 3522-29 (codified at 6 U.S.C. 124n). Generally, the authorized protective measures included, and still include, detection, disruption, seizure, confiscation, and destruction of UAS using reasonable force (if necessary). 6 U.S.C. 124n(b)(1)(F). However, the Act did not authorize SLTT agencies to take such measures.
                    </P>
                    <P>
                        In testimony before the Senate Judiciary Committee in July 2025, DOJ recommended that all SLTT agencies be authorized to address the continuing threat of UAS (for example, smuggling contraband into prisons, or threatening public safety at sporting events or other outdoor gatherings), again notwithstanding these same Federal criminal laws. Dep't of Justice, 
                        <E T="03">Securing the Skies: Law Enforcement, Drones, and Public Safety: Hearing Before the S. Comm. on the Judiciary,</E>
                         119th Cong. 8-9 (2025), 
                        <E T="03">https://www.judiciary.senate.gov/imo/media/doc/94f53245-d172-92ba-152b-06bc9ee00a50/2025-07-22%20-%20Testimony%20-%20Torphy%20&amp;%20Hardee1.pdf</E>
                         [
                        <E T="03">https://perma.cc/F3J7-NWDG</E>
                        ] (statement of Christopher Hardee, Chief, Office of Law &amp; Policy, Nat'l Sec. Div., DOJ, and Micheal Torphy, Unit Chief, Critical Incident Response Grp., FBI). DOJ suggested that State and local law enforcement be authorized to use pre-approved, detection-only equipment, and that certain State and local law enforcement be trained to use all C-UAS capabilities (including mitigation measures such as exercising control of a UAS or destroying a UAS). 
                        <E T="03">Id.</E>
                    </P>
                    <P>
                        In recognition of this continued challenge, Congress passed the SAFER SKIES Act, signed into law by the President on December 18, 2025. National Defense Authorization Act for Fiscal Year 2026, Public Law 119-60, div. H, tit. LXXXVI, §§ 8601-07, 139 Stat. 718, 1938-45 (2025) (“SAFER SKIES Act” or “the Act”) (codified in large part in 6 U.S.C. 124n). The SAFER SKIES Act authorizes SLTT agencies to take certain measures to detect and mitigate credible threats that unmanned aircraft and UAS pose to the safety or security of people, facilities, and assets, a venue or set of venues used for large-scale public gatherings or events, critical infrastructure, or correctional facilities,
                        <SU>1</SU>
                        <FTREF/>
                         notwithstanding the same provisions of Federal criminal law (prohibitions against aircraft piracy, destruction of an aircraft, computer fraud, interference with the operation of a satellite, the Wiretap Act, and the prohibition on pen register and trap and trace device use), and notwithstanding the laws of any particular State, local, Tribal, or territorial jurisdiction, but only under certain conditions. 6 U.S.C. 124n(a)(2).
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             Note that the SAFER SKIES Act also amended the definition of “personnel” under section 124n, thus facilitating the use of detailed and deputized personnel. 6 U.S.C. 124n(l)(6)(A). The FBI is currently using SLTT agencies as federally deputized task force officers in operations to mitigate UAS. This IFR does not address federally deputized or detailed SLTT agency personnel. Note as well that the Act provided two new bases for DOJ and DHS protective measures: that is, to enforce the law, and to protect the public. 6 U.S.C. 124n(a)(1). However, the Act did not make these two new bases available to SLTT agencies.
                        </P>
                    </FTNT>
                    <P>
                        Specifically, the SAFER SKIES Act authorizes SLTT agencies to take the mitigation measures identified in 6 U.S.C. 124n(b)(1)(C), (D), and (F) if they: (1) are trained and certified by the Attorney General, or the Attorney General's designee, through a national schoolhouse, 6 U.S.C. 124n(d)(2)(A)(i); (2) use technologies on authorized technologies and systems lists maintained jointly by DOJ, DHS, the Department of Defense,
                        <SU>2</SU>
                        <FTREF/>
                         the Department of Transportation, the Federal Communications Commission (“FCC”), and the National Telecommunications and Information Administration (“NTIA”), 6 U.S.C. 124n(d)(2)(A)(iii); (3) comply with specific compliance, coordination, and audit requirements, 6 U.S.C. 124n(d)(2)(B) (Oversight), (e) (Privacy protection); and (4) report mitigation actions to DOJ and DHS, 6 U.S.C. 124n(d)(2)(C). At the same time, the SAFER SKIES Act authorized SLTT agencies to take measures identified under 6 U.S.C. 124n(b)(1)(A), (B), and (E)—that is to detect, monitor, identify, track, and confiscate UAS, as well as warn the operator of a UAS, including by passive or active, direct or indirect physical, electronic, radio, or electromagnetic means, and through the use of a remote identification broadcast, or by other means—subject to satisfying training and certification procedures; but the training and certification procedures required to take these specific protective measures need not occur at a national schoolhouse. 6 U.S.C. 124n(a)(2) (allowing SLTT agencies to take measures in subsection (b)(1), but only subject to subsection (d)(2)); 
                        <E T="03">see also</E>
                         6 U.S.C. 124n(d)(2)(A)(ii) (providing that SLTT agencies must satisfy the training and certification procedures before taking any action in all of subsection (b)(1)).
                    </P>
                    <FTNT>
                        <P>
                            <SU>2</SU>
                             The Department of Defense is also known as the Department of War. E.O. 14347, 90 FR 43893 (Sept. 5, 2025). This rule refers to the “Department of Defense” to be consistent with the SAFER SKIES Act.
                        </P>
                    </FTNT>
                    <P>Finally, the Act directs the Secretary of Homeland Security and the Attorney General, in coordination with the Secretary of Defense, the Secretary of Transportation, and the Administrator of the Federal Aviation Administration (“FAA”), to develop and publish regulations governing C-UAS authority—that is, the authority to conduct protective measures to detect, identify, monitor, track, and, if necessary, mitigate the threat of UAS—for SLTT agencies under section 124n. This IFR implements this statutory authority, to include compliance requirements and procedures for coordination.</P>
                    <HD SOURCE="HD1">III. Background and Purpose</HD>
                    <HD SOURCE="HD2">A. Background and Legal Authority</HD>
                    <P>
                        As noted in Section II of this preamble above, the Preventing Emerging Threats Act of 2018 permits the Attorney General and the Secretary of Homeland Security to authorize certain personnel to take certain protective measures (generally, detection, disruption, seizure, confiscation, and disablement, damage, or destruction using reasonable force) necessary to mitigate a credible threat that an unmanned aircraft or UAS poses to the safety or security of a covered facility or asset, notwithstanding certain provisions of Federal criminal law. 
                        <E T="03">See</E>
                         6 U.S.C. 124n(b)(1). Specifically, the Attorney General and the Secretary of Homeland Security are authorized to take such measures notwithstanding Federal criminal prohibitions in 49 U.S.C. 46502 (aircraft piracy), 18 U.S.C. 32 (destruction of aircraft), 18 U.S.C. 1030 (computer fraud), and 18 U.S.C. 1367 (interference with the operation of a satellite), as well as chapters 119 (interception of communications) and 206 (pen registers and trap and trace devices) of Title 18. 6 U.S.C. 124n(a)(1). Generally, a “covered facility or asset” must be identified as high risk and a potential target for unlawful unmanned aircraft activity by the Secretary or the Attorney General, in coordination with the Secretary of Transportation with respect to potentially impacted airspace, through a risk-based assessment. 6 U.S.C. 124n(l)(3)(A).
                    </P>
                    <P>
                        The SAFER SKIES Act amended section 124n in several ways, notably by 
                        <PRTPAGE P="41468"/>
                        authorizing SLTT agencies to take certain protective measures to mitigate a credible threat that unmanned aircraft and UAS pose to the safety or security of people, facilities, and assets, a venue or set of venues used for large-scale public gatherings or events, critical infrastructure, or correctional facilities, notwithstanding certain provisions of Federal criminal law, and notwithstanding the laws of any particular State, local, Tribal, or territorial (“SLTT”) jurisdiction, 6 U.S.C. 124n(a)(2), but subject to additional requirements.
                    </P>
                    <P>
                        Notwithstanding the foregoing statutory changes, the SAFER SKIES Act did not amend or waive the applicability of other Federal statutory provisions that may govern or proscribe SLTT agencies' otherwise authorized activity, including those in the Communications Act or other regulations governing access to spectrum. 
                        <E T="03">See, e.g.,</E>
                         47 U.S.C. 301 (licensing and authorization), 47 U.S.C. 302 (interfering devices), 47 U.S.C. 333 (jamming), 47 U.S.C. 605 (unauthorized transmissions). As a result, this regulation requires SLTT agencies to obtain approvals from the FCC before deploying any C-UAS system (whether detection only or mitigation) that involves the emission of radio waves.
                    </P>
                    <HD SOURCE="HD3">1. Detecting, Identifying, Monitoring, Tracking, and Warning</HD>
                    <P>First, the Act authorizes SLTT agencies to “detect, identify, monitor, and track” UAS or unmanned aircraft, without prior consent, including by means of interception of or other access to a wire communication, an oral communication, or an electronic communication used to control the UAS or unmanned aircraft. 6 U.S.C. 124n(b)(1)(A). The Act also authorizes SLTT agencies to warn the operator of a UAS, including by “passive or active, and direct or indirect physical, electronic, radio, electromagnetic means, and through the use of remote identification broadcast or other means.” 6 U.S.C. 124n(b)(1)(B). The Act also allows SLTT agencies to seize or otherwise confiscate a UAS or unmanned aircraft. 6 U.S.C. 124n(b)(1)(E). This rule covers confiscation under section 124n(b)(1)(E) through the Detection and Warning Certification process alongside the detection and warning activities in section 124n(b)(1)(A) and (B) because, like those activities, confiscation does not involve the use of a mitigation technology. The Act authorizes SLTT agencies to take measures under section 124n(b)(1)(A), (B), and (E) subject to the training and certification requirement described in section 124n(d)(2)(A)(ii), which applies to all actions in section 124n(b)(1), only if they:</P>
                    <P>(1) use “systems or technologies that are included on a list of authorized technologies maintained jointly by the Department of Justice, the Department of Homeland Security, the Department of Defense, the Department of Transportation, the Federal Communications Commission, and the National Telecommunications and Information Administration,” 6 U.S.C. 124n(d)(2)(A)(iii);</P>
                    <P>(2) comply with specific privacy protections identified in section 124n(e), which include compliance with the First and Fourth Amendments to the Constitution of the United States, data retention limitations, and limits on collecting certain data; and</P>
                    <P>(3) comply with Federal oversight, audits, coordination, and compliance requirements, including by the Secretary of Homeland Security and Attorney General, in coordination with the Secretary of Transportation and the Administrator of the FAA, over SLTT agencies' compliance with the privacy protections identified in section 124n(e) and the requirements outlined in this regulation consistent with sections 8602, 8605, and 8606 of the SAFER SKIES Act.</P>
                    <HD SOURCE="HD3">2. Disrupting, Disabling, Interfering, Seizing Control, or Using Reasonable Force Under the Totality of the Circumstances To Disable, Damage, or Destroy</HD>
                    <P>Regarding the protective measures identified in section 124n(b)(1)(C), (D), and (F)—that is, mitigation measures generally involving disruption, seizure and control, and destruction using reasonable force—SLTT agencies are only authorized to use these protective measures under a more restrictive set of conditions. Specifically, in order to use the protective measures identified in section 124n(b)(1)(C), (D), and (F), SLTT agencies must:</P>
                    <P>(1) be trained and certified by the Attorney General, or the Attorney General's designee, in coordination with the Secretary of Homeland Security, through a national schoolhouse, 6 U.S.C. 124n(d)(2)(A)(i);</P>
                    <P>(2) use technologies that are included on a list of authorized technologies and systems maintained jointly by DOJ, DHS, the Department of Defense, the Department of Transportation, the FCC, and the NTIA, 6 U.S.C. 124n(d)(2)(A)(iii);</P>
                    <P>(3) comply with specific privacy protections identified in section 124n(e), which include compliance with the First and Fourth Amendments of the Constitution of the United States, data retention limitations, and limits on collecting certain data, and with Federal oversight, audits, coordination, and compliance requirements, including by the Secretary of Homeland Security and the Attorney General, in coordination with the Secretary of Transportation and the Administrator of the FAA, as concerning compliance with the privacy protections identified in section 124n(e), 6 U.S.C. 124n(d)(2)(B); and</P>
                    <P>(4) notify DHS and DOJ within 48 hours of any mitigation action taken, 6 U.S.C. 124n(d)(2)(C).</P>
                    <P>
                        The Act also provides for suspension of C-UAS authority and civil fines for SLTT agencies, as well as their personnel, authorized to take C-UAS protective measures who knowingly engage in such action without Federal coordination as required by the Act. Public Law 119-60, sec. 8605(f), 139 Stat. at 1944 (codified at 6 U.S.C. 124n-1(f)) (“Penalties for Unauthorized Counter-UAS Actions”); 
                        <E T="03">id.</E>
                         sec. 8605(g) (codified at 6 U.S.C. 124n-1(g)) (“Civil Enforcement”).
                    </P>
                    <P>The Act also requires the “Attorney General, in coordination with the Secretary of Homeland Security, the Secretary of Defense, and the Secretary of Transportation,” to develop training and certification procedures that SLTT law enforcement and correctional officers must satisfy before engaging in those protective measures requiring training and certification. 6 U.S.C. 124n(d)(2)(A)(ii) (training and certification procedures).</P>
                    <P>
                        Finally, the Act directs the “Secretary of Homeland Security and the Attorney General, in coordination with the Secretary of Defense and Secretary of Transportation,” and the Administrator of the FAA to publish regulations governing C-UAS authority for SLTT agencies under section 124n. 
                        <E T="03">See</E>
                         Public Law 119-60, sec. 8606, 139 Stat. 1944-45. This IFR implements the statutory directive to promulgate regulations, to include additional compliance requirements and procedures based on such coordination.
                    </P>
                    <HD SOURCE="HD2">B. Discussion of Interim Rule</HD>
                    <P>
                        This IFR identifies the requirements and procedures for SLTT agencies to become authorized to take C-UAS measures under section 124n. Specifically, for the full range of C-UAS protective measures identified under section 124n(b)(1)(A) and (B) (involving detecting, identifying, monitoring, and tracking UAS, and warning the operator), the mitigation measures under section 124n(b)(1)(C), (D), and (F), and (E) (involving seizure and confiscation of UAS or unmanned 
                        <PRTPAGE P="41469"/>
                        aircraft), the IFR identifies how SLTT agencies must (1) use only systems or technologies that are included on a list of authorized technologies, and how to obtain the list; and (2) comply with specific privacy protections identified in section 124n(e) and how they must comply with Federal oversight, audits, coordination, and compliance requirements by the Secretary of Homeland Security and Attorney General as outlined in this rule, consistent with sections 8602, 8605, and 8606 of the SAFER SKIES Act.
                    </P>
                    <P>Concerning C-UAS protective measures identified under section 124n(b)(1)(C), (D), and (F) (generally involving mitigation—that is, disrupting, disabling, interfering with, seizing control of, or using reasonable force, if necessary, to disable, damage or destroy a UAS), the IFR sets forth the requirements for the use of such measures. Specifically, the IFR explains how SLTT agencies: (1) receive training and certification through the Federal Bureau of Investigation's (“FBI”) national schoolhouse; (2) obtain the list of authorized technologies they may use; (3) comply with the specific privacy protections identified in section 124n(e); and (4) comply with Federal oversight, audits, and compliance requirements established by the Secretary of Homeland Security and the Attorney General, in coordination with the Administrator of the FAA, as outlined in this regulation and as provided in 6 U.S.C. 124n(d)(2)(B), with suspension of authority under sections 8605 and 8606(f) of the SAFER SKIES Act available to the Attorney General or the Secretary.</P>
                    <P>The rule is organized as follows in parts 124 of titles 6 and 28 of the Code of Federal Regulations: purpose and scope (§ 124.1); definitions (§ 124.2); scope of authority and mitigation standards (§ 124.3); authorized personnel, contractors, and mutual aid (§ 124.4); training and certification (§ 124.5); the agency implementation policy (§ 124.6); authorized technologies (§ 124.7); the C-UAS Operations Plan (§ 124.8); advance coordination, notification, and authorization (§ 124.9); interagency and lead-agency coordination (§ 124.10); real-time air traffic control notification (§ 124.11); detection and warning operations (§ 124.12); post-operation reporting (§ 124.13); privacy and civil liberties (§ 124.14); protection of sensitive operational information (§ 124.15); compliance and enforcement (§ 124.16); confiscation and forfeiture (§ 124.17); activities for evaluation, testing, training, and pre-operational validation (§ 124.18); task force arrangements and Federal support (§ 124.19); rules of construction (§ 124.20); termination (§ 124.21); and severability (§ 124.22).</P>
                    <P>This rule establishes the framework governing SLTT agency C-UAS operations under 6 U.S.C. 124n(a)(2). This rule provides requirements for training and certification of SLTT agency personnel, the agency implementation policy, the C-UAS Operations Plan, advance coordination, interagency and lead-agency coordination, notification and reporting requirements, and privacy and data handling protections. The Secretary of Transportation and the Administrator of the FAA have coordinated in the development of this rule as required by 6 U.S.C. 124n(d)(3), and the rule was developed in coordination with the Secretary of Defense as required by 6 U.S.C. 124n(d)(2)(A)(ii) and section 8606(a)(1) of the SAFER SKIES Act.</P>
                    <P>
                        Consistent with the SAFER SKIES Act, the rule does not change the applicability of the Communications Act, 
                        <E T="03">see</E>
                         47 U.S.C. 301 
                        <E T="03">et seq.,</E>
                         or implementing rules administered by the FCC that relate to spectrum licensing, equipment authorization, and harmful interference to authorized services, among other things. SLTT agencies thus remain subject to applicable provisions that may govern or proscribe activities otherwise authorized by this rule.
                    </P>
                    <P>The following discussion describes each provision of the regulatory text added by this rule to new parts 124 in both titles 6 and 28 of the Code of Federal Regulations. The two parts are identical.</P>
                    <P>
                        <E T="03">Section 124.1—Purpose and scope.</E>
                         This section states the purpose and scope of the new part 124 and its relationship to other laws, including the statutory provisions displaced by the notwithstanding clause of 6 U.S.C. 124n(a)(2), provides that this part is the comprehensive framework for SLTT agency C-UAS operations, and identifies for SLTT agencies that conduct only detection and warning operations the provisions of the part principally applicable to them. As used in this rule, the term “notwithstanding clause of 6 U.S.C. 124n(a)(2)” means the provision that permits a certified agency to take the actions described in 6 U.S.C. 124n(b)(1) without violating the Federal criminal laws the clause displaces—49 U.S.C. 46502 (aircraft piracy), 18 U.S.C. 32 (destruction of aircraft), 18 U.S.C. 1030 (computer fraud), 18 U.S.C. 1367 (interference with the operation of a satellite), and chapters 119 (interception of communications) and 206 (pen registers and trap and trace devices) of title 18—as well as “the laws of any particular State, local, Tribal, or territorial jurisdiction.” In plain terms, protective measures described in 124n, such as intercepting the radio link that controls a drone or taking control of a drone away from its operator, are lawful—notwithstanding the laws mentioned above—when a certified SLTT agency performs them in compliance with the Act and the regulations this IFR adopts.
                    </P>
                    <P>For an agency that conducts only detection and warning operations, the provisions principally applicable are those identified in § 124.1(b): the Detection and Warning Certification requirement of § 124.5(c), the detection and warning policy provisions of § 124.6(g), the authorized technology requirements of § 124.7, the C-UAS Operations Plan requirement of § 124.8, the operational conditions of § 124.12, and the privacy and data handling requirements of § 124.14. The authority to regulate detection and monitoring activity conducted in reliance on the Act rests on the statute itself: the opening text of 6 U.S.C. 124n(a)(2) conditions any action on completion of the training detailed in subsection (d)(2); 6 U.S.C. 124n(d)(2)(A)(ii) requires training and certification before personnel take any action described in subsection (b)(1), including detection; 6 U.S.C. 124n(d)(2)(A)(iii) limits the technologies used for any such action to listed technologies; 6 U.S.C. 124n(e) imposes privacy requirements; and section 8606(a)(1) of the SAFER SKIES Act directs publication of regulations governing the authority.</P>
                    <P>This section also clarifies that the Departments maintain parallel regulations for ease of use, and that each Department administers and interprets its own regulations with respect to its programs and authorities.</P>
                    <P>
                        <E T="03">Section 124.2—Definitions.</E>
                         This section defines the terms used in the part, including the two-list technology framework (the Authorized Technologies List and the Authorized Systems List), the two certification tiers (Detection and Warning Certification and Mitigation Certification), the data categories the part regulates (control communications, raw sensor data, and pattern data), the credible threat standard, the Agency Approving Official, and the designated Federal C-UAS coordination portal.
                    </P>
                    <P>
                        Two definitions reflect policy choices that warrant explanation. First, the Agency Approving Official must hold a rank not below a Senior Executive or Senior Official, or its equivalent. The Departments set the threshold at this level because approving a mitigation operation, which may involve the use of force against an aircraft, is a command 
                        <PRTPAGE P="41470"/>
                        decision that in most agencies rests above the line-supervisor level. The same senior official also approves the agency's detection and warning operations, so that authorization of all C-UAS operations under this part rests with one accountable command official. The reference is to the agency's senior command or executive ranks, not to any particular title, and where no equivalent rank exists the agency head or the agency head's designee may serve. Second, the credible threat standard governs agency action on a credible threat to the protected interests the statute enumerates, but the statute does not define the term. The rule's definition adapts the objective, totality-of-the-circumstances standard applied in Federal C-UAS operations under 6 U.S.C. 124n(a)(1) since 2018, reflected in the Attorney General's April 2020 Guidance 
                        <SU>3</SU>
                        <FTREF/>
                         and the DOJ objective standards for C-UAS operations,
                        <SU>4</SU>
                        <FTREF/>
                         and is framed on the reasonable-officer model familiar from use-of-force doctrine, with enumerated indicators drawn from Federal operational experience.
                    </P>
                    <FTNT>
                        <P>
                            <SU>3</SU>
                             Memorandum from the Attorney General, 
                            <E T="03">Guidance Regarding Department Activities to Protect Certain Facilities or Assets from Unmanned Aircraft and Unmanned Aircraft Systems</E>
                             (Apr. 13, 2020), 
                            <E T="03">https://www.justice.gov/archives/ag/page/file/1268401/dl?inline.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>4</SU>
                             
                            <E T="03">See id.</E>
                             at 5.
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Section 124.3—Scope of authority and mitigation standards.</E>
                         This section states the scope of authority, the credible threat determination, proportionality in the reasonableness of the use of force, the protective purpose limitation, the mitigation operator execution requirement, the independent professional judgment of the certified operator under the totality of the circumstances, and the airspace awareness function.
                    </P>
                    <P>The credible threat determination requirement implements the statutory condition of 6 U.S.C. 124n(a)(2) and requires that the determination be made and documented before mitigation. The proportionality standard requires that a mitigation action taken be reasonable in relation to the threat presented; it reflects the statute's authorization of actions that are necessary to mitigate the threat and the reasonable force limitation of 6 U.S.C. 124n(b)(1)(F). The protective purpose limitation confines the exercise of the authority to protective ends and forecloses use of the authority as a general investigative tool, consistent with the structure of 6 U.S.C. 124n(e). The mitigation operator execution requirement provides that only personnel holding Mitigation Certification may execute mitigation actions, implementing 6 U.S.C. 124n(d)(2)(A)(i). The independent professional judgment provision preserves the certified operator's discretion to decline an action the operator assesses to be unsafe, a safeguard the Departments adopted from Federal C-UAS practice because the operator of the system has the best real-time awareness of airspace and spectrum conditions. The airspace awareness function requires the operating agency to maintain awareness of manned aircraft in the vicinity of an operation, implementing the aviation safety coordination obligations of 6 U.S.C. 124n(b)(4) and (d)(3).</P>
                    <P>
                        <E T="03">Section 124.4—Authorized personnel, contractors, and mutual aid.</E>
                         This section limits the exercise of authority to officers and employees of the SLTT agency, prohibits contractor operation of systems requiring the authority of the Act, establishes the conditions for mutual aid, and contains an anti-circumvention provision.
                    </P>
                    <P>The limitation of operational authority to officers and employees implements the Act rather than a discretionary policy choice. Congress defined the personnel who may exercise SLTT agency authority as the officers and employees of the SLTT agency, 6 U.S.C. 124n(l)(6)(B), in contrast to the broader personnel definition applicable to Federal operations under 6 U.S.C. 124n(l)(6)(A), which extends to certain contractors, detailed personnel, and deputized personnel. The prohibition on contractor operation of mitigation systems, including arrangements described as turnkey or managed C-UAS services, follows from that statutory structure. The rule preserves substantial roles for the private sector: contractors and vendors may design, manufacture, sell, install, and maintain C-UAS systems; provide technical support and system-level operator training; receive operational data for diagnostics under the conditions of § 124.14(j); and provide detection services using systems that do not require the authority of the Act or the relief it provides from certain laws.</P>
                    <P>Section 124.4 also permits accredited SLTT agencies to provide C-UAS support to non-accredited SLTT agencies through mutual aid or other written arrangement. This approach reflects the Departments' judgment that public safety is better served by strong regional, county, statewide, and multi-jurisdictional C-UAS programs than by requiring every small or resource-limited agency to establish a separate, rarely used capability. The rule therefore allows a non-accredited agency to request and receive C-UAS support, while ensuring that the accredited agency remains the C-UAS operating agency and that all actions requiring 6 U.S.C. 124n authority are performed by properly certified personnel under the requirements of this part. The Departments invite comment on these provisions, including the conditions governing mutual aid.</P>
                    <P>
                        <E T="03">Section 124.5—Training and certification.</E>
                         This section establishes the training and certification structure required by 6 U.S.C. 124n(d)(2)(A). It implements the statute's two distinct requirements. The national-schoolhouse sole-certifying-authority requirement of 6 U.S.C. 124n(d)(2)(A)(i) applies to mitigation under 6 U.S.C. 124n(b)(1)(C), (D), and (F), and the FBI's National Counter-UAS Training Center (“NCUTC”) is designated as that schoolhouse. The Act separately requires training and certification before personnel take any of the actions it authorizes, including detection. The opening text of 6 U.S.C. 124n(a)(2) permits an agency to act only after completing the training detailed in subsection (d)(2), and 6 U.S.C. 124n(d)(2)(A)(ii) requires the Attorney General to develop training and certification procedures that officers must satisfy before taking any action described in subsection (b)(1). Detection and warning under 6 U.S.C. 124n(b)(1)(A), (B), and (E) are among the actions described in subsection (b)(1), so the training and certification requirement reaches them as well as mitigation. The Departments have accordingly provided for a Detection and Warning Certification requirement for detection and warning operations conducted with systems that require the authority of the Act or the relief it provides from certain laws, but the requirement that training and certification take place “through a national schoolhouse” in clause (i) does not extend to those actions. Thus, the NCUTC delivers the detection and warning curriculum through an online portal that issues the certification automatically on completion, rather than at an in-person resident instruction at the national schoolhouse. Detection activities conducted with systems that do not require the authority of the Act or the relief it provides from certain laws are outside this requirement. Examples of such activities include electro-optical and infrared cameras, acoustic sensors, and radar operated under FCC authorization. Operating those systems does not implicate the prohibitions the Act displaces, because they intercept no communications, so the Act's training requirement does not attach.
                        <PRTPAGE P="41471"/>
                    </P>
                    <P>Online delivery for the detection tier does not create the public safety risks that warrant resident instruction for mitigation. Detection and warning do not involve disrupting, taking control of, or otherwise affecting an aircraft in flight. Although some detection systems (such as radar) transmit radio frequency energy to sense an aircraft, such systems cannot interfere with an aircraft's operation, and the associated risks are legal and privacy compliance risks, which are knowledge-based and are effectively taught and tested through structured online instruction with a required detection assessment. Resident instruction for the detection tier would impose travel and backfill costs on thousands of agencies without a corresponding safety benefit and would consume schoolhouse capacity needed for mitigation training.</P>
                    <P>This section also establishes the correctional-specific curriculum and the decertification, suspension, administrative-review, and reinstatement process. Two choices in this section warrant further explanation.</P>
                    <P>
                        First, training and certification for mitigation occur through a national schoolhouse because Congress required it: 6 U.S.C. 124n(d)(2)(A)(i) conditions the exercise of the mitigation authorities—that is, authorities at 6 U.S.C. 124n(b)(1)(C), (D), and (F)—on certification through a national schoolhouse serving as the sole certifying authority. 
                        <E T="03">See</E>
                         6 U.S.C. 124n(d)(2)(A)(i).
                    </P>
                    <P>Second, the section provides for suspension of certifications and agency accreditations. Suspension is the measure section 8605(f)(2) of the SAFER SKIES Act provides, and the suspension and administrative review process is described in the discussion of the administrative review provisions below. Because the rule provides for suspension of certifications and agency accreditations, the Departments describe the process and its basis here. A suspension decision is communicated in writing and specifies the basis for the action and any available remedial steps. In exigent circumstances that pose a risk to aviation safety, public safety, or national security, the Director or the Director's designee may immediately suspend a certification or accreditation pending administrative review. An individual or agency that receives a suspension notice may request administrative review within 30 calendar days. The Attorney General, acting through the Director, designates a reviewing official from DOJ who did not participate in or supervise the initial decision; that official considers the written submissions of both parties, may hold an informal hearing, and issues a written determination within 60 calendar days stating the factual findings and the basis for the determination. The reviewing official may affirm, modify, condition, or reverse the action, and the determination is final agency action for purposes of this part. The rule contains no separate revocation action. A suspension that is affirmed and not cured remains in effect until reinstatement, and reinstatement of a Mitigation Certification requires completion of the full course. This process affords affected individuals and agencies notice and an opportunity to respond before a neutral reviewing official, while preserving the ability to act immediately when continued exercise of C-UAS authority would pose a safety or security risk.</P>
                    <P>The Departments are considering whether certifications should expire after a given period of time—such as 36 or 48 months—conditioned upon additional training requirements to ensure continuing proficiency and welcome comment on whether certifications should expire, the length of their validity period, and the requirements for renewal.</P>
                    <P>
                        <E T="03">Section 124.6—Agency implementation policy.</E>
                         This section establishes the agency implementation policy, the legal counsel review, the portal attestation, and the detection and warning policy for SLTT agencies conducting only detection and warning operations. An agency's implementation policy is not subject to pre-approval by the NCUTC; the agency self-certifies through a portal attestation, and the NCUTC retains audit and suspension authority. The implementation policy is the agency-level governing document for the agency's C-UAS program; it must address command responsibility, integration with the agency's use-of-force policy, operator rostering and certification verification, equipment control and maintenance, the privacy procedures required by § 124.14, and recordkeeping. The legal counsel review requires the agency's counsel to review the policy for compliance with this part and with applicable SLTT law before adoption. The portal attestation is the agency's certification, submitted through the Federal C-UAS coordination portal, that the policy has been adopted and reviewed. The detection and warning policy is an abbreviated policy, based on a model the Departments will publish, for agencies that conduct only detection and warning operations. The Departments chose self-certification with audit, rather than Federal pre-approval of each agency policy, for two reasons. Pre-approval of policies from the thousands of agencies expected to participate would create a Federal bottleneck, which would be inconsistent with the independent authority Congress conferred on certified SLTT agencies, and would add months of delay without a corresponding compliance benefit. Audit with suspension exposure, by contrast, preserves accountability: an agency that attests falsely or maintains a deficient policy is subject to the compliance audit program of § 124.16 and to suspension under § 124.5.
                    </P>
                    <P>The rule neither directly requires an SLTT agency to notify its State government of the agency's adoption of C-UAS capability or of individual operations, nor prohibits such notification, and nothing in the rule conditions the exercise of authority under 6 U.S.C. 124n(a)(2) on State-level notification, endorsement, or approval; Congress conferred that authority directly on SLTT agencies. The Departments recognize, however, that Governors, State homeland security advisors, and State law enforcement agencies have a legitimate interest in awareness of C-UAS capability within their States, including for purposes of intrastate and interstate deconfliction, mutual aid planning, and security planning for major events, and that the visibility provided through existing channels, such as the State Administrative Agency structure of DHS's C-UAS grant program, does not extend to agencies that participate without grant support through that program. The Departments have therefore included one reference to State notification requirements under § 124.9(b), if otherwise required by State law or policy, and invite comment on whether the rule should provide an additional State-level awareness mechanism and, if so, on its appropriate form, including whether the Federal Government should make available to a State-designated point of contact the roster of attested and accredited agencies within the State, or whether the agency implementation policy should address notification to a State-designated point of contact upon adoption of C-UAS capability, and on how any such mechanism should be structured so that notification does not operate as a condition on, or approval requirement for, the exercise of statutory authority.</P>
                    <P>
                        <E T="03">Section 124.7—Authorized technologies.</E>
                         This section establishes the two-list technology authorization framework and limits SLTT agency C-UAS operations to listed technology 
                        <PRTPAGE P="41472"/>
                        categories and, where the Authorized Systems List is populated, listed systems. It clarifies that the list requirement applies only to technologies the operation of which requires the legal relief provided by the notwithstanding clause of 6 U.S.C. 124n(a)(2). Under the two-list framework, the Authorized Technologies List identifies the categories of technology authorized for SLTT agency use, and the Authorized Systems List identifies specific systems within those categories. The Authorized Systems List is populated for a category when the interagency process has assessed and listed specific systems in that category. Until the Authorized Systems List is populated for a category, an agency is limited to the listed technology categories of the Authorized Technologies List, which is the limit 6 U.S.C. 124n(d)(2)(A)(iii) itself imposes; once the Authorized Systems List is populated for a category, the agency must use a listed system. SLTT agencies are therefore never free of the list requirement: category-level limits apply at all times, and system-level limits attach as listings are completed.
                    </P>
                    <P>The Departments adopted the two-list structure so that category-level policy is set through a deliberate interagency process while system-level additions can keep pace with a rapidly developing market. It clarifies that the list requirement applies only to technologies the operation of which requires the legal relief provided by the notwithstanding clause of 6 U.S.C. 124n(a)(2); technologies an agency may use lawfully without that relief, such as cameras, radar, and acoustic sensors, are not subject to the list requirement and remain available on the same basis as before the Act. Such technologies remain subject to existing laws and regulations, including FCC and equipment authorization requirements, FAA requirements, and SLTT law; the Act neither expands nor restricts their availability.</P>
                    <P>This section also requires an agency to cease use of a system or technology category upon an emergency suspension issued through the interagency process. The detailed mechanics of evaluating, listing, and maintaining technologies are established through the interagency process required by 6 U.S.C. 124n(d)(2)(A)(iii) and section 8606(a)(4) of the SAFER SKIES Act, in which agencies other than the Departments share responsibility, and are therefore not codified in this part. The Departments expect the initial Authorized Technologies List to include radio frequency (“RF”) detection with command-and-control signal interception, RF disruption (broadband and protocol-specific jamming), and RF protocol manipulation (command injection and cyber takeover), and expect the Authorized Systems List to be populated on a phased basis, drawing first on systems with existing Federal operational deployment and interagency coordination history under 10 U.S.C. 130i, 6 U.S.C. 124n, 10 U.S.C. 6227 (or its predecessor, 50 U.S.C. 2661), or 50 U.S.C. 3515a, that have been assessed and authorized for operational use by Federal agencies, and for which the FAA has completed an assessment of aviation safety risks and for which any necessary aviation safety mitigations the using agency or the FAA would need to implement have been identified as operational constraints. Each RF-emitting system listed on the Authorized Systems List will have completed a system-level spectrum evaluation through the interagency process before listing. Accredited agencies would submit nominations for the Authorized Systems List, and feedback regarding systems on the list, via an internal process announced via the Federal C-UAS coordination portal, which houses the list. The Departments expect to coordinate a 60-day sprint to consider any necessary revisions to the list following publication of this rule.</P>
                    <P>
                        <E T="03">Section 124.8—C-UAS Operations Plan.</E>
                         This section establishes the C-UAS Operations Plan, signed by the Agency Approving Official and supported by a legal counsel certification, as the instrument authorizing each detection or mitigation operation, or each combined detection and mitigation operation, on behalf of the SLTT agency. The plan must be prepared on a standardized form prescribed by the Attorney General, appropriately coordinated and deconflicted in accordance with §§ 124.9, 124.10, and 124.11, and establishes the 30-day operational window, the 365-day standing window for fixed-site persistent protection, and the renewal process. The Departments chose these requirements based on the experience of the FBI and the DHS C-UAS programs since 2018.
                    </P>
                    <P>The C-UAS Operations Plan serves three functions: it documents the Agency Approving Official's authorization of mitigation for a defined location and period, it records the legal counsel certification that the planned operation complies with this part and applicable law, and it supplies, in a standardized format, the data elements the Federal coordination process requires. The form is standardized and prescribed by the Attorney General so that every plan carries the same data elements, which permits automated routing through the coordination portal and consistent FAA airspace review; the Federal C-UAS programs' experience since 2018 is that nonstandard submissions are the principal source of coordination delay. The 30-day operational window keeps the threat assessment, airspace picture, and coordination data underlying a plan current, while the 365-day standing window for fixed-site persistent protection, paired with the recurring reviews required elsewhere in this part, avoids requiring a correctional facility or other fixed site to resubmit an unchanged plan every month. Renewal is by updated submission rather than automatic extension so that each operational period rests on a current authorization.</P>
                    <P>
                        <E T="03">Section 124.9—Advance coordination, notification, and authorization.</E>
                         This section establishes the advance coordination and notification process, conducted through a single submission to the designated Federal C-UAS coordination portal, operated by the FBI, that routes the relevant data elements to the FBI and DHS for deconfliction, to the FAA for airspace safety coordination, and to the FCC for spectrum coordination. Consistent with 6 U.S.C. 124n, the airspace process is one of coordination, not approval; however, an SLTT agency may only conduct C-UAS operations once the C-UAS Operations Plan is approved under § 124.8. As to the FCC, however, the process is one of coordination and authorization not mere coordination. Because 6 U.S.C. 124n does not displace 47 U.S.C. 301, an SLTT law enforcement or correctional agency must obtain the authorization it needs from the FCC before operating a C-UAS system that emits radio waves (such as certain radar systems), and FCC coordination alone does not suffice. The Departments and the FCC will work to establish standing or categorical authorizations and a vendor equipment authorization pathway that reduce the need for per-operation FCC approval, and the Departments intend to pursue these mechanisms as a priority following publication of this rule. In the interim, an SLTT law enforcement or correctional agency may operate equipment on the Authorized Technologies List under existing FCC authorizations and waivers, and the FCC may issue expedited waivers under its Part 2 authority, including 47 CFR 2.1204, for equipment already in use and for equipment needed to address a newly identified or evolving threat. The Departments chose these requirements 
                        <PRTPAGE P="41473"/>
                        based on the experience of the FBI and the DHS C-UAS programs since 2018.
                    </P>
                    <P>Advance coordination is the process by which an agency, before commencing a mitigation operation or an operation employing an RF-emitting system, submits the operation's data elements for Federal deconfliction. Notification is the corresponding transmission of those elements to the affected Federal entities. The single-submission design is the central policy choice: the SLTT agency files once, through the Federal C-UAS coordination portal, and the portal routes the relevant elements to the FBI for operational deconfliction, to the FAA for airspace safety coordination, and to the FCC for spectrum coordination. The alternative, separate filings with each Federal entity, would multiply the burden on SLTT agencies, produce inconsistent records, and recreate the sequential processing delays the Federal programs experienced before consolidated coordination mechanisms were adopted.</P>
                    <P>This section also requires the SLTT agency to submit a comparable advance notification to the State if required by State law or policy. This notification does not operate as a condition on, or approval requirement for, the exercise of statutory authority. The Departments welcome comment on this provision, including whether it is more appropriately included as part of the State implementation policy.</P>
                    <P>
                        <E T="03">Section 124.10—Interagency and lead-agency coordination.</E>
                         This section establishes interagency and lead-agency coordination, including early coordination and the notice of intent for nationally significant events, tactical coordination under a designated lead C-UAS agency, the requirement that an agency that does not accept tactical coordination cannot conduct C-UAS operations within the area and period covered by the lead-agency designation, coordination of overlapping SLTT operations, and deconfliction direction when a conflict with a Federal operation cannot otherwise be resolved. Early coordination is advance engagement with the FBI and the designated lead C-UAS agency for an event significant enough to draw multiple C-UAS operators, and the notice of intent is the submission through which an agency states its intent to operate at a nationally significant event so that protective planning can integrate it. Tactical coordination under a designated lead C-UAS SLTT agency places participating SLTT agencies' C-UAS activity under a single, integrated operational picture for the event; the requirement that an agency declining tactical coordination refrain from operating within the covered area and period, and the reasons that requirement is consistent with the independent statutory authority Congress conferred on certified SLTT agencies, are discussed in the following paragraph. Coordination of overlapping SLTT operations addresses adjacent or concurrent operations by multiple agencies outside designated events, and deconfliction direction is the limited mechanism for resolving a conflict between an SLTT agency operation and a Federal operation when coordination fails. Each element responds to the same operational fact, demonstrated repeatedly in Federal C-UAS operations since 2018: simultaneous uncoordinated C-UAS activity is mutually interfering, because RF systems interact and multiple operators may act against the same aircraft.
                    </P>
                    <P>Paragraph (d) of § 124.10 requires an SLTT agency that does not accept tactical coordination by a designated lead C-UAS agency to refrain from conducting C-UAS operations within the geographic area and time period covered by the designation. The Departments considered whether that requirement is consistent with the independent character of the authority Congress provided to certified SLTT agencies in 6 U.S.C. 124n(a)(2) and have concluded that it is. The Act assigns the Secretary of Homeland Security and Attorney General responsibility for developing regulations and guidance governing SLTT agency C-UAS operations, 6 U.S.C. 124n(d)(1); section 8606(a)(1) of the Act, and the Attorney General for oversight of the exercise of the authority, 6 U.S.C. 124n(d)(2)(B). The Act also requires coordination with the Administrator of the FAA on matters that might affect aviation safety, civil aviation and aerospace operations, aircraft airworthiness, or the use of airspace. 6 U.S.C. 124n(b)(4) and (d)(3). Uncoordinated simultaneous C-UAS operations, even at a single event, present unacceptable risks: RF mitigation systems can interfere with one another and with protective communications, multiple agencies may attempt conflicting mitigation actions against the same aircraft, and aviation safety coordination assumes a single integrated operational picture. The requirement is limited in three respects: it applies only within the geographic area and time period of a designated lead-agency event; it does not transfer the SLTT agency's statutory authority, including the authority to make credible threat determinations; and it preserves the emergency exception for an imminent risk to human life. Outside designated events, an SLTT agency's C-UAS operations are subject only to the coordination processes of §§ 124.9, 124.10(e). The Departments invite comment on this approach.</P>
                    <P>
                        <E T="03">Section 124.11—Real-time air traffic control notification.</E>
                         This section establishes the requirement of real-time notification to air traffic control upon activation of any C-UAS system for mitigation action. The requirement protects aviation safety. Activation of an RF-emitting mitigation system can affect aircraft operating near the protected area, by interfering with their communications systems, so real-time notification allows the FAA and air traffic control to account for the mitigation action, issue advisories, and deconflict other aircraft while the system is active. A mitigation action that does not emit radio frequency energy can likewise affect the airspace near the protected area, for example by bringing an unmanned aircraft down or creating falling debris, so the same real-time air traffic awareness is warranted whether or not the system emits radio frequency energy. The Departments set the timing at five minutes or as soon as operationally practicable, rather than a fixed advance-notice requirement, because mitigation against a credible threat is time-sensitive and often cannot be predicted far enough in advance to permit prior notice; the standard requires notification at the earliest point that does not compromise the protective action. Notification is routed through a single FAA notification point and follows procedures jointly established by DHS, DOJ, and the FAA, rather than procedures fixed in this part, so that the operational mechanics can be adjusted as the air traffic procedures develop without amending this rule. The SLTT agency must also provide a follow-up notification confirming the time the mitigation action terminates. Real-time notification under this section is distinct from the advance airspace and spectrum coordination required for a planned operation under §§ 124.8 and 124.9; this section addresses the air traffic awareness that a mitigation action requires in real time. Paragraph (d) accordingly confirms that mitigation actions that do not employ RF-emitting systems also require notification under this section, unless the applicable Department of Transportation or FAA notification procedures provide otherwise.
                    </P>
                    <P>
                        <E T="03">Section 124.12—Detection and warning operations.</E>
                         This section establishes the conditions for detection and warning operations using systems that require the authority of the Act or the relief it provides from certain laws, 
                        <PRTPAGE P="41474"/>
                        which do not require per-operation coordination when no RF-emitting system is employed, and prohibits any mitigation action by personnel holding only a Detection and Warning Certification.
                    </P>
                    <P>The Departments recognize that some SLTT agencies have, before the effective date of this rule, deployed UAS detection systems, including systems that do not require the authority and relief provided by the SAFER SKIES Act. This rule governs operations conducted under 6 U.S.C. 124n(a)(2) on and after the rule's effective date; it does not adjudicate the lawfulness of detection activity conducted before the effective date or under legal authorities other than the Act, and nothing in this rule should be read as a determination that any particular past deployment was or was not lawful. Prospectively, an SLTT agency that intends to operate a detection system, the operation of which requires the authority of the Act or the relief it provides from certain laws must satisfy the conditions of § 124.12, including the Detection and Warning Certification, Operations Plan, and the detection-and-warning policy or implementation policy.</P>
                    <P>The Departments have structured these requirements to minimize disruption to existing protective postures: the detection and warning curriculum is delivered online at no cost through the NCUTC training portal, and certification issues automatically upon completion, the detection-and-warning policy is adopted on the SLTT agency's own attestation without pre-approval, and no per-operation coordination is required for passive non-emitting systems (systems that do not actively transmit RF energy). However, systems that involve radio frequency emissions must be evaluated for compliance with the laws and regulations administered by the FCC.</P>
                    <P>These choices balance the competing concerns directly. Safety is preserved because every operator of a system requiring the Act's authority or relief from criminal liability completes the required curriculum and assessment before operating, and because the certification database gives the Federal Government visibility into who is operating. Privacy is preserved because the privacy protections of § 124.14, including minimization and the retention limit, apply in full to detection operations after the effective date of this rule. Efficiency and cost are addressed by online delivery at no tuition cost, automatic certification, attestation without pre-approval, and the absence of per-operation coordination for passive systems, which together allow an SLTT agency already operating detection equipment to come into compliance in days at the cost of approximately one hour of operator time.</P>
                    <P>
                        <E T="03">Section 124.13—Post-operation reporting.</E>
                         This section establishes a reporting requirement within 48 hours after a mitigation action is taken; the content of the report; consolidated, recurring-venue, and persistent-protection reporting; a semiannual operational summary; and the elements compiled to support the biannual congressional report required by 6 U.S.C. 124n(d)(2)(D), including critical-infrastructure protection requests and the requests an agency was unable to support.
                    </P>
                    <P>The 48-hour reporting requirements and the content elements of the report implement 6 U.S.C. 124n(d)(2)(C)(i), which requires a notification to the Attorney General and the Secretary of Homeland Security “within 48 hours of any mitigation action described in [6 U.S.C. 124n](b)(1)” containing the date, time, and geographic location of the action, a description of the credible threat or safety concern, the type of mitigation capability employed, and any known operational effects. The submission mechanism implements 6 U.S.C. 124n(d)(2)(C)(ii), which directs the Attorney General and the Secretary of Homeland Security to establish a streamlined and secure mechanism for those notifications. Consolidated, recurring-venue, and persistent-protection reporting are burden-reduction formats the Departments adopted for agencies that conduct repeated operations at the same venue or maintain standing fixed-site protection; they preserve every statutory data element while avoiding duplicative per-event filings. The semiannual operational summary and the compiled reporting elements support the report the Attorney General must submit to Congress under 6 U.S.C. 124n(d)(2)(D), including the deployment frequency, location, and circumstance data and the critical-infrastructure protection determination that subparagraph requires.</P>
                    <P>
                        <E T="03">Section 124.14—Privacy and civil liberties.</E>
                         This section implements the privacy protections of 6 U.S.C. 124n(e), addressing the First Amendment limitation, the scope of interception and incidental capture, data collection minimization and periodic review, the 180-day retention limit for records of communications and its statutory exceptions, the treatment of State and local retention requirements, the bases for dissemination of control communications, the dissemination of pattern data, the protective purpose limitation, the prohibition on acquiring unlawfully intercepted control communications from third parties, and the audit trail.
                    </P>
                    <P>Each element implements 6 U.S.C. 124n(e). The First Amendment limitation restates the statutory prohibition on exercising the authority solely to monitor protected activity. The interception and incidental capture provisions define the scope of permissible acquisition of control communications and the handling of communications acquired incidentally. Minimization and periodic review require procedures limiting acquisition, retention, and use to what the protective purpose requires. The 180-day retention limit and its exceptions implement the statutory limit on retaining intercepted communications, and the SLTT agency retention provision addresses the interaction of that Federal limit with SLTT records laws. The dissemination provisions implement the statutory bases on which intercepted communications may be shared, and the pattern data provisions govern derived products. The protective purpose limitation confines use of acquired communications to the protective, law enforcement, and aviation safety purposes related to the UAS activity. The third-party acquisition prohibition forecloses obtaining from a vendor or other third party what the agency could not lawfully intercept itself, and the audit trail creates the record on which the compliance audit program and the Attorney General's oversight under 6 U.S.C. 124n(d)(2)(B) operate.</P>
                    <P>
                        In calibrating these protections, the Departments made several judgments on which they specifically invite comment. First, the rule construes the statutory retention exceptions narrowly: an ongoing security operation justifies continued retention only where a specific, identified threat supports a discrete protective objective, and a standing operational window does not by itself qualify. Second, for standing detection deployments, the rule pairs the narrowest-technical-configuration requirement with a recurring minimization review, conducted not less than quarterly, to address the heightened incidental capture risk of persistent collection. Third, the rule requires that pattern data satisfy written anonymization standards adopted in the agency's implementation policy and verified before dissemination outside the agency, rather than prescribing a single national anonymization standard, because aggregation thresholds and re-identification risks vary substantially with jurisdiction size, population 
                        <PRTPAGE P="41475"/>
                        density, and event frequency; the adequacy of agency standards is subject to the compliance audit program of § 124.16. The Departments invite comment on the operation of the retention exceptions and their documentation requirements, on whether the rule should prescribe minimum Federal anonymization standards for pattern data, on the conditions governing real-time detection feeds, and on whether additional safeguards are warranted for incidental capture during standing deployments.
                    </P>
                    <P>
                        <E T="03">Section 124.15—Protection of sensitive operational information.</E>
                         This section requires the protection of sensitive operational information associated with planned or completed operations as well as protection of sensitive Federal and operational information. The protected information includes C-UAS Operations Plans, advance coordination submissions, system capabilities, locations, and coverage patterns, and the tactical procedures associated with planned or completed operations. The section requires agencies to handle that information under access controls and to protect it from public disclosure to the extent permitted by applicable Federal, State, local, Tribal, and territorial law. The section uses a two-tier approach. Information that ties specific system capabilities, vulnerabilities, or countermeasure effectiveness to a planned or completed operation is handled as law enforcement sensitive and evaluated for classification where it reveals a capability gap of national security concern; general operational coordination information, such as the existence, general timing, or general coverage area of a deployment, is handled as Controlled Unclassified Information so that it can be shared with covered partners, including a State-designated aviation point of contact, without the added handling a law enforcement sensitive caveat would impose. The Departments chose these protections because disclosure of coverage patterns, system locations, or capability details enables a hostile operator to circumvent protection, and the operational record of the Federal C-UAS programs shows that adversaries probe for exactly that information.
                    </P>
                    <P>
                        <E T="03">Section 124.16—Compliance and enforcement.</E>
                         This section establishes the compliance audit program contemplated by section 8606(b)(2) of the SAFER SKIES Act and addresses the civil penalties and civil enforcement that sections 8605(f) and (g) of the Act establish, including their relationship to suspension. The civil penalties are established by the statute, not by this section; § 124.16 implements the statutory penalty scheme, as discussed together with the graduated penalty levels and assessment factors in the following paragraph. The compliance audit program gives an agency the means to demonstrate, and the Departments the means to verify, compliance with the requirements of this part before a violation occurs.
                    </P>
                    <P>With respect to civil penalties, section 8605(f) of the SAFER SKIES Act authorizes a civil fine of up to $100,000 per violation or suspension of C-UAS authority pending review by the Attorney General or the Secretary of Homeland Security. If a fine is not paid, section 8605(g) authorizes the Attorney General to bring a civil action in a United States district court to collect such fines and enforce civil penalties. The rule provides for graduated penalty levels proportionate to the severity of the violation and enumerates the factors that inform assessment, including the agency's compliance history, the availability and quality of compliance assistance from Federal partners, whether the violation resulted in actual harm, and whether the agency took prompt corrective action, and it provides that a first violation of a procedural reporting or notification requirement will not draw a penalty where the agency demonstrates a good-faith effort to comply and voluntarily self-reports. The Departments invite comment on the penalty framework, including the graduated structure, the enumerated factors, and the treatment of first-time procedural violations.</P>
                    <P>
                        <E T="03">Section 124.17—Confiscation and forfeiture.</E>
                         This section implements the confiscation authority of 6 U.S.C. 124n(b)(1)(E) and the forfeiture provision of 6 U.S.C. 124n(c)(2), addresses in-flight physical interception, and requires that the response to a suspected hazardous device delivered by an unmanned aircraft be conducted by a bomb squad accredited through the Hazardous Devices School. Confiscation under 6 U.S.C. 124n(b)(1)(E) is the seizure or other taking of possession of an unmanned aircraft or UAS consistent with the Act. Forfeiture under 6 U.S.C. 124n(c)(2) follows the law of the seizing agency's jurisdiction, as the statute directs, so the section does not create a Federal forfeiture process. The section also notes that an aircraft on the ground may be seized under traditional law enforcement authority—that is, ordinary seizure authority such as seizure incident to arrest or pursuant to a warrant or a recognized exception to the warrant requirement, without reliance on the Act. In-flight physical interception is addressed because catching or netting an aircraft in flight can implicate several of the statutory authorities at once and carries distinct safety risks; the section therefore directs that personnel conducting such actions hold Mitigation Certification. The bomb squad requirement reflects a deliberate policy choice: an unmanned aircraft that is a potential hazardous or destructive device is the domain of certified public safety bomb technicians, not a C-UAS problem, and render-safe response is a separate discipline with its own national certification structure. Requiring response by a bomb squad accredited through the Hazardous Devices School, consistent with the National Guidelines for Bomb Technicians, keeps that response within the established national framework rather than creating a parallel one.
                    </P>
                    <P>
                        <E T="03">Section 124.18—Activities for evaluation, testing, training, and pre-operational validation.</E>
                         This section establishes the conditions for operational testing, pre-operational function checks, on-the-job proficiency training, and pre-operational validation, which are conducted under FCC coordination and authorization and FAA coordination and notification. Testing is the evaluation of a system's function and effects before operational use; proficiency training is recurring operator practice; and pre-operational validation is the verification, before a planned operation, that a system performs as expected at the operating location. These activities are conducted under FCC coordination and authorization and FAA coordination and notification, rather than under the authority of the Act, because the Act's authority is conditioned on a credible threat and these activities, by definition, lack one. The Departments considered permitting testing under the Act's authority and rejected that approach as inconsistent with the statutory predicate; the established Federal mechanisms for experimental spectrum use and airspace safety coordination are the lawful and proven path, and they are the same mechanisms the Federal C-UAS programs use for their own testing.
                    </P>
                    <P>
                        <E T="03">Section 124.19—Task force arrangements and Federal support.</E>
                         This section preserves existing task force and deputization arrangements under 6 U.S.C. 124n(a)(1), provides that the availability of C-UAS authority through such task force and deputization arrangements neither requires accreditation under this part nor affects those arrangements, and establishes the framework for Federal C-UAS support upon SLTT agency request. The section preserves task force arrangements 
                        <PRTPAGE P="41476"/>
                        because 6 U.S.C. 124n(a)(1) authority and 6 U.S.C. 124n(a)(2) authority are separate authorities: an agency with officers who serve as deputized task force officers under Federal sponsorship may continue those arrangements without seeking accreditation under this part, and an accredited agency may still participate in Federal task forces. The Federal support framework establishes how an SLTT agency may request Federal C-UAS support, such as coverage of a threat beyond the agency's certified capabilities. The Departments adopted these provisions to avoid forcing a transition: agencies operating effectively under existing task force models, including those supporting major public events in 2026, should not lose that posture because a separate path now exists. An agency may also request FBI technical exploitation support for a seized UAS through its local FBI field office.
                    </P>
                    <P>
                        <E T="03">Section 124.20—Construction.</E>
                         This section sets out rules of construction, including that this part creates no enforceable right, does not authorize action against any aircraft operated with a human pilot, crew, or passengers onboard, and does not create a new basis of liability for officers participating in the protection of identified mass gatherings.
                    </P>
                    <P>
                        <E T="03">Section 124.21—Termination.</E>
                         This section implements the December 31, 2031, termination date of 6 U.S.C. 124n(j)(2) and provides that obligations and proceedings arising before termination survive it.
                    </P>
                    <P>
                        <E T="03">Section 124.22—Severability.</E>
                         This section is a severability provision. The provisions in this rule are not necessarily interrelated and can function independent of one another. As such, the Departments believe that most of the provisions of this IFR can function sensibly and independently of other provisions. Therefore, in the event that any provisions in this rule are invalidated by a reviewing court, the Departments intend the remaining provisions to remain in effect to the fullest extent possible.
                    </P>
                    <HD SOURCE="HD1">IV. Regulatory Certifications</HD>
                    <HD SOURCE="HD2">A. Administrative Procedure Act</HD>
                    <P>For the reasons described below, there is good cause for the Departments to forgo the APA's notice-and-comment procedures for this rule because following such procedures is impracticable. Additionally, the rule is not subject to the delayed-effective date requirement because it recognizes an exemption or relieves a restriction and because there is good cause for the rule to be immediately effective. Notwithstanding the explanation below, the Departments nonetheless welcome post-promulgation comment on all aspects of this IFR.</P>
                    <P>1. Good Cause To Forgo Notice and Comment</P>
                    <P>
                        The Administrative Procedure Act (“APA”) allows an agency to issue a rule without notice and comment “when the agency for good cause finds . . . that notice and public procedure thereon are impracticable, unnecessary, or contrary to the public interest.” 5 U.S.C. 553(b)(B). “[T]he good cause exception is to be narrowly construed and only reluctantly countenanced.” 
                        <E T="03">Mack Trucks, Inc.</E>
                         v. 
                        <E T="03">EPA,</E>
                         682 F.3d 87, 93 (D.C. Cir. 2012) (citation and quotation marks omitted). Courts apply “the good cause exception to excuse notice and comment in emergency situations, where delay could result in serious harm, or when the very announcement of a proposed rule itself could be expected to precipitate activity by affected parties that would harm the public welfare.” 
                        <E T="03">Am. Pub. Gas Ass'n</E>
                         v. 
                        <E T="03">Dep't of Energy</E>
                         (“
                        <E T="03">APGA</E>
                        ”), 72 F.4th 1324, 1340 (D.C. Cir. 2023) (cleaned up); 
                        <E T="03">see also California</E>
                         v. 
                        <E T="03">Azar,</E>
                         911 F.3d 558, 575 (9th Cir. 2018) (“[T]he good cause exception is usually invoked in emergencies . . . .”).
                    </P>
                    <P>
                        Following the notice-and-comment procedures for this rule is impracticable. Impracticability “is generally confined to emergency situations in which a rule would respond to an immediate threat to safety, such as to air travel, or when immediate implementation of a rule might directly impact public safety.” 
                        <E T="03">NRDC</E>
                         v. 
                        <E T="03">NHTSA,</E>
                         894 F.3d 95, 114 (2d Cir. 2018). For instance, it applies when “air travel security agencies would be unable to address threats posing a possible imminent hazard to aircraft, persons, and property within the United States,” 
                        <E T="03">Mack Trucks,</E>
                         682 F.3d at 93 (internal quotation marks omitted), “if a safety investigation shows that a new safety rule must be put in place immediately,” 
                        <E T="03">id.</E>
                         (internal quotation marks omitted), or when some other “similarly serious threats” exist, 
                        <E T="03">Mid Continent Nail Corp.</E>
                         v. 
                        <E T="03">United States,</E>
                         846 F.3d 1364, 1380 (Fed. Cir. 2017).
                    </P>
                    <P>
                        Those circumstances are present here. Recognizing the imminent threat that unmanned aircraft and UAS pose to public safety, Congress passed the SAFER SKIES Act to provide a framework for SLTT agencies to exercise C-UAS authority independently of Federal task forces and deputization, which limit SLTT agencies to C-UAS activities as part of Federal actions. 
                        <E T="03">See</E>
                         6 U.S.C. 124n(a)(2). Congress set a timetable for the Departments to promulgate regulations to govern that authority, with section 8606(a)(1) of the SAFER SKIES Act directing the Secretary of Homeland Security and the Attorney General to do so not later than 180 days after the date of enactment, and 6 U.S.C. 124n(d)(2)(A)(ii) separately requiring the Attorney General to develop the training and certification procedures within the same 180-day period. The Act was signed into law on December 18, 2025, placing the statutory deadline in mid-June 2026. Congress's compressed timetable reflects its own judgment about the urgency of the threat this authority addresses, and that deadline, coupled with the exigency that motivated it, supports the finding here. As explained below in this section, this rule is not only necessary to fulfill Congress's requirement that the Departments develop regulations and guidance, but it responds to immediate threats related to several high-profile events that are or may be the target of nefarious actors.
                    </P>
                    <P>
                        This rule responds to an immediate threat to safety because a growing number of irresponsible operators ignore flight restrictions and endanger the safety of the airspace and commercial aircraft as they approach airports. In addition, UAS pose an immediate and growing threat to public safety, security at prisons, and national security. For example, they can be used to conduct kinetic attacks using payloads of explosives. 
                        <E T="03">See, e.g., Belfair, Washington, man arrested by FBI in connection to planned attack on government officials at White House UFC event,</E>
                         DOJ (June 22, 2026), 
                        <E T="03">https://www.justice.gov/usao-wdwa/pr/belfair-washington-man-arrested-fbi-connection-planned-attack-government-officials</E>
                         [
                        <E T="03">https://perma.cc/L557-X9MS</E>
                        ] (conspirators planned to load explosives onto drones and attack the White House UFC event on one side in order to force attendees to exit where they could be shot with rifles and other weapons). UAS can also be weaponized with chemical, biological, or nuclear material, used to conduct espionage, and used to traffic in controlled substances and contraband cellphones in prisons. Dep't of Justice, 
                        <E T="03">Securing the Skies: Law Enforcement, Drones, and Public Safety: Hearing Before the S. Comm. on the Judiciary,</E>
                         119th Cong. 5 (2025). Furthermore, without this rule, and specifically the rule's requirement and mechanism to coordinate with the FAA, air travel security agencies will become “unable to address threats posing `a possible imminent hazard to aircraft.' ” 
                        <E T="03">Mack Trucks,</E>
                         682 F.3d at 93 (quoting 
                        <E T="03">Jifry</E>
                         v. 
                        <E T="03">FAA,</E>
                         370 F.3d 1174, 1179 (D.C. Cir. 2004)).
                        <PRTPAGE P="41477"/>
                    </P>
                    <P>
                        The protective need is concrete and increasingly urgent, and this rule provides necessary mechanisms to address that growing need. Prior to this IFR, deputized SLTT agency C-UAS personnel that were fully trained and certified could only be used in connection with a Federal operation or with Federal assistance—they could not engage in C-UAS actions on their own, including to protect their own jurisdictions, without Federal partnership. 
                        <E T="03">See</E>
                         6 U.S.C. 124n(a)(1). This rule allows the deputized C-UAS Task Force operators to conduct C-UAS operations to support the missions of their own SLTT agencies and protect their own “large-scale public gatherings or events, critical infrastructure, or correctional facilities.” 6 U.S.C. 124n(a)(2). Furthermore, each trained and certified C-UAS operator is a force multiplier: one Mitigation trained and certified SLTT C-UAS operator can activate an entire SLTT C-UAS team, with the remaining members completing the online requirements. And, critically, the rule provides a mechanism for SLTT agencies to both coordinate and to deconflict with the FAA, other agencies in the Federal Government, and with other SLTT agencies.
                    </P>
                    <P>The authority Congress provided in 6 U.S.C. 124n(a)(2) is conditioned on the training, technology, and oversight requirements in the statute. This rule implements those requirements by establishing a binding framework under which personnel must complete required training and certification, SLTT agencies must adopt implementation policies, and operators must employ authorized technologies and follow notification and coordination procedures. Without the rule's binding framework, certification of SLTT agency personnel to exercise authority under section 124n(a)(2) would at a minimum be substantially more challenging to monitor and regulate. Specifically, SLTT agencies were able to participate in C-UAS mitigation operations only through Federal task force arrangements under 6 U.S.C. 124n(a)(1), which require Federal sponsorship and individual deputization. Such arrangements could not scale to the public safety need or the volume of SLTT agency operations required to address the current threat level. Current task force arrangements permit SLTT agencies to operate alongside Federal agencies. Section 124n(a)(2) authority, however, would allow SLTT agencies to operate independently, which would drastically increase their capacity in all relevant jurisdictions.</P>
                    <P>
                        The framework this rule establishes can scale in a way the task force model cannot. At the detection tier, the NCUTC online curriculum and automatic certification can train and certify operators nationwide without resident throughput limits; the Departments expect approximately 1,500 agencies to certify at that tier within two years.
                        <SU>5</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>5</SU>
                             The Departments note that DOJ has issued a charging policy to encourage certain SLTT agencies with assigned duties that include the security or protection of people, facilities, or assets to engage in C-UAS detection operations (6 U.S.C. 124n(b)(1)(A)) while the Departments developed this rule in part to address the threat posed by unauthorized unmanned aircraft and UAS activity at the Fédération Internationale de Football Association (“FIFA”) World Cup
                            <SU>TM</SU>
                            . Acting Attorney General Blanche, 
                            <E T="03">Memorandum to all Federal Prosecutors, Charging Policy Concerning Defensive Actions Against Unmanned Aircraft Systems</E>
                             (June 12, 2026), 
                            <E T="03">https://www.justice.gov/olp/media/1450041/dl?inline.</E>
                             Although the charging policy shields SLTT agencies from chapters 119 and 206 of Title 18 (the Wiretap Act and the prohibition on pen register and trap and trace device use), it does not shield them from State, local, Tribal, or territorial law. In contrast, 6 U.S.C. 124n(a)(2) does shield SLTT agencies from State, local, Tribal, or territorial law, so long as they complete the training detailed in subsection (d)(2). 6 U.S.C. 124n(a)(2) (“notwithstanding the laws of any particular State, local, Tribal, or territorial jurisdiction, and after completing the training detailed in subsection (d)(2)”). As a result, this rule is necessary for SLTT agency detection operations.
                        </P>
                    </FTNT>
                    <P>
                        At the mitigation tier, the NCUTC has trained and certified the operators of approximately 46 agencies through its resident courses to date, is conducting additional classes on a continuing schedule, and is expanding the instructor cadre and course frequency to support broader SLTT agency enrollment beginning later in 2026. Although deputized SLTT agencies are critical to Federal operations, deputization is insufficient to address the public safety need, which necessarily increases as UAS technologies improve and become more widely accessible. Unmanned aircraft incursions over stadiums, mass gatherings, airports, critical infrastructure, and correctional facilities are documented and recurring, and they present a threat to public safety, and to the safety-of-flight of manned aircraft and lawfully operating UAS in the national airspace system; moreover, the prospect of weaponized drones also presents a threat to national security.
                        <SU>6</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>6</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Jordy Fee-Platt, 
                            <E T="03">Man charged with allegedly flying drone above Levi's Stadium during NFL game,</E>
                             The Athletic (Feb. 3, 2026), 
                            <E T="03">https://www.nytimes.com/athletic/7018723/2026/02/03/drone-operator-charged-levis-stadium/.</E>
                        </P>
                    </FTNT>
                    <P>
                        In addition, Federal C-UAS resources cannot be present at every site. Congress extended this authority to SLTT agencies precisely because Federal protective capacity is finite. The record is concrete. The National Football League's chief security officer told Congress in December 2024 that unauthorized drone incursions into the restricted airspace over NFL games grew from roughly a dozen in the 2017 season to 2,537 in 2022 and 2,845 in 2023.
                        <SU>7</SU>
                        <FTREF/>
                         Two of those incursions resulted in Federal felony charges announced by the United States Attorney for the District of Maryland: the January 28, 2024, drone flight over M&amp;T Bank Stadium that forced a temporary suspension of the American Football Conference Championship game, and a second flight over the same stadium during a January 11, 2025, playoff game. In December 2024, the United States Attorney for the Central District of California charged a Chinese national who flew a drone over Vandenberg Space Force Base for nearly an hour and photographed the installation after base detection systems tracked the flight. Drone delivery of contraband into correctional facilities is the subject of recurring Federal prosecutions,
                        <SU>8</SU>
                        <FTREF/>
                         including the August 2024 indictments of 23 defendants in the Southern District of Georgia for conspiracies that used drones to deliver methamphetamine, marijuana, and contraband cell phones into State prisons, and earlier prosecutions in the District of Kansas, the Eastern District of California, and the District of New Jersey involving drone deliveries of drugs, cell phones, and tobacco into Federal and State facilities.
                    </P>
                    <FTNT>
                        <P>
                            <SU>7</SU>
                             Statement of Cathy L. Lanier, Chief Security Officer, National Football League, before the House Committee on Homeland Security (Dec. 10, 2024), 
                            <E T="03">https://www.congress.gov/118/meeting/house/117754/witnesses/HHRG-118-HM05-Wstate-LanierC-20241210.pdf</E>
                             [
                            <E T="03">https://perma.cc/V8VQ-KN4J</E>
                            ].
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>8</SU>
                             
                            <E T="03">See, e.g., Twelve Indicted in Alleged Drone Smuggling Conspiracy at Ten Prisons,</E>
                             DOJ (June 24, 2026), 
                            <E T="03">https://www.justice.gov/usao-mdga/pr/twelve-indicted-alleged-drone-smuggling-conspiracy-ten-prisons</E>
                             [
                            <E T="03">https://perma.cc/U824-36YY</E>
                            ].
                        </P>
                    </FTNT>
                    <P>
                        The exposure is increasing rapidly: the Fédération Internationale de Football Association (“FIFA”) World Cup
                        <SU>TM</SU>
                        , the largest sporting event ever held in the United States, began June 11, 2026, and runs through July 19, 2026, across 11 United States host cities; and the Nation's semiquincentennial celebrations culminate on July 4, 2026, in mass gatherings nationwide.
                        <SU>9</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>9</SU>
                             
                            <E T="03">See</E>
                             Holmes Lybrand, 
                            <E T="03">Drones and lone wolf attacks are key concerns as FBI works to secure 11 World Cup cities,</E>
                             CNN (Jun. 13, 2026), 
                            <E T="03">https://www.cnn.com/2026/06/13/politics/drones-lone-wolf-attacks-fbi-world-cup.</E>
                        </P>
                    </FTNT>
                    <P>
                        These events proceed under the same stadium and special-event flight restrictions that the documented incursions repeatedly violated. Since 
                        <PRTPAGE P="41478"/>
                        the 2026 FIFA World Cup began, as of June 20, 2026, DHS and the FBI have recorded over 600 drone incursions into restricted airspace across host-city venues, and Federal C-UAS teams seized hundreds of unauthorized drones in multiple host cities.
                        <SU>10</SU>
                        <FTREF/>
                         And the highest-attendance matches, including the knockout rounds and the final, remain ahead.
                    </P>
                    <FTNT>
                        <P>
                            <SU>10</SU>
                             
                            <E T="03">See</E>
                             David Shepardson, 
                            <E T="03">US agencies have seized more than 300 drones near World Cup sites, TSA says,</E>
                             Reuters (June 23, 2026), 
                            <E T="03">https://www.reuters.com/sports/soccer/us-agencies-have-seized-more-than-300-drones-near-world-cup-sites-tsa-says-2026-06-23/.</E>
                        </P>
                    </FTNT>
                    <P>The Nation's 250th anniversary observances bring large public events to multiple major cities on the same days, beginning the first week of July 2026 and continuing through mid-July, including tall-ship naval reviews, aircraft fly-overs, and major municipal fireworks displays. A number of these are federally designated special security events, including a National Special Security Event. Several involve planned manned-aircraft operations in the same airspace as the public gathering, which makes airspace deconfliction of any C-UAS response especially important. SLTT agencies are already supporting C-UAS protection at these events and will continue to do so through their conclusion, but without this rule's framework, they would not be able to act independently to fully protect their jurisdictions.</P>
                    <P>
                        The reason these agencies cannot yet operate fully is the nature of the only mechanism now available to them. Most of the personnel the NCUTC has trained are already federally deputized, so the constraint is not the pace of deputization. It is that deputized personnel act under Federal authority and can exercise the C-UAS authorities that depend on the Act's legal protections, including mitigation and the use of RF-emitting systems, only when acting in connection with a Federal operation or with Federal assistance.
                        <SU>11</SU>
                        <FTREF/>
                          
                        <E T="03">See</E>
                         6 U.S.C. 124n(a)(1). Federal resources cannot be present at every one of the simultaneous events in July 2026, leaving SLTT agencies unable to nimbly protect their own communities and events under their own authority. This rule supplies the direct pathway that 6 U.S.C. 124n(a)(2) provides. After training and certification through the NCUTC and adoption of an implementation policy, SLTT agencies may exercise these authorities under their own authority, without case-by-case Federal deputization and without a Federal operation on scene. Making that pathway effective on public inspection is what allows these agencies to provide lawful, coordinated, and full C-UAS coverage during the events described above. Any delay for notice and comment would therefore frustrate critical safety and security activities authorized by the Act.
                    </P>
                    <FTNT>
                        <P>
                            <SU>11</SU>
                             Specifically, deputized personnel must be operating pursuant to a Federal action or else risk being subject to State, local, Tribal, or territorial law. Section 124n(a)(1) only provides relief from certain Federal laws, which makes sense because it allows deputization of SLTT agency personnel for Federal operations—thus, relief from State, local, Tribal, and territorial laws is unnecessary. Section 124n(a)(2), on the other hand, provides relief from State, local, Tribal, and territorial law, thus providing relief to SLTT agencies engaged in C-UAS activity outside Federal operations so long as they are trained and certified. In other words, the framework in this rule is the key that unlocks SLTT agencies' ability to fully operate independently under the authority Congress provided.
                        </P>
                    </FTNT>
                    <P>
                        As noted above, approximately 46 SLTT agencies have already completed training and certification through the NCUTC and stand ready to operate, reflecting 61 individually certified officers per NCUTC certification records; the framework this rule establishes is one of the remaining requirements, in addition to the establishment of the list of authorized technologies required by 6 U.S.C. 124n(d)(2)(A)(iii). Delaying this rule's framework for pre-promulgation notice and comment would leave trained State and local protective capacity sidelined during the greatest period of need experienced so far. This rule responds to an increasing pattern of imminent threats to public safety, and its immediate implementation directly impacts public safety. 
                        <E T="03">See NRDC,</E>
                         894 F.3d at 114.
                    </P>
                    <P>Finally, the Departments note that they have been diligently working to expand Federal and SLTT agency C-UAS capacity via a range of efforts, of which this rulemaking effort is only one. For instance:</P>
                    <P>
                        • DOJ has prioritized the full enforcement of applicable civil and criminal laws when drone operators endanger the public, violate established airspace restrictions, or operate a drone in furtherance of an element of another crime; 
                        <SU>12</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>12</SU>
                             
                            <E T="03">See</E>
                             E.O. 14305, Restoring American Airspace Sovereignty, 90 FR 24719 (June 6, 2025).
                        </P>
                    </FTNT>
                    <P>• DOJ, through the FBI, established and continues to expand the NCUTC through a resident mitigation course and an online detection and warning curriculum, which has certified 61 officers across approximately 46 SLTT agencies to date, and is expanding the NCUTC's instructor cadre and course frequency to meet anticipated nationwide demand;</P>
                    <P>
                        • DHS, through the Federal Emergency Management Agency (“FEMA”), noticed and awarded $250 million in Federal funding in FY 2026 to enhance SLTT agency capabilities to detect, identify, track, or monitor UAS in anticipation of the FIFA World Cup 
                        <SU>TM</SU>
                        ; 
                        <SU>13</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>13</SU>
                             
                            <E T="03">See</E>
                             Counter Unmanned Aircraft Systems Grant Program, 
                            <E T="03">FEMA</E>
                             (June 9, 2026), 
                            <E T="03">https://www.fema.gov/grants/preparedness/counter-unmanned-aircraft-systems-grant-program</E>
                             [
                            <E T="03">https://perma.cc/CRC2-9MW5</E>
                            ].
                        </P>
                    </FTNT>
                    <P>
                        • The Departments planned, coordinated, and led C-UAS protection across all 11 U.S. host cities for the FIFA World Cup
                        <SU>TM</SU>
                        , ensuring that trained State and local officers embedded in FBI-led task forces are able to support C-UAS operations at tournament venues and associated sites as needed; 
                        <SU>14</SU>
                        <FTREF/>
                         and
                    </P>
                    <FTNT>
                        <P>
                            <SU>14</SU>
                             
                            <E T="03">See</E>
                             FBI, 
                            <E T="03">Philadelphia is a `No Drone Zone' Around FIFA World Cup and Other Special Events This Summer</E>
                             (June 2, 2026), 
                            <E T="03">https://www.fbi.gov/contact-us/field-offices/philadelphia/news/philadelphia-is-a-no-drone-zone-around-fifa-world-cup-and-other-special-events-this-summer.</E>
                        </P>
                    </FTNT>
                    <P>
                        • DHS provided ongoing assistance to Federal coordination teams and SLTT agencies acquiring and implementing C-UAS technologies in the U.S. host cities by optimizing C-UAS sensor placement, coordinating memoranda of understanding, conducting site surveys and RF analyses, enhancing operational strategies, and developing guidance on C-UAS procurement and field placement.
                        <SU>15</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>15</SU>
                             
                            <E T="03">See, e.g.,</E>
                             DHS, 
                            <E T="03">Counter-Unmanned Aircraft Systems (C-UAS) Equipment Placement Field Guidance for State and Local First Responders</E>
                             (Mar. 9, 2026), 
                            <E T="03">https://www.dhs.gov/science-and-technology/publication/c-uas-equipment-placement-field-guidance-responders;</E>
                             DHS, 
                            <E T="03">Purchasing Tool for Counter Unmanned Aircraft Systems (C-UAS)</E>
                             (Dec. 15, 2025), 
                            <E T="03">https://www.dhs.gov/science-and-technology/publication/c-uas-purchasing-tool;</E>
                             DHS, 
                            <E T="03">S&amp;T Lab is Working with State and Local Agencies to Counter Drones at the World Cup</E>
                             (May 7, 2026), 
                            <E T="03">https://www.dhs.gov/science-and-technology/news/2026/05/07/st-lab-working-state-and-local-agencies-counter-drones-world-cup.</E>
                        </P>
                    </FTNT>
                    <P>
                        The Departments also note that work on C-UAS matters—including this rule—was necessarily complicated by the lingering effects of a 43-day Federal Government shutdown that lasted from October 1, 2025, through November 12, 2025,
                        <SU>16</SU>
                        <FTREF/>
                         and which were compounded 
                        <PRTPAGE P="41479"/>
                        by a 75-day DHS-specific government shutdown that followed the Act's enactment and lasted from February 14, 2026, to April 30, 2026.
                        <SU>17</SU>
                        <FTREF/>
                         Despite the challenges caused by funding disruptions and workforce shutdowns, the Departments have diligently worked to address UAS-related risks across a range of domains.
                    </P>
                    <FTNT>
                        <P>
                            <SU>16</SU>
                             
                            <E T="03">See</E>
                             Marc Labonte &amp; Lida R. Weinstock, Cong. Rsch. Serv., R48832, 
                            <E T="03">The 2025 (FY2026) Government Shutdown: Economic Effects</E>
                             (Jan. 29, 2026), 
                            <E T="03">https://www.congress.gov/crs-product/R48832</E>
                             (“The federal government experienced a funding gap beginning on October 1, 2025—the start of FY2026—and ending when the Continuing Appropriations, Agriculture, Legislative Branch, Military Construction and Veterans Affairs, and Extensions Act, 2026 (P.L. 119-37), was signed into law on November 12, 2025”); 
                            <E T="03">see also</E>
                             Joe Walsh et al., CBS News, 
                            <E T="03">The 2025 U.S. Government Shutdown, by the Numbers</E>
                             (Nov. 13, 2025), 
                            <E T="03">https://www.cbsnews.com/news/2025-government-shutdown-by-numbers/</E>
                             (“The longest government shutdown in modern U.S. history came to a close Wednesday night when President Trump signed a 
                            <PRTPAGE/>
                            bill to fund the government through Jan. 30—ending a 43-day-long impasse that had imperiled air travel and left thousands without paychecks.”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>17</SU>
                             
                            <E T="03">See</E>
                             Scott Wong et al., 
                            <E T="03">Record-long Department of Homeland Security Shutdown Ends,</E>
                             NBC News (Apr. 30, 2026), 
                            <E T="03">https://www.nbcnews.com/politics/congress/congress-expected-end-record-75-day-partial-government-shutdown-rcna342903</E>
                             (“The House on Thursday approved a Senate-passed bill that would fund much of the Department of Homeland Security, ending the record 75-day shutdown of the sprawling federal agency.”).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2. Immediate Effective Date</HD>
                    <P>
                        Additionally, the Departments are making this rule immediately effective. This rule recognizes an exemption or relieves a restriction and is thus not subject to the APA's delayed-effective-date requirement. 
                        <E T="03">See</E>
                         5 U.S.C. 553(d)(1).
                    </P>
                    <P>
                        Additionally, there is good cause to forgo a delayed effective date, 
                        <E T="03">see</E>
                         5 U.S.C. 553(d)(3), for the reasons provided for forgoing notice and comment explained in Section IV.A.1 of this preamble, but also because no one requires time to comply with the rule's requirements before it becomes effective. The primary purpose of the delayed-effective-date requirement is to give people a reasonable time to prepare to comply with the rule. 
                        <E T="03">See</E>
                         U.S. Dep't of Just., 
                        <E T="03">Attorney General's Manual on the Administrative Procedure Act</E>
                         36 (1947); 
                        <E T="03">Riverbend Farms, Inc.</E>
                         v. 
                        <E T="03">Madigan,</E>
                         958 F.2d 1479, 1485 (9th Cir. 1992) (holding that the purpose of 5 U.S.C. 553(d) is “to give affected parties time to adjust their behavior before the final rule takes effect”). This rule does not compel SLTT agencies to take any actions discussed in this rulemaking. Indeed, the requirements this rule sets forth reflect the procedures taught at the NCUTC, the resident mitigation courses of which have trained the operators of the SLTT agencies active to date, and participation remains voluntary at every step. Upon publication, the NCUTC will transmit this rule to every agency it has trained. The online detection and warning curriculum, updated to reflect the rule's data handling, dissemination, and retention requirements, will be available through the NCUTC training portal on the effective date; it requires approximately one hour to complete, and certification issues automatically upon completion. Section 124.5(n) preserves existing Mitigation Certifications while previously trained personnel complete that curriculum, so no SLTT agency loses capability on the effective date and no agency requires additional lead time to come into compliance. Additionally, some of the requirements this rule sets forth are already known to the SLTT agencies who acquired C-UAS technologies using FEMA grant dollars earlier in FY 2026. Specifically, the FEMA Notice of Funding Opportunity stipulated that deputized SLTT agency members must enroll and complete the training course at FBI's NCUTC to employ mitigation capabilities funded by Federal grant dollars.
                        <SU>18</SU>
                        <FTREF/>
                         Thus, SLTT agency personnel and their agencies do not require additional time to prepare to comply.
                    </P>
                    <FTNT>
                        <P>
                            <SU>18</SU>
                             FEMA, 
                            <E T="03">Counter-Unmanned Aircraft Systems Grant Program Fact Sheet</E>
                             (Nov. 10, 2025), 
                            <E T="03">https://www.fema.gov/fact-sheet/counter-unmanned-aircraft-systems-grant-program-fact-sheet</E>
                             [
                            <E T="03">https://perma.cc/6HKW-APHN</E>
                            ].
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">B. Regulatory Flexibility Act</HD>
                    <P>
                        The Regulatory Flexibility Act's (“RFA”) regulatory flexibility analysis requirements apply only to those rules for which an agency is required to publish a general notice of proposed rulemaking pursuant to 5 U.S.C. 553 or any other law. 
                        <E T="03">See</E>
                         5 U.S.C. 604(a). As discussed previously, the Departments did not issue a notice of proposed rulemaking for this action as exempted by 5 U.S.C. 553(b)(B). Therefore, a regulatory flexibility analysis is not required for this rule.
                    </P>
                    <HD SOURCE="HD2">C. Executive Orders 12866 and 13563—Regulatory Review</HD>
                    <P>The Office of Management and Budget (“OMB”) has determined that this rulemaking is a “significant regulatory action” under section 3(f) of Executive Order 12866, 58 FR 51735, 51738 (Sept. 30, 1993), but that it is not a section 3(f)(1) significant action. Accordingly, this rule has been submitted to OMB for review. This rule has been drafted and reviewed in accordance with section 1(b) of Executive Order 12866 and section 1(b) Executive Order 13563, 76 FR 3821 (Jan. 18, 2011).</P>
                    <P>The changes made by this rulemaking are deregulatory in character and impose no mandate on any SLTT agency. The rule does not require any agency to acquire C-UAS capability or to conduct C-UAS operations; it establishes the framework through which agencies may voluntarily obtain certification and exercise the authority Congress provided, and it removes, for participating agencies that satisfy its conditions, exposure to the criminal prohibitions displaced by the notwithstanding clause of 6 U.S.C. 124n(a)(2). In plain terms, an agency that chooses to participate and follows the rule's conditions can lawfully take protective actions against threatening drones that criminal law would otherwise prohibit; an agency that does not participate is left exactly where it was before. The principal benefits are the public safety, critical infrastructure, and correctional security protections that trained and certified SLTT agencies can provide against UAS threats, the reduced reliance on limited Federal C-UAS assets that SLTT participation makes possible, and the immediate availability of a qualified SLTT law enforcement C-UAS capability for major public events. The principal costs are the training, equipment, coordination, and reporting costs that participating agencies, each of which decides whether the benefits justify those costs in light of its own assessment of its needs and resources, voluntarily incur. Because participation is voluntary, and the rule imposes no mandate, the Departments expect the rule's net effect to be beneficial, with costs falling only on agencies that have determined the capability to be worth the expense.</P>
                    <HD SOURCE="HD2">D. Executive Order 14192—Unleashing Prosperity Through Deregulation</HD>
                    <P>
                        Executive Order 14192, 90 FR 9065 (Jan. 31, 2025), requires an agency, unless prohibited by law, to identify at least 10 existing regulations to be repealed or revised when the agency publicly proposes for notice and comment, or otherwise promulgates, a new regulation that qualifies as an Executive Order 14192 regulatory action (defined in OMB Memorandum M-25-20 as a significant regulatory action as defined in section 3(f) of Executive Order 12866 that has been finalized and that imposes total costs greater than zero). In furtherance of this requirement, section 3(c) of Executive Order 14192 requires that the incremental costs associated with such new regulations must, to the extent permitted by law, also be offset by eliminating existing costs associated with at least 10 prior regulations. 90 FR 9065. This IFR is an Executive Order 14192 deregulatory action. 
                        <E T="03">See</E>
                         OMB Memorandum M-25-20, “Guidance Implementing Section 3 of Executive Order 14192, titled `Unleashing Prosperity Through Deregulation' ” (Mar. 26, 2025).
                    </P>
                    <HD SOURCE="HD2">E. Executive Order 14294—Overcriminalization of Federal Regulations</HD>
                    <P>
                        Executive Order 14294, 90 FR 20363 (May 9, 2025), requires agencies promulgating regulations with criminal regulatory offenses potentially subject to 
                        <PRTPAGE P="41480"/>
                        criminal enforcement to explicitly describe the conduct subject to criminal enforcement, the authorizing statutes, and the mens rea standard applicable to each element of those offenses. 90 FR 20363. This rule does not create a criminal regulatory offense and is thus exempt from Executive Order 14294 requirements.
                    </P>
                    <HD SOURCE="HD2">F. Executive Order 13132—Federalism</HD>
                    <P>This IFR will not have substantial direct effects on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government, as outlined by Executive Order 13132, 64 FR 43255 (Aug. 4, 1999). The IFR implements only a voluntary process for SLTT agencies to obtain certification to use certain C-UAS capabilities consistent with the requirements of the SAFER SKIES Act. By virtue of its “notwithstanding” provision, the SAFER SKIES Act may preempt the conflicting laws of any particular SLTT jurisdiction when a duly qualified SLTT law enforcement or correctional officer takes actions authorized under 6 U.S.C. 124n(a)(2). This IFR does not materially expand the preemptive effect of that provision. In developing this rule, the Departments engaged with SLTT agencies, including through the NCUTC and through outreach to SLTT agencies, and will continue that engagement through the comment period. The rule also accommodates State and local law where Congress did not displace it: § 124.14(h) addresses the interaction between the Federal retention limit and the SLTT records retention requirements, and § 124.6(b) requires review of the interplay of proposed operations and implementing policies with applicable SLTT law. The Departments specifically invite comment from SLTT officials on all aspects of this rule, including the coordination requirements of § 124.10.</P>
                    <HD SOURCE="HD2">G. Executive Order 12988—Civil Justice Reform</HD>
                    <P>
                        This rule meets the applicable standards set forth in sections 3(a) and 3(b)(2) of Executive Order 12988, 61 FR 4729, 4730-32 (Feb. 5, 1996), to specify provisions in clear language. Pursuant to section 3(b)(1)(I) of the Executive Order, nothing in this rule is intended to create any legal or procedural rights enforceable against the United States. 
                        <E T="03">See</E>
                         61 FR 4731.
                    </P>
                    <HD SOURCE="HD2">H. Unfunded Mandates Reform Act of 1995</HD>
                    <P>Title II of the Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-38, UMRA) requires each Federal agency to prepare a written statement assessing the effects of any Federal mandate in a proposed rule or final rule for which the agency published a proposed rule, which includes any Federal mandate that may result in a $100 million or more expenditure (adjusted annually for inflation) in any one year by State, local, and Tribal governments, in the aggregate, or by the private sector.</P>
                    <P>
                        A written statement under UMRA is not required unless an agency has published a notice of proposed rulemaking. 
                        <E T="03">See</E>
                         2 U.S.C. 1532(a). In addition, an action is exempt from UMRA if it is necessary for the national security. 
                        <E T="03">See</E>
                         2 U.S.C. 1503(5). As discussed in Section IV.A. of this preamble, this rule is exempt from notice and comment rulemaking procedures and is necessary for the national security. Accordingly, the Departments have not prepared a written statement in connection with this rule.
                    </P>
                    <HD SOURCE="HD2">I. Paperwork Reduction Act</HD>
                    <P>
                        This rule contains information collection requirements subject to review by the Office of Management and Budget under the Paperwork Reduction Act of 1995, 44 U.S.C. 3501 
                        <E T="03">et seq.</E>
                         The information collections in this rule are the agency implementation policy, the detection-and-warning policy, and the portal attestations under § 124.6, feedback on the Authorized Technologies List and Authorized Systems List described in § 124.7, the C-UAS Operations Plan under § 124.8, the advance notification and notice of intent under §§ 124.9 and 124.10, the mutual aid documentation under § 124.4, the real-time air traffic control notification under § 124.11, the post-operation reports and semiannual operational summaries under § 124.13, the testing activities plan under § 124.18, and the recordkeeping, retention determination, and audit trail requirements under § 124.14.
                    </P>
                    <P>The Departments estimate the burden of these collections as follows, based on an expectation of approximately 1,500 detection-tier and 150 mitigation-tier participating agencies within the first two years.</P>
                    <P>
                        • 
                        <E T="03">Agency implementation policy:</E>
                         approximately 16 hours for a mitigation-tier agency to adapt and adopt the model policy the Departments will publish, including legal review.
                    </P>
                    <P>
                        • 
                        <E T="03">Detection-and-warning policy:</E>
                         approximately 4 hours.
                    </P>
                    <P>
                        • 
                        <E T="03">Portal attestation:</E>
                         approximately 15 minutes, renewed annually.
                    </P>
                    <P>
                        • 
                        <E T="03">Annual policy renewal:</E>
                         approximately 1 to 2 hours.
                    </P>
                    <P>
                        • 
                        <E T="03">Feedback on the lists:</E>
                         approximately 5 minutes for 50 agencies.
                    </P>
                    <P>
                        • 
                        <E T="03">C-UAS Operations Plan:</E>
                         for a mitigation operation, approximately 3 hours per plan on the standardized form, and approximately 1 hour for a renewal plan incorporating a prior plan by reference; for a detection and warning operation, approximately 30 minutes per plan.
                    </P>
                    <P>
                        • 
                        <E T="03">Advance notification, including the data elements supporting FAA and FCC coordination:</E>
                         approximately 2 to 6 hours per mitigation operation, varying with the number and complexity of RF-emitting systems to be deployed, and expected to trend toward the lower bound as the Authorized Systems List is populated with systems that have completed system-level spectrum evaluation.
                    </P>
                    <P>
                        • 
                        <E T="03">Notice of intent:</E>
                         approximately 30 minutes.
                    </P>
                    <P>
                        • 
                        <E T="03">Mutual aid documentation:</E>
                         approximately 1 hour.
                    </P>
                    <P>
                        • 
                        <E T="03">Post-operation report:</E>
                         approximately 45 minutes per reportable event.
                    </P>
                    <P>
                        • 
                        <E T="03">Semiannual operational summary:</E>
                         approximately 1 hour for a detection-tier agency and 2 hours for a mitigation-tier agency.
                    </P>
                    <P>
                        • 
                        <E T="03">Testing activities plan:</E>
                         approximately 2 hours.
                    </P>
                    <P>
                        • 
                        <E T="03">Recordkeeping, retention determinations, and audit trail maintenance:</E>
                         approximately 2 hours per year for a detection-tier agency and, for a mitigation-tier agency, approximately 2 hours per year plus approximately 1 hour per mitigation operation, or approximately 17 hours per year at the assumed operational tempo.
                    </P>
                    <P>
                        On these assumptions, and assuming on average 15 mitigation operations per mitigation-tier agency per year and 50 detection and warning operations per detection-tier agency per year, the aggregate annual burden is approximately 65,000 to 80,000 hours across all participating agencies, with a central estimate of approximately 72,000 hours, an average of roughly 33 hours per year for a detection-tier agency and roughly 150 hours per year for a mitigation-tier agency. Monetized respondent costs will be presented in the supporting statement using loaded hourly compensation rates derived from Bureau of Labor Statistics data for law enforcement and correctional personnel. The Departments invite comment on 
                        <PRTPAGE P="41481"/>
                        each of these estimates and assumptions.
                    </P>
                    <P>The FBI and the Justice Management Division of the Department of Justice will coordinate to finalize the information collection analysis, prepare the supporting statement, and obtain an OMB control number for these collections. The Departments invite comment on the estimated burden of these collections and on ways to minimize that burden.</P>
                    <HD SOURCE="HD2">J. National Environmental Policy Act</HD>
                    <P>
                        The Departments have analyzed this rule under the National Environmental Policy Act of 1969 (“NEPA”), 42 U.S.C. 4321 
                        <E T="03">et seq.,</E>
                         as amended by the Fiscal Responsibility Act of 2023, and under their respective NEPA implementing procedures, including Department of Homeland Security Directive 023-01 and Instruction Manual 023-01-001-01 and the Department of Justice procedures at 28 CFR part 61. This rule establishes an administrative and procedural framework consisting of training and certification requirements, agency policy and attestation requirements, technology authorization by reference to interagency lists, coordination and notification procedures, reporting, and privacy protections. The rule does not authorize, fund, or direct the construction of facilities, the acquisition or deployment of any equipment, or any other physical activity, and it has no potential to result in environmental effects. The rule therefore qualifies for categorical exclusion under DHS categorical exclusion A3 (rules of a strictly administrative or procedural nature and rules implementing statutory requirements without substantive change), and the Departments have determined that no extraordinary circumstances are present that would warrant preparation of an environmental assessment or environmental impact statement.
                    </P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects</HD>
                        <CFR>6 CFR Part 124</CFR>
                        <P>Aircraft, Aviation safety, Critical infrastructure, Intergovernmental relations, Investigations, Law enforcement officers, Penalties, Privacy, Reporting and recordkeeping requirements, Security measures, Seizures and forfeitures, Wiretapping and electronic surveillance.</P>
                        <CFR>28 CFR Part 124</CFR>
                        <P>Aircraft, Aviation safety, Critical infrastructure, Intergovernmental relations, Investigations, Law enforcement officers, Penalties, Privacy, Reporting and recordkeeping requirements, Security measures, Seizures and forfeitures, Wiretapping and electronic surveillance.</P>
                    </LSTSUB>
                    <HD SOURCE="HD1">
                        <E T="0742">DEPARTMENT OF HOMELAND SECURITY</E>
                    </HD>
                    <REGTEXT TITLE="6" PART="124">
                        <AMDPAR>Accordingly, for the reasons set forth in the preamble, title 6 of the Code of Federal Regulations is amended by adding part 124 to read as follows:</AMDPAR>
                        <PART>
                            <HD SOURCE="HED">PART 124—COUNTER-UNMANNED AIRCRAFT SYSTEM AUTHORITY FOR STATE, LOCAL, TRIBAL, AND TERRITORIAL LAW ENFORCEMENT AND CORRECTIONAL AGENCIES</HD>
                            <CONTENTS>
                                <SECHD>Sec.</SECHD>
                                <SECTNO>124.1 </SECTNO>
                                <SUBJECT>Purpose and scope.</SUBJECT>
                                <SECTNO>124.2 </SECTNO>
                                <SUBJECT>Definitions.</SUBJECT>
                                <SECTNO>124.3 </SECTNO>
                                <SUBJECT>Scope of authority and mitigation standards.</SUBJECT>
                                <SECTNO>124.4 </SECTNO>
                                <SUBJECT>Authorized personnel, contractors, and mutual aid.</SUBJECT>
                                <SECTNO>124.5 </SECTNO>
                                <SUBJECT>Training and certification.</SUBJECT>
                                <SECTNO>124.6 </SECTNO>
                                <SUBJECT>Agency implementation policy.</SUBJECT>
                                <SECTNO>124.7 </SECTNO>
                                <SUBJECT>Authorized technologies.</SUBJECT>
                                <SECTNO>124.8 </SECTNO>
                                <SUBJECT>C-UAS Operations Plan.</SUBJECT>
                                <SECTNO>124.9 </SECTNO>
                                <SUBJECT>Advance coordination, notification, and authorization.</SUBJECT>
                                <SECTNO>124.10 </SECTNO>
                                <SUBJECT>Interagency and lead-agency coordination.</SUBJECT>
                                <SECTNO>124.11 </SECTNO>
                                <SUBJECT>Real-time air traffic control notification.</SUBJECT>
                                <SECTNO>124.12 </SECTNO>
                                <SUBJECT>Detection and warning operations.</SUBJECT>
                                <SECTNO>124.13 </SECTNO>
                                <SUBJECT>Post-operation reporting.</SUBJECT>
                                <SECTNO>124.14 </SECTNO>
                                <SUBJECT>Privacy and civil liberties.</SUBJECT>
                                <SECTNO>124.15 </SECTNO>
                                <SUBJECT>Protection of sensitive operational information.</SUBJECT>
                                <SECTNO>124.16 </SECTNO>
                                <SUBJECT>Compliance and enforcement.</SUBJECT>
                                <SECTNO>124.17 </SECTNO>
                                <SUBJECT>Confiscation and forfeiture.</SUBJECT>
                                <SECTNO>124.18 </SECTNO>
                                <SUBJECT>Activities for evaluation, testing, training, and pre-operational validation.</SUBJECT>
                                <SECTNO>124.19 </SECTNO>
                                <SUBJECT>Task force arrangements and Federal support.</SUBJECT>
                                <SECTNO>124.20 </SECTNO>
                                <SUBJECT>Construction.</SUBJECT>
                                <SECTNO>124.21 </SECTNO>
                                <SUBJECT>Termination.</SUBJECT>
                                <SECTNO>124.22 </SECTNO>
                                <SUBJECT>Severability.</SUBJECT>
                            </CONTENTS>
                            <AUTH>
                                <HD SOURCE="HED">Authority:</HD>
                                <P> 5 U.S.C. 301; 6 U.S.C. 124n, as amended by the SAFER SKIES Act (Division H, Title LXXXVI of the National Defense Authorization Act for Fiscal Year 2026, Pub. L. 119-60, sec. 8601-8607, 139 Stat. 718, 1938-45 (2025)).</P>
                            </AUTH>
                            <SECTION>
                                <SECTNO>§ 124.1 </SECTNO>
                                <SUBJECT>Purpose and scope.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Purpose.</E>
                                     This part implements the authority of the Secretary of Homeland Security and the Attorney General to develop the governance framework for the exercise of all counter-unmanned aircraft system (C-UAS) actions by State, local, Tribal, and territorial (SLTT) law enforcement and correctional agencies and their personnel under 6 U.S.C. 124n(a)(2), as amended by the SAFER SKIES Act. The purpose of actions taken under this authority is to detect, identify, monitor, track, warn, and, if necessary, mitigate credible threats posed by unmanned aircraft or unmanned aircraft systems (UAS) to the safety or security of people, facilities, or assets; a venue or set of venues used for large-scale public gatherings or events; critical infrastructure; or a correctional facility.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Scope.</E>
                                     This part applies to all SLTT law enforcement and correctional agencies, and their personnel seeking to exercise or exercising authority under 6 U.S.C. 124n(a)(2). This part does not govern Federal agency operations under 6 U.S.C. 124n(a)(1), nor deputized SLTT personnel conducting C-UAS as part of an FBI C-UAS task force, which are subject to separate policies and guidance. An SLTT law enforcement or correctional agency that conducts only detection and warning operations using systems the operation of which requires the authority of the Act or the relief it provides from certain laws is subject principally to the Detection and Warning Certification requirement of § 124.5(c), the detection and warning policy provisions of § 124.6(g), the authorized technology requirements of § 124.7, the C-UAS Operations Plan requirement of § 124.8, the operational conditions of § 124.12, and the privacy and data handling requirements of § 124.14.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Relationship to other laws.</E>
                                     As provided in 6 U.S.C. 124n(a)(2), actions taken by SLTT law enforcement and correctional agencies and their personnel in compliance with this part may be taken notwithstanding section 46502 of title 49, United States Code, and sections 32, 1030, and 1367 and chapters 119 and 206 of title 18, United States Code, and notwithstanding the laws of any particular State, local, Tribal, or territorial jurisdiction. Nothing in this part vests in the Secretary of Homeland Security or the Attorney General any authority of the Secretary of Transportation or the Administrator of the Federal Aviation Administration.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Comprehensive framework.</E>
                                     This part establishes the complete framework governing the exercise of authority under 6 U.S.C. 124n(a)(2), including the training and certification procedures required by 6 U.S.C. 124n(d)(2)(A) and the guidance required by 6 U.S.C. 124n(d)(1) on the matters this part addresses. An SLTT law enforcement or correctional agency and its personnel exercising authority under 6 U.S.C. 124n(a)(2) must conduct operations in accordance with this part. The Attorney General, the Secretary of Homeland Security, the Secretary of Transportation, and the Administrator of the Federal Aviation Administration may issue forms, templates, curricula, and other implementing materials under this part to the extent consistent with 
                                    <PRTPAGE P="41482"/>
                                    law. Where any implementing material addresses a matter also addressed by this part, this part controls. Nothing in this part limits the authority of the Secretary of Homeland Security, the Attorney General, or the Secretary of Transportation to issue guidance under 6 U.S.C. 124n(d)(1) in their respective areas.
                                </P>
                                <P>
                                    (e) 
                                    <E T="03">Parallel regulations.</E>
                                     Consistent with section 8606(a)(1) of the Act, identical implementing regulations appear at 6 CFR part 124 and 28 CFR part 124. The Department of Homeland Security and Department of Justice administer and interpret their respective regulations with respect to their own programs, activities, and solely held authorities. Any description in these regulations of the other Department's programs, activities, or solely held authorities is provided for context and does not itself govern the other Department's exercise of its statutory authorities.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.2 </SECTNO>
                                <SUBJECT>Definitions.</SUBJECT>
                                <P>As used in this part:</P>
                                <P>
                                    <E T="03">Agency accreditation</E>
                                     means an agency's eligibility to exercise authority under this part, established when the agency has adopted the implementation policy and completed the portal attestation required by § 124.6(d), deploys only systems within categories on the Authorized Technologies List and, where populated, on the Authorized Systems List, and ensures that its personnel hold the certifications required for the authorities exercised.
                                </P>
                                <P>
                                    <E T="03">Agency Approving Official</E>
                                     means the senior official designated by an SLTT law enforcement or correctional agency in its implementation policy under § 124.6(a)(1), or in its detection and warning policy under § 124.6(g), authorized to approve C-UAS operations on behalf of the agency. The Agency Approving Official must not be below the rank of a Senior Executive or Senior Official or its equivalent, except that for an agency in which no equivalent rank exists, the agency head or the agency head's designee may serve as Agency Approving Official. The Agency Approving Official may not serve as a mitigation operator for an operation that official has approved.
                                </P>
                                <P>
                                    <E T="03">Authorized Systems List</E>
                                     means the subset of the Authorized Technologies List that identifies specific systems—including make, model, and hardware version—that have been authorized for operational use within one or more technology categories on the Authorized Technologies List. The Authorized Systems List is populated on a phased basis. As systems complete interagency assessment, systems may be added to the Authorized Systems List with appropriate operational limitations based on the approved capabilities, functions, and hardware version of the system.
                                </P>
                                <P>
                                    <E T="03">Authorized Technologies List</E>
                                     means the list of authorized technology categories for C-UAS operations by SLTT law enforcement and correctional agencies, maintained jointly by the Department of Justice, the Department of Homeland Security, the Department of Defense, the Department of Transportation and Federal Aviation Administration, the Federal Communications Commission, and the National Telecommunications and Information Administration, consistent with 6 U.S.C. 124n(d)(2)(A)(iii) and section 8606(a)(4) of the SAFER SKIES Act.
                                </P>
                                <P>
                                    <E T="03">Control communications</E>
                                     means any wire, oral, or electronic communication used to navigate, command, or otherwise control a UAS or unmanned aircraft, including telemetry transmitted from the aircraft to its operator, command-and-control signals transmitted from the operator to the aircraft, and any video, audio, or other data stream used by the operator to navigate the aircraft when other navigation telemetry is unavailable or insufficient. The operational role of a communication, rather than its packet type or transmission frequency, determines whether it is a control communication. Whether a communication is a control communication is determined when captured material is processed under § 124.14 and does not require an operator to determine in real time whether a particular video, audio, or data stream is being used to navigate the aircraft. Control communications also include a UAS unique identifier (such as a manufacturer device identifier or serial-correlated number), the operator or take-off location of the UAS, and the location, velocity, and emergency status of the UAS when that information is acquired by intercepting a communication from an unmanned aircraft or unmanned aircraft system pursuant to the relief provided by 6 U.S.C. 124n. The same information is not a control communication when it is obtainable without that relief.
                                </P>
                                <P>
                                    <E T="03">Correctional agency</E>
                                     has the meaning given in section 8606(c)(2) of the SAFER SKIES Act.
                                </P>
                                <P>
                                    <E T="03">Correctional facility</E>
                                     has the meaning given in 6 U.S.C. 124n(l)(9).
                                </P>
                                <P>
                                    <E T="03">Credible threat</E>
                                     means a threat that, based on the totality of circumstances known to the operator at the time of the determination, would cause a reasonable person in the operator's position, considering the operator's training and experience, to conclude that a UAS or unmanned aircraft poses an articulable risk to the safety or security of people, a facility, or an asset; a venue or set of venues used for large-scale public gatherings or events; critical infrastructure; or a correctional facility.
                                </P>
                                <P>(1) A credible threat may be based on, but is not limited to:</P>
                                <P>(i) Specific intelligence, including information from law enforcement databases, threat assessments, or intelligence community products;</P>
                                <P>(ii) Behavioral indicators, including operation in airspace in which UAS operations have been restricted or prohibited by the Federal Aviation Administration, operation not in compliance with Federal Aviation Administration's flight requirements, approach toward a protected interest, failure to respond to warnings, or evasive maneuvering inconsistent with normal flight operations;</P>
                                <P>(iii) Payload or physical configuration indicators, including observed attachments, modifications, or configurations inconsistent with ordinary recreational or commercial UAS use that suggest capability to cause harm or to deliver prohibited items;</P>
                                <P>(iv) Unauthorized surveillance or reconnaissance of a protected interest that by law is protected from such activities, or interference with the operational mission of a protected interest;</P>
                                <P>(v) Indications that the UAS is being used to gain unauthorized access to, or to disclose, classified, law enforcement sensitive, or otherwise lawfully protected information; or</P>
                                <P>(vi) Pattern-based indicators, including repeated unauthorized UAS activity at a specific location (such as repeat incursions of national defense airspace in violation of 49 U.S.C. 46307), which may inform but do not independently satisfy the credible threat standard.</P>
                                <P>
                                    (2) A credible threat determination rests on the totality of the circumstances. A single indicator may establish a credible threat where it is sufficiently probative. For mitigation actions under 6 U.S.C. 124n(b)(1)(C), (D), and (F), the determination must be supported by a contemporaneous indicator that the specific unmanned aircraft system or unmanned aircraft at issue poses a current, articulable risk if unabated. For detection and warning actions under 6 U.S.C. 124n(b)(1)(A) and (B), a credible threat determination may also be supported by a reasonable basis to anticipate that one or more unmanned aircraft systems or 
                                    <PRTPAGE P="41483"/>
                                    unmanned aircraft poses an articulable risk. Activity protected by the First Amendment to the Constitution of the United States may not be considered in making a credible threat determination.
                                </P>
                                <P>
                                    <E T="03">Critical infrastructure</E>
                                     has the meaning given in subsection (e) of the Critical Infrastructures Protection Act of 2001 (Pub. L. 107-56, sec. 1016, 115 Stat. 272, 400-02 (codified at 42 U.S.C. 5195c)), as referenced in 6 U.S.C. 124n(l)(10).
                                </P>
                                <P>
                                    <E T="03">Data purge verification</E>
                                     means documented confirmation that records subject to purge have been deleted from all systems on which they were stored. Verification may be performed through an automated system, supervisory review, or other documented confirmation process, and must be recorded in the audit trail required by § 124.14.
                                </P>
                                <P>
                                    <E T="03">Designated Federal C-UAS coordination portal</E>
                                     means the electronic submission system designated by the Attorney General and Secretary of Homeland Security for advance notifications, notices of intent, C-UAS Operations Plans, mitigation notifications, post-operation reports, and other submissions required by this part.
                                </P>
                                <P>
                                    <E T="03">Detection and Warning Certification</E>
                                     means certification that personnel have successfully completed the online detection and warning training curriculum developed and maintained through the National Counter-UAS Training Center (NCUTC) and passed the post-course assessment. A Detection and Warning Certification authorizes the holder to exercise the authorities described in 6 U.S.C. 124n(b)(1)(A), (B), and (E). The certification is issued automatically through the NCUTC training portal upon successful completion of the curriculum and assessment and recorded in the NCUTC certification database.
                                </P>
                                <P>
                                    <E T="03">Detection and warning operations</E>
                                     means operations conducted using systems the operation of which requires the authority of, or relief from certain laws under, 6 U.S.C. 124n and involve only the actions described in 6 U.S.C. 124n(b)(1)(A) and (B). Detection and warning activity conducted using systems that do not require the authority of 6 U.S.C. 124n (including, for example, electro-optical, infrared, acoustic sensors, and radar) is not subject to this part. Operation of RF-emitting C-UAS systems remains subject to applicable Federal Communications Commission authorization requirements and Federal Aviation Administration coordination if such emission could impact the National Airspace System or other systems located at or near airports.
                                </P>
                                <P>
                                    <E T="03">Detection system</E>
                                     means a system or technology used to take an action described in 6 U.S.C. 124n(b)(1)(A) or (B)—that is, to detect, identify, monitor, or track a UAS or unmanned aircraft, or to warn its operator, and that has no capability enabled to disrupt or seize control of, or disable, damage, or destroy a UAS or unmanned aircraft.
                                </P>
                                <P>
                                    <E T="03">FAA-designated coordination mechanism</E>
                                     means the program, office, or process designated by the Administrator of the Federal Aviation Administration for the coordination of C-UAS operations that might affect aviation safety, civilian aviation and aerospace operations, aircraft airworthiness, or the use of the airspace.
                                </P>
                                <P>
                                    <E T="03">Hazardous Devices School</E>
                                     means the schoolhouse operated by the Federal Bureau of Investigation at which public safety bomb technicians are certified and recertified in accordance with the National Guidelines for Bomb Technicians, or any successor publication.
                                </P>
                                <P>
                                    <E T="03">Mitigation action</E>
                                     means an action described in 6 U.S.C. 124n(b)(1)(C), (D), or (F). Detection and warning, described in 6 U.S.C. 124n(b)(1)(A) and (B), are not mitigation actions.
                                </P>
                                <P>
                                    <E T="03">Mitigation Certification</E>
                                     means certification issued by the National Counter-UAS Training Center upon successful completion of the NCUTC mitigation training course or a successor course approved by the Attorney General acting through the Director of the Federal Bureau of Investigation, authorizing the holder to exercise the authorities described in 6 U.S.C. 124n(b)(1)(C), (D), and (F), to the extent consistent with this part and applicable laws, using authorized technologies within the mitigation technology categories covered by the approved mitigation courses the holder has completed. A current Detection and Warning Certification is a prerequisite for obtaining and maintaining a Mitigation Certification.
                                </P>
                                <P>
                                    <E T="03">Mitigation operation</E>
                                     means an operation in which a mitigation system is deployed for the purpose of taking an action described in 6 U.S.C. 124n(b)(1)(C), (D), or (F), including disrupting, seizing, or exercising control of, or using reasonable force, if necessary, to disable, damage, or destroy a UAS or unmanned aircraft, whether or not a mitigation action is taken during the operation. A mitigation operation may include elements of detection and warning operations.
                                </P>
                                <P>
                                    <E T="03">Mitigation system</E>
                                     means a system or technology used or capable of being employed to take an action described in 6 U.S.C. 124n(b)(1)(C), (D), or (F), including disrupting, seizing or exercising control of, or using force to disable, damage, or destroy a UAS or unmanned aircraft. A system with both detection and mitigation capability is a mitigation system while its mitigation capability is enabled.
                                </P>
                                <P>
                                    <E T="03">National Counter-UAS Training Center (NCUTC)</E>
                                     means the national schoolhouse operated by the Federal Bureau of Investigation and designated by the Attorney General, acting through the Director of the Federal Bureau of Investigation, as the national training center for purposes of 6 U.S.C. 124n and as the sole certifying authority for SLTT C-UAS mitigation operators under 6 U.S.C. 124n(d)(2)(A)(i).
                                </P>
                                <P>
                                    <E T="03">Pattern data</E>
                                     means a derived data product reflecting aggregated trends, frequencies, or statistical observations of UAS activity across multiple C-UAS operations that has met the anonymization standards established by the agency's implementation policy and contains no information identifying any specific aircraft, operator, or natural person.
                                </P>
                                <P>
                                    <E T="03">Personnel</E>
                                     means officers and employees with assigned duties that include the security or protection of people, facilities, or assets of SLTT law enforcement and correctional agencies, as defined in 6 U.S.C. 124n(a)(2) and (l)(6)(B). This term does not include contractors of SLTT law enforcement and correctional agencies.
                                </P>
                                <P>
                                    <E T="03">Raw sensor data</E>
                                     means unprocessed or minimally processed data generated by C-UAS detection or mitigation systems, including radio frequency signal captures, waveform recordings, radar returns, optical and infrared imagery, acoustic signatures, full sensor logs, and system telemetry. Whether a particular item of raw sensor data constitutes a control communication, and is therefore a record of communications subject to the retention limit of § 124.14, is determined by its function.
                                </P>
                                <P>
                                    <E T="03">RF-emitting C-UAS system</E>
                                     means any C-UAS system that, when employed for detection or mitigation purposes, actively transmits radio frequency energy to detect, disrupt, disable, or seize control of a UAS or unmanned aircraft. This includes systems employing technologies for detection-only purposes, such as radars that transmit radio frequency signals, that may require a radiolocation service license to be issued from the Federal Communications Commission, and mitigation systems that employ radio frequency jamming (broadband or protocol-specific disruption of command-and-control links, video 
                                    <PRTPAGE P="41484"/>
                                    downlinks, or navigation signals) and radio frequency protocol manipulation (command injection or cyber takeover of control signals).
                                </P>
                                <P>
                                    <E T="03">SLTT law enforcement agency</E>
                                     has the meaning given in section 8606(c)(1) of the SAFER SKIES Act.
                                </P>
                                <P>
                                    <E T="03">Special Event Assessment Rating</E>
                                     means a rating assigned to an event under the special event assessment process administered by the Department of Homeland Security, or the equivalent rating under any successor event rating system.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.3 </SECTNO>
                                <SUBJECT>Scope of authority and mitigation standards.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Scope of authority.</E>
                                     An SLTT law enforcement or correctional agency exercising authority under 6 U.S.C. 124n(a)(2) may take actions described in 6 U.S.C. 124n(b)(1), which generally include detection, warning, and mitigation, that are necessary to address or eliminate a credible threat that a UAS or unmanned aircraft poses to the safety or security of people, a facility, or an asset; a venue or set of venues used for large-scale public gatherings or events; critical infrastructure; or a correctional facility. These statutory categories are functional and are not a prescribed list of property types. The determination of whether a specific property falls within these categories is made by the agency's Agency Approving Official, consistent with this part and 6 U.S.C. 124n. No “covered facility or asset” designation under 6 U.S.C. 124n(l)(3) is required for SLTT law enforcement or correctional agency operations; however, a risk-based assessment is required as part of the Operations Plan, as outlined in § 124.8. Whether the property falls within a section 124n(a)(2) category is a separate question from the credible threat determination. The credible threat determination required by paragraph (b) of this section must be made before any mitigation action.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Credible threat determination for mitigation actions.</E>
                                     Before taking any mitigation action, personnel must reasonably determine, under the totality of the circumstances, that a credible threat exists, as defined in § 124.2. The determination must be made in real time by the certified and trained personnel closest to the operational situation and documented as part of the post-operation report required by § 124.13. An established pattern of unauthorized UAS activity at a specific location is relevant to the totality of the circumstances and may, in combination with a contemporaneous indicator—including, for example, a new detection event at the same location during a period consistent with the established pattern—support a credible threat determination. A contemporaneous indicator need not independently establish a threat. Considered with the totality of the circumstances, which may include an established pattern of unauthorized UAS activity, an intelligence indicator, or other contextual information, the contemporaneous indicator must provide a present-tense basis for concluding that the specific aircraft at issue poses a current risk. This operational standard governs individual mitigation decisions by authorized personnel in the application of reasonable force under the totality of the circumstances and does not limit the information or analysis that may be considered at the approval level in determining whether to authorize a C-UAS operation for a specific event or facility.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Proportionality.</E>
                                     Mitigation actions must be proportionate to the credible threat identified. Personnel must employ the least disruptive effective means of mitigation available under the totality of the circumstances. If equipment is available and time permits, a warning to the remote pilot-in-command should precede any mitigation action. Before taking any mitigation action that may result in the disabling, damage, or destruction of an unmanned aircraft, personnel must consider whether the threat posed by the UAS outweighs the risk of collateral harm to public safety. A mitigation action that creates a greater risk to public safety than the threat it is intended to address is not proportionate and must not be taken. Where a non-mitigation measure is sufficient to eliminate the threat, seizure or destruction of the aircraft should be avoided when feasible. The risk of collateral harm to public safety includes the risk of falling debris, damage to persons or property on the ground, disruption to communications systems, and risks to aviation safety, civilian aviation and aerospace operations, aircraft airworthiness, or the use of the airspace.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Protective purpose limitation.</E>
                                     The authority of 6 U.S.C. 124n(a)(2) is limited to the protection of people, facilities, and assets; a venue or set of venues used for large-scale public gatherings or events; critical infrastructure; and correctional facilities from credible threats posed by unmanned aircraft and UAS. C-UAS authority under this part may not be exercised for the sole purpose of collecting evidence for criminal prosecution or as a substitute for the authority provided by chapter 119 or 206 of title 18, United States Code. Evidence obtained incidental to lawful protective C-UAS operations may be used in subsequent criminal proceedings consistent with applicable law.
                                </P>
                                <P>
                                    (e) 
                                    <E T="03">Mitigation operator requirement.</E>
                                     (1) The person who takes a mitigation action, including activating an RF-emitting system, executing a cyber-based takeover, or otherwise causing a C-UAS system to affect or otherwise impact the flight, control, or communications of a UAS or unmanned aircraft, must hold a current Mitigation Certification covering the technology category being employed, and must possess a valid 14 CFR part 107 remote pilot certificate. This requirement is not satisfied by supervision of an uncertified person by a certified operator; the certified operator must be the individual who directly executes the mitigation command or function.
                                </P>
                                <P>(2) Support functions that do not involve the initiation of mitigation actions, such as detection system monitoring, threat triage and prioritization, ground intercept team dispatch, communications, and administrative functions, do not require Mitigation Certification, but must be performed by personnel trained in accordance with the agency's implementation policy and, where the support function involves operation of systems requiring the authority of 6 U.S.C. 124n(a)(2) or the relief it provides from certain laws, by personnel holding a current Detection and Warning Certification.</P>
                                <P>(3) For operations involving multiple personnel performing distinct roles, the agency's implementation policy must define the roles and responsibilities of each position, identify which positions require Mitigation Certification, and which require Detection and Warning Certification only, and establish the communication and concurrence procedures between the mitigation operator and other personnel.</P>
                                <P>
                                    (f) 
                                    <E T="03">Independent professional judgment.</E>
                                     (1) The certified mitigation operator retains independent professional judgment on whether to initiate a mitigation action.
                                </P>
                                <P>(2) A supervisor, commander, or other official, regardless of rank, may provide operational direction, tactical context, and coordination guidance to the operator, and may direct the operator to withhold or cease mitigation when broader operational considerations warrant.</P>
                                <P>
                                    (3) A supervisor, commander, or other official may not direct a certified operator to initiate a mitigation action when the operator has determined that 
                                    <PRTPAGE P="41485"/>
                                    the credible threat standard is not met or that the proportionality requirement of paragraph (c) of this section is not satisfied.
                                </P>
                                <P>(4) The agency's implementation policy must address the chain of command for mitigation decisions and must make clear that non-certified personnel, regardless of rank, may not direct mitigation actions that override the certified operator's professional judgment on whether the conditions for mitigation are present.</P>
                                <P>(5) An operator who declines to initiate mitigation based on a good-faith professional determination that the conditions for mitigation are not met may not be subjected to adverse employment action for that decision.</P>
                                <P>
                                    (g) 
                                    <E T="03">Airspace awareness.</E>
                                     (1) For operations where known authorized manned or unmanned aviation is operating or anticipated in or near the area of operations, the agency's implementation policy or C-UAS Operations Plan must designate a person or position responsible for maintaining real-time awareness of known authorized aviation within the operational area and for ensuring that this information is communicated to personnel authorized to initiate mitigation actions before any mitigation is executed. For purposes of this paragraph, known authorized aviation means any manned or unmanned aircraft that has been identified in the C-UAS Operations Plan, communicated to the C-UAS team during the operation, or otherwise confirmed as lawfully operating in or near the area of operations. The designated person, or the individual filling the designated position, must have the ability to communicate directly with the mitigation operator. No mitigation action may be initiated without reasonable efforts to confirm that the target is not a known authorized aircraft.
                                </P>
                                <P>(2) The scope and formality of this role must be commensurate with the complexity of the aviation environment. For operations with minimal or no known authorized aviation, this role may be performed as an additional duty by the certified operator or other command post personnel; for operations with significant aviation activity, the agency must designate a dedicated individual with airspace awareness and coordination responsibilities. When a target cannot be correlated with any known, authorized aircraft and meets the credible threat standard, mitigation may proceed.</P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.4 </SECTNO>
                                <SUBJECT>Authorized personnel, contractors, and mutual aid.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Officers and employees.</E>
                                     The authority provided by 6 U.S.C. 124n(a)(2) may be exercised only by SLTT law enforcement or correctional agency personnel. No SLTT law enforcement or correctional agency may delegate or transfer the exercise of C-UAS mitigation authority to any person or entity that is not an officer or employee of the agency.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Prohibition on contractor exercise.</E>
                                     Contractors may provide technical support, system maintenance, and training assistance, but may not operate C-UAS mitigation systems, make credible threat determinations, or execute mitigation actions. An arrangement in which a contractor exercises de facto operational control of a C-UAS mitigation system during an operation, including an arrangement described as a turnkey, managed service, or operator-provided C-UAS service, constitutes an unauthorized delegation of authority and is grounds for suspension of accreditation or certification under § 124.5(i). Detection services that do not require the authority of the Act or the relief it provides from certain laws may be provided by contractors.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Mutual aid and regional C-UAS support.</E>
                                     (1) An SLTT law enforcement or correctional agency accredited under 6 U.S.C. 124n(d)(2) may provide C-UAS support to another SLTT law enforcement or correctional agency, including an agency that is not accredited under this part, under a mutual aid agreement, memorandum of understanding, request for assistance, task force arrangement, or other written arrangement authorized by applicable State, local, Tribal, or territorial law.
                                </P>
                                <P>(2) When the requesting or host agency is not accredited under 6 U.S.C. 124n(d)(2), the accredited agency providing C-UAS support is the C-UAS operating agency for purposes of this part and is responsible for compliance with the applicable requirements of this part.</P>
                                <P>(3) Personnel of a non-accredited requesting or host agency may support the operation through ordinary law enforcement, correctional, public safety, evidence-handling, perimeter-security, ground-intercept, evacuation, traffic-control, or incident-command functions. Such personnel may not exercise C-UAS authority under 6 U.S.C. 124n(a)(2), operate systems whose operation requires the authority of or relief from certain laws under 6 U.S.C. 124n, make a credible-threat determination, or initiate any mitigation action, unless those personnel independently satisfy the requirements of this part, hold the applicable certification under § 124.5, and are expressly designated in the accredited C-UAS operating agency's C-UAS Operations Plan to perform that function. Personnel so designated operate under that agency's implementation policy, Agency Approving Official approval, supervision, and compliance responsibility. An individual certification does not, by itself, authorize personnel to exercise 6 U.S.C. 124n(a)(2) authority, and this designation must be established in advance through the C-UAS Operations Plan and the mutual-aid arrangement under paragraph (c)(4) of this section.</P>
                                <P>(4) The written mutual aid arrangement must identify the requesting or host agency, the accredited agency providing C-UAS support, the legal basis for the accredited agency's personnel to operate in the host jurisdiction, the allocation of operational responsibilities, and the handling of C-UAS-derived information consistent with §§ 124.14 and 124.15.</P>
                                <P>(5) For multi-jurisdictional operations, the participating agencies must identify a lead C-UAS agency for tactical C-UAS coordination. The lead C-UAS agency must be an accredited agency unless the operation is conducted under Federal authority pursuant to § 124.19. A non-accredited requesting or host agency may serve as the lead public safety, law enforcement, correctional, or incident-command agency for the overall event or incident, but may not serve as the lead C-UAS agency unless accredited under this part.</P>
                                <P>(6) An accredited agency may enter into standing regional, county, statewide, or other multi-jurisdictional arrangements to provide recurring or on-call C-UAS support to non-accredited agencies. A standing arrangement does not itself authorize a mitigation operation; each mitigation operation remains subject to the applicable requirements of this part.</P>
                                <P>(7) Nothing in this part requires a small, rural, or otherwise resource-limited SLTT law enforcement or correctional agency to acquire C-UAS equipment, obtain accreditation, or establish an independent C-UAS program in order to receive C-UAS support from an accredited agency.</P>
                                <P>
                                    (d) 
                                    <E T="03">Anti-circumvention.</E>
                                     (1) No SLTT law enforcement or correctional agency, officer, employee, contractor, vendor, or other person may structure or use a mutual aid, regional support, managed-service, technical-support, or other 
                                    <PRTPAGE P="41486"/>
                                    arrangement to evade the requirements of this part.
                                </P>
                                <P>(2) Prohibited circumvention includes using an accredited agency as a nominal sponsor while a non-accredited agency, contractor, vendor, or other entity exercises de facto operational control of C-UAS activity requiring the authority of or relief from certain laws under 6 U.S.C. 124n; allowing personnel who lack the certifications required by § 124.5 to exercise C-UAS authority; using systems outside the requirements of § 124.7; avoiding the coordination, reporting, privacy, sensitive-information, or compliance requirements of this part; or acquiring third-party intercepted communications in a manner inconsistent with § 124.14(i).</P>
                                <P>(3) A mutual aid, regional support, statewide support, county support, or multi-jurisdictional C-UAS arrangement is not circumvention merely because the requesting or host agency is not accredited, provided that the C-UAS operating agency is accredited, the personnel exercising C-UAS authority hold the required certifications, and the operation is conducted in compliance with this part.</P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.5 </SECTNO>
                                <SUBJECT>Training and certification.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Training and certification structure.</E>
                                     This section establishes the training and certification structure implementing the requirements of 6 U.S.C. 124n(d)(2)(A). Detection and Warning Certification governs training for detection and warning operations under 6 U.S.C. 124n(b)(1)(A) and (B). Mitigation Certification governs training and certification for mitigation operations under 6 U.S.C. 124n(b)(1)(C), (D), and (F). A current Detection and Warning Certification is a prerequisite both for initial enrollment in the mitigation training course and for mitigation recertification.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Agency implementation policy.</E>
                                     Before conducting any operations under this part, an SLTT law enforcement or correctional agency must adopt an agency implementation policy or detection and warning policy and complete the portal attestation in accordance with § 124.6, and must authorize each operation by a C-UAS Operations Plan in accordance with § 124.8, consistent with the other requirements and obligations of this part and applicable laws and policies.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Detection and Warning Certification.</E>
                                     The Attorney General, acting through the Director of the Federal Bureau of Investigation, will develop and maintain through the NCUTC an online training curriculum for detection and warning operations, accessible through a secure web-based training portal. The curriculum includes the confiscation authority of 6 U.S.C. 124n(b)(1)(E), evidence preservation, and chain of custody. Only those personnel who have completed the curriculum and passed the post-course assessment may exercise the authorities described in 6 U.S.C. 124n(b)(1)(A), (B), and (E). Upon successful completion, the NCUTC training portal automatically issues a Detection and Warning Certification. Detection and Warning Certification is issued only by the NCUTC, and detection and warning training or certification obtained from another agency or a private entity does not satisfy this requirement. Detection and warning activity conducted using systems that do not require the authority of 6 U.S.C. 124n is not subject to this requirement. Upon successful completion, the training portal records the individual's name, agency, date of completion, and certification status in the NCUTC certification database, which is the system of record for all certifications issued under this section. Each agency must maintain a roster of its certified personnel drawn from the NCUTC certification database and must verify the certification status of personnel assigned to C-UAS operations. Vendor-specific and system-level operator training is the responsibility of each agency through its own training procedures and is not part of the detection and warning curriculum.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Mitigation training and certification.</E>
                                     (1) The Attorney General, acting through the Director of the Federal Bureau of Investigation, designates the NCUTC as the national schoolhouse and sole certifying authority for personnel exercising mitigation authorities under 6 U.S.C. 124n(b)(1)(C), (D), and (F), as required by 6 U.S.C. 124n(d)(2)(A)(i). Only personnel who hold a valid Mitigation Certification may exercise these authorities. The NCUTC mitigation training program consists of the mitigation training course and such advanced and supplemental courses as the Attorney General, acting through the Director of the Federal Bureau of Investigation, approves. Each course is evaluated on a pass or fail basis and requires demonstrated proficiency in each mitigation technology category it covers; a person who does not demonstrate proficiency in each category does not pass that course. A person obtains Mitigation Certification by passing the mitigation training course and may extend the scope of that certification to additional mitigation technology categories by passing an advanced or supplemental course covering those additional categories. Failure to pass a particular advanced or supplemental course does not affect the scope of a certification already held.
                                </P>
                                <P>(2) A person who holds a current Mitigation Certification under this paragraph (d) may conduct mitigation operations at a correctional facility. An abbreviated Correctional Mitigation Certification, limited to correctional-facility operations, is available for personnel who will operate only at correctional facilities.</P>
                                <P>(3) The mitigation training course under this paragraph is delivered at the NCUTC. The Attorney General, acting through the Director of the Federal Bureau of Investigation, may authorize the Federal Law Enforcement Training Centers or another qualified Federal training provider to deliver the mitigation training course at one or more additional sites, provided the NCUTC retains approval authority over curriculum and standards, exercises oversight of the delivery, and issues all certifications upon verified completion. Any such authorization is at the sole discretion of the Attorney General, acting through the Director, confers no entitlement on any agency or training provider, and may be modified or withdrawn at any time.</P>
                                <P>
                                    (e) 
                                    <E T="03">Correctional mitigation training and certification.</E>
                                     The NCUTC offers an abbreviated Correctional Mitigation Certification for personnel who will conduct mitigation operations only at correctional facilities. The correctional course of instruction is shorter than the mitigation training course under paragraph (d) of this section because the fixed perimeter and persistent-threat environment of a correctional facility reduce the operational setup and mission-planning instruction required. The correctional course of instruction addresses the persistent-threat environment, perimeter operations, and the legal and safety considerations of correctional settings. A person who holds only the Correctional Mitigation Certification may conduct mitigation operations at a correctional facility but may not conduct other mitigation operations under this part. The NCUTC may arrange for the Federal Law Enforcement Training Centers or another qualified training provider to deliver the correctional curriculum, provided the NCUTC retains approval authority over curriculum and standards, exercises oversight of the delivery, and issues all certifications upon verified completion.
                                </P>
                                <P>
                                    (f) 
                                    <E T="03">Training standards.</E>
                                     The mitigation training course, as administered by the 
                                    <PRTPAGE P="41487"/>
                                    NCUTC, will include instruction on the legal, operational, and technological aspects of C-UAS operations as required by section 8606(b)(1) of the SAFER SKIES Act, including FAA coordination and airspace procedures, spectrum coordination requirements, real-time air traffic control notification procedures, FBI and DHS notification requirements, and the operational use of authorized mitigation technologies. The Attorney General, in coordination with the Secretary of Homeland Security, the Secretary of Defense, the Secretary of Transportation, and the Administrator of the Federal Aviation Administration, will approve training program standards and may approve additional courses of instruction for specialized C-UAS operations. The mitigation training course must include scenario-based instruction on the application of the credible threat standard.
                                </P>
                                <P>
                                    (g) 
                                    <E T="03">Eligible personnel.</E>
                                     Personnel eligible for Mitigation Certification or Detection and Warning Certification must have assigned duties that include the security or protection of people, facilities, or assets, as specified in 6 U.S.C. 124n(a)(2), and must be officers or employees of an SLTT law enforcement or correctional agency accredited by the Attorney General acting through the Director of the Federal Bureau of Investigation. The NCUTC, under the authority of the Attorney General, may establish additional attendance prerequisites.
                                </P>
                                <P>
                                    (h) 
                                    <E T="03">Sufficiency of certification.</E>
                                     Successful completion of the applicable training requirement, combined with the use of systems within technology categories on the Authorized Technologies List and specific systems on the Authorized Systems List where populated, and compliance with the requirements of this part, satisfies the training and certification prerequisites of 6 U.S.C. 124n(d)(2)(A) for the exercise of the corresponding authorities under 6 U.S.C. 124n(a)(2).
                                </P>
                                <P>
                                    (i) 
                                    <E T="03">Suspension.</E>
                                     The Attorney General, acting through the Director of the Federal Bureau of Investigation or the Director's designee, may suspend the Mitigation Certification or Detection and Warning Certification of any individual, or the accreditation of any SLTT law enforcement or correctional agency, for failure to comply with the requirements of this part, violation of the conditions of certification, or for any conduct that demonstrates unfitness to exercise C-UAS authority. Suspension of a certification or accreditation under this section is distinct from suspension of C-UAS authority by the Attorney General or the Secretary of Homeland Security under section 8605(f) of the SAFER SKIES Act, which is addressed in § 124.16. Neither a suspension of certification under this section nor an enforcement action against an individual under section 8605(f) of the SAFER SKIES Act prevents or bars the responsible agency from taking any additional actions it deems necessary to address the circumstances that led to suspension or enforcement action by the Attorney General or designee.
                                </P>
                                <P>
                                    (j) 
                                    <E T="03">Suspension notice.</E>
                                     A suspension will be communicated in writing and will specify the basis for the action and any available remedial steps. The suspension notice must include the factual basis for the action in sufficient detail to enable the affected individual or agency to respond. In exigent circumstances, the Director of the Federal Bureau of Investigation or the Director's designee may immediately suspend a certification or accreditation pending administrative review without the requisite written notice when continued exercise of C-UAS authority poses a risk to aviation safety, public safety, or national security. In such cases, the Director or the Director's designee must provide the requisite notice within 3 days of the suspension.
                                </P>
                                <P>
                                    (k) 
                                    <E T="03">Administrative review.</E>
                                     An individual or agency that receives a suspension notice may request administrative review within 30 calendar days of receipt. The Attorney General, acting through the Director of the Federal Bureau of Investigation, will designate a reviewing official of the Department of Justice who did not participate in or supervise the initial decision. The affected party may submit documentary evidence and written witness statements in support of its response. The reviewing official will consider the written submissions of both parties, may conduct an informal hearing at the reviewing official's discretion, and will issue a written determination within 60 calendar days of receipt of the request, stating the factual findings and the basis for the determination. The reviewing official may affirm the action, modify its terms, impose conditions for reinstatement, or reverse the action. A suspension that is affirmed remains in effect until reinstatement under paragraph (m) of this section or the expiration of the suspended certification or accreditation, whichever occurs first.
                                </P>
                                <P>
                                    (l) 
                                    <E T="03">Conditions.</E>
                                     The Attorney General, acting through the Director of the Federal Bureau of Investigation, may issue a certification or accreditation subject to conditions, and may modify the conditions of a certification or accreditation, consistent with the standards and procedures applicable to suspension under this section.
                                </P>
                                <P>
                                    (m) 
                                    <E T="03">Reinstatement.</E>
                                     An individual or agency whose certification or accreditation has been suspended may apply for reinstatement after completing the remedial steps specified in the suspension notice or the reviewing official's determination. An individual Mitigation Certification may alternatively be reinstated upon the successful recompletion of the full mitigation training course.
                                </P>
                                <P>
                                    (n) 
                                    <E T="03">Transition for previously trained personnel.</E>
                                     Personnel holding a Mitigation Certification issued by the NCUTC before the effective date of this part must complete the detection and warning curriculum under paragraph (c) of this section by September 29, 2026. During that period, the Mitigation Certification remains valid, and the Detection and Warning Certification prerequisite for Mitigation Certification is deemed satisfied. An agency's accreditation is not affected while its personnel complete the curriculum during the transition period.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.6 </SECTNO>
                                <SUBJECT>Agency implementation policy.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Requirement.</E>
                                     Before conducting any operations under this part, each SLTT law enforcement or correctional agency must adopt and maintain an agency implementation policy governing the exercise of authority under 6 U.S.C. 124n(a)(2). The agency implementation policy is comprehensive. It governs all operations the agency conducts under this part, including detection and warning operations, and it addresses the detection and warning matters listed in paragraph (g) of this section. An agency that adopts and maintains an agency implementation policy under this paragraph is not required to adopt a separate policy under paragraph (g) of this section. An agency that conducts only detection and warning operations may instead adopt the abbreviated policy under paragraph (g) of this section. The agency implementation policy must, at a minimum:
                                </P>
                                <P>(1) Designate an Agency Approving Official meeting the requirements of § 124.2;</P>
                                <P>(2) Designate the personnel authorized to exercise C-UAS authority and describe the recurrent training requirements applicable to such personnel;</P>
                                <P>
                                    (3) Establish procedures consistent with § 124.14 for the handling, retention, and dissemination of data acquired during C-UAS operations, including written anonymization standards specifying the aggregation thresholds, identifier suppression, and 
                                    <PRTPAGE P="41488"/>
                                    re-identification risk assessment used to qualify a data product as pattern data;
                                </P>
                                <P>(4) Include provisions for public notification regarding the potential use of C-UAS authority within the agency's jurisdiction;</P>
                                <P>(5) Ensure compliance with the requirements of this part; and</P>
                                <P>(6) Detail standing tactical procedures governing the execution of C-UAS operations, including engagement protocols that account for the risk to persons and property on the surface and in the air before engagement, escalation procedures, use of force considerations, ground intercept team procedures, render safe procedures, evidence collection and chain-of-custody procedures, communications procedures, system operating procedures, data handling and purge procedures consistent with the retention requirements of this part, operation plan requirements, and post-operation procedures that incorporate data purge verification.</P>
                                <P>
                                    (b) 
                                    <E T="03">Legal counsel review.</E>
                                     The implementation policy must be reviewed and concurred in by the agency's legal counsel before adoption and upon each annual renewal. The review must specifically address the privacy and civil liberties requirements of this part, including the data retention, minimization, and dissemination provisions, and the interplay of proposed C-UAS operations and implementing policies with applicable State, local, Tribal, or territorial law. For an agency that has a designated official responsible for the agency's privacy and civil liberties compliance, regardless of title, the implementation policy must also be reviewed by that official.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Alternative certification for agencies without in-house counsel.</E>
                                     For an agency without in-house counsel, the review required by paragraph (b) of this section may alternatively be satisfied by review and certification by a State, local, territorial, or Tribal attorney's office that the implementation policy addresses each element required by paragraph (a) of this section. An agency obtaining a certification under this paragraph (c) must document the basis for using this paragraph (c). Certification pursuant to this paragraph (c) does not relieve the agency of any compliance obligation under this part.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Portal attestation.</E>
                                     Upon adoption of the implementation policy, the agency head or designee must certify compliance through the Federal C-UAS coordination portal by attesting that the agency has adopted an implementation policy addressing each element required by paragraph (a) of this section. The portal records the certifying official, agency, and date of attestation. The implementation policy is not subject to pre-approval by the NCUTC. The NCUTC retains authority to audit implementation policies and to suspend certification or accreditation under § 124.5. The attestation must be renewed annually.
                                </P>
                                <P>
                                    (e) 
                                    <E T="03">Retention and availability.</E>
                                     The agency must retain the implementation policy and make it available to the Attorney General or the Secretary of Homeland Security, or their designee, upon request, including during compliance audits under § 124.16.
                                </P>
                                <P>
                                    (f) 
                                    <E T="03">Operating without attestation.</E>
                                     An agency that conducts operations under this part without a current portal attestation is in violation of this part, and the absence of an attestation constitutes grounds for compliance action under § 124.16.
                                </P>
                                <P>
                                    (g) 
                                    <E T="03">Detection and warning policy.</E>
                                     An SLTT law enforcement or correctional agency that conducts only detection and warning operations requiring the authority of, or the relief from certain laws provided by, 6 U.S.C. 124n may adopt a detection and warning policy in lieu of the implementation policy required by paragraph (a) of this section. A detection and warning policy must satisfy the requirements of this section, except that it need not include the standing tactical procedures of paragraph (a)(6) of this section. The agency must designate an Agency Approving Official under paragraph (a)(1) of this section and complete the portal attestation under paragraph (d) of this section, which must be renewed annually. For purposes of that attestation, a detection and warning policy need address only the elements of paragraph (a) of this section that apply to detection and warning operations.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.7 </SECTNO>
                                <SUBJECT>Authorized technologies.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Two-list authorization framework.</E>
                                     The technology authorization framework consists of two complementary lists. The Authorized Technologies List identifies the technology categories authorized for SLTT law enforcement and correctional agency C-UAS operations. The Authorized Systems List identifies specific systems, at the make and model level, that have completed interagency evaluation within those technology categories and stated operating restrictions. Both lists are maintained jointly by the Department of Justice, the Department of Homeland Security, the Department of Defense, the Department of Transportation and Federal Aviation Administration, the Federal Communications Commission, and the National Telecommunications and Information Administration, consistent with 6 U.S.C. 124n(d)(2)(A)(iii) and section 8606(a)(4) of the SAFER SKIES Act.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">General requirement.</E>
                                     An SLTT law enforcement or correctional agency exercising authority under 6 U.S.C. 124n(a)(2) may deploy only systems within technology categories listed on the Authorized Technologies List. When the Authorized Systems List has been populated for a given technology category, the agency may deploy only specific systems listed on the Authorized Systems List within that category, subject to the advance coordination requirements of § 124.9. For technology categories on the Authorized Technologies List for which the Authorized Systems List has not yet been populated, the agency may deploy specific systems within those categories provided that an operator holds Mitigation Certification covering that technology category and has completed manufacturer or vendor training on the specific system to be deployed, subject to the advance coordination requirements of § 124.9.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Scope of the list requirement.</E>
                                     When operating under the authorities or statutory reliefs in 6 U.S.C. 124n(a)(2), SLTT law enforcement or correctional agencies may employ only listed technology categories, and, where the Authorized Systems List is populated, listed systems. Technology that an SLTT law enforcement or correctional agency may lawfully employ without the authorities or reliefs provided by 6 U.S.C. 124n(a)(2) is not subject to the requirements of this section and remains available to agencies on the same basis as before the SAFER SKIES Act. The detection and warning training curriculum will address the distinction between technology categories subject to and not subject to this section.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Mitigation technology and training alignment.</E>
                                     An SLTT law enforcement or correctional agency may employ mitigation systems only in those technology categories covered by the NCUTC mitigation courses completed by its mitigation-certified personnel. NCUTC may create an additional mitigation module covering the technology category when a new technology category is added to the Authorized Technologies List. Mitigation-certified personnel who completed the NCUTC mitigation course prior to the addition of this new content must successfully complete additional NCUTC training on the new technology category prior to using any system on the Authorized Systems List under that category.
                                    <PRTPAGE P="41489"/>
                                </P>
                                <P>
                                    (e) 
                                    <E T="03">Scope of interception authority.</E>
                                     Systems may be used to intercept communications to or from an unmanned aircraft or UAS only to the extent necessary to support an action described in 6 U.S.C. 124n(b)(1). Any interception, acquisition, maintenance, use of, or access to communications to or from an unmanned aircraft or UAS under this section must be conducted in a manner consistent with the First and Fourth Amendments to the Constitution of the United States and applicable provisions of Federal law.
                                </P>
                                <P>
                                    (f) 
                                    <E T="03">Maintenance of the lists.</E>
                                     The Authorized Technologies List and Authorized Systems List, including the criteria and procedures for evaluating, listing, renewing, suspending, and removing technology categories and systems, are established and maintained through the interagency process described in 6 U.S.C. 124n(d)(2)(A)(iii) and section 8606(a)(4) of the SAFER SKIES Act. The Authorized Systems List is updated by that interagency process and published on the designated interagency C-UAS portal. Each RF-emitting system listed on the Authorized Systems List will have completed a system-level spectrum evaluation through the interagency process before listing, addressing potential interference with non-Federal spectrum users, compatibility with Federal spectrum users, and potential interference with aviation safety systems. System-level evaluations are reviewed and renewed at intervals determined through the interagency process and upon any system change to its operating capabilities, functions, radio frequency characteristics, or power levels that may alter its radio frequency characteristics, capabilities, functions, or assessed configurations. Minor updates that do not alter a system's performance, capabilities, functions, radio frequency characteristics, or assessed configurations do not require renewed evaluation.
                                </P>
                                <P>
                                    (g) 
                                    <E T="03">Emergency suspension.</E>
                                     Upon receipt of an emergency suspension notice issued through the interagency process for the Authorized Technologies List and Authorized Systems List, an SLTT law enforcement or correctional agency must immediately cease deployment of the affected system or technology category. Grounds for emergency suspension include discovery of a critical safety defect, identification of a supply chain compromise or cybersecurity vulnerability, a determination that a system's radio frequency characteristics differ materially from those evaluated during spectrum evaluation, or a finding by any agency participating in the interagency process that continued deployment poses an unacceptable risk. The SLTT law enforcement or correctional agency may not resume deployment of the affected system or technology category until the suspension is lifted or the system or category is restored to the applicable list, and the agency must comply with any conditions attached to the lifting of the suspension or the restoration of the system or category to the applicable list.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.8 </SECTNO>
                                <SUBJECT>C-UAS Operations Plan.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Requirement and function.</E>
                                     Each mitigation operation, and each detection and warning operation conducted under this part using systems that require the authority of, or relief from certain laws under, 6 U.S.C. 124n, must be authorized by a C-UAS Operations Plan signed by the agency's Agency Approving Official. Section 124.12 sets out the conditions specific to detection and warning operations. The signed C-UAS Operations Plan is the instrument authorizing the operation on behalf of the SLTT law enforcement or correctional agency and certifies that the operation is consistent with the agency's implementation or detection and warning policy, that the operators are agency personnel who hold the required training and certification, and that the risk-based assessment factors of paragraph (e) of this section have been addressed. The agency may not commence mitigation operations until both the advance coordination process under § 124.9 and the signed C-UAS Operations Plan are complete.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Legal counsel certification.</E>
                                     The C-UAS Operations Plan must include a certification by the agency's legal counsel or, for an agency without in-house counsel, the applicable prosecuting authority, that the plan has been reviewed for legal sufficiency. The certification may take the form of a signature block, stamp, or attestation on the plan.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Form.</E>
                                     The C-UAS Operations Plan must be prepared on the standardized form prescribed by the Attorney General. The form is structured to use short-answer fields, selection-based fields, and map or diagram attachments, and does not require narrative legal analysis or repetition of standing procedures addressed in the agency's implementation policy. The form may use conditional fields keyed to the type of operation, so that each operation completes only the fields applicable to it; for a detection and warning operation, the fields specific to mitigation, such as mitigation-system parameters and render safe planning, do not apply.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Content.</E>
                                     The C-UAS Operations Plan must address, at a minimum and to the extent applicable to the operation:
                                </P>
                                <P>(1) Operation identification, including the submitting agency, points of contact, the Agency Approving Official, the operation type, planned dates, geographic location, venue type, any Special Event Assessment Rating or National Special Security Event designation, and the identification of any mutual aid agencies;</P>
                                <P>(2) Systems and airspace, including the systems to be deployed by reference to the Authorized Systems List or Authorized Technologies List category; a description of each system's configuration and the hardware version, firmware revision, and software version of each system as deployed; RF-emitting system parameters; class of airspace; and anticipated flight restrictions;</P>
                                <P>(3) Coordination confirmation, including operator certification status, compliance with the agency implementation policy, the legal counsel certification, and compliance with the privacy and civil liberties requirements of this part; and</P>
                                <P>(4) Operational planning elements, including deployment configuration and spectrum deconfliction, personnel and team assignments, render safe and contingency planning, known authorized manned and unmanned aviation and deconfliction processes and procedures, communications, investigative response and data handling, and demobilization.</P>
                                <P>
                                    (e) 
                                    <E T="03">Risk-based assessment.</E>
                                     The C-UAS Operations Plan must address the following factors: potential impacts to aviation safety, civilian aviation and aerospace operations, aircraft airworthiness, or the use of the airspace; procedures to comply with any technical and siting limitations; options for mitigating identified potential impacts; potential consequences if potential impacts are not mitigated; the ability to provide reasonable advance notice to aircraft operators of both manned and unmanned aircraft; the setting and character of the facility or asset; for National Special Security Events and Special Event Assessment Rating events, the event characteristics; and the potential consequences to public safety if UAS threats are not mitigated. For National Special Security Events and Special Event Assessment Rating events, a plan that identifies the systems, airspace environment, and coordination elements from which the assessment can be derived satisfies this paragraph without separately addressing each factor in narrative form. Nothing in 
                                    <PRTPAGE P="41490"/>
                                    this part may be interpreted as limiting the authority of the Administrator of the Federal Aviation Administration to manage the navigable airspace, assess potential aviation safety risks, and implement such mitigations as the Administrator determines appropriate.
                                </P>
                                <P>
                                    (f) 
                                    <E T="03">Timing and submission.</E>
                                     The C-UAS Operations Plan must be completed before the commencement of operations and submitted to the Federal Bureau of Investigation and Department of Homeland Security through the designated Federal C-UAS coordination portal as a supplement to the advance notification not fewer than 7 calendar days before the commencement of operations, or as early as practicable when the applicable notification timeline does not permit 7 calendar days. For a detection and warning operation that is not subject to the advance notification requirement of § 124.9, the C-UAS Operations Plan must be submitted through the designated Federal C-UAS coordination portal before the commencement of operations, for situational awareness and recordkeeping; such submission is not an advance notification under § 124.9 and does not trigger Federal Aviation Administration or Federal Communications Commission coordination. The plan may be updated after submission to reflect changes resulting from Federal Aviation Administration or Federal Communications Commission coordination. Material updates must be resubmitted promptly. Federal Aviation Administration and Federal Communications Commission coordination is valid for the system configuration and the firmware and software version coordinated for the operation. A change in configuration, firmware, or software version does not require re-coordination if it does not materially change the system's radio frequency emission characteristics, its operating frequencies and power levels, or other factors potentially impacting aviation safety from those previously coordinated. A change that would operate outside the frequencies or power levels coordinated for the operation requires re-coordination before deployment; a summary of the change must be provided to the Federal Aviation Administration and Federal Communications Commission to determine if re-coordination is necessary. The Federal Aviation Administration and the Federal Communications Commission may identify by guidance categories of configuration, firmware, or software changes that are deemed to materially affect radio frequency emission characteristics and require re-coordination. Federal review of the C-UAS Operations Plan is for deconfliction and situational awareness purposes and does not constitute approval or disapproval of the operation. For an event, area, or period in which a high volume of simultaneous operations is anticipated, the Federal Bureau of Investigation, in coordination with the Federal Aviation Administration, may establish an earlier submission deadline for affected operations and will communicate that deadline to affected agencies in advance through the designated portal or the lead C-UAS agency.
                                </P>
                                <P>
                                    (g) 
                                    <E T="03">Relationship to implementation policy.</E>
                                     The C-UAS Operations Plan is an event-specific or operation-specific document. Standing tactical procedures required by § 124.6(a) must be addressed in the agency's implementation policy, and the C-UAS Operations Plan must reference the implementation policy by title and version rather than repeating standing procedures.
                                </P>
                                <P>
                                    (h) 
                                    <E T="03">Operational windows.</E>
                                     (1) An individual C-UAS Operations Plan may authorize operations for a period not to exceed 30 consecutive calendar days, except as provided in paragraph (h)(2) of this section. For operations requiring a longer duration, the agency must submit a renewal plan before the expiration of the current operational window; the renewal plan may incorporate the prior plan by reference and address only material changes. The agency must submit a renewal plan, through the designated Federal C-UAS coordination portal under § 124.8(f), before the expiration of the current operational window.
                                </P>
                                <P>(2) For fixed-site facilities for which SLTT law enforcement and correctional agencies conduct ongoing persistent-protection operations, including correctional facilities, critical infrastructure sites, other permanent facilities with a continuing C-UAS mission, and venues where the agency expects to provide recurring C-UAS coverage within the authorization period, the Agency Approving Official may authorize a standing operational window of up to 365 calendar days, renewable upon submission of a renewal plan. The advance notification for a standing operational window must specify the venue and anticipated events or coverage periods; for a detection and warning operation not subject to the advance notification requirement of § 124.9, the C-UAS Operations Plan must specify the venue, the area covered, which may be stated as a radius around the site, and the anticipated coverage periods. Material changes, including a new event, new systems, or a changed threat environment, require an update to the advance notification under § 124.9(a) or, for such a detection and warning operation, an updated C-UAS Operations Plan. Federal coordination requirements continue to apply to each event within a standing window, including lead C-UAS agency coordination under § 124.10 and per-event coordination among the Department of Transportation, the Federal Aviation Administration, and the Federal Communications Commission.</P>
                                <P>(3) No C-UAS Operations Plan may authorize an indefinite or open-ended operational window.</P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.9 </SECTNO>
                                <SUBJECT>Advance coordination, notification, and authorization.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Advance notification.</E>
                                     (1) Before conducting any mitigation operation under 6 U.S.C. 124n(a)(2), an SLTT law enforcement or correctional agency must submit an advance notification through the designated Federal C-UAS coordination portal not fewer than 30 calendar days before the commencement of the operational period. When 30 calendar days is not feasible, the agency must submit the advance notification as early as the circumstances permit, with sufficient lead time to allow the Federal Bureau of Investigation, the Department of Homeland Security, the Department of Transportation, the Federal Aviation Administration, and the Federal Communications Commission to complete their respective reviews, and must include a brief explanation of the circumstances that prevented submission within the 30-day standard.
                                </P>
                                <P>(2) The advance notification is a coordination document that routes the relevant data elements to each recipient agency through a single submission. The advance notification is not a request for approval by the Department of Justice or the Department of Homeland Security, and the absence of a response from the Department of Justice or the Department of Homeland Security does not affect the agency's authority to proceed.</P>
                                <P>
                                    (3) The advance notification must identify the submitting SLTT law enforcement or correctional agency, the planned dates and geographic location of the operation, the systems to be deployed by reference to the Authorized Systems List or Authorized Technologies List category, RF-emitting system parameters, a characterization of the airspace and operational environment, and confirmation of 
                                    <PRTPAGE P="41491"/>
                                    operator certification status and compliance with the agency implementation policy and the privacy requirements of this part.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">C-UAS Operations Plan.</E>
                                     Each mitigation operation must also be authorized by a C-UAS Operations Plan in accordance with § 124.8. The agency may not commence mitigation operations until both the advance coordination process under this section and the signed C-UAS Operations Plan are complete. The SLTT law enforcement or correctional agency must also submit a comparable advance notification to the State if required by State law or policy.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">FBI and DHS notification and routing.</E>
                                     The Attorney General, through the Federal Bureau of Investigation and the Department of Homeland Security, receives the advance notification for purposes of deconflicting planned SLTT law enforcement or correctional agency C-UAS operations with any ongoing or planned Federal C-UAS, law enforcement, or national security operations. Until the portal is fully established, an SLTT law enforcement or correctional agency must notify the Federal Bureau of Investigation and Department of Homeland Security through a channel designated by the Federal Bureau of Investigation and Department of Homeland Security for that purpose.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">DOT/FAA coordination.</E>
                                     Before conducting any mitigation operation, an SLTT law enforcement or correctional agency must coordinate with the Department of Transportation and the Federal Aviation Administration through the coordination mechanism the Federal Aviation Administration has designated. The agency must provide the systems to be deployed, the geographic coordinates of each proposed deployment and enforcement location, the expected duration of the operation, and a characterization of the airspace environment. The Administrator of the Federal Aviation Administration may establish such flight restrictions as the Administrator determines necessary in his sole discretion for reasons of aviation safety. The absence of a formal flight restriction does not preclude mitigation action in exigent circumstances when a credible threat exists and the requirements of this part are otherwise satisfied.
                                </P>
                                <P>
                                    (e) 
                                    <E T="03">Categorical FAA determinations.</E>
                                     The Federal Aviation Administration may issue categorical determinations for specific combinations of authorized technologies, geographic locations, and airspace environments. When a proposed mitigation operation falls within the parameters of a categorical determination by the Federal Aviation Administration, individual case-by-case Federal Aviation Administration coordination is not required, provided the agency operates within the conditions specified in the determination and notifies the Federal Aviation Administration through the Federal Aviation Administration-designated coordination mechanism.
                                </P>
                                <P>
                                    (f) 
                                    <E T="03">FCC authorization.</E>
                                     Before deploying any C-UAS system (whether detection and warning only or mitigation) that involves the emission of radio waves, an SLTT law enforcement or correctional agency must obtain authorization to use that system consistent with Title III of the Communications Act of 1934, as amended. The system must comply with any relevant regulations, policies, and guidance administered by the Federal Communications Commission, and an SLTT law enforcement or correctional agency must submit a request to the Federal Communications Commission through the advance notification process and as directed by the Federal Communications Commission. The Federal Communications Commission will also issue waivers, as appropriate, to C-UAS equipment vendors and manufacturers to allow them to import and sell C-UAS mitigation equipment that employs radio frequency interdiction technologies or electronic counter measures to authorized SLTT law enforcement and correctional agencies.
                                </P>
                                <P>
                                    (g) 
                                    <E T="03">Emergency exception.</E>
                                     When a credible threat poses an imminent risk to human life and advance coordination under this section is not practicable, an SLTT law enforcement or correctional agency may take mitigation action. The agency must complete the notifications required by this section as soon as practicable, and in any event within two hours of the action. If the mitigation action involves an RF-emitting C-UAS system, the agency must additionally comply with the real-time notification requirements of § 124.11. Each invocation of this exception must be documented in the post-operation report with a specific explanation of why advance coordination was not feasible. This exception may not be invoked as a routine alternative to advance coordination, and a pattern of repeated invocations may result in compliance review under § 124.16, accreditation or certification suspension, and penalties under section 8605(f) of the SAFER SKIES Act. The compliance audit program will establish the criteria for identifying patterns of emergency invocations that warrant review.
                                </P>
                                <P>
                                    (h) 
                                    <E T="03">Federal coordination.</E>
                                     Before conducting any operation under this part within a security or protection mission overseen by a Federal Government entity, or within an area, facility, waterway, or other area over which a Federal Government entity exercises a security or protection responsibility, the agency must coordinate with that Federal Government entity through the advance coordination process under § 124.9 before conducting the operation. The Federal Aviation Administration's general regulatory authority over the navigable airspace does not by itself trigger this requirement; airspace safety coordination is addressed in § 124.8 and § 124.11.
                                </P>
                                <P>
                                    (i) 
                                    <E T="03">Detection and warning operations.</E>
                                     Detection and warning operations that do not actively transmit radio frequency energy and do not affect aviation safety are not subject to the advance coordination requirements of this section.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.10 </SECTNO>
                                <SUBJECT>Interagency and lead-agency coordination.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Early coordination and notice of intent.</E>
                                     For operations in support of National Special Security Events, events rated Special Event Assessment Rating 1 through 3, or other events where Federal C-UAS operations are anticipated, an SLTT law enforcement or correctional agency should notify the local FBI field office of its intent to provide C-UAS coverage as early as practicable and before the 30-day advance notification standard of § 124.9. The designated Federal C-UAS coordination portal includes a notice-of-intent function that allows an agency to register its intent to cover a future event without completing the full advance notification. A notice of intent is informational only and does not trigger the advance coordination process, the Federal Aviation Administration or Federal Communications Commission review, or any timeline obligation.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Special event coordination.</E>
                                     When the Federal Bureau of Investigation receives an SLTT law enforcement or correctional agency advance notification or notice of intent for an event at which Federal C-UAS operations are also planned or under consideration, the Federal Bureau of Investigation will present the notification to the interagency C-UAS coordination process maintained by the Department of Justice and the Department of Homeland Security, will serve as the conduit for SLTT law enforcement and correctional agency equities in that process, and will communicate the results to the SLTT law enforcement or 
                                    <PRTPAGE P="41492"/>
                                    correctional agency, including any Federal operational parameters or deconfliction requirements that may affect the SLTT law enforcement or correctional agency C-UAS operation. The interagency coordination process does not approve or disapprove SLTT law enforcement or correctional agency C-UAS operations.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Tactical coordination under a lead C-UAS agency.</E>
                                     An SLTT law enforcement or correctional agency conducting C-UAS operations at an event or location for which a lead C-UAS agency has been designated must operate under the tactical coordination of the lead C-UAS agency for the duration of the event. Tactical coordination includes the assignment of system deployment locations, operating frequencies, detection and mitigation sectors, ground intercept team sectors, render safe locations, communications channels, and risk to persons and property on the surface or in the air. The SLTT law enforcement or correctional agency's C-UAS Operations Plan for the event must be developed in coordination with the lead C-UAS agency and must conform to the lead agency's overall C-UAS operational framework for the event. An SLTT law enforcement or correctional agency coordinating with a lead C-UAS agency acts under its own certified authority under 6 U.S.C. 124n(a)(2); tactical coordination merely integrates the SLTT law enforcement or correctional agency C-UAS operation into a unified C-UAS posture. Where geographic responsibilities are divided among multiple Federal agencies, the SLTT law enforcement or correctional agency must coordinate with the sector-level lead Federal agency responsible for the geographic area in which the SLTT law enforcement or correctional agency intends to operate. Whenever Federal and SLTT operations will be conducted at the same event, or whenever the Federal and SLTT operations will overlap in geographic area and time, the Federal agency will be the lead C-UAS agency. An SLTT law enforcement or correctional agency may serve as the lead C-UAS agency only where multiple SLTT agencies are operating in the same area and no Federal agency is involved.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Coordination required.</E>
                                     An SLTT law enforcement or correctional agency that does not accept tactical coordination by the designated lead C-UAS agency may not conduct C-UAS operations, including detection and warning operations using systems requiring the authority of and relief from certain laws under the Act, within the geographic area and time period covered by the lead-agency designation.
                                </P>
                                <P>
                                    (e) 
                                    <E T="03">Overlapping SLTT operations.</E>
                                     When the Federal Bureau of Investigation and Department of Homeland Security receive advance notifications from two or more SLTT law enforcement or correctional agencies for C-UAS operations that overlap in geographic area and time, the Federal Bureau of Investigation and Department of Homeland Security will notify all affected SLTT law enforcement and correctional agencies of the overlap. The affected agencies must designate a lead C-UAS agency for the overlapping area and time period, or establish a joint operational coordination arrangement, before any agency commences mitigation operations in the overlapping area. The designation or arrangement must be documented and provided to the Federal Bureau of Investigation and Department of Homeland Security. If the agencies cannot reach agreement within 48 hours of the Federal Bureau of Investigation and Department of Homeland Security's notification, the Federal Bureau of Investigation and Department of Homeland Security may designate operational parameters for the overlapping area, including frequency deconfliction assignments and geographic boundaries for each agency's mitigation operations.
                                </P>
                                <P>
                                    (f) 
                                    <E T="03">Deconfliction direction.</E>
                                     If the deconfliction process identifies a conflict between a planned SLTT law enforcement or correctional agency C-UAS operation and an ongoing or planned Federal C-UAS, law enforcement, or national security operation that cannot be resolved through coordination, the Department of Justice, acting through the Federal Bureau of Investigation and in coordination with the Department of Homeland Security, may direct the SLTT law enforcement or correctional agency to modify the operational parameters of, or postpone, the planned operation until the conflict is resolved.
                                </P>
                                <P>
                                    (g) 
                                    <E T="03">Emergency exception preserved.</E>
                                     This section does not affect an SLTT agency's authority to respond to an imminent risk to human life under § 124.9(g), including at an event with a designated lead C-UAS agency; however, the agency must notify the lead C-UAS agency immediately upon taking emergency action and must coordinate with the lead agency as soon as practicable thereafter.
                                </P>
                                <P>(h) The requirements in paragraphs (a) through (g) of this section are established under the Attorney General's oversight authority pursuant to 6 U.S.C. 124n(d)(1) and the coordination obligations of 6 U.S.C. 124n(b)(4) and (d)(3); they do not transfer or diminish the SLTT agency's statutory authority and relief from certain laws under 6 U.S.C. 124n(a)(2).</P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.11 </SECTNO>
                                <SUBJECT>Real-time air traffic control notification.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Notification required.</E>
                                     Any SLTT law enforcement or correctional agency, or its personnel, that activates a C-UAS system for mitigation purposes must, within five minutes of activation or as soon as operationally practicable, provide verbal or electronic notification to the notification point designated by the Federal Aviation Administration for real-time C-UAS coordination, using the procedures established under paragraph (b) of this section. Detection and warning operations do not require notification or coordination under this section.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Notification procedures.</E>
                                     An SLTT law enforcement or correctional agency must comply with the notification and reporting procedures jointly established by the Department of Homeland Security, the Department of Justice, and the Federal Aviation Administration for real-time communication to air traffic control of C-UAS mitigation actions using a radio frequency-emitting C-UAS system. The notification must identify the type of C-UAS action, the time of activation, and the location. The NCUTC will include training on these notification procedures in the mitigation training course.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Notification upon termination.</E>
                                     Upon termination of the mitigation action, the SLTT law enforcement or correctional agency must provide a follow-up notification to the designated Federal Aviation Administration notification point confirming the time of termination.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Non-RF mitigation.</E>
                                     Mitigation actions that do not involve radio frequency-emitting systems do require notification under this section unless the Department of Transportation or Federal Aviation Administration's applicable notification procedures established under this section provide otherwise. Such actions remain subject to the advance coordination and post-operation reporting requirements of §§ 124.9 and 124.13.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.12 </SECTNO>
                                <SUBJECT>Detection and warning operations.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Scope.</E>
                                     This section governs detection and warning operations using systems whose operation requires the authority of and relief from certain laws under 6 U.S.C. 124n(a)(2). Detection and warning activity conducted using systems that do not require the authority 
                                    <PRTPAGE P="41493"/>
                                    of the Act or the relief it provides from certain laws is not subject to this part.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Conditions.</E>
                                     An SLTT law enforcement or correctional agency may conduct detection and warning operations under this section if:
                                </P>
                                <P>(1) All personnel conducting detection and warning operations hold a current Detection and Warning Certification;</P>
                                <P>(2) The agency deploys only systems within technology categories listed on the Authorized Technologies List and, where populated, specific systems listed on the Authorized Systems List;</P>
                                <P>(3) The agency has adopted an implementation policy under § 124.6(a) or a detection and warning policy under § 124.6(g), has completed the applicable portal attestation, and has authorized the operation by a C-UAS Operations Plan under § 124.8; and</P>
                                <P>(4) The agency complies with the privacy, data handling, and retention requirements of § 124.14.</P>
                                <P>
                                    (c) 
                                    <E T="03">Coordination.</E>
                                     No per-operation (that is, for each individual deployment or activation of a C-UAS system) advance notification, Federal Aviation Administration coordination, or Federal Communications Commission coordination is required for detection and warning operations that employ only systems that do not emit radio frequency energy and do not affect aviation safety. Such operations must be authorized by a C-UAS Operations Plan under § 124.8, which documents operational authority, data handling and retention, and legal review. For detection and warning operations involving RF-emitting systems, such as active warning broadcast systems, the advance coordination requirements of § 124.9 apply, and the operation must be authorized by a C-UAS Operations Plan under § 124.8.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Reporting.</E>
                                     The 48-hour reporting requirement of § 124.13 does not require per-event reporting of detection and warning operations. Each SLTT law enforcement or correctional agency conducting detection and warning operations under this section must report detection activity in the semiannual operational summary required by § 124.13, including the detection systems deployed by Authorized Technologies List category, the locations at which systems were deployed, the total number of detection events recorded, instances of retention of records of communication beyond 180 days, and any data-sharing arrangements. A physical seizure or confiscation under 6 U.S.C. 124n(b)(1)(E) that results from a detection and warning operation is a 6 U.S.C. 124n action, but it is documented through the agency's normal evidence-handling procedures and is not separately reported under this part. The recovery of a crashed or abandoned unmanned aircraft that does not involve the use of 6 U.S.C. 124n authority is not a 6 U.S.C. 124n confiscation and is not subject to the reporting requirements of this part.
                                </P>
                                <P>
                                    (e) 
                                    <E T="03">Prohibition on mitigation.</E>
                                     Personnel holding only a Detection and Warning Certification are not authorized to take any mitigation action or any other action that affects an unmanned aircraft in flight, regardless of the operator's ultimate objective. If a detection operation identifies a credible threat requiring mitigation, this rule requires that the agency respond through mitigation-certified personnel operating under §§ 124.8 and 124.9 or through coordination with Federal C-UAS assets. This prohibition is absolute and is not subject to the emergency exception of § 124.9(g), which is available only to an agency with mitigation-certified personnel and authorized mitigation capability.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.13 </SECTNO>
                                <SUBJECT>Post-operation reporting.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Report required.</E>
                                     Any SLTT law enforcement or correctional agency exercising authority under 6 U.S.C. 124n(a)(2) must submit a post-operation report as required by 6 U.S.C. 124n(d)(2)(C)(i) within 48 hours of whichever occurs first:
                                </P>
                                <P>(1) Taking any mitigation action described in 6 U.S.C. 124n(b)(1)(C), (D), or (F);</P>
                                <P>(2) Any confiscation of an unmanned aircraft or UAS under 6 U.S.C. 124n(b)(1)(E); or</P>
                                <P>(3) The conclusion of an operation where notification was provided.</P>
                                <P>
                                    (b) 
                                    <E T="03">Other confiscations.</E>
                                     A confiscation that does not occur pursuant to 6 U.S.C. 124n(b)(1)(E) may be documented through the agency's normal evidence-handling procedures and does not need to be separately reported under this part.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Content.</E>
                                     The post-operation report must contain:
                                </P>
                                <P>(1) Confirmation whether the planned operation did or did not occur as notified;</P>
                                <P>(2) The date, time, and geographic location of the reportable action;</P>
                                <P>(3) A brief description of the credible threat that a UAS or unmanned aircraft posed to the safety or security of people, a facility, or an asset; a venue or set of venues used for large-scale public gatherings or events; critical infrastructure; or a correctional facility necessitating the action;</P>
                                <P>(4) The type of capability employed, including the specific system or systems used by reference to the Authorized Systems List and Authorized Technologies List category, or where the Authorized Systems List had not yet been populated for a particular Authorized Technologies List category at the time of the action, the Authorized Technologies List category; and in all cases the make, model, hardware version, firmware revision, and software version of the system or systems as deployed;</P>
                                <P>(5) Any known operational effects, including the seizure, disabling, damage, or destruction of a UAS or unmanned aircraft; any reported effects on other aviation systems, spectrum users, or persons and property on the surface or in the air; any aviation accident; whether a temporary flight restriction was granted or denied; and any other harm, damage, or loss to a person or to private property;</P>
                                <P>(6) Any issues, anomalies, or deviations encountered during the operation; and</P>
                                <P>(7) Summary operational statistics, including the number of UAS detected, counted as confirmed detections attributable to a distinct unmanned aircraft and reported in good faith with reasonable deduplication; warnings issued; mitigation actions taken; UAS or unmanned aircraft seized or confiscated; and any criminal charges, citations, regulatory enforcement actions, or arrests resulting from the operation.</P>
                                <P>
                                    (d) 
                                    <E T="03">Submission mechanism.</E>
                                     Reports must be submitted through the designated Federal C-UAS coordination portal. Submission through the portal satisfies the notification requirement to both the Attorney General and the Secretary of Homeland Security, as the portal routes reports to the Federal Bureau of Investigation and Department of Homeland Security automatically.
                                </P>
                                <P>
                                    (e) 
                                    <E T="03">Immediate notification for unintended consequences.</E>
                                     If a detection, warning, or mitigation action results in unintended consequences, including interference with manned aviation or lawfully operating UAS, property damage, injury, or system malfunction affecting third parties, the SLTT law enforcement or correctional agency must immediately notify the Federal Bureau of Investigation and Department of Homeland Security by the most expedient means available, in addition to the 48-hour post-operation report. The Federal Bureau of Investigation will notify the Office of the Deputy Attorney General, the Department of Transportation, the Federal Aviation Administration, the Federal Communications Commission, and other affected agencies as appropriate.
                                    <PRTPAGE P="41494"/>
                                </P>
                                <P>
                                    (f) 
                                    <E T="03">Consolidated reporting.</E>
                                     Where multiple reportable events occur within a 48 hour period, an SLTT law enforcement or correctional agency may submit a single consolidated post-operation report covering all actions taken during the period, due within 48 hours of the first reportable event, provided that each action is documented with the data elements required by paragraph (c) of this section and that any action resulting in unintended consequences is reported immediately under paragraph (e) of this section.
                                </P>
                                <P>
                                    (g) 
                                    <E T="03">Recurring venue reporting.</E>
                                     For recurring venue operations conducted under a standing operational window authorized by § 124.8(h), each discrete event within the authorization period must be reported separately.
                                </P>
                                <P>
                                    (h) 
                                    <E T="03">Semiannual operational summary.</E>
                                     Each SLTT law enforcement or correctional agency exercising authority under this part must submit a semiannual operational summary through the designated Federal C-UAS coordination portal, covering total operations conducted, mitigation actions taken, detection activity, instances of retention of records of communication beyond 180 days, instances in which control communications were disclosed outside the originating agency organized by the legal basis for their disclosure, compliance issues identified, and lessons learned. The summary must also report the requests the agency received for C-UAS protection from critical infrastructure or airport owners or operators that are not SLTT law enforcement or correctional agencies, the number of those requests to which it provided protection, and the number it was unable to support as well as the reasons it was unable to provide support.
                                </P>
                                <P>
                                    (i) 
                                    <E T="03">Reporting to support congressional and oversight requirements.</E>
                                     The Federal Bureau of Investigation will compile information from post-operation reports and semiannual summaries to support the biannual report required by 6 U.S.C. 124n(d)(2)(D) and the semiannual briefings required by 6 U.S.C. 124n(g), in coordination with the Secretary of Homeland Security and the Secretary of Transportation. The compilation will include:
                                </P>
                                <P>(1) The frequency, location, and circumstances of SLTT law enforcement and correctional agencies' mitigation deployments and the types of mitigation employed;</P>
                                <P>(2) A list of any aviation security or safety incidents, and any aviation accidents, that occurred due to SLTT law enforcement and correctional agencies' deployment of C-UAS technologies;</P>
                                <P>(3) Recommendations for improving SLTT law enforcement and correctional agencies' C-UAS training, oversight, compliance, and execution, and the compliance audits required by section 8606(b)(2) of the SAFER SKIES Act; and</P>
                                <P>(4) A determination whether SLTT law enforcement and correctional agencies are able to fully protect critical infrastructure from the UAS threat and, if not, recommendations on how to expand C-UAS authorities to critical infrastructure owners. This determination is informed by the protection-request data reported under paragraph (h) of this section.</P>
                                <P>(5) Instances in which records of communications were retained beyond 180 days, or in which control communications were disclosed outside the originating agency.</P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.14 </SECTNO>
                                <SUBJECT>Privacy and civil liberties.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">General.</E>
                                     In exercising authority under 6 U.S.C. 124n(a)(2), an SLTT law enforcement or correctional agency and its personnel must comply with the requirements of 6 U.S.C. 124n(e), including the implementation of privacy protections with respect to the interception, acquisition, access, maintenance, use, and dissemination of communications, consistent with the First and Fourth Amendments to the Constitution of the United States and applicable provisions of Federal law. All operations under this part must comply with the requirements of the Fourth Amendment and the policies of the applicable SLTT law enforcement or correctional agency with respect to searches and seizures, and individual searches and seizures conducted during C-UAS operations remain subject to the Fourth Amendment reasonableness requirement.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">First Amendment.</E>
                                     No C-UAS authority under this part may be used solely to seize, monitor, deter, interfere with, or disrupt individuals exercising rights protected by the First Amendment to the Constitution of the United States. When C-UAS operations are conducted at events or locations where individuals are exercising First Amendment rights, personnel must take affirmative steps to minimize the collection, retention, and dissemination of information about those individuals, and must not use C-UAS-derived information to identify, track, or build records on individuals based on their exercise of protected rights.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Scope of interception.</E>
                                     Communications may be intercepted or acquired only to the extent necessary to support an action described in 6 U.S.C. 124n(b)(1).
                                </P>
                                <P>(1) Material captured that is not control communications is incidental capture. Agencies must configure systems to minimize incidental capture, and incidentally captured material determined not to be relevant to a C-UAS, law enforcement, or national security purpose must not be reviewed, retained, or disseminated and must be purged as soon as practicable.</P>
                                <P>(2) During the contemporaneous C-UAS operation, personnel may view incidentally captured material only to the extent necessary for C-UAS detection, tracking, identification, or mitigation purposes and may not use it for general surveillance or monitoring. If it becomes apparent that the captured video, audio, or other data stream is not control communications, the interception of such communications must be discontinued, and the interception of incidentally captured material must be documented in the post-operation report. When a system's configuration permits adjustment of the scope of interception, such as frequency range, geographic coverage, or signal type, operators must use the narrowest configuration consistent with operational effectiveness.</P>
                                <P>(3) For standing detection deployments exceeding 30 days, the agency must conduct a review, not less than quarterly, to confirm that the scope of interception remains proportionate to the operational need, that incidental collection of non-UAS communications is being minimized, and that data handling and purge procedures are being executed on schedule. The review may be conducted on a program-wide basis for facilities.</P>
                                <P>(4) Where identifying the threat requires processing the control signaling of all unmanned aircraft in range, the control communications of an unmanned aircraft determined not to pose a threat may not be retained or used beyond what is needed to make the threat determination and must be purged on the same schedule as other incidental material.</P>
                                <P>
                                    (d) 
                                    <E T="03">Records of communications and retention.</E>
                                     (1) Control communications captured, recorded, or maintained by SLTT C-UAS systems constitute records of communications to or from a UAS within the meaning of 6 U.S.C. 124n(e)(3) and must be maintained only for as long as necessary, and in no event for more than 180 days, unless the Agency Approving Official or the agency's chief legal officer determines that maintenance of such records is necessary to investigate or prosecute a violation of law, to directly support an 
                                    <PRTPAGE P="41495"/>
                                    ongoing security operation, for the purpose of any litigation, or is required under Federal, State, local, Tribal, or territorial law, consistent with 6 U.S.C. 124n(e)(3).
                                </P>
                                <P>(2) Data retained under the ongoing security operation exception must be reviewed at 90-day intervals and purged when the operation concludes, unless another exception applies.</P>
                                <P>(3) When an agency determines that records of communications will be retained beyond 180 days under any exception, the agency must notify the Federal Bureau of Investigation through the portal within 30 days of the determination.</P>
                                <P>(4) Pattern data, once extracted and recorded independently, is not a record of communications and is not subject to the 180-day limit. Data generated by systems whose operation does not implicate the electronic surveillance laws referenced in the notwithstanding clause of 6 U.S.C. 124n(a)(2) is likewise not subject to the 180-day limit.</P>
                                <P>(5) For data retained under the investigation or prosecution exception, the existence of an open investigative or prosecutorial case file documenting the data as evidence satisfies the required determination. For data retained under any other exception, the Agency Approving Official or the agency's chief legal officer must document the specific basis for retention. If an agency has neither an Agency Approving Official nor a chief legal officer, an official holding a rank not below a Senior Executive or Senior Official, or its equivalent, must document the specific basis for retention.</P>
                                <P>(6) A standing operational window authorized under § 124.8(h) does not itself constitute an ongoing security operation for purposes of the retention exception; that exception applies only when a specific, identified threat or other intelligence justifies continued retention of specific records to support a discrete protective objective, and the 90-day review must assess whether the specific security basis for retention continues to exist.</P>
                                <P>(7) The exception for retention required under Federal, State, local, Tribal, or territorial law applies when a specific provision of law affirmatively requires retention of the particular type of data at issue, not when a general records retention schedule incidentally encompasses C-UAS data.</P>
                                <P>
                                    (e) 
                                    <E T="03">Dissemination.</E>
                                     (1) Control communications acquired under this part may be disclosed outside the disseminating agency only as authorized by 6 U.S.C. 124n(e)(4): when necessary to investigate or prosecute a violation of law; to support the Department of Defense, a Federal law enforcement agency, or the enforcement activities of a regulatory agency of the Federal Government in connection with a criminal or civil investigation of, or any regulatory, statutory, or other enforcement action relating to an action described in 6 U.S.C. 124n(b)(1); or as otherwise required by law.
                                </P>
                                <P>(2) This part does not prohibit the use, as evidence in a subsequent proceeding, of information lawfully obtained incidental to an SLTT law enforcement or correctional agency C-UAS operation, consistent with applicable law.</P>
                                <P>(3) At the time of any dissemination of control communications, the disseminating agency must document, in the audit trail required by paragraph (g) of this section, the 6 U.S.C. 124n(e)(4) basis for the dissemination, the category of recipient, whether the handling caveat required by paragraph (f) of this section was conveyed, and whether the dissemination included control communications.</P>
                                <P>(4) A real-time detection feed is governed by the substantive character of the data it transmits. A feed that transmits control communications acquired under this part is subject to the requirements of this section applicable to such data and the limitations under 6 U.S.C. 124n(e)(1), (2), and (4). A feed that transmits only data described in paragraph (e)(6) of this section is not subject to those limitations.</P>
                                <P>(5) Pattern data that contains no control communications may be disseminated consistent with the agency's standard data handling and information sharing policies and applicable law. Before disseminating pattern data beyond the agency, the disseminating agency must verify anonymization in accordance with its implementation policy and screen the product for operationally sensitive information that would reveal specific coverage patterns, capabilities, gaps, or methods. Public release of pattern data products requires approval at the level designated by the agency's implementation policy.</P>
                                <P>(6) Data not acquired using the authorities or reliefs provided by 6 U.S.C. 124n, including data generated by systems whose operation does not implicate the electronic surveillance laws referenced in the notwithstanding clause of 6 U.S.C. 124n(a)(2), is not subject to the disclosure limitations of paragraph (e)(1) of this section and may be shared consistent with the agency's standard data handling and information sharing policies and applicable law. Sharing for situational awareness with recipients that are not law enforcement or correctional agencies, including critical infrastructure owners or operators and the public, is limited to data described in this paragraph, unless the disclosure of control communications is authorized under paragraph (e)(1) of this section.</P>
                                <P>
                                    (f) 
                                    <E T="03">Protective purpose limitation.</E>
                                     Because the authority of 6 U.S.C. 124n(a)(2) is limited to mitigation of a credible threat, an SLTT law enforcement or correctional agency may disseminate control communications acquired pursuant to the agency's authorities and statutory reliefs under 6 U.S.C. 124n(a)(2) only for law enforcement action arising from the UAS activity that prompted the C-UAS operation, or for aviation safety. An SLTT law enforcement or correctional agency may not disseminate such control communications for use in an investigation or enforcement action unrelated to UAS activity unless the communications are independently obtainable through lawful means not dependent on the authorities and statutory reliefs under 6 U.S.C. 124n(a)(2). At the time of dissemination, the disseminating agency must communicate the protective purpose for which the control communications are being shared.
                                </P>
                                <P>
                                    (g) 
                                    <E T="03">Audit trail.</E>
                                     Each SLTT law enforcement or correctional agency exercising authority under this part must maintain an audit trail sufficient to document each instance in which C-UAS authority was exercised, the basis for the action, the disposition of any data acquired, and any dissemination of data under this part. The audit trail must be searchable and accessible to compliance auditors, protected against unauthorized modification or deletion, and retained for a minimum of 6 years. The agency's implementation policy must specify the format and system of records for the audit trail.
                                </P>
                                <P>
                                    (h) 
                                    <E T="03">State and local retention conflicts.</E>
                                     When an SLTT law enforcement or correctional agency determines that a State, local, Tribal, or territorial records retention requirement applicable to law enforcement or correctional agency records encompasses C-UAS communications data and the agency cannot comply with both the 180-day retention limit and that retention requirement, the agency must retain the data for the period required by the applicable law and must apply the handling restrictions of this part, including the prohibition on use for unrelated law enforcement purposes and the dissemination restrictions of this section, for the full duration of retention.
                                    <PRTPAGE P="41496"/>
                                </P>
                                <P>
                                    (i) 
                                    <E T="03">Third-party acquisition.</E>
                                     An SLTT law enforcement or correctional agency may not request, purchase, subscribe to, or operationally rely on intercepted UAS control communications acquired by any actor lacking lawful authority and relief from certain otherwise applicable laws for the underlying interception, regardless of whether the agency directed or facilitated the original interception. An agency acquiring UAS intelligence from a third-party source must document the source's lawful authority and relief from otherwise applicable laws for any intercepted content and must apply the retention and dissemination requirements of this section to data so acquired. The agency's implementation policy must specify procedures for evaluating third-party source authority and relief from certain otherwise applicable laws, which must include review and concurrence by appropriate State, local, territorial, or Tribal legal counsel.
                                </P>
                                <P>
                                    (j) 
                                    <E T="03">Vendor data sharing.</E>
                                     An SLTT law enforcement or correctional agency may provide operational raw sensor data to system vendors for purposes of system diagnostics, troubleshooting, and performance validation, provided that any communications content is removed before disclosure and the data is used solely for the specific purpose identified. The agency's implementation policy must establish the conditions for vendor data sharing consistent with this paragraph and applicable privacy protections.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.15 </SECTNO>
                                <SUBJECT>Protection of sensitive operational information.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Sensitive system information.</E>
                                     Information that links the specific capabilities, vulnerabilities, operating parameters, or countermeasure effectiveness of C-UAS systems to planned or completed operations, including deployment locations, operating radio frequencies, tactical employment methods, and threat-specific mitigation approaches, must be treated as law enforcement sensitive, protected from public disclosure to the extent permitted by applicable law, and, where the information reveals a capability gap of national security concern, evaluated for classification. Other operational coordination information associated with a planned or completed operation, such as the existence, general timing, or general coverage area of a deployment, must be handled as Controlled Unclassified Information and may be shared with covered Federal and SLTT law enforcement and correctional partners, including a State-designated aviation point of contact, for a lawful government purpose. General technical specifications and evaluation data not associated with a specific planned or completed operation are not subject to these handling requirements. All information described in this paragraph remains subject to any applicable classification, export control, or proprietary restriction.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Protection from disclosure.</E>
                                     An SLTT law enforcement or correctional agency must take the steps available under applicable State, local, Tribal, or territorial law to protect operationally sensitive information from disclosure through public records requests or civil discovery, and should coordinate with the prosecuting authority in criminal prosecutions arising from C-UAS operations to limit testimony and pleadings to the information necessary to establish the elements of the offense. Nothing in this section requires an agency to take any action inconsistent with applicable State, local, Tribal, or territorial public records law.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Markings.</E>
                                     Advance notifications, C-UAS Operations Plans, post-operation reports, and compliance audit records must be marked with appropriate sensitivity designations.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Permitted disclosures.</E>
                                     This section does not prohibit disclosure of sensitive system information to authorized Federal officials, to other participating SLTT agencies in the course of operational coordination, or to the public to the extent required by statute or court order.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.16 </SECTNO>
                                <SUBJECT>Compliance and enforcement.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Compliance audits.</E>
                                     The Attorney General, in coordination with the Secretary of Homeland Security and the Administrator of the Federal Aviation Administration, will periodically conduct compliance audits of SLTT law enforcement and correctional agencies exercising authority under 6 U.S.C. 124n(a)(2), as required by 6 U.S.C. 124n(d)(2)(B) and section 8606(b)(2) of the SAFER SKIES Act, to oversee compliance with this part and the privacy protections of 6 U.S.C. 124n(e) as well as to prevent misuse of C-UAS authority. The audit program will include review of post-operation reports, advance notification records, and agency implementation policies. The FAA will participate with respect to the aviation safety, airspace safety coordination, and deconfliction aspects of the compliance audits conducted under this section.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Civil fines and penalties.</E>
                                     An SLTT law enforcement or correctional agency, or its personnel authorized to take mitigation actions under 6 U.S.C. 124n(a)(2), that knowingly engages in such actions without Federal coordination as required by 6 U.S.C. 124n and the SAFER SKIES Act, including the advance coordination required by § 124.9, the real-time air traffic control notification required by § 124.11, and the post-action notification to the Attorney General and the Secretary of Homeland Security required by 6 U.S.C. 124n(d)(2)(C) and implemented by § 124.13(a), may be subject to a civil fine of up to $100,000 per violation, or suspension of C-UAS authority pending review by the Attorney General or the Secretary of Homeland Security, as provided in section 8605(f) of the SAFER SKIES Act. Civil penalties will be assessed in accordance with graduated penalty levels proportionate to the severity of the violation and the factors set forth in this part, including the agency's compliance history, the availability and quality of compliance assistance from Federal partners, whether the violation resulted in actual harm, and whether the agency took prompt corrective action. A civil penalty will not be assessed for a first violation of a procedural reporting or notification requirement when the agency demonstrates a good-faith effort to comply and voluntarily self-reports the deficiency. Violations of requirements of this part other than the Federal coordination requirements described in this paragraph do not give rise to civil penalties under section 8605(f) of the SAFER SKIES Act; they are addressed through the compliance audit program of this section, certification and accreditation suspension under § 124.5, and any other remedy available under law.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Civil enforcement.</E>
                                     The Attorney General is authorized to bring a civil action in a United States district court to collect fines and enforce civil penalties imposed under this section against any agency or individual, as provided in section 8605(g) of the SAFER SKIES Act.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Relationship to certification or accreditation suspension.</E>
                                     In addition to civil penalties, the Attorney General or designee may suspend a Mitigation Certification, Detection and Warning Certification, or accreditation under § 124.5(i) for violations of this part. Certification or accreditation suspension may be imposed independently of or in conjunction with other actions described in this section.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.17 </SECTNO>
                                <SUBJECT>Confiscation and forfeiture.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Confiscation authority.</E>
                                     (1) An SLTT law enforcement or correctional agency and its personnel may seize or 
                                    <PRTPAGE P="41497"/>
                                    otherwise confiscate a UAS or unmanned aircraft as described in 6 U.S.C. 124n(b)(1)(E). This authority is contingent on a credible threat and applies to the physical taking of possession of an unmanned aircraft that is no longer active in flight or any other UAS component, such as a ground control station.
                                </P>
                                <P>(2) This authority does not require Mitigation Certification, the use of systems on the Authorized Technologies List or Authorized Systems List, or advance coordination under § 124.9. However, personnel exercising confiscation authority under 6 U.S.C. 124n(b)(1)(E) must hold a current Detection and Warning Certification issued by the NCUTC. An officer who seizes an unmanned aircraft or any other UAS component under traditional law enforcement authority, including an abandoned or crashed unmanned aircraft, does not require Detection and Warning Certification.</P>
                                <P>(3) Any action that employs C-UAS technology to disrupt or seize control of, damage, disable, or destroy the unmanned aircraft or UAS is an action under 6 U.S.C. 124n(b)(1)(C), (D), or (F) and requires Mitigation Certification.</P>
                                <P>(4) Personnel exercising confiscation authority should follow standard law enforcement evidence handling procedures, including maintaining chain of custody, preserving digital evidence stored on the aircraft or its flight controller, and observing applicable hazardous materials precautions.</P>
                                <P>(5) This part does not affect the authority of any law enforcement or correctional officer to take physical custody of an unmanned aircraft or UAS under traditional law enforcement authority independent of 6 U.S.C. 124n. Traditional law enforcement authority refers to the seizure authorities generally available to law enforcement under applicable Federal, State, local, Tribal, or territorial law, including seizure incident to arrest, seizure of evidence or contraband pursuant to a warrant or a recognized exception to the warrant requirement, and seizure of abandoned property. Once an unmanned aircraft or UAS is on the ground and confiscated, subsequent law enforcement actions, including threat assessment, render safe procedures, evidence collection, and search warrant execution, are governed by traditional legal authorities, including Fourth Amendment requirements and applicable exigency or emergency doctrines, rather than by 6 U.S.C. 124n.</P>
                                <P>(6) When a C-UAS operation involves a known or suspected unmanned aircraft being used as a delivery mechanism for a hazardous device, the response to the hazardous device must be conducted by a public safety bomb squad accredited through the Hazardous Devices School, consistent with the National Guidelines for Bomb Technicians or any successor publication.</P>
                                <P>(7) The physical act of interception of a third-party unmanned aircraft while it is in flight, such as catching or netting an aircraft by hand or using a non-electronic physical device to capture it in the air, implicates 6 U.S.C. 124n(b)(1)(D), (E), or (F). Personnel conducting such actions must therefore hold a Mitigation Certification. This does not apply to the erection of physical barriers that a drone operator has an obligation to avoid, such as netting affixed to a physical structure.</P>
                                <P>
                                    (b) 
                                    <E T="03">Forfeiture.</E>
                                     Any UAS or unmanned aircraft seized by an SLTT law enforcement or correctional agency pursuant to 6 U.S.C. 124n(a)(2) is subject to forfeiture under the laws of the seizing agency's jurisdiction, as provided in 6 U.S.C. 124n(c)(2).
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.18 </SECTNO>
                                <SUBJECT>Activities for evaluation, testing, training, and pre-operational validation.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Scope and legal basis.</E>
                                     An SLTT law enforcement or correctional agency that holds current accreditation under this part may conduct operational acceptance testing of acquired systems and systems under procurement consideration, on-the-job proficiency training, and interoperability training exercises to maintain C-UAS operational readiness. Testing and training do not and must not involve the mitigation of a credible threat and are not conducted under the authority of 6 U.S.C. 124n(a)(2). The operation of RF-emitting systems during testing and training is conducted under applicable Federal Communications Commission authorization and Federal Aviation Administration coordination requirements, and only against controlled test targets owned or operated by, or operated with the consent of, the SLTT law enforcement or correctional agency. An SLTT law enforcement or correctional agency acting pursuant to this section may utilize only authorized technologies under § 124.7. The SLTT law enforcement or correctional agency is responsible for verifying that all necessary Federal Aviation Administration authorizations or regulatory relief for operation of any unmanned aircraft or UAS, including unmanned aircraft or UAS forming part of a C-UAS system, have been obtained prior to any testing, training, or exercises. Compliance with this section is a condition of maintaining certification and accreditation under this part.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Personnel.</E>
                                     Only personnel holding a current Mitigation Certification may operate mitigation systems during evaluation testing, training, and exercises. Testing, training, and exercises may not be used to train or evaluate uncertified personnel on the operation of mitigation systems. Contractors and vendor representatives may provide technical support and instruction on system-specific procedures but may not independently operate mitigation systems against test targets.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Evaluation testing and training activities plan.</E>
                                     Before conducting testing, training, or exercises involving RF-emitting C-UAS mitigation systems, the agency must prepare a written activities plan specifying the date, time, and location; the purpose; the systems and equipment to be used; the test, training, or exercise targets; the assigned operators; safety controls; privacy measures; the types of data to be collected and their planned disposition; documentation of Federal Aviation Administration and Federal Communications Commission spectrum coordination for the C-UAS activities, and documentation of any necessary Federal Aviation Administration authorizations or regulatory relief for the operator of the target unmanned aircraft or UAS and for the operation any unmanned aircraft or UAS that form part of the C-UAS system. The activities plan must be approved by the Agency Approving Official or designee and reviewed by the agency's legal counsel.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Coordination.</E>
                                     Testing, training, and exercises, involving RF-emitting systems, or systems that may affect aviation safety, civilian aviation and aerospace operations, aircraft airworthiness, or the use of the airspace, require advance coordination with the Federal Aviation Administration and, for spectrum authorization, with the Federal Communications Commission.
                                </P>
                                <P>
                                    (e) 
                                    <E T="03">Privacy within evaluation testing and training.</E>
                                     The agency must favor testing, training, and exercise locations and activities that minimize exposure to non-participating third parties. The agency must not intentionally target, monitor, or collect the communications of non-participating third parties. Communications incidentally collected from non-participating third parties must be purged at the conclusion of the testing, training, or exercise activity, or as soon as practicable thereafter.
                                </P>
                                <P>
                                    (f) 
                                    <E T="03">Mitigation restriction.</E>
                                     During testing, training, and exercises, the agency may not intentionally mitigate 
                                    <PRTPAGE P="41498"/>
                                    any UAS or unmanned aircraft that is not a controlled test target, unless necessary to protect against an imminent risk to human life or as part of an approved C-UAS Operations Plan. An action taken to protect against an imminent risk to human life must comply with the emergency exception set forth in § 124.9(g).
                                </P>
                                <P>
                                    (g) 
                                    <E T="03">Pre-operational validation.</E>
                                     Before commencing mitigation operations at an event or facility, an agency may conduct pre-operational validation or equipment functional checks within the operational window and airspace restrictions already coordinated through the advance notification process under § 124.9. The C-UAS Operations Plan must document the pre-operational validation plan and required notifications. No separate authorization from the Department of Homeland Security or the Department of Justice beyond the advance notification is required.
                                </P>
                                <P>
                                    (h) 
                                    <E T="03">Participation in Federal RTTE.</E>
                                     Personnel holding active Mitigation Certification may participate in research, testing, training, and evaluation (RTTE) events conducted by Federal components under 6 U.S.C. 124n(b)(3). Personnel may engage with systems in mitigation technology categories beyond those for which they hold an active Mitigation Certification or that are not on the ATL or ASL as part of the event. Participants act under the Federal component's authority and supervision.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.19 </SECTNO>
                                <SUBJECT>Task force arrangements and Federal support.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Task force and deputization arrangements preserved.</E>
                                     Task force and deputization arrangements under 6 U.S.C. 124n(a)(1) are not affected by this part. An SLTT law enforcement or correctional agency participating in such an arrangement may continue that participation indefinitely, so long as the deputizing Federal agency continues to have C-UAS authority and relief from certain laws under 6 U.S.C. 124n(a)(1). Nothing in this part requires an agency to seek accreditation under this part, conditions any task force or deputization arrangement on accreditation, or terminates or limits any such arrangement.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Concurrent authority.</E>
                                     The availability of independent SLTT law enforcement and correctional agency authority under 6 U.S.C. 124n(a)(2) does not preclude continued participation in C-UAS task forces or deputization arrangements under 6 U.S.C. 124n(a)(1). An SLTT law enforcement or correctional agency and its officers may exercise independent authority and participate in Federal task force operations concurrently or at different times as operational circumstances warrant. Task force operations are governed by the policies applicable to the sponsoring Federal component.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Federal support.</E>
                                     An SLTT law enforcement or correctional agency may request C-UAS support from an authorized Department of Justice or Department of Homeland Security component. Such support, when provided, constitutes a Federal operation under 6 U.S.C. 124n(a)(1) and is governed by the policies applicable to the supporting component, and the requesting agency's personnel participating in the operation do so under the Federal component's authority and supervision, consistent with applicable task force or deputization arrangements. No formal gubernatorial request is required under this part. Support from the Department of Defense, when available, is governed by the Department of Defense's own authorities, including 10 U.S.C. 130i and 2564, and applicable Department of Defense policies, not by this part.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.20 </SECTNO>
                                <SUBJECT>Construction.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">No private right.</E>
                                     This part is not intended to, does not, and may not be relied upon to create any right or benefit, substantive or procedural, enforceable at law or in equity by any party against the United States, its departments, agencies, or entities, its officers, employees, or agents, or any other person.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Manned aircraft.</E>
                                     Nothing in this part authorizes the use of C-UAS authority against any aircraft or aircraft system operated with a human pilot, crew, or passengers onboard.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Mass gatherings.</E>
                                     Consistent with 6 U.S.C. 124n(h)(5), nothing in this part provides a new basis of liability for any State, local, territorial, or Tribal law enforcement officer who participates in the protection of a mass gathering identified by the Secretary of Homeland Security or the Attorney General under 6 U.S.C. 124n(l)(3)(C)(iii)(II), acts within the scope of the officer's authority, and does not exercise the authority granted to the Secretary of Homeland Security and the Attorney General by 6 U.S.C. 124n.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Statutory scope.</E>
                                     Nothing in this part alters the scope of the authority of, or the statutory reliefs under 6 U.S.C. 124n(a)(2). A determination that an action does not comply with this part may give rise to administrative, civil, or other consequences provided by law, but does not by itself determine whether the action falls outside the scope of the statutory authorization in, or the relief from criminal liability available under, 6 U.S.C. 124n. Such a determination will be made by the Attorney General, in coordination with the Secretary of Homeland Security and other appropriate officials.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.21 </SECTNO>
                                <SUBJECT>Termination.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Termination.</E>
                                     Absent additional statutory authority, the authority of SLTT law enforcement and correctional agencies and their personnel under 6 U.S.C. 124n(a)(2) will terminate on December 31, 2031, as provided in 6 U.S.C. 124n(j)(2).
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Savings.</E>
                                     Termination under paragraph (a) of this section does not affect any obligation, proceeding, or liability that arose before the termination date. Recordkeeping, retention, audit, reporting, and enforcement obligations with respect to operations conducted before the termination date, and any administrative or civil proceeding arising from those operations, survive the termination of authority under this part and remain in effect until satisfied or otherwise resolved.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.22 </SECTNO>
                                <SUBJECT>Severability.</SUBJECT>
                                <P>If any provision of this part, or the application of any provision to any person, entity, or circumstance, is held to be invalid or unenforceable by a court of competent jurisdiction, the remainder of this part, and the application of its provisions to any other persons, entities, or circumstances, shall not be affected and shall remain in full force and effect.</P>
                            </SECTION>
                        </PART>
                    </REGTEXT>
                    <HD SOURCE="HD1">
                        <E T="0742">DEPARTMENT OF JUSTICE</E>
                    </HD>
                    <REGTEXT TITLE="7" PART="124">
                        <AMDPAR>Accordingly, for the reasons set forth in the preamble, and by the authority vested in the Assistant Attorney General for the Office of Legal Policy by Attorney General Order Number 6966-2026, title 28 of the Code of Federal Regulations is amended by adding part 124 to read as follows:</AMDPAR>
                        <PART>
                            <HD SOURCE="HED">PART 124—COUNTER-UNMANNED AIRCRAFT SYSTEM AUTHORITY FOR STATE, LOCAL, TRIBAL, AND TERRITORIAL LAW ENFORCEMENT AND CORRECTIONAL AGENCIES</HD>
                            <CONTENTS>
                                <SECHD>Sec.</SECHD>
                                <SECTNO>124.1 </SECTNO>
                                <SUBJECT>Purpose and scope.</SUBJECT>
                                <SECTNO>124.2 </SECTNO>
                                <SUBJECT>Definitions.</SUBJECT>
                                <SECTNO>124.3 </SECTNO>
                                <SUBJECT>Scope of authority and mitigation standards.</SUBJECT>
                                <SECTNO>124.4 </SECTNO>
                                <SUBJECT>Authorized personnel, contractors, and mutual aid.</SUBJECT>
                                <SECTNO>124.5 </SECTNO>
                                <SUBJECT>Training and certification.</SUBJECT>
                                <SECTNO>124.6 </SECTNO>
                                <SUBJECT>Agency implementation policy.</SUBJECT>
                                <SECTNO>124.7 </SECTNO>
                                <SUBJECT>Authorized technologies.</SUBJECT>
                                <SECTNO>124.8 </SECTNO>
                                <SUBJECT>C-UAS Operations Plan.</SUBJECT>
                                <SECTNO>124.9 </SECTNO>
                                <SUBJECT>
                                    Advance coordination, notification, and authorization.
                                    <PRTPAGE P="41499"/>
                                </SUBJECT>
                                <SECTNO>124.10 </SECTNO>
                                <SUBJECT>Interagency and lead-agency coordination.</SUBJECT>
                                <SECTNO>124.11 </SECTNO>
                                <SUBJECT>Real-time air traffic control notification.</SUBJECT>
                                <SECTNO>124.12 </SECTNO>
                                <SUBJECT>Detection and warning operations.</SUBJECT>
                                <SECTNO>124.13 </SECTNO>
                                <SUBJECT>Post-operation reporting.</SUBJECT>
                                <SECTNO>124.14 </SECTNO>
                                <SUBJECT>Privacy and civil liberties.</SUBJECT>
                                <SECTNO>124.15 </SECTNO>
                                <SUBJECT>Protection of sensitive operational information.</SUBJECT>
                                <SECTNO>124.16 </SECTNO>
                                <SUBJECT>Compliance and enforcement.</SUBJECT>
                                <SECTNO>124.17 </SECTNO>
                                <SUBJECT>Confiscation and forfeiture.</SUBJECT>
                                <SECTNO>124.18 </SECTNO>
                                <SUBJECT>Activities for evaluation, testing, training, and pre-operational validation.</SUBJECT>
                                <SECTNO>124.19 </SECTNO>
                                <SUBJECT>Task force arrangements and Federal support.</SUBJECT>
                                <SECTNO>124.20 </SECTNO>
                                <SUBJECT>Construction.</SUBJECT>
                                <SECTNO>124.21 </SECTNO>
                                <SUBJECT>Termination.</SUBJECT>
                                <SECTNO>124.22 </SECTNO>
                                <SUBJECT>Severability.</SUBJECT>
                            </CONTENTS>
                            <AUTH>
                                <HD SOURCE="HED">Authority:</HD>
                                <P> 5 U.S.C. 301; 6 U.S.C. 124n, as amended by the SAFER SKIES Act (Division H, Title LXXXVI of the National Defense Authorization Act for Fiscal Year 2026, Pub. L. 119-60, sec. 8601-8607, 139 Stat. 718, 1938-45 (2025)).</P>
                            </AUTH>
                            <SECTION>
                                <SECTNO>§ 124.1 </SECTNO>
                                <SUBJECT>Purpose and scope.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Purpose.</E>
                                     This part implements the authority of the Secretary of Homeland Security and the Attorney General to develop the governance framework for the exercise of all counter-unmanned aircraft system (C-UAS) actions by State, local, Tribal, and territorial (SLTT) law enforcement and correctional agencies and their personnel under 6 U.S.C. 124n(a)(2), as amended by the SAFER SKIES Act. The purpose of actions taken under this authority is to detect, identify, monitor, track, warn, and, if necessary, mitigate credible threats posed by unmanned aircraft or unmanned aircraft systems (UAS) to the safety or security of people, facilities, or assets; a venue or set of venues used for large-scale public gatherings or events; critical infrastructure; or a correctional facility.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Scope.</E>
                                     This part applies to all SLTT law enforcement and correctional agencies, and their personnel seeking to exercise or exercising authority under 6 U.S.C. 124n(a)(2). This part does not govern Federal agency operations under 6 U.S.C. 124n(a)(1), nor deputized SLTT personnel conducting C-UAS as part of an FBI C-UAS task force, which are subject to separate policies and guidance. An SLTT law enforcement or correctional agency that conducts only detection and warning operations using systems the operation of which requires the authority of the Act or the relief it provides from certain laws is subject principally to the Detection and Warning Certification requirement of § 124.5(c), the detection and warning policy provisions of § 124.6(g), the authorized technology requirements of § 124.7, the C-UAS Operations Plan requirement of § 124.8, the operational conditions of § 124.12, and the privacy and data handling requirements of § 124.14.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Relationship to other laws.</E>
                                     As provided in 6 U.S.C. 124n(a)(2), actions taken by SLTT law enforcement and correctional agencies and their personnel in compliance with this part may be taken notwithstanding section 46502 of title 49, United States Code, and sections 32, 1030, and 1367 and chapters 119 and 206 of title 18, United States Code, and notwithstanding the laws of any particular State, local, Tribal, or territorial jurisdiction. Nothing in this part vests in the Secretary of Homeland Security or the Attorney General any authority of the Secretary of Transportation or the Administrator of the Federal Aviation Administration.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Comprehensive framework.</E>
                                     This part establishes the complete framework governing the exercise of authority under 6 U.S.C. 124n(a)(2), including the training and certification procedures required by 6 U.S.C. 124n(d)(2)(A) and the guidance required by 6 U.S.C. 124n(d)(1) on the matters this part addresses. An SLTT law enforcement or correctional agency and its personnel exercising authority under 6 U.S.C. 124n(a)(2) must conduct operations in accordance with this part. The Attorney General, the Secretary of Homeland Security, the Secretary of Transportation, and the Administrator of the Federal Aviation Administration may issue forms, templates, curricula, and other implementing materials under this part to the extent consistent with law. Where any implementing material addresses a matter also addressed by this part, this part controls. Nothing in this part limits the authority of the Secretary of Homeland Security, the Attorney General, or the Secretary of Transportation to issue guidance under 6 U.S.C. 124n(d)(1) in their respective areas.
                                </P>
                                <P>
                                    (e) 
                                    <E T="03">Parallel regulations.</E>
                                     Consistent with section 8606(a)(1) of the Act, identical implementing regulations appear at 6 CFR part 124 and 28 CFR part 124. The Department of Homeland Security and Department of Justice administer and interpret their respective regulations with respect to their own programs, activities, and solely held authorities. Any description in these regulations of the other Department's programs, activities, or solely held authorities is provided for context and does not itself govern the other Department's exercise of its statutory authorities.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.2 </SECTNO>
                                <SUBJECT>Definitions.</SUBJECT>
                                <P>As used in this part:</P>
                                <P>
                                    <E T="03">Agency accreditation</E>
                                     means an agency's eligibility to exercise authority under this part, established when the agency has adopted the implementation policy and completed the portal attestation required by § 124.6(d), deploys only systems within categories on the Authorized Technologies List and, where populated, on the Authorized Systems List, and ensures that its personnel hold the certifications required for the authorities exercised.
                                </P>
                                <P>
                                    <E T="03">Agency Approving Official</E>
                                     means the senior official designated by an SLTT law enforcement or correctional agency in its implementation policy under § 124.6(a)(1), or in its detection and warning policy under § 124.6(g), authorized to approve C-UAS operations on behalf of the agency. The Agency Approving Official must not be below the rank of a Senior Executive or Senior Official or its equivalent, except that for an agency in which no equivalent rank exists, the agency head or the agency head's designee may serve as Agency Approving Official. The Agency Approving Official may not serve as a mitigation operator for an operation that official has approved.
                                </P>
                                <P>
                                    <E T="03">Authorized Systems List</E>
                                     means the subset of the Authorized Technologies List that identifies specific systems—including make, model, and hardware version—that have been authorized for operational use within one or more technology categories on the Authorized Technologies List. The Authorized Systems List is populated on a phased basis. As systems complete interagency assessment, systems may be added to the Authorized Systems List with appropriate operational limitations based on the approved capabilities, functions, and hardware version of the system.
                                </P>
                                <P>
                                    <E T="03">Authorized Technologies List</E>
                                     means the list of authorized technology categories for C-UAS operations by SLTT law enforcement and correctional agencies, maintained jointly by the Department of Justice, the Department of Homeland Security, the Department of Defense, the Department of Transportation and Federal Aviation Administration, the Federal Communications Commission, and the National Telecommunications and Information Administration, consistent with 6 U.S.C. 124n(d)(2)(A)(iii) and section 8606(a)(4) of the SAFER SKIES Act.
                                </P>
                                <P>
                                    <E T="03">Control communications</E>
                                     means any wire, oral, or electronic communication used to navigate, command, or otherwise control a UAS or unmanned aircraft, including telemetry transmitted from the aircraft to its operator, command-and-control signals 
                                    <PRTPAGE P="41500"/>
                                    transmitted from the operator to the aircraft, and any video, audio, or other data stream used by the operator to navigate the aircraft when other navigation telemetry is unavailable or insufficient. The operational role of a communication, rather than its packet type or transmission frequency, determines whether it is a control communication. Whether a communication is a control communication is determined when captured material is processed under § 124.14 and does not require an operator to determine in real time whether a particular video, audio, or data stream is being used to navigate the aircraft. Control communications also include a UAS unique identifier (such as a manufacturer device identifier or serial-correlated number), the operator or take-off location of the UAS, and the location, velocity, and emergency status of the UAS when that information is acquired by intercepting a communication from an unmanned aircraft or unmanned aircraft system pursuant to the relief provided by 6 U.S.C. 124n. The same information is not a control communication when it is obtainable without that relief.
                                </P>
                                <P>
                                    <E T="03">Correctional agency</E>
                                     has the meaning given in section 8606(c)(2) of the SAFER SKIES Act.
                                </P>
                                <P>
                                    <E T="03">Correctional facility</E>
                                     has the meaning given in 6 U.S.C. 124n(l)(9).
                                </P>
                                <P>
                                    <E T="03">Credible threat</E>
                                     means a threat that, based on the totality of circumstances known to the operator at the time of the determination, would cause a reasonable person in the operator's position, considering the operator's training and experience, to conclude that a UAS or unmanned aircraft poses an articulable risk to the safety or security of people, a facility, or an asset; a venue or set of venues used for large-scale public gatherings or events; critical infrastructure; or a correctional facility.
                                </P>
                                <P>(1) A credible threat may be based on, but is not limited to:</P>
                                <P>(i) Specific intelligence, including information from law enforcement databases, threat assessments, or intelligence community products;</P>
                                <P>(ii) Behavioral indicators, including operation in airspace in which UAS operations have been restricted or prohibited by the Federal Aviation Administration, operation not in compliance with Federal Aviation Administration's flight requirements, approach toward a protected interest, failure to respond to warnings, or evasive maneuvering inconsistent with normal flight operations;</P>
                                <P>(iii) Payload or physical configuration indicators, including observed attachments, modifications, or configurations inconsistent with ordinary recreational or commercial UAS use that suggest capability to cause harm or to deliver prohibited items;</P>
                                <P>(iv) Unauthorized surveillance or reconnaissance of a protected interest that by law is protected from such activities, or interference with the operational mission of a protected interest;</P>
                                <P>(v) Indications that the UAS is being used to gain unauthorized access to, or to disclose, classified, law enforcement sensitive, or otherwise lawfully protected information; or</P>
                                <P>(vi) Pattern-based indicators, including repeated unauthorized UAS activity at a specific location (such as repeat incursions of national defense airspace in violation of 49 U.S.C. 46307), which may inform but do not independently satisfy the credible threat standard.</P>
                                <P>(2) A credible threat determination rests on the totality of the circumstances. A single indicator may establish a credible threat where it is sufficiently probative. For mitigation actions under 6 U.S.C. 124n(b)(1)(C), (D), and (F), the determination must be supported by a contemporaneous indicator that the specific unmanned aircraft system or unmanned aircraft at issue poses a current, articulable risk if unabated. For detection and warning actions under 6 U.S.C. 124n(b)(1)(A) and (B), a credible threat determination may also be supported by a reasonable basis to anticipate that one or more unmanned aircraft systems or unmanned aircraft poses an articulable risk. Activity protected by the First Amendment to the Constitution of the United States may not be considered in making a credible threat determination.</P>
                                <P>
                                    <E T="03">Critical infrastructure</E>
                                     has the meaning given in subsection (e) of the Critical Infrastructures Protection Act of 2001 (Pub. L. 107-56, sec. 1016, 115 Stat. 272, 400-02 (codified at 42 U.S.C. 5195c)), as referenced in 6 U.S.C. 124n(l)(10).
                                </P>
                                <P>
                                    <E T="03">Data purge verification</E>
                                     means documented confirmation that records subject to purge have been deleted from all systems on which they were stored. Verification may be performed through an automated system, supervisory review, or other documented confirmation process, and must be recorded in the audit trail required by § 124.14.
                                </P>
                                <P>
                                    <E T="03">Designated Federal C-UAS coordination portal</E>
                                     means the electronic submission system designated by the Attorney General and Secretary of Homeland Security for advance notifications, notices of intent, C-UAS Operations Plans, mitigation notifications, post-operation reports, and other submissions required by this part.
                                </P>
                                <P>
                                    <E T="03">Detection and Warning Certification</E>
                                     means certification that personnel have successfully completed the online detection and warning training curriculum developed and maintained through the National Counter-UAS Training Center (NCUTC) and passed the post-course assessment. A Detection and Warning Certification authorizes the holder to exercise the authorities described in 6 U.S.C. 124n(b)(1)(A), (B), and (E). The certification is issued automatically through the NCUTC training portal upon successful completion of the curriculum and assessment and recorded in the NCUTC certification database.
                                </P>
                                <P>
                                    <E T="03">Detection and warning operations</E>
                                     means operations conducted using systems the operation of which requires the authority of, or relief from certain laws under, 6 U.S.C. 124n and involve only the actions described in 6 U.S.C. 124n(b)(1)(A) and (B). Detection and warning activity conducted using systems that do not require the authority of 6 U.S.C. 124n (including, for example, electro-optical, infrared, acoustic sensors, and radar) is not subject to this part. Operation of RF-emitting C-UAS systems remains subject to applicable Federal Communications Commission authorization requirements and Federal Aviation Administration coordination if such emission could impact the National Airspace System or other systems located at or near airports.
                                </P>
                                <P>
                                    <E T="03">Detection system</E>
                                     means a system or technology used to take an action described in 6 U.S.C. 124n(b)(1)(A) or (B)—that is, to detect, identify, monitor, or track a UAS or unmanned aircraft, or to warn its operator, and that has no capability enabled to disrupt or seize control of, or disable, damage, or destroy a UAS or unmanned aircraft.
                                </P>
                                <P>
                                    <E T="03">FAA-designated coordination mechanism</E>
                                     means the program, office, or process designated by the Administrator of the Federal Aviation Administration for the coordination of C-UAS operations that might affect aviation safety, civilian aviation and aerospace operations, aircraft airworthiness, or the use of the airspace.
                                </P>
                                <P>
                                    <E T="03">Hazardous Devices School</E>
                                     means the schoolhouse operated by the Federal Bureau of Investigation at which public safety bomb technicians are certified and recertified in accordance with the National Guidelines for Bomb Technicians, or any successor publication.
                                    <PRTPAGE P="41501"/>
                                </P>
                                <P>
                                    <E T="03">Mitigation action</E>
                                     means an action described in 6 U.S.C. 124n(b)(1)(C), (D), or (F). Detection and warning, described in 6 U.S.C. 124n(b)(1)(A) and (B), are not mitigation actions.
                                </P>
                                <P>
                                    <E T="03">Mitigation Certification</E>
                                     means certification issued by the National Counter-UAS Training Center upon successful completion of the NCUTC mitigation training course or a successor course approved by the Attorney General acting through the Director of the Federal Bureau of Investigation, authorizing the holder to exercise the authorities described in 6 U.S.C. 124n(b)(1)(C), (D), and (F), to the extent consistent with this part and applicable laws, using authorized technologies within the mitigation technology categories covered by the approved mitigation courses the holder has completed. A current Detection and Warning Certification is a prerequisite for obtaining and maintaining a Mitigation Certification.
                                </P>
                                <P>
                                    <E T="03">Mitigation operation</E>
                                     means an operation in which a mitigation system is deployed for the purpose of taking an action described in 6 U.S.C. 124n(b)(1)(C), (D), or (F), including disrupting, seizing, or exercising control of, or using reasonable force, if necessary, to disable, damage, or destroy a UAS or unmanned aircraft, whether or not a mitigation action is taken during the operation. A mitigation operation may include elements of detection and warning operations.
                                </P>
                                <P>
                                    <E T="03">Mitigation system</E>
                                     means a system or technology used or capable of being employed to take an action described in 6 U.S.C. 124n(b)(1)(C), (D), or (F), including disrupting, seizing or exercising control of, or using force to disable, damage, or destroy a UAS or unmanned aircraft. A system with both detection and mitigation capability is a mitigation system while its mitigation capability is enabled.
                                </P>
                                <P>
                                    <E T="03">National Counter-UAS Training Center (NCUTC)</E>
                                     means the national schoolhouse operated by the Federal Bureau of Investigation and designated by the Attorney General, acting through the Director of the Federal Bureau of Investigation, as the national training center for purposes of 6 U.S.C. 124n and as the sole certifying authority for SLTT C-UAS mitigation operators under 6 U.S.C. 124n(d)(2)(A)(i).
                                </P>
                                <P>
                                    <E T="03">Pattern data</E>
                                     means a derived data product reflecting aggregated trends, frequencies, or statistical observations of UAS activity across multiple C-UAS operations that has met the anonymization standards established by the agency's implementation policy and contains no information identifying any specific aircraft, operator, or natural person.
                                </P>
                                <P>
                                    <E T="03">Personnel</E>
                                     means officers and employees with assigned duties that include the security or protection of people, facilities, or assets of SLTT law enforcement and correctional agencies, as defined in 6 U.S.C. 124n(a)(2) and (l)(6)(B). This term does not include contractors of SLTT law enforcement and correctional agencies.
                                </P>
                                <P>
                                    <E T="03">Raw sensor data</E>
                                     means unprocessed or minimally processed data generated by C-UAS detection or mitigation systems, including radio frequency signal captures, waveform recordings, radar returns, optical and infrared imagery, acoustic signatures, full sensor logs, and system telemetry. Whether a particular item of raw sensor data constitutes a control communication, and is therefore a record of communications subject to the retention limit of § 124.14, is determined by its function.
                                </P>
                                <P>
                                    <E T="03">RF-emitting C-UAS system</E>
                                     means any C-UAS system that, when employed for detection or mitigation purposes, actively transmits radio frequency energy to detect, disrupt, disable, or seize control of a UAS or unmanned aircraft. This includes systems employing technologies for detection-only purposes, such as radars that transmit radio frequency signals, that may require a radiolocation service license to be issued from the Federal Communications Commission, and mitigation systems that employ radio frequency jamming (broadband or protocol-specific disruption of command-and-control links, video downlinks, or navigation signals) and radio frequency protocol manipulation (command injection or cyber takeover of control signals).
                                </P>
                                <P>
                                    <E T="03">SLTT law enforcement agency</E>
                                     has the meaning given in section 8606(c)(1) of the SAFER SKIES Act.
                                </P>
                                <P>
                                    <E T="03">Special Event Assessment Rating</E>
                                     means a rating assigned to an event under the special event assessment process administered by the Department of Homeland Security, or the equivalent rating under any successor event rating system.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.3 </SECTNO>
                                <SUBJECT>Scope of authority and mitigation standards.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Scope of authority.</E>
                                     An SLTT law enforcement or correctional agency exercising authority under 6 U.S.C. 124n(a)(2) may take actions described in 6 U.S.C. 124n(b)(1), which generally include detection, warning, and mitigation, that are necessary to address or eliminate a credible threat that a UAS or unmanned aircraft poses to the safety or security of people, a facility, or an asset; a venue or set of venues used for large-scale public gatherings or events; critical infrastructure; or a correctional facility. These statutory categories are functional and are not a prescribed list of property types. The determination of whether a specific property falls within these categories is made by the agency's Agency Approving Official, consistent with this part and 6 U.S.C. 124n. No “covered facility or asset” designation under 6 U.S.C. 124n(l)(3) is required for SLTT law enforcement or correctional agency operations; however, a risk-based assessment is required as part of the Operations Plan, as outlined in § 124.8. Whether the property falls within a section 124n(a)(2) category is a separate question from the credible threat determination. The credible threat determination required by paragraph (b) of this section must be made before any mitigation action.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Credible threat determination for mitigation actions.</E>
                                     Before taking any mitigation action, personnel must reasonably determine, under the totality of the circumstances, that a credible threat exists, as defined in § 124.2. The determination must be made in real time by the certified and trained personnel closest to the operational situation and documented as part of the post-operation report required by § 124.13. An established pattern of unauthorized UAS activity at a specific location is relevant to the totality of the circumstances and may, in combination with a contemporaneous indicator—including, for example, a new detection event at the same location during a period consistent with the established pattern—support a credible threat determination. A contemporaneous indicator need not independently establish a threat. Considered with the totality of the circumstances, which may include an established pattern of unauthorized UAS activity, an intelligence indicator, or other contextual information, the contemporaneous indicator must provide a present-tense basis for concluding that the specific aircraft at issue poses a current risk. This operational standard governs individual mitigation decisions by authorized personnel in the application of reasonable force under the totality of the circumstances and does not limit the information or analysis that may be considered at the approval level in determining whether to authorize a C-UAS operation for a specific event or facility.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Proportionality.</E>
                                     Mitigation actions must be proportionate to the credible threat identified. Personnel must employ the least disruptive effective 
                                    <PRTPAGE P="41502"/>
                                    means of mitigation available under the totality of the circumstances. If equipment is available and time permits, a warning to the remote pilot-in-command should precede any mitigation action. Before taking any mitigation action that may result in the disabling, damage, or destruction of an unmanned aircraft, personnel must consider whether the threat posed by the UAS outweighs the risk of collateral harm to public safety. A mitigation action that creates a greater risk to public safety than the threat it is intended to address is not proportionate and must not be taken. Where a non-mitigation measure is sufficient to eliminate the threat, seizure or destruction of the aircraft should be avoided when feasible. The risk of collateral harm to public safety includes the risk of falling debris, damage to persons or property on the ground, disruption to communications systems, and risks to aviation safety, civilian aviation and aerospace operations, aircraft airworthiness, or the use of the airspace.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Protective purpose limitation.</E>
                                     The authority of 6 U.S.C. 124n(a)(2) is limited to the protection of people, facilities, and assets; a venue or set of venues used for large-scale public gatherings or events; critical infrastructure; and correctional facilities from credible threats posed by unmanned aircraft and UAS. C-UAS authority under this part may not be exercised for the sole purpose of collecting evidence for criminal prosecution or as a substitute for the authority provided by chapter 119 or 206 of title 18, United States Code. Evidence obtained incidental to lawful protective C-UAS operations may be used in subsequent criminal proceedings consistent with applicable law.
                                </P>
                                <P>
                                    (e) 
                                    <E T="03">Mitigation operator requirement.</E>
                                     (1) The person who takes a mitigation action, including activating an RF-emitting system, executing a cyber-based takeover, or otherwise causing a C-UAS system to affect or otherwise impact the flight, control, or communications of a UAS or unmanned aircraft, must hold a current Mitigation Certification covering the technology category being employed, and must possess a valid 14 CFR part 107 remote pilot certificate. This requirement is not satisfied by supervision of an uncertified person by a certified operator; the certified operator must be the individual who directly executes the mitigation command or function.
                                </P>
                                <P>(2) Support functions that do not involve the initiation of mitigation actions, such as detection system monitoring, threat triage and prioritization, ground intercept team dispatch, communications, and administrative functions, do not require Mitigation Certification, but must be performed by personnel trained in accordance with the agency's implementation policy and, where the support function involves operation of systems requiring the authority of 6 U.S.C. 124n(a)(2) or the relief it provides from certain laws, by personnel holding a current Detection and Warning Certification.</P>
                                <P>(3) For operations involving multiple personnel performing distinct roles, the agency's implementation policy must define the roles and responsibilities of each position, identify which positions require Mitigation Certification, and which require Detection and Warning Certification only, and establish the communication and concurrence procedures between the mitigation operator and other personnel.</P>
                                <P>
                                    (f) 
                                    <E T="03">Independent professional judgment.</E>
                                     (1) The certified mitigation operator retains independent professional judgment on whether to initiate a mitigation action.
                                </P>
                                <P>(2) A supervisor, commander, or other official, regardless of rank, may provide operational direction, tactical context, and coordination guidance to the operator, and may direct the operator to withhold or cease mitigation when broader operational considerations warrant.</P>
                                <P>(3) A supervisor, commander, or other official may not direct a certified operator to initiate a mitigation action when the operator has determined that the credible threat standard is not met or that the proportionality requirement of paragraph (c) of this section is not satisfied.</P>
                                <P>(4) The agency's implementation policy must address the chain of command for mitigation decisions and must make clear that non-certified personnel, regardless of rank, may not direct mitigation actions that override the certified operator's professional judgment on whether the conditions for mitigation are present.</P>
                                <P>(5) An operator who declines to initiate mitigation based on a good-faith professional determination that the conditions for mitigation are not met may not be subjected to adverse employment action for that decision.</P>
                                <P>
                                    (g) 
                                    <E T="03">Airspace awareness.</E>
                                     (1) For operations where known authorized manned or unmanned aviation is operating or anticipated in or near the area of operations, the agency's implementation policy or C-UAS Operations Plan must designate a person or position responsible for maintaining real-time awareness of known authorized aviation within the operational area and for ensuring that this information is communicated to personnel authorized to initiate mitigation actions before any mitigation is executed. For purposes of this paragraph, known authorized aviation means any manned or unmanned aircraft that has been identified in the C-UAS Operations Plan, communicated to the C-UAS team during the operation, or otherwise confirmed as lawfully operating in or near the area of operations. The designated person, or the individual filling the designated position, must have the ability to communicate directly with the mitigation operator. No mitigation action may be initiated without reasonable efforts to confirm that the target is not a known authorized aircraft.
                                </P>
                                <P>(2) The scope and formality of this role must be commensurate with the complexity of the aviation environment. For operations with minimal or no known authorized aviation, this role may be performed as an additional duty by the certified operator or other command post personnel; for operations with significant aviation activity, the agency must designate a dedicated individual with airspace awareness and coordination responsibilities. When a target cannot be correlated with any known, authorized aircraft and meets the credible threat standard, mitigation may proceed.</P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.4 </SECTNO>
                                <SUBJECT>Authorized personnel, contractors, and mutual aid.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Officers and employees.</E>
                                     The authority provided by 6 U.S.C. 124n(a)(2) may be exercised only by SLTT law enforcement or correctional agency personnel. No SLTT law enforcement or correctional agency may delegate or transfer the exercise of C-UAS mitigation authority to any person or entity that is not an officer or employee of the agency.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Prohibition on contractor exercise.</E>
                                     Contractors may provide technical support, system maintenance, and training assistance, but may not operate C-UAS mitigation systems, make credible threat determinations, or execute mitigation actions. An arrangement in which a contractor exercises de facto operational control of a C-UAS mitigation system during an operation, including an arrangement described as a turnkey, managed service, or operator-provided C-UAS service, constitutes an unauthorized delegation of authority and is grounds for suspension of accreditation or certification under § 124.5(i). Detection services that do not require the 
                                    <PRTPAGE P="41503"/>
                                    authority of the Act or the relief it provides from certain laws may be provided by contractors.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Mutual aid and regional C-UAS support.</E>
                                     (1) An SLTT law enforcement or correctional agency accredited under 6 U.S.C. 124n(d)(2) may provide C-UAS support to another SLTT law enforcement or correctional agency, including an agency that is not accredited under this part, under a mutual aid agreement, memorandum of understanding, request for assistance, task force arrangement, or other written arrangement authorized by applicable State, local, Tribal, or territorial law.
                                </P>
                                <P>(2) When the requesting or host agency is not accredited under 6 U.S.C. 124n(d)(2), the accredited agency providing C-UAS support is the C-UAS operating agency for purposes of this part and is responsible for compliance with the applicable requirements of this part.</P>
                                <P>(3) Personnel of a non-accredited requesting or host agency may support the operation through ordinary law enforcement, correctional, public safety, evidence-handling, perimeter-security, ground-intercept, evacuation, traffic-control, or incident-command functions. Such personnel may not exercise C-UAS authority under 6 U.S.C. 124n(a)(2), operate systems whose operation requires the authority of or relief from certain laws under 6 U.S.C. 124n, make a credible-threat determination, or initiate any mitigation action, unless those personnel independently satisfy the requirements of this part, hold the applicable certification under § 124.5, and are expressly designated in the accredited C-UAS operating agency's C-UAS Operations Plan to perform that function. Personnel so designated operate under that agency's implementation policy, Agency Approving Official approval, supervision, and compliance responsibility. An individual certification does not, by itself, authorize personnel to exercise 6 U.S.C. 124n(a)(2) authority, and this designation must be established in advance through the C-UAS Operations Plan and the mutual-aid arrangement under paragraph (c)(4) of this section.</P>
                                <P>(4) The written mutual aid arrangement must identify the requesting or host agency, the accredited agency providing C-UAS support, the legal basis for the accredited agency's personnel to operate in the host jurisdiction, the allocation of operational responsibilities, and the handling of C-UAS-derived information consistent with §§ 124.14 and 124.15.</P>
                                <P>(5) For multi-jurisdictional operations, the participating agencies must identify a lead C-UAS agency for tactical C-UAS coordination. The lead C-UAS agency must be an accredited agency unless the operation is conducted under Federal authority pursuant to § 124.19. A non-accredited requesting or host agency may serve as the lead public safety, law enforcement, correctional, or incident-command agency for the overall event or incident, but may not serve as the lead C-UAS agency unless accredited under this part.</P>
                                <P>(6) An accredited agency may enter into standing regional, county, statewide, or other multi-jurisdictional arrangements to provide recurring or on-call C-UAS support to non-accredited agencies. A standing arrangement does not itself authorize a mitigation operation; each mitigation operation remains subject to the applicable requirements of this part.</P>
                                <P>(7) Nothing in this part requires a small, rural, or otherwise resource-limited SLTT law enforcement or correctional agency to acquire C-UAS equipment, obtain accreditation, or establish an independent C-UAS program in order to receive C-UAS support from an accredited agency.</P>
                                <P>
                                    (d) 
                                    <E T="03">Anti-circumvention.</E>
                                     (1) No SLTT law enforcement or correctional agency, officer, employee, contractor, vendor, or other person may structure or use a mutual aid, regional support, managed-service, technical-support, or other arrangement to evade the requirements of this part.
                                </P>
                                <P>(2) Prohibited circumvention includes using an accredited agency as a nominal sponsor while a non-accredited agency, contractor, vendor, or other entity exercises de facto operational control of C-UAS activity requiring the authority of or relief from certain laws under 6 U.S.C. 124n; allowing personnel who lack the certifications required by § 124.5 to exercise C-UAS authority; using systems outside the requirements of § 124.7; avoiding the coordination, reporting, privacy, sensitive-information, or compliance requirements of this part; or acquiring third-party intercepted communications in a manner inconsistent with § 124.14(i).</P>
                                <P>(3) A mutual aid, regional support, statewide support, county support, or multi-jurisdictional C-UAS arrangement is not circumvention merely because the requesting or host agency is not accredited, provided that the C-UAS operating agency is accredited, the personnel exercising C-UAS authority hold the required certifications, and the operation is conducted in compliance with this part.</P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.5 </SECTNO>
                                <SUBJECT>Training and certification.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Training and certification structure.</E>
                                     This section establishes the training and certification structure implementing the requirements of 6 U.S.C. 124n(d)(2)(A). Detection and Warning Certification governs training for detection and warning operations under 6 U.S.C. 124n(b)(1)(A) and (B). Mitigation Certification governs training and certification for mitigation operations under 6 U.S.C. 124n(b)(1)(C), (D), and (F). A current Detection and Warning Certification is a prerequisite both for initial enrollment in the mitigation training course and for mitigation recertification.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Agency implementation policy.</E>
                                     Before conducting any operations under this part, an SLTT law enforcement or correctional agency must adopt an agency implementation policy or detection and warning policy and complete the portal attestation in accordance with § 124.6, and must authorize each operation by a C-UAS Operations Plan in accordance with § 124.8, consistent with the other requirements and obligations of this part and applicable laws and policies.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Detection and Warning Certification.</E>
                                     The Attorney General, acting through the Director of the Federal Bureau of Investigation, will develop and maintain through the NCUTC an online training curriculum for detection and warning operations, accessible through a secure web-based training portal. The curriculum includes the confiscation authority of 6 U.S.C. 124n(b)(1)(E), evidence preservation, and chain of custody. Only those personnel who have completed the curriculum and passed the post-course assessment may exercise the authorities described in 6 U.S.C. 124n(b)(1)(A), (B), and (E). Upon successful completion, the NCUTC training portal automatically issues a Detection and Warning Certification. Detection and Warning Certification is issued only by the NCUTC, and detection and warning training or certification obtained from another agency or a private entity does not satisfy this requirement. Detection and warning activity conducted using systems that do not require the authority of 6 U.S.C. 124n is not subject to this requirement. Upon successful completion, the training portal records the individual's name, agency, date of completion, and certification status in the NCUTC certification database, which is the system of record for all certifications issued under this section. Each agency must maintain a roster of 
                                    <PRTPAGE P="41504"/>
                                    its certified personnel drawn from the NCUTC certification database and must verify the certification status of personnel assigned to C-UAS operations. Vendor-specific and system-level operator training is the responsibility of each agency through its own training procedures and is not part of the detection and warning curriculum.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Mitigation training and certification.</E>
                                     (1) The Attorney General, acting through the Director of the Federal Bureau of Investigation, designates the NCUTC as the national schoolhouse and sole certifying authority for personnel exercising mitigation authorities under 6 U.S.C. 124n(b)(1)(C), (D), and (F), as required by 6 U.S.C. 124n(d)(2)(A)(i). Only personnel who hold a valid Mitigation Certification may exercise these authorities. The NCUTC mitigation training program consists of the mitigation training course and such advanced and supplemental courses as the Attorney General, acting through the Director of the Federal Bureau of Investigation, approves. Each course is evaluated on a pass or fail basis and requires demonstrated proficiency in each mitigation technology category it covers; a person who does not demonstrate proficiency in each category does not pass that course. A person obtains Mitigation Certification by passing the mitigation training course and may extend the scope of that certification to additional mitigation technology categories by passing an advanced or supplemental course covering those additional categories. Failure to pass a particular advanced or supplemental course does not affect the scope of a certification already held.
                                </P>
                                <P>(2) A person who holds a current Mitigation Certification under this paragraph (d) may conduct mitigation operations at a correctional facility. An abbreviated Correctional Mitigation Certification, limited to correctional-facility operations, is available for personnel who will operate only at correctional facilities.</P>
                                <P>(3) The mitigation training course under this paragraph is delivered at the NCUTC. The Attorney General, acting through the Director of the Federal Bureau of Investigation, may authorize the Federal Law Enforcement Training Centers or another qualified Federal training provider to deliver the mitigation training course at one or more additional sites, provided the NCUTC retains approval authority over curriculum and standards, exercises oversight of the delivery, and issues all certifications upon verified completion. Any such authorization is at the sole discretion of the Attorney General, acting through the Director, confers no entitlement on any agency or training provider, and may be modified or withdrawn at any time.</P>
                                <P>
                                    (e) 
                                    <E T="03">Correctional mitigation training and certification.</E>
                                     The NCUTC offers an abbreviated Correctional Mitigation Certification for personnel who will conduct mitigation operations only at correctional facilities. The correctional course of instruction is shorter than the mitigation training course under paragraph (d) of this section because the fixed perimeter and persistent-threat environment of a correctional facility reduce the operational setup and mission-planning instruction required. The correctional course of instruction addresses the persistent-threat environment, perimeter operations, and the legal and safety considerations of correctional settings. A person who holds only the Correctional Mitigation Certification may conduct mitigation operations at a correctional facility but may not conduct other mitigation operations under this part. The NCUTC may arrange for the Federal Law Enforcement Training Centers or another qualified training provider to deliver the correctional curriculum, provided the NCUTC retains approval authority over curriculum and standards, exercises oversight of the delivery, and issues all certifications upon verified completion.
                                </P>
                                <P>
                                    (f) 
                                    <E T="03">Training standards.</E>
                                     The mitigation training course, as administered by the NCUTC, will include instruction on the legal, operational, and technological aspects of C-UAS operations as required by section 8606(b)(1) of the SAFER SKIES Act, including FAA coordination and airspace procedures, spectrum coordination requirements, real-time air traffic control notification procedures, FBI and DHS notification requirements, and the operational use of authorized mitigation technologies. The Attorney General, in coordination with the Secretary of Homeland Security, the Secretary of Defense, the Secretary of Transportation, and the Administrator of the Federal Aviation Administration, will approve training program standards and may approve additional courses of instruction for specialized C-UAS operations. The mitigation training course must include scenario-based instruction on the application of the credible threat standard.
                                </P>
                                <P>
                                    (g) 
                                    <E T="03">Eligible personnel.</E>
                                     Personnel eligible for Mitigation Certification or Detection and Warning Certification must have assigned duties that include the security or protection of people, facilities, or assets, as specified in 6 U.S.C. 124n(a)(2), and must be officers or employees of an SLTT law enforcement or correctional agency accredited by the Attorney General acting through the Director of the Federal Bureau of Investigation. The NCUTC, under the authority of the Attorney General, may establish additional attendance prerequisites.
                                </P>
                                <P>
                                    (h) 
                                    <E T="03">Sufficiency of certification.</E>
                                     Successful completion of the applicable training requirement, combined with the use of systems within technology categories on the Authorized Technologies List and specific systems on the Authorized Systems List where populated, and compliance with the requirements of this part, satisfies the training and certification prerequisites of 6 U.S.C. 124n(d)(2)(A) for the exercise of the corresponding authorities under 6 U.S.C. 124n(a)(2).
                                </P>
                                <P>
                                    (i) 
                                    <E T="03">Suspension.</E>
                                     The Attorney General, acting through the Director of the Federal Bureau of Investigation or the Director's designee, may suspend the Mitigation Certification or Detection and Warning Certification of any individual, or the accreditation of any SLTT law enforcement or correctional agency, for failure to comply with the requirements of this part, violation of the conditions of certification, or for any conduct that demonstrates unfitness to exercise C-UAS authority. Suspension of a certification or accreditation under this section is distinct from suspension of C-UAS authority by the Attorney General or the Secretary of Homeland Security under section 8605(f) of the SAFER SKIES Act, which is addressed in § 124.16. Neither a suspension of certification under this section nor an enforcement action against an individual under section 8605(f) of the SAFER SKIES Act prevents or bars the responsible agency from taking any additional actions it deems necessary to address the circumstances that led to suspension or enforcement action by the Attorney General or designee.
                                </P>
                                <P>
                                    (j) 
                                    <E T="03">Suspension notice.</E>
                                     A suspension will be communicated in writing and will specify the basis for the action and any available remedial steps. The suspension notice must include the factual basis for the action in sufficient detail to enable the affected individual or agency to respond. In exigent circumstances, the Director of the Federal Bureau of Investigation or the Director's designee may immediately suspend a certification or accreditation pending administrative review without the requisite written notice when continued exercise of C-UAS authority poses a risk to aviation safety, public safety, or national security. In such cases, the Director or the Director's 
                                    <PRTPAGE P="41505"/>
                                    designee must provide the requisite notice within 3 days of the suspension.
                                </P>
                                <P>
                                    (k) 
                                    <E T="03">Administrative review.</E>
                                     An individual or agency that receives a suspension notice may request administrative review within 30 calendar days of receipt. The Attorney General, acting through the Director of the Federal Bureau of Investigation, will designate a reviewing official of the Department of Justice who did not participate in or supervise the initial decision. The affected party may submit documentary evidence and written witness statements in support of its response. The reviewing official will consider the written submissions of both parties, may conduct an informal hearing at the reviewing official's discretion, and will issue a written determination within 60 calendar days of receipt of the request, stating the factual findings and the basis for the determination. The reviewing official may affirm the action, modify its terms, impose conditions for reinstatement, or reverse the action. A suspension that is affirmed remains in effect until reinstatement under paragraph (m) of this section or the expiration of the suspended certification or accreditation, whichever occurs first.
                                </P>
                                <P>
                                    (l) 
                                    <E T="03">Conditions.</E>
                                     The Attorney General, acting through the Director of the Federal Bureau of Investigation, may issue a certification or accreditation subject to conditions, and may modify the conditions of a certification or accreditation, consistent with the standards and procedures applicable to suspension under this section.
                                </P>
                                <P>
                                    (m) 
                                    <E T="03">Reinstatement.</E>
                                     An individual or agency whose certification or accreditation has been suspended may apply for reinstatement after completing the remedial steps specified in the suspension notice or the reviewing official's determination. An individual Mitigation Certification may alternatively be reinstated upon the successful recompletion of the full mitigation training course.
                                </P>
                                <P>
                                    (n) 
                                    <E T="03">Transition for previously trained personnel.</E>
                                     Personnel holding a Mitigation Certification issued by the NCUTC before the effective date of this part must complete the detection and warning curriculum under paragraph (c) of this section by September 29, 2026. During that period, the Mitigation Certification remains valid, and the Detection and Warning Certification prerequisite for Mitigation Certification is deemed satisfied. An agency's accreditation is not affected while its personnel complete the curriculum during the transition period.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.6 </SECTNO>
                                <SUBJECT>Agency implementation policy.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Requirement.</E>
                                     Before conducting any operations under this part, each SLTT law enforcement or correctional agency must adopt and maintain an agency implementation policy governing the exercise of authority under 6 U.S.C. 124n(a)(2). The agency implementation policy is comprehensive. It governs all operations the agency conducts under this part, including detection and warning operations, and it addresses the detection and warning matters listed in paragraph (g) of this section. An agency that adopts and maintains an agency implementation policy under this paragraph is not required to adopt a separate policy under paragraph (g) of this section. An agency that conducts only detection and warning operations may instead adopt the abbreviated policy under paragraph (g) of this section. The agency implementation policy must, at a minimum:
                                </P>
                                <P>(1) Designate an Agency Approving Official meeting the requirements of § 124.2;</P>
                                <P>(2) Designate the personnel authorized to exercise C-UAS authority and describe the recurrent training requirements applicable to such personnel;</P>
                                <P>(3) Establish procedures consistent with § 124.14 for the handling, retention, and dissemination of data acquired during C-UAS operations, including written anonymization standards specifying the aggregation thresholds, identifier suppression, and re-identification risk assessment used to qualify a data product as pattern data;</P>
                                <P>(4) Include provisions for public notification regarding the potential use of C-UAS authority within the agency's jurisdiction;</P>
                                <P>(5) Ensure compliance with the requirements of this part; and</P>
                                <P>(6) Detail standing tactical procedures governing the execution of C-UAS operations, including engagement protocols that account for the risk to persons and property on the surface and in the air before engagement, escalation procedures, use of force considerations, ground intercept team procedures, render safe procedures, evidence collection and chain-of-custody procedures, communications procedures, system operating procedures, data handling and purge procedures consistent with the retention requirements of this part, operation plan requirements, and post-operation procedures that incorporate data purge verification.</P>
                                <P>
                                    (b) 
                                    <E T="03">Legal counsel review.</E>
                                     The implementation policy must be reviewed and concurred in by the agency's legal counsel before adoption and upon each annual renewal. The review must specifically address the privacy and civil liberties requirements of this part, including the data retention, minimization, and dissemination provisions, and the interplay of proposed C-UAS operations and implementing policies with applicable State, local, Tribal, or territorial law. For an agency that has a designated official responsible for the agency's privacy and civil liberties compliance, regardless of title, the implementation policy must also be reviewed by that official.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Alternative certification for agencies without in-house counsel.</E>
                                     For an agency without in-house counsel, the review required by paragraph (b) of this section may alternatively be satisfied by review and certification by a State, local, territorial, or Tribal attorney's office that the implementation policy addresses each element required by paragraph (a) of this section. An agency obtaining a certification under this paragraph (c) must document the basis for using this paragraph (c). Certification pursuant to this paragraph (c) does not relieve the agency of any compliance obligation under this part.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Portal attestation.</E>
                                     Upon adoption of the implementation policy, the agency head or designee must certify compliance through the Federal C-UAS coordination portal by attesting that the agency has adopted an implementation policy addressing each element required by paragraph (a) of this section. The portal records the certifying official, agency, and date of attestation. The implementation policy is not subject to pre-approval by the NCUTC. The NCUTC retains authority to audit implementation policies and to suspend certification or accreditation under § 124.5. The attestation must be renewed annually.
                                </P>
                                <P>
                                    (e) 
                                    <E T="03">Retention and availability.</E>
                                     The agency must retain the implementation policy and make it available to the Attorney General or the Secretary of Homeland Security, or their designee, upon request, including during compliance audits under § 124.16.
                                </P>
                                <P>
                                    (f) 
                                    <E T="03">Operating without attestation.</E>
                                     An agency that conducts operations under this part without a current portal attestation is in violation of this part, and the absence of an attestation constitutes grounds for compliance action under § 124.16.
                                </P>
                                <P>
                                    (g) 
                                    <E T="03">Detection and warning policy.</E>
                                     An SLTT law enforcement or correctional agency that conducts only detection and warning operations requiring the authority of, or the relief from certain laws provided by, 6 U.S.C. 124n may adopt a detection and warning policy in 
                                    <PRTPAGE P="41506"/>
                                    lieu of the implementation policy required by paragraph (a) of this section. A detection and warning policy must satisfy the requirements of this section, except that it need not include the standing tactical procedures of paragraph (a)(6) of this section. The agency must designate an Agency Approving Official under paragraph (a)(1) of this section and complete the portal attestation under paragraph (d) of this section, which must be renewed annually. For purposes of that attestation, a detection and warning policy need address only the elements of paragraph (a) of this section that apply to detection and warning operations.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.7</SECTNO>
                                <SUBJECT>Authorized technologies.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Two-list authorization framework.</E>
                                     The technology authorization framework consists of two complementary lists. The Authorized Technologies List identifies the technology categories authorized for SLTT law enforcement and correctional agency C-UAS operations. The Authorized Systems List identifies specific systems, at the make and model level, that have completed interagency evaluation within those technology categories and stated operating restrictions. Both lists are maintained jointly by the Department of Justice, the Department of Homeland Security, the Department of Defense, the Department of Transportation and Federal Aviation Administration, the Federal Communications Commission, and the National Telecommunications and Information Administration, consistent with 6 U.S.C. 124n(d)(2)(A)(iii) and section 8606(a)(4) of the SAFER SKIES Act.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">General requirement.</E>
                                     An SLTT law enforcement or correctional agency exercising authority under 6 U.S.C. 124n(a)(2) may deploy only systems within technology categories listed on the Authorized Technologies List. When the Authorized Systems List has been populated for a given technology category, the agency may deploy only specific systems listed on the Authorized Systems List within that category, subject to the advance coordination requirements of § 124.9. For technology categories on the Authorized Technologies List for which the Authorized Systems List has not yet been populated, the agency may deploy specific systems within those categories provided that an operator holds Mitigation Certification covering that technology category and has completed manufacturer or vendor training on the specific system to be deployed, subject to the advance coordination requirements of § 124.9.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Scope of the list requirement.</E>
                                     When operating under the authorities or statutory reliefs in 6 U.S.C. 124n(a)(2), SLTT law enforcement or correctional agencies may employ only listed technology categories, and, where the Authorized Systems List is populated, listed systems. Technology that an SLTT law enforcement or correctional agency may lawfully employ without the authorities or reliefs provided by 6 U.S.C. 124n(a)(2) is not subject to the requirements of this section and remains available to agencies on the same basis as before the SAFER SKIES Act. The detection and warning training curriculum will address the distinction between technology categories subject to and not subject to this section.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Mitigation technology and training alignment.</E>
                                     An SLTT law enforcement or correctional agency may employ mitigation systems only in those technology categories covered by the NCUTC mitigation courses completed by its mitigation-certified personnel. NCUTC may create an additional mitigation module covering the technology category when a new technology category is added to the Authorized Technologies List. Mitigation-certified personnel who completed the NCUTC mitigation course prior to the addition of this new content must successfully complete additional NCUTC training on the new technology category prior to using any system on the Authorized Systems List under that category.
                                </P>
                                <P>
                                    (e) 
                                    <E T="03">Scope of interception authority.</E>
                                     Systems may be used to intercept communications to or from an unmanned aircraft or UAS only to the extent necessary to support an action described in 6 U.S.C. 124n(b)(1). Any interception, acquisition, maintenance, use of, or access to communications to or from an unmanned aircraft or UAS under this section must be conducted in a manner consistent with the First and Fourth Amendments to the Constitution of the United States and applicable provisions of Federal law.
                                </P>
                                <P>
                                    (f) 
                                    <E T="03">Maintenance of the lists.</E>
                                     The Authorized Technologies List and Authorized Systems List, including the criteria and procedures for evaluating, listing, renewing, suspending, and removing technology categories and systems, are established and maintained through the interagency process described in 6 U.S.C. 124n(d)(2)(A)(iii) and section 8606(a)(4) of the SAFER SKIES Act. The Authorized Systems List is updated by that interagency process and published on the designated interagency C-UAS portal. Each RF-emitting system listed on the Authorized Systems List will have completed a system-level spectrum evaluation through the interagency process before listing, addressing potential interference with non-Federal spectrum users, compatibility with Federal spectrum users, and potential interference with aviation safety systems. System-level evaluations are reviewed and renewed at intervals determined through the interagency process and upon any system change to its operating capabilities, functions, radio frequency characteristics, or power levels that may alter its radio frequency characteristics, capabilities, functions, or assessed configurations. Minor updates that do not alter a system's performance, capabilities, functions, radio frequency characteristics, or assessed configurations do not require renewed evaluation.
                                </P>
                                <P>
                                    (g) 
                                    <E T="03">Emergency suspension.</E>
                                     Upon receipt of an emergency suspension notice issued through the interagency process for the Authorized Technologies List and Authorized Systems List, an SLTT law enforcement or correctional agency must immediately cease deployment of the affected system or technology category. Grounds for emergency suspension include discovery of a critical safety defect, identification of a supply chain compromise or cybersecurity vulnerability, a determination that a system's radio frequency characteristics differ materially from those evaluated during spectrum evaluation, or a finding by any agency participating in the interagency process that continued deployment poses an unacceptable risk. The SLTT law enforcement or correctional agency may not resume deployment of the affected system or technology category until the suspension is lifted or the system or category is restored to the applicable list, and the agency must comply with any conditions attached to the lifting of the suspension or the restoration of the system or category to the applicable list.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.8</SECTNO>
                                <SUBJECT>C-UAS Operations Plan.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Requirement and function.</E>
                                     Each mitigation operation, and each detection and warning operation conducted under this part using systems that require the authority of, or relief from certain laws under, 6 U.S.C. 124n, must be authorized by a C-UAS Operations Plan signed by the agency's Agency Approving Official. Section 124.12 sets out the conditions specific to detection and warning operations. The signed C-UAS Operations Plan is the instrument authorizing the operation on behalf of 
                                    <PRTPAGE P="41507"/>
                                    the SLTT law enforcement or correctional agency and certifies that the operation is consistent with the agency's implementation or detection and warning policy, that the operators are agency personnel who hold the required training and certification, and that the risk-based assessment factors of paragraph (e) of this section have been addressed. The agency may not commence mitigation operations until both the advance coordination process under § 124.9 and the signed C-UAS Operations Plan are complete.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Legal counsel certification.</E>
                                     The C-UAS Operations Plan must include a certification by the agency's legal counsel or, for an agency without in-house counsel, the applicable prosecuting authority, that the plan has been reviewed for legal sufficiency. The certification may take the form of a signature block, stamp, or attestation on the plan.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Form.</E>
                                     The C-UAS Operations Plan must be prepared on the standardized form prescribed by the Attorney General. The form is structured to use short-answer fields, selection-based fields, and map or diagram attachments, and does not require narrative legal analysis or repetition of standing procedures addressed in the agency's implementation policy. The form may use conditional fields keyed to the type of operation, so that each operation completes only the fields applicable to it; for a detection and warning operation, the fields specific to mitigation, such as mitigation-system parameters and render safe planning, do not apply.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Content.</E>
                                     The C-UAS Operations Plan must address, at a minimum and to the extent applicable to the operation:
                                </P>
                                <P>(1) Operation identification, including the submitting agency, points of contact, the Agency Approving Official, the operation type, planned dates, geographic location, venue type, any Special Event Assessment Rating or National Special Security Event designation, and the identification of any mutual aid agencies;</P>
                                <P>(2) Systems and airspace, including the systems to be deployed by reference to the Authorized Systems List or Authorized Technologies List category; a description of each system's configuration and the hardware version, firmware revision, and software version of each system as deployed; RF-emitting system parameters; class of airspace; and anticipated flight restrictions;</P>
                                <P>(3) Coordination confirmation, including operator certification status, compliance with the agency implementation policy, the legal counsel certification, and compliance with the privacy and civil liberties requirements of this part; and</P>
                                <P>(4) Operational planning elements, including deployment configuration and spectrum deconfliction, personnel and team assignments, render safe and contingency planning, known authorized manned and unmanned aviation and deconfliction processes and procedures, communications, investigative response and data handling, and demobilization.</P>
                                <P>
                                    (e) 
                                    <E T="03">Risk-based assessment.</E>
                                     The C-UAS Operations Plan must address the following factors: potential impacts to aviation safety, civilian aviation and aerospace operations, aircraft airworthiness, or the use of the airspace; procedures to comply with any technical and siting limitations; options for mitigating identified potential impacts; potential consequences if potential impacts are not mitigated; the ability to provide reasonable advance notice to aircraft operators of both manned and unmanned aircraft; the setting and character of the facility or asset; for National Special Security Events and Special Event Assessment Rating events, the event characteristics; and the potential consequences to public safety if UAS threats are not mitigated. For National Special Security Events and Special Event Assessment Rating events, a plan that identifies the systems, airspace environment, and coordination elements from which the assessment can be derived satisfies this paragraph without separately addressing each factor in narrative form. Nothing in this part may be interpreted as limiting the authority of the Administrator of the Federal Aviation Administration to manage the navigable airspace, assess potential aviation safety risks, and implement such mitigations as the Administrator determines appropriate.
                                </P>
                                <P>
                                    (f) 
                                    <E T="03">Timing and submission.</E>
                                     The C-UAS Operations Plan must be completed before the commencement of operations and submitted to the Federal Bureau of Investigation and Department of Homeland Security through the designated Federal C-UAS coordination portal as a supplement to the advance notification not fewer than 7 calendar days before the commencement of operations, or as early as practicable when the applicable notification timeline does not permit 7 calendar days. For a detection and warning operation that is not subject to the advance notification requirement of § 124.9, the C-UAS Operations Plan must be submitted through the designated Federal C-UAS coordination portal before the commencement of operations, for situational awareness and recordkeeping; such submission is not an advance notification under § 124.9 and does not trigger Federal Aviation Administration or Federal Communications Commission coordination. The plan may be updated after submission to reflect changes resulting from Federal Aviation Administration or Federal Communications Commission coordination. Material updates must be resubmitted promptly. Federal Aviation Administration and Federal Communications Commission coordination is valid for the system configuration and the firmware and software version coordinated for the operation. A change in configuration, firmware, or software version does not require re-coordination if it does not materially change the system's radio frequency emission characteristics, its operating frequencies and power levels, or other factors potentially impacting aviation safety from those previously coordinated. A change that would operate outside the frequencies or power levels coordinated for the operation requires re-coordination before deployment; a summary of the change must be provided to the Federal Aviation Administration and Federal Communications Commission to determine if re-coordination is necessary. The Federal Aviation Administration and the Federal Communications Commission may identify by guidance categories of configuration, firmware, or software changes that are deemed to materially affect radio frequency emission characteristics and require re-coordination. Federal review of the C-UAS Operations Plan is for deconfliction and situational awareness purposes and does not constitute approval or disapproval of the operation. For an event, area, or period in which a high volume of simultaneous operations is anticipated, the Federal Bureau of Investigation, in coordination with the Federal Aviation Administration, may establish an earlier submission deadline for affected operations and will communicate that deadline to affected agencies in advance through the designated portal or the lead C-UAS agency.
                                </P>
                                <P>
                                    (g) 
                                    <E T="03">Relationship to implementation policy.</E>
                                     The C-UAS Operations Plan is an event-specific or operation-specific document. Standing tactical procedures required by § 124.6(a) must be addressed in the agency's implementation policy, and the C-UAS Operations Plan must reference the implementation policy by title and version rather than repeating standing procedures.
                                    <PRTPAGE P="41508"/>
                                </P>
                                <P>
                                    (h) 
                                    <E T="03">Operational windows.</E>
                                     (1) An individual C-UAS Operations Plan may authorize operations for a period not to exceed 30 consecutive calendar days, except as provided in paragraph (h)(2) of this section. For operations requiring a longer duration, the agency must submit a renewal plan before the expiration of the current operational window; the renewal plan may incorporate the prior plan by reference and address only material changes. The agency must submit a renewal plan, through the designated Federal C-UAS coordination portal under § 124.8(f), before the expiration of the current operational window.
                                </P>
                                <P>(2) For fixed-site facilities for which SLTT law enforcement and correctional agencies conduct ongoing persistent-protection operations, including correctional facilities, critical infrastructure sites, other permanent facilities with a continuing C-UAS mission, and venues where the agency expects to provide recurring C-UAS coverage within the authorization period, the Agency Approving Official may authorize a standing operational window of up to 365 calendar days, renewable upon submission of a renewal plan. The advance notification for a standing operational window must specify the venue and anticipated events or coverage periods; for a detection and warning operation not subject to the advance notification requirement of § 124.9, the C-UAS Operations Plan must specify the venue, the area covered, which may be stated as a radius around the site, and the anticipated coverage periods. Material changes, including a new event, new systems, or a changed threat environment, require an update to the advance notification under § 124.9(a) or, for such a detection and warning operation, an updated C-UAS Operations Plan. Federal coordination requirements continue to apply to each event within a standing window, including lead C-UAS agency coordination under § 124.10 and per-event coordination among the Department of Transportation, the Federal Aviation Administration, and the Federal Communications Commission.</P>
                                <P>(3) No C-UAS Operations Plan may authorize an indefinite or open-ended operational window.</P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.9</SECTNO>
                                <SUBJECT>Advance coordination, notification, and authorization.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Advance notification.</E>
                                     (1) Before conducting any mitigation operation under 6 U.S.C. 124n(a)(2), an SLTT law enforcement or correctional agency must submit an advance notification through the designated Federal C-UAS coordination portal not fewer than 30 calendar days before the commencement of the operational period. When 30 calendar days is not feasible, the agency must submit the advance notification as early as the circumstances permit, with sufficient lead time to allow the Federal Bureau of Investigation, the Department of Homeland Security, the Department of Transportation, the Federal Aviation Administration, and the Federal Communications Commission to complete their respective reviews, and must include a brief explanation of the circumstances that prevented submission within the 30-day standard.
                                </P>
                                <P>(2) The advance notification is a coordination document that routes the relevant data elements to each recipient agency through a single submission. The advance notification is not a request for approval by the Department of Justice or the Department of Homeland Security, and the absence of a response from the Department of Justice or the Department of Homeland Security does not affect the agency's authority to proceed.</P>
                                <P>(3) The advance notification must identify the submitting SLTT law enforcement or correctional agency, the planned dates and geographic location of the operation, the systems to be deployed by reference to the Authorized Systems List or Authorized Technologies List category, RF-emitting system parameters, a characterization of the airspace and operational environment, and confirmation of operator certification status and compliance with the agency implementation policy and the privacy requirements of this part.</P>
                                <P>
                                    (b) 
                                    <E T="03">C-UAS Operations Plan.</E>
                                     Each mitigation operation must also be authorized by a C-UAS Operations Plan in accordance with § 124.8. The agency may not commence mitigation operations until both the advance coordination process under this section and the signed C-UAS Operations Plan are complete. The SLTT law enforcement or correctional agency must also submit a comparable advance notification to the State if required by State law or policy.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">FBI and DHS notification and routing.</E>
                                     The Attorney General, through the Federal Bureau of Investigation and the Department of Homeland Security, receives the advance notification for purposes of deconflicting planned SLTT law enforcement or correctional agency C-UAS operations with any ongoing or planned Federal C-UAS, law enforcement, or national security operations. Until the portal is fully established, an SLTT law enforcement or correctional agency must notify the Federal Bureau of Investigation and Department of Homeland Security through a channel designated by the Federal Bureau of Investigation and Department of Homeland Security for that purpose.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">DOT/FAA coordination.</E>
                                     Before conducting any mitigation operation, an SLTT law enforcement or correctional agency must coordinate with the Department of Transportation and the Federal Aviation Administration through the coordination mechanism the Federal Aviation Administration has designated. The agency must provide the systems to be deployed, the geographic coordinates of each proposed deployment and enforcement location, the expected duration of the operation, and a characterization of the airspace environment. The Administrator of the Federal Aviation Administration may establish such flight restrictions as the Administrator determines necessary in his sole discretion for reasons of aviation safety. The absence of a formal flight restriction does not preclude mitigation action in exigent circumstances when a credible threat exists and the requirements of this part are otherwise satisfied.
                                </P>
                                <P>
                                    (e) 
                                    <E T="03">Categorical FAA determinations.</E>
                                     The Federal Aviation Administration may issue categorical determinations for specific combinations of authorized technologies, geographic locations, and airspace environments. When a proposed mitigation operation falls within the parameters of a categorical determination by the Federal Aviation Administration, individual case-by-case Federal Aviation Administration coordination is not required, provided the agency operates within the conditions specified in the determination and notifies the Federal Aviation Administration through the Federal Aviation Administration-designated coordination mechanism.
                                </P>
                                <P>
                                    (f) 
                                    <E T="03">FCC authorization.</E>
                                     Before deploying any C-UAS system (whether detection and warning only or mitigation) that involves the emission of radio waves, an SLTT law enforcement or correctional agency must obtain authorization to use that system consistent with Title III of the Communications Act of 1934, as amended. The system must comply with any relevant regulations, policies, and guidance administered by the Federal Communications Commission, and an SLTT law enforcement or correctional agency must submit a request to the Federal Communications Commission through the advance notification process and as directed by the Federal Communications Commission. The 
                                    <PRTPAGE P="41509"/>
                                    Federal Communications Commission will also issue waivers, as appropriate, to C-UAS equipment vendors and manufacturers to allow them to import and sell C-UAS mitigation equipment that employs radio frequency interdiction technologies or electronic counter measures to authorized SLTT law enforcement and correctional agencies.
                                </P>
                                <P>
                                    (g) 
                                    <E T="03">Emergency exception.</E>
                                     When a credible threat poses an imminent risk to human life and advance coordination under this section is not practicable, an SLTT law enforcement or correctional agency may take mitigation action. The agency must complete the notifications required by this section as soon as practicable, and in any event within two hours of the action. If the mitigation action involves an RF-emitting C-UAS system, the agency must additionally comply with the real-time notification requirements of § 124.11. Each invocation of this exception must be documented in the post-operation report with a specific explanation of why advance coordination was not feasible. This exception may not be invoked as a routine alternative to advance coordination, and a pattern of repeated invocations may result in compliance review under § 124.16, accreditation or certification suspension, and penalties under section 8605(f) of the SAFER SKIES Act. The compliance audit program will establish the criteria for identifying patterns of emergency invocations that warrant review.
                                </P>
                                <P>
                                    (h) 
                                    <E T="03">Federal coordination.</E>
                                     Before conducting any operation under this part within a security or protection mission overseen by a Federal Government entity, or within an area, facility, waterway, or other area over which a Federal Government entity exercises a security or protection responsibility, the agency must coordinate with that Federal Government entity through the advance coordination process under § 124.9 before conducting the operation. The Federal Aviation Administration's general regulatory authority over the navigable airspace does not by itself trigger this requirement; airspace safety coordination is addressed in § 124.8 and § 124.11.
                                </P>
                                <P>
                                    (i) 
                                    <E T="03">Detection and warning operations.</E>
                                     Detection and warning operations that do not actively transmit radio frequency energy and do not affect aviation safety are not subject to the advance coordination requirements of this section.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.10</SECTNO>
                                <SUBJECT>Interagency and lead-agency coordination.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Early coordination and notice of intent.</E>
                                     For operations in support of National Special Security Events, events rated Special Event Assessment Rating 1 through 3, or other events where Federal C-UAS operations are anticipated, an SLTT law enforcement or correctional agency should notify the local FBI field office of its intent to provide C-UAS coverage as early as practicable and before the 30-day advance notification standard of § 124.9. The designated Federal C-UAS coordination portal includes a notice-of-intent function that allows an agency to register its intent to cover a future event without completing the full advance notification. A notice of intent is informational only and does not trigger the advance coordination process, the Federal Aviation Administration or Federal Communications Commission review, or any timeline obligation.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Special event coordination.</E>
                                     When the Federal Bureau of Investigation receives an SLTT law enforcement or correctional agency advance notification or notice of intent for an event at which Federal C-UAS operations are also planned or under consideration, the Federal Bureau of Investigation will present the notification to the interagency C-UAS coordination process maintained by the Department of Justice and the Department of Homeland Security, will serve as the conduit for SLTT law enforcement and correctional agency equities in that process, and will communicate the results to the SLTT law enforcement or correctional agency, including any Federal operational parameters or deconfliction requirements that may affect the SLTT law enforcement or correctional agency C-UAS operation. The interagency coordination process does not approve or disapprove SLTT law enforcement or correctional agency C-UAS operations.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Tactical coordination under a lead C-UAS agency.</E>
                                     An SLTT law enforcement or correctional agency conducting C-UAS operations at an event or location for which a lead C-UAS agency has been designated must operate under the tactical coordination of the lead C-UAS agency for the duration of the event. Tactical coordination includes the assignment of system deployment locations, operating frequencies, detection and mitigation sectors, ground intercept team sectors, render safe locations, communications channels, and risk to persons and property on the surface or in the air. The SLTT law enforcement or correctional agency's C-UAS Operations Plan for the event must be developed in coordination with the lead C-UAS agency and must conform to the lead agency's overall C-UAS operational framework for the event. An SLTT law enforcement or correctional agency coordinating with a lead C-UAS agency acts under its own certified authority under 6 U.S.C. 124n(a)(2); tactical coordination merely integrates the SLTT law enforcement or correctional agency C-UAS operation into a unified C-UAS posture. Where geographic responsibilities are divided among multiple Federal agencies, the SLTT law enforcement or correctional agency must coordinate with the sector-level lead Federal agency responsible for the geographic area in which the SLTT law enforcement or correctional agency intends to operate. Whenever Federal and SLTT operations will be conducted at the same event, or whenever the Federal and SLTT operations will overlap in geographic area and time, the Federal agency will be the lead C-UAS agency. An SLTT law enforcement or correctional agency may serve as the lead C-UAS agency only where multiple SLTT agencies are operating in the same area and no Federal agency is involved.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Coordination required.</E>
                                     An SLTT law enforcement or correctional agency that does not accept tactical coordination by the designated lead C-UAS agency may not conduct C-UAS operations, including detection and warning operations using systems requiring the authority of and relief from certain laws under the Act, within the geographic area and time period covered by the lead-agency designation.
                                </P>
                                <P>
                                    (e) 
                                    <E T="03">Overlapping SLTT operations.</E>
                                     When the Federal Bureau of Investigation and Department of Homeland Security receive advance notifications from two or more SLTT law enforcement or correctional agencies for C-UAS operations that overlap in geographic area and time, the Federal Bureau of Investigation and Department of Homeland Security will notify all affected SLTT law enforcement and correctional agencies of the overlap. The affected agencies must designate a lead C-UAS agency for the overlapping area and time period, or establish a joint operational coordination arrangement, before any agency commences mitigation operations in the overlapping area. The designation or arrangement must be documented and provided to the Federal Bureau of Investigation and Department of Homeland Security. If the agencies cannot reach agreement within 48 hours of the Federal Bureau of Investigation and Department of 
                                    <PRTPAGE P="41510"/>
                                    Homeland Security's notification, the Federal Bureau of Investigation and Department of Homeland Security may designate operational parameters for the overlapping area, including frequency deconfliction assignments and geographic boundaries for each agency's mitigation operations.
                                </P>
                                <P>
                                    (f) 
                                    <E T="03">Deconfliction direction.</E>
                                     If the deconfliction process identifies a conflict between a planned SLTT law enforcement or correctional agency C-UAS operation and an ongoing or planned Federal C-UAS, law enforcement, or national security operation that cannot be resolved through coordination, the Department of Justice, acting through the Federal Bureau of Investigation and in coordination with the Department of Homeland Security, may direct the SLTT law enforcement or correctional agency to modify the operational parameters of, or postpone, the planned operation until the conflict is resolved.
                                </P>
                                <P>
                                    (g) 
                                    <E T="03">Emergency exception preserved.</E>
                                     This section does not affect an SLTT agency's authority to respond to an imminent risk to human life under § 124.9(g), including at an event with a designated lead C-UAS agency; however, the agency must notify the lead C-UAS agency immediately upon taking emergency action and must coordinate with the lead agency as soon as practicable thereafter.
                                </P>
                                <P>(h) The requirements in paragraphs (a) through (g) of this section are established under the Attorney General's oversight authority pursuant to 6 U.S.C. 124n(d)(1) and the coordination obligations of 6 U.S.C. 124n(b)(4) and (d)(3); they do not transfer or diminish the SLTT agency's statutory authority and relief from certain laws under 6 U.S.C. 124n(a)(2).</P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.11</SECTNO>
                                <SUBJECT>Real-time air traffic control notification.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Notification required.</E>
                                     Any SLTT law enforcement or correctional agency, or its personnel, that activates a C-UAS system for mitigation purposes must, within five minutes of activation or as soon as operationally practicable, provide verbal or electronic notification to the notification point designated by the Federal Aviation Administration for real-time C-UAS coordination, using the procedures established under paragraph (b) of this section. Detection and warning operations do not require notification or coordination under this section.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Notification procedures.</E>
                                     An SLTT law enforcement or correctional agency must comply with the notification and reporting procedures jointly established by the Department of Homeland Security, the Department of Justice, and the Federal Aviation Administration for real-time communication to air traffic control of C-UAS mitigation actions using a radio frequency-emitting C-UAS system. The notification must identify the type of C-UAS action, the time of activation, and the location. The NCUTC will include training on these notification procedures in the mitigation training course.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Notification upon termination.</E>
                                     Upon termination of the mitigation action, the SLTT law enforcement or correctional agency must provide a follow-up notification to the designated Federal Aviation Administration notification point confirming the time of termination.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Non-RF mitigation.</E>
                                     Mitigation actions that do not involve radio frequency-emitting systems do require notification under this section unless the Department of Transportation or Federal Aviation Administration's applicable notification procedures established under this section provide otherwise. Such actions remain subject to the advance coordination and post-operation reporting requirements of §§ 124.9 and 124.13.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.12</SECTNO>
                                <SUBJECT>Detection and warning operations.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Scope.</E>
                                     This section governs detection and warning operations using systems whose operation requires the authority of and relief from certain laws under 6 U.S.C. 124n(a)(2). Detection and warning activity conducted using systems that do not require the authority of the Act or the relief it provides from certain laws is not subject to this part.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Conditions.</E>
                                     An SLTT law enforcement or correctional agency may conduct detection and warning operations under this section if:
                                </P>
                                <P>(1) All personnel conducting detection and warning operations hold a current Detection and Warning Certification;</P>
                                <P>(2) The agency deploys only systems within technology categories listed on the Authorized Technologies List and, where populated, specific systems listed on the Authorized Systems List;</P>
                                <P>(3) The agency has adopted an implementation policy under § 124.6(a) or a detection and warning policy under § 124.6(g), has completed the applicable portal attestation, and has authorized the operation by a C-UAS Operations Plan under § 124.8; and</P>
                                <P>(4) The agency complies with the privacy, data handling, and retention requirements of § 124.14.</P>
                                <P>
                                    (c) 
                                    <E T="03">Coordination.</E>
                                     No per-operation (that is, for each individual deployment or activation of a C-UAS system) advance notification, Federal Aviation Administration coordination, or Federal Communications Commission coordination is required for detection and warning operations that employ only systems that do not emit radio frequency energy and do not affect aviation safety. Such operations must be authorized by a C-UAS Operations Plan under § 124.8, which documents operational authority, data handling and retention, and legal review. For detection and warning operations involving RF-emitting systems, such as active warning broadcast systems, the advance coordination requirements of § 124.9 apply, and the operation must be authorized by a C-UAS Operations Plan under § 124.8.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Reporting.</E>
                                     The 48-hour reporting requirement of § 124.13 does not require per-event reporting of detection and warning operations. Each SLTT law enforcement or correctional agency conducting detection and warning operations under this section must report detection activity in the semiannual operational summary required by § 124.13, including the detection systems deployed by Authorized Technologies List category, the locations at which systems were deployed, the total number of detection events recorded, instances of retention of records of communication beyond 180 days, and any data-sharing arrangements. A physical seizure or confiscation under 6 U.S.C. 124n(b)(1)(E) that results from a detection and warning operation is a 6 U.S.C. 124n action, but it is documented through the agency's normal evidence-handling procedures and is not separately reported under this part. The recovery of a crashed or abandoned unmanned aircraft that does not involve the use of 6 U.S.C. 124n authority is not a 6 U.S.C. 124n confiscation and is not subject to the reporting requirements of this part.
                                </P>
                                <P>
                                    (e) 
                                    <E T="03">Prohibition on mitigation.</E>
                                     Personnel holding only a Detection and Warning Certification are not authorized to take any mitigation action or any other action that affects an unmanned aircraft in flight, regardless of the operator's ultimate objective. If a detection operation identifies a credible threat requiring mitigation, this rule requires that the agency respond through mitigation-certified personnel operating under §§ 124.8 and 124.9 or through coordination with Federal C-UAS assets. This prohibition is absolute and is not subject to the emergency exception of § 124.9(g), which is available only to an agency with mitigation-certified personnel and authorized mitigation capability.
                                </P>
                            </SECTION>
                            <SECTION>
                                <PRTPAGE P="41511"/>
                                <SECTNO>§ 124.13</SECTNO>
                                <SUBJECT>Post-operation reporting.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Report required.</E>
                                     Any SLTT law enforcement or correctional agency exercising authority under 6 U.S.C. 124n(a)(2) must submit a post-operation report as required by 6 U.S.C. 124n(d)(2)(C)(i) within 48 hours of whichever occurs first:
                                </P>
                                <P>(1) Taking any mitigation action described in 6 U.S.C. 124n(b)(1)(C), (D), or (F);</P>
                                <P>(2) Any confiscation of an unmanned aircraft or UAS under 6 U.S.C. 124n(b)(1)(E); or</P>
                                <P>(3) The conclusion of an operation where notification was provided.</P>
                                <P>
                                    (b) 
                                    <E T="03">Other confiscations.</E>
                                     A confiscation that does not occur pursuant to 6 U.S.C. 124n(b)(1)(E) may be documented through the agency's normal evidence-handling procedures and does not need to be separately reported under this part.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Content.</E>
                                     The post-operation report must contain:
                                </P>
                                <P>(1) Confirmation whether the planned operation did or did not occur as notified;</P>
                                <P>(2) The date, time, and geographic location of the reportable action;</P>
                                <P>(3) A brief description of the credible threat that a UAS or unmanned aircraft posed to the safety or security of people, a facility, or an asset; a venue or set of venues used for large-scale public gatherings or events; critical infrastructure; or a correctional facility necessitating the action;</P>
                                <P>(4) The type of capability employed, including the specific system or systems used by reference to the Authorized Systems List and Authorized Technologies List category, or where the Authorized Systems List had not yet been populated for a particular Authorized Technologies List category at the time of the action, the Authorized Technologies List category; and in all cases the make, model, hardware version, firmware revision, and software version of the system or systems as deployed;</P>
                                <P>(5) Any known operational effects, including the seizure, disabling, damage, or destruction of a UAS or unmanned aircraft; any reported effects on other aviation systems, spectrum users, or persons and property on the surface or in the air; any aviation accident; whether a temporary flight restriction was granted or denied; and any other harm, damage, or loss to a person or to private property;</P>
                                <P>(6) Any issues, anomalies, or deviations encountered during the operation; and</P>
                                <P>(7) Summary operational statistics, including the number of UAS detected, counted as confirmed detections attributable to a distinct unmanned aircraft and reported in good faith with reasonable deduplication; warnings issued; mitigation actions taken; UAS or unmanned aircraft seized or confiscated; and any criminal charges, citations, regulatory enforcement actions, or arrests resulting from the operation.</P>
                                <P>
                                    (d) 
                                    <E T="03">Submission mechanism.</E>
                                     Reports must be submitted through the designated Federal C-UAS coordination portal. Submission through the portal satisfies the notification requirement to both the Attorney General and the Secretary of Homeland Security, as the portal routes reports to the Federal Bureau of Investigation and Department of Homeland Security automatically.
                                </P>
                                <P>
                                    (e) 
                                    <E T="03">Immediate notification for unintended consequences.</E>
                                     If a detection, warning, or mitigation action results in unintended consequences, including interference with manned aviation or lawfully operating UAS, property damage, injury, or system malfunction affecting third parties, the SLTT law enforcement or correctional agency must immediately notify the Federal Bureau of Investigation and Department of Homeland Security by the most expedient means available, in addition to the 48-hour post-operation report. The Federal Bureau of Investigation will notify the Office of the Deputy Attorney General, the Department of Transportation, the Federal Aviation Administration, the Federal Communications Commission, and other affected agencies as appropriate.
                                </P>
                                <P>
                                    (f) 
                                    <E T="03">Consolidated reporting.</E>
                                     Where multiple reportable events occur within a 48 hour period, an SLTT law enforcement or correctional agency may submit a single consolidated post-operation report covering all actions taken during the period, due within 48 hours of the first reportable event, provided that each action is documented with the data elements required by paragraph (c) of this section and that any action resulting in unintended consequences is reported immediately under paragraph (e) of this section.
                                </P>
                                <P>
                                    (g) 
                                    <E T="03">Recurring venue reporting.</E>
                                     For recurring venue operations conducted under a standing operational window authorized by § 124.8(h), each discrete event within the authorization period must be reported separately.
                                </P>
                                <P>
                                    (h) 
                                    <E T="03">Semiannual operational summary.</E>
                                     Each SLTT law enforcement or correctional agency exercising authority under this part must submit a semiannual operational summary through the designated Federal C-UAS coordination portal, covering total operations conducted, mitigation actions taken, detection activity, instances of retention of records of communication beyond 180 days, instances in which control communications were disclosed outside the originating agency organized by the legal basis for their disclosure, compliance issues identified, and lessons learned. The summary must also report the requests the agency received for C-UAS protection from critical infrastructure or airport owners or operators that are not SLTT law enforcement or correctional agencies, the number of those requests to which it provided protection, and the number it was unable to support as well as the reasons it was unable to provide support.
                                </P>
                                <P>
                                    (i) 
                                    <E T="03">Reporting to support congressional and oversight requirements.</E>
                                     The Federal Bureau of Investigation will compile information from post-operation reports and semiannual summaries to support the biannual report required by 6 U.S.C. 124n(d)(2)(D) and the semiannual briefings required by 6 U.S.C. 124n(g), in coordination with the Secretary of Homeland Security and the Secretary of Transportation. The compilation will include:
                                </P>
                                <P>(1) The frequency, location, and circumstances of SLTT law enforcement and correctional agencies' mitigation deployments and the types of mitigation employed;</P>
                                <P>(2) A list of any aviation security or safety incidents, and any aviation accidents, that occurred due to SLTT law enforcement and correctional agencies' deployment of C-UAS technologies;</P>
                                <P>(3) Recommendations for improving SLTT law enforcement and correctional agencies' C-UAS training, oversight, compliance, and execution, and the compliance audits required by section 8606(b)(2) of the SAFER SKIES Act; and</P>
                                <P>(4) A determination whether SLTT law enforcement and correctional agencies are able to fully protect critical infrastructure from the UAS threat and, if not, recommendations on how to expand C-UAS authorities to critical infrastructure owners. This determination is informed by the protection-request data reported under paragraph (h) of this section.</P>
                                <P>(5) Instances in which records of communications were retained beyond 180 days, or in which control communications were disclosed outside the originating agency.</P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.14</SECTNO>
                                <SUBJECT>Privacy and civil liberties.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">General.</E>
                                     In exercising authority under 6 U.S.C. 124n(a)(2), an SLTT law enforcement or correctional agency and its personnel must comply with the 
                                    <PRTPAGE P="41512"/>
                                    requirements of 6 U.S.C. 124n(e), including the implementation of privacy protections with respect to the interception, acquisition, access, maintenance, use, and dissemination of communications, consistent with the First and Fourth Amendments to the Constitution of the United States and applicable provisions of Federal law. All operations under this part must comply with the requirements of the Fourth Amendment and the policies of the applicable SLTT law enforcement or correctional agency with respect to searches and seizures, and individual searches and seizures conducted during C-UAS operations remain subject to the Fourth Amendment reasonableness requirement.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">First Amendment.</E>
                                     No C-UAS authority under this part may be used solely to seize, monitor, deter, interfere with, or disrupt individuals exercising rights protected by the First Amendment to the Constitution of the United States. When C-UAS operations are conducted at events or locations where individuals are exercising First Amendment rights, personnel must take affirmative steps to minimize the collection, retention, and dissemination of information about those individuals, and must not use C-UAS-derived information to identify, track, or build records on individuals based on their exercise of protected rights.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Scope of interception.</E>
                                     Communications may be intercepted or acquired only to the extent necessary to support an action described in 6 U.S.C. 124n(b)(1).
                                </P>
                                <P>(1) Material captured that is not control communications is incidental capture. Agencies must configure systems to minimize incidental capture, and incidentally captured material determined not to be relevant to a C-UAS, law enforcement, or national security purpose must not be reviewed, retained, or disseminated and must be purged as soon as practicable.</P>
                                <P>(2) During the contemporaneous C-UAS operation, personnel may view incidentally captured material only to the extent necessary for C-UAS detection, tracking, identification, or mitigation purposes and may not use it for general surveillance or monitoring. If it becomes apparent that the captured video, audio, or other data stream is not control communications, the interception of such communications must be discontinued, and the interception of incidentally captured material must be documented in the post-operation report. When a system's configuration permits adjustment of the scope of interception, such as frequency range, geographic coverage, or signal type, operators must use the narrowest configuration consistent with operational effectiveness.</P>
                                <P>(3) For standing detection deployments exceeding 30 days, the agency must conduct a review, not less than quarterly, to confirm that the scope of interception remains proportionate to the operational need, that incidental collection of non-UAS communications is being minimized, and that data handling and purge procedures are being executed on schedule. The review may be conducted on a program-wide basis for facilities.</P>
                                <P>(4) Where identifying the threat requires processing the control signaling of all unmanned aircraft in range, the control communications of an unmanned aircraft determined not to pose a threat may not be retained or used beyond what is needed to make the threat determination and must be purged on the same schedule as other incidental material.</P>
                                <P>
                                    (d) 
                                    <E T="03">Records of communications and retention.</E>
                                     (1) Control communications captured, recorded, or maintained by SLTT C-UAS systems constitute records of communications to or from a UAS within the meaning of 6 U.S.C. 124n(e)(3) and must be maintained only for as long as necessary, and in no event for more than 180 days, unless the Agency Approving Official or the agency's chief legal officer determines that maintenance of such records is necessary to investigate or prosecute a violation of law, to directly support an ongoing security operation, for the purpose of any litigation, or is required under Federal, State, local, Tribal, or territorial law, consistent with 6 U.S.C. 124n(e)(3).
                                </P>
                                <P>(2) Data retained under the ongoing security operation exception must be reviewed at 90-day intervals and purged when the operation concludes, unless another exception applies.</P>
                                <P>(3) When an agency determines that records of communications will be retained beyond 180 days under any exception, the agency must notify the Federal Bureau of Investigation through the portal within 30 days of the determination.</P>
                                <P>(4) Pattern data, once extracted and recorded independently, is not a record of communications and is not subject to the 180-day limit. Data generated by systems whose operation does not implicate the electronic surveillance laws referenced in the notwithstanding clause of 6 U.S.C. 124n(a)(2) is likewise not subject to the 180-day limit.</P>
                                <P>(5) For data retained under the investigation or prosecution exception, the existence of an open investigative or prosecutorial case file documenting the data as evidence satisfies the required determination. For data retained under any other exception, the Agency Approving Official or the agency's chief legal officer must document the specific basis for retention. If an agency has neither an Agency Approving Official nor a chief legal officer, an official holding a rank not below a Senior Executive or Senior Official, or its equivalent, must document the specific basis for retention.</P>
                                <P>(6) A standing operational window authorized under § 124.8(h) does not itself constitute an ongoing security operation for purposes of the retention exception; that exception applies only when a specific, identified threat or other intelligence justifies continued retention of specific records to support a discrete protective objective, and the 90-day review must assess whether the specific security basis for retention continues to exist.</P>
                                <P>(7) The exception for retention required under Federal, State, local, Tribal, or territorial law applies when a specific provision of law affirmatively requires retention of the particular type of data at issue, not when a general records retention schedule incidentally encompasses C-UAS data.</P>
                                <P>
                                    (e) 
                                    <E T="03">Dissemination.</E>
                                     (1) Control communications acquired under this part may be disclosed outside the disseminating agency only as authorized by 6 U.S.C. 124n(e)(4): when necessary to investigate or prosecute a violation of law; to support the Department of Defense, a Federal law enforcement agency, or the enforcement activities of a regulatory agency of the Federal Government in connection with a criminal or civil investigation of, or any regulatory, statutory, or other enforcement action relating to an action described in 6 U.S.C. 124n(b)(1); or as otherwise required by law.
                                </P>
                                <P>(2) This part does not prohibit the use, as evidence in a subsequent proceeding, of information lawfully obtained incidental to an SLTT law enforcement or correctional agency C-UAS operation, consistent with applicable law.</P>
                                <P>(3) At the time of any dissemination of control communications, the disseminating agency must document, in the audit trail required by paragraph (g) of this section, the 6 U.S.C. 124n(e)(4) basis for the dissemination, the category of recipient, whether the handling caveat required by paragraph (f) of this section was conveyed, and whether the dissemination included control communications.</P>
                                <P>
                                    (4) A real-time detection feed is governed by the substantive character of the data it transmits. A feed that 
                                    <PRTPAGE P="41513"/>
                                    transmits control communications acquired under this part is subject to the requirements of this section applicable to such data and the limitations under 6 U.S.C. 124n(e)(1), (2), and (4). A feed that transmits only data described in paragraph (e)(6) of this section is not subject to those limitations.
                                </P>
                                <P>(5) Pattern data that contains no control communications may be disseminated consistent with the agency's standard data handling and information sharing policies and applicable law. Before disseminating pattern data beyond the agency, the disseminating agency must verify anonymization in accordance with its implementation policy and screen the product for operationally sensitive information that would reveal specific coverage patterns, capabilities, gaps, or methods. Public release of pattern data products requires approval at the level designated by the agency's implementation policy.</P>
                                <P>(6) Data not acquired using the authorities or reliefs provided by 6 U.S.C. 124n, including data generated by systems whose operation does not implicate the electronic surveillance laws referenced in the notwithstanding clause of 6 U.S.C. 124n(a)(2), is not subject to the disclosure limitations of paragraph (e)(1) of this section and may be shared consistent with the agency's standard data handling and information sharing policies and applicable law. Sharing for situational awareness with recipients that are not law enforcement or correctional agencies, including critical infrastructure owners or operators and the public, is limited to data described in this paragraph, unless the disclosure of control communications is authorized under paragraph (e)(1) of this section.</P>
                                <P>
                                    (f) 
                                    <E T="03">Protective purpose limitation.</E>
                                     Because the authority of 6 U.S.C. 124n(a)(2) is limited to mitigation of a credible threat, an SLTT law enforcement or correctional agency may disseminate control communications acquired pursuant to the agency's authorities and statutory reliefs under 6 U.S.C. 124n(a)(2) only for law enforcement action arising from the UAS activity that prompted the C-UAS operation, or for aviation safety. An SLTT law enforcement or correctional agency may not disseminate such control communications for use in an investigation or enforcement action unrelated to UAS activity unless the communications are independently obtainable through lawful means not dependent on the authorities and statutory reliefs under 6 U.S.C. 124n(a)(2). At the time of dissemination, the disseminating agency must communicate the protective purpose for which the control communications are being shared.
                                </P>
                                <P>
                                    (g) 
                                    <E T="03">Audit trail.</E>
                                     Each SLTT law enforcement or correctional agency exercising authority under this part must maintain an audit trail sufficient to document each instance in which C-UAS authority was exercised, the basis for the action, the disposition of any data acquired, and any dissemination of data under this part. The audit trail must be searchable and accessible to compliance auditors, protected against unauthorized modification or deletion, and retained for a minimum of 6 years. The agency's implementation policy must specify the format and system of records for the audit trail.
                                </P>
                                <P>
                                    (h) 
                                    <E T="03">State and local retention conflicts.</E>
                                     When an SLTT law enforcement or correctional agency determines that a State, local, Tribal, or territorial records retention requirement applicable to law enforcement or correctional agency records encompasses C-UAS communications data and the agency cannot comply with both the 180-day retention limit and that retention requirement, the agency must retain the data for the period required by the applicable law and must apply the handling restrictions of this part, including the prohibition on use for unrelated law enforcement purposes and the dissemination restrictions of this section, for the full duration of retention.
                                </P>
                                <P>
                                    (i) 
                                    <E T="03">Third-party acquisition.</E>
                                     An SLTT law enforcement or correctional agency may not request, purchase, subscribe to, or operationally rely on intercepted UAS control communications acquired by any actor lacking lawful authority and relief from certain otherwise applicable laws for the underlying interception, regardless of whether the agency directed or facilitated the original interception. An agency acquiring UAS intelligence from a third-party source must document the source's lawful authority and relief from otherwise applicable laws for any intercepted content and must apply the retention and dissemination requirements of this section to data so acquired. The agency's implementation policy must specify procedures for evaluating third-party source authority and relief from certain otherwise applicable laws, which must include review and concurrence by appropriate State, local, territorial, or Tribal legal counsel.
                                </P>
                                <P>
                                    (j) 
                                    <E T="03">Vendor data sharing.</E>
                                     An SLTT law enforcement or correctional agency may provide operational raw sensor data to system vendors for purposes of system diagnostics, troubleshooting, and performance validation, provided that any communications content is removed before disclosure and the data is used solely for the specific purpose identified. The agency's implementation policy must establish the conditions for vendor data sharing consistent with this paragraph and applicable privacy protections.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.15 </SECTNO>
                                <SUBJECT>Protection of sensitive operational information.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Sensitive system information.</E>
                                     Information that links the specific capabilities, vulnerabilities, operating parameters, or countermeasure effectiveness of C-UAS systems to planned or completed operations, including deployment locations, operating radio frequencies, tactical employment methods, and threat-specific mitigation approaches, must be treated as law enforcement sensitive, protected from public disclosure to the extent permitted by applicable law, and, where the information reveals a capability gap of national security concern, evaluated for classification. Other operational coordination information associated with a planned or completed operation, such as the existence, general timing, or general coverage area of a deployment, must be handled as Controlled Unclassified Information and may be shared with covered Federal and SLTT law enforcement and correctional partners, including a State-designated aviation point of contact, for a lawful government purpose. General technical specifications and evaluation data not associated with a specific planned or completed operation are not subject to these handling requirements. All information described in this paragraph remains subject to any applicable classification, export control, or proprietary restriction.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Protection from disclosure.</E>
                                     An SLTT law enforcement or correctional agency must take the steps available under applicable State, local, Tribal, or territorial law to protect operationally sensitive information from disclosure through public records requests or civil discovery, and should coordinate with the prosecuting authority in criminal prosecutions arising from C-UAS operations to limit testimony and pleadings to the information necessary to establish the elements of the offense. Nothing in this section requires an agency to take any action inconsistent with applicable State, local, Tribal, or territorial public records law.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Markings.</E>
                                     Advance notifications, C-UAS Operations Plans, post-operation reports, and compliance audit 
                                    <PRTPAGE P="41514"/>
                                    records must be marked with appropriate sensitivity designations.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Permitted disclosures.</E>
                                     This section does not prohibit disclosure of sensitive system information to authorized Federal officials, to other participating SLTT agencies in the course of operational coordination, or to the public to the extent required by statute or court order.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.16 </SECTNO>
                                <SUBJECT>Compliance and enforcement.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Compliance audits.</E>
                                     The Attorney General, in coordination with the Secretary of Homeland Security and the Administrator of the Federal Aviation Administration, will periodically conduct compliance audits of SLTT law enforcement and correctional agencies exercising authority under 6 U.S.C. 124n(a)(2), as required by 6 U.S.C. 124n(d)(2)(B) and section 8606(b)(2) of the SAFER SKIES Act, to oversee compliance with this part and the privacy protections of 6 U.S.C. 124n(e) as well as to prevent misuse of C-UAS authority. The audit program will include review of post-operation reports, advance notification records, and agency implementation policies. The FAA will participate with respect to the aviation safety, airspace safety coordination, and deconfliction aspects of the compliance audits conducted under this section.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Civil fines and penalties.</E>
                                     An SLTT law enforcement or correctional agency, or its personnel authorized to take mitigation actions under 6 U.S.C. 124n(a)(2), that knowingly engages in such actions without Federal coordination as required by 6 U.S.C. 124n and the SAFER SKIES Act, including the advance coordination required by § 124.9, the real-time air traffic control notification required by § 124.11, and the post-action notification to the Attorney General and the Secretary of Homeland Security required by 6 U.S.C. 124n(d)(2)(C) and implemented by § 124.13(a), may be subject to a civil fine of up to $100,000 per violation, or suspension of C-UAS authority pending review by the Attorney General or the Secretary of Homeland Security, as provided in section 8605(f) of the SAFER SKIES Act. Civil penalties will be assessed in accordance with graduated penalty levels proportionate to the severity of the violation and the factors set forth in this part, including the agency's compliance history, the availability and quality of compliance assistance from Federal partners, whether the violation resulted in actual harm, and whether the agency took prompt corrective action. A civil penalty will not be assessed for a first violation of a procedural reporting or notification requirement when the agency demonstrates a good-faith effort to comply and voluntarily self-reports the deficiency. Violations of requirements of this part other than the Federal coordination requirements described in this paragraph do not give rise to civil penalties under section 8605(f) of the SAFER SKIES Act; they are addressed through the compliance audit program of this section, certification and accreditation suspension under § 124.5, and any other remedy available under law.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Civil enforcement.</E>
                                     The Attorney General is authorized to bring a civil action in a United States district court to collect fines and enforce civil penalties imposed under this section against any agency or individual, as provided in section 8605(g) of the SAFER SKIES Act.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Relationship to certification or accreditation suspension.</E>
                                     In addition to civil penalties, the Attorney General or designee may suspend a Mitigation Certification, Detection and Warning Certification, or accreditation under § 124.5(i) for violations of this part. Certification or accreditation suspension may be imposed independently of or in conjunction with other actions described in this section.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.17 </SECTNO>
                                <SUBJECT>Confiscation and forfeiture.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Confiscation authority.</E>
                                     (1) An SLTT law enforcement or correctional agency and its personnel may seize or otherwise confiscate a UAS or unmanned aircraft as described in 6 U.S.C. 124n(b)(1)(E). This authority is contingent on a credible threat and applies to the physical taking of possession of an unmanned aircraft that is no longer active in flight or any other UAS component, such as a ground control station.
                                </P>
                                <P>(2) This authority does not require Mitigation Certification, the use of systems on the Authorized Technologies List or Authorized Systems List, or advance coordination under § 124.9. However, personnel exercising confiscation authority under 6 U.S.C. 124n(b)(1)(E) must hold a current Detection and Warning Certification issued by the NCUTC. An officer who seizes an unmanned aircraft or any other UAS component under traditional law enforcement authority, including an abandoned or crashed unmanned aircraft, does not require Detection and Warning Certification.</P>
                                <P>(3) Any action that employs C-UAS technology to disrupt or seize control of, damage, disable, or destroy the unmanned aircraft or UAS is an action under 6 U.S.C. 124n(b)(1)(C), (D), or (F) and requires Mitigation Certification.</P>
                                <P>(4) Personnel exercising confiscation authority should follow standard law enforcement evidence handling procedures, including maintaining chain of custody, preserving digital evidence stored on the aircraft or its flight controller, and observing applicable hazardous materials precautions.</P>
                                <P>(5) This part does not affect the authority of any law enforcement or correctional officer to take physical custody of an unmanned aircraft or UAS under traditional law enforcement authority independent of 6 U.S.C. 124n. Traditional law enforcement authority refers to the seizure authorities generally available to law enforcement under applicable Federal, State, local, Tribal, or territorial law, including seizure incident to arrest, seizure of evidence or contraband pursuant to a warrant or a recognized exception to the warrant requirement, and seizure of abandoned property. Once an unmanned aircraft or UAS is on the ground and confiscated, subsequent law enforcement actions, including threat assessment, render safe procedures, evidence collection, and search warrant execution, are governed by traditional legal authorities, including Fourth Amendment requirements and applicable exigency or emergency doctrines, rather than by 6 U.S.C. 124n.</P>
                                <P>(6) When a C-UAS operation involves a known or suspected unmanned aircraft being used as a delivery mechanism for a hazardous device, the response to the hazardous device must be conducted by a public safety bomb squad accredited through the Hazardous Devices School, consistent with the National Guidelines for Bomb Technicians or any successor publication.</P>
                                <P>(7) The physical act of interception of a third-party unmanned aircraft while it is in flight, such as catching or netting an aircraft by hand or using a non-electronic physical device to capture it in the air, implicates 6 U.S.C. 124n(b)(1)(D), (E), or (F). Personnel conducting such actions must therefore hold a Mitigation Certification. This does not apply to the erection of physical barriers that a drone operator has an obligation to avoid, such as netting affixed to a physical structure.</P>
                                <P>
                                    (b) 
                                    <E T="03">Forfeiture.</E>
                                     Any UAS or unmanned aircraft seized by an SLTT law enforcement or correctional agency pursuant to 6 U.S.C. 124n(a)(2) is subject to forfeiture under the laws of the seizing agency's jurisdiction, as provided in 6 U.S.C. 124n(c)(2).
                                </P>
                            </SECTION>
                            <SECTION>
                                <PRTPAGE P="41515"/>
                                <SECTNO>§ 124.18 </SECTNO>
                                <SUBJECT>Activities for evaluation, testing, training, and pre-operational validation.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Scope and legal basis.</E>
                                     An SLTT law enforcement or correctional agency that holds current accreditation under this part may conduct operational acceptance testing of acquired systems and systems under procurement consideration, on-the-job proficiency training, and interoperability training exercises to maintain C-UAS operational readiness. Testing and training do not and must not involve the mitigation of a credible threat and are not conducted under the authority of 6 U.S.C. 124n(a)(2). The operation of RF-emitting systems during testing and training is conducted under applicable Federal Communications Commission authorization and Federal Aviation Administration coordination requirements, and only against controlled test targets owned or operated by, or operated with the consent of, the SLTT law enforcement or correctional agency. An SLTT law enforcement or correctional agency acting pursuant to this section may utilize only authorized technologies under § 124.7. The SLTT law enforcement or correctional agency is responsible for verifying that all necessary Federal Aviation Administration authorizations or regulatory relief for operation of any unmanned aircraft or UAS, including unmanned aircraft or UAS forming part of a C-UAS system, have been obtained prior to any testing, training, or exercises. Compliance with this section is a condition of maintaining certification and accreditation under this part.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Personnel.</E>
                                     Only personnel holding a current Mitigation Certification may operate mitigation systems during evaluation testing, training, and exercises. Testing, training, and exercises may not be used to train or evaluate uncertified personnel on the operation of mitigation systems. Contractors and vendor representatives may provide technical support and instruction on system-specific procedures but may not independently operate mitigation systems against test targets.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Evaluation testing and training activities plan.</E>
                                     Before conducting testing, training, or exercises involving RF-emitting C-UAS mitigation systems, the agency must prepare a written activities plan specifying the date, time, and location; the purpose; the systems and equipment to be used; the test, training, or exercise targets; the assigned operators; safety controls; privacy measures; the types of data to be collected and their planned disposition; documentation of Federal Aviation Administration and Federal Communications Commission spectrum coordination for the C-UAS activities, and documentation of any necessary Federal Aviation Administration authorizations or regulatory relief for the operator of the target unmanned aircraft or UAS and for the operation any unmanned aircraft or UAS that form part of the C-UAS system. The activities plan must be approved by the Agency Approving Official or designee and reviewed by the agency's legal counsel.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Coordination.</E>
                                     Testing, training, and exercises, involving RF-emitting systems, or systems that may affect aviation safety, civilian aviation and aerospace operations, aircraft airworthiness, or the use of the airspace, require advance coordination with the Federal Aviation Administration and, for spectrum authorization, with the Federal Communications Commission.
                                </P>
                                <P>
                                    (e) 
                                    <E T="03">Privacy within evaluation testing and training.</E>
                                     The agency must favor testing, training, and exercise locations and activities that minimize exposure to non-participating third parties. The agency must not intentionally target, monitor, or collect the communications of non-participating third parties. Communications incidentally collected from non-participating third parties must be purged at the conclusion of the testing, training, or exercise activity, or as soon as practicable thereafter.
                                </P>
                                <P>
                                    (f) 
                                    <E T="03">Mitigation restriction.</E>
                                     During testing, training, and exercises, the agency may not intentionally mitigate any UAS or unmanned aircraft that is not a controlled test target, unless necessary to protect against an imminent risk to human life or as part of an approved C-UAS Operations Plan. An action taken to protect against an imminent risk to human life must comply with the emergency exception set forth in § 124.9(g).
                                </P>
                                <P>
                                    (g) 
                                    <E T="03">Pre-operational validation.</E>
                                     Before commencing mitigation operations at an event or facility, an agency may conduct pre-operational validation or equipment functional checks within the operational window and airspace restrictions already coordinated through the advance notification process under § 124.9. The C-UAS Operations Plan must document the pre-operational validation plan and required notifications. No separate authorization from the Department of Homeland Security or the Department of Justice beyond the advance notification is required.
                                </P>
                                <P>
                                    (h) 
                                    <E T="03">Participation in Federal RTTE.</E>
                                     Personnel holding active Mitigation Certification may participate in research, testing, training, and evaluation (RTTE) events conducted by Federal components under 6 U.S.C. 124n(b)(3). Personnel may engage with systems in mitigation technology categories beyond those for which they hold an active Mitigation Certification or that are not on the ATL or ASL as part of the event. Participants act under the Federal component's authority and supervision.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.19 </SECTNO>
                                <SUBJECT>Task force arrangements and Federal support.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Task force and deputization arrangements preserved.</E>
                                     Task force and deputization arrangements under 6 U.S.C. 124n(a)(1) are not affected by this part. An SLTT law enforcement or correctional agency participating in such an arrangement may continue that participation indefinitely, so long as the deputizing Federal agency continues to have C-UAS authority and relief from certain laws under 6 U.S.C. 124n(a)(1). Nothing in this part requires an agency to seek accreditation under this part, conditions any task force or deputization arrangement on accreditation, or terminates or limits any such arrangement.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Concurrent authority.</E>
                                     The availability of independent SLTT law enforcement and correctional agency authority under 6 U.S.C. 124n(a)(2) does not preclude continued participation in C-UAS task forces or deputization arrangements under 6 U.S.C. 124n(a)(1). An SLTT law enforcement or correctional agency and its officers may exercise independent authority and participate in Federal task force operations concurrently or at different times as operational circumstances warrant. Task force operations are governed by the policies applicable to the sponsoring Federal component.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Federal support.</E>
                                     An SLTT law enforcement or correctional agency may request C-UAS support from an authorized Department of Justice or Department of Homeland Security component. Such support, when provided, constitutes a Federal operation under 6 U.S.C. 124n(a)(1) and is governed by the policies applicable to the supporting component, and the requesting agency's personnel participating in the operation do so under the Federal component's authority and supervision, consistent with applicable task force or deputization arrangements. No formal gubernatorial request is required under this part. Support from the Department of Defense, when available, is governed by the Department of Defense's own authorities, including 10 U.S.C. 130i and 2564, and applicable Department of Defense policies, not by this part.
                                </P>
                            </SECTION>
                            <SECTION>
                                <PRTPAGE P="41516"/>
                                <SECTNO>§ 124.20 </SECTNO>
                                <SUBJECT>Construction.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">No private right.</E>
                                     This part is not intended to, does not, and may not be relied upon to create any right or benefit, substantive or procedural, enforceable at law or in equity by any party against the United States, its departments, agencies, or entities, its officers, employees, or agents, or any other person.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Manned aircraft.</E>
                                     Nothing in this part authorizes the use of C-UAS authority against any aircraft or aircraft system operated with a human pilot, crew, or passengers onboard.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Mass gatherings.</E>
                                     Consistent with 6 U.S.C. 124n(h)(5), nothing in this part provides a new basis of liability for any State, local, territorial, or Tribal law enforcement officer who participates in the protection of a mass gathering identified by the Secretary of Homeland Security or the Attorney General under 6 U.S.C. 124n(l)(3)(C)(iii)(II), acts within the scope of the officer's authority, and does not exercise the authority granted to the Secretary of Homeland Security and the Attorney General by 6 U.S.C. 124n.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Statutory scope.</E>
                                     Nothing in this part alters the scope of the authority of, or the statutory reliefs under 6 U.S.C. 124n(a)(2). A determination that an action does not comply with this part may give rise to administrative, civil, or other consequences provided by law, but does not by itself determine whether the action falls outside the scope of the statutory authorization in, or the relief from criminal liability available under, 6 U.S.C. 124n. Such a determination will be made by the Attorney General, in coordination with the Secretary of Homeland Security and other appropriate officials.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.21 </SECTNO>
                                <SUBJECT>Termination.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Termination.</E>
                                     Absent additional statutory authority, the authority of SLTT law enforcement and correctional agencies and their personnel under 6 U.S.C. 124n(a)(2) will terminate on December 31, 2031, as provided in 6 U.S.C. 124n(j)(2).
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Savings.</E>
                                     Termination under paragraph (a) of this section does not affect any obligation, proceeding, or liability that arose before the termination date. Recordkeeping, retention, audit, reporting, and enforcement obligations with respect to operations conducted before the termination date, and any administrative or civil proceeding arising from those operations, survive the termination of authority under this part and remain in effect until satisfied or otherwise resolved.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 124.22 </SECTNO>
                                <SUBJECT>Severability.</SUBJECT>
                                <P>If any provision of this part, or the application of any provision to any person, entity, or circumstance, is held to be invalid or unenforceable by a court of competent jurisdiction, the remainder of this part, and the application of its provisions to any other persons, entities, or circumstances, shall not be affected and shall remain in full force and effect.</P>
                            </SECTION>
                        </PART>
                    </REGTEXT>
                    <SIG>
                        <NAME>Markwayne Mullin,</NAME>
                        <TITLE>Secretary of Homeland Security,</TITLE>
                        <NAME>Daniel E. Burrows,</NAME>
                        <TITLE>Assistant Attorney General, Office of Legal Policy, Department of Justice.</TITLE>
                    </SIG>
                </SUPLINF>
                <FRDOC>[FR Doc. 2026-13609 Filed 7-1-26; 4:15 pm]</FRDOC>
                <BILCOD>BILLING CODE 9110-9F-P; 4410-02-P</BILCOD>
            </RULE>
        </RULES>
    </NEWPART>
    <VOL>91</VOL>
    <NO>127</NO>
    <DATE>Monday, July 6, 2026</DATE>
    <UNITNAME>Presidential Documents</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="41517"/>
            <PARTNO>Part VII</PARTNO>
            <PRES>The President</PRES>
            <DETNO>Presidential Determination No. 2026-17 of June 26, 2026—Presidential Determination on Assistance to Venezuela Consistent With the Trafficking Victims Protection Act of 2000</DETNO>
        </PTITLE>
        <PRESDOCS>
            <PRESDOCU>
                <DETERM>
                    <TITLE3>Title 3— </TITLE3>
                    <PRES>
                        The President
                        <PRTPAGE P="41519"/>
                    </PRES>
                    <DETNO>Presidential Determination No. 2026-17 of June 26, 2026</DETNO>
                    <HD SOURCE="HED">Presidential Determination on Assistance to Venezuela Consistent With the Trafficking Victims Protection Act of 2000</HD>
                    <HD SOURCE="HED">Memorandum for the Secretary of State</HD>
                    <FP>Following Presidential Determination 2026-02 of November 21, 2025, and consistent with section 110(d)(4) of the Trafficking Victims Protection Act of 2000 (22 U.S.C. 7107(d)(4)) (the “Act”), I hereby determine that providing the assistance described in section 110(d)(1)(B) of the Act to Venezuela would promote the purposes of the Act or is otherwise in the national interest of the United States.</FP>
                    <FP>
                        You are authorized and directed to submit this determination and the Memorandum of Justification, on which I have relied, to the Congress, and to publish this determination in the 
                        <E T="03">Federal Register</E>
                        .
                    </FP>
                    <GPH SPAN="1" DEEP="80" HTYPE="RIGHT">
                        <GID>Trump.EPS</GID>
                    </GPH>
                    <PSIG> </PSIG>
                    <PLACE>THE WHITE HOUSE,</PLACE>
                    <DATE>Washington, June 26, 2026</DATE>
                    <FRDOC>[FR Doc. 2026-13631 </FRDOC>
                    <FILED>Filed 7-1-26; 4:15 pm]</FILED>
                    <BILCOD>Billing code 4710-10-P</BILCOD>
                </DETERM>
            </PRESDOCU>
        </PRESDOCS>
    </NEWPART>
</FEDREG>
