<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="fedregister.xsl"?>
<FEDREG xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="FRMergedXML.xsd">
    <VOL>89</VOL>
    <NO>8</NO>
    <DATE>Thursday, January 11, 2024</DATE>
    <UNITNAME>Contents</UNITNAME>
    <CNTNTS>
        <AGCY>
            <EAR>
                Agency
                <PRTPAGE P="iii"/>
            </EAR>
            <HD>Agency for International Development</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Workforce Commuter Survey, </SJDOC>
                    <PGS>1875</PGS>
                    <FRDOCBP>2024-00475</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Agriculture</EAR>
            <HD>Agriculture Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>1875-1876</PGS>
                    <FRDOCBP>2024-00444</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Consumer Financial Protection</EAR>
            <HD>Bureau of Consumer Financial Protection</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Civil Monetary Penalty Inflation Adjustment, </DOC>
                    <PGS>1787-1789</PGS>
                    <FRDOCBP>2024-00456</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Centers Medicare</EAR>
            <HD>Centers for Medicare &amp; Medicaid Services</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>1920</PGS>
                    <FRDOCBP>2024-00474</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Children</EAR>
            <HD>Children and Families Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Survey on where Parents Look for and Find Information and How They Use Information when Selecting Child Care, </SJDOC>
                    <PGS>1920-1921</PGS>
                    <FRDOCBP>2024-00395</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Civil Rights</EAR>
            <HD>Civil Rights Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Hearings, Meetings, Proceedings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Georgia Advisory Committee, </SJDOC>
                    <PGS>1876</PGS>
                    <FRDOCBP>2024-00424</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Commerce</EAR>
            <HD>Commerce Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Industry and Security Bureau</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>International Trade Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Oceanic and Atmospheric Administration</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Defense Department</EAR>
            <HD>Defense Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Privacy Act; Matching Program, </DOC>
                    <PGS>1910-1911</PGS>
                    <FRDOCBP>2024-00589</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Education Department</EAR>
            <HD>Education Department</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>General Administrative Regulations and Related Regulatory Provisions, </DOC>
                    <PGS>1982-2031</PGS>
                    <FRDOCBP>2023-27682</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Office of State Support Progress Check Quarterly Protocol, </SJDOC>
                    <PGS>1911-1912</PGS>
                    <FRDOCBP>2024-00438</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Employment and Training</EAR>
            <HD>Employment and Training Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Federal Civil Penalties Inflation Adjustment Act Annual Adjustments for 2024, </DOC>
                    <PGS>1810-1822</PGS>
                    <FRDOCBP>2024-00253</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>
        </AGCY>
        <AGCY>
            <EAR>Environmental Protection</EAR>
            <HD>Environmental Protection Agency</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Significant New Uses:</SJ>
                <SJDENT>
                    <SJDOC>Per- and Poly-fluoroalkyl Chemical Substances Designated as Inactive on the Toxic Substances Control Act Inventory, </SJDOC>
                    <PGS>1822-1831</PGS>
                    <FRDOCBP>2024-00412</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Hearings, Meetings, Proceedings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>National Drinking Water Advisory Council, </SJDOC>
                    <PGS>1915</PGS>
                    <FRDOCBP>2024-00413</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Aviation</EAR>
            <HD>Federal Aviation Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Airspace Designations and Reporting Points:</SJ>
                <SJDENT>
                    <SJDOC>Bedford, PA, </SJDOC>
                    <PGS>1789-1790</PGS>
                    <FRDOCBP>2024-00193</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Hutchinson, MN, </SJDOC>
                    <PGS>1792-1793</PGS>
                    <FRDOCBP>2024-00195</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Jackson, OH, </SJDOC>
                    <PGS>1800-1801</PGS>
                    <FRDOCBP>2024-00197</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Minden-Tahoe Airport, Minden, NV; Correction, </SJDOC>
                    <PGS>1793</PGS>
                    <FRDOCBP>2024-00352</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Natchez, MS, </SJDOC>
                    <PGS>1799-1800</PGS>
                    <FRDOCBP>2024-00399</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Ozark, AL and Columbus, GA; Correction, </SJDOC>
                    <PGS>1800</PGS>
                    <FRDOCBP>2023-28314</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Vicinity of Acequia, ID, </SJDOC>
                    <PGS>1790-1792</PGS>
                    <FRDOCBP>2024-00070</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Vicinity of Beaumont, TX, </SJDOC>
                    <PGS>1795-1797</PGS>
                    <FRDOCBP>2024-00150</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Vicinity of Bowling Green, MO, </SJDOC>
                    <PGS>1797-1798</PGS>
                    <FRDOCBP>2024-00072</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Vicinity of Burley, ID, </SJDOC>
                    <PGS>1801-1803</PGS>
                    <FRDOCBP>2024-00071</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Vicinity of Paynesville, CA, </SJDOC>
                    <PGS>1793-1795</PGS>
                    <FRDOCBP>2024-00069</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Standard Instrument Approach Procedures, and Takeoff Minimums and Obstacle Departure Procedures, </DOC>
                    <PGS>1803-1806</PGS>
                    <FRDOCBP>2024-00098</FRDOCBP>
                      
                    <FRDOCBP>2024-00099</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Airspace Designations and Reporting Points:</SJ>
                <SJDENT>
                    <SJDOC>Northcentral United States, </SJDOC>
                    <PGS>1851-1854</PGS>
                    <FRDOCBP>2024-00152</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Southern Utah, </SJDOC>
                    <PGS>1854-1856</PGS>
                    <FRDOCBP>2024-00085</FRDOCBP>
                </SJDENT>
                <SJ>Airworthiness Directives:</SJ>
                <SJDENT>
                    <SJDOC>CFM International, S.A. Engines, </SJDOC>
                    <PGS>1847-1849</PGS>
                    <FRDOCBP>2024-00377</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>MHI RJ Aviation ULC (Type Certificate Previously Held by Bombardier, Inc.) Airplanes, </SJDOC>
                    <PGS>1849-1851</PGS>
                    <FRDOCBP>2024-00343</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Communications</EAR>
            <HD>Federal Communications Commission</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Connect America Fund, </DOC>
                    <PGS>1833-1834</PGS>
                    <FRDOCBP>2024-00417</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Promoting Telehealth in Rural America, </DOC>
                    <PGS>1834-1846</PGS>
                    <FRDOCBP>2024-00415</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Accelerating Wireline Broadband Deployment by Removing Barriers to Infrastructure Investment, </DOC>
                    <PGS>1859-1874</PGS>
                    <FRDOCBP>2023-28763</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>1915-1917</PGS>
                    <FRDOCBP>2024-00376</FRDOCBP>
                      
                    <FRDOCBP>2024-00379</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Deposit</EAR>
            <HD>Federal Deposit Insurance Corporation</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Civil Monetary Penalty Inflation Adjustment, </DOC>
                    <PGS>1917-1919</PGS>
                    <FRDOCBP>2024-00409</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Emergency</EAR>
            <HD>Federal Emergency Management Agency</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Flood Hazard Determinations, </DOC>
                    <PGS>1931-1936</PGS>
                    <FRDOCBP>2024-00477</FRDOCBP>
                      
                    <FRDOCBP>2024-00478</FRDOCBP>
                      
                    <FRDOCBP>2024-00479</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Energy</EAR>
            <HD>Federal Energy Regulatory Commission</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Civil Monetary Penalty Inflation Adjustment, </DOC>
                    <PGS>1806-1808</PGS>
                    <FRDOCBP>2024-00425</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Authorization for Continued Project Operation:</SJ>
                <SJDENT>
                    <SJDOC>Georgia Power Co., </SJDOC>
                    <PGS>1912-1913</PGS>
                    <FRDOCBP>2024-00420</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Combined Filings, </DOC>
                    <PGS>1913-1914</PGS>
                    <FRDOCBP>2024-00418</FRDOCBP>
                      
                    <FRDOCBP>2024-00419</FRDOCBP>
                    <PRTPAGE P="iv"/>
                </DOCENT>
                <SJ>Complaint:</SJ>
                <SJDENT>
                    <SJDOC>Husky US Marketing LLC and Phillips 66 Co. v. TransCanada Keystone Pipeline, LP, </SJDOC>
                    <PGS>1912</PGS>
                    <FRDOCBP>2024-00426</FRDOCBP>
                </SJDENT>
                <SJ>Environmental Assessments; Availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Ketchikan Public Utilities, </SJDOC>
                    <PGS>1914-1915</PGS>
                    <FRDOCBP>2024-00421</FRDOCBP>
                </SJDENT>
                <SJ>Environmental Review:</SJ>
                <SJDENT>
                    <SJDOC>Port Arthur LNG, LLC, PALNG Common Facilities Co., LLC, Port Arthur Liquified Natural Gas Amendment, </SJDOC>
                    <PGS>1913-1914</PGS>
                    <FRDOCBP>2024-00427</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Reserve</EAR>
            <HD>Federal Reserve System</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Formations of, Acquisitions by, and Mergers of Bank Holding Companies, </DOC>
                    <PGS>1919-1920</PGS>
                    <FRDOCBP>2024-00480</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Trade</EAR>
            <HD>Federal Trade Commission</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Children's Online Privacy Protection, </DOC>
                    <PGS>2034-2076</PGS>
                    <FRDOCBP>2023-28569</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Food and Drug</EAR>
            <HD>Food and Drug Administration</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Food Additive Petition:</SJ>
                <SJDENT>
                    <SJDOC>Environmental Defense Fund, et al.; Remove the Solvents Benzene, Ethylene Dichloride, Methylene Chloride, and Trichloroethylene, </SJDOC>
                    <PGS>1857-1858</PGS>
                    <FRDOCBP>2024-00411</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Environmental Defense Fund, et al.; Remove the Solvents Ethylene Dichloride, Methylene Chloride, and Trichloroethylene, </SJDOC>
                    <PGS>1856-1857</PGS>
                    <FRDOCBP>2024-00410</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Electronic Records; Electronic Signatures, </SJDOC>
                    <PGS>1921-1922</PGS>
                    <FRDOCBP>2024-00406</FRDOCBP>
                </SJDENT>
                <SJ>Guidance:</SJ>
                <SJDENT>
                    <SJDOC>Q5A(R2) Viral Safety Evaluation of Biotechnology Products Derived from Cell Lines of Human or Animal Origin, </SJDOC>
                    <PGS>1925-1927</PGS>
                    <FRDOCBP>2024-00407</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Requests for Reconsideration at the Division Level Under the Generic Drug User Fee Amendments, </SJDOC>
                    <PGS>1923-1924</PGS>
                    <FRDOCBP>2024-00403</FRDOCBP>
                </SJDENT>
                <SJ>Issuance of Priority Review Voucher:</SJ>
                <SJDENT>
                    <SJDOC>Rare Pediatric Disease Product, </SJDOC>
                    <PGS>1924-1925</PGS>
                    <FRDOCBP>2024-00400</FRDOCBP>
                      
                    <FRDOCBP>2024-00401</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>General Services</EAR>
            <HD>General Services Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Civil Monetary Penalty Inflation Adjustment, </DOC>
                    <PGS>1832-1833</PGS>
                    <FRDOCBP>2024-00446</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Health and Human</EAR>
            <HD>Health and Human Services Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Centers for Medicare &amp; Medicaid Services</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Children and Families Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Food and Drug Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Institutes of Health</P>
            </SEE>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Safeguarding the Rights of Conscience as Protected by Federal Statutes, </DOC>
                    <PGS>2078-2109</PGS>
                    <FRDOCBP>2024-00091</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Homeland</EAR>
            <HD>Homeland Security Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Federal Emergency Management Agency</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>U.S. Customs and Border Protection</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Housing</EAR>
            <HD>Housing and Urban Development Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Competitive Discretionary Funding Opportunity Announcements, </SJDOC>
                    <PGS>1936-1938</PGS>
                    <FRDOCBP>2024-00430</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Industry</EAR>
            <HD>Industry and Security Bureau</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Hearings, Meetings, Proceedings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Sensors and Instrumentation Technical Advisory Committee, </SJDOC>
                    <PGS>1876</PGS>
                    <FRDOCBP>2024-00422</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Interior</EAR>
            <HD>Interior Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Park Service</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Internal Revenue</EAR>
            <HD>Internal Revenue Service</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Hearings, Meetings, Proceedings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Section 30D Excluded Entities; Transfer of Clean Vehicle Credits Under Section 25E and Section 30D; Section 30D New Clean Vehicle Credit, </SJDOC>
                    <PGS>1858-1859</PGS>
                    <FRDOCBP>2024-00375</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>International Trade Adm</EAR>
            <HD>International Trade Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Antidumping or Countervailing Duty Investigations, Orders, or Reviews:</SJ>
                <SJDENT>
                    <SJDOC>Certain Carbon and Alloy Steel Cut-to-Length Plate from the Federal Republic of Germany, </SJDOC>
                    <PGS>1882-1883</PGS>
                    <FRDOCBP>2024-00398</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Certain Frozen Warmwater Shrimp from the People's Republic of China, India, Thailand, and the Socialist Republic of Vietnam; Correction, </SJDOC>
                    <PGS>1883-1884</PGS>
                    <FRDOCBP>2024-00396</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Certain Welded Carbon Steel Pipes and Tubes from India, Thailand et al.; Certain Circular Welded Non-Alloy Steel Pipe from Brazil, Mexico et al.; etc., </SJDOC>
                    <PGS>1877-1880</PGS>
                    <FRDOCBP>2024-00397</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Export Trade Certificate of Review, </DOC>
                    <PGS>1880-1882</PGS>
                    <FRDOCBP>2024-00367</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>International Trade Com</EAR>
            <HD>International Trade Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Meetings; Sunshine Act, </DOC>
                    <PGS>1944</PGS>
                    <FRDOCBP>2024-00544</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Labor Department</EAR>
            <HD>Labor Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Employment and Training Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Labor Statistics Bureau</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Mine Safety and Health Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Occupational Safety and Health Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Wage and Hour Division</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Workers Compensation Programs Office</P>
            </SEE>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Federal Civil Penalties Inflation Adjustment Act Annual Adjustments for 2024, </DOC>
                    <PGS>1810-1822</PGS>
                    <FRDOCBP>2024-00253</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Labor Statistics</EAR>
            <HD>Labor Statistics Bureau</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>1944-1945</PGS>
                    <FRDOCBP>2024-00374</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Maritime</EAR>
            <HD>Maritime Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Coastwise-Qualified Launch Barges, </DOC>
                    <PGS>1975-1976</PGS>
                    <FRDOCBP>2024-00443</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Mine</EAR>
            <HD>Mine Safety and Health Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Federal Civil Penalties Inflation Adjustment Act Annual Adjustments for 2024, </DOC>
                    <PGS>1810-1822</PGS>
                    <FRDOCBP>2024-00253</FRDOCBP>
                </DOCENT>
            </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>1945-1946</PGS>
                    <FRDOCBP>2024-00429</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Endowment for the Humanities</EAR>
            <HD>National Endowment for the Humanities</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Civil Monetary Penalty Inflation Adjustment, </DOC>
                    <PGS>1946</PGS>
                    <FRDOCBP>2024-00405</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>
                National Foundation
                <PRTPAGE P="v"/>
            </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>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Endowment for the Humanities</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>Ford Motor Co., </SJDOC>
                    <PGS>1976-1979</PGS>
                    <FRDOCBP>2024-00392</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Institute</EAR>
            <HD>National Institutes of Health</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Hearings, Meetings, Proceedings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Center for Scientific Review, </SJDOC>
                    <PGS>1929</PGS>
                    <FRDOCBP>2024-00372</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Eunice Kennedy Shriver National Institute of Child Health and Human Development, </SJDOC>
                    <PGS>1928-1929</PGS>
                    <FRDOCBP>2024-00369</FRDOCBP>
                      
                    <FRDOCBP>2024-00441</FRDOCBP>
                      
                    <FRDOCBP>2024-00442</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>National Heart, Lung, and Blood Institute, </SJDOC>
                    <PGS>1927-1928</PGS>
                    <FRDOCBP>2024-00440</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>National Institute of Neurological Disorders and Stroke, </SJDOC>
                    <PGS>1928</PGS>
                    <FRDOCBP>2024-00370</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Oceanic</EAR>
            <HD>National Oceanic and Atmospheric Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Environmental Impact Statements; Availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Endangered and Threatened Species; Take of Anadromous Fish; Withdrawal, </SJDOC>
                    <PGS>1910</PGS>
                    <FRDOCBP>2024-00473</FRDOCBP>
                </SJDENT>
                <SJ>Hearings, Meetings, Proceedings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>New England Fishery Management Council, </SJDOC>
                    <PGS>1909-1910</PGS>
                    <FRDOCBP>2024-00471</FRDOCBP>
                </SJDENT>
                <SJ>Permits; Applications, Issuances, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Marine Mammals; File No. 27099, </SJDOC>
                    <PGS>1908-1909</PGS>
                    <FRDOCBP>2024-00450</FRDOCBP>
                </SJDENT>
                <SJ>Taking or Importing of Marine Mammals:</SJ>
                <SJDENT>
                    <SJDOC>Geophysical Surveys Related to Oil and Gas Activities in the Gulf of Mexico, </SJDOC>
                    <PGS>1905-1908</PGS>
                    <FRDOCBP>2024-00368</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Sitka Seaplane Base Construction, </SJDOC>
                    <PGS>1884-1905</PGS>
                    <FRDOCBP>2024-00390</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Park</EAR>
            <HD>National Park Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Inventory Completion:</SJ>
                <SJDENT>
                    <SJDOC>Denver Museum of Nature and Science, Denver, CO, </SJDOC>
                    <PGS>1943-1944</PGS>
                    <FRDOCBP>2024-00434</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Indiana University, Bloomington, IN, </SJDOC>
                    <PGS>1940</PGS>
                    <FRDOCBP>2024-00436</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>University of California, Riverside, Riverside, CA, </SJDOC>
                    <PGS>1941-1943</PGS>
                    <FRDOCBP>2024-00432</FRDOCBP>
                      
                    <FRDOCBP>2024-00433</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>University of Minnesota Twin Cities, Minneapolis MN; Minnesota Indian Affairs Council, St. Paul/Bemidji, MN; et al., </SJDOC>
                    <PGS>1939-1940</PGS>
                    <FRDOCBP>2024-00431</FRDOCBP>
                </SJDENT>
                <SJ>Repatriation of Cultural Items:</SJ>
                <SJDENT>
                    <SJDOC>Indiana University, Bloomington, IN, </SJDOC>
                    <PGS>1938-1939</PGS>
                    <FRDOCBP>2024-00435</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Nuclear Regulatory</EAR>
            <HD>Nuclear Regulatory Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Licenses and Radiation Safety Requirements for Irradiators, </SJDOC>
                    <PGS>1946-1948</PGS>
                    <FRDOCBP>2024-00463</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Occupational Safety Health Adm</EAR>
            <HD>Occupational Safety and Health Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Federal Civil Penalties Inflation Adjustment Act Annual Adjustments for 2024, </DOC>
                    <PGS>1810-1822</PGS>
                    <FRDOCBP>2024-00253</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Peace</EAR>
            <HD>Peace Corps</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Privacy Act; Systems of Records, </DOC>
                    <PGS>1948-1950</PGS>
                    <FRDOCBP>2024-00371</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>1950-1951</PGS>
                    <FRDOCBP>2024-00423</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Postal Service</EAR>
            <HD>Postal Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Product Change:</SJ>
                <SJDENT>
                    <SJDOC>Priority Mail and USPS Ground Advantage Negotiated Service Agreement, </SJDOC>
                    <PGS>1951-1952</PGS>
                    <FRDOCBP>2024-00380</FRDOCBP>
                      
                    <FRDOCBP>2024-00381</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Priority Mail Express, Priority Mail, and USPS Ground Advantage Negotiated Service Agreement, </SJDOC>
                    <PGS>1951</PGS>
                    <FRDOCBP>2024-00387</FRDOCBP>
                </SJDENT>
            </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>1964</PGS>
                    <FRDOCBP>2024-00402</FRDOCBP>
                </DOCENT>
                <SJ>Application:</SJ>
                <SJDENT>
                    <SJDOC>Octagon XAI CLO Income Fund and XA Investments LLC, </SJDOC>
                    <PGS>1964</PGS>
                    <FRDOCBP>2024-00472</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Civil Monetary Penalty Inflation Adjustment, </DOC>
                    <PGS>1970-1972</PGS>
                    <FRDOCBP>2024-00378</FRDOCBP>
                </DOCENT>
                <SJ>Self-Regulatory Organizations; Proposed Rule Changes:</SJ>
                <SJDENT>
                    <SJDOC>Cboe EDGX Exchange, Inc., </SJDOC>
                    <PGS>1966-1970</PGS>
                    <FRDOCBP>2024-00385</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>LCH SA, </SJDOC>
                    <PGS>1952-1963</PGS>
                    <FRDOCBP>2024-00383</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>New York Stock Exchange LLC, </SJDOC>
                    <PGS>1965-1966</PGS>
                    <FRDOCBP>2024-00386</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>NYSE Arca, Inc., </SJDOC>
                    <PGS>1972-1973</PGS>
                    <FRDOCBP>2024-00384</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Social</EAR>
            <HD>Social Security Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Civil Monetary Penalty Inflation Adjustment, </DOC>
                    <PGS>1973</PGS>
                    <FRDOCBP>2024-00408</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Finding Regarding Foreign Social Insurance or Pension System of Cambodia, </DOC>
                    <PGS>1973-1975</PGS>
                    <FRDOCBP>2024-00404</FRDOCBP>
                </DOCENT>
            </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>Hidden Faces: Covered Portraits of the Renaissance, </SJDOC>
                    <PGS>1975</PGS>
                    <FRDOCBP>2024-00388</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Transportation Department</EAR>
            <HD>Transportation Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Federal Aviation Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>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>Internal Revenue Service</P>
            </SEE>
            <CAT>
                <HD>RULES</HD>
                <SJ>Import Restrictions:</SJ>
                <SJDENT>
                    <SJDOC>Certain Archaeological Material from China, </SJDOC>
                    <PGS>1808-1810</PGS>
                    <FRDOCBP>2024-00394</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Customs</EAR>
            <HD>U.S. Customs and Border Protection</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Import Restrictions:</SJ>
                <SJDENT>
                    <SJDOC>Certain Archaeological Material from China, </SJDOC>
                    <PGS>1808-1810</PGS>
                    <FRDOCBP>2024-00394</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Quarterly Interest Rates Used in Calculating Interest on Overdue Accounts and Refunds of Customs Duties, </DOC>
                    <PGS>1929-1931</PGS>
                    <FRDOCBP>2024-00389</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Wage</EAR>
            <HD>Wage and Hour Division</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Federal Civil Penalties Inflation Adjustment Act Annual Adjustments for 2024, </DOC>
                    <PGS>1810-1822</PGS>
                    <FRDOCBP>2024-00253</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Workers'</EAR>
            <HD>Workers Compensation Programs Office</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Federal Civil Penalties Inflation Adjustment Act Annual Adjustments for 2024, </DOC>
                    <PGS>1810-1822</PGS>
                    <FRDOCBP>2024-00253</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <PTS>
            <HD SOURCE="HED">Separate Parts In This Issue</HD>
            <HD>Part II</HD>
            <DOCENT>
                <DOC>Education Department, </DOC>
                <PGS>1982-2031</PGS>
                <FRDOCBP>2023-27682</FRDOCBP>
                <PRTPAGE P="vi"/>
            </DOCENT>
            <HD>Part III</HD>
            <DOCENT>
                <DOC>Federal Trade Commission, </DOC>
                <PGS>2034-2076</PGS>
                <FRDOCBP>2023-28569</FRDOCBP>
            </DOCENT>
            <HD>Part IV</HD>
            <DOCENT>
                <DOC>Health and Human Services Department, </DOC>
                <PGS>2078-2109</PGS>
                <FRDOCBP>2024-00091</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>89</VOL>
    <NO>8</NO>
    <DATE>Thursday, January 11, 2024</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <RULES>
        <RULE>
            <PREAMB>
                <PRTPAGE P="1787"/>
                <AGENCY TYPE="F">CONSUMER FINANCIAL PROTECTION BUREAU</AGENCY>
                <CFR>12 CFR Part 1083</CFR>
                <SUBJECT>Civil Penalty Inflation Adjustments</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Consumer Financial Protection Bureau.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Consumer Financial Protection Bureau (CFPB) is adjusting for inflation the maximum amount of each civil penalty within the CFPB's jurisdiction. These adjustments are required by the Federal Civil Penalties Inflation Adjustment Act of 1990 (Inflation Adjustment Act), as amended by the Debt Collection Improvement Act of 1996 and further amended by the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015. The inflation adjustments mandated by the Inflation Adjustment Act serve to maintain the deterrent effect of civil penalties and to promote compliance with the law.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This final rule is effective January 15, 2024.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Anna Boadwee and Adrien Fernandez, Attorney-Advisors, Office of Regulations, at (202) 435-7700. If you require this document in an alternative electronic format, please contact 
                        <E T="03">CFPB_Accessibility@cfpb.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    The Inflation Adjustment Act,
                    <SU>1</SU>
                    <FTREF/>
                     as amended by the Debt Collection Improvement Act of 1996 
                    <SU>2</SU>
                    <FTREF/>
                     and further amended by the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015,
                    <SU>3</SU>
                    <FTREF/>
                     directs Federal agencies to adjust the civil penalty amounts within their jurisdictions for inflation not later than July 1, 2016, and then not later than January 15 every year thereafter.
                    <SU>4</SU>
                    <FTREF/>
                     Each agency was required to make the 2016 one-time catch-up adjustments through an interim final rule published in the 
                    <E T="04">Federal Register</E>
                    . On June 14, 2016, the CFPB published its interim final rule (IFR) to make the initial catch-up adjustments to civil penalties within the CFPB's jurisdiction.
                    <SU>5</SU>
                    <FTREF/>
                     The June 2016 IFR created a new part 1083 and in § 1083.1 established the inflation-adjusted maximum amounts for each civil penalty within the CFPB's jurisdiction.
                    <SU>6</SU>
                    <FTREF/>
                     The CFPB finalized the IFR on January 31, 2019.
                    <SU>7</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Public Law 101-410, 104 Stat. 890.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Public Law 104-134, sec. 31001(s)(1), 110 Stat. 1321, 1321-373.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         Public Law 114-74, sec. 701, 129 Stat. 584, 599.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         Section 1301(a) of the Federal Reports Elimination Act of 1998, Public Law 105-362, 112 Stat. 3293, also amended the Inflation Adjustment Act by striking section 6, which contained annual reporting requirements, and redesignating section 7 as section 6, but did not alter the civil penalty adjustment requirements; 28 U.S.C. 2461 note.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         81 FR 38569 (June 14, 2016). Although the CFPB was not obligated to solicit comment for the interim final rule, the CFPB invited public comment and received none.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         12 CFR 1083.1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         84 FR 517 (Jan. 31, 2019).
                    </P>
                </FTNT>
                <P>
                    The Inflation Adjustment Act also requires subsequent adjustments to be made annually, not later than January 15, and notwithstanding section 553 of the Administrative Procedure Act (APA).
                    <SU>8</SU>
                    <FTREF/>
                     The CFPB annually adjusted its civil penalty amounts, as required by the Act.
                    <SU>9</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         Inflation Adjustment Act section 4, codified at 28 U.S.C. 2461 note. As discussed in guidance issued by the Director of the Office of Management and Budget (OMB), the APA generally requires notice, an opportunity for comment, and a delay in effective date for certain rulemakings, but the Inflation Adjustment Act provides that these procedures are not required for agencies to issue regulations implementing the annual adjustment. 
                        <E T="03">See</E>
                         Memorandum for the Heads of Exec. Dep'ts &amp; Agencies from Shalanda D. Young, Director, Implementation of Penalty Inflation Adjustments for 2023, Pursuant to the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015, Off. of Mgmt. &amp; Budget (Dec. 19, 2023), 
                        <E T="03">available at https://www.whitehouse.gov/wp-content/uploads/2023/12/M-24-07-Implementation-of-Penalty-Inflation-Adjustments-for-2024.pdf.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See</E>
                         82 FR 3601 (Jan. 12, 2017); 83 FR 1525 (Jan. 12, 2018); 84 FR 517 (Jan. 31, 2019); 85 FR 2012 (Jan. 14, 2020); 86 FR 3767 (Jan. 15, 2021); 87 FR 2314 (Jan. 14, 2022); 88 FR 1 (Jan. 3, 2023).
                    </P>
                </FTNT>
                <P>
                    Specifically, the Inflation Adjustment Act directs Federal agencies to adjust annually each civil penalty provided by law within the jurisdiction of each agency by the “cost-of-living adjustment.” 
                    <SU>10</SU>
                    <FTREF/>
                     The “cost-of-living adjustment” is defined as the percentage (if any) by which the Consumer Price Index for All Urban Consumers (CPI-U) for the month of October preceding the date of the adjustment, exceeds the CPI-U for October of the prior year.
                    <SU>11</SU>
                    <FTREF/>
                     The Director of the Office of Management and Budget (OMB) is required to issue guidance (OMB Guidance) every year by December 15 to agencies on implementing the annual civil penalty inflation adjustments. Pursuant to the Inflation Adjustment Act and OMB Guidance, agencies must apply the multiplier reflecting the “cost-of-living adjustment” to the current penalty amount and then round that amount to the nearest dollar to determine the annual adjustments.
                    <SU>12</SU>
                    <FTREF/>
                     The adjustments are designed to keep pace with inflation so that civil penalties retain their deterrent effect and promote compliance with the law.
                    <SU>13</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         Inflation Adjustment Act sections 4 and 5, codified at 28 U.S.C. 2461 note.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         Inflation Adjustment Act sections 3 and 5, codified at 28 U.S.C. 2461 note.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         Inflation Adjustment Act section 5, codified at 28 U.S.C. 2461 note; 
                        <E T="03">see also</E>
                         Memorandum for the Heads of Exec. Dep'ts &amp; Agencies from Shalanda D. Young, Director, Implementation of Penalty Inflation Adjustments for 2023, Pursuant to the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015, Off. of Mgmt. &amp; Budget (Dec. 19, 2023), 
                        <E T="03">available at https://www.whitehouse.gov/wp-content/uploads/2023/12/M-24-07-Implementation-of-Penalty-Inflation-Adjustments-for-2024.pdf.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See</E>
                         Inflation Adjustment Act section 2, codified at 28 U.S.C. 2461 note.
                    </P>
                </FTNT>
                <P>For the 2024 annual adjustment, the multiplier reflecting the “cost-of-living adjustment” is 1.03241.</P>
                <HD SOURCE="HD1">II. Adjustment</HD>
                <P>
                    Pursuant to the Inflation Adjustment Act and OMB Guidance, the CFPB multiplied each of its civil penalty amounts by the “cost-of-living adjustment” multiplier and rounded to the nearest dollar.
                    <SU>14</SU>
                    <FTREF/>
                     The new penalty amounts that apply to civil penalties assessed after January 15, 2024 are as follows:
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         Inflation Adjustment Act section 4, codified at 28 U.S.C. 2461 note.
                    </P>
                </FTNT>
                <PRTPAGE P="1788"/>
                <GPOTABLE COLS="5" OPTS="L2,tp0,i1" CDEF="s50,xs135,11,15,10">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Law</CHED>
                        <CHED H="1">Penalty description</CHED>
                        <CHED H="1">
                            Penalty
                            <LI>amounts</LI>
                            <LI>established</LI>
                            <LI>under 2023</LI>
                            <LI>final rule</LI>
                        </CHED>
                        <CHED H="1">
                            OMB
                            <LI>“cost-of-living</LI>
                            <LI>adjustment”</LI>
                            <LI>multiplier</LI>
                        </CHED>
                        <CHED H="1">
                            New
                            <LI>penalty</LI>
                            <LI>
                                amount 
                                <SU>15</SU>
                            </LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Consumer Financial Protection Act, 12 U.S.C. 5565(c)(2)(A)</ENT>
                        <ENT>Tier 1 penalty</ENT>
                        <ENT>$6,813</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>$7,034</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Consumer Financial Protection Act, 12 U.S.C. 5565(c)(2)(B)</ENT>
                        <ENT>Tier 2 penalty</ENT>
                        <ENT>34,065</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>35,169</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Consumer Financial Protection Act, 12 U.S.C. 5565(c)(2)(C)</ENT>
                        <ENT>Tier 3 penalty</ENT>
                        <ENT>1,362,567</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>1,406,728</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Interstate Land Sales Full Disclosure Act, 15 U.S.C. 1717a(a)(2)</ENT>
                        <ENT>Per violation</ENT>
                        <ENT>2,374</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>2,451</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Interstate Land Sales Full Disclosure Act, 15 U.S.C. 1717a(a)(2)</ENT>
                        <ENT>Annual cap</ENT>
                        <ENT>2,372,677</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>2,449,575</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Real Estate Settlement Procedures Act, 12 U.S.C. 2609(d)(1)</ENT>
                        <ENT>Per failure</ENT>
                        <ENT>111</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>115</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Real Estate Settlement Procedures Act, 12 U.S.C. 2609(d)(1)</ENT>
                        <ENT>Annual cap</ENT>
                        <ENT>223,229</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>230,464</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Real Estate Settlement Procedures Act, 12 U.S.C. 2609(d)(2)(A)</ENT>
                        <ENT>Per failure, where intentional</ENT>
                        <ENT>223</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>230</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SAFE Act, 12 U.S.C. 5113(d)(2)</ENT>
                        <ENT>Per violation</ENT>
                        <ENT>34,401</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>35,516</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Truth in Lending Act, 15 U.S.C. 1639e(k)(1)</ENT>
                        <ENT>First violation</ENT>
                        <ENT>13,627</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>14,069</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Truth in Lending Act, 15 U.S.C. 1639e(k)(2)</ENT>
                        <ENT>Subsequent violations</ENT>
                        <ENT>27,252</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>28,135</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">III. Procedural Requirements</HD>
                <HD SOURCE="HD2">A. Administrative Procedure Act</HD>
                <P>
                    Under
                    <FTREF/>
                     the APA, notice and opportunity for public comment are not required if the CFPB finds that notice and public comment are impracticable, unnecessary, or contrary to the public interest.
                    <SU>16</SU>
                    <FTREF/>
                     The adjustments to the civil penalty amounts are technical and non-discretionary, and they merely apply the statutory method for adjusting civil penalty amounts. These adjustments are required by the Inflation Adjustment Act. Moreover, the Inflation Adjustment Act directs agencies to adjust civil penalties annually notwithstanding section 553 of the APA,
                    <SU>17</SU>
                    <FTREF/>
                     and OMB Guidance reaffirms that agencies need not complete a notice-and-comment process before making the annual adjustments for inflation.
                    <SU>18</SU>
                    <FTREF/>
                     For these reasons, the CFPB has determined that publishing a notice of proposed rulemaking and providing opportunity for public comment are unnecessary. The amendments therefore are adopted in final form.
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         Numbers may not multiply to totals shown because of rounding.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         5 U.S.C. 553(b)(B).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         Inflation Adjustment Act section 4, codified at 28 U.S.C. 2461 note.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         Memorandum for the Heads of Exec. Dep'ts &amp; Agencies from Shalanda D. Young, Director, Implementation of Penalty Inflation Adjustments for 2023, Pursuant to the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015, Off. of Mgmt. &amp; Budget (Dec. 19, 2023), 
                        <E T="03">available at https://www.whitehouse.gov/wp-content/uploads/2023/12/M-24-07-Implementation-of-Penalty-Inflation-Adjustments-for-2024.pdf.</E>
                    </P>
                </FTNT>
                <P>
                    Section 553(d) of the APA generally requires publication of a final rule not less than 30 days before its effective date, except (1) a substantive rule which grants or recognizes an exemption or relieves a restriction; (2) interpretive rules and statements of policy; or (3) as otherwise provided by the agency for good cause found and published with the rule.
                    <SU>19</SU>
                    <FTREF/>
                     At minimum, the CFPB believes the annual adjustments to the civil penalty amounts in § 1083.1(a) fall under the third exception to section 553(d). The CFPB finds that there is good cause to make the amendments effective on January 15, 2024. The amendments to § 1083.1(a) in this final rule are technical and non-discretionary, and they merely apply the statutory method for adjusting civil penalty amounts and follow the statutory directive to make annual adjustments each year. Moreover, the Inflation Adjustment Act directs agencies to adjust the civil penalties annually notwithstanding section 553 of the APA,
                    <SU>20</SU>
                    <FTREF/>
                     and OMB Guidance reaffirms that agencies need not provide a delay in effective date for the annual adjustments for inflation.
                    <SU>21</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         5 U.S.C. 553(d).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         Inflation Adjustment Act section 4, codified at 28 U.S.C. 2461 note.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         Memorandum for the Heads of Exec. Dep'ts &amp; Agencies from Shalanda D. Young, Director, Implementation of Penalty Inflation Adjustments for 2023, Pursuant to the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015, Off. of Mgmt. &amp; Budget (Dec. 19, 2023), 
                        <E T="03">available at https://www.whitehouse.gov/wp-content/uploads/2023/12/M-24-07-Implementation-of-Penalty-Inflation-Adjustments-for-2024.pdf.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Regulatory Flexibility Act</HD>
                <P>
                    The Regulatory Flexibility Act (RFA) does not apply to a rulemaking where a general notice of proposed rulemaking is not required.
                    <SU>22</SU>
                    <FTREF/>
                     As noted previously, the CFPB has determined that it is unnecessary to publish a general notice of proposed rulemaking for this final rule. Accordingly, the RFA's requirements relating to an initial and final regulatory flexibility analysis do not apply.
                </P>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         5 U.S.C. 603(a), 604(a).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">C. Paperwork Reduction Act</HD>
                <P>
                    In accordance with the Paperwork Reduction Act of 1995,
                    <SU>23</SU>
                    <FTREF/>
                     the CFPB reviewed this final rule. The CFPB has determined that this rule does not create any new information collections or substantially revise any existing collections.
                </P>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         44 U.S.C. 3506; 5 CFR part 1320.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">D. Congressional Review Act</HD>
                <P>
                    Pursuant to the Congressional Review Act (5 U.S.C. 801 
                    <E T="03">et seq.</E>
                    ), the CFPB will submit a report containing this rule and other required information to the United States Senate, the United States House of Representatives, and the Comptroller General of the United States prior to the rule taking effect. The Office of Information and Regulatory Affairs (OIRA) has designated this rule as not a “major rule” as defined by 5 U.S.C. 804(2).
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 12 CFR Part 1083</HD>
                    <P>Administrative practice and procedure, Consumer protection, Penalties.</P>
                </LSTSUB>
                <HD SOURCE="HD1">Authority and Issuance</HD>
                <P>For the reasons set forth in the preamble, the CFPB amends 12 CFR part 1083 as set forth below:</P>
                <PART>
                    <PRTPAGE P="1789"/>
                    <HD SOURCE="HED">PART 1083—CIVIL PENALTY ADJUSTMENTS</HD>
                </PART>
                <REGTEXT TITLE="12" PART="1083">
                    <AMDPAR>1. The authority citation for part 1083 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 12 U.S.C. 2609(d); 12 U.S.C. 5113(d)(2); 12 U.S.C. 5565(c); 15 U.S.C. 1639e(k); 15 U.S.C. 1717a(a); 28 U.S.C. 2461 note.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="12" PART="1083">
                    <AMDPAR>2. Section 1083.1 is revised to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1083.1</SECTNO>
                        <SUBJECT>Adjustment of civil penalty amounts.</SUBJECT>
                        <P>(a) The maximum amount of each civil penalty within the jurisdiction of the Consumer Financial Protection Bureau to impose is adjusted in accordance with the Federal Civil Penalties Inflation Adjustment Act of 1990, as amended by the Debt Collection Improvement Act of 1996 and further amended by the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015 (28 U.S.C. 2461 note), as follows:</P>
                        <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s50,r50,14">
                            <TTITLE>
                                Table 1 to Paragraph 
                                <E T="01">(a)</E>
                            </TTITLE>
                            <BOXHD>
                                <CHED H="1">Law</CHED>
                                <CHED H="1">Penalty description</CHED>
                                <CHED H="1">
                                    Adjusted
                                    <LI>maximum civil</LI>
                                    <LI>penalty amount</LI>
                                </CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">12 U.S.C. 5565(c)(2)(A)</ENT>
                                <ENT>Tier 1 penalty</ENT>
                                <ENT>$7,034</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">12 U.S.C. 5565(c)(2)(B)</ENT>
                                <ENT>Tier 2 penalty</ENT>
                                <ENT>35,169</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">12 U.S.C. 5565(c)(2)(C)</ENT>
                                <ENT>Tier 3 penalty</ENT>
                                <ENT>1,406,728</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">15 U.S.C. 1717a(a)(2)</ENT>
                                <ENT>Per violation</ENT>
                                <ENT>2,451</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">15 U.S.C. 1717a(a)(2)</ENT>
                                <ENT>Annual cap</ENT>
                                <ENT>2,449,575</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">12 U.S.C. 2609(d)(1)</ENT>
                                <ENT>Per failure</ENT>
                                <ENT>115</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">12 U.S.C. 2609(d)(1)</ENT>
                                <ENT>Annual cap</ENT>
                                <ENT>230,464</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">12 U.S.C. 2609(d)(2)(A)</ENT>
                                <ENT>Per failure, where intentional</ENT>
                                <ENT>230</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">12 U.S.C. 5113(d)(2)</ENT>
                                <ENT>Per violation</ENT>
                                <ENT>35,516</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">15 U.S.C. 1639e(k)(1)</ENT>
                                <ENT>First violation</ENT>
                                <ENT>14,069</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">15 U.S.C. 1639e(k)(2)</ENT>
                                <ENT>Subsequent violations</ENT>
                                <ENT>28,135</ENT>
                            </ROW>
                        </GPOTABLE>
                        <P>(b) The adjustments in paragraph (a) of this section shall apply to civil penalties assessed after January 15, 2024, whose associated violations occurred on or after November 2, 2015.</P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <NAME>Brian Shearer,</NAME>
                    <TITLE>Senior Advisor, Consumer Financial Protection Bureau.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00456 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4810-AM-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 71</CFR>
                <DEPDOC>[Docket No. FAA-2023-2114; Airspace Docket No. 23-AEA-17]</DEPDOC>
                <RIN>RIN 2120-AA66</RIN>
                <SUBJECT>Amendment of Class E Airspace; Bedford, PA</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 Class E airspace at Bedford, PA. This action is the result of an airspace review conducted due to the decommissioning of the St. Thomas very high frequency omnidirectional range (VOR) as part of the VOR Minimum Operating Network (MON) Program. This action brings the airspace into compliance with FAA orders to support instrument flight rule (IFR) operations.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective 0901 UTC, March 21, 2024. The Director of the Federal Register approves this incorporation by reference action under 1 CFR part 51, subject to the annual revision of FAA Order JO 7400.11 and publication of conforming amendments.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        A copy of the Notice of Proposed Rulemaking (NPRM), all comments received, 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.
                    </P>
                    <P>
                        FAA Order JO 7400.11H, Airspace Designations and Reporting Points, and subsequent amendments can be viewed online at 
                        <E T="03">www.faa.gov/air_traffic/publications/.</E>
                         You may also contact the Rules and Regulations Group, Office of Policy, Federal Aviation Administration, 800 Independence Avenue SW, Washington, DC 20591; telephone: (202) 267-8783.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Jeffrey Claypool, Federal Aviation Administration, Operations Support Group, Central Service Center, 10101 Hillwood Parkway, Fort Worth, TX 76177; telephone (817) 222-5711.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>The FAA's authority to issue rules regarding aviation safety is found in Title 49 of the United States Code. Subtitle I, Section 106 describes the authority of the FAA Administrator. Subtitle VII, Aviation Programs, describes in more detail the scope of the agency's authority. This rulemaking is promulgated under the authority described in Subtitle VII, Part A, Subpart I, Section 40103. Under that section, the FAA is charged with prescribing regulations to assign the use of airspace necessary to ensure the safety of aircraft and the efficient use of airspace. This regulation is within the scope of that authority as it amends the Class E airspace extending upward from 700 feet above the surface at Bedford County Airport, Bedford, PA, to support IFR operations at this airport.</P>
                <HD SOURCE="HD1">History</HD>
                <P>
                    The FAA published an NPRM for Docket No. FAA-2023-2114 in the 
                    <E T="04">Federal Register</E>
                     (88 FR 76155; November 6, 2023) proposing to amend the Class E airspace at Bedford, PA. Interested parties were invited to participate in this rulemaking effort by submitting written comments on the proposal to the FAA. No comments were received.
                </P>
                <HD SOURCE="HD1">Incorporation by Reference</HD>
                <P>
                    Class E airspace designations are published in paragraph 6005 of FAA Order JO 7400.11, Airspace Designations and Reporting Points, which is incorporated by reference in 14 CFR 71.1 on an annual basis. This document amends the current version of that order, FAA Order JO 7400.11H, dated August 11, 2023, and effective September 15, 2023. FAA Order JO 7400.11H is publicly available as listed in the 
                    <E T="02">ADDRESSES</E>
                     section of this 
                    <PRTPAGE P="1790"/>
                    document. These amendments will be published in the next update to FAA Order JO 7400.11.
                </P>
                <P>FAA Order JO 7400.11H lists Class A, B, C, D, and E airspace areas, air traffic service routes, and reporting points.</P>
                <HD SOURCE="HD1">The Rule</HD>
                <P>This amendment to 14 CFR part 71 modifies the Class E airspace extending upward from 700 feet above the surface to within an 8-mile (decreased from a 12.5-mile) radius of Bedford County Airport, Bedford, PA; and within 2 miles each side of the 128° bearing from the airport extending from the 8-mile radius to 13 miles southeast of the airport; and within 2 miles each side of the 308° bearing from the airport extending from the 8-mile radius to 14. 8 miles northwest of the airport.</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 Regulatory Policies and Procedures (44 FR 11034; February 26, 1979); and (3) does not warrant preparation of a regulatory evaluation as the anticipated impact is so minimal. Since this is a routine matter that only affects air traffic procedures and air navigation, it is certified 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 qualifies for categorical exclusion under the National Environmental Policy Act in accordance with FAA Order 1050.1F, “Environmental Impacts: Policies and Procedures,” paragraph 5-6.5.a. This airspace action is not expected to cause any potentially significant environmental impacts, and no extraordinary circumstances exist that warrant preparation of an environmental assessment.</P>
                <LSTSUB>
                    <HD SOURCE="HED">Lists of Subjects in 14 CFR 71</HD>
                    <P>Airspace, Incorporation by reference, Navigation (air).</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Amendment</HD>
                <P>In consideration of the foregoing, the Federal Aviation Administration amends 14 CFR part 71 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 71—DESIGNATION OF CLASS A, B, C, D, AND E AIRSPACE AREAS; AIR TRAFFIC SERVICE ROUTES; AND REPORTING POINTS</HD>
                </PART>
                <REGTEXT TITLE="14" PART="71">
                    <AMDPAR>1. The authority citation for 14 CFR part 71 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 49 U.S.C. 106(f), 106(g); 40103, 40113, 40120; E.O. 10854, 24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 71.1</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="14" PART="71">
                    <AMDPAR>2. The incorporation by reference in 14 CFR 71.1 of FAA Order JO 7400.11H, Airspace Designations and Reporting Points, dated August 11, 2023, and effective September 15, 2023, is amended as follows:</AMDPAR>
                    <EXTRACT>
                        <HD SOURCE="HD2">Paragraph 6005 Class E Airspace Areas Extending Upward From 700 Feet or More Above the Surface of the Earth.</HD>
                        <STARS/>
                        <HD SOURCE="HD1">AEA PA E5 Bedford, PA [Amended]</HD>
                        <FP SOURCE="FP-2">Bedford County Airport, PA</FP>
                        <FP SOURCE="FP1-2">(Lat 40°05′10″ N, long 78°30′49″ W)</FP>
                        <P>That airspace extending upward from 700 feet above the surface within an 8-mile radius of Bedford County Airport; and within 2 miles each side of the 128° bearing from the airport extending from the 8-mile radius to 13 miles southeast of the airport; and within 2 miles each side of the 308° bearing from the airport extending from the 8-mile radius to 14.8 miles northwest of the airport.</P>
                    </EXTRACT>
                    <STARS/>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Fort Worth, Texas, on January 3, 2024.</DATED>
                    <NAME>Martin A. Skinner,</NAME>
                    <TITLE>Acting Manager, Operations Support Group, ATO Central Service Center.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00193 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 71</CFR>
                <DEPDOC>[Docket No. FAA-2023-1548; Airspace Docket No. 22-ANM-62]</DEPDOC>
                <RIN>RIN 2120-AA66</RIN>
                <SUBJECT>Amendment of United States Area Navigation (RNAV) Route T-302 in the Vicinity of Acequia, ID</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 United States Area Navigation (RNAV) route T-302 in the vicinity of Acequia, ID to increase the RNAV route's lateral separation from restricted area 3203 (R-3203) and from parachute activities at Nampa Municipal Airport (MAN) and Caldwell Executive Airport in Idaho (EUL).</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective date 0901 UTC, March 21, 2024. The Director of the Federal Register approves this incorporation by reference action under 1 CFR part 51, subject to the annual revision of FAA Order JO 7400.11 and publication of conforming amendments.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        A copy of the Notice of Proposed Rulemaking (NPRM), all comments received, 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.
                    </P>
                    <P>
                        FAA Order JO 7400.11H, Airspace Designations and Reporting Points, and subsequent amendments can be viewed online at 
                        <E T="03">www.faa.gov/air_traffic/publications/.</E>
                         You may also contact the Rules and Regulations Group, Office of Policy, Federal Aviation Administration, 800 Independence Avenue SW, Washington, DC 20591; telephone: (202) 267-8783.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Steven Roff, Rules and Regulations Group, Office of Policy, Federal Aviation Administration, 800 Independence Avenue SW, Washington, DC 20591; telephone: (202) 267-8783.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>The FAA's authority to issue rules regarding aviation safety is found in Title 49 of the United States Code. Subtitle I, Section 106 describes the authority of the FAA Administrator. Subtitle VII, Aviation Programs, describes in more detail the scope of the agency's authority. This rulemaking is promulgated under the authority described in Subtitle VII, Part A, Subpart I, Section 40103. Under that section, the FAA is charged with prescribing regulations to assign the use of 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 would increase the efficiency and safety of the flow of air traffic within the National Airspace System (NAS).</P>
                <HD SOURCE="HD1">History</HD>
                <P>
                    The FAA published a NPRM for Docket No. FAA-2023-1548 in the 
                    <E T="04">Federal Register</E>
                     (88 FR 46121; July 19, 2023), proposing to amend RNAV route T-302 in the vicinity of Acequia, ID. Interested parties were invited to participate in this rulemaking effort by submitting comments on the proposal. No comments were received.
                    <PRTPAGE P="1791"/>
                </P>
                <HD SOURCE="HD1">Differences From the NPRM</HD>
                <P>
                    The NPRM published for Docket No. FAA-2023-1548 in the 
                    <E T="04">Federal Register</E>
                     (88 FR 46121; July 19, 2023) contained a typographical error in the table listing the route points that describe the airway. The table stated that the UKAYI waypoint (WP) was in Idaho (ID). The UKAYI WP is in Oregon (OR). This rule corrects this error.
                </P>
                <HD SOURCE="HD1">Incorporation by Reference</HD>
                <P>
                    United States Area Navigation routes are published in paragraph 6011 of FAA Order JO 7400.11, Airspace Designations and Reporting Points, which is incorporated by reference in 14 CFR 71.1 on an annual basis. This document amends the current version of that order, FAA Order JO 7400.11H, dated August 11, 2023, and effective September 15, 2023. FAA Order JO 7400.11H is publicly available as listed in the 
                    <E T="02">ADDRESSES</E>
                     section of this document. These amendments will be published in the next update to FAA Order JO 7400.11.
                </P>
                <P>FAA Order JO 7400.11H lists Class A, B, C, D, and E airspace areas, air traffic service routes, and reporting points.</P>
                <HD SOURCE="HD1">The Rule</HD>
                <P>This action amends 14 CFR part 71 by amending RNAV route T-302 in the vicinity of Acequia, ID, to increase the RNAV route's lateral separation from R-3203 and from parachute activities at Nampa Municipal Airport and Caldwell Executive Airport in Idaho. The amendment is described below.</P>
                <P>
                    <E T="03">T-302:</E>
                     This rule adds the ALKAL, ID, Fix to the airway description. Additionally, the CANEK, ID, Fix is added between the ADEXE, ID, WP and the ALKAL, ID, Fix. Lastly, this rule removes the PARMO, ID, Fix from the airway. As amended T-302 extends between the CUKIS, OR, WP and the GRIFT, IL, WP.
                </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 Regulatory Policies and Procedures (44 FR 11034; February 26, 1979); and (3) does not warrant preparation of a regulatory evaluation as the anticipated impact is so minimal. Since this is a routine matter that only affects air traffic procedures and air navigation, it is certified 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 airspace action of amending RNAV route T-302 in the vicinity of Acequia, ID, qualifies for categorical exclusion under the National Environmental Policy Act (42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ) and its implementing regulations at 40 CFR part 1500, and in accordance with FAA Order 1050.1F, Environmental Impacts: Policies and Procedures, paragraph 5-6.5a, which categorically excludes from further environmental impact review rulemaking actions that designate or modify classes of airspace areas, airways, routes, and reporting points (see 14 CFR part 71, Designation of Class A, B, C, D, and E Airspace Areas; Air Traffic Service Routes; and Reporting Points), and paragraph 5-6.5i, which categorically excludes from further environmental review the establishment of new or revised air traffic control procedures conducted at 3,000 feet or more above ground level (AGL); procedures conducted below 3,000 feet AGL that do not cause traffic to be routinely routed over noise sensitive areas; modifications to currently approved procedures conducted below 3,000 feet AGL that do not significantly increase noise over noise sensitive areas; and increases in minimum altitudes and landing minima. As such, this action is not expected to result in any potentially significant environmental impacts. In accordance with FAA Order 1050.1F, paragraph 5-2 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. Accordingly, the FAA has determined that no extraordinary circumstances exist that warrant preparation of an environmental assessment or environmental impact study.
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 71</HD>
                    <P>Airspace, Incorporation by reference, Navigation (air).</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Amendment</HD>
                <P>In consideration of the foregoing, the Federal Aviation Administration amends 14 CFR part 71 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 71—DESIGNATION OF CLASS A, B, C, D, AND E AIRSPACE AREAS; AIR TRAFFIC SERVICE ROUTES; AND REPORTING POINTS</HD>
                </PART>
                <REGTEXT TITLE="14" PART="71">
                    <AMDPAR>1. The authority citation for 14 CFR part 71 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 49 U.S.C. 106(f), 106(g); 40103, 40113, 40120; E.O. 10854, 24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 71.1</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="14" PART="71">
                    <AMDPAR>2. The incorporation by reference in 14 CFR 71.1 of FAA Order JO 7400.11H, Airspace Designations and Reporting Points, dated August 11, 2023, and effective September 15, 2023, is amended as follows:</AMDPAR>
                    <EXTRACT>
                        <HD SOURCE="HD2">Paragraph 6011 United States Area Navigation Routes.</HD>
                        <STARS/>
                        <GPOTABLE COLS="3" OPTS="L0,tp0,p0,7/8,g1,t1,i1" CDEF="xls100,xls50,xls180">
                            <TTITLE> </TTITLE>
                            <BOXHD>
                                <CHED H="1"> </CHED>
                                <CHED H="1"> </CHED>
                                <CHED H="1"> </CHED>
                            </BOXHD>
                            <ROW EXPSTB="02" RUL="s">
                                <ENT I="22">
                                    <E T="04">T-302 CUKIS, OR to GRIFT, IL</E>
                                </ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="01">CUKIS, OR</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 45°20′59.59″ N, long. 122°21′49.41″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">JJETT, OR</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 44°56′35.43″ N, long. 121°40′56.36″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">CUPRI, OR</ENT>
                                <ENT>FIX</ENT>
                                <ENT>(Lat. 44°37′03.76″ N, long. 121°15′13.89″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">ZUDMI, OR</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 44°19′59.29″ N, long. 120°28′10.92″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Wildhorse, OR (ILR)</ENT>
                                <ENT>VOR/DME</ENT>
                                <ENT>(Lat. 43°35′35.27″ N, long. 118°57′18.18″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">JOSTN, OR</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 43°34′16.92″ N, long. 117°53′51.34″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">UKAYI, OR</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 43°46′57.60″ N, long. 117°05′24.14″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">ADEXE, ID</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 43°30′16.79″ N, long. 116°26′53.72″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">CANEK, ID</ENT>
                                <ENT>FIX</ENT>
                                <ENT>(Lat. 43°18′57.88″ N, long. 115°48′28.06″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">ALKAL, ID</ENT>
                                <ENT>FIX</ENT>
                                <ENT>(Lat. 43°00′58.35″ N, long. 115°19′41.26″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">FEVDO, ID</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 42°53′48.88″ N, long. 115°02′00.30″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">TOXEE, ID</ENT>
                                <ENT>FIX</ENT>
                                <ENT>(Lat. 42°41′41.81″ N, long. 114°27′13.10″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">JADUP, ID</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 42°44′32.00″ N, long. 113°42′15.22″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">MIKAE, WY</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 42°06′36.88″ N, long. 110°35′59.28″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">BXTER, WY</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 41°53′13.97″ N, long. 110°04′52.38″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">EEBEE, WY</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 41°44′07.05″ N, long. 109°35′10.21″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">REGVE, WY</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 41°38′35.07″ N, long. 109°20′30.96″ W)</ENT>
                            </ROW>
                            <ROW>
                                <PRTPAGE P="1792"/>
                                <ENT I="01">Rock Springs, WY (OCS)</ENT>
                                <ENT>VOR/DME</ENT>
                                <ENT>(Lat. 41°35′24.76″ N, long. 109°00′55.18″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">FIKLA, WY</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 41°56′20.50″ N, long. 106°57′11.03″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Medicine Bow, WY (MBW)</ENT>
                                <ENT>VOR/DME</ENT>
                                <ENT>(Lat. 41°50′43.88″ N, long. 106°00′15.42″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Scottsbluff, NE (BFF)</ENT>
                                <ENT>VORTAC</ENT>
                                <ENT>(Lat. 41°53′38.99″ N, long. 103°28′55.31″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">WAKPA, NE</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 42°03′21.64″ N, long. 103°04′57.99″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Alliance, NE (AIA)</ENT>
                                <ENT>VOR/DME</ENT>
                                <ENT>(Lat. 42°03′20.27″ N, long. 102°48′16.00″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">MARSS, NE</ENT>
                                <ENT>FIX</ENT>
                                <ENT>(Lat. 42°27′48.92″ N, long. 100°36′15.32″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">PUKFA, NE</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 42°22′59.52″ N, long. 099°59′36.42″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">GIYED, NE</ENT>
                                <ENT>FIX</ENT>
                                <ENT>(Lat. 42°30′22.02″ N, long. 099°08′05.55″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">LLUKY, NE</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 42°29′20.26″ N, long. 098°38′11.44″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">KAATO, IA</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 42°35′06.89″ N, long. 095°58′53.08″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">ROKKK, IA</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 42°37′00.00″ N, long. 094°04′03.00″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Waterloo, IA (ALO)</ENT>
                                <ENT>VOR/DME</ENT>
                                <ENT>(Lat. 42°33′23.39″ N, long. 092°23′56.13″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Dubuque, IA (DBQ)</ENT>
                                <ENT>VORTAC</ENT>
                                <ENT>(Lat. 42°24′05.29″ N, long. 090°42′32.68″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">JOOLZ, IL</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 42°20′41.49″ N, long. 090°12′12.00″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">GRIFT, IL</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 42°17′28.14″ N, long. 088°53′41.42″ W)</ENT>
                            </ROW>
                        </GPOTABLE>
                    </EXTRACT>
                    <STARS/>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Washington, DC, on January 2, 2024.</DATED>
                    <NAME>Frank Lias,</NAME>
                    <TITLE>Manager, Rules and Regulations Group.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00070 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 71</CFR>
                <DEPDOC>[Docket No. FAA-2023-2116; Airspace Docket No. 23-AGL-29]</DEPDOC>
                <RIN>RIN 2120-AA66</RIN>
                <SUBJECT>Amendment of Class E Airspace; Hutchinson, MN</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 Class E airspace at Hutchinson, MN. This action is the result of an airspace review conducted due to the decommissioning of the Darwin very high frequency omnidirectional range (VOR) as part of the VOR Minimum Operating Network (MON) Program. The name of the airport is also being updated to coincide with the FAA's aeronautical database. This action brings the airspace into compliance with FAA orders to support instrument flight rule (IFR) operations.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective 0901 UTC, March 21, 2024. The Director of the Federal Register approves this incorporation by reference action under 1 CFR part 51, subject to the annual revision of FAA Order JO 7400.11 and publication of conforming amendments.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        A copy of the Notice of Proposed Rulemaking (NPRM), all comments received, 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.
                    </P>
                    <P>
                        FAA Order JO 7400.11H, Airspace Designations and Reporting Points, and subsequent amendments can be viewed online at 
                        <E T="03">www.faa.gov/air_traffic/publications/.</E>
                         You may also contact the Rules and Regulations Group, Office of Policy, Federal Aviation Administration, 800 Independence Avenue SW, Washington, DC 20591; telephone: (202) 267-8783.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Jeffrey Claypool, Federal Aviation Administration, Operations Support Group, Central Service Center, 10101 Hillwood Parkway, Fort Worth, TX 76177; telephone (817) 222-5711.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>The FAA's authority to issue rules regarding aviation safety is found in Title 49 of the United States Code. Subtitle I, Section 106 describes the authority of the FAA Administrator. Subtitle VII, Aviation Programs, describes in more detail the scope of the agency's authority. This rulemaking is promulgated under the authority described in Subtitle VII, Part A, Subpart I, Section 40103. Under that section, the FAA is charged with prescribing regulations to assign the use of airspace necessary to ensure the safety of aircraft and the efficient use of airspace. This regulation is within the scope of that authority as it amends the Class E airspace extending upward from 700 feet above the surface at Hutchinson Municipal Airport/Butler Field, Hutchinson, MN, to support IFR operations at this airport.</P>
                <HD SOURCE="HD1">History</HD>
                <P>
                    The FAA published an NPRM for Docket No. FAA-2023-2116 in the 
                    <E T="04">Federal Register</E>
                     (88 FR 76153; November 6, 2023) proposing to amend the Class E airspace at Hutchinson, MN. Interested parties were invited to participate in this rulemaking effort by submitting written comments on the proposal to the FAA. No comments were received.
                </P>
                <HD SOURCE="HD1">Incorporation by Reference</HD>
                <P>
                    Class E airspace designations are published in paragraph 6005 of FAA Order JO 7400.11, Airspace Designations and Reporting Points, which is incorporated by reference in 14 CFR 71.1 on an annual basis. This document amends the current version of that order, FAA Order JO 7400.11H, dated August 11, 2023, and effective September 15, 2023. FAA Order JO 7400.11H is publicly available as listed in the 
                    <E T="02">ADDRESSES</E>
                     section of this document. These amendments will be published in the next update to FAA Order JO 7400.11.
                </P>
                <P>FAA Order JO 7400.11H lists Class A, B, C, D, and E airspace areas, air traffic service routes, and reporting points.</P>
                <HD SOURCE="HD1">The Rule</HD>
                <P>This amendment to 14 CFR part 71 modifies the Class E airspace extending upward from 700 feet above the surface to within a 6.4-mile (decreased from a 6.6-mile) radius of Hutchinson Municipal Airport/Butler Field, Hutchinson, MN; and updates the name (previously Hutchinson Municipal Airport-Butler Field) of airport to coincide with the FAA's aeronautical database.</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 Regulatory Policies and Procedures (44 FR 11034; February 26, 1979); and (3) does not warrant preparation of a regulatory evaluation as the anticipated impact is so minimal. Since this is a routine matter that only affects air traffic procedures and air navigation, it is certified that this rule, when 
                    <PRTPAGE P="1793"/>
                    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 qualifies for categorical exclusion under the National Environmental Policy Act in accordance with FAA Order 1050.1F, “Environmental Impacts: Policies and Procedures,” paragraph 5-6.5.a. This airspace action is not expected to cause any potentially significant environmental impacts, and no extraordinary circumstances exist that warrant preparation of an environmental assessment.</P>
                <LSTSUB>
                    <HD SOURCE="HED">Lists of Subjects in 14 CFR 71</HD>
                    <P>Airspace, Incorporation by reference, Navigation (air).</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Amendment</HD>
                <P>In consideration of the foregoing, the Federal Aviation Administration amends 14 CFR part 71 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 71—DESIGNATION OF CLASS A, B, C, D, AND E AIRSPACE AREAS; AIR TRAFFIC SERVICE ROUTES; AND REPORTING POINTS</HD>
                </PART>
                <REGTEXT TITLE="14" PART="71">
                    <AMDPAR>1. The authority citation for 14 CFR part 71 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 49 U.S.C. 106(f), 106(g); 40103, 40113, 40120; E.O. 10854, 24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 71.1</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="14" PART="71">
                    <AMDPAR>2. The incorporation by reference in 14 CFR 71.1 of FAA Order JO 7400.11H, Airspace Designations and Reporting Points, dated August 11, 2023, and effective September 15, 2023, is amended as follows:</AMDPAR>
                    <EXTRACT>
                        <HD SOURCE="HD2">Paragraph 6005 Class E Airspace Areas Extending Upward From 700 Feet or More Above the Surface of the Earth.</HD>
                        <STARS/>
                        <HD SOURCE="HD1">AGL MN E5 Hutchinson, MN [Amended]</HD>
                        <FP SOURCE="FP-2">Hutchinson Municipal Airport/Butler Field, MN</FP>
                        <FP SOURCE="FP1-2">(Lat 44°51′36″ N, long 94°22′57″ W)</FP>
                        <P>That airspace extending upward from 700 feet above the surface within a 6.4-mile radius of Hutchinson Municipal Airport/Butler Field.</P>
                        <STARS/>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Fort Worth, Texas, on January 3, 2024.</DATED>
                    <NAME>Martin A. Skinner,</NAME>
                    <TITLE>Acting Manager, Operations Support Group, ATO Central Service Center.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00195 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 71</CFR>
                <DEPDOC>[Docket No. FAA-2023-1006; Airspace Docket No. 22-AWP-65]</DEPDOC>
                <RIN>RIN 2120-AA66</RIN>
                <SUBJECT>Modification of Class E Airspace; Minden-Tahoe Airport, Minden, NV; Correction</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule; correction.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The FAA is correcting a final rule that published in the 
                        <E T="04">Federal Register</E>
                         on December 22, 2023. The final rule modified Class E airspace extending upward from 700 feet above the surface at Minden-Tahoe Airport, Minden, NV. This action corrects an error in the airspace legal description.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective 0901 UTC, March 21, 2024. The Director of the Federal Register approves this incorporation by reference action under 1 CFR part 51, subject to the annual revision of FAA Order 7400.11, Airspace Designations and Reporting Points, and publication of conforming amendments.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        FAA Order 7400.11H, and subsequent amendments, can be viewed online at 
                        <E T="03">www.faa.gov//air_traffic/publications/.</E>
                         You may also contact the Rules and Regulations Group, Office of Policy, Federal Aviation Administration, 800 Independence Avenue SW, Washington, DC 20591; telephone: (202) 267-8783.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Keith Adams, Federal Aviation Administration, Western Service Center, Operations Support Group, 2200 S 216th Street, Des Moines, WA 98198; telephone (206) 231-2428.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">History</HD>
                <P>
                    The FAA published a final rule in the 
                    <E T="04">Federal Register</E>
                     (88 FR 88528; December 22, 2023) for Docket FAA-2023-1006, which modified Class E airspace extending upward from 700 feet above the surface at the Minden-Tahoe Airport, Minden, NV. Subsequent to publication, the FAA identified that line one of the Class E airspace legal description contained the two-letter abbreviation for the state as “CA”, which was incorrect. The two-letter abbreviation of the state in line one of the legal description should be “NV”. This action corrects the error.
                </P>
                <HD SOURCE="HD1">Correction to the Final Rule</HD>
                <P>
                    In FR Doc 2023-28228 at 88529, published in the 
                    <E T="04">Federal Register</E>
                     on December 22, 2023, the FAA makes the following corrections:
                </P>
                <REGTEXT TITLE="14" PART="71">
                    <AMDPAR>1. On page 88529, in the second column, correct the first line of the legal description for E5 Minden, NV to read as follows:</AMDPAR>
                    <EXTRACT>
                        <HD SOURCE="HD1">AWP NV E5 Minden, NV [Corrected]</HD>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Des Moines, Washington, on January 5, 2024.</DATED>
                    <NAME>B.G. Chew,</NAME>
                    <TITLE>Group Manager, Western Service Center, Operations Support Group.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00352 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 71</CFR>
                <DEPDOC>[Docket No. FAA-2023-1338; Airspace Docket No. 22-AWP-86]</DEPDOC>
                <RIN>RIN 2120-AA66</RIN>
                <SUBJECT>Establishment of United States Area Navigation (RNAV) Route T-401 in the Vicinity of Paynesville, CA</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 establishes United States Area Navigation (RNAV) route T-401 in the vicinity of Paynesville, CA.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective date 0901 UTC, March 21, 2024. The Director of the Federal Register approves this incorporation by reference action under 1 CFR part 51, subject to the annual revision of FAA Order JO 7400.11 and publication of conforming amendments.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        A copy of the Notice of Proposed Rulemaking (NPRM), all comments received, 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.
                    </P>
                    <P>
                        FAA Order JO 7400.11H, Airspace Designations and Reporting Points, and subsequent amendments can be viewed online at 
                        <E T="03">www.faa.gov/air_traffic/publications/.</E>
                         You may also contact the Rules and Regulations Group, Office of Policy, Federal Aviation Administration, 800 Independence Avenue SW, Washington, DC 20591; telephone: (202) 267-8783.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Steven Roff, Rules and Regulations 
                        <PRTPAGE P="1794"/>
                        Group, Office of Policy, Federal Aviation Administration, 800 Independence Avenue SW, Washington, DC 20591; telephone: (202) 267-8783.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>The FAA's authority to issue rules regarding aviation safety is found in Title 49 of the United States Code. Subtitle I, Section 106 describes the authority of the FAA Administrator. Subtitle VII, Aviation Programs, describes in more detail the scope of the agency's authority. This rulemaking is promulgated under the authority described in Subtitle VII, Part A, Subpart I, Section 40103. Under that section, the FAA is charged with prescribing regulations to assign the use of 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 expands the availability of RNAV in California and improves the efficient flow of air traffic within the National Airspace System by lessening the dependency on ground-based navigation.</P>
                <HD SOURCE="HD1">History</HD>
                <P>
                    The FAA published a NPRM for Docket No. FAA-2023-1338 in the 
                    <E T="04">Federal Register</E>
                     (88 FR 39382; June 16, 2023), establishing RNAV route T-401 in the vicinity of Paynesville, CA. Interested parties were invited to participate in this rulemaking effort by submitting comments on the proposal. One comment was received in support of this action. The commentor stated “I support this action because establishing more low altitude airways within the NAS enhances the safety of general aviation pilots who would otherwise have to operate at higher altitudes off airways when IFR.”
                </P>
                <HD SOURCE="HD1">Differences From the NPRM</HD>
                <P>
                    The NPRM published for Docket No. FAA-2023-1338 in the 
                    <E T="04">Federal Register</E>
                     (88 FR 39382; June 16, 2023) contained an error in the table listing the route points that describe the airway. The table listed the route points in order of north to south, this rule corrects this error and lists the route points in order of south to north.
                </P>
                <HD SOURCE="HD1">Incorporation by Reference</HD>
                <P>
                    United States Area Navigation routes are published in paragraph 6011 of FAA Order JO 7400.11, Airspace Designations and Reporting Points, which is incorporated by reference in 14 CFR 71.1 on an annual basis. This document amends the current version of that order, FAA Order JO 7400.11H, dated August 11, 2023, and effective September 15, 2023. FAA Order JO 7400.11H is publicly available as listed in the 
                    <E T="02">ADDRESSES</E>
                     section of this document. These amendments will be published in the next update to FAA Order JO 7400.11.
                </P>
                <P>FAA Order JO 7400.11H lists Class A, B, C, D, and E airspace areas, air traffic service routes, and reporting points.</P>
                <HD SOURCE="HD1">The Rule</HD>
                <P>This action amends 14 CFR part 71 by establishing RNAV route T-401 in the vicinity of Paynesville, CA. The amendment is described below.</P>
                <P>
                    <E T="03">T-401:</E>
                     T-401 extends between EXTRA, CA, Fix and MARRI, CA, Fix.
                </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 Regulatory Policies and Procedures (44 FR 11034; February 26, 1979); and (3) does not warrant preparation of a regulatory evaluation as the anticipated impact is so minimal. Since this is a routine matter that only affects air traffic procedures and air navigation, it is certified 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 airspace action of establishing RNAV route T-401 in the vicinity of Paynesville, CA, qualifies for categorical exclusion under the National Environmental Policy Act (42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ) and its implementing regulations at 40 CFR part 1500, and in accordance with FAA Order 1050.1F, Environmental Impacts: Policies and Procedures, paragraph 5-6.5a, which categorically excludes from further environmental impact review rulemaking actions that designate or modify classes of airspace areas, airways, routes, and reporting points (see 14 CFR part 71, Designation of Class A, B, C, D, and E Airspace Areas; Air Traffic Service Routes; and Reporting Points), and paragraph 5-6.5i, which categorically excludes from further environmental review the establishment of new or revised air traffic control procedures conducted at 3,000 feet or more above ground level (AGL); procedures conducted below 3,000 feet AGL that do not cause traffic to be routinely routed over noise sensitive areas; modifications to currently approved procedures conducted below 3,000 feet AGL that do not significantly increase noise over noise sensitive areas; and increases in minimum altitudes and landing minima. As such, this action is not expected to result in any potentially significant environmental impacts. In accordance with FAA Order 1050.1F, paragraph 5-2 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. Accordingly, the FAA has determined that no extraordinary circumstances exist that warrant preparation of an environmental assessment or environmental impact study.
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 71</HD>
                    <P>Airspace, Incorporation by reference, Navigation (air).</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Amendment</HD>
                <P>In consideration of the foregoing, the Federal Aviation Administration amends 14 CFR part 71 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 71—DESIGNATION OF CLASS A, B, C, D, AND E AIRSPACE AREAS; AIR TRAFFIC SERVICE ROUTES; AND REPORTING POINTS</HD>
                </PART>
                <REGTEXT TITLE="14" PART="71">
                    <AMDPAR>1. The authority citation for 14 CFR part 71 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 49 U.S.C. 106(f), 106(g); 40103, 40113, 40120; E.O. 10854, 24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 71.1</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="14" PART="71">
                    <AMDPAR>2. The incorporation by reference in 14 CFR 71.1 of FAA Order JO 7400.11H, Airspace Designations and Reporting Points, dated August 11, 2023, and effective September 15, 2023, is amended as follows:</AMDPAR>
                    <EXTRACT>
                        <HD SOURCE="HD2">Paragraph 6011 United States Area Navigation Routes.</HD>
                        <STARS/>
                        <GPOTABLE COLS="3" OPTS="L0,tp0,p0,7/8,g1,t1,il" CDEF="xls75,xls50,xls180">
                            <TTITLE> </TTITLE>
                            <BOXHD>
                                <CHED H="1"> </CHED>
                                <CHED H="1"> </CHED>
                                <CHED H="1"> </CHED>
                            </BOXHD>
                            <ROW EXPSTB="02" RUL="s">
                                <ENT I="22">
                                    <E T="04">T-401 EXTRA, CA to MARRI, CA [New]</E>
                                </ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="01">EXTRA, CA</ENT>
                                <ENT>FIX</ENT>
                                <ENT>(Lat. 36°19′39.06″ N, long. 119°13′06.84″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">ALTTA, CA</ENT>
                                <ENT>FIX</ENT>
                                <ENT>(Lat. 36°33′08.91″ N, long. 119°19′36.45″ W)</ENT>
                            </ROW>
                            <ROW>
                                <PRTPAGE P="1795"/>
                                <ENT I="01">NOHIT, CA</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 37°08′36.00″ N, long. 119°23′02.00″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">BNAKI, CA</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 37°53′25.61″ N, long. 119°40′02.43″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">UNDRR, CA</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 38°05′31.13″ N, long. 119°45′59.22″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">OVRRR, CA</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 38°32′14.57″ N, long. 119°46′21.21″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">MARRI, CA</ENT>
                                <ENT>FIX</ENT>
                                <ENT>(Lat. 38°45′47.21″ N, long. 119°42′00.31″ W)</ENT>
                            </ROW>
                        </GPOTABLE>
                        <STARS/>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Washington, DC, on January 2, 2024.</DATED>
                    <NAME>Frank Lias,</NAME>
                    <TITLE>Manager, Airspace and Rules Group.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00069 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 71</CFR>
                <DEPDOC>[Docket No. FAA-2023-1528; Airspace Docket No. 23-ASW-9]</DEPDOC>
                <RIN>RIN 2120-AA66</RIN>
                <SUBJECT>Amendment of VOR Federal Airways V-20, V-222, V-289, V-552, V-569 and V-574, and Establishment of United States Area Navigation (RNAV) Routes T-483 and T-485 in the Vicinity of Beaumont, TX</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 Very High Frequency Omnidirectional Range (VOR) Federal airways V-20, V-222, V-289, V-552, V-569, and V-574, and establishes United States Area Navigation (RNAV) routes T-483 and T-485. The FAA is taking this action due to the planned decommissioning of the VOR portion of the Beaumont, TX (BPT), VOR/Distance Measuring Equipment (VOR/DME) navigational aid (NAVAID). The Beaumont VOR is being decommissioned in support of the FAA's VOR Minimum Operational Network (MON) program.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective date 0901 UTC, March 21, 2024. The Director of the Federal Register approves this incorporation by reference action under 1 CFR part 51, subject to the annual revision of FAA Order JO 7400.11 and publication of conforming amendments.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        A copy of the Notice of Proposed Rulemaking (NPRM), all comments received, 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.
                    </P>
                    <P>
                        FAA Order JO 7400.11H, Airspace Designations and Reporting Points, and subsequent amendments can be viewed online at 
                        <E T="03">www.faa.gov/air_traffic/publications/.</E>
                         You may also contact the Rules and Regulations Group, Office of Policy, Federal Aviation Administration, 800 Independence Avenue SW, Washington, DC 20591; telephone: (202) 267-8783.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Colby Abbott, Rules and Regulations Group, Office of Policy, Federal Aviation Administration, 800 Independence Avenue SW, Washington, DC 20591; telephone: (202) 267-8783.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>The FAA's authority to issue rules regarding aviation safety is found in Title 49 of the United States Code. Subtitle I, Section 106 describes the authority of the FAA Administrator. Subtitle VII, Aviation Programs, describes in more detail the scope of the agency's authority. This rulemaking is promulgated under the authority described in Subtitle VII, Part A, Subpart I, Section 40103. Under that section, the FAA is charged with prescribing regulations to assign the use of 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 modifies the Air Traffic Service (ATS) route structure as necessary to preserve the safe and efficient flow of air traffic within the National Airspace System.</P>
                <HD SOURCE="HD1">History</HD>
                <P>
                    The FAA published a notice of proposed rulemaking for Docket No. FAA-2023-1528 in the 
                    <E T="04">Federal Register</E>
                     (88 FR 44744; July 13, 2023), proposing to amend VOR Federal airways V-20, V-222, V-289, V-552, V-569, and V-574, and establish United States RNAV routes T-483 and T-485 due to the planned decommissioning of the VOR portion of the Beaumont, TX, VOR/DME NAVAID. Interested parties were invited to participate in this rulemaking effort by submitting written comments on the proposal. No comments were received.
                </P>
                <HD SOURCE="HD1">Incorporation by Reference</HD>
                <P>
                    VOR Federal airways are published in paragraph 6010(a) and United States Area Navigation Routes (T-routes) are published in paragraph 6011 of FAA Order JO 7400.11, Airspace Designations and Reporting Points, which is incorporated by reference in 14 CFR 71.1 on an annual basis. This document amends the current version of that order, FAA Order JO 7400.11H, dated August 11, 2023, and effective September 15, 2023. FAA Order JO 7400.11H is publicly available as listed in the 
                    <E T="02">ADDRESSES</E>
                     section of this document. These amendments will be published in the next update to FAA Order JO 7400.11.
                </P>
                <P>FAA Order JO 7400.11H lists Class A, B, C, D, and E airspace areas, air traffic service routes, and reporting points.</P>
                <HD SOURCE="HD1">The Rule</HD>
                <P>This action amends 14 CFR part 71 by amending VOR Federal airways V-20, V-222, V-289, V-552, V-569, and V-574, and establishing RNAV routes T-483 and T-485. The ATS route amendments and establishments are due to the planned decommissioning of the VOR portion of the Beaumont, TX, VOR/DME. The ATS route actions are described below.</P>
                <P>
                    <E T="03">V-20:</E>
                     Prior to this final rule, V-20 extended between the Mc Allen, TX, VOR/DME and the Palacios, TX, VOR/Tactical Air Navigation (VORTAC); between the Beaumont, TX, VOR/DME and the Montgomery, AL, VORTAC; and between the Athens, GA, VOR/DME and the Richmond, VA, VORTAC. The airspace on the main airway above 14,000 feet MSL from Mc Allen to 49 miles northeast and the airspace within Mexico was excluded. The airway segment between the Beaumont VOR/DME and the Lake Charles, LA, VORTAC is removed. Additionally, the exclusion for the airspace on the main airway above 14,000 feet MSL from Mc Allen to 49 miles northeast is also removed as it has not been required since the V-20 south alternate airway was removed in 1994 and there is no operational requirement to retain it. Further, the exclusion for the airspace within Mexico is removed as the airway does not extend into Mexico's airspace. As amended, the airway now extends between the Mc Allen VOR/DME and the Palacios VORTAC, between the Lake Charles VORTAC and the Montgomery VORTAC, and between the Athens VOR/DME and the Richmond VORTAC.
                </P>
                <P>
                    <E T="03">V-222:</E>
                     Prior to this final rule, V-222 extended between the El Paso, TX, VORTAC and the intersection of the LaGrange, GA, VORTAC 048° and Rome, GA, VORTAC 166° radials (TIROE fix). The airway segment between the Humble, TX, VORTAC and 
                    <PRTPAGE P="1796"/>
                    the Lake Charles, LA, VORTAC is removed. As amended, the airway now extends between the El Paso VORTAC and the Humble VORTAC and between the Lake Charles VORTAC and the intersection of the LaGrange VORTAC 048° and Rome VORTAC 166° radials (TIROE fix).
                </P>
                <P>
                    <E T="03">V-289:</E>
                     Prior to this final rule, V-289 extended between the Beaumont, TX, VOR/DME and the Vichy, MO, VOR/DME. The airway segment between the Beaumont VOR/DME and the Lufkin, TX, VORTAC is removed. As amended, the airway now extends between the Lufkin VORTAC and Vichy VOR/DME.
                </P>
                <P>
                    <E T="03">V-552:</E>
                     Prior to this final rule, V-552 extended between the Beaumont, TX, VOR/DME and the Monroeville, AL, VORTAC. The airspace within restricted area R-4403F was excluded during its times of use. The airway segment between the Beaumont VOR/DME and the Lake Charles, LA, VORTAC is removed. As amended, the airway now extends between the Lake Charles VORTAC and the Monroeville VORTAC.
                </P>
                <P>
                    <E T="03">V-569:</E>
                     Prior to this final rule, V-569 extended between the Beaumont, TX, VOR/DME and the Cedar Creek, TX, VORTAC. The airway segment between the Beaumont VOR/DME and the Lufkin, TX, VORTAC is removed. As amended, the airway now extends between the Lufkin VORTAC and the Cedar Creek VORTAC.
                </P>
                <P>
                    <E T="03">V-574:</E>
                     Prior to this final rule, V-574 extended between the Centex, TX, VORTAC and the Lake Charles, LA, VORTAC. The airway segment between the Daisetta, TX, VORTAC and the Lake Charles VORTAC is removed. As amended, the airway now extends between the Centex VORTAC and the Daisetta VORTAC.
                </P>
                <P>
                    <E T="03">T-483:</E>
                     T-483 is established as a RNAV route extending between the SHWNN, TX, waypoint (WP), located near the Beaumont, TX, VOR/DME and the Lufkin, TX, VORTAC. The new T-483 provides mitigation for the removal of the V-289 airway segment between the Beaumont VOR/DME and the Lufkin VORTAC. The full T-483 route description is listed in the amendments to part 71 as set forth below.
                </P>
                <P>
                    <E T="03">T-485:</E>
                     T-485 is established as a RNAV route extending between the SHWNN, TX, WP, located near the Beaumont, TX, VOR/DME and the Lufkin, TX (LFK), VORTAC. The new T-485 provides mitigation for the removal of the V-569 airway segment between the Beaumont VOR/DME and the Lufkin VORTAC. The full T-485 route description is listed in the amendments to part 71 as set forth below.
                </P>
                <P>The NAVAID radials listed in the VOR Federal airway descriptions in The Amendment section below are unchanged and stated in degrees True north.</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 Regulatory Policies and Procedures (44 FR 11034; February 26, 1979); and (3) does not warrant preparation of a regulatory evaluation as the anticipated impact is so minimal. Since this is a routine matter that only affects air traffic procedures and air navigation, it is certified 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 amending VOR Federal airways V-20, V-222, V-289, V-552, V-569, and V-574, and establishing RNAV routes T-483 and T-485, due to the planned decommissioning of the VOR portion of the Beaumont, TX, VOR/DME NAVAID, qualifies for categorical exclusion under the National Environmental Policy Act (42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ) and its implementing regulations at 40 CFR part 1500, and in accordance with FAA Order 1050.1F, Environmental Impacts: Policies and Procedures, paragraph 5-6.5a, which categorically excludes from further environmental impact review rulemaking actions that designate or modify classes of airspace areas, airways, routes, and reporting points (see 14 CFR part 71, Designation of Class A, B, C, D, and E Airspace Areas; Air Traffic Service Routes; and Reporting Points); and paragraph 5-6.5i, which categorically excludes from further environmental impact review the establishment of new or revised air traffic control procedures conducted at 3,000 feet or more above ground level (AGL); procedures conducted below 3,000 feet AGL that do not cause traffic to be routinely routed over noise sensitive areas; modifications to currently approved procedures conducted below 3,000 feet AGL that do not significantly increase noise over noise sensitive areas; and increases in minimum altitudes and landing minima. As such, this action is not expected to result in any potentially significant environmental impacts. In accordance with FAA Order 1050.1F, paragraph 5-2 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 study.
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 71</HD>
                    <P>Airspace, Incorporation by reference, Navigation (air).</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Amendment</HD>
                <P>In consideration of the foregoing, the Federal Aviation Administration amends 14 CFR part 71 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 71—DESIGNATION OF CLASS A, B, C, D, AND E AIRSPACE AREAS; AIR TRAFFIC SERVICE ROUTES; AND REPORTING POINTS</HD>
                </PART>
                <REGTEXT TITLE="14" PART="71">
                    <AMDPAR>1. The authority citation for 14 CFR part 71 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 49 U.S.C. 106(f), 106(g); 40103, 40113, 40120; E.O. 10854, 24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 71.1</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="14" PART="71">
                    <AMDPAR>2. The incorporation by reference in 14 CFR 71.1 of FAA Order JO 7400.11H, Airspace Designations and Reporting Points, dated August 11, 2023, and effective September 15, 2023, is amended as follows:</AMDPAR>
                    <EXTRACT>
                        <HD SOURCE="HD2">Paragraph 6010(a) Domestic VOR Federal Airways.</HD>
                        <STARS/>
                        <HD SOURCE="HD1">V-20 [Amended]</HD>
                        <P>From Mc Allen, TX; INT Mc Allen 038° and Corpus Christi, TX, 178° radials; 10 miles 8 miles wide, 37 miles 7 miles wide (3 miles E and 4 miles W of centerline), Corpus Christi; INT Corpus Christi 054° and Palacios, TX, 226° radials; to Palacios. From Lake Charles, LA; Lafayette, LA; Reserve, LA; INT Reserve 084° and Gulfport, MS, 247° radials; Gulfport; Semmes, AL; INT Semmes 048° and Monroeville, AL, 231° radials; Monroeville; to Montgomery, AL. From Athens, GA; Electric City, SC; Sugarloaf Mountain, NC; Barretts Mountain, NC; South Boston, VA; to Richmond, VA.</P>
                        <STARS/>
                        <HD SOURCE="HD1">V-222 [Amended]</HD>
                        <P>
                            From El Paso, TX; Salt Flat, TX; Fort Stockton, TX; 20 miles, 116 miles, 55 MSL, Junction, TX; Stonewall, TX; INT Stonewall 113° and Industry, TX, 267° radials; Industry; INT Industry 101° and Humble, TX, 259° radials; to Humble. From Lake Charles, LA; McComb, MS; Eaton, MS; Monroeville, AL; 
                            <PRTPAGE P="1797"/>
                            Montgomery, AL; LaGrange, GA; to INT LaGrange 048° and Rome, GA, 166° radials.
                        </P>
                        <STARS/>
                        <HD SOURCE="HD1">V-289 [Amended]</HD>
                        <P>From Lufkin, TX; Gregg County, TX; Texarkana, AR; Fort Smith, AR; Harrison, AR; Dogwood, MO; INT Dogwood 058° and Vichy, MO, 204° radials; to Vichy.</P>
                        <STARS/>
                        <HD SOURCE="HD1">V-552 [Amended]</HD>
                        <P>From Lake Charles, LA; INT Lake Charles 064° and Lafayette, LA, 281° radials; Lafayette; Tibby, LA; Harvey, LA; Picayune, MS; Semmes, AL; INT Semmes 063° and Monroeville, AL, 216° radials; to Monroeville. The airspace within restricted area R-4403F is excluded during its times of use.</P>
                        <STARS/>
                        <HD SOURCE="HD1">V-569 [Amended]</HD>
                        <P>From Lufkin, TX; Frankston, TX; to Cedar Creek, TX.</P>
                        <STARS/>
                        <HD SOURCE="HD1">V-574 [Amended]</HD>
                        <P>From Centex, TX; INT Centex 116° and Navasota, TX, 258° radials; Navasota; Humble, TX; to Daisetta, TX.</P>
                        <STARS/>
                        <HD SOURCE="HD2">Paragraph 6011 United States Area Navigation Routes.</HD>
                        <STARS/>
                        <GPOTABLE COLS="3" OPTS="L0,tp0,p0,7/8,g1,t1,i1" CDEF="xls100,xls50,xls180">
                            <TTITLE> </TTITLE>
                            <BOXHD>
                                <CHED H="1"> </CHED>
                                <CHED H="1"> </CHED>
                                <CHED H="1"> </CHED>
                            </BOXHD>
                            <ROW EXPSTB="02">
                                <ENT I="22">
                                    <E T="04">T-483 SHWNN, TX to Lufkin, TX (LFK) [New]</E>
                                </ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="01">SHWNN, TX</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 29°56′45.94″ N, long. 094°00′57.73″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">HONEE, TX</ENT>
                                <ENT>FIX</ENT>
                                <ENT>(Lat. 30°24′21.96″ N, long. 094°24′59.99″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Lufkin, TX (LFK)</ENT>
                                <ENT>VORTAC</ENT>
                                <ENT>(Lat. 31°09′44.79″ N, long. 094°43′00.60″ W)</ENT>
                            </ROW>
                        </GPOTABLE>
                        <STARS/>
                        <GPOTABLE COLS="3" OPTS="L0,tp0,p0,7/8,g1,t1,i1" CDEF="xls100,xls50,xls180">
                            <TTITLE> </TTITLE>
                            <BOXHD>
                                <CHED H="1"> </CHED>
                                <CHED H="1"> </CHED>
                                <CHED H="1"> </CHED>
                            </BOXHD>
                            <ROW EXPSTB="02">
                                <ENT I="22">
                                    <E T="04">T-485 SHWNN, TX to Lufkin, TX (LFK) [New]</E>
                                </ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="01">SHWNN, TX</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 29°56′45.94″ N, long. 094°00′57.73″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">ROMER, TX</ENT>
                                <ENT>FIX</ENT>
                                <ENT>(Lat. 30°44′47.33″ N, long. 094°23′33.01″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Lufkin, TX (LFK)</ENT>
                                <ENT>VORTAC</ENT>
                                <ENT>(Lat. 31°09′44.79″ N, long. 094°43′00.60″ W)</ENT>
                            </ROW>
                        </GPOTABLE>
                        <STARS/>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Washington, DC, on January 2, 2024.</DATED>
                    <NAME>Frank Lias,</NAME>
                    <TITLE>Manager, Rules and Regulations Group.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00150 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 71</CFR>
                <DEPDOC>[Docket No. FAA-2023-2365; Airspace Docket No. 23-ACE-7]</DEPDOC>
                <RIN>RIN 2120-AA66</RIN>
                <SUBJECT>Amendment of United States RNAV Route T-251 in the Vicinity of Bowling Green, MO</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 United States (U.S.) Area Navigation (RNAV) route T-251 Part 71 description. The FAA is changing the type of point for the RIVRS, IL, route point from being listed as a “Fix” to a “Waypoint (WP)” to match the FAA National Airspace System Resource (NASR) database information. This is an editorial amendment only and does not alter the alignment, dimensions, or operating requirements of T-251.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective date 0901 UTC, March 21, 2024. The Director of the Federal Register approves this incorporation by reference action under 1 CFR part 51, subject to the annual revision of FAA Order JO 7400.11 and publication of conforming amendments.</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.
                    </P>
                    <P>
                        FAA Order JO 7400.11H, Airspace Designations and Reporting Points, and subsequent amendments can be viewed online at 
                        <E T="03">www.faa.gov/air_traffic/publications/.</E>
                         You may also contact the Rules and Regulations Group, Office of Policy, Federal Aviation Administration, 800 Independence Avenue SW, Washington, DC 20591; telephone: (202) 267-8783.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Colby Abbott, Rules and Regulations Group, Office of Policy, Federal Aviation Administration, 800 Independence Avenue SW, Washington, DC 20591; telephone: (202) 267-8783.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>The FAA's authority to issue rules regarding aviation safety is found in Title 49 of the United States Code. Subtitle I, Section 106 describes the authority of the FAA Administrator. Subtitle VII, Aviation Programs, describes in more detail the scope of the agency's authority. This rulemaking is promulgated under the authority described in Subtitle VII, Part A, Subpart I, Section 40103. Under that section, the FAA is charged with prescribing regulations to assign the use of 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 modifies the Air Traffic Service (ATS) route structure as necessary to preserve the safe and efficient flow of air traffic within the National Airspace System.</P>
                <HD SOURCE="HD1">History</HD>
                <P>On June 15, 2023, the FAA decommissioned the Quincy, IL, Very High Frequency Omnidirectional Range (VOR) as part of the VOR Minimum Operational Network (MON) Program. As a result of the Quincy VOR being decommissioned, the RIVRS, IL, Fix was changed in the FAA NASR database to a WP and on all associated Instrument Flight Rules (IFR) enroute, Visual Flight Rules (VFR) sectional, and controller charts. The Part 71 editorial amendment of the T-251 description was overlooked at that time and the RIVRS, IL, route point is still reflected as a Fix. The correct type of point for the RIVRS, IL, route point is WP. This rule corrects that difference by changing the type of point for the RIVRS, IL, route point listed in the T-251 route description from “Fix” to “WP.”</P>
                <HD SOURCE="HD1">Incorporation by Reference</HD>
                <P>
                    United States Area Navigation Routes (T-routes) are published in paragraph 6011 of FAA Order JO 7400.11, Airspace Designations and Reporting Points, which is incorporated by reference in 14 CFR 71.1 on an annual basis. This document amends the current version of that order, FAA Order JO 7400.11H, dated August 11, 2023, and effective 
                    <PRTPAGE P="1798"/>
                    September 15, 2023. FAA Order JO 7400.11H is publicly available as listed in the 
                    <E T="02">ADDRESSES</E>
                     section of this document. These amendments will be published in the next update to FAA Order JO 7400.11.
                </P>
                <P>FAA Order JO 7400.11H lists Class A, B, C, D, and E airspace areas, air traffic service routes, and reporting points.</P>
                <HD SOURCE="HD1">The Rule</HD>
                <P>This action amends 14 CFR part 71 by amending U.S. RNAV route T-251 to change the type of point of the RIVRS, IL, route point from “Fix” to “WP.” This change to the T-251 description will match the FAA NASR database information and charted depiction of the point.</P>
                <P>Since this action merely involves an editorial amendment in the Part 71 description of U.S. RNAV route T-251, and does not involve a change in the alignment, dimensions, or operating requirements of that route, 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 Regulatory Policies and Procedures (44 FR 11034; February 26, 1979); and (3) does not warrant preparation of a regulatory evaluation as the anticipated impact is so minimal. Since this is a routine matter that only affects air traffic procedures and air navigation, it is certified 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 editorial amendment action of U.S. RNAV route T-251, to reflect the RIVRS, IL, route point as a WP and match the FAA NASR database information and charts, qualifies for categorical exclusion under the National Environmental Policy Act (42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ) and its implementing regulations at 40 CFR part 1500, and in accordance with FAA Order 1050.1F, Environmental Impacts: Policies and Procedures, paragraph 5-6.5a, which categorically excludes from full environmental impact review rulemaking actions that designate or modify classes of airspace areas, airways, routes, and reporting points; and paragraph 5-6.5k, which categorically excludes from further environmental impact review publication of existing air traffic control procedures that do not essentially change existing tracks, create new tracks, change altitudes, or change concentration of aircraft on these tracks. As such, this action is not expected to result in any potentially significant environmental impacts. In accordance with FAA Order 1050.1F, paragraph 5-2 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 study.
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 71</HD>
                    <P>Airspace, Incorporation by reference, Navigation (air).</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Amendment</HD>
                <P>In consideration of the foregoing, the Federal Aviation Administration amends 14 CFR part 71 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 71—DESIGNATION OF CLASS A, B, C, D, AND E AIRSPACE AREAS; AIR TRAFFIC SERVICE ROUTES; AND REPORTING POINTS</HD>
                </PART>
                <REGTEXT TITLE="14" PART="71">
                    <AMDPAR>1. The authority citation for 14 CFR part 71 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 49 U.S.C. 106(f), 106(g); 40103, 40113, 40120; E.O. 10854, 24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 71.1</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="14" PART="71">
                    <AMDPAR>2. The incorporation by reference in 14 CFR 71.1 of FAA Order JO 7400.11H, Airspace Designations and Reporting Points, dated August 11, 2023, and effective September 15, 2023, is amended as follows:</AMDPAR>
                    <EXTRACT>
                        <HD SOURCE="HD2">Paragraph 6011 United States Area Navigation Routes.</HD>
                        <STARS/>
                        <GPOTABLE COLS="3" OPTS="L0,tp0,p0,7/8,g1,t1,i1" CDEF="xls100,xls50,xls180">
                            <TTITLE> </TTITLE>
                            <BOXHD>
                                <CHED H="1"> </CHED>
                                <CHED H="1"> </CHED>
                                <CHED H="1"> </CHED>
                            </BOXHD>
                            <ROW EXPSTB="02">
                                <ENT I="22">
                                    <E T="04">T-251 FRNIA, MO to KOETZ, WI [Amended]</E>
                                </ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="01">FRNIA, MO</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 36°33′18.69″ N, long. 089°54′40.47″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Farmington, MO (FAM)</ENT>
                                <ENT>VORTAC</ENT>
                                <ENT>(Lat. 37°40′24.46″ N, long. 090°14′02.62″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Foristell, MO (FTZ)</ENT>
                                <ENT>VORTAC</ENT>
                                <ENT>(Lat. 38°41′39.60″ N, long. 090°58′16.57″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">RIVRS, IL</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 39°25′21.41″ N, long. 090°55′56.70″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">KAYUU, MO</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 40°19′05.81″ N, long. 091°41′36.59″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">MERKR, IA</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 40°49′16.02″ N, long. 092°08′26.88″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">AGENS, IA</ENT>
                                <ENT>FIX</ENT>
                                <ENT>(Lat. 41°01′43.78″ N, long. 092°20′50.25″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">PICRA, IA</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 41°35′00.72″ N, long. 092°32′34.29″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">HAVOS, IA</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 42°04′16.32″ N, long. 092°28′29.38″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Waterloo, IA (ALO)</ENT>
                                <ENT>VOR/DME</ENT>
                                <ENT>(Lat. 42°33′23.39″ N, long. 092°23′56.13″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">ZEZDU, IA</ENT>
                                <ENT>FIX</ENT>
                                <ENT>(Lat. 42°49′29.02″ N, long. 092°04′58.05″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">FALAR, MN</ENT>
                                <ENT>FIX</ENT>
                                <ENT>(Lat. 43°34′26.04″ N, long. 091°30′18.32″ W)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">KOETZ, WI</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 44°13′15.00″ N, long. 091°28′14.00″ W)</ENT>
                            </ROW>
                        </GPOTABLE>
                        <STARS/>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Washington, DC, on January 2, 2024.</DATED>
                    <NAME>Frank Lias,</NAME>
                    <TITLE>Manager, Rules and Regulations Group.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00072 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <PRTPAGE P="1799"/>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 71</CFR>
                <DEPDOC>[Docket No. FAA-2023-2115; Airspace Docket No. 23-ASO-40]</DEPDOC>
                <RIN>RIN 2120-AA66</RIN>
                <SUBJECT>Amendment of Class E Airspace; Natchez, MS</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 Class E airspace at Natchez, MS. This action is the result of an airspace review conducted due to the decommissioning of the Natchez very high frequency omnidirectional range (VOR) as part of the VOR Minimum Operating Network (MON) Program. The name and geographic coordinates of the airport are also being updated to coincide with the FAA's aeronautical database. This action brings the airspace into compliance with FAA orders to support instrument flight rule (IFR) operations.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective 0901 UTC, March 21, 2024. The Director of the Federal Register approves this incorporation by reference action under 1 CFR part 51, subject to the annual revision of FAA Order JO 7400.11 and publication of conforming amendments.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        A copy of the Notice of Proposed Rulemaking (NPRM), all comments received, 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.
                    </P>
                    <P>
                        FAA Order JO 7400.11H, Airspace Designations and Reporting Points, and subsequent amendments can be viewed online at 
                        <E T="03">www.faa.gov/air_traffic/publications/.</E>
                         You may also contact the Rules and Regulations Group, Office of Policy, Federal Aviation Administration, 800 Independence Avenue SW, Washington, DC 20591; telephone: (202) 267-8783.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Jeffrey Claypool, Federal Aviation Administration, Operations Support Group, Central Service Center, 10101 Hillwood Parkway, Fort Worth, TX 76177; telephone (817) 222-5711.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>The FAA's authority to issue rules regarding aviation safety is found in Title 49 of the United States Code. Subtitle I, Section 106 describes the authority of the FAA Administrator. Subtitle VII, Aviation Programs, describes in more detail the scope of the agency's authority. This rulemaking is promulgated under the authority described in Subtitle VII, Part A, Subpart I, Section 40103. Under that section, the FAA is charged with prescribing regulations to assign the use of airspace necessary to ensure the safety of aircraft and the efficient use of airspace. This regulation is within the scope of that authority as it amends the Class E airspace extending upward from 700 feet above the surface at Hardy-Anders Field/Natchez-Adams County Airport, Natchez, MS, to support IFR operations at this airport.</P>
                <HD SOURCE="HD1">History</HD>
                <P>
                    The FAA published an NPRM for Docket No. FAA-2023-2115 in the 
                    <E T="04">Federal Register</E>
                     (88 FR 76150; November 6, 2023) proposing to amend the Class E airspace at Natchez, MS. Interested parties were invited to participate in this rulemaking effort by submitting written comments on the proposal to the FAA. No comments were received.
                </P>
                <HD SOURCE="HD1">Incorporation by Reference</HD>
                <P>
                    Class E airspace designations are published in paragraph 6005 of FAA Order JO 7400.11, Airspace Designations and Reporting Points, which is incorporated by reference in 14 CFR 71.1 on an annual basis. This document amends the current version of that order, FAA Order JO 7400.11H, dated August 11, 2023, and effective September 15, 2023. FAA Order JO 7400.11H is publicly available as listed in the 
                    <E T="02">ADDRESSES</E>
                     section of this document. These amendments will be published in the next update to FAA Order JO 7400.11.
                </P>
                <P>FAA Order JO 7400.11H lists Class A, B, C, D, and E airspace areas, air traffic service routes, and reporting points.</P>
                <HD SOURCE="HD1">Differences From the NPRM</HD>
                <P>The NPRM stated that the geographic coordinates of the airport would be updated, however that update was omitted. The geographic coordinates are updated in this action.</P>
                <HD SOURCE="HD1">The Rule</HD>
                <P>This amendment to 14 CFR part 71 modifies the Class E airspace extending upward from 700 feet above the surface to within a 6.6-mile (decreased from a 7-mile) radius of Hardy-Anders Field/Natchez-Adams County Airport, Natchez, MS; updates the name (previously Hardy-Anders Field Natchez-Adams County Airport) and geographic coordinates of the airport to coincide with the FAA's aeronautical database; and removes the city associated with the airport from the header to comply with changes to FAA Order JO 7400.2P, Procedures for Handling Airspace Matters.</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 Regulatory Policies and Procedures (44 FR 11034; February 26, 1979); and (3) does not warrant preparation of a regulatory evaluation as the anticipated impact is so minimal. Since this is a routine matter that only affects air traffic procedures and air navigation, it is certified 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 qualifies for categorical exclusion under the National Environmental Policy Act in accordance with FAA Order 1050.1F, “Environmental Impacts: Policies and Procedures,” paragraph 5-6.5.a. This airspace action is not expected to cause any potentially significant environmental impacts, and no extraordinary circumstances exist that warrant preparation of an environmental assessment.</P>
                <LSTSUB>
                    <HD SOURCE="HED">Lists of Subjects in 14 CFR 71</HD>
                    <P>Airspace, Incorporation by reference, Navigation (air).</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Amendment</HD>
                <P>In consideration of the foregoing, the Federal Aviation Administration amends 14 CFR part 71 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 71—DESIGNATION OF CLASS A, B, C, D, AND E AIRSPACE AREAS; AIR TRAFFIC SERVICE ROUTES; AND REPORTING POINTS</HD>
                </PART>
                <REGTEXT TITLE="14" PART="71">
                    <AMDPAR>1. The authority citation for 14 CFR part 71 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 49 U.S.C. 106(f), 106(g); 40103, 40113, 40120; E.O. 10854, 24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 71.1</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="14" PART="71">
                    <AMDPAR>
                        2. The incorporation by reference in 14 CFR 71.1 of FAA Order JO 7400.11H, Airspace Designations and Reporting 
                        <PRTPAGE P="1800"/>
                        Points, dated August 11, 2023, and effective September 15, 2023, is amended as follows:
                    </AMDPAR>
                    <EXTRACT>
                        <HD SOURCE="HD2">Paragraph 6005 Class E Airspace Areas Extending Upward From 700 Feet or More Above the Surface of the Earth.</HD>
                        <STARS/>
                        <HD SOURCE="HD1">ASO MS E5 Natchez, MS [Amended]</HD>
                        <FP SOURCE="FP-2">Hardy-Anders Field/Natchez-Adams County Airport, MS</FP>
                        <FP SOURCE="FP1-2">(Lat 31°36′49″ N, long 91°17′50″ W)</FP>
                        <P>That airspace extending upward from 700 feet above the surface within a 6.6-mile radius of Hardy-Anders Field/Natchez-Adams County Airport.</P>
                    </EXTRACT>
                    <STARS/>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Fort Worth, Texas, on January 8, 2024.</DATED>
                    <NAME>Martin A. Skinner,</NAME>
                    <TITLE>Acting Manager, Operations Support Group, ATO Central Service Center.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00399 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 71</CFR>
                <DEPDOC>[Docket No. FAA-2023-1352; Airspace Docket No. 23-ASO-55]</DEPDOC>
                <RIN>RIN 2120-AA66</RIN>
                <SUBJECT>Amendment of Class D and Class E Airspace; Ozark, AL and Columbus, GA; Correction</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule; correction.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The FAA is correcting a final rule that published in the 
                        <E T="04">Federal Register</E>
                         on December 12, 2023. The final rule amended Class D and Class E surface airspace for Fort Novosel, Ozark, AL, and Fort Moore, Columbus, GA. This action corrects errors in the Class E legal descriptions for both Air Fields.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective 0901 UTC, March 21, 2024. The Director of the Federal Register approves this incorporation by reference action under 1 CFR part 51, subject to the annual revision of FAA Order JO 7400.11 and publication of conforming amendments.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        FAA Order JO 7400.11H, Airspace Designations and Reporting Points, and subsequent amendments can be viewed online at 
                        <E T="03">https://www.faa.gov/air_traffic/publications/.</E>
                         For further information, you can contact the Rules and Regulations Group, Federal Aviation Administration, 800 Independence Avenue SW, Washington, DC 20591; telephone: (202) 267-8783.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>John Fornito, Operations Support Group, Eastern Service Center, Federal Aviation Administration, 1701 Columbia Avenue, College Park, GA 30337; telephone: (404) 305-6364.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">History</HD>
                <P>
                    The FAA published a final rule in the 
                    <E T="04">Federal Register</E>
                     on December 12, 2023 (88 FR 86039), for Docket No. FAA-2023-1352, updating the Class D airspace and Class E airspace for Fort Novosel, Ozark, AL, and Fort Moore, Columbus, GA, by updating each airport's name and replacing Notice to Airmen with Notice to Air Missions, and replacing the term Airport/Facility Directory with Chart Supplement in the appropriate descriptions. After publication, the FAA found the Class E surface description for Fort Novosel was inadvertently transposed. Also, the Class E airspace extending upward from 700 feet above the surface for Columbus, GA, was incorrectly transposed with the Columbus, MS description. This action corrects these errors.
                </P>
                <HD SOURCE="HD1">Correction to the Final Rule</HD>
                <P>
                    In FR Doc 2023-27195 at 86039, published in the 
                    <E T="04">Federal Register</E>
                     on December 12, 2023, the FAA makes the following corrections:
                </P>
                <REGTEXT TITLE="14" PART="71">
                    <AMDPAR>1. On page 86040, in the first column, correct the ASO AL E2 description for Fort Novosel (Ozark), AL, to read as follows:</AMDPAR>
                    <EXTRACT>
                        <HD SOURCE="HD1">ASO AL E2 Fort Novosel (Ozark), AL [Corrected]</HD>
                        <FP SOURCE="FP-2">Cairns Army Air Field (Fort Novosel), AL</FP>
                        <FP SOURCE="FP1-2">(Lat. 31°16′33″ N, long 85°42′48″ W)</FP>
                        <P>That airspace extending upward from the surface within a 5-mile radius of lat. 31°18′30″ N, long. 85°42′20″ W. This Class E airspace area is effective during the specific dates and times established in advance by a Notice to Air Missions. The effective date and time will thereafter be continuously published in the Chart Supplement.</P>
                    </EXTRACT>
                </REGTEXT>
                <REGTEXT TITLE="14" PART="71">
                    <AMDPAR>2. On page 86040, beginning in the first column under Paragraph 6005 Class E Airspace Areas Extending Upward From 700 Feet or More Above the Surface of the Earth, correct the Class E Airspace Areas description to read as follows:</AMDPAR>
                    <EXTRACT>
                        <HD SOURCE="HD2">Paragraph 6005 Class E Airspace Areas Extending Upward From 700 Feet or More Above the Surface of the Earth [Corrected]</HD>
                        <STARS/>
                        <HD SOURCE="HD1">ASO GA E5 Columbus, GA [Amended]</HD>
                        <FP SOURCE="FP-2">Columbus Airport, GA</FP>
                        <FP SOURCE="FP1-2">(Lat. 32°30′59″ N, long 84°56′20″ W)</FP>
                        <FP SOURCE="FP-2">Lawson AAF (Fort Moore), GA</FP>
                        <FP SOURCE="FP1-2">(Lat. 32°19′54″ N, long 84°59′14″ W)</FP>
                        <P>That airspace extending upward from 700 feet above the surface within a 9.6-mile radius of Columbus Airport, within a 9.3-mile radius of Lawson AAF (Fort Moore), and 3.8 miles each side of Lawson AAF (Fort Moore) 341° bearing from the AAF extending from the 9.3-mile radius to 15.2 miles northwest of the AAF, and 4.1 miles each side of the Lawson AAF (Fort Moore) 145° bearing from the AAF extending from the 9.3-mile radius to 10.6 miles southeast of the AAF.</P>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in College Park, Georgia, on December 19, 2023.</DATED>
                    <NAME>Andreese C. Davis,</NAME>
                    <TITLE>Manager, Airspace &amp; Procedures Team South, Eastern Service Center, Air Traffic Organization.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2023-28314 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 71</CFR>
                <DEPDOC>[Docket No. FAA-2023-2113; Airspace Docket No. 23-AGL-28]</DEPDOC>
                <RIN>RIN 2120-AA66</RIN>
                <SUBJECT>Amendment of Class E Airspace; Jackson, OH</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 Class E airspace at Jackson, OH. This action is the result of an airspace review conducted due to the decommissioning of the York very high frequency omnidirectional range (VOR) as part of the VOR Minimum Operating Network (MON) Program. The geographic coordinates of the airport are also being updated to coincide with the FAA's aeronautical database. This action brings the airspace into compliance with FAA orders to support instrument flight rule (IFR) operations.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective 0901 UTC, March 21, 2024. The Director of the Federal Register approves this incorporation by reference action under 1 CFR part 51, subject to the annual revision of FAA Order JO 7400.11 and publication of conforming amendments.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        A copy of the Notice of Proposed Rulemaking (NPRM), all comments received, 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.
                    </P>
                    <P>
                        FAA Order JO 7400.11H, Airspace Designations and Reporting Points, and 
                        <PRTPAGE P="1801"/>
                        subsequent amendments can be viewed online at 
                        <E T="03">www.faa.gov/air_traffic/publications/.</E>
                         You may also contact the Rules and Regulations Group, Office of Policy, Federal Aviation Administration, 800 Independence Avenue SW, Washington, DC 20591; telephone: (202) 267-8783.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Jeffrey Claypool, Federal Aviation Administration, Operations Support Group, Central Service Center, 10101 Hillwood Parkway, Fort Worth, TX 76177; telephone (817) 222-5711.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>The FAA's authority to issue rules regarding aviation safety is found in Title 49 of the United States Code. Subtitle I, Section 106 describes the authority of the FAA Administrator. Subtitle VII, Aviation Programs, describes in more detail the scope of the agency's authority. This rulemaking is promulgated under the authority described in Subtitle VII, Part A, Subpart I, Section 40103. Under that section, the FAA is charged with prescribing regulations to assign the use of airspace necessary to ensure the safety of aircraft and the efficient use of airspace. This regulation is within the scope of that authority as it amends the Class E airspace extending upward from 700 feet above the surface at James A. Rhodes Airport, Jackson, OH, to support IFR operations at this airport.</P>
                <HD SOURCE="HD1">History</HD>
                <P>
                    The FAA published an NPRM for Docket No. FAA-2023-2113 in the 
                    <E T="04">Federal Register</E>
                     (88 FR 76158; November 6, 2023) proposing to amend the Class E airspace at Jackson, OH. Interested parties were invited to participate in this rulemaking effort by submitting written comments on the proposal to the FAA. No comments were received.
                </P>
                <HD SOURCE="HD1">Incorporation by Reference</HD>
                <P>
                    Class E airspace designations are published in paragraph 6005 of FAA Order JO 7400.11, Airspace Designations and Reporting Points, which is incorporated by reference in 14 CFR 71.1 on an annual basis. This document amends the current version of that order, FAA Order JO 7400.11H, dated August 11, 2023, and effective September 15, 2023. FAA Order JO 7400.11H is publicly available as listed in the 
                    <E T="02">ADDRESSES</E>
                     section of this document. These amendments will be published in the next update to FAA Order JO 7400.11.
                </P>
                <P>FAA Order JO 7400.11H lists Class A, B, C, D, and E airspace areas, air traffic service routes, and reporting points.</P>
                <HD SOURCE="HD1">The Rule</HD>
                <P>This amendment to 14 CFR part 71 modifies the Class E airspace extending upward from 700 feet above the surface to within a 6.8-mile (decreased from a 7.5-mile) radius of James A. Rhodes Airport, Jackson, OH; updates the geographic coordinates of airport to coincide with the FAA's aeronautical database; and removes the city associated with the airport from the header to comply with changes to FAA Order JO 7400.2P, Procedures for Handling Airspace Matters.</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 Regulatory Policies and Procedures (44 FR 11034; February 26, 1979); and (3) does not warrant preparation of a regulatory evaluation as the anticipated impact is so minimal. Since this is a routine matter that only affects air traffic procedures and air navigation, it is certified 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 qualifies for categorical exclusion under the National Environmental Policy Act in accordance with FAA Order 1050.1F, “Environmental Impacts: Policies and Procedures,” paragraph 5-6.5.a. This airspace action is not expected to cause any potentially significant environmental impacts, and no extraordinary circumstances exist that warrant preparation of an environmental assessment.</P>
                <LSTSUB>
                    <HD SOURCE="HED">Lists of Subjects in 14 CFR 71</HD>
                    <P>Airspace, Incorporation by reference, Navigation (air).</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Amendment</HD>
                <P>In consideration of the foregoing, the Federal Aviation Administration amends 14 CFR part 71 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 71—DESIGNATION OF CLASS A, B, C, D, AND E AIRSPACE AREAS; AIR TRAFFIC SERVICE ROUTES; AND REPORTING POINTS</HD>
                </PART>
                <REGTEXT TITLE="14" PART="71">
                    <AMDPAR>1. The authority citation for 14 CFR part 71 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 49 U.S.C. 106(f), 106(g); 40103, 40113, 40120; E.O. 10854, 24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 71.1</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="14" PART="71">
                    <AMDPAR>2. The incorporation by reference in 14 CFR 71.1 of FAA Order JO 7400.11H, Airspace Designations and Reporting Points, dated August 11, 2023, and effective September 15, 2023, is amended as follows:</AMDPAR>
                    <EXTRACT>
                        <HD SOURCE="HD2">Paragraph 6005 Class E Airspace Areas Extending Upward From 700 Feet or More Above the Surface of the Earth.</HD>
                        <STARS/>
                        <HD SOURCE="HD1">AGL OH E5 Jackson, OH [Amended]</HD>
                        <FP SOURCE="FP-2">James A. Rhodes Airport, OH</FP>
                        <FP SOURCE="FP1-2">(Lat 38°58′53″ N, long 82°34′40″ W)</FP>
                        <P>That airspace extending upward from 700 feet above the surface within a 6.8-mile radius of the James A. Rhodes Airport.</P>
                        <STARS/>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Fort Worth, Texas, on January 3, 2024.</DATED>
                    <NAME>Martin A. Skinner,</NAME>
                    <TITLE>Acting Manager, Operations Support Group, ATO Central Service Center.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00197 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 71</CFR>
                <DEPDOC>[Docket No. FAA-2023-2453; Airspace Docket No. 22-ANM-57]</DEPDOC>
                <RIN>RIN 2120-AA66</RIN>
                <SUBJECT>Amendment of Very High Frequency Omnidirectional Range Federal Airway V-4 in the Vicinity of Burley, ID</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 Very High Frequency Omnidirectional Range (VOR) Federal Airway V-4 in the vicinity of Burley, ID. The FAA is taking this action to update one of the radials used in the airway description.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Effective date 0901 UTC, March 21, 2024. The Director of the Federal Register approves this incorporation by reference action under 1 CFR part 51, subject to the annual revision of FAA 
                        <PRTPAGE P="1802"/>
                        Order JO 7400.11 and publication of conforming amendments.
                    </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        FAA Order JO 7400.11H, Airspace Designations and Reporting Points, and subsequent amendments can be viewed online at 
                        <E T="03">www.faa.gov/air_traffic/publications/.</E>
                         You may also contact the Rules and Regulations Group, Office of Policy, Federal Aviation Administration, 800 Independence Avenue SW, Washington, DC 20591; telephone: (202) 267-8783.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Steven Roff, Rules and Regulations Group, Office of Policy, Federal Aviation Administration, 800 Independence Avenue SW, Washington, DC 20591; telephone: (202) 267-8783.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>The FAA's authority to issue rules regarding aviation safety is found in Title 49 of the United States Code. Subtitle I, Section 106 describes the authority of the FAA Administrator. Subtitle VII, Aviation Programs, describes in more detail the scope of the agency's authority. This rulemaking is promulgated under the authority described in Subtitle VII, Part A, Subpart I, Section 40103. Under that section, the FAA is charged with prescribing regulations to assign the use of 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 would modify the route structure as necessary to preserve the safe and efficient flow of air traffic within the National Airspace System (NAS).</P>
                <HD SOURCE="HD1">Incorporation by Reference</HD>
                <P>
                    VOR Federal Airways are published in paragraph 6010 of FAA Order JO 7400.11, Airspace Designations and Reporting Points, which is incorporated by reference in 14 CFR 71.1 on an annual basis. This document amends the current version of that order, FAA Order JO 7400.11H, dated August 11, 2023, and effective September 15, 2023. These updates will be published in the next update to FAA Order JO 7400.11. That order is publicly available as listed in the 
                    <E T="02">ADDRESSES</E>
                     section of this document.
                </P>
                <P>FAA Order JO 7400.11H lists Class A, B, C, D, and E airspace areas, air traffic service routes, and reporting points.</P>
                <HD SOURCE="HD1">The Rule</HD>
                <P>This action amends 14 CFR part 71 by amending VOR Federal Airway V-4 in the vicinity of Burley, ID. The FAA is taking this action to update one of the radials used in the airway description. During a review of VOR Federal Airway V-4, the FAA discovered that V-4 was established without the accuracy of the Terminal Area Route Generation and Traffic Simulation software tool used today. Because of this, there is a one-degree discrepancy in the airway description. The current airway description for V-4 includes the intersection of the Boise, ID, Very High Frequency Omnidirectional Range/Tactical Air Navigation (VORTAC) 130° and the Burley, ID, Very High Frequency Omnidirectional Range/Distance Measuring Equipment (VOR/DME) 292° radials (ALKAL, Fix). However, the ALKAL Fix has been reviewed and is located at the intersection of the Boise VORTAC 130° and the Burley VOR/DME 293° radials. This action corrects the Burley VOR/DME radial used for defining the ALKAL Fix. The amendment is described below.</P>
                <P>
                    <E T="03">V-4:</E>
                     V-4 currently extends between the Tatoosh, WA, VORTAC and the Armel, VA, VOR/DME and includes the intersection of the INT Boise 130° and Burley, ID, 292° radials (ALKAL, Fix). This rule changes the component radials that makeup the ALKAL Fix to the intersection of the Boise VORTAC 130° and Burley VOR/DME 293° radials.
                </P>
                <P>The radials in the V-4 airway description are listed in degrees True north.</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 Regulatory Policies and Procedures (44 FR 11034; February 26, 1979); and (3) does not warrant preparation of a regulatory evaluation as the anticipated impact is so minimal. Since this is a routine matter that only affects air traffic procedures and air navigation, it is certified 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 amending Federal Airway V-4 in the vicinity of Burley, ID qualifies for categorical exclusion under the National Environmental Policy Act (42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ) and its implementing regulations at 40 CFR part 1500, and in accordance with FAA Order 1050,1F, Environmental Impacts: Policies and Procedures, paragraph 5-6-5a, which categorically excludes from further environmental impact review rulemaking actions that designate or modify classes of airspace areas, airways, routes, and reporting points (see 14 CFR part 71, Designation of Class A, B, C, D and E Airspace Areas; Air Traffic Service Routes; and Reporting Points); and paragraph 5-6.5.k., which categorically excludes from further environmental review the publication of existing air traffic control procedures that do not essentially change existing tracks, create new tracks, change altitude, or change concentration of aircraft on these tracks. As such, this action is not expected to result in in any potentially significant environmental impacts. In accordance with FAA Order 1050.1f, paragraph 5-2 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. Accordingly, the FAA has determined that no extraordinary circumstances exist that warrant prepared of an environmental impact statement.
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">Lists of Subjects in 14 CFR Part 71</HD>
                    <P>Airspace, Incorporation by reference, Navigation (air).</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Amendment</HD>
                <P>In consideration of the foregoing, the Federal Aviation Administration amends 14 CFR part 71 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 71—DESIGNATION OF CLASS A, B, C, D, AND E AIRSPACE AREAS; AIR TRAFFIC SERVICE ROUTES; AND REPORTING POINTS</HD>
                </PART>
                <REGTEXT TITLE="14" PART="71">
                    <AMDPAR>1. The authority citation for 14 CFR part 71 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 49 U.S.C. 106(f), 106(g), 40103, 40113, 40120; E.O. 10854, 24 FR 9565, 3 CFR, 1959-1963 Comp., p.389.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 71.1</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="14" PART="71">
                    <AMDPAR>2. The incorporation by reference in 14 CFR 71.1 of FAA Order JO 7400.11H, Airspace Designations and Reporting Points, dated August 11, 2023, and effective September 15, 2023, is amended as follows:</AMDPAR>
                    <EXTRACT>
                        <HD SOURCE="HD2">Paragraph 6010(a) Domestic VOR Federal Airways</HD>
                        <STARS/>
                        <HD SOURCE="HD1">V-4 [Amended]</HD>
                        <P>
                            From Tatoosh, WA; INT of Tatoosh 102° and Seattle, WA, 329° radials; Seattle; Yakima, WA; Pendleton, OR; Baker, OR; 
                            <PRTPAGE P="1803"/>
                            Boise, ID; INT Boise 130° and Burley, ID, 293° radials; Burley; Malad City, ID; Rock Springs, WY; Cherokee, WY; Laramie, WY; Gill, CO; Thurman, CO; Goodland, KS; Hill City, KS; Salina, KS; Topeka, KS; Kansas City, MO; Hallsville, MO; St. Louis, MO; Troy, IL; Centralia, IL; Pocket City, IN; Louisville, KY; to Lexington, KY. From Charleston, WV; Elkins, WV; Kessel, WV; INT Kessel 097° and Armel, VA, 292° radials; to Armel.
                        </P>
                        <STARS/>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Washington, DC, on January 2, 2024.</DATED>
                    <NAME>Frank Lias,</NAME>
                    <TITLE>Manager, Rules and Regulations Group.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00071 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 97</CFR>
                <DEPDOC>[Docket No. 31523; Amdt. No. 4093]</DEPDOC>
                <SUBJECT>Standard Instrument Approach Procedures, and Takeoff Minimums and Obstacle Departure Procedures; Miscellaneous Amendments</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This rule establishes, amends, suspends, or removes Standard Instrument Approach Procedures (SIAPS) and associated Takeoff Minimums and Obstacle Departure procedures (ODPs) for operations at certain airports. These regulatory actions are needed because of the adoption of new or revised criteria, or because of changes occurring in the National Airspace System, such as the commissioning of new navigational facilities, adding new obstacles, or changing air traffic requirements. These changes are designed to provide safe and efficient use of the navigable airspace and to promote safe flight operations under instrument flight rules at the affected airports.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This rule is effective January 11, 2024. The compliance date for each SIAP, associated Takeoff Minimums, and ODP is specified in the amendatory provisions.</P>
                    <P>The incorporation by reference of certain publications listed in the regulations is approved by the Director of the Federal Register as of January 11, 2024.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Availability of matters incorporated by reference in the amendment is as follows:</P>
                </ADD>
                <HD SOURCE="HD1">For Examination</HD>
                <P>1. U.S. Department of Transportation, Docket Ops-M30. 1200 New Jersey Avenue SE, West Bldg., Ground Floor, Washington, DC 20590-0001.</P>
                <P>2. The FAA Air Traffic Organization Service Area in which the affected airport is located;</P>
                <P>3. The office of Aeronautical Information Services, 6500 South MacArthur Blvd., Oklahoma City, OK 73169 or,</P>
                <P>
                    4. The National Archives and Records Administration (NARA). For information on the availability of this material at NARA, visit 
                    <E T="03">www.archives.gov/federal-register/cfr/ibr-locations</E>
                     or email 
                    <E T="03">fr.inspection@nara.gov.</E>
                </P>
                <HD SOURCE="HD1">Availability</HD>
                <P>
                    All SIAPs and Takeoff Minimums and ODPs are available online free of charge. Visit the National Flight Data Center at 
                    <E T="03">nfdc.faa.gov</E>
                     to register. Additionally, individual SIAP and Takeoff Minimums and ODP copies may be obtained from the FAA Air Traffic Organization Service Area in which the affected airport is located.
                </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Thomas J. Nichols, Flight Procedures and Airspace Group, Flight Technologies and Procedures Division, Flight Standards Service, Federal Aviation Administration. Mailing Address: FAA Mike Monroney Aeronautical Center, Flight Procedures and Airspace Group, 6500 South MacArthur Blvd., STB Annex, Bldg 26, Room 217, Oklahoma City, OK 73099. Telephone (405) 954-1139.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This rule amends 14 CFR part 97 by establishing, amending, suspending, or removes SIAPS, Takeoff Minimums and/or ODPS. The complete regulatory description of each SIAP and its associated Takeoff Minimums or ODP for an identified airport is listed on FAA form documents which are incorporated by reference in this amendment under 5 U.S.C. 552(a), 1 CFR part 51, and 14 CFR 97.20. The applicable FAA Forms 8260-3, 8260-4, 8260-5, 8260-15A, 8260-15B, when required by an entry on 8260-15A, and 8260-15C.</P>
                <P>
                    The large number of SIAPs, Takeoff Minimums and ODPs, their complex nature, and the need for a special format make publication in the 
                    <E T="04">Federal Register</E>
                     expensive and impractical. Further, pilots do not use the regulatory text of the SIAPs, Takeoff Minimums or ODPs, but instead refer to their graphic depiction on charts printed by publishers or aeronautical materials. Thus, the advantages of incorporation by reference are realized and publication of the complete description of each SIAP, Takeoff Minimums and ODP listed on FAA form documents is unnecessary. This amendment provides the affected CFR sections and specifies the types of SIAPS, Takeoff Minimums and ODPs with their applicable effective dates. This amendment also identifies the airport and its location, the procedure, and the amendment number.
                </P>
                <HD SOURCE="HD1">Availability and Summary of Material Incorporated by Reference</HD>
                <P>
                    The material incorporated by reference is publicly available as listed in the 
                    <E T="02">ADDRESSES</E>
                     section.
                </P>
                <P>The material incorporated by reference describes SIAPS, Takeoff Minimums and/or ODPs as identified in the amendatory language for part 97 of this final rule.</P>
                <HD SOURCE="HD1">The Rule</HD>
                <P>This amendment to 14 CFR part 97 is effective upon publication of each separate SIAP, Takeoff Minimums and ODP as amended in the transmittal. Some SIAP and Takeoff Minimums and textual ODP amendments may have been issued previously by the FAA in a Flight Data Center (FDC) Notice to Air Missions (NOTAM) as an emergency action of immediate flights safety relating directly to published aeronautical charts.</P>
                <P>The circumstances that created the need for some SIAP and Takeoff Minimums and ODP amendments may require making them effective in less than 30 days. For the remaining SIAPs and Takeoff Minimums and ODPs, an effective date at least 30 days after publication is provided.</P>
                <P>Further, the SIAPs and Takeoff Minimums and ODPs contained in this amendment are based on the criteria contained in the U.S. Standard for Terminal Instrument Procedures (TERPS). In developing these SIAPs and Takeoff Minimums and ODPs, the TERPS criteria were applied to the conditions existing or anticipated at the affected airports. Because of the close and immediate relationship between these SIAPs, Takeoff Minimums and ODPs, and safety in air commerce, I find that notice and public procedure under 5 U.S.C. 553(b) are impracticable and contrary to the public interest and, where applicable, under 5 U.S.C. 553(d), good cause exists for making some SIAPs effective in less than 30 days.</P>
                <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 
                    <PRTPAGE P="1804"/>
                    “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under DOT Regulatory Policies and Procedures (44 FR 11034; February 26, 1979); and (3) does not warrant preparation of a regulatory evaluation as the anticipated impact is so minimal. For the same reason, the FAA certifies that this amendment will not have a significant economic impact on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">Lists of Subjects in 14 CFR Part 97</HD>
                    <P>Air Traffic Control, Airports, Incorporation by reference, Navigation (Air).</P>
                </LSTSUB>
                <SIG>
                    <DATED>Issued in Washington, DC, on December 22, 2023.</DATED>
                    <NAME>Thomas J. Nichols,</NAME>
                    <TITLE>Aviation Safety, Flight Standards Service, Manager, Standards Section, Flight Procedures &amp; Airspace Group, Flight Technologies &amp; Procedures Division.</TITLE>
                </SIG>
                <HD SOURCE="HD1">Adoption of the Amendment</HD>
                <P>Accordingly, pursuant to the authority delegated to me, 14 CFR part 97 is amended by establishing, amending, suspending, or removing Standard Instrument Approach Procedures and/or Takeoff Minimums and Obstacle Departure Procedures effective at 0901 UTC on the dates specified, as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 97—STANDARD INSTRUMENT APPROACH PROCEDURES</HD>
                </PART>
                <REGTEXT TITLE="14" PART="97">
                    <AMDPAR>1. The authority citation for part 97 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>49 U.S.C. 106(f), 106(g), 40103, 40106, 40113, 40114, 40120, 44502, 44514, 44701, 44719, 44721-44722.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="14" PART="97">
                    <AMDPAR>2. Part 97 is amended to read as follows:</AMDPAR>
                    <EXTRACT>
                        <HD SOURCE="HD1">Effective 25 January 2024</HD>
                        <FP SOURCE="FP-1">Palm Springs, CA, PSP, VOR-B, Orig</FP>
                        <FP SOURCE="FP-1">Palm Springs, CA, PSP, VOR OR GPS-B, Amdt 3, CANCELED</FP>
                        <FP SOURCE="FP-1">Victorville, CA, VCV, LOC RWY 17, Amdt 3</FP>
                        <FP SOURCE="FP-1">Victorville, CA, KVCV, RNAV (GPS) RWY 17, Amdt 1</FP>
                        <FP SOURCE="FP-1">Victorville, CA, KVCV, RNAV (GPS) RWY 21, Orig</FP>
                        <FP SOURCE="FP-1">Victorville, CA, KVCV, RNAV (GPS) RWY 35, Orig</FP>
                        <FP SOURCE="FP-1">Eagle, CO, KEGE, RNAV (GPS) Y RWY 25, Orig</FP>
                        <FP SOURCE="FP-1">Eagle, CO, KEGE, RNAV (RNP) X RWY 25, Orig</FP>
                        <FP SOURCE="FP-1">Eagle, CO, KEGE, RNAV (RNP) Z RWY 25, Orig</FP>
                        <FP SOURCE="FP-1">Belleville, IL, BLV, ILS OR LOC RWY 14L, Orig-I</FP>
                        <FP SOURCE="FP-1">Casey, IL, 1H8, RNAV (GPS) RWY 4, Orig-C</FP>
                        <FP SOURCE="FP-1">Chicago/Rockford, IL, RFD, ILS OR LOC RWY 1, Amdt 30</FP>
                        <FP SOURCE="FP-1">Chicago/Rockford, IL, RFD, RNAV (GPS) RWY 1, Amdt 1E</FP>
                        <FP SOURCE="FP-1">Chicago/Rockford, IL, RFD, RNAV (GPS) RWY 7, Amdt 1E</FP>
                        <FP SOURCE="FP-1">Greenville, IL, GRE, RNAV (GPS) RWY 18, Amdt 1B</FP>
                        <FP SOURCE="FP-1">Greenville, IL, GRE, RNAV (GPS) RWY 36, Orig-B</FP>
                        <FP SOURCE="FP-1">Greenville, IL, KGRE, VOR-A, Amdt 3A, CANCELED</FP>
                        <FP SOURCE="FP-1">Jacksonville, IL, IJX, RNAV (GPS) RWY 13, Orig-D</FP>
                        <FP SOURCE="FP-1">Jacksonville, IL, IJX, RNAV (GPS) RWY 22, Orig-D</FP>
                        <FP SOURCE="FP-1">Shelbyville, IL, 2H0, NDB-A, Amdt 3A</FP>
                        <FP SOURCE="FP-1">Shelbyville, IL, 2H0, RNAV (GPS) RWY 36, Orig-E</FP>
                        <FP SOURCE="FP-1">Springfield, IL, SPI, VOR/DME RWY 31, Amdt 1B</FP>
                        <FP SOURCE="FP-1">Taylorville, IL, TAZ, RNAV (GPS) RWY 36, Orig-B</FP>
                        <FP SOURCE="FP-1">Vandalia, IL, VLA, RNAV (GPS) RWY 18, Orig-C</FP>
                        <FP SOURCE="FP-1">Vandalia, IL, VLA, RNAV (GPS) RWY 36, Orig-C</FP>
                        <FP SOURCE="FP-1">Vandalia, IL, VLA, VOR RWY 18, Amdt 12A, CANCELED</FP>
                        <FP SOURCE="FP-1">Saginaw, MI, MBS, ILS OR LOC RWY 5, Amdt 11A</FP>
                        <FP SOURCE="FP-1">Saginaw, MI, MBS, ILS OR LOC RWY 23, Amdt 5A</FP>
                        <FP SOURCE="FP-1">Saginaw, MI, MBS, VOR RWY 14, Amdt 14A</FP>
                        <FP SOURCE="FP-1">Fergus Falls, MN, FFM, RNAV (GPS) RWY 13, Orig-C</FP>
                        <FP SOURCE="FP-1">Jackson, MN, KMJQ, RNAV (GPS) RWY 13, Amdt 2, CANCELED</FP>
                        <FP SOURCE="FP-1">Jackson, MN, MJQ, RNAV (GPS) RWY 14, Orig</FP>
                        <FP SOURCE="FP-1">Jackson, MN, KMJQ, RNAV (GPS) RWY 31, Amdt 1B, CANCELED</FP>
                        <FP SOURCE="FP-1">Jackson, MN, MJQ, RNAV (GPS) RWY 32, Orig</FP>
                        <FP SOURCE="FP-1">Jackson, MN, KMJQ, Takeoff Minimums and Obstacle DP, Amdt 1</FP>
                        <FP SOURCE="FP-1">Drew, MS, M37, VOR-A, Amdt 5A</FP>
                        <FP SOURCE="FP-1">Beaufort, NC, KMRH, RNAV (GPS) RWY 21, Amdt 2C</FP>
                        <FP SOURCE="FP-1">Beaufort, NC, KMRH, RNAV (GPS) RWY 26, Amdt 3A</FP>
                        <FP SOURCE="FP-1">Greensboro, NC, KGSO, Takeoff Minimums and Obstacle DP, Amdt 1A</FP>
                        <FP SOURCE="FP-1">Norfolk, NE, OFK, RNAV (GPS) RWY 14, Amdt 2A</FP>
                        <FP SOURCE="FP-1">Norfolk, NE, OFK, RNAV (GPS) RWY 20, Amdt 2A</FP>
                        <FP SOURCE="FP-1">Minden, NV, MEV, RNAV (GPS) RWY 16, Orig</FP>
                        <FP SOURCE="FP-1">Minden, NV, MEV, RNAV (GPS) RWY 34, Orig</FP>
                        <FP SOURCE="FP-1">Minden, NV, KMEV, RNAV (GPS)-A, Amdt 1, CANCELED</FP>
                        <FP SOURCE="FP-1">Minden, NV, KMEV, RNAV (GPS)-B, Amdt 1, CANCELED</FP>
                        <FP SOURCE="FP-1">Philadelphia, PA, PHL, ILS OR LOC RWY 27L, ILS RWY 27L (SA CAT II), Amdt 16</FP>
                        <FP SOURCE="FP-1">Philadelphia, PA, PHL, RNAV (GPS) RWY 27L, Amdt 4</FP>
                        <FP SOURCE="FP-1">Beaumont/Port Arthur, TX, BPT, ILS OR LOC RWY 12, Amdt 24</FP>
                        <FP SOURCE="FP-1">Beaumont/Port Arthur, TX, BPT, RNAV (GPS) RWY 12, Amdt 1</FP>
                        <FP SOURCE="FP-1">Beaumont/Port Arthur, TX, BPT, RNAV (GPS) RWY 16, Amdt 1</FP>
                        <FP SOURCE="FP-1">Beaumont/Port Arthur, TX, BPT, RNAV (GPS) RWY 30, Amdt 1</FP>
                        <FP SOURCE="FP-1">Beaumont/Port Arthur, TX, BPT, RNAV (GPS) RWY 34, Amdt 1</FP>
                        <FP SOURCE="FP-1">Beaumont/Port Arthur, TX, KBPT, VOR RWY 12, Amdt 9E, CANCELED</FP>
                        <FP SOURCE="FP-1">Beaumont/Port Arthur, TX, KPBT, VOR/DME RWY 34, Amdt 7F, CANCELED</FP>
                        <FP SOURCE="FP-1">Commerce, TX, 2F7, RNAV (GPS) RWY 18, Amdt 1A</FP>
                        <FP SOURCE="FP-1">Escalante, UT, 1L7, HASSL ONE, Graphic DP</FP>
                        <FP SOURCE="FP-1">Escalante, UT, 1L7, RNAV (GPS) RWY 31, Orig</FP>
                        <FP SOURCE="FP-1">Escalante, UT, 1L7, Takeoff Minimums and Obstacle DP, Orig</FP>
                        <P>
                            <E T="03">Rescinded:</E>
                             On December 5, 2023 (88 FR 84234), the FAA published an Amendment in Docket No. 31519, Amdt No. 4089, to part 97 of the Federal Aviation Regulations under § 97.20. The following entry for Hickory, NC, effective January 25, 2024, is hereby rescinded in its entirety:
                        </P>
                        <FP SOURCE="FP-1">Hickory, NC, KHKY, HICKORY THREE, Graphic DP, CANCELED</FP>
                    </EXTRACT>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00098 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 97</CFR>
                <DEPDOC>[Docket No. 31524; Amdt. No. 4094]</DEPDOC>
                <SUBJECT>Standard Instrument Approach Procedures, and Takeoff Minimums and Obstacle Departure Procedures; Miscellaneous Amendments</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This rule amends, suspends, or removes Standard Instrument Approach Procedures (SIAPs) and associated Takeoff Minimums and Obstacle Departure Procedures for operations at certain airports. These regulatory actions are needed because of the adoption of new or revised criteria, or because of changes occurring in the National Airspace System, such as the commissioning of new navigational facilities, adding new obstacles, or changing air traffic requirements. These changes are designed to provide for the safe and efficient use of the navigable airspace and to promote safe flight operations under instrument flight rules at the affected airports.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This rule is effective January 11, 2024. The compliance date for each SIAP, associated Takeoff Minimums, and ODP is specified in the amendatory provisions.</P>
                    <P>The incorporation by reference of certain publications listed in the regulations is approved by the Director of the Federal Register as of January 11, 2024.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Availability of matter incorporated by reference in the amendment is as follows:
                        <PRTPAGE P="1805"/>
                    </P>
                </ADD>
                <HD SOURCE="HD1">For Examination</HD>
                <P>1. U.S. Department of Transportation, Docket Ops-M30, 1200 New Jersey Avenue SE, West Bldg., Ground Floor, Washington, DC 20590-0001;</P>
                <P>2. The FAA Air Traffic Organization Service Area in which the affected airport is located;</P>
                <P>3. The office of Aeronautical Information Services, 6500 South MacArthur Blvd., Oklahoma City, OK 73169 or,</P>
                <P>4. The National Archives and Records Administration (NARA).</P>
                <P>
                    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>
                <HD SOURCE="HD1">Availability</HD>
                <P>
                    All SIAPs and Takeoff Minimums and ODPs are available online free of charge. Visit the National Flight Data Center online at 
                    <E T="03">nfdc.faa.gov</E>
                     to register. Additionally, individual SIAP and Takeoff Minimums and ODP copies may be obtained from the FAA Air Traffic Organization Service Area in which the affected airport is located.
                </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Thomas J. Nichols, Flight Procedures and Airspace Group, Flight Technologies and Procedures Division, Flight Standards Service, Federal Aviation Administration. Mailing Address: FAA Mike Monroney Aeronautical Center, Flight Procedures and Airspace Group, 6500 South MacArthur Blvd., STB Annex, Bldg 26, Room 217, Oklahoma City, OK 73099. Telephone: (405) 954-1139.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    This rule amends 14 CFR part 97 by amending the referenced SIAPs. The complete regulatory description of each SIAP is listed on the appropriate FAA Form 8260, as modified by the National Flight Data Center (NFDC)/Permanent Notice to Air Missions (P-NOTAM), and is incorporated by reference under 5 U.S.C. 552(a), 1 CFR part 51, and 14 CFR 97.20. The large number of SIAPs, their complex nature, and the need for a special format make their verbatim publication in the 
                    <E T="04">Federal Register</E>
                     expensive and impractical. Further, pilots do not use the regulatory text of the SIAPs, but refer to their graphic depiction on charts printed by publishers of aeronautical materials. Thus, the advantages of incorporation by reference are realized and publication of the complete description of each SIAP contained on FAA form documents is unnecessary. This amendment provides the affected CFR sections, and specifies the SIAPs and Takeoff Minimums and ODPs with their applicable effective dates. This amendment also identifies the airport and its location, the procedure and the amendment number.
                </P>
                <HD SOURCE="HD1">Availability and Summary of Material Incorporated by Reference</HD>
                <P>
                    The material incorporated by reference is publicly available as listed in the 
                    <E T="02">ADDRESSES</E>
                     section.
                </P>
                <P>The material incorporated by reference describes SIAPs, Takeoff Minimums and ODPs as identified in the amendatory language for part 97 of this final rule.</P>
                <HD SOURCE="HD1">The Rule</HD>
                <P>This amendment to 14 CFR part 97 is effective upon publication of each separate SIAP and Takeoff Minimums and ODP as amended in the transmittal. For safety and timeliness of change considerations, this amendment incorporates only specific changes contained for each SIAP and Takeoff Minimums and ODP as modified by FDC permanent NOTAMs.</P>
                <P>The SIAPs and Takeoff Minimums and ODPs, as modified by FDC permanent NOTAM, and contained in this amendment are based on criteria contained in the U.S. Standard for Terminal Instrument Procedures (TERPS). In developing these changes to SIAPs and Takeoff Minimums and ODPs, the TERPS criteria were applied only to specific conditions existing at the affected airports. All SIAP amendments in this rule have been previously issued by the FAA in a FDC NOTAM as an emergency action of immediate flight safety relating directly to published aeronautical charts.</P>
                <P>The circumstances that created the need for these SIAP and Takeoff Minimums and ODP amendments require making them effective in less than 30 days.</P>
                <P>Because of the close and immediate relationship between these SIAPs, Takeoff Minimums and ODPs, and safety in air commerce, I find that notice and public procedure under 5 U.S.C. 553(b) are impracticable and contrary to the public interest and, where applicable, under 5 U.S.C. 553(d), good cause exists for making these SIAPs effective in less than 30 days.</P>
                <P>The FAA has determined that this regulation only involves an established body of technical regulations for which frequent and routine amendments are necessary to keep them operationally current. It, therefore—(1) is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under DOT regulatory Policies and Procedures (44 FR 11034; February 26, 1979); and (3) does not warrant preparation of a regulatory evaluation as the anticipated impact is so minimal. For the same reason, the FAA certifies that this amendment will not have a significant economic impact on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 97</HD>
                    <P>Air Traffic Control, Airports, Incorporation by reference, Navigation (Air).</P>
                </LSTSUB>
                <SIG>
                    <DATED>Issued in Washington, DC, on December 22, 2023.</DATED>
                    <NAME>Thomas J. Nichols,</NAME>
                    <TITLE>Aviation Safety, Flight Standards Service, Manager, Standards Section, Flight Procedures &amp; Airspace Group,  Flight Technologies &amp; Procedures Division.</TITLE>
                </SIG>
                <HD SOURCE="HD1">Adoption of the Amendment</HD>
                <P>Accordingly, pursuant to the authority delegated to me, 14 CFR part 97 is amended by amending Standard Instrument Approach Procedures and Takeoff Minimums and ODPs, effective at 0901 UTC on the dates specified, as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 97—STANDARD INSTRUMENT APPROACH PROCEDURES</HD>
                </PART>
                <REGTEXT TITLE="14" PART="97">
                    <AMDPAR>1. The authority citation for part 97 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 49 U.S.C. 106(f), 106(g), 40103, 40106, 40113, 40114, 40120, 44502, 44514, 44701, 44719, 44721-44722.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="14" PART="97">
                    <AMDPAR>2. Part 97 is amended to read as follows:</AMDPAR>
                    <P>By amending: § 97.23 VOR, VOR/DME, VOR or TACAN, and VOR/DME or TACAN; § 97.25 LOC, LOC/DME, LDA, LDA/DME, SDF, SDF/DME; § 97.27 NDB, NDB/DME; § 97.29 ILS, ILS/DME, MLS, MLS/DME, MLS/RNAV; § 97.31 RADAR SIAPs; § 97.33 RNAV SIAPs; and § 97.35 COPTER SIAPs, Identified as follows: </P>
                    <HD SOURCE="HD2">
                        Effective Upon Publication
                        <PRTPAGE P="1806"/>
                    </HD>
                    <GPOTABLE COLS="7" OPTS="L2,tp0,i1" CDEF="xs60,xls20,r50,r50,10,10,xs120">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1">AIRAC date</CHED>
                            <CHED H="1">State</CHED>
                            <CHED H="1">City</CHED>
                            <CHED H="1">Airport name</CHED>
                            <CHED H="1">FDC No.</CHED>
                            <CHED H="1">FDC date</CHED>
                            <CHED H="1">Procedure name</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">25-Jan-24</ENT>
                            <ENT>FL</ENT>
                            <ENT>Orlando</ENT>
                            <ENT>Orlando Intl</ENT>
                            <ENT>3/8059</ENT>
                            <ENT>10/5/23</ENT>
                            <ENT>This NOTAM, published in Docket No. 31522, Amdt No. 4092, TL 24-03, (88 FR 87666, December 19, 2023) is hereby rescinded in its entirety.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">25-Jan-24</ENT>
                            <ENT>CA</ENT>
                            <ENT>Mountain View</ENT>
                            <ENT>Moffett Federal Airfield</ENT>
                            <ENT>3/8470</ENT>
                            <ENT>11/9/23</ENT>
                            <ENT>This NOTAM, published in Docket No. 31522, Amdt No. 4092, TL 24-03, (88 FR 87666, December 19, 2023) is hereby rescinded in its entirety.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">25-Jan-24</ENT>
                            <ENT>TN</ENT>
                            <ENT>Gallatin</ENT>
                            <ENT>Music City Exec</ENT>
                            <ENT>3/0406</ENT>
                            <ENT>12/4/23</ENT>
                            <ENT>TAKEOFF MINIMUMS AND OBSTACLE DP, Amdt 4A.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">25-Jan-24</ENT>
                            <ENT>TX</ENT>
                            <ENT>Dallas-Fort Worth</ENT>
                            <ENT>Dallas-Fort Worth Intl</ENT>
                            <ENT>3/1410</ENT>
                            <ENT>11/29/23</ENT>
                            <ENT>ILS OR LOC RWY 36L, ILS RWY 36L (SA CAT II), Amdt 4.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">25-Jan-24</ENT>
                            <ENT>MO</ENT>
                            <ENT>Kansas City</ENT>
                            <ENT>Charles B Wheeler Downtown</ENT>
                            <ENT>3/2405</ENT>
                            <ENT>12/7/23</ENT>
                            <ENT>RNAV (GPS) RWY 4, Amdt 3B.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">25-Jan-24</ENT>
                            <ENT>MO</ENT>
                            <ENT>Kansas City</ENT>
                            <ENT>Charles B Wheeler Downtown</ENT>
                            <ENT>3/2407</ENT>
                            <ENT>12/7/23</ENT>
                            <ENT>ILS OR LOC RWY 4, Amdt 6.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">25-Jan-24</ENT>
                            <ENT>IL</ENT>
                            <ENT>Decatur</ENT>
                            <ENT>Decatur</ENT>
                            <ENT>3/2454</ENT>
                            <ENT>12/8/23</ENT>
                            <ENT>RNAV (GPS) RWY 12, Orig-B.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">25-Jan-24</ENT>
                            <ENT>UT</ENT>
                            <ENT>Provo</ENT>
                            <ENT>Provo Muni</ENT>
                            <ENT>3/3135</ENT>
                            <ENT>12/12/23</ENT>
                            <ENT>RNAV (GPS) RWY 13, Amdt 3.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">25-Jan-24</ENT>
                            <ENT>CA</ENT>
                            <ENT>Salinas</ENT>
                            <ENT>Salinas Muni</ENT>
                            <ENT>3/6109</ENT>
                            <ENT>12/6/23</ENT>
                            <ENT>RNAV (GPS) RWY 8, Orig.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">25-Jan-24</ENT>
                            <ENT>GA</ENT>
                            <ENT>Atlanta</ENT>
                            <ENT>Hartsfield-Jackson Atlanta Intl</ENT>
                            <ENT>3/7626</ENT>
                            <ENT>12/7/23</ENT>
                            <ENT>ILS OR LOC RWY 10, ILS RWY 10 (SA CAT I), ILS RWY 10 (CAT II-III), Amdt 5B.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">25-Jan-24</ENT>
                            <ENT>IL</ENT>
                            <ENT>Decatur</ENT>
                            <ENT>Decatur</ENT>
                            <ENT>3/8046</ENT>
                            <ENT>12/20/23</ENT>
                            <ENT>RNAV (GPS) RWY 6, Orig-C.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">25-Jan-24</ENT>
                            <ENT>MI</ENT>
                            <ENT>Mason</ENT>
                            <ENT>Mason Jewett Fld</ENT>
                            <ENT>3/8373</ENT>
                            <ENT>12/11/23</ENT>
                            <ENT>RNAV (GPS) RWY 28, Orig-D.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">25-Jan-24</ENT>
                            <ENT>LA</ENT>
                            <ENT>Galliano</ENT>
                            <ENT>South Lafourche Leonard Miller, Jr</ENT>
                            <ENT>3/8422</ENT>
                            <ENT>12/4/23</ENT>
                            <ENT>RNAV (GPS) RWY 18, Amdt 2B.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">25-Jan-24</ENT>
                            <ENT>MT</ENT>
                            <ENT>Livingston</ENT>
                            <ENT>Mission Fld</ENT>
                            <ENT>3/8454</ENT>
                            <ENT>12/6/23</ENT>
                            <ENT>RNAV (GPS) RWY 22, Orig-B.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">25-Jan-24</ENT>
                            <ENT>NC</ENT>
                            <ENT>Greensboro</ENT>
                            <ENT>Piedmont Triad Intl</ENT>
                            <ENT>3/8520</ENT>
                            <ENT>11/30/23</ENT>
                            <ENT>ILS OR LOC RWY 5R, Amdt 7C.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">25-Jan-24</ENT>
                            <ENT>NC</ENT>
                            <ENT>Greensboro</ENT>
                            <ENT>Piedmont Triad Intl</ENT>
                            <ENT>3/8524</ENT>
                            <ENT>11/30/23</ENT>
                            <ENT>RNAV (GPS) RWY 5L, Orig-D.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">25-Jan-24</ENT>
                            <ENT>WI</ENT>
                            <ENT>Madison</ENT>
                            <ENT>Dane County Rgnl/Truax Fld</ENT>
                            <ENT>3/8909</ENT>
                            <ENT>12/4/23</ENT>
                            <ENT>ILS OR LOC RWY 21, Orig-C.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">25-Jan-24</ENT>
                            <ENT>NJ</ENT>
                            <ENT>Newark</ENT>
                            <ENT>Newark Liberty Intl</ENT>
                            <ENT>3/9488</ENT>
                            <ENT>12/14/23</ENT>
                            <ENT>RNAV (RNP) Y RWY 22L, Amdt 1.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">25-Jan-24</ENT>
                            <ENT>OK</ENT>
                            <ENT>Ketchum</ENT>
                            <ENT>South Grand Lake Rgnl</ENT>
                            <ENT>3/9580</ENT>
                            <ENT>12/4/23</ENT>
                            <ENT>RNAV (GPS) RWY 18, Orig-A.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">25-Jan-24</ENT>
                            <ENT>OK</ENT>
                            <ENT>Ketchum</ENT>
                            <ENT>South Grand Lake Rgnl</ENT>
                            <ENT>3/9581</ENT>
                            <ENT>12/4/23</ENT>
                            <ENT>RNAV (GPS) RWY 36, Orig-B.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">25-Jan-24</ENT>
                            <ENT>AK</ENT>
                            <ENT>Koliganek</ENT>
                            <ENT>Koliganek</ENT>
                            <ENT>3/9584</ENT>
                            <ENT>12/6/23</ENT>
                            <ENT>RNAV (GPS) RWY 9, Amdt 1.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">25-Jan-24</ENT>
                            <ENT>PR</ENT>
                            <ENT>Ponce</ENT>
                            <ENT>Mercedita</ENT>
                            <ENT>3/9586</ENT>
                            <ENT>12/4/23</ENT>
                            <ENT>RNAV (GPS) RWY 12, Orig-E.</ENT>
                        </ROW>
                    </GPOTABLE>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00099 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <CFR>18 CFR Parts 250 and 385</CFR>
                <DEPDOC>[Docket No. RM24-3; Order No. 903]</DEPDOC>
                <SUBJECT>Civil Monetary Penalty Inflation Adjustments</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Energy Regulatory Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Federal Energy Regulatory Commission (Commission) is issuing a final rule to amend its regulations governing the maximum civil monetary penalties assessable for violations of statutes, rules, and orders within the Commission's jurisdiction. The Federal Civil Penalties Inflation Adjustment Act of 1990, as amended most recently by the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015, requires the Commission to issue this final rule.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This final rule is effective January 11, 2024.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Colin Chazen, Attorney, Office of Enforcement, Federal Energy Regulatory Commission, 888 First Street NE, Washington, DC 20426. Phone: (202) 502-8732; email: 
                        <E T="03">Colin.Chazen@ferc.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>1. In this final rule, the Federal Energy Regulatory Commission (Commission) is complying with its statutory obligation to amend the civil monetary penalties provided by law for matters within the agency's jurisdiction.</P>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    2. The Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015 (2015 Adjustment Act),
                    <SU>1</SU>
                    <FTREF/>
                     which further amended the Federal Civil Penalties Inflation Adjustment Act of 1990 (1990 Adjustment Act),
                    <SU>2</SU>
                    <FTREF/>
                     required the head of each Federal agency to issue a rule by July 2016 adjusting for inflation each “civil monetary penalty” provided by law within the agency's jurisdiction and to make further inflation adjustments on an annual basis every January 15 thereafter.
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Public Law  114-74, Sec. 701, 129 Stat. 584, 599.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Public Law  101-410, 104 Stat. 890 (codified as amended at 28 U.S.C. 2461 note).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         28 U.S.C. 2461 note, at (4). The Commission made its January 2023 adjustment on January 6, 2023, in Docket No. RM23-3000. 
                        <E T="03">See Civil Monetary Penalty Inflation Adjustments,</E>
                         Order No. 886, 88 FR 1989 (Jan. 12, 2023), 182 FERC ¶ 61,002 (2023).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">II. Discussion</HD>
                <P>
                    3. The 2015 Adjustment Act defines a civil monetary penalty as any penalty, fine, or other sanction that: (A)(i) is for a specific monetary amount as provided by Federal law; or (ii) has a maximum amount provided for by Federal law; (B) is assessed or enforced by an agency pursuant to Federal law; and (C) is assessed or enforced pursuant to an administrative proceeding or a civil 
                    <PRTPAGE P="1807"/>
                    action in the federal courts.
                    <SU>4</SU>
                    <FTREF/>
                     This definition applies to the maximum civil penalties that may be imposed under the Federal Power Act (FPA),
                    <SU>5</SU>
                    <FTREF/>
                     the Natural Gas Act (NGA),
                    <SU>6</SU>
                    <FTREF/>
                     the Natural Gas Policy Act of 1978 (NGPA),
                    <SU>7</SU>
                    <FTREF/>
                     and the Interstate Commerce Act (ICA).
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         28 U.S.C. 2461 note at (3).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         16 U.S.C. 791a 
                        <E T="03">et seq.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         15 U.S.C. 717 
                        <E T="03">et seq.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         15 U.S.C. 3301 
                        <E T="03">et seq.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         49 App. U.S.C. 1 
                        <E T="03">et seq.</E>
                         (1988).
                    </P>
                </FTNT>
                <P>
                    4. Under the 2015 Adjustment Act, the first step for such adjustment of a civil monetary penalty for inflation requires determining the percentage by which the U.S. Department of Labor's Consumer Price Index for all-urban consumers (CPI-U) for October of the preceding year exceeds the CPI-U for October of the year before that.
                    <SU>9</SU>
                    <FTREF/>
                     The CPI-U for October 2023 exceeded the CPI-U for October 2022 by 3.241%.
                    <SU>10</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         28 U.S.C. 2461 note at (5)(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See, e.g.,</E>
                         Memorandum from Shalanda D. Young, Office of Management and Budget, Implementation of the Penalty Inflation Adjustments for 2024, Pursuant to the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015 (Dec. 19, 2023).
                    </P>
                </FTNT>
                <P>
                    5. The second step requires multiplying the CPI-U percentage increase by the applicable existing maximum civil monetary penalty.
                    <SU>11</SU>
                    <FTREF/>
                     This step results in a base penalty increase amount.
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         28 U.S.C. 2461 note at (5)(a).
                    </P>
                </FTNT>
                <P>
                    6. The third step requires rounding the base penalty increase amount to the nearest dollar and adding that amount to the base penalty to calculate the new adjusted maximum civil monetary penalty.
                    <SU>12</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    7. Under the 2015 Adjustment Act, an agency is directed to use the maximum civil monetary penalty applicable at the time of assessment of a civil penalty, regardless of the date on which the violation occurred.
                    <SU>13</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">Id.</E>
                         at (6).
                    </P>
                </FTNT>
                <P>8. The adjustments that the Commission is required to make pursuant to the 2015 Adjustment Act are reflected in the following table:</P>
                <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s200,r100,r100">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Source</CHED>
                        <CHED H="1">
                            Existing maximum civil
                            <LI>monetary penalty</LI>
                        </CHED>
                        <CHED H="1">
                            New adjusted maximum civil 
                            <LI>monetary penalty</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">16 U.S.C. 825o-1(b), Sec. 316A of the Federal Power Act</ENT>
                        <ENT>$1,496,035 per violation, per day</ENT>
                        <ENT>$1,544,521 per violation, per day.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">16 U.S.C. 823b(c), Sec. 31(c) of the Federal Power Act</ENT>
                        <ENT>$27,017 per violation, per day</ENT>
                        <ENT>$27,893 per violation, per day.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">16 U.S.C. 825n(a), Sec. 315(a) of the Federal Power Act</ENT>
                        <ENT>$3,529 per violation</ENT>
                        <ENT>$3,643 per violation.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">15 U.S.C. 717t-1, Sec. 22 of the Natural Gas Act</ENT>
                        <ENT>$1,496,035 per violation, per day</ENT>
                        <ENT>$1,544,521 per violation, per day.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">15 U.S.C. 3414(b)(6)(A)(i), Sec. 504(b)(6)(A)(i) of the Natural Gas Policy Act of 1978</ENT>
                        <ENT>$1,496,035 per violation, per day</ENT>
                        <ENT>$1,544,521 per violation, per day.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">49 App. U.S.C. 6(10) (1988), Sec. 6(10) of the Interstate Commerce Act</ENT>
                        <ENT>$1,566 per offense and $78 per day after the first day</ENT>
                        <ENT>$1,617 per offense and $81 per day after the first day.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">49 App. U.S.C. 16(8) (1988), Sec. 16(8) of the Interstate Commerce Act</ENT>
                        <ENT>$15,662 per violation, per day</ENT>
                        <ENT>$16,170 per violation, per day.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">49 App. U.S.C. 19a(k) (1988), Sec. 19a(k) of the Interstate Commerce Act</ENT>
                        <ENT>$1,566 per offense, per day</ENT>
                        <ENT>$1,617 per offense, per day.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">49 App. U.S.C. 20(7)(a) (1988), Sec. 20(7)(a) of the Interstate Commerce Act</ENT>
                        <ENT>$1,566 per offense, per day</ENT>
                        <ENT>$1,617 per offense, per day.</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">III. Administrative Findings</HD>
                <P>
                    9. Congress directed that agencies issue final rules to adjust their maximum civil monetary penalties notwithstanding the requirements of the Administrative Procedure Act (APA).
                    <SU>14</SU>
                    <FTREF/>
                     Because the Commission is required by law to undertake these inflation adjustments notwithstanding the notice and comment requirements that otherwise would apply pursuant to the APA, and because the Commission lacks discretion with respect to the method and amount of the adjustments, prior notice and comment would be impractical, unnecessary, and contrary to the public interest.
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">Id.</E>
                         at (3)(b)(2).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Regulatory Flexibility Statement</HD>
                <P>
                    10. The Regulatory Flexibility Act, as amended, requires agencies to certify that rules promulgated under their authority will not have a significant economic impact on a substantial number of small businesses.
                    <SU>15</SU>
                    <FTREF/>
                     The requirements of the Regulatory Flexibility Act apply only to rules promulgated following notice and comment.
                    <SU>16</SU>
                    <FTREF/>
                     The requirements of the Regulatory Flexibility Act do not apply to this rulemaking because the Commission is issuing this final rule without notice and comment.
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         5 U.S.C. 601 
                        <E T="03">et seq.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         5 U.S.C. 603, 604.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">V. Paperwork Reduction Act</HD>
                <P>
                    11. This rule does not require the collection of information. The Commission is therefore not required to submit this rule for review to the Office of Management and Budget pursuant to the Paperwork Reduction Act of 1995.
                    <SU>17</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         44 U.S.C. 3507(d).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">VI. Document Availability</HD>
                <P>
                    12. 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 print the contents of this document via the internet through the Commission's Home Page (
                    <E T="03">http://www.ferc.gov</E>
                    ).
                </P>
                <P>13. 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 downloading. To access this document in eLibrary, type the docket number (excluding the last three digits) in the docket number field.</P>
                <P>
                    14. User assistance is available for eLibrary and the Commission's website during normal business hours from the Commission's 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, or email at 
                    <E T="03">public.referenceroom@ferc.gov</E>
                    .
                </P>
                <HD SOURCE="HD1">VII. Effective Date and Congressional Notification</HD>
                <P>
                    15. For the same reasons the Commission has determined that public notice and comment are unnecessary, impractical, and contrary to the public interest, the Commission finds good cause to adopt an effective date that is less than 30 days after the date of publication in the 
                    <E T="04">Federal Register</E>
                     pursuant to the APA,
                    <SU>18</SU>
                    <FTREF/>
                     and therefore, the regulation is effective upon publication in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         5 U.S.C. 553(d)(3).
                    </P>
                </FTNT>
                <P>
                    16. The Commission has determined, with the concurrence of the Administrator of the Office of 
                    <PRTPAGE P="1808"/>
                    Information and Regulatory Affairs of the Office of Management and Budget, that this rule is not a “major rule” as defined in section 351 of the Small Business Regulatory Enforcement Fairness Act of 1996. This final rule is being submitted to the Senate, House, and Government Accountability Office.
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects</HD>
                    <CFR>18 CFR Part 250</CFR>
                    <P>Natural gas, Reporting and recordkeeping requirements.</P>
                    <CFR>18 CFR Part 385</CFR>
                    <P>Administrative practice and procedure, Electric power, Penalties, Pipelines, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <SIG>
                    <P>By the Commission.</P>
                    <DATED>Issued: January 5, 2024.</DATED>
                    <NAME>Debbie-Anne A. Reese,</NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
                <P>
                    In consideration of the foregoing, the Commission amends parts 250 and 385, chapter I, title 18, 
                    <E T="03">Code of Federal Regulations</E>
                     as follows:
                </P>
                <PART>
                    <HD SOURCE="HED">PART 250—FORMS</HD>
                </PART>
                <REGTEXT TITLE="18" PART="250">
                    <AMDPAR>1. The authority citation for part 250 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>15 U.S.C. 717-717w, 3301-3432; 42 U.S.C. 7101-7352; 28 U.S.C. 2461 note.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="18" PART="250">
                    <AMDPAR>2. Amend § 250.16 by revising paragraph (e)(1) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 250.16</SECTNO>
                        <SUBJECT>Format of compliance plan for transportation services and affiliate transactions.</SUBJECT>
                        <STARS/>
                        <P>(e) * * *</P>
                        <P>(1) Any person who transports gas for others pursuant to subpart B or G of part 284 of this chapter and who knowingly violates the requirements of §§ 358.4 and 358.5 of this chapter, this section, or § 284.13 of this chapter will be subject, pursuant to sections 311(c), 501, and 504(b)(6) of the Natural Gas Policy Act of 1978, to a civil penalty, which the Commission may assess, of not more than $1,544,521 for any one violation.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 385—RULES OF PRACTICE AND PROCEDURE</HD>
                </PART>
                <REGTEXT TITLE="18" PART="385">
                    <AMDPAR>3. The authority citation for part 385 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>5 U.S.C. 551-557; 15 U.S.C. 717-717w, 3301-3432; 16 U.S.C. 791a-825v, 2601-2645; 28 U.S.C. 2461; 31 U.S.C. 3701, 9701; 42 U.S.C. 7101-7352, 16441, 16451-16463; 49 U.S.C. 60502; 49 App. U.S.C. 1-85 (1988); 28 U.S.C. 2461 note (1990); 28 U.S.C. 2461 note (2015).</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="18" PART="385">
                    <AMDPAR>4. Amend § 385.1504 by revising paragraph (a) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 385.1504</SECTNO>
                        <SUBJECT>Maximum civil penalty (Rule 1504).</SUBJECT>
                        <P>(a) Except as provided in paragraph (b) of this section, the Commission may assess a civil penalty of up to $27,893 for each day that the violation continues.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="18" PART="385">
                    <AMDPAR>5. Revise § 385.1602 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 385.1602</SECTNO>
                        <SUBJECT>Civil penalties, as adjusted (Rule 1602).</SUBJECT>
                        <P>The current inflation-adjusted civil monetary penalties provided by law within the jurisdiction of the Commission are:</P>
                        <P>(a) 15 U.S.C. 3414(b)(6)(A)(i), Natural Gas Policy Act of 1978: $1,544,521 per violation, per day.</P>
                        <P>(b) 16 U.S.C. 823b(c), Federal Power Act: $27,893 per violation, per day.</P>
                        <P>(c) 16 U.S.C. 825n(a), Federal Power Act: $3,643 per violation.</P>
                        <P>(d) 16 U.S.C. 825o-1(b), Federal Power Act: $1,544,521 per violation, per day.</P>
                        <P>(e) 15 U.S.C. 717t-1, Natural Gas Act: $1,544,521 per violation, per day.</P>
                        <P>(f) 49 App. U.S.C. 6(10) (1988), Interstate Commerce Act: $1,617 per offense and $78 per day after the first day.</P>
                        <P>(g) 49 App. U.S.C. 16(8) (1988), Interstate Commerce Act: $16,170 per violation, per day.</P>
                        <P>(h) 49 App. U.S.C. 19a(k) (1988), Interstate Commerce Act: $1,617 per offense, per day.</P>
                        <P>(i) 49 App. U.S.C. 20(7)(a) (1988), Interstate Commerce Act: $1,617 per offense, per day.</P>
                    </SECTION>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00425 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>U.S. Customs and Border Protection</SUBAGY>
                <AGENCY TYPE="O">DEPARTMENT OF THE TREASURY</AGENCY>
                <CFR>19 CFR Part 12</CFR>
                <DEPDOC>[CBP Dec. 24-01]</DEPDOC>
                <RIN>RIN 1515-AE87</RIN>
                <SUBJECT>Extension of Import Restrictions Imposed on Certain Archaeological Material From China</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Customs and Border Protection, Department of Homeland Security; Department of the Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document amends the U.S. Customs and Border Protection (CBP) regulations to extend import restrictions on certain archaeological material from China. The Assistant Secretary for Educational and Cultural Affairs, United States Department of State, has made the requisite determinations for extending the import restrictions, which were originally imposed by CBP Dec. 09-03 and last extended by CBP Dec. 19-02. Accordingly, these import restrictions will remain in effect for an additional five years, and the CBP regulations are being amended to reflect this further extension through January 14, 2029.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective January 14, 2024.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For legal aspects, W. Richmond Beevers, Chief, Cargo Security, Carriers and Restricted Merchandise Branch, Regulations and Rulings, Office of Trade, (202) 325-0084, 
                        <E T="03">ot-otrrculturalproperty@cbp.dhs.gov.</E>
                         For operational aspects, Julie L. Stoeber, Chief, 1USG Branch, Trade Policy and Programs, Office of Trade, (202) 945-7064, 
                        <E T="03">1USGBranch@cbp.dhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    The Convention on Cultural Property Implementation Act (Pub. L. 97-446, 19 U.S.C. 2601 
                    <E T="03">et seq.</E>
                    ) (CPIA), which implements the 1970 United Nations Educational, Scientific and Cultural Organization (UNESCO) Convention on the Means of Prohibiting and Preventing the Illicit Import, Export and Transfer of Ownership of Cultural Property (823 U.N.T.S. 231 (1972)) (the Convention), allows for the conclusion of an agreement between the United States and another party to the Convention to impose import restrictions on eligible archaeological and ethnological materials. Under the CPIA and the applicable U.S. Customs and Border Protection (CBP) regulations, found in § 12.104 of title 19 of the Code of Federal Regulations (19 CFR 12.104), the restrictions are effective for no more than five years beginning on the date on which an agreement enters into force with respect to the United States (19 U.S.C. 2602(b)). This period may be extended for additional periods, each extension not to exceed five years, if it is determined that the factors justifying the initial agreement still pertain and no cause for suspension of the agreement exists (19 U.S.C. 2602(e); 19 CFR 12.104g(a)).
                </P>
                <P>
                    On January 14, 2009, the United States entered into a bilateral agreement with the People's Republic of China (China) to impose import restrictions on 
                    <PRTPAGE P="1809"/>
                    certain archaeological material representing China's cultural heritage from the Paleolithic Period (c. 75,000 B.C.) through the end of the Tang Period (A.D. 907), and monumental sculpture and wall art at least 250 years old. On January 16, 2009, CBP published a final rule (CBP Dec. 09-03) in the 
                    <E T="04">Federal Register</E>
                     (74 FR 2838), which amended 19 CFR 12.104g(a) to reflect the imposition of these restrictions, including a list designating the types of archaeological materials covered by the restrictions.
                </P>
                <P>
                    The import restrictions were subsequently extended two more times in accordance with 19 U.S.C. 2602(e) and 19 CFR 12.104g(a), and the designated list was amended once. On January 13, 2014, CBP published a final rule (CBP Dec. 14-02) in the 
                    <E T="04">Federal Register</E>
                     (79 FR 2088), which amended § 12.104g(a) to reflect the extension of these import restrictions for an additional five years. By request of China, this document also amended the Designated List to clarify that the restrictions as to monumental sculpture and wall art at least 250 years old were to be calculated as of January 14, 2009, the date the agreement became effective.
                </P>
                <P>
                    Subsequently, on January 10, 2019, the United States and China entered into a new memorandum of understanding (2019 MOU), that superseded and replaced the prior agreement, extending the import restrictions for an additional five years. The new MOU added a new subcategory of glass objects from the Zhou period through the Tang period and revised the Designated List of cultural property described in CBP Dec. 14-02. On January 14, 2019, CBP published a final rule (CBP Dec. 19-02) in the 
                    <E T="04">Federal Register</E>
                     (84 FR 107), which amended § 12.104g(a) to reflect the extension of these import restrictions for an additional five years and amended the Designated List to include the new subcategory of glass objects from the Zhou period through the Tang Period. These import restrictions are due to expire on January 14, 2024.
                </P>
                <P>
                    On May 19, 2023, the United States Department of State proposed in the 
                    <E T="04">Federal Register</E>
                     (88 FR 32264) to extend the 2019 MOU. On November 14, 2023, after considering the views and recommendations of the Cultural Property Advisory Committee, the Acting Assistant Secretary for Educational and Cultural Affairs, United States Department of State, made the necessary determinations to extend the import restrictions for an additional five years. Following an exchange of diplomatic notes, the United States Department of State and the Government of the People's Republic of China have agreed to extend the restrictions for an additional five-year period, through January 14, 2029.
                </P>
                <P>Accordingly, CBP is amending 19 CFR 12.104g(a) to reflect the extension of these import restrictions. The restrictions on the importation of archaeological material from China will continue in effect through January 14, 2029. Importation of such material from China continues to be restricted through that date unless the conditions set forth in 19 U.S.C. 2606 and 19 CFR 12.104c are met.</P>
                <P>
                    The Designated List and additional information may also be found at the following website address: 
                    <E T="03">https://eca.state.gov/cultural-heritage-center/cultural-property-advisory-committee/current-import-restrictions</E>
                     by selecting the material for “China.”
                </P>
                <HD SOURCE="HD1">Inapplicability of Notice and Delayed Effective Date</HD>
                <P>This amendment involves a foreign affairs function of the United States and is, therefore, being made without notice or public procedure under 5 U.S.C. 553(a)(1). For the same reason, a delayed effective date is not required under 5 U.S.C. 553(d)(3).</P>
                <HD SOURCE="HD1">Executive Orders 12866 and 13563</HD>
                <P>Executive Orders 12866 (as amended by Executive Order 14994) and 13563 direct agencies to assess the costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety effects, distributive impacts, and equity). Executive Order 13563 emphasizes the importance of quantifying both costs and benefits, of reducing costs, of harmonizing rules, and of promoting flexibility. CBP has determined that this document is not a regulation or rule subject to the provisions of Executive Orders 12866 and 13563 because it pertains to a foreign affairs function of the United States, as described above, and therefore is specifically exempted by section 3(d)(2) of Executive Order 12866 and, by extension, Executive Order 13563.</P>
                <HD SOURCE="HD1">Regulatory Flexibility Act</HD>
                <P>
                    The Regulatory Flexibility Act (5 U.S.C. 601 
                    <E T="03">et seq.</E>
                    ), as amended by the Small Business Regulatory Enforcement Fairness Act of 1996, requires an agency to prepare and make available to the public a regulatory flexibility analysis that describes the effect of a proposed rule on small entities (
                    <E T="03">i.e.,</E>
                     small businesses, small organizations, and small governmental jurisdictions) when the agency is required to publish a general notice of proposed rulemaking for a rule. Since a general notice of proposed rulemaking is not necessary for this rule, CBP is not required to prepare a regulatory flexibility analysis for this rule.
                </P>
                <HD SOURCE="HD1">Signing Authority</HD>
                <P>This regulation is being issued in accordance with 19 CFR 0.1(a)(1) pertaining to the Secretary of the Treasury's authority (or that of the Secretary's delegate) to approve regulations related to customs revenue functions.</P>
                <P>
                    Troy A. Miller, the Senior Official Performing the Duties of the Commissioner, having reviewed and approved this document, has delegated the authority to electronically sign this document to the Director (or Acting Director, if applicable) of the Regulations and Disclosure Law Division for CBP, for purposes of publication in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 19 CFR Part 12</HD>
                    <P>Cultural property, Customs duties and inspection, Imports, Prohibited merchandise, and Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <HD SOURCE="HD1">Amendment to the CBP Regulations</HD>
                <P>For the reasons set forth above, part 12 of title 19 of the Code of Federal Regulations (19 CFR part 12), is amended as set forth below:</P>
                <PART>
                    <HD SOURCE="HED">PART 12—SPECIAL CLASSES OF MERCHANDISE</HD>
                </PART>
                <REGTEXT TITLE="19" PART="12">
                    <AMDPAR>1. The general authority citation for part 12 and the specific authority citation for § 12.104g continue to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>5 U.S.C. 301; 19 U.S.C. 66, 1202 (General Note 3(i), Harmonized Tariff Schedule of the United States (HTSUS)), 1624.</P>
                    </AUTH>
                    <EXTRACT>
                        <STARS/>
                        <P>Sections 12.104 through 12.104i also issued under 19 U.S.C. 2612;</P>
                        <STARS/>
                    </EXTRACT>
                </REGTEXT>
                <REGTEXT TITLE="19" PART="12">
                    <AMDPAR>2. In § 12.104g, amend the table in paragraph (a) by revising the entry for the People's Republic of China to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 12.104g</SECTNO>
                        <SUBJECT>Specific items or categories designated by agreements or emergency actions.</SUBJECT>
                        <P>
                            (a) * * *
                            <PRTPAGE P="1810"/>
                        </P>
                        <GPOTABLE COLS="3" OPTS="L1,tp0,i1" CDEF="s25,r100,r50">
                            <TTITLE> </TTITLE>
                            <BOXHD>
                                <CHED H="1">State party</CHED>
                                <CHED H="1">Cultural property</CHED>
                                <CHED H="1">Decision No.</CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">People's Republic of China</ENT>
                                <ENT>Archaeological materials representing China's cultural heritage from the Paleolithic Period (c. 75,000 B.C.) through the end of the Tang Period (A.D. 907) and monumental sculpture and wall art at least 250 years old as of January 14, 2009</ENT>
                                <ENT>CBP Dec. 19-02, extended by CBP Dec. 24-01.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                        </GPOTABLE>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <NAME>Robert F. Altneu,</NAME>
                    <TITLE>Director, Regulations and Disclosure Law Division, Regulations and Rulings, Office of Trade, U.S. Customs and Border Protection.</TITLE>
                    <FP>Approved:</FP>
                    <NAME>Thomas C. West, Jr.,</NAME>
                    <TITLE>Deputy Assistant Secretary of the Treasury for Tax Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00394 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9111-14-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF LABOR</AGENCY>
                <SUBAGY>Employment and Training Administration</SUBAGY>
                <CFR>20 CFR Part 655</CFR>
                <SUBAGY>Office of Workers' Compensation Programs</SUBAGY>
                <CFR>20 CFR Parts 702, 725, and 726</CFR>
                <SUBAGY>Office of the Secretary</SUBAGY>
                <CFR>29 CFR Part 5</CFR>
                <CFR>41 CFR Part 50-201</CFR>
                <SUBAGY>Wage and Hour Division</SUBAGY>
                <CFR>29 CFR Parts 500, 501, 503, 530, 570, 578, 579, 801, 810, and 825</CFR>
                <SUBAGY>Occupational Safety and Health Administration</SUBAGY>
                <CFR>29 CFR Part 1903</CFR>
                <SUBAGY>Mine Safety and Health Administration</SUBAGY>
                <CFR>30 CFR Part 100</CFR>
                <RIN>RIN 1290-AA48</RIN>
                <SUBJECT>Federal Civil Penalties Inflation Adjustment Act Annual Adjustments for 2024</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Employment and Training Administration, Office of Workers' Compensation Programs, Office of the Secretary, Wage and Hour Division, Occupational Safety and Health Administration, Employee Benefits Security Administration, and Mine Safety and Health Administration, Department of Labor.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The U.S. Department of Labor (Department) is publishing this final rule to adjust for inflation the civil monetary penalties assessed or enforced by the Department, pursuant to the Federal Civil Penalties Inflation Adjustment Act of 1990 as amended by the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015 (Inflation Adjustment Act). The Inflation Adjustment Act requires the Department to annually adjust its civil money penalty levels for inflation no later than January 15 of each year. The Inflation Adjustment Act provides that agencies shall adjust civil monetary penalties notwithstanding Section 553 of the Administrative Procedure Act (APA). Additionally, the Inflation Adjustment Act provides a cost-of-living formula for adjustment of the civil penalties. Accordingly, this final rule sets forth the Department's 2024 annual adjustments for inflation to its civil monetary penalties.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This final rule is effective on January 15, 2024. As provided by the Inflation Adjustment Act, the increased penalty levels apply to any penalties assessed after January 15, 2024.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Erin FitzGerald, Senior Policy Advisor, U.S. Department of Labor, Room S-2312, 200 Constitution Avenue NW, Washington, DC 20210; telephone: (202) 693-5076 (this is not a toll-free number). Copies of this final rule may be obtained in alternative formats (large print, Braille, audio tape or disc), upon request, by calling (202) 693-5959 (this is not a toll-free number). TTY/TDD callers may dial toll-free 1-877-889-5627 to obtain information or request materials in alternative formats.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Preamble Table of Contents</HD>
                <EXTRACT>
                    <FP SOURCE="FP-2">I. Background</FP>
                    <FP SOURCE="FP-2">II. Adjustment for 2024</FP>
                    <FP SOURCE="FP-2">III. Paperwork Reduction Act</FP>
                    <FP SOURCE="FP-2">IV. Administrative Procedure Act</FP>
                    <FP SOURCE="FP-2">V. Executive Order 12866: Regulatory Planning and Review and Executive Order 13563: Improving Regulation and Regulatory Review</FP>
                    <FP SOURCE="FP-2">VI. Regulatory Flexibility Act and Small Business Regulatory Enforcement Fairness Act</FP>
                    <FP SOURCE="FP-2">VII. Other Regulatory Considerations</FP>
                    <FP SOURCE="FP1-2">A. The Unfunded Mandates Reform Act of 1995</FP>
                    <FP SOURCE="FP1-2">B. Executive Order 13132: Federalism</FP>
                    <FP SOURCE="FP1-2">C. Executive Order 13175: Indian Tribal Governments</FP>
                    <FP SOURCE="FP1-2">D. The Treasury and General Government Appropriations Act of 1999: Assessment of Federal Regulations and Policies on Families</FP>
                    <FP SOURCE="FP1-2">E. Executive Order 13045: Protection of Children From Environmental Health Risks and Safety Risks</FP>
                    <FP SOURCE="FP1-2">F. Environmental Impact Assessment</FP>
                    <FP SOURCE="FP1-2">G. Executive Order 13211: Energy Supply</FP>
                    <FP SOURCE="FP1-2">H. Executive Order 12630: Constitutionally Protected Property Rights</FP>
                    <FP SOURCE="FP1-2">I. Executive Order 12988: Civil Justice Reform Analysis</FP>
                </EXTRACT>
                <HD SOURCE="HD1">I. Background</HD>
                <P>On November 2, 2015, Congress enacted the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015, Public Law 114-74, sec. 701 (Inflation Adjustment Act), which further amended the Federal Civil Penalties Inflation Adjustment Act of 1990 as previously amended by the 1996 Debt Collection Improvement Act (collectively, the “Prior Inflation Adjustment Act”), to improve the effectiveness of civil monetary penalties and to maintain their deterrent effect. The Inflation Adjustment Act required agencies to (1) adjust the level of civil monetary penalties with an initial “catch-up” adjustment through an interim final rule (IFR); and (2) make subsequent annual adjustments for inflation no later than January 15 of each year.</P>
                <P>
                    On July 1, 2016, the Department published an IFR that established the initial catch-up adjustment for most civil penalties that the Department administers and requested comments. 
                    <E T="03">See</E>
                     81 FR 43430 (DOL IFR). On January 18, 2017, the Department published the final rule establishing the 2017 Annual Adjustment for those civil monetary penalties adjusted in the DOL IFR. 
                    <E T="03">See</E>
                     82 FR 5373 (DOL 2017 Annual 
                    <PRTPAGE P="1811"/>
                    Adjustment). On July 1, 2016, the U.S. Department of Homeland Security (DHS) and the U.S. Department of Labor (DOL) (collectively, “the Departments”) jointly published an IFR that established the initial catch-up adjustment for civil monetary penalties assessed or enforced in connection with the employment of temporary nonimmigrant workers under the H-2B program. 
                    <E T="03">See</E>
                     81 FR 42983 (Joint IFR). On March 17, 2017, the Departments jointly published the final rule establishing the 2017 Annual Adjustment for the H-2B civil monetary penalties. 
                    <E T="03">See</E>
                     82 FR 14147 (Joint 2017 Annual Adjustment). The Joint 2017 Annual Adjustment also explained that DOL would make future adjustments to the H-2B civil monetary penalties consistent with DOL's delegated authority under 8 U.S.C. 1184(c)(14), Immigration and Nationality Act section 214(c)(14), and the Inflation Adjustment Act. 
                    <E T="03">See</E>
                     82 FR 14147-48. On January 2, 2018, the Department published the final rule establishing the 2018 Annual Adjustment for civil monetary penalties assessed or enforced by the Department, including H-2B civil monetary penalties. 
                    <E T="03">See</E>
                     83 FR 7 (DOL 2018 Annual Adjustment). On January 23, 2019, the Department published the final rule establishing the 2019 Annual Adjustment for civil monetary penalties assessed or enforced by the Department, including H-2B civil monetary penalties. 
                    <E T="03">See</E>
                     84 FR 213 (DOL 2019 Annual Adjustment). On January 15, 2020, the Department published the final rule establishing the 2020 Annual Adjustment for civil monetary penalties assessed or enforced by the Department, including H-2B civil monetary penalties. 
                    <E T="03">See</E>
                     85 FR 2292 (DOL 2020 Annual Adjustment). On January 14, 2021, the Department published the final rule establishing the 2021 Annual Adjustment for civil monetary penalties assessed or enforced by the Department, including H-2B civil monetary penalties. 
                    <E T="03">See</E>
                     86 FR 2964 (DOL 2021 Annual Adjustment). On January 14, 2022, the Department published the final rule establishing the 2022 Annual Adjustment for civil monetary penalties assessed or enforced by the Department, including H-2B civil monetary penalties. 
                    <E T="03">See</E>
                     87 FR 2328 (DOL 2022 Annual Adjustment). The DOL 2022 Annual Adjustment also included the first annual adjustments for a newly enacted civil monetary penalty regarding retention of tips under the Fair Labor Standards Act (FLSA) and a newly established civil monetary penalty regarding whistleblower protections under the high-wage components of the labor value content requirements of the United States-Mexico-Canada Agreement Implementation Act (USMCA). On January 13, 2023, the Department published the final rule establishing the 2023 Annual Adjustment for civil monetary penalties assessed or enforced by the Department, including H-2B civil monetary penalties. 
                    <E T="03">See</E>
                     88 FR 2210 (DOL 2023 Annual Adjustment).
                </P>
                <P>This rule implements the 2024 annual inflation adjustments, as required by the Inflation Adjustment Act, for civil monetary penalties assessed or enforced by the Department, including H-2B civil monetary penalties. The Inflation Adjustment Act provides that the increased penalty levels apply to any penalties assessed after the effective date of the increase. Pursuant to the Inflation Adjustment Act, this final rule is published notwithstanding Section 553 of the APA.</P>
                <P>This rule is not significant under Executive Order 12866.</P>
                <P>
                    Pursuant to the Congressional Review Act (5 U.S.C. 801 
                    <E T="03">et seq.</E>
                    ), the Office of Information and Regulatory Affairs designated this rule as not a `major rule,' as defined by 5 U.S.C. 804(2).
                </P>
                <HD SOURCE="HD1">II. Adjustment for 2024</HD>
                <P>
                    The Department has undertaken a thorough review of civil penalties administered by its various components pursuant to the Inflation Adjustment Act and in accordance with guidance issued by the Office of Management and Budget.
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         M-24-07, Implementation of Penalty Inflation Adjustments for 2024, Pursuant to the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015 (Dec. 19, 2023).
                    </P>
                </FTNT>
                <P>The Department first identified the most recent penalty amount, which is the amount established by the 2023 annual adjustment as set forth in the DOL 2023 Annual Adjustment published on January 13, 2023.</P>
                <P>
                    The Department is required to calculate the annual adjustment based on the Consumer Price Index for all Urban Consumers (CPI-U). Annual inflation adjustments are based on the percent change between the October CPI-U preceding the date of the adjustment, and the prior year's October CPI-U; in this case, the percent change between the October 2023 CPI-U and the October 2022 CPI-U. The cost-of-living adjustment multiplier for 2024, based on the Consumer Price Index (CPI-U) for the month of October 2023, not seasonally adjusted, is 1.03241.
                    <SU>2</SU>
                    <FTREF/>
                     In order to compute the 2024 annual adjustment, the Department multiplied the most recent penalty amount for each applicable penalty by the multiplier, 1.03241, and rounded to the nearest dollar.
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         OMB provided the year-over-year multiplier, rounded to 5 decimal points. 
                        <E T="03">Id.</E>
                         at 1.
                    </P>
                </FTNT>
                <P>
                    As provided by the Inflation Adjustment Act, the increased penalty levels apply to any penalties assessed after the effective date of this rule.
                    <SU>3</SU>
                    <FTREF/>
                     Accordingly, for penalties assessed after January 15, 2024, whose associated violations occurred after the applicable dates listed below, the higher penalty amounts outlined in this rule will apply. The tables below demonstrate the penalty amounts that apply:
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         Appendix 1 consists of a table that provides ready access to key information about each penalty.
                    </P>
                </FTNT>
                <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="xs130,r100,r60">
                    <TTITLE>
                        Civil Monetary Penalties for Violations of Section 3(
                        <E T="01">m</E>
                        )(2)(B) of the FLSA (Tips)
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">Violations occurring</CHED>
                        <CHED H="1">Penalty assessed</CHED>
                        <CHED H="1">Which penalty level applies</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">After March 23, 2018</ENT>
                        <ENT>After March 23, 2018 but on or before November 23, 2021</ENT>
                        <ENT>Consolidated Appropriations Act of 2018 amount.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">After March 23, 2018</ENT>
                        <ENT>After November 23, 2021 but on or before January 15, 2022</ENT>
                        <ENT>November 23, 2021 level.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">After March 23, 2018</ENT>
                        <ENT>After January 15, 2022 but on or before January 15, 2023</ENT>
                        <ENT>January 15, 2022 level.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">After March 23, 2018</ENT>
                        <ENT>After January 15, 2023 but on or before January 15, 2024</ENT>
                        <ENT>January 15, 2023 level.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">After March 23, 2018</ENT>
                        <ENT>After January 15, 2024</ENT>
                        <ENT>January 15, 2024 level.</ENT>
                    </ROW>
                </GPOTABLE>
                <PRTPAGE P="1812"/>
                <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="xs130,r100,r60">
                    <TTITLE>Civil Monetary Penalties for USMCA Violations</TTITLE>
                    <BOXHD>
                        <CHED H="1">Violations occurring</CHED>
                        <CHED H="1">Penalty assessed</CHED>
                        <CHED H="1">Which penalty level applies</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">After July 1, 2020</ENT>
                        <ENT>After July 1, 2020 but on or before January 15, 2022</ENT>
                        <ENT>2020 USMCA IFR amount.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">After July 1, 2020</ENT>
                        <ENT>After January 15, 2022 but on or before January 15, 2023</ENT>
                        <ENT>January 15, 2022 level.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">After July 1, 2020</ENT>
                        <ENT>After January 15, 2023 but on or before January 15, 2024</ENT>
                        <ENT>January 15, 2023 level.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">After July 1, 2020</ENT>
                        <ENT>After January 15, 2024</ENT>
                        <ENT>January 15, 2024 level.</ENT>
                    </ROW>
                </GPOTABLE>
                <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="xs130,r100,r60">
                    <TTITLE>Civil Monetary Penalties for the H-2B Temporary Non-Agricultural Worker Program</TTITLE>
                    <BOXHD>
                        <CHED H="1">Violations occurring</CHED>
                        <CHED H="1">Penalty assessed</CHED>
                        <CHED H="1">Which penalty level applies</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">On or before November 2, 2015</ENT>
                        <ENT>On or before August 1, 2016</ENT>
                        <ENT>Pre-August 1, 2016 levels.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">On or before November 2, 2015</ENT>
                        <ENT>After August 1, 2016</ENT>
                        <ENT>Pre-August 1, 2016 levels.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">After November 2, 2015</ENT>
                        <ENT>After August 1, 2016, but on or before March 17, 2017</ENT>
                        <ENT>August 1, 2016 levels.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">After November 2, 2015</ENT>
                        <ENT>After March 17, 2017 but on or before January 2, 2018</ENT>
                        <ENT>March 17, 2017 levels.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">After November 2, 2015</ENT>
                        <ENT>After January 2, 2018 but on or before January 23, 2019</ENT>
                        <ENT>January 2, 2018 levels.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">After November 2, 2015</ENT>
                        <ENT>After January 23, 2019 but on or before January 15, 2020</ENT>
                        <ENT>January 23, 2019 levels.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">After November 2, 2015</ENT>
                        <ENT>After January 15, 2020 but on or before January 15, 2021</ENT>
                        <ENT>January 15, 2020 levels.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">After November 2, 2015</ENT>
                        <ENT>After January 15, 2021 but on or before January 15, 2022</ENT>
                        <ENT>January 15, 2021 levels.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">After November 2, 2015</ENT>
                        <ENT>After January 15, 2022 but on or before January 15, 2023</ENT>
                        <ENT>January 15, 2022 levels.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">After November 2, 2015</ENT>
                        <ENT>After January 15, 2023 but on or before January 15, 2024</ENT>
                        <ENT>January 15, 2023 level.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">After November 2, 2015</ENT>
                        <ENT>After January 15, 2024</ENT>
                        <ENT>January 15, 2024 level.</ENT>
                    </ROW>
                </GPOTABLE>
                <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="xs130,r100,r60">
                    <TTITLE>Civil Monetary Penalties for Other DOL Programs</TTITLE>
                    <BOXHD>
                        <CHED H="1">Violations occurring</CHED>
                        <CHED H="1">Penalty assessed</CHED>
                        <CHED H="1">Which penalty level applies</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">On or before November 2, 2015</ENT>
                        <ENT>On or before August 1, 2016</ENT>
                        <ENT>Pre-August 1, 2016 levels.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">On or before November 2, 2015</ENT>
                        <ENT>After August 1, 2016</ENT>
                        <ENT>Pre-August 1, 2016 levels.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">After November 2, 2015</ENT>
                        <ENT>After August 1, 2016, but on or before January 13, 2017</ENT>
                        <ENT>August 1, 2016 levels.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">After November 2, 2015</ENT>
                        <ENT>After January 13, 2017 but on or before January 2, 2018</ENT>
                        <ENT>January 13, 2017 levels.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">After November 2, 2015</ENT>
                        <ENT>After January 2, 2018 but on or before January 23, 2019</ENT>
                        <ENT>January 2, 2018 levels.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">After November 2, 2015</ENT>
                        <ENT>After January 23, 2019 but on or before January 15, 2020</ENT>
                        <ENT>January 23, 2019 levels.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">After November 2, 2015</ENT>
                        <ENT>After January 15, 2020 but on or before January 15, 2021</ENT>
                        <ENT>January 15, 2020 levels.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">After November 2, 2015</ENT>
                        <ENT>After January 15, 2021 but on or before January 15, 2022</ENT>
                        <ENT>January 15, 2021 levels.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">After November 2, 2015</ENT>
                        <ENT>After January 15, 2022 but on or before January 15, 2023</ENT>
                        <ENT>January 15, 2022 levels.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">After November 2, 2015</ENT>
                        <ENT>After January 15, 2023 but on or before January 15, 2024</ENT>
                        <ENT>January 15, 2023 level.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">After November 2, 2015</ENT>
                        <ENT>After January 15, 2024</ENT>
                        <ENT>January 15, 2024 level.</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">III. Paperwork Reduction Act</HD>
                <P>The Paperwork Reduction Act of 1995 (44 U.S.C. 3507(d)) requires that the Department consider the impact of paperwork and other information collection burdens imposed on the public. The Department has determined that this final rule does not require any collection of information.</P>
                <HD SOURCE="HD1">IV. Administrative Procedure Act</HD>
                <P>
                    The Inflation Adjustment Act provides that agencies shall annually adjust civil monetary penalties for inflation notwithstanding section 553 of the APA. Additionally, the Inflation Adjustment Act provides a nondiscretionary cost-of-living formula for annual adjustment of the civil monetary penalties. For these reasons, the requirements in sections 553(b), (c), and (d) of the APA, relating to notice and comment and requiring that a rule be effective 30 days after publication in the 
                    <E T="04">Federal Register</E>
                    , are inapplicable.
                </P>
                <HD SOURCE="HD1">V. Executive Order 12866: Regulatory Planning and Review and Executive Order 13563: Improving Regulation and Regulatory Review</HD>
                <P>Executive Order 12866 (as supplemented by E.O. 14094) requires that regulatory agencies assess both the costs and benefits of significant regulatory actions. Under the Executive Order, a “significant regulatory action” is one meeting any of a number of specified conditions, including the following: having an annual effect on the economy of $200 million or more; creating a serious inconsistency or interfering with an action of another agency; materially altering the budgetary impact of entitlements or the rights of entitlement recipients; or raising novel legal or policy issues.</P>
                <P>The Department has determined that this final rule is not a “significant” regulatory action and a cost-benefit and economic analysis is not required. This regulation merely adjusts civil monetary penalties in accordance with inflation as required by the Inflation Adjustment Act, and has no impact on disclosure or compliance costs. The benefit provided by the inflationary adjustment to the maximum civil monetary penalties is that of maintaining the incentive for the regulated community to comply with the laws enforced by the Department, and not allowing the incentive to be diminished by inflation.</P>
                <P>Executive Order 13563 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). Executive Order 13563 emphasizes the importance of quantifying both costs and benefits, reducing costs, harmonizing rules, and promoting flexibility to minimize burden.</P>
                <P>
                    The Inflation Adjustment Act directed the Department to issue the annual adjustments without regard to section 553 of the APA. In that context, Congress has already determined that any possible increase in costs is justified 
                    <PRTPAGE P="1813"/>
                    by the overall benefits of such adjustments. This final rule makes only the statutory changes outlined herein; thus there are no alternatives or further analysis required by Executive Order 13563.
                </P>
                <HD SOURCE="HD1">VI. Regulatory Flexibility Act and Small Business Regulatory Enforcement Fairness Act</HD>
                <P>
                    The Regulatory Flexibility Act, 5 U.S.C. 601 
                    <E T="03">et seq.</E>
                     (RFA), imposes certain requirements on Federal agency rules that are subject to the notice and comment requirements of the APA, 5 U.S.C. 553(b). This final rule is exempt from the requirements of the APA because the Inflation Adjustment Act directed the Department to issue the annual adjustments without regard to section 553 of the APA. Therefore, the requirements of the RFA applicable to notices of proposed rulemaking, 5 U.S.C. 603, do not apply to this rule. Accordingly, the Department is not required to either certify that the final rule would not have a significant economic impact on a substantial number of small entities or conduct a regulatory flexibility analysis.
                </P>
                <HD SOURCE="HD1">VII. Other Regulatory Considerations</HD>
                <HD SOURCE="HD2">A. The Unfunded Mandates Reform Act of 1995</HD>
                <P>The Unfunded Mandates Reform Act of 1995, 2 U.S.C. 1531-1538, requires Federal agencies to assess the effects of their discretionary regulatory actions. In particular, the Act addresses actions that may result in the expenditure by a state, local, or tribal government, in the aggregate, or by the private sector of $100,000,000 (adjusted for inflation) or more in any one year. This Final Rule will not result in such an expenditure. Therefore, no actions were deemed necessary under the provisions of the Unfunded Mandates Reform Act of 1995.</P>
                <HD SOURCE="HD2">B. Executive Order 13132: Federalism</HD>
                <P>
                    Section 18 of the Occupational Safety and Health Act of 1970 (OSH Act) (29 U.S.C. 667) requires Occupational Safety and Health Administration (OSHA)-approved State Plans to have standards and an enforcement program that are at least as effective as Federal OSHA's standards and enforcement program. OSHA-approved State Plans must have maximum and minimum penalty levels that are at least as effective as Federal OSHA's, per section 18(c)(2) of the OSH Act. 
                    <E T="03">See also</E>
                     29 CFR 1902.4(c)(2)(xi); 1902.37(b)(12). State Plans are required to increase their penalties in alignment with OSHA's penalty increases to maintain at least as effective penalty levels.
                </P>
                <P>
                    State Plans are not required to impose monetary penalties on state and local government employers. 
                    <E T="03">See</E>
                     § 1956.11(c)(2)(x). Six (6) states and one territory have State Plans that cover only state and local government employees: Connecticut, Illinois, Maine, Massachusetts, New Jersey, New York, and the Virgin Islands. Therefore, the requirements to increase the penalty levels do not apply to these State Plans. Twenty-one states and one U.S. territory have State Plans that cover both private sector employees and state and local government employees: Alaska, Arizona, California, Hawaii, Indiana, Iowa, Kentucky, Maryland, Michigan, Minnesota, Nevada, New Mexico, North Carolina, Oregon, Puerto Rico, South Carolina, Tennessee, Utah, Vermont, Virginia, Washington, and Wyoming. They must increase their penalties for private-sector employers.
                </P>
                <P>Other than as listed above, this final rule does not have federalism implications because it does 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. Accordingly, Executive Order 13132, Federalism, requires no further agency action or analysis.</P>
                <HD SOURCE="HD2">C. Executive Order 13175: Indian Tribal Governments</HD>
                <P>This final rule does not have “tribal implications” because it does not have substantial direct effects on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes. Accordingly, Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, requires no further agency action or analysis.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects</HD>
                    <CFR>20 CFR Part 655</CFR>
                    <P>Immigration, Labor, Penalties.</P>
                    <CFR>20 CFR Part 702</CFR>
                    <P>Administrative practice and procedure, Longshore and harbor workers, Penalties, Reporting and recordkeeping requirements, Workers' compensation.</P>
                    <CFR>20 CFR Part 725</CFR>
                    <P>Administrative practice and procedure, Black lung benefits, Coal miners, Penalties, Reporting and recordkeeping requirements.</P>
                    <CFR>20 CFR Part 726</CFR>
                    <P>Administrative practice and procedure, Black lung benefits, Coal miners, Mines, Penalties.</P>
                    <CFR>29 CFR Part 5</CFR>
                    <P>Administrative practice and procedure, Construction industry, Employee benefit plans, Government contracts, Law enforcement, Minimum wages, Penalties, Reporting and recordkeeping requirements.</P>
                    <CFR>29 CFR Part 500</CFR>
                    <P>Administrative practice and procedure, Aliens, Housing, Insurance, Intergovernmental relations, Investigations, Migrant labor, Motor vehicle safety, Occupational safety and health, Penalties, Reporting and recordkeeping requirements, Wages, Whistleblowing.</P>
                    <CFR>29 CFR Part 501</CFR>
                    <P>Administrative practice and procedure, Agriculture, Aliens, Employment, Housing, Housing standards, Immigration, Labor, Migrant labor, Penalties, Transportation, Wages.</P>
                    <CFR>29 CFR Part 503</CFR>
                    <P>Administrative practice and procedure, Aliens, Employment, Housing, Immigration, Labor, Penalties, Transportation, Wages.</P>
                    <CFR>29 CFR Part 530</CFR>
                    <P>Administrative practice and procedure, Clothing, Homeworkers, Indians—arts and crafts, Penalties, Reporting and recordkeeping requirements, Surety bonds, Watches and jewelry.</P>
                    <CFR>29 CFR Part 570</CFR>
                    <P>Child labor, Law enforcement, Penalties.</P>
                    <CFR>29 CFR Part 578</CFR>
                    <P>Penalties, Wages.</P>
                    <CFR>29 CFR Part 579</CFR>
                    <P>Child labor, Penalties.</P>
                    <CFR>29 CFR Part 801</CFR>
                    <P>Administrative practice and procedure, Employment, Lie detector tests, Penalties, Reporting and recordkeeping requirements.</P>
                    <CFR>29 CFR Part 810</CFR>
                    <P>Labor, Wages, Hours of work, Trade agreement, Motor vehicle, Tariffs, Imports, Whistleblowing.</P>
                    <CFR>29 CFR Part 825</CFR>
                    <P>
                        Administrative practice and procedure, Airmen, Employee benefit plans, Health, Health insurance, Labor 
                        <PRTPAGE P="1814"/>
                        management relations, Maternal and child health, Penalties, Reporting and recordkeeping requirements, Teachers.
                    </P>
                    <CFR>29 CFR Part 1903</CFR>
                    <P>Intergovernmental relations, Law enforcement, Occupational Safety and Health, Penalties.</P>
                    <CFR>30 CFR Part 100</CFR>
                    <P>Mine safety and health, Penalties.</P>
                    <CFR>41 CFR Part 50-201</CFR>
                    <P>Child labor, Government procurement, Minimum wages, Occupational safety and health, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <P>For the reasons set out in the preamble, 20 CFR chapters VI and VII, 29 CFR subtitle A and chapters V, XVII, and XXV, 30 CFR chapter I, and 41 CFR chapter 50 are amended as follows.</P>
                <HD SOURCE="HD1">
                    <E T="0742">DEPARTMENT OF LABOR</E>
                </HD>
                <HD SOURCE="HD1">
                    <E T="0742">Employment and Training Administration</E>
                </HD>
                <TITLE>Title 20—Employees' Benefits</TITLE>
                <PART>
                    <HD SOURCE="HED">PART 655—TEMPORARY EMPLOYMENT OF FOREIGN WORKERS IN THE UNITED STATES</HD>
                </PART>
                <REGTEXT TITLE="20" PART="655">
                    <AMDPAR>1. The authority citation for part 655 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> Section 655.0 issued under 8 U.S.C. 1101(a)(15)(E)(iii), 1101(a)(15)(H)(i) and (ii), 8 U.S.C. 1103(a)(6), 1182(m), (n), and (t), 1184(c), (g), and (j), 1188, and 1288(c) and (d); sec. 3(c)(1), Pub. L. 101-238, 103 Stat. 2099, 2102 (8 U.S.C. 1182 note); sec. 221(a), Pub. L. 101-649, 104 Stat. 4978, 5027 (8 U.S.C. 1184 note); sec. 303(a)(8), Pub. L. 102-232, 105 Stat. 1733, 1748 (8 U.S.C. 1101 note); sec. 323(c), Pub. L. 103-206, 107 Stat. 2428; sec. 412(e), Pub. L. 105-277, 112 Stat. 2681 (8 U.S.C. 1182 note); sec. 2(d), Pub. L. 106-95, 113 Stat. 1312, 1316 (8 U.S.C. 1182 note); 29 U.S.C. 49k; Pub. L. 107-296, 116 Stat. 2135, as amended; Pub. L. 109-423, 120 Stat. 2900; 8 CFR 214.2(h)(4)(i); and 8 CFR 214.2(h)(6)(iii); and sec. 6, Pub. L. 115-128, 132 Stat. 1547 (48 U.S.C. 1806).</P>
                    </AUTH>
                    <EXTRACT>
                        <P>Subpart A issued under 8 CFR 214.2(h).</P>
                        <P>Subpart B issued under 8 U.S.C. 1101(a)(15)(H)(ii)(a), 1184(c), and 1188; and 8 CFR 214.2(h).</P>
                        <P>Subpart E issued under 48 U.S.C. 1806.</P>
                        <P>Subparts F and G issued under 8 U.S.C. 1288(c) and (d); sec. 323(c), Pub. L. 103-206, 107 Stat. 2428; and 28 U.S.C. 2461 note, Pub. L. 114-74 at section 701.</P>
                        <P>Subparts H and I issued under 8 U.S.C. 1101(a)(15)(H)(i)(b) and (b)(1), 1182(n), and (t), and 1184(g) and (j); sec. 303(a)(8), Pub. L. 102-232, 105 Stat. 1733, 1748 (8 U.S.C. 1101 note); sec. 412(e), Pub. L. 105-277, 112 Stat. 2681; 8 CFR 214.2(h); and 28 U.S.C. 2461 note, Pub. L. 114-74 at section 701.</P>
                        <P>Subparts L and M issued under 8 U.S.C. 1101(a)(15)(H)(i)(c) and 1182(m); sec. 2(d), Pub. L. 106-95, 113 Stat. 1312, 1316 (8 U.S.C. 1182 note); Pub. L. 109-423, 120 Stat. 2900; and 8 CFR 214.2(h).</P>
                    </EXTRACT>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§§ 655.620, 655.801, and 655.810</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="20" PART="655">
                    <AMDPAR>2. In the following table, for each paragraph indicated in the left column, remove the dollar amount indicated in the middle column from wherever it appears in the paragraph and add in its place the dollar amount indicated in the right column.</AMDPAR>
                    <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s100,12,12">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1">Paragraph</CHED>
                            <CHED H="1">Remove</CHED>
                            <CHED H="1">Add</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">§ 655.620(a)</ENT>
                            <ENT>$11,162</ENT>
                            <ENT>$11,524</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 655.801(b)</ENT>
                            <ENT>9,086</ENT>
                            <ENT>9,380</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 655.810(b)(1) introductory text</ENT>
                            <ENT>2,232</ENT>
                            <ENT>2,304</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 655.810(b)(2) introductory text</ENT>
                            <ENT>9,086</ENT>
                            <ENT>9,380</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 655.810(b)(3) introductory text</ENT>
                            <ENT>63,600</ENT>
                            <ENT>65,661</ENT>
                        </ROW>
                    </GPOTABLE>
                </REGTEXT>
                <HD SOURCE="HD1">
                    <E T="0742">Office of Workers' Compensation Programs</E>
                </HD>
                <PART>
                    <HD SOURCE="HED">PART 702—ADMINISTRATION AND PROCEDURE</HD>
                </PART>
                <REGTEXT TITLE="20" PART="702">
                    <AMDPAR>3. The authority citation for part 702 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>
                             5 U.S.C. 301, and 8171 
                            <E T="03">et seq.;</E>
                             33 U.S.C. 901 
                            <E T="03">et seq.;</E>
                             42 U.S.C. 1651 
                            <E T="03">et seq.;</E>
                             43 U.S.C. 1333; 28 U.S.C. 2461 note (Federal Civil Penalties Inflation Adjustment Act of 1990); Pub. L. 114-74 at sec. 701; Reorganization Plan No. 6 of 1950, 15 FR 3174, 64 Stat. 1263; Secretary's Order 10-2009, 74 FR 58834.
                        </P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§§ 702.204, 702.236, and 702.271</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="20" PART="702">
                    <AMDPAR>4. In the following table, for each paragraph indicated in the left column, remove the dollar amount or date indicated in the middle column from wherever it appears in the section or paragraph and add in its place the dollar amount or date indicated in the right column.</AMDPAR>
                    <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s100,r100,xs100">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1">Section/paragraph</CHED>
                            <CHED H="1">Remove</CHED>
                            <CHED H="1">Add</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">§ 702.204</ENT>
                            <ENT>$28,304</ENT>
                            <ENT>$29,221</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 702.204</ENT>
                            <ENT>January 15, 2023</ENT>
                            <ENT>January 15, 2024</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 702.236</ENT>
                            <ENT>$345</ENT>
                            <ENT>$356</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 702.236</ENT>
                            <ENT>January 15, 2023</ENT>
                            <ENT>January 15, 2024</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 702.271(a)(2)</ENT>
                            <ENT>January 15, 2023</ENT>
                            <ENT>January 15, 2024</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 702.271(a)(2)</ENT>
                            <ENT>$2,830</ENT>
                            <ENT>$2,922</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 702.271(a)(2)</ENT>
                            <ENT>$14,149</ENT>
                            <ENT>$14,608</ENT>
                        </ROW>
                    </GPOTABLE>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 725—CLAIMS FOR BENEFITS UNDER PART C OF TITLE IV OF THE FEDERAL MINE SAFETY AND HEALTH ACT, AS AMENDED</HD>
                </PART>
                <REGTEXT TITLE="20" PART="725">
                    <AMDPAR>5. The authority citation for part 725 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>
                             5 U.S.C. 301; 28 U.S.C. 2461 note (Federal Civil Penalties Inflation Adjustment Act of 1990); Pub. L. 114-74 at sec. 701; Reorganization Plan No. 6 of 1950, 15 FR 3174; 30 U.S.C. 901 
                            <E T="03">et seq.,</E>
                             902(f), 921, 932, 936; 33 U.S.C. 901 
                            <E T="03">et seq.;</E>
                             42 U.S.C. 405; Secretary's Order 10-2009, 74 FR 58834.
                        </P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 725.621</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>6. In § 725.621, amend paragraph (d) by removing “January 15, 2023” and adding in its place “January 15, 2024” and by removing “$1,724” and adding in its place “$1,780”.</AMDPAR>
                </REGTEXT>
                <PART>
                    <PRTPAGE P="1815"/>
                    <HD SOURCE="HED">PART 726—BLACK LUNG BENEFITS; REQUIREMENTS FOR COAL MINE OPERATOR'S INSURANCE</HD>
                </PART>
                <REGTEXT TITLE="20" PART="726">
                    <AMDPAR>7. The authority citation for part 726 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>
                             5 U.S.C. 301; 30 U.S.C. 901 
                            <E T="03">et seq.,</E>
                             902(f), 925, 932, 933, 934, 936; 33 U.S.C. 901 
                            <E T="03">et seq.;</E>
                             28 U.S.C. 2461 note (Federal Civil Penalties Inflation Adjustment Act of 1990); Pub. L. 114-74 at sec. 701; Reorganization Plan No. 6 of 1950, 15 FR 3174; Secretary's Order 10-2009, 74 FR 58834.
                        </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="20" PART="726">
                    <AMDPAR>8. In § 726.302:</AMDPAR>
                    <AMDPAR>a. In paragraph (c)(2)(i) introductory text, remove “January 15, 2023” and add “January 15, 2024” in its place;</AMDPAR>
                    <AMDPAR>b. Revise the Table 1 to paragraph (c)(2)(i); and</AMDPAR>
                    <AMDPAR>c. In the following table, for each paragraph indicated in the left column, remove the dollar amount or date indicated in the middle column from wherever it appears in the paragraph and add in its place the dollar amount or date indicated in the right column.</AMDPAR>
                    <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s100,r100,xs100">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1">Paragraph</CHED>
                            <CHED H="1">Remove</CHED>
                            <CHED H="1">Add</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">(c)(4)</ENT>
                            <ENT>January 15, 2023</ENT>
                            <ENT>January 15, 2024</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(c)(4)</ENT>
                            <ENT>$169</ENT>
                            <ENT>$174</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(c)(5)</ENT>
                            <ENT>January 15, 2023</ENT>
                            <ENT>January 15, 2024</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(c)(5)</ENT>
                            <ENT>$504</ENT>
                            <ENT>$520</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(c)(6)</ENT>
                            <ENT>January 15, 2023</ENT>
                            <ENT>January 15, 2024</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(c)(6)</ENT>
                            <ENT>$3,446</ENT>
                            <ENT>$3,558</ENT>
                        </ROW>
                    </GPOTABLE>
                    <SECTION>
                        <SECTNO>§ 726.302</SECTNO>
                        <SUBJECT>Determination of penalty.</SUBJECT>
                        <STARS/>
                        <P>(c) * * *</P>
                        <P>(2) * * *</P>
                        <P>(i) * * *</P>
                        <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s25,9">
                            <TTITLE>
                                Table 1 to Paragraph 
                                <E T="01">(c)(2)(i)</E>
                            </TTITLE>
                            <BOXHD>
                                <CHED H="1">Employees</CHED>
                                <CHED H="1">
                                    Penalty
                                    <LI>(per day)</LI>
                                </CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">Less than 25</ENT>
                                <ENT>$174</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">25-50</ENT>
                                <ENT>346</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">51-199</ENT>
                                <ENT>520</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">More than 100</ENT>
                                <ENT>692</ENT>
                            </ROW>
                        </GPOTABLE>
                    </SECTION>
                </REGTEXT>
                <HD SOURCE="HD1">
                    <E T="0742">DEPARTMENT OF LABOR</E>
                </HD>
                <TITLE>Title 29—Labor</TITLE>
                <PART>
                    <HD SOURCE="HED">PART 5—LABOR STANDARDS PROVISIONS APPLICABLE TO CONTRACTS COVERING FEDERALLY FINANCED AND ASSISTED CONSTRUCTION (ALSO LABOR STANDARDS PROVISIONS APPLICABLE TO NONCONSTRUCTION CONTRACTS SUBJECT TO THE CONTRACT WORK HOURS AND SAFETY STANDARDS ACT)</HD>
                </PART>
                <REGTEXT TITLE="29" PART="5">
                    <AMDPAR>9. The authority citation for part 5 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>
                             5 U.S.C. 301; R.S. 161, 64 Stat. 1267; Reorganization Plan No. 14 of 1950, 5 U.S.C. appendix; 40 U.S.C. 3141 
                            <E T="03">et seq.;</E>
                             40 U.S.C. 3145; 40 U.S.C. 3148; 40 U.S.C. 3701 
                            <E T="03">et seq.;</E>
                             and the laws listed in 5.1(a) of this part; Secretary's Order No. 01-2014 (Dec. 19, 2014), 79 FR 77527 (Dec. 24, 2014); 28 U.S.C. 2461 note (Federal Civil Penalties Inflation Adjustment Act of 1990); Pub. L. 114-74 at sec. 701, 129 Stat 584.
                        </P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 5.5</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="29" PART="5">
                    <AMDPAR>10. In § 5.5, amend paragraph (b)(2) by removing “$31” and adding in its place “$32”.</AMDPAR>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 5.8</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="29" PART="5">
                    <AMDPAR>11. In § 5.8, amend paragraph (a) by removing “$31” and adding in its place “$32”.</AMDPAR>
                </REGTEXT>
                <HD SOURCE="HD1">
                    <E T="0742">Wage and Hour Division</E>
                </HD>
                <PART>
                    <HD SOURCE="HED">PART 500—MIGRANT AND SEASONAL AGRICULTURAL WORKER PROTECTION</HD>
                </PART>
                <REGTEXT TITLE="29" PART="500">
                    <AMDPAR>12. The authority citation for part 500 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> Pub. L. 97-470, 96 Stat. 2583 (29 U.S.C. 1801-1872); Secretary's Order No. 01-2014 (Dec. 19, 2014), 79 FR 77527 (Dec. 24, 2014); 28 U.S.C. 2461 note (Federal Civil Penalties Inflation Adjustment Act of 1990); and Pub. L. 114-74, 129 Stat 584.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 500.1</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="29" PART="500">
                    <AMDPAR>13. In § 500.1, amend paragraph (e) by removing “$2,951” and adding in its place “$3,047”.</AMDPAR>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 501—ENFORCEMENT OF CONTRACTUAL OBLIGATIONS FOR TEMPORARY ALIEN AGRICULTURAL WORKERS ADMITTED UNDER SECTION 218 OF THE IMMIGRATION AND NATIONALITY ACT</HD>
                </PART>
                <REGTEXT TITLE="29" PART="501">
                    <AMDPAR>14. The authority citation for part 501 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 8 U.S.C. 1101(a)(15)(H)(ii)(a), 1184(c), and 1188; 28 U.S.C. 2461 note; and sec. 701, Pub. L. 114-74, 129 Stat. 584.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 501.19</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="29" PART="501">
                    <AMDPAR>15. In the following table, for each paragraph indicated in the left column, remove the dollar amount indicated in the middle column from wherever it appears in the paragraph and add in its place the dollar amount indicated in the right column.</AMDPAR>
                    <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s100,12,12">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1">Paragraph</CHED>
                            <CHED H="1">Remove</CHED>
                            <CHED H="1">Add</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">§ 501.19(c) introductory text</ENT>
                            <ENT>$2,045</ENT>
                            <ENT>$2,111</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 501.19(c)(1)</ENT>
                            <ENT>6,881</ENT>
                            <ENT>7,104</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 501.19(c)(2)</ENT>
                            <ENT>68,129</ENT>
                            <ENT>70,337</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 501.19(c)(3)</ENT>
                            <ENT>136,258</ENT>
                            <ENT>140,674</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 501.19(d)</ENT>
                            <ENT>6,881</ENT>
                            <ENT>7,104</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 501.19(e)</ENT>
                            <ENT>20,439</ENT>
                            <ENT>21,101</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 501.19(f)</ENT>
                            <ENT>20,439</ENT>
                            <ENT>21,101</ENT>
                        </ROW>
                    </GPOTABLE>
                </REGTEXT>
                <PART>
                    <PRTPAGE P="1816"/>
                    <HD SOURCE="HED">PART 503—ENFORCEMENT OF OBLIGATIONS FOR TEMPORARY NONIMMIGRANT NON-AGRICULTURAL WORKERS DESCRIBED IN THE IMMIGRATION AND NATIONALITY ACT</HD>
                </PART>
                <REGTEXT TITLE="29" PART="503">
                    <AMDPAR>16. The authority citation for part 503 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 8 U.S.C. 1101(a)(15)(H)(ii)(b); 8 U.S.C. 1184; 8 CFR 214.2(h); 28 U.S.C. 2461 note (Federal Civil Penalties Inflation Adjustment Act of 1990); Pub. L. 114-74 at sec. 701.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 503.23</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="29" PART="503">
                    <AMDPAR>17. In the following table, for each paragraph indicated in the left column, remove the dollar amount indicated in the middle column from wherever it appears in the paragraph, and add in its place the dollar amount indicated in the right column:</AMDPAR>
                    <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s100,12,12">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1">Paragraph</CHED>
                            <CHED H="1">Remove</CHED>
                            <CHED H="1">Add</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">§ 503.23(b)</ENT>
                            <ENT>$14,960</ENT>
                            <ENT>$15,445</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 503.23(c)</ENT>
                            <ENT>14,960</ENT>
                            <ENT>15,445</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 503.23(d)</ENT>
                            <ENT>14,960</ENT>
                            <ENT>15,445</ENT>
                        </ROW>
                    </GPOTABLE>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 530—EMPLOYMENT OF HOMEWORKERS IN CERTAIN INDUSTRIES</HD>
                </PART>
                <REGTEXT TITLE="29" PART="530">
                    <AMDPAR>18. The authority citation for part 530 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> Sec. 11, 52 Stat. 1066 (29 U.S.C. 211) as amended by sec. 9, 63 Stat. 910 (29 U.S.C. 211(d)); Secretary's Order No. 01-2014 (Dec. 19, 2014), 79 FR 77527 (Dec. 24, 2014); 28 U.S.C. 2461 note (Federal Civil Penalties Inflation Adjustment Act of 1990); Pub. L. 114-74 at sec. 701, 129 Stat 584.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="29" PART="530">
                    <AMDPAR>19. In § 530.302:</AMDPAR>
                    <AMDPAR>a. Amend paragraph (a) by removing “$1,240” and adding in its place “$1,280;” and</AMDPAR>
                    <AMDPAR>b. Revise paragraph (b).</AMDPAR>
                    <P>The revision reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 530.302</SECTNO>
                        <SUBJECT>Amounts of civil penalties.</SUBJECT>
                        <STARS/>
                        <P>(b) The amount of civil money penalties shall be determined per affected homeworker within the limits set forth in the following schedule, except that no penalty shall be assessed in the case of violations which are deemed to be de minimis in nature:</P>
                        <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s100,12,12,12">
                            <TTITLE>
                                Table 1 to Paragraph 
                                <E T="01">(b)</E>
                            </TTITLE>
                            <BOXHD>
                                <CHED H="1">Nature of violation</CHED>
                                <CHED H="1">Penalty per affected homeworker</CHED>
                                <CHED H="2">Minor</CHED>
                                <CHED H="2">Substantial</CHED>
                                <CHED H="2">
                                    Repeated,
                                    <LI>intentional</LI>
                                    <LI>or knowing</LI>
                                </CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">Recordkeeping</ENT>
                                <ENT>$25-257</ENT>
                                <ENT>$257-512</ENT>
                                <ENT>$512-1,280</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Monetary violations</ENT>
                                <ENT>25-257</ENT>
                                <ENT>257-512</ENT>
                                <ENT/>
                            </ROW>
                            <ROW>
                                <ENT I="01">Employment of homeworkers without a certificate</ENT>
                                <ENT/>
                                <ENT>257-512</ENT>
                                <ENT>512-1,280</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Other violations of statutes, regulations or employer assurances</ENT>
                                <ENT>25-257</ENT>
                                <ENT>257-512</ENT>
                                <ENT>512-1,280</ENT>
                            </ROW>
                        </GPOTABLE>
                    </SECTION>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 570—CHILD LABOR REGULATIONS, ORDERS AND STATEMENTS OF INTERPRETATION</HD>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart G—General Statements of Interpretation of the Child Labor Provisions of the Fair Labor Standards Act of 1938, as Amended</HD>
                    </SUBPART>
                </PART>
                <REGTEXT TITLE="29" PART="570">
                    <AMDPAR>20. The authority citation for subpart G of part 570 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 52 Stat. 1060-1069, as amended; 29 U.S.C. 201-219; 28 U.S.C. 2461 note (Federal Civil Penalties Inflation Adjustment Act of 1990); Pub. L. 114-74 at sec. 701.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 570.140</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="29" PART="570">
                    <AMDPAR>21. In § 570.140, amend paragraph (b)(1) by removing “$15,138” and adding in its place “$15,629” and paragraph (b)(2) by removing “$68,801” and adding in its place “$71,031”.</AMDPAR>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 578—TIP RETENTION, MINIMUM WAGE, AND OVERTIME VIOLATIONS—CIVIL MONEY PENALTIES</HD>
                </PART>
                <REGTEXT TITLE="29" PART="578">
                    <AMDPAR>22. The authority citation for part 578 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 29 U.S.C. 216(e), as amended by sec. 9, Pub. L. 101-157, 103 Stat. 938, sec. 3103, Pub. L. 101-508, 104 Stat. 1388-29, sec. 302(a), Pub. L. 110-233, 122 Stat. 920, and sec. 1201, Div. S., Tit. XII, Pub. L. 115-141, 132 Stat. 348; Pub. L. 101-410, 104 Stat. 890 (28 U.S.C. 2461 note), as amended by sec. 31001(s), Pub. L. 104-134, 110 Stat. 1321-358, 1321-373, and sec. 701, Pub. L. 114-74, 129 Stat 584.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 578.3</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="29" PART="578">
                    <AMDPAR>23. In § 578.3, amend paragraph (a)(1) by removing “$1,330” and adding in its place “$1,373” and paragraph (a)(2) by removing “$2,374” and adding in its place “$2,451”.</AMDPAR>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 579—CHILD LABOR VIOLATIONS—CIVIL MONEY PENALTIES</HD>
                </PART>
                <REGTEXT TITLE="29" PART="579">
                    <AMDPAR>24. The authority citation for part 579 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 29 U.S.C. 203(m), (l), 211, 212, 213(c), 216; Reorg. Plan No. 6 of 1950, 64 Stat. 1263, 5 U.S.C. App; secs. 25, 29, 88 Stat. 72, 76; Secretary of Labor's Order No. 01-2014 (Dec. 19, 2014), 79 FR 77527 (Dec. 24, 2014); 28 U.S.C. 2461 Note.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 579.1</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="29" PART="579">
                    <AMDPAR>25. In the following table, for each paragraph indicated in the left column, remove the dollar amount indicated in the middle column from wherever it appears in the paragraph and add in its place the dollar amount indicated in the right column.</AMDPAR>
                    <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s100,12,12">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1">Paragraph</CHED>
                            <CHED H="1">Remove</CHED>
                            <CHED H="1">Add</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">§ 579.1(a)(1)(i)(A)</ENT>
                            <ENT>$15,138</ENT>
                            <ENT>$15,629</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 579.1(a)(1)(i)(B)</ENT>
                            <ENT>68,801</ENT>
                            <ENT>71,031</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="1817"/>
                            <ENT I="01">§ 579.1(a)(2)(i)</ENT>
                            <ENT>2,374</ENT>
                            <ENT>2,451</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 579.1(a)(2)(ii)</ENT>
                            <ENT>1,330</ENT>
                            <ENT>1,373</ENT>
                        </ROW>
                    </GPOTABLE>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 801—APPLICATION OF THE EMPLOYEE POLYGRAPH PROTECTION ACT OF 1988</HD>
                </PART>
                <REGTEXT TITLE="29" PART="801">
                    <AMDPAR>26. The authority citation for part 801 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> Pub. L. 100-347, 102 Stat. 646, 29 U.S.C. 2001-2009; 28 U.S.C. 2461 note (Federal Civil Penalties Inflation Adjustment Act of 1990); Pub. L. 114-74 at sec. 701, 129 Stat 584.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 801.42</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="29" PART="801">
                    <AMDPAR>27. In § 801.42, amend paragraph (a) introductory text by removing “$24,793” and adding in its place “$25,597”.</AMDPAR>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 810—HIGH-WAGE COMPONENTS OF THE LABOR VALUE CONTENT REQUIREMENTS UNDER THE UNITED STATES-MEXICO-CANADA AGREEMENT IMPLEMENTATION ACT</HD>
                </PART>
                <REGTEXT TITLE="29" PART="810">
                    <AMDPAR>28. The authority citation for part 810 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 19 U.S.C. 1508(b)(4) and 19 U.S.C. 4535(b); 28 U.S.C. 2461 note (Federal Civil Penalties Inflation Adjustment Act of 1990); and Pub. L. 114-74 at sec. 701.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 810.800</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="29" PART="810">
                    <AMDPAR>29. In § 810.800, amend paragraph (c)(3)(i) by removing “$57,224” and adding in its place “$59,079”.</AMDPAR>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 825—THE FAMILY AND MEDICAL LEAVE ACT OF 1993</HD>
                </PART>
                <REGTEXT TITLE="29" PART="825">
                    <AMDPAR>30. The authority citation for part 825 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 29 U.S.C. 2654; 28 U.S.C. 2461 note (Federal Civil Penalties Inflation Adjustment Act of 1990); and Pub. L. 114-74 at sec. 701.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 825.300</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="29" PART="825">
                    <AMDPAR>31. In § 825.300, amend paragraph (a)(1) by removing “$204” and adding in its place “$211”.</AMDPAR>
                </REGTEXT>
                <HD SOURCE="HD1">
                    <E T="0742">OCCUPATIONAL SAFETY AND HEALTH ADMINISTRATION</E>
                </HD>
                <PART>
                    <HD SOURCE="HED">PART 1903—INSPECTIONS, CITATIONS, AND PROPOSED PENALTIES</HD>
                </PART>
                <REGTEXT TITLE="29" PART="1903">
                    <AMDPAR>32. The authority citation for part 1903 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> Secs. 8 and 9 of the Occupational Safety and Health Act of 1970 (29 U.S.C. 657, 658); 5 U.S.C. 553; 28 U.S.C. 2461 note (Federal Civil Penalties Inflation Adjustment Act of 1990), as amended by Section 701, Pub. L. 114-74; Secretary of Labor's Order No. 1-2012 (77 FR 3912, Jan. 25, 2012).</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 1903.15</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="29" PART="1903">
                    <AMDPAR>33. In the following table, for each paragraph indicated in the left column, remove the dollar amount or date indicated in the middle column from wherever it appears in the paragraph and add in its place the dollar amount or date indicated in the right column.</AMDPAR>
                    <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s100,r100,xs100">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1">Paragraph</CHED>
                            <CHED H="1">Remove</CHED>
                            <CHED H="1">Add</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">§ 1903.15(d) introductory text</ENT>
                            <ENT>January 15, 2023</ENT>
                            <ENT>January 15, 2024.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 1903.15(d)(1)</ENT>
                            <ENT>$11,162</ENT>
                            <ENT>$11,524.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 1903.15(d)(1)</ENT>
                            <ENT>156,259</ENT>
                            <ENT>161,323.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 1903.15(d)(2)</ENT>
                            <ENT>156,259</ENT>
                            <ENT>161,323.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 1903.15(d)(3)</ENT>
                            <ENT>15,625</ENT>
                            <ENT>16,131.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 1903.15(d)(4)</ENT>
                            <ENT>15,625</ENT>
                            <ENT>16,131.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 1903.15(d)(5)</ENT>
                            <ENT>15,625</ENT>
                            <ENT>16,131.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 1903.15(d)(6)</ENT>
                            <ENT>15,625</ENT>
                            <ENT>16,131.</ENT>
                        </ROW>
                    </GPOTABLE>
                </REGTEXT>
                <HD SOURCE="HD1">
                    <E T="0742">Mine Safety and Health Administration</E>
                </HD>
                <TITLE>Title 30—Mineral Resources</TITLE>
                <PART>
                    <HD SOURCE="HED">PART 100—CRITERIA AND PROCEDURES FOR PROPOSED ASSESSMENT OF CIVIL PENALTIES</HD>
                </PART>
                <REGTEXT TITLE="30" PART="100">
                    <AMDPAR>34. The authority citation for part 100 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 5 U.S.C. 301; 30 U.S.C. 815, 820, 957; 28 U.S.C. 2461 note (Federal Civil Penalties Inflation Adjustment Act of 1990); Pub. L. 114-74 at sec. 701.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="30" PART="100">
                    <AMDPAR>35. In § 100.3:</AMDPAR>
                    <AMDPAR>a. Amend paragraph (a)(1) introductory text by removing “$85,580” and adding in its place “$88,354”; and</AMDPAR>
                    <AMDPAR>b. By revising table 14 to paragraph (g).</AMDPAR>
                    <P>The revision reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 100.3</SECTNO>
                        <SUBJECT>Determination of penalty amount; regular assessment.</SUBJECT>
                        <STARS/>
                        <P>(g) * * *</P>
                        <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s25,12">
                            <TTITLE>
                                Table 14 to Paragraph 
                                <E T="01">(g)</E>
                                —Penalty Conversion Table
                            </TTITLE>
                            <BOXHD>
                                <CHED H="1">Points</CHED>
                                <CHED H="1">
                                    Penalty
                                    <LI>($)</LI>
                                </CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">60 or fewer</ENT>
                                <ENT>$164</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">61</ENT>
                                <ENT>179</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">62</ENT>
                                <ENT>192</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">63</ENT>
                                <ENT>210</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">64</ENT>
                                <ENT>227</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">65</ENT>
                                <ENT>246</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">66</ENT>
                                <ENT>266</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">67</ENT>
                                <ENT>289</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">68</ENT>
                                <ENT>312</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">69</ENT>
                                <ENT>339</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">70</ENT>
                                <ENT>365</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">71</ENT>
                                <ENT>397</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">72</ENT>
                                <ENT>432</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">73</ENT>
                                <ENT>468</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">74</ENT>
                                <ENT>504</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">75</ENT>
                                <ENT>547</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">76</ENT>
                                <ENT>595</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">77</ENT>
                                <ENT>641</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">78</ENT>
                                <ENT>696</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">79</ENT>
                                <ENT>755</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">80</ENT>
                                <ENT>818</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">81</ENT>
                                <ENT>886</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">82</ENT>
                                <ENT>957</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">83</ENT>
                                <ENT>1,039</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">84</ENT>
                                <ENT>1,124</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">85</ENT>
                                <ENT>1,220</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">86</ENT>
                                <ENT>1,321</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">87</ENT>
                                <ENT>1,430</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">88</ENT>
                                <ENT>1,550</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">89</ENT>
                                <ENT>1,679</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">90</ENT>
                                <ENT>1,819</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">91</ENT>
                                <ENT>1,970</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">92</ENT>
                                <ENT>2,132</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">93</ENT>
                                <ENT>2,311</ENT>
                            </ROW>
                            <ROW>
                                <PRTPAGE P="1818"/>
                                <ENT I="01">94</ENT>
                                <ENT>2,504</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">95</ENT>
                                <ENT>2,712</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">96</ENT>
                                <ENT>2,938</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">97</ENT>
                                <ENT>3,180</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">98</ENT>
                                <ENT>3,448</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">99</ENT>
                                <ENT>3,735</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">100</ENT>
                                <ENT>4,047</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">101</ENT>
                                <ENT>4,383</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">102</ENT>
                                <ENT>4,748</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">103</ENT>
                                <ENT>5,143</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">104</ENT>
                                <ENT>5,571</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">105</ENT>
                                <ENT>6,037</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">106</ENT>
                                <ENT>6,538</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">107</ENT>
                                <ENT>7,083</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">108</ENT>
                                <ENT>7,673</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">109</ENT>
                                <ENT>8,313</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">110</ENT>
                                <ENT>9,005</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">111</ENT>
                                <ENT>9,752</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">112</ENT>
                                <ENT>10,567</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">113</ENT>
                                <ENT>11,447</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">114</ENT>
                                <ENT>12,401</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">115</ENT>
                                <ENT>13,433</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">116</ENT>
                                <ENT>14,551</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">117</ENT>
                                <ENT>15,765</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">118</ENT>
                                <ENT>17,077</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">119</ENT>
                                <ENT>18,500</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">120</ENT>
                                <ENT>20,039</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">121</ENT>
                                <ENT>21,711</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">122</ENT>
                                <ENT>23,515</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">123</ENT>
                                <ENT>25,477</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">124</ENT>
                                <ENT>27,599</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">125</ENT>
                                <ENT>29,893</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">126</ENT>
                                <ENT>32,386</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">127</ENT>
                                <ENT>35,084</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">128</ENT>
                                <ENT>38,005</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">129</ENT>
                                <ENT>41,171</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">130</ENT>
                                <ENT>44,601</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">131</ENT>
                                <ENT>48,316</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">132</ENT>
                                <ENT>52,338</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">133</ENT>
                                <ENT>56,698</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">134</ENT>
                                <ENT>61,221</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">135</ENT>
                                <ENT>65,741</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">136</ENT>
                                <ENT>70,266</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">137</ENT>
                                <ENT>74,785</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">138</ENT>
                                <ENT>79,309</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">139</ENT>
                                <ENT>83,830</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">140 or more</ENT>
                                <ENT>88,354</ENT>
                            </ROW>
                        </GPOTABLE>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§§ 100.4 and 100.5</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="30" PART="100">
                    <AMDPAR>36. In the following table, for each paragraph indicated in the left column, remove the dollar amount indicated in the middle column from wherever it appears in the paragraph, and add in its place the dollar amount indicated in the right column.</AMDPAR>
                    <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s100,12,12">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1">Paragraph</CHED>
                            <CHED H="1">Remove</CHED>
                            <CHED H="1">Add</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">§ 100.4(a)</ENT>
                            <ENT>$2,853</ENT>
                            <ENT>$2,945</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 100.4(b)</ENT>
                            <ENT>5,703</ENT>
                            <ENT>5,888</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 100.4(c) introductory text</ENT>
                            <ENT>7,133</ENT>
                            <ENT>7,364</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 100.4(c) introductory text</ENT>
                            <ENT>85,580</ENT>
                            <ENT>88,354</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 100.5(c)</ENT>
                            <ENT>9,271</ENT>
                            <ENT>9,571</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 100.5(d)</ENT>
                            <ENT>391</ENT>
                            <ENT>404</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 100.5(e)</ENT>
                            <ENT>313,790</ENT>
                            <ENT>323,960</ENT>
                        </ROW>
                    </GPOTABLE>
                </REGTEXT>
                <TITLE>Title 41—Public Contracts and Property Management</TITLE>
                <PART>
                    <HD SOURCE="HED">PART 50-201—GENERAL REGULATIONS</HD>
                </PART>
                <REGTEXT TITLE="41" PART="50-201">
                    <AMDPAR>37. The authority citation for part 50-201 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> Sec. 4, 49 Stat. 2038; 41 U.S.C. 38. Interpret or apply sec. 6, 49 Stat. 2038, as amended; 41 U.S.C. 40; 108 Stat. 7201; 28 U.S.C. 2461 note (Federal Civil Penalties Inflation Adjustment Act of 1990); Pub. L. 114-74 at sec. 701, 129 Stat 584.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 50-201.3</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="41" PART="50-201">
                    <AMDPAR>38. In § 50-201.3, amend paragraph (e) by removing “$31” and adding in its place “$32”.</AMDPAR>
                </REGTEXT>
                <SIG>
                    <P>Signed in Washington, DC.</P>
                    <NAME>Julie A. Su, </NAME>
                    <TITLE>Acting Secretary, U.S. Department of Labor.</TITLE>
                </SIG>
                <NOTE>
                    <HD SOURCE="HED">Note:</HD>
                    <P>The following Appendix will not appear in the Code of Federal Regulations.</P>
                </NOTE>
                <GPOTABLE COLS="8" OPTS="L2,tp0,p7,7/8,i1" CDEF="xs30,r25,r60,r50,12,r20,12,r20">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Agency</CHED>
                        <CHED H="1">Law</CHED>
                        <CHED H="1">Name/description</CHED>
                        <CHED H="1">CFR citation</CHED>
                        <CHED H="1">2023</CHED>
                        <CHED H="2">
                            Min penalty
                            <LI>(rounded to</LI>
                            <LI>nearest dollar)</LI>
                        </CHED>
                        <CHED H="2">
                            Max penalty
                            <LI>(rounded to</LI>
                            <LI>nearest</LI>
                            <LI>dollar)</LI>
                        </CHED>
                        <CHED H="1">2024</CHED>
                        <CHED H="2">
                            Min penalty
                            <LI>(rounded to</LI>
                            <LI>nearest dollar)</LI>
                        </CHED>
                        <CHED H="2">
                            Max penalty
                            <LI>(rounded to</LI>
                            <LI>nearest</LI>
                            <LI>dollar)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">MSHA</ENT>
                        <ENT>Federal Mine Safety &amp; Health Act of 1977</ENT>
                        <ENT>Regular Assessment</ENT>
                        <ENT>30 CFR 100.3(a)</ENT>
                        <ENT/>
                        <ENT>$85,580</ENT>
                        <ENT/>
                        <ENT>$88,354.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MSHA</ENT>
                        <ENT>Federal Mine Safety &amp; Health Act of 1977</ENT>
                        <ENT>Penalty Conversion Table</ENT>
                        <ENT>30 CFR 100.3(g)</ENT>
                        <ENT>$159</ENT>
                        <ENT>$85,580</ENT>
                        <ENT>$164</ENT>
                        <ENT>$88,354.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MSHA</ENT>
                        <ENT>Federal Mine Safety &amp; Health Act of 1977</ENT>
                        <ENT>Minimum Penalty for any citation or order issued under 104(d)(1) of the Mine Act</ENT>
                        <ENT>30 CFR 100.4(a)</ENT>
                        <ENT>2,853</ENT>
                        <ENT/>
                        <ENT>2,945</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MSHA</ENT>
                        <ENT>Federal Mine Safety &amp; Health Act of 1977</ENT>
                        <ENT>Minimum penalty for any citation or order issued under 104(d)(2) of the Mine Act</ENT>
                        <ENT>30 CFR 100.4(b)</ENT>
                        <ENT>5,703</ENT>
                        <ENT/>
                        <ENT>5,888</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MSHA</ENT>
                        <ENT>Federal Mine Safety &amp; Health Act of 1977</ENT>
                        <ENT>Penalty for failure to provide timely notification to the Secretary under 103(j) of the Mine Act</ENT>
                        <ENT>30 CFR 100.4(c)</ENT>
                        <ENT>7,133</ENT>
                        <ENT>$85,580</ENT>
                        <ENT>7,364</ENT>
                        <ENT>$88,354.</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="1819"/>
                        <ENT I="01">MSHA</ENT>
                        <ENT>Federal Mine Safety &amp; Health Act of 1977</ENT>
                        <ENT>Any operator who fails to correct a violation for which a citation or order was issued under 104(a) of the Mine Act</ENT>
                        <ENT>30 CFR 100.5(c)</ENT>
                        <ENT/>
                        <ENT>$9,271</ENT>
                        <ENT/>
                        <ENT>$9,571.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MSHA</ENT>
                        <ENT>Federal Mine Safety &amp; Health Act of 1977</ENT>
                        <ENT>Violation of mandatory safety standards related to smoking standards</ENT>
                        <ENT>30 CFR 100.5(d)</ENT>
                        <ENT/>
                        <ENT>$391</ENT>
                        <ENT/>
                        <ENT>$404.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MSHA</ENT>
                        <ENT>Federal Mine Safety &amp; Health Act of 1977</ENT>
                        <ENT>Flagrant violations under 110(b)(2) of the Mine Act</ENT>
                        <ENT>30 CFR 100.5(e)</ENT>
                        <ENT/>
                        <ENT>$313,790</ENT>
                        <ENT/>
                        <ENT>$323,960.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EBSA</ENT>
                        <ENT>Employee Retirement Income Security Act</ENT>
                        <ENT>
                            Section 209(b): Per plan year for failure to furnish reports (
                            <E T="03">e.g.,</E>
                             pension benefit statements) to certain former employees or maintain employee records—each employee a separate violation
                        </ENT>
                        <ENT>29 CFR 2575.1-3</ENT>
                        <ENT/>
                        <ENT>$36</ENT>
                        <ENT/>
                        <ENT>$37.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EBSA</ENT>
                        <ENT>Employee Retirement Income Security Act</ENT>
                        <ENT>Section 502 (c)(2)—Per day for failure/refusal to properly file plan annual report</ENT>
                        <ENT>29 CFR 2575.1-3</ENT>
                        <ENT/>
                        <ENT>$2,586</ENT>
                        <ENT/>
                        <ENT>$2,670.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EBSA</ENT>
                        <ENT>Employee Retirement Income Security Act</ENT>
                        <ENT>Section 502 (c)(4)—Per day for failure to disclose certain documents upon request under Section 101(k) and (l); failure to furnish notices under Sections 101(j) and 514(e)(3)—each statutory recipient a separate violation</ENT>
                        <ENT>29 CFR 2575.1-3</ENT>
                        <ENT/>
                        <ENT>$2,046</ENT>
                        <ENT/>
                        <ENT>$2,112.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EBSA</ENT>
                        <ENT>Employee Retirement Income Security Act</ENT>
                        <ENT>Section 502 (c)(5)—Per day for each failure to file annual report for Multiple Employer Welfare Arrangements (MEWAs) under Section 101(g)</ENT>
                        <ENT>29 CFR 2575.1-3</ENT>
                        <ENT/>
                        <ENT>$1,881</ENT>
                        <ENT/>
                        <ENT>$1,942.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EBSA</ENT>
                        <ENT>Employee Retirement Income Security Act</ENT>
                        <ENT>Section 502 (c)(6)—Per day for each failure to provide Secretary of Labor requested documentation not to exceed a per-request maximum</ENT>
                        <ENT>29 CFR 2575.1-3</ENT>
                        <ENT/>
                        <ENT>$184 per day, not to exceed $1,846 per request</ENT>
                        <ENT/>
                        <ENT>$190 per day, not to exceed $1,906 per request.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EBSA</ENT>
                        <ENT>Employee Retirement Income Security Act</ENT>
                        <ENT>Section 502 (c)(7)—Per day for each failure to provide notices of blackout periods and of right to divest employer securities—each statutory recipient a separate violation</ENT>
                        <ENT>29 CFR 2575.1-3</ENT>
                        <ENT/>
                        <ENT>$164</ENT>
                        <ENT/>
                        <ENT>$169.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EBSA</ENT>
                        <ENT>Employee Retirement Income Security Act</ENT>
                        <ENT>Section 502 (c)(8)—Per each failure by an endangered status multiemployer plan to adopt a funding improvement plan or meet benchmarks; or failure of a critical status multiemployer plan to adopt a rehabilitation plan</ENT>
                        <ENT>29 CFR 2575.1-3</ENT>
                        <ENT/>
                        <ENT>$1,624</ENT>
                        <ENT/>
                        <ENT>$1,677.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EBSA</ENT>
                        <ENT>Employee Retirement Income Security Act</ENT>
                        <ENT>Section 502(c)(9)(A)—Per day for each failure by an employer to inform employees of CHIP coverage opportunities under Section 701(f)(3)(B)(i)(l)—each employee a separate violation</ENT>
                        <ENT>29 CFR 2575.1-3</ENT>
                        <ENT/>
                        <ENT>$137</ENT>
                        <ENT/>
                        <ENT>$141.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EBSA</ENT>
                        <ENT>Employee Retirement Income Security Act</ENT>
                        <ENT>Section 502(c)(9)(B)—Per day for each failure by a plan to timely provide to any State information required to be disclosed under Section 701(f)(3)(B)(ii), as added by CHIP regarding coverage coordination—each participant/beneficiary a separate violation</ENT>
                        <ENT>29 CFR 2575.1-3</ENT>
                        <ENT/>
                        <ENT>$137</ENT>
                        <ENT/>
                        <ENT>$141.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EBSA</ENT>
                        <ENT>Employee Retirement Income Security Act</ENT>
                        <ENT>Section 502(c)(10)—Failure by any plan sponsor of group health plan, or any health insurance issuer offering health insurance coverage in connection with the plan, to meet the requirements of Sections 702(a)(1)(F), (b)(3), (c) or (d); or Section 701; or Section 702(b)(1) with respect to genetic information—daily per participant and beneficiary during non-compliance period</ENT>
                        <ENT>29 CFR 2575.1-3</ENT>
                        <ENT/>
                        <ENT>$137</ENT>
                        <ENT/>
                        <ENT>$141.</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="1820"/>
                        <ENT I="01">EBSA</ENT>
                        <ENT>Employee Retirement Income Security Act</ENT>
                        <ENT>Section 502(c)(10)—uncorrected de minimis violation</ENT>
                        <ENT>29 CFR 2575.1-3</ENT>
                        <ENT>3,439</ENT>
                        <ENT/>
                        <ENT>3,550</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EBSA</ENT>
                        <ENT>Employee Retirement Income Security Act</ENT>
                        <ENT>Section 502(c)(10)—uncorrected violations that are not de minimis</ENT>
                        <ENT>29 CFR 2575.1-3</ENT>
                        <ENT>20,641</ENT>
                        <ENT/>
                        <ENT>21,310</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EBSA</ENT>
                        <ENT>Employee Retirement Income Security Act</ENT>
                        <ENT>Section 502(c)(10)—unintentional failure maximum cap</ENT>
                        <ENT>29 CFR 2575.1-3</ENT>
                        <ENT/>
                        <ENT>$688,012</ENT>
                        <ENT/>
                        <ENT>$710,310.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EBSA</ENT>
                        <ENT>Employee Retirement Income Security Act</ENT>
                        <ENT>Section 502(c)(12)—Per day for each failure of a CSEC plan in restoration status to adopt a restoration plan</ENT>
                        <ENT>29CFR 2575.1-3</ENT>
                        <ENT/>
                        <ENT>$126</ENT>
                        <ENT/>
                        <ENT>$130.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EBSA</ENT>
                        <ENT>Employee Retirement Income Security Act</ENT>
                        <ENT>Section 502 (m)—Failure of fiduciary to make a proper distribution from a defined benefit plan under section 206(e) of ERISA</ENT>
                        <ENT>29 CFR 2575.1-3</ENT>
                        <ENT/>
                        <ENT>$19,933</ENT>
                        <ENT/>
                        <ENT>$20,579.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EBSA</ENT>
                        <ENT>Employee Retirement Income Security Act</ENT>
                        <ENT>Failure to provide Summary of Benefits Coverage under PHS Act section 2715(f), as incorporated in ERISA section 715 and 29 CFR 2590.715-2715(e)</ENT>
                        <ENT>29 CFR 2575.1-3</ENT>
                        <ENT/>
                        <ENT>$1,362</ENT>
                        <ENT/>
                        <ENT>$1,406.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OSHA</ENT>
                        <ENT>Occupational Safety and Health Act</ENT>
                        <ENT>Serious Violation</ENT>
                        <ENT>29 CFR 1903.15(d)(3)</ENT>
                        <ENT/>
                        <ENT>$15,625</ENT>
                        <ENT/>
                        <ENT>$16,131.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OSHA</ENT>
                        <ENT>Occupational Safety and Health Act</ENT>
                        <ENT>Other-Than-Serious</ENT>
                        <ENT>29 CFR 1903.15(d)(4)</ENT>
                        <ENT/>
                        <ENT>$15,625</ENT>
                        <ENT/>
                        <ENT>$16,131.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OSHA</ENT>
                        <ENT>Occupational Safety and Health Act</ENT>
                        <ENT>Willful</ENT>
                        <ENT>29 CFR 1903.15(d)(1)</ENT>
                        <ENT>11,162</ENT>
                        <ENT>$156,259</ENT>
                        <ENT>11,524</ENT>
                        <ENT>$161,323.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OSHA</ENT>
                        <ENT>Occupational Safety and Health Act</ENT>
                        <ENT>Repeated</ENT>
                        <ENT>29 CFR 1903.15(d)(2)</ENT>
                        <ENT/>
                        <ENT>$156,259</ENT>
                        <ENT/>
                        <ENT>$161,323.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OSHA</ENT>
                        <ENT>Occupational Safety and Health Act</ENT>
                        <ENT>Posting Requirement</ENT>
                        <ENT>29 CFR 1903.15(d)(6)</ENT>
                        <ENT/>
                        <ENT>$15,625</ENT>
                        <ENT/>
                        <ENT>$16,131.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OSHA</ENT>
                        <ENT>Occupational Safety and Health Act</ENT>
                        <ENT>Failure to Abate</ENT>
                        <ENT>29 CFR 1903.15(d)(5)</ENT>
                        <ENT/>
                        <ENT>$15,625 per day</ENT>
                        <ENT/>
                        <ENT>$16,131 per day.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>Family and Medical Leave Act</ENT>
                        <ENT>FMLA</ENT>
                        <ENT>29 CFR 825.300(a)(1)</ENT>
                        <ENT/>
                        <ENT>$204</ENT>
                        <ENT/>
                        <ENT>$211.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>Fair Labor Standards Act</ENT>
                        <ENT>FLSA</ENT>
                        <ENT>29 CFR 578.3(a)(1)</ENT>
                        <ENT/>
                        <ENT>$1,330</ENT>
                        <ENT/>
                        <ENT>$1,373.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>Fair Labor Standards Act</ENT>
                        <ENT>FLSA</ENT>
                        <ENT>29 CFR 578.3(a)(2)</ENT>
                        <ENT/>
                        <ENT>$2,374</ENT>
                        <ENT/>
                        <ENT>$2,451.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>Fair Labor Standards Act</ENT>
                        <ENT>Child Labor</ENT>
                        <ENT>29 CFR 579.1(a)(2)(i)</ENT>
                        <ENT/>
                        <ENT>$2,374</ENT>
                        <ENT/>
                        <ENT>$2,451.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>Fair Labor Standards Act</ENT>
                        <ENT>Child Labor</ENT>
                        <ENT>29 CFR 579.1(a)(2)(ii)</ENT>
                        <ENT/>
                        <ENT>$1,330</ENT>
                        <ENT/>
                        <ENT>$1,373.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>Fair Labor Standards Act</ENT>
                        <ENT>Child Labor</ENT>
                        <ENT>29 CFR 570.140(b)(1)</ENT>
                        <ENT/>
                        <ENT>$15,138</ENT>
                        <ENT/>
                        <ENT>$15,629.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>Fair Labor Standards Act</ENT>
                        <ENT>Child Labor</ENT>
                        <ENT>29 CFR 579.1(a)(1)(i)(A)</ENT>
                        <ENT/>
                        <ENT>$15,138</ENT>
                        <ENT/>
                        <ENT>$15,629.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>Fair Labor Standards Act</ENT>
                        <ENT>Child Labor that causes serious injury or death</ENT>
                        <ENT>29 CFR 570.140(b)(2)</ENT>
                        <ENT/>
                        <ENT>$68,801</ENT>
                        <ENT/>
                        <ENT>$71,031.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>Fair Labor Standards Act</ENT>
                        <ENT>Child Labor that causes serious injury or death</ENT>
                        <ENT>29 CFR 579.1(a)(1)(i)(B)</ENT>
                        <ENT/>
                        <ENT>$68,801</ENT>
                        <ENT/>
                        <ENT>$71,031.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>Fair Labor Standards Act</ENT>
                        <ENT>Child Labor willful or repeated that causes serious injury or death (penalty amount doubled)</ENT>
                        <ENT>29 CFR 570.140(b)(2); 29 CFR 579.1(a)(1)(i)(B) Doubled</ENT>
                        <ENT/>
                        <ENT>$137,602</ENT>
                        <ENT/>
                        <ENT>$142,062.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>Migrant and Seasonal Agricultural Worker Protection Act</ENT>
                        <ENT>MSPA</ENT>
                        <ENT>29 CFR 500.1(e)</ENT>
                        <ENT/>
                        <ENT>$2,951</ENT>
                        <ENT/>
                        <ENT>$3,047.</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="1821"/>
                        <ENT I="01">WHD</ENT>
                        <ENT>Immigration &amp; Nationality Act</ENT>
                        <ENT>H1B</ENT>
                        <ENT>20 CFR 655.810(b)(1)</ENT>
                        <ENT/>
                        <ENT>$2,232</ENT>
                        <ENT/>
                        <ENT>$2,304.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>Immigration &amp; Nationality Act</ENT>
                        <ENT>H1B retaliation</ENT>
                        <ENT>20 CFR 655.801(b)</ENT>
                        <ENT/>
                        <ENT>$9,086</ENT>
                        <ENT/>
                        <ENT>$9,380.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>Immigration &amp; Nationality Act</ENT>
                        <ENT>H1B willful or discrimination</ENT>
                        <ENT>20 CFR 655.810(b)(2)</ENT>
                        <ENT/>
                        <ENT>$9,086</ENT>
                        <ENT/>
                        <ENT>$9,380.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>Immigration &amp; Nationality Act</ENT>
                        <ENT>H1B willful that resulted in displacement of a US worker</ENT>
                        <ENT>20 CFR 655.810(b)(3)</ENT>
                        <ENT/>
                        <ENT>$63,600</ENT>
                        <ENT/>
                        <ENT>$65,661.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>Immigration &amp; Nationality Act</ENT>
                        <ENT>D-1</ENT>
                        <ENT>20 CFR 655.620(a)</ENT>
                        <ENT/>
                        <ENT>$11,162</ENT>
                        <ENT/>
                        <ENT>$11,524.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>Contract Work Hours and Safety Standards Act</ENT>
                        <ENT>CWHSSA</ENT>
                        <ENT>29 CFR 5.5(b)(2)</ENT>
                        <ENT/>
                        <ENT>$31</ENT>
                        <ENT/>
                        <ENT>$32.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>Contract Work Hours and Safety Standards Act</ENT>
                        <ENT>CWHSSA</ENT>
                        <ENT>29 CFR 5.8(a)</ENT>
                        <ENT/>
                        <ENT>$31</ENT>
                        <ENT/>
                        <ENT>$32.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>Walsh-Healey Public Contracts Act</ENT>
                        <ENT>Walsh-Healey</ENT>
                        <ENT>41 CFR 50-201.3(e)</ENT>
                        <ENT/>
                        <ENT>$31</ENT>
                        <ENT/>
                        <ENT>$32.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>Employee Polygraph Protection Act</ENT>
                        <ENT>EPPA</ENT>
                        <ENT>29 CFR 801.42(a)</ENT>
                        <ENT/>
                        <ENT>$24,793</ENT>
                        <ENT/>
                        <ENT>$25,597.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>Immigration &amp; Nationality Act</ENT>
                        <ENT>H2A</ENT>
                        <ENT>29 CFR 501.19(c)</ENT>
                        <ENT/>
                        <ENT>$2,045</ENT>
                        <ENT/>
                        <ENT>$2,111.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>Immigration &amp; Nationality Act</ENT>
                        <ENT>H2A willful or discrimination</ENT>
                        <ENT>29 CFR 501.19(c)(1)</ENT>
                        <ENT/>
                        <ENT>$6,881</ENT>
                        <ENT/>
                        <ENT>$7,104.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>Immigration &amp; Nationality Act</ENT>
                        <ENT>H2A Safety or health resulting in serious injury or death</ENT>
                        <ENT>29 CFR 501.19(c)(2)</ENT>
                        <ENT/>
                        <ENT>$68,129</ENT>
                        <ENT/>
                        <ENT>$70,337.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>Immigration &amp; Nationality Act</ENT>
                        <ENT>H2A willful or repeated safety or health resulting in serious injury or death</ENT>
                        <ENT>29 CFR 501.19(c)(3)</ENT>
                        <ENT/>
                        <ENT>$136,258</ENT>
                        <ENT/>
                        <ENT>$140,674.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>Immigration &amp; Nationality Act</ENT>
                        <ENT>H2A failing to cooperate in an investigation</ENT>
                        <ENT>29 CFR 501.19(d)</ENT>
                        <ENT/>
                        <ENT>$6,881</ENT>
                        <ENT/>
                        <ENT>$7,104.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>Immigration &amp; Nationality Act</ENT>
                        <ENT>H2A displacing a US worker</ENT>
                        <ENT>29 CFR 501.19(e)</ENT>
                        <ENT/>
                        <ENT>$20,439</ENT>
                        <ENT/>
                        <ENT>$21,101.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>Immigration &amp; Nationality Act</ENT>
                        <ENT>H2A improperly rejecting a US worker</ENT>
                        <ENT>29 CFR 501.19(f)</ENT>
                        <ENT/>
                        <ENT>$20,439</ENT>
                        <ENT/>
                        <ENT>$21,101.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>Immigration &amp; Nationality Act</ENT>
                        <ENT>H-2B</ENT>
                        <ENT>29 CFR 503.23(b)</ENT>
                        <ENT/>
                        <ENT>$14,960</ENT>
                        <ENT/>
                        <ENT>$15,445.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>Immigration &amp; Nationality Act</ENT>
                        <ENT>H-2B</ENT>
                        <ENT>29 CFR 503.23(c)</ENT>
                        <ENT/>
                        <ENT>$14,960</ENT>
                        <ENT/>
                        <ENT>$15,445.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>Immigration &amp; Nationality Act</ENT>
                        <ENT>H-2B</ENT>
                        <ENT>29 CFR 503.23(d)</ENT>
                        <ENT/>
                        <ENT>$14,960</ENT>
                        <ENT/>
                        <ENT>$15,445.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>Fair Labor Standards Act</ENT>
                        <ENT>Home Worker</ENT>
                        <ENT>29 CFR 530.302(a)</ENT>
                        <ENT/>
                        <ENT>$1,240</ENT>
                        <ENT/>
                        <ENT>$1,280.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>Fair Labor Standards Act</ENT>
                        <ENT>Home Worker</ENT>
                        <ENT>29 CFR 530.302(b)</ENT>
                        <ENT>24</ENT>
                        <ENT>$1,240</ENT>
                        <ENT>25</ENT>
                        <ENT>$1,280.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHD</ENT>
                        <ENT>United States-Mexico-Canada Agreement Implementation Act.</ENT>
                        <ENT>Whistleblower</ENT>
                        <ENT>29 CFR 810.800(c)(3)(i)</ENT>
                        <ENT/>
                        <ENT>$57,224</ENT>
                        <ENT/>
                        <ENT>$59,079.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OWCP</ENT>
                        <ENT>Longshore and Harbor Workers' Compensation Act</ENT>
                        <ENT>Failure to file first report of injury or filing a false statement or misrepresentation in first report</ENT>
                        <ENT>20 CFR 702.204</ENT>
                        <ENT/>
                        <ENT>$28,304</ENT>
                        <ENT/>
                        <ENT>$29,221.</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="1822"/>
                        <ENT I="01">OWCP</ENT>
                        <ENT>Longshore and Harbor Workers' Compensation Act</ENT>
                        <ENT>Failure to report termination of payments</ENT>
                        <ENT>20 CFR 702.236</ENT>
                        <ENT/>
                        <ENT>$345</ENT>
                        <ENT/>
                        <ENT>$356.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OWCP</ENT>
                        <ENT>Longshore and Harbor Workers' Compensation Act</ENT>
                        <ENT>Discrimination against employees who claim compensation or testify in a LHWCA proceeding</ENT>
                        <ENT>20 CFR 702.271(a)(2)</ENT>
                        <ENT>2,830</ENT>
                        <ENT>$14,149</ENT>
                        <ENT>2,922</ENT>
                        <ENT>$14,608.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OWCP</ENT>
                        <ENT>Black Lung Benefits Act</ENT>
                        <ENT>Failure to report termination of payments</ENT>
                        <ENT>20 CFR 725.621 (d)</ENT>
                        <ENT/>
                        <ENT>$1,724</ENT>
                        <ENT/>
                        <ENT>$1,780.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OWCP</ENT>
                        <ENT>Black Lung Benefits Act</ENT>
                        <ENT>Failure to secure payment of benefits for mines with fewer than 25 employees</ENT>
                        <ENT>20 CFR 726.302(c)(2)(i)</ENT>
                        <ENT>169</ENT>
                        <ENT/>
                        <ENT>174</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OWCP</ENT>
                        <ENT>Black Lung Benefits Act</ENT>
                        <ENT>Failure to secure payment of benefits for mines with 25-50 employees</ENT>
                        <ENT>20 CFR 726.302(c)(2)(i)</ENT>
                        <ENT>335</ENT>
                        <ENT/>
                        <ENT>346</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OWCP</ENT>
                        <ENT>Black Lung Benefits Act</ENT>
                        <ENT>Failure to secure payment of benefits for mines with 51-100 employees</ENT>
                        <ENT>20 CFR 726.302(c)(2)(i)</ENT>
                        <ENT>504</ENT>
                        <ENT/>
                        <ENT>520</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OWCP</ENT>
                        <ENT>Black Lung Benefits Act</ENT>
                        <ENT>Failure to secure payment of benefits for mines with more than 100 employees</ENT>
                        <ENT>20 CFR 726.302(c)(2)(i)</ENT>
                        <ENT>670</ENT>
                        <ENT/>
                        <ENT>692</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OWCP</ENT>
                        <ENT>Black Lung Benefits Act</ENT>
                        <ENT>Failure to secure payment of benefits after 10th day of notice</ENT>
                        <ENT>20 CFR 726.302(c)(4)</ENT>
                        <ENT>169</ENT>
                        <ENT/>
                        <ENT>174</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OWCP</ENT>
                        <ENT>Black Lung Benefits Act</ENT>
                        <ENT>Failure to secure payment of benefits for repeat offenders</ENT>
                        <ENT>20 CFR 726.302(c)(5)</ENT>
                        <ENT>504</ENT>
                        <ENT/>
                        <ENT>520</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OWCP</ENT>
                        <ENT>Black Lung Benefits Act</ENT>
                        <ENT>Failure to secure payment of benefits</ENT>
                        <ENT>20 CFR 726.302(c)(5)</ENT>
                        <ENT/>
                        <ENT>$3,446</ENT>
                        <ENT/>
                        <ENT>$3,558.</ENT>
                    </ROW>
                </GPOTABLE>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00253 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4510-HL-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <CFR>40 CFR Parts 9 and 721</CFR>
                <DEPDOC>[EPA-HQ-OPPT-2022-0867; FRL 9655-02-OCSPP]</DEPDOC>
                <RIN>RIN 2070-AL10</RIN>
                <SUBJECT>Per- and Poly-Fluoroalkyl Chemical Substances Designated as Inactive on the TSCA Inventory; Significant New Use Rule</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>Under the Toxic Substances Control Act (TSCA), EPA is finalizing a significant new use rule (SNUR) for 329 per- and poly-fluoroalkyl substances (PFAS) that are designated as inactive on the TSCA Chemical Substance Inventory. PFAS are a group of chemicals that have been used in industry and consumer products since the 1940s because of their useful properties, such as water and stain resistance. Many PFAS break down very slowly and can build up in people, animals, and the environment over time. Exposure at certain levels to specific PFAS can adversely impact human health and other living things. Persons subject to the final SNUR are required to notify EPA at least 90 days before commencing any manufacture (including import) or processing of the chemical substance for a significant new use. Once EPA receives a notification, EPA must review and make an affirmative determination on the notification, and take such action as is required by any such determination before the manufacture (including import) or processing for the significant new use can commence. Such a review will assess whether the new use may present unreasonable risk to health or the environment and ensure that EPA takes appropriate action as required to protect health or the environment.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This final rule is effective March 11, 2024. For purposes of judicial review, this rule shall be promulgated at 1 p.m. (EST) on January 25, 2024.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The docket for this action, identified by docket identification (ID) number EPA-HQ-OPPT-2022-0867, is available online at 
                        <E T="03">https://www.regulations.gov</E>
                         or in person at the Office of Pollution Prevention and Toxics Docket (OPPT Docket) in the Environmental Protection Agency Docket Center (EPA/DC) in Washington, DC. Please review the visitor instructions and additional information about the docket available at 
                        <E T="03">https://www.epa.gov/dockets.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P/>
                    <P>
                        <E T="03">For technical information contact:</E>
                         Bethany Masten, Existing Chemicals Risk Management Division (7404M), Office of Pollution Prevention and Toxics, Environmental Protection Agency, 1200 Pennsylvania Ave. NW, Washington, DC 20460-0001; telephone number: (202) 564-8803; email address: 
                        <E T="03">TSCA_PFAS@epa.gov.</E>
                    </P>
                    <P>
                        <E T="03">For general information contact:</E>
                         The TSCA-Hotline, ABVI-Goodwill, 422 South Clinton Ave., Rochester, NY 14620; telephone number: (202) 554-1404; email address: 
                        <E T="03">TSCA-Hotline@epa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">I. Executive Summary</HD>
                <HD SOURCE="HD2">A. Does this action apply to me?</HD>
                <P>You may be potentially affected by this action if you manufacture (including import), process, or distribute in commerce chemical substances and mixtures. The following list of North American Industrial Classification System (NAICS) codes is not intended to be exhaustive, but rather provides a guide to help readers determine whether this document applies to them. Potentially affected entities may include:</P>
                <P>• NAICS 221210—Natural Gas Distribution;</P>
                <P>
                    • NAICS 236220—Commercial and Institutional Building Construction;
                    <PRTPAGE P="1823"/>
                </P>
                <P>• NAICS 324—Petroleum and Coal Product Manufacturing;</P>
                <P>• NAICS 324—Petroleum and Coal Product Manufacturing;</P>
                <P>• NAICS 32419—Petroleum Lubricating Oil and Grease Manufacturing;</P>
                <P>• NAICS 325—Chemical Manufacturing;</P>
                <P>• NAICS 325120—Industrial Gas Manufacturing;</P>
                <P>• NAICS 325180—Other Basic Inorganic Chemical Manufacturing;</P>
                <P>• NAICS 325199—All Other Basic Organic Chemical Manufacturing;</P>
                <P>• NAICS 325211—Plastics Material and Resin Manufacturing;</P>
                <P>• NAICS 325212—Synthetic Rubber Manufacturing;</P>
                <P>• NAICS 325220—Artificial and Synthetic Fibers and Filaments Manufacturing;</P>
                <P>• NAICS 325320—Pesticide and Other Agricultural Chemical Manufacturing;</P>
                <P>• NAICS 325411—Medicinal and Botanical Manufacturing;</P>
                <P>• NAICS 325412—Pharmaceutical Preparation Manufacturing;</P>
                <P>• NAICS 325612—Polish and Other Sanitation Good Manufacturing;</P>
                <P>• NAICS 325613—Surface Active Agent Manufacturing;</P>
                <P>• NAICS 325998—All Other Miscellaneous Chemical Product and Preparation Manufacturing;</P>
                <P>• NAICS 326113—Unlaminated Plastics Film and Sheet (except Packaging) Manufacturing;</P>
                <P>• NAICS 327910—Abrasive Product Manufacturing;</P>
                <P>• NAICS 333999—All Other Miscellaneous General Purpose Machinery Manufacturing;</P>
                <P>• NAICS 334511—Search, Detection, Navigation, Guidance, Aeronautical, and Nautical System and Instrument Manufacturing;</P>
                <P>• NAICS 336111—Automobile Manufacturing;</P>
                <P>• NAICS 423120—Motor Vehicle Supplies and New Parts Merchant Wholesalers;</P>
                <P>• NAICS 423420—Office Equipment Merchant Wholesalers;</P>
                <P>• NAICS 423510—Metal Service Centers and Other Metal Merchant Wholesalers;</P>
                <P>• NAICS 423740—Refrigeration Equipment and Supplies Merchant Wholesalers;</P>
                <P>• NAICS 423990—Other Miscellaneous Durable Goods Merchant Wholesalers;</P>
                <P>• NAICS 424690—Other Chemical and Allied Products Merchant Wholesalers;</P>
                <P>• NAICS 424720—Petroleum and Petroleum Products Merchant Wholesalers (except Bulk Stations and Terminals);</P>
                <P>• NAICS 424950—Paint, Varnish, and Supplies Merchant Wholesalers;</P>
                <P>• NAICS 441110—New Car Dealers;</P>
                <P>• NAICS 447190—Other Gasoline Stations;</P>
                <P>• NAICS 551112—Offices of Other Holding Companies; and</P>
                <P>• NAICS 562—Waste Management and Remediation Services.</P>
                <P>This action may also affect certain entities through pre-existing import, including import certification, and export notification rules under TSCA. Chemical importers are subject to the import provision of TSCA section 13 (15 U.S.C. 2612), which requires that the Secretary of the Treasury “refuse entry into the customs territory of the United States” of any substance, mixture, or article containing a chemical substance or mixture that fails to comply with any rule issued under TSCA or that “is offered for entry in violation” of TSCA or certain rules or orders issued under TSCA, including rules issued under TSCA section 5. Persons who import any chemical substance in bulk form, as part of a mixture, or as part of an article (if required by rule) are also subject to TSCA section 13 import certification requirements and the corresponding regulations promulgated at 19 CFR 12.118 through 12.127 (see also 19 CFR 127.28). Chemical importers of the chemical substances in bulk form, as part of a mixture, or as part of an article (if required by rule) must certify that the shipment of the chemical substance complies with all applicable rules and orders under TSCA, including regulations issued under TSCA sections 5, 6, 7 and Title IV. The EPA policy in support of import certification appears at 40 CFR part 707, subpart B.</P>
                <P>In addition, pursuant to 40 CFR 721.20, any persons who export or intend to export a chemical substance that is the subject of this final rule are subject to the export notification provisions of TSCA section 12(b) (15 U.S.C. 2611(b)) and must comply with the export notification requirements in 40 CFR part 707, subpart D.</P>
                <HD SOURCE="HD2">B. What is the Agency's authority for taking this action?</HD>
                <P>TSCA section 5(a)(2) (15 U.S.C. 2604(a)(2)) authorizes EPA to determine that a use of a chemical substance is a “significant new use.” EPA must make this determination by rule after considering all relevant factors, including those listed in TSCA section 5(a)(2). Once EPA determines that a use of a chemical substance is a significant new use, TSCA section 5(a)(1) requires persons to submit a significant new use notice (SNUN) to EPA at least 90 days before they manufacture (including import) or process the chemical substance for that use (15 U.S.C. 2604(a)(1)(B)(i)). TSCA further provides that such manufacturing (including import) or processing may not commence until EPA has conducted a review of the notice, made an appropriate determination on the notice, and taken such actions as are required in association with that determination (15 U.S.C. 2604(a)(1)(B)(ii)). As described in Unit V., the general SNUR provisions are found at 40 CFR part 721, subpart A.</P>
                <P>TSCA section 26(c) (15 U.S.C. 2625(c)) authorizes EPA to take action under other sections of TSCA with respect to categories of chemical substances.</P>
                <HD SOURCE="HD2">C. What action is the Agency taking?</HD>
                <P>This final SNUR will require persons to notify EPA at least 90 days before commencing any manufacture (including import) or processing of those 329 PFAS described in Unit II. that are designated as inactive on the TSCA Chemical Substance Inventory (TSCA Inventory) and that are not subject to an existing SNUR, including the existing SNURs cited at 40 CFR 721.9582 and 721.10536, for any use. EPA is providing a list of the 299 inactive PFAS that do not mask “fluor” or “fluorine” in the generic name in the public docket for this rule (Ref. 1). This category of PFAS chemical substances (“inactive PFAS”) is described further in Unit II.</P>
                <P>EPA is exempting from the notice requirement PFAS present as impurities, any byproducts which are not used for commercial purposes, and the importing or processing of inactive PFAS-containing articles because notification for the commercial activity designation (as active or inactive) on the TSCA Inventory is not required for such substances (see 40 CFR 710.27(a)). Similarly, EPA is exempting from the notice requirement PFAS manufactured or processed: in small quantities solely for research and development, for test marketing purposes, as a non-isolated intermediate, or solely for export from the United States as described in 40 CFR 720.30(e) or 721.3, except where the Administrator has made a finding described in TSCA section 12(a)(2).</P>
                <P>
                    The SNUR was proposed in the 
                    <E T="04">Federal Register</E>
                     on January 26, 2023 (88 FR 4937 (FRL 9655-01-OCSPP)). EPA received a total of 20 public comment submissions in response to the notice. EPA received one ongoing use claim in Unit V. of the Response to Comments document (Ref. 2). EPA 
                    <PRTPAGE P="1824"/>
                    reviewed the ongoing use claim, requested additional information, and has determined that the use is not ongoing, as described in Unit XI.D.
                </P>
                <HD SOURCE="HD2">D. Why is the Agency taking this action?</HD>
                <P>As noted in the January 26, 2023, proposed rule (88 FR 4937 (FRL 9655-01-OCSPP)), this action is part of the comprehensive approach outlined in the Agency's “PFAS Strategic Roadmap: EPA's Commitments to Action 2021-2024” to proactively prevent PFAS from entering air, land, and water at levels that can adversely impact human health and the environment (Ref. 3). This SNUR is necessary to ensure that EPA receives timely advance notice of any future manufacturing (including import) or processing of inactive PFAS for new uses that may produce changes in human or environmental exposures.</P>
                <P>The rationale and objectives for this SNUR are further explained in Unit III.</P>
                <HD SOURCE="HD2">E. What are the estimated incremental impacts of this action?</HD>
                <P>EPA has evaluated the potential costs of establishing SNUR reporting requirements for potential manufacturers (including importers) and processors of the chemical substances included in this rule. This analysis (Ref. 4), which is available in the docket, is discussed in Unit IX., and is briefly summarized here.</P>
                <P>In the event that a SNUN is submitted, costs are estimated to be approximately $26,894 per SNUN submission for large business submitters and $11,204 for small business submitters. In addition, for persons exporting a substance that is the subject of a SNUR, a one-time notice to EPA must be provided for the first export or intended export to a particular country, which is estimated to be approximately $43 per notification.</P>
                <HD SOURCE="HD1">II. Chemical Substances Subject to This Rule</HD>
                <P>As discussed in Units II. and III. of the proposed rule (88 FR 4937, January 26, 2023 (FRL 9655-01-OCSPP)), this SNUR applies to chemical substances designated as inactive on the TSCA Inventory that are also PFAS, except that inactive PFAS already subject to a significant new use rule, including but not limited to the significant new use rules cited at 40 CFR 721.9582 and 721.10536, are not subject to notice requirements under this action to avoid potential redundancies or conflicts between the SNURs.</P>
                <P>For the purposes of this SNUR, the definition of “PFAS” includes chemicals that contain at least one of these three structures:</P>
                <P>• R-(CF2)-CF(R′)R″, where both the CF2 and CF moieties are saturated carbons;</P>
                <P>• R-CF2OCF2-R′, where R and R′ can either be F, O, or saturated carbons; or</P>
                <P>• CF3C(CF3)R′R″, where R′ and R″ can either be F or saturated carbons.</P>
                <P>As described in Unit II. of the January 26, 2023, proposed rule (88 FR 4937 (FRL-9655-01-OCSPP)), this definition was developed to focus on substances most likely to be persistent in the environment and EPA notes that this definition may not be identical to other definitions of PFAS used within EPA or by other domestic or international organizations.</P>
                <P>The chemical substances for which EPA is finalizing a SNUR are the 329 PFAS that are both currently designated as inactive on the TSCA Inventory and that are not subject to an existing SNUR. The specific chemical identities for 30 of these substances that have been claimed as Confidential Business Information (CBI) have generic names (the nonconfidential substitute for the specific chemical name) that do not contain “fluor” or “fluorine.” EPA is providing a list of the 299 inactive PFAS that do not mask “fluor” or “fluorine” in the generic name in the public docket for this rule (Ref. 1). Because EPA is finalizing a structural definition of PFAS for this SNUR, EPA need not take additional steps to list the 30 inactive PFAS that are not subject to an existing SNUR and whose generic names do not contain “fluor” or “fluorine”.</P>
                <P>On October 14, 2022, prior to the publication of the proposed SNUR, EPA received a Notice of Activity for CASRN 306-92-3. This substance was erroneously included in the initial count and list of the 300 inactive PFAS that do not mask “fluor” or “fluorine” in the supplemental document, “List of Select Chemicals Subject to the Proposed Significant New Use Rule Per- and Poly-fluoroalkyl Chemical Substances Designated as Inactive on the TSCA Inventory” (Ref. 5). The designation of this substance was “active” at the time of the proposed rule and, as such, it is not subject to this final rule and the correct number of chemical substances for which EPA is finalizing a SNUR is 329.</P>
                <P>EPA received one Notice of Activity for CASRN 35101-47-7 on March 2, 2023, after the publication of the proposed rule. As described in Unit IV of the proposed rule, uses arising after January 26, 2023, are significant new uses, and persons who began commercial manufacturing (including importing) or processing for a significant new use have to cease upon the effective date of the final rule. To resume their activities, these persons must first comply with all applicable SNUR notification requirements and wait until all TSCA prerequisites for the commencement of manufacturing (including importing) or processing have been satisfied.</P>
                <HD SOURCE="HD1">III. Rationale and Objectives</HD>
                <HD SOURCE="HD2">A. What is the rationale for this action?</HD>
                <P>As discussed in Units II. and III. of the proposed rule (88 FR 4937, January 26, 2023 (FRL-9655-01-OCSPP)), PFAS can adversely impact human health and the environment. This final action is part of a comprehensive approach to proactively prevent PFAS from entering air, land, and water at levels that can adversely impact human health and the environment.</P>
                <P>In the absence of this final SNUR, manufacturing (including importing) or processing for the significant new uses in this rule could begin at any time after a manufacturer submits a Notice of Activity under section 8 of TSCA and the substance becomes “active” on the TSCA Inventory; EPA would not be provided prior notice under section 5 or an opportunity to review and address potential risks associated with the proposed new use. The manufacture (including import) or processing for any use of inactive PFAS would increase the magnitude and duration of exposure to humans and the environment to these chemicals. Given the concerns described in Units II. and III. of the proposed rule (88 FR 4937, January 26, 2023 (FRL-9655-01-OCSPP)), EPA has determined that notification and EPA's required review are warranted for these chemicals prior to their potential reintroduction into commerce.</P>
                <P>Consistent with EPA's past practice for issuing SNURs under TSCA section 5(a)(2), as described in Unit IV. of the proposed rule (88 FR 4937, January 26, 2023 (FRL-9655-01-OCSPP)), EPA's decision to issue a SNUR for a particular chemical use follows an analysis of the relevant factors listed in section 5(a)(2) and need not be based on an extensive evaluation of the hazard, exposure, or potential risk associated with that use. If a person decides to begin manufacturing (including importing) or processing any of these chemicals for the significant new use, the notice to EPA allows the Agency to evaluate the new use according to the specific parameters and circumstances surrounding the conditions of use at the time it receives such a notification.</P>
                <HD SOURCE="HD2">B. What are the objectives of this action?</HD>
                <P>
                    Based on the considerations in Unit III.A., EPA will achieve the following 
                    <PRTPAGE P="1825"/>
                    objectives with regard to the significant new use(s) of inactive PFAS that are designated in this rule:
                </P>
                <P>• EPA will receive notice of any person's intent to manufacture (including import) or process the chemical substances for the described significant new use before that activity begins.</P>
                <P>• EPA will have an opportunity to review and evaluate information submitted in a SNUN before the notice submitter begins manufacturing (including importing) or processing the chemical substances for the described significant new use.</P>
                <P>• EPA must either determine that the significant new use is not likely to present an unreasonable risk of injury or take such regulatory action as is associated with an alternative determination under TSCA section 5 before the manufacture or processing for the significant new use could commence.</P>
                <HD SOURCE="HD1">IV. Significant New Use Determination</HD>
                <P>TSCA section 5(a)(2) states that EPA's determination that a use of a chemical substance is a significant new use must be made after consideration of all relevant factors including:</P>
                <P>• The projected volume of manufacturing and processing of a chemical substance.</P>
                <P>• The extent to which a use changes the type or form of exposure of human beings or the environment to a chemical substance.</P>
                <P>• The extent to which a use increases the magnitude and duration of exposure of human beings or the environment to a chemical substance.</P>
                <P>• The reasonably anticipated manner and methods of manufacturing (including importing), processing, distribution in commerce, and disposal of a chemical substance.</P>
                <P>In addition to these factors enumerated in TSCA section 5(a)(2), the statute authorizes EPA to consider any other relevant factors.</P>
                <P>To determine what constitutes a significant new use of an inactive PFAS, EPA considered relevant information about the toxicity or expected toxicity of these substances, likely human exposures and environmental releases associated with possible uses, and the four factors listed in TSCA section 5(a)(2). Since the manufacture (including import) and processing of inactive PFAS has been discontinued in the United States, exposure will decrease over time. As such, EPA expects their presence in humans and the environment to decline over time. If any new uses of inactive PFAS were to resume after having been phased out, EPA believes that such uses could both change the type and form and increase the magnitude and duration of human and environmental exposure to the substances, constituting a significant new use.</P>
                <P>EPA acknowledges that the reporting of commercial activity under the TSCA Inventory Notification (Active-Inactive) Requirements Rule (“Active-Inactive rule”) was not required for several activities, including, but not limited to, importing or processing of inactive PFAS-containing articles, and manufacturing (including importing) or processing of inactive PFAS as impurities, byproducts not used for commercial purposes, small quantities solely for research and development, for test marketing purposes, as a non-isolated intermediate, or solely for export from the United States (Ref. 6). Thus, EPA has determined that the designation of these PFAS as inactive does not provide a sufficient basis to conclude that there are not ongoing uses of inactive PFAS for these activities, and because this SNUR is based on information obtained from the Active-Inactive rule, EPA is not at this time designating uses for these activities as significant new uses. Based on consideration of the statutory factors discussed herein, EPA has determined as significant new uses: manufacture (including import) or processing of inactive PFAS for any use except:</P>
                <EXTRACT>
                    <P>(1) Importing or processing of inactive PFAS-containing articles; and/or</P>
                    <P>(2) Manufacture (including import) or processing of inactive PFAS:</P>
                    <P>• As impurities,</P>
                    <P>• As byproducts not used for commercial purposes,</P>
                    <P>• In small quantities solely for research and development,</P>
                    <P>• For test marketing purposes,</P>
                    <P>• For use as a non-isolated intermediate, or</P>
                    <P>• Solely for export from the United States.</P>
                </EXTRACT>
                <HD SOURCE="HD1">V. Applicability of General Provisions</HD>
                <P>General provisions for SNURs appear under 40 CFR part 721, subpart A. These provisions describe persons subject to the rule, recordkeeping requirements, exemptions to reporting requirements, and applicability of the rule to uses occurring before the effective date of the final rule.</P>
                <P>
                    Provisions relating to user fees appear at 40 CFR part 700. According to 40 CFR 721.1(c), persons subject to SNURs must comply with the same notice requirements and EPA regulatory procedures as submitters of Pre-manufacture Notices (PMNs) under TSCA section 5(a)(1)(A). In particular, these requirements include the information submission requirements of TSCA sections 5(b) and 5(d)(1), the exemptions authorized by TSCA sections 5(h)(1), (h)(2), (h)(3), and (h)(5), and the regulations at 40 CFR part 720. Once EPA receives a SNUN, EPA must either determine that the significant new use is not likely to present an unreasonable risk of injury or take such regulatory action as is associated with an alternative determination under TSCA section 5 before the manufacturing (including importing) or processing for the significant new use could commence. If EPA determines that the significant new use is not likely to present an unreasonable risk, EPA is required under TSCA section 5(g) to make public, and submit for publication in the 
                    <E T="04">Federal Register</E>
                    , a statement of EPA's finding.
                </P>
                <P>Persons who export or intend to export a chemical substance identified in a proposed or final SNUR are subject to the export notification provisions of TSCA section 12(b). The regulations that interpret TSCA section 12(b) appear at 40 CFR part 707, subpart D. Persons who import a chemical substance identified in a final SNUR are subject to TSCA section 13, which requires that the Secretary of the Treasury “refuse entry into the customs territory of the United States” of any substance, mixture, or article containing a chemical substance or mixture that fails to comply with any rule issued under TSCA or that “is offered for entry in violation” of TSCA or certain rules or orders issued under TSCA, including SNURs issued under TSCA section 5. Persons who import any chemical substance in bulk form, as part of a mixture, or as part of an article (if required by rule) are also subject to TSCA section 13 import certification requirements, codified at 19 CFR 12.118 through 12.127; see also 19 CFR 127.28. Those persons must certify that the shipment of the chemical substance complies with all applicable rules and orders under TSCA, including any SNUR requirements. The EPA policy in support of import certification appears at 40 CFR part 707, subpart B.</P>
                <HD SOURCE="HD1">VI. Applicability of Rule to Uses Occurring Before Effective Date of the Final Rule</HD>
                <P>
                    As discussed in the 
                    <E T="04">Federal Register</E>
                     of April 24, 1990 (55 FR 17376 (FRL-3658-5)), EPA has decided that the intent of TSCA section 5(a)(1)(B) is best served by designating a use as a significant new use as of the date of publication of the proposed rule, rather than as of the effective date of the final rule. This rule was proposed on January 26, 2023 (88 FR 4937 (FRL-9655-01-OCSPP)). Uses arising after the publication of the proposed rule are 
                    <PRTPAGE P="1826"/>
                    distinguished from uses that existed at publication of the proposed rule. The former would be new uses, the latter ongoing uses, except that uses that are ongoing as of the publication of the proposed rule would not be considered ongoing uses if they have ceased by the date of issuance of a final rule. EPA solicited public comment to identify any ongoing manufacturing or processing of inactive PFAS subject to the proposed SNUR. EPA received one ongoing use claim captured in the Response to Comments in Unit V. (Ref. 2). EPA reviewed the ongoing use claim, requested additional information, and has determined that the use is not ongoing, as described in Unit XI.D.
                </P>
                <P>
                    Persons who began commercial manufacturing (including importing) or processing of the chemical substances for a significant new use identified as of January 26, 2023, must cease any such activity upon the effective date of this final rule. To resume their activities, these persons first have to comply with all applicable SNUR notification requirements and wait until all TSCA prerequisites for the commencement of manufacturing (including importing) or processing have been satisfied. Consult the 
                    <E T="04">Federal Register</E>
                     document of April 24, 1990 (55 FR 17376 (FRL-3658-5)) for a more detailed discussion of the cutoff date for ongoing uses.
                </P>
                <HD SOURCE="HD1">VII. Development and Submission of Information</HD>
                <P>
                    EPA recognizes that TSCA section 5 does not usually require developing new information (
                    <E T="03">e.g.,</E>
                     generating test data) before submission of a SNUN. There is an exception: development of information is required where the chemical substance subject to the SNUR is also subject to a rule, order, or consent agreement under TSCA section 4 (see TSCA section 5(b)(1)).
                </P>
                <P>In the absence of a TSCA section 4 test rule or order covering the chemical substance, persons are required to submit only information in their possession or control and to describe any other information known to or reasonably ascertainable by them (15 U.S.C. 2604(d); 40 CFR 721.25 and 720.50). However, as a general matter, EPA recommends that SNUN submitters include information that would permit a reasoned evaluation of risks posed by the chemical substance during its manufacture (including import), processing, distribution in commerce, use, or disposal. Potentially useful information includes physical-chemical property data and any information related to persistence, bioaccumulation, toxicity, and other characteristics that may help predict the impact of a chemical substance on health or the environment.</P>
                <P>Submitting a SNUN that does not include information sufficient to permit a reasoned evaluation may increase the likelihood that EPA will either respond with a determination that the information available to the Agency is insufficient to permit a reasoned evaluation of the health and environmental effects of the significant new use or, alternatively, that in the absence of sufficient information, the manufacture, processing, distribution in commerce, use, or disposal of the chemical substance may present an unreasonable risk of injury.</P>
                <P>SNUN submitters should be aware that EPA will be better able to evaluate SNUNs and define the terms of any potentially necessary controls if the submitter provides detailed information on human exposure and environmental releases that may result from the significant new use of the chemical substances.</P>
                <HD SOURCE="HD1">VIII. SNUN Submissions</HD>
                <P>
                    EPA recommends that submitters consult with the Agency prior to submitting a SNUN to discuss what information may be useful in evaluating a significant new use notice. Discussions with the Agency prior to submission can afford ample time to conduct any tests that might be helpful in evaluating risks posed by the substance. According to 40 CFR 721.1(c), persons submitting a SNUN must comply with the same notice requirements and EPA regulatory procedures as persons submitting a PMN, including submission of test data on health and environmental effects as described in 40 CFR 720.50. SNUNs must be submitted on EPA Form No. 7710-25, generated using e-PMN software, and submitted to the Agency in accordance with the procedures set forth in 40 CFR 721.25 and 720.40. E-PMN software is available electronically at 
                    <E T="03">https://www.epa.gov/chemicals-under-tsca.</E>
                </P>
                <HD SOURCE="HD1">IX. Economic Analysis</HD>
                <HD SOURCE="HD2">A. What is the analysis for SNUNs?</HD>
                <P>EPA has evaluated the potential costs of establishing SNUR reporting requirements for potential manufacturers (including importers) and processors of the chemical substances included in this rule (Ref. 4). In the event that a SNUN is submitted, costs are estimated at approximately $26,894 per SNUN submission for large business submitters and $11,204 for small business submitters. These estimates include the cost to prepare and submit the SNUN, and the payment of a user fee. Businesses that submit a SNUN would be subject to either a $19,020 user fee required by 40 CFR 700.45(b)(2)(iii), or, if they are a small business as defined at 13 CFR 121.201, a reduced user fee of $3,330 (40 CFR 700.45(b)(1)). Additionally, these estimates reflect the costs and fees as they are known at the time this rule is promulgated. EPA's complete economic analysis is available in the public docket for this rule (Ref. 4).</P>
                <HD SOURCE="HD2">B. What is the analysis for export notifications?</HD>
                <P>
                    Under TSCA section 12(b) and the implementing regulations at 40 CFR part 707, subpart D, exporters must notify EPA if they export or intend to export a chemical substance or mixture for which, among other things, a rule has been proposed or promulgated under TSCA section 5. For persons exporting a substance that is the subject of a SNUR, a one-time notice to EPA must be provided for the first export or intended export to a particular country. The total costs of export notification will vary by chemical, depending on the number of required notifications (
                    <E T="03">i.e.,</E>
                     the number of countries to which the chemical is exported). While EPA is unable to make any estimate of the likely number of export notifications for the chemicals covered in this SNUR, as stated in the accompanying economic analysis of this SNUR, the estimated cost of the export notification requirement on a per unit basis is approximately $43.
                </P>
                <HD SOURCE="HD1">X. Scientific Standards, Evidence, and Available Information</HD>
                <P>EPA has used scientific information, technical procedures, measures, methods, protocols, methodologies, and models consistent with the best available science, as applicable. These information sources supply information relevant to whether a particular use would be a significant new use, based on relevant factors including those listed under TSCA section 5(a)(2). As noted in Unit III., EPA's decision to promulgate a SNUR for a particular chemical use need not be based on an extensive evaluation of the hazard, exposure, or potential risk associated with that use.</P>
                <P>
                    The clarity and completeness of the data, assumptions, methods, quality assurance, and analyses employed in EPA's decision are documented, as applicable and to the extent necessary for purposes of this SNUR, in Unit II. of the January 26, 2023, proposed rule (88 FR 4937 (FRL-9655-01-OCSPP)), and in the references cited throughout the preamble of the proposed rule. EPA 
                    <PRTPAGE P="1827"/>
                    recognizes, based on the available information, that there is variability and uncertainty in whether any particular significant new use would actually present an unreasonable risk. For precisely this reason, it is appropriate to secure a future notice and review process for these uses, at such time as they are known more definitely. The extent to which the various information, procedures, measures, methods, protocols, methodologies or models used in EPA's decision have been subject to independent verification or peer review is adequate to justify their use, collectively, in the record for a significant new use rule.
                </P>
                <HD SOURCE="HD1">XI. Response to Public Comment</HD>
                <P>The Agency reviewed and considered all comments received related to the January 26, 2023, proposed rule (88 FR 4937 (FRL-9655-01-OCSPP)). Copies of all comments are available in the docket for this action (EPA-HQ-OPPT-2022-0867), and EPA responses are in the Response to Comments document (Ref. 2), which is also available in the docket. Several primary comment topics included: the Agency's statutory authority; the definition of PFAS; significant new uses; ongoing manufacturing and processing; chemical identity claimed as CBI; byproducts, impurities, and non-isolated intermediates; and costs and fees of SNUN submissions which are summarized in this unit, along with EPA responses.</P>
                <P>
                    1. 
                    <E T="03">Comment:</E>
                     Several commenters stated that EPA is acting within its authority under TSCA with the proposed SNUR. Other commenters commented that EPA is acting outside of its statutory authority and one commenter claimed that the inactive status of a chemical or chemicals on the TSCA Inventory should not be used as the sole basis for a SNUR and that the proposal appears to undercut the simple notification procedure for changing the status of a chemical substance from inactive to active that Congress included when TSCA was amended. One commenter stated that Congress did not include in the 2016 amendments a provision that requires any form of substantive review of substances prior to change of status from inactive to active. The same commenter stated that EPA appears not to have undertaken a chemical-by-chemical review for the three hundred substances subject to this SNUR, and findings on a chemical-specific basis have not been provided.
                </P>
                <P>
                    <E T="03">Response:</E>
                     EPA disagrees that this SNUR, issued pursuant to TSCA section 5(a) undercuts the notification procedure established under TSCA section 8(b). TSCA section 8(b)(5)(B)(i) requires that “[a]ny person that intends to manufacture or process for a nonexempt commercial purpose a chemical substance that is designated as an inactive substance shall notify the Administrator before the date on which the inactive substance is manufactured or processed.” This Notice of Activity reporting requirement applies to all chemical substances designated as inactive, including those subject to this SNUR. EPA separately has authority under TSCA section 5(a) to determine that uses of a chemical substance (or category of chemical substances) are “significant new uses” for which notification to EPA is required before manufacture (including import) or processing for the significant new use can commence. EPA has authority under TSCA section 5(a) to promulgate SNURs for “any chemical substance,” without regard to whether the chemical substance is designated as active or inactive. There is also no requirement that EPA need undertake a chemical-by-chemical review as the commenter suggests. One common characteristic of concern of PFAS is that many break down very slowly and can build up in people, animals, and the environment over time (Ref. 7). As described in Unit IV. of the January 26, 2023, proposed rule (88 FR 4639 (FRL-9655-01-OCSPP)), the baseline projected volume for these 329 inactive PFAS is presumed to be minimal based on their inactive TSCA Inventory designation. As such, any new manufacturing or processing of any of these chemical substances would significantly change the production volume and produce changes in human or environmental exposures to these chemical substances. Thus, EPA has determined it is necessary to review and make an affirmative determination on potential risks of the chemical substances under section 5 before the manufacture (including import) or processing of the chemical substances for the described significant new use could begin.
                </P>
                <P>
                    2. 
                    <E T="03">Comment:</E>
                     Many commenters discussed the proposed definition of PFAS for this rule. Several commenters suggested that EPA identify covered PFAS by specific identification rather than through a structural definition. One commenter stated that structural definitions are difficult to use as they require an extensive understanding of the often-complex chemistry of PFAS, and structural definitions may also be ambiguous and over-inclusive. Other commenters stated that should EPA move ahead with a broad definition and stated that the definition should be consistent with the definition of PFAS the Agency uses in other regulations, or that EPA should work with Federal partners to ensure a consistent Federal definition of PFAS. Two commenters stated that EPA should adopt a definition of PFAS that more closely aligns with the Organization for Economic Co-operation and Development's (OECD) broad definition (Ref. 8).
                </P>
                <P>
                    <E T="03">Response:</E>
                     EPA believes it has been chemically precise in the proposed structural definition and appreciates that there are differences between the definition of PFAS used for this rule, for other actions in the Agency, and by other Federal agencies. The Agency considered adopting various definitions, including some of those suggested by commenters, but ultimately determined those definitions were not appropriate for this rule because they were not developed to focus on substances most likely to be persistent in the environment while excluding those substances that are “lightly” fluorinated. In reaching this decision, EPA considered that OECD also stipulates that there may be different definitions of “PFAS” for different entities or for different purposes, and that it may be appropriate for there to be different definitions or interpretations depending on the specific scenario. The proposed definition focused on substances with greater potential for exposures to people and/or the environment and by extension more potential to present risks. Adopting the OECD definition of PFAS for this rule would have included many substances whose only fluorine molecule is in a terminal -CF3 and that do not share a structure that is likely to result in the substance's persistence in the environment, or which would degrade to a substance that shares toxicological or physiochemical properties with perfluorooctanoic acid (PFOA), perfluorooctanesulfonic acid (PFOS), or GenX (Ref. 9).
                </P>
                <P>
                    EPA disagrees that the scope of substances subject to notification requirements should be a discrete list and not a structural definition. EPA points out that other regulations promulgated pursuant to TSCA have relied on a structural definition when appropriate (
                    <E T="03">e.g.,</E>
                     the long-chain perfluoroalkyl carboxylate (LCPFAC) SNUR defines covered substances using a structural definition (40 CFR 721.10536), and the polymer exemption rule for new chemical PMNs defines covered PFAS polymers using structural definitions (40 CFR 723.250)).
                </P>
                <P>
                    Additionally, there are PFAS on the TSCA Inventory whose generic names 
                    <PRTPAGE P="1828"/>
                    do not clearly state the substance is fluorinated (
                    <E T="03">i.e.,</E>
                     no “fluor” included in the generic name). The inclusion of those chemicals on a discrete list for reporting under this rule would disclose structural information for these substances that has been claimed as CBI. EPA is finalizing the rule as proposed and is providing the list of the 299 inactive PFAS that do not mask “fluor” or “fluorine” in the generic name in the public docket for this rule. EPA believes that providing a list of the 299 PFAS should eliminate most ambiguity, and notes that an entity with a valid commercial need for EPA to verify if a substance is on the inventory can submit a Bona Fide Intent to Manufacture or Import Notice (“bona fide notice”). EPA will consider the information submitted in a bona fide notice and, if the Agency believes that the submitter has demonstrated a genuine intent to manufacture or import, search the full TSCA Inventory master file and provide a written determination to the submitter on the TSCA Inventory status (including SNUR status) for the requested chemical substance.
                </P>
                <P>
                    3. 
                    <E T="03">Comment:</E>
                     Several commenters stated that SNURs are intended to address truly new uses. The commenters state that the dormant status of a substance on the TSCA Inventory does not mean that a previous use should be considered new when reintroduced into commerce. Two commenters stated that under TSCA, EPA is required to evaluate a substance prior to promulgating a SNUR. One commenter suggested that EPA specifically exclude from the notification requirements any uses that were identified to EPA in previously submitted PMNs. Another commenter said that addressing the discontinued use of an existing chemical with a SNUR is only administratively efficient where other requirements of TSCA section 5 have been met and where (1) stakeholder groups are broadly aware of the proposal and (2) agree with EPA that the use is permanently discontinued or being phased out; the commenter stated that these elements have not been met.
                </P>
                <P>
                    <E T="03">Response:</E>
                     EPA disagrees that the previous use of a chemical substance listed as inactive on the TSCA Inventory should not be considered new when such use is restarted. TSCA section 5 gives EPA the authority to designate uses of a chemical as Significant New Uses, including but not limited to uses that were ongoing in the past but are not longer in process. Part of EPA's rationale for promulgating this SNUR is that the chemical substances subject to this SNUR are considered to be PFAS. Certain PFAS are associated with risk to human health and the environment, and one common characteristic of concern of PFAS is that many break down very slowly and can build up in people, animals, and the environment over time. Therefore, EPA has determined that any use of these PFAS would produce changes in human or environmental exposures and should trigger a SNUN and accompanying EPA review and action as necessary. EPA also disagrees in part with the commenter who suggested that EPA specifically exclude from the SNUN requirements any uses that were identified to EPA in previously submitted PMNs. However, uses of chemical substances for which a PMN has been submitted (and for which EPA has reasonably available information that such uses are ongoing) are considered ongoing uses for which the SNUR does not apply. If production of a chemical has ceased, the use of the chemical substance is not considered to be ongoing and such use is covered by this SNUR.
                </P>
                <P>EPA required reporting (with certain exemptions from reporting at 40 CFR 710.27(a)) under the Active-Inactive reporting rule of each chemical substance manufactured (including imported) or processed in the U.S. over a 10-year period ending on June 21, 2016, and there was no manufacturing (including import), or processing reported for these inactive PFAS (Ref. 6). EPA believes the comment period for the proposed SNUR allowed for stakeholder groups to be broadly aware of the proposal notice and provided an additional opportunity for industry to provide specific documentation of the status of each chemical. EPA received one ongoing use claim and has determined that the use is not ongoing, as described in Unit XI.D.</P>
                <P>
                    4. 
                    <E T="03">Comment:</E>
                     An anonymous submitter notified EPA that it intends to manufacture a PFAS covered by the proposed SNUR. The commenter stated that since EPA is not authorized under TSCA to adopt a SNUR for an ongoing use, it should exclude this substance from the final SNUR.
                </P>
                <P>
                    <E T="03">Response:</E>
                     EPA investigated the confidentially submitted information and determined that the manufacture of this substance is not ongoing. EPA is therefore not excluding the manufacture of this substance from the final SNUR.
                </P>
                <P>
                    5. 
                    <E T="03">Comment:</E>
                     Several commenters provided feedback on the options described in the proposed rule for potential further agency action to list out in the regulation either the specific chemical identity or generic name of all of the chemicals that fall within the scope of the proposed SNUR. Some commenters stated that EPA must identify all substances for which the chemical identity has been claimed as CBI, regardless as to whether “fluor” or “fluorine” appears in the name. Another commenter stated that TSCA section 14(d)(3) allows information claimed as CBI to be disclosed if the Agency determines that disclosure is “necessary to protect health or the environment against an unreasonable risk of injury to health or the environment.” Thus, the commenter stated that EPA should override CBI claims in the context of this proposed SNUR and identify those PFAS whose generic names do not include “fluor” or “fluorine”. The commenter concluded that since these PFAS are inactive, any business interest in their confidentiality is minimal and overridden by the need of states and the public for the information. Another commenter stated that although EPA must maintain substantiated CBI claims for these substances, EPA can include the generic names and PMN and accession numbers, which are not CBI, which will minimize the potential for confusion about whether certain substances are subject to this proposal. Another commenter stated that EPA should use its authority under TSCA section 14(f) to require re-substantiation of and review the chemical identity CBI claims for these PFAS. Additionally, the commenter stated that EPA should initiate review of the remaining specific chemical identity CBI claims to ensure they comply with TSCA section 14. Another commenter relinquished its CBI claims for the specific chemical identities for twelve substances listed in the confidential portion of the TSCA Inventory that EPA has identified as being subject to the proposed SNUR and requested that EPA move them to the public portion of the TSCA Inventory.
                </P>
                <P>
                    <E T="03">Response:</E>
                     EPA disagrees that all substances for which the chemical identity has been claimed as CBI must be identified. Under section 14(c) of TSCA, submitters may claim information submitted to EPA under TSCA as CBI. The listing of a chemical substance as “inactive” on the TSCA inventory does not itself impact CBI claims relating to such chemical substance, including CBI claims relating to the structure or chemical identity of a chemical substance. Further, as explained previously, EPA is finalizing a structural definition of the chemical substances subject to this SNUR, and EPA believes that persons will be able to identify PFAS subject to this SNUR based on that structural definition, regardless of whether there is a universally known unique identifier. 
                    <PRTPAGE P="1829"/>
                    For additional convenience, EPA is providing a list of the inactive PFAS that do not mask “fluor” or “fluorine” in the generic name in the public docket for this rule.
                </P>
                <P>EPA disagrees that its conclusions pursuant to section 5 of TSCA supporting the proposed SNUR for these substances meet the very different conclusions that would prompt mandatory CBI review in accordance with section 14(f). The fact that the substances are currently designated as inactive following reporting under section 8(b) of TSCA does not mean that the substance identities are no longer treated as confidential by the original CBI claimant or by subsequent or prospective manufacturers, and therefore EPA has not determined that the status of a substance as inactive on the TSCA inventory is a “reasonable basis to believe” that chemical identity information about such substance “does not qualify” for CBI protection, as is required by TSCA section 14(f)(2)(B). Further, CBI claims asserted prior to the enactment of the Lautenberg amendments to TSCA in 2016 do not automatically expire as do most post-Lautenberg CBI claims. However, if a SNUN on any of these substances is submitted, EPA would review any renewed CBI claim for chemical identity at that time, in accordance with the requirements of TSCA section 14(g). Submitters of such SNUNs that assert a CBI claim for chemical identity should expect that if the generic name submitted with such a claim does not identify the substance as a PFAS, EPA expects to require revision of the generic name to meet the generic name requirements in TSCA section 14(c). Finally, the request that EPA initiate review of the remaining specific chemical identity CBI claims to ensure they comply with TSCA section 14 is outside the scope of this rulemaking.</P>
                <P>EPA acknowledges the commenter who relinquished its CBI claims for the specific chemical identities and plans to move the twelve substances into the public portion of the TSCA Inventory.</P>
                <P>
                    6. 
                    <E T="03">Comment:</E>
                     Many commenters stated that requiring reporting on the manufacture of any substances that were exempt under the Active-Inactive Rule would not be appropriate, including substances manufactured and processed solely for export or test marketing, non-isolated intermediates, and all other exemptions from PMN requirements listed at 40 CFR 720.30(h) (Ref. 6). Other commenters expressed opposition to the proposed exemptions. One commenter stated that exposure to minuscule amounts of PFAS is a threat to human health and safety, and the reintroduction of inactive PFAS, in even the smallest quantities, should therefore be subject to the same intense health and safety review as other quantities of PFAS. One commenter urged EPA to finalize the rule without regulatory exemptions and extend the proposed SNUR to byproducts because they are significant sources of PFAS exposure and environmental releases.
                </P>
                <P>
                    <E T="03">Response:</E>
                     EPA acknowledges that the standard SNUR exemptions do not fully align with the Active-Inactive reporting exemptions. In the final rule, EPA is adding an exemption for non-isolated intermediates and expanding the exemption for byproducts for consistency with the PMN exemptions at 40 CFR 720.30(g) and (h)(2) and believes that these exemptions are now consistent with the exemptions from Active-Inactive reporting. As EPA collects evidence of the use of PFAS, potentially including inactive PFAS, EPA may consider making certain exemptions inapplicable in the future. The Agency expects to receive additional information about any ongoing use of PFAS as part of the separate TSCA section 8(a)(7) PFAS reporting rule that was proposed on June 28, 2021 (86 FR 33962 (FRL-7902-01-OCSPP)) and finalized on October 11, 2023 (88 FR 70516 (FRL 7902-02-OCSPP)).
                </P>
                <P>
                    7. 
                    <E T="03">Comment:</E>
                     One commenter stated that the proposal incorrectly estimated the costs related to the submission of a SNUN. The commenter said that the estimated cost of $26,737 is inconsistent with the Agency's latest proposal for increasing TSCA fees. Another commenter stated that while the user fee may discourage a manufacturer from using PFAS in a significant way, it is likely that the user fee will deter users from submitting a SNUN altogether.
                </P>
                <P>
                    <E T="03">Response:</E>
                     EPA disagrees that the proposal incorrectly estimated the costs related to the submission of a SNUN, and notes that the latest proposal for TSCA fees referenced by the commenter has not been finalized. EPA disagrees with the commenter that a user fee would encourage a manufacturer to circumvent the SNUR. EPA has enforcement mechanisms in place to ensure compliance with EPA regulations.
                </P>
                <HD SOURCE="HD1">XII. References</HD>
                <P>
                    The following is a listing of the documents that are specifically referenced in this document. The docket includes these documents and other information considered by EPA, including documents that are referenced within the documents that are included in the docket, even if the referenced document is not physically located in the docket. For assistance in locating these other documents, please consult the technical person listed under 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    .
                </P>
                <EXTRACT>
                    <FP SOURCE="FP-2">1. U.S. EPA. “List of Select Chemicals Subject to the Proposed Significant New Use Rule Per- and Poly-fluoroalkyl Chemical Substances Designated as Inactive on the TSCA Inventory.” October 2022.</FP>
                    <FP SOURCE="FP-2">2. U.S. EPA. “Response to Comments on the Final Per- and Poly-fluoroalkyl Chemical Substances Designated as Inactive on the TSCA Inventory Significant New Use Rule (SNUR).” October 2023.</FP>
                    <FP SOURCE="FP-2">3. U.S. EPA. “PFAS Strategic Roadmap: EPA's Commitment to Action 2021-2024.” EPA-100-K-21-002, October 2021.</FP>
                    <FP SOURCE="FP-2">4. U.S. EPA. “Economic Analysis of the Final Significant New Use Rule Per- and Poly-fluoroalkyl Chemical Substances Designated as Inactive on the TSCA Inventory.” October 2023.</FP>
                    <FP SOURCE="FP-2">5. U.S. EPA. “List of Select Chemicals Subject to the Proposed Significant New Use Rule Per- and Poly-fluoroalkyl Chemical Substances Designated as Inactive on the TSCA Inventory.” January 2022.</FP>
                    <FP SOURCE="FP-2">6. U.S. EPA. TSCA Inventory Notification (Active-Inactive) Requirements; Final Rule, 82 FR 37520 (FRL-9964-22), August 11, 2017.</FP>
                    <FP SOURCE="FP-2">7. Evich, Marina G., Davis, Mary J.B., McCord, James P., Acrey, Brad, Awkerman, Jill A., Knappe, Detlef R.U., Lindstrom, Andrew B., Speth, Thomas F., Tebes-Stevens, Caroline, Strynar, Mark J., Wang, Zhanyun, Weber, Eric J., Henderson, Matthew W., Washington, John W. Per- and polyfluoroalkyl substances in the environment. Science. 375: 6580, 1-14. February 4, 2022</FP>
                    <FP SOURCE="FP-2">8. Organisation for Economic Co-operation and Development (OECD). “Reconciling Terminology of the Universe of Per- and Polyfluoroalkyl Substances: Recommendations and Practical Guidance.” July 9, 2021.</FP>
                    <FP SOURCE="FP-2">
                        9. United Nations Environment Programme. Sources, Fates, Toxicity, and Risks of Trifluoroacetic Acid and Its Salts: Relevance to Substances Regulated Under the Montreal and Kyoto Protocols. Report No. 2016-01. February 2016. 
                        <E T="03">https://ozone.unep.org/sites/default/files/2019-08/TFA2016.pdf.</E>
                    </FP>
                </EXTRACT>
                <HD SOURCE="HD1">XIII. 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/regulations/and-executive-orders.</E>
                </P>
                <HD SOURCE="HD2">A. Executive Order 12866: Regulatory Planning and Review and 14094: Modernizing Regulatory Review</HD>
                <P>
                    This action is not a significant regulatory action under Executive Order 12866 (58 FR 51735, October 4, 1993), as amended by Executive Order 14094 
                    <PRTPAGE P="1830"/>
                    (88 FR 21879, April 11, 2023), and was therefore not subject to Executive Order 12866 review.
                </P>
                <HD SOURCE="HD2">B. Paperwork Reduction Act (PRA)</HD>
                <P>
                    This action does not impose any new information collection burden under the PRA, 44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                     The Office of Management and Budget (OMB) has previously approved the information collection activities contained in the existing regulations and has assigned OMB control numbers 2070-0038 (EPA ICR No. 1188.13) and 2070-0030 (EPA ICR No. 0795.16). If an entity were to submit a SNUN to the Agency, the annual burden is estimated to be less than 100 hours per response, and the estimated burden for export notifications is less than 1.5 hours per notification. In both cases, burden is estimated to be reduced for submitters who have already registered to use the electronic submission system. This burden estimate includes the time needed to review instructions, search existing data sources, gather and maintain the data needed, and complete, review and submit the required SNUN.
                </P>
                <P>EPA is amending the table in 40 CFR part 9 to list the SNURs and OMB approval number for the information collection activities contained in this action. This listing of the OMB control numbers and their subsequent codification in the CFR satisfies the display requirements of PRA and OMB's implementing regulations at 5 CFR part 1320. The Information Collection Request (ICR) covering the SNUR activities was previously subject to public notice and comment prior to OMB approval, and given the technical nature of the table, EPA finds that further notice and comment to amend it is unnecessary. As a result, EPA finds that there is “good cause” under section 553(b)(3)(B) of the Administrative Procedure Act (5 U.S.C. 553(b)(3)(B)) to amend this table without further notice and comment.</P>
                <P>EPA always welcomes your feedback on the burden estimate. Send any comments about the accuracy of the burden estimate, and any suggested methods for minimizing respondent burden, including through the use of automated collection techniques, to the Director, Regulatory Support Division, Office of Mission Support (2822T), Environmental Protection Agency, 1200 Pennsylvania Ave. NW, Washington, DC 20460-0001. Please remember to include the OMB control number in any correspondence, but do not submit any completed forms to this address.</P>
                <HD SOURCE="HD2">C. Regulatory Flexibility Act (RFA)</HD>
                <P>
                    I certify this action will not have a significant economic impact on a substantial number of small entities under the RFA, 5 U.S.C. 601 
                    <E T="03">et seq.</E>
                     The small entities subject to the requirements of this action are potential future manufacturers (defined by statute to include importers), processors, and exporters of one or more subject chemical substances for a significant new use designated in the SNUR. The requirement to submit a SNUN applies to any person (including small or large entities) who intends to engage in any activity described in the final rule as a “significant new use.” Because these uses are “new,” based on all information currently available to EPA, the Agency has determined that no small or large entities presently engage in such activities. A SNUR requires that any person who intends to engage in such activity in the future must first notify EPA by submitting a SNUN. EPA's experience to date is that, in response to the promulgation of SNURs covering over 1,000 chemicals, the Agency receives only a small number of notices per year. For example, the number of SNUNs received was 10 in Federal fiscal year (FY) FY2016, 14 in FY2017, 16 in FY2018, five in FY2019, seven in FY2020, and 13 in FY2021, and only a fraction of these were from small businesses. In addition, the Agency currently offers relief to qualifying small businesses by reducing the SNUN submission fee from $19,020 to $3,330. This lower fee reduces the total reporting and recordkeeping cost of submitting a SNUN to about $11,204 for qualifying small firms.
                </P>
                <P>
                    Therefore, the potential economic impacts of complying with this SNUR are not expected to be significant or adversely impact a substantial number of small entities. In a SNUR that published in the 
                    <E T="04">Federal Register</E>
                     of June 2, 1997 (62 FR 29684 (FRL-5597-1)), the Agency presented its general determination that final SNURs are not expected to have a significant economic impact on a substantial number of small entities, which was provided to the Chief Counsel for Advocacy of the Small Business Administration.
                </P>
                <HD SOURCE="HD2">D. Unfunded Mandates Reform Act (UMRA)</HD>
                <P>
                    This action does not contain any unfunded mandates as described in UMRA, 2 U.S.C. 1531-1538, and does not significantly or uniquely affect small governments. Based on EPA's experience with proposing and finalizing SNURs, state, local, and tribal governments have not been impacted by these rulemakings, and EPA does not have any reasons to believe that any state, local, or tribal government will be impacted by this action. As such, EPA has determined that this final rule will not impose any enforceable duty, contain any unfunded mandate, or the otherwise have any effect on small governments subject to the requirements of UMRA section 202, 203, 204, or 205 (2 U.S.C. 1501 
                    <E T="03">et seq.</E>
                    ).
                </P>
                <HD SOURCE="HD2">E. Executive Order 13132: Federalism</HD>
                <P>This action does not have federalism implications as specified in Executive Order 13132 (64 FR 43255, August 10, 1999) because it will not have substantial direct effects on the states, on the relationship between the National Government and the states, or on the distribution of power and responsibilities among the various levels of government.</P>
                <HD SOURCE="HD2">F. Executive Order 13175: Consultation and Coordination With Indian Tribal Governments</HD>
                <P>This action does not have tribal implications as specified in Executive Order 13175 (65 FR 67249, November 9, 2000) because it will not have substantial direct effects on tribal governments, on the relationship between the Federal Government and the Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes. Thus, Executive Order 13175 does not apply to this action.</P>
                <HD SOURCE="HD2">G. Executive Order 13045: Protection of Children From Environmental Health Risks and Safety Risks</HD>
                <P>EPA interprets Executive Order 13045 as applying only to those regulatory actions that concern environmental health or safety risks that EPA has reason to believe may disproportionately affect children, per the definition of “covered regulatory action” in section 2-202 of the Executive order. Therefore, this action is not subject to Executive Order 13045 because it does not concern an environmental health risk or safety risk. Since this action does not concern human health, EPA's Policy on Children's Health also does not apply.</P>
                <P>
                    Although this action does not concern an environmental health or safety risk, the designation of certain uses of PFAS as significant new uses ensures the Agency has an opportunity to review and address potential risks associated with such uses before an entity begins commencing any manufacture (including import) or processing of PFAS for that use. Once EPA receives a notification, EPA must review and make 
                    <PRTPAGE P="1831"/>
                    an affirmative determination on the notification, and take such action as is required by any such determination before the manufacture (including import) or processing for the significant new use can commence. Such a review will assess whether the use identified in the SNUN may present unreasonable risk to health or the environment and ensure that EPA can prevent future unsafe environmental releases of PFAS subject to the SNUR. As discussed previously, EPA is concerned about the potential for adverse health effects from PFAS for children and will evaluate the risk.
                </P>
                <HD SOURCE="HD2">H. Executive Order 13211: Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use</HD>
                <P>This action is not subject to Executive Order 13211 (66 FR 28355, May 22, 2001), because it is not a “significant regulatory action” under Executive Order 12866.</P>
                <HD SOURCE="HD2">I. National Technology Transfer and Advancement Act (NTTAA)</HD>
                <P>This action does not involve any technical standards under the NTTAA section 12(d), 15 U.S.C. 272.</P>
                <HD SOURCE="HD2">J. Executive Order 12898: Federal Actions To Address Environmental Justice in Minority Populations and Low-Income Populations and Executive Order 14096: Revitalizing Our Nation's Commitment to Environmental Justice for All</HD>
                <P>The EPA believes that it is not practicable to assess whether the human health or environmental conditions that exist prior to this action result in disproportionate and adverse effects on communities with environmental justice concerns.</P>
                <P>The Agency believes that the inactive PFAS included in this action are no longer being manufactured (including imported) or processed for any uses in the United States. EPA believes that it is not practicable to assess whether this action is likely to result in new disproportionate and adverse effects on environmental justice communities because the Agency is not able anticipate which chemical substances and uses, if any, will be submitted for a significant new use notice under this action.</P>
                <HD SOURCE="HD2">K. Congressional Review Act (CRA)</HD>
                <P>
                    This action is subject to the CRA, 5 U.S.C. 801 
                    <E T="03">et seq.,</E>
                     and 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</HD>
                    <CFR>40 CFR Part 9</CFR>
                    <P>Environmental protection, Reporting and recordkeeping requirements.</P>
                    <CFR>40 CFR Part 721</CFR>
                    <P>Environmental protection, Chemicals, Hazardous substances, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <SIG>
                    <DATED>Dated: January 8, 2024.</DATED>
                    <NAME>Michal Freedhoff,</NAME>
                    <TITLE>Assistant Administrator, Office of Chemical Safety and Pollution Prevention.</TITLE>
                </SIG>
                <P>Therefore, for the reasons set forth in the preamble, 40 CFR chapter I is amended as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 9—OMB APPROVALS UNDER THE PAPERWORK REDUCTION ACT</HD>
                </PART>
                <REGTEXT TITLE="40" PART="9">
                    <AMDPAR>1. The authority citation for part 9 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>
                             7 U.S.C. 135 
                            <E T="03">et seq.,</E>
                             136-136y; 15 U.S.C. 2001, 2003, 2005, 2006, 2601-2671; 21 U.S.C. 331j, 346a, 31 U.S.C. 9701; 33 U.S.C. 1251 
                            <E T="03">et seq.,</E>
                             1311, 1313d, 1314, 1318, 1321, 1326, 1330, 1342, 1344, 1345 (d) and (e), 1361; E.O. 11735, 38 FR 21243, 3 CFR, 1971-1975 Comp. p. 973; 42 U.S.C. 241, 242b, 243, 246, 300f, 300g, 300g-1, 300g-2, 300g-3, 300g-4, 300g-5, 300g-6, 300j-1, 300j-2, 300j-3, 300j-4, 300j-9, 1857 
                            <E T="03">et seq.,</E>
                             6901-6992k, 7401-7671q, 7542, 9601-9657, 11023, 11048.
                        </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="40" PART="9">
                    <AMDPAR>2. Amend § 9.1 in the table by adding an entry for § 721.11777 in numerical order under the undesignated center heading “Significant New Uses of Chemical Substances” to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 9.1</SECTNO>
                        <SUBJECT>OMB approvals under the Paperwork Reduction Act.</SUBJECT>
                        <STARS/>
                        <GPOTABLE COLS="2" OPTS="L1,tp0,i1" CDEF="s25,12">
                            <TTITLE> </TTITLE>
                            <BOXHD>
                                <CHED H="1">40 CFR citation</CHED>
                                <CHED H="1">
                                    OMB
                                    <LI>control No.</LI>
                                </CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW RUL="s">
                                <ENT I="28">*    *    *    *    *</ENT>
                            </ROW>
                            <ROW EXPSTB="01" RUL="s">
                                <ENT I="21">
                                    <E T="02">Significant New Uses of Chemical Substances</E>
                                </ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW RUL="s">
                                <ENT I="28">*    *    *    *    *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">721.11777</ENT>
                                <ENT>2070-0038</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*    *    *    *    *</ENT>
                            </ROW>
                        </GPOTABLE>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 721—SIGNIFICANT NEW USES OF CHEMICAL SUBSTANCES</HD>
                </PART>
                <REGTEXT TITLE="40" PART="721">
                    <AMDPAR>3. The authority citation for part 721 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 15 U.S.C. 2604, 2607, and 2625(c).</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="40" PART="721">
                    <AMDPAR>4. Add § 721.11777 in numerical order to subpart E to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 721.11777</SECTNO>
                        <SUBJECT>Per- and poly-fluoroalkyl chemical substances designated as inactive on the TSCA Inventory.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Definitions.</E>
                             The definitions in § 721.3 apply to this section.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Chemical substances and significant new uses subject to reporting.</E>
                             (1) The 329 chemical substances identified in paragraphs (b)(1)(i) through (iii) of this section, designated as inactive on the TSCA Chemical Substance Inventory as of January 26, 2023, are subject to reporting under this section for the significant new uses described in paragraph (b)(2) of this section. The requirements of this section do not apply to quantities of the substance that are manufactured or processed as nonisolated intermediates, as defined at 40 CFR 720.3(w), or to quantities of the substance that are manufactured or processed as a byproduct, as defined in 40 CFR 720.3(d), which are not used for commercial purposes.
                        </P>
                        <P>(i) R-(CF2)-CF(R′)″, where both the CF2 and CF moieties are saturated carbons;</P>
                        <P>(ii) R-CF2OCF2-R′, where R and R′ can either be F, O, or saturated carbons; and</P>
                        <P>(iii) CF3C(CF3)R′R″, where R′ and R″ can either be F or saturated carbons.</P>
                        <P>(2) The significant new uses for the chemical substances identified in paragraph (b)(1) of this section are: manufacture (including import) or processing for any use.</P>
                        <P>
                            (c) 
                            <E T="03">Chemical substances not subject to reporting.</E>
                             The chemical substances already subject to a rule under this part, including § 721.9582, and § 721.10536, are not subject to reporting under this section.
                        </P>
                        <P>
                            (d) 
                            <E T="03">Specific requirements.</E>
                             The provisions of subpart A of this part apply to this section.
                        </P>
                    </SECTION>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00412 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <PRTPAGE P="1832"/>
                <AGENCY TYPE="N">GENERAL SERVICES ADMINISTRATION</AGENCY>
                <CFR>41 CFR Part 105-70</CFR>
                <DEPDOC>[FPMR Case 2024-01; Docket No. GSA-FPMR-2023-0027; Sequence No. 1]</DEPDOC>
                <RIN>RIN 3090-AK77</RIN>
                <SUBJECT>Civil Monetary Penalties Inflation Adjustment</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>The Office of the General Counsel, General Services Administration.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Federal Civil Penalties Inflation Adjustment Act of 1990, as amended by the Debt Collection Improvement Act of 1996, and further amended by the Federal Civil Penalties Inflation Adjustment Act Improvement Act of 2015, this final rule applies the inflation adjustments for GSA's civil monetary penalties.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective January 15, 2024.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mr. Aaron Pound, Assistant General Counsel, General Law Division (LG), General Services Administration, 1800 F Street NW, Washington, DC 20405. Telephone Number 202-501-1460.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">I. The Debt Collection Improvement Act of 1996</HD>
                <P>
                    To maintain the remedial impact of civil monetary penalties (CMPs) and to promote compliance with the law, the Federal Civil Penalties Inflation Adjustment Act of 1990 (Pub. L. 101-410) was amended by the Debt Collection Improvement Act of 1996 (Pub. L. 104-134) and the Federal Civil Penalties Inflation Adjustment Act Improvement Act of 2015 (Sec. 701 of Pub. L. 114-74) to require Federal agencies to regularly adjust certain CMPs for inflation. As amended, the law requires each agency to make an initial inflationary adjustment for all applicable CMPs, and to make further adjustments at least once every year thereafter for these penalty amounts. The Debt Collection Improvement Act of 1996 further stipulates that any resulting increases in a CMP due to the calculated inflation adjustments shall apply only to violations which occur after the date the increase takes effect, 
                    <E T="03">i.e.,</E>
                     thirty (30) days after date of publication in the 
                    <E T="04">Federal Register</E>
                    . Pursuant to the 2015 Act, agencies are required to adjust the level of the CMP with an initial “fix“, and make subsequent annual adjustments for inflation. Catch up adjustments are based on the percent change between the Consumer Price Index for Urban Consumers (CPI-U) for the month of October for the year of the previous adjustment, and the October 2015 CPI-U. Annual inflation adjustments will be based on the percent change between the October CPI-U preceding the date of adjustment and the prior year's October CPI-U.
                </P>
                <HD SOURCE="HD1">II. The Program Fraud Civil Remedies Act of 1986</HD>
                <P>
                    Sections 6103 and 6104 of the Omnibus Budget Reconciliation Act of 1986 (Pub. L. 99-509) set forth the Program Fraud Civil Remedies Act of 1986 (PFCRA). Specifically, this statute imposes a CMP and an assessment against any person who, with knowledge or reason to know, makes, submits, or presents a false, fictitious, or fraudulent claim or statement to the Government. The General Services Administration's regulations, published in the 
                    <E T="04">Federal Register</E>
                     (61 FR 246, December 20, 1996) and codified at 41 CFR part 105-70, currently set forth a CMP of up to $13,000 for each false claim or statement made to the agency. Based on the penalty amount inflation factor calculation, derived from originally dividing the October 2022 CPI by the October 2023 CPI and making the CPI-based annual adjustment thereafter, after rounding, we are adjusting the maximum penalty amount for this CMP to $13,400 for each false claim or statement made to the agency.
                </P>
                <HD SOURCE="HD1">III. Waiver of Proposed Rulemaking</HD>
                <P>In developing this final rule, we are waiving the usual notice of proposed rulemaking, public comment, and effective date procedures set forth in the Administrative Procedure Act, 5 U.S.C. 553 (APA). The APA, at 5 U.S.C. 559, provides that a subsequent statute may supersede the APA if it does so expressly. This rulemaking effectuates the statutory requirements set forth in section 4(b)(2) of the 2015 Act, which provides that each agency shall make the annual inflation adjustments “notwithstanding section 553” of the APA. Furthermore, the APA provides an exception to the usual notice of proposed rulemaking, public comment, and effective date procedures when an agency finds there is good cause for dispensing with such procedures on the basis that they are impracticable, unnecessary, or contrary to the public interest. We have determined that, under 5 U.S.C. 553(b)(3)(B) and 553(d)(3), good cause exists for dispensing with these procedures. The 2015 Act provides a non-discretionary cost-of-living formula for making the annual adjustment to the civil monetary penalties. GSA merely performs the ministerial task of calculating the amount of the adjustments. Therefore, under the clear terms of the APA and the language of the 2015 Act, this rule is not subject to notice, an opportunity for public comment, or a delayed effective date, and will be final and effective on January 15, 2024.</P>
                <HD SOURCE="HD1">IV. Executive Orders 12866 and 13563</HD>
                <P>Executive Orders (E.O.s) 12866 and 13563 direct agencies to assess all costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety effects, distributive impacts, and equity). E.O. 13563 emphasizes the importance of quantifying both costs and benefits, of reducing costs, of harmonizing rules, and of promoting flexibility. The Office of Management and Budget (OMB) has reviewed this final rule in accordance with the provisions of E.O. 12866 and has determined that it does not meet the criteria for a significant regulatory action and thus was not subject to review under Section 6(b) of E.O. 12866. As indicated above, the provisions contained in this final rulemaking set forth the inflation adjustments in compliance with the Federal Civil Penalties Inflation Adjustment Act of 1990, as amended, for specific applicable CMPs. The great majority of individuals, organizations and entities addressed through these regulations do not engage in such prohibited conduct, and as a result, we believe that any aggregate economic impact of these revised regulations will be minimal, affecting only those limited few who may engage in prohibited conduct in violation of the statute. As such, this final rule and the inflation adjustment contained therein should have no effect on Federal or state expenditures.</P>
                <HD SOURCE="HD1">V. Congressional Review Act</HD>
                <P>
                    The agency and the Office of Information and Regulatory Affairs, OMB have determined that this rule is not a major rule under 5 U.S.C. 804(2). Subtitle E of the Small Business Regulatory Enforcement Fairness Act of 1996 (codified at 5 U.S.C. 801-808), also known as the Congressional Review Act or CRA, generally provides that before a rule may take effect, the agency promulgating the rule must submit a rule report, which includes a copy of the rule, to each House of the Congress and to the Comptroller General of the United States. GSA will submit a report 
                    <PRTPAGE P="1833"/>
                    containing this rule and other required information to the U.S. Senate, the U.S. House of Representatives, and the Comptroller General of the United States.
                </P>
                <HD SOURCE="HD1">VI. Regulatory Flexibility Act</HD>
                <P>The Regulatory Flexibility Act (RFA) requires an agency to prepare a regulatory flexibility analysis for rules unless the agency certifies that the rule will not have a significant economic impact on a substantial number of small entities. The RFA applies only to rules for which an agency is required to first publish a proposed rule. See 5 U.S.C. 603(a) and 604(a). As explained above, GSA is not required to first publish a proposed rule here. Thus, the RFA does not apply to this final rule.</P>
                <HD SOURCE="HD1">VII. Paperwork Reduction Act</HD>
                <P>This final rule imposes no new reporting or recordkeeping requirements necessitating clearance by OMB.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 41 CFR Part 105-70</HD>
                    <P>Administrative hearing, Claims, Program fraud.</P>
                </LSTSUB>
                <SIG>
                    <NAME>Robin Carnahan,</NAME>
                    <TITLE>Administrator.</TITLE>
                </SIG>
                <P>Accordingly, 41 CFR part 105-70 is amended as set forth below:</P>
                <PART>
                    <HD SOURCE="HED">PART 105-70—IMPLEMENTATION OF THE PROGRAM FRAUD CIVIL REMEDIES ACT OF 1986</HD>
                </PART>
                <REGTEXT TITLE="41" PART="105-70">
                    <AMDPAR>1. The authority citation for part 105-70 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 40 U.S.C. 121(c); 31 U.S.C. 3809.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 105-70.003</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="41" PART="105-70">
                    <AMDPAR>2. Amend § 105-70.003 by—</AMDPAR>
                    <AMDPAR>a. Removing from paragraph (a)(1)(iv) the amount “13,000” and adding “13,400” in its place; and</AMDPAR>
                    <AMDPAR>b. Removing from paragraph (b)(1)(ii) the amount “13,000” and adding “13,400” in its place.</AMDPAR>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00446 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6820-81-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                <CFR>47 CFR Part 54</CFR>
                <DEPDOC>[WC Docket Nos. 10-90, 14-58, 09-197, 16-271; RM 11868; FCC 23-60; FR ID 196019]</DEPDOC>
                <SUBJECT>Connect America Fund</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule; announcement of effective date.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In this document, the Federal Communications Commission (Commission) announces that the Office of Management and Budget (OMB) has approved, for a period of three years, an information collection associated with the rules for Enhanced Alternative Connect America Cost Model (A-CAM) contained in the Commission's 
                        <E T="03">Enhanced A-CAM Order</E>
                         (Order), WC Docket No. 10-90 et al., FCC 23-60. This document is consistent with the 
                        <E T="03">Order,</E>
                         which stated that the Commission would publish a document in the 
                        <E T="04">Federal Register</E>
                         announcing the effective date of the revised information collection requirements.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The amendments to § 54.308(e)(2) and (6) published at 88 FR 55918, August 17, 2023, are effective January 11, 2024.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Jesse Jachman, Wireline Competition Bureau at (202) 418-7400. For additional information concerning the Paperwork Reduction Act information collection requirements contact Nicole Ongele at (202) 418-2991 or via email at 
                        <E T="03">Nicole.Ongele@fcc.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The Commission submitted new information collection requirements for review and approval by OMB, as required by the Paperwork Reduction Act (PRA) of 1995, on November 22, 2023. OMB approved the new information collection requirements on January 2, 2024. The information collection requirements are contained in the Commission's 
                    <E T="03">Enhanced A-CAM Order,</E>
                     FCC 23-60, published at 88 FR 55918, August 17, 2023. The OMB Control Number is 3060-1319. The Commission publishes this document as an announcement of the effective date of the rules published on August 17, 2023. If you have any comments on the burden estimates listed in the following, or how the Commission can improve the collections and reduce any burdens caused thereby, please contact Nicole Ongele, Federal Communications Commission, 45 L Street NE, Washington, DC 20554. Please include the OMB Control Number, 3060-1319, in your correspondence. The Commission will also accept your comments via email at 
                    <E T="03">PRA@fcc.gov.</E>
                     To request materials in accessible formats for people with disabilities (Braille, large print, electronic files, audio format), send an email to 
                    <E T="03">fcc504@fcc.gov</E>
                     or call the Consumer and Governmental Affairs Bureau at (202) 418-0530.
                </P>
                <HD SOURCE="HD1">Synopsis</HD>
                <P>As required by the Paperwork Reduction Act of 1995 (44 U.S.C. 3507), the Commission is notifying the public that it received OMB approval on January 2, 2024, for the amendments to 47 CFR 54.308(e)(2) and (6) published at 88 FR 55918, August 17, 2023.</P>
                <P>Under 5 CFR part 1320, an agency may not conduct or sponsor a collection of information unless it displays a current, valid OMB Control Number. No person shall be subject to any penalty for failing to comply with a collection of information subject to the Paperwork Reduction Act that does not display a current, valid OMB Control Number. The OMB Control Number is 3060-1319. The foregoing notification is required by the Paperwork Reduction Act of 1995, Public Law 104-13, October 1, 1995, and 44 U.S.C. 3507.</P>
                <P>The total annual reporting burdens and costs for the respondents are as follows:</P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     3060-1319.
                </P>
                <P>
                    <E T="03">OMB Approval Date:</E>
                     January 2, 2024.
                </P>
                <P>
                    <E T="03">OMB Expiration Date:</E>
                     January 31, 2027. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Enhanced A-CAM Cybersecurity and Supply Chain Risk Management Plan Requirements. 
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     N/A. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     New collection. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit entities, and State, Local or Tribal governments. 
                </P>
                <P>
                    <E T="03">Number of Respondents and Responses:</E>
                     450 respondents; 900 responses. 
                </P>
                <P>
                    <E T="03">Estimated Time per Response:</E>
                     10-50 hours. 
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     One-time and on occasion reporting requirements. 
                </P>
                <P>
                    <E T="03">Obligation to Respond:</E>
                     Required to obtain or retain benefits. Statutory authority for this information collection is contained in 47 U.S.C. 154(i), 214, 218-220, 254, 303(r), and 403. 
                </P>
                <P>
                    <E T="03">Total Annual Burden:</E>
                     27,000 hours. 
                </P>
                <P>
                    <E T="03">Total Annual Cost:</E>
                     No Cost. 
                </P>
                <P>
                    <E T="03">Needs and Uses:</E>
                     On July 24, 2023, the Commission released the 
                    <E T="03">Enhanced A-CAM Order</E>
                     (Order), 88 FR 55918, August 17, 2023, WC Docket No. 10-90 et al., FCC 23-60, which adopted a voluntary path for supporting the widespread deployment of 100/20 Mbps broadband service throughout the rural areas served by carriers currently receiving Alternative Connect America Cost Model (A-CAM) support and in areas served by rate-of-return carriers eligible to receive legacy support by the end of 2028. The Commission extended by 10 years beyond the remaining five years, for a total of 15 years, the term of support for electing carriers and set a methodology for determining support amounts for locations without 100/20 Mbps broadband service within a potential budget of no more than $1.27 
                    <PRTPAGE P="1834"/>
                    billion annually, or no more than $1.33 billion annually if certain conditions are met, using an updated version of the A-CAM. By adopting this program, the Commission furthered its long-standing goals by promoting the universal availability of voice and broadband networks, while also taking measures to minimize the burden on the nation's ratepayers. The Commission also adopted requirements for the Enhanced A-CAM program to complement existing Federal, state, and local funding programs, so that broadband funding can be used efficiently to maximize the deployment of high-quality broadband service across the United States.
                </P>
                <P>To ensure that the Enhanced A-CAM program does not deprive rural consumers in high-cost areas of broadband service that is as secure as the service deployed pursuant to other Federal funding initiatives, the Commission required Enhanced A-CAM carriers to implement operational cybersecurity and supply chain risk management plans by January 1, 2024—the start of the Enhanced A-CAM support term. Enhanced A-CAM carriers must submit such plans to the Universal Service Administrative Company (USAC) and certify they have done so, by January 2, 2024, or within 30 days of approval under the Paperwork Reduction Act, whichever is later. Failure to submit the plans and make the certification shall result in 25% of monthly support being withheld until the carrier comes into compliance. If a carrier makes a substantive modification to its cybersecurity or supply chain risk management plan, the Commission requires that the carrier submit its updated plan to USAC within 30 days of making that modification.</P>
                <P>The purpose of this information collection is to collect the operational cybersecurity and supply chain risk management plans required of the Enhanced A-CAM carriers by the start of the Enhanced A-CAM support term and address the burdens associated with that requirement.</P>
                <SIG>
                    <FP>Federal Communications Commission.</FP>
                    <NAME>Marlene Dortch,</NAME>
                    <TITLE>Secretary, Office of the Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00417 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                <CFR>47 CFR Part 54</CFR>
                <DEPDOC>[WC Docket No. 17-310; FCC No. 23-110; FR ID 195910]</DEPDOC>
                <SUBJECT>Promoting Telehealth in Rural America</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In this document, the Federal Communications Commission (Commission) seeks to provide vital support to assist rural health care providers with the costs of broadband and other eligible services. By offering discounted rates for these services, the Rural Health Care (RHC) Program enables health care providers to better treat patients in rural areas that often have fewer medical resources and higher service rates than in urban areas.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Effective February 12, 2024, except for §§ 54.601(b) and (c) (amendatory instruction 2) and 54.622(e)(1)(i) through (ii) and (i)(3)(iv) (amendatory instruction 4), which are delayed indefinitely. The Commission will publish a document in the 
                        <E T="04">Federal Register</E>
                         announcing the effective date for those rule sections.
                    </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Philip A. Bonomo, 
                        <E T="03">Philip.Bonomo@fcc.gov,</E>
                         Wireline Competition Bureau, 202-418-7400 or TTY: 202-418-0484. Requests for accommodations should be made as soon as possible in order to allow the agency to satisfy such requests whenever possible. Send an email to 
                        <E T="03">fcc504@fcc.gov</E>
                         or call the Consumer and Governmental Affairs Bureau at (202) 418-0530 (voice), 202-418-0432 (TTY).
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    This is a synopsis of the Commission's Third Report and (
                    <E T="03">Third R&amp;O</E>
                    ) in WC Docket No. 17-310; FCC No. 23-110, adopted on December 13, 2023, and released on December 14, 2023.The full text of this document is available for public inspection during regular business hours at Commission's headquarters 45 L Street NE, Washington, DC 20554 or at the following internet address: 
                    <E T="03">https://docs.fcc.gov/public/attachments/FCC-23-110A1.pdf.</E>
                </P>
                <HD SOURCE="HD1">I. Introduction</HD>
                <P>
                    1. In the 
                    <E T="03">Third R&amp;O,</E>
                     the Commission continues its efforts to improve the effectiveness and efficiency of the Rural Health Care (RHC) Program. The RHC Program offers discounted rates for broadband and other communications services to health care providers who use these increasingly essential services to better treat patients in rural areas that may have limited resources, fewer medical professionals, and higher rates for these services than in urban areas. Broadband-enabled telehealth and telemedicine services in particular have proven to be critical tools for the effective delivery of health care to millions of patients in rural areas, as demonstrated by the heightened dependency on these services during the COVID-19 pandemic. Telemedicine and telehealth make the provision of high-quality health care a reality for patients regardless of location or ability to travel. The measures adopted will enhance the provision of these vital services through the RHC Program.
                </P>
                <P>2. The Commission adopts four revisions to the RHC Program as proposed in the Second Further Notice of Proposed Rulemaking, 88 FR 17495, March 23, 2023 (Second FNPRM) (FCC 23-6), aimed at facilitating participation in and improving the administration of the Program. First, the Commission revises the RHC Program rules to permit conditional approval of eligibility for health care providers that expect to be eligible in the near future to allow them to initiate competitive bidding and request funding. Second, to give participants more flexibility with deadlines, the Commission revises its rules to move back the RHC Program's Service Provider Identification Number (SPIN) change deadline to align with the invoice deadline. Third, the Commission simplifies the rules for determining urban rates by eliminating the seldom-used “standard urban distance” component of the urban rate rules. Fourth, in a separate action to provide more flexibility with deadlines, the Commission revises the RHC Program rules to permit health care providers to request changes to the dates of their evergreen contracts following a funding commitment.</P>
                <P>
                    3. In addition to these revisions, the Commission also on its own motion makes two programmatic improvements to the administration of the RHC Program and Universal Service Fund. To reduce burdens and promote efficiency, the Commission harmonizes the RHC Program eligibility determination process by shifting to the use of a single universal eligibility form for all program participants. Finally, to free up for other uses unclaimed RHC Program support, the Commission establishes a deadline by which health care providers must submit invoices for any undisbursed funding commitments from funding year 2019 and prior that do not currently have an applicable invoice deadline.
                    <PRTPAGE P="1835"/>
                </P>
                <HD SOURCE="HD1">II. Discussion</HD>
                <P>
                    4. In the 
                    <E T="03">Third R&amp;O,</E>
                     the Commission continues to improve the RHC Program by facilitating health care provider participation in and improving the administration of the Program. Specifically, the Commission revises the RHC Program rules to permit conditional eligibility for health care providers and eliminate the seldom-used “standard urban distance” component of the urban rate rule. The Commission also makes two changes relating to RHC Program administrative deadlines by aligning the SPIN change deadline with the existing invoice deadline and permitting health care providers to request a change to evergreen contract dates. The Commission then amends the rules to shift to the use of the same form when determining Telecom and Healthcare Connect Fund (HCF) Program eligibility. Finally, the Commission establishes a deadline by which invoices must be submitted for undisbursed funding commitments from before funding year 2020.
                </P>
                <P>
                    5. 
                    <E T="03">Conditional Approval of Eligibility for Future Eligible Health Care Providers.</E>
                     The Commission first adopts amendments to the RHC Program rules to allow conditional approval of eligibility consistent with what the Commission proposed in the Second FNPRM. The amendments enable entities that do not meet all eligibility requirements at the time they seek eligibility determinations to obtain conditional approval of eligibility, conduct competitive bidding, and request funding prior to receiving formal approval of eligibility. With this change, entities granted such conditional approval may conduct competitive bidding and request funding before they receive formal eligibility approval, ensuring that they are able to participate in the RHC Program for the funding year in which they expect to receive a formal eligibility approval. However, entities with conditional approval will not receive funding commitments until they meet all eligibility requirements. The substantive standard used to determine full eligibility remains unchanged. This change ensures that health care providers that are not yet eligible during the application window, but expect to become eligible in the near future, are not locked out of much needed funding. All commenters who addressed this proposal supported it, and no commenters opposed this change. This change will be effective for funding year 2025, the competitive bidding process for which begins in mid-2024.
                </P>
                <P>6. Eligible health care providers, as defined in section 254(h)(7)(B) of the Communications Act and implemented in the Commission's rules, are limited to the following categories: (1) post-secondary educational institutions offering health care instruction, teaching hospitals, and medical schools; (2) community health centers or health centers providing health care to migrants; (3) local health departments or agencies; (4) community mental health centers; (5) not-for-profit hospitals; (6) rural health clinics; (7) skilled nursing facilities; and (8) consortia of health care providers consisting of one or more entities falling into the first seven categories. In addition, eligible health care providers must be non-profit or public. In the Telecom Program, only eligible health care providers located in a “rural area” defined in § 54.600(e) of the Commission's rules can receive support. The HCF Program, on the other hand, permits rural eligible health care providers as well as non-rural eligible health care providers participating in a majority-rural consortium to receive support.</P>
                <P>
                    7. To allow health care providers to receive RHC Program funding as soon as they become eligible, the Commission amends § 54.601 of its rules to permit entities that expect to meet all eligibility requirements before the end of a given upcoming funding year to request and receive a conditional approval of eligibility. The Commission also amends § 54.622(e)(1) of its rules to allow those entities to make the required certifications when filing a Request for Services to initiate competitive bidding. The amendments adopted will enable entities that receive conditional approval of program eligibility to conduct competitive bidding and submit funding requests 
                    <E T="03">prior</E>
                     to receiving formal approval of eligibility. However, the substantive standard used to determine eligibility remains unchanged. Entities that receive conditional approval of eligibility will not receive funding commitments until they actually become eligible and receive the formal approval of eligibility under the existing substantive standard. No RHC funding shall be committed or disbursed to an entity for any time period that is prior to the date the entity is formally approved as eligible. The Commission directs the Universal Service Administrative Company (Administrator or USAC), upon approval from the Wireline Competition Bureau (Bureau), to implement the conditional approval of eligibility mechanism.
                </P>
                <P>8. This change is warranted given the change to a fixed application filing window in the RHC Program. Before funding year 2016, after an initial application filing window, the Administrator accepted applications on a rolling basis until the last day of the funding year. Since funding year 2017, no applications have been accepted following the close of the initial application window. Beginning in funding year 2021, the Commission's rules require the Administrator to open an initial filing window period with an end date no later than April 1 prior to the start of the funding year.</P>
                <P>9. In 2016, when applications were still accepted on a rolling basis and there were two application windows, the Bureau issued the Hope Community Order, DA 16-855, rel. July 29, 2016 (Hope Order), which held that that if an entity had not demonstrated its eligibility at the time of its eligibility determination form submission for a funding year, it would be ineligible to receive RHC Telecommunications Program support for that funding year. The change the Commission makes eliminates this limitation and allows health care providers to seek conditional eligibility approval so they can participate in the program in the year in which they expect to become fully eligible, even if they receive their full eligibility approval after the initial application window closes. Based on experience administering the program, the Commission finds it appropriate to eliminate the Hope Order's requirement that a site be eligible for RHC Program support, which requires that it qualifies as one of the eligible health care providers defined by section 254(h)(7)(B) of the Communications Act, at the time of its request for eligibility determination. In funding year 2013, the funding year at issue in the Hope Order, the Administrator accepted applications on a rolling basis throughout the funding year, which permitted a health care provider to begin receiving funding for RHC Program supported services within a few months after it became an eligible entity under section 254(h)(7)(B) of the Communications Act. Shortly after meeting eligibility requirements, the health care provider could receive its eligibility determination, engage in competitive bidding, file a Request for Funding during the rolling application window, and start to receive funding.</P>
                <P>
                    10. Absent this change with the current use of a fixed filing window, a health care provider might have to wait more than one year after becoming an eligible health care provider to receive RHC Program funding. For example, if a new medical provider is in the process of opening and expects to become eligible under section 254(h)(7)(B) of the 
                    <PRTPAGE P="1836"/>
                    Communications Act on July 1, 2025, which is after the initial application filing window, it may not be able to receive RHC Program support for funding year 2025 because it could not have been approved as eligible until after the provider's July 1, 2025 opening date. Permitting conditional approvals of eligibility will allow health care providers that are not yet eligible but expect to become an eligible health care provider in a given upcoming funding year to complete competitive bidding and file Requests for Funding so they are able to receive RHC Program funding as soon as they are fully designated as an eligible health care provider under the Commission's rules.
                </P>
                <P>11. To protect the integrity and success of the RHC program and ensure that no RHC Program funding is disbursed for entities that are not yet fully approved as eligible, the Commission adopts the following safeguards for conditional approvals of eligibility. First, to request conditional approval of eligibility, an applicant must submit an eligibility determination form and supporting documentation to the Administrator, which will include the estimated date that it expects to meet all eligibility requirements. The documentation must show that the entity is or reasonably expects to qualify as a public or non-profit health care provider defined in § 54.600(b) of the Commission's rules by the estimated eligibility date. Additionally, if applying for the Telecom Program or if applying as an individual applicant in the HCF Program, the entity must be located or reasonably expect to be located in a rural area defined in § 54.600(e) of the Commission's rules by the estimated eligibility date, or, if not located in such a rural area, for purposes of applying for the HCF Program, be or plan to be a member of a majority-rural HCF Program consortium that satisfies the eligible rural health care provider composition requirement set forth in § 54.607(b) of the Commission's rules by the estimated eligibility date.</P>
                <P>12. Once the Administrator approves an applicant's conditional eligibility, the applicant can proceed to conduct competitive bidding for the conditionally-approved site(s). In order to provide notice of the applicant's conditional eligibility to potential bidders and service providers, an applicant engaging in competitive bidding with conditional eligibility must provide a written indication with its competitive bidding form indicating (1) that the eligibility is conditional, and (2) when the estimated expected eligibility date is. After conducting competitive bidding and signing a service contract, the applicant can submit a funding request during the application filing window for a given funding year, provided that the applicant's estimated expected eligibility date is no later than the end of that funding year. To ensure that no funding is committed or disbursed for health care providers that are conditionally eligible under section 254(h)(7)(B) of the Communications Act or the RHC Program rules, entities with conditional approval of eligibility will not be able to receive funding commitments or disbursements until they meet all eligibility requirements and are granted a formal approval of eligibility. This restriction is consistent with the Commission rule that RHC Program funding is provided to eligible health care providers for services for health care purposes.</P>
                <P>
                    13. An applicant with conditional approval of eligibility is expected to notify the Administrator within 30 calendar days of its actual eligibility date and provide documentation confirming that it is actually eligible. If the Administrator determines that the entity meets the requirements for a public or non-profit health care provider defined in § 54.600(b) Commission's rules and the requirements for rural location or majority-rural HCF consortium membership set forth in the Commission's rules, the Administrator shall formally approve the applicant's eligibility and designate the applicant as an eligible health care provider. The Administrator will then review the applicant's funding request and issue a funding commitment or denial in a timely manner. The funding commitment shall cover only a time period that starts no earlier than the applicant's actual approved eligibility date and that is within the funding year for which support was requested. No funding shall be committed to ineligible entities or entities with only conditional approval and any support erroneously disbursed to ineligible entities or entities with only conditional approval must be recovered. The Commission directs the Administrator to implement these requirements in its procedures and delegate authority to the Bureau to issue further direction consistent with the 
                    <E T="03">Third R&amp;O</E>
                     as necessary.
                </P>
                <P>
                    14. 
                    <E T="03">Alignment of the Service Provider Identification Number Change Deadline with Invoice Deadline.</E>
                     The Commissions next amends its rules to move back the Service Provider Identification Number (SPIN) change filing deadline to align with the invoice filing deadline, rather than the service delivery deadline. A SPIN is a unique number that the Administrator assigns to an eligible service provider seeking to participate in the universal service support programs. An applicant under the HCF Program or Telecom Program may request either a “corrective SPIN change” (in cases not involving a change in the service provider associated with the applicant's funding request number) or an “operational SPIN change” (in cases involving a change to the service provider associated with the applicant's funding request number). The current filing deadline to submit a SPIN change request is no later than the service delivery deadline, which, with limited exceptions, is June 30 of the funding year for which program support is sought. The invoice deadline is 120 days after the later of the service delivery deadline or the date of a revised funding commitment letter. In the Second FNPRM, the Commission proposed to align the SPIN change deadline with the invoice deadline and commenters supported this change.
                </P>
                <P>15. The Commission moves back the deadline for requesting SPIN changes effective funding year 2023 in response to program participant requests asserting that the nature of corrective SPIN changes creates a “recurring hardship for applicants” unable to meet the deadline, which, in turn, results in deadline waiver requests filed with the Commission. According to these participant comments, two commonly recurring situations support a change to the corrective SPIN change deadline: (1) mergers and acquisitions that can occur at any time during the funding year and (2) a service provider that assigns one of its multiple SPINs to a funding request without advising the healthcare provider as to the correct SPIN before invoicing begins, a situation that, in many instances, occurs after the service delivery deadline has passed. These commenters maintain that changing the deadline to request a corrective SPIN change to match the invoice deadline will provide the Administrator with sufficient time to process the change request without the need for applicants to request deadline waivers from the Commission. The Commission agrees with these commenters that the current deadline for requesting corrective SPIN changes imposes unnecessary burdens and challenges for program participants that a later-in-time deadline will largely eliminate.</P>
                <P>
                    16. The Commission moves back the SPIN change deadline to align with the invoice deadline, which, in most cases is 120 days after the close of the funding year, to reduce the need for applicants to seek, and for the Commission to address, waivers of the current 
                    <PRTPAGE P="1837"/>
                    corrective SPIN change deadline. This change facilitates participation in and the administration of the program, while still maintaining an administratively reasonable date by which such change requests must be made. Aligning the SPIN change deadline with the invoice deadline will not cause Program participants to miss the invoice deadline because a SPIN change results in a revised commitment letter, which will create a new invoice deadline 120 days from the issuance of the revised commitment letter.
                </P>
                <P>
                    17. 
                    <E T="03">Simplifying Urban Rate Calculations.</E>
                     In this section, the Commission simplifies the rules for calculating urban rates for the Telecom Program by eliminating the rarely-invoked “standard urban distance” provision from its rules. In the Order on Reconsideration, 88 FR 17379, March 23, 2023 (Order on Recon) (FCC 23-6), the Commission eliminated the Rates Database and reinstated the long-standing rules for calculating urban rates. These rules provide that the urban rate for an eligible service shall be a rate no higher than the highest tariffed or publicly-available rate charged to a commercial customer for a functionally similar service in any city with a population of 50,000 or more in that state. If, however, the service is provided over a distance greater than the standard urban distance, which is the average of the longest diameters of all cities with a population of 50,000 or more within a state, the urban rate is the rate no higher than the highest tariffed or publicly-available rate provided over the standard urban distance. In the Second FNPRM, the Commission proposed to simplify program rules by eliminating the distinction between services provided over and within the standard urban distance and proposed to base all urban rates calculations on rates provided in a city, rather than over the standard urban distance. It also sought comment on the extent to which health care providers rely on the standard urban distance distinction to calculate urban rates.
                </P>
                <P>18. Based on the record, the Commission finds that adopting its proposal to eliminate the standard urban distance provision from the urban rate rules will help simplify the calculation of urban rates in the Telecom Program. Eliminating it will make clearer the process for determining urban rates and there is no evidence that it will adversely impact health care providers because few, if any, Telecom Program participants calculate urban rates using this distinction. No commenters opined on the extent to which health care providers rely on the standard urban distance provision to calculate urban rates, which suggests that standard urban distance was not commonly invoked to calculate urban rates. The only commenter that addressed this proposal, the Schools, Health &amp; Libraries Broadband (SHLB) Coalition, supported this change. Therefore, the Commission adopts the proposal to base all urban rates calculations on rates provided in a city rather than over the standard urban distance. This change shall be applicable for funding year 2025.</P>
                <P>
                    19. 
                    <E T="03">Change of Evergreen Contract Dates.</E>
                     The Commission next amends the RHC Program rules to permit health care providers to request a change in the evergreen contract dates following a funding commitment. Upon approving such a change, the Administrator will issue a revised funding commitment letter. This change will provide health care providers with the benefits of evergreen contract designation across the full length of the contract's term while also reducing the need for health care providers to seek relief from the Administrator in cases where a post-commitment evergreen contract date change is necessary. This new rule will become effective for funding year 2024.
                </P>
                <P>20. Evergreen contracts are multi-year agreements under which covered services are exempt from the competitive bidding requirements for the term of the contract, which may be extended by up to an aggregate of five years. When the Administrator issues a funding commitment letter, it sets the period for an evergreen contract based on the estimated service start and end dates provided by the health care provider on the Request for Funding. However, as the Commission explained in the Second FNPRM, services sometimes start after the estimated service start date, which means that the evergreen status of the contract expires before it would have if the evergreen designation period was based on the actual service start date. In the Second FNPRM, the Commission sought comments on whether there should be a process for health care providers to change evergreen contract dates after a funding commitment has been made. The Commission also requested comments on how such a process could be accomplished.</P>
                <P>21. SHLB and New England Telehealth Consortium (NETC) support, and no party opposes, allowing health care providers to request changes to their evergreen contract dates in cases when the contract supports those changes. SHLB maintains that such requests should always be deemed timely and not precluded by expiration of the 60-day window for an appeal of the original funding commitment. SHLB also suggests that the Commission clarify that the Administrator should defer to the parties' interpretation of a contract's start and end date unless it is “obviously inconsistent” with the language of the contract.</P>
                <P>22. The Commission agrees with SHLB and NETC that health care providers should be permitted to request evergreen contract changes following a funding commitment provided the contract supports a change. Aligning a contract's actual service start date with the start date that determines the duration of the evergreen contract period will exempt health care providers from the competitive bidding process for the full length of the contract, thereby providing certainty to RHC Program participants. This change will not alter rules or processes for multi-year commitments or other competitive bidding exemptions. Accordingly, the Commission amends the RHC Program rules to allow health care providers to request changes to evergreen contract dates, subject to the following two requirements.</P>
                <P>23. First, the Commission requires that the terms of the evergreen contract support any requested date change. For example, an evergreen contract that specifies a start date effective upon signature of the contracting parties would not be eligible for a contract date change because the start date is a date established by the contract independent of the service start date. By contrast, an evergreen contract with terms specifying a start date tied to the commencement of services yet to be delivered would be eligible for a date change regardless of the date of signature. The Commission makes clear that any changes to the dates of the evergreen contract must be supported by the contract, and declines to adopt SHLB's suggestion that the Administrator defer to the contracting parties' interpretation on the contract timing. As in the case of “verification of discounts, offsets, or support amounts” as a general matter under § 54.707 of the Commission's rules, it will be incumbent upon applicants to ensure that the available evidence sufficiently justifies a given date change.</P>
                <P>
                    24. Second, the Commission requires that health care providers request an evergreen contract change within 60 days of the date service commences. This 60-day window should provide health care providers with ample time to request a date change without having to resort to appealing the original funding commitment, which addresses the timing concern raised by SHLB and 
                    <PRTPAGE P="1838"/>
                    NETC. The Commission declines, however, to adopt SHLB's approach that all requests for evergreen contract changes be deemed timely. Such an open-ended option would provide no incentive to health care providers to promptly notify the Administrator of evergreen contract date changes. To memorialize the changed evergreen contract dates, the Commission directs the Administrator to issue a revised funding commitment letter to the health care provider reflecting the changed dates. If the Administrator denies a requested change, the Commission directs it to issue a letter to the health care provider explaining the basis for the denial. Finally, the Commission directs the Administrator to develop procedures subject to prior Bureau approval for accepting changes to evergreen contract dates consistent with the amended Commission's rules § 54.622(i)(3), and to publicize instructions on requesting changes to evergreen contract dates with the stakeholder community.
                </P>
                <P>
                    25. 
                    <E T="03">Single Eligibility Form.</E>
                     To reduce burdens on Telecom Program applicants and improve the efficiency and operation of the RHC Program, the Commission next harmonizes the RHC Program eligibility determination process by establishing a single eligibility determination form for both the Telecom Program and the HCF Program that is required to be filed only once. Applicants must first be determined eligible under section 254(h)(7)(B) of the Communications Act and RHC Program rules to receive support from the RHC Program. The Telecom Program and the HCF Program currently have different procedures for eligibility determinations. In the Telecom Program, applicants seeking eligibility determinations use the FCC Form 465 (Description of Services Requested and Certification Form), which is the same form used to initiate competitive bidding. Thus, even though most Telecom Program applicants' eligibilities are very unlikely to change from year to year, they are required to provide, and the Administrator is required to review, information regarding their eligibility statuses every time there is a new competitive bidding process, which is generally every year.
                </P>
                <P>26. In contrast, when the HCF Program was established in 2012, the Commission instituted a more efficient process for eligibility determinations by separating the process for eligibility determination from the process for competitive bidding. In the HCF Program, applicants file an FCC Form 460 (Eligibility and Registration Form) to seek a one-time eligibility determination that remains in place unless there is a material change in the entity's eligibility. After receiving this eligibility determination, the applicant may file an FCC Form 461 (Request for Services Form) to initiate competitive bidding. Thus, applicants are able to know whether they are eligible before they spend time and resources planning competitive bidding. Because the FCC Form 460 is filed only once, the eligibility determination process in the HCF Program improves efficiency and reduces costs and time for both health care providers and the Administrator.</P>
                <P>27. Therefore, beginning funding year 2025, the FCC Form 460 will be used for eligibility determinations in the Telecom Program and the eligibility determination portion will be eliminated from the FCC Form 465. As a result of this change, starting for funding year 2025, the FCC Form 465 will be used solely for competitive bidding in the Telecom Program while the FCC Form 461 will continue to be used for competitive bidding in the HCF Program. Because there are certain differences in eligibility requirements between the Telecom Program and the HCF Program, applicants who are determined eligible in one program are not necessarily eligible in the other program even though one eligibility determination form is used for both programs. For example, non-rural public or non-profit health care providers who are members of majority-rural consortia are eligible to receive support under the HCF Program, but not under the Telecom Program. Thus, in this example, applicants whose FCC Form 460s are submitted specifically for the HCF Program and approved on that basis are not automatically eligible for support in the Telecom Program and must seek eligibility determinations in the Telecom Program if they subsequently wish to demonstrate their eligibility for that program. The Commission directs the Bureau to amend the FCC Form 460 for eligibility determinations for both the Telecom Program and the HCF Program and direct the Administrator to track whether a health care provider is eligible for the Telecom Program, the HCF Program, or both.</P>
                <P>28. As part of adopting the FCC Form 460 for the Telecom Program, the Commission also amends § 54.601(b) of its rules to extend it to the Telecom Program effective for funding year 2025. Section 54.601(b) of the Commission's rules addresses the timing requirements for eligibility determinations in the HCF Program and requires health care providers to notify the Administrator of changes to their name, location, contact information, or eligible entity type. It was adopted when the Commission established the HCF Program in 2012 as a procedural rule for specifying the process for determining health care provider eligibility in the HCF Program. There are no corresponding rules for the eligibility determination process in the Telecom Program where applicants previously had to make a new eligibility showing every year they wished to seek support. Since a single eligibility determination form will be used for both programs, and thus now in the Telecom Program, like the HCF Program, applicants will be required to file separate forms for eligibility determination and request for services, and findings of eligibility will remain in place absent a material change in circumstances, it is reasonable to amend § 54.601(b) of the Commission's rules to make it apply to both programs to provide greater clarity to program participants.</P>
                <P>29. To further reduce unnecessary burdens and ease the implementation of this change, the Commission directs the Administrator to deem presumptively eligible for funding year 2025 and beyond any health care provider with an existing eligibility approval in the Telecom Program. Because the eligibility status of health care providers rarely changes, an additional up-front eligibility determination for funding year 2025 is unnecessary. This direction is consistent with the eligibility determination process in the HCF Program. The Commission reminds any health care providers with changes to conditions that might impact their eligibility status of the requirement to update the Administrator within 30 days of the change. As before, health care providers in both the Telecom and HCF Programs are required to certify their eligibility when filing a Request for Services to initiate competitive bidding.</P>
                <P>30. The Commission emphasizes that its actions do not change the substantive requirements for determining eligibility in the RHC Program. It is the RHC Program applicants' obligation to submit accurate information and certifications regarding their eligibility, including the obligation to notify the Administrator within 30 days of a material change in their eligibility information. Because health care provider eligibility is limited by the Act, the Commission does not have discretion to waive eligibility requirements, and must recover any support erroneously disbursed to ineligible entities.</P>
                <P>
                    31. 
                    <E T="03">De-Obligation of Undisbursed, Un-Invoiced Commitments.</E>
                     The Commission establishes a deadline of July 1, 2024, for Telecom Program 
                    <PRTPAGE P="1839"/>
                    participants to submit invoices for funding years 2019 and earlier, the period during which there was no invoice deadline in the Telecom Program. After that date, funding commitments from funding year 2019 and earlier that have not yet been invoiced will be de-obligated and will not be able to be invoiced. The Commission established an invoice deadline for the Telecom Program effective funding year 2020 in the 
                    <E T="03">Promoting Telehealth Report and Order,</E>
                     84 FR 54952, Oct. 11, 2019. The Commission explained that this deadline of 120 days from the service delivery deadline supported the “harmonization of the invoice deadline for RHC programs” and provided “applicants with sufficient time to submit their invoices and seek reimbursements from the Administrator,” while being “necessary for the efficient administration of the RHC program.”
                </P>
                <P>32. There is currently $22.2 million in undisbursed, un-invoiced commitments from funding year 2019 and earlier, when there was no invoice submission deadline. Establishing an invoice submission deadline of July 1, 2024, for Telecom Program funding requests from funding year 2019 and earlier and de-obligating unused funding is appropriate for several reasons. It is highly unlikely, given the significant lapse of time, that a significant portion of this funding will ever be invoiced, and some of these commitments may be for services that were ultimately never used. At this point, the Administrator receives very few invoices for services from prior to funding year 2019. Further, this deadline provides ample time for Program participants to assess whether they have undisbursed commitments requiring invoicing and to complete the invoicing process for those funding requests. Any funding de-obligated as a result of this change can be used for more useful purposes.</P>
                <P>33. Therefore, all existing Telecom Program commitments from funding year 2019 and earlier must be invoiced by July 1, 2024. This decision does not affect the invoice deadline for Telecom Program funding requests for funding year 2020 and later, which are subject to the invoice deadlines established in § 54.627 of the Commission's rules. In the event that the Administrator issues a funding commitment in the future for a funding request for funding year 2019 or earlier, invoices for that funding commitment must be submitted within 120 days of the issuance of a commitment letter.</P>
                <HD SOURCE="HD1">III. Procedural Matters</HD>
                <HD SOURCE="HD2">A. Paperwork Reduction Act Analysis</HD>
                <P>
                    34. This document contains new and modified information collection requirements subject to the Paperwork Reduction Act of 1995 (PRA), Public Law 104-13. All such requirements will be submitted to the Office of Management and Budget (OMB) for review under section 3507(d) of the PRA. OMB, the general public, and other federal agencies will be invited to comment on any new or modified information collection requirements contained in this proceeding. The Commission will publish a separate document in the 
                    <E T="04">Federal Register</E>
                     at a later date seeking these comments. In addition, its noted that, pursuant to the Small Business Paperwork Relief Act of 2002, Public Law 107-198, 
                    <E T="03">see</E>
                     44 U.S.C. 3506(c)(4), the Commission previously sought specific comment on how it might further reduce the information collection burden for small business concerns with fewer than 25 employees.
                </P>
                <P>35. In this present document, the Commission has assessed the effects of allowing conditional approvals of eligibility, allowing changes to evergreen contract dates, and adopting for the entire RHC Program eligibility form filing requirements that previously existed only in the HCF Program and finds that the additional funding and administrative conveniences these changes give health care providers justify these changes.</P>
                <HD SOURCE="HD2">B. Congressional Review Act</HD>
                <P>
                    36. The Commission has determined and the Administrator of the Office of Information and Regulatory Affairs, Office of Management and Budget, concurs that the rules are non-major under the Congressional Review Act, 5 U.S.C. 804(2). The Commission will send a copy of the 
                    <E T="03">Third R&amp;O</E>
                     to Congress and the Government Accountability Office pursuant to Congressional Review Act, 
                    <E T="03">see</E>
                     5 U.S.C. 801(a)(1)(A).
                </P>
                <P>
                    37. In addition, the Commission will send a copy of the 
                    <E T="03">Third R&amp;O,</E>
                     including the Final Regulatory Flexibility Analysis (FRFA), to the Chief Counsel for Advocacy of the Small Business Administration pursuant to the Small Business Regulatory Enforcement Fairness Act of 1996.
                </P>
                <HD SOURCE="HD2">C. Final Regulatory Flexibility Analysis</HD>
                <P>
                    38. The Regulatory Flexibility Act of 1980, as amended (RFA), requires that an agency prepare a regulatory flexibility analysis for notice-and-comment rulemaking proceedings, unless the agency certifies that “the rule will not, if promulgated, have a significant economic impact on a substantial number of small entities.” Accordingly, the Commission has prepared an FRFA concerning the potential impact of the rule and policy changes adopted in the 
                    <E T="03">Third R&amp;O.</E>
                </P>
                <P>39. As required by the RFA, an Initial Regulatory Flexibility Analysis (IRFA) was incorporated into the Second FNPRM, FCC 23-6, rel. January 27, 2023. The Commission sought written public comment on the proposals in the Second FNPRM, including comment on the IRFA. No comments were filed addressing the IRFA. This FRFA conforms to the RFA.</P>
                <HD SOURCE="HD3">i. Need for, and Objectives of, the Third R&amp;O</HD>
                <P>
                    40. In the 
                    <E T="03">Third R&amp;O,</E>
                     the Commission seeks to further improve the Rural Health Care (RHC) Program's capacity to distribute telecommunications and broadband support to health care providers—especially small, rural healthcare providers (HCPs)—in the most equitable and efficient manner possible. Over the years, telehealth has become an increasingly vital component of healthcare delivery to rural Americans. Rural healthcare facilities are typically limited by the equipment and supplies they have and the scope of services they can offer, which ultimately can have an impact on the availability of high-quality health care. Therefore, the RHC Program plays a critical role in overcoming some of the obstacles healthcare providers face in delivering their services to rural communities. Considering the significance of RHC Program support, the Commission implements several measures to most effectively meet HCPs' needs while responsibly distributing the RHC Program's limited funds.
                </P>
                <P>
                    41. Additionally, the 
                    <E T="03">Third R&amp;O</E>
                     adopts proposals from the Second FNPRM that allow conditional approvals of eligibility to allow soon-to-be eligible providers to engage in competitive bidding, align the Service Provider Identification Number (SPIN) change deadline with the invoice deadline, simplify urban rate calculations, and allow health care providers to change evergreen contract dates. The Commission also harmonizes the RHC Program eligibility determination process by establishing a single eligibility determination form for the Telecom Program and RHC program and announce a new deadline for the de-obligation of undisbursed, un-invoiced commitments.
                    <PRTPAGE P="1840"/>
                </P>
                <HD SOURCE="HD3">ii. Summary of Significant Issues Raised by Public Comments in Response to the IRFA</HD>
                <P>42. There were no comments filed that specifically address the rules and policies proposed in the IRFA.</P>
                <HD SOURCE="HD3">iii. Response to Comments by the Chief Counsel for Advocacy of the Small Business Administration</HD>
                <P>43. Pursuant to the Small Business Jobs Act of 2010, which amended the RFA, the Commission is required to respond to any comments filed by the Chief Counsel of the Small Business Administration (SBA), and to provide a detailed statement of any change made to the proposed rule(s) as a result of those comments. The Chief Counsel did not file any comments in response to the proposed rules in this proceeding.</P>
                <HD SOURCE="HD3">iv. Description and Estimate of the Number of Small Entities to Which the Rules Will Apply</HD>
                <P>44. The RFA directs agencies to provide a description of and, where feasible, an estimate of the number of small entities that may be affected by the rules adopted herein. The RFA generally defines the term “small entity” as having the same meaning as the terms “small business,” “small organization,” and “small governmental jurisdiction.” In addition, the term “small business” has the same meaning as the term “small business concern” under the Small Business Act. A “small business concern” is one that: (1) is independently owned and operated; (2) is not dominant in its field of operation; and (3) satisfies any additional criteria established by SBA.</P>
                <P>
                    45. 
                    <E T="03">Small Businesses, Small Organizations, Small Governmental Jurisdictions.</E>
                     The Commission's actions, over time, may affect small entities that are not easily categorized at present. The Commission therefore describes, at the outset, three broad groups of small entities that could be directly affected herein. First, while there are industry specific size standards for small businesses that are used in the regulatory flexibility analysis, according to data from SBA's Office of Advocacy, in general a small business is an independent business having fewer than 500 employees. These types of small businesses represent 99.9% of all businesses in the United States, which translates to 33.2 million businesses.
                </P>
                <P>46. Next, the type of small entity described as a “small organization” is generally “any not-for-profit enterprise which is independently owned and operated and is not dominant in its field.” The Internal Revenue Service (IRS) uses a revenue benchmark of $50,000 or less to delineate its annual electronic filing requirements for small exempt organizations. Nationwide, for tax year 2020, there were approximately 447,689 small exempt organizations in the U.S. reporting revenues of $50,000 or less according to the registration and tax data for exempt organizations available from the IRS.</P>
                <P>47. Finally, the small entity described as a “small governmental jurisdiction” is defined generally as “governments of cities, counties, towns, townships, villages, school districts, or special districts, with a population of less than fifty thousand.” U.S. Census Bureau data from the 2017 Census of Governments indicate there were 90,075 local governmental jurisdictions consisting of general purpose governments and special purpose governments in the United States. Of this number, there were 36,931 general purpose governments (county, municipal, and town or township) with populations of less than 50,000 and 12,040 special purpose governments—independent school districts with enrollment populations of less than 50,000. Accordingly, based on the 2017 U.S. Census of Governments data, the Commission estimates that at least 48,971 entities fall into the category of “small governmental jurisdictions.”</P>
                <HD SOURCE="HD3">a. Healthcare Providers</HD>
                <P>
                    48. 
                    <E T="03">Offices of Physicians (except Mental Health Specialists).</E>
                     This industry comprises establishments of health practitioners having the degree of M.D. (Doctor of Medicine) or D.O. (Doctor of Osteopathy) primarily engaged in the independent practice of general or specialized medicine (except psychiatry or psychoanalysis) or surgery. These practitioners operate private or group practices in their own offices (
                    <E T="03">e.g.,</E>
                     centers, clinics) or in the facilities of others, such as hospitals or health maintenance organization (HMO) medical centers. The SBA small business size standard for this industry classifies a business having annual receipts of $14 million or less as small. The 2017 Economic Census indicates that 137,366 firms operated in this industry for the entire year. Of this number, 126,098 firms had revenue of less than $10 million. Based on this data, the Commission concludes that a majority of firms operating in this industry are small under the SBA size standard.
                </P>
                <P>
                    49. 
                    <E T="03">Offices of Dentists.</E>
                     This industry comprises establishments of health practitioners having the degree of D.M.D. (Doctor of Dental Medicine), D.D.S. (Doctor of Dental Surgery), or D.D.Sc. (Doctor of Dental Science) primarily engaged in the independent practice of general or specialized dentistry or dental surgery. These practitioners operate private or group practices in their own offices (
                    <E T="03">e.g.,</E>
                     centers, clinics) or in the facilities of others, such as hospitals or HMO medical centers. They can provide either comprehensive preventive, cosmetic, or emergency care, or specialize in a single field of dentistry. The SBA small business size standard for this industry classifies a business having annual receipts of $8 million or less as small. The 2017 Economic Census indicates that 113,795 firms operated in this industry for the entire year. Of that number, 112,332 firms had revenue of less than $5 million. Based on this data, the Commission concludes that a majority of dental businesses are small entities.
                </P>
                <P>
                    50. 
                    <E T="03">Offices of Chiropractors.</E>
                     This industry comprises establishments of health practitioners having the degree of DC (Doctor of Chiropractic) primarily engaged in the independent practice of chiropractic. These practitioners provide diagnostic and therapeutic treatment of neuromusculoskeletal and related disorders through the manipulation and adjustment of the spinal column and extremities, and operate private or group practices in their own offices (
                    <E T="03">e.g.,</E>
                     centers, clinics) or in the facilities of others, such as hospitals or HMO medical centers. The SBA small business size standard for this industry classifies a business having annual receipts of $8 million or less as small. The 2017 Economic Census indicates that 34,414 firms operated in this industry for the entire year. Of that number, 34,366 firms operated with revenue of less than $5 million per year. Based on this data, the Commission concludes that a majority of chiropractors are small.
                </P>
                <P>
                    51. 
                    <E T="03">Offices of Optometrists.</E>
                     This industry comprises establishments of health practitioners having the degree of O.D. (Doctor of Optometry) primarily engaged in the independent practice of optometry. These practitioners examine, diagnose, treat, and manage diseases and disorders of the visual system, the eye and associated structures as well as diagnose related systemic conditions. Offices of optometrists prescribe and/or provide eyeglasses, contact lenses, low vision aids, and vision therapy. They operate private or group practices in their own offices (
                    <E T="03">e.g.,</E>
                     centers, clinics) or in the facilities of others, such as hospitals or HMO medical centers, and may also provide the same services as opticians, such as selling and fitting prescription eyeglasses and contact 
                    <PRTPAGE P="1841"/>
                    lenses. The SBA small business size standard for this industry classifies a business having annual receipts of $8 million or less as small. The 2017 Economic Census indicates that 17,879 firms operated in this industry for the entire year. Of this number, 16,792 firms had revenue of less than $5 million. Based on this data, the Commission concludes that a majority of firms in this industry are small.
                </P>
                <P>
                    52. 
                    <E T="03">Offices of Mental Health Practitioners (except Physicians).</E>
                     This industry comprises establishments of independent mental health practitioners (except physicians) primarily engaged in (1) the diagnosis and treatment of mental, emotional, and behavioral disorders and/or (2) the diagnosis and treatment of individual or group social dysfunction brought about by such causes as mental illness, alcohol and substance abuse, physical and emotional trauma, or stress. These practitioners operate private or group practices in their own offices (
                    <E T="03">e.g.,</E>
                     centers, clinics) or in the facilities of others, such as hospitals or HMO medical centers. The SBA small business size standard for this industry classifies a business having annual receipts of $8 million or less as small. The 2017 Economic Census indicates that 19,316 firms operated in this industry for the entire year. Of that number, 13,318 firms had revenue of less than $5 million. Based on this data, the Commission concludes that a majority of mental health practitioners who do not employ physicians are small.
                </P>
                <P>
                    53. 
                    <E T="03">Offices of Physical, Occupational and Speech Therapists and Audiologists.</E>
                     This industry comprises establishments of independent health practitioners primarily engaged in one of the following: (1) providing physical therapy services to patients who have impairments, functional limitations, disabilities, or changes in physical functions and health status resulting from injury, disease or other causes, or who require prevention, wellness or fitness services; (2) planning and administering educational, recreational, and social activities designed to help patients or individuals with disabilities, regain physical or mental functioning or to adapt to their disabilities; and (3) diagnosing and treating speech, language, or hearing problems. These practitioners operate private or group practices in their own offices (
                    <E T="03">e.g.,</E>
                     centers, clinics) or in the facilities of others, such as hospitals or HMO medical centers. The SBA small business size standard for this industry classifies a business having annual receipts of $11 million or less as small. The 2017 Economic Census indicates that 22,402 firms in this industry operated for the entire year. Of that number, 21,712 firms had revenue of less than $5 million. Based on this data, the Commission concludes that a majority of businesses in this industry are small.
                </P>
                <P>
                    54. 
                    <E T="03">Offices of Podiatrists.</E>
                     This industry comprises establishments of health practitioners having the degree of D.P.M. (Doctor of Podiatric Medicine) primarily engaged in the independent practice of podiatry. These practitioners diagnose and treat diseases and deformities of the foot and operate private or group practices in their own offices (
                    <E T="03">e.g.,</E>
                     centers, clinics) or in the facilities of others, such as hospitals or HMO medical centers. The SBA small business size standard for this industry classifies a business having annual receipts of $8 million or less as small. The 2017 Economic Census indicates that 6,673 firms operated in this industry for the entire year. Of that number, 6,235 firms had revenue of less than $5 million. Based on this data, the Commission concludes that a majority of firms in this industry are small.
                </P>
                <P>
                    55. 
                    <E T="03">Offices of All Other Miscellaneous Health Practitioners.</E>
                     This industry comprises establishments of independent health practitioners (except physicians; dentists; chiropractors; optometrists; mental health specialists; physical, occupational, and speech therapists; audiologists; and podiatrists). These practitioners operate private or group practices in their own offices (
                    <E T="03">e.g.,</E>
                     centers, clinics) or in the facilities of others, such as hospitals or HMO medical centers. The SBA small business size standard for this industry classifies firms having annual receipts of $9 million or less as small. The 2017 Economic Census indicates that 14,194 firms in this industry operated the entire year. Of that number, 10,874 firms had revenue of less than $5 million. Based on this data, the Commission concludes the majority of firms in this industry are small.
                </P>
                <P>
                    56. 
                    <E T="03">Family Planning Centers.</E>
                     This industry comprises establishments with medical staff primarily engaged in providing a range of family planning services on an outpatient basis, such as contraceptive services, genetic and prenatal counseling, voluntary sterilization, and therapeutic and medically induced termination of pregnancy. The SBA small business size standard for this industry classifies firms having annual receipts of $16.5 million or less as small. The 2017 Economic Census indicates that 1,339 firms in this industry operated for the entire year. Of that number, 1,014 firms had revenue of less than $10 million. Based on this data, the Commission concludes that the majority of firms in this industry is small.
                </P>
                <P>
                    57. 
                    <E T="03">Outpatient Mental Health and Substance Abuse Centers.</E>
                     This industry comprises establishments with medical staff primarily engaged in providing outpatient services related to the diagnosis and treatment of mental health disorders and alcohol and other substance abuse. These establishments generally treat patients who do not require inpatient treatment. They may provide a counseling staff and information regarding a wide range of mental health and substance abuse issues and/or refer patients to more extensive treatment programs, if necessary. The SBA small business size standard for this industry classifies a firm as small if it has $16.5 million or less in annual receipts. The 2017 Economic Census indicates that 5,637 firms operated for the entire year. Of this number, 4,534 firms had of less than $10 million. Based on this data, the Commission concludes that a majority of firms in this industry are small.
                </P>
                <P>
                    58. 
                    <E T="03">HMO Medical Centers.</E>
                     This industry comprises establishments with physicians and other medical staff primarily engaged in providing a range of outpatient medical services to the HMO subscribers with a focus generally on primary health care. These establishments are owned by the HMO. HMO establishments that both provide health care services and underwrite health and medical insurance policies are also included in this industry. The SBA small business size standard for this industry classifies firms having $39 million or less in annual receipts as small. The 2017 U.S. Economic Census indicates that 17 firms in this industry operated for the entire year. However, the 2017 Economic Census does not provide disaggregated financial information for this industry, therefore the Commission cannot determine how many of the firms in this industry are small under the SBA small business size standard.
                </P>
                <P>
                    59. 
                    <E T="03">Freestanding Ambulatory Surgical and Emergency Centers.</E>
                     This industry comprises establishments with physicians and other medical staff primarily engaged in (1) providing surgical services (
                    <E T="03">e.g.,</E>
                     orthoscopic and cataract surgery) on an outpatient basis or (2) providing emergency care services (
                    <E T="03">e.g.,</E>
                     setting broken bones, treating lacerations, or tending to patients suffering injuries as a result of accidents, trauma, or medical conditions necessitating immediate medical care) on an outpatient basis. 
                    <PRTPAGE P="1842"/>
                    Outpatient surgical establishments have specialized facilities, such as operating and recovery rooms, and specialized equipment, such as anesthetic or X-ray equipment. The SBA small business size standard for this industry classifies firms having annual receipts of $16.5 million or less as small. The 2017 U.S. Economic Census indicates that 3,888 firms in this industry operated for the entire year. Of that number, 3,132 firms had revenue of less than $10 million. Based on this data, the Commission concludes that a majority of firms in this industry are small.
                </P>
                <P>
                    60. 
                    <E T="03">All Other Outpatient Care Centers.</E>
                     This industry comprises establishments with medical staff primarily engaged in providing general or specialized outpatient care (except family planning centers, outpatient mental health and substance abuse centers, HMO medical centers, kidney dialysis centers, and freestanding ambulatory surgical and emergency centers). Centers or clinics of health practitioners with different degrees from more than one industry practicing within the same establishment (
                    <E T="03">i.e.,</E>
                     Doctor of Medicine and Doctor of Dental Medicine) are included in this industry. The SBA small business size standard for this industry classifies a business with annual receipts of $22.5 million or less as small. The 2017 U.S. Economic Census indicates that 5,524 firms operated in this industry for the entire year. Of this number, 4,584 firms had revenue of less than $10 million. Based on this data, the Commission concludes that a majority of firms in this industry are small.
                </P>
                <P>
                    61. 
                    <E T="03">Blood and Organ Banks.</E>
                     This industry comprises establishments primarily engaged in collecting, storing, and distributing blood and blood products and storing and distributing body organs. The SBA small business size standard for this industry classifies firms having annual receipts of $35 million or less as small. The 2017 U.S. Census Bureau data indicate that 293 firms operated in this industry for the entire year. Of that number, 219 firms operated with revenue of less than $25 million. Based on this data, the Commission concludes the major of firms that operate in this industry are small.
                </P>
                <P>
                    62. 
                    <E T="03">All Other Miscellaneous Ambulatory Health Care Services.</E>
                     This U.S. industry comprises establishments primarily engaged in providing ambulatory health care services (except offices of physicians, dentists, and other health practitioners; outpatient care centers; medical and diagnostic laboratories; home health care providers; ambulances; and blood and organ banks). The SBA small business size standard for this industry classifies businesses having annual receipts of $18 million or less as small. 2017 U.S. Bureau Census data show that 2,968 firms operated in this industry for the entire year. Of that number, 2,810 firms had revenue of less than $10 million. Based on this data, the Commission concludes that a majority of the firms in this industry are small. This industry comprises establishments known as medical laboratories primarily engaged in providing analytic or diagnostic services, including body fluid analysis, generally to the medical profession or to the patient on referral from a health practitioner. The SBA small business size standard for this industry classifies a business as small if it has annual receipts of $36.5 million or less. 2017 U.S. Census Bureau data indicate that 2,799 firms operated in this industry for the entire year. Of this number, 2,640 firms had revenue of less than $25 million. Based on this data, the Commission concludes that a majority of firms that operate in this industry are small.
                </P>
                <P>
                    63. 
                    <E T="03">Medical Laboratories.</E>
                     This industry comprises establishments known as medical laboratories primarily engaged in providing analytic or diagnostic services, including body fluid analysis, generally to the medical profession or to the patient on referral from a health practitioner. The SBA small business size standard for this industry classifies a business as small if it has annual receipts of $36.5 million or less. 2017 U.S. Census Bureau data indicate that 2,799 firms operated in this industry for the entire year. Of this number, 2,640 firms had revenue of less than $25 million. Based on this data, the Commission concludes that a majority of firms that operate in this industry are small.
                </P>
                <P>
                    64. 
                    <E T="03">Diagnostic Imaging Centers.</E>
                     This U.S. industry comprises establishments known as diagnostic imaging centers primarily engaged in producing images of the patient generally on referral from a health practitioner. The SBA small business size standard for this industry classifies firms having annual receipts of $16.5 million or less as small. The 2017 U.S. Economic Census indicates that 3,556 firms operated in this industry for the entire year. Of that number, 3,233 firms had revenue of less than $10 million. Based on this data, the Commission concludes that a majority of firms that operate in this industry are small.
                </P>
                <P>
                    65. 
                    <E T="03">Home Health Care Services.</E>
                     This industry comprises establishments primarily engaged in providing skilled nursing services in the home, along with a range of the following: personal care services; homemaker and companion services; physical therapy; medical social services; medications; medical equipment and supplies; counseling; 24-hour home care; occupation and vocational therapy; dietary and nutritional services; speech therapy; audiology; and high-tech care, such as intravenous therapy. The SBA small business size standard for this industry classifies a firm having annual receipts of $16.5 million or less as small. The 2017 Economic Census indicates that 19,414 firms operated in this industry for the entire year. Of that number, 18,291 firms had revenue of less than $10 million. Based on this data, the Commission concludes that a majority of firms that operate in this industry are small.
                </P>
                <P>
                    66. 
                    <E T="03">Ambulance Services.</E>
                     This industry comprises establishments primarily engaged in providing transportation of patients by ground or air, along with medical care. These services are often provided during a medical emergency but are not restricted to emergencies. The vehicles are equipped with lifesaving equipment operated by medically trained personnel. The SBA small business size standard for this industry classifies businesses having annual receipts of $20 million or less as small. The 2017 U.S. Economic Census indicates that 2,744 firms operated in this industry for the entire year. Of that number, 2,539 firms had revenue of less than $10 million. Based on this data, the Commission concludes that a majority of firms in this industry is small.
                </P>
                <P>
                    67. 
                    <E T="03">Kidney Dialysis Centers.</E>
                     This industry comprises establishments with medical staff primarily engaged in providing outpatient kidney or renal dialysis services. The SBA small business size standard for this industry classifies firms having annual receipts of $41.5 million or less as small. The 2017 U.S. Economic Census indicates that 378 firms operated in this industry for the entire year. Of that number, 271 firms had revenue of less than $25 million. Based on this data, the Commission concludes that a majority of firms in this industry are small.
                </P>
                <P>
                    68. 
                    <E T="03">General Medical and Surgical Hospitals.</E>
                     This industry comprises “establishments known and licensed as general medical and surgical hospitals primarily engaged in providing diagnostic and medical treatment (both surgical and nonsurgical) to inpatients with any of a wide variety of medical conditions. These establishments maintain inpatient beds and provide patients with food services that meet their nutritional requirements. The 
                    <PRTPAGE P="1843"/>
                    hospitals have an organized staff of physicians and other medical staff to provide patient care services and usually provide other services, such as outpatient services, anatomical pathology services, diagnostic X-ray services, clinical laboratory services, operating room services for a variety of procedures, and pharmacy services. The SBA small business size standard for this industry classifies firms having annual receipts of $41.5 million or less as small. The 2017 U.S. Economic Census indicates that 2,948 firms operated in this industry for the entire year. Of that number, 705 firms had revenue of less than $25 million, while 709 firms had revenue between $25 million and $99,999,999 and 1,072 firms had revenue greater than $100,000,000. Based on this data, the Commission concludes that approximately one-quarter of firms in this industry are small.
                </P>
                <P>
                    69. 
                    <E T="03">Psychiatric and Substance Abuse Hospitals.</E>
                     This industry comprises establishments known and licensed as psychiatric and substance abuse hospitals primarily engaged in providing diagnostic, medical treatment, and monitoring services for inpatients who suffer from mental illness or substance abuse disorders. The treatment often requires an extended stay in the hospital. These establishments maintain inpatient beds and provide patients with food services that meet their nutritional requirements. They have an organized staff of physicians and other medical staff to provide patient care services. Psychiatric, psychological, and social work services are available at the facility. These hospitals usually provide other services, such as outpatient services, clinical laboratory services, diagnostic X-ray services, and electroencephalograph services. The SBA small business size standard for this industry classifies a business having annual receipts of $41.5 million or less as small. 2017 U.S. Census Bureau data indicate that 414 firms operated in this industry for the entire year. Of this number, 174 firms had revenue of less than $25 million. The Commission notes that 195 firms had revenue between $25 million and $99,999,999 but are unable to determine the number of firms in this group that have revenue of $41.5 million or less. Thus, based on the available data, under the SBA size standard slightly more than one-third of the businesses in this industry are small.
                </P>
                <P>
                    70. 
                    <E T="03">Specialty (Except Psychiatric and Substance Abuse) Hospitals.</E>
                     This industry consists of “establishments known and licensed as specialty hospitals primarily engaged in providing diagnostic, and medical treatment to inpatients with a specific type of disease or medical condition (except psychiatric or substance abuse).” Hospitals providing long-term care for the chronically ill and hospitals providing rehabilitation, restorative, and adjustive services to physically challenged or disabled people are included in this industry. These establishments maintain inpatient beds and provide patients with food services that meet their nutritional requirements. They have an organized staff of physicians and other medical staff to provide patient care services. These hospitals may provide other services, such as outpatient services, diagnostic X-ray services, clinical laboratory services, operating room services, physical therapy services, educational and vocational services, and psychological and social work services. The SBA small business size standard for this industry classifies businesses having annual receipts of $41.5 million or less as small. 2017 U.S. Census Bureau data indicate that 346 firms operated in this industry for the entire year. Of that number, 119 firms had revenue of less than $25 million, while 169 firms had revenue of $25 million or more. Based on this data, the Commission concludes the less than half of the firms in this industry are small.
                </P>
                <P>
                    71. 
                    <E T="03">Emergency and Other Relief Services.</E>
                     This industry comprises establishments primarily engaged in providing food, shelter, clothing, medical relief, resettlement, and counseling to victims of domestic or international disasters or conflicts (
                    <E T="03">e.g.,</E>
                     wars). The SBA small business size standard for this industry classifies firms having annual receipts of $36.5 million or less as small. The 2017 U.S. Economic Census indicates that 499 firms operated in this industry for the entire year. Of that number, 413 firms had revenue of less than $25 million. Based on this data, the Commission concludes that a majority of firms in this industry are small.
                </P>
                <HD SOURCE="HD3">b. Providers of Telecommunications and Other Services</HD>
                <HD SOURCE="HD3">(i) Telecommunications Service Providers</HD>
                <P>72. The small entities that may be affected are Wireline Providers, Wireless Carriers and Service Providers, and Internet Service Providers.</P>
                <HD SOURCE="HD3">(ii) Vendors and Equipment Manufacturers</HD>
                <P>
                    73. 
                    <E T="03">Vendors of Infrastructure Development or “Network Buildout.”</E>
                     The Commission nor the SBA have developed a small business size standard specifically directed toward manufacturers of network facilities. There are two applicable industries in which manufacturers of network facilities could fall and each have different SBA business size standards. The applicable industries are “Radio and Television Broadcasting and Wireless Communications Equipment” with a SBA small business size standard of 1,250 employees or less, and “Other Communications Equipment Manufacturing” with a SBA small business size standard of 750 employees or less.” U.S. Census Bureau data for 2017 show that for Radio and Television Broadcasting and Wireless Communications Equipment there were 656 firms in this industry that operated for the entire year. Of this number, 624 firms had fewer than 250 employees. For Other Communications Equipment Manufacturing, U.S. Census Bureau data for 2017 show that there were 321 firms in this industry that operated for the entire year. Of that number, 310 firms operated with fewer than 250 employees. Based on this data, the Commission concludes that the majority of firms in this industry are small.
                </P>
                <P>
                    74. 
                    <E T="03">Telephone Apparatus Manufacturing.</E>
                     This industry comprises establishments primarily engaged in manufacturing wire telephone and data communications equipment. These products may be stand-alone or board-level components of a larger system. Examples of products made by these establishments are central office switching equipment, cordless and wire telephones (except cellular), private branch exchange (PBX) equipment, telephone answering machines, local area network (LAN) modems, multi-user modems, and other data communications equipment, such as bridges, routers, and gateways. The SBA small business size standard for Telephone Apparatus Manufacturing classifies businesses having 1,250 or fewer employees as small. U.S. Census Bureau data for 2017 show that there were 189 firms in this industry that operated for the entire year. Of this number, 177 firms operated with fewer than 250 employees. Thus, under the SBA size standard, the majority of firms in this industry can be considered small.
                </P>
                <P>
                    75. 
                    <E T="03">
                        Radio and Television Broadcasting and Wireless Communications Equipment 
                        <PRTPAGE P="1844"/>
                        Manufacturing.
                    </E>
                     This industry comprises establishments primarily engaged in manufacturing radio and television broadcast and wireless communications equipment. Examples of products made by these establishments are: transmitting and receiving antennas, cable television equipment, global positioning system (GPS) equipment, pagers, cellular phones, mobile communications equipment, and radio and television studio and broadcasting equipment. The SBA small business size standard for this industry classifies businesses having 1,250 employees or less as small. U.S. Census Bureau data for 2017 show that there were 656 firms in this industry that operated for the entire year. Of this number, 624 firms had fewer than 250 employees. Thus, under the SBA size standard, the majority of firms in this industry can be considered small.
                </P>
                <P>
                    76. 
                    <E T="03">Other Communications Equipment Manufacturing.</E>
                     This industry comprises establishments primarily engaged in manufacturing communications equipment (except telephone apparatus, and radio and television broadcast, and wireless communications equipment). Examples of such manufacturing include fire detection and alarm systems manufacturing, Intercom systems and equipment manufacturing, and signals (
                    <E T="03">e.g.,</E>
                     highway, pedestrian, railway, traffic) manufacturing. The SBA small business size standard for this industry classifies firms having 750 or fewer employees as small. U.S. Census Bureau data for 2017 show that 321 firms in this industry operated for the entire year. Of this number, 310 firms operated with fewer than 250 employees. Based on this data, the Commission concludes that the majority of firms in this industry are small.
                </P>
                <HD SOURCE="HD3">v. Description of Projected Reporting, Recordkeeping, and Other Compliance Requirements for Small Entities</HD>
                <P>
                    77. The rules adopted in the 
                    <E T="03">Third R&amp;O</E>
                     will result in modified reporting, recordkeeping, or other compliance requirements for small and other entities. Applicants that request conditional approval for eligibility must submit an eligibility determination and supporting documentation, along with an estimated date to meet all eligibility requirements. They must also be located in a rural area as defined in § 54.600(e) of the Commission's rules by the estimated eligibility date, or plan to be a member of a majority-rural Healthcare Connect Fund (HCF) Program consortium that satisfies the eligible rural health care provider composition requirement set forth in § 54.607(b) of the Commission's rules by the estimated eligibility date. An applicant with conditional eligibility that plans to engage in competitive bidding must indicate that the eligibility is conditional, and state the estimated date of eligibility on its competitive bidding form. Applicants with conditional approval of eligibility must also notify the Universal Service Administrative Company (Administrator) within 30 calendar days of its actual eligibility date and provide documentation confirming eligibility. Beginning funding year 2025, a single eligibility determination form for the RHC Program for both the Telecom Program and the HCF Program, FCC Form 469, will be required to be filed once. Applicants will use the FCC Form 460 for eligibility determinations in the Telecom Program and the eligibility determination portion will be eliminated from the FCC Form 465. The Commission also amends § 54.601(b) of the Commission's rules to require health care providers in both programs to notify the Administrator of changes to their name, location, contact information, or eligible entity type. Telecom Program providers with invoices for funding years 2019 and earlier, must submit invoices by July 1, 2024, after which, any funding commitments for 2019 and earlier will be de-obligated and providers will not be able to invoice for services.
                </P>
                <P>
                    78. The Commission expects the actions taken in the 
                    <E T="03">Third R&amp;O</E>
                     will achieve the goals of improving the effectiveness and efficiency of the RHC Program without placing significant additional costs and burdens on small entities. At present, there is not sufficient information on the record to quantify the cost of compliance for small entities, however, the Commission anticipates that the compliance obligations for small providers will be outweighed by the benefits of improving the RHC Program's capacity to distribute telecommunications and broadband support to rural health care providers.
                </P>
                <HD SOURCE="HD3">vi. Steps Taken To Minimize the Significant Economic Impact on Small Entities, and Significant Alternatives Considered</HD>
                <P>79. The RFA requires an agency to provide “a description of the steps the agency has taken to minimize the significant economic impact on small entities . . . including a statement of the factual, policy, and legal reasons for selecting the alternative adopted in the final rule and why each one of the other significant alternatives to the rule considered by the agency which affect the impact on small entities was rejected.”</P>
                <P>
                    80. In the 
                    <E T="03">Third R&amp;O,</E>
                     the Commission takes steps to minimize the economic impact on small entities with the rule changes that are adopted. For example, conditional approval of eligibility for RHC Program funding will allow soon-to-be eligible providers to begin competitive bidding and request funding so that they may receive support as soon as they become eligible. The Commission aligns the SPIN change deadline with the invoice filing deadline to give small entities more time to complete SPIN changes. The Commission simplifies urban rate calculations by eliminating the standard urban distance provision, which will ease administrative burdens on small entities. The Commission changes evergreen contract dates to provide small entities with the benefits of evergreen contract designation across the full length of the contract's term. As a part of the reforms to use the same form for eligibility determinations in the Telecom and HCF Program, the Commission allows small entities to continue using their existing eligibility determinations. Finally, in establishing an invoice deadline for funding year 2019 and earlier, the Commission provides ample time for small providers and other entities to meet that deadline. These actions will promote efficiency and promote the goals of these programs, while strengthening protections against waste, fraud and abuse.
                </P>
                <HD SOURCE="HD3">vii. Report to Congress</HD>
                <P>
                    81. The Commission will send a copy of the 
                    <E T="03">Third R&amp;O,</E>
                     including the FRFA, in a report to Congress pursuant to the Congressional Review Act. In addition, the Commission will send a copy of the 
                    <E T="03">Third R&amp;O,</E>
                     including the FRFA, to the Chief Counsel for Advocacy of the SBA. A copy of the 
                    <E T="03">Third R&amp;O</E>
                     and FRFA (or summaries thereof) will also be published in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <HD SOURCE="HD1">IV. Ordering Clauses</HD>
                <P>
                    82. Accordingly, 
                    <E T="03">it is ordered,</E>
                     pursuant to the authority contained in sections 1, 4(j), 214, and 254 of the Communications Act of 1934, as amended, 47 U.S.C. 151, 154(j), 214, and 254 and § 1.429 of the Commission's rules, 47 CFR 1.429, that the 
                    <E T="03">Third R&amp;O</E>
                     is adopted.
                </P>
                <P>
                    83. 
                    <E T="03">It is further ordered,</E>
                     that pursuant to § 1.103 of the Commission's rules, the provisions of the 
                    <E T="03">Third R&amp;O will become effective</E>
                     February 12, 2024, unless indicated otherwise herein.
                </P>
                <P>
                    84. 
                    <E T="03">It is further ordered,</E>
                     that pursuant to the authority contained in sections 1-
                    <PRTPAGE P="1845"/>
                    4, 201 through 205, 254, 303(r), and 403 of the Communications Act of 1934, as amended, 47 U.S.C. 151-154, 201-205, 254, 303(r), and 403, and section 706 of the Telecommunications Act of 1996, 47 U.S.C. 1302, part 54 of the Commission's rules, 47 CFR part 54, 
                    <E T="03">is amended,</E>
                     and such rule amendments shall be effective February 12, 2024, except for §§ 54.601(b) and (c) and 54.622(e)(1)(i) through (ii) and (i)(3)(iv), which may contain new or modified information collection requirements, will not become effective until the Office of Management and Budget completes any required review under the Paperwork Reduction Act. The Commission directs the Wireline Competition Bureau to publish a document in the 
                    <E T="04">Federal Register</E>
                     announcing completion of such reviews and the relevant effective dates.
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 47 CFR Part 54</HD>
                    <P>Communications common carriers, Health facilities, Infants and children, Internet, Puerto Rico, Reporting and recordkeeping requirements, Telecommunications, Telephone, Virgin Islands.</P>
                </LSTSUB>
                <SIG>
                    <FP>Federal Communications Commission.</FP>
                    <NAME>Marlene Dortch,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
                <HD SOURCE="HD1">Final Rules</HD>
                <P>For the reasons discussed in the preamble, the Federal Communications Commission amends 47 CFR part 54 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 54—UNIVERSAL SERVICE</HD>
                </PART>
                <REGTEXT TITLE="47" PART="54">
                    <AMDPAR>1. The authority citation for part 54 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 47 U.S.C. 151, 154(i), 155, 201, 205, 214, 219, 220, 229, 254, 303(r), 403, 1004, 1302, 1601-1609, and 1752, unless otherwise noted.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="54">
                    <AMDPAR>2. Delayed indefinitely, amend § 54.601 by revising paragraph (b) and adding paragraph (c) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 54.601</SECTNO>
                        <SUBJECT>Health care provider eligibility.</SUBJECT>
                        <STARS/>
                        <P>
                            (b) 
                            <E T="03">Determination of health care provider eligibility for the Rural Health Care Program.</E>
                             (1) Before funding year 2025, health care providers in the Healthcare Connect Fund Program may certify to the eligibility of particular sites at any time prior to, or concurrently with, filing a request for services to initiate competitive bidding for the site. Applicants who utilize a competitive bidding exemption must provide eligibility information for the site to the Administrator prior to, or concurrently with, filing a request for funding for the site. Health care providers must also notify the Administrator within 30 days of a change in the health care provider's name, site location, contact information, or eligible entity type.
                        </P>
                        <P>(2) Effective for funding year 2025, applicants in the Rural Health Care Program may certify to the eligibility of particular sites prior to, or concurrently with, filing a request for services to initiate competitive bidding for the site. Applicants who utilize a competitive bidding exemption must provide eligibility information for the site to the Administrator prior to, or concurrently with, filing a Request for Funding for the site. Health care providers must notify the Administrator within 30 days of a change in the health care provider's name, site location, contact information, or eligible entity type.</P>
                        <P>
                            (c) 
                            <E T="03">Conditional approval of eligibility.</E>
                             Effective for funding year 2025:
                        </P>
                        <P>(1) An entity that does not yet meet all eligibility requirements under the Rural Health Care Program may request and receive a conditional approval of eligibility from the Administrator if the entity provides documentation showing that it satisfies the following requirements:</P>
                        <P>(i) The entity is or reasonably expects to qualify as a public or non-profit health care provider as defined in § 54.600(b) by an estimated eligibility date;</P>
                        <P>(ii) The entity is or reasonably expects to be physically located in a rural area defined in § 54.600(e) by the estimated eligibility date or, for the Healthcare Connect Fund Program only, is not located in a rural area but is or plans to be a member of a majority-rural Healthcare Connect Fund Program consortium that satisfies the eligible rural health care provider composition requirement set forth in § 54.607(b) by the estimated eligibility date; and</P>
                        <P>(iii) The estimated eligibility date is in the same funding year as or in the next funding year of the date that the entity requests the conditional approval of eligibility.</P>
                        <P>(2) An entity that receives conditional approval of eligibility may conduct competitive bidding for the site. An entity engaging in competitive bidding with conditional approval of eligibility must provide a written notification to potential bidders that the entity's eligibility is conditional and specify the estimated eligibility date.</P>
                        <P>(3) An entity that receives conditional approval of eligibility may file a request for funding for the site during an application filing window opened for a funding year that ends after the estimated eligibility date. The Administrator shall not issue any funding commitments to applicants that have received conditional approval of eligibility only. Funding commitments may be issued only after such applicants receive formal approval of eligibility as described in paragraph (c)(4) of this section.</P>
                        <P>(4) An entity that receives conditional approval of eligibility is expected to notify the Administrator, along with supporting documentation for the eligibility, within 30 days of its actual eligibility date. The actual eligibility date is the date that the entity qualifies as a public or non-profit health care provider as defined in § 54.600(b) and meets the requirements under paragraph (c)(1)(ii) of this section. The actual eligibility date may be a different date from the estimated eligibility date. The Administrator shall formally approve the entity's eligibility if the entity meets the requirements for a public or non-profit health care provider defined in § 54.600(b) and the requirements under paragraph (c)(1)(ii) of this section. Upon the entity receiving a formal approval of eligibility, the Administrator may issue funding commitments covering a time period that starts no earlier than the entity's actual eligibility date and that is within the funding year for which support was requested.</P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="54">
                    <AMDPAR>3. Revise § 54.604 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 54.604</SECTNO>
                        <SUBJECT>Determining the urban rate.</SUBJECT>
                        <P>(a) Effective funding year 2024:</P>
                        <P>(1) If a rural health care provider requests support for an eligible service to be funded from the Telecommunications Program that is to be provided over a distance that is less than or equal to the “standard urban distance,” as defined in paragraph (a)(3) of this section, for the state in which it is located, the “urban rate” for that service shall be a rate no higher than the highest tariffed or publicly-available rate charged to a commercial customer for a functionally similar service in any city with a population of 50,000 or more in that state, calculated as if it were provided between two points within the city.</P>
                        <P>
                            (2) If a rural health care provider requests an eligible service to be provided over a distance that is greater than the “standard urban distance,” as defined in paragraph (a)(3) of this section, for the state in which it is located, the urban rate for that service shall be a rate no higher than the highest tariffed or publicly-available rate charged to a commercial customer for a functionally similar service provided over the standard urban distance in any city with a population of 50,000 or more in that state, calculated as if the service 
                            <PRTPAGE P="1846"/>
                            were provided between two points within the city.
                        </P>
                        <P>(3) The “standard urban distance” for a state is the average of the longest diameters of all cities with a population of 50,000 or more within the state.</P>
                        <P>(4) The Administrator shall calculate the “standard urban distance” and shall post the “standard urban distance” and the maximum supported distance for each state on its website.</P>
                        <P>(b) As of funding year 2025, if a rural health care provider requests support for an eligible service to be funded from the Telecommunications Program the “urban rate” for that service shall be a rate no higher than the highest tariffed or publicly-available rate charged to a commercial customer for a functionally similar service in any city with a population of 50,000 or more in that state, calculated as if it were provided between two points within the city.</P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="54">
                    <AMDPAR>4. Delayed indefinitely, amend § 54.622 by revising paragraphs (e)(1)(i) and (ii) and adding paragraph (i)(3)(iv) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 54.622</SECTNO>
                        <SUBJECT>Competitive bidding requirements and exemptions.</SUBJECT>
                        <STARS/>
                        <P>(e) * * *</P>
                        <P>(1) * * *</P>
                        <P>(i) The entity seeking supported services is a public or nonprofit health care provider that falls within one of the categories set forth in the definition of health care provider listed in § 54.600, or expects to be such a public or nonprofit health care provider before the end of the funding year for which the supported services are requested provided that the entity has received a conditional approval of eligibility pursuant to § 54.601(c);</P>
                        <P>(ii) The health care provider seeking supported services is physically located in a rural area as defined in § 54.600 or is a member of a Healthcare Connect Fund Program consortium which satisfies the rural health care provider composition requirements set forth in § 54.607(b). If an entity seeks supported services under a conditional approval of eligibility set forth in § 54.601(c), the entity expects to be located in a rural area defined in § 54.600 before the end of the funding year for which the supported services are requested, or plans to be a member of a Healthcare Connect Fund Program consortium which satisfies the rural health care provider composition requirements set forth in § 54.607(b) before the end of the funding year for which the supported services are requested;</P>
                        <STARS/>
                        <P>(i) * * *</P>
                        <P>(3) * * *</P>
                        <P>(iv) As of funding year 2024, if the date that services start under an evergreen contract differs from the date services were estimated to start, participants may request a change of the start date and end date of their evergreen contract within 60 days of the actual service start date provided the terms of the evergreen contract support such a change. Upon approving a requested change, the Administrator will issue a revised funding commitment letter to the health care provider reflecting the changed dates. If the Administrator denies a requested change, it will issue a letter to the health care provider explaining the basis for the denial.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="54">
                    <AMDPAR>5. Amend § 54.625 by revising paragraph (c) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 54.625</SECTNO>
                        <SUBJECT>Service Provider Identification Number (SPIN) changes.</SUBJECT>
                        <STARS/>
                        <P>
                            (c) 
                            <E T="03">Filing deadline.</E>
                             An applicant must file its request for a corrective or operational SPIN change with the Administrator no later than the invoice filing deadline as defined by § 54.627.
                        </P>
                    </SECTION>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00415 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </RULE>
    </RULES>
    <VOL>89</VOL>
    <NO>8</NO>
    <DATE>Thursday, January 11, 2024</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <PRORULES>
        <PRORULE>
            <PREAMB>
                <PRTPAGE P="1847"/>
                <AGENCY TYPE="F">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. FAA-2024-0030; Project Identifier AD-2023-01066-E]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; CFM International, S.A. 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 adopt a new airworthiness directive (AD) for CFM International (CFM) Model LEAP-1A23, LEAP-1A24, LEAP-1A24E1, LEAP-1A26, LEAP-1A26CJ, LEAP-1A26E1, LEAP-1A29, LEAP-1A29CJ, LEAP-1A30, LEAP-1A32, LEAP-1A33, LEAP-1A33B2, and LEAP-1A35A engines. This proposed AD was prompted by detection of melt-related freckles in the billet, which may reduce the life of certain high-pressure turbine (HPT) rotor interstage seals. This proposed AD would require removing the affected HPT rotor interstage seals from service and replacing with a part eligible for installation. The FAA is proposing this AD to address the unsafe condition on these products.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The FAA must receive comments on this proposed AD by February 26, 2024.</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-2024-0030; or in person at Docket Operations between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains this NPRM, any comments received, and other information. The street address for Docket Operations is listed above.
                    </P>
                    <P>
                        <E T="03">Material Incorporated by Reference:</E>
                    </P>
                    <P>
                        • For service information identified in this NPRM, contact CFM International, S.A., GE Aviation Fleet Support, 1 Neumann Way, M/D Room 285, Cincinnati, OH 45215; phone: (877) 432-3272; email: 
                        <E T="03">aviation.fleetsupport@ge.com.</E>
                    </P>
                    <P>• You may view this service information at the FAA, Airworthiness Products Section, Operational Safety Branch, 1200 District Avenue, Burlington, MA 01803. For information on the availability of this material at the FAA, call (817) 222-5110.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Mehdi Lamnyi, Aviation Safety Engineer, FAA, 2200 South 216th Street, Des Moines, WA 98198; phone: (781) 238-7743; email: 
                        <E T="03">mehdi.lamnyi@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 to an address listed under 
                    <E T="02">ADDRESSES</E>
                    . Include “Docket No. FAA-2024-0030; Project Identifier AD-2023-01066-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 this proposal because of those comments.
                </P>
                <P>
                    Except for Confidential Business Information (CBI) as described in the following paragraph, and other information as described in 14 CFR 11.35, the FAA will post all comments received, without change, to 
                    <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 Mehdi Lamnyi, 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 was notified by the manufacturer of the detection of melt-related freckles in the billet, which may reduce the life of certain HPT rotor interstage seals. Through the manufacturer's investigation, it was determined that these affected parts may have subsurface anomalies that developed during the manufacturing process, resulting in a lower life capability. This condition, if not addressed, could result in failure of the HPT rotor interstage seal, release of uncontained debris, damage to the engine, and damage to the airplane.</P>
                <HD SOURCE="HD1">FAA's Determination</HD>
                <P>The FAA is issuing this NPRM after determining that the unsafe condition described previously is likely to exist or develop on other products of the same type design.</P>
                <HD SOURCE="HD1">Related Service Information Under 1 CFR Part 51</HD>
                <P>
                    The FAA reviewed CFM Service Bulletin LEAP-1A-72-00-0492-01A-930A-D, Issue 001-00, dated April 6, 2023, which provides the serial numbers of the affected HPT rotor interstage seals and specifies procedures for replacement of the HPT rotor 
                    <PRTPAGE P="1848"/>
                    interstage seal. This service information is reasonably available because the interested parties have access to it through their normal course of business or by the means identified in 
                    <E T="02">ADDRESSES</E>
                    .
                </P>
                <HD SOURCE="HD1">Proposed AD Requirements in This NPRM</HD>
                <P>This proposed AD would require accomplishing the actions specified in the service information already described.</P>
                <HD SOURCE="HD1">Costs of Compliance</HD>
                <P>The FAA estimates that this AD, if adopted as proposed, would affect 1 engine installed on an airplane 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,r50,12C,12C,12C">
                    <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">Remove HPT rotor interstage seal</ENT>
                        <ENT>225 work-hours × $85 per hour = $19,125</ENT>
                        <ENT>$168,000</ENT>
                        <ENT>$187,125</ENT>
                        <ENT>$187,125</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. Subtitle VII: Aviation Programs, describes in more detail the scope of the Agency's authority.</P>
                <P>The FAA is issuing this rulemaking under the authority described in Subtitle VII, Part A, Subpart III, Section 44701: General requirements. Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action.</P>
                <HD SOURCE="HD1">Regulatory Findings</HD>
                <P>The FAA determined that this proposed AD would not have federalism implications under Executive Order 13132. This proposed AD would not have a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
                <P>For the reasons discussed above, I certify this proposed regulation:</P>
                <P>(1) Is not a “significant regulatory action” under Executive Order 12866,</P>
                <P>(2) Would not affect intrastate aviation in Alaska, and</P>
                <P>(3) Would not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Proposed Amendment</HD>
                <P>Accordingly, under the authority delegated to me by the Administrator, the FAA proposes to amend 14 CFR part 39 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
                </PART>
                <AMDPAR>1. The authority citation for part 39 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P> 49 U.S.C. 106(g), 40113, 44701.</P>
                </AUTH>
                <SECTION>
                    <SECTNO>§ 39.13</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <AMDPAR>2. The FAA amends § 39.13 by adding the following new airworthiness directive:</AMDPAR>
                <EXTRACT>
                    <FP SOURCE="FP-2">
                        <E T="04">CFM International, S.A.:</E>
                         Docket No. FAA-2024-0030; Project Identifier AD-2023-01066-E.
                    </FP>
                    <HD SOURCE="HD1">(a) Comments Due Date</HD>
                    <P>The FAA must receive comments on this airworthiness directive (AD) by February 26, 2024.</P>
                    <HD SOURCE="HD1">(b) Affected ADs</HD>
                    <P>None.</P>
                    <HD SOURCE="HD1">(c) Applicability</HD>
                    <P>This AD applies to CFM International, S.A. (CFM) Model LEAP-1A23, LEAP-1A24, LEAP-1A24E1, LEAP-1A26, LEAP-1A26CJ, LEAP-1A26E1, LEAP-1A29, LEAP-1A29CJ, LEAP-1A30, LEAP-1A32, LEAP-1A33, LEAP-1A33B2, and LEAP-1A35A engines.</P>
                    <HD SOURCE="HD1">(d) Subject</HD>
                    <P>Joint Aircraft System Component (JASC) Code 7250, Turbine Section.</P>
                    <HD SOURCE="HD1">(e) Unsafe Condition</HD>
                    <P>This AD was prompted by detection of melt-related freckles in the billet, which may reduce the life of certain high-pressure turbine (HPT) rotor interstage seals. The FAA is issuing this AD to prevent failure of the HPT rotor interstage seal. The unsafe condition, if not addressed, could result in release of uncontained debris, damage to the engine, and damage to the airplane.</P>
                    <HD SOURCE="HD1">(f) Compliance</HD>
                    <P>Comply with this AD within the compliance times specified, unless already done.</P>
                    <HD SOURCE="HD1">(g) Required Actions</HD>
                    <P>For engines with an affected HPT rotor interstage seal installed, before exceeding the applicable threshold specified in Table 1 of paragraph 3.E., Compliance, of CFM Service Bulletin (SB) LEAP-1A-72-00-0492-01A-930A-D, Issue 001-00, dated April 6, 2023 (CFM SB LEAP-1A-72-00-0492-01A-930A-D, Issue 001-00), or at the next HPT rotor module exposure, whichever occurs first after the effective date of this AD, remove the affected HPT rotor interstage seal from service and replace it with a part eligible for installation.</P>
                    <HD SOURCE="HD1">(h) Definitions</HD>
                    <P>(1) For the purpose of this AD, an “affected HPT rotor interstage seal” is any HPT rotor interstage seal having part number 2466M68P02 and a serial number listed in Table 1 of paragraph 3.E., Compliance, of CFM SB LEAP-1A-72-00-0492-01A-930A-D, Issue 001-00.</P>
                    <P>(2) For the purpose of this AD, a “part eligible for installation” is any HPT rotor interstage seal having a serial number that is not listed in Table 1 of paragraph 3.E., Compliance, of CFM SB LEAP-1A-72-00-0492-01A-930A-D, Issue 001-00.</P>
                    <P>(3) For the purpose of this AD, an “HPT rotor module exposure” is an engine shop visit during which the HPT rotor assembly is fully removed from the engine core.</P>
                    <HD SOURCE="HD1">(i) Alternative Methods of Compliance (AMOCs)</HD>
                    <P>
                        (1) The Manager, AIR-520 Continued Operational Safety Branch, FAA, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. In accordance with 14 CFR 39.19, send your request to your principal inspector or 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 (j) of this AD and email to 
                        <E T="03">ANE-AD-AMOC@faa.gov.</E>
                    </P>
                    <P>(2) Before using any approved AMOC, notify your appropriate principal inspector, or lacking a principal inspector, the manager of the local flight standards district office/certificate holding district office.</P>
                    <HD SOURCE="HD1">(j) Additional Information</HD>
                    <P>
                        For more information about this AD, contact Mehdi Lamnyi, Aviation Safety Engineer, FAA, 2200 South 216th Street, Des 
                        <PRTPAGE P="1849"/>
                        Moines, WA 98198; phone: (781) 238-7743; email: 
                        <E T="03">mehdi.lamnyi@faa.gov</E>
                        .
                    </P>
                    <HD SOURCE="HD1">(k) Material Incorporated by Reference</HD>
                    <P>(1) The Director of the Federal Register approved the incorporation by reference (IBR) of the service information listed in this paragraph under 5 U.S.C. 552(a) and 1 CFR part 51.</P>
                    <P>(2) You must use this service information as applicable to do the actions required by this AD, unless the AD specifies otherwise.</P>
                    <P>(i) CFM International, S.A. (CFM) Service Bulletin LEAP-1A-72-00-0492-01A-930A-D, Issue 001-00, dated April 6, 2023.</P>
                    <P>(ii) [Reserved]</P>
                    <P>
                        (3) For service information identified in this AD, contact CFM International, S.A., Aviation Operations Center, 1 Neumann Way, M/D Room 285, Cincinnati, OH 45125; phone: (877) 432-3272; email: 
                        <E T="03">fleetsupport@ge.com.</E>
                    </P>
                    <P>(4) You may view this service information at FAA, Airworthiness Products Section, Operational Safety Branch, 1200 District Avenue, Burlington, MA 01803. For information on the availability of this material at the FAA, call (817) 222-5110.</P>
                    <P>
                        (5) You may view this material at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, visit 
                        <E T="03">www.archives.gov/federal-register/cfr/ibr-locationsoremailfr.inspection@nara.gov.</E>
                    </P>
                </EXTRACT>
                <SIG>
                    <DATED>Issued on January 5, 2024.</DATED>
                    <NAME>Victor Wicklund,</NAME>
                    <TITLE>Deputy Director, Compliance &amp; Airworthiness Division, Aircraft Certification Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00377 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. FAA-2024-0026; Project Identifier MCAI-2023-00776-T]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; MHI RJ Aviation ULC (Type Certificate Previously Held by Bombardier, Inc.) Airplanes</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking (NPRM).</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The FAA proposes to adopt a new airworthiness directive (AD) for all MHI RJ Aviation ULC Model CL-600-2E25 (Regional Jet Series 1000) airplanes. This proposed AD was prompted by a determination that new or more restrictive airworthiness limitations are necessary. This proposed AD would require revising the existing maintenance or inspection program, as applicable, to incorporate new or more restrictive airworthiness limitations, as specified in a Transport Canada AD, which is proposed for incorporation by reference (IBR). The FAA is proposing this AD to address the unsafe condition on these products.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The FAA must receive comments on this proposed AD by February 26, 2024.</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-2024-0026; 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 Transport Canada material that is proposed for IBR in this NPRM, contact Transport Canada, Transport Canada National Aircraft Certification, 159 Cleopatra Drive, Nepean, Ontario K1A 0N5, Canada; telephone 888-663-3639; email 
                        <E T="03">TC.AirworthinessDirectives-Consignesdenavigabilite.TC@tc.gc.ca;</E>
                         website 
                        <E T="03">tc.canada.ca/en/aviation.</E>
                         It is also available at 
                        <E T="03">regulations.gov</E>
                         under Docket No. FAA-2024-0026.
                    </P>
                    <P>• You may view this service information at the FAA, Airworthiness Products Section, Operational Safety Branch, 2200 South 216th St., Des Moines, WA. For information on the availability of this material at the FAA, call 206-231-3195.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Fatin Saumik, Aviation Safety Engineer, FAA, 1600 Stewart Avenue, Suite 410, Westbury, NY 11590; telephone 516-228-7300; email 
                        <E T="03">9-avs-nyaco-cos@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 to an address listed under 
                    <E T="02">ADDRESSES</E>
                    . Include “Docket No. FAA-2024-0026; Project Identifier MCAI-2023-00776-T” at the beginning of your comments. The most helpful comments reference a specific portion of the proposal, explain the reason for any recommended change, and include supporting data. The FAA will consider all comments received by the closing date and may amend this proposal because of those comments.
                </P>
                <P>
                    Except for Confidential Business Information (CBI) as described in the following paragraph, and other information as described in 14 CFR 11.35, the FAA will post all comments received, without change, to 
                    <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 Fatin Saumik, Aviation Safety Engineer, FAA, 1600 Stewart Avenue, Suite 410, Westbury, NY 11590; telephone 516-228-7300; email 
                    <E T="03">9-avs-nyaco-cos@faa.gov.</E>
                     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>Transport Canada, which is the aviation authority for Canada, has issued AD CF-2023-43, dated June 21, 2023 (Transport Canada AD CF-2023-43) (also referred to as the MCAI), to correct an unsafe condition for all MHI RJ Aviation ULC Model CL-600-2E25 (Regional Jet Series 1000) airplanes. The MCAI states that new or more restrictive airworthiness limitations have been developed.</P>
                <P>
                    The FAA is proposing this AD to prevent potential fatigue cracking and 
                    <PRTPAGE P="1850"/>
                    damage in principal structural elements. The unsafe condition, if not addressed, could result in reduced structural integrity of the airplane. You may examine the MCAI in the AD docket at 
                    <E T="03">regulations.gov</E>
                     under Docket No. FAA-2024-0026.
                </P>
                <HD SOURCE="HD1">Related Service Information Under 1 CFR Part 51</HD>
                <P>
                    The FAA reviewed Transport Canada AD CF-2023-43, which specifies new or more restrictive airworthiness limitations for airplane structures and a safe life limit. This service information is reasonably available because the interested parties have access to it through their normal course of business or by the means identified in 
                    <E T="02">ADDRESSES</E>
                    .
                </P>
                <HD SOURCE="HD1">FAA's Determination</HD>
                <P>This product has been approved by the aviation authority of another country and is approved for operation in the United States. Pursuant to the FAA's bilateral agreement with this State of Design Authority, it has notified the FAA of the unsafe condition described in the MCAI referenced above. The FAA is issuing this NPRM after determining that the unsafe condition described previously is likely to exist or develop in other products of the same type design.</P>
                <HD SOURCE="HD1">Proposed AD Requirements in This NPRM</HD>
                <P>This proposed AD would require revising the existing maintenance or inspection program, as applicable, to incorporate new or more restrictive airworthiness limitations, which are specified in Transport Canada AD CF-2023-43 described previously, as incorporated by reference. Any differences with Transport Canada AD CF-2023-43 are identified as exceptions in the regulatory text of this proposed AD.</P>
                <P>
                    This proposed AD would require revisions to certain operator maintenance documents to include new actions (
                    <E T="03">e.g.,</E>
                     inspections). Compliance with these actions is required by 14 CFR 91.403(c). For airplanes that have been previously modified, altered, or repaired in the areas addressed by this proposed AD, the operator may not be able to accomplish the actions described in the revisions. In this situation, to comply with 14 CFR 91.403(c), the operator must request approval for an alternative method of compliance (AMOC) according to paragraph (j)(1) of this proposed 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 civil aviation authority (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 Transport Canada AD CF-2023-43 by reference in the FAA final rule. This proposed AD would, therefore, require compliance with Transport Canada AD CF-2023-43 through that incorporation, except for any differences identified as exceptions in the regulatory text of this proposed AD. Service information required by Transport Canada AD CF-2023-43 for compliance will be available at 
                    <E T="03">regulations.gov</E>
                     by searching for and locating Docket No. FAA-2024-0026 after the FAA final rule is published.
                </P>
                <HD SOURCE="HD1">Airworthiness Limitation ADs Using the New Process</HD>
                <P>The FAA's process of incorporating by reference MCAI ADs as the primary source of information for compliance with corresponding FAA ADs has been limited to certain MCAI ADs (primarily those with service bulletins as the primary source of information for accomplishing the actions required by the FAA AD). However, the FAA is now expanding the process to include MCAI ADs that require a change to airworthiness limitation documents, such as airworthiness limitation sections.</P>
                <P>For these ADs that incorporate by reference an MCAI AD that changes airworthiness limitations, the FAA requirements are unchanged. Operators must revise the existing maintenance or inspection program, as applicable, to incorporate the information specified in the new airworthiness limitation document. The airworthiness limitations must be followed according to 14 CFR 91.403(c) and 91.409(e).</P>
                <P>
                    The previous format of the airworthiness limitation ADs included a paragraph that specified that no alternative actions (
                    <E T="03">e.g.,</E>
                     inspections) or intervals may be used unless the actions and intervals are approved as an AMOC in accordance with the procedures specified in the AMOC paragraph under “Additional AD Provisions.” This new format includes a “New Provisions for Alternative Actions and Intervals” paragraph that does not specifically refer to AMOCs, but operators may still request an AMOC to use an alternative action or interval.
                </P>
                <HD SOURCE="HD1">Costs of Compliance</HD>
                <P>The FAA estimates that this AD, if adopted as proposed, would affect 5 airplanes of U.S. registry. The FAA estimates the following costs to comply with this proposed AD:</P>
                <P>The FAA has determined that revising the existing maintenance or inspection program takes an average of 90 work-hours per operator, although the agency recognizes that this number may vary from operator to operator. Since operators incorporate maintenance or inspection program changes for their affected fleet(s), the FAA has determined that a per-operator estimate is more accurate than a per-airplane estimate. Therefore, the agency estimates the average total cost per operator to be $7,650 (90 work-hours × $85 per work-hour).</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>The FAA has determined that this proposed AD would not have federalism implications under Executive Order 13132. This proposed AD would not have a substantial direct effect on the States, on the relationship between the national Government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
                <P>For the reasons discussed above, I certify this proposed regulation:</P>
                <P>(1) Is not a “significant regulatory action” under Executive Order 12866,</P>
                <P>(2) Would not affect intrastate aviation in Alaska, and</P>
                <P>
                    (3) Would not have a significant economic impact, positive or negative, 
                    <PRTPAGE P="1851"/>
                    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 adding the following new airworthiness directive:</AMDPAR>
                <EXTRACT>
                    <FP SOURCE="FP-1">
                        <E T="04">MHI RJ Aviation ULC (Type Certificate Previously Held by Bombardier, Inc.):</E>
                         Docket No. FAA-2024-0026; Project Identifier MCAI-2023-00776-T.
                    </FP>
                    <HD SOURCE="HD1">(a) Comments Due Date</HD>
                    <P>The FAA must receive comments on this airworthiness directive (AD) by February 26, 2024.</P>
                    <HD SOURCE="HD1">(b) Affected ADs</HD>
                    <P>None.</P>
                    <HD SOURCE="HD1">(c) Applicability</HD>
                    <P>This AD applies to all MHI RJ Aviation ULC (Type Certificate previously held by Bombardier, Inc.) Model CL-600-2E25 (Regional Jet Series 1000) airplanes, certificated in any category.</P>
                    <HD SOURCE="HD1">(d) Subject</HD>
                    <P>Air Transport Association (ATA) of America Code 05, Time Limits/Maintenance Checks.</P>
                    <HD SOURCE="HD1">(e) Unsafe Condition</HD>
                    <P>This AD was prompted by a determination that new or more restrictive airworthiness limitations are necessary. The FAA is issuing this AD to prevent potential fatigue cracking and damage in principal structural elements. The unsafe condition, if not addressed, could result in reduced structural integrity of the airplane.</P>
                    <HD SOURCE="HD1">(f) Compliance</HD>
                    <P>Comply with this AD within the compliance times specified, unless already done.</P>
                    <HD SOURCE="HD1">(g) Requirements</HD>
                    <P>Except as specified in paragraph (h) of this AD: Comply with all required actions and compliance times specified in, and in accordance with, Transport Canada AD CF-2023-43, dated June 21, 2023 (Transport Canada AD CF-2023-43).</P>
                    <HD SOURCE="HD1">(h) Exceptions to Transport Canada AD CF-2023-43</HD>
                    <P>(1) Where Transport Canada AD CF-2023-43 refers to its effective date, this AD requires using the effective date of this AD.</P>
                    <P>(2) Where paragraph 1. of Transport Canada AD CF-2023-43 specifies to “incorporate the new and revised tasks identified in Table 1 below, in the appropriate chapter within Section 2 and Section 3 of the MRM CSP B-053 Part 2 manual,” this AD requires replacing those words with “revise the existing maintenance or inspection program, as applicable, by incorporating the new and revised tasks identified in Table 1.”</P>
                    <P>(3) The initial compliance time for doing the tasks specified in paragraph 1. of Transport Canada AD CF-2023-43 is at the applicable “thresholds” and “discard times” as specified in the service information referenced in paragraph 1. of Transport Canada AD CF-2023-43, or within 60 days after the effective date of this AD, whichever occurs later.</P>
                    <P>(4) This AD does not adopt paragraph 2. of Transport Canada AD CF-2023-43.</P>
                    <HD SOURCE="HD1">(i) Provisions for Alternative Actions and Intervals</HD>
                    <P>
                        After the existing maintenance or inspection program has been revised as required by paragraph (g) of this AD, no alternative actions (
                        <E T="03">e.g.,</E>
                         inspections) and intervals are allowed unless they are approved as specified in the provisions of the “Corrective Actions” section of Transport Canada AD CF-2023-43.
                    </P>
                    <HD SOURCE="HD1">(j) Additional AD Provisions</HD>
                    <P>The following provisions also apply to this AD:</P>
                    <P>
                        (1) 
                        <E T="03">Alternative Methods of Compliance (AMOCs):</E>
                         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 responsible Flight Standards Office, as appropriate. If sending information directly to the manager of the International Validation Branch, mail it to the address identified in paragraph (k) of this AD. Information may be emailed to 
                        <E T="03">9-AVS-NYACO-COS@faa.gov.</E>
                         Before using any approved AMOC, notify your appropriate principal inspector, or lacking a principal inspector, the manager of the responsible Flight Standards Office.
                    </P>
                    <P>
                        (2) 
                        <E T="03">Contacting the Manufacturer:</E>
                         For any requirement in this AD to obtain instructions from a manufacturer, the instructions must be accomplished using a method approved by the Manager, International Validation Branch, FAA; or Transport Canada; or MHI RJ Aviation ULC's Transport Canada Design Approval Organization (DAO). If approved by the DAO, the approval must include the DAO-authorized signature.
                    </P>
                    <HD SOURCE="HD1">(k) Additional Information</HD>
                    <P>
                        For more information about this AD, contact Fatin Saumik, Aviation Safety Engineer, FAA, 1600 Stewart Avenue, Suite 410, Westbury, NY 11590; telephone 516-228-7300; email 
                        <E T="03">9-avs-nyaco-cos@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 service information listed in this paragraph under 5 U.S.C. 552(a) and 1 CFR part 51.</P>
                    <P>(2) You must use this service information as applicable to do the actions required by this AD, unless this AD specifies otherwise.</P>
                    <P>(i) Transport Canada AD CF-2023-43, dated June 21, 2023.</P>
                    <P>(ii) [Reserved]</P>
                    <P>
                        (3) For Transport Canada AD CF-2023-43, contact Transport Canada, Transport Canada National Aircraft Certification, 159 Cleopatra Drive, Nepean, Ontario K1A 0N5, Canada; telephone 888-663-3639; email 
                        <E T="03">TC.AirworthinessDirectives-Consignesdenavigabilite.TC@tc.gc.ca;</E>
                         website 
                        <E T="03">tc.canada.ca/en/aviation.</E>
                    </P>
                    <P>(4) You may view this service information at the FAA, Airworthiness Products Section, Operational Safety Branch, 2200 South 216th St., Des Moines, WA. For information on the availability of this material at the FAA, call 206-231-3195.</P>
                    <P>
                        (5) You may view this material at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, visit 
                        <E T="03">www.archives.gov/federal-register/cfr/ibr-locations,</E>
                         or email 
                        <E T="03">fr.inspection@nara.gov.</E>
                    </P>
                </EXTRACT>
                <SIG>
                    <DATED>Issued on January 5, 2024.</DATED>
                    <NAME>Victor Wicklund,</NAME>
                    <TITLE>Deputy Director, Compliance &amp; Airworthiness Division, Aircraft Certification Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00343 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 71</CFR>
                <DEPDOC>[Docket No. FAA-2023-2493; Airspace Docket No. 23-AGL-25]</DEPDOC>
                <RIN>RIN 2120-AA66</RIN>
                <SUBJECT>Amendment of Jet Route J-89 and VOR Federal Airway V-161, and Establishment of Canadian RNAV Routes Q-834 and T-765; Northcentral United States</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking (NPRM).</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This action proposes to amend Jet Route J-89 and Very High Frequency Omnidirectional Range (VOR) Federal Airway V-161 and to establish Canadian Area Navigation (RNAV) routes Q-834 and T-765 in United States (U.S.) airspace. The FAA is proposing this action due to the planned decommissioning of the Winnipeg, Manitoba (MB), Canada, 
                        <PRTPAGE P="1852"/>
                        VOR/Tactical Air Navigation (VORTAC) navigational aid (NAVAID). This action is in support of NAV CANADA's NAVAID Modernization Program.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before February 26, 2024.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Send comments identified by FAA Docket No. FAA-2023-2493 and Airspace Docket No. 23-AGL-25 using any of the following methods:</P>
                    <P>
                        * 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">www.regulations.gov</E>
                         and follow the online instructions for sending your comments electronically.
                    </P>
                    <P>
                        * 
                        <E T="03">Mail:</E>
                         Send comments to Docket Operations, M-30; U.S. Department of Transportation, 1200 New Jersey Avenue SE, Room W12-140, West Building Ground Floor, Washington, DC 20590-0001.
                    </P>
                    <P>
                        * 
                        <E T="03">Hand Delivery or Courier:</E>
                         Take comments to Docket Operations in Room W12-140 of the West Building Ground Floor at 1200 New Jersey Avenue SE, Washington, DC, between 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 W12-140 of the West Building Ground Floor at 1200 New Jersey Avenue SE, Washington, DC, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.
                    </P>
                    <P>
                        FAA Order JO 7400.11H, Airspace Designations and Reporting Points, and subsequent amendments can be viewed online at 
                        <E T="03">www.faa.gov/air_traffic/publications/.</E>
                         You may also contact the Rules and Regulations Group, Office of Policy, Federal Aviation Administration, 800 Independence Avenue SW, Washington, DC 20591; telephone: (202) 267-8783.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Colby Abbott, Rules and Regulations Group, Office of Policy, 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 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 would modify the National Airspace System (NAS) as necessary to preserve the safe and efficient flow of air traffic.</P>
                <HD SOURCE="HD1">Comments Invited</HD>
                <P>The FAA invites interested persons to participate in this rulemaking by submitting written comments, data, or views. Comments are specifically invited on the overall regulatory, aeronautical, economic, environmental, and energy-related aspects of the proposal. The most helpful comments reference a specific portion of the proposal, explain the reason for any recommended change, and include supporting data. To ensure the docket does not contain duplicate comments, commenters should submit only one time if comments are filed electronically, or commenters should send only one copy of written comments if comments are filed in writing.</P>
                <P>The FAA will file in the docket all comments it receives, as well as a report summarizing each substantive public contact with FAA personnel concerning this proposed rulemaking. Before acting on this proposal, the FAA will consider all comments it receives on or before the closing date for comments. The FAA will consider comments filed after the comment period has closed if it is possible to do so without incurring expense or delay. The FAA may change this proposal in light of the comments it receives.</P>
                <P>
                    <E T="03">Privacy:</E>
                     In accordance with 5 U.S.C. 553(c), DOT solicits comments from the public to better inform its rulemaking process. DOT posts these comments, without edit, including any personal information the commenter provides, to 
                    <E T="03">www.regulations.gov,</E>
                     as described in the system of records notice (DOT/ALL-14 FDMS), which can be reviewed at 
                    <E T="03">www.dot.gov/privacy.</E>
                </P>
                <HD SOURCE="HD1">Availability of Rulemaking Documents</HD>
                <P>
                    An electronic copy of this document may be downloaded through the internet at 
                    <E T="03">www.regulations.gov.</E>
                     Recently published rulemaking documents can also be accessed through the FAA's web page at 
                    <E T="03">www.faa.gov/air_traffic/publications/airspace_amendments/.</E>
                </P>
                <P>
                    You may review the public docket containing the proposal, any comments received and any final disposition in person in the Dockets Operations office (see 
                    <E T="02">ADDRESSES</E>
                     section for address, phone number, and hours of operations). An informal docket may also be examined during normal business hours at the office of the Operations Support Group, Central Service Center, Federal Aviation Administration, 10101 Hillwood Parkway, Fort Worth, TX 76177.
                </P>
                <HD SOURCE="HD1">Incorporation by Reference</HD>
                <P>
                    Jet Routes are published in paragraph 2004, Canadian Area Navigation Routes (Q-routes) are published in paragraph 2007, VOR Federal airways are published in paragraph 6010(a), and Canadian Area Navigation Routes (T-routes) are published in paragraph 6013 of FAA Order JO 7400.11, Airspace Designations and Reporting Points, which is incorporated by reference in 14 CFR 71.1 on an annual basis. This document proposes to amend the current version of that order, FAA Order JO 7400.11H, dated August 11, 2023, and effective September 15, 2023. These updates would be published in the next update to FAA Order JO 7400.11. That order is publicly available as listed in the 
                    <E T="02">ADDRESSES</E>
                     section of this document.
                </P>
                <P>FAA Order JO 7400.11H lists Class A, B, C, D, and E airspace areas, air traffic service routes, and reporting points.</P>
                <HD SOURCE="HD1">Background</HD>
                <P>NAV CANADA, which operates Canada's civil air navigation service, is implementing changes to Canada's instrument flight rules (IFR) navigation infrastructure as part of their NAVAID Modernization Program. This modernization program is designed to enhance the efficiency of Canada's flying operations by taking advantage of performance-based navigation and RNAV avionics capabilities. The changes being implemented by NAV CANADA affect Jet Route J-89 and portions of VOR Federal Airway V-161 that extend across the U.S./Canada border through U.S. airspace.</P>
                <P>
                    NAV CANADA is planning to decommission the Winnipeg, MB, Canada, VORTAC in September 2024 as part of their NAVAID Modernization Program. As a result, amendments to J-89 and V-161 in U.S. airspace are necessary due to the loss of navigational guidance provided by the Winnipeg VORTAC and to match the Air Traffic Service (ATS) route changes planned by NAV CANADA within Canadian airspace. Additionally, NAV CANADA plans to establish new Canadian RNAV routes, Q-834 in the high-altitude enroute structure and T-765 in the low-altitude enroute structure, as route segment replacements for the affected 
                    <PRTPAGE P="1853"/>
                    ATS routes within Canadian and U.S. airspace.
                </P>
                <P>To mitigate the loss of the J-89 and V-161 route segments in U.S. airspace and support NAV CANADA's planned RNAV route replacements for these affected routes, the FAA is proposing to establish portions of Canadian RNAV routes Q-834 and T-765 within U.S. airspace. The new Canadian RNAV route segments in U.S. airspace would provide airway continuity with NAV CANADA's RNAV routes being established within Canadian airspace and provide cross-border airway connectivity between the U.S. and Canada. Existing NAVAIDs that provide conventional enroute structure in the affected area are limited and alternate, parallel, or adjacent Jet Routes or VOR Federal Airways to use as mitigations are not available. To compensate for the loss of the conventional enroute structure, IFR pilots with RNAV-equipped aircraft could navigate using the Canadian RNAV routes proposed in this action or fly point-to-point using the Fixes and waypoints (WP) that would remain in place. Additionally, IFR pilots could request air traffic control (ATC) radar vectors to fly through or around the affected area. Visual flight rules pilots who elect to navigate via airways could also take advantage of the ATC services listed previously.</P>
                <HD SOURCE="HD1">The Proposal</HD>
                <P>The FAA is proposing to amend 14 CFR part 71 by amending Jet Route J-89 and VOR Federal Airway V-161 and by establishing Canadian RNAV Routes Q-834 and T-765 in U.S. airspace. This action is necessary due to the planned decommissioning of the Winnipeg, MB, Canada, VORTAC by NAV CANADA as part of their NAVAID Modernization Program. The proposed ATS route actions are described below.</P>
                <P>
                    <E T="03">J-89:</E>
                     J-89 currently extends between the Louisville, KY, VORTAC and the Winnipeg, MB, Canada, VORTAC, excluding the airspace within Canada. The FAA proposes to remove the route segment between the Duluth, MN, VORTAC and the Winnipeg VORTAC. As amended, the route would be changed to extend between the Louisville VORTAC and the Duluth VORTAC.
                </P>
                <P>
                    <E T="03">Q-834:</E>
                     Q-834 is a new Canadian RNAV route proposed to be established within U.S. airspace extending between the Duluth, MN, VORTAC and the ALBNG, MN, WP that would replace the “CFHBZ” Computer Navigation Fix (CNF) on the U.S./Canada border. The new RNAV route would mitigate the proposed J-89 route segment removal and provide route continuity and cross-border connectivity with the Q-834 route being established by NAV CANADA within Canadian airspace between the ALBNG WP and the Winnipeg, MB, area.
                </P>
                <P>
                    <E T="03">V-161:</E>
                     V-161 currently extends between the Three Rivers, TX, VORTAC and the Tulsa, OK, VORTAC; between the Butler, MO, VORTAC and the Gopher, MN, VORTAC; and between the International Falls, MN, VOR/Distance Measuring Equipment (VOR/DME) and the Winnipeg, MB, Canada, VORTAC, excluding the airspace within Canada. The FAA proposes to remove the airway segment between the International Falls VOR/DME and the Winnipeg VORTAC. As amended, the airway would be changed to extend between the Three Rivers VORTAC and the Tulsa VORTAC, and between the Butler VORTAC and the Gopher VORTAC.
                </P>
                <P>
                    <E T="03">T-765:</E>
                     T-765 is a new Canadian RNAV route proposed to be established in two segments within U.S. airspace extending between the International Falls, MN, VOR/DME and the KORTY, MN, WP replacing the “CFFQV” CNF on the U.S./Canada border; and between the LCROS, MN, WP replacing the “CFXDP” CNF on the U.S./Canada border and the CALDU, MN, WP replacing the “CFZMG” CNF on the U.S./Canada border. The new RNAV route segments would mitigate the proposed V-161 airway segments removal between the International Falls VOR/DME and the Winnipeg, MB, Canada VORTAC and provide route continuity and cross-border connectivity with the T-765 route segments being established by NAV CANADA within Canadian airspace.
                </P>
                <P>The NAVAID radials listed in the VOR Federal Airway V-161 description in the proposed regulatory text of this NPRM are unchanged and stated in degrees True north.</P>
                <HD SOURCE="HD1">Regulatory Notices and Analyses</HD>
                <P>The FAA has determined that this proposed regulation only involves an established body of technical regulations for which frequent and routine amendments are necessary to keep them operationally current. It, therefore: (1) is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under DOT Regulatory Policies and Procedures (44 FR 11034; February 26, 1979); and (3) does not warrant preparation of a regulatory evaluation as the anticipated impact is so minimal. Since this is a routine matter that will only affect air traffic procedures and air navigation, it is certified that this proposed rule, when promulgated, will not have a significant economic impact on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <HD SOURCE="HD1">Environmental Review</HD>
                <P>This proposal will be subject to an environmental analysis in accordance with FAA Order 1050.1F, “Environmental Impacts: Policies and Procedures” prior to any FAA final regulatory action.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 71</HD>
                    <P>Airspace, Incorporation by reference, Navigation (air).</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Proposed Amendment</HD>
                <P>In consideration of the foregoing, the Federal Aviation Administration proposes to amend 14 CFR part 71 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 71—DESIGNATION OF CLASS A, B, C, D, AND E AIRSPACE AREAS; AIR TRAFFIC SERVICE ROUTES; AND REPORTING POINTS</HD>
                </PART>
                <AMDPAR>1. The authority citation for 14 CFR part 71 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P> 49 U.S.C. 106(f), 106(g); 40103, 40113, 40120; E.O. 10854, 24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389.</P>
                </AUTH>
                <SECTION>
                    <SECTNO>§ 71.1</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <AMDPAR>2. The incorporation by reference in 14 CFR 71.1 of FAA Order JO 7400.11H, Airspace Designations and Reporting Points, dated August 11, 2023, and effective September 15, 2023, is amended as follows:</AMDPAR>
                <EXTRACT>
                    <HD SOURCE="HD2">Paragraph 2004 Jet Routes.</HD>
                    <STARS/>
                    <HD SOURCE="HD1">J-89 [Amended]</HD>
                    <P>From Louisville, KY; Boiler, IN; Northbrook, IL; Badger, WI; to Duluth, MN.</P>
                    <STARS/>
                    <HD SOURCE="HD2">Paragraph 2007 Canadian Area Navigation Routes.</HD>
                    <STARS/>
                    <GPOTABLE COLS="3" OPTS="L0,tp0,p0,8/9,g1,t1,i1" CDEF="xls125,xls50,xls190">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1"> </CHED>
                            <CHED H="1"> </CHED>
                            <CHED H="1"> </CHED>
                        </BOXHD>
                        <ROW EXPSTB="02">
                            <ENT I="22">
                                <E T="02">Q-834 Duluth, MN (DLH) to ALBNG, MN [New]</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Duluth, MN (DLH)</ENT>
                            <ENT>VORTAC</ENT>
                            <ENT>(Lat. 46°48′07.79″ N, long. 092°12′10.33&gt;″ W)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">ALBNG, MN</ENT>
                            <ENT>WP</ENT>
                            <ENT>(Lat. 48°59′58.05″ N, long. 095°38′10.41″ W)</ENT>
                        </ROW>
                    </GPOTABLE>
                    <PRTPAGE P="1854"/>
                    <STARS/>
                    <HD SOURCE="HD2">Paragraph 6010(a) VOR Federal Airways.</HD>
                    <STARS/>
                    <HD SOURCE="HD1">V-161 [Amended]</HD>
                    <P>From Three Rivers, TX; Center Point, TX; Llano, TX; INT Llano 026° and Millsap, TX, 193° radials; Millsap; Bowie, TX; Ardmore, OK; Okmulgee, OK; to Tulsa, OK. From Butler, MO; Napoleon, MO; Lamoni, IA; Des Moines, IA; Mason City, IA; Rochester, MN; Farmington, MN; to Gopher, MN.</P>
                    <STARS/>
                    <HD SOURCE="HD2">Paragraph 6013 Canadian Area Navigation Routes.</HD>
                    <STARS/>
                    <GPOTABLE COLS="3" OPTS="L0,tp0,p0,8/9,g1,t1,i1" CDEF="xls125,xls50,xls190">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1"> </CHED>
                            <CHED H="1"> </CHED>
                            <CHED H="1"> </CHED>
                        </BOXHD>
                        <ROW EXPSTB="02">
                            <ENT I="22">
                                <E T="02">T-765 International Falls, MN (INL) to CALDU, MN [New]</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">International Falls, MN (INL)</ENT>
                            <ENT>VOR/DME</ENT>
                            <ENT>(Lat. 48°33′56.87″ N, long. 093°24′20.44″ W)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">KORTY, MN</ENT>
                            <ENT>WP</ENT>
                            <ENT>(Lat. 48°35′20.54″ N, long. 093°27′59.55″ W)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01" O="xl">and</ENT>
                            <ENT/>
                            <ENT/>
                        </ROW>
                        <ROW>
                            <ENT I="01">LCROS, MN</ENT>
                            <ENT>WP</ENT>
                            <ENT>(Lat. 49°03′44.39″ N, long. 094°44′18.17″ W)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">CALDU, MN</ENT>
                            <ENT>WP</ENT>
                            <ENT>(Lat. 49°12′42.53″ N, long. 095°09′11.89″ W)</ENT>
                        </ROW>
                    </GPOTABLE>
                    <STARS/>
                </EXTRACT>
                <SIG>
                    <DATED>Issued in Washington, DC, on January 2, 2024.</DATED>
                    <NAME>Frank Lias,</NAME>
                    <TITLE>Manager, Rules and Regulations Group.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00152 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 71</CFR>
                <DEPDOC>[Docket No. FAA-2023-2567 Airspace Docket No. 23-ANM-32]</DEPDOC>
                <RIN>RIN 2120-AA66</RIN>
                <SUBJECT>Establishment of United States Area Navigation Routes Q-143 and T-467 in Southern Utah</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking (NPRM).</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This action proposes to establish United States Area Navigation Routes (RNAV) Q-143 and T-467 in southern Utah. The FAA is proposing this action to provide alternative routing around the TIPET and SEVIER Air Traffic Control Assigned Airspaces (ATCAA) and the WHITE ELK and GANDY Military Operations Areas (MOA).</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before February 26, 2024.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Send comments identified by FAA Docket No. FAA-2023-2567 and Airspace Docket No. 23-ANM-32 using any of the following methods:</P>
                    <P>
                        * 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">www.regulations.gov</E>
                         and follow the online instructions for sending your comments electronically.
                    </P>
                    <P>
                        * 
                        <E T="03">Mail:</E>
                         Send comments to Docket Operations, M-30; U.S. Department of Transportation, 1200 New Jersey Avenue SE, Room W12-140, West Building Ground Floor, Washington, DC 20590-0001.
                    </P>
                    <P>
                        * 
                        <E T="03">Hand Delivery or Courier:</E>
                         Take comments to Docket Operations in Room W12-140 of the West Building Ground Floor at 1200 New Jersey Avenue SE, Washington, DC, between 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 W12-140 of the West Building Ground Floor at 1200 New Jersey Avenue SE, Washington, DC, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.
                    </P>
                    <P>
                        FAA Order JO 7400.11H, Airspace Designations and Reporting Points, and subsequent amendments can be viewed online at 
                        <E T="03">www.faa.gov/air_traffic/publications/.</E>
                         You may also contact the Rules and Regulations Group, Office of Policy, Federal Aviation Administration, 800 Independence Avenue SW, Washington, DC 20591; telephone: (202) 267-8783.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Steven Roff, Rules and Regulations Group, Office of Policy, 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 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 would modify the route structure as necessary to preserve the safe and efficient flow of air traffic within the National Airspace System (NAS).</P>
                <HD SOURCE="HD1">Comments Invited</HD>
                <P>The FAA invites interested persons to participate in this rulemaking by submitting written comments, data, or views. Comments are specifically invited on the overall regulatory, aeronautical, economic, environmental, and energy-related aspects of the proposal. The most helpful comments reference a specific segment of the proposal, explain the reason for any recommended change, and include supporting data. To ensure the docket does not contain duplicate comments, commenters should submit only one time if comments are filed electronically, or commenters should send only one copy of written comments if comments are filed in writing.</P>
                <P>The FAA will file in the docket all comments it receives, as well as a report summarizing each substantive public contact with FAA personnel concerning this proposed rulemaking. Before acting on this proposal, the FAA will consider all comments it receives on or before the closing date for comments. The FAA will consider comments filed after the comment period has closed if it is possible to do so without incurring expense or delay. The FAA may change this proposal in light of the comments it receives.</P>
                <P>
                    <E T="03">Privacy:</E>
                     In accordance with 5 U.S.C. 553(c), DOT solicits comments from the public to better inform its rulemaking process. DOT posts these comments, without edit, including any personal information the commenter provides, to 
                    <E T="03">www.regulations.gov,</E>
                     as described in the system of records notice (DOT/ALL-14 FDMS), which can be reviewed at 
                    <E T="03">www.dot.gov/privacy.</E>
                </P>
                <HD SOURCE="HD1">Availability of Rulemaking Documents</HD>
                <P>
                    An electronic copy of this document may be downloaded through the 
                    <PRTPAGE P="1855"/>
                    internet at 
                    <E T="03">https://www.regulations.gov.</E>
                     Recently published rulemaking documents can also be accessed through the FAA's web page at 
                    <E T="03">www.faa.gov/air_traffic/publications/airspace_amendments/.</E>
                </P>
                <P>
                    You may review the public docket containing the proposal, any comments received and any final disposition in person in the Dockets Office (see 
                    <E T="02">ADDRESSES</E>
                     section for address, phone number, and hours of operations). An informal docket may also be examined during normal business hours at the office of the Operations Support Group, Western Service Center, Federal Aviation Administration, 2200 South 216th St., Des Moines, WA 98198.
                </P>
                <HD SOURCE="HD1">Incorporation by Reference</HD>
                <P>
                    United States Area Navigation Routes are published in paragraph 2006 (Q routes) and paragraph 6011 (T routes) of FAA Order JO 7400.11, Airspace Designations and Reporting Points, which is incorporated by reference in 14 CFR 71.1 on an annual basis. This document proposes to amend the current version of that order, FAA Order JO 7400.11H, dated August 11, 2023, and effective September 15, 2023. These updates would be published in the next update to FAA Order JO 7400.11. That order is publicly available as listed in the 
                    <E T="02">ADDRESSES</E>
                     section of this document.
                </P>
                <P>FAA Order JO 7400.11H lists Class A, B, C, D, and E airspace areas, air traffic service routes, and reporting points.</P>
                <HD SOURCE="HD1">Background</HD>
                <P>This action proposes to establish United States Area Navigation Routes (RNAV) Q-143 and T-467 in southern Utah. The FAA is proposing this action to provide alternative routing around the TIPET and SEVIER Air Traffic Control Assigned Airspaces (ATCAA) and the WHITE ELK and GANDY Military Operations Areas (MOA). This action would improve the safety and efficiency of the NAS by offering high and low altitude alternate RNAV routing when the aforementioned special use airspace is active. Currently, pilots are issued point-to-point clearances from air traffic control to ensure proper separation is maintained between the aircraft and the active special use airspace. The ability to issue a route clearance increases safety of flight and efficiency by reducing the workload on air traffic controllers and pilots. Q-143 would extend between the WINEN, waypoint (WP), UT to the BROPH, WP, ID and provide alternate routing to Q-73 when the TIPET and SEVIER ATCAAs are active. T-467 would extend between the BERYL, Fix, UT and the BROPH, WP, ID and provide alternative routing when the WHITE ELK and GANDY MOAs are active.</P>
                <HD SOURCE="HD1">The Proposal</HD>
                <P>The FAA is proposing an amendment to 14 CFR part 71 establishing United States Area Navigation Routes (RNAV) Q-143 and T-467 in southern Utah. The FAA is proposing this action to provide alternative routing around the TIPET and SEVIER ATCAAs and the WHITE ELK and GANDY MOAs when active.</P>
                <P>
                    <E T="03">T-467:</E>
                     T-467 would extend between the BERYL, Fix, UT and the BROPH, WP, ID and provide alternative routing when the WHITE ELK and GANDY MOAs are active.
                </P>
                <P>
                    <E T="03">Q-143:</E>
                     Q-143 would extend between the WINEN, WP, UT to the BROPH, WP, ID and provide alternate routing to Q-73 when the TIPET and SEVIER ATCAAs are active.
                </P>
                <HD SOURCE="HD1">Regulatory Notices and Analyses</HD>
                <P>The FAA has determined that this proposed regulation only involves an established body of technical regulations for which frequent and routine amendments are necessary to keep them operationally current. It, therefore: (1) is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under Department of Transportation (DOT) Regulatory Policies and Procedures (44 FR 11034; February 26, 1979); and (3) does not warrant preparation of a regulatory evaluation as the anticipated impact is so minimal. Since this is a routine matter that will only affect air traffic procedures and air navigation, it is certified that this proposed rule, when promulgated, will not have a significant economic impact on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <HD SOURCE="HD1">Environmental Review</HD>
                <P>This proposal will be subject to an environmental analysis in accordance with FAA Order 1050.1F, “Environmental Impacts: Policies and Procedures” prior to any FAA final regulatory action.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 71</HD>
                    <P>Airspace, Incorporation by reference, Navigation (air).</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Proposed Amendment</HD>
                <P>In consideration of the foregoing, the Federal Aviation Administration proposes to amend 14 CFR part 71 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 71—DESIGNATION OF CLASS A, B, C, D, AND E AIRSPACE AREAS; AIR TRAFFIC SERVICE ROUTES; AND REPORTING POINTS</HD>
                </PART>
                <AMDPAR>1. The authority citation for 14 CFR part 71 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P> 49 U.S.C. 106(f), 106(g); 40103, 40113, 40120; E.O. 10854, 24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389.</P>
                </AUTH>
                <SECTION>
                    <SECTNO>§ 71.1</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <AMDPAR>2. The incorporation by reference in 14 CFR 71.1 of FAA Order JO 7400.11H, Airspace Designations and Reporting Points, dated August 11, 2023, and effective September 15, 2023, is amended as follows:</AMDPAR>
                <EXTRACT>
                    <HD SOURCE="HD2">Paragraph 2006 United States Area Navigation Routes.</HD>
                    <STARS/>
                    <GPOTABLE COLS="3" OPTS="L0,tp0,p0,7/8,g1,t1,i1" CDEF="xls100,xls50,xls180">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1"> </CHED>
                            <CHED H="1"> </CHED>
                            <CHED H="1"> </CHED>
                        </BOXHD>
                        <ROW EXPSTB="02">
                            <ENT I="22">
                                <E T="04">Q-143 WINEN, UT to BROPH, ID [New]</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">WINEN, UT</ENT>
                            <ENT>WP</ENT>
                            <ENT>(Lat. 37°56′00.00″ N, long. 113°30′00.00″ W)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">TESSA, NV</ENT>
                            <ENT>WP</ENT>
                            <ENT>(Lat. 39°39′15.04″ N, long. 115°16′15.97″ W)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">RUBII, NV</ENT>
                            <ENT>WP</ENT>
                            <ENT>(Lat. 40°27′03.58″ N, long. 115°16′15.97″ W)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">CLEIN, NV</ENT>
                            <ENT>WP</ENT>
                            <ENT>(Lat. 41°53′37.36″ N, long. 114°52′51.96″ W)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BROPH, ID</ENT>
                            <ENT>WP</ENT>
                            <ENT>(Lat. 42°43′15.71″ N, long. 114°52′31.80″ W)</ENT>
                        </ROW>
                    </GPOTABLE>
                    <STARS/>
                    <HD SOURCE="HD2">Paragraph 6011 United States Area Navigation Routes.</HD>
                    <STARS/>
                    <GPOTABLE COLS="3" OPTS="L0,tp0,p0,7/8,g1,t1,i1" CDEF="xls100,xls50,xls180">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1"> </CHED>
                            <CHED H="1"> </CHED>
                            <CHED H="1"> </CHED>
                        </BOXHD>
                        <ROW EXPSTB="02">
                            <ENT I="22">
                                <E T="04">T-467 BERYL, UT to BROPH, ID [New]</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">BERYL, UT</ENT>
                            <ENT>FIX</ENT>
                            <ENT>(Lat. 37°54′00.17″ N, long. 113°23′08.58″ W)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">ELY, NV (ELY)</ENT>
                            <ENT>VOR/DME</ENT>
                            <ENT>(Lat. 39°17′53.25″ N, long. 114°50′53.90″ W)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">TESSA, NV</ENT>
                            <ENT>WP</ENT>
                            <ENT>(Lat. 39°39′15.04″ N, long. 115°16′15.97″ W)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">RUBII, NV</ENT>
                            <ENT>WP</ENT>
                            <ENT>(Lat. 40°27′03.58″ N, long. 115°16′15.97″ W)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">WELLS, NV (LWL)</ENT>
                            <ENT>VOR/DME</ENT>
                            <ENT>(Lat. 41°08′41.29″ N, long. 114°58′39.04″ W)</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="1856"/>
                            <ENT I="01">YIKUK, NV</ENT>
                            <ENT>FIX</ENT>
                            <ENT>(Lat. 41°59′05.16″ N, long. 114°51′49.12″ W)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BROPH, ID</ENT>
                            <ENT>WP</ENT>
                            <ENT>(Lat. 42°43′15.71″ N, long. 114°52′31.80″ W)</ENT>
                        </ROW>
                    </GPOTABLE>
                    <STARS/>
                </EXTRACT>
                <SIG>
                    <DATED>Issued in Washington, DC, on January 2, 2024.</DATED>
                    <NAME>Frank Lias,</NAME>
                    <TITLE>Manager, Rules and Regulations Group.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00085 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <CFR>21 CFR Part 73</CFR>
                <DEPDOC>[Docket No. FDA-2023-C-5679]</DEPDOC>
                <SUBJECT>Filing of Color Additive Petition From Environmental Defense Fund, et al.; Request To Amend the Color Additive Regulations To Remove the Solvents Ethylene Dichloride, Methylene Chloride, and Trichloroethylene</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notification of petition.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Food and Drug Administration (FDA or we) is announcing that we have filed a color additive petition, submitted by Environmental Defense Fund, et al., proposing that the color additive regulations be amended to remove three specified solvents.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The color additive petition was filed on December 21, 2023. Either electronic or written comments must be submitted by March 11, 2024.</P>
                </EFFDATE>
                <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 March 11, 2024. Comments received by mail/hand delivery/courier (for written/paper submissions) will be considered timely if they are received on or before that date.
                    </P>
                </ADD>
                <HD SOURCE="HD2">Electronic Submissions</HD>
                <P>Submit electronic comments in the following way:</P>
                <P>
                    • 
                    <E T="03">Federal eRulemaking Portal: https://www.regulations.gov.</E>
                     Follow the instructions for submitting comments. Comments submitted electronically, including attachments, to 
                    <E T="03">https://www.regulations.gov</E>
                     will be posted to the docket unchanged. Because your comment will be made public, you are solely responsible for ensuring that your comment does not include any confidential information that you or a third party may not wish to be posted, such as medical information, your or anyone else's Social Security number, or confidential business information, such as a manufacturing process. Please note that if you include your name, contact information, or other information that identifies you in the body of your comment, 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 instructions 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 objection, as well as any attachments, except for information submitted, marked and identified, as confidential, if submitted as detailed in “Instructions.”</P>
                <P>
                    <E T="03">Instructions:</E>
                     All submissions received must include the Docket No. FDA-2023-C-5679 for “Filing of Color Additive Petition From Environmental Defense Fund, et al.; Request To Amend the Color Additive Regulations To Remove the Solvents Ethylene Dichloride, Methylene Chloride, and Trichloroethylene.” Received comments, those filed in a timely manner (see DATES), 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 comment 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.” We will review this copy, including the claimed confidential information, in our 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>Paulette M. Gaynor, Center for Food Safety and Applied Nutrition, Food and Drug Administration, 5001 Campus Dr., College Park, MD 20740, 240-402-1192.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>Under section 721(d)(1) of the Federal Food, Drug, and Cosmetic Act (FD&amp;C Act) (21 U.S.C. 379e(d)(1)), we are giving notice that we have filed a color additive petition (CAP 4C0327), submitted by Environmental Defense Fund, Breast Cancer Prevention Partners, Center for Environmental Health, Environmental Working Group, and Lisa Lefferts, c/o Lisa Lefferts, Nellysford, VA 22958. The petition proposes that we amend §§ 73.1 (21 CFR 73.1, “Diluents in color additive mixtures for food use exempt from certification”), 73.30 (21 CFR 73.30, “Annatto extract”), 73.345 (21 CFR 73.345, “Paprika oleoresin”), and 73.615 (21 CFR 73.615, “Turmeric oleoresin”) to remove the use of three specified solvents.</P>
                <P>
                    The three solvents that are the subject of this petition are:
                    <PRTPAGE P="1857"/>
                </P>
                <P>1. Ethylene dichloride (CAS No. 107-06-2);</P>
                <P>2. Methylene chloride (CAS No. 75-09-2); and</P>
                <P>3. Trichloroethylene (CAS No. 79-01-6).</P>
                <HD SOURCE="HD1">II. Request To Amend 21 CFR Part 73</HD>
                <P>In accordance with the procedure in section 721(d) of the FD&amp;C Act for issuance, amendment, or repeal of regulations, the petition asks us to amend §§ 73.1, 73.30, 73.345, and 73.615 to remove ethylene dichloride, methylene chloride, and trichloroethylene. Specifically, the petitioners state these substances have been found to induce cancer in humans or animals and, therefore, are not safe pursuant to section 721(b)(5)(B) of the FD&amp;C Act (also referred to as the “Delaney Clause”). The Delaney Clause provides, in relevant part, that no color additive shall be deemed safe for any use which will or may result in ingestion of all or part of such additive, if the additive is found by the Secretary of Health and Human Services (Secretary) to induce cancer when ingested by man or animal, or if it is found by the Secretary, after tests which are appropriate for the evaluation of the safety of additives for use in food, to induce cancer in man or animal.</P>
                <P>
                    The petition is available in the docket. We invite comments, additional scientific data, and other information related to the issues raised by this petition. If we determine that the available data justify amending §§ 73.1, 73.30, 73.345, and 73.615 to remove ethylene dichloride, methylene chloride, and trichloroethylene, we will publish our decision in the 
                    <E T="04">Federal Register</E>
                     in accordance with 21 CFR 71.20.
                </P>
                <P>The petitioners have claimed that this action is categorically excluded under 21 CFR 25.32(m), which applies to an action to prohibit or otherwise restrict or reduce the use of a substance in food, food packaging, or cosmetics. In addition, the petitioners have stated that, to their knowledge, no extraordinary circumstances exist (see 21 CFR 25.21). If FDA determines a categorical exclusion applies, neither an environmental assessment nor an environmental impact statement is required. If FDA determines a categorical exclusion does not apply, we will request an environmental assessment and make it available for public inspection.</P>
                <SIG>
                    <DATED>Dated: January 8, 2024.</DATED>
                    <NAME>Lauren K. Roth,</NAME>
                    <TITLE>Associate Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00410 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4164-01-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <CFR>21 CFR Parts 172 and 173</CFR>
                <DEPDOC>[Docket No. FDA-2023-F-5684]</DEPDOC>
                <SUBJECT>Filing of Food Additive Petition From Environmental Defense Fund, et al.; Request To Amend the Food Additive Regulations To Remove the Solvents Benzene, Ethylene Dichloride, Methylene Chloride, and Trichloroethylene</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notification of petition.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Food and Drug Administration (FDA or we) is announcing that we have filed a food additive petition, submitted by Environmental Defense Fund, et al., proposing that the food additive regulations be amended to remove four specified solvents.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The food additive petition was filed on December 21, 2023. Submit either electronic or written comments on the filing notice by March 11, 2024.</P>
                </EFFDATE>
                <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 March 11, 2024. Comments received by mail/hand delivery/courier (for written/paper submissions) will be considered timely if they are received on or before that date.
                    </P>
                </ADD>
                <HD SOURCE="HD2">Electronic Submissions</HD>
                <P>Submit electronic comments in the following way:</P>
                <P>
                    • 
                    <E T="03">Federal eRulemaking Portal: https://www.regulations.gov.</E>
                     Follow the instructions for submitting comments. Comments submitted electronically, including attachments, to 
                    <E T="03">https://www.regulations.gov</E>
                     will be posted to the docket unchanged. Because your comment will be made public, you are solely responsible for ensuring that your comment does not include any confidential information that you or a third party may not wish to be posted, such as medical information, your or anyone else's Social Security number, or confidential business information, such as a manufacturing process. Please note that if you include your name, contact information, or other information that identifies you in the body of your comments, that information will be posted on 
                    <E T="03">https://www.regulations.gov.</E>
                </P>
                <P>• If you want to submit a comment with confidential information that you do not wish to be made available to the public, submit the comment as a written/paper submission and in the manner detailed (see “Written/Paper Submissions” and “Instructions”).</P>
                <HD SOURCE="HD2">Written/Paper Submissions</HD>
                <P>Submit written/paper submissions as follows:</P>
                <P>
                    • 
                    <E T="03">Mail/Hand Delivery/Courier (for written/paper submissions):</E>
                     Dockets Management Staff (HFA-305), Food and Drug Administration, 5630 Fishers Lane, Rm. 1061, Rockville, MD 20852.
                </P>
                <P>• For written/paper comments submitted to the Dockets Management Staff, FDA will post your comment, as well as any attachments, except for information submitted, marked and identified, as confidential, if submitted as detailed in “Instructions.”</P>
                <P>
                    <E T="03">Instructions:</E>
                     All submissions received must include the Docket No. FDA-2023-F-5684 for “Filing of Food Additive Petition from Environmental Defense Fund, et al.; Request To Amend the Food Additive Regulations To Remove the Solvents Benzene, Ethylene Dichloride, Methylene Chloride, and Trichloroethylene.” Received comments, those filed in a timely manner (see DATES), 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 comment 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.” We will review this copy, including the claimed confidential information, in our 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 
                    <PRTPAGE P="1858"/>
                    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>Paulette M. Gaynor, Center for Food Safety and Applied Nutrition, Food and Drug Administration, 5001 Campus Dr., College Park, MD 20740, 240-402-1192.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>Under section 409(b)(5) of the Federal Food, Drug, and Cosmetic Act (21 U.S.C. 348(b)(5)), we are giving notice that we have filed a food additive petition (FAP 4A4839), submitted by Environmental Defense Fund, Breast Cancer Prevention Partners, Center for Environmental Health, Environmental Working Group, and Lisa Lefferts, c/o Lisa Lefferts, Nellysford, VA 22958. The petition proposes that we amend §§ 172.560 (21 CFR 172.560, “Modified hop extract”), 172.710 (21 CFR 172.710, “Adjuvants for pesticide use dilutions”), 173.230 (21 CFR 173.230, “Ethylene dichloride”), 173.255 (21 CFR 172.255, “Methylene chloride”), 173.290 (21 CFR 173.290, “Trichloroethylene”), and 173.315 (21 CFR 173.315, “Chemicals used in washing or to assist in the peeling of fruits and vegetables”) to remove the use of four specified solvents.</P>
                <P>The four solvents that are the subject of this petition are:</P>
                <EXTRACT>
                    <P>1. Benzene (CAS No. 71-43-2);</P>
                    <P>2. Ethylene dichloride (CAS No. 107-06-2);</P>
                    <P>3. Methylene chloride (CAS No. 75-09-2); and</P>
                    <P>4. Trichloroethylene (CAS No. 79-01-6).</P>
                </EXTRACT>
                <HD SOURCE="HD1">II. Request To Amend 21 CFR Parts 172 and 173</HD>
                <P>In accordance with the procedures for amending or repealing a food additive regulation in § 171.130 (21 CFR 171.130), the petition asks us to amend §§ 172.560, 172.710, 173.230, 173.255, 173.290, and 173.315 to remove benzene, ethylene dichloride, methylene chloride, and trichloroethylene. Specifically, the petitioners state that these substances have been found to induce cancer in humans or animals and, therefore, are not safe pursuant to section 409(c)(3)(A) of the FD&amp;C Act (also referred to as the “Delaney Clause”). The Delaney Clause provides that no food additive shall be deemed to be safe if it is found to induce cancer when ingested by man or animal, or if it is found after tests which are appropriate for the evaluation of the safety of food additives, to induce cancer in man or animal.</P>
                <P>
                    The petition is available in the docket. We invite comments, additional scientific data, and other information related to the issues raised by this petition. If we determine that the available data justify amending §§ 172.560, 172.710, 173.230, 173.255, 173.290, and 173.315 to remove benzene, ethylene dichloride, methylene chloride, and trichloroethylene, we will publish our decision in the 
                    <E T="04">Federal Register</E>
                     in accordance with § 171.130.
                </P>
                <P>The petitioners have claimed that this action is categorically excluded under 21 CFR 25.32(m), which applies to an action to prohibit or otherwise restrict or reduce the use of a substance in food, food packaging, or cosmetics. In addition, the petitioners have stated that, to their knowledge, no extraordinary circumstances exist (see 21 CFR 25.21). If FDA determines a categorical exclusion applies, neither an environmental assessment nor an environmental impact statement is required. If FDA determines a categorical exclusion does not apply, we will request an environmental assessment and make it available for public inspection.</P>
                <SIG>
                    <DATED>Dated: January 8, 2024.</DATED>
                    <NAME>Lauren K. Roth,</NAME>
                    <TITLE>Associate Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00411 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4164-01-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Internal Revenue Service</SUBAGY>
                <CFR>26 CFR Part 1 and 301</CFR>
                <DEPDOC>[REG-118492-23; REG-113064-23; REG-120080-22]</DEPDOC>
                <RIN>RIN 1545-BQ99; RIN 1545-BQ86; RIN 1545-BQ52</RIN>
                <SUBJECT>Section 30D Excluded Entities; Transfer of Clean Vehicle Credits Under Section 25E and Section 30D; Section 30D New Clean Vehicle Credit; Hearing</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Internal Revenue Service (IRS), Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking; notice of hearing.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document provides a notice of public hearing on proposed regulations that would provide guidance regarding the proposed regulations under sections 25E, 30D, and 6213 with respect to the clean vehicle credits as amended by the Inflation Reduction Act of 2022.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The public hearing on these proposed regulations has been scheduled for Wednesday, January 31, 2024, at 10 a.m. ET. The IRS must receive speakers' outlines of the topics to be discussed at the public hearing by Thursday, January 18, 2024. If no outlines are received by Thursday, January 18, 2024, the public hearing will be cancelled.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The public hearing is being held in the Auditorium, at the Internal Revenue Service Building, 1111 Constitution Avenue NW, Washington, DC. Due to security procedures, visitors must enter at the Constitution Avenue entrance. In addition, all visitors must present a valid photo identification to enter the building. Because of access restrictions, visitors will not be admitted beyond the immediate entrance area more than 30 minutes before the hearing starts. Participants may alternatively attend the public hearing by telephone.</P>
                    <P>
                        Send Submissions to CC:PA:01:PR (REG-130080-22, REG-113064-23, and REG-118492-23), Room 5205, Internal Revenue Service, P.O. Box 7604, Ben Franklin Station, Washington, DC 20044. Submissions may be hand delivered Monday through Friday to CC:PA:01:PR (REG-130080-22, REG-113064-23, and REG-118492-23), Couriers Desk, Internal Revenue Service, 1111 Constitution Avenue NW, Room 5205, Washington, DC 20224 or sent electronically via the Federal eRulemaking Portal at 
                        <PRTPAGE P="1859"/>
                        <E T="03">www.regulations.gov</E>
                         (IRS REG-130080-22, IRS REG-113064-23, or IRS REG-118492-23).
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Concerning the proposed regulations, the Office of Associate Chief Counsel (Passthroughs and Special Industries), (202) 317-6835 (not a toll-free number); concerning submissions of comments, the hearing and/or to be placed on the building access list to attend the public hearing, call Vivian Hayes (202-317-6901) (not a toll-free number) or by email to 
                        <E T="03">publichearings@irs.gov</E>
                         (preferred).
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The subject of the public hearing is the notices of proposed rulemakings (REG-130080-22, REG-113064-23, REG-118492-23) that were published in the 
                    <E T="04">Federal Register</E>
                     on Monday, April 17, 2023, (FR 88 23370), Tuesday, October 10, 2023 (FR 88 70310), and Monday, December 4, 2023, (FR 88 84098) respectively.
                </P>
                <P>The rules of 26 CFR 601.601(a)(3) apply to the hearing. Persons who wish to present oral comments at the hearing must submit an outline of the topics to be discussed and the time to be devoted to each topic by January 18, 2024.</P>
                <P>
                    A period of 10 minutes will be allotted to each person for making comments. An agenda showing the scheduling of the speakers will be prepared after the deadline for receiving outlines has passed. Copies of the agenda will be available free of charge at the hearing, and via the Federal eRulemaking Portal (
                    <E T="03">www.Regulations.gov</E>
                    ) under the title of Supporting &amp; Related Material. If no outline of the topics to be discussed at the hearing is received by January 18, 2024, the public hearing will be cancelled. If the public hearing is cancelled, a notice of cancellation of the public hearing will be published in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <P>
                    Individuals who want to testify in person at the public hearing must send an email to 
                    <E T="03">publichearings@irs.gov</E>
                     to have your name added to the building access list. The subject line of the email must contain the regulation number REG-130080-22, REG-113064-23, and REG-118492-23 and the language TESTIFY In Person. For example, the subject line may say: Request to TESTIFY In Person at Hearing for REG-130080-22, REG-113064-23, and REG-118492-23.
                </P>
                <P>
                    Individuals who want to testify by telephone at the public hearing must send an email to 
                    <E T="03">publichearings@irs.gov</E>
                     to receive the telephone number and access code for the hearing. The subject line of the email must contain the regulation number REG-130080-22, REG-113064-23, and REG-118492-23 and the language TESTIFY Telephonically. For example, the subject line may say: Request to TESTIFY Telephonically at Hearing for REG-130080-22, REG-113064-23, and REG-118492-23, whichever applies.
                </P>
                <P>
                    Individuals who want to attend the public hearing in person without testifying must also send an email to 
                    <E T="03">publichearings@irs.gov</E>
                     to have your name added to the building access list. The subject line of the email must contain the regulation number REG-130080-22, REG-113064-23, and REG-118492-23 and the language ATTEND In Person. For example, the subject line may say: Request to ATTEND Hearing In Person for REG-130080-22, REG-113064-23, and REG-118492-23, whichever applies. Requests to attend the public hearing must be received by 5 p.m. ET by Monday, January 29, 2024.
                </P>
                <P>
                    Individuals who want to attend the public hearing by telephone without testifying must also send an email to 
                    <E T="03">publichearings@irs.gov</E>
                     to receive the telephone number and access code for the hearing. The subject line of the email must contain the regulation number REG-130080-22, REG-113064-23, and REG-118492-23 and the language ATTEND Hearing Telephonically. For example, the subject line may say: Request to ATTEND Hearing Telephonically for REG-130080-22, REG-113064-23, and REG-118492-23, whichever applies. Requests to attend the public hearing must be received by 5:00 p.m. ET by Monday, January 29, 2024.
                </P>
                <P>
                    Hearings will be made accessible to people with disabilities. To request special assistance during a hearing please contact the Publications and Regulations Section of the Office of Associate Chief Counsel (Procedure and Administration) by sending an email to 
                    <E T="03">publichearings@irs.gov</E>
                     (preferred) or by telephone at (202) 317-6901 (not a toll-free number) by 5:00 p.m. ET on Friday, January 26, 2024.
                </P>
                <P>
                    Any questions regarding speaking at or attending a public hearing may also be emailed to 
                    <E T="03">publichearings@irs.gov.</E>
                </P>
                <SIG>
                    <NAME>Oluwafunmilayo A. Taylor,</NAME>
                    <TITLE>Section Chief, Publications and Regulations Section, Associate Chief Counsel (Procedure and Administration).</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00375 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4830-01-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                <CFR>47 CFR Part 1</CFR>
                <DEPDOC>[WC Docket No. 17-84; FCC 23-109; FR ID 193610]</DEPDOC>
                <SUBJECT>Accelerating Wireline Broadband Deployment by Removing Barriers to Infrastructure Investment</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In this document, the Commission adopted a Third Further Notice of Proposed Rulemaking (FNPRM) that tentatively concludes that the Commission should take further action to facilitate the processing of pole attachment applications that are submitted in large numbers. It also seeks comment on whether the Commission should modify its self-help rules to enable prospective attachers to access poles more quickly. Finally, it seeks comment on the impact of contractor availability when attachers seek to use their own contractors when conducting self-help or one-touch make-ready for surveys and make-ready work.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments are due on or before February 13, 2024, and reply comments are due on or before February 28, 2024. Written comments on the Paperwork Reduction Act proposed information collection requirements must be submitted by the public, Office of Management and Budget (OMB), and other interested parties on or before March 11, 2024.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Pursuant to sections 1.415 and 1.419 of the Commission's rules, 47 CFR 1.415, 1.419, interested parties may file comments and reply comments on or before the dates indicated in this document. Comments and reply comments may be filed using the Commission's Electronic Comment Filing System (ECFS). See 
                        <E T="03">Electronic Filing of Documents in Rulemaking Proceedings,</E>
                         63 FR 24121 (1998). Interested parties may file comments or reply comments, identified by CG Docket No. 17-59 and WC Docket No. 17-97 by any of the following methods:
                    </P>
                    <P>
                        • 
                        <E T="03">Electronic Filers:</E>
                         Comments may be filed electronically by accessing ECFS at 
                        <E T="03">https://www.fcc.gov/ecfs/.</E>
                    </P>
                    <P>
                        • 
                        <E T="03">Paper Filers:</E>
                         Parties who choose to file by paper must file an original and one copy of each filing. Paper filings can be sent by commercial overnight courier, or by first-class or overnight U.S. Postal Service mail.
                    </P>
                    <P>
                        • Effective March 19, 2020, and until further notice, the Commission no 
                        <PRTPAGE P="1860"/>
                        longer accepts any hand or messenger delivered filings.
                    </P>
                    <P>• Commercial overnight mail (other than U.S. Postal Service Express Mail and Priority Mail) must be sent to 9050 Junction Drive, Annapolis Junction, MD 20701.</P>
                    <P>• U.S. Postal Service first-class, Express, and Priority mail must be addressed to 45 L Street NE, Washington, DC 20554.</P>
                    <P>
                        In addition to filing comments with the Secretary, a copy of any comments on the Paperwork Reduction Act proposed information collection requirements contained herein should be submitted to the Federal Communications Commission via email to 
                        <E T="03">PRA@fcc.gov</E>
                         and to Nicole Ongele, FCC, via email to 
                        <E T="03">Nicole.Ongele@fcc.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For further information, please contact either Michele Berlove, Assistant Division Chief, Competition Policy Division, Wireline Competition Bureau, at 
                        <E T="03">michele.berlove@fcc.gov</E>
                         or at (202) 418-1477, or Michael Ray, Attorney Advisor, Competition Policy Division, Wireline Competition Bureau, at 
                        <E T="03">michael.ray@fcc.gov</E>
                         or at (202) 418-0357. For additional information concerning the Paperwork Reduction Act proposed information collection requirements contained in this document, send an email to 
                        <E T="03">PRA@fcc.gov</E>
                         or contact Nicole Ongele at (202) 418-2991.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    This is a summary of the Commission's Third Further Notice of Proposed Rulemaking (FNPRM) in WC Docket No. 17-84, FCC 23-109, adopted on December 13, 2023, and released on December 15, 2023. The full text of this document is available for public inspection at the following internet address: 
                    <E T="03">https://www.fcc.gov/document/fcc-seeks-make-pole-attachment-process-faster-more-transparent-and-more-cost-effective.</E>
                     The Providing Accountability Through Transparency Act, Public Law 118-9, requires each agency, in providing notice of a rulemaking, to post online a brief plain-language summary of the proposed rule. The required summary of this 
                    <E T="03">FNPRM</E>
                     is available at 
                    <E T="03">https://www.fcc.gov/proposed-rulemakings.</E>
                     To request materials in accessible formats for people with disabilities (
                    <E T="03">e.g.,</E>
                     Braille, large print, electronic files, audio format), send an email to 
                    <E T="03">fcc504@fcc.gov</E>
                     or call the Consumer &amp; Governmental Affairs Bureau at (202) 418-0530.
                </P>
                <HD SOURCE="HD1">Initial Paperwork Reduction Act of 1995 Analysis</HD>
                <P>This document may contain proposed information collection requirements. The Commission, as part of its continuing effort to reduce paperwork burdens, invites the general public to comment on the information collection requirements contained in this document, as required by the Paperwork Reduction Act of 1995, Public Law 104-13.</P>
                <P>
                    <E T="03">Comments should address:</E>
                     (a) whether the proposed collection of information is necessary for the proper performance of the functions of the Commission, including whether the information shall have practical utility; (b) the accuracy of the Commission's burden estimates; (c) ways to enhance the quality, utility, and clarity of the information collected; (d) ways to minimize the burden of the collection of information on the respondents, including the use of automated collection techniques or other forms of information technology; and (e) way to further reduce the information collection burden on small business concerns with fewer than 25 employees. In addition, pursuant to the Small Business Paperwork Relief Act of 2002, Public Law 107-198, 
                    <E T="03">see</E>
                     44 U.S.C. 3506(c)(4), we seek specific comment on how we might further reduce the information collection burden for small business concerns with fewer than 25 employees.
                </P>
                <HD SOURCE="HD1">Comment Period and Filing Procedures</HD>
                <P>
                    Pursuant to sections 1.415 and 1.419 of the Commission's rules, 47 CFR 1.415, 1.419, interested parties may file comments and reply comments on or before the dates indicated on the first page of this document. Comments may be filed using the Commission's Electronic Comment Filing System (ECFS) or by paper. Commenters should refer to WC Docket No. 21-341 when filing in response to this 
                    <E T="03">FNPRM.</E>
                </P>
                <P>
                    • 
                    <E T="03">Electronic Filers:</E>
                     Comments may be filed electronically by accessing ECFS at 
                    <E T="03">https://www.fcc.gov/ecfs.</E>
                </P>
                <P>
                    • 
                    <E T="03">Paper Filers:</E>
                     Parties who choose to file by paper must file an original and one copy of each filing. Paper filings can be sent by commercial overnight courier, or by first-class or overnight U.S. Postal Service mail.
                </P>
                <P>• Effective March 19, 2020, and until further notice, the Commission no longer accepts any hand or messenger delivered filings.</P>
                <P>• Commercial overnight mail (other than U.S. Postal Service Express Mail and Priority Mail) must be sent to 9050 Junction Drive, Annapolis Junction, MD 20701.</P>
                <P>U.S. Postal Service first-class, Express, and Priority Mail must be addressed to 45 L Street NE, Washington, DC 20554.</P>
                <P>
                    <E T="03">People with Disabilities:</E>
                     To request materials in accessible formats for people with disabilities (braille, large print, electronic files, audio format), send an email to 
                    <E T="03">fcc504@fcc.gov</E>
                     or call the Consumer &amp; Governmental Affairs Bureau at 202-418-0530 (voice), 202-418-0432 (TTY).
                </P>
                <HD SOURCE="HD1">Synopsis</HD>
                <HD SOURCE="HD1">I. Introduction</HD>
                <P>1. Access to a broadband connection is a necessity of modern life. With consumers more dependent than ever on fixed and mobile broadband networks for work, healthcare services, education, and social activities, the Commission remains committed to ensuring consumers across the nation have meaningful access to broadband. With the support of the Commission's universal service fund, the Infrastructure Investment and Jobs Act, which included the largest ever federal investment in broadband, as well as other federal and state broadband deployment programs, more funding than ever is available to build the necessary infrastructure to bring much-needed broadband services to unserved and underserved areas in the United States. Key to these broadband projects are the utility poles that support the wires and the wireless equipment that carry broadband to American homes and businesses.</P>
                <P>
                    2. Over the last several years, the Commission has taken significant steps in setting the “rules for the road” for the discussions between utilities and telecommunications companies about the timing and cost of attaching broadband equipment to utility poles, with the backstop of a robust complaint process when parties cannot agree on the rates, terms, and conditions for pole attachments. (Note that section 224(c) of the Communications Act of 1934, as amended (the Act), exempts from Commission jurisdiction those pole attachments in states that have elected to regulate pole attachments themselves. To date, 23 states and the District of Columbia have opted out of Commission regulation of pole attachments in their jurisdictions. The Commission's pole attachment rules currently only apply to cable operators and providers of telecommunications services and therefore do not apply to broadband-only internet service providers. We recently proposed to reclassify broadband internet access service as a telecommunications service, 
                    <PRTPAGE P="1861"/>
                    which would, if completed, apply section 224 and the Commission's pole attachment rules to broadband-only internet service providers.) In this item, we take additional steps to speed broadband deployment by making the pole attachment process faster, more transparent, and more cost effective. Specifically, we adopt rules (1) establishing a new process for the Commission's review and assessment of pole attachment disputes that impede or delay broadband deployment in order to expedite resolution of such disputes, and (2) providing communications providers with information about the status of the utility poles they plan to use as they map out their broadband builds. Additionally, as a follow-on to the pole replacement clarification issued in the 
                    <E T="03">2021 Pole Replacement Declaratory Ruling,</E>
                     in the Declaratory Ruling below we provide further clarification regarding cost causation when a pole must be replaced for any reason other than lacking capacity to support a new attachment. Specifically, we clarify that a “red tagged” pole is one that the utility has identified as needing replacement for any reason other than the pole's lack of capacity, and we provide additional examples of when a pole replacement is not “necessitated solely” as a result of a third party's attachment or modification request—
                    <E T="03">i.e.,</E>
                     when a pole already requires replacement at the time the new attacher makes a request. We also clarify the obligation to share easement information and the applicable timelines for the processing of attachment requests for 3,000 or more poles. Finally, we seek comment in the FNPRM on ways to further facilitate the processing of pole attachment applications and make-ready to enable faster broadband deployment.
                </P>
                <HD SOURCE="HD1">II. Background</HD>
                <P>
                    3. In 1996, as part of its implementation of the pole attachment requirements located in sections 224(h) and 224(i) of the Act, the Commission determined that when a modification, such as a pole replacement, is undertaken for the benefit of a particular party, then under cost causation principles, the benefiting party must assume the cost of the modification. (Section 224(h) states that “[w]henever the owner of a pole, duct, conduit, or right-of-way intends to modify or alter such pole, duct, conduit, or right-of-way, the owner shall provide written notification of such action to any entity that has obtained an attachment to such conduit or right-of-way so that such entity may have a reasonable opportunity to add to or modify its existing attachment. Any entity that adds to or modifies its existing attachment after receiving such notification shall bear a proportionate share of the costs incurred by the owner in making such pole, duct, conduit, or right-of-way accessible.” Section 224(i) states that “[a]n entity that obtains an attachment to a pole, conduit, or right-of-way shall not be required to bear any of the costs of rearranging or replacing its attachment, if such rearrangement or replacement is required as a result of an additional attachment or the modification of an existing attachment sought by any other entity (including the owner of such pole, duct, conduit, or right-of-way).”) The Commission also found that when a utility decides to modify a pole for its own benefit, and no other attachers derive a benefit from the modification, the utility must bear the full cost of the new pole. The Commission further adopted a cost sharing principle for when an existing attacher uses a modification by another party as an opportunity to add to or modify its own attachments and applied this principle to utilities and other attachers seeking to use modifications as an opportunity to bring their own facilities into compliance with safety or other requirements. In the 
                    <E T="03">2018 Wireline Infrastructure Order,</E>
                     the Commission reiterated that application of the cost sharing principle.
                </P>
                <P>4. On July 16, 2020, NCTA—the Internet &amp; Television Association (NCTA) filed a Petition asking the Commission to clarify its rules in the context of pole replacements. Specifically, NCTA asked the Commission to declare that: (1) utilities must share in the cost of pole replacements in unserved areas pursuant to section 224 of the Act, section 1.1408(b) of the Commission's rules, and Commission precedent; (2) pole attachment complaints arising in unserved areas should be prioritized through placement on the Accelerated Docket under § 1.736 of the Commission's rules; and (3) § 1.1407(b) of the Commission's rules authorizes the Commission to order a utility to complete a pole replacement within a specified time frame or designate an authorized contractor to do so. NCTA argued that without Commission action, the costs and operational challenges associated with pole replacements will inhibit attachers from deploying broadband services to Americans in unserved areas.</P>
                <P>
                    5. In the 
                    <E T="03">2021 Pole Replacement Declaratory Ruling,</E>
                     although the Wireline Competition Bureau declined to act on NCTA's Petition, finding that “it is more appropriate to address questions concerning the allocation of pole replacement costs within the context of a rulemaking, which provides the Commission with greater flexibility to tailor regulatory solutions,” it observed that the record developed in response to the NCTA Petition revealed inconsistent practices by utilities with regard to cost responsibility for pole replacements. Accordingly, the Bureau clarified that, pursuant to § 1.1408(b) of the Commission's rules and prior precedent, “utilities may not require requesting attachers to pay the entire cost of pole replacements that are not solely caused by the new attacher and, thus, may not avoid responsibility for pole replacement costs by postponing replacements until new attachment requests are submitted.” The Commission subsequently affirmed the Bureau's clarifications.
                </P>
                <P>
                    6. Last year, the Commission issued a 
                    <E T="03">Second Further Notice</E>
                     (87 FR 25181; Apr. 28, 2022) in this proceeding seeking comment on the universe of situations where the requesting attacher should not be required to pay for the full cost of a pole replacement and the proper allocation of costs among utilities and attachers in those situations. (To the extent that this Report and Order does not expressly address a topic that was subject to comment in the 
                    <E T="03">Second Further Notice,</E>
                     that issue remains pending.) Specifically, the Commission sought comment on the applicability of cost causation and cost allocation principles in the context of pole replacements—
                    <E T="03">e.g.,</E>
                     when is a pole replacement not caused (necessitated solely) by a new attachment request, and when and how parties must share in the costs of a pole replacement. The Commission also sought comment on the extent to which utilities directly benefit from pole replacements, including a utility's responsibility for the costs of pole upgrades and modifications unrelated to new attachments and the effect of early pole retirements on pole replacement cost causation and cost allocation calculations. The 
                    <E T="03">Second Further Notice</E>
                     also sought comment on whether the Commission should require utilities to share information with potential attachers concerning the condition and replacement status of their poles and other measures that may help avoid or expedite the resolution of disputes between the parties, including whether to expand use of the Commission's Accelerated Docket for pole attachment complaints and the specific criteria that Commission staff should use in deciding whether to place a pole complaint on the Accelerated Docket.
                    <PRTPAGE P="1862"/>
                </P>
                <HD SOURCE="HD1">III. Further Notice of Proposed Rulemaking</HD>
                <P>7. We recognize that Congress has undertaken a number of initiatives allocating funding to further the deployment of broadband to unserved and underserved areas of the United States. In connection with this funding, broadband providers will have to deploy extensive facilities. This, in turn will require that they file significant numbers of applications seeking to attach these facilities to large numbers of poles. To that end, we seek comment on ways to further facilitate the approval process for pole attachment applications and make-ready to enable speedier broadband deployment. In seeking comment on these areas, we emphasize that even when there is not a specific Commission rule or policy that governs a particular situation, it is our expectation that parties negotiate in good faith to resolve issues that may arise.</P>
                <P>
                    8. 
                    <E T="03">Large Orders.</E>
                     We tentatively conclude that we should adopt a defined make-ready timeline for orders that exceed 3,000 poles or 5 percent of the utility's poles in a state in order to facilitate the processing of pole attachment applications that are submitted in large numbers. We seek comment on this tentative conclusion. Our current make-ready rule requires make-ready in the communications space to be completed within 30 days after the utility sends a notification to all existing attachers on a pole. (The rule provides 90 days from attachments above the communications space.) The 30-day timeframe applies for communications space make-ready requests up to the lesser of 300 poles or 0.5 percent of the utility's poles in a state. This make-ready timeframe is extended 45 extra days for requests up to the lesser of 3,000 poles or 5 percent of the utility's poles in a state. For requests exceeding 3,000 poles or 5 percent of the utility's poles in the state, the Commission's rules require that a utility shall negotiate the timing of the make-ready in good faith. (As we clarify in the Declaratory Ruling accompanying this FNPRM, the first 3,000 poles of these large orders are subject to the timeline set forth in § 1.1411(g)(3).) We tentatively conclude that utilities should have an additional 90 days for make-ready for requests exceeding 3,000 poles or 5 percent of the utility's poles in a state and seek comment on this tentative conclusion.
                </P>
                <P>9. NCTA asserts that our rules do not at present sufficiently address the needs of attachers with these larger requests in the latter category. For example, NCTA asserts that its members have faced situations where the utilities have imposed limits on (1) the number of poles that may be included in any one application, and (2) the number of applications an attacher may submit at a time. NCTA states that these limitations “create problematic delays and jeopardize operators' ability to meet broadband build-out commitments.” At the same time, USTelecom notes the difficulties presented by these very large orders, noting that “make-ready requests involving more than 3,000 poles require flexibility that make-ready timelines cannot provide, given the many outside factors that impact the time required for make-ready for such large orders, including permitting delays, workforce shortages and staffing issues, and the coordination required among all the attachers to the poles.” Given these factors, would 90 additional days over the timeline set forth in § 1.411(e) be sufficient for processing these larger orders? Would some other amount of time be reasonable in all circumstances, or should the Commission create additional make-ready timeline tiers in its rules to differentiate between attachment applications that could range from requesting access to thousands of poles to tens or even hundreds of thousands of poles? If the Commission were to adopt additional make-ready timeline tiers, what would be an appropriate cut off number of poles for each tier? For instance, should the Commission add an additional number of days for application processing per 3,000 poles? Does the ability to deviate from the timelines specified in § 1.1411 provide utilities with enough flexibility such that imposing a 90 additional day limit would be reasonable?</P>
                <P>
                    10. We also seek comment on NCTA's proposal that the Commission revise its rules to prohibit utilities from limiting “the size of an application or the number of poles included in an application so as to avoid the timelines.” How prevalent are situations of the type described by NCTA? Are the reasons underlying utilities' imposition of such limitations as laid out by USTelecom valid, and do other reasons exist for these limitations? Would prohibiting utilities from imposing such limitations in fact speed up the attachment process, or would the same delays still exist for other reasons (
                    <E T="03">e.g.,</E>
                     lack of qualified workers, shortages in materials, etc.) or even, as USTelecom alleges, “ultimately slow—rather than—accelerate deployment”? Specifically, NCTA proposes adding additional time to the existing timelines for these “larger” orders, for which our rules require that utilities negotiate the timing in good faith. Would NCTA's proposed new timing requirements for larger orders facilitate the pole attachment process for such orders? Utilities have raised multiple concerns with such requirements. For example, they assert that compliance with expanded timelines may not be possible “if many permit applications by multiple attachers are submitted at approximately the same time, or if the contractor's workload is already heavy.” They also assert that given constraints on workforce availability, utilities would be forced to “choose between providing safe, reliable and affordable power to electric customers (which is mandated by the states), and performing requested pole replacements in an unreasonable and likely unattainable amount of time.” Are these concerns valid? Are there any other reasons why NCTA's proposed new timing requirements for larger orders would not work? What are the respective costs and benefits of such potential requirements? What other steps could we take to facilitate the pole attachment process for larger orders?
                </P>
                <P>
                    11. 
                    <E T="03">Self-Help and Use of Contractors.</E>
                     Should the Commission consider modifying its self-help rules to enable prospective attachers to access poles more quickly? NCTA also asserts that it has faced issues with utilities failing to process attachment applications in a timely manner. NCTA therefore proposes that utilities notify attachers in advance of survey and make-ready deadlines if the utility will be unable to complete a portion of the process. For instance, NCTA proposes that the utility notify an attacher 15 days after receiving a complete application that it cannot conduct the survey within the required 45-day period so that the attacher can elect self-help for the survey sooner. NCTA also proposes making self-help available for the estimate process, which is not contemplated under current Commission rules. We seek comment on NCTA's proposal. (We decline NCTA's request to adopt rules in the Fourth Report and Order regarding self-help and the use of contractors. We find that these issues would be better addressed after a more comprehensive record is developed.) How prevalent is the issue cited by NCTA? Can utilities feasibly be required to inform attachers within 15 business days of receiving a completed application that they will be unable to conduct a survey, estimate, or make-ready within the required time period? Do sufficient contractors exist that meet the minimum qualification 
                    <PRTPAGE P="1863"/>
                    requirements set forth in our rules such that adoption of NCTA's proposal would have the desired effect of speeding broadband deployment? What are the respective costs and benefits of adopting NCTA's proposal? Are there other ways to assist utilities in processing the larger number of applications they will likely receive in the coming months and years based on the funding initiatives in place for accelerating broadband deployment to unserved and underserved areas?
                </P>
                <P>12. We also seek comment on the impact of contractor availability when attachers seek to use their own contractors when conducting self-help or one-touch make-ready for surveys and make-ready work. Specifically, do we need to amend the Commission's rules to make it easier for attachers to use their own contractors to do self-help and one-touch make-ready surveys and make-ready work when there are no contractors available from a utility list? Utility commenters point out the labor constraints in the contractor workforce; given such constraints, do our current rules provide adequate relief to attachers to timely identify and use qualified contractors to do self-help and one-touch make-ready work? If not, what can the Commission do to change this dynamic?</P>
                <P>13. Pursuant to our rules, an attacher can do its own work when (1) completing surveys and make-ready work when the utility misses the deadlines for these activities, or (2) electing to use the one-touch make-ready process. (Note that there are no attacher self-help remedies for pole replacements.) When conducting self-help or one-touch make-ready work, the attacher must use a utility-approved contractor. For self-help surveys and make-ready work that is complex or is above the communications space on a pole, our rules require that a utility make available and keep up to date a reasonably sufficient list of contractors that it authorizes to perform such work. (The term “complex make-ready” means transfers and work within the communications space on a pole that would be reasonably likely to cause a service outage(s) or facility damage, including work such as splicing of any communication attachment or relocation of existing wireless attachments. Any and all wireless activities, including those involving mobile, fixed, and point-to-point wireless communications and wireless internet service providers, are to be considered complex.) Attachers can request to add contactors to the utility's list—provided the contractor meets the minimum qualifications in the Commission's rules—and the utility cannot unreasonably withhold its consent. Further, a utility may, but is not required to, keep up-to-date a reasonably sufficient list of contractors it authorizes to perform surveys and simple make-ready. If a utility provides such a list, then the new attacher must choose a contractor from the list to perform the work. Again, attachers may request the addition to the list of any contractor that meets the minimum qualifications in the Commission's rules, and the utility cannot unreasonably withhold its consent. However, if the utility does not provide a list of approved contractors for surveys or simple make-ready work or no utility-approved contractor is available within a reasonable time period, then the new attacher may choose its own qualified contractor who meets the Commission's minimum requirements. Utilities retain the right to disqualify such contractor, but disqualification must be based on reasonable safety or reliability concerns related to the contractor's failure to meet any of the Commission's minimum qualifications or to meet the utility's publicly available and commercially reasonable safety or reliability standards. The utility must provide notice of this objection to the attacher and must identify at least one available qualified contractor that the attacher can use instead to perform simple surveys and make-ready work.</P>
                <P>14. Given that our current rules allow for attachers to choose their own contractors for one-touch make-ready and for self-help when the utility fails to meet the Commission's deadlines (provided such contractors meet the minimum qualifications set forth in our rules), we seek comment on whether attachers are availing themselves of this option. Have attachers faced any obstacles from utilities when seeking to invoke this option? While a utility cannot be blamed for a lack of available contractors in an area due to workforce constraints, are utilities seeking to use their discretion set forth in the rules to disqualify otherwise-qualified contractors whom attachers may seek to bring in from outside of an area? We note that, at least for surveys and simple make-ready work, our current rules already require the utility to designate an available contractor if it properly exercises its discretion to disqualify one chosen by an attacher—is this not being done? If not, is it due to labor constraints for which the utility should not be held responsible? In the instance where no qualified contractors are available for a project, how could the Commission help to solve that problem?</P>
                <HD SOURCE="HD1">IV. Initial Regulatory Flexibility Analysis</HD>
                <P>
                    15. As required by the Regulatory Flexibility Act of 1980, as amended (RFA), the Commission has prepared this Initial Regulatory Flexibility Analysis (IRFA) of the possible significant economic impact on small entities by the policies and rules proposed in this 
                    <E T="03">FNPRM.</E>
                     The Commission requests written public comments on this IRFA. Comments must be identified as responses to the IRFA and must be filed by the deadlines for comments provided on the first page of the 
                    <E T="03">FNPRM.</E>
                     The Commission will send a copy of the 
                    <E T="03">FNPRM,</E>
                     including this IRFA, to the Chief Counsel for Advocacy of the Small Business Administration (SBA). In addition, the 
                    <E T="03">FNPRM</E>
                     and IRFA (or summaries thereof) will be published in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <HD SOURCE="HD2">A. Need for, and Objectives of, the Proposed Rules</HD>
                <P>16. In order to continue the Commission's work combating illegal calls, this FNPRM proposes to impose several obligations on gateway providers. Specifically, the FNPRM proposes to require gateway providers to authenticate and employ robocall mitigation techniques on all SIP calls that they allow into the United States from abroad that display a U.S. number in the caller ID field. The FNPRM also proposes that gateway providers should engage in robocall mitigation by (1) responding to all traceback requests from the Commission, law enforcement, and the industry traceback consortium within 24 hours; (2) complying with mandatory call blocking requirements; (3) complying with enhanced know-your-customer obligations; (4) complying with a general duty to mitigate illegal robocalls; and (5) filing a certification in the Robocall Mitigation Database. The Commission also proposes one blocking requirement for intermediate and terminating providers immediately downstream from the gateway provider, which would require those providers to block all traffic from a gateway provider that fails to block or effectively mitigate illegal traffic when notified of such traffic by the Commission.</P>
                <HD SOURCE="HD2">B. Legal Basis</HD>
                <P>
                    17. The FNPRM proposes to find authority largely under those provisions through which it has previously adopted rules to stem the tide of robocalls in its 
                    <E T="03">Call Blocking</E>
                     and 
                    <E T="03">
                        Call 
                        <PRTPAGE P="1864"/>
                        Authentication Orders.
                    </E>
                     Specifically, the FNPRM proposes to find authority under sections 201(a) and (b), 202(a), 251(e), the Truth in Caller ID Act, the TRACED Act and, where appropriate, ancillary authority. The FNPRM also proposes to conclude that, to the extent any of the rules we seek to adopt have an effect on foreign service providers, that effect is only indirect and therefore consistent with the Commission's authority. The FNPRM solicits comment on these proposals.
                </P>
                <HD SOURCE="HD2">C. Description and Estimate of the Number of Small Entities to Which the Proposed Rules Will Apply</HD>
                <P>
                    18. The RFA directs agencies to provide a description of, and where feasible, an estimate of the number of small entities that may be affected by the proposed rules, if adopted. The RFA generally defines the term “small entity” as having the same meaning as the terms “small business,” “small organization,” and “small governmental jurisdiction.” In addition, the term “small business” has the same meaning as the term “small business concern” under the Small Business Act. (Pursuant to 5 U.S.C. 601(3), the statutory definition of a small business applies “unless an agency, after consultation with the Office of Advocacy of the Small Business Administration and after opportunity for public comment, establishes one or more definitions of such term which are appropriate to the activities of the agency and publishes such definition(s) in the 
                    <E T="04">Federal Register</E>
                    .”) A “small business concern” is one which: (1) is independently owned and operated; (2) is not dominant in its field of operation; and (3) satisfies any additional criteria established by the SBA.
                </P>
                <P>
                    19. 
                    <E T="03">Small Businesses, Small Organizations, Small Governmental Jurisdictions.</E>
                     Our actions, over time, may affect small entities that are not easily categorized at present. We therefore describe, at the outset, three broad groups of small entities that could be directly affected herein. First, while there are industry specific size standards for small businesses that are used in the regulatory flexibility analysis, according to data from the Small Business Administration's (SBA) Office of Advocacy, in general a small business is an independent business having fewer than 500 employees. These types of small businesses represent 99.9% of all businesses in the United States, which translates to 33.2 million businesses.
                </P>
                <P>20. Next, the type of small entity described as a “small organization” is generally “any not-for-profit enterprise which is independently owned and operated and is not dominant in its field.” The Internal Revenue Service (IRS) uses a revenue benchmark of $50,000 or less to delineate its annual electronic filing requirements for small exempt organizations. (The IRS benchmark is similar to the population of less than 50,000 benchmark in 5 U.S.C. 601(5) that is used to define a small governmental jurisdiction. Therefore, the IRS benchmark has been used to estimate the number of small organizations in this small entity description. We note that the IRS data does not provide information on whether a small exempt organization is independently owned and operated or dominant in its field.) Nationwide, for tax year 2020, there were approximately 447,689 small exempt organizations in the U.S. reporting revenues of $50,000 or less according to the registration and tax data for exempt organizations available from the IRS. (The IRS Exempt Organization Business Master File (E.O. BMF) Extract provides information on all registered tax-exempt/non-profit organizations. The data utilized for purposes of this description was extracted from the IRS E.O. BMF data for businesses for the tax year 2020 with revenue less than or equal to $50,000 for Region 1—Northeast Area (58,577), Region 2—Mid-Atlantic and Great Lakes Areas (175,272), and Region 3—Gulf Coast and Pacific Coast Areas (213,840) that includes the continental U.S., Alaska, and Hawaii. This data does not include information for Puerto Rico.)</P>
                <P>21. Finally, the small entity described as a “small governmental jurisdiction” is defined generally as “governments of cities, counties, towns, townships, villages, school districts, or special districts, with a population of less than fifty thousand.” U.S. Census Bureau data from the 2017 Census of Governments indicate there were 90,075 local governmental jurisdictions consisting of general purpose governments and special purpose governments in the United States. (The Census of Governments survey is conducted every five (5) years compiling data for years ending with “2” and “7”.) (Local governmental jurisdictions are made up of general purpose governments (county, municipal and town or township) and special purpose governments (special districts and independent school districts).) Of this number, there were 36,931 general purpose governments (county, (there were 2,105 county governments with populations less than 50,000. This category does not include subcounty (municipal and township) governments) municipal, and town or township (there were 18,729 municipal and 16,097 town and township governments with populations less than 50,000)) with populations of less than 50,000 and 12,040 special purpose governments—independent school districts (there were 12,040 independent school districts with enrollment populations less than 50,000) with enrollment populations of less than 50,000. (While the special purpose governments category also includes local special district governments, the 2017 Census of Governments data does not provide data aggregated based on population size for the special purpose governments category. Therefore, only data from independent school districts is included in the special purpose governments category.) Accordingly, based on the 2017 U.S. Census of Governments data, we estimate that at least 48,971 entities fall into the category of “small governmental jurisdictions.” (This total is derived from the sum of the number of general purpose governments (county, municipal and town or township) with populations of less than 50,000 (36,931) and the number of special purpose governments—independent school districts with enrollment populations of less than 50,000 (12,040), from the 2017 Census of Governments—Organizations tbls. 5, 6 &amp; 10.)</P>
                <HD SOURCE="HD3">1. Internet Access Service Providers</HD>
                <P>
                    22. 
                    <E T="03">Wired Broadband Internet Access Service Providers (Wired ISPs).</E>
                     (Formerly included in the scope of the Internet Service Providers (Broadband), Wired Telecommunications Carriers and All Other Telecommunications small entity industry descriptions.) Providers of wired broadband internet access service include various types of providers except dial-up internet access providers. Wireline service that terminates at an end user location or mobile device and enables the end user to receive information from and/or send information to the internet at information transfer rates exceeding 200 kilobits per second (kbps) in at least one direction is classified as a broadband connection under the Commission's rules. Wired broadband internet services fall in the Wired Telecommunications Carriers industry. The SBA small business size standard for this industry classifies firms having 1,500 or fewer employees as small. U.S. Census Bureau data for 2017 show that there were 3,054 firms that operated in this industry for the entire year. Of this number, 2,964 firms operated with fewer than 250 employees. (The available U.S. Census Bureau data does not provide a more 
                    <PRTPAGE P="1865"/>
                    precise estimate of the number of firms that meet the SBA size standard.)
                </P>
                <P>
                    23. Additionally, according to Commission data on internet access services as of June 30, 2019, nationwide there were approximately 2,747 providers of connections over 200 kbps in at least one direction using various wireline technologies. (The technologies used by providers include aDSL, sDSL, Other Wireline, Cable Modem and FTTP). Other wireline includes: all copper-wire based technologies other than xDSL (such as Ethernet over copper, T-1/DS-1 and T3/DS-1) as well as power line technologies which are included in this category to maintain the confidentiality of the providers.) The Commission does not collect data on the number of employees for providers of these services, therefore, at this time we are not able to estimate the number of providers that would qualify as small under the SBA's small business size standard. However, in light of the general data on fixed technology service providers in the Commission's 
                    <E T="03">2022 Communications Marketplace Report,</E>
                     we believe that the majority of wireline internet access service providers can be considered small entities.
                </P>
                <P>
                    24. Internet Service Providers (Non-Broadband). Internet access service providers using client-supplied telecommunications connections (
                    <E T="03">e.g.,</E>
                     dial-up ISPs) as well as VoIP service providers using client-supplied telecommunications connections fall in the industry classification of All Other Telecommunications. The SBA small business size standard for this industry classifies firms with annual receipts of $35 million or less as small. For this industry, U.S. Census Bureau data for 2017 show that there were 1,079 firms in this industry that operated for the entire year. Of those firms, 1,039 had revenue of less than $25 million. (The available U.S. Census Bureau data does not provide a more precise estimate of the number of firms that meet the SBA size standard. We also note that according to the U.S. Census Bureau glossary, the terms receipts and revenues are used interchangeably.) Consequently, under the SBA size standard a majority of firms in this industry can be considered small.
                </P>
                <HD SOURCE="HD3">2. Wireline Providers</HD>
                <P>
                    25. 
                    <E T="03">Wired Telecommunications Carriers.</E>
                     The U.S. Census Bureau defines this industry as establishments primarily engaged in operating and/or providing access to transmission facilities and infrastructure that they own and/or lease for the transmission of voice, data, text, sound, and video using wired communications networks. Transmission facilities may be based on a single technology or a combination of technologies. Establishments in this industry use the wired telecommunications network facilities that they operate to provide a variety of services, such as wired telephony services, including VoIP services, wired (cable) audio and video programming distribution, and wired broadband internet services. By exception, establishments providing satellite television distribution services using facilities and infrastructure that they operate are included in this industry. Wired Telecommunications Carriers are also referred to as wireline carriers or fixed local service providers. (Fixed Local Service Providers include the following types of providers: Incumbent Local Exchange Carriers (ILECs), Competitive Access Providers (CAPs) and Competitive Local Exchange Carriers (CLECs), Cable/Coax CLECs, Interconnected VOIP Providers, Non-Interconnected VOIP Providers, Shared-Tenant Service Providers, Audio Bridge Service Providers, and Other Local Service Providers. Local Resellers fall into another U.S. Census Bureau industry group and therefore data for these providers is not included in this industry.)
                </P>
                <P>26. The SBA small business size standard for Wired Telecommunications Carriers classifies firms having 1,500 or fewer employees as small. U.S. Census Bureau data for 2017 show that there were 3,054 firms that operated in this industry for the entire year. Of this number, 2,964 firms operated with fewer than 250 employees. (The available U.S. Census Bureau data does not provide a more precise estimate of the number of firms that meet the SBA size standard.) Additionally, based on Commission data in the 2022 Universal Service Monitoring Report, as of December 31, 2021, there were 4,590 providers that reported they were engaged in the provision of fixed local services. Of these providers, the Commission estimates that 4,146 providers have 1,500 or fewer employees. Consequently, using the SBA's small business size standard, most of these providers can be considered small entities.</P>
                <P>
                    27. 
                    <E T="03">Local Exchange Carriers (LECs).</E>
                     Neither the Commission nor the SBA has developed a size standard for small businesses specifically applicable to local exchange services. Providers of these services include both incumbent and competitive local exchange service providers. Wired Telecommunications Carriers is the closest industry with an SBA small business size standard. Wired Telecommunications Carriers are also referred to as wireline carriers or fixed local service providers. (Fixed Local Exchange Service Providers include the following types of providers: Incumbent Local Exchange Carriers (ILECs), Competitive Access Providers (CAPs) and Competitive Local Exchange Carriers (CLECs), Cable/Coax CLECs, Interconnected VOIP Providers, Non-Interconnected VOIP Providers, Shared Tenant Service Providers, Audio Bridge Service Providers, Local Resellers, and Other Local Service Providers.) The SBA small business size standard for Wired Telecommunications Carriers classifies firms having 1,500 or fewer employees as small. U.S. Census Bureau data for 2017 show that there were 3,054 firms that operated in this industry for the entire year. Of this number, 2,964 firms operated with fewer than 250 employees. (The available U.S. Census Bureau data does not provide a more precise estimate of the number of firms that meet the SBA size standard.) Additionally, based on Commission data in the 2022 Universal Service Monitoring Report, as of December 31, 2021, there were 4,590 providers that reported they were fixed local exchange service providers. Of these providers, the Commission estimates that 4,146 providers have 1,500 or fewer employees. Consequently, using the SBA's small business size standard, most of these providers can be considered small entities.
                </P>
                <P>
                    28. 
                    <E T="03">Incumbent Local Exchange Carriers (Incumbent LECs).</E>
                     Neither the Commission nor the SBA have developed a small business size standard specifically for incumbent local exchange carriers. Wired Telecommunications Carriers is the closest industry with an SBA small business size standard. The SBA small business size standard for Wired Telecommunications Carriers classifies firms having 1,500 or fewer employees as small. U.S. Census Bureau data for 2017 show that there were 3,054 firms in this industry that operated for the entire year. Of this number, 2,964 firms operated with fewer than 250 employees. (The available U.S. Census Bureau data does not provide a more precise estimate of the number of firms that meet the SBA size standard.) Additionally, based on Commission data in the 2022 Universal Service Monitoring Report, as of December 31, 2021, there were 1,212 providers that reported they were incumbent local exchange service providers. Of these providers, the Commission estimates that 916 providers have 1,500 or fewer employees. Consequently, using the 
                    <PRTPAGE P="1866"/>
                    SBA's small business size standard, the Commission estimates that the majority of incumbent local exchange carriers can be considered small entities.
                </P>
                <P>
                    29. 
                    <E T="03">Competitive Local Exchange Carriers (LECs).</E>
                     Neither the Commission nor the SBA has developed a size standard for small businesses specifically applicable to local exchange services. Providers of these services include several types of competitive local exchange service providers. (Competitive Local Exchange Service Providers include the following types of providers: Competitive Access Providers (CAPs) and Competitive Local Exchange Carriers (CLECs), Cable/Coax CLECs, Interconnected VOIP Providers, Non-Interconnected VOIP Providers, Shared Tenant Service Providers, Audio Bridge Service Providers, Local Resellers, and Other Local Service Providers.) Wired Telecommunications Carriers is the closest industry with an SBA small business size standard. The SBA small business size standard for Wired Telecommunications Carriers classifies firms having 1,500 or fewer employees as small. U.S. Census Bureau data for 2017 show that there were 3,054 firms that operated in this industry for the entire year. Of this number, 2,964 firms operated with fewer than 250 employees. (The available U.S. Census Bureau data does not provide a more precise estimate of the number of firms that meet the SBA size standard.) Additionally, based on Commission data in the 2022 Universal Service Monitoring Report, as of December 31, 2021, there were 3,378 providers that reported they were competitive local exchange service providers. Of these providers, the Commission estimates that 3,230 providers have 1,500 or fewer employees. Consequently, using the SBA's small business size standard, most of these providers can be considered small entities.
                </P>
                <P>
                    30. 
                    <E T="03">Interexchange Carriers (IXCs).</E>
                     Neither the Commission nor the SBA has developed a small business size standard specifically for Interexchange Carriers. Wired Telecommunications Carriers is the closest industry with an SBA small business size standard. The SBA small business size standard for Wired Telecommunications Carriers classifies firms having 1,500 or fewer employees as small. U.S. Census Bureau data for 2017 show that there were 3,054 firms that operated in this industry for the entire year. Of this number, 2,964 firms operated with fewer than 250 employees. (The available U.S. Census Bureau data does not provide a more precise estimate of the number of firms that meet the SBA size standard.) Additionally, based on Commission data in the 2022 Universal Service Monitoring Report, as of December 31, 2021, there were 127 providers that reported they were engaged in the provision of interexchange services. Of these providers, the Commission estimates that 109 providers have 1,500 or fewer employees. Consequently, using the SBA's small business size standard, the Commission estimates that the majority of providers in this industry can be considered small entities.
                </P>
                <P>
                    31. 
                    <E T="03">Operator Service Providers (OSPs).</E>
                     Neither the Commission nor the SBA has developed a small business size standard specifically for operator service providers. The closest applicable industry with an SBA small business size standard is Wired Telecommunications Carriers. The SBA small business size standard classifies a business as small if it has 1,500 or fewer employees. U.S. Census Bureau data for 2017 show that there were 3,054 firms in this industry that operated for the entire year. Of this number, 2,964 firms operated with fewer than 250 employees. (The available U.S. Census Bureau data does not provide a more precise estimate of the number of firms that meet the SBA size standard.) Additionally, based on Commission data in the 2022 Universal Service Monitoring Report, as of December 31, 2021, there were 20 providers that reported they were engaged in the provision of operator services. Of these providers, the Commission estimates that all 20 providers have 1,500 or fewer employees. Consequently, using the SBA's small business size standard, all of these providers can be considered small entities.
                </P>
                <P>
                    32. 
                    <E T="03">Other Toll Carriers.</E>
                     Neither the Commission nor the SBA has developed a definition for small businesses specifically applicable to Other Toll Carriers. This category includes toll carriers that do not fall within the categories of interexchange carriers, operator service providers, prepaid calling card providers, satellite service carriers, or toll resellers. Wired Telecommunications Carriers is the closest industry with an SBA small business size standard. The SBA small business size standard for Wired Telecommunications Carriers classifies firms having 1,500 or fewer employees as small. U.S. Census Bureau data for 2017 show that there were 3,054 firms in this industry that operated for the entire year. Of this number, 2,964 firms operated with fewer than 250 employees. (The available U.S. Census Bureau data does not provide a more precise estimate of the number of firms that meet the SBA size standard.) Additionally, based on Commission data in the 2022 Universal Service Monitoring Report, as of December 31, 2021, there were 90 providers that reported they were engaged in the provision of other toll services. Of these providers, the Commission estimates that 87 providers have 1,500 or fewer employees. Consequently, using the SBA's small business size standard, most of these providers can be considered small entities.
                </P>
                <HD SOURCE="HD3">3. Wireless Providers—Fixed and Mobile</HD>
                <P>33. The broadband internet access service provider category covered by these new rules may cover multiple wireless firms and categories of regulated wireless services. (This includes, among others, the approximately 800 members of WISPA, including those entities who provide fixed wireless broadband service using unlicensed spectrum. We also consider the impact to these entities for the purposes of this FRFA, by including them under the “Wireless Providers—Fixed and Mobile” category.) Thus, to the extent the wireless services listed below are used by wireless firms for broadband internet access service, the actions may have an impact on those small businesses as set forth above and further below. In addition, for those services subject to auctions, we note that, as a general matter, the number of winning bidders that claim to qualify as small businesses at the close of an auction does not necessarily represent the number of small businesses currently in service. Also, the Commission does not generally track subsequent business size unless, in the context of assignments and transfers or reportable eligibility events, unjust enrichment issues are implicated.</P>
                <P>
                    34. 
                    <E T="03">Wireless Telecommunications Carriers (except Satellite).</E>
                     This industry comprises establishments engaged in operating and maintaining switching and transmission facilities to provide communications via the airwaves. Establishments in this industry have spectrum licenses and provide services using that spectrum, such as cellular services, paging services, wireless internet access, and wireless video services. The SBA size standard for this industry classifies a business as small if it has 1,500 or fewer employees. U.S. Census Bureau data for 2017 show that there were 2,893 firms in this industry that operated for the entire year. Of that number, 2,837 firms employed fewer than 250 employees. (The available U.S. Census Bureau data does not provide a more precise estimate of the number of firms that meet the SBA size standard.) 
                    <PRTPAGE P="1867"/>
                    Additionally, based on Commission data in the 2022 Universal Service Monitoring Report, as of December 31, 2021, there were 594 providers that reported they were engaged in the provision of wireless services. Of these providers, the Commission estimates that 511 providers have 1,500 or fewer employees. Consequently, using the SBA's small business size standard, most of these providers can be considered small entities.
                </P>
                <P>
                    35. 
                    <E T="03">Wireless Communications Services.</E>
                     Wireless Communications Services (WCS) can be used for a variety of fixed, mobile, radiolocation, and digital audio broadcasting satellite services. Wireless spectrum is made available and licensed for the provision of wireless communications services in several frequency bands subject to Part 27 of the Commission's rules. Wireless Telecommunications Carriers (
                    <E T="03">except</E>
                     Satellite) is the closest industry with an SBA small business size standard applicable to these services. The SBA small business size standard for this industry classifies a business as small if it has 1,500 or fewer employees. U.S. Census Bureau data for 2017 show that there were 2,893 firms that operated in this industry for the entire year. Of this number, 2,837 firms employed fewer than 250 employees. (The available U.S. Census Bureau data does not provide a more precise estimate of the number of firms that meet the SBA size standard.) Thus under the SBA size standard, the Commission estimates that a majority of licensees in this industry can be considered small.
                </P>
                <P>36. The Commission's small business size standards with respect to WCS involve eligibility for bidding credits and installment payments in the auction of licenses for the various frequency bands included in WCS. When bidding credits are adopted for the auction of licenses in WCS frequency bands, such credits may be available to several types of small businesses based average gross revenues (small, very small and entrepreneur) pursuant to the competitive bidding rules adopted in conjunction with the requirements for the auction and/or as identified in the designated entities section in Part 27 of the Commission's rules for the specific WCS frequency bands. (The “Designated entities” sections in subparts D-Q each contain the small business size standards adopted for the auction of the frequency band covered by that subpart.)</P>
                <P>37. In frequency bands where licenses were subject to auction, the Commission notes that as a general matter, the number of winning bidders that qualify as small businesses at the close of an auction does not necessarily represent the number of small businesses currently in service. Further, the Commission does not generally track subsequent business size unless, in the context of assignments or transfers, unjust enrichment issues are implicated. Additionally, since the Commission does not collect data on the number of employees for licensees providing these services, at this time we are not able to estimate the number of licensees with active licenses that would qualify as small under the SBA's small business size standard.</P>
                <P>
                    38. 
                    <E T="03">1670-1675 MHz Services.</E>
                     These wireless communications services can be used for fixed and mobile uses, except aeronautical mobile. Wireless Telecommunications Carriers (except Satellite) is the closest industry with an SBA small business size standard applicable to these services. The SBA size standard for this industry classifies a business as small if it has 1,500 or fewer employees. U.S. Census Bureau data for 2017 show that there were 2,893 firms that operated in this industry for the entire year. Of this number, 2,837 firms employed fewer than 250 employees. (The available U.S. Census Bureau data does not provide a more precise estimate of the number of firms that meet the SBA size standard.) Thus under the SBA size standard, the Commission estimates that a majority of licensees in this industry can be considered small.
                </P>
                <P>39. According to Commission data as of November 2021, there were three active licenses in this service. (Based on an FCC Universal Licensing System search on November 8, 2021, search parameters: Service Group = All, “Match only the following radio service(s)”, Radio Service = BC; Authorization Type = All; Status = Active. We note that the number of active licenses does not equate to the number of licensees. A licensee can have one or more licenses.) The Commission's small business size standards with respect to 1670-1675 MHz Services involve eligibility for bidding credits and installment payments in the auction of licenses for these services. For licenses in the 1670-1675 MHz service band, a “small business” is defined as an entity that, together with its affiliates and controlling interests, has average gross revenues not exceeding $40 million for the preceding three years, and a “very small business” is defined as an entity that, together with its affiliates and controlling interests, has had average annual gross revenues not exceeding $15 million for the preceding three years. The 1670-1675 MHz service band auction's winning bidder did not claim small business status.</P>
                <P>40. In frequency bands where licenses were subject to auction, the Commission notes that as a general matter, the number of winning bidders that qualify as small businesses at the close of an auction does not necessarily represent the number of small businesses currently in service. Further, the Commission does not generally track subsequent business size unless, in the context of assignments or transfers, unjust enrichment issues are implicated. Additionally, since the Commission does not collect data on the number of employees for licensees providing these services, at this time we are not able to estimate the number of licensees with active licenses that would qualify as small under the SBA's small business size standard.</P>
                <P>
                    41. 
                    <E T="03">Wireless Telephony.</E>
                     Wireless telephony includes cellular, personal communications services, and specialized mobile radio telephony carriers. The closest applicable industry with an SBA small business size standard is Wireless Telecommunications Carriers (except Satellite). The size standard for this industry under SBA rules is that a business is small if it has 1,500 or fewer employees. For this industry, U.S. Census Bureau data for 2017 show that there were 2,893 firms that operated for the entire year. Of this number, 2,837 firms employed fewer than 250 employees. (The available U.S. Census Bureau data does not provide a more precise estimate of the number of firms that meet the SBA size standard.) Additionally, based on Commission data in the 2022 Universal Service Monitoring Report, as of December 31, 2021, there were 331 providers that reported they were engaged in the provision of cellular, personal communications services, and specialized mobile radio services. Of these providers, the Commission estimates that 255 providers have 1,500 or fewer employees. Consequently, using the SBA's small business size standard, most of these providers can be considered small entities.
                </P>
                <P>
                    42. 
                    <E T="03">Broadband Personal Communications Service.</E>
                     The broadband personal communications services (PCS) spectrum encompasses services in the 1850-1910 and 1930-1990 MHz bands. The closest industry with a SBA small business size standard applicable to these services is Wireless Telecommunications Carriers (except Satellite). The SBA small business size standard for this industry classifies a business as small if it has 1,500 or fewer employees. U.S. Census Bureau data for 
                    <PRTPAGE P="1868"/>
                    2017 show that there were 2,893 firms that operated in this industry for the entire year. Of this number, 2,837 firms employed fewer than 250 employees. (The available U.S. Census Bureau data does not provide a more precise estimate of the number of firms that meet the SBA size standard.) Thus under the SBA size standard, the Commission estimates that a majority of licensees in this industry can be considered small.
                </P>
                <P>43. Based on Commission data as of November 2021, there were approximately 5,060 active licenses in the Broadband PCS service. (Based on a FCC Universal Licensing System search on November 16, 2021, search parameters: Service Group = All, “Match only the following radio service(s)”, Radio Service = CW; Authorization Type = All; Status = Active. We note that the number of active licenses does not equate to the number of licensees. A licensee can have one or more licenses.) The Commission's small business size standards with respect to Broadband PCS involve eligibility for bidding credits and installment payments in the auction of licenses for these services. In auctions for these licenses, the Commission defined “small business” as an entity that, together with its affiliates and controlling interests, has average gross revenues not exceeding $40 million for the preceding three years, and a “very small business” as an entity that, together with its affiliates and controlling interests, has had average annual gross revenues not exceeding $15 million for the preceding three years. Winning bidders claiming small business credits won Broadband PCS licenses in C, D, E, and F Blocks.</P>
                <P>44. In frequency bands where licenses were subject to auction, the Commission notes that as a general matter, the number of winning bidders that qualify as small businesses at the close of an auction does not necessarily represent the number of small businesses currently in service. Further, the Commission does not generally track subsequent business size unless, in the context of assignments or transfers, unjust enrichment issues are implicated. Additionally, since the Commission does not collect data on the number of employees for licensees providing these, at this time we are not able to estimate the number of licensees with active licenses that would qualify as small under the SBA's small business size standard.</P>
                <P>
                    45. 
                    <E T="03">Specialized Mobile Radio Licenses.</E>
                     Special Mobile Radio (SMR) licenses allow licensees to provide land mobile communications services (other than radiolocation services) in the 800 MHz and 900 MHz spectrum bands on a commercial basis including but not limited to services used for voice and data communications, paging, and facsimile services, to individuals, Federal Government entities, and other entities licensed under Part 90 of the Commission's rules. Wireless Telecommunications Carriers (except Satellite) is the closest industry with a SBA small business size standard applicable to these services. The SBA size standard for this industry classifies a business as small if it has 1,500 or fewer employees. For this industry, U.S. Census Bureau data for 2017 show that there were 2,893 firms in this industry that operated for the entire year. Of this number, 2,837 firms employed fewer than 250 employees. (The available U.S. Census Bureau data does not provide a more precise estimate of the number of firms that meet the SBA size standard.) Additionally, based on Commission data in the 2022 Universal Service Monitoring Report, as of December 31, 2021, there were 95 providers that reported they were of SMR (dispatch) providers. Of this number, the Commission estimates that all 95 providers have 1,500 or fewer employees. Consequently, using the SBA's small business size standard, these 119 SMR licensees can be considered small entities. (We note that there were also SMR providers reporting in the “Cellular/PCS/SMR” classification, therefore there are maybe additional SMR providers that have not been accounted for in the SMR (dispatch) classification.)
                </P>
                <P>46. Based on Commission data as of December 2021, there were 3,924 active SMR licenses. (Based on a FCC Universal Licensing System search on December 15, 2021, search parameters: Service Group = All, “Match radio services within this group”, Radio Service = SMR; Authorization Type = All; Status = Active. We note that the number of active licenses does not equate to the number of licensees. A licensee can have one or more licenses.) However, since the Commission does not collect data on the number of employees for licensees providing SMR services, at this time we are not able to estimate the number of licensees with active licenses that would qualify as small under the SBA's small business size standard. Nevertheless, for purposes of this analysis the Commission estimates that the majority of SMR licensees can be considered small entities using the SBA's small business size standard.</P>
                <P>
                    47. 
                    <E T="03">Lower 700 MHz Band Licenses.</E>
                     The lower 700 MHz band encompasses spectrum in the 698-746 MHz frequency bands. Permissible operations in these bands include flexible fixed, mobile, and broadcast uses, including mobile and other digital new broadcast operation; fixed and mobile wireless commercial services (including FDD- and TDD-based services); as well as fixed and mobile wireless uses for private, internal radio needs, two-way interactive, cellular, and mobile television broadcasting services. Wireless Telecommunications Carriers (
                    <E T="03">except</E>
                     Satellite) is the closest industry with a SBA small business size standard applicable to licenses providing services in these bands. The SBA small business size standard for this industry classifies a business as small if it has 1,500 or fewer employees. U.S. Census Bureau data for 2017 show that there were 2,893 firms that operated in this industry for the entire year. Of this number, 2,837 firms employed fewer than 250 employees. (The available U.S. Census Bureau data does not provide a more precise estimate of the number of firms that meet the SBA size standard.) Thus under the SBA size standard, the Commission estimates that a majority of licensees in this industry can be considered small.
                </P>
                <P>
                    48. According to Commission data as of December 2021, there were approximately 2,824 active Lower 700 MHz Band licenses. (Based on a FCC Universal Licensing System search on December 14, 2021, search parameters: Service Group = All, “Match only the following radio service(s)”, Radio Service = WY, WZ; Authorization Type = All; Status = Active. We note that the number of active licenses does not equate to the number of licensees. A licensee can have one or more licenses.) The Commission's small business size standards with respect to Lower 700 MHz Band licensees involve eligibility for bidding credits and installment payments in the auction of licenses. For auctions of Lower 700 MHz Band licenses the Commission adopted criteria for three groups of small businesses. A very small business was defined as an entity that, together with its affiliates and controlling interests, has average annual gross revenues not exceeding $15 million for the preceding three years, a small business was defined as an entity that, together with its affiliates and controlling interests, has average gross revenues not exceeding $40 million for the preceding three years, and an entrepreneur was defined as an entity that, together with its affiliates and controlling interests, has average gross revenues not exceeding $3 million for the preceding 
                    <PRTPAGE P="1869"/>
                    three years. In auctions for Lower 700 MHz Band licenses seventy-two winning bidders claiming a small business classification won 329 licenses, twenty-six winning bidders claiming a small business classification won 214 licenses, and three winning bidders claiming a small business classification won all five auctioned licenses.
                </P>
                <P>49. In frequency bands where licenses were subject to auction, the Commission notes that as a general matter, the number of winning bidders that qualify as small businesses at the close of an auction does not necessarily represent the number of small businesses currently in service. Further, the Commission does not generally track subsequent business size unless, in the context of assignments or transfers, unjust enrichment issues are implicated. Additionally, since the Commission does not collect data on the number of employees for licensees providing these services, at this time we are not able to estimate the number of licensees with active licenses that would qualify as small under the SBA's small business size standard.</P>
                <P>
                    50. 
                    <E T="03">Upper 700 MHz Band Licenses.</E>
                     The upper 700 MHz band encompasses spectrum in the 746-806 MHz bands. Upper 700 MHz D Block licenses are nationwide licenses associated with the 758-763 MHz and 788-793 MHz bands. Permissible operations in these bands include flexible fixed, mobile, and broadcast uses, including mobile and other digital new broadcast operation; fixed and mobile wireless commercial services (including FDD- and TDD-based services); as well as fixed and mobile wireless uses for private, internal radio needs, two-way interactive, cellular, and mobile television broadcasting services. (We note that in Auction 73, Upper 700 MHz Band C and D Blocks as well as Lower 700 MHz Band A, B, and E Blocks were auctioned.) Wireless Telecommunications Carriers (
                    <E T="03">except</E>
                     Satellite) is the closest industry with a SBA small business size standard applicable to licenses providing services in these bands. The SBA small business size standard for this industry classifies a business as small if it has 1,500 or fewer employees. U.S. Census Bureau data for 2017 show that there were 2,893 firms that operated in this industry for the entire year. Of that number, 2,837 firms employed fewer than 250 employees. (The available U.S. Census Bureau data does not provide a more precise estimate of the number of firms that meet the SBA size standard.) Thus, under the SBA size standard, the Commission estimates that a majority of licensees in this industry can be considered small.
                </P>
                <P>51. According to Commission data as of December 2021, there were approximately 152 active Upper 700 MHz Band licenses. (Based on a FCC Universal Licensing System search on December 14, 2021, search parameters: Service Group = All, “Match only the following radio service(s)”, Radio Service = WP, WU; Authorization Type = All; Status = Active. We note that the number of active licenses does not equate to the number of licensees. A licensee can have one or more licenses.) The Commission's small business size standards with respect to Upper 700 MHz Band licensees involve eligibility for bidding credits and installment payments in the auction of licenses. For the auction of these licenses, the Commission defined a “small business” as an entity that, together with its affiliates and controlling principals, has average gross revenues not exceeding $40 million for the preceding three years, and a “very small business” an entity that, together with its affiliates and controlling principals, has average gross revenues that are not more than $15 million for the preceding three years. Pursuant to these definitions, three winning bidders claiming very small business status won five of the twelve available licenses.</P>
                <P>
                    52. 
                    <E T="03">Air-Ground Radiotelephone Service.</E>
                     Air-Ground Radiotelephone Service is a wireless service in which licensees are authorized to offer and provide radio telecommunications service for hire to subscribers in aircraft. A licensee may provide any type of air-ground service (
                    <E T="03">i.e.,</E>
                     voice telephony, broadband internet, data, etc.) to aircraft of any type, and serve any or all aviation markets (commercial, government, and general). A licensee must provide service to aircraft and may not provide ancillary land mobile or fixed services in the 800 MHz air-ground spectrum.
                </P>
                <P>
                    53. The closest industry with an SBA small business size standard applicable to these services is Wireless Telecommunications Carriers (
                    <E T="03">except</E>
                     Satellite). The SBA small business size standard for this industry classifies a business as small if it has 1,500 or fewer employees. U.S. Census Bureau data for 2017 show that there were 2,893 firms that operated in this industry for the entire year. Of this number, 2,837 firms employed fewer than 250 employees. (The available U.S. Census Bureau data does not provide a more precise estimate of the number of firms that meet the SBA size standard.) Thus under the SBA size standard, the Commission estimates that a majority of licensees in this industry can be considered small.
                </P>
                <P>54. Based on Commission data as of December 2021, there were approximately four licensees with 110 active licenses in the Air-Ground Radiotelephone Service. (Based on a FCC Universal Licensing System search on December 20, 2021, search parameters: Service Group = All, “Match only the following radio service(s)”, Radio Service = CG, CJ; Authorization Type = All; Status = Active. We note that the number of active licenses does not equate to the number of licensees. A licensee can have one or more licenses.) The Commission's small business size standards with respect to Air-Ground Radiotelephone Service involve eligibility for bidding credits and installment payments in the auction of licenses. For purposes of auctions, the Commission defined “small business” as an entity that, together with its affiliates and controlling interests, has average gross revenues not exceeding $40 million for the preceding three years, and a “very small business” as an entity that, together with its affiliates and controlling interests, has had average annual gross revenues not exceeding $15 million for the preceding three years. In the auction of Air-Ground Radiotelephone Service licenses in the 800 MHz band, neither of the two winning bidders claimed small business status.</P>
                <P>55. In frequency bands where licenses were subject to auction, the Commission notes that as a general matter, the number of winning bidders that qualify as small businesses at the close of an auction does not necessarily represent the number of small businesses currently in service. Further, the Commission does not generally track subsequent business size unless, in the context of assignments or transfers, unjust enrichment issues are implicated. Additionally, the Commission does not collect data on the number of employees for licensees providing these services therefore, at this time we are not able to estimate the number of licensees with active licenses that would qualify as small under the SBA's small business size standard.</P>
                <P>
                    56. 
                    <E T="03">3650-3700 MHz Band.</E>
                     Wireless broadband service licensing in the 3650-3700 MHz band provides for nationwide, non-exclusive licensing of terrestrial operations, utilizing contention-based technologies, in the 3650 MHz band (
                    <E T="03">i.e.,</E>
                     3650-3700 MHz). Licensees are permitted to provide services on a non-common carrier and/or on a common carrier basis. Wireless broadband services in the 3650-3700 
                    <PRTPAGE P="1870"/>
                    MHz band fall in the Wireless Telecommunications Carriers (
                    <E T="03">except</E>
                     Satellite) industry with an SBA small business size standard that classifies a business as small if it has 1,500 or fewer employees. U.S. Census Bureau data for 2017 show that there were 2,893 firms that operated in this industry for the entire year. Of this number, 2,837 firms employed fewer than 250 employees. (The available U.S. Census Bureau data does not provide a more precise estimate of the number of firms that meet the SBA size standard.) Thus under the SBA size standard, the Commission estimates that a majority of licensees in this industry can be considered small.
                </P>
                <P>57. The Commission has not developed a small business size standard applicable to 3650-3700 MHz band licensees. Based on the licenses that have been granted, however, we estimate that the majority of licensees in this service are small internet Access Service Providers (ISPs). As of November 2021, Commission data shows that there were 902 active licenses in the 3650-3700 MHz band. (Based on an FCC Universal Licensing System search on November 19, 2021, search parameters: Service Group = All, “Match only the following radio service(s)”, Radio Service = NN; Authorization Type =All; Status = Active. We note that the number of active licenses does not equate to the number of licensees. A licensee can have one or more licenses.) However, since the Commission does not collect data on the number of employees for licensees providing these services, at this time we are not able to estimate the number of licensees with active licenses that would qualify as small under the SBA's small business size standard.</P>
                <P>
                    58. 
                    <E T="03">Fixed Microwave Services.</E>
                     Fixed microwave services include common carrier, private-operational fixed, and broadcast auxiliary radio services. (Auxiliary Microwave Service is governed by part 74 of Title 47 of the Commission's Rules. Available to licensees of broadcast stations and to broadcast and cable network entities, broadcast auxiliary microwave stations are used for relaying broadcast television signals from the studio to the transmitter, or between two points such as a main studio and an auxiliary studio. The service also includes mobile TV pickups, which relay signals from a remote location back to the studio.) They also include the Upper Microwave Flexible Use Service (UMFUS), Millimeter Wave Service (70/80/90 GHz), Local Multipoint Distribution Service (LMDS), the Digital Electronic Message Service (DEMS), 24 GHz Service, Multiple Address Systems (MAS), and Multichannel Video Distribution and Data Service (MVDDS), where in some bands licensees can choose between common carrier and non-common carrier status. Wireless Telecommunications Carriers (
                    <E T="03">except</E>
                     Satellite) is the closest industry with a SBA small business size standard applicable to these services. The SBA small size standard for this industry classifies a business as small if it has 1,500 or fewer employees. U.S. Census Bureau data for 2017 show that there were 2,893 firms that operated in this industry for the entire year. Of this number, 2,837 firms employed fewer than 250 employees. (The available U.S. Census Bureau data does not provide a more precise estimate of the number of firms that meet the SBA size standard.) Thus under the SBA size standard, the Commission estimates that a majority of fixed microwave service licensees can be considered small.
                </P>
                <P>59. The Commission's small business size standards with respect to fixed microwave services involve eligibility for bidding credits and installment payments in the auction of licenses for the various frequency bands included in fixed microwave services. When bidding credits are adopted for the auction of licenses in fixed microwave services frequency bands, such credits may be available to several types of small businesses based average gross revenues (small, very small and entrepreneur) pursuant to the competitive bidding rules adopted in conjunction with the requirements for the auction and/or as identified in part 101 of the Commission's rules for the specific fixed microwave services frequency bands.</P>
                <P>60. In frequency bands where licenses were subject to auction, the Commission notes that as a general matter, the number of winning bidders that qualify as small businesses at the close of an auction does not necessarily represent the number of small businesses currently in service. Further, the Commission does not generally track subsequent business size unless, in the context of assignments or transfers, unjust enrichment issues are implicated. Additionally, since the Commission does not collect data on the number of employees for licensees providing these services, at this time we are not able to estimate the number of licensees with active licenses that would qualify as small under the SBA's small business size standard.</P>
                <P>
                    61. 
                    <E T="03">Broadband Radio Service and Educational Broadband Service.</E>
                     Broadband Radio Service systems, previously referred to as Multipoint Distribution Service (MDS) and Multichannel Multipoint Distribution Service (MMDS) systems, and “wireless cable,” transmit video programming to subscribers and provide two-way high speed data operations using the microwave frequencies of the Broadband Radio Service (BRS) and Educational Broadband Service (EBS) (previously referred to as the Instructional Television Fixed Service (ITFS)). (The use of the term “wireless cable” does not imply that it constitutes cable television for statutory or regulatory purposes.) Wireless cable operators that use spectrum in the BRS often supplemented with leased channels from the EBS, provide a competitive alternative to wired cable and other multichannel video programming distributors. Wireless cable programming to subscribers resembles cable television, but instead of coaxial cable, wireless cable uses microwave channels. (Generally, a wireless cable system may be described as a microwave station transmitting on a combination of BRS and EBS channels to numerous receivers with antennas, such as single-family residences, apartment complexes, hotels, educational institutions, business entities and governmental offices. The range of the transmission depends upon the transmitter power, the type of receiving antenna and the existence of a line-of-sight path between the transmitter or signal booster and the receiving antenna.)
                </P>
                <P>
                    62. In light of the use of wireless frequencies by BRS and EBS services, the closest industry with a SBA small business size standard applicable to these services is Wireless Telecommunications Carriers (
                    <E T="03">except</E>
                     Satellite). The SBA small business size standard for this industry classifies a business as small if it has 1,500 or fewer employees. U.S. Census Bureau data for 2017 show that there were 2,893 firms that operated in this industry for the entire year. Of this number, 2,837 firms employed fewer than 250 employees. (The available U.S. Census Bureau data does not provide a more precise estimate of the number of firms that meet the SBA size standard.) Thus under the SBA size standard, the Commission estimates that a majority of licensees in this industry can be considered small.
                </P>
                <P>
                    63. According to Commission data as December 2021, there were approximately 5,869 active BRS and EBS licenses. (Based on an FCC Universal Licensing System search on December 10, 2021, search parameters: Service Group = All, “Match only the following radio service(s)”, Radio 
                    <PRTPAGE P="1871"/>
                    Service = BR, ED; Authorization Type = All; Status = Active. We note that the number of active licenses does not equate to the number of licensees. A licensee can have one or more licenses.) The Commission's small business size standards with respect to BRS involves eligibility for bidding credits and installment payments in the auction of licenses for these services. For the auction of BRS licenses, the Commission adopted criteria for three groups of small businesses. A very small business is an entity that, together with its affiliates and controlling interests, has average annual gross revenues exceed $3 million and did not exceed $15 million for the preceding three years, a small business is an entity that, together with its affiliates and controlling interests, has average gross revenues exceed $15 million and did not exceed $40 million for the preceding three years, and an entrepreneur is an entity that, together with its affiliates and controlling interests, has average gross revenues not exceeding $3 million for the preceding three years. Of the ten winning bidders for BRS licenses, two bidders claiming the small business status won 4 licenses, one bidder claiming the very small business status won three licenses and two bidders claiming entrepreneur status won six licenses. One of the winning bidders claiming a small business status classification in the BRS license auction has an active license as of December 2021. (We note that the number of active licenses does not equate to the number of licensees. A licensee can have one or more licenses.) We note that the number of active licenses does not equate to the number of licensees. A licensee can have one or more licenses.
                </P>
                <P>64. The Commission's small business size standards for EBS define a small business as an entity that, together with its affiliates, its controlling interests and the affiliates of its controlling interests, has average gross revenues that are not more than $55 million for the preceding five (5) years, and a very small business is an entity that, together with its affiliates, its controlling interests and the affiliates of its controlling interests, has average gross revenues that are not more than $20 million for the preceding five (5) years. In frequency bands where licenses were subject to auction, the Commission notes that as a general matter, the number of winning bidders that qualify as small businesses at the close of an auction does not necessarily represent the number of small businesses currently in service. Further, the Commission does not generally track subsequent business size unless, in the context of assignments or transfers, unjust enrichment issues are implicated. Additionally, since the Commission does not collect data on the number of employees for licensees providing these services, at this time we are not able to estimate the number of licensees with active licenses that would qualify as small under the SBA's small business size standard.</P>
                <HD SOURCE="HD3">4. Satellite Service Providers</HD>
                <P>
                    65. 
                    <E T="03">Satellite Telecommunications.</E>
                     This industry comprises firms “primarily engaged in providing telecommunications services to other establishments in the telecommunications and broadcasting industries by forwarding and receiving communications signals via a system of satellites or reselling satellite telecommunications.” Satellite telecommunications service providers include satellite and earth station operators. The SBA small business size standard for this industry classifies a business with $35 million or less in annual receipts as small. U.S. Census Bureau data for 2017 show that 275 firms in this industry operated for the entire year. Of this number, 242 firms had revenue of less than $25 million. (The available U.S. Census Bureau data does not provide a more precise estimate of the number of firms that meet the SBA size standard. We also note that according to the U.S. Census Bureau glossary, the terms receipts and revenues are used interchangeably.) Additionally, based on Commission data in the 2022 Universal Service Monitoring Report, as of December 31, 2021, there were 65 providers that reported they were engaged in the provision of satellite telecommunications services. Of these providers, the Commission estimates that approximately 42 providers have 1,500 or fewer employees. Consequently, using the SBA's small business size standard, a little more than half of these providers can be considered small entities.
                </P>
                <P>
                    66. 
                    <E T="03">All Other Telecommunications.</E>
                     This industry is comprised of establishments primarily engaged in providing specialized telecommunications services, such as satellite tracking, communications telemetry, and radar station operation. This industry also includes establishments primarily engaged in providing satellite terminal stations and associated facilities connected with one or more terrestrial systems and capable of transmitting telecommunications to, and receiving telecommunications from, satellite systems. Providers of internet services (
                    <E T="03">e.g.</E>
                     dial-up ISPs) or voice over internet protocol (VoIP) services, via client-supplied telecommunications connections are also included in this industry. The SBA small business size standard for this industry classifies firms with annual receipts of $35 million or less as small. U.S. Census Bureau data for 2017 show that there were 1,079 firms in this industry that operated for the entire year. Of those firms, 1,039 had revenue of less than $25 million. (The available U.S. Census Bureau data does not provide a more precise estimate of the number of firms that meet the SBA size standard. We also note that according to the U.S. Census Bureau glossary, the terms receipts and revenues are used interchangeably.) Based on this data, the Commission estimates that the majority of “All Other Telecommunications” firms can be considered small.
                </P>
                <HD SOURCE="HD3">5. Cable Service Providers</HD>
                <P>67. Because section 706 of the Act requires us to monitor the deployment of broadband using any technology, we anticipate that some broadband service providers may not provide telephone service. Accordingly, we describe below other types of firms that may provide broadband services, including cable companies, MDS providers, and utilities, among others.</P>
                <P>
                    68. 
                    <E T="03">Cable and Other Subscription Programming.</E>
                     The U.S. Census Bureau defines this industry as establishments primarily engaged in operating studios and facilities for the broadcasting of programs on a subscription or fee basis. The broadcast programming is typically narrowcast in nature (
                    <E T="03">e.g.,</E>
                     limited format, such as news, sports, education, or youth-oriented). These establishments produce programming in their own facilities or acquire programming from external sources. The programming material is usually delivered to a third party, such as cable systems or direct-to-home satellite systems, for transmission to viewers. The SBA small business size standard for this industry classifies firms with annual receipts less than $41.5 million as small. Based on U.S. Census Bureau data for 2017, 378 firms operated in this industry during that year. (The U.S. Census Bureau withheld publication of the number of firms that operated for the entire year to avoid disclosing data for individual companies (see Cell Notes for this category).) Of that number, 149 firms operated with revenue of less than $25 million a year and 44 firms operated with revenue of $25 million or more. (The available U.S. Census Bureau data does not provide a more precise estimate of the number of firms that meet the SBA size standard. We note 
                    <PRTPAGE P="1872"/>
                    that the U.S. Census Bureau withheld publication of the number of firms that operated with sales/value of shipments/revenue in all categories of revenue less than $500,000 to avoid disclosing data for individual companies (see Cell Notes for the sales/value of shipments/revenue in these categories). Therefore, the number of firms with revenue that meet the SBA size standard would be higher than noted herein. We also note that according to the U.S. Census Bureau glossary, the terms receipts and revenues are used interchangeably.) Based on this data, the Commission estimates that a majority of firms in this industry are small.
                </P>
                <P>
                    69. 
                    <E T="03">Cable Companies and Systems (Rate Regulation).</E>
                     The Commission has developed its own small business size standard for the purpose of cable rate regulation. Under the Commission's rules, a “small cable company” is one serving 400,000 or fewer subscribers nationwide. Based on industry data, there are about 420 cable companies in the U.S. Of these, only seven have more than 400,000 subscribers. In addition, under the Commission's rules, a “small system” is a cable system serving 15,000 or fewer subscribers. Based on industry data, there are about 4,139 cable systems (headends) in the U.S. Of these, about 639 have more than 15,000 subscribers. Accordingly, the Commission estimates that the majority of cable companies and cable systems are small.
                </P>
                <P>
                    70. 
                    <E T="03">Cable System Operators (Telecom Act Standard).</E>
                     The Communications Act of 1934, as amended, contains a size standard for a “small cable operator,” which is “a cable operator that, directly or through an affiliate, serves in the aggregate fewer than one percent of all subscribers in the United States and is not affiliated with any entity or entities whose gross annual revenues in the aggregate exceed $250,000,000.” For purposes of the Telecom Act Standard, the Commission determined that a cable system operator that serves fewer than 498,000 subscribers, either directly or through affiliates, will meet the definition of a small cable operator. (In the 
                    <E T="03">2023 Subscriber Threshold Public Notice,</E>
                     the Commission determined that there were approximately 49.8 million cable subscribers in the United States at that time using the most reliable source publicly available. This threshold will remain in effect until the Commission issues a superseding Public Notice.) Based on industry data, only six cable system operators have more than 498,000 subscribers. Accordingly, the Commission estimates that the majority of cable system operators are small under this size standard. We note however, that the Commission neither requests nor collects information on whether cable system operators are affiliated with entities whose gross annual revenues exceed $250 million. (The Commission does receive such information on a case-by-case basis if a cable operator appeals a local franchise authority's finding that the operator does not qualify as a small cable operator pursuant to § 76.901(e) of the Commission's rules.) Therefore, we are unable at this time to estimate with greater precision the number of cable system operators that would qualify as small cable operators under the definition in the Communications Act.
                </P>
                <HD SOURCE="HD3">6. All Other Telecommunications</HD>
                <P>
                    71. 
                    <E T="03">Electric Power Generators, Transmitters, and Distributors.</E>
                     The U.S. Census Bureau defines the utilities sector industry as comprised of “establishments, primarily engaged in generating, transmitting, and/or distributing electric power. Establishments in this industry group may perform one or more of the following activities: (1) operate generation facilities that produce electric energy; (2) operate transmission systems that convey the electricity from the generation facility to the distribution system; and (3) operate distribution systems that convey electric power received from the generation facility or the transmission system to the final consumer.” This industry group is categorized based on fuel source and includes Hydroelectric Power Generation, Fossil Fuel Electric Power Generation, Nuclear Electric Power Generation, Solar Electric Power Generation, Wind Electric Power Generation, Geothermal Electric Power Generation, Biomass Electric Power Generation, Other Electric Power Generation, Electric Bulk Power Transmission and Control and Electric Power Distribution.
                </P>
                <P>72. The SBA has established a small business size standard for each of these groups based on the number of employees which ranges from having fewer than 250 employees to having fewer than 1,000 employees. U.S. Census Bureau data for 2017 indicate that for the Electric Power Generation, Transmission and Distribution industry there were 1,693 firms that operated in this industry for the entire year. Of this number, 1,552 firms had less than 250 employees. (The available U.S. Census Bureau data does not provide a more precise estimate of the number of firms that meet the SBA size standard.) Based on this data and the associated SBA size standards, the majority of firms in this industry can be considered small entities.</P>
                <HD SOURCE="HD2">D. Description of Projected Reporting, Recordkeeping, and Other Compliance Requirements for Small Entities</HD>
                <P>
                    73. In the 
                    <E T="03">FNPRM,</E>
                     we seek comment on ways to further facilitate the approval process for pole attachment applications and make-ready to enable quicker broadband deployment. Some of these proposals may impose new or additional reporting or recordkeeping and/or other compliance obligations on small entities. Specifically, we seek comment on a proposal that utilities should have an additional 90 days for make-ready for requests exceeding 3,000 poles or 5 percent of the utility's poles in a state. We also seek comment on whether NCTA's proposal to add additional time to the existing application timelines for larger orders and prohibit utilities from limiting the size of an application or the number of poles included in an application, to avoid these timelines, will facilitate the pole attachment process for such orders. Additionally, we seek comment on whether the Commission should create additional make-ready timeline tiers in its rules to differentiate between attachment applications that could range from requesting access to thousands of poles to tens or even hundreds of thousands of poles. We also consider whether to require that a utility notify an attacher 15 days after receiving a complete application that it cannot conduct the survey within the required 45-day period, making self-help available for the estimate process, which is not contemplated under current Commission rules. We also seek comment on whether attachers face any obstacles from utilities when seeking to invoke self-help options, which allows attachers to choose their own contractors for one-touch make-ready and for self-help when the utility fails to meet the Commission's deadlines. This information will help to inform whether potential rule changes are necessary. At this time, the Commission cannot quantify the cost of compliance for small entities with the approaches discussed in the 
                    <E T="03">FNPRM,</E>
                     or whether any compliance requirements will require small entities to hire professionals; however, the Commission requests information on the costs and benefits of the approaches discussed, such as the availability of qualified contractors and other workforce constraints that may impact the speed and cost of deployment for utilities and attachers.
                    <PRTPAGE P="1873"/>
                </P>
                <HD SOURCE="HD2">E. Steps Taken To Minimize the Significant Economic Impact on Small Entities, and Significant Alternatives Considered</HD>
                <P>74. The RFA requires an agency to describe any significant, specifically small business, alternatives that it has considered in reaching its proposed approach, which may include the following four alternatives (among others): “(1) the establishment of differing compliance or reporting requirements or timetables that take into account the resources available to small entities; (2) the clarification, consolidation, or simplification of compliance and reporting requirements under the rule for such small entities; (3) the use of performance rather than design standards; and (4) an exemption from coverage of the rule, or any part thereof, for such small entities.”</P>
                <P>
                    75. The 
                    <E T="03">FNPRM</E>
                     seeks comment on whether the Commission should revise its rules to further facilitate the approval process for pole attachment applications and make-ready to enable quicker broadband deployment, including a tentative conclusion that utilities should have an additional 90 days for make-ready for requests exceeding 3,000 poles or 5 percent of the utility's poles in a state. The Commission's objective in requesting this information is to determine whether it can and should establish clear standards for when and how attachers and utilities must share the costs of a pole replacement precipitated by a new attachment request. Among the alternatives considered in the 
                    <E T="03">FNPRM</E>
                     is whether the Commission should allow additional time for the existing larger order timelines where our current rules require that utilities negotiate timing in good faith. We seek comment on whether requiring that the utility notify an attacher 15 days after receiving a complete application that it cannot conduct the survey within the required 45-day period would allow the attacher to elect self-help for the survey sooner. In the alternative, we inquire whether such expansion of time is reasonable for utilities if numerous permits are submitted around the same time or contractor workload is heavy. We also consider whether attachers are choosing to find their own contractors for one-touch make-ready and for self-help when utilities fail to meet the Commission's deadlines. Similarly, we request information on whether or not utilities designate an available contractor if it properly exercises its discretion to disqualify one chosen by an attacher. We also seek comment on how the Commission can help resolve situations where labor shortages may hinder utilities from meeting deadlines to respond to attachers. The Commission also seeks comment on and will consider the relative costs and benefits of any such revisions to its rules. Information submitted in response to these requests for comment will enable the Commission to evaluate the impact that revising its pole attachment rules would have on smaller entities.
                </P>
                <HD SOURCE="HD2">F. Federal Rules That May Duplicate, Overlap, or Conflict With the Proposed Rules</HD>
                <P>76. None.</P>
                <HD SOURCE="HD1">V. Procedural Matters</HD>
                <P>
                    77. 
                    <E T="03">Initial Regulatory Flexibility Analysis.</E>
                     As required by the Regulatory Flexibility Act, the Commission has prepared an Initial Regulatory Flexibility Analysis (IRFA) of the possible significant economic impact on small entities of the policies and rules addressed in this FNPRM. Written public comments are requested on the IRFA. Comments must be filed by the deadlines for comments on the FNPRM indicated on the first page of this document and must have a separate and distinct heading designating them as responses to the IRFA. The Commission's Consumer and Governmental Affairs Bureau, Reference Information Center, will send a copy of this FNPRM, including the IRFA, to the Chief Counsel for Advocacy of the SBA.
                </P>
                <P>
                    78. 
                    <E T="03">Paperwork Reduction Act.</E>
                     The FNPRM contains proposed new information collection requirements. The Commission, as part of its continuing effort to reduce paperwork burdens, invites the general public and OMB to comment on the information collection requirements contained in this document, as required by the Paperwork Reduction Act of 1995, Public Law 104-13. In addition, pursuant to the Small Business Paperwork Relief Act of 2002, Public Law 107-198, 
                    <E T="03">see</E>
                     44 U.S.C. 3506(c)(4), we seek specific comment on how we might further reduce the information collection burden for small business concerns with fewer than 25 employees.
                </P>
                <P>
                    79. 
                    <E T="03">Ex Parte Presentations—Permit-But-Disclose.</E>
                     The proceeding this FNPRM initiates shall be treated as a “permit-but-disclose” proceeding in accordance with the Commission's 
                    <E T="03">ex parte</E>
                     rules. Persons making 
                    <E T="03">ex parte</E>
                     presentations must file a copy of any written presentation or a memorandum summarizing any oral presentation within two business days after the presentation (unless a different deadline applicable to the Sunshine period applies). Persons making oral 
                    <E T="03">ex parte</E>
                     presentations are reminded that memoranda summarizing the presentation must (1) list all persons attending or otherwise participating in the meeting at which the 
                    <E T="03">ex parte</E>
                     presentation was made, and (2) summarize all data presented and arguments made during the presentation. If the presentation consisted in whole or in part of the presentation of data or arguments already reflected in the presenter's written comments, memoranda or other filings in the proceeding, the presenter may provide citations to such data or arguments in his or her prior comments, memoranda, or other filings (specifying the relevant page and/or paragraph numbers where such data or arguments can be found) in lieu of summarizing them in the memorandum. Documents shown or given to Commission staff during 
                    <E T="03">ex parte</E>
                     meetings are deemed to be written 
                    <E T="03">ex parte</E>
                     presentations and must be filed consistent with § 1.1206(b) of the Commission's rules. In proceedings governed by § 1.49(f) of the Commission's rules or for which the Commission has made available a method of electronic filing, written 
                    <E T="03">ex parte</E>
                     presentations and memoranda summarizing oral 
                    <E T="03">ex parte</E>
                     presentations, and all attachments thereto, must be filed through the electronic comment filing system available for that proceeding, and must be filed in their native format (
                    <E T="03">e.g.,</E>
                     .doc, .xml, .ppt, searchable .pdf). Participants in this proceeding should familiarize themselves with the Commission's 
                    <E T="03">ex parte</E>
                     rules.
                </P>
                <HD SOURCE="HD1">VI. Ordering Clauses</HD>
                <P>
                    80. Accordingly, 
                    <E T="03">it is ordered</E>
                    , pursuant to sections 4(i), 4(j), 201, 202, 217, 227, 227b, 251(e), 303(r), and 403 of the Communications Act of 1934, as amended, 47 U.S.C. 154(i), 154(j), 201, 202, 217, 227, 227b, 251(e), 303(r), 403, that this Third Further Notice of Proposed Rulemaking 
                    <E T="03">is adopted</E>
                    .
                </P>
                <P>
                    81. 
                    <E T="03">It is further ordered</E>
                     that the Commission's Consumer and Governmental Affairs Bureau, Reference information Center, 
                    <E T="03">shall send</E>
                     a copy of this Third Further Notice of Proposed Rulemaking, including the Initial Regulatory Flexibility Analysis (IRFA), to the Chief Counsel for Advocacy of the Small Business Administration.
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 47 CFR Part 1</HD>
                    <P>Administrative practice and procedure.</P>
                </LSTSUB>
                <SIG>
                    <PRTPAGE P="1874"/>
                    <FP>Federal Communications Commission.</FP>
                    <NAME>Katura Jackson,</NAME>
                    <TITLE>Federal Register Liaison Officer.</TITLE>
                </SIG>
                <HD SOURCE="HD1">Proposed Rules</HD>
                <P>The Federal Communications Commission proposes to amend part 1 of Title 47 of the Code of Federal Regulations as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 1—PRACTICE AND PROCEDURE</HD>
                </PART>
                <AMDPAR>1. The authority citation for part 1 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>47 U.S.C. chs. 2, 5, 9, 13; 28 U.S.C. 2461.</P>
                </AUTH>
                <AMDPAR>2. Amend § 1.1411 by revising paragraph (g)(4) to read as follows:</AMDPAR>
                <SECTION>
                    <SECTNO>§ 1.1411</SECTNO>
                    <SUBJECT>Timeline for access to utility poles.</SUBJECT>
                    <STARS/>
                    <P>(g) * * *</P>
                    <P>(4) A utility may add 90 days to the make-ready periods described in paragraph (e) of this section to all requests for attachment larger than the lesser of 3000 poles or 5 percent of the utility's poles in a state.</P>
                    <STARS/>
                </SECTION>
            </SUPLINF>
            <FRDOC>[FR Doc. 2023-28763 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </PRORULE>
    </PRORULES>
    <VOL>89</VOL>
    <NO>8</NO>
    <DATE>Thursday, January 11, 2024</DATE>
    <UNITNAME>Notices</UNITNAME>
    <NOTICES>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="1875"/>
                <AGENCY TYPE="F">AGENCY FOR INTERNATIONAL DEVELOPMENT</AGENCY>
                <SUBJECT>Agency Information Collection Activities; Submission to the Office of Management and Budget for Review and Approval; Comment Request; USAID Workforce Commuter Survey</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Agency for International Development (USAID).</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, USAID is proposing a new information collection.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>All comments should be submitted within 30 calendar days from the date of this publication.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Written comments and recommendations for the proposed information collection should be sent within 30 days of publication of this notice to 
                        <E T="03">www.reginfo.gov/public/do/PRAMain.</E>
                         Find this particular information collection by selecting “Currently under 30-day Review—Open for Public Comments” or by using the search function.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For specific questions related to collection activities, please contact Greg Shanahan, 
                        <E T="03">mbureauclimatechangewg@usaid.gov,</E>
                         202-921-5107.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>USAID, in accordance with the Paperwork Reduction Act of 1995 (PRA) (44 U.S.C. 3506(c)(2)(A)), provides the general public and Federal agencies with an opportunity to comment on proposed, revised, and continuing collections of information. This helps USAID assess the impact of its information collection requirements and minimize the public's reporting burden. It also helps the public understand USAID's information collection requirements and provide USAID the data it requested in the format it prefers. USAID is soliciting comments on the proposed information collection request (ICR) that USAID describes below. USAID is especially interested in public comment addressing the following issues: (1) how USAID might enhance the quality, utility, and clarity of the information it is planning to collect; and (2) how USAID might minimize the burden for the members of USAID's workforce who respond to the commuter survey, including by using information technology. Written comments USAID receives in response to this notice will be public records.</P>
                <P>
                    <E T="03">Title of Collection:</E>
                     USAID Workforce Commuter Survey.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     XXXX.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     A new information collection.
                </P>
                <P>
                    <E T="03">Respondents/Affected Public:</E>
                     USAID's workforce, including contractor staff.
                </P>
                <P>
                    <E T="03">Total Estimated Number of Annual Responses:</E>
                     6,500.
                </P>
                <P>
                    <E T="03">Total Estimated Number of Annual Burden Hours:</E>
                     1,083.33 (6,500 * 10 mins = 65,000 mins ÷ 60 mins = 1,083.33 hours).
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     USAID's workforce commuter survey enables USAID to estimate the greenhouse gas (GHG) emissions associated with its workforce's commuting and to gather data on its workforce's commuting habits. USAID will use these data to inform its GHG emissions inventory, measure progress against its GHG emissions reduction targets, and inform and improve its commuter benefits program and reporting.
                </P>
                <SIG>
                    <DATED>Dated: January 8, 2024.</DATED>
                    <NAME>Ruth Buckley,</NAME>
                    <TITLE>Deputy Assistant Administrator for Management, Bureau for Management, USAID.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00475 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
                <P>The Department of Agriculture has submitted the following information collection requirement(s) to OMB for review and clearance under the Paperwork Reduction Act of 1995, Public Law 104-13. Comments are requested regarding; whether the collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility; the accuracy of the agency's estimate of burden including the validity of the methodology and assumptions used; ways to enhance the quality, utility and clarity of the information to be collected; and ways to minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology.</P>
                <P>
                    Comments regarding this information collection received by February 12, 2024 will be considered. Written comments and recommendations for the proposed information collection should be submitted within 30 days of the publication of this notice on the following website 
                    <E T="03">www.reginfo.gov/public/do/PRAMain.</E>
                     Find this particular information collection by selecting “Currently under 30-day Review—Open for Public Comments” or by using the search function.
                </P>
                <P>An agency may not conduct or sponsor a collection of information unless the collection of information displays a currently valid OMB control number and the agency informs potential persons who are to respond to the collection of information that such persons are not required to respond to the collection of information unless it displays a currently valid OMB control number.</P>
                <HD SOURCE="HD1">Food and Nutrition Service</HD>
                <P>
                    <E T="03">Title:</E>
                     Improving Coordination Between SNAP and Medicaid in State Agencies.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     0584-NEW.
                </P>
                <P>
                    <E T="03">Summary of Collection:</E>
                     SNAP and Medicaid serve similar populations, which provides opportunities for State Agencies administering the programs to coordinate policies and processes to improve efficiency, customer service, and program access. This study will conduct case studies in up to five states to understand the challenges with improving program coordination and highlight the best practices that could be shared with other states.
                </P>
                <P>
                    <E T="03">Need and Use of the Information:</E>
                     FNS has identified five objectives for this study:
                    <PRTPAGE P="1876"/>
                </P>
                <P>1. Identify and describe relevant federal statutory, regulatory, and operational barriers and facilitators that have considerable impact on coordination between SNAP and Medicaid agencies.</P>
                <P>2. Identify and describe relevant State statutory, regulatory, and operational barriers and facilitators that have considerable impact on coordination between SNAP and Medicaid agencies.</P>
                <P>3. Identify and describe systems used by States to determine eligibility and manage SNAP and Medicaid application and recertification information.</P>
                <P>4. Identify and describe similarities and differences in State SNAP and Medicaid applications.</P>
                <P>5. Using information collected from Objectives 1-4, develop a Best Practices Guide that explains how States can better improve coordination between SNAP and Medicaid.</P>
                <P>
                    <E T="03">Description of Respondents:</E>
                     State and Local Government, Businesses or other For- Profit and Not-for-Profit.
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     180.
                </P>
                <P>
                    <E T="03">Frequency of Responses:</E>
                     Reporting: Once.
                </P>
                <P>
                    <E T="03">Total Burden Hours:</E>
                     184.
                </P>
                <SIG>
                    <NAME>Levi S. Harrell,</NAME>
                    <TITLE>Departmental Information Collection Clearance Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-00444 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">COMMISSION ON CIVIL RIGHTS</AGENCY>
                <SUBJECT>Notice of Public Meeting of the Georgia Advisory Committee to the U.S. Commission on Civil Rights</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Commission on Civil Rights.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of public meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Notice is hereby given, pursuant to the provisions of the rules and regulations of the U.S. Commission on Civil Rights (Commission) and the Federal Advisory Committee Act, that the Georgia Advisory Committee (Committee) to the U.S. Commission on Civil Rights will hold a public meeting via Zoom. The purpose of the meeting is to discuss the post-report activities of the Committee's recent civil rights project on civil asset forfeiture in Georgia.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Tuesday, January 30, 2024, from 12 p.m.-1 p.m. eastern time.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The meeting will be held via Zoom.</P>
                    <FP SOURCE="FP-1">
                        <E T="03">Registration Link (Audio/Visual): https://www.zoomgov.com/j/1607844568</E>
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Join by Phone (Audio Only):</E>
                         1-833-435-1820 USA Toll-Free; Meeting ID: 160 784 4568#
                    </FP>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Melissa Wojnaroski, Designated Federal Officer (DFO), at 
                        <E T="03">mwojnaroski@usccr.gov</E>
                         or 1-202-618-4158.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    This Committee meeting is available to the public through the registration link above. Any interested member of the public may attend this meeting. An open comment period will be provided to allow members of the public to make oral statements as time allows. Pursuant to the Federal Advisory Committee Act, public minutes of the meeting will include a list of persons who are present at the meeting. If joining via phone, callers can expect to incur regular charges for calls they initiate over wireless lines, according to their wireless plan. The Commission will not refund any incurred charges. Callers will incur no charge for calls they initiate over land-line connections to the toll-free telephone number. Closed captioning is available by selecting “CC” in the meeting platform. To request additional accommodations, please email 
                    <E T="03">svillanueva@usccr.gov</E>
                     at least 10 business days prior to the meeting.
                </P>
                <P>
                    Members of the public are entitled to submit written comments; the comments must be received in the regional office within 30 days following the scheduled meeting. Written comments may be emailed to Sarah Villanueva at 
                    <E T="03">svillanueva@usccr.gov.</E>
                     Persons who desire additional information may contact the Regional Programs Coordination Unit at 1-434-515-0204.
                </P>
                <P>
                    Records generated from this meeting may be inspected and reproduced at the Regional Programs Coordination Unit Office, as they become available, both before and after the meeting. Records of the meetings will be available via 
                    <E T="03">www.facadatabase.gov</E>
                     under the Commission on Civil Rights, Georgia Advisory Committee link. Persons interested in the work of this Committee are directed to the Commission's website, 
                    <E T="03">http://www.usccr.gov,</E>
                     or may contact the Regional Programs Coordination Unit at 
                    <E T="03">svillanueva@usccr.gov.</E>
                </P>
                <HD SOURCE="HD1">Agenda</HD>
                <FP SOURCE="FP-1">I. Welcome &amp; Roll Call</FP>
                <FP SOURCE="FP-1">II. Approval of Minutes</FP>
                <FP SOURCE="FP-1">III. Announcements and Updates</FP>
                <FP SOURCE="FP-1">IV. Discussion: Post-Report Activities</FP>
                <FP SOURCE="FP-1">V. Next Steps</FP>
                <FP SOURCE="FP-1">VI. Public Comment</FP>
                <FP SOURCE="FP-1">VII. Adjournment</FP>
                <SIG>
                    <DATED>Dated: January 8, 2024.</DATED>
                    <NAME>David Mussatt,</NAME>
                    <TITLE>Supervisory Chief, Regional Programs Unit.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00424 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>Bureau of Industry and Security</SUBAGY>
                <SUBJECT>Sensors and Instrumentation Technical Advisory Committee; Notice of Open Meeting</SUBJECT>
                <P>The Sensors and Instrumentation Technical Advisory Committee (SITAC) will meet on Tuesday, January 30, 2024, 9:30 a.m., (Pacific standard time) at the SPIE Photonics West 2023, at the InterContinental Hotel San Francisco, 888 Howard Street, in the Fremont Room (Level 5), San Francisco, CA 94103. The Committee advises the Office of the Assistant Secretary for Export Administration on technical questions that affect the level of export controls applicable to sensors and instrumentation equipment and technology. The purpose of the meeting is to have Committee members and U.S. Government representatives mutually review updated technical data and policy-driving information that has been gathered.</P>
                <HD SOURCE="HD1">Agenda</HD>
                <HD SOURCE="HD2">Open Session</HD>
                <FP SOURCE="FP-1">1. Welcome and Introductions</FP>
                <FP SOURCE="FP-1">2. Remarks from the Bureau of Industry and Security Management</FP>
                <FP SOURCE="FP-1">3. Industry Presentations</FP>
                <FP SOURCE="FP-1">4. New Business</FP>
                <P>
                    To join the conference, submit inquiries to Ms. Yvette Springer at 
                    <E T="03">Yvette.Springer@bis.doc.gov</E>
                     no later than January 23, 2024.
                </P>
                <P>A limited number of seats will be available during the public session of the meeting.</P>
                <P>Reservations are not accepted. To the extent that time permits, members of the public may present oral statements to the Committee. The public may submit written statements at any time before or after the meeting. However, to facilitate distribution of public presentation materials to the Committee members, the Committee suggests that the materials be forwarded before the meeting to Ms. Springer.</P>
                <P>For more information contact Ms. Springer via email.</P>
                <SIG>
                    <NAME>Yvette Springer,</NAME>
                    <TITLE>Committee Liaison Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-00422 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-JT-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="1877"/>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>International Trade Administration</SUBAGY>
                <DEPDOC>[A-533-502, A-549-502, A-489-501, A-201-805, A-580-809, A-583-008, A-583-814, C-489-502, A-351-809]</DEPDOC>
                <SUBJECT>Certain Welded Carbon Steel Pipes and Tubes From India, Thailand, and the Republic of Turkey; Certain Circular Welded Non-Alloy Steel Pipe From Brazil, Mexico, the Republic of Korea, and Taiwan; and Certain Circular Welded Carbon Steel Pipes and Tubes From Taiwan: Continuation of Antidumping Duty Orders (India, Mexico, the Republic of Korea, Taiwan, Thailand, and the Republic of Turkey), Continuation of Countervailing Duty Order (the Republic of Turkey), and Revocation of Antidumping Duty Order (Brazil)</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>As a result of the determinations by the U.S. Department of Commerce (Commerce) and the U.S. International Trade Commission (ITC) that revocation of the antidumping duty (AD) orders on: certain welded carbon steel pipes and tubes (pipes and tubes) from India, Thailand, and the Republic of Turkey (Turkey); certain circular welded non-alloy steel pipe (non-alloy steel pipe) from Mexico, the Republic of Korea (Korea), and Taiwan; and certain circular welded carbon steel pipes and tubes (circular pipes and tubes) from Taiwan would likely lead to continuation or recurrence of dumping and material injury to an industry in the United States, Commerce is publishing a notice of continuation of these AD orders. Additionally, as a result of determinations by Commerce and the ITC that revocation of the countervailing duty (CVD) order on pipes and tubes from Turkey would likely lead to continuation or recurrence of countervailable subsidies and material injury to an industry in the United States, Commerce is publishing a notice of continuation of this CVD order. Furthermore, as a result of the ITC's determination that revocation of the AD order on non-alloy steel pipe from Brazil is not likely to lead to continuation or recurrence of material injury to an industry in the United States, Commerce is revoking the AD order on pipes and tubes from Brazil.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>AD Revocation (Brazil): Applicable February 7, 2023; AD and CVD Continuations (India, Mexico, Korea, Thailand, Taiwan, and Turkey): Applicable January 4, 2024.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Richard Roberts, AD/CVD Operations, Office I, and Jacqueline Arrowsmith, 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-3464 and (202) 482-5255, respectively.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On May 7, 1984, Commerce published the AD order on circular pipes and tubes from Taiwan.
                    <SU>1</SU>
                    <FTREF/>
                     Between March 7 and May 15, 1986, Commerce published the AD orders on pipes and tubes from India, Thailand, and Turkey and the CVD order on pipe and tubes from Turkey.
                    <SU>2</SU>
                    <FTREF/>
                     On November 2, 1992, Commerce published the AD orders on non-alloy steel pipe from Brazil, Mexico, Korea, and Taiwan.
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See Certain Circular Welded Carbon Steel Pipes and Tubes from Taiwan: Antidumping Duty Order,</E>
                         49 FR 19369 (May 7, 1984).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See Antidumping Duty Order: Certain Welded Carbon Steel Standard Pipes and Tubes from India,</E>
                         51 FR 17384 (May 12, 1986); 
                        <E T="03">Antidumping Duty Order: Circular Welded Carbon Steel Pipes and Tubes from Thailand,</E>
                         51 FR 8341 (March 11, 1986); 
                        <E T="03">Antidumping Duty Order: Welded Carbon Steel Standard Pipe and Tube Products from Turkey,</E>
                         51 FR 17784 (May 15, 1986); and 
                        <E T="03">Countervailing Duty Order: Certain Welded Carbon Steel Pipe and Tube Products from Turkey,</E>
                         51 FR 7984 (March 7, 1986).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See Notice of Antidumping Duty Orders: Certain Circular Non-Alloy Steel Pipe from Brazil, the Republic of Korea, Mexico, Taiwan, and Venezuela and Amendment to Final Determination of Sales at Less Than Fair Value: Certain Circular Welded Non-Alloy Steel Pipe from Korea,</E>
                         57 FR 49453 (November 2, 1992).
                    </P>
                </FTNT>
                <P>
                    On January 3, 2023, Commerce initiated, and the ITC instituted the fifth sunset review of the AD orders on pipes and tubes from India, Thailand, and Turkey; non-alloy steel pipe from Brazil, Mexico, Korea, and Taiwan; circular pipes and tubes from Taiwan; and the CVD order on pipes and tubes from Turkey, pursuant to section 751© of the Tariff Act of 1930, as amended (the Act).
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See Initiation of Five-Year (Sunset) Reviews,</E>
                         88 FR 63 (January 3, 2023); 
                        <E T="03">see also Circular Welded Pipe and Tube from Brazil, India, Mexico, South Korea, Taiwan, Thailand, and Turkey; Institution of Five-Year Reviews,</E>
                         88 FR 107 (January 3, 2023).
                    </P>
                </FTNT>
                <P>
                    As a result of its reviews, Commerce determined, pursuant to sections 751(c)(1) and 752(c) of the Act, that revocation of the AD orders on pipes and tubes from India, Thailand, and Turkey; non-alloy steel pipe from Brazil, Mexico, Korea, and Taiwan; and circular pipes and tubes from Taiwan would likely lead to the continuation or recurrence of dumping and, therefore, notified the ITC of the magnitude of the margins of dumping likely to prevail should these AD orders be revoked.
                    <SU>5</SU>
                    <FTREF/>
                     Additionally, Commerce determined pursuant to sections 751(c)(1) and 752(b) of the Act, that revocation of the CVD order on pipes and tubes from Turkey would likely lead to continuation or recurrence of countervailable subsidies and notified the ITC of the net countervailable subsidy rates likely to prevail should the order be revoked.
                    <SU>6</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03"> See Certain Welded Carbon Steel Pipes and Tubes from India, Thailand, and Republic of Turkey: Final Results of the Expedited Sunset Review of the Antidumping Duty Orders,</E>
                         88 FR 29636 (May 8, 2023), and accompanying Issues and Decision Memorandum (IDM); and 
                        <E T="03">Certain Circular Welded Non-Alloy Steel Pipe from Brazil, Mexico, the Republic of Korea, and Taiwan and Certain Circular Welded Carbon Steel Pipes and Tubes from Taiwan: Final Results of Expedited Fifth Sunset Reviews of the Antidumping Duty Orders,</E>
                         88 FR 29880 (May 9, 2023).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See Circular Welded Carbon Steel Pipes and Tubes from Turkey: Final Results of the Expedited Sunset Review of the Countervailing Duty Order,</E>
                         88 FR 24757 (April 24, 2023), and accompanying IDM.
                    </P>
                </FTNT>
                <P>
                    On January 4, 2024, the ITC published its determination, pursuant to sections 751(c) and 752(a) of the Act, that revocation of the AD orders on pipes and tubes from India, Thailand, and Turkey; the CVD order on pipes and tubes from Turkey; the AD orders on non-alloy steel pipe from Mexico, Korea, and Taiwan; and the AD order on circular pipes and tubes from Taiwan would likely lead to continuation or recurrence of material injury to an industry in the United States within a reasonably foreseeable time, but that revocation of the AD order on non-alloy steel pipe from Brazil would not be likely to lead to continuation or recurrence of material injury within a reasonably foreseeable time.
                    <SU>7</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See Circular Welded Pipe and Tube From Brazil, India, Mexico, South Korea, Taiwan, Thailand, and Turkey; Determination,</E>
                         89 FR 478 (January 4, 2024); and 
                        <E T="03">Circular Welded Pipe and Tube from Brazil, India, Mexico, South Korea, Taiwan, Thailand, and Turkey: Investigation Nos. 701-TA-253 and 731-TA-132, 252, 271, 273, 532-534, and 536</E>
                         (Fifth Review), 89 FR 478 (January 4, 2024).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Scope of the AD and CVD Orders</HD>
                <P>
                    The products covered by the orders are pipes and tubes, non-alloy steel pipe, and circular pipes and tubes. For a complete description of the scope of the AD and CVD orders, 
                    <E T="03">see</E>
                     the appendix to this notice.
                </P>
                <HD SOURCE="HD1">Continuation of the AD Orders and CVD Order on Pipes and Tubes From India, Thailand, and Turkey; Non-Alloy Steel Pipe From Mexico, Korea, and Taiwan; and Circular Pipes and Tubes From Taiwan</HD>
                <P>
                    As a result of the determinations by Commerce and the ITC that revocation of the AD orders on pipes and tubes 
                    <PRTPAGE P="1878"/>
                    from India, Thailand, and Turkey; non-alloy steel pipe from Mexico, Korea, and Taiwan; circular pipes and tubes from Taiwan; and the CVD order on pipes and tubes from Turkey would likely lead to continuation or recurrence of dumping and countervailable subsidies and material injury to an industry in the United States, pursuant to section 751(d)(2) of the Act, Commerce hereby orders the continuation of the AD orders on pipes and tubes from India, Thailand, and Turkey; non-alloy steel pipe from Mexico, Korea, and Taiwan; circular pipes and tubes from Taiwan; and the CVD order on pipes and tubes from Turkey. U.S. Customs and Border Protection will continue to collect AD and CVD cash deposits at the rates in effect at the time of entry for all imports of subject merchandise.
                </P>
                <P>The effective date of the continuation of the AD and CVD orders will be January 4, 2024. Commerce intends to initiate the next five-year reviews of the AD and CVD orders not later than 30 days prior to the fifth anniversary of the effective date of continuation.</P>
                <HD SOURCE="HD1">Revocation of the AD Order on Non-Alloy Steel Pipe From Brazil</HD>
                <P>
                    As a result of the determination by the ITC that revocation of the AD order on non-alloy steel pipe from Brazil would not be likely to lead to continuation or recurrence of material injury to an industry in the United States, pursuant to section 751(d)(2) of the Act, 19 CFR 351.222(i)(1)(iii), and 19 CFR 351.218(a), Commerce is revoking the AD order on non-alloy steel pipe from Brazil. Pursuant to section 751(d)(3) of the Act and 19 CFR 351.222 (i)(2)(i), the effective date of the revocation is February 7, 2023 (
                    <E T="03">i.e.,</E>
                     the fifth anniversary of the date of publication in the 
                    <E T="04">Federal Register</E>
                     of the notice of continuation of the AD order).
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See Certain Welded Carbon Steel Pipes and Tubes from India, Thailand, and Turkey; Certain Circular Welded Non Alloy Steel Pipe from Brazil, Mexico, the Republic of Korea, and Taiwan; and Certain Circular Welded Carbon Steel Pipes and Tubes from Taiwan: Continuation of Antidumping Duty Orders and Countervailing Duty Order,</E>
                         83 FR 5402 (February 7, 2018).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Cash Deposits and Assessment of Duties on Non-Alloy Steel Pipe From Brazil</HD>
                <P>Commerce intends to notify CBP to terminate the suspension of liquidation and to discontinue the collection of AD cash deposits on entries of non-alloy steel pipe from Brazil, entered or withdrawn from warehouse, on or after February 7, 2023. Commerce intends to further instruct CBP to refund with interest all cash deposits on unliquidated entries made on or after February 7, 2023. Entries of subject merchandise prior to the effective date of revocation will continue to be subject to suspension of liquidation and AD deposit requirements and assessments.</P>
                <HD SOURCE="HD1">Administrative Protective Order</HD>
                <P>This notice serves as the only reminder to parties subject to an administrative protective order (APO) of their responsibility concerning the return/destruction or conversion to judicial protective order of proprietary information disclosed under APO in accordance with 19 CFR 351.305(a)(3), which continues to govern business proprietary information in this segment of the proceedings. Timely written notification of the return or destruction of APO materials, or conversion to judicial protective order, is hereby requested. Failure to comply with the regulations and terms of the APO is a sanctionable violation.</P>
                <HD SOURCE="HD1">Notification to Interested Parties</HD>
                <P>We are issuing and publishing this notice in accordance with sections 751(c) and (d)(2) and 777(i)(1) of the Act, and 19 CFR 351.218(f)(4) and 19 CFR 351.222(i)(1)(iii).</P>
                <SIG>
                    <DATED>Dated: January 5, 2024.</DATED>
                    <NAME>Abdelali Elouaradia,</NAME>
                    <TITLE>Deputy Assistant Secretary for Enforcement and Compliance.</TITLE>
                </SIG>
                <APPENDIX>
                    <HD SOURCE="HED">Appendix—Scope of the Antidumping Duty Orders and Countervailing Duty Order </HD>
                    <HD SOURCE="HD1">Certain Welded Carbon Steel Pipes and Tubes From India (A-533-502)</HD>
                    <P>The products covered by this order are certain welded carbon steel standard pipes and tubes with an outside diameter of 0.375 inch or more but not over 16 inches. These products are commonly referred to in the industry as standard pipes and tubes produced to various American Society for Testing Materials (ASTM) specifications, most notably A-53, A-120, or A-135.</P>
                    <P>
                        The antidumping duty order on certain welded carbon steel standard pipes and tubes from India, published on May 12, 1986, included standard scope language which used the import classification system as defined by Tariff Schedules of the United States, Annotated (TSUSA). The United States developed a system of tariff classification based on the international harmonized system of customs nomenclature. On January 1, 1989, the U.S. tariff schedules were fully converted from the TSUSA to the Harmonized Tariff Schedule of the United States (HTSUS). 
                        <E T="03">See, e.g., Certain Welded Carbon Steel Standard Pipes and Tubes from India; Preliminary Results of Antidumping Duty Administrative Reviews,</E>
                         56 FR 26650, 26651 (June 10, 1991). As a result of this transition, the scope language we used in the 1991 
                        <E T="04">Federal Register</E>
                         notice is slightly different from the scope language of the original final determination and antidumping duty order.
                    </P>
                    <P>Until January 1, 1989, such merchandise was classifiable under item numbers 610.3231, 610.3234, 610.3241, 610.3242, 610.3243, 610.3252, 610.3254, 610.3256, 610.3258, and 610.4925 of the TSUSA. This merchandise is currently classifiable under HTS item numbers 7306.30.1000, 7306.30.5025, 7306.30.5032, 7306.30.5040, 7306.30.5055, 7306.30.5085, 7306.30.5090. As with the TSUSA numbers, the HTS numbers are provided for convenience and customs purposes. The written product description remains dispositive.</P>
                    <HD SOURCE="HD1">Certain Welded Carbon Steel Pipes and Tubes From Thailand (A-549-502)</HD>
                    <P>
                        The products covered by this order are certain circular welded carbon steel pipes and tubes from Thailand. The subject merchandise has an outside diameter of 0.375 inches or more, but not exceeding 16 inches. These products, which are commonly referred to in the industry as “standard pipe” or “structural tubing” are hereinafter designated as “pipes and tubes.” The merchandise is classifiable under the Harmonized Tariff Schedule of the United States (HTSUS) item numbers 7306.30.1000, 7306.30.5025, 7306.30.5032, 7306.30.5040, 7306.30.5055, 7306.30.5085 and 7306.30.5090. Although the HTSUS subheadings are provided for convenience and purposes of U.S. Customs and Border Protection (CBP), the written description of the merchandise subject to the Thailand Order is dispositive.
                        <SU>9</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>9</SU>
                             
                            <E T="03">See Circular Welded Carbon Steel Pipes and Tubes from Thailand: Final Results of Antidumping Duty Administrative Review and Final Determination of No Shipments; 2020-2021,</E>
                             87 FR 60656 (October 6, 2022).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">Certain Welded Carbon Steel Pipes and Tubes From Turkey (A-489-501)</HD>
                    <P>The products covered by this order are welded carbon steel standard pipe and tube products with an outside diameter of 0.375 inch or more but not over 16 inches of any wall thickness, and are currently classified under the following Harmonized Tariff Schedule of the United States (HTSUS) subheadings: 7306.30.1000, 7306.30.5025, 7306.30.5032, 7306.30.5040, 7306.30.5055, 7306.30.5085, and 7306.30.5090.10. Although the HTSUS subheading is provided for convenience and customs purposes, the written description of the merchandise under investigation is dispositive. These products, commonly referred to in the industry as standard pipe or tube, are produced to various ASTM specifications, most notably A-120, A-53, or A-135.</P>
                    <HD SOURCE="HD1">Certain Welded Carbon Steel Pipes and Tubes From Turkey (C-489-502)</HD>
                    <P>The products covered by this order are certain welded carbon steel pipe and tube with an outside diameter of 0.375 inch or more, but not over 16 inches, of any wall thickness (pipe and tube) from Turkey. These products are currently provided for under the Harmonized Tariff Schedule of the United </P>
                    <PRTPAGE P="1879"/>
                    <FP>States (HTSUS) as item numbers 7306.30.10, 7306.30.50, and 7306.90.10. Although the HTSUS subheadings are provided for convenience and customs purposes, the written description of the merchandise is dispositive.</FP>
                    <HD SOURCE="HD1">Certain Circular Welded Non-Alloy Steel Pipe From Brazil (A-351-809)</HD>
                    <P>The products covered by this order are circular welded non-alloy steel pipes and tubes, of circular cross-section, not more than 406.4 mm (16 inches) in outside diameter, regardless of wall thickness, surface finish (black, galvanized, or painted), or end finish (plain end, bevelled end, threaded, or threaded and coupled). These pipes and tubes are generally known as standard pipes and tubes are intended for the low pressure conveyance of water, steam, natural gas, and other liquids and gases in plumbing and heating systems, air conditioning units, automatic sprinkler systems, and other related uses, and generally meet ASTM A-53 specifications.</P>
                    <P>Standard pipe may also be used for light load-bearing applications, such as for fence tubing, and as structural pipe tubing used for framing and support members for reconstruction or load-bearing purposes in the construction, shipbuilding, trucking, farm equipment, and related industries. Unfinished conduit pipe is also included in these orders. All carbon steel pipes and tubes within the physical description outlined above are included within the scope of these orders, except line pipe, oil country tubular goods, boiler tubing, mechanical tubing, pipe and tube hollows for redraws, finished scaffolding, and finished conduit. Standard pipe that is dual or triple certified/stenciled that enters the U.S. as line pipe of a kind used for oil or gas pipelines is also not included in these orders.</P>
                    <P>Imports of the products covered by these orders are currently classifiable under the following Harmonized Tariff Schedule (HTS) subheadings: 7306.30.10.00, 7306.30.50.25, 7306.30.50.32, 7306.30.50.40, 7306.30.50.55, 7306.30.50.85, and 7306.30.50.90. Although the HTS subheadings are provided for convenience and customs purposes, our written description of the scope of these orders is dispositive.</P>
                    <HD SOURCE="HD1">Certain Circular Welded Non-Alloy Steel Pipe From Mexico (A-201-805)</HD>
                    <P>The products covered by this order are circular welded non-alloy steel pipes and tubes, of circular cross-section, not more than 406.4 mm (16 inches) in outside diameter, regardless of wall thickness, surface finish (black, galvanized, or painted), or end finish (plain end, bevelled end, threaded, or threaded and coupled). These pipes and tubes are generally known as standard pipes and tubes are intended for the low pressure conveyance of water, steam, natural gas, and other liquids and gases in plumbing and heating systems, air conditioning units, automatic sprinkler systems, and other related uses, and generally meet ASTM A-53 specifications.</P>
                    <P>Standard pipe may also be used for light load-bearing applications, such as for fence tubing, and as structural pipe tubing used for framing and support members for reconstruction or load-bearing purposes in the construction, shipbuilding, trucking, farm equipment, and related industries. Unfinished conduit pipe is also included in these orders. All carbon steel pipes and tubes within the physical description outlined above are included within the scope of these orders, except line pipe, oil country tubular goods, boiler tubing, mechanical tubing, pipe and tube hollows for redraws, finished scaffolding, and finished conduit. Standard pipe that is dual or triple certified/stenciled that enters the U.S. as line pipe of a kind used for oil or gas pipelines is also not included in these orders.</P>
                    <P>Imports of the products covered by these orders are currently classifiable under the following Harmonized Tariff Schedule (HTS) subheadings: 7306.30.10.00, 7306.30.50.25, 7306.30.50.32, 7306.30.50.40, 7306.30.50.55, 7306.30.50.85, and 7306.30.50.90. Although the HTS subheadings are provided for convenience and customs purposes, our written description of the scope of these orders is dispositive.</P>
                    <HD SOURCE="HD1">Certain Circular Welded Non-Alloy Steel Pipe From Korea (A-580-809)</HD>
                    <P>The products covered by this order are circular welded non-alloy steel pipes and tubes, of circular cross-section, not more than 406.4 mm (16 inches) in outside diameter, regardless of wall thickness, surface finish (black, galvanized, or painted), or end finish (plain end, bevelled end, threaded, or threaded and coupled). These pipes and tubes are generally known as standard pipes and tubes are intended for the low pressure conveyance of water, steam, natural gas, and other liquids and gases in plumbing and heating systems, air conditioning units, automatic sprinkler systems, and other related uses, and generally meet ASTM A-53 specifications.</P>
                    <P>Standard pipe may also be used for light load-bearing applications, such as for fence tubing, and as structural pipe tubing used for framing and support members for reconstruction or load-bearing purposes in the construction, shipbuilding, trucking, farm equipment, and related industries. Unfinished conduit pipe is also included in these orders. All carbon steel pipes and tubes within the physical description outlined above are included within the scope of these orders, except line pipe, oil country tubular goods, boiler tubing, mechanical tubing, pipe and tube hollows for redraws, finished scaffolding, and finished conduit. Standard pipe that is dual or triple certified/stenciled that enters the U.S. as line pipe of a kind used for oil or gas pipelines is also not included in these orders.</P>
                    <P>Imports of the products covered by these orders are currently classifiable under the following Harmonized Tariff Schedule (HTS) subheadings: 7306.30.10.00, 7306.30.50.25, 7306.30.50.32, 7306.30.50.40, 7306.30.50.55, 7306.30.50.85, and 7306.30.50.90. Although the HTS subheadings are provided for convenience and customs purposes, our written description of the scope of these orders is dispositive.</P>
                    <HD SOURCE="HD1">Certain Circular Welded Non-Alloy Steel Pipe From Taiwan (A-583-814)</HD>
                    <P>The products covered by this order are (1) circular welded non-alloy steel pipes and tubes, of circular cross section over 114.3 millimeters (4.5 inches), but not over 406.4 millimeters (16 inches) in outside diameter, with a wall thickness of 1.65 millimeters (0.065 inches) or more, regardless of surface finish (black, galvanized, or painted), or end-finish (plain end, beveled end, threaded, or threaded and coupled); and (2) circular welded non-alloy steel pipes and tubes, of circular cross-section less than 406.4 millimeters (16 inches), with a wall thickness of less than 1.65 millimeters (0.065 inches), regardless of surface finish (black, galvanized, or painted) or end-finish (plain end, beveled end, threaded, or threaded and coupled). These pipes and tubes are generally known as standard pipes and tubes and are intended for the low pressure conveyance of water, steam, natural gas, air, and other liquids and gases in plumbing and heating systems, air conditioning units, automatic sprinkling systems, and other related uses, and generally meet ASTM A-53 specifications. Standard pipe may also be used for light load-bearing applications, such as for fence-tubing and as structural pipe tubing used for framing and support members for construction, or load-bearing purposes in the construction, shipbuilding, trucking, farm-equipment, and related industries. Unfinished conduit pipe is also included in this order.</P>
                    <P>All carbon steel pipes and tubes within the physical description outlined above are included within the scope of this order, except line pipe, oil country tubular goods, boiler tubing, mechanical tubing, pipe and tube hollows for redraws, finished scaffolding, and finished conduit. Standard pipe that is dual or triple certified/stenciled that enters the U.S. as line pipe of a kind or used for oil and gas pipelines is also not included in this investigation.</P>
                    <P>Imports of the products covered by this order are currently classifiable under the following Harmonized Tariff Schedule (HTS) subheadings, 7306.30.10.00, 7306.30.50.25, 7306.30.50.32, 7306.30.50.40, 7306.30.50.55, 7306.30.50.85, 7306.30.50.90. Although the HTS subheadings are provided for convenience and customs purposes, our written description of the scope of this order is dispositive.</P>
                    <HD SOURCE="HD1">Certain Circular Welded Carbon Steel Pipes and Tubes From Taiwan (A-583-008)</HD>
                    <P>
                        The merchandise covered by this order is certain circular welded carbon steel pipes and tubes from Taiwan, which are defined as: welded carbon steel pipes and tubes, of circular cross section, with walls not thinner than 0.065 inch, and 0.375 inch or more but not over 4.5 inches in outside diameter, currently classified under Harmonized Tariff Schedule of the United States (HTSUS) item numbers 7306.30.5025, 7306.30.5032, 7306.30.5040, and 7306.30.5055. Although the HTSUS subheading is provided for convenience and customs purposes, the 
                        <PRTPAGE P="1880"/>
                        written description of the merchandise under investigation is dispositive.
                        <FTREF/>
                        <SU>10</SU>
                    </P>
                    <FTNT>
                        <P>
                            <SU>10</SU>
                             
                            <E T="03">See Certain Circular Welded Carbon Steel Pipes and Tubes from Taiwan: Final Results of Antidumping Duty Administrative Review, 2018-2019,</E>
                             86 FR 6302 (January 21, 2020).
                        </P>
                    </FTNT>
                </APPENDIX>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00397 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>International Trade Administration</SUBAGY>
                <DEPDOC>[Application No. 92-17A001]</DEPDOC>
                <SUBJECT>Export Trade Certificate of Review</SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of application for an amended Export Trade Certificate of Review by Aerospace Industries Association of America, Inc. (AIA), Application No. 92-17A001.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Secretary of Commerce, through the Office of Trade and Economic Analysis (OTEA) of the International Trade Administration, received an application for an amended Export Trade Certificate of Review (Certificate). This notice summarizes the proposed application and requests comments relevant to whether the amended Certificate should be issued.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Joseph Flynn, Director, Office of Trade and Economic Analysis, International Trade Administration, (202) 482-5131 (this is not a toll-free number) or email at 
                        <E T="03">etca@trade.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Title III of the Export Trading Company Act of 1982 (15 U.S.C. 4011-21) (the Act) authorizes the Secretary of Commerce to issue Export Trade Certificates of Review. An Export Trade Certificate of Review protects the holder and the members identified in the Certificate from State and Federal government antitrust actions and from private treble damage antitrust actions for the export conduct specified in the Certificate and carried out in compliance with its terms and conditions. The regulations implementing Title III are found at 15 CFR part 325. OTEA is issuing this notice pursuant to 15 CFR 325.6(a), which requires the Secretary of Commerce to publish a summary of the application in the 
                    <E T="04">Federal Register</E>
                    , identifying the applicant and each member and summarizing the proposed export conduct.
                </P>
                <HD SOURCE="HD1">Request for Public Comments</HD>
                <P>Interested parties may submit written comments relevant to the determination whether a Certificate should be issued. If the comments include any privileged or confidential business information, it must be clearly marked and a nonconfidential version of the comments (identified as such) should be included. Any comments not marked as privileged or confidential business information will be deemed to be nonconfidential.</P>
                <P>
                    Written comments should be sent to 
                    <E T="03">ETCA@trade.gov.</E>
                     An original and five (5) copies, plus two (2) copies of the nonconfidential version, should also be submitted no later than 20 days after the date of this notice to: Office of Trade and Economic Analysis, International Trade Administration, U.S. Department of Commerce, Room 21028, Washington, DC 20230.
                </P>
                <P>Information submitted by any person is exempt from disclosure under the Freedom of Information Act (5 U.S.C. 552). However, nonconfidential versions of the comments will be made available to the applicant if necessary for determining whether or not to issue the Certificate. Comments should refer to this application as “Export Trade Certificate of Review, application number 92-17A001.”</P>
                <P>A summary of the application follows.</P>
                <HD SOURCE="HD1">Summary of the Application</HD>
                <P>
                    <E T="03">Applicant:</E>
                     AIA, 1000 Wilson Boulevard, Suite 1700, Arlington, VA 22209.
                </P>
                <P>
                    <E T="03">Contact:</E>
                     Matthew F. Hall, General Counsel, Dunaway &amp; Cross, P.C.
                </P>
                <P>
                    <E T="03">Application No.:</E>
                     92-17A001.
                </P>
                <P>
                    <E T="03">Date Deemed Submitted:</E>
                     December 26, 2023
                </P>
                <P>
                    <E T="03">Proposed Amendment:</E>
                     AIA seeks to amend its Certificate as follows:
                </P>
                <P>1. Add the following companies as new Members of the Certificate within the meaning of section 325.2(l) of the Regulations (15 CFR 325.2(l)):</P>
                <FP SOURCE="FP-1">• Albany Engineered Composites; Rochester, NH (controlling entity Albany International Corp.; Rochester, NH)</FP>
                <FP SOURCE="FP-1">• ALTEN Technology USA, Inc.; Troy, MI (controlling entity The ALTEN Group; Boulogne-Billancourt, France)</FP>
                <FP SOURCE="FP-1">• Archer Aviation Inc.; Palo Alto, CA</FP>
                <FP SOURCE="FP-1">• ATLAS Space Operations, Inc.; Traverse City, MI</FP>
                <FP SOURCE="FP-1">• Bain &amp; Company, Inc.; Boston, MA</FP>
                <FP SOURCE="FP-1">• BlackSky Technology Inc.; Herndon, VA</FP>
                <FP SOURCE="FP-1">• Chicago Precision, Inc.; Elk Grove Village, IL</FP>
                <FP SOURCE="FP-1">• Cre8tive Technology and Design, Inc.; San Diego, CA</FP>
                <FP SOURCE="FP-1">• Deltek, Inc.; Herndon, VA</FP>
                <FP SOURCE="FP-1">• Epirus, Inc.; Los Angeles, CA</FP>
                <FP SOURCE="FP-1">• Estes Energetics; Penrose, CO</FP>
                <FP SOURCE="FP-1">• ExoAnalytic Solutions Inc.; Foothill Ranch, CA</FP>
                <FP SOURCE="FP-1">• GKN Aerospace North America; Westlake, TX (controlling entity GKN Aerospace Services Limited Solihull, UK)</FP>
                <FP SOURCE="FP-1">• GXA Consulting LLC; Ely, IA</FP>
                <FP SOURCE="FP-1">• Ivis Technologies, LLC; Phoenix, AZ</FP>
                <FP SOURCE="FP-1">• Janes Capital Partners, Inc.; Irvine, CA</FP>
                <FP SOURCE="FP-1">• LeoLabs, Inc.; Menlo Park, CA</FP>
                <FP SOURCE="FP-1">• LOAR Group; White Plains, NY</FP>
                <FP SOURCE="FP-1">• MapLarge, Inc.; Atlanta, GA</FP>
                <FP SOURCE="FP-1">• Merlin Labs, Inc.; Boston, MA</FP>
                <FP SOURCE="FP-1">• Overair, Inc.; Santa Ana, CA</FP>
                <FP SOURCE="FP-1">• Primer AI; Arlington, VA</FP>
                <FP SOURCE="FP-1">• RCM Technologies, Inc.; Pennsauken, N.J.</FP>
                <FP SOURCE="FP-1">• Riveron Consulting, LLC; Dallas, TX</FP>
                <FP SOURCE="FP-1">• Rocket Lab USA, Inc.; Long Beach, CA</FP>
                <FP SOURCE="FP-1">• Shift5; Rosslyn, VA</FP>
                <FP SOURCE="FP-1">• Slingshot Aerospace, Inc.; Austin, TX</FP>
                <FP SOURCE="FP-1">• The Haskell Company; Jacksonville, FL</FP>
                <FP SOURCE="FP-1">• TransDigm Group, Inc.; Cleveland, OH</FP>
                <FP SOURCE="FP-1">• True Anomaly; Centennial, CO</FP>
                <FP SOURCE="FP-1">• TTM Technologies Inc.; Santa Ana, CA</FP>
                <FP SOURCE="FP-1">• United Launch Alliance; Centennial, CO</FP>
                <FP SOURCE="FP-1">• Ursa Major Technologies, Inc.; Berthoud, CO</FP>
                <FP SOURCE="FP-1">• Weldaloy Specialty Forgings; Warren, MI</FP>
                <FP SOURCE="FP-1">• Westinghouse Electric Company LLC; Cranberry Township, PA</FP>
                <P>2. Remove the following companies as Members of AIA's Certificate:</P>
                <FP SOURCE="FP-1">• ADDMAN Tech Production Center</FP>
                <FP SOURCE="FP-1">• Aernnova Aerospace</FP>
                <FP SOURCE="FP-1">• Aerojet Rocketdyne</FP>
                <FP SOURCE="FP-1">• AMETEK Pacific Design Technologies</FP>
                <FP SOURCE="FP-1">• Apex International Management Company</FP>
                <FP SOURCE="FP-1">• Astronics Corporation</FP>
                <FP SOURCE="FP-1">• Avascent</FP>
                <FP SOURCE="FP-1">• CAE USA</FP>
                <FP SOURCE="FP-1">• ENSCO, Inc.</FP>
                <FP SOURCE="FP-1">• Ferra Aerospace, Inc.</FP>
                <FP SOURCE="FP-1">• IBM Corporation</FP>
                <FP SOURCE="FP-1">• Metis Flight Research Associates</FP>
                <FP SOURCE="FP-1">• Microsoft Azure</FP>
                <FP SOURCE="FP-1">• MTI Motion</FP>
                <FP SOURCE="FP-1">• Net-Inspect, LLC</FP>
                <FP SOURCE="FP-1">• Plexus Corporation</FP>
                <FP SOURCE="FP-1">• PTC Inc.</FP>
                <FP SOURCE="FP-1">• SB Technology, Inc.</FP>
                <FP SOURCE="FP-1">• Sunbelt Design and Development, Inc.</FP>
                <FP SOURCE="FP-1">• SysArc Inc.</FP>
                <FP SOURCE="FP-1">• Tip Technologies</FP>
                <FP SOURCE="FP-1">• Virgin Orbit Holdings, Inc.</FP>
                <P>3. Change in names or addresses for the following Members:</P>
                <FP SOURCE="FP-1">• ATI Defense of Pittsburgh, PA is now ATI Inc. located in Dallas, TX.</FP>
                <FP SOURCE="FP-1">• AUSCO, Inc. of Port Washington, NY is now located in Farmingdale, NY.</FP>
                <FP SOURCE="FP-1">• Exosonic, Inc. of Los Angeles, CA is now located in Torrance, CA</FP>
                <FP SOURCE="FP-1">
                    • General Electric Aviation of Cincinnati, OH is now GE Aerospace at the same location.
                    <PRTPAGE P="1881"/>
                </FP>
                <FP SOURCE="FP-1">• Parker Meggitt USA Inc. of Simi Valley, CA is now Parker Aerospace at the same location.</FP>
                <FP SOURCE="FP-1">• Raytheon Technologies Corporation of Arlington, VA is now RTX Corporation at the same location.</FP>
                <FP SOURCE="FP-1">• Securitas Critical Information Services, Inc. of Springfield, VA is now located in Herndon, VA.</FP>
                <FP SOURCE="FP-1">• Sierra Space Corporation of Broomfield, CO is now Sierra Nevada Corporation located in Sparks, NV.</FP>
                <FP SOURCE="FP-1">• Verify, Inc. of Irvine, CA is now located in Costa Mesa, CA.</FP>
                <P>AIA's proposed amendment of its Export Trade Certificate of Review would result in the following membership list:</P>
                <FP SOURCE="FP-1">• 3M Company; St. Paul, MN</FP>
                <FP SOURCE="FP-1">• AAR Corp.; Wood Dale, IL</FP>
                <FP SOURCE="FP-1">• Accenture; Chicago, IL</FP>
                <FP SOURCE="FP-1">• Acorn Growth Companies, LLC; Oklahoma City, OK</FP>
                <FP SOURCE="FP-1">• Acutec Precision Aerospace, Inc.; Meadville, PA</FP>
                <FP SOURCE="FP-1">• ACUTRONIC USA, Inc.; Pittsburgh, PA</FP>
                <FP SOURCE="FP-1">• ADI American Distributors LLC; Randolph, NJ</FP>
                <FP SOURCE="FP-1">• Advanced Logistics for Aerospace (ALA); Bethpage, NY</FP>
                <FP SOURCE="FP-1">• AeroMed Group; Charlotte, NC</FP>
                <FP SOURCE="FP-1">• Aero-Mark, LLC; Ontario, CA</FP>
                <FP SOURCE="FP-1">• AeroVironment, Inc.; Arlington, VA</FP>
                <FP SOURCE="FP-1">• Aireon LLC; McLean, VA</FP>
                <FP SOURCE="FP-1">• Albany Engineered Composites; Rochester, NH</FP>
                <FP SOURCE="FP-1">• AlixPartners, LLP; New York, NY</FP>
                <FP SOURCE="FP-1">• Allied Telesis, Inc.; Bothell, WA</FP>
                <FP SOURCE="FP-1">• ALTEN Technology USA, Inc.; Troy, MI</FP>
                <FP SOURCE="FP-1">• Alvarez &amp; Marsal Holdings, LLC; New York, NY</FP>
                <FP SOURCE="FP-1">• Amazon.com Inc.; Seattle, WA</FP>
                <FP SOURCE="FP-1">• American Pacific Corporation; Cedar City, UT</FP>
                <FP SOURCE="FP-1">• Ansys, Inc.; Canonsburg, PA</FP>
                <FP SOURCE="FP-1">• Applied Composites; Lake Forest, CA</FP>
                <FP SOURCE="FP-1">• Archer Aviation Inc.; Palo Alto, CA</FP>
                <FP SOURCE="FP-1">• Astronautics Corporation of America; Oak Hill, WI</FP>
                <FP SOURCE="FP-1">• Astroscale U.S. Inc.; Denver, CO</FP>
                <FP SOURCE="FP-1">• AT Kearney Public Sector and Defense Services; Arlington, VA</FP>
                <FP SOURCE="FP-1">• Athena Manufacturing, LP; Austin, TX</FP>
                <FP SOURCE="FP-1">• ATI Inc.; Dallas, TX</FP>
                <FP SOURCE="FP-1">• ATLAS Space Operations, Inc.; Traverse City, MI</FP>
                <FP SOURCE="FP-1">• Aura Network Systems, Inc.; McLean, VA</FP>
                <FP SOURCE="FP-1">• AUSCO, Inc.; Farmingdale, NY</FP>
                <FP SOURCE="FP-1">• Aviation Management Associates, Inc.; Washington, DC</FP>
                <FP SOURCE="FP-1">• BAE Systems, Inc.; Falls Church, VA</FP>
                <FP SOURCE="FP-1">• Bain &amp; Company, Inc.; Boston, MA</FP>
                <FP SOURCE="FP-1">• Ball Aerospace &amp; Technologies Corp.; Boulder, CO</FP>
                <FP SOURCE="FP-1">• Belcan Corporation; Cincinnati, OH</FP>
                <FP SOURCE="FP-1">• Beta Technologies; South Burlington, VT</FP>
                <FP SOURCE="FP-1">• BlackSky Technology Inc.; Herndon, VA</FP>
                <FP SOURCE="FP-1">• Boom Technology, Inc.; Denver, CO</FP>
                <FP SOURCE="FP-1">• Booz Allen Hamilton; McClean, VA</FP>
                <FP SOURCE="FP-1">• Boston Consulting Group; Boston, MA</FP>
                <FP SOURCE="FP-1">• BRPH Architects Engineers, Inc.; Melbourne, FL</FP>
                <FP SOURCE="FP-1">• Burns &amp; McDonnell Engineering Corporation, Inc.; Kansas City, MO</FP>
                <FP SOURCE="FP-1">• BWX Technologies, Inc.; Lynchburg, VA</FP>
                <FP SOURCE="FP-1">• CADENAS PARTsolutions, LLC; Cincinnati, OH</FP>
                <FP SOURCE="FP-1">• Cadence Design Systems, Inc.; San Jose, CA</FP>
                <FP SOURCE="FP-1">• Capewell Aerial Systems; South Windsor, CT</FP>
                <FP SOURCE="FP-1">• Capgemini; New York, NY</FP>
                <FP SOURCE="FP-1">• Celestica Inc.; Toronto, Canada</FP>
                <FP SOURCE="FP-1">• Chicago Precision, Inc.; Elk Grove Village, IL</FP>
                <FP SOURCE="FP-1">• Click Bond, Inc.; Carson City, NV</FP>
                <FP SOURCE="FP-1">• Cobham Advanced Electronic Solutions (CAES); Arlington, VA</FP>
                <FP SOURCE="FP-1">• COMSPOC Corporation; Exton, PA</FP>
                <FP SOURCE="FP-1">• CPI Aerostructures, Inc.; Edgewood, NY</FP>
                <FP SOURCE="FP-1">• Crane Aerospace &amp; Electronics; Lynnwood, WA</FP>
                <FP SOURCE="FP-1">• Cre8tive Technology and Design, Inc.; San Diego, CA</FP>
                <FP SOURCE="FP-1">• Deloitte Consulting LLP; New York, NY</FP>
                <FP SOURCE="FP-1">• Deltek, Inc.; Herndon, VA</FP>
                <FP SOURCE="FP-1">• Ducommun Incorporated; Santa Ana, CA</FP>
                <FP SOURCE="FP-1">• DXC Technology Company, Ashburn, VA</FP>
                <FP SOURCE="FP-1">• Eaton Corporation; Cleveland, OH</FP>
                <FP SOURCE="FP-1">• Elbit Systems of America, LLC; Fort Worth, TX</FP>
                <FP SOURCE="FP-1">• Electra.aero; Manassas, VA</FP>
                <FP SOURCE="FP-1">• Embraer Aircraft Holding Inc.; Fort Lauderdale, FL</FP>
                <FP SOURCE="FP-1">• Enjet Aero, LLC; Overland Park, KS</FP>
                <FP SOURCE="FP-1">• Epirus, Inc.; Los Angeles, CA</FP>
                <FP SOURCE="FP-1">• EPS Corporation; Tinton Falls, NJ</FP>
                <FP SOURCE="FP-1">• Ernst &amp; Young LLP; New York, NY</FP>
                <FP SOURCE="FP-1">• Estes Energetics; Penrose, CO</FP>
                <FP SOURCE="FP-1">• ExoAnalytic Solutions Inc.; Foothill Ranch, CA</FP>
                <FP SOURCE="FP-1">• Exosonic, Inc.; Torrance, CA</FP>
                <FP SOURCE="FP-1">• Exostar LLC; Herndon, VA</FP>
                <FP SOURCE="FP-1">• FTG Circuits, Inc.; Chatsworth, CA</FP>
                <FP SOURCE="FP-1">• GE Aerospace; Cincinnati, OH</FP>
                <FP SOURCE="FP-1">• General Atomics Aeronautical Systems, Inc.; Poway, CA</FP>
                <FP SOURCE="FP-1">• General Dynamics Corporation; Reston, VA</FP>
                <FP SOURCE="FP-1">• GKN Aerospace North America; Westlake, TX</FP>
                <FP SOURCE="FP-1">• Google, LLC; Mountain View, CA</FP>
                <FP SOURCE="FP-1">• GSE Dynamics, Inc.; Hauppauge, NY</FP>
                <FP SOURCE="FP-1">• GXA Consulting LLC; Ely, IA</FP>
                <FP SOURCE="FP-1">• HCL America Inc.; Sunnyvale, CA</FP>
                <FP SOURCE="FP-1">• HEICO Corporation; Hollywood, FL</FP>
                <FP SOURCE="FP-1">• Hexcel Corporation; Stamford, CT</FP>
                <FP SOURCE="FP-1">• Honeywell Aerospace; Phoenix, AZ</FP>
                <FP SOURCE="FP-1">• Howmet Aerospace Inc.; Pittsburgh, PA</FP>
                <FP SOURCE="FP-1">• Huntington Ingalls Industries, Inc.; Newport News, VA</FP>
                <FP SOURCE="FP-1">• Infosys; Richardson, TX</FP>
                <FP SOURCE="FP-1">• Interos, Inc.; Arlington, VA</FP>
                <FP SOURCE="FP-1">• Iron Mountain, Inc.; Boston, MA</FP>
                <FP SOURCE="FP-1">• Ivis Technologies, LLC; Phoenix, AZ</FP>
                <FP SOURCE="FP-1">• Jabil Defense &amp; Aerospace Services LLC; St. Petersburg, FL</FP>
                <FP SOURCE="FP-1">• Janes Capital Partners, Inc.; Irvine, CA</FP>
                <FP SOURCE="FP-1">• Joby Aviation, Inc.; Santa Cruz, CA</FP>
                <FP SOURCE="FP-1">• Kaman Corporation; Bloomfield, CT</FP>
                <FP SOURCE="FP-1">• KPMG LLP; New York, NY</FP>
                <FP SOURCE="FP-1">• Kratos Defense &amp; Security Solutions, Inc.; Round Rock, TX</FP>
                <FP SOURCE="FP-1">• L3Harris Technologies, Inc.; Melbourne, FL</FP>
                <FP SOURCE="FP-1">• Leidos, Inc; Reston, VA</FP>
                <FP SOURCE="FP-1">• LeoLabs, Inc.; Menlo Park, CA</FP>
                <FP SOURCE="FP-1">• LOAR Group; White Plains, NY</FP>
                <FP SOURCE="FP-1">• LS Technologies, LLC; Fairfax, VA</FP>
                <FP SOURCE="FP-1">• MapLarge, Inc.; Atlanta, GA</FP>
                <FP SOURCE="FP-1">• Marotta Controls, Inc.; Montville, NJ</FP>
                <FP SOURCE="FP-1">• Mercury Systems, Inc.; Andover, MA</FP>
                <FP SOURCE="FP-1">• Merlin Labs, Inc.; Boston, MA</FP>
                <FP SOURCE="FP-1">• Microchip Technology Incorporated; Chandler, AZ</FP>
                <FP SOURCE="FP-1">• National Technical Systems, Inc.; Calabasas, CA</FP>
                <FP SOURCE="FP-1">• New England Air Foil Products, Inc.; Farmington, CT</FP>
                <FP SOURCE="FP-1">• Nimbis Services, Inc.; Oro Valley, AZ</FP>
                <FP SOURCE="FP-1">• Nokia US; Murray Hill, NJ</FP>
                <FP SOURCE="FP-1">• Norsk Titanium US Inc.; Plattsburgh, NY</FP>
                <FP SOURCE="FP-1">• Northrop Grumman Corporation; Falls Church, VA</FP>
                <FP SOURCE="FP-1">• Oliver Wyman Inc.; New York, NY</FP>
                <FP SOURCE="FP-1">• O'Neil &amp; Associates, Inc.; Miamisburg, OH</FP>
                <FP SOURCE="FP-1">• Overair, Inc.; Santa Ana, CA</FP>
                <FP SOURCE="FP-1">• Pacific Forge Incorporated; Fontana, CA</FP>
                <FP SOURCE="FP-1">• Parker Aerospace; Simi Valley, CA</FP>
                <FP SOURCE="FP-1">• PCX Aerosystems; Santa Ana, CA</FP>
                <FP SOURCE="FP-1">• Perryman Company; Houston, PA</FP>
                <FP SOURCE="FP-1">• PPG Aerospace-Sierracin Corporation; Sylmar, CA</FP>
                <FP SOURCE="FP-1">• Primer AI; Arlington, VA</FP>
                <FP SOURCE="FP-1">• PWC Aerospace &amp; Defense Advisory Services; McLean, VA</FP>
                <FP SOURCE="FP-1">• RCM Technologies, Inc.; Pennsauken, NJ</FP>
                <FP SOURCE="FP-1">• RTX Corporation; Arlington, VA</FP>
                <FP SOURCE="FP-1">• Reaction Engines, Inc.; Denver, CO</FP>
                <FP SOURCE="FP-1">• Relativity Space, Inc.; Long Beach, CA</FP>
                <FP SOURCE="FP-1">• Reliable Robotics Corporation; Mountain View, CA</FP>
                <FP SOURCE="FP-1">• Rhinestahl Corporation; Mason, OH</FP>
                <FP SOURCE="FP-1">• Riveron Consulting, LLC; Dallas, TX</FP>
                <FP SOURCE="FP-1">• Rocket Lab USA, Inc.; Long Beach, CA</FP>
                <FP SOURCE="FP-1">• Rolls-Royce North America Inc.; Reston, VA</FP>
                <FP SOURCE="FP-1">• Salesforce, Inc.; San Francisco, CA</FP>
                <FP SOURCE="FP-1">
                    • SAP America, Inc.; Newtown Square, PA
                    <PRTPAGE P="1882"/>
                </FP>
                <FP SOURCE="FP-1">• Securitas Critical Infrastructure Services, Inc.; Herndon, VA</FP>
                <FP SOURCE="FP-1">• Shift5; Rosslyn, VA</FP>
                <FP SOURCE="FP-1">• SI2 Technologies; North Billerica, MA</FP>
                <FP SOURCE="FP-1">• Siemens Government Technologies, Inc.; Reston, VA</FP>
                <FP SOURCE="FP-1">• Sierra Nevada Corporation; Sparks, NV</FP>
                <FP SOURCE="FP-1">• SkyThread Corporation; Irvine, CA</FP>
                <FP SOURCE="FP-1">• Slingshot Aerospace, Inc.; Austin, TX</FP>
                <FP SOURCE="FP-1">• Solvay; Alpharetta, GA</FP>
                <FP SOURCE="FP-1">• Spartronics LLC; Williamsport, PA</FP>
                <FP SOURCE="FP-1">• Special Aerospace Services, LLC; Boulder, CO</FP>
                <FP SOURCE="FP-1">• Spirit AeroSystems; Wichita, KS</FP>
                <FP SOURCE="FP-1">• Spright; Gilbert, AZ</FP>
                <FP SOURCE="FP-1">• Stratolaunch LLC; Mojave, CA</FP>
                <FP SOURCE="FP-1">• Supernal LLC; Washington, DC</FP>
                <FP SOURCE="FP-1">• SupplyOn North America, Inc.; Greer, SC</FP>
                <FP SOURCE="FP-1">• Synergetic Technologies Group, Inc.; La Verne, CA</FP>
                <FP SOURCE="FP-1">• Tata Consultancy Services; Edison, NJ</FP>
                <FP SOURCE="FP-1">• Textron Inc.; Providence, RI</FP>
                <FP SOURCE="FP-1">• The Aerospace Corporation, Civil Systems Group; El Segundo, CA</FP>
                <FP SOURCE="FP-1">• The Boeing Company; Chicago, IL</FP>
                <FP SOURCE="FP-1">• The Haskell Company; Jacksonville, FL</FP>
                <FP SOURCE="FP-1">• The Lundquist Group LLC; New York, NY</FP>
                <FP SOURCE="FP-1">• The Padina Group, Inc.; Lancaster, PA</FP>
                <FP SOURCE="FP-1">• Therm, Incorporated; Ithaca, NY</FP>
                <FP SOURCE="FP-1">• TransDigm Group, Inc.; Cleveland, OH</FP>
                <FP SOURCE="FP-1">• Tribus Aerospace Corporation; Poway, CA</FP>
                <FP SOURCE="FP-1">• TriMas Aerospace; Irvine, CA</FP>
                <FP SOURCE="FP-1">• Triumph Group, Inc.; Berwyn, PA</FP>
                <FP SOURCE="FP-1">• True Anomaly; Centennial, CO</FP>
                <FP SOURCE="FP-1">• TTM Technologies Inc.; Santa Ana, CA</FP>
                <FP SOURCE="FP-1">• Umbra Lab, Inc.; Santa Barbara, CA</FP>
                <FP SOURCE="FP-1">• Unitech Composites Inc.; Hayden, ID</FP>
                <FP SOURCE="FP-1">• United Launch Alliance; Centennial, CO</FP>
                <FP SOURCE="FP-1">• Ursa Major Technologies, Inc.; Berthoud, CO</FP>
                <FP SOURCE="FP-1">• Verify, Inc.; Costa Mesa, CA</FP>
                <FP SOURCE="FP-1">• VIASAT, INC.; Carlsbad, CA</FP>
                <FP SOURCE="FP-1">• Virgin Galactic, LLC; Las Cruces, NM</FP>
                <FP SOURCE="FP-1">• Weldaloy Specialty Forgings; Warren, MI</FP>
                <FP SOURCE="FP-1">• Westinghouse Electric Company LLC; Cranberry Township, PA</FP>
                <FP SOURCE="FP-1">• Wisk Aero LLC; Mountain View, CA</FP>
                <FP SOURCE="FP-1">• Woodward, Inc.; Fort Collins, CO</FP>
                <FP SOURCE="FP-1">• World View Enterprises, Inc.; Tucson, AZ</FP>
                <SIG>
                    <DATED>Dated: January 5, 2024.</DATED>
                    <NAME>Joseph Flynn,</NAME>
                    <TITLE>Director, Office of Trade and Economic Analysis, International Trade Administration, U.S. Department of Commerce.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00367 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DR-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>International Trade Administration</SUBAGY>
                <DEPDOC>[A-428-844]</DEPDOC>
                <SUBJECT>Certain Carbon and Alloy Steel Cut-to-Length Plate From the Federal Republic of Germany: Notice of Court Decision Not in Harmony With the Amended Final Determination of Antidumping Investigation; Notice of Second 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 December 21, 2023, the U.S. Court of International Trade (CIT) issued its final judgment in 
                        <E T="03">AG der Dillinger Hüttenwerke</E>
                         v. 
                        <E T="03">United States,</E>
                         Court No. 17-00158, sustaining the U.S. Department of Commerce's (Commerce) fourth final results of redetermination pertaining to the antidumping duty (AD) investigation of certain carbon and alloy steel cut-to-length plate (CTL plate) from the Federal Republic of Germany (Germany) covering the period April 1, 2015, through March 31, 2016. Commerce is notifying the public that the CIT's final judgment is not in harmony with Commerce's amended final determination and Commerce is amending the amended final determination with respect to the dumping margins assigned to AG Der Dillinger Hüttenwerke (Dillinger) and all other producers and exporters of subject merchandise.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Applicable December 31, 2023.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Adam Simons, AD/CVD Operations, Office IX, Enforcement and Compliance, International Trade Administration, U.S. Department of Commerce, 1401 Constitution Avenue NW, Washington, DC 20230; telephone: (202) 482-6172.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On April 4, 2017, Commerce published its final determination in the AD investigation of CTL plate from Germany.
                    <SU>1</SU>
                    <FTREF/>
                     After correcting ministerial errors in the 
                    <E T="03">Final Determination,</E>
                     on May 25, 2017, Commerce published the 
                    <E T="03">Amended Final Determination,</E>
                     calculating estimated weighted-average dumping margins of: 5.52 percent for Dillinger; 22.90 percent for Ilsenburger Grobblech GmbH, Salzgitter Mannesmann Grobblech GmbH, Salzgitter Flachstahl GmbH, and Salzgitter Mannesmann International GmbH (collectively, Salzgitter); and 21.04 percent for all other producers and exporters.
                    <SU>2</SU>
                    <FTREF/>
                     In this same notice, Commerce published its AD order on CTL plate from Germany.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See Certain Carbon and Alloy Steel Cut-to-Length Plate from the Federal Republic of Germany: Final Determination of Sales at Less Than Fair Value,</E>
                         82 FR 16360 (April 4, 2017) (
                        <E T="03">Final Determination</E>
                        ).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See Certain Carbon and Alloy Steel Cut-to-Length Plate from Austria, Belgium, France, the Federal Republic of Germany, Italy, Japan, the Republic of Korea, and Taiwan: Amended Final Affirmative Antidumping Determinations for France, the Federal Republic of Germany, the Republic of Korea and Taiwan, and Antidumping Duty Orders,</E>
                         82 FR 24096 (May 25, 2017) (
                        <E T="03">Amended Final Determination</E>
                        ).
                    </P>
                </FTNT>
                <P>
                    Dillinger and Salzgitter appealed Commerce's 
                    <E T="03">Amended Final Determination.</E>
                     On July 16, 2019, the CIT remanded to Commerce to reconsider its application of partial adverse facts available (AFA) to certain downstream home market sales reported by Dillinger.
                    <SU>3</SU>
                    <FTREF/>
                     Pursuant to 
                    <E T="03">Dillinger Germany I,</E>
                     Commerce reconsidered how it applied partial AFA to these sales.
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See AG der Dillinger Hüttenwerke</E>
                         v. 
                        <E T="03">United States,</E>
                         399 F. Supp. 3d 1247 (CIT 2019) (
                        <E T="03">Dillinger Germany I</E>
                        ).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See Final Results of Redetermination Pursuant to Court Remand, Certain Carbon and Alloy Steel Cut-to-Length Plate from Germany,</E>
                         Court No. 17-00158, Slip Op. 19-87 (CIT July 16, 2019), dated October 8, 2019, available at 
                        <E T="03">https://access.trade.gov/resources/remands/index.html.</E>
                    </P>
                </FTNT>
                <P>
                    On August 18, 2021, in 
                    <E T="03">Dillinger Germany II,</E>
                     the CIT remanded to Commerce to consider its reallocation of costs between prime and non-prime steel plate for Dillinger, among other Dillinger cost issues, as well as the application of a partial AFA methodology to certain downstream home market sales reported by Salzgitter.
                    <SU>5</SU>
                    <FTREF/>
                     In parallel with 
                    <E T="03">Dillinger Germany II,</E>
                     the CIT issued a separate memorandum and order sustaining Commerce's rejection of Dillinger's proposed quality code for sour service pressure vessel plate and staying Dillinger's challenge to Commerce's rejection of the proposed quality code for sour service petroleum transport plate pending the outcome of the cost issues on remand.
                    <SU>6</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See AG der Dillinger Hüttenwerke</E>
                         v. 
                        <E T="03">United States,</E>
                         534 F. Supp. 3d 1403 (CIT 2021) (
                        <E T="03">Dillinger Germany II</E>
                        ).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See Memorandum and Order,</E>
                         ECF No. 121 (August 18, 2021).
                    </P>
                </FTNT>
                <P>
                    On September 23, 2022, in 
                    <E T="03">Dillinger Germany III,</E>
                     the CIT remanded to Commerce to again reconsider its selection of the facts otherwise available for determining the cost of production of Dillinger's non-prime products.
                    <SU>7</SU>
                    <FTREF/>
                     On June 23, 2023, in 
                    <E T="03">Dillinger Germany IV,</E>
                     the CIT sustained Commerce's determination to assign the “likely 
                    <PRTPAGE P="1883"/>
                    selling price” recorded Dillinger's books and records as the cost of production for non-prime plate and the application of partial AFA to Salzgittter.
                    <SU>8</SU>
                    <FTREF/>
                     However, the CIT remanded Commerce's model-match methodology, related specifically to Commerce's rejection of Dillinger's proposed quality code for sour service petroleum transport plate, for further explanation or, if appropriate, reconsideration in light of Commerce's approach in 
                    <E T="03">Bohler.</E>
                    <SU>9</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See AG der Dillinger Hüttenwerke</E>
                         v. 
                        <E T="03">United States,</E>
                         592 F. Supp. 3d 1344 (CIT 2022) (
                        <E T="03">Dillinger Germany III</E>
                        ).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See AG der Dillinger Hüttenwerke</E>
                         v. 
                        <E T="03">United States,</E>
                         Court No. 17-00158, Slip Op. 23-94 (CIT 2023) (
                        <E T="03">Dillinger Germany IV</E>
                        ).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See Dillinger Germany IV,</E>
                         Court No. 17-00158, Slip Op. 23-94 at 4 and 25; 
                        <E T="03">see also Bohler Bleche GMBH &amp; Co.</E>
                          
                        <E T="03">KG</E>
                         v. 
                        <E T="03">United States,</E>
                         324 F. Supp. 3d 1344 (CIT 2018) (
                        <E T="03">Bohler</E>
                        ).
                    </P>
                </FTNT>
                <P>
                    In its final results of redetermination, issued on September 6, 2023, Commerce reconsidered its rejection of Dillinger's proposed quality code for sour service petroleum transport plate and included this quality code in the control numbers used in Dillinger's margin calculations.
                    <SU>10</SU>
                    <FTREF/>
                     As a result of this change, Dillinger's final estimated weighted-average dumping margin became 4.99 percent. The CIT sustained Commerce's final results of redetermination.
                    <SU>11</SU>
                    <FTREF/>
                     While this revision to Dillinger's margin did not affect the calculation of the all-others rate, Commerce revised the all-others rate to be 20.99 percent in the 
                    <E T="03">Second Remand Redetermination.</E>
                    <SU>12</SU>
                    <FTREF/>
                     The CIT sustained this aspect of Commerce's redetermination.
                    <SU>13</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See Final Results of Redetermination Pursuant to Court Remand; Certain Carbon and Alloy Steel Cut-to-Length Plate from Germany,</E>
                         Court No. 17-00158, Slip Op. 23-94 (CIT June 23, 2023), dated September 6, 2023, available at 
                        <E T="03">https://access.trade.gov/resources/remands/index.html.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See AG Der Dillinger Hüttenwerke,</E>
                         v. 
                        <E T="03">United States,</E>
                         Court No. 17-00158, Slip Op. 23-187 (CIT 2023).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">See Final Results of Redetermination Pursuant to Court Remand; Certain Carbon and Alloy Steel Cut-to-Length Plate from Germany,</E>
                         Court No. 17-00158, Slip. Op. 21-101 (CIT August 18, 2021), dated January 19, 2022 (
                        <E T="03">Second Remand Redetermination</E>
                        ), available at 
                        <E T="03">https://access.trade.gov/resources/remands/index.html.</E>
                         As a result of this redetermination, Commerce reinstated the dumping margin for Salzgitter of 22.90 percent calculated in the 
                        <E T="03">Amended Final Determination.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See Dillinger Germany III.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Timken Notice</HD>
                <P>
                    In its decision in 
                    <E T="03">Timken,</E>
                    <SU>14</SU>
                    <FTREF/>
                     as clarified by 
                    <E T="03">Diamond Sawblades,</E>
                    <SU>15</SU>
                    <FTREF/>
                     the U.S. Court of Appeals for the Federal Circuit held that, pursuant to section 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 December 21, 2023, judgment constitutes a final decision of the CIT that is not in harmony with Commerce's 
                    <E T="03">Amended Final Determination.</E>
                     Thus, this notice is published in fulfillment of the publication requirements of 
                    <E T="03">Timken.</E>
                </P>
                <FTNT>
                    <P>
                        <SU>14</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>15</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</HD>
                <P>
                    Because there is now a final court judgment, Commerce is amending its 
                    <E T="03">Amended Final Determination</E>
                     with respect to Dillinger and all other producers and/or exporters as follows:
                </P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s25,9">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Producer/exporter</CHED>
                        <CHED H="1">
                            Weighted-
                            <LI>average</LI>
                            <LI>dumping</LI>
                            <LI>margin</LI>
                            <LI>(percent)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">AG Der Dillinger Hüttenwerke</ENT>
                        <ENT>4.99</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">All Others</ENT>
                        <ENT>20.99</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Cash Deposit Requirements</HD>
                <P>
                    Because Dillinger has a superseding cash deposit rate, 
                    <E T="03">i.e.,</E>
                     there have been final results published in a subsequent administrative review, we will not issue revised cash deposit instructions to U.S. Customs and Border Protection (CBP). This notice will not affect the current cash deposit rate. For all other producers and exporters, Commerce will issue revised cash 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: January 5, 2024.</DATED>
                    <NAME>Abdelali Elouaradia,</NAME>
                    <TITLE>Deputy Assistant Secretary for Enforcement and Compliance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00398 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>International Trade Administration</SUBAGY>
                <DEPDOC>[A-552-802, A-533-840, A-570-893, A-549-822]</DEPDOC>
                <SUBJECT>Certain Frozen Warmwater Shrimp From the People's Republic of China, India, Thailand, and the Socialist Republic of Vietnam: Continuation of Antidumping Duty Orders; Correction</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Enforcement and Compliance, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; correction.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In the 
                        <E T="04">Federal Register</E>
                         of July 5, 2023, the U.S. Department of Commerce (Commerce) published a notice of continuation of the antidumping duty (AD) orders on certain frozen warmwater shrimp from the People's Republic of China (China), India, Thailand, and the Socialist Republic of Vietnam (Vietnam). This notice contained an incorrect scope of the orders.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Andrew Hart, 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-1058.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Correction</HD>
                <P>
                    In the 
                    <E T="04">Federal Register</E>
                     of July 5, 2023, in FR Doc 2023-14181, on page 42915 in the first and second columns, correct the scope of the orders to state: “The scope of the orders includes certain frozen warmwater shrimp and prawns, whether wild caught (ocean harvested) or farm raised (produced by aquaculture), head on or head off, shell on or peeled, tail on or tail off,
                    <SU>1</SU>
                    <FTREF/>
                     deveined or not deveined, cooked or raw, or otherwise processed in frozen form.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         “Tails” in this context means the tail fan, which includes the telson and the uropods.
                    </P>
                </FTNT>
                <P>The frozen warmwater shrimp and prawn products included in the scope of the orders, regardless of definitions in the Harmonized Tariff Schedule of the United States (HTSUS), are products which are processed from warmwater shrimp and prawns through freezing and which are sold in any count size.</P>
                <P>
                    The products described above may be processed from any species of warmwater shrimp and prawns. Warmwater shrimp and prawns are generally classified in, but are not limited to, the 
                    <E T="03">Penaeidae</E>
                     family. Some examples of the farmed and wild-caught warmwater species include, but are not limited to, white-leg shrimp (
                    <E T="03">Penaeus vannemei</E>
                    ), banana prawn (
                    <E T="03">Penaeus merguiensis</E>
                    ), fleshy prawn (
                    <E T="03">Penaeus chinensis</E>
                    ), giant river prawn (
                    <E T="03">Macrobrachium rosenbergii</E>
                    ), giant tiger prawn (
                    <E T="03">Penaeus monodon</E>
                    ), redspotted shrimp (
                    <E T="03">Penaeus brasiliensis</E>
                    ), southern brown shrimp (
                    <E T="03">Penaeus subtilis</E>
                    ), southern pink shrimp (
                    <E T="03">Penaeus notialis</E>
                    ), southern rough shrimp (
                    <E T="03">Trachypenaeus curvirostris</E>
                    ), southern white shrimp (
                    <E T="03">Penaeus schmitti</E>
                    ), blue shrimp (
                    <E T="03">Penaeus stylirostris</E>
                    ), western white shrimp (
                    <E T="03">Penaeus occidentalis</E>
                    ), and Indian white prawn (
                    <E T="03">Penaeus indicus</E>
                    ).
                    <PRTPAGE P="1884"/>
                </P>
                <P>Frozen shrimp and prawns that are packed with marinade, spices or sauce are included in the scope of the orders. In addition, food preparations, which are not “prepared meals,” that contain more than 20 percent by weight of shrimp or prawn are also included in the scope of the orders.</P>
                <P>
                    Excluded from the scope are: (1) breaded shrimp and prawns (HTSUS subheading 1605.20.1020); (2) shrimp and prawns generally classified in the 
                    <E T="03">Pandalidae</E>
                     family and commonly referred to as coldwater shrimp, in any state of processing; (3) fresh shrimp and prawns whether shell on or peeled (HTSUS subheadings 0306.23.0020 and 0306.23.0040); (4) shrimp and prawns in prepared meals (HTSUS subheading 1605.20.0510); (5) dried shrimp and prawns; (6) Lee Kum Kee's shrimp sauce; 
                    <SU>2</SU>
                    <FTREF/>
                     (7) canned warmwater shrimp and prawns (HTSUS subheading 1605.20.1040); and (8) certain battered shrimp. Battered shrimp is a shrimp-based product: (1) that is produced from fresh (or thawed-from-frozen) and peeled shrimp; (2) to which a “dusting” layer of rice or wheat flour of at least 95 percent purity has been applied; (3) with the entire surface of the shrimp flesh thoroughly and evenly coated with the flour; (4) with the non-shrimp content of the end product constituting between four and 10 percent of the product's total weight after being dusted, but prior to being frozen; and (5) that is subjected to individually quick frozen (“IQF”) freezing immediately after application of the dusting layer. When dusted in accordance with the definition of dusting above, the battered shrimp product is also coated with a wet viscous layer containing egg and/or milk, and par-fried.
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         The specific exclusion for Lee Kum Kee's shrimp sauce applies only to the scope of the AD order on certain frozen warmwater shrimp from China.
                    </P>
                </FTNT>
                <P>
                    The products covered by the orders are currently classified under the following HTSUS subheadings: 0306.17.00.03, 0306.17.00.06, 0306.17.00.09, 0306.17.00.12, 0306.17.00.15, 0306.17.00.18, 0306.17.00.21, 0306.17.00.24, 0306.17.00.27, 0306.17.00.40, 1605.21.10.30, 1605.29.10.10, 0306.17.0004, 0306.17.0005, 0306.17.0007, 0306.17.0008, 0306.17.0010, 0306.17.0011, 0306.17.0013, 0306.17.0014, 0306.17.0016, 0306.17.0017, 0306.17.0019, 0306.17.0020, 0306.17.0022, 0306.17.0023, 0306.17.0025, 0306.17.0026, 0306.17.0028, 0306.17.0029, 0306.17.0041, 0306.17.0042. These HTSUS subheadings are provided for convenience and for customs purposes only; the written description of the scope of the orders are dispositive.” 
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         On April 26, 2011, Commerce amended the orders to include dusted shrimp, pursuant to the Court decision in 
                        <E T="03">Ad Hoc Shrimp Trade Action Committee</E>
                         v. 
                        <E T="03">United States,</E>
                         703 F. Supp. 2d 1330 (CIT 2010) and the U.S. International Trade Commission determination, which found the domestic like product to include dusted shrimp. 
                        <E T="03">See Certain Frozen Warmwater Shrimp from Brazil, India, the People's Republic of China, Thailand, and the Socialist Republic of Vietnam: Amended Antidumping Duty Orders in Accordance with Final Court Decision,</E>
                         76 FR 23277 (April 26, 2011); 
                        <E T="03">see also Frozen Warmwater Shrimp from Brazil, China, India, Thailand, and Vietnam,</E>
                         Inv. Nos. 731-TA1063, 1064, 1066-1068 (Review), USITC Pub. 4221 (March 2011).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On July 5, 2023, Commerce published in the 
                    <E T="04">Federal Register</E>
                     the continuation of the orders for certain frozen warmwater shrimp from China, India, Thailand, and Vietnam.
                    <SU>4</SU>
                    <FTREF/>
                     We inadvertently included the wrong scope of the orders.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See Certain Frozen Warmwater Shrimp from the People's Republic of China, India, Thailand, and the Socialist Republic of Vietnam: Continuation of Antidumping Duty Orders,</E>
                         88 FR 42914 (July 5, 2023).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Notification to Interested Parties</HD>
                <P>This notice is issued and published in accordance with sections 751(c), 751(d)(2), and 777(i) of the Tariff Act of 1930, as amended, and 19 CFR 351.218(f)(4).</P>
                <SIG>
                    <DATED>Dated: January 5, 2024.</DATED>
                    <NAME>Abdelali Elouaradia,</NAME>
                    <TITLE>Deputy Assistant Secretary for Enforcement and Compliance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00396 Filed 1-10-24; 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>
                <DEPDOC>[RTID 0648-XD574]</DEPDOC>
                <SUBJECT>Takes of Marine Mammals Incidental to Specified Activities; Taking Marine Mammals Incidental to Sitka Seaplane Base Construction</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; proposed incidental harassment authorizations; request for comments on proposed authorizations and possible renewals.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>NMFS has received a request from the City and Borough of Sitka (CBS) for authorization to take marine mammals incidental to Sitka seaplane base construction activities over two years in Sitka, Alaska. Pursuant to the Marine Mammal Protection Act (MMPA), NMFS is requesting comments on its proposal to issue two incidental harassment authorizations (IHA) to incidentally take marine mammals during the specified activities. NMFS is also requesting comments on possible one-time, 1-year renewals for each IHA that could be issued under certain circumstances and if all requirements are met, as described in Request for Public Comments at the end of this notice. NMFS will consider public comments prior to making any final decision on the issuance of the requested MMPA authorizations and agency responses will be summarized in the final notice of our decision.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments and information must be received no later than February 12, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments should be addressed to Jolie Harrison, Chief, Permits and Conservation Division, Office of Protected Resources, National Marine Fisheries Service and should be submitted via email to 
                        <E T="03">ITP.harlacher@noaa.gov.</E>
                         Electronic copies of the application and supporting documents, as well as a list of the references cited in this document, may be obtained online at: 
                        <E T="03">https://www.fisheries.noaa.gov/national/marine-mammal-protection/incidental-take-authorizations-construction-activities.</E>
                         In case of problems accessing these documents, please call the contact listed above.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         NMFS is not responsible for comments sent by any other method, to any other address or individual, or received after the end of the comment period. Comments, including all attachments, must not exceed a 25-megabyte file size. All comments received are a part of the public record and will generally be posted online at 
                        <E T="03">https://www.fisheries.noaa.gov/national/marine-mammal-protection/incidental-take-authorizations-construction-activities</E>
                         without change. All personal identifying information (
                        <E T="03">e.g.,</E>
                         name, address) voluntarily submitted by the commenter may be publicly accessible. Do not submit confidential business information or otherwise sensitive or protected information.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Jenna Harlacher, Office of Protected Resources, NMFS, (301) 427-8401.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">
                    SUPPLEMENTARY INFORMATION:
                    <PRTPAGE P="1885"/>
                </HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    The MMPA prohibits the “take” of marine mammals, with certain exceptions. Sections 101(a)(5)(A) and (D) of the MMPA (16 U.S.C. 1361 
                    <E T="03">et seq.</E>
                    ) direct the Secretary of Commerce (as delegated to NMFS) to allow, upon request, the incidental, but not intentional, taking of small numbers of marine mammals by U.S. citizens who engage in a specified activity (other than commercial fishing) within a specified geographical region if certain findings are made and either regulations are proposed or, if the taking is limited to harassment, a notice of a proposed IHA is provided to the public for review.
                </P>
                <P>Authorization for incidental takings shall be granted if NMFS finds that the taking will have a negligible impact on the species or stock(s) and will not have an unmitigable adverse impact on the availability of the species or stock(s) for taking for subsistence uses (where relevant). Further, NMFS must prescribe the permissible methods of taking and other “means of effecting the least practicable adverse impact” on the affected species or stocks and their habitat, paying particular attention to rookeries, mating grounds, and areas of similar significance, and on the availability of the species or stocks for taking for certain subsistence uses (referred to in shorthand as “mitigation”); and requirements pertaining to the mitigation, monitoring and reporting of the takings are set forth. The definitions of all applicable MMPA statutory terms cited above are included in the relevant sections below.</P>
                <HD SOURCE="HD1">National Environmental Policy Act</HD>
                <P>
                    To comply with the National Environmental Policy Act of 1969 (NEPA; 42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ) and NOAA Administrative Order (NAO) 216-6A, NMFS must review our proposed action (
                    <E T="03">i.e.,</E>
                     the issuance of an IHA) with respect to potential impacts on the human environment.
                </P>
                <P>This action is consistent with categories of activities identified in Categorical Exclusion B4 (IHAs with no anticipated serious injury or mortality) of the Companion Manual for NAO 216-6A, which do not individually or cumulatively have the potential for significant impacts on the quality of the human environment and for which we have not identified any extraordinary circumstances that would preclude this categorical exclusion. Accordingly, NMFS has preliminarily determined that the issuance of the proposed IHA qualifies to be categorically excluded from further NEPA review. We will review all comments submitted in response to this notice prior to concluding our NEPA process or making a final decision on the IHA request.</P>
                <HD SOURCE="HD1">Summary of Request</HD>
                <P>On September 1, 2023, NMFS received a request from CBS for two IHAs to take marine mammals incidental to the Sitka seaplane base construction project in Sitka, Alaska, over the course of two years. Following NMFS' review of the application and a revised version, CBS submitted a final version on November 15, 2023. The application was deemed adequate and complete on December 1, 2023. For both IHAs, CBS's request is for take of seven species of marine mammals by Level B harassment and, for a subset of three of these species, Level A harassment. Neither CBS nor NMFS expect serious injury or mortality to result from this activity and, therefore, IHAs are appropriate.</P>
                <HD SOURCE="HD1">Description of Proposed Activity</HD>
                <HD SOURCE="HD2">Overview</HD>
                <P>CBS proposes to replace the existing seaplane base in the Sitka Channel in Sitka, Alaska. The purpose of this project is to construct a new seaplane base, which would address existing capacity, safety, and condition deficiencies for critical seaplane operations, and for all seaplanes to transit the Sitka Chanel more safely. The proposed location of the new seaplane base in the Sitka Channel is located on the northern shore of Japonski Island in the Sitka Sound. Over the course of 2 years spanning July 2024-June 2025 and July 2025-June 2026, CBS would use a variety of methods, including vibratory and impact pile driving, and down-the-hole (DTH) drilling to install and remove piles. These methods of pile driving would introduce underwater sounds that may result in take, by Level A and Level B harassment, of marine mammals.</P>
                <HD SOURCE="HD2">Dates and Duration</HD>
                <P>CBS anticipates that the seaplane base construction project would occur over 2 years (phases). The in-water work window would last from July 2024 to June 2025 (Phase I) and July 2025 to June 2026 (Phase II). Pile driving and removal activities are anticipated to take 45 hours over 31 days in Phase I and 13 hours over 9 days in Phase II. All in-water pile driving would be completed during daylight hours. The Phase I IHA would be valid from July 1, 2024 to June 30, 2025, and the Phase II IHA would be valid from July 1, 2025 to June 30, 2026.</P>
                <HD SOURCE="HD2">Specific Geographic Region</HD>
                <P>The CBS seaplane base is located on the northern shore of Japonski Island in the Sitka Channel. Sitka Channel separates Japonski Island from Sitka Harbor and downtown Sitka on the much larger Baranof Island. The Sitka Channel is located on the eastern shore of Sitka Sound, west of Crescent Bay and adjacent to Whiting Harbor. Sitka Channel is bookended by the Channel Rock Breakwaters to the north and James O'Connell Bridge to the south. Sitka Channel is approximately 150 feet (ft) (46 meters (m)) wide and about 22 ft (6.7 m) deep at its narrowest.</P>
                <GPH SPAN="3" DEEP="304">
                    <PRTPAGE P="1886"/>
                    <GID>EN11JA24.000</GID>
                </GPH>
                <HD SOURCE="HD1">Figure 1—Project Location</HD>
                <HD SOURCE="HD2">Detailed Description of the Specified Activity</HD>
                <P>The purpose of the proposed project is to replace the existing seaplane base in Sitka that has come to the end of its useful life and has several shortcomings, including limited docking capacity. The existing facility is expensive to maintain, has wildlife conflicts with a nearby seafood processing plant, and requires pilots to navigate a busy channel with heavy ship traffic. The new seaplane base would improve safety of seaplane operations by reducing traffic and congestion in Sitka Channel. The proposed project would consist of several components including in-water and landside construction, completed over two phases. All components of landside construction would not cause harassment of marine mammals and are not discussed further.</P>
                <P>Phase I would involve the installation and removal of temporary piles, and the installation of permanent piles. During Phase I, 10 16-inch (in, 0.4 m) and 16 24-in (0.6 m) permanent steel piles would be installed. The installation and removal of 12 temporary 16-in (0.4 m) steel pipe piles would be completed to support permanent pile installation. Vibratory hammers, impact hammers, and DTH drilling would be used for the installation and removal of the piles (table 1). The installation and removal of temporary piles would be conducted using impact and vibratory hammers. All permanent piles would be initially installed with a vibratory hammer. After vibratory driving, piles would be socketed into the bedrock with DTH drilling equipment. Finally, piles would be driven the final few inches of embedment with an impact hammer.</P>
                <P>Phase II similarly would involve the installation and removal of temporary piles, and the installation of permanent piles. During Phase II six 24-in (0.6 m) steel piles would be installed. The installation and removal of six temporary 16-in (0.4 m) steel pipe piles would be completed to support the permanent pile installation. As in Phase I, vibratory hammers, impact hammers, and DTH drilling would be used for the installation and removal of the piles (table 2). The installation and removal of temporary piles would be conducted using impact and vibratory hammers. All permanent piles would be initially installed with a vibratory hammer. After vibratory driving, piles would be socketed into the bedrock with DTH drilling equipment. Finally, piles would be driven the final few inches of embedment with an impact hammer.</P>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s50,12,12,12,12">
                    <TTITLE>Table 1—Phase 1 Project Pile Installation and Removal Summary</TTITLE>
                    <BOXHD>
                        <CHED H="1">Project component</CHED>
                        <CHED H="1">
                            Temp install
                            <LI>(16-in)</LI>
                        </CHED>
                        <CHED H="1">
                            Temp remove
                            <LI>(16-in)</LI>
                        </CHED>
                        <CHED H="1">
                            Perm install
                            <LI>(16-in)</LI>
                        </CHED>
                        <CHED H="1">Perm Install (24-in)</CHED>
                    </BOXHD>
                    <ROW RUL="s">
                        <ENT I="01">Total # of piles</ENT>
                        <ENT>12</ENT>
                        <ENT>12</ENT>
                        <ENT>10</ENT>
                        <ENT>16</ENT>
                    </ROW>
                    <ROW EXPSTB="04" RUL="s">
                        <ENT I="21">
                            <E T="02">Vibratory Pile Driving</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">Max # of piles/day</ENT>
                        <ENT>6</ENT>
                        <ENT>6</ENT>
                        <ENT>6</ENT>
                        <ENT>6</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Time/pile (minutes)</ENT>
                        <ENT>10</ENT>
                        <ENT>10</ENT>
                        <ENT>10</ENT>
                        <ENT>10</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Time/day (min)</ENT>
                        <ENT>60</ENT>
                        <ENT>60</ENT>
                        <ENT>60</ENT>
                        <ENT>60</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="1887"/>
                        <ENT I="01"># of days</ENT>
                        <ENT>2</ENT>
                        <ENT>2</ENT>
                        <ENT>1.7</ENT>
                        <ENT>2.7</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">Total # of hours</ENT>
                        <ENT>2</ENT>
                        <ENT>2</ENT>
                        <ENT>1.7</ENT>
                        <ENT>2.7</ENT>
                    </ROW>
                    <ROW EXPSTB="04" RUL="s">
                        <ENT I="21">
                            <E T="02">DTH Drilling</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">Max # of piles/day</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>2</ENT>
                        <ENT>2</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">strikes/pile</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>36,000</ENT>
                        <ENT>54,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">strikes/sec</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>10</ENT>
                        <ENT>10</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">time/pile</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>60</ENT>
                        <ENT>90</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">time/day (min)</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>120</ENT>
                        <ENT>180</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01"># of days</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>5</ENT>
                        <ENT>8</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">Total # of hours</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>10</ENT>
                        <ENT>24</ENT>
                    </ROW>
                    <ROW EXPSTB="04" RUL="s">
                        <ENT I="21">
                            <E T="02">Impact Pile Driving</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">Max # of piles/day</ENT>
                        <ENT>4</ENT>
                        <ENT/>
                        <ENT>4</ENT>
                        <ENT>4</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">strikes/pile</ENT>
                        <ENT>175</ENT>
                        <ENT/>
                        <ENT>175</ENT>
                        <ENT>175</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">time/pile (min)</ENT>
                        <ENT>5</ENT>
                        <ENT/>
                        <ENT>5</ENT>
                        <ENT>5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">time/day (min)</ENT>
                        <ENT>20</ENT>
                        <ENT/>
                        <ENT>20</ENT>
                        <ENT>20</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01"># of days</ENT>
                        <ENT>3</ENT>
                        <ENT/>
                        <ENT>2.5</ENT>
                        <ENT>4</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Total # of hours</ENT>
                        <ENT>1</ENT>
                        <ENT/>
                        <ENT>0.8</ENT>
                        <ENT>1.3</ENT>
                    </ROW>
                </GPOTABLE>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,12,12,12">
                    <TTITLE>Table 2—Phase 2 Project Pile Installation and Removal Summary</TTITLE>
                    <BOXHD>
                        <CHED H="1">Project component</CHED>
                        <CHED H="1">
                            Temp install
                            <LI>(16-in)</LI>
                        </CHED>
                        <CHED H="1">
                            Temp remove
                            <LI>(16-in)</LI>
                        </CHED>
                        <CHED H="1">
                            Perm install
                            <LI>(24-in)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW RUL="s">
                        <ENT I="01">Total # of piles</ENT>
                        <ENT>6</ENT>
                        <ENT>6</ENT>
                        <ENT>6</ENT>
                    </ROW>
                    <ROW EXPSTB="03" RUL="s">
                        <ENT I="21">
                            <E T="02">Vibratory Pile Driving</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">Max # of piles/day</ENT>
                        <ENT>6</ENT>
                        <ENT>6</ENT>
                        <ENT>6</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Time/pile (minutes)</ENT>
                        <ENT>10</ENT>
                        <ENT>10</ENT>
                        <ENT>10</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Time/day (min)</ENT>
                        <ENT>60</ENT>
                        <ENT>60</ENT>
                        <ENT>60</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01"># of days</ENT>
                        <ENT>1</ENT>
                        <ENT>1</ENT>
                        <ENT>1</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">Total # of hours</ENT>
                        <ENT>1</ENT>
                        <ENT>1</ENT>
                        <ENT>1</ENT>
                    </ROW>
                    <ROW EXPSTB="03" RUL="s">
                        <ENT I="21">
                            <E T="02">DTH Drilling</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">Max # of piles/day</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>2</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">strikes/pile</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>54,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">strikes/sec</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>10</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">time/pile</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>90</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">time/day (min)</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>180</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01"># of days</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>3</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">Total # of hours</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>9</ENT>
                    </ROW>
                    <ROW EXPSTB="03" RUL="s">
                        <ENT I="21">
                            <E T="02">Impact Pile Driving</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">Max # of piles/day</ENT>
                        <ENT>4</ENT>
                        <ENT/>
                        <ENT>4</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">strikes/pile</ENT>
                        <ENT>175</ENT>
                        <ENT/>
                        <ENT>175</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">time/pile (min)</ENT>
                        <ENT>5</ENT>
                        <ENT/>
                        <ENT>5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">time/day (min)</ENT>
                        <ENT>20</ENT>
                        <ENT/>
                        <ENT>20</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01"># of days</ENT>
                        <ENT>1.5</ENT>
                        <ENT/>
                        <ENT>1.5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Total # of hours</ENT>
                        <ENT>0.5</ENT>
                        <ENT/>
                        <ENT>0.5</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    Additionally, this project would include in-water work that is not expected to result in take of marine mammals. During Phase I and II, CBS proposed to discharge fill below the high tide line. The excavated materials from above the high tide line would be placed below the high tide line to develop the seaplane base uplands. The fill would be placed using an excavator and dozer and then compacted using a vibratory soil compactor. The total area of placement of fill below the high tide line in Phase I would be 1.6 acres (6,475 square meters (m
                    <SU>2</SU>
                    )) and in Phase II would be 1.3 acres (5,261 m
                    <SU>2</SU>
                    ). While marine mammals may behaviorally respond in some small degree to the noise generated by the placement of fill operations, given the slow, predictable movements of the equipment, and absent any other contextual features that would cause enhanced concern, NMFS does not expect CBS's planned placement of fill to result in the take of marine mammals and it is not discussed further.
                </P>
                <P>
                    Proposed mitigation, monitoring, and reporting measures are described in detail later in this document (please see Proposed Mitigation and Proposed Monitoring and Reporting).
                    <PRTPAGE P="1888"/>
                </P>
                <HD SOURCE="HD1">Description of Marine Mammals in the Area of Specified Activities</HD>
                <P>
                    Sections 3 and 4 of the application summarize available information regarding status and trends, distribution and habitat preferences, and behavior and life history of the potentially affected species. NMFS fully considered all of this information, and we refer the reader to these descriptions, instead of reprinting the information. Additional information regarding population trends and threats may be found in NMFS' Stock Assessment Reports (SARs; 
                    <E T="03">https://www.fisheries.noaa.gov/national/marine-mammal-protection/marine-mammal-stock-assessments</E>
                    ) and more general information about these species (
                    <E T="03">e.g.,</E>
                     physical and behavioral descriptions) may be found on NMFS' website (
                    <E T="03">https://www.fisheries.noaa.gov/find-species).</E>
                </P>
                <P>Table 3 lists all species or stocks for which take is expected and proposed to be authorized for this activity and summarizes information related to the population or stock, including regulatory status under the MMPA and Endangered Species Act (ESA) and potential biological removal (PBR), where known. PBR is defined by the MMPA as the maximum number of animals, not including natural mortalities, that may be removed from a marine mammal stock while allowing that stock to reach or maintain its optimum sustainable population (as described in NMFS' SARs). While no serious injury or mortality is anticipated or proposed to be authorized here, PBR and annual serious injury and mortality from anthropogenic sources are included here as gross indicators of the status of the species or stocks and other threats.</P>
                <P>
                    Marine mammal abundance estimates presented in this document represent the total number of individuals that make up a given stock or the total number estimated within a particular study or survey area. NMFS' stock abundance estimates for most species represent the total estimate of individuals within the geographic area, if known, that comprises that stock. For some species, this geographic area may extend beyond U.S. waters. All managed stocks in this region are assessed in NMFS' 2022 U.S. Alaska SAR. All values presented in table 3 are the most recent available at the time of publication and are available online at: 
                    <E T="03">https://www.fisheries.noaa.gov/national/marine-mammal-protection/marine-mammal-stock-assessments.</E>
                </P>
                <GPOTABLE COLS="7" OPTS="L2,p7,7/8,i1" CDEF="s50,r50,r50,xls30,r40,8,8">
                    <TTITLE>Table 3—Species Likely Impacted by the Specified Activities</TTITLE>
                    <BOXHD>
                        <CHED H="1">Common name</CHED>
                        <CHED H="1">Scientific name</CHED>
                        <CHED H="1">Stock</CHED>
                        <CHED H="1">
                            ESA/
                            <LI>MMPA</LI>
                            <LI>status;</LI>
                            <LI>strategic</LI>
                            <LI>
                                (Y/N) 
                                <SU>1</SU>
                            </LI>
                        </CHED>
                        <CHED H="1">
                            Stock abundance
                            <LI>
                                (CV, N
                                <E T="0732">min</E>
                                , most recent
                            </LI>
                            <LI>
                                abundance survey) 
                                <SU>2</SU>
                            </LI>
                        </CHED>
                        <CHED H="1">PBR</CHED>
                        <CHED H="1">
                            Annual M/SI 
                            <SU>3</SU>
                        </CHED>
                    </BOXHD>
                    <ROW EXPSTB="06" RUL="s">
                        <ENT I="21">
                            <E T="02">Order Cetartiodactyla—Cetacea—Superfamily Mysticeti (baleen whales)</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="22">Family Balaenopteridae (rorquals):</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Humpback Whale</ENT>
                        <ENT>
                            <E T="03">Megaptera novaeangliae</E>
                        </ENT>
                        <ENT>Hawai'i</ENT>
                        <ENT>-,-,N</ENT>
                        <ENT>11,278 (0.56, 7,265, 2020)</ENT>
                        <ENT>127</ENT>
                        <ENT>27</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl"/>
                        <ENT>Mexico-North Pacific</ENT>
                        <ENT>T,D,Y</ENT>
                        <ENT>N/A (N/A, N/A, 2006)</ENT>
                        <ENT>UND</ENT>
                        <ENT>0.6</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Minke Whale</ENT>
                        <ENT>
                            <E T="03">Balaenoptera acutorostrata</E>
                        </ENT>
                        <ENT>Alaska</ENT>
                        <ENT>-,-,N</ENT>
                        <ENT>N/A (N/A, N/A, 2018)</ENT>
                        <ENT/>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Family Eschrichtiidae:</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="03">Gray Whale</ENT>
                        <ENT>
                            <E T="03">Eschrichtius robustus</E>
                        </ENT>
                        <ENT>Eastern North Pacific</ENT>
                        <ENT>-,-,N</ENT>
                        <ENT>26,960 (0.05, 25,849, 2016)</ENT>
                        <ENT>801</ENT>
                        <ENT>131</ENT>
                    </ROW>
                    <ROW EXPSTB="06" RUL="s">
                        <ENT I="21">
                            <E T="02">Superfamily Odontoceti (toothed whales, dolphins, and porpoises)</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="22">Family Delphinidae:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Killer whale</ENT>
                        <ENT>
                            <E T="03">Orca orcinus</E>
                        </ENT>
                        <ENT>Northern Resident</ENT>
                        <ENT>-,-,N</ENT>
                        <ENT>302 (N/A, 302, 2018)</ENT>
                        <ENT>2.2</ENT>
                        <ENT>0.2</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl"/>
                        <ENT>Alaska Resident</ENT>
                        <ENT>-,-,N</ENT>
                        <ENT>1,920 (N/A, 1,920, 2019)</ENT>
                        <ENT>19</ENT>
                        <ENT>1.3</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl"/>
                        <ENT>Gulf of Alaska/Aleutian Islands/Bering Sea Transient</ENT>
                        <ENT>-,-,N</ENT>
                        <ENT>587 (N/A, 587, 2012)</ENT>
                        <ENT>5.9</ENT>
                        <ENT>0.8</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl"/>
                        <ENT>West Coast Transient</ENT>
                        <ENT>-,-,N</ENT>
                        <ENT>349 (N/A, 349, 2018)</ENT>
                        <ENT>3.5</ENT>
                        <ENT>0.4</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Family Phocoenidae (porpoises):</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="03">Harbor porpoise</ENT>
                        <ENT>
                            <E T="03">Phocoena phocoena</E>
                        </ENT>
                        <ENT>Northern Southeast Alaska</ENT>
                        <ENT>-,-,N</ENT>
                        <ENT>1,619 (0.26, 1,250, 2019)</ENT>
                        <ENT>13</ENT>
                        <ENT>5.6</ENT>
                    </ROW>
                    <ROW EXPSTB="06" RUL="s">
                        <ENT I="21">
                            <E T="02">Order Carnivora—Superfamily Pinnipedia</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="22">Family Otariidae (eared seals and sea lions):</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Steller sea lion</ENT>
                        <ENT>
                            <E T="03">Eumetopias jubatus</E>
                        </ENT>
                        <ENT>Western Stock</ENT>
                        <ENT>E,D,Y</ENT>
                        <ENT>52,932 (N/A, 52,932, 2019)</ENT>
                        <ENT>318</ENT>
                        <ENT>254</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl"/>
                        <ENT>Eastern Stock</ENT>
                        <ENT>-,-,N</ENT>
                        <ENT>43,201 (N/A, 43,201, 2017)</ENT>
                        <ENT>2,592</ENT>
                        <ENT>112</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Family Phocidae (earless seals):</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Harbor seal</ENT>
                        <ENT>
                            <E T="03">Phoca vituline richardii</E>
                        </ENT>
                        <ENT>Sitka/Chatham</ENT>
                        <ENT>-,-,N</ENT>
                        <ENT>13,289 (N/A, 11,883, 2015)</ENT>
                        <ENT>356</ENT>
                        <ENT>77</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>1</SU>
                         Endangered Species Act (ESA) status: Endangered (E), Threatened (T)/MMPA status: Depleted (D). A dash (-) indicates that the species is not listed under the ESA or designated as depleted under the MMPA. Under the MMPA, a strategic stock is one for which the level of direct human-caused mortality exceeds PBR or which is determined to be declining and likely to be listed under the ESA within the foreseeable future. Any species or stock listed under the ESA is automatically designated under the MMPA as depleted and as a strategic stock.
                    </TNOTE>
                    <TNOTE>
                        <SU>2</SU>
                         NMFS marine mammal stock assessment reports online at:
                        <E T="03"> https://www.fisheries.noaa.gov/national/marine-mammal-protection/marine-mammal-stock-assessment-reports</E>
                         CV is coefficient of variation; N
                        <E T="0732">min</E>
                         is the minimum estimate of stock abundance.
                    </TNOTE>
                    <TNOTE>
                        <SU>3</SU>
                         These values, found in NMFS's SARs, represent annual levels of human-caused mortality plus serious injury from all sources combined (
                        <E T="03">e.g.,</E>
                         commercial fisheries, ship strike). Annual M/SI often cannot be determined precisely and is in some cases presented as a minimum value or range.
                    </TNOTE>
                </GPOTABLE>
                <P>
                    As indicated above, all 7 species (with 12 managed stocks) in table 3 temporally and spatially co-occur with the activity to the degree that take is reasonably likely to occur. All species that could potentially occur in the proposed action area are included in table 8 of the IHA application. While northern fur seal, Pacific white-sided 
                    <PRTPAGE P="1889"/>
                    dolphin, Dall's porpoise, North Pacific right whale, sperm whale, fin whale, and Cuvier's beaked whale have been documented in or near Sitka Sound and Sitka Channel, the temporal and/or spatial occurrence of these species is such that take is not expected to occur, and they are not discussed further beyond the explanation provided here. These species are all considered to be rare (no sightings in recent years) or very rare (no local knowledge of sightings within the project vicinity) within Sitka Sound or near the action area. The take of these species has not been requested nor is proposed to be authorized and these species are not considered further in this document. In addition to what is included in Sections 3 and 4 of the application, the SARs, and NMFS' website, further localized data and detail informing the baseline for select species (
                    <E T="03">i.e.,</E>
                     information regarding current Unusual Mortality Events (UME) and important habitat areas) is provided below.
                </P>
                <P>Additionally, the Northern Sea Otter may be found in Sitka Sound. However, the Northern Sea Otter are managed by the U.S. Fish and Wildlife Service and are not considered further in this document.</P>
                <HD SOURCE="HD2">Gray Whale</HD>
                <P>
                    The migration pattern of gray whales appears to follow a route along the western coast of Southeast Alaska, traveling northward from British Columbia through Hecate Strait and Dixon Entrance, passing the west coast of Baranof Island from late March to May and then return south in October and November (Jones 
                    <E T="03">et al.</E>
                     1984, Ford 
                    <E T="03">et al.</E>
                     2013). The project area is inside Sitka Sound on the northern shore of Japonski Island, adjacent to Baranof Island.
                </P>
                <P>
                    During 190 hours of observation from 1994 to 2002 from Sitka's Whale Park, three gray whales were observed (Straley 
                    <E T="03">et al.,</E>
                     2017). During recent marine mammal surveys conducted in the vicinity of the project action area, no gray whales were sighted, and these species are not known or expected to occur near or within Sitka Channel (Windward 2017; Turnagain 2017; Straley 
                    <E T="03">et al.,</E>
                     2017; Turnagain 2018; SolsticeAK 2019; SolsticeAK 2020; Halibut Point Marine Services 2021; SolsticeAK 2022). However, Sitka Sound is within a gray whale migratory route Biologically Important Area (BIA) (March-May; November-January) and a feeding BIA (March-June) (Wild 
                    <E T="03">et al.,</E>
                     2023).
                </P>
                <P>
                    Since January 1, 2019, elevated gray whale strandings have occurred along the west coast of North America from Mexico through Alaska. This event has been declared an UME, though a cause has not yet been determined. More information is available at 
                    <E T="03">https://www.fisheries.noaa.gov/national/marine-life-distress/active-and-closed-unusual-mortality-events.</E>
                </P>
                <HD SOURCE="HD2">Humpback Whale</HD>
                <P>
                    Humpback whales are the most commonly observed baleen whale in Sitka Sound. They have been observed in Southeast Alaska in all months of the year (Baker 
                    <E T="03">et al.</E>
                     1985, 1986), although they are most common in Sitka Sound's Eastern Channel in November, December, and January (Straley 
                    <E T="03">et al.,</E>
                     2017). In late fall and winter, herring sometimes overwinter in deep fjords in Silver Bay and Eastern Channel, and humpback whales aggregate in these areas to feed on them. In the summer when prey is dispersed throughout Sitka Sound, humpback whales also disperse throughout the Sound (Straley 
                    <E T="03">et al.,</E>
                     2017).
                </P>
                <P>
                    Humpback whales have been frequently observed during construction projects in Sitka Sound, including the Biorka Island Dock Replacement Project (Turnagain Marine Construction, 2018) and the Sitka GPIP Multipurpose Dock Project (Turnagain Marine Construction, 2017). During 190 hours of observation from 1994 to 2002 from Sitka's Whale Park, 440 humpback whales were observed (Straley 
                    <E T="03">et al.,</E>
                     2017). During 21 days of monitoring during the construction of GPIP Dock between October 9 and November 9, 2017, 39 humpback whales were observed (Turnagain 2017). No humpback whales were observed within Sitka Channel during the eight days of monitoring in January 2017 during the construction of the Sitka Petro Dock (Windward 2017). Near Biorka Island, about 25 kilometers south of the project, humpback whales were sighted in June (22 whales), July (3 whales), and September (2 whales) 2018 (Turnagain 2018). No whales were sighted in August during the Biorka Island monitoring effort. Humpback whales were not observed during recent monitoring conducted for short periods over 8 days in September 2018 within a 400-meter radius surrounding the O'Connell Bridge Lightering Float (SolsticeAK 2019). During 39 days of monitoring in January through March 2020 for the Crescent Harbor Float Rebuild Project, no humpbacks were observed. Humpback whales were not observed in the project area during 5 days of monitoring in March 2022 during the geotechnical survey for this project (SolsticeAK 2022).
                </P>
                <P>Given their widespread range and their opportunistic foraging strategies, humpback whales may be in Sitka Sound year-round but are more likely to occur in the summer months, although they are not as frequent in the action area.</P>
                <P>
                    According to Wade 
                    <E T="03">et al.</E>
                     (2016), humpback whales in Southeast Alaska are most likely to be from the Hawaii DPS (distinct population segment, 98 percent probability), with a 2 percent probability of being from the threatened Mexico DPS. Sitka Sound is within seasonal humpback whale feeding BIAs from March-May and September-December (Wild 
                    <E T="03">et al.,</E>
                     2023).
                </P>
                <HD SOURCE="HD2">Steller Sea Lion</HD>
                <P>
                    Steller sea lions occur year-round in the project area. Most are expected to be from the Eastern DPS; however, it is likely that some Steller sea lions in the action area are from the endangered Western DPS (Jemison 
                    <E T="03">et al.</E>
                     2013; NMFS 2013). Jemison 
                    <E T="03">et al.</E>
                     (2013) estimated an average annual breeding season movement of 917 Western DPS Steller sea lions to Southeast Alaska. Based on surveys and analysis conducted by Hastings 
                    <E T="03">et al.</E>
                     (2020), an estimated 2.2 percent of Steller sea lions in the vicinity of the project are Western DPS Steller sea lions.
                </P>
                <P>Critical habitat has been defined in Southeast Alaska at major haulouts and major rookeries (50 CFR 226.202), but the project action area does not overlap with Steller sea lion critical habitat. The Biorka Island haulout is the closest designated critical habitat and is approximately 25 kilometers southwest of the project area.</P>
                <P>
                    Based on Straley 
                    <E T="03">et al.</E>
                     (2017) and other vessel-based surveys conducted from 1994 to 2016, Steller sea lion numbers are highest near the project area in January and February. January was the most abundant month with about 190 Steller sea lions spotted. February and November were next with about 170 and 120 Steller sea lions spotted, respectively. The fewest Steller sea lions were spotted in the month of May (1995-2002).
                </P>
                <P>
                    Individual sea lions were seen on 19 of 21 days in Silver Bay and Easter Channel during monitoring for GPIP dock construction between October and November 2017 (Turnagain 2017). Near Biorka Island, sea lions were seen infrequently; sea lions were sighted in June (six animals), July (two animals), and no sea lions were seen in August 2018 (Turnagain 2018). During 8 days of monitoring in January 2017 for the Petro Marine dock, about 1.6 kilometers (1 mile) southwest of the Sitka SPB, individual sea lions were seen on 3 days (Windward 2017). Steller sea lions were observed 5 of 8 days during monitoring 
                    <PRTPAGE P="1890"/>
                    conducted for 15-minute periods in September 2018 for the O'Connell Bridge Lightering Float (SolsticeAK 2019). During in-water construction work for the O'Connell Bridge Lightering Float Pile Replacement Project between June 9 and June 12, 2019, 42 Steller sea lions were sighted (SolsticeAK 2019). During 39 days of marine mammal monitoring for the Crescent Harbor Float Replacement Project in January and February 2020, six sea lions were observed southwest of Sitka Channel (SolsticeAK 2020). Steller sea lions were most often observed alone or in small groups of 2 or 3 during these monitoring efforts; however, a group of more than 100 was sighted on at least 1 occasion (Straley 
                    <E T="03">et al.</E>
                     2017; Windward 2017; SolsticeAK 2019; SolsticeAK 2020). During the original construction of the Halibut Point Marine Services dock facility, no Steller sea lions were recorded within the 200-meter shutdown zone during pile driving operations; however, observers indicated observing individual sea lions outside the 200-meter zone four to five times per week (McGraw, 2019).
                </P>
                <P>During the summer months, sea lions are seen in the project area daily. Two to three individual sea lions feed on fish carcasses dumped adjacent to the project site from fishing charter operations in a nearby private marina. However, during the fall and winter, the charter fishing operations are not underway and the sea lions are not as active in the area (McGraw, pers. com., 2019).</P>
                <HD SOURCE="HD2">Marine Mammal Hearing</HD>
                <P>
                    Hearing is the most important sensory modality for marine mammals underwater, and exposure to anthropogenic sound can have deleterious effects. To appropriately assess the potential effects of exposure to sound, it is necessary to understand the frequency ranges marine mammals are able to hear. Not all marine mammal species have equal hearing capabilities (
                    <E T="03">e.g.,</E>
                     Richardson 
                    <E T="03">et al.,</E>
                     1995; Wartzok and Ketten, 1999; Au and Hastings, 2008). To reflect this, Southall 
                    <E T="03">et al.</E>
                     (2007, 2019) recommended that marine mammals be divided into hearing groups based on directly measured (behavioral or auditory evoked potential techniques) or estimated hearing ranges (behavioral response data, anatomical modeling, 
                    <E T="03">etc.</E>
                    ). Note that no direct measurements of hearing ability have been successfully completed for mysticetes (
                    <E T="03">i.e.,</E>
                     low-frequency cetaceans). Subsequently, NMFS (2018) described generalized hearing ranges for these marine mammal hearing groups. Generalized hearing ranges were chosen based on the approximately 65 decibel (dB) threshold from the normalized composite audiograms, with the exception for lower limits for low-frequency cetaceans where the lower bound was deemed to be biologically implausible and the lower bound from Southall 
                    <E T="03">et al.</E>
                     (2007) retained. Marine mammal hearing groups and their associated hearing ranges are provided in table 4.
                </P>
                <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s100,xs72">
                    <TTITLE>Table 4—Marine Mammal Hearing Groups</TTITLE>
                    <TDESC>[NMFS, 2018]</TDESC>
                    <BOXHD>
                        <CHED H="1">Hearing group</CHED>
                        <CHED H="1">
                            Generalized hearing
                            <LI>range *</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Low-frequency (LF) cetaceans (baleen whales)</ENT>
                        <ENT>7 Hz to 35 kHz.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Mid-frequency (MF) cetaceans (dolphins, toothed whales, beaked whales, bottlenose whales)</ENT>
                        <ENT>150 Hz to 160 kHz.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            High-frequency (HF) cetaceans (true porpoises, 
                            <E T="03">Kogia,</E>
                             river dolphins, Cephalorhynchid, 
                            <E T="03">Lagenorhynchus cruciger</E>
                             &amp; 
                            <E T="03">L. australis</E>
                            )
                        </ENT>
                        <ENT>275 Hz to 160 kHz.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Phocid pinnipeds (PW) (underwater) (true seals)</ENT>
                        <ENT>50 Hz to 86 kHz.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Otariid pinnipeds (OW) (underwater) (sea lions and fur seals)</ENT>
                        <ENT>60 Hz to 39 kHz.</ENT>
                    </ROW>
                    <TNOTE>
                        * Represents the generalized hearing range for the entire group as a composite (
                        <E T="03">i.e.,</E>
                         all species within the group), where individual species' hearing ranges are typically not as broad. Generalized hearing range chosen based on ~65 dB threshold from normalized composite audiogram, with the exception for lower limits for LF cetaceans (Southall 
                        <E T="03">et al.</E>
                         2007) and PW pinniped (approximation).
                    </TNOTE>
                </GPOTABLE>
                <P>
                    The pinniped functional hearing group was modified from Southall 
                    <E T="03">et al.</E>
                     (2007) on the basis of data indicating that phocid species have consistently demonstrated an extended frequency range of hearing compared to otariids, especially in the higher frequency range (Hemilä 
                    <E T="03">et al.,</E>
                     2006; Kastelein 
                    <E T="03">et al.,</E>
                     2009; Reichmuth and Holt, 2013).
                </P>
                <P>For more detail concerning these groups and associated frequency ranges, please see NMFS (2018) for a review of available information.</P>
                <HD SOURCE="HD1">Potential Effects of Specified Activities on Marine Mammals and Their Habitat</HD>
                <P>This section provides a discussion of the ways in which components of the specified activity may impact marine mammals and their habitat. The Estimated Take of Marine Mammals section later in this document includes a quantitative analysis of the number of individuals that are expected to be taken by this activity. The Negligible Impact Analysis and Determination section considers the content of this section, the Estimated Take of Marine Mammals section, and the Proposed Mitigation section, to draw conclusions regarding the likely impacts of these activities on the reproductive success or survivorship of individuals and whether those impacts are reasonably expected to, or reasonably likely to, adversely affect the species or stock through effects on annual rates of recruitment or survival.</P>
                <HD SOURCE="HD2">Description of Sound Sources</HD>
                <P>
                    The marine soundscape is comprised of both ambient and anthropogenic sounds. Ambient sound is defined as the all-encompassing sound in a given place and is usually a composite of sound from many sources both near and far. The sound level of an area is defined by the total acoustical energy being generated by known and unknown sources. These sources may include physical (
                    <E T="03">e.g.,</E>
                     waves, wind, precipitation, earthquakes, ice, atmospheric sound), biological (
                    <E T="03">e.g.,</E>
                     sounds produced by marine mammals, fish, and invertebrates), and anthropogenic sound (
                    <E T="03">e.g.,</E>
                     vessels, dredging, aircraft, construction).
                </P>
                <P>
                    The sum of the various natural and anthropogenic sound sources at any given location and time—which comprise “ambient” or “background” sound—depends not only on the source levels (as determined by current weather conditions and levels of biological and shipping activity) but also on the ability of sound to propagate through the environment. In turn, sound propagation is dependent on the spatially and temporally varying properties of the water column and sea floor, and is frequency-dependent. As a result of the dependence on a large number of varying factors, ambient sound levels can be expected to vary widely over both coarse and fine spatial and temporal scales. Sound levels at a 
                    <PRTPAGE P="1891"/>
                    given frequency and location can vary by 10-20 dB from day to day (Richardson 
                    <E T="03">et al.,</E>
                     1995). The result is that, depending on the source type and its intensity, sound from the specified activity may be a negligible addition to the local environment or could form a distinctive signal that may affect marine mammals.
                </P>
                <P>
                    In-water construction activities associated with the project would include impact and vibratory pile driving and DTH drilling. The sounds produced by these activities fall into one of two general sound types: impulsive and non-impulsive. Impulsive sounds (
                    <E T="03">e.g.,</E>
                     explosions, gunshots, sonic booms, impact pile driving) are typically transient, brief (less than 1 second), broadband, and consist of high peak sound pressure with rapid rise time and rapid decay (American National Standards Institute (ANSI) 1986; National Institute for Occupational Safety and Health (NIOSH) 1998; ANSI 2005; NMFS 2018a). Non-impulsive sounds (
                    <E T="03">e.g.,</E>
                     aircraft, machinery operations such as drilling or dredging, vibratory pile driving, and active sonar systems) can be broadband, narrowband or tonal, brief or prolonged (continuous or intermittent), and typically do not have the high peak sound pressure with raid rise/decay time that impulsive sounds do (ANSI 1995; NIOSH 1998; NMFS 2018a). The distinction between these two sound types is important because they have differing potential to cause physical effects, particularly with regard to hearing (
                    <E T="03">e.g.,</E>
                     Ward 1997 in Southall 
                    <E T="03">et al.,</E>
                     2007).
                </P>
                <P>
                    Three types of hammers would be used on this project: impact, vibratory, and DTH. Impact hammers operate by repeatedly dropping a heavy piston onto a pile to drive the pile into the substrate. Sound generated by impact hammers is characterized by rapid rise times and high peak levels, a potentially injurious combination (Hastings and Popper, 2005). Vibratory hammers install piles by vibrating them and allowing the weight of the hammer to push them into the sediment. Vibratory hammers produce significantly less sound than impact hammers. Peak sound pressure levels (SPLs) may be 180 dB or greater, but are generally 10 to 20 dB lower than SPLs generated during impact pile driving of the same-sized pile (Oestman 
                    <E T="03">et al.,</E>
                     2009). Rise time is slower, reducing the probability and severity of injury, and sound energy is distributed over a greater amount of time (Nedwell and Edwards 2002; Carlson 
                    <E T="03">et al.,</E>
                     2005).
                </P>
                <P>
                    A DTH hammer is essentially a drill bit that drills through the bedrock using a rotating function like a normal drill, in concert with a hammering mechanism operated by a pneumatic (or sometimes hydraulic) component integrated into the DTH hammer to increase speed of progress through the substrate (
                    <E T="03">i.e.,</E>
                     it is similar to a “hammer drill” hand tool). The sounds produced by the DTH method contain both a continuous non-impulsive component from the drilling action and an impulsive component from the hammering effect. Therefore, we treat DTH systems as both impulsive and non-impulsive sound source types simultaneously.
                </P>
                <P>The likely or possible impacts of CBS's proposed activity on marine mammals involve both non-acoustic and acoustic stressors. Potential non-acoustic stressors could result from the physical presence of equipment and personnel; however, any impacts to marine mammals are expected to be primarily acoustic in nature. Acoustic stressors include effects of heavy equipment operation during pile driving and drilling.</P>
                <HD SOURCE="HD2">Acoustic Impacts</HD>
                <P>
                    The introduction of anthropogenic noise into the aquatic environment from pile driving or drilling is the primary means by which marine mammals may be harassed from the CBS's specified activity. In general, animals exposed to natural or anthropogenic sound may experience physical and psychological effects, ranging in magnitude from none to severe (Southall 
                    <E T="03">et al.,</E>
                     2007). In general, exposure to pile driving or drilling noise has the potential to result in auditory threshold shifts and behavioral reactions (
                    <E T="03">e.g.,</E>
                     avoidance, temporary cessation of foraging and vocalizing, changes in dive behavior). Exposure to anthropogenic noise can also lead to non-observable physiological responses such an increase in stress hormones. Additional noise in a marine mammal's habitat can mask acoustic cues used by marine mammals to carry out daily functions such as communication and predator and prey detection. The effects of pile driving or drilling noise on marine mammals are dependent on several factors, including, but not limited to, sound type (
                    <E T="03">e.g.,</E>
                     impulsive vs. non-impulsive), the species, age and sex class (
                    <E T="03">e.g.,</E>
                     adult male vs. mom with calf), duration of exposure, the distance between the pile and the animal, received levels, behavior at time of exposure, and previous history with exposure (Wartzok 
                    <E T="03">et al.,</E>
                     2004; Southall 
                    <E T="03">et al.,</E>
                     2007). Here we discuss physical auditory effects (threshold shifts) followed by behavioral effects and potential impacts on habitat.
                </P>
                <P>
                    NMFS defines a noise-induced threshold shift (TS) as a change, usually an increase, in the threshold of audibility at a specified frequency or portion of an individual's hearing range above a previously established reference level (NMFS 2018). The amount of threshold shift is customarily expressed in dB. TS can be permanent or temporary. As described in NMFS (2018), there are numerous factors to consider when examining the consequence of TS, including, but not limited to, the signal temporal pattern (
                    <E T="03">e.g.,</E>
                     impulsive or non-impulsive), likelihood an individual would be exposed for a long enough duration or to a high enough level to induce a TS, the magnitude of the TS, time to recovery (seconds to minutes or hours to days), the frequency range of the exposure (
                    <E T="03">i.e.,</E>
                     spectral content), the hearing and vocalization frequency range of the exposed species relative to the signal's frequency spectrum (
                    <E T="03">i.e.,</E>
                     how an animal uses sound within the frequency band of the signal; 
                    <E T="03">e.g.,</E>
                     Kastelein 
                    <E T="03">et al.,</E>
                     2014), and the overlap between the animal and the source (
                    <E T="03">e.g.,</E>
                     spatial, temporal, and spectral).
                </P>
                <P>
                    <E T="03">Permanent Threshold Shift (PTS)</E>
                    —NMFS defines PTS as a permanent, irreversible increase in the threshold of audibility at a specified frequency or portion of an individual's hearing range above a previously established reference level (NMFS 2018). Available data from humans and other terrestrial mammals indicate that a 40 dB threshold shift approximates PTS onset (see Ward 
                    <E T="03">et al.,</E>
                     1958, 1959; Ward 1960; Kryter 
                    <E T="03">et al.,</E>
                     1966; Miller 1974; Ahroon 
                    <E T="03">et al.,</E>
                     1996; Henderson 
                    <E T="03">et al.,</E>
                     2008). PTS levels for marine mammals are estimates, as with the exception of a single study unintentionally inducing PTS in a harbor seal (Kastak 
                    <E T="03">et al.,</E>
                     2008), there are no empirical data measuring PTS in marine mammals largely due to the fact that, for various ethical reasons, experiments involving anthropogenic noise exposure at levels inducing PTS are not typically pursued or authorized (NMFS 2018).
                </P>
                <P>
                    <E T="03">Temporary Threshold Shift (TTS)</E>
                    —TTS is a temporary, reversible increase in the threshold of audibility at a specified frequency or portion of an individual's hearing range above a previously established reference level (NMFS 2018). Based on data from cetacean TTS measurements (see Southall 
                    <E T="03">et al.,</E>
                     2007), a TTS of 6 dB is considered the minimum threshold shift clearly larger than any day-to-day or session-to-session variation in a subject's normal hearing ability (Schlundt 
                    <E T="03">et al.,</E>
                     2000; Finneran 
                    <E T="03">et al.,</E>
                     2000, 2002). As described in Finneran 
                    <PRTPAGE P="1892"/>
                    (2015), marine mammal studies have shown the amount of TTS increases with cumulative sound exposure level (SELcum) in an accelerating fashion: At low exposures with lower SELcum, the amount of TTS is typically small and the growth curves have shallow slopes. At exposures with higher SELcum, the growth curves become steeper and approach linear relationships with the noise SEL.
                </P>
                <P>
                    Depending on the degree (elevation of threshold in dB), duration (
                    <E T="03">i.e.,</E>
                     recovery time), and frequency range of TTS, and the context in which it is experienced, TTS can have effects on marine mammals ranging from discountable to serious (similar to those discussed in auditory masking, below). For example, a marine mammal may be able to readily compensate for a brief, relatively small amount of TTS in a non-critical frequency range that takes place during a time when the animal is traveling through the open ocean, where ambient noise is lower and there are not as many competing sounds present. Alternatively, a larger amount and longer duration of TTS sustained during a time when communication is critical for successful mother/calf interactions could have more serious impacts. We note that reduced hearing sensitivity as a simple function of aging has been observed in marine mammals, as well as humans and other taxa (Southall 
                    <E T="03">et al.,</E>
                     2007), so we can infer that strategies exist for coping with this condition to some degree, though likely not without cost.
                </P>
                <P>
                    Many studies have examined noise-induced hearing loss in marine mammals (see Finneran (2015) and Southall 
                    <E T="03">et al.</E>
                     (2019) for summaries). For cetaceans, published data on the onset of TTS are limited to the captive bottlenose dolphin (
                    <E T="03">Tursiops truncatus</E>
                    ), beluga whale (
                    <E T="03">Delphinapterus leucas</E>
                    ), harbor porpoise, and Yangtze finless porpoise (
                    <E T="03">Neophocoena asiaeorientalis</E>
                    ), and for pinnipeds in water, measurements of TTS are limited to harbor seals, elephant seals (
                    <E T="03">Mirounga angustirostris</E>
                    ), and California sea lions (
                    <E T="03">Zalophus californianus</E>
                    ). These studies examine hearing thresholds measured in marine mammals before and after exposure to intense sounds. The difference between the pre-exposure and post-exposure thresholds can be used to determine the amount of threshold shift at various post-exposure times. The amount and onset of TTS depends on the exposure frequency. Sounds at low frequencies, well below the region of best sensitivity, are less hazardous than those at higher frequencies, near the region of best sensitivity (Finneran and Schlundt, 2013). At low frequencies, onset-TTS exposure levels are higher compared to those in the region of best sensitivity (
                    <E T="03">i.e.,</E>
                     a low frequency noise would need to be louder to cause TTS onset when TTS exposure level is higher), as shown for harbor porpoises and harbor seals (Kastelein 
                    <E T="03">et al.,</E>
                     2019a, 2019b). In addition, TTS can accumulate across multiple exposures, but the resulting TTS will be less than the TTS from a single, continuous exposure with the same SEL (Finneran 
                    <E T="03">et al.,</E>
                     2010; Kastelein 
                    <E T="03">et al.,</E>
                     2014; Kastelein 
                    <E T="03">et al.,</E>
                     2015a; Mooney 
                    <E T="03">et al.,</E>
                     2009). This means that TTS predictions based on the total, cumulative SEL will overestimate the amount of TTS from intermittent exposures such as sonars and impulsive sources. Nachtigall 
                    <E T="03">et al.</E>
                     (2018) describe the measurements of hearing sensitivity of multiple odontocete species (bottlenose dolphin, harbor porpoise, beluga, and false killer whale (
                    <E T="03">Pseudorca crassidens</E>
                    )) when a relatively loud sound was preceded by a warning sound. These captive animals were shown to reduce hearing sensitivity when warned of an impending intense sound. Based on these experimental observations of captive animals, the authors suggest that wild animals may dampen their hearing during prolonged exposures or if conditioned to anticipate intense sounds. Another study showed that echolocating animals (including odontocetes) might have anatomical specializations that might allow for conditioned hearing reduction and filtering of low-frequency ambient noise, including increased stiffness and control of middle ear structures and placement of inner ear structures (Ketten 
                    <E T="03">et al.,</E>
                     2021). Data available on noise-induced hearing loss for mysticetes are currently lacking (NMFS, 2018).
                </P>
                <P>
                    <E T="03">Behavioral Harassment</E>
                    —Exposure to noise from pile driving and removal also has the potential to behaviorally disturb marine mammals. Available studies show wide variation in response to underwater sound; therefore, it is difficult to predict specifically how any given sound in a particular instance might affect marine mammals perceiving the signal. If a marine mammal does react briefly to an underwater sound by changing its behavior or moving a small distance, the impacts of the change are unlikely to be significant to the individual, let alone the stock or population. However, if a sound source displaces marine mammals from an important feeding or breeding area for a prolonged period, impacts on individuals and populations could be significant (
                    <E T="03">e.g.,</E>
                     Lusseau and Bejder 2007; Weilgart 2007).
                </P>
                <P>
                    Disturbance may result in changing durations of surfacing and dives, number of blows per surfacing, or moving direction and/or speed; reduced/increased vocal activities; changing/cessation of certain behavioral activities (such as socializing or feeding); visible startle response or aggressive behavior (such as tail/fluke slapping or jaw clapping); avoidance of areas where sound sources are located. Pinnipeds may increase their haul out time, possibly to avoid in-water disturbance (Thorson and Reyff 2006). Behavioral responses to sound are highly variable and context-specific and any reactions depend on numerous intrinsic and extrinsic factors (
                    <E T="03">e.g.,</E>
                     species, state of maturity, experience, current activity, reproductive state, auditory sensitivity, time of day), as well as the interplay between factors (
                    <E T="03">e.g.,</E>
                     Richardson 
                    <E T="03">et al.,</E>
                     1995; Wartzok 
                    <E T="03">et al.,</E>
                     2003; Southall 
                    <E T="03">et al.,</E>
                     2007; Weilgart 2007). Behavioral reactions can vary not only among individuals but also within an individual, depending on previous experience with a sound source, context, and numerous other factors (Ellison 
                    <E T="03">et al.,</E>
                     2012), and can vary depending on characteristics associated with the sound source (
                    <E T="03">e.g.,</E>
                     whether it is moving or stationary, number of sources, distance from the source). In general, pinnipeds seem more tolerant of, or at least habituate more quickly to, potentially disturbing underwater sound than do cetaceans, and generally seem to be less responsive to exposure to industrial sound than most cetaceans. Please see Appendices B-C of Southall 
                    <E T="03">et al.</E>
                     (2007) for a review of studies involving marine mammal behavioral responses to sound.
                </P>
                <P>
                    Disruption of feeding behavior can be difficult to correlate with anthropogenic sound exposure, so it is usually inferred by observed displacement from known foraging areas, the appearance of secondary indicators (
                    <E T="03">e.g.,</E>
                     bubble nets or sediment plumes), or changes in dive behavior. As for other types of behavioral response, the frequency, duration, and temporal pattern of signal presentation, as well as differences in species sensitivity, are likely contributing factors to differences in response in any given circumstance (
                    <E T="03">e.g.,</E>
                     Croll 
                    <E T="03">et al.,</E>
                     2001; Nowacek 
                    <E T="03">et al.,</E>
                     2004; Madsen 
                    <E T="03">et al.,</E>
                     2006; Yazvenko 
                    <E T="03">et al.,</E>
                     2007). A determination of whether foraging disruptions incur fitness consequences would require information on or estimates of the energetic requirements of the affected individuals and the relationship between prey availability, foraging effort 
                    <PRTPAGE P="1893"/>
                    and success, and the life history stage of the animal.
                </P>
                <P>
                    <E T="03">Stress responses</E>
                    —An animal's perception of a threat may be sufficient to trigger stress responses consisting of some combination of behavioral responses, autonomic nervous system responses, neuroendocrine responses, or immune responses (
                    <E T="03">e.g.,</E>
                     Seyle 1950; Moberg 2000). In many cases, an animal's first and sometimes most economical (in terms of energetic costs) response is behavioral avoidance of the potential stressor. Autonomic nervous system responses to stress typically involve changes in heart rate, blood pressure, and gastrointestinal activity. These responses have a relatively short duration and may or may not have a significant long-term effect on an animal's fitness.
                </P>
                <P>
                    Neuroendocrine stress responses often involve the hypothalamus-pituitary-adrenal system. Virtually all neuroendocrine functions that are affected by stress—including immune competence, reproduction, metabolism, and behavior—are regulated by pituitary hormones. Stress-induced changes in the secretion of pituitary hormones have been implicated in failed reproduction, altered metabolism, reduced immune competence, and behavioral disturbance (
                    <E T="03">e.g.,</E>
                     Moberg 1987; Blecha 2000). Increases in the circulation of glucocorticoids are also equated with stress (Romano 
                    <E T="03">et al.,</E>
                     2004).
                </P>
                <P>The primary distinction between stress (which is adaptive and does not normally place an animal at risk) and “distress” is the cost of the response. During a stress response, an animal uses glycogen stores that can be quickly replenished once the stress is alleviated. In such circumstances, the cost of the stress response would not pose serious fitness consequences. However, when an animal does not have sufficient energy reserves to satisfy the energetic costs of a stress response, energy resources must be diverted from other functions. This state of distress will last until the animal replenishes its energetic reserves sufficient to restore normal function.</P>
                <P>
                    Relationships between these physiological mechanisms, animal behavior, and the costs of stress responses are well studied through controlled experiments and for both laboratory and free-ranging animals (
                    <E T="03">e.g.,</E>
                     Holberton 
                    <E T="03">et al.,</E>
                     1996; Hood 
                    <E T="03">et al.,</E>
                     1998; Jessop 
                    <E T="03">et al.,</E>
                     2003; Lankford 
                    <E T="03">et al.,</E>
                     2005). Stress responses due to exposure to anthropogenic sounds or other stressors and their effects on marine mammals have also been reviewed (Fair and Becker 2000; Romano 
                    <E T="03">et al.,</E>
                     2002b) and, more rarely, studied in wild populations (
                    <E T="03">e.g.,</E>
                     Romano 
                    <E T="03">et al.,</E>
                     2002a). For example, Rolland 
                    <E T="03">et al.</E>
                     (2012) found that noise reduction from reduced ship traffic in the Bay of Fundy was associated with decreased stress in North Atlantic right whales. These and other studies lead to a reasonable expectation that some marine mammals will experience physiological stress responses upon exposure to acoustic stressors and that it is possible that some of these would be classified as “distress.” In addition, any animal experiencing TTS would likely also experience stress responses (National Research Council (NRC), 2003), however distress is an unlikely result of this project based on observations of marine mammals during previous, similar projects in the area.
                </P>
                <P>
                    <E T="03">Masking</E>
                    —Sound can disrupt behavior through masking, or interfering with, an animal's ability to detect, recognize, or discriminate between acoustic signals of interest (
                    <E T="03">e.g.,</E>
                     those used for intraspecific communication and social interactions, prey detection, predator avoidance, navigation) (Richardson 
                    <E T="03">et al.,</E>
                     1995). Masking occurs when the receipt of a sound is interfered with by another coincident sound at similar frequencies and at similar or higher intensity, and may occur whether the sound is natural (
                    <E T="03">e.g.,</E>
                     snapping shrimp, wind, waves, precipitation) or anthropogenic (
                    <E T="03">e.g.,</E>
                     pile driving, shipping, sonar, seismic exploration) in origin. The ability of a noise source to mask biologically important sounds depends on the characteristics of both the noise source and the signal of interest (
                    <E T="03">e.g.,</E>
                     signal-to-noise ratio, temporal variability, direction), in relation to each other and to an animal's hearing abilities (
                    <E T="03">e.g.,</E>
                     sensitivity, frequency range, critical ratios, frequency discrimination, directional discrimination, age or TTS hearing loss), and existing ambient noise and propagation conditions. Masking of natural sounds can result when human activities produce high levels of background sound at frequencies important to marine mammals. Conversely, if the background level of underwater sound is high (
                    <E T="03">e.g.,</E>
                     on a day with strong wind and high waves), an anthropogenic sound source would not be detectable as far away as would be possible under quieter conditions and would itself be masked.
                </P>
                <P>
                    <E T="03">Airborne Acoustic Effects</E>
                    —Although pinnipeds are known to haul out regularly on man-made objects, we believe that incidents of take resulting solely from airborne sound are unlikely due to the sheltered proximity between the proposed project area and haulout sites (outside of Sitka Channel). There is a possibility that an animal could surface in-water, but with head out, within the area in which airborne sound exceeds relevant thresholds and thereby be exposed to levels of airborne sound that we associate with harassment, but any such occurrence would likely be accounted for in our estimation of incidental take from underwater sound. Therefore, authorization of incidental take resulting from airborne sound for pinnipeds is not warranted, and airborne sound is not discussed further here. Cetaceans are not expected to be exposed to airborne sounds that would result in harassment as defined under the MMPA.
                </P>
                <HD SOURCE="HD3">Marine Mammal Habitat Effects</HD>
                <P>CBS's construction activities could have localized, temporary impacts on marine mammal habitat and their prey by increasing in-water sound pressure levels and slightly decreasing water quality. However, its proposed location is within the Sitka harbor and is located in an area that is currently used by numerous commercial fishing and personal vessels. Construction activities are of short duration and would likely have temporary impacts on marine mammal habitat through increases in underwater and airborne sound. Increased noise levels may affect acoustic habitat (see masking discussion above) and adversely affect marine mammal prey in the vicinity of the project area (see discussion below). During DTH drilling, impact, and vibratory pile driving, elevated levels of underwater noise would ensonify the project area where both fish and mammals occur and could affect foraging success. Additionally, marine mammals may avoid the area during construction; however, displacement due to noise is expected to be temporary and is not expected to result in long-term effects to the individuals or populations.</P>
                <P>
                    Temporary and localized increase in turbidity near the seafloor would occur in the immediate area surrounding the area where piles are installed or removed. In general, turbidity associated with pile installation is localized to about a 25-ft (7.6 m) radius around the pile (Everitt 
                    <E T="03">et al.,</E>
                     1980). The sediments of the project site would settle out rapidly when disturbed. Cetaceans are not expected to be close enough to the pile driving areas to experience effects of turbidity, and any pinnipeds could avoid localized areas of turbidity. Therefore, we expect the impact from increased turbidity levels to be discountable to marine mammals and do not discuss it further.
                    <PRTPAGE P="1894"/>
                </P>
                <HD SOURCE="HD2">In-Water Construction Effects on Potential Foraging Habitat</HD>
                <P>The proposed activities would not result in permanent impacts to habitats used directly by marine mammals as the project would not expand outside of the Sitka Channel, and no increases in vessel traffic in the area are expected as a result of this project. The total seafloor area likely impacted by the project is relatively small compared to the available habitat in Southeast Alaska. Sitka Sound is included as a BIA for humpback whales and gray whales, however the action area is within the breakwaters where baleen whales are rare. Additionally, the area already has elevated noise levels because of busy vessel traffic transiting through the area, and critical habitat impacts would not be permanent nor would it result long-term effects to the local population. No known rookeries or major haulouts would be impacted. Additionally, the total seafloor area affected by pile installation and removal is a small area compared to the vast foraging area available to marine mammals in the area. At best, the impact area provides marginal foraging habitat for marine mammals and fishes. Furthermore, pile driving at the project site would not obstruct movements or migration of marine mammals.</P>
                <HD SOURCE="HD2">Effects on Potential Prey</HD>
                <P>
                    Sound may affect marine mammals through impacts on the abundance, behavior, or distribution of prey species (
                    <E T="03">e.g.,</E>
                     crustaceans, cephalopods, fish, zooplankton, 
                    <E T="03">etc.</E>
                    ). Marine mammal prey varies by species, season, and location. Here, we describe studies regarding the effects of noise on known marine mammal prey.
                </P>
                <P>
                    Fish utilize the soundscape and components of sound in their environment to perform important functions such as foraging, predator avoidance, mating, and spawning (
                    <E T="03">e.g.,</E>
                     Zelick and Mann, 1999; Fay, 2009). Depending on their hearing anatomy and peripheral sensory structures, which vary among species, fishes hear sounds using pressure and particle motion sensitivity capabilities and detect the motion of surrounding water (Fay 
                    <E T="03">et al.,</E>
                     2008). The potential effects of noise on fishes depends on the overlapping frequency range, distance from the sound source, water depth of exposure, and species-specific hearing sensitivity, anatomy, and physiology. Key impacts to fishes may include behavioral responses, hearing damage, barotrauma (pressure-related injuries), and mortality.
                </P>
                <P>
                    Fish react to sounds which are especially strong and/or intermittent low-frequency sounds, and behavioral responses such as flight or avoidance are the most likely effects. Short duration, sharp sounds can cause overt or subtle changes in fish behavior and local distribution. The reaction of fish to noise depends on the physiological state of the fish, past exposures, motivation (
                    <E T="03">e.g.,</E>
                     feeding, spawning, migration), and other environmental factors. Hastings and Popper (2005) identified several studies that suggest fish may relocate to avoid certain areas of sound energy. Additional studies have documented effects of pile driving on fish, although several are based on studies in support of large, multiyear bridge construction projects (
                    <E T="03">e.g.,</E>
                     Scholik and Yan, 2001, 2002; Popper and Hastings, 2009). Several studies have demonstrated that impulse sounds might affect the distribution and behavior of some fishes, potentially impacting foraging opportunities or increasing energetic costs (
                    <E T="03">e.g.,</E>
                     Fewtrell and McCauley, 2012; Pearson 
                    <E T="03">et al.,</E>
                     1992; Skalski 
                    <E T="03">et al.,</E>
                     1992; Santulli 
                    <E T="03">et al.,</E>
                     1999; Paxton 
                    <E T="03">et al.,</E>
                     2017). However, some studies have shown no or slight reaction to impulse sounds (
                    <E T="03">e.g.,</E>
                     Wardle 
                    <E T="03">et al.,</E>
                     2001; Jorgenson and Gyselman, 2009).
                </P>
                <P>
                    SPLs of sufficient strength have been known to cause injury to fish and fish mortality. However, in most fish species, hair cells in the ear continuously regenerate and loss of auditory function likely is restored when damaged cells are replaced with new cells. Halvorsen 
                    <E T="03">et al.</E>
                     (2012a) showed that a TTS of 4-6 dB was recoverable within 24 hours for one species. Impacts would be most severe when the individual fish is close to the source and when the duration of exposure is long. Injury caused by barotrauma can range from slight to severe and can cause death, and is most likely for fish with swim bladders. Barotrauma injuries have been documented during controlled exposure to impact pile driving (Halvorsen 
                    <E T="03">et al.,</E>
                     2012b; Casper 
                    <E T="03">et al.,</E>
                     2013).
                </P>
                <P>The most likely impact to fish from pile driving activities at the project areas would be temporary behavioral avoidance of the area. The duration of fish avoidance of an area after pile driving stops is unknown, but a rapid return to normal recruitment, distribution and behavior is anticipated.</P>
                <P>Construction activities, in the form of increased turbidity, have the potential to adversely affect forage fish in the project area. Forage fish form a significant prey base for many marine mammal species that occur in the project area. Increased turbidity is expected to occur in the immediate vicinity (on the order of 10 ft (3 m) or less) of construction activities. However, suspended sediments and particulates are expected to dissipate quickly within a single tidal cycle. Given the limited area affected and high tidal dilution rates, any effects on forage fish are expected to be minor or negligible.</P>
                <P>
                    Avoidance by potential prey (
                    <E T="03">i.e.,</E>
                     fish) of the immediate area due to the temporary loss of this foraging habitat is also possible. The duration of fish avoidance of this area after pile driving stops is unknown, but a rapid return to normal recruitment, distribution and behavior is anticipated. Any behavioral avoidance by fish of the disturbed area would still leave significantly large areas of fish and marine mammal foraging habitat in the nearby vicinity.
                </P>
                <P>In summary, given the short daily duration of sound associated with individual pile driving events and the relatively small areas being affected, pile driving activities associated with the proposed action are not likely to have a permanent adverse effect on any fish habitat, or populations of fish species. Any behavioral avoidance by fish of the disturbed area would still leave significantly large areas of fish and marine mammal foraging habitat in the nearby vicinity. Thus, we conclude that impacts of the specified activity are not likely to have more than short-term adverse effects on any prey habitat or populations of prey species. Further, any impacts to marine mammal habitat are not expected to result in significant or long-term consequences for individual marine mammals, or to contribute to adverse impacts on their populations.</P>
                <HD SOURCE="HD1">Estimated Take of Marine Mammals</HD>
                <P>This section provides an estimate of the number of incidental takes proposed for authorization through the IHA, which will inform both NMFS' consideration of “small numbers,” and the negligible impact determinations.</P>
                <P>
                    Harassment is the only type of take expected to result from these activities. Except with respect to certain activities not pertinent here, section 3(18) of the MMPA defines “harassment” as any act of pursuit, torment, or annoyance, which (i) has the potential to injure a marine mammal or marine mammal stock in the wild (Level A harassment); or (ii) has the potential to disturb a marine mammal or marine mammal stock in the wild by causing disruption of behavioral patterns, including, but not limited to, migration, breathing, nursing, breeding, feeding, or sheltering (Level B harassment).
                    <PRTPAGE P="1895"/>
                </P>
                <P>
                    Authorized takes would primarily be by Level B harassment, as use of the acoustic sources (
                    <E T="03">i.e.,</E>
                     vibratory or impact pile driving and DTH drilling) has the potential to result in disruption of behavioral patterns for individual marine mammals. There is also some potential for auditory injury (Level A harassment) to result, primarily for harbor porpoise, harbor seals and Steller sea lions. Harbor porpoise have larger predicted auditory injury zones and due to their small size they could enter the Level A harassment zone and remain undetected for sufficient duration to incur auditory injury. While Steller sea lion do not have large Level A harassment zones, they are frequently sighted in the project area and therefor have some potential for auditory injury. Additionally harbor seals have larger Level A harassment zones and are common in the action area, and therefore have potential for auditory injury. Auditory injury is unlikely to occur for all other species, based on the unlikelihood of the species in the action area and the smaller Level A harassment zones. The proposed mitigation and monitoring measures are expected to minimize the severity of the taking to the extent practicable.
                </P>
                <P>As described previously, no serious injury or mortality is anticipated or proposed to be authorized for this activity. Below we describe how the proposed take numbers are estimated.</P>
                <P>
                    For acoustic impacts, generally speaking, we estimate take by considering: (1) acoustic thresholds above which NMFS believes the best available science indicates marine mammals will be behaviorally harassed or incur some degree of permanent hearing impairment; (2) the area or volume of water that will be ensonified above these levels in a day; (3) the density or occurrence of marine mammals within these ensonified areas; and, (4) the number of days of activities. We note that while these factors can contribute to a basic calculation to provide an initial prediction of potential takes, additional information that can qualitatively inform take estimates is also sometimes available (
                    <E T="03">e.g.,</E>
                     previous monitoring results or average group size). Below, we describe the factors considered here in more detail and present the proposed take estimates. 
                </P>
                <HD SOURCE="HD2">Acoustic Thresholds</HD>
                <P>NMFS recommends the use of acoustic thresholds that identify the received level of underwater sound above which exposed marine mammals would be reasonably expected to be behaviorally harassed (equated to Level B harassment) or to incur PTS of some degree (equated to Level A harassment).</P>
                <P>
                    <E T="03">Level B Harassment</E>
                    —Though significantly driven by received level, the onset of behavioral disturbance from anthropogenic noise exposure is also informed to varying degrees by other factors related to the source or exposure context (
                    <E T="03">e.g.,</E>
                     frequency, predictability, duty cycle, duration of the exposure, signal-to-noise ratio, distance to the source), the environment (
                    <E T="03">e.g.,</E>
                     bathymetry, other noises in the area, predators in the area), and the receiving animals (hearing, motivation, experience, demography, life stage, depth) and can be difficult to predict (
                    <E T="03">e.g.,</E>
                     Southall 
                    <E T="03">et al.,</E>
                     2007, 2021, Ellison 
                    <E T="03">et al.,</E>
                     2012). Based on what the available science indicates and the practical need to use a threshold based on a metric that is both predictable and measurable for most activities, NMFS typically uses a generalized acoustic threshold based on received level to estimate the onset of behavioral harassment. NMFS generally predicts that marine mammals are likely to be behaviorally harassed in a manner considered to be Level B harassment when exposed to underwater anthropogenic noise above root-mean-squared pressure received levels (RMS SPL) of 120 dB (referenced to 1 micropascal (re 1 μPa)) for continuous (
                    <E T="03">e.g.,</E>
                     vibratory pile driving, drilling) and above RMS SPL 160 dB re 1 μPa for non-explosive impulsive (
                    <E T="03">e.g.,</E>
                     seismic airguns) or intermittent (
                    <E T="03">e.g.,</E>
                     scientific sonar) sources. Generally speaking, Level B harassment take estimates based on these behavioral harassment thresholds are expected to include any likely takes by TTS as, in most cases, the likelihood of TTS occurs at distances from the source less than those at which behavioral harassment is likely. TTS of a sufficient degree can manifest as behavioral harassment, as reduced hearing sensitivity and the potential reduced opportunities to detect important signals (conspecific communication, predators, prey) may result in changes in behavior patterns that would not otherwise occur.
                </P>
                <P>CBS's proposed activity includes the use of continuous (vibratory hammer and DTH drilling) and impulsive (DTH drilling and impact pile driving) sources, and therefore the RMS SPL thresholds of 120 and 160 dB re 1 μPa are applicable.</P>
                <P>
                    <E T="03">Level A harassment</E>
                    —NMFS' Technical Guidance for Assessing the Effects of Anthropogenic Sound on Marine Mammal Hearing (Version 2.0) (Technical Guidance, 2018) identifies dual criteria to assess auditory injury (Level A harassment) to five different marine mammal groups (based on hearing sensitivity) as a result of exposure to noise from two different types of sources (impulsive or non-impulsive). CBS's proposed activity includes the use of impulsive (impact pile-driving and DTH drilling) and non-impulsive (vibratory hammer and DTH drilling) sources.
                </P>
                <P>
                    These thresholds are provided in the table below. The references, analysis, and methodology used in the development of the thresholds are described in NMFS' 2018 Technical Guidance, which may be accessed at: 
                    <E T="03">https://www.fisheries.noaa.gov/national/marine-mammal-protection/marine-mammal-acoustic-technical-guidance.</E>
                </P>
                <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s50,r50p,xs100">
                    <TTITLE>Table 5—Thresholds Identifying the Onset of Permanent Threshold Shift</TTITLE>
                    <BOXHD>
                        <CHED H="1">Hearing group</CHED>
                        <CHED H="1">
                            PTS onset acoustic thresholds * 
                            <LI>(received level)</LI>
                        </CHED>
                        <CHED H="2">Impulsive</CHED>
                        <CHED H="2">Non-impulsive</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Low-Frequency (LF) Cetaceans</ENT>
                        <ENT>
                            <E T="03">Cell 1: L</E>
                            <E T="0732">pk,flat</E>
                            <E T="03">:</E>
                             219 dB; 
                            <E T="03">L</E>
                            <E T="0732">E,LF,24h</E>
                            <E T="03">:</E>
                             183 dB
                        </ENT>
                        <ENT>
                            <E T="03">Cell 2: L</E>
                            <E T="0732">E,LF,24h</E>
                            <E T="03">:</E>
                             199 dB.
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Mid-Frequency (MF) Cetaceans</ENT>
                        <ENT>
                            <E T="03">Cell 3: L</E>
                            <E T="0732">pk,flat</E>
                            <E T="03">:</E>
                             230 dB; 
                            <E T="03">L</E>
                            <E T="0732">E,MF,24h</E>
                            <E T="03">:</E>
                             185 dB
                        </ENT>
                        <ENT>
                            <E T="03">Cell 4: L</E>
                            <E T="0732">E,MF,24h</E>
                            <E T="03">:</E>
                             198 dB.
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">High-Frequency (HF) Cetaceans</ENT>
                        <ENT>
                            <E T="03">Cell 5: L</E>
                            <E T="0732">pk,flat</E>
                            <E T="03">:</E>
                             202 dB; 
                            <E T="03">L</E>
                            <E T="0732">E,HF,24h</E>
                            <E T="03">:</E>
                             155 dB
                        </ENT>
                        <ENT>
                            <E T="03">Cell 6: L</E>
                            <E T="0732">E,HF,24h</E>
                            <E T="03">:</E>
                             173 dB.
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Phocid Pinnipeds (PW) (Underwater)</ENT>
                        <ENT>
                            <E T="03">Cell 7: L</E>
                            <E T="0732">pk,flat</E>
                            <E T="03">:</E>
                             218 dB; 
                            <E T="03">L</E>
                            <E T="0732">E,PW,24h</E>
                            <E T="03">:</E>
                             185 dB
                        </ENT>
                        <ENT>
                            <E T="03">Cell 8: L</E>
                            <E T="0732">E,PW,24h</E>
                            <E T="03">:</E>
                             201 dB.
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Otariid Pinnipeds (OW) (Underwater)</ENT>
                        <ENT>
                            <E T="03">Cell 9: L</E>
                            <E T="0732">pk,flat</E>
                            <E T="03">:</E>
                             232 dB; 
                            <E T="03">L</E>
                            <E T="0732">E,OW,24h</E>
                            <E T="03">:</E>
                             203 dB
                        </ENT>
                        <ENT>
                            <E T="03">Cell 10: L</E>
                            <E T="0732">E,OW,24h</E>
                            <E T="03">:</E>
                             219 dB.
                        </ENT>
                    </ROW>
                    <TNOTE>
                        * Dual metric acoustic thresholds for impulsive sounds: Use whichever results in the largest isopleth for calculating PTS onset. If a non-impulsive sound has the potential of exceeding the peak sound pressure level thresholds associated with impulsive sounds, these thresholds should also be considered.
                        <PRTPAGE P="1896"/>
                    </TNOTE>
                    <TNOTE>
                        <E T="02">Note:</E>
                         Peak sound pressure (
                        <E T="03">L</E>
                        <E T="0732">pk</E>
                        ) has a reference value of 1 µPa, and cumulative sound exposure level (
                        <E T="03">L</E>
                        <E T="0732">E</E>
                        ) has a reference value of 1 μPa
                        <SU>2</SU>
                        s. In this table, thresholds are abbreviated to reflect American National Standards Institute standards (ANSI 2013). However, peak sound pressure is defined by ANSI as incorporating frequency weighting, which is not the intent for this Technical Guidance. Hence, the subscript “flat” is being included to indicate peak sound pressure should be flat weighted or unweighted within the generalized hearing range. The subscript associated with cumulative sound exposure level thresholds indicates the designated marine mammal auditory weighting function (LF, MF, and HF cetaceans, and PW and OW pinnipeds) and that the recommended accumulation period is 24 hours. The cumulative sound exposure level thresholds could be exceeded in a multitude of ways (
                        <E T="03">i.e.,</E>
                         varying exposure levels and durations, duty cycle). When possible, it is valuable for action proponents to indicate the conditions under which these acoustic thresholds will be exceeded.
                    </TNOTE>
                </GPOTABLE>
                <HD SOURCE="HD2">Ensonified Area</HD>
                <P>Here, we describe operational and environmental parameters of the activity that are used in estimating the area ensonified above the acoustic thresholds, including source levels and transmission loss coefficient.</P>
                <P>
                    The sound field in the project area is the existing background noise plus additional construction noise from the proposed project. Marine mammals are expected to be affected via sound generated by the primary components of the project (
                    <E T="03">i.e.,</E>
                     impact pile driving, vibratory pile driving and removal, and DTH).
                </P>
                <P>In order to calculate distances to the Level A harassment and Level B harassment thresholds for the methods and piles being used in this project, NMFS used acoustic monitoring data from other locations to develop source levels for the various pile types, sizes and methods (table 6). This analysis uses practical spreading loss, a standard assumption regarding sound propagation for similar environments, to estimate transmission of sound through water. For this analysis, the transmission loss factor of 15 (4.5 dB per doubling of distance) is used. A weighting adjustment factor of 2.5 or 2, a standard default value for vibratory pile driving and removal or impact driving and DTH respectively, were used to calculate Level A harassment areas.</P>
                <P>
                    NMFS recommends treating DTH systems as both impulsive and continuous, non-impulsive sound source types simultaneously. Thus, impulsive thresholds are used to evaluate Level A harassment, and continuous thresholds are used to evaluate Level B harassment. With regards to DTH mono-hammers, NMFS recommends proxy levels for Level A harassment based on available data regarding DTH systems of similar sized piles and holes (Denes 
                    <E T="03">et al.,</E>
                     2019; Guan and Miner, 2020; Reyff and Heyvaert, 2019; Reyff, 2020; Heyvaert and Reyff, 2021) (table 1 and 2 includes number of piles and duration for each phase; table 6 includes peak pressure, sound pressure, and sound exposure levels for each pile type).
                </P>
                <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s50,24,r50">
                    <TTITLE>Table 6—Estimates Underwater Proxy Source Level for Pile Installation and Removal</TTITLE>
                    <BOXHD>
                        <CHED H="1">Method and pile type</CHED>
                        <CHED H="1">Sound source at 10 meters</CHED>
                        <CHED H="1">Source</CHED>
                    </BOXHD>
                    <ROW RUL="s">
                        <ENT I="21">Vibratory Hammer</ENT>
                        <ENT O="oi0">dB rms</ENT>
                        <ENT O="xl"/>
                    </ROW>
                    <ROW>
                        <ENT I="01">16 in</ENT>
                        <ENT>161</ENT>
                        <ENT>NAVFAC 2015.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">24 in</ENT>
                        <ENT>161</ENT>
                        <ENT>NAVFAC 2015.</ENT>
                    </ROW>
                </GPOTABLE>
                <GPOTABLE COLS="5" OPTS="L2,ns,tp0,p0,8/9,i1" CDEF="s50,7,7,7,r50">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1"> </CHED>
                        <CHED H="1"> </CHED>
                        <CHED H="1"> </CHED>
                        <CHED H="1"> </CHED>
                    </BOXHD>
                    <ROW RUL="s">
                        <ENT I="21">DTH Drill</ENT>
                        <ENT O="oi0">dB rms</ENT>
                        <ENT O="oi0">dB SEL</ENT>
                        <ENT O="oi0">dB peak</ENT>
                        <ENT O="xl"/>
                    </ROW>
                    <ROW>
                        <ENT I="01">16 in</ENT>
                        <ENT>167</ENT>
                        <ENT>146</ENT>
                        <ENT>172</ENT>
                        <ENT>Heyvaert and Reyff 2021, Guan and Miner 2020.</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">24 in</ENT>
                        <ENT>167</ENT>
                        <ENT>159</ENT>
                        <ENT>184</ENT>
                        <ENT>Heyvaert and Reyff 2021.</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="21">Impact Hammer</ENT>
                        <ENT O="oi0">dB rms</ENT>
                        <ENT O="oi0">dB SEL</ENT>
                        <ENT O="oi0">dB peak</ENT>
                        <ENT O="xl"/>
                    </ROW>
                    <ROW>
                        <ENT I="01">16 in</ENT>
                        <ENT>185</ENT>
                        <ENT>175</ENT>
                        <ENT>200</ENT>
                        <ENT>Caltrans 2020.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">24 in</ENT>
                        <ENT>190</ENT>
                        <ENT>177</ENT>
                        <ENT>203</ENT>
                        <ENT>Caltrans 2015.</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD2">Level B Harassment Zones</HD>
                <P>Transmission loss (TL) is the decrease in acoustic intensity as an acoustic pressure wave propagates out from a source. TL parameters vary with frequency, temperature, sea conditions, current, source and receiver depth, water depth, water chemistry, and bottom composition and topography. The general formula for underwater TL is:</P>
                <FP SOURCE="FP-2">
                    TL = B * log
                    <E T="52">10</E>
                     (R
                    <E T="52">1</E>
                    /R
                    <E T="52">2</E>
                    ),
                </FP>
                <EXTRACT>
                    <FP SOURCE="FP-2">Where: </FP>
                    <FP SOURCE="FP-2">TL = transmission loss in dB</FP>
                    <FP SOURCE="FP-2">B = transmission loss coefficient; for practical spreading equals 15</FP>
                    <FP SOURCE="FP-2">
                        R
                        <E T="52">1</E>
                         = the distance of the modeled SPL from the driven pile, and
                    </FP>
                    <FP SOURCE="FP-2">
                        R
                        <E T="52">2</E>
                         = the distance from the driven pile of the initial measurement.
                    </FP>
                </EXTRACT>
                <P>The recommended TL coefficient for most nearshore environments is the practical spreading value of 15. This value results in an expected propagation environment that would lie between spherical and cylindrical spreading loss conditions, which is the most appropriate assumption for CBS's proposed underwater activities. The Level B harassment zones and approximate amount of area ensonified for the proposed underwater activities are shown in table 7.</P>
                <HD SOURCE="HD2">Level A Harassment Zones</HD>
                <P>
                    The ensonified area associated with Level A harassment is more technically challenging to predict due to the need to account for a duration component. Therefore, NMFS developed an optional User Spreadsheet tool to accompany the Technical Guidance that can be used to relatively simply predict an isopleth distance for use in conjunction with marine mammal density or occurrence to help predict potential takes. We note that because of some of the assumptions included in the methods underlying this optional tool, we anticipate that the resulting isopleth estimates are typically going to be overestimates of some degree, which may result in an overestimate of potential take by Level A harassment. However, this optional tool offers the best way to estimate isopleth distances when more sophisticated modeling methods are not available or practical. For stationary sources such as pile installation or removal, the optional User Spreadsheet 
                    <PRTPAGE P="1897"/>
                    tool predicts the distance at which, if a marine mammal remained at that distance for the duration of the activity, it would be expected to incur PTS. The isopleths generated by the User Spreadsheet used the same TL coefficient as the Level B harassment zone calculations (
                    <E T="03">i.e.,</E>
                     the practical spreading value of 15). Inputs used in the User Spreadsheet (
                    <E T="03">e.g.,</E>
                     number of piles per day, duration and/or strikes per pile) are presented in tables 1 and 2. The maximum RMS SPL, SEL, and resulting isopleths are reported in tables 6 and 7.
                </P>
                <GPOTABLE COLS="7" OPTS="L2,p7,7/8,i1" CDEF="s50,10,10,10,10,10,10">
                    <TTITLE>Table 7—Level A and Level B Harassment Isopleths for Pile Driving Activities</TTITLE>
                    <BOXHD>
                        <CHED H="1">Activity</CHED>
                        <CHED H="1">
                            Level A isopleth
                            <LI>(m)</LI>
                        </CHED>
                        <CHED H="2">LF</CHED>
                        <CHED H="2">MF</CHED>
                        <CHED H="2">HF</CHED>
                        <CHED H="2">Phocids</CHED>
                        <CHED H="2">Otariids</CHED>
                        <CHED H="1">
                            Level B isopleth
                            <LI>(m)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW EXPSTB="06" RUL="s">
                        <ENT I="21">
                            <E T="02">Vibratory Pile Removal/Installation</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="22">Phase I:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">16-in temp install</ENT>
                        <ENT>6.8</ENT>
                        <ENT>0.6</ENT>
                        <ENT>10.1</ENT>
                        <ENT>4.2</ENT>
                        <ENT>0.3</ENT>
                        <ENT>5,411.7</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">16-in temp removal</ENT>
                        <ENT>6.8</ENT>
                        <ENT>0.6</ENT>
                        <ENT>10.1</ENT>
                        <ENT>4.2</ENT>
                        <ENT>0.3</ENT>
                        <ENT>5,411.7</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">16-in perm install</ENT>
                        <ENT>6.8</ENT>
                        <ENT>0.6</ENT>
                        <ENT>10.1</ENT>
                        <ENT>4.2</ENT>
                        <ENT>0.3</ENT>
                        <ENT>5,411.7</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">24-in perm install</ENT>
                        <ENT>6.8</ENT>
                        <ENT>0.6</ENT>
                        <ENT>10.1</ENT>
                        <ENT>4.2</ENT>
                        <ENT>0.3</ENT>
                        <ENT>5,411.7</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Phase II:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">16-in temp install</ENT>
                        <ENT>6.8</ENT>
                        <ENT>0.6</ENT>
                        <ENT>10.1</ENT>
                        <ENT>4.2</ENT>
                        <ENT>0.3</ENT>
                        <ENT>5,411.7</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">16-in temp removal</ENT>
                        <ENT>6.8</ENT>
                        <ENT>0.6</ENT>
                        <ENT>10.1</ENT>
                        <ENT>4.2</ENT>
                        <ENT>0.3</ENT>
                        <ENT>5,411.7</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="03">24-in perm install</ENT>
                        <ENT>6.8</ENT>
                        <ENT>0.6</ENT>
                        <ENT>10.1</ENT>
                        <ENT>4.2</ENT>
                        <ENT>0.3</ENT>
                        <ENT>5,411.7</ENT>
                    </ROW>
                    <ROW EXPSTB="06" RUL="s">
                        <ENT I="21">
                            <E T="02">DTH Pile Installation</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="22">Phase I:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">16-in perm install</ENT>
                        <ENT>59</ENT>
                        <ENT>2.1</ENT>
                        <ENT>70.3</ENT>
                        <ENT>31.6</ENT>
                        <ENT>2.3</ENT>
                        <ENT>
                            <SU>1</SU>
                             8,500
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">24-in perm install</ENT>
                        <ENT>568.9</ENT>
                        <ENT>20.2</ENT>
                        <ENT>677.6</ENT>
                        <ENT>304.4</ENT>
                        <ENT>22.2</ENT>
                        <ENT>
                            <SU>1</SU>
                             8,500
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Phase II:</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="03">24-in perm install</ENT>
                        <ENT>568.9</ENT>
                        <ENT>20.2</ENT>
                        <ENT>677.6</ENT>
                        <ENT>304.4</ENT>
                        <ENT>22.2</ENT>
                        <ENT>
                            <SU>1</SU>
                             8,500
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="06" RUL="s">
                        <ENT I="21">
                            <E T="02">Impact Pile Installation</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="22">Phase I:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">16-in temp install</ENT>
                        <ENT>231</ENT>
                        <ENT>8.2</ENT>
                        <ENT>275</ENT>
                        <ENT>123</ENT>
                        <ENT>9</ENT>
                        <ENT>464.2</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">16-in perm install</ENT>
                        <ENT>231</ENT>
                        <ENT>8.2</ENT>
                        <ENT>275</ENT>
                        <ENT>123</ENT>
                        <ENT>9</ENT>
                        <ENT>464.2</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">24-in perm install</ENT>
                        <ENT>313</ENT>
                        <ENT>11.1</ENT>
                        <ENT>373</ENT>
                        <ENT>168</ENT>
                        <ENT>12.2</ENT>
                        <ENT>1,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Phase II:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">16-in temp install</ENT>
                        <ENT>231</ENT>
                        <ENT>8.2</ENT>
                        <ENT>275</ENT>
                        <ENT>123</ENT>
                        <ENT>9</ENT>
                        <ENT>464.2</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">24-in perm install</ENT>
                        <ENT>313</ENT>
                        <ENT>11.1</ENT>
                        <ENT>373</ENT>
                        <ENT>168</ENT>
                        <ENT>12.2</ENT>
                        <ENT>1,000</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>1</SU>
                         The calculated Level B harassment zone is 13,594 m. However, the farthest distance that sound will transmit from the source is 8,500 m before transmission is stopped by landmasses.
                    </TNOTE>
                </GPOTABLE>
                <HD SOURCE="HD2">Marine Mammal Occurrence</HD>
                <P>In this section we provide information about the occurrence of marine mammals, including density or other relevant information which will inform the take calculations.</P>
                <P>Daily occurrence probability of each marine mammal species in the action area is based on consultation with previous monitoring reports, local researchers and marine professionals. Occurrence probability estimates are based on conservative density approximations for each species and factor in historic data of occurrence, seasonality, and group size in Sitka Sound and Sitka Channel. A summary of proposed occurrence is shown in table 9. To accurately describe species occurrence near the action area, marine mammals were described as either common (species sighted consistently during all monitoring efforts in the project vicinity, assume one to two groups per day), frequent (species sighted with some consistency during most monitoring efforts in the project vicinity, assume one group per week), or infrequent (species sighted occasionally during a few monitoring efforts in the project vicinity, assume one group per 2 weeks).</P>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,r50,12,xs80">
                    <TTITLE>Table 8—Estimated Occurrence of Group Sightings of Marine Mammal Species</TTITLE>
                    <BOXHD>
                        <CHED H="1">Species</CHED>
                        <CHED H="1">Frequency</CHED>
                        <CHED H="1">Average group size</CHED>
                        <CHED H="1">Expected occurrence</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Humpback whale</ENT>
                        <ENT>Frequent</ENT>
                        <ENT>3.4</ENT>
                        <ENT>1 group/week.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Minke whale 
                            <SU>1</SU>
                        </ENT>
                        <ENT>Infrequent</ENT>
                        <ENT>3.5</ENT>
                        <ENT>1 group/2 weeks.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Gray whale</ENT>
                        <ENT>Infrequent</ENT>
                        <ENT>3.5</ENT>
                        <ENT>1 group/2 weeks.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Killer whale</ENT>
                        <ENT>Frequent</ENT>
                        <ENT>6.6</ENT>
                        <ENT>1 group/week.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Harbor porpoise</ENT>
                        <ENT>Infrequent</ENT>
                        <ENT>5.0</ENT>
                        <ENT>1 group/2 weeks.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Harbor seal 
                            <SU>2</SU>
                        </ENT>
                        <ENT>Common</ENT>
                        <ENT>2.1</ENT>
                        <ENT>1-2 groups/day.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Steller sea lion 
                            <SU>2</SU>
                        </ENT>
                        <ENT>Common</ENT>
                        <ENT>2.0</ENT>
                        <ENT>1-2 groups/day.</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>1</SU>
                         Minke whale considered rare in Sitka Channel, but to be conservative they are treated as infrequent for take estimation as there is a small likelihood they could be in the area during the activity.
                    </TNOTE>
                    <TNOTE>
                        <SU>2</SU>
                         Likelihood of one group/day in the Level A harassment zone and likelihood of two groups/day in the level B harassment zone.
                    </TNOTE>
                </GPOTABLE>
                <PRTPAGE P="1898"/>
                <HD SOURCE="HD2">Take Estimation</HD>
                <P>Here we describe how the information provided above is synthesized to produce a quantitative estimate of the take that is reasonably likely to occur and proposed for authorization.</P>
                <P>For the total underwater take estimate, the daily occurrence probability for a species was multiplied by the estimated group size and by the number of days of each type of pile driving activity. Group size is based on the best available published research for these species and their presence in the action area.</P>
                <FP>Estimated take = Group size × Groups per day × Days of pile driving activity</FP>
                <P>Take by Level A harassment is requested for Steller sea lions and harbor seals. Although Steller sea lion Level A harassment zones are small, as previously discussed they are known to spend extended periods of time within the breakwaters in Sitka sound and in the project area. Harbor seals are also common in the project area and although their Level A harassment zones are farther from the project area, CBS has requested a maximum shutdown zone of 125 m for harbor seals and therefor there is likelihood for take by Level A harassment of harbor seals. Take by Level A harassment is also requested for harbor porpoise. We are proposing a maximum shutdown zone for high frequency species of 300 m and therefor there is likelihood for some take by Level A harassment. Even though they are not as common within the breakwaters, their Level A harassment zone extends beyond the breakwaters and they are elusive in nature. The take by Level A harassment for both pinniped species, are based on a lower daily occurrence rate based on the frequency of sightings within the smaller Level A harassment zone of the breakwaters (table 8).</P>
                <P>Additionally, for species that are large and/or infrequent (gray whale, minke whale, humpback whale, and harbor porpoise) in Sitka Sound and are unlikely to be within the breakwaters where the proposed action will take place, take by Level B harassment is only anticipated to occur incidental to vibratory and DTH methods, given the larger Level B harassment zones which will extend beyond the breakwaters. Anticipated take by Level A harassment for harbor seal and harbor porpoise would likely occur only incidental to impact pile driving and DTH drilling, and anticipated take of Steller sea lion by Level A harassment would likely occur only incidental to DTH drilling, due to the larger Level A harassment zones for these activities. See table 7.</P>
                <GPOTABLE COLS="8" OPTS="L2,p7,7/8,i1" CDEF="s50,r50,10,10,10,10,10,10">
                    <TTITLE>Table 9—Proposed Take of Marine Mammals by Level A and Level B Harassment and Percent of Stock Proposed To Be Taken</TTITLE>
                    <BOXHD>
                        <CHED H="1">Species</CHED>
                        <CHED H="1">Stock</CHED>
                        <CHED H="1">Phase 1</CHED>
                        <CHED H="2">Level A</CHED>
                        <CHED H="2">Level B</CHED>
                        <CHED H="2">
                            Percent of
                            <LI>stock</LI>
                        </CHED>
                        <CHED H="1">Phase 2</CHED>
                        <CHED H="2">Level A</CHED>
                        <CHED H="2">Level B</CHED>
                        <CHED H="2">
                            Percent of
                            <LI>stock</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">
                            Humpback whale 
                            <SU>1</SU>
                        </ENT>
                        <ENT>Hawai'i</ENT>
                        <ENT>0</ENT>
                        <ENT>11</ENT>
                        <ENT>0.1</ENT>
                        <ENT>0</ENT>
                        <ENT>* 4</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>
                            Mexico-North Pacific 
                            <SU>2</SU>
                        </ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Gray Whale</ENT>
                        <ENT>Eastern North Pacific</ENT>
                        <ENT>0</ENT>
                        <ENT>6</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>* 4</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Minke Whale</ENT>
                        <ENT>Alaska</ENT>
                        <ENT>0</ENT>
                        <ENT>6</ENT>
                        <ENT>NA</ENT>
                        <ENT>0</ENT>
                        <ENT>* 4</ENT>
                        <ENT>NA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Killer whale</ENT>
                        <ENT>West Coast Transients</ENT>
                        <ENT>0</ENT>
                        <ENT>3</ENT>
                        <ENT>0.9</ENT>
                        <ENT>0</ENT>
                        <ENT>1</ENT>
                        <ENT>0.3</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Gulf, Aleutian, Bering Transient</ENT>
                        <ENT>0</ENT>
                        <ENT>6</ENT>
                        <ENT>0.9</ENT>
                        <ENT>0</ENT>
                        <ENT>2</ENT>
                        <ENT>0.3</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Northern Resident</ENT>
                        <ENT>0</ENT>
                        <ENT>3</ENT>
                        <ENT>0.9</ENT>
                        <ENT>0</ENT>
                        <ENT>1</ENT>
                        <ENT>0.3</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Alaska Resident</ENT>
                        <ENT>0</ENT>
                        <ENT>18</ENT>
                        <ENT>0.9</ENT>
                        <ENT>0</ENT>
                        <ENT>6</ENT>
                        <ENT>0.3</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Harbor porpoise</ENT>
                        <ENT>Northern Southeast Alaska</ENT>
                        <ENT>* 5</ENT>
                        <ENT>8</ENT>
                        <ENT>0.9</ENT>
                        <ENT>* 5</ENT>
                        <ENT>* 5</ENT>
                        <ENT>0.7</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Harbor seal</ENT>
                        <ENT>Sitka/Chatham Alaska</ENT>
                        <ENT>48</ENT>
                        <ENT>130</ENT>
                        <ENT>1.3</ENT>
                        <ENT>13</ENT>
                        <ENT>38</ENT>
                        <ENT>0.4</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Steller sea lion</ENT>
                        <ENT>Eastern US</ENT>
                        <ENT>16</ENT>
                        <ENT>121</ENT>
                        <ENT>0.3</ENT>
                        <ENT>6</ENT>
                        <ENT>35</ENT>
                        <ENT>0.1</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Western US</ENT>
                        <ENT>0</ENT>
                        <ENT>3</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>2*</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>1</SU>
                         Take estimates are weighted based on calculated percentages of population for each distinct stock, assuming animals present would follow same probability of presence in project area. Humpback whale probability by stock based on Southeast Alaska estimates from NMFS 2021 (98 percent Hawaii DPS; 2 percent Mexico DPS).
                    </TNOTE>
                    <TNOTE>
                        <SU>2</SU>
                         ESA listed Mexico humpback whales take calculation resulted in less than 0.5 takes, therefore no takes are anticipate or are proposed for authorization.
                    </TNOTE>
                    <TNOTE>* Where proposed calculated take was less than the average group size, the take was rounded up to a group size as that is likely what would be encountered.</TNOTE>
                </GPOTABLE>
                <HD SOURCE="HD1">Proposed Mitigation</HD>
                <P>In order to issue an IHA under section 101(a)(5)(D) of the MMPA, NMFS must set forth the permissible methods of taking pursuant to the activity, and other means of effecting the least practicable impact on the species or stock and its habitat, paying particular attention to rookeries, mating grounds, and areas of similar significance, and on the availability of the species or stock for taking for certain subsistence uses. NMFS regulations require applicants for incidental take authorizations to include information about the availability and feasibility (economic and technological) of equipment, methods, and manner of conducting the activity or other means of effecting the least practicable adverse impact upon the affected species or stocks, and their habitat (50 CFR 216.104(a)(11)).</P>
                <P>In evaluating how mitigation may or may not be appropriate to ensure the least practicable adverse impact on species or stocks and their habitat, as well as subsistence uses where applicable, NMFS considers two primary factors:</P>
                <P>(1) The manner in which, and the degree to which, the successful implementation of the measure(s) is expected to reduce impacts to marine mammals, marine mammal species or stocks, and their habitat, as well as subsistence uses. This considers the nature of the potential adverse impact being mitigated (likelihood, scope, range). It further considers the likelihood that the measure will be effective if implemented (probability of accomplishing the mitigating result if implemented as planned), the likelihood of effective implementation (probability implemented as planned), and;</P>
                <P>(2) The practicability of the measures for applicant implementation, which may consider such things as cost, and impact on operations.</P>
                <HD SOURCE="HD2">Mitigation Measures</HD>
                <P>For each IHA, CBS must follow mitigation measures as specified below:</P>
                <P>• Ensure that construction supervisors and crews, the monitoring team, and relevant CBS staff are trained prior to the start of all pile driving and DTH drilling activity, so that responsibilities, communication procedures, monitoring protocols, and operational procedures are clearly understood. New personnel joining during the project must be trained prior to commencing work;</P>
                <P>
                    • Employ Protected Species Observers (PSOs) and establish 
                    <PRTPAGE P="1899"/>
                    monitoring locations as described in the application and the IHA. The Holder must monitor the project area to the maximum extent possible based on the required number of PSOs, required monitoring locations, and environmental conditions. For all pile driving and removal at least one PSO must be used. The PSO will be stationed as close to the activity as possible;
                </P>
                <P>• The placement of the PSOs during all pile driving and removal and DTH drilling activities will ensure that the entire shutdown zone is visible during pile installation;</P>
                <P>
                    • Monitoring must take place from 30 minutes prior to initiation of pile driving or DTH drilling activity (
                    <E T="03">i.e.,</E>
                     pre-clearance monitoring) through 30 minutes post-completion of pile driving or DTH drilling activity;
                </P>
                <P>• Pre-start clearance monitoring must be conducted during periods of visibility sufficient for the lead PSO to determine that the shutdown zones indicated in table 10 are clear of marine mammals. Pile driving and DTH drilling may commence following 30 minutes of observation when the determination is made that the shutdown zones are clear of marine mammals;</P>
                <P>• CBS must use soft start techniques when impact pile driving. Soft start requires contractors to provide an initial set of three strikes at reduced energy, followed by a 30-second waiting period, then two subsequent reduced-energy strike sets. A soft start must be implemented at the start of each day's impact pile driving and at any time following cessation of impact pile driving for a period of 30 minutes or longer; and</P>
                <P>• If a marine mammal is observed entering or within the shutdown zones indicated in table 10, pile driving and DTH drilling must be delayed or halted. If pile driving is delayed or halted due to the presence of a marine mammal, the activity may not commence or resume until either the animal has voluntarily exited and been visually confirmed beyond the shutdown zone (table 11) or 15 minutes have passed without re-detection of the animal.</P>
                <P>As proposed by the applicant, in water activities will take place only between civil dawn and civil dusk when PSOs can effectively monitor for the presence of marine mammals; during conditions with a Beaufort sea state of 4 or less. Pile driving and DTH drilling may continue for up to 30 minutes after sunset during evening civil twilight, as necessary to secure a pile for safety prior to demobilization during this time. The length of the post-activity monitoring period may be reduced if darkness precludes visibility of the shutdown and monitoring zones.</P>
                <HD SOURCE="HD2">Shutdown Zones</HD>
                <P>CBS will establish shutdown zones for all pile driving and DTH drilling activities. The purpose of a shutdown zone is generally to define an area within which shutdown of the activity would occur upon sighting of a marine mammal (or in anticipation of an animal entering the defined area). Shutdown zones would be based upon the Level A harassment isopleth for each pile size/type and driving method where applicable, as shown in table 10.</P>
                <P>For in-water heavy machinery activities other than pile driving, if a marine mammal comes within 10 m, work will stop and vessels will reduce speed to the minimum level required to maintain steerage and safe working conditions. A 10 m shutdown zone serves to protect marine mammals from physical interactions with project vessels during pile driving and other construction activities, such as barge positioning or drilling. If an activity is delayed or halted due to the presence of a marine mammal, the activity may not commence or resume until either the animal has voluntarily exited and been visually confirmed beyond the shutdown zone indicated in table 10 or 15 minutes have passed without re-detection of the animal. Construction activities must be halted upon observation of a species for which incidental take is not authorized or a species for which incidental take has been authorized but the authorized number of takes has been met entering or within the harassment zone.</P>
                <P>All marine mammals will be monitored in the Level B harassment zones and throughout the area as far as visual monitoring can take place. If a marine mammal enters the Level B harassment zone, construction activities including in-water work will continue and the animal's presence within the estimated harassment zone will be documented.</P>
                <P>CBS would also establish shutdown zones for all marine mammals for which take has not been authorized or for which incidental take has been authorized but the authorized number of takes has been met. These zones are equivalent to the Level B harassment zones for each activity. If a marine mammal species not covered under this IHA enters the shutdown zone, all in-water activities will cease until the animal leaves the zone or has not been observed for at least 15 minutes, and NMFS will be notified about species and precautions taken. Pile driving will proceed if the non-IHA species is observed to leave the Level B harassment zone or if 15 minutes have passed since the last observation.</P>
                <P>If shutdown and/or clearance procedures would result in an imminent safety concern, as determined by CBS or its designated officials, the in-water activity will be allowed to continue until the safety concern has been addressed, and the animal will be continuously monitored.</P>
                <GPOTABLE COLS="7" OPTS="L2,p7,7/8,i1" CDEF="s50,10,10,10,10,10,10">
                    <TTITLE>Table 10—Proposed Shutdown and Monitoring Zones</TTITLE>
                    <BOXHD>
                        <CHED H="1">Activity</CHED>
                        <CHED H="1">
                            Level A isopleth
                            <LI>(m)</LI>
                        </CHED>
                        <CHED H="2">LF</CHED>
                        <CHED H="2">MF</CHED>
                        <CHED H="2">
                            HF 
                            <SU>2</SU>
                        </CHED>
                        <CHED H="2">
                            Phocids 
                            <SU>1</SU>
                        </CHED>
                        <CHED H="2">Otariids</CHED>
                        <CHED H="1">
                            Level B isopleth
                            <LI>(m)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW EXPSTB="06" RUL="s">
                        <ENT I="21">
                            <E T="02">Vibratory Pile Removal/Installation</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="22">Phase I:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">16-in temp install</ENT>
                        <ENT>10</ENT>
                        <ENT>10</ENT>
                        <ENT>20</ENT>
                        <ENT>10</ENT>
                        <ENT>10</ENT>
                        <ENT>5,415</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">16-in temp removal</ENT>
                        <ENT>10</ENT>
                        <ENT>10</ENT>
                        <ENT>20</ENT>
                        <ENT>10</ENT>
                        <ENT>10</ENT>
                        <ENT>5,415</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">16-in perm install</ENT>
                        <ENT>10</ENT>
                        <ENT>10</ENT>
                        <ENT>20</ENT>
                        <ENT>10</ENT>
                        <ENT>10</ENT>
                        <ENT>5,415</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">24-in perm install</ENT>
                        <ENT>10</ENT>
                        <ENT>10</ENT>
                        <ENT>20</ENT>
                        <ENT>10</ENT>
                        <ENT>10</ENT>
                        <ENT>5,415</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Phase II:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">16-in temp install</ENT>
                        <ENT>10</ENT>
                        <ENT>10</ENT>
                        <ENT>20</ENT>
                        <ENT>10</ENT>
                        <ENT>10</ENT>
                        <ENT>5,415</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">16-in temp removal</ENT>
                        <ENT>10</ENT>
                        <ENT>10</ENT>
                        <ENT>20</ENT>
                        <ENT>10</ENT>
                        <ENT>10</ENT>
                        <ENT>5,415</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="03">24-in perm install</ENT>
                        <ENT>10</ENT>
                        <ENT>10</ENT>
                        <ENT>20</ENT>
                        <ENT>10</ENT>
                        <ENT>10</ENT>
                        <ENT>5,415</ENT>
                    </ROW>
                    <ROW EXPSTB="06" RUL="s">
                        <ENT I="21">
                            <E T="02">DTH Pile Installation</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="22">Phase I:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">16-in perm install</ENT>
                        <ENT>60</ENT>
                        <ENT>10</ENT>
                        <ENT>75</ENT>
                        <ENT>35</ENT>
                        <ENT>10</ENT>
                        <ENT>8,500</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="1900"/>
                        <ENT I="03">24-in perm install</ENT>
                        <ENT>570</ENT>
                        <ENT>30</ENT>
                        <ENT>300</ENT>
                        <ENT>125</ENT>
                        <ENT>30</ENT>
                        <ENT>8,500</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Phase II:</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="03">24-in perm install</ENT>
                        <ENT>570</ENT>
                        <ENT>30</ENT>
                        <ENT>300</ENT>
                        <ENT>125</ENT>
                        <ENT>30</ENT>
                        <ENT>8,500</ENT>
                    </ROW>
                    <ROW EXPSTB="06" RUL="s">
                        <ENT I="21">
                            <E T="02">Impact Pile Installation</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="22">Phase I:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">16-in temp install</ENT>
                        <ENT>235</ENT>
                        <ENT>10</ENT>
                        <ENT>275</ENT>
                        <ENT>125</ENT>
                        <ENT>10</ENT>
                        <ENT>465</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">16-in perm install</ENT>
                        <ENT>235</ENT>
                        <ENT>10</ENT>
                        <ENT>275</ENT>
                        <ENT>125</ENT>
                        <ENT>10</ENT>
                        <ENT>465</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">24-in perm install</ENT>
                        <ENT>315</ENT>
                        <ENT>20</ENT>
                        <ENT>300</ENT>
                        <ENT>125</ENT>
                        <ENT>20</ENT>
                        <ENT>1,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Phase II:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">16-in temp install</ENT>
                        <ENT>235</ENT>
                        <ENT>10</ENT>
                        <ENT>275</ENT>
                        <ENT>125</ENT>
                        <ENT>10</ENT>
                        <ENT>465</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">24-in perm install</ENT>
                        <ENT>315</ENT>
                        <ENT>20</ENT>
                        <ENT>300</ENT>
                        <ENT>125</ENT>
                        <ENT>20</ENT>
                        <ENT>1,000</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>1</SU>
                         Maximum shutdown for phocids is reduced to 125 m as they are a common species within the breakwaters of Sitka Sound.
                    </TNOTE>
                    <TNOTE>
                        <SU>2</SU>
                         Maximum shutdown for high frequency species is reduced to 300 m, given the difficulty observing harbor porpoise at greater distances.
                    </TNOTE>
                </GPOTABLE>
                <HD SOURCE="HD2">Protected Species Observers</HD>
                <P>
                    The placement of PSOs during all construction activities (described in the Proposed Monitoring and Reporting section) would ensure that the entire shutdown zone is visible. Should environmental conditions deteriorate such that the entire shutdown zone would not be visible (
                    <E T="03">e.g.,</E>
                     fog, heavy rain), pile driving would be delayed until the PSO is confident marine mammals within the shutdown zone could be detected.
                </P>
                <P>PSOs would monitor the full shutdown zones and the remaining Level A harassment and the Level B harassment zones to the extent practicable. Monitoring zones provide utility for observing by establishing monitoring protocols for areas adjacent to the shutdown zones. Monitoring zones enable observers to be aware of and communicate the presence of marine mammals in the project areas outside the shutdown zones and thus prepare for a potential cessation of activity should the animal enter the shutdown zone.</P>
                <HD SOURCE="HD2">Pre-Activity Monitoring</HD>
                <P>
                    Prior to the start of daily in-water construction activity, or whenever a break in pile driving or DTH drilling of 30 minutes or longer occurs, PSOs would observe the shutdown and monitoring zones for a period of 30 minutes. The shutdown zone would be considered cleared when a marine mammal has not been observed within the zone for that 30-minute period. If a marine mammal is observed within the shutdown zones listed in table 10, pile driving activity would be delayed or halted. If work ceases for more than 30 minutes, the pre-activity monitoring of the shutdown zones would commence. A determination that the shutdown zone is clear must be made during a period of good visibility (
                    <E T="03">i.e.,</E>
                     the entire shutdown zone and surrounding waters must be visible to the naked eye).
                </P>
                <HD SOURCE="HD2">Soft-Start Procedures</HD>
                <P>Soft-start procedures provide additional protection to marine mammals by providing warning and/or giving marine mammals a chance to leave the area prior to the hammer operating at full capacity. For impact pile driving, contractors would be required to provide an initial set of three strikes from the hammer at reduced energy, followed by a 30-second waiting period, then two subsequent reduced-energy strike sets. Soft-start would be implemented at the start of each day's impact pile driving and at any time following cessation of impact pile driving for a period of 30 minutes or longer.</P>
                <P>Based on our evaluation of the applicant's proposed measures NMFS has preliminarily determined that the proposed mitigation measures provide the means of effecting the least practicable impact on the affected species or stocks and their habitat, paying particular attention to rookeries, mating grounds, and areas of similar significance.</P>
                <HD SOURCE="HD1">Proposed Monitoring and Reporting</HD>
                <P>In order to issue an IHA for an activity, section 101(a)(5)(D) of the MMPA states that NMFS must set forth requirements pertaining to the monitoring and reporting of such taking. The MMPA implementing regulations at 50 CFR 216.104(a)(13) indicate that requests for authorizations must include the suggested means of accomplishing the necessary monitoring and reporting that will result in increased knowledge of the species and of the level of taking or impacts on populations of marine mammals that are expected to be present while conducting the activities. Effective reporting is critical both to compliance as well as ensuring that the most value is obtained from the required monitoring.</P>
                <P>Monitoring and reporting requirements prescribed by NMFS should contribute to improved understanding of one or more of the following:</P>
                <P>
                    • Occurrence of marine mammal species or stocks in the area in which take is anticipated (
                    <E T="03">e.g.,</E>
                     presence, abundance, distribution, density);
                </P>
                <P>
                    • Nature, scope, or context of likely marine mammal exposure to potential stressors/impacts (individual or cumulative, acute or chronic), through better understanding of: (1) action or environment (
                    <E T="03">e.g.,</E>
                     source characterization, propagation, ambient noise); (2) affected species (
                    <E T="03">e.g.,</E>
                     life history, dive patterns); (3) co-occurrence of marine mammal species with the activity; or (4) biological or behavioral context of exposure (
                    <E T="03">e.g.,</E>
                     age, calving or feeding areas);
                </P>
                <P>• Individual marine mammal responses (behavioral or physiological) to acoustic stressors (acute, chronic, or cumulative), other stressors, or cumulative impacts from multiple stressors;</P>
                <P>• How anticipated responses to stressors impact either: (1) long-term fitness and survival of individual marine mammals; or (2) populations, species, or stocks;</P>
                <P>
                    • Effects on marine mammal habitat (
                    <E T="03">e.g.,</E>
                     marine mammal prey species, acoustic habitat, or other important physical components of marine mammal habitat); and,
                </P>
                <P>• Mitigation and monitoring effectiveness.</P>
                <HD SOURCE="HD2">Visual Monitoring</HD>
                <P>
                    Marine mammal monitoring must be conducted in accordance with the conditions in this section and the IHA. 
                    <PRTPAGE P="1901"/>
                    Marine mammal monitoring during pile driving activities would be conducted by PSOs meeting NMFS' following requirements:
                </P>
                <P>• PSOs must be independent of the activity contractor (for example, employed by a subcontractor) and have no other assigned tasks during monitoring periods;</P>
                <P>• At least one PSO would have prior experience performing the duties of a PSO during construction activity pursuant to a NMFS-issued incidental take authorization;</P>
                <P>• Other PSOs may substitute education (degree in biological science or related field) or training for experience; and</P>
                <P>• Where a team of three or more PSOs is required, a lead observer or monitoring coordinator would be designated. The lead observer would be required to have prior experience working as a marine mammal observer during construction.</P>
                <P>PSOs should have the following additional qualifications:</P>
                <P>○ Ability to conduct field observations and collect data according to assigned protocols;</P>
                <P>○ Experience or training in the field identification of marine mammals, including the identification of behaviors;</P>
                <P>○ Sufficient training, orientation, or experience with the construction operation to provide for personal safety during observations;</P>
                <P>○ Writing skills sufficient to prepare a report of observations including but not limited to the number and species of marine mammals observed; dates and times when in-water construction activities were conducted; dates, times and reason for implementation of mitigation (or why mitigation was not implemented when required); and marine mammal behavior; and</P>
                <P>○ Ability to communicate orally, by radio or in person, with project personnel to provide real-time information on marine mammals observed in the area as necessary.</P>
                <P>• CBS must employ up to five PSOs depending on the size of the monitoring and shutdown zones. A minimum of two PSOs (including the lead PSO) must be assigned to the active pile driving location to monitor the shutdown zones and as much of the Level B harassment zones as possible.</P>
                <P>• CBS must establish monitoring locations with the best views of monitoring zones as described in the IHA and Monitoring Plan posted on our website.</P>
                <P>• Up to four monitors will be used at a time depending on the size of the monitoring area. PSOs would be deployed in strategic locations around the area of potential effects at all times during in-water pile driving and removal. PSOs will be positioned at locations that provide full views of the monitoring zones and the Level A harassment Shutdown Zones. All PSOs would have access to high-quality binoculars, range finders to monitor distances, and a compass to record bearing to animals as well as radios or cell phones for maintaining contact with work crews.</P>
                <P>• Up to four PSOs will be stationed at the following locations: the project site, Sandy Beach Day use site, O'Connell lightering float, and Whale Park.</P>
                <P>Monitoring would be conducted 30 minutes before, during, and 30 minutes after all in water construction activities. In addition, PSOs would record all incidents of marine mammal occurrence, regardless of distance from activity, and would document any behavioral reactions in concert with distance from piles being driven or removed. Pile driving activities include the time to install or remove a single pile or series of piles, as long as the time elapsed between uses of the pile driving equipment is no more than 30 minutes.</P>
                <P>CBS shall conduct briefings between construction supervisors and crews, PSOs, CBS staff prior to the start of all pile driving activities and when new personnel join the work. These briefings would explain responsibilities, communication procedures, marine mammal monitoring protocol, and operational procedures.</P>
                <HD SOURCE="HD2">Reporting</HD>
                <P>A draft marine mammal monitoring report will be submitted to NMFS within 90 days after the completion of pile driving and removal activities for each IHA, or 60 days prior to a requested date of issuance from any future IHAs for projects at the same location, whichever comes first. The report will include an overall description of work completed, a narrative regarding marine mammal sightings, and associated PSO data sheets. Specifically, the report must include:</P>
                <P>• Dates and times (begin and end) of all marine mammal monitoring;</P>
                <P>
                    • Construction activities occurring during each daily observation period, including the number and type of piles driven or removed and by what method (
                    <E T="03">i.e.,</E>
                     impact, vibratory, or DTH drilling) and the total equipment duration for vibratory removal for each pile or total number of strikes for each pile (impact driving);
                </P>
                <P>• PSO locations during marine mammal monitoring;</P>
                <P>• Environmental conditions during monitoring periods (at beginning and end of PSO shift and whenever conditions change significantly), including Beaufort sea state and any other relevant weather conditions including cloud cover, fog, sun glare, and overall visibility to the horizon, and estimated observable distance;</P>
                <P>• Upon observation of a marine mammal, the following information:</P>
                <P>• Name of PSO who sighted the animal(s) and PSO location and activity at the time of sighting;</P>
                <P>• Time of sighting;</P>
                <P>
                    • Identification of the animal(s) (
                    <E T="03">e.g.,</E>
                     genus/species, lowest possible taxonomic level, or unidentifiable), PSO confidence in identification, and the composition of the group if there is a mix of species;
                </P>
                <P>• Distance and bearing of each marine mammal observed relative to the pile being driven for each sighting (if pile driving was occurring at time of sighting);</P>
                <P>• Estimated number of animals (min/max/best estimate);</P>
                <P>
                    • Estimated number of animals by cohort (adults, juveniles, neonates, group composition, sex class, 
                    <E T="03">etc.</E>
                    );
                </P>
                <P>• Animal's closest point of approach and estimated time spent within the harassment zone;</P>
                <P>
                    • Description of any marine mammal behavioral observations (
                    <E T="03">e.g.,</E>
                     observed behaviors such as feeding or traveling), including an assessment of behavioral responses thought to have resulted from the activity (
                    <E T="03">e.g.,</E>
                     no response or changes in behavioral state such as ceasing feeding, changing direction, flushing, or breaching);
                </P>
                <P>• Number of marine mammals detected within the harassment zones and shutdown zones; by species; and</P>
                <P>
                    • Detailed information about any implementation of any mitigation triggered (
                    <E T="03">e.g.,</E>
                     shutdowns and delays), a description of specific actions that ensured, and resulting changes in behavior of the animal(s), if any.
                </P>
                <P>If no comments are received from NMFS within 30 days, the draft reports will constitute the final reports. If comments are received, a final report addressing NMFS comments must be submitted within 30 days after receipt of comments.</P>
                <HD SOURCE="HD2">Reporting Injured or Dead Marine Mammals</HD>
                <P>
                    In the event that personnel involved in the construction activities discover an injured or dead marine mammal, the IHA-holder must immediately cease the specified activities and report the 
                    <PRTPAGE P="1902"/>
                    incident to the Office of Protected Resources (OPR) (
                    <E T="03">PR.ITP.MonitoringReports@noaa.gov</E>
                    ), NMFS and to the Alaska Regional Stranding Coordinator as soon as feasible. If the death or injury was clearly caused by the specified activity, CBS must immediately cease the specified activities until NMFS is able to review the circumstances of the incident and determine what, if any, additional measures are appropriate to ensure compliance with the terms of the IHA. The IHA-holder must not resume their activities until notified by NMFS. The report must include the following information:
                </P>
                <P>• Time, date, and location (latitude/longitude) of the first discovery (and updated location information if known and applicable);</P>
                <P>• Species identification (if known) or description of the animal(s) involved;</P>
                <P>• Condition of the animal(s) (including carcass condition if the animal is dead);</P>
                <P>• Observed behaviors of the animal(s), if alive;</P>
                <P>• If available, photographs or video footage of the animal(s); and</P>
                <P>• General circumstances under which the animal was discovered.</P>
                <HD SOURCE="HD1">Negligible Impact Analysis and Determination</HD>
                <P>
                    NMFS has defined negligible impact as an impact resulting from the specified activity that cannot be reasonably expected to, and is not reasonably likely to, adversely affect the species or stock through effects on annual rates of recruitment or survival (50 CFR 216.103). A negligible impact finding is based on the lack of likely adverse effects on annual rates of recruitment or survival (
                    <E T="03">i.e.,</E>
                     population-level effects). An estimate of the number of takes alone is not enough information on which to base an impact determination. In addition to considering estimates of the number of marine mammals that might be “taken” through harassment, NMFS considers other factors, such as the likely nature of any impacts or responses (
                    <E T="03">e.g.,</E>
                     intensity, duration), the context of any impacts or responses (
                    <E T="03">e.g.,</E>
                     critical reproductive time or location, foraging impacts affecting energetics), as well as effects on habitat, and the likely effectiveness of the mitigation. We also assess the number, intensity, and context of estimated takes by evaluating this information relative to population status. Consistent with the 1989 preamble for NMFS' implementing regulations (54 FR 40338, September 29, 1989), the impacts from other past and ongoing anthropogenic activities are incorporated into this analysis via their impacts on the baseline (
                    <E T="03">e.g.,</E>
                     as reflected in the regulatory status of the species, population size and growth rate where known, ongoing sources of human-caused mortality, or ambient noise levels).
                </P>
                <P>To avoid repetition, the discussion of our analysis applies to all species listed in table 3, given that the anticipated effects of this activity on these different marine mammal stocks are expected to be similar. There is little information about the nature or severity of the impacts, or the size, status, or structure of any of these species or stocks that would lead to a different analysis for this activity. In addition, because both the number and nature of the estimated takes anticipated to occur are identical in Phase I and II, the analysis below applies to both of the IHAs.</P>
                <P>Pile driving and DTH drilling activities associated with the project, as outlined previously, have the potential to disturb or displace marine mammals. Specifically, the specified activities may result in take, in the form of Level B harassment and, for some species, Level A harassment from underwater sounds generated by pile driving and DTH drilling. Potential takes could occur if individuals are present in the ensonified zone when these activities are underway.</P>
                <P>No serious injury or mortality would be expected, even in the absence of required mitigation measures, given the nature of the activities. Further, no take by Level A harassment is anticipated for killer whales, humpback whales, gray whales, or minke whales due to the application of planned mitigation measures, such as shutdown zones that encompass the Level A harassment zones for the species, the rarity of the species near the action area, and the small Level A harassment zones (for killer whales only). The potential for harassment would be minimized through the construction method and the implementation of the planned mitigation measures (see Proposed Mitigation section).</P>
                <P>
                    Take by Level A harassment is proposed for three species (harbor porpoise, Steller sea lion, and harbor seal) as the Level A harassment isopleths exceed the size of the shutdown zones for specific construction scenarios, the Level A harassment zones are large, and/or the species is frequent near the action area. Therefore, there is the possibility that an animal could enter a Level A harassment zone and remain within that zone for a duration long enough to incur PTS. Level A harassment of these species is therefore proposed for authorization. Any take by Level A harassment is expected to arise from, at most, a small degree of PTS (
                    <E T="03">i.e.,</E>
                     minor degradation of hearing capabilities within regions of hearing that align most completely with the energy produced by impact pile driving such as the low-frequency region below 2 kHz), not severe hearing impairment or impairment within the ranges of greatest hearing sensitivity. Animals would need to be exposed to higher levels and/or longer duration than are expected to occur here in order to incur any more than a small degree of PTS.
                </P>
                <P>Further, the amount of take proposed for authorization by Level A harassment is very low for the marine mammal stocks and species. If hearing impairment occurs, it is most likely that the affected animal would lose only a few decibels in its hearing sensitivity. Due to the small degree anticipated, any PTS potential incurred would not be expected to affect the reproductive success or survival of any individuals, much less result in adverse impacts on the species or stock.</P>
                <P>
                    The Level A harassment zones identified in table 7 are based upon an animal exposed to pile driving or DTH drilling of several piles per day (six piles per day for vibratory removal and installation, four piles per day of impact driving, and two piles per day of DTH drilling). Given the short duration to impact drive or vibratory install or remove, or use DTH drilling, each pile and break between pile installations (to reset equipment and move piles into place), an animal would have to remain within the area estimated to be ensonified above the Level A harassment threshold for multiple hours. This is highly unlikely given marine mammal movement patterns in the area. If an animal was exposed to accumulated sound energy, the resulting PTS would likely be small (
                    <E T="03">e.g.,</E>
                     PTS onset) at lower frequencies where pile driving energy is concentrated, and unlikely to result in impacts to individual fitness, reproduction, or survival.
                </P>
                <P>
                    Additionally, some subset of the individuals that are behaviorally harassed could also simultaneously incur some small degree of TTS for a short duration of time. However, since the hearing sensitivity of individuals that incur TTS is expected to recover completely within minutes to hours, it is unlikely that the brief hearing impairment would affect the individual's long-term ability to forage and communicate with conspecifics, and would therefore not likely impact reproduction or survival of any individual marine mammal, let alone 
                    <PRTPAGE P="1903"/>
                    adversely affect rates of recruitment or survival of the species or stock.
                </P>
                <P>The nature of the pile driving project precludes the likelihood of serious injury or mortality. For all species and stocks, take would occur within a limited, confined area (adjacent to the project site) of the stock's range. The intensity and duration of take by Level A and Level B harassment would be minimized through use of mitigation measures described herein. Further, the amount of take proposed to be authorized is extremely small when compared to stock abundance.</P>
                <P>Behavioral responses of marine mammals to pile driving, pile removals, and DTH drilling in Sitka Channel and the surrounding Sitka Sound are expected to be mild, short term, and temporary. Marine mammals within the Level B harassment zones may not show any visual cues they are disturbed by activities or they could become alert, avoid the area, leave the area, or display other mild responses that are not observable such as changes in vocalization patterns. Given that pile driving, pile removal, and DTH drilling are temporary activities and effects would cease when equipment is not operating, any harassment occurring would be temporary. Additionally, many of the species present in the region would only be present temporarily based on seasonal patterns or during transit between other habitats. These species would be exposed to even smaller periods of noise-generating activity, further decreasing the impacts.</P>
                <P>
                    Nearly all inland waters of southeast Alaska, including Sitka Sound, are included in the southeast Alaska humpback whale feeding BIA (Wild 
                    <E T="03">et al.,</E>
                     2023), though humpback whale distribution in southeast Alaska varies by season and waterway (Dahlheim 
                    <E T="03">et al.,</E>
                     2009). Humpback whales could be present within Sitka Sound year round, however the action area is within the breakwaters where humpback whales are not commonly found and therefore, the BIA is not expected to be affected. Therefore, the proposed project is not expected to have significant adverse effects on the foraging of humpback whales.
                </P>
                <P>
                    Sitka Sound is also within a gray whale migratory corridor BIA (Wild 
                    <E T="03">et al.,</E>
                     2023). Construction is expected to occur while the BIA is active during the southbound migration (November to January) and northbound migration (March-May). The Sound is also a Gray whale feeding BIA. Construction is expected to overlap with the feeding BIA (March-June). However, as noted for humpback whales, project activities will only overlap seasonally in the gray whale migratory and feeding BIAs, and the overall 2 year project (Phase I and Phase II) is expected to occur over just 40 in-water workdays, further reducing the temporal overlap with the BIAs. Additionally, the area of the feeding BIA in which impacts of the planned project may occur is small relative to both the overall area of the BIA and the overall area of suitable gray whale habitat outside of this BIA. The area of Sitka Sound affected by this project is also small relative to the rest of the Sound, such that it allows animals within the migratory corridor to still utilize Sitka Sound without necessarily being disturbed by the construction. Specifically, all Level A harassment isopleths for gray whale are within the breakwaters where gray whales are not expected. Therefore, take of gray whales using the feeding and migratory BIAs is not expected to impact feeding or migratory behavior and, therefore, would not impact reproduction or survivorship.
                </P>
                <P>As noted previously, since January 1, 2019, elevated gray whale strandings have occurred along the west coast of North America from Mexico through Alaska. The event has been declared an UME, though a cause has not yet been determined. While 6 takes by Level B harassment in phase I and 4 takes by Level B harassment in phase II of gray whale are proposed to be authorized for each year this is an extremely small portion of the stock (&lt;1 percent), and CBS will be required to implement a shutdown zone that includes the entire Level A harassment zone for low-frequency cetaceans such as gray whales.</P>
                <P>
                    The same regions are also a part of the Western DPS Steller sea lion ESA critical habitat. While Steller sea lions are common in the project area, there are no essential physical and biological habitat features, such as haulouts or rookeries, within the proposed project area. The nearest haulout is approximately 25 km away from the proposed project area. Therefore, the proposed project is not expected to have significant adverse effects on the critical habitat of Western DPS Steller sea lions. No areas of specific biological importance (
                    <E T="03">e.g.,</E>
                     ESA critical habitat, other BIAs, or other areas) for any other species are known to co-occur with the project area.
                </P>
                <P>In addition, it is unlikely that minor noise effects in a small, localized area of habitat would have any effect on each stock's ability to recover. In combination, we believe that these factors, as well as the available body of evidence from other similar activities, demonstrate that the potential effects of the specified activities would have only minor, short-term effects on individuals. The specified activities are not expected to impact rates of recruitment or survival and would therefore not result in population-level impacts.</P>
                <P>In summary and as described above, the following factors primarily support our preliminary determination that the impacts resulting from this activity are not expected to adversely affect any of the species or stocks through effects on annual rates of recruitment or survival:</P>
                <P>• No serious injury or mortality is anticipated or authorized;</P>
                <P>• Level A harassment would be very small amounts and of low degree;</P>
                <P>• Level A harassment takes of only harbor porpoise, Steller sea lions and harbor seals;</P>
                <P>• For all species, the Sitka Sound and channel are a very small and peripheral part of their range;</P>
                <P>• Anticipated takes by Level B harassment are relatively low for all stocks. Level B harassment would be primarily in the form of behavioral disturbance, resulting in avoidance of the project areas around where impact or vibratory pile driving is occurring, with some low-level TTS that may limit the detection of acoustic cues for relatively brief amounts of time in relatively confined footprints of the activities;</P>
                <P>• Effects on species that serve as prey for marine mammals from the activities are expected to be short-term and, therefore, any associated impacts on marine mammal feeding are not expected to result in significant or long-term consequences for individuals, or to accrue to adverse impacts on their populations;</P>
                <P>• The ensonified areas are very small relative to the overall habitat ranges of all species and stocks, and would not adversely affect ESA-designated critical habitat for any species or any areas of known biological importance;</P>
                <P>• The lack of anticipated significant or long-term negative effects to marine mammal habitat; and</P>
                <P>• CBS would implement mitigation measures including soft-starts and shutdown zones to minimize the numbers of marine mammals exposed to injurious levels of sound, and to ensure that take by Level A harassment is, at most, a small degree of PTS.</P>
                <P>
                    Based on the analysis contained herein of the likely effects of the specified activity on marine mammals and their habitat, and taking into consideration the implementation of the proposed monitoring and mitigation measures, NMFS preliminarily finds that the total marine mammal take, specific to each of the 2 consecutive 
                    <PRTPAGE P="1904"/>
                    years of proposed activity, would have a negligible impact on all affected marine mammal species or stocks.
                </P>
                <HD SOURCE="HD1">Small Numbers</HD>
                <P>As noted previously, only take of small numbers of marine mammals may be authorized under sections 101(a)(5)(A) and (D) of the MMPA for specified activities other than military readiness activities. The MMPA does not define small numbers and so, in practice, where estimated numbers are available, NMFS compares the number of individuals taken to the most appropriate estimation of abundance of the relevant species or stock in our determination of whether an authorization is limited to small numbers of marine mammals. When the predicted number of individuals to be taken is fewer than one-third of the species or stock abundance, the take is considered to be of small numbers. Additionally, other qualitative factors may be considered in the analysis, such as the temporal or spatial scale of the activities.</P>
                <P>The amount of take NMFS proposes to authorize, for each of the 2 consecutive years of proposed activity, is below one third of the estimated stock abundance for all species (in fact, take of individuals is less than 2 percent of the abundance of the affected stocks, see table 9). This is likely a conservative estimate because we assume all takes are of different individual animals, which is likely not the case. Some individuals may return multiple times in a day, but PSOs would count them as separate takes if they cannot be individually identified.</P>
                <P>
                    There is no current or historical estimate of the Alaska minke whale stock, but there are known to be over 1,000 minke whales in the Gulf of Alaska (Muto 
                    <E T="03">et al.</E>
                     2018), so the 10 takes by Level B harassment proposed over the 2 years of the project duration is small relative to estimated survey abundance, even if each take occurred to a new individual. Additionally, the range of the Alaska stock of minke whales is extensive, stretching from the Canadian Pacific coast to the Chukchi Sea, and CBS's project would only impact a small portion of this range.
                </P>
                <P>Based on the analysis contained herein of the proposed activity (including the proposed mitigation and monitoring measures) and the anticipated take of marine mammals, NMFS preliminarily finds that, specific to each of the two consecutive years of proposed activity, small numbers of marine mammals would be taken relative to the population size of the affected species or stocks.</P>
                <HD SOURCE="HD1">Unmitigable Adverse Impact Analysis and Determination</HD>
                <P>In order to issue an IHA, NMFS must find that the specified activity will not have an “unmitigable adverse impact” on the subsistence uses of the affected marine mammal species or stocks by Alaskan Natives. NMFS has defined “unmitigable adverse impact” in 50 CFR 216.103 as an impact resulting from the specified activity: (1) That is likely to reduce the availability of the species to a level insufficient for a harvest to meet subsistence needs by: (i) Causing the marine mammals to abandon or avoid hunting areas; (ii) Directly displacing subsistence users; or (iii) Placing physical barriers between the marine mammals and the subsistence hunters; and (2) That cannot be sufficiently mitigated by other measures to increase the availability of marine mammals to allow subsistence needs to be met.</P>
                <P>
                    Sitka Channel and other nearby areas are within the traditional territory of the Sheet'ká 
                    <E T="8405">B</E>
                    wáan. Alaska natives have traditionally harvested marine mammals in Sitka, however today a majority of the subsistence harvest is of species other than marine mammals. Alaska Department Fish and Game reported that in 2013, around 11 percent of Sitka households used subsistence-caught marine mammals (ADF&amp;G, 2023), however this is the most recent data available and there has not been a survey since.
                </P>
                <P>The proposed project is not likely to adversely impact the availability of any marine mammal species or stocks that are commonly used for subsistence purposes or impact subsistence harvest of marine mammals in the region because:</P>
                <P>• There is no recent recorded subsistence harvest of marine mammals in the area;</P>
                <P>• Construction activities are temporary and localized primarily within Sitka Channel;</P>
                <P>• Construction will not take place during the herring spawning season when subsistence species are more active;</P>
                <P>• Mitigation measures will be implemented to minimize disturbance of marine mammals in the action area; and,</P>
                <P>• The project will not result in significant changes to availability of subsistence resources.</P>
                <P>Based on the description of the specified activity, the measures described to minimize adverse effects on the availability of marine mammals for subsistence purposes, and the proposed mitigation and monitoring measures; NMFS has preliminarily determined that, specific to each of the two consecutive years of proposed activity, there will not be an unmitigable adverse impact on subsistence uses from CBS's proposed activities.</P>
                <HD SOURCE="HD1">Endangered Species Act</HD>
                <P>
                    Section 7(a)(2) of the Endangered Species Act of 1973 (ESA; 16 U.S.C. 1531 
                    <E T="03">et seq.</E>
                    ) requires that each Federal agency insure that any action it authorizes, funds, or carries out is not likely to jeopardize the continued existence of any endangered or threatened species or result in the destruction or adverse modification of designated critical habitat. To ensure ESA compliance for the issuance of IHAs, NMFS Office of Protected Resources (OPR) consults internally whenever we propose to authorize take for endangered or threatened species, in this case with the NMFS Alaska Regional Office (AKR).
                </P>
                <P>NMFS OPR has requested initiation of section 7 consultation with the NMFS AKR for the issuance of this IHA. NMFS will conclude the ESA consultation prior to reaching a determination regarding the proposed issuance of the authorization.</P>
                <HD SOURCE="HD1">Proposed Authorization</HD>
                <P>
                    As a result of these preliminary determinations, NMFS proposes to issue two sequential IHAs, each lasting 1 year, to CBS for conducting Seaplane Base construction in Sitka, Alaska, starting in July 2024 for Phase I and July 2025 for Phase II, provided the previously mentioned mitigation, monitoring, and reporting requirements are incorporated. Drafts of the proposed IHAs can be found at: 
                    <E T="03">https://www.fisheries.noaa.gov/national/marine-mammal-protection/incidental-take-authorizations-construction-activities.</E>
                </P>
                <HD SOURCE="HD1">Request for Public Comments</HD>
                <P>We request comment on our analyses, the proposed authorization, and any other aspect of this notice of proposed IHAs for the proposed construction project. We also request comment on the potential renewal of these proposed IHAs as described in the paragraph below. Please include with your comments any supporting data or literature citations to help inform decisions on the request for these IHAs or subsequent renewal IHAs.</P>
                <P>
                    On a case-by-case basis, NMFS may issue a one-time, 1-year renewal IHA following notice to the public providing an additional 15 days for public comments when (1) up to another year of identical or nearly identical activities 
                    <PRTPAGE P="1905"/>
                    as described in the Description of Proposed Activity section of this notice is planned or (2) the activities as described in the Description of Proposed Activity section of this notice would not be completed by the time the IHA expires and a renewal would allow for completion of the activities beyond that described in the 
                    <E T="03">Dates and Duration</E>
                     section of this notice, provided all of the following conditions are met:
                </P>
                <P>• A request for renewal is received no later than 60 days prior to the needed renewal IHA effective date (recognizing that the renewal IHA expiration date cannot extend beyond one year from expiration of the initial IHA).</P>
                <P>• The request for renewal must include the following:</P>
                <P>
                    (1) An explanation that the activities to be conducted under the requested renewal IHA are identical to the activities analyzed under the initial IHA, are a subset of the activities, or include changes so minor (
                    <E T="03">e.g.,</E>
                     reduction in pile size) that the changes do not affect the previous analyses, mitigation and monitoring requirements, or take estimates (with the exception of reducing the type or amount of take).
                </P>
                <P>(2) A preliminary monitoring report showing the results of the required monitoring to date and an explanation showing that the monitoring results do not indicate impacts of a scale or nature not previously analyzed or authorized.</P>
                <P>Upon review of the request for renewal, the status of the affected species or stocks, and any other pertinent information, NMFS determines that there are no more than minor changes in the activities, the mitigation and monitoring measures will remain the same and appropriate, and the findings in the initial IHA remain valid.</P>
                <SIG>
                    <DATED>Dated: January 5, 2024.</DATED>
                    <NAME>Kimberly Damon-Randall,</NAME>
                    <TITLE>Director, Office of Protected Resources, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00390 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <DEPDOC>[RTID 0648-XD640]</DEPDOC>
                <SUBJECT>Taking and Importing Marine Mammals; Taking Marine Mammals Incidental to Geophysical Surveys Related to Oil and Gas Activities in the Gulf of Mexico</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of issuance of Letter of Authorization.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Marine Mammal Protection Act (MMPA), as amended, its implementing regulations, and NMFS' MMPA Regulations for Taking Marine Mammals Incidental to Geophysical Surveys Related to Oil and Gas Activities in the Gulf of Mexico, notification is hereby given that a Letter of Authorization (LOA) has been issued to Chevron U.S.A. Inc. (Chevron) for the take of marine mammals incidental to geophysical survey activity in the Gulf of Mexico.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The LOA is effective from January 5, 2024 through February 19, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The LOA, LOA request, and supporting documentation are available online at: 
                        <E T="03">https://www.fisheries.noaa.gov/action/incidental-take-authorization-oil-and-gas-industry-geophysical-survey-activity-gulf-mexico</E>
                        . In case of problems accessing these documents, please call the contact listed below (see 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                        ).
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Jenna Harlacher, Office of Protected Resources, NMFS, (301) 427-8401.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    Sections 101(a)(5)(A) and (D) of the MMPA (16 U.S.C. 1361 
                    <E T="03">et seq.</E>
                    ) direct the Secretary of Commerce to allow, upon request, the incidental, but not intentional, taking of small numbers of marine mammals by U.S. citizens who engage in a specified activity (other than commercial fishing) within a specified geographical region if certain findings are made and either regulations are issued or, if the taking is limited to harassment, a notice of a proposed authorization is provided to the public for review.
                </P>
                <P>An authorization for incidental takings shall be granted if NMFS finds that the taking will have a negligible impact on the species or stock(s), will not have an unmitigable adverse impact on the availability of the species or stock(s) for subsistence uses (where relevant), and if the permissible methods of taking and requirements pertaining to the mitigation, monitoring and reporting of such takings are set forth. NMFS has defined “negligible impact” in 50 CFR 216.103 as an impact resulting from the specified activity that cannot be reasonably expected to, and is not reasonably likely to, adversely affect the species or stock through effects on annual rates of recruitment or survival.</P>
                <P>Except with respect to certain activities not pertinent here, the MMPA defines “harassment” as: any act of pursuit, torment, or annoyance which (i) has the potential to injure a marine mammal or marine mammal stock in the wild (Level A harassment); or (ii) has the potential to disturb a marine mammal or marine mammal stock in the wild by causing disruption of behavioral patterns, including, but not limited to, migration, breathing, nursing, breeding, feeding, or sheltering (Level B harassment).</P>
                <P>On January 19, 2021, we issued a final rule with regulations to govern the unintentional taking of marine mammals incidental to geophysical survey activities conducted by oil and gas industry operators, and those persons authorized to conduct activities on their behalf (collectively “industry operators”), in U.S. waters of the Gulf of Mexico (GOM) over the course of 5 years (86 FR 5322, January 19, 2021). The rule was based on our findings that the total taking from the specified activities over the 5-year period will have a negligible impact on the affected species or stock(s) of marine mammals and will not have an unmitigable adverse impact on the availability of those species or stocks for subsistence uses. The rule became effective on April 19, 2021.</P>
                <P>
                    Our regulations at 50 CFR 217.180 
                    <E T="03">et seq.</E>
                     allow for the issuance of LOAs to industry operators for the incidental take of marine mammals during geophysical survey activities and prescribe the permissible methods of taking and other means of effecting the least practicable adverse impact on marine mammal species or stocks and their habitat (often referred to as mitigation), as well as requirements pertaining to the monitoring and reporting of such taking. Under 50 CFR 217.186(e), issuance of an LOA shall be based on a determination that the level of taking will be consistent with the findings made for the total taking allowable under these regulations and a determination that the amount of take authorized under the LOA is of no more than small numbers.
                </P>
                <HD SOURCE="HD1">Summary of Request and Analysis</HD>
                <P>
                    This LOA covers work that was not completed under Chevron's 2023 LOA that expired on January 2, 2024 (88 FR 40209, June 21, 2023). Chevron requested an additional LOA covering 26 days of work. There are no other changes from the previously analyzed and issued LOA (88 FR 40209, June 21, 2023) other than a reduction in the 
                    <PRTPAGE P="1906"/>
                    amount of surveys, reflecting the remaining portion of the original survey plan.
                </P>
                <P>
                    Chevron plans to conduct a three-dimensional (3D) ocean bottom node (OBN) survey over Walker Ridge Lease Blocks 758, 759, and 802, and the surrounding lease blocks, with approximate water depths ranging from approximately 2,000 to 2,400 meters (m). Chevron anticipates using a single dual source vessel, towing airgun array sources consisting of 42 elements, with a total volume of 5,380 cubic inches (in
                    <SU>3</SU>
                    ). Please see Chevron's previous LOA application for additional detail.
                </P>
                <P>
                    Consistent with the preamble to the final rule, the survey effort proposed by Chevron in its LOA request was used to develop LOA-specific take estimates based on the acoustic exposure modeling results described in the preamble (86 FR 5398, January 19, 2021). In order to generate the appropriate take number for authorization, the following information was considered: (1) survey type; (2) location (by modeling zone 
                    <SU>1</SU>
                    <FTREF/>
                    ); (3) number of days; and (4) season.
                    <SU>2</SU>
                    <FTREF/>
                     The acoustic exposure modeling performed in support of the rule provides 24-hour exposure estimates for each species, specific to each modeled survey type in each zone and season.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         For purposes of acoustic exposure modeling, the GOM was divided into seven zones. Zone 1 is not included in the geographic scope of the rule.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         For purposes of acoustic exposure modeling, seasons include Winter (December-March) and Summer (April-November).
                    </P>
                </FTNT>
                <P>
                    No 3D OBN surveys were included in the modeled survey types, and use of existing proxies (
                    <E T="03">i.e.,</E>
                     2D, 3D NAZ, 3D WAZ, Coil) is generally conservative for use in evaluation of 3D OBN survey effort, largely due to the greater area covered by the modeled proxies. Summary descriptions of these modeled survey geometries are available in the preamble to the proposed rule (83 FR 29212, 29220, June 22, 2018). Coil was selected as the best available proxy survey type in this case because the spatial coverage of the planned survey is most similar to the coil survey pattern. The planned 3D OBN survey will involve a single source vessel sailing along closely spaced survey lines that are approximately 100-150 m apart and approximately 40 kilometers (km) in length. The coil survey pattern was assumed to cover approximately 144 kilometers squared (km
                    <SU>2</SU>
                    ) per day (compared with approximately 795 km
                    <SU>2</SU>
                    , 199 km
                    <SU>2</SU>
                    , and 845 km
                    <SU>2</SU>
                     per day for the 2D, 3D NAZ, and 3D WAZ survey patterns, respectively). Among the different parameters of the modeled survey patterns (
                    <E T="03">e.g.,</E>
                     area covered, line spacing, number of sources, shot interval, total simulated pulses), NMFS considers area covered per day to be most influential on daily modeled exposures exceeding Level B harassment criteria. Although Chevron is not proposing to perform a survey using the coil geometry, its planned 3D OBN survey is expected to cover approximately 10 km
                    <SU>2</SU>
                     per day, meaning that the coil proxy is most representative of the effort planned by Chevron in terms of predicted Level B harassment exposures.
                </P>
                <P>
                    All available acoustic exposure modeling results assume use of a 72-element, 8,000 in
                    <SU>3</SU>
                     array. Thus, take numbers authorized through the LOA are considered conservative due to differences in the airgun array (43 elements, 5,380 in
                    <SU>3</SU>
                    ), as compared to the source modeled for the rule.
                </P>
                <P>The survey will take place over approximately 26 days. The entire survey would occur within Zone 7. Chevron plans to conduct all 26 survey days in the “Winter” season.</P>
                <P>
                    For some species, take estimates based solely on the modeling yielded results that are not realistically likely to occur when considered in light of other relevant information available during the rulemaking process regarding marine mammal occurrence in the GOM. The approach used in the acoustic exposure modeling, in which seven modeling zones were defined over the U.S. GOM, necessarily averages fine-scale information about marine mammal distribution over the large area of each modeling zone. Thus, although the modeling conducted for the rule is a natural starting point for estimating take, the rule acknowledged that other information could be considered (see, 
                    <E T="03">e.g.,</E>
                     86 FR 5442, January 19, 2021), discussing the need to provide flexibility and make efficient use of previous public and agency review of other information and identifying that additional public review is not necessary unless the model or inputs used differ substantively from those that were previously reviewed by NMFS and the public. For this survey, NMFS has other relevant information reviewed during the rulemaking that indicates use of the acoustic exposure modeling to generate a take estimate for one marine mammal species produces results inconsistent with what is known regarding its occurrence in the GOM. Accordingly, we have adjusted the calculated take estimates for the species as described below.
                </P>
                <P>
                    Killer whales are the most rarely encountered species in the GOM, typically in deep waters of the central GOM (Roberts 
                    <E T="03">et al.,</E>
                     2015; Maze-Foley and Mullin, 2006). The approach used in the acoustic exposure modeling, in which seven modeling zones were defined over the U.S. GOM, necessarily averages fine-scale information about marine mammal distribution over the large area of each modeling zone. NMFS has determined that the approach results in unrealistic projections regarding the likelihood of encountering killer whales.
                </P>
                <P>
                    As discussed in the final rule, the density models produced by Roberts 
                    <E T="03">et al.</E>
                     (2016) provide the best available scientific information regarding predicted density patterns of cetaceans in the U.S. GOM. The predictions represent the output of models derived from multi-year observations and associated environmental parameters that incorporate corrections for detection bias. However, in the case of killer whales, the model is informed by few data, as indicated by the coefficient of variation associated with the abundance predicted by the model (0.41, the second-highest of any GOM species model; Roberts 
                    <E T="03">et al.,</E>
                     2016). The model's authors noted the expected non-uniform distribution of this rarely-encountered species (as discussed above) and expressed that, due to the limited data available to inform the model, it “should be viewed cautiously” (Roberts 
                    <E T="03">et al.,</E>
                     2015).
                </P>
                <P>
                    NOAA surveys in the GOM from 1992-2009 reported only 16 sightings of killer whales, with an additional 3 encounters during more recent survey effort from 2017-18 (Waring 
                    <E T="03">et al.,</E>
                     2013; 
                    <E T="03">https://www.boem.gov/gommapps</E>
                    ). Two other species were also observed on fewer than 20 occasions during the 1992-2009 NOAA surveys (Fraser's dolphin and false killer whale 
                    <SU>3</SU>
                    <FTREF/>
                    ). However, observational data collected by protected species observers (PSOs) on industry geophysical survey vessels from 2002-2015 distinguish the killer whale in terms of rarity. During this period, killer whales were encountered on only 10 occasions, whereas the next most rarely encountered species (Fraser's dolphin) was recorded on 69 occasions (Barkaszi and Kelly, 2019). The false killer whale and pygmy killer whale were the next most rarely encountered species, with 110 records each. The killer whale was the species with the lowest detection frequency during each period over which PSO data were synthesized (2002-2008 and 2009-2015). This information qualitatively informed our rulemaking process, as discussed at 86 FR 5334 (January 19, 
                    <PRTPAGE P="1907"/>
                    2021), and similarly informs our analysis here.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         However, note that these species have been observed over a greater range of water depths in the GOM than have killer whales.
                    </P>
                </FTNT>
                <P>
                    The rarity of encounters during seismic surveys is not likely to be the product of high bias on the probability of detection. Unlike certain cryptic species with high detection bias, such as 
                    <E T="03">Kogia</E>
                     spp. or beaked whales, or deep-diving species with high availability bias, such as beaked whales or sperm whales, killer whales are typically available for detection when present and are easily observed. Roberts 
                    <E T="03">et al.</E>
                     (2015) stated that availability is not a major factor affecting detectability of killer whales from shipboard surveys, as they are not a particularly long-diving species. Baird 
                    <E T="03">et al.</E>
                     (2005) reported that mean dive durations for 41 fish-eating killer whales for dives greater than or equal to 1 minute in duration was 2.3-2.4 minutes, and Hooker 
                    <E T="03">et al.</E>
                     (2012) reported that killer whales spent 78 percent of their time at depths between 0-10 m. Similarly, Kvadsheim 
                    <E T="03">et al.</E>
                     (2012) reported data from a study of 4 killer whales, noting that the whales performed 20 times as many dives 1-30 m in depth than to deeper waters, with an average depth during those most common dives of approximately 3 m.
                </P>
                <P>In summary, killer whales are the most rarely encountered species in the GOM and typically occur only in particularly deep water (&gt;700 m). This survey would take place in deep waters that would overlap with depths in which killer whales typically occur. While this information is reflected through the density model informing the acoustic exposure modeling results, there is relatively high uncertainty associated with the model for this species, and the acoustic exposure modeling applies mean distribution data over areas where the species is in fact less likely to occur. NMFS' determination in reflection of the data discussed above, which informed the final rule, is that use of the generic acoustic exposure modeling results for killer whales will generally result in estimated take numbers that are inconsistent with the assumptions made in the rule regarding expected killer whale take (86 FR 5403, January 19, 2021).</P>
                <P>
                    In past authorizations, NMFS has often addressed situations involving the low likelihood of encountering a rare species, such as killer whales in the GOM, through authorization of take of a single group of average size (
                    <E T="03">i.e.,</E>
                     representing a single potential encounter). See 83 FR 63268, December 7, 2018. See also 86 FR 29090, May 28, 2021 and 85 FR 55645, September 9, 2020. For the reasons expressed above, NMFS determined that a single encounter of killer whales is more likely than the model-generated estimates and has authorized take associated with a single group encounter (
                    <E T="03">i.e.,</E>
                     up to seven animals).
                </P>
                <P>Based on the results of our analysis, NMFS has determined that the level of taking expected for this survey and authorized through the LOA is consistent with the findings made for the total taking allowable under the regulations. See table 1 in this notice and table 9 of the rule (86 FR 5322, January 19, 2021).</P>
                <HD SOURCE="HD1">Small Numbers Determination</HD>
                <P>Under the GOM rule, NMFS may not authorize incidental take of marine mammals in an LOA if it will exceed “small numbers.” In short, when an acceptable estimate of the individual marine mammals taken is available, if the estimated number of individual animals taken is up to, but not greater than, one-third of the best available abundance estimate, NMFS will determine that the numbers of marine mammals taken of a species or stock are small. For more information please see NMFS' discussion of the MMPA's small numbers requirement provided in the final rule (86 FR 5438, January 19, 2021).</P>
                <P>The take numbers for authorization are determined as described above in the Summary of Request and Analysis section. Subsequently, the total incidents of harassment for each species are multiplied by scalar ratios to produce a derived product that better reflects the number of individuals likely to be taken within a survey (as compared to the total number of instances of take), accounting for the likelihood that some individual marine mammals may be taken on more than 1 day (see 86 FR 5404, January 19, 2021). The output of this scaling, where appropriate, is incorporated into adjusted total take estimates that are the basis for NMFS' small numbers determinations, as depicted in table 1.</P>
                <P>
                    This product is used by NMFS in making the necessary small numbers determinations through comparison with the best available abundance estimates (see discussion at 86 FR 5391, January 19, 2021). For this comparison, NMFS' approach is to use the maximum theoretical population, determined through review of current stock assessment reports (SAR; 
                    <E T="03">https://www.fisheries.noaa.gov/national/marine-mammal-protection/marine-mammal-stock-assessments</E>
                    ) and model-predicted abundance information (
                    <E T="03">https://seamap.env.duke.edu/models/Duke/GOM/</E>
                    ). For the latter, for taxa where a density surface model could be produced, we use the maximum mean seasonal (
                    <E T="03">i.e.,</E>
                     3-month) abundance prediction for purposes of comparison as a precautionary smoothing of month-to-month fluctuations and in consideration of a corresponding lack of data in the literature regarding seasonal distribution of marine mammals in the GOM. Information supporting the small numbers determinations is provided in table 1.
                </P>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s50,12,10,12,10">
                    <TTITLE>Table 1—Take Analysis</TTITLE>
                    <BOXHD>
                        <CHED H="1">Species</CHED>
                        <CHED H="1">
                            Authorized 
                            <LI>take</LI>
                        </CHED>
                        <CHED H="1">
                            Scaled 
                            <LI>
                                take 
                                <SU>1</SU>
                            </LI>
                        </CHED>
                        <CHED H="1">
                            Abundance 
                            <SU>2</SU>
                        </CHED>
                        <CHED H="1">
                            Percent 
                            <LI>abundance</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">
                            Rice's whale 
                            <SU>3</SU>
                        </ENT>
                        <ENT>0</ENT>
                        <ENT>n/a</ENT>
                        <ENT>51</ENT>
                        <ENT>n/a</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Sperm whale</ENT>
                        <ENT>138</ENT>
                        <ENT>58.2</ENT>
                        <ENT>2,207</ENT>
                        <ENT>2.6</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            <E T="03">Kogia</E>
                             spp
                        </ENT>
                        <ENT>
                            <SU>4</SU>
                             77
                        </ENT>
                        <ENT>22.8</ENT>
                        <ENT>4,373</ENT>
                        <ENT>0.7</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Beaked whales</ENT>
                        <ENT>1,216</ENT>
                        <ENT>122.8</ENT>
                        <ENT>3,768</ENT>
                        <ENT>3.3</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Rough-toothed dolphin</ENT>
                        <ENT>226</ENT>
                        <ENT>64.9</ENT>
                        <ENT>4,853</ENT>
                        <ENT>1.3</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bottlenose dolphin</ENT>
                        <ENT>
                            <SU>5</SU>
                             21
                        </ENT>
                        <ENT>6.0</ENT>
                        <ENT>176,108</ENT>
                        <ENT>0.0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Clymene dolphin</ENT>
                        <ENT>596</ENT>
                        <ENT>171.2</ENT>
                        <ENT>11,895</ENT>
                        <ENT>1.4</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Atlantic spotted dolphin</ENT>
                        <ENT>0</ENT>
                        <ENT>n/a</ENT>
                        <ENT>74,785</ENT>
                        <ENT>n/a</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pantropical spotted dolphin</ENT>
                        <ENT>5,921</ENT>
                        <ENT>1,699.5</ENT>
                        <ENT>102,361</ENT>
                        <ENT>1.7</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Spinner dolphin</ENT>
                        <ENT>139</ENT>
                        <ENT>39.9</ENT>
                        <ENT>25,114</ENT>
                        <ENT>0.2</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Striped dolphin</ENT>
                        <ENT>310</ENT>
                        <ENT>88.9</ENT>
                        <ENT>5,229</ENT>
                        <ENT>1.7</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Fraser's dolphin</ENT>
                        <ENT>97</ENT>
                        <ENT>28.0</ENT>
                        <ENT>1,665</ENT>
                        <ENT>1.7</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Risso's dolphin</ENT>
                        <ENT>96</ENT>
                        <ENT>28.4</ENT>
                        <ENT>3,764</ENT>
                        <ENT>0.8</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Melon-headed whale</ENT>
                        <ENT>384</ENT>
                        <ENT>113.4</ENT>
                        <ENT>7,003</ENT>
                        <ENT>1.6</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pygmy killer whale</ENT>
                        <ENT>187</ENT>
                        <ENT>55.2</ENT>
                        <ENT>2,126</ENT>
                        <ENT>2.6</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="1908"/>
                        <ENT I="01">False killer whale</ENT>
                        <ENT>212</ENT>
                        <ENT>62.4</ENT>
                        <ENT>3,204</ENT>
                        <ENT>1.9</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Killer whale</ENT>
                        <ENT>7</ENT>
                        <ENT>n/a</ENT>
                        <ENT>267</ENT>
                        <ENT>2.6</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Short-finned pilot whale</ENT>
                        <ENT>30</ENT>
                        <ENT>9.0</ENT>
                        <ENT>1,981</ENT>
                        <ENT>0.5</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>1</SU>
                         Scalar ratios were applied to “Authorized Take” values as described at 86 FR 5322, 5404 (January 19, 2021) to derive scaled take numbers shown here.
                    </TNOTE>
                    <TNOTE>
                        <SU>2</SU>
                         Best abundance estimate. For most taxa, the best abundance estimate for purposes of comparison with take estimates is considered here to be the model-predicted abundance (Roberts 
                        <E T="03">et al.,</E>
                         2016). For those taxa where a density surface model predicting abundance by month was produced, the maximum mean seasonal abundance was used. For those taxa where abundance is not predicted by month, only mean annual abundance is available. For Rice's whale and killer whale, the larger estimated SAR abundance estimate is used.
                    </TNOTE>
                    <TNOTE>
                        <SU>3</SU>
                         The final rule refers to the GOM Bryde's whale (
                        <E T="03">Balaenoptera edeni</E>
                        ). These whales were subsequently described as a new species, Rice's whale (
                        <E T="03">Balaenoptera ricei</E>
                        ) (Rosel 
                        <E T="03">et al.,</E>
                         2021).
                    </TNOTE>
                    <TNOTE>
                        <SU>4</SU>
                         Includes 6 takes by Level A harassment and 71 takes by Level B harassment. Scalar ratio is applied to takes by Level B harassment only; small numbers determination made on basis of scaled Level B harassment take plus authorized Level A harassment take.
                    </TNOTE>
                    <TNOTE>
                        <SU>5</SU>
                         Modeled take of 6 increased to account for potential encounter with group of average size (Maze-Foley and Mullin, 2006).
                    </TNOTE>
                </GPOTABLE>
                <P>
                    Based on the analysis contained herein of Chevron's proposed survey activity described in its LOA application and the anticipated take of marine mammals, NMFS finds that small numbers of marine mammals will be taken relative to the affected species or stock sizes (
                    <E T="03">i.e.,</E>
                     less than one-third of the best available abundance estimate) and therefore the taking is of no more than small numbers.
                </P>
                <HD SOURCE="HD1">Authorization</HD>
                <P>NMFS has determined that the level of taking for this LOA request is consistent with the findings made for the total taking allowable under the incidental take regulations and that the amount of take authorized under the LOA is of no more than small numbers. Accordingly, we have issued an LOA to Chevron authorizing the take of marine mammals incidental to its geophysical survey activity, as described above.</P>
                <SIG>
                    <DATED>Dated: January 5, 2024.</DATED>
                    <NAME>Kimberly Damon-Randall,</NAME>
                    <TITLE>Director, Office of Protected Resources, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00368 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <DEPDOC>[RTID 0648-XD589]</DEPDOC>
                <SUBJECT>Marine Mammals; File No. 27099</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; receipt of application for permit amendment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Notice is hereby given that Pacific Whale Foundation (Responsible Party: Jens Curie), 300 Ma'alaea Rd. Ste. 211, Wailuku, Hawaii 96793, has applied for an amendment to Scientific Research Permit No. 27099.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments must be received on or before February 12, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The application and related documents are available for review by selecting “Records Open for Public Comment” from the “Features” box on the Applications and Permits for Protected Species (APPS) home page, 
                        <E T="03">https://apps.nmfs.noaa.gov,</E>
                         and then selecting File No. 27099 from the list of available applications. These documents are also available upon written request via email to 
                        <E T="03">NMFS.Pr1Comments@noaa.gov.</E>
                    </P>
                    <P>
                        Written comments on this application should be submitted via email to 
                        <E T="03">NMFS.Pr1Comments@noaa.gov.</E>
                         Please include File No. 27099 in the subject line of the email comment.
                    </P>
                    <P>
                        Those individuals requesting a public hearing should submit a written request via email to 
                        <E T="03">NMFS.Pr1Comments@noaa.gov.</E>
                         The request should set forth the specific reasons why a hearing on this application would be appropriate.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Courtney Smith, Ph.D., or Erin Markin, Ph.D., (301) 427-8401.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The subject amendment to Permit No. 27099 is requested under the authority of the Marine Mammal Protection Act of 1972, as amended (16 U.S.C. 1361 
                    <E T="03">et seq.</E>
                    ), the regulations governing the taking and importing of marine mammals (50 CFR part 216), the Endangered Species Act of 1973, as amended (16 U.S.C. 1531 
                    <E T="03">et seq.</E>
                    ), and the regulations governing the taking, importing, and exporting of endangered and threatened species (50 CFR parts 222-226).
                </P>
                <P>
                    Permit No. 27099, issued on April 28, 2023 (88 FR 31737, May 18, 2023), authorizes the permit holder to harass up to 1200 of the following cetaceans species, annually, during vessel, underwater, and unoccupied aerial systems (UAS) surveys within waters of the Main Hawaiian Islands: Blainville's beaked (
                    <E T="03">Mesoplodon densirostris</E>
                    ), Bryde's (
                    <E T="03">Balaenoptera brydei</E>
                    ), Cuvier's beaked (
                    <E T="03">Ziphius cavirostris</E>
                    ), dwarf sperm (
                    <E T="03">Kogia sima</E>
                    ), false killer (
                    <E T="03">Pseudorca crassidens;</E>
                     including the endangered Main Hawaiian Islands insular Distinct Population Segment), fin (
                    <E T="03">Balaenoptera physalus</E>
                    ), humpback (
                    <E T="03">Megaptera novaeangliae</E>
                    ), killer (
                    <E T="03">Orcinus orca</E>
                    ), melon-headed (
                    <E T="03">Peponocephala electra</E>
                    ), minke (
                    <E T="03">Balaenoptera acutorostrata</E>
                    ), pygmy killer (
                    <E T="03">Feresa attenuata</E>
                    ), pygmy sperm (
                    <E T="03">Kogia breviceps</E>
                    ), short-finned pilot (
                    <E T="03">Globicephala macrorhynchus</E>
                    ), and sperm (
                    <E T="03">Physeter macrocephalus</E>
                    ) whales; and common bottlenose (
                    <E T="03">Tursiops truncatus</E>
                    ), Fraser's (
                    <E T="03">Lagenodelphis hosei</E>
                    ), pantropical spotted (
                    <E T="03">Stenella attenuata</E>
                    ), Risso's (
                    <E T="03">Grampus griseus</E>
                    ), rough-toothed (
                    <E T="03">Steno bredanensis</E>
                    ), short-beaked common (
                    <E T="03">Delphinus delphis</E>
                    ), spinner (
                    <E T="03">Stenella longistrostris longirostris</E>
                    ), and striped (
                    <E T="03">Stenella coeruleoalba</E>
                    ) dolphins. The objective of research is to assess the human impacts on, and the distribution, abundance, social organization, population structure, population size, foraging, diet, reproduction, movements, habitat use, body condition, health, and behavior of Hawaiian cetaceans. Permitted research procedures include photo-ID, photogrammetry, underwater filming, suction-cup tagging, biopsy collection, fecal sampling, sloughed skin collection, and exhaled air sample collection. Up to 10 suction-cup tags and up to 40 biopsy samples may be taken from the above-listed species. The permit holder is requesting the permit be amended to include authorization to import up to 40 humpback whale (East Australia Distinct Population Segment) biopsy samples from Australia. The imported samples will be used to 
                    <PRTPAGE P="1909"/>
                    address a new study objective to understand the factors influencing humpback whale migration along the east coast of Australia within the context of a rapidly changing environment. Specifically, the study aims to analyze the size, age, and body condition of the sub-population of whales undertaking migration in a given year to provide insights into the overall health and status of the regional humpback whale population. The permit is valid through April 30, 2028. All other terms and conditions of the permit would remain the same.
                </P>
                <P>
                    In compliance with the National Environmental Policy Act of 1969 (42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ), an initial determination has been made that the activity proposed is categorically excluded from the requirement to prepare an environmental assessment or environmental impact statement.
                </P>
                <P>
                    Concurrent with the publication of this notice in the 
                    <E T="04">Federal Register</E>
                    , NMFS is forwarding copies of this application to the Marine Mammal Commission and its Committee of Scientific Advisors.
                </P>
                <SIG>
                    <DATED>Dated: January 8, 2024.</DATED>
                    <NAME>Julia M. Harrison,</NAME>
                    <TITLE>Chief, Permits and Conservation Division, Office of Protected Resources, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00450 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <DEPDOC>[RTID 0648-XD644]</DEPDOC>
                <SUBJECT>New England Fishery Management Council; Public Meeting</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of public meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The New England Fishery Management Council (Council, NEFMC) will hold a three-day hybrid meeting with both in-person and remote participation to consider actions affecting New England fisheries in the exclusive economic zone (EEZ).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The meeting will be held on Tuesday, Wednesday, and Thursday, January 30, January 31, and February 1, 2024, beginning at 9 a.m. each day.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The meeting will take place at The Venue at Portwalk Place, 22 Portwalk Place, Portsmouth, NH 03801; telephone (603) 422-6114; online at 
                        <E T="03">https://www.thevenueatportwalkplace.com</E>
                        . Join the webinar at 
                        <E T="03">https://attendee.gotowebinar.com/register/4656306835494284629</E>
                        .
                    </P>
                    <P>
                        <E T="03">Council address:</E>
                         New England Fishery Management Council, 50 Water Street, Mill 2, Newburyport, MA 01950; telephone (978) 465-0492; 
                        <E T="03">www.nefmc.org</E>
                        .
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Cate O'Keefe, Executive Director, New England Fishery Management Council; telephone: (978) 465-0492, ext. 113.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Agenda</HD>
                <HD SOURCE="HD2">Tuesday, January 30, 2024</HD>
                <P>The Council will begin this meeting in Closed Session to discuss appointments to its Scientific and Statistical Committee. At 9:30 a.m., the open session will begin with brief announcements, followed by reports on recent activities from the Council's Chair and Executive Director, the GARFO Regional Administrator, the NOAA Office of General Counsel, the Northeast Fisheries Science Center (NEFSC) Director, the Mid-Atlantic Fishery Management Council liaison, and representatives from the Atlantic States Marine Fisheries Commission (ASMFC), the U.S. Coast Guard, NOAA's Office of Law Enforcement, the U.S. Fish and Wildlife Service, and the Advisory Committee to the U.S. Section of the International Commission for the Conservation of Atlantic Tunas (ICCAT). The Council then will receive a progress report from its Risk Policy Working Group that will focus on addressing Terms of Reference 1 and 2 to revise the Council's Risk Policy. Next, the Council will receive an update from GARFO and the NOAA National Centers for Coastal Ocean Science on revised siting for the Blue Water Fisheries offshore aquaculture project in federal waters off the coast of New Hampshire.</P>
                <P>
                    After the lunch break, members of the public will have the opportunity to speak during an open comment period on issues that relate to Council business but are not included on the published agenda for this meeting. The Council asks the public to limit remarks to 3-5 minutes. These comments will be received both in person and through the webinar. A guide for how to publicly comment through the webinar is available on the Council website at 
                    <E T="03">https://s3.amazonaws.com/nefmc.org/NEFMC-meeting-remote-participation_generic.pdf.</E>
                     The Council then will hear from its Herring Committee, which will provide an update on Amendment 10 to the Atlantic Herring Fishery Management Plan. This is an action to minimize user conflicts in the herring fishery. The Council will review a draft scoping document and scoping meeting schedule to gather public input on the range of issues that potentially could be addressed in this amendment. To close out the day, the Council will receive a congressional update on current legislative activities. Following the adjournment of official business, the Council will host a public outreach session to foster open lines of communication among Council members, staff, industry, and all meeting attendees. This event will be held at the AC Hotel on the Lobby Level, 299 Vaughn Street, which is a four-minute walk from the Council meeting room at The Venue at Portwalk Place in Portsmouth, NH.
                </P>
                <HD SOURCE="HD2">Wednesday, January 31, 2024</HD>
                <P>
                    The Council will begin the second day of its meeting with a presentation on the three-year review of the Northeast Region's Standardized Bycatch Reporting Methodology. Next, the Council will receive a report on activities within the Northeast Fisheries Science Center's Fishery Monitoring and Research Division, including: (1) the status of ongoing responsibilities; (2) at-sea monitoring and observer program activities; and (3) cooperative research updates. This report will be followed by an overview of a Northeast Fisheries Science Center white paper outlining potential plans for industry-based surveys to complement federal spring and fall bottom trawl surveys on the NOAA ship 
                    <E T="03">Henry B. Bigelow.</E>
                     The Council will have an opportunity to provide input on research priorities for consideration in future industry-based survey as they relate to its own research priorities.
                </P>
                <P>
                    Following the lunch break, the Council will receive a NOAA Fisheries presentation on the Marine Recreational Information Program (MRIP), which will include an update on the status of MRIP's Fishing Effort Survey (FES). This will be followed by the Groundfish Committee report, which will cover four items as follows. (1) Recreational Measures: the Council will provide recommendations to GARFO on fishing year 2024 recreational measures for Georges Bank cod, Gulf of Maine cod, and Gulf of Maine haddock. (2) The Atlantic Cod Management Transition Plan: the Council will receive an update on transition planning. (3) Metrics for the Groundfish Amendment 23 Monitoring System Review: the Council will receive a progress report on this action. And (4) 2024 Groundfish Priorities: the Council will receive a preliminary overview of the groundfish 
                    <PRTPAGE P="1910"/>
                    workplan for year ahead. As the final item of business for the day, the Council will revisit fishing year 2024-2026 specifications approved in December 2023 for the small-mesh multispecies (whiting) fishery to address southern red hake rebuilding.
                </P>
                <HD SOURCE="HD2">Thursday, February 1, 2024</HD>
                <P>The Council will lead off the third day of its meeting with a Spiny Dogfish Committee report, where it will review, discuss, and approve fishing year 2024-2026 spiny dogfish specifications. Next, the Council will receive a progress report on Monkfish Framework 15, which is part of a joint New England/Mid-Atlantic Council action to reduce monkfish/dogfish large-mesh gillnet fishery interactions with Atlantic sturgeon. Then, the Council will receive an update from its On-Demand Fishing Gear Conflict Working Group on activities to prevent or reduce potential gear conflicts between mobile, fixed, and recreational gear and on-demand (ropeless) fishing gear. This update will be followed by a presentation on the peer-reviewed 2023 Black Sea Bass Research Track Stock Assessment. The Council then will close out the meeting with other business.</P>
                <P>Although non-emergency issues not contained on this agenda may come before the Council for discussion, those issues may not be the subject of formal action during this meeting. Council action will be restricted to those issues specifically listed in this notice and any issues arising after publication of this notice that require emergency action under section 305(c) of the Magnuson-Stevens Fishery Conservation and Management Act, provided the public has been notified of the Council's intent to take final action to address the emergency. The public also should be aware that the meeting will be recorded. Consistent with 16 U.S.C. 1852, a copy of the recording is available upon request.</P>
                <HD SOURCE="HD1">Special Accommodations</HD>
                <P>
                    This meeting is physically accessible to people with disabilities. Requests for sign language interpretation or other auxiliary aids should be directed to Executive Director Cate O'Keefe (see 
                    <E T="02">ADDRESSES</E>
                    ) at least 5 days prior to the meeting date.
                </P>
                <P>
                    <E T="03">Authority:</E>
                     16 U.S.C. 1801 
                    <E T="03">et seq.</E>
                </P>
                <SIG>
                    <DATED>Dated: January 8, 2024.</DATED>
                    <NAME>Rey Israel Marquez,</NAME>
                    <TITLE>Acting Deputy Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00471 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <DEPDOC>[RTID 0648-XD638]</DEPDOC>
                <SUBJECT>Endangered and Threatened Species; Take of Anadromous Fish</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>Withdrawal of notice of intent to prepare an environmental impact statement.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>NMFS is issuing this notice to advise Federal, state, and local government agencies and the public of withdrawal of the Notice of Intent (NOI) to prepare an Environmental Impact Statement (EIS) for the proposed operation of salmon hatchery programs in the Nooksack River Basin in Washington.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Morgan Robinson, Lacey, WA (phone: 253-307-2670, email: 
                        <E T="03">morgan.robinson@noaa.gov</E>
                        ).
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    NMFS published a NOI in the 
                    <E T="04">Federal Register</E>
                     on June 20, 2016 (81 FR 39911) to prepare an EIS in accordance with the National Environmental Policy Act (NEPA) to analyze the impacts on the human environment resulting from the operation of salmon hatchery programs in the Nooksack River Basin in Washington. NMFS hereby advises the public of the rescission of this NOI. This change occurred because the proposed hatchery and genetic management plans jointly submitted by the Washington Department of Fish and Wildlife, the Lummi Nation, the Nooksack Indian Tribe, the Upper Skagit Indian Tribe, and the Swinomish Indian Tribal Community as co-managers were withdrawn since the NOI was published.
                </P>
                <P>Any future hatchery and genetic management plans submitted by the above parties to NMFS will comply with the environmental review requirements of NEPA.</P>
                <SIG>
                    <DATED>Dated: January 8, 2024.</DATED>
                    <NAME>Angela Somma,</NAME>
                    <TITLE>Chief, Endangered Species Division, Office of Protected Resources, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00473 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF DEFENSE</AGENCY>
                <SUBAGY>Office of the Secretary</SUBAGY>
                <DEPDOC>[Docket ID: DoD-2024-OS-0005]</DEPDOC>
                <SUBJECT>Privacy Act of 1974; Matching Program</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Secretary, Department of Defense (DoD).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of a new matching program.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This Computer Matching Agreement (CMA) verifies the eligibility of Military Health System (MHS) beneficiaries who are Medicare eligible to receive TRICARE Benefits.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments will be accepted on or before February 12, 2024. This proposed action will be effective the day following the end of the comment period unless comments are received which result in a contrary determination.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by docket number and title, by any of the following methods:</P>
                    <P>
                        * 
                        <E T="03">Federal Rulemaking Portal: https://www.regulations.gov.</E>
                    </P>
                    <P>Follow the instructions for submitting comments.</P>
                    <P>
                        * 
                        <E T="03">Mail:</E>
                         Department of Defense, Office of the Assistant to the Secretary of Defense for Privacy, Civil Liberties, and Transparency, 4800 Mark Center Drive, Mailbox #24, Suite 08D09, Alexandria, VA 22350-1700.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions received must include the agency name and docket number for this 
                        <E T="04">Federal Register</E>
                         document. The general policy for comments and other submissions from members of the public is to make these submissions available for public viewing on the internet at 
                        <E T="03">https://www.regulations.gov</E>
                         as they are received without change, including any personal identifiers or contact information.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Ms. Mindy Smith, Management and Program Analyst, Privacy and Civil Liberties Directorate at (703) 571-0070.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The DoD, Defense Manpower Data Center (DMDC) will provide the Department of Health and Human Services (HHS), Centers for Medicare and Medicaid Services (CMS) a list of specific data elements for all DoD eligible beneficiaries both over and under the age of 65. CMS will: (1) match the Social Security Numbers (SSNs) of beneficiaries provided by DMDC against the information found in CMS's “Enrollment Database (EDB)” system of records; (2) validate the identification of the individual against CMS beneficiary records based on SSN and date of birth 
                    <PRTPAGE P="1911"/>
                    provided by DMDC; (3) provide the individual's Medicare Beneficiary ID (MBI), Medicare enrollment status and address in the response file to DMDC. After receipt of the response file from CMS, DMDC will update the Defense Enrollment Eligibility Reporting System (DEERS) with appropriate Medicare information provided in the response file. The verified identification of eligible beneficiaries and their current Medicare enrollment status is maintained in DEERS for use by the Defense Health Agency in the management of its programs.
                </P>
                <P>
                    <E T="03">Participating Agencies:</E>
                     The Department of Defense, Defense Manpower Data Center, and the Department of Health and Human Services, Centers for Medicare and Medicaid Services.
                </P>
                <P>
                    <E T="03">Authority for Conducting the Matching Program:</E>
                     10 U.S.C. 1086(d).
                </P>
                <P>
                    <E T="03">Purpose(s):</E>
                     This matching program verifies the eligibility of MHS beneficiaries who are Medicare eligible to receive TRICARE benefits.
                </P>
                <P>
                    <E T="03">Categories of Individuals:</E>
                     The categories of individuals whose information is involved in the matching program is all members and retirees of the DoD and all the Uniformed Services, and DoD beneficiaries (
                    <E T="03">e.g.,</E>
                     dependent family members, legal guardians and other protectors and prior military members eligible for Department of Veterans Affairs benefits).
                </P>
                <P>
                    <E T="03">Categories of Records:</E>
                     The categories of records involved in the matching program are SSN, date of birth, sex code, and Medicare data, including the assigned MBI, Medicare enrollment status, and address. DMDC will provide CMS with a finder file for the Under and Over 65 Populations to match against an assigned CMS Health Insurance Claim Number (HICN) or MBI which are contained within EDB. The finder file sent from DoD will contain SSN, date of birth, sex code, and first and last name. The finder file will be used for SSN matching against an assigned HICN or MBI number. CMS will provide DoD with a reply file which will contain SSN, date of birth, sex code, first name, last name, and Medicare data. DMDC will provide data for approximately 10 million beneficiaries from DEERS to CMS for matching on a weekly basis. CMS will provide a reply file containing all appropriate matched and failed responses.
                </P>
                <P>
                    <E T="03">System of Records:</E>
                     “Defense Enrollment Eligibility Reporting System (DEERS),” DMDC 02 DoD, published in full at 87 FR 32384 (May 31, 2022). “Military Health Information System (MHIS),” EDHA 07, published at 85 FR 36190 (June 15, 2020). “Enrollment Database (EDB),” 09-70-0502, published in full at 73 FR 10249 (February 26, 2008), updated at 78 FR 23938 (April 23, 2013), 81 FR 8204 (February 18, 2016), and 83 FR 6591 (February 14, 2018).
                </P>
                <SIG>
                    <DATED>Dated: January 9, 2024.</DATED>
                    <NAME>Aaron T. Siegel,</NAME>
                    <TITLE>Alternate OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00589 Filed 1-9-24; 4:15 pm]</FRDOC>
            <BILCOD>BILLING CODE 6001-FR-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF EDUCATION</AGENCY>
                <DEPDOC>[Docket No.: ED-2024-SCC-0004]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Comment Request; Office of State Support Progress Check Quarterly Protocol</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Elementary and Secondary Education (OESE), Department of Education (ED).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Paperwork Reduction Act (PRA) of 1995, the Department is proposing an extension without change of a currently approved information collection request (ICR).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Interested persons are invited to submit comments on or before March 11, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        To access and review all the documents related to the information collection listed in this notice, please use 
                        <E T="03">http://www.regulations.gov</E>
                         by searching the Docket ID number ED-2024-SCC-0004. Comments submitted in response to this notice should be submitted electronically through the Federal eRulemaking Portal at 
                        <E T="03">http://www.regulations.gov</E>
                         by selecting the Docket ID number or via postal mail, commercial delivery, or hand delivery. If the regulations.gov site is not available to the public for any reason, the Department will temporarily accept comments at 
                        <E T="03">ICDocketMgr@ed.gov.</E>
                         Please include the docket ID number and the title of the information collection request when requesting documents or submitting comments. Please note that comments submitted after the comment period will not be accepted. Written requests for information or comments submitted by postal mail or delivery should be addressed to the Manager of the Strategic Collections and Clearance Governance and Strategy Division, U.S. Department of Education, 400 Maryland Ave. SW, LBJ, Room 6W203, Washington, DC 20202-8240.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>For specific questions related to collection activities, please contact Andrew Brake, 202-453-6136.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Department, in accordance with the Paperwork Reduction Act of 1995 (PRA) (44 U.S.C. 3506(c)(2)(A)), provides the general public and Federal agencies with an opportunity to comment on proposed, revised, and continuing collections of information. This helps the Department assess the impact of its information collection requirements and minimize the public's reporting burden. It also helps the public understand the Department's information collection requirements and provide the requested data in the desired format. The Department is soliciting comments on the proposed information collection request (ICR) that is described below. The Department is especially interested in public comment addressing the following issues: (1) is this collection necessary to the proper functions of the Department; (2) will this information be processed and used in a timely manner; (3) is the estimate of burden accurate; (4) how might the Department enhance the quality, utility, and clarity of the information to be collected; and (5) how might the Department minimize the burden of this collection on the respondents, including through the use of information technology. Please note that written comments received in response to this notice will be considered public records.</P>
                <P>
                    <E T="03">Title of Collection:</E>
                     Office of State Support Progress Check Quarterly Protocol.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     1810-0733.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     An extension without change of a currently approved ICR.
                </P>
                <P>
                    <E T="03">Respondents/Affected Public:</E>
                     State, Local, and Tribal Governments.
                </P>
                <P>
                    <E T="03">Total Estimated Number of Annual Responses:</E>
                     212.
                </P>
                <P>
                    <E T="03">Total Estimated Number of Annual Burden Hours:</E>
                     636.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The Office of School Support and Accountability (SSA) administers Title I, Sections 1001-1004 (School Improvement); Title I, Part A (Improving Basic Programs Operated by Local Educational Agencies); Title I, Part B Grants for State Assessments and Related Activities; Title II, Part A (Supporting Effective Instruction); Title I, Part D (Neglected, Delinquent, or At-Risk); Title IV, Part B (21st Century Community Learning Centers); and McKinney-Vento Education for Homeless Children and Youth Program. Quarterly progress checks, phone or in-person conversations every three months of a fiscal year with State 
                    <PRTPAGE P="1912"/>
                    directors and coordinators, help ensure that State Educational Agencies (SEAs) are making progress toward increasing student achievement and improving the quality of instruction for all students through regular conversations about the quality of SEA implementation of SSA administered programs. The information shared with SSA helps inform the selection and delivery of technical assistance to SEAs and aligns structures, processes, and routines so SSA can regularly monitor the connection between grant administration and intended outcomes. Progress checks also allow SSA to proactively engage with SEAs to identify any issues ahead of formal monitoring visits, decreasing the need for enforcement actions and minimizing burden for SEAs. This is a request for a renewal without change of this collection.
                </P>
                <SIG>
                    <DATED>Dated: January 8, 2024.</DATED>
                    <NAME>Kun Mullan,</NAME>
                    <TITLE>PRA Coordinator, Strategic Collections and Clearance, Governance and Strategy Division, Office of Chief Data Officer, Office of Planning, Evaluation and Policy Development.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00438 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4000-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket No. OR24-2-000]</DEPDOC>
                <SUBJECT>Husky US Marketing LLC and Phillips 66 Company v. TransCanada Keystone Pipeline, LP; Notice of Complaint</SUBJECT>
                <P>Take notice that on January 3, 2024, pursuant to Rule 206 of the Rules of Practice and Procedure of the Federal Energy Regulatory Commission, 18 CFR 385.206 (2022), Husky US Marketing LLC and Phillips 66 Company filed a complaint against TransCanada Keystone Pipeline, LP challenging the lawfulness of rates charged by TransCanada Keystone Pipeline, LP.</P>
                <P>The Complainant certifies that copies of the complaint were served on the contacts listed for Respondents in the Commission's list of Corporate Officials.</P>
                <P>Any person desiring to intervene or to protest this filing must file in accordance with Rules 211 and 214 of the Commission's Rules of Practice and Procedure (18 CFR 385.211, 385.214). Protests will be considered by the Commission in determining the appropriate action to be taken but will not serve to make protestants parties to the proceeding. Any person wishing to become a party must file a notice of intervention or motion to intervene, as appropriate. The Respondent's answer and all interventions, or protests must be filed on or before the comment date. The Respondent's answer, motions to intervene, and protests must be served on the Complainants.</P>
                <P>
                    In addition to publishing the full text of this document in the 
                    <E T="04">Federal Register</E>
                    , the Commission provides all interested persons an opportunity to view and/or print the contents of this document via the internet through the Commission's Home Page (
                    <E T="03">http://www.ferc.gov</E>
                    ) using the “eLibrary” link. To access this document in eLibrary, type the docket number excluding the last three digits of this document in the docket number field. 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>
                    The Commission strongly encourages electronic filings of comments, protests and interventions in lieu of paper using the “eFiling” link at 
                    <E T="03">http://www.ferc.gov.</E>
                     Persons unable to file electronically may mail similar pleadings to the Federal Energy Regulatory Commission, 888 First Street NE, Washington, DC 20426. Hand delivered submissions in docketed proceedings should be delivered to Health and Human Services, 12225 Wilkins Avenue, Rockville, Maryland 20852.
                </P>
                <P>
                    The Commission's Office of Public Participation (OPP) supports meaningful public engagement and participation in Commission proceedings. OPP can help members of the public, including landowners, environmental justice communities, Tribal members and others, access publicly available information and navigate Commission processes. For public inquiries and assistance with making filings such as interventions, comments, or requests for rehearing, the public is encouraged to contact OPP at (202) 502-6595 or 
                    <E T="03">OPP@ferc.gov.</E>
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. eastern time on February 02, 2024.
                </P>
                <SIG>
                    <DATED>Dated: January 5, 2024.</DATED>
                    <NAME>Debbie-Anne A. Reese,</NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-00426 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Project No. 2336-000]</DEPDOC>
                <SUBJECT>Georgia Power Company; Notice of Authorization for Continued Project Operation</SUBJECT>
                <P>The license for the Lloyd Shoals Hydroelectric Project No. 2336 was issued for a period ending December 31, 2023.</P>
                <P>Section 15(a)(1) of the FPA, 16 U.S.C. 808(a)(1), requires the Commission, at the expiration of a license term, to issue from year-to-year an annual license to the then licensee(s) under the terms and conditions of the prior license until a new license is issued, or the project is otherwise disposed of as provided in section 15 or any other applicable section of the FPA. If the project's prior license waived the applicability of section 15 of the FPA, then, based on section 9(b) of the Administrative Procedure Act, 5 U.S.C. 558(c), and as set forth at 18 CFR 16.21(a), if the licensee of such project has filed an application for a subsequent license, the licensee may continue to operate the project in accordance with the terms and conditions of the license after the minor or minor part license expires, until the Commission acts on its application. If the licensee of such a project has not filed an application for a subsequent license, then it may be required, pursuant to 18 CFR 16.21(b), to continue project operations until the Commission issues someone else a license for the project or otherwise orders disposition of the project.</P>
                <P>If the project is subject to section 15 of the FPA, notice is hereby given that an annual license for Project No. 2336 is issued to Georgia Power Company for a period effective January 1, 2024, through December 31, 2024, or until the issuance of a new license for the project or other disposition under the FPA, whichever comes first. If issuance of a new license (or other disposition) does not take place on or before December 31, 2024, notice is hereby given that, pursuant to 18 CFR 16.18(c), an annual license under section 15(a)(1) of the FPA is renewed automatically without further order or notice by the Commission, unless the Commission orders otherwise.</P>
                <P>
                    If the project is not subject to section 15 of the FPA, notice is hereby given that Georgia Power Company is authorized to continue operation of the Lloyd Shoals Hydroelectric Project under the terms and conditions of the prior license until the issuance of a 
                    <PRTPAGE P="1913"/>
                    subsequent license for the project or other disposition under the FPA, whichever comes first.
                </P>
                <SIG>
                    <DATED>Dated: January 5, 2024.</DATED>
                    <NAME>Debbie-Anne A. Reese,</NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-00420 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <SUBJECT>Combined Notice of Filings</SUBJECT>
                <P>Take notice that the Commission has received the following Natural Gas Pipeline Rate and Refund Report filings:</P>
                <HD SOURCE="HD1">Filings Instituting Proceedings</HD>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP24-301-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Rockies Express Pipeline LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     4(d) Rate Filing: REX 2024-01-04 Negotiated Rate Agreement Amendment to be effective 1/5/2024.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     1/4/24.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20240104-5163.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 1/16/24.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP24-302-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Guardian Pipeline, L.L.C.
                </P>
                <P>
                    <E T="03">Description:</E>
                     4(d) Rate Filing: Amendment to Summary of Non-Conforming and Negotiated Rate Agreements to be effective 2/5/2024.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     1/5/24.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20240105-5025.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 1/17/24.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP24-303-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Rockies Express Pipeline LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     4(d) Rate Filing: REX 2024-01-05 Negotiated Rate Agreement to be effective 1/6/2024.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     1/5/24.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20240105-5115.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 1/17/24.
                </P>
                <P>Any person desiring to intervene, to protest, or to answer a complaint in any of the above proceedings must file in accordance with Rules 211, 214, or 206 of the Commission's Regulations (18 CFR 385.211, 385.214, or 385.206) on or before 5:00 p.m. Eastern time on the specified comment date. Protests may be considered, but intervention is necessary to become a party to the proceeding. </P>
                <P>
                    The filings are accessible in the Commission's eLibrary system (
                    <E T="03">https://elibrary.ferc.gov/idmws/search/fercgensearch.asp</E>
                    ) by querying the docket number.
                </P>
                <P>
                    eFiling is encouraged. More detailed information relating to filing requirements, interventions, protests, service, and qualifying facilities filings can be found at: 
                    <E T="03">http://www.ferc.gov/docs-filing/efiling/filing-req.pdf.</E>
                     For other information, call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.
                </P>
                <P>
                    The Commission's Office of Public Participation (OPP) supports meaningful public engagement and participation in Commission proceedings. OPP can help members of the public, including landowners, environmental justice communities, Tribal members and others, access publicly available information and navigate Commission processes. For public inquiries and assistance with making filings such as interventions, comments, or requests for rehearing, the public is encouraged to contact OPP at (202) 502-6595 or 
                    <E T="03">OPP@ferc.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: January 5, 2024.</DATED>
                    <NAME>Debbie-Anne A. Reese,</NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-00419 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket No. CP23-501-000]</DEPDOC>
                <SUBJECT>Port Arthur LNG, LLC, PALNG Common Facilities Company, LLC; Notice of Revised Schedule for Environmental Review of the Port Arthur Liquified Natural Gas Amendment</SUBJECT>
                <P>
                    This notice identifies the Federal Energy Regulatory Commission (Commission or FERC) staff's revised schedule for the completion of the environmental assessment (EA) for Port Arthur LNG, LLC's and PALNG Common Facilities Company, LLC's (collectively, PALNG) Port Arthur Liquified Natural Gas Amendment. The first notice of schedule, issued on August 30, 2023, identified December 19, 2023 as the EA issuance date. However, changes to the amendment scope by PALNG and deficient responses to environmental and engineering data requests precluded FERC staff from completing the environmental review by the EA issuance date.
                    <SU>1</SU>
                    <FTREF/>
                     As a result, staff has revised the schedule for issuance of the EA.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         On November 15, 2023, the Commission issued an environmental information request to PALNG requesting additional information needed to complete the environmental review for the amendment. The request stated that a schedule change was necessary for the issuance of the EA based on changes to the amendment scope identified in information provided by PALNG on November 6 and November 13, 2023. FERC staff also stated that a revised notice of schedule would be issued once the information needs identified in the environmental information request are reviewed for completeness to issue the EA.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Schedule for Environmental Review</HD>
                <FP SOURCE="FP-1">Issuance of EA—March 15, 2024</FP>
                <FP SOURCE="FP-1">
                    90-day Federal Authorization Decision Deadline 
                    <SU>2</SU>
                    <FTREF/>
                    —June 13, 2024
                </FP>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         The Commission's deadline applies to the decisions of other Federal agencies, and State agencies acting under federally delegated authority, that are responsible for Federal authorizations, permits, and other approvals necessary for proposed projects under the Natural Gas Act. Per 18 CFR 157.22(a), the Commission's deadline for other agency's decisions applies unless a schedule is otherwise established by Federal law.
                    </P>
                </FTNT>
                <P>If a schedule change becomes necessary, an additional notice will be provided so that the relevant agencies are kept informed of the amendment's progress.</P>
                <HD SOURCE="HD1">Additional Information</HD>
                <P>
                    In order to receive notification of the issuance of the EA and to keep track of all formal issuances and submittals in specific dockets, the Commission offers a free service called eSubscription. This can reduce the amount of time you spend researching proceedings by automatically providing you with notification of these filings, document summaries, and direct links to the documents. Go to 
                    <E T="03">https://www.ferc.gov/ferc-online/overview</E>
                     to register for eSubscription.
                </P>
                <P>
                    The Commission's Office of Public Participation (OPP) supports meaningful public engagement and participation in Commission proceedings. OPP can help members of the public, including landowners, environmental justice communities, Tribal members and others, access publicly available information and navigate Commission processes. For public inquiries and assistance with making filings such as interventions, comments, or requests for rehearing, the public is encouraged to contact OPP at (202) 502-6595 or 
                    <E T="03">OPP@ferc.gov.</E>
                </P>
                <P>
                    Additional information about the amendment is available from the Commission's Office of External Affairs at (866) 208-FERC or on the FERC website (
                    <E T="03">www.ferc.gov</E>
                    ). Using the “eLibrary” link, select “General Search” from the eLibrary menu, enter the selected date range and “Docket Number” (
                    <E T="03">i.e.,</E>
                     CP23-501), and follow the instructions. For assistance with access to eLibrary, the helpline can be reached at (866) 208-3676, TTY (202) 502-8659, or at 
                    <E T="03">FERCOnlineSupport@ferc.gov.</E>
                     The eLibrary link on the FERC website also provides access to the texts of formal documents issued by the 
                    <PRTPAGE P="1914"/>
                    Commission, such as orders, notices, and rule makings.
                </P>
                <SIG>
                    <DATED>Dated: January 5, 2024.</DATED>
                    <NAME>Debbie-Anne A. Reese,</NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-00427 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <SUBJECT>Combined Notice of Filings #1</SUBJECT>
                <P>Take notice that the Commission received the following electric rate filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER20-1977-006.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Versant Power.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Joint Offer of Settlement Re: MPD 2023-2024 Charges (ER20-1977-) to be effective N/A.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     1/5/24.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20240105-5092.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 1/26/24.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER23-2212-002.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     New York Independent System Operator, Inc., Consolidated Edison Company of New York, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Consolidated Edison Company of New York, Inc. submits tariff filing per 35: Con Edison Compliance: Rate Schedule 19 Formula Rate Template to be effective 8/22/2023.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     1/4/24.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20240104-5161.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 1/25/24.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER24-89-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     PJM Interconnection, L.L.C.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: Response to Commission's 12/8/2023 Deficiency Letter in ER24-89-000 to be effective 9/13/2023.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     1/5/24.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20240105-5147.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 1/26/24.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER24-821-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Tri-State Generation and Transmission Association, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     205(d) Rate Filing: Initial Filing of Rate Schedule FERC No. 363 to be effective 12/6/2023.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     1/5/24.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20240105-5082.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 1/26/24.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER24-822-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Tri-State Generation and Transmission Association, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     205(d) Rate Filing: Amendment to Rate Schedule FERC No. 12 to be effective 3/5/2024.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     1/5/24.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20240105-5086.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 1/26/24.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER24-823-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Midcontinent Independent System Operator, Inc., ALLETE, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     205(d) Rate Filing: Midcontinent Independent System Operator, Inc. submits tariff filing per 35.13(a)(2)(iii: 2023-01-05_ALLETE-GRE Zonal Agreement Filing to be effective 1/1/2024.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     1/5/24.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20240105-5097.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 1/26/24.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER24-824-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: Camellia Solar (Camellia II) LGIA Filing to be effective 12/21/2023.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     1/5/24.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20240105-5099.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 1/26/24.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER24-825-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Midcontinent Independent System Operator, Inc., ALLETE, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     205(d) Rate Filing: Midcontinent Independent System Operator, Inc. submits tariff filing per 35.13(a)(2)(iii: 2024-01-05_SA 2905 ALLETE-GRE WDS to be effective 1/1/2024.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     1/5/24.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20240105-5105.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 1/26/24.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER24-826-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Public Service Company of Colorado.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: CSU Midway SISA &amp; FAC 736-NOC to be effective 1/6/2024.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     1/5/24.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20240105-5144.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 1/26/24.
                </P>
                <P>
                    The filings are accessible in the Commission's eLibrary system (
                    <E T="03">https://elibrary.ferc.gov/idmws/search/fercgensearch.asp</E>
                    ) by querying the docket number.
                </P>
                <P>Any person desiring to intervene, to protest, or to answer a complaint in any of the above proceedings must file in accordance with Rules 211, 214, or 206 of the Commission's Regulations (18 CFR 385.211, 385.214, or 385.206) on or before 5:00 p.m. Eastern time on the specified comment date. Protests may be considered, but intervention is necessary to become a party to the proceeding.</P>
                <P>
                    eFiling is encouraged. More detailed information relating to filing requirements, interventions, protests, service, and qualifying facilities filings can be found at: 
                    <E T="03">http://www.ferc.gov/docs-filing/efiling/filing-req.pdf.</E>
                     For other information, call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.
                </P>
                <P>
                    The Commission's Office of Public Participation (OPP) supports meaningful public engagement and participation in Commission proceedings. OPP can help members of the public, including landowners, environmental justice communities, Tribal members and others, access publicly available information and navigate Commission processes. For public inquiries and assistance with making filings such as interventions, comments, or requests for rehearing, the public is encouraged to contact OPP at (202) 502-6595 or 
                    <E T="03">OPP@ferc.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: January 5, 2024.</DATED>
                    <NAME>Debbie-Anne A. Reese,</NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-00418 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Project No. 1922-052]</DEPDOC>
                <SUBJECT>Ketchikan Public Utilities; Notice of Intent To Prepare an Environmental Assessment</SUBJECT>
                <P>On October 27, 2022, Ketchikan Public Utilities (KPU) filed an application for a new major license for the 7.1-megawatt Beaver Falls Hydroelectric Project (Beaver Falls Project; FERC No. 1922). The Beaver Falls Project is located on Beaver Falls Creek in Ketchikan Gateway Borough, Alaska. The project currently occupies 478.4 acres of United States lands administered by U.S. Forest Service.</P>
                <P>In accordance with the Commission's regulations, on October 10, 2023, 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 a draft and final Environmental Assessment (EA) on the application to relicense the Beaver Falls Project.</P>
                <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>
                    The Commission's Office of Public Participation (OPP) supports meaningful 
                    <PRTPAGE P="1915"/>
                    public engagement and participation in Commission proceedings. OPP can help members of the public, including landowners, environmental justice communities, Tribal members and others, access publicly available information and navigate Commission processes. For public inquiries and assistance with making filings such as interventions, comments, or requests for rehearing, the public is encouraged to contact OPP at (202) 502-6595 or 
                    <E T="03">OPP@ferc.gov.</E>
                </P>
                <P>
                    The application will be processed according to the following schedule. Revisions to the schedule may be made as appropriate.
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         The Council on Environmental Quality's (CEQ) regulations under 40 CFR 1501.10(b)(1) (2022) require that EAs be completed within 1 year of the Federal action agency's decision to prepare an EA. 
                        <E T="03">See</E>
                         National Environmental Policy Act, 42 U.S.C. 4321 
                        <E T="03">et seq., as amended by</E>
                         section 107(g)(1)(B)(iii) of the Fiscal Responsibility Act of 2023, Public Law 118-5, 4336a, 137 Stat. 42.
                    </P>
                </FTNT>
                <GPOTABLE COLS="2" OPTS="L2,tp0,p7,7/8,i1" CDEF="s25,xs64">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Milestone</CHED>
                        <CHED H="1">Target date</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Commission issues draft EA</ENT>
                        <ENT>June 2024.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Comments on draft EA due</ENT>
                        <ENT>July 2024.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Commission issues final EA</ENT>
                        <ENT>
                            December 2024.
                            <SU>1</SU>
                        </ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    Any questions regarding this notice may be directed to Golbahar Mirhosseini at 
                    <E T="03">Golbahar.Mirhosseini@ferc.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: January 5, 2024.</DATED>
                    <NAME>Debbie-Anne A. Reese,</NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-00421 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <DEPDOC>[FRL-11622-01-OW]</DEPDOC>
                <SUBJECT>National Drinking Water Advisory Council; Meeting</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of a public meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The U.S. Environmental Protection Agency's (EPA) Office of Ground Water and Drinking Water is announcing a meeting of the National Drinking Water Advisory Council (NDWAC or Council) as authorized under the Safe Drinking Water Act (SDWA). The primary purpose of the meeting is for EPA to consult with the NDWAC as required by the SDWA on a final National Primary Drinking Water Regulation: Lead and Copper Rule Improvements. Additional details will be provided in the meeting agenda, which will be posted on EPA's NDWAC website prior to the meeting. See the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section of this announcement for more information.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The meeting will be held on January 31, 2024, from 10:30 a.m. to 5:30 p.m., eastern time.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        This will be a virtual meeting. There will be no in-person gathering for this meeting. For more information about attending, providing oral statements, and accessibility for the meeting, as well as sending written comments, see the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section of this announcement.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Elizabeth Corr, NDWAC Designated Federal Officer, Office of Ground Water and Drinking Water (Mail Code 4601), U.S. Environmental Protection Agency, 1200 Pennsylvania Avenue NW, Washington, DC 20460; telephone number: (202) 564-3798; email address: 
                        <E T="03">corr.elizabeth@epa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Attending the Meeting:</E>
                     The meeting will be open to the general public. The meeting agenda and information on how to register for and attend the meeting online will be provided on EPA's website at: 
                    <E T="03">https://www.epa.gov/ndwac</E>
                     prior to the meeting.
                </P>
                <P>
                    <E T="03">Oral Statements:</E>
                     EPA will allocate one hour for the public to present oral comments during the meeting. Oral statements will be limited to three minutes per person during the public comment period. It is preferred that only one person present a statement on behalf of a group or organization. Persons interested in presenting an oral statement should send an email to 
                    <E T="03">NDWAC@epa.gov</E>
                     by noon, eastern time, on January 24, 2024.
                </P>
                <P>
                    <E T="03">Written Statements:</E>
                     Any person who wishes to file a written statement can do so before or after the Council meeting. Send written statements by email to 
                    <E T="03">NDWAC@epa.gov</E>
                     or see the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section if sending statements by mail. Written statements received by noon, eastern time, on January 24, 2024, will be distributed to all members of the Council prior to the meeting. Statements received after that time will become part of the permanent file for the meeting and will be forwarded to the Council members after conclusion of the meeting. Members of the public should be aware that their personal contact information, if included in any written comments, may be posted to the NDWAC website. Copyrighted material will not be posted without the explicit permission of the copyright holder.
                </P>
                <P>
                    <E T="03">Accessibility:</E>
                     For information on access or services for individuals with disabilities, or to request accommodations for a disability, please contact Elizabeth Corr by email at 
                    <E T="03">corr.elizabeth@epa.gov,</E>
                     or by phone at (202) 564-3798, preferably at least 10 days prior to the meeting to allow as much time as possible to process your request.
                </P>
                <P>
                    <E T="03">National Drinking Water Advisory Council:</E>
                     The NDWAC was created by Congress on December 16, 1974, as part of the Safe Drinking Water Act (SDWA) of 1974, Public Law 93-523, 42 U.S.C. 300j-5, and is operated in accordance with the provisions of the Federal Advisory Committee Act (FACA), 5 U.S.C. app. 2. The NDWAC was established to advise, consult with, and make recommendations to the EPA Administrator on matters relating to activities, functions, policies, and regulations under the SDWA. General information concerning the NDWAC is available at: 
                    <E T="03">https://www.epa.gov/ndwac.</E>
                </P>
                <SIG>
                    <NAME>Jennifer L. McLain,</NAME>
                    <TITLE>Director, Office of Ground Water and Drinking Water.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00413 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                <DEPDOC>[OMB 3060-XXXX, OMB 3060-0848; FR ID 195711]</DEPDOC>
                <SUBJECT>Information Collection Being Submitted for Review and Approval to Office of Management and Budget</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        As part of its continuing effort to reduce paperwork burdens, as required by the Paperwork Reduction Act (PRA) of 1995, the Federal Communications Commission (FCC or the Commission) invites the general public and other Federal Agencies to take this opportunity to comment on the following information collection. Pursuant to the Small Business Paperwork Relief Act of 2002, the FCC seeks specific comment on how it might “further reduce the information collection burden for small business concerns with fewer than 25 employees.” The Commission may not conduct or sponsor a collection of information unless it displays a currently valid Office of Management and Budget (OMB) control number. No person shall be subject to any penalty for failing to comply with a collection 
                        <PRTPAGE P="1916"/>
                        of information subject to the PRA that does not display a valid OMB control number.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments and recommendations for the proposed information collection should be submitted on or before February 12, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments should be sent to 
                        <E T="03">www.reginfo.gov/public/do/PRAMain.</E>
                         Find this particular information collection by selecting “Currently under 30-day Review—Open for Public Comments” or by using the search function. Your comment must be submitted into 
                        <E T="03">www.reginfo.gov</E>
                         per the above instructions for it to be considered. In addition to submitting in 
                        <E T="03">www.reginfo.gov</E>
                         also send a copy of your comment on the proposed information collection to Nicole Ongele, FCC, via email to 
                        <E T="03">PRA@fcc.gov</E>
                         and to 
                        <E T="03">Nicole.Ongele@fcc.gov.</E>
                         Include in the comments the OMB control number as shown in the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         below.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For additional information or copies of the information collection, contact Nicole Ongele at (202) 418-2991. To view a copy of this information collection request (ICR) submitted to OMB: (1) go to the web page 
                        <E T="03">https://www.reginfo.gov/public/do/PRAMain,</E>
                         (2) look for the section of the web page called “Currently Under Review,” (3) click on the downward-pointing arrow in the “Select Agency” box below the “Currently Under Review” heading, (4) select “Federal Communications Commission” from the list of agencies presented in the “Select Agency” box, (5) click the “Submit” button to the right of the “Select Agency” box, (6) when the list of FCC ICRs currently under review appears, look for the Title of this ICR and then click on the ICR Reference Number. A copy of the FCC submission to OMB will be displayed.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>As part of its continuing effort to reduce paperwork burdens, as required by the Paperwork Reduction Act (PRA) of 1995 (44 U.S.C. 3501-3520), the FCC invited the general public and other Federal Agencies to take this opportunity to comment on the following information collection. Comments are requested concerning: (a) Whether the proposed collection of information is necessary for the proper performance of the functions of the Commission, including whether the information shall have practical utility; (b) the accuracy of the Commission's burden estimates; (c) ways to enhance the quality, utility, and clarity of the information collected; and (d) ways to minimize the burden of the collection of information on the respondents, including the use of automated collection techniques or other forms of information technology. Pursuant to the Small Business Paperwork Relief Act of 2002, Public Law 107-198, see 44 U.S.C. 3506(c)(4), the FCC seeks specific comment on how it might “further reduce the information collection burden for small business concerns with fewer than 25 employees.”</P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     3060-XXXX.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Request For Religious Accommodation.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     FCC Form-5652.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     New Collection.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Individuals or households; Federal Government.
                </P>
                <P>
                    <E T="03">Number of Respondents and Responses:</E>
                     3 respondents; 3 responses.
                </P>
                <P>
                    <E T="03">Estimated Time per Response:</E>
                     2.5 hours.
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     One-time reporting requirement.
                </P>
                <P>
                    <E T="03">Obligation to Respond:</E>
                     Voluntary. Statutory authority for this information collection is contained Title VII of the Civil Rights Act of 1964, as amended, 29 U.S.C. Part 1605; U.S. Equal Employment Opportunity Commission's Compliance Manual, Section 12: Religious Discrimination (January 15, 2021); U.S. Equal Employment Opportunity Commission's Questions and Answers: Religious Discrimination in the Workplace (July 22, 2008); U.S. Office of Personnel Management's Fact Sheet: Adjustment of Work Schedules for Religious Observances.
                </P>
                <P>
                    <E T="03">Total Annual Burden:</E>
                     8 hours.
                </P>
                <P>
                    <E T="03">Total Annual Cost:</E>
                     $600.
                </P>
                <P>
                    <E T="03">Needs and Uses:</E>
                     In order to file a religious accommodation request, requesters must provide certain information to allow the FCC's Office of Workplace Diversity to determine that the employee or applicant satisfies the requirements of the Title VII of the Civil Rights Act of 1964 for filing a request. The information requested in the Religious Accommodation Form assists requesters to provide information to ascertain if the requesters sincerely held religious beliefs, observances or practices conflict with a specific task or requirement of the position or an application process. Specifically, the FCC Form 5652, the Religious Accommodation Request Form provides information regarding the type of accommodation or modification requested, the requesters sincerely held belief, and which FCC requirement, policy, or practice that conflicts with the requesters sincerely held religious observance, practice, or belief.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     3060-0848.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Deployment of Wireline Services Offering Advanced Telecommunications Capability, CC Docket No. 98-147.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     N/A.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of a currently approved collection.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit.
                </P>
                <P>
                    <E T="03">Number of Respondents and Responses:</E>
                     750 respondents; 9,270 responses.
                </P>
                <P>
                    <E T="03">Estimated Time per Response:</E>
                     3.54 hours (average burden per response).
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion reporting requirement, recordkeeping requirement and third-party disclosure requirement.
                </P>
                <P>
                    <E T="03">Obligation to Respond:</E>
                     Required to obtain or retain benefits. Statutory authority for this information collection is contained in Sections 201 and 251 of the Communications Act of 1934, as amended, 47 U.S.C. 201, 251.
                </P>
                <P>
                    <E T="03">Total Annual Burden:</E>
                     32,845 hours.
                </P>
                <P>
                    <E T="03">Total Annual Cost:</E>
                     No cost.
                </P>
                <P>
                    <E T="03">Needs and Uses:</E>
                     The information collection requirements implement sections 201 and 251 of the Communications Act of 1934, as amended, to provide for physical collocation on rates, terms and conditions that are just, reasonable and nondiscriminatory, and to promote deployment of advanced telecommunications services without significantly degrading the performance of other services. All of the requirements will be used by the Commission and competitive local exchange carriers (LECs) to facilitate the deployment of telecommunications services, including advanced telecommunications services.
                </P>
                <SIG>
                    <FP>Federal Communications Commission.</FP>
                    <NAME>Marlene Dortch,</NAME>
                    <TITLE>Secretary, Office of the Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00376 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                <DEPDOC>[OMB 3060-1046; FR ID 196008]</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 and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        As part of its continuing effort to reduce paperwork burdens, and as required by the Paperwork Reduction 
                        <PRTPAGE P="1917"/>
                        Act (PRA) of 1995, the Federal Communications Commission (FCC or the Commission) invites the general public and other Federal agencies to take this opportunity to comment on the following information collection. 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>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written PRA comments should be submitted on or before March 11, 2024. 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 contact listed below as soon as possible.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Direct all PRA comments to Nicole Ongele, FCC, via email 
                        <E T="03">PRA@fcc.gov</E>
                         and to 
                        <E T="03">nicole.ongele@fcc.gov</E>
                        .
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>For additional information about the information collection, contact Nicole Ongele, (202) 418-2991.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The FCC may not conduct or sponsor a collection of information unless it displays a currently valid 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 Office of Management and Budget (OMB) control number.</P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     3060-1046.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Part 64, Modernization of Payphone Compensation Rules, 
                    <E T="03">et al.,</E>
                     WC Docket No. 17-141, 
                    <E T="03">et al.</E>
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     N/A.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of a currently approved collection.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit.
                </P>
                <P>
                    <E T="03">Number of Respondents and Responses:</E>
                     216 respondents; 1,456 responses.
                </P>
                <P>
                    <E T="03">Estimated Time per Response:</E>
                     0.50-122 hours.
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion, one-time, and quarterly reporting requirements; third party disclosure requirements; and recordkeeping requirement.
                </P>
                <P>
                    <E T="03">Obligation to Respond:</E>
                     Required to obtain or retain benefits. Statutory authority for this information collection is contained in 47 U.S.C. 151, 154 and 276.
                </P>
                <P>
                    <E T="03">Total Annual Burden:</E>
                     22,524 hours.
                </P>
                <P>
                    <E T="03">Total Annual Cost:</E>
                     No cost.
                </P>
                <P>
                    <E T="03">Needs and Uses:</E>
                     Section 276 of the Communications Act, as amended (the Act), requires that the Federal Communications Commission (Commission or FCC) establish rules ensuring that payphone service providers or PSPs are “fairly compensated” for each and every completed payphone-originated call. The Commission's Payphone Compensation Rules satisfy section 276 by identifying the party liable for compensation and establishing a mechanism for PSPs to be paid. A 2003 Report and Order (FCC 03-235) established detailed rules (Payphone Compensation Rules) ensuring that payphone service providers or PSPs are “fairly compensated” for each and every completed payphone-originated call pursuant to section 276 of the Communications Act, as amended (the Act), which the Commission revised in a 2018 Report and Order (FCC 18-21). The Payphone Compensation Rules satisfy section 276 by identifying the party liable for compensation and establishing a mechanism for PSPs to be paid. The Payphone Compensation Rules: (1) place liability to compensate PSPs for payphone-originated calls on the facilities-based long distance carriers or switch-based resellers (SBRs) from whose switches such calls are completed; (2) define these responsible carriers as “Completing Carriers” and require them to develop their own system of tracking calls to completion; (3) require Completing Carriers to file with PSPs a quarterly report and also submit an attestation by a company official, including but not limited to the chief financial officer (CFO), that the payment amount for that quarter is accurate and is based on 100% of all completed calls; (4) require quarterly reporting obligations for other facilities-based long distance carriers in the call path, if any, and define these carriers as “Intermediate Carriers;” and (5) give parties flexibility to agree to alternative compensation arrangements (ACA) so that small Completing Carriers may avoid the expense of instituting a tracking system. The revisions adopted in the 2018 Report and Order significantly decreased the paperwork burden on carriers.
                </P>
                <SIG>
                    <FP>Federal Communications Commission.</FP>
                    <NAME>Marlene Dortch, </NAME>
                    <TITLE>Secretary, Office of the Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00379 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL DEPOSIT INSURANCE CORPORATION</AGENCY>
                <RIN>RIN 3064-ZA40</RIN>
                <SUBJECT>Notice of Inflation Adjustments for Civil Money Penalties</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Deposit Insurance Corporation.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of monetary penalties 2024.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Federal Deposit Insurance Corporation is providing notice of its maximum civil money penalties as adjusted for inflation.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The adjusted maximum amounts of civil money penalties in this notice are applicable to penalties assessed after January 15, 2024, for conduct occurring on or after November 2, 2015.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Graham N. Rehrig, Counsel, Legal Division, 703-314-3401, 
                        <E T="03">grehrig@fdic.gov;</E>
                         Federal Deposit Insurance Corporation, 550 17th Street NW, Washington, DC 20429.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    This notice announces changes to the maximum amount of each civil money penalty (CMP) within the Federal Deposit Insurance Corporation's (FDIC) jurisdiction to administer to account for inflation under the Federal Civil Penalties Inflation Adjustment Act of 1990 (1990 Adjustment Act),
                    <SU>1</SU>
                    <FTREF/>
                     as amended by the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015 (2015 Adjustment Act).
                    <SU>2</SU>
                    <FTREF/>
                     Under the 1990 Adjustment Act, as amended, federal agencies must make annual adjustments to the maximum amount of each CMP the agency administers. The Office of Management and Budget (OMB) is required to issue guidance to federal agencies no later than December 15 of each year providing an inflation-adjustment multiplier (
                    <E T="03">i.e.,</E>
                     the inflation-adjustment factor agencies must use) applicable to CMPs assessed in the following year.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Public Law 101-410, 104 Stat. 890, codified at 28 U.S.C. 2461 note.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Public Law 114-74, 701(b), 129 Stat. 599, codified at 28 U.S.C. 2461 note.
                    </P>
                </FTNT>
                <P>
                    Agencies are required to publish their CMPs, adjusted under the multiplier provided by the OMB, by January 15 of the applicable year. Agencies like the FDIC that have codified the statutory 
                    <PRTPAGE P="1918"/>
                    formula for making the CMP adjustments may make annual inflation adjustments by providing notice in the 
                    <E T="04">Federal Register</E>
                    .
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         Office of Mgmt. &amp; Budget, Exec. Office of the President, OMB Memorandum No. M-24-07, 
                        <E T="03">Implementation of Penalty Inflation Adjustments for 2024, Pursuant to the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015</E>
                         4 (Dec. 19, 2023), 
                        <E T="03">https://www.whitehouse.gov/wp-content/uploads/2023/12/M-24-07-Implementation-of-Penalty-Inflation-Adjustments-for-2024.pdf</E>
                         (OMB Guidance); 
                        <E T="03">see also</E>
                         12 CFR 308.132(d) (FDIC regulation that guides readers to the 
                        <E T="04">Federal Register</E>
                         to see the annual notice of CMP inflation adjustments).
                    </P>
                </FTNT>
                <P>
                    On December 19, 2023, the OMB issued guidance to affected agencies on implementing the required annual adjustment, which guidance included the relevant inflation multiplier.
                    <SU>4</SU>
                    <FTREF/>
                     The FDIC has applied that multiplier to the maximum CMPs allowable in 2023 for FDIC-supervised institutions and other parties subject to the FDIC's jurisdiction to calculate the maximum amount of CMPs that may be assessed by the FDIC in 2024.
                    <SU>5</SU>
                    <FTREF/>
                     There were no new statutory CMPs administered by the FDIC during 2023.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See</E>
                         OMB Guidance at 1 (providing an inflation multiplier of 1.03241).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         Penalties assessed for violations occurring prior to November 2, 2015, will be subject to the maximum amounts set forth in the FDIC's regulations in effect prior to the enactment of the 2015 Adjustment Act.
                    </P>
                </FTNT>
                <P>
                    The following charts
                    <FTREF/>
                     provide the inflation-adjusted maximum CMP amounts for use after January 15, 2024—the effective date of the 2024 annual adjustments—under 12 CFR part 308, for conduct occurring on or after November 2, 2015:
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         The maximum penalty amount is per day, unless otherwise indicated.
                    </P>
                    <P>
                        <SU>7</SU>
                         12 U.S.C. 1464(v) provides the maximum CMP amounts for the late filing of certain Call Reports. In 2012, however, the FDIC issued regulations that further subdivided these amounts based upon the size of the institution and the lateness of the filing. 
                        <E T="03">See</E>
                         77 FR 74573, 74576-78 (Dec. 17, 2012), codified at 12 CFR 308.132(e)(1). These adjusted subdivided amounts are found at the end of this chart.
                    </P>
                    <P>
                        <SU>8</SU>
                         The maximum penalty amount for an institution is the lesser of this amount or 1 percent of total assets.
                    </P>
                    <P>
                        <SU>9</SU>
                         12 U.S.C. 1817(a) provides the maximum CMP amounts for the late filing of certain Call Reports. In 1991, however, the FDIC issued regulations that further subdivided these amounts based upon the size of the institution and the lateness of the filing. 
                        <E T="03">See</E>
                         56 FR 37968, 37992-93 (Aug. 9, 1991), codified at 12 CFR 308.132(e)(1). These adjusted subdivided amounts are found at the end of this chart.
                    </P>
                    <P>
                        <SU>10</SU>
                         The maximum penalty amount for an institution is the lesser of this amount or 1 percent of total assets.
                    </P>
                    <P>
                        <SU>11</SU>
                         The maximum penalty amount for an institution is the lesser of this amount or 1 percent of total assets.
                    </P>
                    <P>
                        <SU>12</SU>
                         The maximum penalty amount for an institution is the lesser of this amount or 1 percent of total assets.
                    </P>
                    <P>
                        <SU>13</SU>
                         These amounts also apply to CMPs in statutes that cross-reference 12 U.S.C. 1818, such as 12 U.S.C. 2601, 2804(b), 3108(b), 3349(b), 4009(a), 4309(a), 4717(b); 15 U.S.C. 1607(a), 1681s(b), 1691(b), 1691c(a), 1693
                        <E T="03">o</E>
                        (a); and 42 U.S.C. 3601.
                    </P>
                    <P>
                        <SU>14</SU>
                         The maximum penalty amount for an institution is the lesser of this amount or 1 percent of total assets.
                    </P>
                    <P>
                        <SU>15</SU>
                         The $153-per-day maximum CMP under 12 U.S.C. 1828(h) for failure or refusal to pay any assessment applies only when the assessment is less than $10,000. When the amount of the assessment is $10,000 or more, the maximum CMP under section 1828(h) is 1 percent of the amount of the assessment for each day that the failure or refusal continues.
                    </P>
                    <P>
                        <SU>16</SU>
                         The maximum penalty amount for an institution is the lesser of this amount or 1 percent of total assets.
                    </P>
                </FTNT>
                <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s50,15,18">
                    <TTITLE>Maximum Civil Money Penalty Amounts</TTITLE>
                    <BOXHD>
                        <CHED H="1">U.S. Code citation</CHED>
                        <CHED H="1">
                            Current maximum CMP
                            <LI>(through January 14, 2024)</LI>
                        </CHED>
                        <CHED H="1">
                            Adjusted maximum CMP 
                            <SU>6</SU>
                            <LI>(beginning January 15, 2024)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="22">12 U.S.C. 1464(v):</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">
                            Tier One CMP 
                            <SU>7</SU>
                        </ENT>
                        <ENT>$4,745</ENT>
                        <ENT>$4,899</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Tier Two CMP</ENT>
                        <ENT>47,454</ENT>
                        <ENT>48,992</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">
                            Tier Three CMP 
                            <SU>8</SU>
                        </ENT>
                        <ENT>2,372,677</ENT>
                        <ENT>2,449,575</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12 U.S.C. 1467(d)</ENT>
                        <ENT>11,864</ENT>
                        <ENT>12,249</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">12 U.S.C. 1817(a):</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">
                            Tier One CMP 
                            <SU>9</SU>
                        </ENT>
                        <ENT>4,745</ENT>
                        <ENT>4,899</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Tier Two CMP</ENT>
                        <ENT>47,454</ENT>
                        <ENT>48,992</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">
                            Tier Three CMP 
                            <SU>10</SU>
                        </ENT>
                        <ENT>2,372,677</ENT>
                        <ENT>2,449,575</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">12 U.S.C. 1817(c):</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Tier One CMP</ENT>
                        <ENT>4,339</ENT>
                        <ENT>4,480</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Tier Two CMP</ENT>
                        <ENT>43,377</ENT>
                        <ENT>44,783</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">
                            Tier Three CMP 
                            <SU>11</SU>
                        </ENT>
                        <ENT>2,168,915</ENT>
                        <ENT>2,239,210</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">12 U.S.C. 1817(j)(16):</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Tier One CMP</ENT>
                        <ENT>11,864</ENT>
                        <ENT>12,249</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Tier Two CMP</ENT>
                        <ENT>59,316</ENT>
                        <ENT>61,238</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">
                            Tier Three CMP 
                            <SU>12</SU>
                        </ENT>
                        <ENT>2,372,677</ENT>
                        <ENT>2,449,575</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">
                            12 U.S.C. 1818(i)(2): 
                            <SU>13</SU>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Tier One CMP</ENT>
                        <ENT>11,864</ENT>
                        <ENT>12,249</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Tier Two CMP</ENT>
                        <ENT>59,316</ENT>
                        <ENT>61,238</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">
                            Tier Three CMP 
                            <SU>14</SU>
                        </ENT>
                        <ENT>2,372,677</ENT>
                        <ENT>2,449,575</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12 U.S.C. 1820(e)(4)</ENT>
                        <ENT>10,846</ENT>
                        <ENT>11,198</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12 U.S.C. 1820(k)(6)</ENT>
                        <ENT>390,271</ENT>
                        <ENT>402,920</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12 U.S.C. 1828(a)(3)</ENT>
                        <ENT>148</ENT>
                        <ENT>153</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">
                            12 U.S.C. 1828(h): 
                            <SU>15</SU>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">For assessments &lt;$10,000</ENT>
                        <ENT>148</ENT>
                        <ENT>153</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12 U.S.C. 1829b(j)</ENT>
                        <ENT>24,793</ENT>
                        <ENT>25,597</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12 U.S.C. 1832(c)</ENT>
                        <ENT>3,446</ENT>
                        <ENT>3,558</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12 U.S.C. 1884</ENT>
                        <ENT>345</ENT>
                        <ENT>356</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">12 U.S.C. 1972(2)(F):</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Tier One CMP</ENT>
                        <ENT>11,864</ENT>
                        <ENT>12,249</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Tier Two CMP</ENT>
                        <ENT>59,316</ENT>
                        <ENT>61,238</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">
                            Tier Three CMP 
                            <SU>16</SU>
                        </ENT>
                        <ENT>2,372,677</ENT>
                        <ENT>2,449,575</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12 U.S.C. 3909(d)</ENT>
                        <ENT>2,951</ENT>
                        <ENT>3,047</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">15 U.S.C. 78u-2:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Tier One CMP (individuals)</ENT>
                        <ENT>11,162</ENT>
                        <ENT>11,524</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="1919"/>
                        <ENT I="03">Tier One CMP (others)</ENT>
                        <ENT>111,614</ENT>
                        <ENT>115,231</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Tier Two CMP (individuals)</ENT>
                        <ENT>111,614</ENT>
                        <ENT>115,231</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Tier Two CMP (others)</ENT>
                        <ENT>558,071</ENT>
                        <ENT>576,158</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Tier Three CMP (individuals)</ENT>
                        <ENT>223,229</ENT>
                        <ENT>230,464</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Tier Three CMP (others)</ENT>
                        <ENT>1,116,140</ENT>
                        <ENT>1,152,314</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">15 U.S.C. 1639e(k):</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">First violation</ENT>
                        <ENT>13,627</ENT>
                        <ENT>14,069</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Subsequent violations</ENT>
                        <ENT>27,252</ENT>
                        <ENT>28,135</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">31 U.S.C. 3802</ENT>
                        <ENT>13,508</ENT>
                        <ENT>13,946</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">42 U.S.C. 4012a(f)</ENT>
                        <ENT>2,577</ENT>
                        <ENT>2,661</ENT>
                    </ROW>
                </GPOTABLE>
                <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s100,r50,r50">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">CFR citation</CHED>
                        <CHED H="1">
                            Current presumptive CMP
                            <LI>(through January 14, 2024)</LI>
                        </CHED>
                        <CHED H="1">
                            Adjusted presumptive CMP
                            <LI>(beginning January 15, 2024)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="22">12 CFR 308.132(e)(1)(i):</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Institutions with $25 million or more in assets.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">1 to 15 days late</ENT>
                        <ENT>$651</ENT>
                        <ENT>$672.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">16 or more days late</ENT>
                        <ENT>1,302</ENT>
                        <ENT>1,344.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Institutions with less than $25 million in assets.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">
                            1 to 15 days late 
                            <SU>17</SU>
                        </ENT>
                        <ENT>218</ENT>
                        <ENT>225.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">
                            16 or more days late 
                            <SU>18</SU>
                        </ENT>
                        <ENT>433</ENT>
                        <ENT>447.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">12 CFR 308.132(e)(1)(ii):</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Institutions with $25 million or more in assets.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">1 to 15 days late</ENT>
                        <ENT>1,084</ENT>
                        <ENT>1,119.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">16 or more days late</ENT>
                        <ENT>2,168</ENT>
                        <ENT>2,238.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Institutions with less than $25 million in assets.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">1 to 15 days late</ENT>
                        <ENT>1/50,000th of the institution's total assets</ENT>
                        <ENT>1/50,000th of the institution's total assets.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">16 or more days late</ENT>
                        <ENT>1/25,000th of the institution's total assets</ENT>
                        <ENT>1/25,000th of the institution's total assets.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12 CFR 308.132(e)(2)</ENT>
                        <ENT>47,454</ENT>
                        <ENT>48,992.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">12 CFR 308.132(e)(3):</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Tier One CMP</ENT>
                        <ENT>4,745</ENT>
                        <ENT>4,899.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Tier Two CMP</ENT>
                        <ENT>47,454</ENT>
                        <ENT>48,992.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">
                            Tier Three CMP 
                            <SU>19</SU>
                        </ENT>
                        <ENT>2,372,677</ENT>
                        <ENT>2,449,575.</ENT>
                    </ROW>
                </GPOTABLE>
                <SIG>
                    <FP>Federal Deposit Insurance Corporation.</FP>
                    <DATED>Dated at Washington, DC, on January 8, 2024.</DATED>
                    <NAME>James P. Sheesley,</NAME>
                    <TITLE>Assistant Executive Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00409 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6714-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL RESERVE SYSTEM</AGENCY>
                <SUBJECT>Formations of, Acquisitions by, and Mergers of Bank Holding Companies</SUBJECT>
                <P>
                    The companies
                    <FTREF/>
                     listed in this notice have applied to the Board for approval, pursuant to the Bank Holding Company Act of 1956 (12 U.S.C. 1841 
                    <E T="03">et seq.</E>
                    ) (BHC Act), Regulation Y (12 CFR part 225), and all other applicable statutes and regulations to become a bank holding company and/or to acquire the assets or the ownership of, control of, or the power to vote shares of a bank or bank holding company and all of the banks and nonbanking companies owned by the bank holding company, including the companies listed below.
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         The maximum penalty amount for an institution is the greater of this amount or 1/100,000th of the institution's total assets.
                    </P>
                    <P>
                        <SU>18</SU>
                         The maximum penalty amount for an institution is the greater of this amount or 1/50,000th of the institution's total assets.
                    </P>
                    <P>
                        <SU>19</SU>
                         The maximum penalty amount for an institution is the lesser of this amount or 1 percent of total assets.
                    </P>
                </FTNT>
                <P>
                    The public portions of the applications listed below, as well as other related filings required by the Board, if any, are available for immediate inspection at the Federal Reserve Bank(s) indicated below and at the offices of the Board of Governors. This information may also be obtained on an expedited basis, upon request, by contacting the appropriate Federal Reserve Bank and from the Board's Freedom of Information Office at 
                    <E T="03">https://www.federalreserve.gov/foia/request.htm.</E>
                     Interested persons may express their views in writing on the standards enumerated in the BHC Act (12 U.S.C. 1842(c)).
                </P>
                <P>Comments regarding each of these applications must be received at the Reserve Bank indicated or the offices of the Board of Governors, Ann E. Misback, Secretary of the Board, 20th Street and Constitution Avenue NW, Washington, DC 20551-0001, not later than February 12, 2024.</P>
                <P>
                    <E T="03">A. Federal Reserve Bank of Cleveland</E>
                     (Nadine M. Wallman, Vice President)  1455 East Sixth Street, Cleveland, Ohio 44114. Comments can also be sent electronically to 
                    <E T="03">comments.applications@clev.frb.org:</E>
                </P>
                <P>
                    1. 
                    <E T="03">KFB Holdings, Inc.,</E>
                     to become a bank holding company by acquiring Kentucky Farmers Bank Corporation, both of Ashland, Kentucky.
                </P>
                <P>
                    <E T="03">B. Federal Reserve Bank of Kansas City</E>
                     (Jeffrey Imgarten, Assistant Vice President) One Memorial Drive, Kansas City, Missouri 64198-0001. Comments can also be sent electronically to 
                    <E T="03">KCApplicationComments@kc.frb.org:</E>
                </P>
                <P>
                    1. 
                    <E T="03">Prairie Bell Holdings, Inc., Tulsa, Oklahoma;</E>
                     to become a bank holding company by acquiring Spiro Bancshares, Inc., and thereby indirectly acquiring Spiro State Bank, both of Spiro, Oklahoma.
                </P>
                <SIG>
                    <PRTPAGE P="1920"/>
                    <P>Board of Governors of the Federal Reserve System.</P>
                    <NAME>Michele Taylor Fennell,</NAME>
                    <TITLE>Deputy Associate Secretary of the Board.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-00480 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Centers for Medicare &amp; Medicaid Services</SUBAGY>
                <DEPDOC>[Document Identifier: CMS-10718]</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 February 12, 2024.</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>
                <P>
                    <E T="03">1. Type of Information Collection Request:</E>
                     Revision with change to the currently approved collection; 
                    <E T="03">Title of Information Collection:</E>
                     Model Medicare Advantage and Medicare Prescription Drug Plan Individual Enrollment Request Form; 
                    <E T="03">Use:</E>
                     The enrollment form is considered a “model” under Medicare regulations at §§ 422.2262 and 423.2262, for purposes of communication and marketing review and approval; therefore, MA and Part D plans are able to modify the language, content, format, or order of the enrollment form. The model enrollment form includes the minimal amount of information to process the enrollment, located in Section 1 of the MA/PDP enrollment form, and other limited information, in Section 2, that the sponsor is required (
                    <E T="03">i.e.,</E>
                     race and ethnicity data, accessible format preference) or chooses (
                    <E T="03">i.e.,</E>
                     premium payment information) to provide to the beneficiary.
                </P>
                <P>CMS expects MA and PDP organizations to ensure the enrollment form complies with CMS' instructions regarding content and format. New and current enrollees that utilize the enrollment form to elect an MA or Part D plan must acknowledge the requirement to: (1) maintain Medicare Part A and B to stay in MA, or Part A or B to stay in Part D; (2) reside in the plan's service area; (3) make a valid request during a valid election period; (4) follow plan rules; (5) consent to the disclosure and exchange of information between the plan and CMS; and (6) enroll in only one Medicare health plan and that enrollment in the MA or Part D plan automatically disenrolls them from any other Medicare health plan and prescription drug plan.</P>
                <P>
                    CMS will use this information to: track beneficiary enrollment, including tracking patterns in enrollment by race and ethnicity, sexual orientation, and gender identity over time; to identify, monitor, and develop effective and efficient strategies and incentives to reduce and eliminate health and health care inequities; to validate existing race and ethnicity imputation methods; and to ensure that clinically appropriate and equitable care (in terms of payment, access and quality) is consistently provided to all Medicare beneficiaries. 
                    <E T="03">Form Number:</E>
                     CMS-10718 (OMB control number: 0938-0832); 
                    <E T="03">Frequency:</E>
                     Occasionally; 
                    <E T="03">Affected Public:</E>
                     Individuals and Households, Private sector—(Business or other for-profits and Not-for-profit institutions); 
                    <E T="03">Number of Respondents:</E>
                     19,815,897; Total 
                    <E T="03">Annual Responses:</E>
                     39,632,597; 
                    <E T="03">Total Annual Hours:</E>
                     10,557,541. (For policy questions regarding this collection contact AnhViet Nguyen at 410-786-4548).
                </P>
                <SIG>
                    <DATED>Dated: January 8, 2024.</DATED>
                    <NAME>William N. Parham, III,</NAME>
                    <TITLE>Director, Division of Information Collections and Regulatory Impacts, Office of Strategic Operations and Regulatory Affairs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00474 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4120-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Administration for Children and Families</SUBAGY>
                <SUBJECT>Submission for OMB Review; Survey on Where Parents Look for and Find Information and How They Use Information When Selecting Child Care (New Collection)</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Planning, Research, and Evaluation, Administration for Children and Families, U.S. Department of Health and Human Services.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Request for public comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Administration for Children and Families (ACF) within the U.S. Department of Health and Human Services (HHS) is proposing to collect 
                        <PRTPAGE P="1921"/>
                        nationally representative survey data to learn more about where parents look for and find information about Child Care and Early Education (CCEE); how parents assess the people, places, or things that may offer CCEE information; what types of CCEE information parents look for; and how parents use information to make CCEE selections. The study aims to gather information that may be used by Child Care Lead Agencies to inform their consumer education efforts.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Comments due within 30 days of publication.</E>
                         OMB must make a decision about the collection of information between 30 and 60 days after publication of this document in the 
                        <E T="04">Federal Register</E>
                        . Therefore, a comment is best assured of having its full effect if OMB receives it within 30 days of publication.
                    </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. You can also obtain copies of the proposed collection of information by emailing 
                        <E T="03">OPREinfocollection@acf.hhs.gov.</E>
                         Identify all requests by the title of the information collection.
                    </P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Description:</E>
                     ACF has contracted with NORC to implement this study, which is part of the Consumer Education and Parental Choice in Early Care and Education (CEPC) project. The study will select a nationally representative sample from NORC's probability-based AmeriSpeak panel. The AmeriSpeak panel provides sample coverage of approximately 97 percent of the U.S. population. It currently contains 48,900 panel members age 13 and over residing in over 40,000 households. U.S. households are randomly selected with a known, non-zero probability from the NORC National Frame, and then recruited by mail, telephone, and by field interviewers face-to-face. NORC's in-person recruitment enhances representativeness for young adults, lower socio-economic households, non-internet households, and other households that are typically hard to reach for statistical surveys of the population.
                </P>
                <P>We will collect information about (a) where parents look for and find information about CCEE; (b) how parents assess the people, places, or things that may offer CCEE information; (c) how easy or hard it is for parents to find CCEE information, (d) the types of CCEE information that parents look for and say are helpful in choosing CCEE; (e) information about the last time parents made a decision about CCEE and what information they tried to learn about at that time; (f) parent's assessments of the CCEE options at the time they made their last CCEE decision; (g) how well parents' CCEE decision met their family's needs; and (h) demographic information about families.</P>
                <P>
                    <E T="03">Respondents:</E>
                     AmeriSpeak panelists who indicated that they have a young child in the household will be invited to complete the survey if they are at least 18 years of age. If a household has two or more panel members who reside in a household with a young child, one will be selected at random to complete the survey, with preference given to parents/legal guardians. Selected panelists will be asked questions to confirm eligibility for the survey, including that the household has at least one child under the age of 6 but not in kindergarten.
                </P>
                <P>
                    <E T="03">Annual Burden Estimates:</E>
                </P>
                <GPOTABLE COLS="5" OPTS="L2,tp0,i1" CDEF="s50,12,12,12,12">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Instrument</CHED>
                        <CHED H="1">
                            Number of
                            <LI>respondents</LI>
                            <LI>(total over</LI>
                            <LI>request</LI>
                            <LI>period)</LI>
                        </CHED>
                        <CHED H="1">
                            Number of
                            <LI>responses per</LI>
                            <LI>respondent</LI>
                            <LI>(total over</LI>
                            <LI>request</LI>
                            <LI>period)</LI>
                        </CHED>
                        <CHED H="1">
                            Average
                            <LI>burden per</LI>
                            <LI>response</LI>
                            <LI>(in hours)</LI>
                        </CHED>
                        <CHED H="1">
                            Total/annual
                            <LI>burden</LI>
                            <LI>(in hours)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Parent Survey Questionnaire (Section AE Only)</ENT>
                        <ENT>2,100</ENT>
                        <ENT>1</ENT>
                        <ENT>.08</ENT>
                        <ENT>168</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Parent Survey Questionnaire (Section A-DA)</ENT>
                        <ENT>1,500</ENT>
                        <ENT>1</ENT>
                        <ENT>.25</ENT>
                        <ENT>375</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     543.
                </P>
                <P>
                    <E T="03">Authority:</E>
                     Child Care and Development Block Grant (CCDBG) Act of 1990, as amended (42 U.S.C. 9857 
                    <E T="03">et seq.</E>
                    ).
                </P>
                <SIG>
                    <NAME>Mary B. Jones,</NAME>
                    <TITLE>ACF/OPRE Certifying Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00395 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4184-23-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. FDA-2023-N-3743]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Submission for Office of Management and Budget Review; Comment Request; Electronic Records; Electronic Signatures</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, the Agency, or we) is announcing that a proposed collection of information has been submitted to the Office of Management and Budget (OMB) for review and clearance under the Paperwork Reduction Act of 1995.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit written comments (including recommendations) on the collection of information by February 12, 2024.</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-0303. Also include the FDA docket number found in brackets in the heading of this document.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Domini Bean, Office of Operations, Food and Drug Administration, Three White Flint North, 10A-12M, 11601 Landsdown St., North Bethesda, MD 
                        <PRTPAGE P="1922"/>
                        20852, 301-796-5733, 
                        <E T="03">PRAStaff@fda.hhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>In compliance with 44 U.S.C. 3507, FDA has submitted the following proposed collection of information to OMB for review and clearance.</P>
                <HD SOURCE="HD1">Electronic Records; Electronic Signatures—21 CFR Part 11</HD>
                <HD SOURCE="HD2">OMB Control Number 0910-0303—Revision</HD>
                <P>This information collection supports implementation of statutory and regulatory authorities that govern criteria for the acceptance of electronic records, electronic signatures, and handwritten signatures executed to electronic records as equivalent to paper records. Agency regulations in part 11 (21 CFR part 11) provide for the submission of records and reports and establish that information may be submitted to FDA electronically provided that we have stated our ability to accept the records electronically in an Agency-established public docket and that the other requirements of part 11 are met. The regulations apply to records in electronic form that are created, modified, maintained, archived, retrieved, or transmitted, under any records requirements set forth in Agency regulations and to electronic records submitted under requirements of the Federal Food, Drug, and Cosmetic Act and the Public Health Service Act, even if such records are not specifically identified in Agency regulations.</P>
                <P>Regulations in part 11, subpart B (§§ 11.10 through 11.70) require the establishment of standard operating procedures to ensure appropriate use of and precautions for systems using electronic records and signatures, including the following: (1) § 11.10 specifies procedures and controls for persons who use closed systems to create, modify, maintain, or transmit electronic records; (2) § 11.30 specifies procedures and controls for persons who use open systems to create, modify, maintain, or transmit electronic records; and (3) § 11.50 specifies procedures and controls for persons who use electronic signatures.</P>
                <P>Regulations in subpart C (§§ 11.100 through 11.300) require specific controls to ensure the security and integrity of electronic signatures based upon use of identification codes in combination with passwords.</P>
                <P>
                    On March 2, 2023 (88 FR 13018) (Docket No. FDA-2019-N-0646), we revised the regulations. Before using an electronic signature in an electronic record required by FDA, a person must submit a letter of nonrepudiation to FDA (§  11.100(c)). Letters of nonrepudiation are required under §  11.100(c)(1) to certify that a person's electronic signatures are intended to be the legally binding equivalent of traditional handwritten signatures. The regulations were amended to update the address for submission of a certification in paper form and to provide an option for electronic submission. The regulations were also amended to communicate that information on where to submit the certification may be found on FDA's website, currently available at: 
                    <E T="03">https://www.fda.gov/industry/about-esg/appendix-g-letters-non-repudiation-agreement.</E>
                </P>
                <P>
                    In the 
                    <E T="04">Federal Register</E>
                     of September 19, 2023 (88 FR 64441), we published a 60-day notice requesting public comment on the proposed collection of information. No comments were received.
                </P>
                <P>We estimate the burden of this collection of information as follows:</P>
                <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s50,12C,12C,12C,12C,12C">
                    <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 respondent</LI>
                        </CHED>
                        <CHED H="1">Total annual responses</CHED>
                        <CHED H="1">
                            Average
                            <LI>burden per</LI>
                            <LI>response</LI>
                        </CHED>
                        <CHED H="1">Total hours</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">§ 11.100; submission of nonrepudiation letters</ENT>
                        <ENT>5,000</ENT>
                        <ENT>1</ENT>
                        <ENT>5,000</ENT>
                        <ENT>1</ENT>
                        <ENT>5,000</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>1</SU>
                         There are no capital costs or operating and maintenance costs associated with this collection of information.
                    </TNOTE>
                </GPOTABLE>
                <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s50,15,15,15,15,15">
                    <TTITLE>
                        Table 2—Estimated Annual Recordkeeping Burden 
                        <SU>1</SU>
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">21 CFR section</CHED>
                        <CHED H="1">
                            Number of
                            <LI>recordkeepers</LI>
                        </CHED>
                        <CHED H="1">
                            Number of
                            <LI>record per</LI>
                            <LI>recordkeepers</LI>
                        </CHED>
                        <CHED H="1">Total annual records</CHED>
                        <CHED H="1">
                            Average burden per
                            <LI>recordkeeping</LI>
                        </CHED>
                        <CHED H="1">Total hours</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">§ 11.10; controls for closed systems</ENT>
                        <ENT>2,500</ENT>
                        <ENT>1</ENT>
                        <ENT>2,500</ENT>
                        <ENT>20</ENT>
                        <ENT>50,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">§ 11.30; controls for open systems</ENT>
                        <ENT>2,500</ENT>
                        <ENT>1</ENT>
                        <ENT>2,500</ENT>
                        <ENT>20</ENT>
                        <ENT>50,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">§ 11.50; signature manifestations</ENT>
                        <ENT>5,000</ENT>
                        <ENT>1</ENT>
                        <ENT>5,000</ENT>
                        <ENT>20</ENT>
                        <ENT>100,000</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">§ 11.300; controls for identifications and passwords</ENT>
                        <ENT>5,000</ENT>
                        <ENT>1</ENT>
                        <ENT>5,000</ENT>
                        <ENT>20</ENT>
                        <ENT>100,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT>300,000</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>1</SU>
                         There are no capital costs or operating and maintenance costs associated with this collection of information.
                    </TNOTE>
                </GPOTABLE>
                <P>Based on a review of the information collection since our last request for OMB approval, we have increased our estimated burden. We assume 5,000 nonrepudiation letters will be submitted annually. We arrived at this figure by looking at the average number of nonrepudiation letters received through March 2023. We further assume that half of the estimated respondents will establish controls for open systems and half will establish controls for closed systems. Finally, we assume all respondents will establish controls for the remaining technical specifications required by the regulations.</P>
                <SIG>
                    <DATED>Dated: January 8, 2024.</DATED>
                    <NAME>Lauren K. Roth,</NAME>
                    <TITLE>Associate Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00406 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4164-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="1923"/>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. FDA-2017-D-5868]</DEPDOC>
                <SUBJECT>Requests for Reconsideration at the Division Level Under the Generic Drug User Fee Amendments; Draft Guidance for Industry; Availability; Agency Information Collection Activities; Proposed Collection; Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Food and Drug Administration (FDA, Agency, or we) is announcing the availability of a draft guidance for industry entitled “Requests for Reconsideration at the Division Level Under GDUFA.” This draft guidance provides recommendations on the procedures for applicants of abbreviated new drug applications (ANDAs) that wish to pursue a request for reconsideration within the review discipline at the division level or original signatory authority. This draft guidance revises the draft guidance of the same title issued in October 2017. This revision is being issued to reflect the most recent reauthorization of the Generic Drug User Fee Amendments (GDUFA) and to clarify what matters are appropriate for requests for reconsideration.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit either electronic or written comments on the draft guidance by March 11, 2024 to ensure that the Agency considers your comment on this draft guidance before it begins work on the final version of the guidance. Submit electronic or written comments on the proposed collection of information in the draft guidance by March 11, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments on any guidance at any time as follows:</P>
                </ADD>
                <HD SOURCE="HD2">Electronic Submissions</HD>
                <P>Submit electronic comments in the following way:</P>
                <P>
                    • 
                    <E T="03">Federal eRulemaking Portal: https://www.regulations.gov.</E>
                     Follow the instructions for submitting comments. Comments submitted electronically, including attachments, to 
                    <E T="03">https://www.regulations.gov</E>
                     will be posted to the docket unchanged. Because your comment will be made public, you are solely responsible for ensuring that your comment does not include any confidential information that you or a third party may not wish to be posted, such as medical information, your or anyone else's Social Security number, or confidential business information, such as a manufacturing process. Please note that if you include your name, contact information, or other information that identifies you in the body of your comments, that information will be posted on 
                    <E T="03">https://www.regulations.gov.</E>
                </P>
                <P>• If you want to submit a comment with confidential information that you do not wish to be made available to the public, submit the comment as a written/paper submission and in the manner detailed (see “Written/Paper Submissions” and “Instructions”).</P>
                <HD SOURCE="HD2">Written/Paper Submissions</HD>
                <P>Submit written/paper submissions as follows:</P>
                <P>
                    • 
                    <E T="03">Mail/Hand Delivery/Courier (for written/paper submissions):</E>
                     Dockets Management Staff (HFA-305), Food and Drug Administration, 5630 Fishers Lane, Rm. 1061, Rockville, MD 20852.
                </P>
                <P>• For written/paper comments submitted to the Dockets Management Staff, FDA will post your comment, as well as any attachments, except for information submitted, marked and identified, as confidential, if submitted as detailed in “Instructions.”</P>
                <P>
                    <E T="03">Instructions:</E>
                     All submissions received must include the Docket No. FDA-2017-D-5868 for “Requests for Reconsideration at the Division Level Under GDUFA.” Received comments will be placed in the docket and, except for those submitted as “Confidential Submissions,” publicly viewable at 
                    <E T="03">https://www.regulations.gov</E>
                     or at the Dockets Management Staff between 9 a.m. and 4 p.m., Monday through Friday, 240-402-7500.
                </P>
                <P>
                    • Confidential Submissions—To submit a comment with confidential information that you do not wish to be made publicly available, submit your comments only as a written/paper submission. You should submit two copies total. One copy will include the information you claim to be confidential with a heading or cover note that states “THIS DOCUMENT CONTAINS CONFIDENTIAL INFORMATION.” The Agency will review this copy, including the claimed confidential information, in its consideration of comments. The second copy, which will have the claimed confidential information redacted/blacked out, will be available for public viewing and posted on 
                    <E T="03">https://www.regulations.gov.</E>
                     Submit both copies to the Dockets Management Staff. If you do not wish your name and contact information to be made publicly available, you can provide this information on the cover sheet and not in the body of your comments and you must identify this information as “confidential.” Any information marked as “confidential” will not be disclosed except in accordance with 21 CFR 10.20 and other applicable disclosure law. For more information about FDA's posting of comments to public dockets, see 80 FR 56469, September 18, 2015, or access the information at: 
                    <E T="03">https://www.govinfo.gov/content/pkg/FR-2015-09-18/pdf/2015-23389.pdf.</E>
                </P>
                <P>
                    <E T="03">Docket:</E>
                     For access to the docket to read background documents or the electronic and written/paper comments received, go to 
                    <E T="03">https://www.regulations.gov</E>
                     and insert the docket number, found in brackets in the heading of this document, into the “Search” box and follow the prompts and/or go to the Dockets Management Staff, 5630 Fishers Lane, Rm. 1061, Rockville, MD 20852, 240-402-7500.
                </P>
                <P>You may submit comments on any guidance at any time (see 21 CFR 10.115(g)(5)).</P>
                <P>
                    Submit written requests for single copies of the draft guidance to the Division of Drug Information, Center for Drug Evaluation and Research, Food and Drug Administration, 10001 New Hampshire Ave., Hillandale Building, 4th Floor, Silver Spring, MD 20993-0002. Send one self-addressed adhesive label to assist that office in processing your requests. See the 
                    <E T="02">SUPPLEMENTARY INFORMATION</E>
                     section for electronic access to the draft guidance document.
                </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        <E T="03">With regard to the draft guidance:</E>
                         Martha Nguyen, Center for Drug Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 75, Rm. 1676, Silver Spring, MD 20903, 240-695-3412, 
                        <E T="03">Martha.Nguyen@fda.hhs.gov; With regard to the proposed collection of information:</E>
                         Duong T (Diane) Nhu, Office of Operations, Food and Drug Administration, Three White Flint North, 10A-12M, 11601 Landsdown St., North Bethesda, MD 20852, 240-402-3953, 
                        <E T="03">PRAStaff@fda.hhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    FDA is announcing the availability of a draft guidance for industry entitled “Requests for Reconsideration at the Division Level Under GDUFA.” This draft guidance provides recommendations on the procedures for applicants of ANDAs that wish to pursue a request for reconsideration within the review discipline at the division level or original signatory authority. Requests within the scope of this guidance document should concern certain actions that relate to an ANDA and have scientific significance.
                    <PRTPAGE P="1924"/>
                </P>
                <P>During the assessment of an ANDA, FDA considers important issues that are central to product evaluation. Sometimes, an applicant may disagree with FDA, and because these disagreements often involve intricate matters, it is critical to have procedures in place to ensure open and prompt consideration of an applicant's concern(s). The procedures and policies described in this guidance are intended to formalize FDA's current and historical practices and to continue to promote rapid and fair resolution of eligible requests between an applicant and FDA. This draft guidance revises the draft guidance of the same title issued on October 12, 2017 (82 FR 47531). This revision is being issued to reflect the most recent reauthorization of GDUFA in the Continuing Appropriations and Ukraine Supplemental Appropriations Act, 2023 (Division F, Title III, Pub. L. 117-180, 136 Stat. 2155), and to clarify what matters are appropriate for requests for reconsideration.</P>
                <P>This draft guidance is being issued consistent with FDA's good guidance practices regulation (21 CFR 10.115). The draft guidance, when finalized, will represent the current thinking of FDA on “Requests for Reconsideration at the Division Level Under GDUFA.” It does not establish any rights for any person and is not binding on FDA or the public. You can use an alternative approach if it satisfies the requirements of the applicable statutes and regulations.</P>
                <HD SOURCE="HD1">II. Paperwork Reduction Act of 1995</HD>
                <P>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. “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.</P>
                <P>
                    Section 3506(c)(2)(A) of the PRA (44 U.S.C. 3506(c)(2)(A)) requires Federal agencies to provide a 60-day notice in the 
                    <E T="04">Federal Register</E>
                     concerning each proposed collection of information before submitting the collection to OMB for approval. To comply with this requirement, FDA is publishing notice of the proposed collection of information set forth in this document.
                </P>
                <P>With respect to the following collection of information, FDA invites comments on these topics: (1) whether the proposed collection of information is necessary for the proper performance of FDA's functions, including whether the information will have practical utility; (2) the accuracy of FDA's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used; (3) ways to enhance the quality, utility, and clarity of the information to be collected; and (4) ways to minimize the burden of the collection of information on respondents, including through the use of automated collection techniques, when appropriate, and other forms of information technology.</P>
                <HD SOURCE="HD1">Applications for FDA Approval To Market a New Drug</HD>
                <HD SOURCE="HD2">OMB Control Number 0910-0001—Revision</HD>
                <P>The information collection request supports the Agency's draft guidance entitled, “Requests for Reconsideration at the Division Level Under GDUFA.” As discussed in section I of this notice, this draft guidance provides information to respondents regarding procedures for submitting requests for reconsideration, including details on the content and format of the submission. Respondents to the collection of information are applicants of ANDAs. Based on available data with regard to similar information collections, FDA's Center for Drug Evaluation and Research will receive approximately 310 requests for reconsideration annually from 155 respondents. Because we estimate it will take 5 hours to prepare a request for reconsideration, we estimate it will take an average of 1,550 total hours annually for respondents to prepare and submit requests for reconsideration.</P>
                <GPOTABLE COLS="6" OPTS="L2,nj,i1" CDEF="s50,12C,12C,12C,12C,12C">
                    <TTITLE>
                        Table 1—Estimated Annual Reporting Burden 
                        <SU>1</SU>
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">Section of guidance/reporting activity</CHED>
                        <CHED H="1">
                            Number of
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Number of
                            <LI>responses per respondent</LI>
                        </CHED>
                        <CHED H="1">Total annual responses</CHED>
                        <CHED H="1">
                            Average
                            <LI>burden per</LI>
                            <LI>response</LI>
                            <LI>(in hours)</LI>
                        </CHED>
                        <CHED H="1">Total hours</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Section IV: Procedures for Submitting and Responding to a Request for Reconsideration</ENT>
                        <ENT>155</ENT>
                        <ENT>2</ENT>
                        <ENT>310</ENT>
                        <ENT>5</ENT>
                        <ENT>1,550</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>This draft guidance refers to previously approved FDA collections of information found in FDA regulations. The collections of information in 21 CFR part 314 have been approved under OMB control number 0910-0001. The collections of information pertaining to the GDUFA III commitment letter, meetings related to generic drug development, and the Generic Drug User Fee Program have been approved under OMB control number 0910-0727.</P>
                <HD SOURCE="HD1">III. Electronic Access</HD>
                <P>
                    Persons with access to the internet may obtain the draft guidance at 
                    <E T="03">https://www.fda.gov/drugs/guidance-compliance-regulatory-information/guidances-drugs, https://www.fda.gov/regulatory-information/search-fda-guidance-documents,</E>
                     or 
                    <E T="03">https://www.regulations.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: January 8, 2024.</DATED>
                    <NAME>Lauren K. Roth,</NAME>
                    <TITLE>Associate Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00403 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4164-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. FDA-2020-N-0026]</DEPDOC>
                <SUBJECT>Issuance of Priority Review Voucher; Rare Pediatric Disease Product</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 the issuance of a priority review voucher to the sponsor of a rare pediatric disease product application. The Federal Food, Drug, and Cosmetic Act (FD&amp;C Act) 
                        <PRTPAGE P="1925"/>
                        authorizes FDA to award priority review vouchers to sponsors of approved rare pediatric disease product applications that meet certain criteria. FDA is required to publish notice of the award of the priority review voucher. FDA has determined that FILSUVEZ (birch triterpenes), manufactured by Amryt Pharmaceuticals, meets the criteria for a priority review voucher.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Cathryn Lee, Center for Drug Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Silver Spring, MD 20993-0002, 301-796-1394.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>FDA is announcing the issuance of a priority review voucher to the sponsor of an approved rare pediatric disease product application. Under section 529 of the FD&amp;C Act (21 U.S.C. 360ff), FDA will award priority review vouchers to sponsors of approved rare pediatric disease product applications that meet certain criteria. FDA has determined that FILSUVEZ (birch triterpenes), manufactured by Amryt Pharmaceuticals, meets the criteria for a priority review voucher. FILSUVEZ (birch triterpenes) gel is indicated for the treatment of wounds associated with dystrophic and junctional epidermolysis bullosa in adult and pediatric patients 6 months of age and older.</P>
                <P>
                    For further information about the Rare Pediatric Disease Priority Review Voucher Program and for a link to the full text of section 529 of the FD&amp;C Act, go to 
                    <E T="03">http://www.fda.gov/ForIndustry/DevelopingProductsforRareDiseasesConditions/RarePediatricDiseasePriorityVoucherProgram/default.htm.</E>
                     For further information about FILSUVEZ (birch triterpenes), go to the “Drugs@FDA” website at 
                    <E T="03">http://www.accessdata.fda.gov/scripts/cder/daf/.</E>
                </P>
                <SIG>
                    <DATED>Dated: January 8, 2024.</DATED>
                    <NAME>Lauren K. Roth,</NAME>
                    <TITLE>Associate Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00400 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4164-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. FDA-2020-N-0026]</DEPDOC>
                <SUBJECT>Issuance of Priority Review Voucher; Rare Pediatric Disease Product</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 the issuance of a priority review voucher to the sponsor of a rare pediatric disease product application. The Federal Food, Drug, and Cosmetic Act (FD&amp;C Act) authorizes FDA to award priority review vouchers to sponsors of approved rare pediatric disease product applications that meet certain criteria. FDA is required to publish notice of the award of the priority review voucher. FDA has determined that ADZYNMA (ADAMTS13, recombinant-krhn), manufactured by Takeda Pharmaceuticals U.S.A., Inc., meets the criteria for a priority review voucher.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Myrna Hanna, Center for Biologics Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 71, Rm. 7301, Silver Spring, MD 20993-0002, 240-402-7911.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>FDA is announcing the issuance of a priority review voucher to the sponsor of an approved rare pediatric disease product application. Under section 529 of the FD&amp;C Act (21 U.S.C. 360ff), FDA will award priority review vouchers to sponsors of approved rare pediatric disease product applications that meet certain criteria. FDA has determined that ADZYNMA (ADAMTS13, recombinant-krhn), manufactured by Takeda Pharmaceuticals U.S.A., Inc., meets the criteria for a priority review voucher.</P>
                <P>ADZYNMA (ADAMTS13, recombinant-krhn) is indicated for prophylactic or on-demand enzyme replacement therapy in adult and pediatric patients with congenital thrombotic thrombocytopenic purpura.</P>
                <P>
                    For further information about the Rare Pediatric Disease Priority Review Voucher Program and for a link to the full text of section 529 of the FD&amp;C Act, go to 
                    <E T="03">https://www.fda.gov/industry/developing-products-rare-diseases-conditions/rare-pediatric-disease-rpd-designation-and-voucher-programs.</E>
                     For further information about ADZYNMA (ADAMTS13, recombinant-krhn), go to the Center for Biologics Evaluation and Research's Approved Blood Products website at 
                    <E T="03">https://www.fda.gov/vaccines-blood-biologics/adzynma.</E>
                </P>
                <SIG>
                    <DATED>Dated: January 8, 2024.</DATED>
                    <NAME>Lauren K. Roth,</NAME>
                    <TITLE>Associate Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00401 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4164-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. FDA-2022-D-2512]</DEPDOC>
                <SUBJECT>Q5A(R2) Viral Safety Evaluation of Biotechnology Products Derived From Cell Lines of Human or Animal Origin; International Council for Harmonisation; Guidance for Industry; Availability</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Food and Drug Administration (FDA or Agency) is announcing the availability of a final guidance for industry entitled “Q5A(R2) Viral Safety Evaluation of Biotechnology Products Derived from Cell Lines of Human or Animal Origin.” The guidance was prepared under the auspices of the International Council for Harmonisation of Technical Requirements for Pharmaceuticals for Human Use (ICH). The guidance is intended to describe risk-based principles and mitigation strategies to assure the viral safety of biotechnology products, including the data necessary to submit in a marketing application. The guidance also finalizes the updates based on advances in scientific knowledge and regulatory expectations to the first version of the ICH guidance for industry “Q5A Viral Safety Evaluation of Biotechnology Products Derived from Cell Lines of Human or Animal Origin,” issued in September 1998. Lastly, the guidance replaces the draft guidance “Q5A(R2) Viral Safety Evaluation of Biotechnology Products Derived from Cell Lines of Human or Animal Origin” issued on November 14, 2022.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        The announcement of the guidance is published in the 
                        <E T="04">Federal Register</E>
                         on January 11, 2024.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit either electronic or written comments on Agency guidances at any time as follows:</P>
                </ADD>
                <HD SOURCE="HD2">Electronic Submissions</HD>
                <P>Submit electronic comments in the following way:</P>
                <P>
                    • 
                    <E T="03">Federal eRulemaking Portal:</E>
                      
                    <E T="03">https://www.regulations.gov.</E>
                     Follow the instructions for submitting comments. Comments submitted electronically, including attachments, to 
                    <E T="03">https://www.regulations.gov</E>
                     will be posted to the docket unchanged. Because your comment will be made public, you are solely responsible for ensuring that your comment does not include any 
                    <PRTPAGE P="1926"/>
                    confidential information that you or a third party may not wish to be posted, such as medical information, your or anyone else's Social Security number, or confidential business information, such as a manufacturing process. Please note that if you include your name, contact information, or other information that identifies you in the body of your comments, that information will be posted on 
                    <E T="03">https://www.regulations.gov.</E>
                </P>
                <P>• If you want to submit a comment with confidential information that you do not wish to be made available to the public, submit the comment as a written/paper submission and in the manner detailed (see “Written/Paper Submissions” and “Instructions”).</P>
                <HD SOURCE="HD2">Written/Paper Submissions</HD>
                <P>Submit written/paper submissions as follows:</P>
                <P>
                    • 
                    <E T="03">Mail/Hand Delivery/Courier (for written/paper submissions):</E>
                     Dockets Management Staff (HFA-305), Food and Drug Administration, 5630 Fishers Lane, Rm. 1061, Rockville, MD 20852.
                </P>
                <P>• For written/paper comments submitted to the Dockets Management Staff, FDA will post your comment, as well as any attachments, except for information submitted, marked and identified, as confidential, if submitted as detailed in “Instructions.”</P>
                <P>
                    <E T="03">Instructions:</E>
                     All submissions received must include the Docket No. FDA-2022-D-2512 for “Q5A(R2) Viral Safety Evaluation of Biotechnology Products Derived from Cell Lines of Human or Animal Origin.” Received comments will be placed in the docket and, except for those submitted as “Confidential Submissions,” publicly viewable at 
                    <E T="03">https://www.regulations.gov</E>
                     or at the Dockets Management Staff between 9 a.m. and 4 p.m., Monday through Friday, 240-402-7500.
                </P>
                <P>
                    • Confidential Submissions—To submit a comment with confidential information that you do not wish to be made publicly available, submit your comments only as a written/paper submission. You should submit two copies total. One copy will include the information you claim to be confidential with a heading or cover note that states “THIS DOCUMENT CONTAINS CONFIDENTIAL INFORMATION.” The Agency will review this copy, including the claimed confidential information, in its consideration of comments. The second copy, which will have the claimed confidential information redacted/blacked out, will be available for public viewing and posted on 
                    <E T="03">https://www.regulations.gov.</E>
                     Submit both copies to the Dockets Management Staff. If you do not wish your name and contact information to be made publicly available, you can provide this information on the cover sheet and not in the body of your comments and you must identify this information as “confidential.” Any information marked as “confidential” will not be disclosed except in accordance with 21 CFR 10.20 and other applicable disclosure law. For more information about FDA's posting of comments to public dockets, see 80 FR 56469, September 18, 2015, or access the information at: 
                    <E T="03">https://www.govinfo.gov/content/pkg/FR-2015-09-18/pdf/2015-23389.pdf.</E>
                </P>
                <P>
                    <E T="03">Docket:</E>
                     For access to the docket to read background documents or the electronic and written/paper comments received, go to 
                    <E T="03">https://www.regulations.gov</E>
                     and insert the docket number, found in brackets in the heading of this document, into the “Search” box and follow the prompts and/or go to the Dockets Management Staff, 5630 Fishers Lane, Rm. 1061, Rockville, MD 20852, 240-402-7500.
                </P>
                <P>You may submit comments on any guidance at any time (see 21 CFR 10.115(g)(5)).</P>
                <P>
                    Submit written requests for single copies of this guidance to the Division of Drug Information, Center for Drug Evaluation and Research, Food and Drug Administration, 10001 New Hampshire Ave., Hillandale Building, 4th Floor, Silver Spring, MD 20993-0002, or the Office of Communication, Outreach and Development, Center for Biologics Evaluation and Research (CBER), Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 71, Rm. 3128, Silver Spring, MD 20993-0002. Send one self-addressed adhesive label to assist that office in processing your requests. The guidance may also be obtained by mail by calling CBER at 1-800-835-4709 or 240-402-8010. See the 
                    <E T="02">SUPPLEMENTARY INFORMATION</E>
                     section for electronic access to the guidance document.
                </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        <E T="03">Regarding the guidance:</E>
                         Kathryn King, Center for Drug Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 51, Silver Spring, MD 20993-0002, 240-402-9634, 
                        <E T="03">kathryn.kingk@fda.hhs.gov;</E>
                         or James Myers, Center for Biologics Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 71, Rm. 7301, Silver Spring, MD 20993-0002, 240-402-7911.
                    </P>
                    <P>
                        <E T="03">Regarding the ICH:</E>
                         Jill Adleberg, Center for Drug Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 51, Rm. 6364, Silver Spring, MD 20993-0002, 301-796-5259, 
                        <E T="03">Jill.Adleberg@fda.hhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>FDA is announcing the availability of a guidance for industry entitled “Q5A(R2) Viral Safety Evaluation of Biotechnology Products Derived from Cell Lines of Human or Animal Origin.” The guidance was prepared under the auspices of ICH. ICH seeks to achieve greater regulatory harmonization worldwide to ensure that safe, effective, high-quality medicines are developed, registered, and maintained in the most resource-efficient manner.</P>
                <P>By harmonizing the regulatory requirements in regions around the world, ICH guidelines enhance global drug development, improve manufacturing standards, and increase the availability of medications. For example, ICH guidelines have substantially reduced duplicative clinical studies, prevented unnecessary animal studies, standardized the reporting of important safety information, and standardized marketing application submissions.</P>
                <P>
                    The six Founding Members of the ICH are FDA; the Pharmaceutical Research and Manufacturers of America; the European Commission; the European Federation of Pharmaceutical Industries Associations; the Japanese Ministry of Health, Labour, and Welfare; and the Japanese Pharmaceutical Manufacturers Association. The Standing Members of the ICH Association include Health Canada and Swissmedic. ICH membership continues to expand to include other regulatory authorities and industry associations from around the world (refer to 
                    <E T="03">https://www.ich.org/</E>
                    ).
                </P>
                <P>ICH works by engaging global regulatory and industry experts in a detailed, science-based, and consensus-driven process that results in the development of ICH guidelines. The regulators around the world are committed to consistently adopting these consensus-based guidelines, realizing the benefits for patients and for industry.</P>
                <P>As a Founding Regulatory Member of ICH, FDA plays a major role in the development of each of the ICH guidelines, which FDA then adopts and issues as guidance for industry. FDA's guidance documents do not establish legally enforceable responsibilities. Instead, they describe the Agency's current thinking on a topic and should be viewed only as recommendations, unless specific regulatory or statutory requirements are cited.</P>
                <P>
                    In the 
                    <E T="04">Federal Register</E>
                     of November 14, 2022 (87 FR 68176), FDA published 
                    <PRTPAGE P="1927"/>
                    a notice announcing the availability of a draft guidance entitled “Q5A(R2) Viral Safety Evaluation of Biotechnology Products Derived from Cell Lines of Human or Animal Origin.” The notice gave interested persons an opportunity to submit comments by January 13, 2023. After consideration of the comments received and revisions to the guideline, a final draft of the guideline was submitted to the ICH Assembly and endorsed by the regulatory agencies in November 2023.
                </P>
                <P>
                    This guidance revises and finalizes the updates included in the draft guidance issued on November 14, 2022. Like the draft guidance, the final guidance reflects updates in scientific advances and regulatory expectations since the publication of the ICH guidance for industry, “Q5A Viral Safety Evaluation of Biotechnology Products Derived from Cell Lines of Human or Animal Origin,” issued in September 1998. These revisions include descriptions of new classes of products now in scope, inclusion of new virus detection technologies, clarification of new validation strategies, and considerations specific to new manufacturing approaches, such as continuous manufacturing. The final guidance expands on the draft by including additional detail on the strategy for replacement of conventional testing methods with alternatives and additional details to better describe the scope of products addressed in the guidance. Additional definitions were added to the glossary to better align with terminology elsewhere in the guidance as well as guidances that may be read in parallel (
                    <E T="03">e.g.,</E>
                     ICH guidance for industry “Q13 Continuous Manufacturing of Drug Substances and Drug Products,” available at 
                    <E T="03">https://www.fda.gov/media/165775/download</E>
                    ).
                </P>
                <P>This guidance is being issued consistent with FDA's good guidance practices regulation (21 CFR 10.115). The guidance represents the current thinking of FDA on “Q5A(R2) Viral Safety Evaluation of Biotechnology Products Derived from Cell Lines of Human or Animal Origin.” It does not establish any rights for any person and is not binding on FDA or the public. You can use an alternative approach if it satisfies the requirements of the applicable statutes and regulations.</P>
                <HD SOURCE="HD1">II. Paperwork Reduction Act of 1995</HD>
                <P>While this guidance contains no collection of information, it does refer to previously approved FDA collections of information. The previously approved collections of information are subject to review by the Office of Management and Budget (OMB) under the Paperwork Reduction Act of 1995 (PRA) (44 U.S.C. 3501-3521). The collections of information in 21 CFR parts 210 and 211 pertaining to current good manufacturing practice have been approved under OMB control number 0910-0139. The collections of information in 21 CFR part 312 for the submissions of investigational new drug applications have been approved under OMB control number 0910-0014. The collections of information in 21 CFR part 601 for the submissions of biologics license applications have been approved under OMB control number 0910-0338. The collections of information 21 CFR part 58 pertaining to good laboratory practices for nonclinical laboratory studies have been approved under OMB control number 0910-0119.</P>
                <HD SOURCE="HD1">III. Electronic Access</HD>
                <P>
                    Persons with access to the internet may obtain the guidance at 
                    <E T="03">https://www.regulations.gov, https://www.fda.gov/drugs/guidance-compliance-regulatory-information/guidances-drugs,</E>
                      
                    <E T="03">https://www.fda.gov/vaccines-blood-biologics/guidance-compliance-regulatory-information-biologics/biologics-guidances,</E>
                     or 
                    <E T="03">https://www.fda.gov/regulatory-information/search-fda-guidance-documents.</E>
                </P>
                <SIG>
                    <DATED>Dated: January 8, 2024.</DATED>
                    <NAME>Lauren K. Roth,</NAME>
                    <TITLE>Associate Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00407 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4164-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>National Heart, Lung, and Blood Institute; Notice of Meeting</SUBJECT>
                <P>Pursuant to section 1009 of the Federal Advisory Committee Act, as amended, notice is hereby given of a meeting of the National Heart, Lung, and Blood Advisory Council.</P>
                <P>
                    The meeting will be held virtually and is open to the public as indicated below. Individuals who plan to attend the virtual meeting and need special assistance, such as sign language interpretation or other reasonable accommodations, should notify the Contact Person listed below in advance of the meeting. The meeting can be accessed from the NIH Videocast at the following links: 
                    <E T="03">http://videocast.nih.gov/</E>
                     or 
                    <E T="03">https://www.nhlbi.nih.gov/about/advisory-and-peer-review-committees/advisory-council.</E>
                </P>
                <P>The meeting will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), title 5 U.S.C., as amended. The 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>
                         National Heart, Lung, and Blood Advisory Council.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         February 6, 2024.
                    </P>
                    <P>
                        <E T="03">Closed:</E>
                         10:00 a.m. to 11:00 a.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, Rockledge I, 6705 Rockledge Drive, Rockville, MD 20892 (Virtual Meeting).
                    </P>
                    <P>
                        <E T="03">Open:</E>
                         11:00 a.m. to 2:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To discuss program policies and issues.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, Rockledge I, 6705 Rockledge Dr., Bethesda, MD 20892 (Virtual Meeting).
                    </P>
                    <P>
                        <E T="03">Virtual Access: https://www.nhlbi.nih.gov/about/advisory-and-peer-review-committees/advisory-council.</E>
                    </P>
                    <P>Please note, the link to the videocast meeting will be posted within a week of the meeting date.</P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Valerie L. Prenger, Ph.D., MPH, Deputy Director, Division of Extramural Research Activities, National Heart, Lung, and Blood Institute, National Institutes of Health, 6705 Rockledge Drive, Room 207-C, Bethesda, MD 20892-7924, 301-435-0270, 
                        <E T="03">Valerie.Prenger@nih.gov.</E>
                    </P>
                    <P>Any member of the public interested in presenting oral comments to the committee may notify the Contact Person listed on this notice at least 10 days in advance of the meeting. Interested individuals and representatives of organizations may submit a letter of intent, a brief description of the organization represented, and a short description of the oral presentation. Only one representative of an organization may be allowed to present oral comments and if accepted by the committee, presentations may be limited to five minutes. Both printed and electronic copies are requested for the record. In addition, any interested person may file written comments with the committee by forwarding their statement to the Contact Person listed on this notice. The statement should include the name, address, telephone number and when applicable, the business or professional affiliation of the interested person.</P>
                    <P>
                        In the interest of security, NIH has procedures at 
                        <E T="03">https://www.nih.gov/about-nih/visitor-information/campus-access-security</E>
                         for entrance into on-campus and off-campus facilities. All visitor vehicles, including taxicabs, hotel, and airport shuttles will be inspected before being allowed on campus. Visitors attending a meeting on campus or at an off-campus federal facility will be asked to show one form of identification (for example, a government-issued photo ID, driver's license, or passport) and to state the purpose of their visit.
                        <PRTPAGE P="1928"/>
                    </P>
                    <P>
                        Information is also available on the Institute's/Center's home page: 
                        <E T="03">www.nhlbi.nih.gov/meetings/nhlbac/index.htm,</E>
                         where an agenda and any additional information for the meeting will be posted when available.
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.233, National Center for Sleep Disorders Research; 93.837, Heart and Vascular Diseases Research; 93.838, Lung Diseases Research; 93.839, Blood Diseases and Resources Research, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: January 8, 2024.</DATED>
                    <NAME>Melanie J. Pantoja,</NAME>
                    <TITLE>Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-00440 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>Eunice Kennedy Shriver National Institute of Child Health and Human Development; 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 meeting.</P>
                <P>The meeting will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The 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>
                         Eunice Kennedy Shriver, National Institute of Child Health and Human Development, Initial Review Group, Population Sciences Study Section.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         March 1, 2024.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10:00 a.m. to 4:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, Eunice Kennedy Shriver, National Institute of Child Health and Human Development, 6710B Rockledge Drive, Bethesda, MD 20817 (Virtual Meeting).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Christiane M. Robbins, Scientific Review Officer, Scientific Review Branch (SRB), DER, Eunice Kennedy Shriver, National Institute of Child Health and Human Development, NIH, DHHS, 6710B Rockledge Drive, Rm. 2121B, Bethesda, MD 20817, 301-451-4989, 
                        <E T="03">crobbins@mail.nih.gov.</E>
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.864, Population Research; 93.865, Research for Mothers and Children; 93.929, Center for Medical Rehabilitation Research; 93.209, Contraception and Infertility Loan Repayment Program, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: January 5, 2024. </DATED>
                    <NAME>Lauren A. Fleck, </NAME>
                    <TITLE>Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-00369 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>Eunice Kennedy Shriver National Institute of Child Health and Human Development; 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 meeting.</P>
                <P>The meeting will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The 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>
                         Eunice Kennedy Shriver National Institute of Child Health and Human Development Special Emphasis Panel; Member Conflict: Biobehavioral and Behavioral Sciences Study Section.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         March 12, 2024.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10:00 a.m. to 12:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, Eunice Kennedy Shriver National Institute of Child Health and Human Development, 6710B Rockledge Drive, Bethesda, MD 20817, (Virtual Meeting).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Magnus A. Azuine, Ph.D., Scientific Review Branch Eunice Kennedy Shriver National Institute, of Child Health &amp; Human Development, NIH 6710B Rockledge Drive, Room 2125C Bethesda, MD 20817, (301) 480-4645, 
                        <E T="03">magnus.azuine@nih.gov.</E>
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.864, Population Research; 93.865, Research for Mothers and Children; 93.929, Center for Medical Rehabilitation Research; 93.209, Contraception and Infertility Loan Repayment Program, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: January 8, 2024. </DATED>
                    <NAME>Lauren A. Fleck, </NAME>
                    <TITLE>Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-00442 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>National Institute of Neurological Disorders and Stroke; Notice of Closed Meeting</SUBJECT>
                <P>Pursuant to section 1009 of the Federal Advisory Committee Act, as amended, notice is hereby given of the following meeting.</P>
                <P>The meeting will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The 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>
                         Neurological Sciences Training Initial Review Group; Neurological Sciences Training 3 Study Section.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         February 5-6, 2024.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         7: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">Place:</E>
                         New Orleans Marriott, 555 Canal Street, New Orleans, LA 70130.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Lataisia Cherie Jones, Ph.D., Scientific Review Officer, Scientific Review Branch, Division of Extramural Activities, NINDS/NIH, 6001 Executive Blvd., Rockville, MD 20852, 301-496-9223, 
                        <E T="03">lataisia.jones@nih.gov</E>
                        .
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.853, Clinical Research Related to Neurological Disorders; 93.854, Biological Basis Research in the Neurosciences, National Institutes of Health, HHS.)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: January 5, 2024.</DATED>
                    <NAME>Lauren A. Fleck, </NAME>
                    <TITLE>Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-00370 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="1929"/>
                <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; RFA-OD-23-017: Tobacco Regulatory Science B.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         February 6, 2024.
                    </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">Place:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892 (Virtual Meeting).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Annie Laurie McRee, DRPH, Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 100, Bethesda, MD 20892, (301) 827-7396, 
                        <E T="03">mcreeal@csr.nih.gov</E>
                        .
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Collaborative Applications: Pathophysiology in Mental Illness.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         February 6, 2024.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         5:00 p.m. to 8:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892 (Virtual Meeting).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Brittany L. Mason-Mah, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 1000A, Bethesda, MD 20892, (301) 594-3163, 
                        <E T="03">masonmahbl@mail.nih.gov</E>
                        .
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.306, Comparative Medicine; 93.333, Clinical Research, 93.306, 93.333, 93.337, 93.393-93.396, 93.837-93.844, 93.846-93.878, 93.892, 93.893, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: January 5, 2024.</DATED>
                    <NAME>Miguelina Perez, </NAME>
                    <TITLE>Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-00372 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>Eunice Kennedy Shriver National Institute of Child Health and Human Development; 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 meeting.</P>
                <P>The meeting will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The 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>
                         Eunice Kennedy Shriver National Institute of Child Health and Human Development Special Emphasis Panel; Understanding and Mitigating Health Disparities experienced by People with Disabilities caused by Ableism (R01)—OCT compatible.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         March 21-22, 2024.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10:00 a.m. to 5:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, Eunice Kennedy Shriver National Institute, of Child Health and Human Development, 6710B Rockledge Drive, Bethesda, MD 20892 (Virtual Meeting).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Helen Huang, Ph.D., Scientific Review Officer, Scientific Review Branch Eunice Kennedy Shriver National Institute, of Child Health and Human Development, NIH, 6710B Rockledge Drive, Room 2137D, Bethesda, MD 20892, (301) 496-8558, 
                        <E T="03">helen.huang@nih.gov.</E>
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.864, Population Research; 93.865, Research for Mothers and Children; 93.929, Center for Medical Rehabilitation Research; 93.209, Contraception and Infertility Loan Repayment Program, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: January 8, 2024. </DATED>
                    <NAME>Lauren A. Fleck, </NAME>
                    <TITLE>Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-00441 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBJECT>U.S. Customs and Border Protection</SUBJECT>
                <SUBJECT>Quarterly IRS Interest Rates Used in Calculating Interest on Overdue Accounts and Refunds of Customs Duties</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 notice advises the public that the quarterly Internal Revenue Service interest rates used to calculate interest on overdue accounts (underpayments) and refunds (overpayments) of customs duties will remain the same from the previous quarter. For the calendar quarter beginning January 1, 2024, the interest rates for underpayments will be 8 percent for both corporations and non-corporations. The interest rate for overpayments will be 8 percent for non-corporations and 7 percent for corporations. This notice is published for the convenience of the importing public and U.S. Customs and Border Protection personnel.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The rates announced in this notice are applicable as of January 1, 2024.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Bruce Ingalls, Revenue Division, Collection Refunds &amp; Analysis Branch, 6650 Telecom Drive, Suite #100, Indianapolis, Indiana 46278; telephone (317) 298-1107.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    Pursuant to 19 U.S.C. 1505 and Treasury Decision 85-93, published in the 
                    <E T="04">Federal Register</E>
                     on May 29, 1985 (50 FR 21832), the interest rate paid on applicable overpayments or underpayments of customs duties must be in accordance with the Internal Revenue Code rate established under 26 U.S.C. 6621 and 6622. Section 6621 provides different interest rates applicable to overpayments: one for corporations and one for non-corporations.
                </P>
                <P>The interest rates are based on the Federal short-term rate and determined by the Internal Revenue Service (IRS) on behalf of the Secretary of the Treasury on a quarterly basis. The rates effective for a quarter are determined during the first-month period of the previous quarter.</P>
                <P>
                    In Revenue Ruling 2023-22, the IRS determined the rates of interest for the calendar quarter beginning January 1, 
                    <PRTPAGE P="1930"/>
                    2024, and ending on March 31, 2024. The interest rate paid to the Treasury for underpayments will be the Federal short-term rate (5%) plus three percentage points (3%) for a total of eight percent (8%) for both corporations and non-corporations. For overpayments made by non-corporations, the rate is the Federal short-term rate (5%) plus three percentage points (3%) for a total of eight percent (8%). For corporate overpayments, the rate is the Federal short-term rate (5%) plus two percentage points (2%) for a total of seven percent (7%). These interest rates used to calculate interest on overdue accounts (underpayments) and refunds (overpayments) of customs duties remain the same from the previous quarter. These interest rates are subject to change for the calendar quarter beginning April 1, 2024, and ending on June 30, 2024.
                </P>
                <P>For the convenience of the importing public and U.S. Customs and Border Protection personnel, the following list of IRS interest rates used, covering the period from July of 1974 to date, to calculate interest on overdue accounts and refunds of customs duties, is published in summary format.</P>
                <GPOTABLE COLS="5" OPTS="L2,tp0,i1" CDEF="s50,15,15,15,15">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Beginning date</CHED>
                        <CHED H="1">Ending date</CHED>
                        <CHED H="1">
                            Underpayments
                            <LI>(percent)</LI>
                        </CHED>
                        <CHED H="1">
                            Overpayments
                            <LI>(percent)</LI>
                        </CHED>
                        <CHED H="1">
                            Corporate
                            <LI>overpayments</LI>
                            <LI>(Eff. 1-1-99)</LI>
                            <LI>(percent)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">070174</ENT>
                        <ENT>063075</ENT>
                        <ENT>6</ENT>
                        <ENT>6</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">070175</ENT>
                        <ENT>013176</ENT>
                        <ENT>9</ENT>
                        <ENT>9</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">020176</ENT>
                        <ENT>013178</ENT>
                        <ENT>7</ENT>
                        <ENT>7</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">020178</ENT>
                        <ENT>013180</ENT>
                        <ENT>6</ENT>
                        <ENT>6</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">020180</ENT>
                        <ENT>013182</ENT>
                        <ENT>12</ENT>
                        <ENT>12</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">020182</ENT>
                        <ENT>123182</ENT>
                        <ENT>20</ENT>
                        <ENT>20</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">010183</ENT>
                        <ENT>063083</ENT>
                        <ENT>16</ENT>
                        <ENT>16</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">070183</ENT>
                        <ENT>123184</ENT>
                        <ENT>11</ENT>
                        <ENT>11</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">010185</ENT>
                        <ENT>063085</ENT>
                        <ENT>13</ENT>
                        <ENT>13</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">070185</ENT>
                        <ENT>123185</ENT>
                        <ENT>11</ENT>
                        <ENT>11</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">010186</ENT>
                        <ENT>063086</ENT>
                        <ENT>10</ENT>
                        <ENT>10</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">070186</ENT>
                        <ENT>123186</ENT>
                        <ENT>9</ENT>
                        <ENT>9</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">010187</ENT>
                        <ENT>093087</ENT>
                        <ENT>9</ENT>
                        <ENT>8</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">100187</ENT>
                        <ENT>123187</ENT>
                        <ENT>10</ENT>
                        <ENT>9</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">010188</ENT>
                        <ENT>033188</ENT>
                        <ENT>11</ENT>
                        <ENT>10</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">040188</ENT>
                        <ENT>093088</ENT>
                        <ENT>10</ENT>
                        <ENT>9</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">100188</ENT>
                        <ENT>033189</ENT>
                        <ENT>11</ENT>
                        <ENT>10</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">040189</ENT>
                        <ENT>093089</ENT>
                        <ENT>12</ENT>
                        <ENT>11</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">100189</ENT>
                        <ENT>033191</ENT>
                        <ENT>11</ENT>
                        <ENT>10</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">040191</ENT>
                        <ENT>123191</ENT>
                        <ENT>10</ENT>
                        <ENT>9</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">010192</ENT>
                        <ENT>033192</ENT>
                        <ENT>9</ENT>
                        <ENT>8</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">040192</ENT>
                        <ENT>093092</ENT>
                        <ENT>8</ENT>
                        <ENT>7</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">100192</ENT>
                        <ENT>063094</ENT>
                        <ENT>7</ENT>
                        <ENT>6</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">070194</ENT>
                        <ENT>093094</ENT>
                        <ENT>8</ENT>
                        <ENT>7</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">100194</ENT>
                        <ENT>033195</ENT>
                        <ENT>9</ENT>
                        <ENT>8</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">040195</ENT>
                        <ENT>063095</ENT>
                        <ENT>10</ENT>
                        <ENT>9</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">070195</ENT>
                        <ENT>033196</ENT>
                        <ENT>9</ENT>
                        <ENT>8</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">040196</ENT>
                        <ENT>063096</ENT>
                        <ENT>8</ENT>
                        <ENT>7</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">070196</ENT>
                        <ENT>033198</ENT>
                        <ENT>9</ENT>
                        <ENT>8</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">040198</ENT>
                        <ENT>123198</ENT>
                        <ENT>8</ENT>
                        <ENT>7</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">010199</ENT>
                        <ENT>033199</ENT>
                        <ENT>7</ENT>
                        <ENT>7</ENT>
                        <ENT>6</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">040199</ENT>
                        <ENT>033100</ENT>
                        <ENT>8</ENT>
                        <ENT>8</ENT>
                        <ENT>7</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">040100</ENT>
                        <ENT>033101</ENT>
                        <ENT>9</ENT>
                        <ENT>9</ENT>
                        <ENT>8</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">040101</ENT>
                        <ENT>063001</ENT>
                        <ENT>8</ENT>
                        <ENT>8</ENT>
                        <ENT>7</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">070101</ENT>
                        <ENT>123101</ENT>
                        <ENT>7</ENT>
                        <ENT>7</ENT>
                        <ENT>6</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">010102</ENT>
                        <ENT>123102</ENT>
                        <ENT>6</ENT>
                        <ENT>6</ENT>
                        <ENT>5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">010103</ENT>
                        <ENT>093003</ENT>
                        <ENT>5</ENT>
                        <ENT>5</ENT>
                        <ENT>4</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">100103</ENT>
                        <ENT>033104</ENT>
                        <ENT>4</ENT>
                        <ENT>4</ENT>
                        <ENT>3</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">040104</ENT>
                        <ENT>063004</ENT>
                        <ENT>5</ENT>
                        <ENT>5</ENT>
                        <ENT>4</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">070104</ENT>
                        <ENT>093004</ENT>
                        <ENT>4</ENT>
                        <ENT>4</ENT>
                        <ENT>3</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">100104</ENT>
                        <ENT>033105</ENT>
                        <ENT>5</ENT>
                        <ENT>5</ENT>
                        <ENT>4</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">040105</ENT>
                        <ENT>093005</ENT>
                        <ENT>6</ENT>
                        <ENT>6</ENT>
                        <ENT>5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">100105</ENT>
                        <ENT>063006</ENT>
                        <ENT>7</ENT>
                        <ENT>7</ENT>
                        <ENT>6</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">070106</ENT>
                        <ENT>123107</ENT>
                        <ENT>8</ENT>
                        <ENT>8</ENT>
                        <ENT>7</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">010108</ENT>
                        <ENT>033108</ENT>
                        <ENT>7</ENT>
                        <ENT>7</ENT>
                        <ENT>6</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">040108</ENT>
                        <ENT>063008</ENT>
                        <ENT>6</ENT>
                        <ENT>6</ENT>
                        <ENT>5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">070108</ENT>
                        <ENT>093008</ENT>
                        <ENT>5</ENT>
                        <ENT>5</ENT>
                        <ENT>4</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">100108</ENT>
                        <ENT>123108</ENT>
                        <ENT>6</ENT>
                        <ENT>6</ENT>
                        <ENT>5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">010109</ENT>
                        <ENT>033109</ENT>
                        <ENT>5</ENT>
                        <ENT>5</ENT>
                        <ENT>4</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">040109</ENT>
                        <ENT>123110</ENT>
                        <ENT>4</ENT>
                        <ENT>4</ENT>
                        <ENT>3</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">010111</ENT>
                        <ENT>033111</ENT>
                        <ENT>3</ENT>
                        <ENT>3</ENT>
                        <ENT>2</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">040111</ENT>
                        <ENT>093011</ENT>
                        <ENT>4</ENT>
                        <ENT>4</ENT>
                        <ENT>3</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">100111</ENT>
                        <ENT>033116</ENT>
                        <ENT>3</ENT>
                        <ENT>3</ENT>
                        <ENT>2</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">040116</ENT>
                        <ENT>033118</ENT>
                        <ENT>4</ENT>
                        <ENT>4</ENT>
                        <ENT>3</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">040118</ENT>
                        <ENT>123118</ENT>
                        <ENT>5</ENT>
                        <ENT>5</ENT>
                        <ENT>4</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">010119</ENT>
                        <ENT>063019</ENT>
                        <ENT>6</ENT>
                        <ENT>6</ENT>
                        <ENT>5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">070119</ENT>
                        <ENT>063020</ENT>
                        <ENT>5</ENT>
                        <ENT>5</ENT>
                        <ENT>4</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">070120</ENT>
                        <ENT>033122</ENT>
                        <ENT>3</ENT>
                        <ENT>3</ENT>
                        <ENT>2</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="1931"/>
                        <ENT I="01">040122</ENT>
                        <ENT>063022</ENT>
                        <ENT>4</ENT>
                        <ENT>4</ENT>
                        <ENT>3</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">070122</ENT>
                        <ENT>093022</ENT>
                        <ENT>5</ENT>
                        <ENT>5</ENT>
                        <ENT>4</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">100122</ENT>
                        <ENT>123122</ENT>
                        <ENT>6</ENT>
                        <ENT>6</ENT>
                        <ENT>5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">010123</ENT>
                        <ENT>093023</ENT>
                        <ENT>7</ENT>
                        <ENT>7</ENT>
                        <ENT>6</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">100123</ENT>
                        <ENT>033124</ENT>
                        <ENT>8</ENT>
                        <ENT>8</ENT>
                        <ENT>7</ENT>
                    </ROW>
                </GPOTABLE>
                <SIG>
                    <DATED>Dated: January 5, 2024.</DATED>
                    <NAME>Crinley S. Hoover,</NAME>
                    <TITLE>Acting Chief Financial Officer, U.S. Customs and Border Protection.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00389 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9111-14-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Federal Emergency Management Agency</SUBAGY>
                <DEPDOC>[Docket ID FEMA-2024-0002; Internal Agency Docket No. FEMA-B-2401]</DEPDOC>
                <SUBJECT>Changes in Flood Hazard Determinations</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Emergency Management Agency, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice lists communities where the addition or modification of Base Flood Elevations (BFEs), base flood depths, Special Flood Hazard Area (SFHA) boundaries or zone designations, or the regulatory floodway (hereinafter referred to as flood hazard determinations), as shown on the Flood Insurance Rate Maps (FIRMs), and where applicable, in the supporting Flood Insurance Study (FIS) reports, prepared by the Federal Emergency Management Agency (FEMA) for each community, is appropriate because of new scientific or technical data. The FIRM, and where applicable, portions of the FIS report, have been revised to reflect these flood hazard determinations through issuance of a Letter of Map Revision (LOMR), in accordance with Federal Regulations. The currently effective community number is shown in the table below and must be used for all new policies and renewals.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>These flood hazard determinations will be finalized on the dates listed in the table below and revise the FIRM panels and FIS report in effect prior to this determination for the listed communities.</P>
                    <P>From the date of the second publication of notification of these changes in a newspaper of local circulation, any person has 90 days in which to request through the community that the Deputy Associate Administrator for Insurance and Mitigation reconsider the changes. The flood hazard determination information may be changed during the 90-day period.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The affected communities are listed in the table below. Revised flood hazard information for each community is available for inspection at both the online location and the respective community map repository address listed in the table below. Additionally, the current effective FIRM and FIS report for each community are accessible online through the FEMA Map Service Center at 
                        <E T="03">https://msc.fema.gov</E>
                         for comparison.
                    </P>
                    <P>Submit comments and/or appeals to the Chief Executive Officer of the community as listed in the table below.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Rick Sacbibit, Chief, Engineering Services Branch, Federal Insurance and Mitigation Administration, FEMA, 400 C Street SW, Washington, DC 20472, (202) 646-7659, or (email) 
                        <E T="03">patrick.sacbibit@fema.dhs.gov;</E>
                         or visit the FEMA Mapping and Insurance eXchange (FMIX) online at 
                        <E T="03">https://www.floodmaps.fema.gov/fhm/fmx_main.html</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The specific flood hazard determinations are not described for each community in this notice. However, the online location and local community map repository address where the flood hazard determination information is available for inspection is provided.</P>
                <P>Any request for reconsideration of flood hazard determinations must be submitted to the Chief Executive Officer of the community as listed in the table below.</P>
                <P>
                    The modifications are made pursuant to section 201 of the Flood Disaster Protection Act of 1973, 42 U.S.C. 4105, and are in accordance with the National Flood Insurance Act of 1968, 42 U.S.C. 4001 
                    <E T="03">et seq.,</E>
                     and with 44 CFR part 65.
                </P>
                <P>The FIRM and FIS report are the basis of the floodplain management measures that the community is required either to adopt or to show evidence of having in effect in order to qualify or remain qualified for participation in the National Flood Insurance Program (NFIP).</P>
                <P>These flood hazard determinations, together with the floodplain management criteria required by 44 CFR 60.3, are the minimum that are required. They should not be construed to mean that the community must change any existing ordinances that are more stringent in their floodplain management requirements. The community may at any time enact stricter requirements of its own or pursuant to policies established by other Federal, State, or regional entities. The flood hazard determinations are in accordance with 44 CFR 65.4.</P>
                <P>
                    The affected communities are listed in the following table. Flood hazard determination information for each community is available for inspection at both the online location and the respective community map repository address listed in the table below. Additionally, the current effective FIRM and FIS report for each community are accessible online through the FEMA Map Service Center at 
                    <E T="03">https://msc.fema.gov</E>
                     for comparison.
                </P>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance No. 97.022, “Flood Insurance.”)</FP>
                </EXTRACT>
                <SIG>
                    <NAME>Nicholas A. Shufro,</NAME>
                    <TITLE>Deputy Assistant Administrator for Risk Management, Federal Emergency Management Agency, Department of Homeland Security.</TITLE>
                </SIG>
                <PRTPAGE P="1932"/>
                <GPOTABLE COLS="7" OPTS="L2,nj,tp0,p7,7/8,i1" CDEF="xls50,xl50,xl75,xl75,xl90,xs55,10">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">State and county</CHED>
                        <CHED H="1">Location and case No.</CHED>
                        <CHED H="1">
                            Chief executive 
                            <LI>officer of community</LI>
                        </CHED>
                        <CHED H="1">
                            Community map 
                            <LI>repository</LI>
                        </CHED>
                        <CHED H="1">
                            Online location of 
                            <LI>letter of map revision</LI>
                        </CHED>
                        <CHED H="1">
                            Date of 
                            <LI>modification</LI>
                        </CHED>
                        <CHED H="1">
                            Community 
                            <LI>No.</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Arkansas: Washington</ENT>
                        <ENT>City of Fayetteville (23-06-0884P).</ENT>
                        <ENT>The Honorable Lioneld Jordan, Mayor, City of Fayetteville, 113 West Mountain Street, Fayetteville, AR 72701.</ENT>
                        <ENT>City Hall, 113 West Mountain Street, Fayetteville, AR 72701.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Feb. 20, 2024</ENT>
                        <ENT>050216</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Colorado: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Boulder</ENT>
                        <ENT>City of Lafayette (23-08-0459P).</ENT>
                        <ENT>The Honorable J. D. Mangat, Mayor, City of Lafayette, 1290 South Public Road, Lafayette, CO 80026.</ENT>
                        <ENT>Planning Department, 1290 South Public Road, Lafayette, CO 80026.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Apr. 15, 2024</ENT>
                        <ENT>080026</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Boulder</ENT>
                        <ENT>Unincorporated areas of Boulder County (23-08-0459P).</ENT>
                        <ENT>Claire Levy, Chair, Boulder County Board of Commissioners, P.O. Box 471, Boulder, CO 80306.</ENT>
                        <ENT>Boulder County Transportation Department, 1739 Broadway, Suite 300, Boulder, CO 80306.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Apr. 15, 2024</ENT>
                        <ENT>080023</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Broomfield</ENT>
                        <ENT>City and County of Broomfield (23-08-0459P).</ENT>
                        <ENT>The Honorable Guyleen Castriotta, Mayor, City and County of Broomfield, 1 DesCombes Drive, Broomfield, CO 80020.</ENT>
                        <ENT>Engineering Department, 1 DesCombes Drive, Broomfield, CO 80020.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Apr. 15, 2024</ENT>
                        <ENT>085073</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Delaware: New Castle</ENT>
                        <ENT>Unincorporated areas of New Castle County (23-03-0137P).</ENT>
                        <ENT>Matthew Meyer, New Castle County Executive, 87 Read's Way, New Castle, DE 19720.</ENT>
                        <ENT>New Castle County Government Center, 87 Read's Way, New Castle, DE 19720.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Feb. 15, 2024</ENT>
                        <ENT>105085</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Florida: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Lee</ENT>
                        <ENT>Unincorporated areas of Lee County (23-04-3191P).</ENT>
                        <ENT>David Harner, Lee County Manager, 2115 2nd Street, Fort Myers, FL 33901.</ENT>
                        <ENT>Lee County Building Department, 1500 Monroe Street, Fort Myers, FL 33901.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Mar. 22, 2024</ENT>
                        <ENT>125124</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Miami-Dade</ENT>
                        <ENT>Town of Surfside (23-04-5056P).</ENT>
                        <ENT>The Honorable Shlomo Danzinger, Mayor, Town of Surfside, 9293 Harding Avenue, Surfside, FL 33154.</ENT>
                        <ENT>Town Hall, 9293 Harding Avenue, Surfside, FL 33154.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Apr. 18, 2024</ENT>
                        <ENT>120659</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Sarasota</ENT>
                        <ENT>City of Sarasota (23-04-4295P).</ENT>
                        <ENT>The Honorable Kyle Scott Battie, Mayor, City of Sarasota, 1565 1st Street, Room 101, Sarasota, FL 34236.</ENT>
                        <ENT>Development Service Department, 1565 1st Street, Room 101, Sarasota, FL 34236.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Mar. 27, 2024</ENT>
                        <ENT>125150</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Massachusetts: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Middlesex</ENT>
                        <ENT>City of Lowell (23-01-0132P).</ENT>
                        <ENT>Thomas A. Golden, Jr., Manager, City of Lowell, 375 Merrimack Street, 2nd Floor, Room 43, Lowell, MA 01852.</ENT>
                        <ENT>Fire Department Administration Office, 99 Moody Street, Lowell, MA 01852.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Feb. 23, 2024</ENT>
                        <ENT>250201</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Middlesex</ENT>
                        <ENT>Town of Chelmsford (23-01-0132P).</ENT>
                        <ENT>Paul Cohen, Manager, Town of Chelmsford, 50 Billerica Road, Chelmsford, MA 01824.</ENT>
                        <ENT>Community Development Department, 50 Billerica Road, Chelmsford, MA 01824.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Feb. 23, 2024</ENT>
                        <ENT>250188</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Suffolk</ENT>
                        <ENT>City of Revere (24-01-0009P).</ENT>
                        <ENT>The Honorable Patrick M. Keefe, Jr., Acting Mayor, City of Revere, 281 Broadway, Revere, MA 02151.</ENT>
                        <ENT>City Hall, 281 Broadway, Revere, MA 02151.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Mar. 21, 2024</ENT>
                        <ENT>250288</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Montana: Lewis and Clark</ENT>
                        <ENT>Unincorporated areas of Lewis and Clark County (23-08-0467P).</ENT>
                        <ENT>Tom Rolfe, Chair, Lewis and Clark County Board of Commissioners, 316 North Park Avenue, Room 345, Helena, MT 59623.</ENT>
                        <ENT>Lewis and Clark County Department of Floodplain Development, 316 North Park Avenue, Room 230, Helena, MT 59623.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Apr. 8, 2024</ENT>
                        <ENT>300038</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">North Carolina:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Buncombe</ENT>
                        <ENT>Unincorporated areas of Buncombe County (24-04-0526P)</ENT>
                        <ENT>Brownie Newman, Chair, Buncombe County Board of Commissioners, 200 College Street, Suite 300, Asheville, NC 28801.</ENT>
                        <ENT>Buncombe County Planning and Development, 46 Valley Street, Asheville, NC 28801.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Apr. 1, 2024</ENT>
                        <ENT>370031</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Forsyth</ENT>
                        <ENT>City of Winston-Salem (24-04-0523P)</ENT>
                        <ENT>The Honorable Allen Joines, Mayor, City of Winston-Salem, P.O. Box 2511, Winston-Salem, NC 27102.</ENT>
                        <ENT>Planning and Development Services Department, 100 East 1st Street, Winston-Salem, NC 27101.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch.</E>
                        </ENT>
                        <ENT>Apr. 2, 2024</ENT>
                        <ENT>375360</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Forsyth</ENT>
                        <ENT>Unincorporated areas of Forsyth County (24-04-0523P)</ENT>
                        <ENT>The Honorable David Plyler, Chair, Forsyth County Board of Commissioners, 201 North Chestnut Street, Winston-Salem, NC 27101</ENT>
                        <ENT>Forsyth County Planning and Development Services, 100 East First Street, Winston-Salem, NC 27101</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Apr. 2, 2024</ENT>
                        <ENT>375349</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="1933"/>
                        <ENT I="03">Madison</ENT>
                        <ENT>Unincorporated areas of Madison County (24-04-0526P)</ENT>
                        <ENT>Matthew Wechtel, Chair, Madison County Board of Commissioners, P.O. Box 579, Marshall, NC 28753.</ENT>
                        <ENT>Madison County Development Services Development, 5707 U.S. Highway 25/70, Marshall, NC 28779.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Apr. 1, 2024</ENT>
                        <ENT>370152</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Rowan</ENT>
                        <ENT>Town of Landis (22-04-3669P)</ENT>
                        <ENT>The Honorable Meredith Smith, Mayor, Town of Landis, P.O. Box 8165, Landis, NC 28088.</ENT>
                        <ENT>Town Hall, 312 South Main Street, Landis, NC 28088.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Apr. 1, 2024</ENT>
                        <ENT>370213</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Rowan</ENT>
                        <ENT>Unincorporated areas of Rowan County (22-04-3669P)</ENT>
                        <ENT>The Honorable Greg Edds, Chair, Rowan County Board of Commissioners, 130 West Innes Street, Salisbury, NC 28144</ENT>
                        <ENT>Rowan County Planning and Development Department, 402 North Main Street, #204, Salisbury, NC 28144</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Apr. 1, 2024</ENT>
                        <ENT>370351</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Wake</ENT>
                        <ENT>Town of Rolesville (24-04-0517P)</ENT>
                        <ENT>The Honorable Ronnie Currin, Mayor, Town of Rolesville, P.O. Box 250, Rolesville, NC 27571.</ENT>
                        <ENT>Planning Department, 502 Southtown Circle, Rolesville, NC 27571.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Apr. 11, 2024</ENT>
                        <ENT>370468</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Wake</ENT>
                        <ENT>Town of Wake Forest (24-04-0517P)</ENT>
                        <ENT>The Honorable Vivian A. Jones, Mayor, Town of Wake Forest, 301 South Brooks Street, Wake Forest, NC 27587.</ENT>
                        <ENT>Planning Department, 301 South Brooks Street, Wake Forest, NC 27587.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Apr. 11, 2024</ENT>
                        <ENT>370244</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Wake</ENT>
                        <ENT>Unincorporated areas of Wake County (24-04-0517P)</ENT>
                        <ENT>Shinica Thomas, Chair, Wake County Board of Commissioners, P.O. Box 550, Raleigh, NC 27602.</ENT>
                        <ENT>Wake County Environmental Services Department, 337 South Salisbury Street, Raleigh, NC 27601.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Apr. 11, 2024</ENT>
                        <ENT>370368</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Oklahoma: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Logan</ENT>
                        <ENT>City of Guthrie (23-06-0569P).</ENT>
                        <ENT>The Honorable Steven J. Gentling, Mayor, City of Guthrie, 101 North 2nd Street, Guthrie, OK 73044.</ENT>
                        <ENT>City Hall, 101 North 2nd Street, Guthrie, OK 73044.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Mar. 7, 2024</ENT>
                        <ENT>400099</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Logan</ENT>
                        <ENT>Unincorporated areas of Logan County (23-06-0569P).</ENT>
                        <ENT>Monty Piearcy, Chair, Logan County Board of Commissioners, 312 East Harrison Avenue, Guthrie, OK 73044.</ENT>
                        <ENT>Logan County Emergency Management Department, 219 South Broad Street, Guthrie, OK 73044.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Mar. 7, 2024</ENT>
                        <ENT>400096</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Texas: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Collin</ENT>
                        <ENT>City of Blue Ridge (23-06-0921P).</ENT>
                        <ENT>The Honorable Rhonda Williams, Mayor, City of Blue Ridge, 200 South Main Street, Blue Ridge, TX 75424.</ENT>
                        <ENT>Public Works Department, 200 South Main Street, Blue Ridge, TX 75424.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Mar. 11, 2024</ENT>
                        <ENT>481628</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Collin</ENT>
                        <ENT>City of Celina (23-06-0718P).</ENT>
                        <ENT>The Honorable Ryan Tubbs, Mayor, City of Celina, 142 North Ohio Street, Celina, TX 75009.</ENT>
                        <ENT>City Hall, 142 North Ohio Street, Celina, TX 75009.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Feb. 20, 2024</ENT>
                        <ENT>480133</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Collin</ENT>
                        <ENT>City of McKinney (23-06-1123P).</ENT>
                        <ENT>The Honorable George Fuller, Mayor, City of McKinney, 222 North Tennessee Street, McKinney, TX 75069.</ENT>
                        <ENT>City Hall, 222 North Tennessee Street, McKinney, TX 75069.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Apr. 1, 2024</ENT>
                        <ENT>480135</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Collin</ENT>
                        <ENT>City of Murphy (23-06-1486P).</ENT>
                        <ENT>The Honorable Scott Bradley, Mayor, City of Murphy, 206 North Murphy Road, Murphy, TX 75094.</ENT>
                        <ENT>City Hall, 206 North Murphy Road, Murphy, TX 75094.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Mar. 29, 2024</ENT>
                        <ENT>480137</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Dallas</ENT>
                        <ENT>City of Dallas (23-06-1122P).</ENT>
                        <ENT>The Honorable Eric Johnson, Mayor, City of Dallas, 1500 Marilla Street, Suite 5EN, Dallas, TX 75201.</ENT>
                        <ENT>Floodplain Management Department, 2245 Irving Boulevard, 2nd Floor, Dallas, TX 75207.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Mar. 4, 2024</ENT>
                        <ENT>480171</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Dallas</ENT>
                        <ENT>City of Garland (23-06-1006P).</ENT>
                        <ENT>The Honorable Scott LeMay, Mayor, City of Garland, 200 North 5th Street, Garland, TX 75040.</ENT>
                        <ENT>City Hall, 200 North 5th Street, Garland, TX 75040.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Mar. 11, 2024</ENT>
                        <ENT>485471</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Dallas</ENT>
                        <ENT>City of Mesquite (23-06-1636P).</ENT>
                        <ENT>The Honorable Daniel Alemán, Jr., Mayor, City of Mesquite, P.O. Box 850137, Mesquite, TX 75185.</ENT>
                        <ENT>City Hall, 757 North Galloway Avenue, Mesquite, TX 75149.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Apr. 8, 2024</ENT>
                        <ENT>485490</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Dallas</ENT>
                        <ENT>City of Rowlett (23-06-1006P).</ENT>
                        <ENT>The Honorable Blake Margolis, Mayor, City of Rowlett, 4000 Main Street, Rowlett, TX 75088.</ENT>
                        <ENT>Community Development Department, 5702 Rowlett Road, Rowlett, TX 75089.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Mar. 11, 2024</ENT>
                        <ENT>480185</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="1934"/>
                        <ENT I="03">Dallas</ENT>
                        <ENT>City of Sachse (23-06-1006P).</ENT>
                        <ENT>The Honorable Jeff Bickerstaff, Mayor, City of Sachse, 3815 Sachse Road, Building B, Sachse, TX 75048.</ENT>
                        <ENT>City Hall, 3815 Sachse Road, Building B, Sachse, TX 75048.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Mar. 11, 2024</ENT>
                        <ENT>480186</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Denton</ENT>
                        <ENT>Town of Argyle (23-06-1120P).</ENT>
                        <ENT>The Honorable Rick Bradford, Mayor, Town of Argyle, P.O. Box 609, Argyle, TX 76226.</ENT>
                        <ENT>Town Hall, 308 Denton Street, Argyle, TX 76226.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Mar. 1, 2024</ENT>
                        <ENT>480775</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Denton</ENT>
                        <ENT>Town of Flower Mound (23-06-1120P).</ENT>
                        <ENT>The Honorable Derek France, Mayor, Town of Flower Mound, 2121 Cross Timbers Road, Flower Mound, TX 75028.</ENT>
                        <ENT>Town Hall, 2121 Cross Timbers Road, Flower Mound, TX 75028.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Mar. 1, 2024</ENT>
                        <ENT>480777</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Grayson</ENT>
                        <ENT>City of Denison (23-06-0905P).</ENT>
                        <ENT>The Honorable Janet Gott, Mayor, City of Denison, 300 West Main Street, Denison, TX 75020.</ENT>
                        <ENT>Department of Public Works, 300 West Main Street, Denison, TX 75020.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Feb. 20, 2024</ENT>
                        <ENT>480259</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Harris</ENT>
                        <ENT>Unincorporated areas of Harris County (22-06-2700P).</ENT>
                        <ENT>The Honorable Lina Hidalgo, Harris County Judge, 1001 Preston Street, Suite 911, Houston, TX 77002.</ENT>
                        <ENT>Harris County Permit Office, 1111 Fannin Street, 8th Floor, Houston, TX 77002.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Mar. 4, 2024</ENT>
                        <ENT>480287</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Medina</ENT>
                        <ENT>Unincorporated areas of Medina County (23-06-1697P).</ENT>
                        <ENT>The Honorable Keith Lutz, Medina County Judge, 1300 Avenue M, Room 250, Hondo, TX 78861.</ENT>
                        <ENT>Medina County Old Jail Building, 1502 Avenue K, Hondo, TX 78861.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Mar. 8, 2024</ENT>
                        <ENT>480472</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Travis</ENT>
                        <ENT>Unincorporated areas of Travis County (23-06-1281P).</ENT>
                        <ENT>The Honorable Andy Brown, Travis County Judge, P.O. Box 1748, Austin, TX 78767.</ENT>
                        <ENT>Travis County Transportation and Natural Resources Department, 700 Lavaca Street, 5th Floor, Austin, TX 78701.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Apr. 1, 2024</ENT>
                        <ENT>481026</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Utah: Washington</ENT>
                        <ENT>Town of Springdale (23-08-0323P).</ENT>
                        <ENT>Rick Wixom, Manager, Town of Springdale, 118 Lion Boulevard, Springdale, UT 84767.</ENT>
                        <ENT>Community Development Department, 118 Lion Boulevard, Springdale, UT 84767.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Apr. 18, 2024</ENT>
                        <ENT>490179</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Virginia: Chesterfield</ENT>
                        <ENT>Unincorporated areas of Chesterfield County (23-03-0270P).</ENT>
                        <ENT>Joseph P. Casey, Chesterfield County Administrator, 9901 Lori Road, Chesterfield, VA 23832.</ENT>
                        <ENT>Chesterfield County Community Development Department, 9800 Government Center Parkway, Chesterfield, VA 23832.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Mar. 22, 2024</ENT>
                        <ENT>510035</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">West Virginia: Tucker</ENT>
                        <ENT>Unincorporated areas of Tucker County (23-03-0296P).</ENT>
                        <ENT>Michael Rosenau, President, Tucker County Commission, 211 1st Street, Suite 307, Parsons, WV 26287.</ENT>
                        <ENT>Tucker County Floodplain Administration, 211 1st Street, Suite 1, Parsons, WV 26287.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                            .
                        </ENT>
                        <ENT>Feb. 8, 2024</ENT>
                        <ENT>540191</ENT>
                    </ROW>
                </GPOTABLE>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00479 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-12-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Federal Emergency Management Agency</SUBAGY>
                <DEPDOC>[Docket ID FEMA-2024-0002; Internal Agency Docket No. FEMA-B-2400]</DEPDOC>
                <SUBJECT>Proposed Flood Hazard Determinations</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Emergency Management Agency, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Comments are requested on proposed flood hazard determinations, which may include additions or modifications of any Base Flood Elevation (BFE), base flood depth, Special Flood Hazard Area (SFHA) boundary or zone designation, or regulatory floodway on the Flood Insurance Rate Maps (FIRMs), and where applicable, in the supporting Flood Insurance Study (FIS) reports for the communities listed in the table below. The purpose of this notice is to seek general information and comment regarding the preliminary FIRM, and where applicable, the FIS report that the Federal Emergency Management Agency (FEMA) has provided to the affected communities. The FIRM and FIS report are the basis of the floodplain management measures that the community is required either to adopt or to show evidence of having in effect in order to qualify or remain qualified for participation in the National Flood Insurance Program (NFIP).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments are to be submitted on or before April 10, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The Preliminary FIRM, and where applicable, the FIS report for each community are available for inspection at both the online location 
                        <E T="03">https://hazards.fema.gov/femaportal/prelimdownload</E>
                         and the respective Community Map Repository address listed in the tables below. Additionally, the current effective FIRM and FIS report for each community are accessible online through the FEMA Map Service Center at 
                        <E T="03">https://msc.fema.gov</E>
                         for comparison.
                    </P>
                    <P>
                        You may submit comments, identified by Docket No. FEMA-B-2400, to Rick Sacbibit, Chief, Engineering Services Branch, Federal Insurance and Mitigation Administration, FEMA, 400 C Street SW, Washington, DC 20472, (202) 646-7659, or (email) 
                        <E T="03">patrick.sacbibit@fema.dhs.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Rick Sacbibit, Chief, Engineering Services Branch, Federal Insurance and 
                        <PRTPAGE P="1935"/>
                        Mitigation Administration, FEMA, 400 C Street SW, Washington, DC 20472, (202) 646-7659, or (email) 
                        <E T="03">patrick.sacbibit@fema.dhs.gov;</E>
                         or visit the FEMA Mapping and Insurance eXchange (FMIX) online at 
                        <E T="03">https://www.floodmaps.fema.gov/fhm/fmx_main.html.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>FEMA proposes to make flood hazard determinations for each community listed below, in accordance with section 110 of the Flood Disaster Protection Act of 1973, 42 U.S.C. 4104, and 44 CFR 67.4(a).</P>
                <P>These proposed flood hazard determinations, together with the floodplain management criteria required by 44 CFR 60.3, are the minimum that are required. They should not be construed to mean that the community must change any existing ordinances that are more stringent in their floodplain management requirements. The community may at any time enact stricter requirements of its own or pursuant to policies established by other Federal, State, or regional entities. These flood hazard determinations are used to meet the floodplain management requirements of the NFIP.</P>
                <P>The communities affected by the flood hazard determinations are provided in the tables below. Any request for reconsideration of the revised flood hazard information shown on the Preliminary FIRM and FIS report that satisfies the data requirements outlined in 44 CFR 67.6(b) is considered an appeal. Comments unrelated to the flood hazard determinations also will be considered before the FIRM and FIS report become effective.</P>
                <P>
                    Use of a Scientific Resolution Panel (SRP) is available to communities in support of the appeal resolution process. SRPs are independent panels of experts in hydrology, hydraulics, and other pertinent sciences established to review conflicting scientific and technical data and provide recommendations for resolution. Use of the SRP only may be exercised after FEMA and local communities have been engaged in a collaborative consultation process for at least 60 days without a mutually acceptable resolution of an appeal. Additional information regarding the SRP process can be found online at 
                    <E T="03">https://www.floodsrp.org/pdfs/srp_overview.pdf.</E>
                </P>
                <P>
                    The watersheds and/or communities affected are listed in the tables below. The Preliminary FIRM, and where applicable, FIS report for each community are available for inspection at both the online location 
                    <E T="03">https://hazards.fema.gov/femaportal/prelimdownload</E>
                     and the respective Community Map Repository address listed in the tables. For communities with multiple ongoing Preliminary studies, the studies can be identified by the unique project number and Preliminary FIRM date listed in the tables. Additionally, the current effective FIRM and FIS report for each community are accessible online through the FEMA Map Service Center at 
                    <E T="03">https://msc.fema.gov</E>
                     for comparison.
                </P>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance No. 97.022, “Flood Insurance.”)</FP>
                </EXTRACT>
                <SIG>
                    <NAME>Nicholas A. Shufro,</NAME>
                    <TITLE>Deputy Assistant Administrator for Risk Management, Federal Emergency Management Agency, Department of Homeland Security.</TITLE>
                </SIG>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s100,r100">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Community</CHED>
                        <CHED H="1">Community map repository address</CHED>
                    </BOXHD>
                    <ROW EXPSTB="01">
                        <ENT I="21">
                            <E T="02">Mineral County, Colorado and Incorporated Areas</E>
                        </ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="21">
                            <E T="02">Project: 19-08-0036S Preliminary Date: January 13, 2023</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">City of Creede</ENT>
                        <ENT>Town Hall, 2223 North Main Street, Creede, CO 81130.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Unincorporated Areas of Mineral County</ENT>
                        <ENT>Mineral County Courthouse, 1201 North Main Street, Creede, CO 81130.</ENT>
                    </ROW>
                </GPOTABLE>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00478 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-12-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Federal Emergency Management Agency</SUBAGY>
                <DEPDOC>[Docket ID FEMA-2024-0002]</DEPDOC>
                <SUBJECT>Final Flood Hazard Determinations</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Emergency Management Agency, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Flood hazard determinations, which may include additions or modifications of Base Flood Elevations (BFEs), base flood depths, Special Flood Hazard Area (SFHA) boundaries or zone designations, or regulatory floodways on the Flood Insurance Rate Maps (FIRMs) and where applicable, in the supporting Flood Insurance Study (FIS) reports have been made final for the communities listed in the table below. The FIRM and FIS report are the basis of the floodplain management measures that a community is required either to adopt or to show evidence of having in effect in order to qualify or remain qualified for participation in the Federal Emergency Management Agency's (FEMA's) National Flood Insurance Program (NFIP).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The date of May 22, 2024 has been established for the FIRM and, where applicable, the supporting FIS report showing the new or modified flood hazard information for each community.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The FIRM, and if applicable, the FIS report containing the final flood hazard information for each community is available for inspection at the respective Community Map Repository address listed in the tables below and will be available online through the FEMA Map Service Center at 
                        <E T="03">https://msc.fema.gov</E>
                         by the date indicated above.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Rick Sacbibit, Chief, Engineering Services Branch, Federal Insurance and Mitigation Administration, FEMA, 400 C Street SW, Washington, DC 20472, (202) 646-7659, or (email) 
                        <E T="03">patrick.sacbibit@fema.dhs.gov;</E>
                         or visit the FEMA Mapping and Insurance eXchange (FMIX) online at 
                        <E T="03">https://www.floodmaps.fema.gov/fhm/fmx_main.html.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Federal Emergency Management Agency (FEMA) makes the final determinations listed below for the new or modified flood hazard information for each community listed. Notification of these changes has been published in newspapers of local circulation and 90 days have elapsed since that publication. The Deputy Associate Administrator for Insurance and Mitigation has resolved any appeals resulting from this notification.</P>
                <P>
                    This final notice is issued in accordance with section 110 of the Flood Disaster Protection Act of 1973, 42 U.S.C. 4104, and 44 CFR part 67. FEMA has developed criteria for floodplain management in floodprone 
                    <PRTPAGE P="1936"/>
                    areas in accordance with 44 CFR part 60.
                </P>
                <P>
                    Interested lessees and owners of real property are encouraged to review the new or revised FIRM and FIS report available at the address cited below for each community or online through the FEMA Map Service Center at 
                    <E T="03">https://msc.fema.gov.</E>
                </P>
                <P>The flood hazard determinations are made final in the watersheds and/or communities listed in the table below.</P>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance No. 97.022, “Flood Insurance.”)</FP>
                </EXTRACT>
                <SIG>
                    <NAME>Nicholas A. Shufro,</NAME>
                    <TITLE>Deputy Assistant Administrator for Risk Management, Federal Emergency Management Agency, Department of Homeland Security.</TITLE>
                </SIG>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s100,r100">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Community</CHED>
                        <CHED H="1">Community map repository address</CHED>
                    </BOXHD>
                    <ROW EXPSTB="01">
                        <ENT I="21">
                            <E T="02">Shasta County, California and Incorporated Areas</E>
                        </ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="21">
                            <E T="02">Docket No.: FEMA-B-2322</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">City of Redding</ENT>
                        <ENT>Permit Center, 777 Cypress Avenue, 1st Floor, Redding, CA 96001.</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">Unincorporated Areas of Shasta County</ENT>
                        <ENT>Shasta County Department of Public Works, 1855 Placer Street, Redding, CA 96001.</ENT>
                    </ROW>
                    <ROW EXPSTB="01">
                        <ENT I="21">
                            <E T="02">Linn County, Iowa and Incorporated Areas</E>
                        </ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="21">
                            <E T="02">Docket No.: FEMA-B-2279</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">City of Cedar Rapids</ENT>
                        <ENT>City Services Center, 500 15th Avenue Southwest, Cedar Rapids, IA 52404.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">City of Center Point</ENT>
                        <ENT>City Hall, 200 Franklin Street, Center Point, IA 52213.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">City of Marion</ENT>
                        <ENT>City Hall, 1225 6th Avenue, Suite 200, Marion, IA 52302.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">City of Palo</ENT>
                        <ENT>City Hall, 2800 Hollenbeck Road, Palo, IA 52324.</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">Unincorporated Areas of Linn County</ENT>
                        <ENT>Linn County Planning and Development Department, 935 2nd Street Southwest, Cedar Rapids, IA 52404.</ENT>
                    </ROW>
                    <ROW EXPSTB="01">
                        <ENT I="21">
                            <E T="02">Kingsbury County, South Dakota and Incorporated Areas</E>
                        </ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="21">
                            <E T="02">Docket No.: FEMA-B-2292</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">City of De Smet</ENT>
                        <ENT>City Hall, 106 Calumet Avenue SE, De Smet, SD 57231.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">City of Iroquois</ENT>
                        <ENT>City Hall, 320 East Washita Street, Iroquois, SD 57353.</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">Unincorporated Areas of Kingsbury County</ENT>
                        <ENT>Kingsbury County Courthouse, 202 2nd Street SE, De Smet, SD 57231.</ENT>
                    </ROW>
                    <ROW EXPSTB="01">
                        <ENT I="21">
                            <E T="02">Cumberland County, Virginia and Incorporated Areas</E>
                        </ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="21">
                            <E T="02">Docket No.: FEMA-B-2300</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00" RUL="s">
                        <ENT I="01">Unincorporated Areas of Cumberland County</ENT>
                        <ENT>Cumberland County Courthouse, Building Inspector's Office, 1 Courthouse Circle, Cumberland, VA 23040.</ENT>
                    </ROW>
                    <ROW EXPSTB="01">
                        <ENT I="21">
                            <E T="02">Skamania County, Washington and Incorporated Areas</E>
                        </ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="21">
                            <E T="02">Docket No.: FEMA-B-2215</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">City of North Bonneville</ENT>
                        <ENT>City Hall, 214 CBD Mall Drive, North Bonneville, WA 98639.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">City of Stevenson</ENT>
                        <ENT>City Hall, 7121 East Loop Road, Stevenson, WA 98648.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Unincorporated Areas of Skamania County</ENT>
                        <ENT>Skamania County Courthouse Annex, 170 Northwest Vancouver Avenue, Stevenson, WA 98648.</ENT>
                    </ROW>
                </GPOTABLE>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00477 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT</AGENCY>
                <DEPDOC>[Docket No. FR-7090-N-01]</DEPDOC>
                <SUBJECT>30 Day Notice of Proposed Information Collection: Generic Solution for Solicitation for HUD's Competitive Discretionary Funding Opportunity Announcements, OMB Control No.: 2501-NEW</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Policy Development and Research, Chief Data Officer, HUD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>HUD is seeking approval from the Office of Management and Budget (OMB) for the information collection described below. In accordance with the Paperwork Reduction Act, HUD is requesting comment from all interested parties on the proposed collection of information. The purpose of this notice is to allow for an additional 30 days of public comment.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Comments Due Date:</E>
                         February 12, 2024.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Interested persons are invited to submit comments regarding this proposal. 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. Interested persons are also invited to submit comments regarding this proposal and comments should refer to the proposal by name and/or OMB Control Number and should be sent to: Anna Guido, Clearance Officer, REE, Department of Housing and Urban Development, 451 7th Street SW, Room 8210, Washington, DC 20410-5000; email 
                        <E T="03">PaperworkReductionActOffice@hud.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Colette Pollard, Reports Management Officer, Department of Housing and Urban Development, 451 7th Street SW, Room 4176, Washington, DC 20410; email 
                        <E T="03">Colette.Pollard@hud.gov</E>
                         or telephone 202-402-3400 (this is not a toll-free number). HUD welcomes and is prepared to receive calls from 
                        <PRTPAGE P="1937"/>
                        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>
                         Copies of available documents submitted to OMB may be obtained from Ms. Pollard.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This notice informs the public that HUD is seeking approval from OMB for the information collection described in Section A.</P>
                <P>
                    The 
                    <E T="04">Federal Register</E>
                     notice that solicited public comment on the information collection for a period of 60 days was published on October 6, 2023 at 88 FR 69647.
                </P>
                <HD SOURCE="HD1">A. Overview of Information Collection</HD>
                <P>
                    <E T="03">Title of Proposal:</E>
                     Generic Solution for Solicitation for Competitive Discretionary Funding Opportunity Announcements.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     New Information Collection Request.
                </P>
                <P>
                    <E T="03">OMB Control Number, if applicable:</E>
                     2501-NEW.
                </P>
                <P>Additional OMB control numbers applicable to government-wide standardized forms are also noted in this collection. As the burden is accounted for in those separate collections, it is not included in this calculation.</P>
                <FP SOURCE="FP-1">SF 424, OMB Control No. 4040-0004</FP>
                <FP SOURCE="FP-1">SF 424-A, OMB Control No. 4040-0006</FP>
                <FP SOURCE="FP-1">SF 424-B, OMB Control No. 4040-0007</FP>
                <FP SOURCE="FP-1">SF 424-C, OMB Control No. 4040-0008</FP>
                <FP SOURCE="FP-1">SF 424 D, OMB Control No. 4040-0009</FP>
                <FP SOURCE="FP-1">SF LLL, OMB Control No. 4040-0013</FP>
                <FP SOURCE="FP-1">Lobbying Form, OMB Control No. 4040-0013</FP>
                <FP SOURCE="FP-1">Projects Abstract Summary, OMB Control No. 4040-0019</FP>
                <P>
                    <E T="03">Description of the need for the information and proposed use:</E>
                     HUD is required by 2 CFR 200.204 to publicly announce the availability of discretionary awards that are competed. To ensure grants and cooperative agreements are awarded to applicants best suited to perform the functions of the awards, applicants are generally required to perform two pre-award steps, the submission of the application and the negotiation of the individual award terms. The first part of HUD's funding applications consists of submitting the Standard Form 424 (SF-424), “Application for Federal Assistance” along with mandatory and optional standard government-wide and HUD forms. The burden associated with these government-wide forms are reflected in separate OMB-sponsored government-wide information collections and are not reflected in this collection.
                </P>
                <P>After the applicants have been selected as part of an objective competition process, HUD usually requires negotiation between HUD and the selected applicant to determine the terms of the award. A technical proposal (or technical submission) is required during the negotiation process. The technical proposal demonstrates the selected applicant's capabilities in accordance with the application or statement of work submitted with the application and/or selection criteria and other related information as specified in the funding announcement.</P>
                <P>The provisions of 2 CFR 200.207 instruct Federal agencies to comply with the requirements of 5 CFR part 1320, “Controlling Paperwork Burdens on the Public,” with regard to all forms or collection of additional information used by HUD in place of or as a supplement to the SF-424 series.</P>
                <P>
                    <E T="03">Respondents:</E>
                     Applicants for HUD's competitively funded financial assistance programs.
                </P>
                <P>
                    <E T="03">Information Collection/Form Number:</E>
                     SF 424 (4040-0004); SF-424B (4040-0007); SF-424D (4040-0009); SF 424A (4040-0006); SF-424C (4040-0008); SF LLL (4040-0013); Lobbying Form (4040-0013); Project Abstract Summary (4040-0019); HUD-424B; HUD-424CB (2501-0017); HUD-424CBW (2501-0017); HUD-424M (2501-0017); HUD-2880 (2501-0017); HUD-50070; Rural Partners Network (RPN) Community Networks (CN) Certification Form and Instructions; HUD 50153 (2501-0033); HUD 2991; HUD 2993; and Program specific requirements and rating factors (narrative and other attachments).
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     HUD bases the following estimates on historical experience. HUD's average of 45 funding announcements per fiscal year will fall under this generic request, plus an expected average of 10 NOFOs derived from supplemental funding enacted outside of the regular appropriations process. Additionally, the Department projects that it will receive approximately 30,000 applications annually.
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     Refer to Table 1.
                </P>
                <P>
                    <E T="03">Responses per Annum:</E>
                     Refer to Table 1.
                </P>
                <P>
                    <E T="03">Average Burden Hours per Response:</E>
                     HUD estimates it takes an average of 60 working hours to prepare and submit an application in grants.gov in response to a funding announcement. For applications submitted through 
                    <E T="03">esnaps.gov</E>
                    , HUD estimates it takes an average of 100 working hours, including completing the registration in 
                    <E T="03">esnaps.hud.gov,</E>
                     preparing and submitting an application and technical submission, and proper storage of records.
                </P>
                <P>
                    <E T="03">Total Estimated Burdens:</E>
                     For purposes of this information collection request, the HUD has used the average hourly earnings of a Project Management Specialist ($48.85 per hour) to monetize the value of respondent time. Therefore, the burden for these reporting activities is as follows using average response times:
                </P>
                <FP SOURCE="FP-2">30,000 applications * 160 hours * 1.2 frequency = 5,760,000 hours</FP>
                <FP SOURCE="FP-2">5,760,000 hours * $48.85 = $281,376,000</FP>
                <GPOTABLE COLS="8" OPTS="L2,p7,7/8,i1" CDEF="s50,10,10,10,10,12,10,14">
                    <TTITLE>Table 1—Estimated Burden for Respondents</TTITLE>
                    <BOXHD>
                        <CHED H="1">
                            Information collection
                            <LI>(OMB control No.)</LI>
                        </CHED>
                        <CHED H="1">Number of respondents</CHED>
                        <CHED H="1">Frequency of response</CHED>
                        <CHED H="1">
                            Responses
                            <LI>per annum</LI>
                        </CHED>
                        <CHED H="1">
                            Burden
                            <LI>hour per</LI>
                            <LI>response</LI>
                        </CHED>
                        <CHED H="1">Annual burden hours</CHED>
                        <CHED H="1">
                            Hourly
                            <LI>cost per</LI>
                            <LI>response</LI>
                        </CHED>
                        <CHED H="1">Annual cost</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">SF 424 (4040-0004)</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT/>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SF-424B (4040-0007)</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT/>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SF-424D (4040-0009)</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT/>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SF 424A (4040-0006)</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT/>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SF-424C (4040-0008)</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT/>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SF LLL (4040-0013)</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT/>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Lobbying Form (4040-0013)</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT/>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Project Abstract Summary (4040-0019)</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT/>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HUD-424B</ENT>
                        <ENT>30,000</ENT>
                        <ENT>1.2</ENT>
                        <ENT>36,000</ENT>
                        <ENT>0.5</ENT>
                        <ENT>$18,000.00</ENT>
                        <ENT>$48.85</ENT>
                        <ENT>$879,300.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HUD-424CB</ENT>
                        <ENT>1,375</ENT>
                        <ENT>1.2</ENT>
                        <ENT>1,650</ENT>
                        <ENT>3</ENT>
                        <ENT>4,950.00</ENT>
                        <ENT>48.85</ENT>
                        <ENT>241,807.50</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HUD-424CBW</ENT>
                        <ENT>1,375</ENT>
                        <ENT>1.2</ENT>
                        <ENT>1,650</ENT>
                        <ENT>3</ENT>
                        <ENT>4,950.00</ENT>
                        <ENT>48.85</ENT>
                        <ENT>241,807.50</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HUD-424M</ENT>
                        <ENT>250</ENT>
                        <ENT>1.2</ENT>
                        <ENT>300</ENT>
                        <ENT>0.5</ENT>
                        <ENT>150.00</ENT>
                        <ENT>48.85</ENT>
                        <ENT>7,327.50</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HUD-2880</ENT>
                        <ENT>30,000</ENT>
                        <ENT>1.2</ENT>
                        <ENT>36,000</ENT>
                        <ENT>2</ENT>
                        <ENT>72,000.00</ENT>
                        <ENT>48.85</ENT>
                        <ENT>3,517,200.00</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="1938"/>
                        <ENT I="01">HUD-50070</ENT>
                        <ENT>30,000</ENT>
                        <ENT>1.2</ENT>
                        <ENT>36,000</ENT>
                        <ENT>0.25</ENT>
                        <ENT>9,000.00</ENT>
                        <ENT>48.85</ENT>
                        <ENT>439,650.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Rural Partners Certification</ENT>
                        <ENT>800</ENT>
                        <ENT>1.2</ENT>
                        <ENT>960</ENT>
                        <ENT>0.50</ENT>
                        <ENT>480.00</ENT>
                        <ENT>48.85</ENT>
                        <ENT>23,448.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HUD 50153</ENT>
                        <ENT>800</ENT>
                        <ENT>1.2</ENT>
                        <ENT>960</ENT>
                        <ENT>0.25</ENT>
                        <ENT>240.00</ENT>
                        <ENT>48.85</ENT>
                        <ENT>11,724.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HUD 2991</ENT>
                        <ENT>30,000</ENT>
                        <ENT>1.2</ENT>
                        <ENT>36,000</ENT>
                        <ENT>3</ENT>
                        <ENT>108,000.00</ENT>
                        <ENT>48.85</ENT>
                        <ENT>5,275,800.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HUD 2993</ENT>
                        <ENT>30,000</ENT>
                        <ENT>1.2</ENT>
                        <ENT>36,000</ENT>
                        <ENT>0.25</ENT>
                        <ENT>9,000.00</ENT>
                        <ENT>48.85</ENT>
                        <ENT>439,650.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Program specific requirements and rating factors (narrative and other attachments)</ENT>
                        <ENT>30,000</ENT>
                        <ENT>1.2</ENT>
                        <ENT>36,000</ENT>
                        <ENT>140</ENT>
                        <ENT>5,040,000.00</ENT>
                        <ENT>48.85</ENT>
                        <ENT>246,204,000.00</ENT>
                    </ROW>
                </GPOTABLE>
                <P>HUD bases the following estimates on historical experience. HUD estimates it takes an average of 30 working hours for HUD to complete its pre-award activities associated with competitive applications, including parts 1 and 2 of the pre-award process. This includes activities related to proper storage of related records. For purposes of this information collection request, HUD has used a GS 13 step 5 rate ($51.25 per hour) to monetize the value of HUD time. Therefore, the burden for pre-award activities is as follows using average response times:</P>
                <FP SOURCE="FP-2">30,000 applications * 30 hours * 1.2 frequency = 1,080,000 hours</FP>
                <FP SOURCE="FP-2">1,080,000 hours * $51.25 = $55,350,000</FP>
                <P>If the Department incurs any unique start-up or operational and maintenance costs with the collection of information covered by this ICR, HUD will include them on the request to OMB.</P>
                <HD SOURCE="HD1">B. Solicitation of Public Comment</HD>
                <P>
                    This notice is soliciting comments from members of the public and affecting agencies concerning the proposed collection of information to: (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; (2) Evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information; (3) Enhance the quality, utility, and clarity of the information to be collected; and (4) Minimize the burden of the collection of information on those who are to respond; including through the use of appropriate automated collection techniques or other forms of information technology, 
                    <E T="03">e.g.,</E>
                     permitting electronic submission of responses. (5) ways to minimize the burden of the collection of information on those who are to respond, including the use of automated collection techniques or other forms of information technology.
                </P>
                <HD SOURCE="HD1">C. Authority</HD>
                <P>The Paperwork Reduction Act of 1995, 44 U.S.C. chapter 35, as amended.</P>
                <SIG>
                    <NAME>Colette Pollard,</NAME>
                    <TITLE>Department Reports Management Officer, Office of Policy Development and Research, Chief Data Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00430 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>National Park Service</SUBAGY>
                <DEPDOC>[NPS-WASO-NAGPRA-NPS0037220; PPWOCRADN0-PCU00RP14.R50000]</DEPDOC>
                <SUBJECT>Notice of Intent To Repatriate Cultural Items: Indiana University, Bloomington, IN</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Park Service, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Native American Graves Protection and Repatriation Act (NAGPRA), Indiana University intends to repatriate certain cultural items that meet the definition of sacred objects and that have a cultural affiliation with the Indian Tribes or Native Hawaiian organizations in this notice.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Repatriation of the cultural items in this notice may occur on or after February 12, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Dr. Jayne-Leigh Thomas, Indiana University, Student Building 318, 701 E Kirkwood Avenue, Bloomington, IN 47405, telephone (812) 856-5315, email 
                        <E T="03">thomajay@indiana.edu.</E>
                    </P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This notice is published as part of the National Park Service's administrative responsibilities under NAGPRA. The determinations in this notice are the sole responsibility of Indiana University. The National Park Service is not responsible for the determinations in this notice. Additional information on the determinations in this notice, including the results of consultation, can be found in the summary or related records held by Indiana University.</P>
                <HD SOURCE="HD1">Description</HD>
                <P>The 27 cultural items were removed from unknown locations and given at various times to the university. The 27 sacred objects are nine rattles, four whistles, two necklaces, three dance accessories, three pipe bowls, three pipe stems, two otter skins, and one beaver pelt.</P>
                <HD SOURCE="HD1">Cultural Affiliation</HD>
                <P>The cultural items in this notice are connected to one or more identifiable earlier groups, tribes, peoples, or cultures. There is a relationship of shared group identity between the identifiable earlier groups, tribes, peoples, or cultures and one or more Indian Tribes or Native Hawaiian organizations. The following types of information were used to reasonably trace the relationship: anthropological information and expert opinion.</P>
                <HD SOURCE="HD1">Determinations</HD>
                <P>Pursuant to NAGPRA and its implementing regulations, and after consultation with the appropriate Indian Tribes and Native Hawaiian organizations, Indiana University has determined that:</P>
                <P>• The 27 cultural items described above are specific ceremonial objects needed by traditional Native American religious leaders for the practice of traditional Native American religions by their present-day adherents.</P>
                <P>• There is a relationship of shared group identity that can be reasonably traced between the cultural items and the Pawnee Nation of Oklahoma.</P>
                <HD SOURCE="HD1">Requests for Repatriation</HD>
                <P>
                    Additional, written requests for repatriation of the cultural items in this notice must be sent to the Responsible Official identified in 
                    <E T="02">ADDRESSES</E>
                    . Requests for repatriation may be submitted by any lineal descendant, Indian Tribe, or Native Hawaiian organization not identified in this notice who shows, by a preponderance of the evidence, that the requestor is a lineal descendant or a culturally affiliated Indian Tribe or Native Hawaiian organization.
                    <PRTPAGE P="1939"/>
                </P>
                <P>Repatriation of the cultural items in this notice to a requestor may occur on or after February 12, 2024. If competing requests for repatriation are received, Indiana University must determine the most appropriate requestor prior to repatriation. Requests for joint repatriation of the cultural items are considered a single request and not competing requests. Indiana University is responsible for sending a copy of this notice to the Indian Tribes and Native Hawaiian organizations identified in this notice.</P>
                <P>
                    <E T="03">Authority:</E>
                     Native American Graves Protection and Repatriation Act, 25 U.S.C. 3003, and the implementing regulations, 43 CFR 10.8, 10.10, and 10.14.
                </P>
                <SIG>
                    <DATED>Dated: January 4, 2024.</DATED>
                    <NAME>Melanie O'Brien,</NAME>
                    <TITLE>Manager, National NAGPRA Program.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00435 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4312-52-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>National Park Service</SUBAGY>
                <DEPDOC>[NPS-WASO-NAGPRA-NPS0037216; PPWOCRADN0-PCU00RP14.R50000]</DEPDOC>
                <SUBJECT>Notice of Inventory Completion Amendment: University of Minnesota Twin Cities, Minneapolis, MN; Minnesota Indian Affairs Council, St. Paul/Bemidji, MN; Science Museum of Minnesota, Saint Paul, MN; University of Colorado Museum (Boulder), Boulder, CO; Milwaukee Public Museum, Milwaukee, WI; Denver Art Museum, Denver, CO; Yale Peabody Museum, New Haven, CT; and Cleveland Museum of Art, Cleveland, OH</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Park Service, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; amendment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In accordance with the Native American Graves Protection and Repatriation Act (NAGPRA), the University of Minnesota Twin Cities (UMN); Minnesota Indian Affairs Council; Science Museum of Minnesota; University of Colorado Museum (Boulder); Milwaukee Public Museum; Denver Art Museum; Yale Peabody Museum; and Cleveland Museum of Art, hereafter the Collaborating Museums, have amended a Notice of Inventory Completion published in the 
                        <E T="04">Federal Register</E>
                         on February 24, 2023. This notice amends the number of associated funerary objects in a collection removed from Grant and Catron Counties, NM.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Repatriation of the human remains and associated funerary objects in this notice may occur on or after February 12, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Alejandra Peña Gutiérrez, Weisman Art Museum, University of Minnesota, 333 East River Road, Minneapolis, MN 55455, telephone (612) 624-5934, email 
                        <E T="03">apenagut@umn.edu.</E>
                    </P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This notice is published as part of the National Park Service's administrative responsibilities under NAGPRA. The determinations in this notice are the sole responsibility of the Collaborating Museums. The National Park Service is not responsible for the determinations in this notice. Additional information on the amendments and determinations in this notice, including the results of consultation, can be found in the inventory or related records held by the Collaborating Museums.</P>
                <HD SOURCE="HD1">Amendment</HD>
                <P>
                    This notice amends the determinations published in a Notice of Inventory Completion in the 
                    <E T="04">Federal Register</E>
                     (88 FR 11932-11934, February 24, 2023). Repatriation of the items in the original Notice of Inventory Completion has not occurred. This amendment is being made because physical inventory has identified additional items which were previously unreported, and because additional known items were subsequently identified to be associated funerary objects.
                </P>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,12,12,r150">
                    <TTITLE>Associated Funerary Objects</TTITLE>
                    <BOXHD>
                        <CHED H="1">Site</CHED>
                        <CHED H="1">
                            Original
                            <LI>number</LI>
                        </CHED>
                        <CHED H="1">
                            Amended
                            <LI>number</LI>
                        </CHED>
                        <CHED H="1">Amended description</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Cameron Creek and Warm Springs sites in Grant County, NM</ENT>
                        <ENT>571</ENT>
                        <ENT>575</ENT>
                        <ENT>One carved jade pendant, 92 stone tools or other items, two carved shell or stone items, 43 shell items, one shell pendant, 16 bead lots, seven turquoise item lots, 45 bone tools or other items, 191 ceramic vessels, one non-vessel ceramic item, 167 ceramic sherds or sherd lots, four organic items including charcoal, and one adobe lot. In addition, the Collaborating Museums continue to look for two ceramic vessels and two turquoise pendants which are documented but not physically located.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Galaz Ruin site in Grant County, NM</ENT>
                        <ENT>3,236</ENT>
                        <ENT>3,256</ENT>
                        <ENT>1,009 ceramic vessels, 23 ceramic non-vessel items, 798 ceramic sherds or sherd lots, three copper bell fragments, 51 bead lots, 738 stone tools or other items, 16 stone vessels, four lots of faunal material, 205 shell items, 51 turquoise items or lots, 260 bone tools or other items, 17 horn items, 13 mineral samples or objects, 20 unidentified organic items, and two unidentified residue samples. In addition, the Collaborating Museums continue to look for the missing 46 associated funerary objects, which are 34 pottery vessels, four bead lots, four shell adornments, one stone pendant, one stone axe, one stone palette, and one projectile point.</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Determinations (as Amended)</HD>
                <P>Pursuant to NAGPRA and its implementing regulations, and after consultation with the appropriate Indian Tribes and Native Hawaiian organizations, the Collaborating Museums have determined that:</P>
                <P>• The human remains described in this amended notice represent the physical remains of 198 individuals of Native American ancestry.</P>
                <P>
                    • The 4,234 objects described in this amended notice are reasonably believed to have been placed with or near 
                    <PRTPAGE P="1940"/>
                    individual human remains at the time of death or later as part of the death rite or ceremony.
                </P>
                <P>• There is a relationship of shared group identity that can be reasonably traced between the human remains and associated funerary objects described in this notice and the Hopi Tribe of Arizona; Mescalero Apache Tribe of the Mescalero Reservation, New Mexico; Okhay Owingeh, New Mexico; Pueblo of Acoma, New Mexico; Pueblo of Cochiti, New Mexico; Pueblo of Isleta, New Mexico; Pueblo of Jemez, New Mexico; Pueblo of Laguna, New Mexico; Pueblo of Nambe, New Mexico; Pueblo of Picuris, New Mexico; Pueblo of Pojoaque, New Mexico; Pueblo of San Felipe, New Mexico; Pueblo of San Ildefonso, New Mexico; Pueblo of Santa Ana, New Mexico; Pueblo of Santa Clara, New Mexico; Pueblo of Taos, New Mexico; Pueblo of Tesuque, New Mexico; Pueblo of Zia, New Mexico; Santo Domingo Pueblo; Ysleta del Sur Pueblo; and the Zuni Tribe of the Zuni Reservation, New Mexico.</P>
                <HD SOURCE="HD1">Requests for Repatriation</HD>
                <P>
                    Written requests for repatriation of the human remains and associated funerary objects in this notice must be sent to the Responsible Official identified in 
                    <E T="02">ADDRESSES</E>
                    . Requests for repatriation may be submitted by:
                </P>
                <P>1. Any one or more of the Indian Tribes or Native Hawaiian organizations identified in this notice.</P>
                <P>2. Any lineal descendant, Indian Tribe, or Native Hawaiian organization not identified in this notice who shows, by a preponderance of the evidence, that the requestor is a lineal descendant or a culturally affiliated Indian Tribe or Native Hawaiian organization.</P>
                <P>Repatriation of the human remains and associated funerary objects in this notice to a requestor may occur on or after February 12, 2024. If competing requests for repatriation are received, the Collaborating Museums must determine the most appropriate requestor prior to repatriation. Requests for joint repatriation of the human remains and associated funerary objects are considered a single request and not competing requests. The Collaborating Museums is responsible for sending a copy of this notice to the Indian Tribes and Native Hawaiian organizations identified in this notice.</P>
                <P>
                    <E T="03">Authority:</E>
                     Native American Graves Protection and Repatriation Act, 25 U.S.C. 3003, and the implementing regulations, 43 CFR 10.9, 10.10, 10.13, and 10.14.
                </P>
                <SIG>
                    <DATED>Dated: January 4, 2024.</DATED>
                    <NAME>Melanie O'Brien,</NAME>
                    <TITLE>Manager, National NAGPRA Program.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00431 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4312-52-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>National Park Service</SUBAGY>
                <DEPDOC>[NPS-WASO-NAGPRA-NPS0037221; PPWOCRADN0-PCU00RP14.R50000]</DEPDOC>
                <SUBJECT>Notice of Inventory Completion: Indiana University, Bloomington, IN</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Park Service, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Native American Graves Protection and Repatriation Act (NAGPRA), Indiana University (IU) has completed an inventory of human remains and has determined that there is a cultural affiliation between the human remains and Indian Tribes or Native Hawaiian organizations in this notice. The human remains were removed from an unknown location.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Repatriation of the human remains in this notice may occur on or after February 12, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Dr. Jayne-Leigh Thomas, Indiana University, Student Building 318, 701 E Kirkwood Avenue, Bloomington, IN 47405, telephone (812) 856-5315, email 
                        <E T="03">thomajay@indiana.edu.</E>
                    </P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This notice is published as part of the National Park Service's administrative responsibilities under NAGPRA. The determinations in this notice are the sole responsibility of Indiana University. The National Park Service is not responsible for the determinations in this notice. Additional information on the determinations in this notice, including the results of consultation, can be found in the inventory or related records held by Indiana University.</P>
                <HD SOURCE="HD1">Description</HD>
                <P>Human remains representing, at minimum, three individuals were removed from an unknown location. The collection was transferred to IU prior to 1956 by the Cincinnati Society for Natural History. No associated funerary objects are present.</P>
                <HD SOURCE="HD1">Cultural Affiliation</HD>
                <P>The human remains in this notice are connected to one or more identifiable earlier groups, tribes, peoples, or cultures. There is a relationship of shared group identity between the identifiable earlier groups, tribes, peoples, or cultures and one or more Indian Tribes or Native Hawaiian organizations. The following types of information were used to reasonably trace the relationship: oral history, expert opinion, and historical information.</P>
                <HD SOURCE="HD1">Determinations</HD>
                <P>Pursuant to NAGPRA and its implementing regulations, and after consultation with the appropriate Indian Tribes and Native Hawaiian organizations, Indiana University has determined that:</P>
                <P>• The human remains described in this notice represent the physical remains of three individuals of Native American ancestry.</P>
                <P>• There is a relationship of shared group identity that can be reasonably traced between the human remains and associated funerary objects described in this notice and The Muscogee (Creek) Nation.</P>
                <HD SOURCE="HD1">Requests for Repatriation</HD>
                <P>
                    Written requests for repatriation of the human remains in this notice must be sent to the Responsible Official identified in 
                    <E T="02">ADDRESSES</E>
                    . Requests for repatriation may be submitted by:
                </P>
                <P>1. Any one or more of the Indian Tribes or Native Hawaiian organizations identified in this notice.</P>
                <P>2. Any lineal descendant, Indian Tribe, or Native Hawaiian organization not identified in this notice who shows, by a preponderance of the evidence, that the requestor is a lineal descendant or a culturally affiliated Indian Tribe or Native Hawaiian organization.</P>
                <P>Repatriation of the human remains in this notice to a requestor may occur on or after February 12, 2024. If competing requests for repatriation are received, Indiana University must determine the most appropriate requestor prior to repatriation. Requests for joint repatriation of the human remains are considered a single request and not competing requests. Indiana University is responsible for sending a copy of this notice to the Indian Tribes and Native Hawaiian organizations identified in this notice.</P>
                <P>
                    <E T="03">Authority:</E>
                     Native American Graves Protection and Repatriation Act, 25 U.S.C. 3003, and the implementing regulations, 43 CFR 10.9, 10.10, and 10.14.
                </P>
                <SIG>
                    <DATED>Dated: January 4, 2024.</DATED>
                    <NAME>Melanie O'Brien,</NAME>
                    <TITLE>Manager, National NAGPRA Program.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00436 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4312-52-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="1941"/>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>National Park Service</SUBAGY>
                <DEPDOC>[NPS-WASO-NAGPRA-NPS0037218; PPWOCRADN0-PCU00RP14.R50000]</DEPDOC>
                <SUBJECT>Notice of Inventory Completion: University of California, Riverside, Riverside, CA</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Park Service, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Native American Graves Protection and Repatriation Act (NAGPRA), the University of California, Riverside has completed an inventory of human remains and has determined that there is a cultural affiliation between the human remains and Indian Tribes or Native Hawaiian organizations in this notice. The human remains were removed from Chatham County, GA.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Repatriation of the human remains in this notice may occur on or after February 12, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Megan Murphy, University of California, Riverside, 900 University Avenue, Riverside, CA 92517-5900, telephone (951) 827-6349, email 
                        <E T="03">megan.murphy@ucr.edu.</E>
                    </P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This notice is published as part of the National Park Service's administrative responsibilities under NAGPRA. The determinations in this notice are the sole responsibility of the University of California, Riverside. The National Park Service is not responsible for the determinations in this notice. Additional information on the determinations in this notice, including the results of consultation, can be found in the inventory or related records held by the University of California, Riverside.</P>
                <HD SOURCE="HD1">Description</HD>
                <P>Human remains representing, at minimum, one individual were removed from Chatham County, GA. In 1983, a partially fossilized human jaw representing one Native American adult individual was removed from the Forest River in Savannah, Georgia by Bobby Schauber, a local bait shrimper, who reportedly found the jaw in his shrimping net after dragging the river bed. Schauber displayed the human remains in a display case at the Coffee Bluff Fishing Camp where it was noticed by members of an amateur archeological society who contacted assistant professor, Clark Larson, at Northern Illinois University. The jaw was subsequently studied at the Center for Study of Early Man, University of Maine under the direction of Robson Bonnichsen. In 1988, Dr. R.E. Taylor, director of the University of California, Riverside Radiocarbon Laboratory, obtained a sample of the individual for radiocarbon dating. The residual sample material was subsequently stored by Dr. Taylor at an off-campus storage facility and never reported to the UCR NAGPRA Program Staff. In February of 2022, the sample from the individual was discovered by NAGPRA Program Staff during a collections inventory. No associated funerary objects were found with the individual.</P>
                <HD SOURCE="HD1">Cultural Affiliation</HD>
                <P>The human remains in this notice are connected to one or more identifiable earlier groups, tribes, peoples, or cultures. There is a relationship of shared group identity between the identifiable earlier groups, tribes, peoples, or cultures and one or more Indian Tribes or Native Hawaiian organizations. The following types of information were used to reasonably trace the relationship: archeological information, geographical information, historical information, kinship, oral tradition, and expert opinion.</P>
                <HD SOURCE="HD1">Determinations</HD>
                <P>Pursuant to NAGPRA and its implementing regulations, and after consultation with the appropriate Indian Tribes and Native Hawaiian organizations, the University of California, Riverside has determined that:</P>
                <P>• The human remains described in this notice represent the physical remains of one individual of Native American ancestry.</P>
                <P>• There is a relationship of shared group identity that can be reasonably traced between the human remains described in this notice and the Alabama-Quassarte Tribal Town; Catawba Indian Nation; Eastern Band of Cherokee Indians; Kialegee Tribal Town; Miccosukee Tribe of Indians; Poarch Band of Creek Indians; Seminole Tribe of Florida; The Muscogee (Creek) Nation; The Seminole Nation of Oklahoma; and the Thlopthlocco Tribal Town.</P>
                <HD SOURCE="HD1">Requests for Repatriation</HD>
                <P>
                    Written requests for repatriation of the human remains in this notice must be sent to the Responsible Official identified in 
                    <E T="02">ADDRESSES</E>
                    . Requests for repatriation may be submitted by:
                </P>
                <P>1. Any one or more of the Indian Tribes or Native Hawaiian organizations identified in this notice.</P>
                <P>2. Any lineal descendant, Indian Tribe, or Native Hawaiian organization not identified in this notice who shows, by a preponderance of the evidence, that the requestor is a lineal descendant or a culturally affiliated Indian Tribe or Native Hawaiian organization.</P>
                <P>Repatriation of the human remains in this notice to a requestor may occur on or after February 12, 2024. If competing requests for repatriation are received, the University of California, Riverside must determine the most appropriate requestor prior to repatriation. Requests for joint repatriation of the human remains are considered a single request and not competing requests. The University of California, Riverside is responsible for sending a copy of this notice to the Indian Tribes and Native Hawaiian organizations identified in this notice.</P>
                <P>
                    <E T="03">Authority:</E>
                     Native American Graves Protection and Repatriation Act, 25 U.S.C. 3003, and the implementing regulations, 43 CFR 10.9, 10.10, and 10.14.
                </P>
                <SIG>
                    <DATED>Dated: January 4, 2024.</DATED>
                    <NAME>Melanie O'Brien,</NAME>
                    <TITLE>Manager, National NAGPRA Program.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00433 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4312-52-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>National Park Service</SUBAGY>
                <DEPDOC>[NPS-WASO-NAGPRA-NPS0037217; PPWOCRADN0-PCU00RP14.R50000]</DEPDOC>
                <SUBJECT>Notice of Inventory Completion: University of California, Riverside, Riverside, CA</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Park Service, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Native American Graves Protection and Repatriation Act (NAGPRA), the University of California, Riverside has completed an inventory of human remains and associated funerary objects and has determined that there is a cultural affiliation between the human remains and associated funerary objects and Indian Tribes or Native Hawaiian organizations in this notice. The human remains and associated funerary objects were removed from Riverside, CA.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Repatriation of the human remains and associated funerary objects in this notice may occur on or after February 12, 2024.</P>
                </DATES>
                <ADD>
                    <PRTPAGE P="1942"/>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Megan Murphy, University of California, Riverside, 900 University Avenue, Riverside, CA 92517-5900, telephone (951) 827-6349, email 
                        <E T="03">megan.murphy@ucr.edu.</E>
                    </P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This notice is published as part of the National Park Service's administrative responsibilities under NAGPRA. The determinations in this notice are the sole responsibility of the University of California, Riverside. The National Park Service is not responsible for the determinations in this notice. Additional information on the determinations in this notice, including the results of consultation, can be found in the inventory or related records held by the University of California, Riverside.</P>
                <HD SOURCE="HD1">Description</HD>
                <P>Human remains representing, at minimum, one individual were removed from Riverside County, CA. In 1972, the human remains of at least one Native American individual were removed from archeological site CA-RIV-64 (also known as the Indian Wells Site) during an archeological field school for students of Cabrillo College and the University of California, Riverside. The human remains, identified as a human canine tooth, were not initially identified as human in the field, but were noted as being possibly human in the original catalog records. This identification went unnoticed until 2023 during consultation with Tribal representatives and an osteological consultant, who confirmed the tooth to be human. During consultation the Tribal representatives also identified associated funerary objects. The seven lots of associated funerary objects are one lot of ceramics, one lot of clay, one lot of lithic artifacts, one lot of animal bone, one lot of floral/organic materials, one lot of fire-altered rock, and one lot of geological materials.</P>
                <P>Human remains representing, at minimum, one individual were removed from Riverside County, CA. In 1985, the human remains of at least one Native American individual were removed by the University of California, Riverside Archaeological Research Unit under direction of Philip Wilke during the excavation of Burns Ranch (also known as Rancho del Gato, and La Quinta Cove, archeological sites CA-RIV-1179 and CA-RIV-2827). The excavation was contracted by the Crystal Canyon Country Club ahead of the building of a housing property and golf course that would destroy the sites. Native American human remains of at least nine individuals were removed during excavation and a sample of human bone was submitted to the UCR Radiocarbon Laboratory which yielded an age of 720 +/−120 years BP. According to catalog records, 51 catalog numbers representing human bone and associated funerary objects, were reportedly removed from the collection to be reburied in La Quinta in 1990 at the request of the Tribe who was monitoring the project. During NAGPRA consultation in 2023, an osteological consultant identified additional human bone fragments and cremation elements in the collection which were not returned in 1990. Tribal representatives also identified associated funerary objects that were also not reburied in 1990. It is unclear how many individuals are still represented in the collection as the original catalogs do not differentiate between specific individuals and the human remains are too fragmentary to make a reliable determination beyond a minimum of one individual. The 15 associated funerary objects are two lots of animal bone, two lots of ceramics, two lots of lithic materials and tools, one lot of metal objects, one lot of shell beads, one lot of basketry, two lots of other organic/floral materials, one lot of geological materials, two lots of unmodified shell, and one lot of fire-altered rock.</P>
                <P>Human remains representing, at minimum, one individual were removed from Riverside County, CA. In 1990, the University of California, Riverside Archaeological Research Unit was contracted by the Chateau Development Company to conduct an archeological assessment of a tract of land in the city of La Quinta ahead of plans for a residential development. During the archeological excavation, five archeological sites were identified including CA-RIV-1182, CA-RIV-3143, CA-RIV-3144, CA-RIV-3868, and CA-RIV-3882. A cremation locus was identified in the boundaries of CA-RIV-3144 and the human remains of one adult, male Native American were removed from the surface of the area. Following the conclusion of the archeological excavations, 2,648 cremated human bone fragments were returned to a local Tribe and were reburied nearby in La Quinta on August 16, 1990. The funerary objects buried with the individual, however, were not returned and remained in the collections housed at UCR. In 2023, during Tribal consultation, an osteological consulted identified additional human remains that were still present in the collections. Tribal representatives also identified a number of funerary objects present in the collections. The 16 associated funerary objects are three lots of ceramics, three lots of lithics, two lots of shell beads, three lots of faunal remains, three lots of floral material, and two lots of unmodified shell.</P>
                <P>Human remains representing, at minimum, three individuals were removed from Riverside County, CA. In 1989, the University of California, Riverside Archaeological Research Unit was contracted by the Transpacific Development Company to conduct an archeological assessment of a tract of land at the northeast corner of Washington Street and State Highway 111 in the city of La Quinta. During the archeological excavation, which was in the vicinity of the historic Cahuilla village of Pal Kavinic, six archeological sites were identified including CA-RIV-2200, CA-RIV-2936, CA-RIV-3679, CA-RIV-3680, CA-RIV-3681, and CA-RIV-3682. One human tarsal bone was removed from CA-RIV-3682 but was not identified as human during the project analysis. In 2023, during Tribal consultation, an osteological consultant identified the bone as human. Additionally, the osteologist identified one cranial fragment and one juvenile long-bone fact from CA-RIV-3680 and one humerus fragment from CA-RIV-3681. Tribal representatives also identified associated funerary objects in the collection. The 19 associated funerary objects are three lots of animal bones, three lots of ceramic, two lots of lithics, one lot of metal, two lots of shell objects, two lots of floral material, one lot of other organic material, two lots of geological materials, two lots of unmodified shell, and one lot of fire-altered rock.</P>
                <P>
                    Human remains representing, at minimum, two individuals were removed from Riverside County, CA. In 1992, the Keith Companies, Archaeology Division, were contracted by the Shadowridge Creek Country Club to conduct a field survey for a parcel of land proposed for the development of a golf course and residential area. During the survey two prehistoric sites were identified, CA-RIV-785 and CA-RIV-4729, and surface materials were collected. At CA-RIV-785, archeologists observed a hearth feature and collected ceramic sherds, animal bone, and cremated human remains from the surface. They also collected surface materials from a small nearby scatter assigned the trinomial CA-RIV-4729. These collections were subsequently housed at UCR. In 1993, a Tribe requested that the Keith Companies return the cremated human bone and associated shell beads that were collected from CA-RIV-785 to the Tribe 
                    <PRTPAGE P="1943"/>
                    for reburial. On October 29, 1993, Tribal representatives for the Tribe reburied 118 human bone elements and five associated shell beads that were returned to them. The other materials in the collection, however, remained at UCR and Tribes were not given the opportunity to review them. In 2023, during NAGPRA consultation, an osteological consultant identified additional human remains in the collections that were not returned to the Tribe in 1993, including one cremated infant bone and cremated adult bone fragments. Tribal representatives also identified additional associated funerary objects in the collection that were not returned in 1993. The 10 associated funerary objects are two lots of ceramic, one lot of glass, two lots of lithic flakes and objects, one lot of metal, one lot of shell beads, two lots of animal bone, and one lot of floral material and charcoal.
                </P>
                <HD SOURCE="HD1">Cultural Affiliation</HD>
                <P>The human remains and associated funerary objects in this notice are connected to one or more identifiable earlier groups, tribes, peoples, or cultures. There is a relationship of shared group identity between the identifiable earlier groups, tribes, peoples, or cultures and one or more Indian Tribes or Native Hawaiian organizations. The following types of information were used to reasonably trace the relationship: archeological information, geographical information, historical information, kinship, oral tradition, and expert opinion.</P>
                <HD SOURCE="HD1">Determinations</HD>
                <P>Pursuant to NAGPRA and its implementing regulations, and after consultation with the appropriate Indian Tribes and Native Hawaiian organizations, the University of California, Riverside has determined that:</P>
                <P>• The human remains described in this notice represent the physical remains of eight individuals of Native American ancestry.</P>
                <P>• The 67 objects described in this notice are reasonably believed to have been placed with or near individual human remains at the time of death or later as part of the death rite or ceremony.</P>
                <P>
                    • There is a relationship of shared group identity that can be reasonably traced between the human remains and associated funerary objects described in this notice and the Agua Caliente Band of Cahuilla Indians of the Agua Caliente Indian Reservation, California; Augustine Band of Cahuilla Indians, California; Cabazon Band of Cahuilla Indians (
                    <E T="03">Previously</E>
                     listed as Cabazon Band of Mission Indians, California); Cahuilla Band of Indians; Los Coyotes Band of Cahuilla and Cupeno Indians, California; Morongo Band of Mission Indians, California; Ramona Band of Cahuilla, California; Santa Rosa Band of Cahuilla Indians, California; and the Torrez Martinez Desert Cahuilla Indians, California.
                </P>
                <HD SOURCE="HD1">Requests for Repatriation</HD>
                <P>
                    Written requests for repatriation of the human remains and associated funerary objects in this notice must be sent to the Responsible Official identified in 
                    <E T="02">ADDRESSES</E>
                    . Requests for repatriation may be submitted by:
                </P>
                <P>1. Any one or more of the Indian Tribes or Native Hawaiian organizations identified in this notice.</P>
                <P>2. Any lineal descendant, Indian Tribe, or Native Hawaiian organization not identified in this notice who shows, by a preponderance of the evidence, that the requestor is a lineal descendant or a culturally affiliated Indian Tribe or Native Hawaiian organization.</P>
                <P>Repatriation of the human remains and associated funerary objects in this notice to a requestor may occur on or after February 12, 2024. If competing requests for repatriation are received, the University of California, Riverside must determine the most appropriate requestor prior to repatriation. Requests for joint repatriation of the human remains and associated funerary objects are considered a single request and not competing requests. The University of California, Riverside is responsible for sending a copy of this notice to the Indian Tribes and Native Hawaiian organizations identified in this notice.</P>
                <P>
                    <E T="03">Authority:</E>
                     Native American Graves Protection and Repatriation Act, 25 U.S.C. 3003, and the implementing regulations, 43 CFR 10.9, 10.10, and 10.14.
                </P>
                <SIG>
                    <DATED>Dated: January 4, 2024.</DATED>
                    <NAME>Melanie O'Brien,</NAME>
                    <TITLE>Manager, National NAGPRA Program. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00432 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4312-52-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>National Park Service</SUBAGY>
                <DEPDOC>[NPS-WASO-NAGPRA-NPS0037219; PPWOCRADN0-PCU00RP14.R50000]</DEPDOC>
                <SUBJECT>Notice of Inventory Completion: Denver Museum of Nature &amp; Science, Denver, CO</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Park Service, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Native American Graves Protection and Repatriation Act (NAGPRA), the Denver Museum of Nature &amp; Science (DMNS) has completed an inventory of human remains and has determined that there is a cultural affiliation between the human remains and Indian Tribes or Native Hawaiian organizations in this notice. The human remains were removed from the Magic Mountain site, 5JF223, Jefferson County, CO.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Repatriation of the human remains in this notice may occur on or after February 12, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Michele L. Koons, Curator of Archaeology, Denver Museum of Nature &amp; Science, 2001 Colorado Boulevard, Denver, CO 80205, telephone (303) 370-6457, email 
                        <E T="03">Michele.Koons@dmns.org.</E>
                    </P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This notice is published as part of the National Park Service's administrative responsibilities under NAGPRA. The determinations in this notice are the sole responsibility of the Denver Museum of Nature &amp; Science. The National Park Service is not responsible for the determinations in this notice. Additional information on the determinations in this notice, including the results of consultation, can be found in the inventory or related records held by the Denver Museum of Nature &amp; Science.</P>
                <HD SOURCE="HD1">Description</HD>
                <P>Between 1939 and 1941, human remains representing, at minimum, one individual were removed from the Magic Mountain site, 5JF223, in Jefferson County, CO, by Harold and Elizabeth (Betty) Huscher. In 1940, the Huschers donated the collection to the Colorado Museum of Natural History, now DMNS. In 2019, DMNS staff processed several bags labeled “faunal remains” from the Huscher excavation. Analysis shows that nine of those “faunal remains” are actually human bone fragments (A540.18-R). The Huschers excavated animal remains from the site and inadvertently mixed in human remains. The bone fragments are associated with the Early Ceramic period occupational component of the site, which dates approximately 200 to 1000 C.E. No associated funerary objects are present.</P>
                <P>
                    Between 1971 and 1972, human remains representing, at minimum, five individuals were removed from the Magic Mountain site, 5JF223, in Jefferson County, CO, by Metropolitan State College of Denver (now the Metropolitan State University of Denver). In 2007, the Center of 
                    <PRTPAGE P="1944"/>
                    Southwest Studies, Fort Lewis College, acquired part of the Magic Mountain collection from the Rimrocker Historical Society. The Rimrock Historical Society originally accepted the materials as part of a larger donation in 1998 from Dr. Jonathan Kent of Metropolitan State College of Denver (now the Metropolitan State University of Denver). In April 2023, DMNS staff learned of the Center of Southwest Studies, Fort Lewis College Magic Mountain collection. Both parties agreed to transfer the materials to DMNS in 2023 since the Museum holds the majority of the collections from the site. Prior to transfer analysis conducted by Dr. Dawn Mulhern identified 31 bone fragments. No associated funerary objects are present.
                </P>
                <HD SOURCE="HD1">Cultural Affiliation</HD>
                <P>The human remains in this notice are connected to one or more identifiable earlier groups, tribes, peoples, or cultures. There is a relationship of shared group identity between the identifiable earlier groups, tribes, peoples, or cultures and one or more Indian Tribes or Native Hawaiian organizations. The following types of information were used to reasonably trace the relationship: anthropological information, archeological information, biological information, folklore, geographical information, historical information, kinship, linguistics, oral tradition, other relevant information, or expert opinion.</P>
                <HD SOURCE="HD1">Determinations</HD>
                <P>Pursuant to NAGPRA and its implementing regulations, and after consultation with the appropriate Indian Tribes and Native Hawaiian organizations, the Denver Museum of Nature &amp; Science has determined that:</P>
                <P>• The human remains described in this notice represent the physical remains of six individuals of Native American ancestry.</P>
                <P>• There is a relationship of shared group identity that can be reasonably traced between the human remains and associated funerary objects described in this notice and the Cheyenne and Arapaho Tribes, Oklahoma; Northern Arapaho Tribe of the Wind River Reservation, Wyoming; Northern Cheyenne Tribe of the Northern Cheyenne Indian Reservation, Montana; Southern Ute Indian Tribe of the Southern Ute Reservation, Colorado; Ute Indian Tribe of the Uintah &amp; Ouray Reservation, Utah; and the Ute Mountain Ute Tribe.</P>
                <HD SOURCE="HD1">Requests for Repatriation</HD>
                <P>
                    Written requests for repatriation of the human remains in this notice must be sent to the Responsible Official identified in 
                    <E T="02">ADDRESSES</E>
                    . Requests for repatriation may be submitted by:
                </P>
                <P>1. Any one or more of the Indian Tribes or Native Hawaiian organizations identified in this notice.</P>
                <P>2. Any lineal descendant, Indian Tribe, or Native Hawaiian organization not identified in this notice who shows, by a preponderance of the evidence, that the requestor is a lineal descendant or a culturally affiliated Indian Tribe or Native Hawaiian organization.</P>
                <P>Repatriation of the human remains in this notice to a requestor may occur on or after February 12, 2024. If competing requests for repatriation are received, the Denver Museum of Nature &amp; Science must determine the most appropriate requestor prior to repatriation. Requests for joint repatriation of the human remains are considered a single request and not competing requests. The Denver Museum of Nature &amp; Science is responsible for sending a copy of this notice to the Indian Tribes and Native Hawaiian organizations identified in this notice.</P>
                <P>
                    <E T="03">Authority:</E>
                     Native American Graves Protection and Repatriation Act, 25 U.S.C. 3003, and the implementing regulations, 43 CFR 10.9, 10.10, and 10.14.
                </P>
                <SIG>
                    <DATED>Dated: January 4, 2024.</DATED>
                    <NAME>Melanie O'Brien,</NAME>
                    <TITLE>Manager, National NAGPRA Program.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00434 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4312-52-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">INTERNATIONAL TRADE COMMISSION</AGENCY>
                <DEPDOC>[USITC SE-24-002]</DEPDOC>
                <SUBJECT>Sunshine Act Meetings</SUBJECT>
                <PREAMHD>
                    <HD SOURCE="HED">Agency Holding the Meeting:</HD>
                    <P>United States International Trade Commission.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">TIME AND DATE:</HD>
                    <P>January 19, 2024 at 9:30 a.m.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">PLACE:</HD>
                    <P>Room 101, 500 E Street SW, Washington, DC 20436, Telephone: (202) 205-2000.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">STATUS:</HD>
                    <P>Open to the public.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">MATTERS TO BE CONSIDERED:</HD>
                    <P/>
                    <P>1. Agendas for future meetings: none.</P>
                    <P>2. Minutes.</P>
                    <P>3. Ratification List.</P>
                    <P>4. Commission vote on Inv. Nos. 701-TA-576-577 and 731-TA-1362-1367 (Review) (Cold-Drawn Mechanical Tubing (CDMT) from China, Germany, India, Italy, South Korea, and Switzerland). The Commission currently is scheduled to complete and file its determinations and views of the Commission on February 9, 2024.</P>
                    <P>5. Outstanding action jackets: none.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">CONTACT PERSON FOR MORE INFORMATION: </HD>
                    <P>Sharon Bellamy, Supervisory Hearings and Information Officer, 202-205-2000.</P>
                    <P>The Commission is holding the meeting under the Government in the Sunshine Act, 5 U.S.C. 552(b). In accordance with Commission policy, subject matter listed above, not disposed of at the scheduled meeting, may be carried over to the agenda of the following meeting.</P>
                </PREAMHD>
                <SIG>
                    <P>By order of the Commission.</P>
                    <DATED>Issued: January 9, 2024.</DATED>
                    <NAME>Sharon Bellamy,</NAME>
                    <TITLE>Supervisory Hearings and Information Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-00544 Filed 1-9-24; 11:15 am]</FRDOC>
            <BILCOD>BILLING CODE 7020-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF LABOR</AGENCY>
                <SUBAGY>Bureau of Labor Statistics</SUBAGY>
                <SUBJECT>Information Collection Activities; Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Labor Statistics, Department of Labor.</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>
                        The Department of Labor, as part of its continuing effort to reduce paperwork and respondent burden, conducts a pre-clearance consultation program to provide the general public and Federal agencies with an opportunity to comment on proposed and/or continuing collections of information in accordance with the Paperwork Reduction Act of 1995. This program helps to ensure that requested data can be provided in the desired format, reporting burden (time and financial resources) is minimized, collection instruments are clearly understood, and the impact of collection requirements on respondents can be properly assessed. The Bureau of Labor Statistics (BLS) is soliciting comments concerning the proposed revision of the “Quarterly Census of Employment and Wages Business Supplement.” A copy of the proposed information collection request can be obtained by contacting the individual listed below in the 
                        <E T="02">Addresses</E>
                         section of this notice.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Written comments must be submitted to the office listed in the 
                        <E T="02">Addresses</E>
                         section of this notice on or before March 11, 2024.
                    </P>
                </DATES>
                <ADD>
                    <PRTPAGE P="1945"/>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Send comments to Carol Rowan, BLS Clearance Officer, Division of Management Systems, Bureau of Labor Statistics, Room G225, 2 Massachusetts Avenue NE, Washington, DC 20212. Written comments also may be transmitted by email to 
                        <E T="03">BLS_PRA_Public@bls.gov</E>
                        .
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Carol Rowan, BLS Clearance Officer, at 202-691-7628 (this is not a toll free number). (See 
                        <E T="02">ADDRESSES</E>
                         section.)
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>The Quarterly Census of Employment and Wages Business Supplement (QBS) is a versatile collection instrument designed to capture information on the US economy quickly and efficiently. The QBS collection is designed to incorporate new questionnaires as the need arises to allow BLS to collect and publish information quickly so that stakeholders and data users can understand the impact of specific events, or economic issues of relevance, on the US economy.</P>
                <P>The BLS will primarily use the Annual Refiling Survey (ARS) as a platform for conducting the QBS. Each year, the BLS Quarterly Census of Employment and Wages (QCEW) Program conducts the ARS by reaching out to approximately 1.5 million establishments requesting verification of their main business activity, and their mailing and physical location addresses. The fully web-based ARS allows for an accelerated timeframe for collection and provides a low-cost platform for conducting the quick, short surveys of the QBS. The QBSs accompanying the ARS have little data collection overhead, leveraging the respondent contact process undertaken as part of the production ARS. QBS respondents already logged into the ARS secure website are directed to a QBS and asked to answer a limited number of additional survey questions after completing the ARS. QBS respondents that are not in the ARS are solicited using established contact methods (email and/or printed letters) and directed to a stand-alone interface to access and answer the QBS questions online.</P>
                <HD SOURCE="HD1">II. Current Action</HD>
                <P>Office of Management and Budget clearance is being sought for a revision of the QCEW Business Supplement (QBS).</P>
                <P>The QBS is designed to encourage a fast response and minimize respondent burden on the public by limiting the number of questions on each survey and by asking questions that respondents should be able to answer without research or referring to records. In this manner, BLS can provide information that is needed quickly and is not collected elsewhere. The QBS will incorporate new questionnaires as the need for data arises, as frequently as twice a year. The BLS plans to conduct multiple small surveys under the QBS clearance. The 2024 survey will focus on establishments' telework policies and practices, recent experiences in hiring, and how they advertise vacancies. These questions were previously asked in the 2022 QBS collected under this clearance (the 2022 Business Response Survey). Asking these questions again, a full two years later, will provide an understanding of how these business operations have changed.</P>
                <HD SOURCE="HD1">III. Desired Focus of Comments</HD>
                <P>The Bureau of Labor Statistics is particularly interested in comments that:</P>
                <P>• 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>• 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>• Enhance the quality, utility, and clarity of the information to be collected.</P>
                <P>
                    • 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.
                </P>
                <P>
                    <E T="03">Title of Collection:</E>
                     QCEW Business Supplement.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1220-0198.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Revision of a currently approved collection.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Business or other for-profit, not-for-profit institutions, and farms.
                </P>
                <P>
                    <E T="03">Total Number of Respondents:</E>
                     80,000.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     Once.
                </P>
                <P>
                    <E T="03">Total Responses:</E>
                     80,000.
                </P>
                <P>
                    <E T="03">Average Time per Response:</E>
                     5 minutes.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     6,667 hours.
                </P>
                <P>Comments submitted in response to this notice will be summarized and/or included in the request for Office of Management and Budget approval of the information collection request; they also will become a matter of public record.</P>
                <SIG>
                    <DATED>Signed at Washington, DC, on January 5, 2024.</DATED>
                    <NAME>Eric Molina,</NAME>
                    <TITLE>Chief, Division of Management Systems, Branch of Policy Analysis.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00374 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4510-24-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 5 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 David Travis, Office of Guidelines &amp; Panel Operations, National Endowment for the Arts, Washington, DC 20506; 
                        <E T="03">travisd@arts.gov,</E>
                         or call 202-682-5001.
                    </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 March 11, 2022, these sessions will be closed to the public pursuant to 5 U.S.C. 10.</P>
                <P>The upcoming meetings are:</P>
                <P>
                    <E T="03">NEA Jazz Masters Fellowships Panel A</E>
                     (review of applications): This meeting will be closed.
                </P>
                <P>
                    <E T="03">Date and time:</E>
                     February 6, 2024; 2:00 p.m. to 4:00 p.m.
                </P>
                <P>
                    <E T="03">NEA Jazz Masters Fellowships Panel B</E>
                     (review of applications): This meeting will be closed.
                </P>
                <P>
                    <E T="03">Date and time:</E>
                     February 6, 2024; 2:00 p.m. to 4:00 p.m.
                </P>
                <P>
                    <E T="03">
                        Shakespeare in American Communities Cooperative Agreement 
                        <PRTPAGE P="1946"/>
                        Panel
                    </E>
                     (review of applications): This meeting will be closed.
                </P>
                <P>
                    <E T="03">Date and time:</E>
                     February 13, 2024; 1:00 p.m. to 3:00 p.m.
                </P>
                <P>
                    <E T="03">NEA Big Read Cooperative Agreement Panel</E>
                     (review of applications): This meeting will be closed.
                </P>
                <P>
                    <E T="03">Date and time:</E>
                     February 14, 2024; 2:00 p.m. to 4:00 p.m.
                </P>
                <P>
                    <E T="03">Creative Placemaking Technical Assistance</E>
                     (review of applications): This meeting will be closed.
                </P>
                <P>
                    <E T="03">Date and time:</E>
                     February 15, 2024; 2:00 p.m. to 4:00 p.m.
                </P>
                <SIG>
                    <DATED>Dated: January 8, 2024.</DATED>
                    <NAME>David Travis,</NAME>
                    <TITLE>Specialist, National Endowment for the Arts.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00429 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7537-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">NATIONAL FOUNDATION ON THE ARTS AND HUMANITIES</AGENCY>
                <SUBAGY>National Endowment for the Humanities</SUBAGY>
                <SUBJECT>Civil Penalty Adjustments for 2024</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Endowment for the Humanities; National Foundation on the Arts and the Humanities.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of civil penalty adjustments for 2024.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The National Endowment for the Humanities (NEH) is giving notice of the adjusted maximum and minimum civil monetary penalties that may be imposed for violations of its New Restrictions on Lobbying and Program Fraud Civil Remedies Act regulations to reflect the requirements of the Federal Civil Penalties Inflation Adjustment Act of 1990, as amended by the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015. The updated penalty amounts are adjusted for inflation and are effective from January 15, 2024, through January 14, 2025.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The updated civil penalties in this notice are applicable to penalties assessed on or after January 15, 2024, if the associated violations occurred after November 2, 2015.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Elizabeth Voyatzis, Deputy General Counsel, Office of the General Counsel, National Endowment for the Humanities, 400 7th Street SW, Room 4060, Washington, DC 20506; (202) 606-8322; 
                        <E T="03">gencounsel@neh.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">1. Background</HD>
                <P>
                    The Federal Civil Penalties Inflation Adjustment Act of 1990, as amended by the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015 (the Inflation Adjustment Act) 
                    <SU>1</SU>
                    <FTREF/>
                     directs each Executive agency to make an annual inflation adjustment for each civil monetary penalty provided by law within the jurisdiction of the agency, and to publish notice of each such adjustment in the 
                    <E T="04">Federal Register</E>
                    . An agency adjusts a civil monetary penalty by increasing the maximum amount of such penalty (or the range of minimum and maximum amounts, as applicable) by the percentage by which the Consumer Price Index for All Urban Consumers (CPI-U) for the month of October preceding the date of adjustment (in this case, October 2023) exceeds the CPI-U for the October one year prior to the October immediately preceding the date of the adjustment (in this case, October 2022), then rounding each amount to the nearest dollar.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         28 U.S.C. 2461 note.
                    </P>
                </FTNT>
                <P>
                    NEH administers two civil monetary penalties subject to adjustment pursuant to the Inflation Adjustment Act: A civil monetary penalty that NEH may impose for violation of its New Restrictions on Lobbying regulation (the Lobbying Civil Monetary Penalty) 
                    <SU>2</SU>
                    <FTREF/>
                     and a civil monetary penalty that NEH may impose under its Program Fraud Civil Remedies Act Regulations (the PFCRA Civil Monetary Penalty).
                    <SU>3</SU>
                    <FTREF/>
                     NEH made the initial “catch-up” adjustments to the Lobbying Civil Monetary Penalty for years 2016-2020 when it amended its New Restrictions on Lobbying regulation on April 21, 2020,
                    <SU>4</SU>
                    <FTREF/>
                     and to the PFCRA Civil Monetary Penalty for years 2016-2021 when it adopted its Program Fraud Civil Monetary Penalties Act regulations on August 13, 2021.
                    <SU>5</SU>
                    <FTREF/>
                     NEH then adjusted the amount of those civil monetary penalties accordingly when it codified the statutory formula for inflation adjustments in NEH's New Restrictions on Lobbying and Program Fraud Civil Remedies Act regulations on March 30, 2023.
                    <SU>6</SU>
                    <FTREF/>
                     Each regulation provides for subsequent annual adjustment of its respective civil monetary penalty by notice in the 
                    <E T="04">Federal Register</E>
                    .
                    <SU>7</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         45 CFR 1168.400(a), (b), (e).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         45 CFR 1174.3(a), (b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         85 FR 22025.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         86 FR 44626.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         88 FR 18998.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         45 CFR 1168.400(g), (h), 1174.3(f), (g).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">2. 2024 Adjustments for Inflation</HD>
                <P>
                    OMB has issued guidance on implementing and calculating the 2024 adjustment under the Inflation Adjustment Act.
                    <SU>8</SU>
                    <FTREF/>
                     Per this guidance, the CPI-U adjustment multiplier for this annual adjustment is 1.03241.
                    <SU>9</SU>
                    <FTREF/>
                     The post-adjustment penalty or range is obtained by multiplying the pre-adjustment penalty or range by the percent change in the CPI-U over the relevant time period and rounding to the nearest dollar. Between October 2022 and October 2023, the CPI-U increased by a multiplier of 103.241% Therefore, NEH will adjust each civil monetary penalty amount by multiplying it by 1.03241 and rounding to the nearest dollar.
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         Office of Management and Budget (OMB) Memorandum M-24-07 (December 19, 2023).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD2">A. 2024 Adjustment To Lobbying Civil Monetary Penalty</HD>
                <P>For 2023, the Lobbying Civil Monetary Penalty had a minimum amount of $23,727 and a maximum amount of $237,268. Therefore, the adjusted minimum Lobbying Civil Monetary Penalty for 2024 is $24,496 ($23,727 multiplied by 1.03241) and the adjusted maximum Lobbying Civil Monetary Penalty for 2024 is $244,958 ($237,268 multiplied by 1.03241).</P>
                <P>Thus, the Lobbying Civil Monetary Penalty, following the 2024 adjustment, has a minimum amount of $24,496 and a maximum amount of $244,958.</P>
                <HD SOURCE="HD2">B. 2024 Adjustment to PFCRA Civil Monetary Penalty</HD>
                <P>For 2023, the PFCRA Civil Monetary Penalty had a maximum amount of $13,508. Therefore, the new, post-adjustment maximum penalty for 2024 under NEH's PFCRA regulation is $13,946 ($13,508 multiplied by 1.03241).</P>
                <SIG>
                    <DATED>Dated: January 8, 2024.</DATED>
                    <NAME>Jessica Graves,</NAME>
                    <TITLE>Paralegal Specialist, National Endowment for the Humanities.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00405 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7536-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">NUCLEAR REGULATORY COMMISSION</AGENCY>
                <DEPDOC>[NRC-2023-0151]</DEPDOC>
                <SUBJECT>Information Collection: Licenses and Radiation Safety Requirements for Irradiators</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Nuclear Regulatory Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Renewal of existing information collection; request for comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The U.S. Nuclear Regulatory Commission (NRC) invites public comment on the renewal of Office of Management and Budget (OMB) approval for an existing collection of 
                        <PRTPAGE P="1947"/>
                        information. The information collection is entitled, “Licenses and Radiation Safety Requirements for Irradiators.”
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit comments by March 11, 2024. Comments received after this date will be considered if it is practical to do so, but the Commission is able to ensure consideration only for comments received on or before this date.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments by any of the following methods, however, the NRC encourages electronic comment submission through the Federal rulemaking website:</P>
                    <P>
                        • 
                        <E T="03">Federal rulemaking website:</E>
                         Go to 
                        <E T="03">https://www.regulations.gov</E>
                         and search for Docket ID NRC-2023-0151. Address questions about Docket IDs in 
                        <E T="03">Regulations.gov</E>
                         to Stacy Schumann; telephone: 301-415-0624; email: 
                        <E T="03">Stacy.Schumann@nrc.gov.</E>
                         For technical questions, contact the individual listed in the 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section of this document.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail comments to:</E>
                         David C. Cullison, Office of the Chief Information Officer, Mail Stop: T-6 A10M, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001.
                    </P>
                    <P>
                        For additional direction on obtaining information and submitting comments, see “Obtaining Information and Submitting Comments” in the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section of this document.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        David C. Cullison, Office of the Chief Information Officer, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001; telephone: 301-415-2084; email: 
                        <E T="03">Infocollects.Resource@nrc.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">I. Obtaining Information and Submitting Comments</HD>
                <HD SOURCE="HD2">A. Obtaining Information</HD>
                <P>Please refer to Docket ID NRC-2023-0151 when contacting the NRC about the availability of information for this action. You may obtain publicly available information related to this action by any of the following methods:</P>
                <P>
                    • 
                    <E T="03">Federal Rulemaking Website:</E>
                     Go to 
                    <E T="03">https://www.regulations.gov</E>
                     and search for Docket ID NRC-2023-0151.
                </P>
                <P>
                    • 
                    <E T="03">NRC's Agencywide Documents Access and Management System (ADAMS):</E>
                     You may obtain publicly available documents online in the ADAMS Public Documents collection at 
                    <E T="03">https://www.nrc.gov/reading-rm/adams.html.</E>
                     To begin the search, select “Begin Web-based ADAMS Search.” For problems with ADAMS, please contact the NRC's Public Document Room (PDR) reference staff at 1-800-397-4209, at 301-415-4737, or by email to 
                    <E T="03">PDR.Resource@nrc.gov.</E>
                     The supporting statement is available in ADAMS under Accession No. ML23332A046.
                </P>
                <P>
                    • 
                    <E T="03">NRC's PDR:</E>
                     The PDR, where you may examine and order copies of publicly available documents, is open by appointment. To make an appointment to visit the PDR, please send an email to 
                    <E T="03">PDR.Resource@nrc.gov</E>
                     or call 1-800-397-4209 or 301-415-4737, between 8 a.m. and 4 p.m. eastern time, Monday through Friday, except Federal holidays.
                </P>
                <P>
                    • 
                    <E T="03">NRC's Clearance Officer:</E>
                     A copy of the collection of information and related instructions may be obtained without charge by contacting the NRC's Clearance Officer, David C. Cullison, Office of the Chief Information Officer, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001; telephone: 301-415-2084; email: 
                    <E T="03">Infocollects.Resource@nrc.gov.</E>
                </P>
                <HD SOURCE="HD2">B. Submitting Comments</HD>
                <P>
                    The NRC encourages electronic comment submission through the Federal rulemaking website (
                    <E T="03">https://www.regulations.gov</E>
                    ). Please include Docket ID NRC-2023-0151, in your comment submission.
                </P>
                <P>
                    The NRC cautions you not to include identifying or contact information in comment submissions that you do not want to be publicly disclosed in your comment submission. All comment submissions are posted at 
                    <E T="03">https://www.regulations.gov</E>
                     and entered into ADAMS. Comment submissions are not routinely edited to remove identifying or contact information.
                </P>
                <P>If you are requesting or aggregating comments from other persons for submission to the NRC, then you should inform those persons not to include identifying or contact information that they do not want to be publicly disclosed in their comment submission. Your request should state that comment submissions are not routinely edited to remove such information before making the comment submissions available to the public or entering the comment into ADAMS.</P>
                <HD SOURCE="HD1">II. Background</HD>
                <P>In accordance with the Paperwork Reduction Act of 1995 (44 U.S.C. chapter 35), the NRC is requesting public comment on its intention to request the OMB's approval for the information collection summarized below.</P>
                <P>
                    1. 
                    <E T="03">The title of the information collection:</E>
                     10 CFR part 36, “Licenses and Radiation Safety Requirements for Irradiators.”
                </P>
                <P>
                    2. 
                    <E T="03">OMB approval number:</E>
                     3150-0158.
                </P>
                <P>
                    3. 
                    <E T="03">Type of submission:</E>
                     Extension.
                </P>
                <P>
                    4. 
                    <E T="03">The form number, if applicable:</E>
                     NA.
                </P>
                <P>
                    5. 
                    <E T="03">How often the collection is required or requested:</E>
                     Applications for new licenses and amendment may be submitted at any time (on occasion). Applications for renewal are submitted every 15 years. Reports are submitted as events occur.
                </P>
                <P>
                    6. 
                    <E T="03">Who will be required or asked to respond:</E>
                     Applicants for and holders of specific licenses authorizing the use of licensed material for irradiators.
                </P>
                <P>
                    7. 
                    <E T="03">The estimated number of annual responses:</E>
                     1,527.2 (19.2 for reporting [2.2 NRC licensees and 17 Agreement State licensees], 52 for recordkeepers [6 NRC licensees and 46 Agreement State Licensees], and 1,456 for third-party disclosures [168 NRC licensees and 1,288 Agreement State licensees]).
                </P>
                <P>
                    8. 
                    <E T="03">The estimated number of annual respondents:</E>
                     52 (6 NRC licensees and 46 Agreement State licensees).
                </P>
                <P>
                    9. 
                    <E T="03">The estimated number of hours needed annually to comply with the information collection requirement or request:</E>
                     29,781 hours (687 reporting hours + 21,762 recordkeeping hours + 7,332 third-party disclosure hours).
                </P>
                <P>
                    10. 
                    <E T="03">Abstract:</E>
                     Part 36 of title 10 of the Code of Federal Regulations, establishes radiation safety requirements for the use of radioactive material for irradiators. The information in the applications, reports, and records is used by the NRC staff to ensure that the health and safety of the public is protected and that the licensee possession and use of source or byproduct material is in compliance with license and regulatory requirements.
                </P>
                <HD SOURCE="HD1">III. Specific Requests for Comments</HD>
                <P>The NRC is seeking comments that address the following questions:</P>
                <P>1. Is the proposed collection of information necessary for the NRC to properly perform its functions? Does the information have practical utility? Please explain your answer.</P>
                <P>2. Is the estimate of the burden of the information collection accurate? Please explain your answer.</P>
                <P>3. Is there a way to enhance the quality, utility, and clarity of the information to be collected?</P>
                <P>4. How can the burden of the information collection on respondents be minimized, including the use of automated collection techniques or other forms of information technology?</P>
                <SIG>
                    <DATED>Dated: January 8, 2024.</DATED>
                    <PRTPAGE P="1948"/>
                    <P>For the Nuclear Regulatory Commission.</P>
                    <NAME>David C. Cullison,</NAME>
                    <TITLE>NRC Clearance Officer, Office of the Chief Information Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00463 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7590-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">PEACE CORPS</AGENCY>
                <SUBJECT>Privacy Act of 1974; System of Records</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Peace Corps.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of a modified system of records.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Peace Corps Office of Inspector General is issuing public notice of its intent to amend a system of records that it maintains subject to the Privacy Act of 1974. PC-19, entitled “Office of Inspector General Investigative Records” is being amended to reflect two new routine uses for information contained in the system and to make various technical corrections and/or clarifications. The amendments also reflect the expanded authority granted to the Peace Corps Inspector General since the initial publication of PC-19.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This modified system of records is effective 30 days upon publication; however, comments on the Routine Uses will be accepted on or before February 9, 2024. The Routine Uses are effective at the close of the comment period.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Send written comments, identified by the docket number and title, to the Peace Corps, ATTN: James Olin, FOIA/Privacy Act Officer, 1275 First Street NE, Washington, DC 20526, or by email at 
                        <E T="03">pcfr@peacecorps.gov.</E>
                         Email comments must be made in text and not in attachments.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        James Olin, FOIA/Privacy Act Officer, 1275 First Street NE, Washington, DC 20526; 
                        <E T="03">pcfr@peacecorps.gov;</E>
                         or 202-692-2507.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Peace Corps is amending a system of records that it maintains subject to the Privacy Act of 1974 (5 U.S.C. 552a), as amended. Specifically, PC-19, entitled “Office of Inspector General Investigative Records” is being amended to reflect two new routine uses at paragraphs M and N:</P>
                <P>“(M). Disclosure to all appropriate agencies, entities, and persons when (1) the Peace Corps suspects or has confirmed that there has been a breach of the system of records; (2) the Peace Corps has determined that as a result of the suspected or confirmed breach, there is a risk of harm to individuals, the Peace Corps (including its information systems, programs, and operations), the Federal Government, or national security; and (3) the disclosure made to such agencies, entities, and persons is reasonably necessary to assist in connection with the Peace Corps' efforts to respond to the suspected or confirmed breach or to prevent, minimize, or remedy such harm.”</P>
                <P>“(N). Disclosure to another Federal agency or Federal entity, when the Peace Corps determines that information from this system of records is reasonably necessary to assist the recipient agency or entity in (1) responding to a suspected or confirmed breach or (2) preventing, minimizing, or remedying the risk of harm to individuals, the recipient agency or entity (including its information systems, programs, and operations), the Federal Government, or national security, resulting from a suspected or confirmed breach.”</P>
                <P>The Peace Corps is also making technical amendments to references to the Inspector General Act, which has been amended and is now cited at 5 U.S.C. 401-424.</P>
                <P>
                    Pursuant to 5 U.S.C. 552a(j)(2), there is one substantive change being made to the exemptions promulgated for the system. The addition of this exemption is in keeping with the Inspector General's delegated law enforcement authority from the Attorney General. The added exemption also aligns with the Peace Corps' published rule, entitled, “Privacy Act Regulations,” establishing its procedures relating to access, maintenance, disclosure and amendment of records which are in a Peace Corps system of records per the Privacy Act, promulgated at 22 CFR part 308 (
                    <E T="03">https://www.ecfr.gov/current/title-22/chapter-III/part-308</E>
                    ). In accordance with 5 U.S.C. 552a(r), the Peace Corps has provided a report of this amended system of records to the Office of Management and Budget and to Congress.
                </P>
                <PRIACT>
                    <HD SOURCE="HD2">SYSTEM NAME AND NUMBER:</HD>
                    <P>Office of Inspector General Investigative Records, PC-19.</P>
                    <HD SOURCE="HD2">SECURITY CLASSIFICATION:</HD>
                    <P>Unclassified.</P>
                    <HD SOURCE="HD2">SYSTEM LOCATION:</HD>
                    <P>Office of Inspector General, Peace Corps, 1275 First Street NE, Washington, DC 20526.</P>
                    <HD SOURCE="HD2">SYSTEM MANAGER(S):</HD>
                    <P>Inspector General, Peace Corps, 1275 First Street NE, Washington, DC 20526.</P>
                    <HD SOURCE="HD2">AUTHORITY FOR MAINTENANCE OF THE SYSTEM:</HD>
                    <P>The Inspector General Act of 1978, as amended, 5 U.S.C. 401-424; The Peace Corps Act of 1961, as amended, 22 U.S.C. chapter 34.</P>
                    <HD SOURCE="HD2">PURPOSE(S) OF THE SYSTEM:</HD>
                    <P>The purpose of this system is to enable the Peace Corps Office of Inspector General to carry out its responsibilities under the Inspector General Act of 1978, as amended, 5 U.S.C. 401-424, and the Peace Corps Act of 1961, as amended, including the affirmative responsibility to conduct and supervise investigations.</P>
                    <HD SOURCE="HD2">CATEGORIES OF INDIVIDUALS COVERED BY THE SYSTEM:</HD>
                    <P>The investigative record subject, individuals who are part of an investigation of fraud, waste, or abuse concerning Peace Corps programs or operations; individuals interviewed or involved in the death of a Volunteer; current and former Peace Corps employees, Peace Corps Volunteers, Returned Peace Corps Volunteers, contractors, witnesses, complainants, informants, suspects or other persons associated with an investigation.</P>
                    <HD SOURCE="HD2">CATEGORIES OF RECORDS IN THE SYSTEM:</HD>
                    <P>The categories of records in this system include the correspondence related to investigations; information provided by subjects, witnesses, or investigatory or law enforcement organizations; reports of investigation, including affidavits, statements, transcripts of testimony, or other documents pertinent to investigations, as well as medical and behavioral health records.</P>
                    <HD SOURCE="HD2">RECORD SOURCE CATEGORIES:</HD>
                    <P>
                        The information sources include Peace Corps office and program officials, employees, contractors, grantees, and other individuals or entities associated with Peace Corps; subjects of an investigation; individuals, businesses, or entities with whom the subjects are or were associated (
                        <E T="03">e.g.,</E>
                         colleagues, business associates, acquaintances, or relatives); Federal, State, local, international, and foreign investigative or law enforcement agencies; other government agencies; confidential sources; complainants; witnesses; concerned citizens; and public source materials.
                    </P>
                    <HD SOURCE="HD2">ROUTINE USES OF RECORDS MAINTAINED IN THE SYSTEM, INCLUDING CATEGORIES OF USERS AND PURPOSES OF SUCH USES:</HD>
                    <P>
                        In addition to those disclosures generally permitted under 5 U.S.C. 552a(b) of the Privacy Act, the Peace Corps may disclose all or a portion of 
                        <PRTPAGE P="1949"/>
                        the records or information contained in this system outside of the Peace Corps without the consent of the subject individual, if the disclosure is compatible with the purpose for which the record was collected, as a routine use pursuant to 5 U.S.C. 552a(b)(3) as follows:
                    </P>
                    <P>A. Disclosure for Law Enforcement Purposes. Information may be disclosed to the appropriate Federal, State, local, or foreign agency responsible for investigating, prosecuting, enforcing, or implementing a statute, rule, regulation, or order, if the information indicates a violation or potential violation of civil or criminal law or regulation within the jurisdiction of the receiving entity.</P>
                    <P>B. Disclosure Incident to Requesting Information. Information may be disclosed to any source from which additional information is requested (to the extent necessary to identify the individual, inform the source of the purpose(s) of the request, or to identify the type of information requested); when necessary to obtain information relevant to a Peace Corps decision concerning retention of an employee or other personnel action (other than hiring), retention of a security clearance, the letting of a contract, or the issuance or retention of a grant or other benefit.</P>
                    <P>C. Disclosure to Requesting Agency. Information may be disclosed to a Federal, State, local, or other public authority of the fact that this system of records contains information relevant to the requesting agency's retention of an employee, the retention of a security clearance, the letting of a contract, or the issuance or retention of a license, grant, or other benefit. The other agency or licensing organization may then make a request supported by the written consent of the individual for part or all of the record if it so chooses. No disclosure will be made unless the information has been determined to be sufficiently reliable to support a referral to another office within the agency or to another Federal agency for criminal, civil, administrative, personnel, or regulatory action.</P>
                    <P>D. Disclosure to Office of Management and Budget. Information may be disclosed to the Office of Management and Budget at any stage in the legislative coordination and clearance process in connection with private relief legislation as set forth in OMB Circular No. A-19.</P>
                    <P>E. Disclosure to Congressional Offices. Information may be disclosed to a congressional office from the record of an individual in response to an inquiry from the congressional office made at the request of the individual.</P>
                    <P>F. Disclosure to Department of Justice. Information may be disclosed for purposes of litigation, provided that in each case the disclosure is compatible with the purpose for which the records were collected. Disclosure for these purposes may be made to the Department of Justice, or in a proceeding before a court, adjudicative body, or other administrative body before which the Peace Corps is authorized to appear. This disclosure may be made when: 1. The Peace Corps, or any component thereof; 2. Any employee of the Peace Corps in his or her official capacity; 3. Any employee of the Peace Corps in his or her individual capacity where the Department of Justice or the Peace Corps has agreed to represent the employee; or 4. The United States (when the Peace Corps determines that litigation is likely to affect the Peace Corps or any of its components) is a party to litigation or has an interest in such litigation, and the use of such records by the Department of Justice or the Peace Corps is deemed by the Peace Corps to be relevant and necessary to the litigation.</P>
                    <P>G. Disclosure to the National Archives. Information may be disclosed to the National Archives and Records Administration in records management inspections.</P>
                    <P>H. Disclosure to Contractors, Grantees, and Others. Information may be disclosed to contractors, grantees, consultants, or Volunteers performing or working on a contract, service, grant, cooperative agreement, job, or other activity for the Peace Corps and who have a need to have access to the information in the performance of their duties or activities for the Peace Corps. When appropriate, recipients will be required to comply with the requirements of the Privacy Act of 1974 as provided in 5 U.S.C. 552a(m).</P>
                    <P>I. Disclosures for Administrative Claims, Complaints, and Appeals. Information may be disclosed to an authorized appeal grievance examiner, formal complaints examiner, equal employment opportunity investigator, arbitrator, or other person properly engaged in investigation or settlement of an administrative grievance, complaint, claim, or appeal filed by an employee, but only to the extent that the information is relevant and necessary to the proceeding, Agencies that may obtain information under this routine use include, but are not limited to: the Office of Personnel Management, Office of Special Counsel, Federal Labor Relations Authority, U.S. Equal Employment Commission, and Office of Government Ethics.</P>
                    <P>J. Disclosure to the Office of Personnel Management. Information may be disclosed to the Office of Personnel Management pursuant to that agency's responsibility for evaluation and oversight of Federal personnel management.</P>
                    <P>K. Disclosure in Connection with Litigation. Information may be disclosed in connection with litigation or settlement discussions regarding claims by or against the Peace Corps, including public filings with a court, to the extent that disclosure of the information is relevant and necessary to the litigation or discussions and except where court orders are otherwise required under Section (b)(11) of the Privacy Act of 1974, 5 U.S.C. 552a(b)(11).</P>
                    <P>L. Disclosure to U.S. Ambassadors. Information from this system of records may be disclosed to a U.S. Ambassador or his or her designee in a country where the Peace Corps serves when the information is needed to perform an official responsibility, to allow the Ambassador to knowledgeably respond to official inquiries and deal with in- country situations that are within the scope of the Ambassador's responsibility.</P>
                    <P>M. Disclosure to all appropriate agencies, entities, and persons when (1) the Peace Corps suspects or has confirmed that there has been a breach of the system of records; (2) the Peace Corps has determined that as a result of the suspected or confirmed breach, there is a risk of harm to individuals, the Peace Corps (including its information systems, programs, and operations), the Federal Government, or national security; and (3) the disclosure made to such agencies, entities, and persons is reasonably necessary to assist in connection with the Peace Corps' efforts to respond to the suspected or confirmed breach or to prevent, minimize, or remedy such harm.</P>
                    <P>N. Disclosure to another Federal agency or Federal entity, when the Peace Corps determines that information from this system of records is reasonably necessary to assist the recipient agency or entity in (1) responding to a suspected or confirmed breach or (2) preventing, minimizing, or remedying the risk of harm to individuals, the recipient agency or entity (including its information systems, programs, and operations), the Federal Government, or national security, resulting from a suspected or confirmed breach.</P>
                    <P>Additionally, records may also be disclosed to:</P>
                    <P>
                        1. To non-governmental parties where those parties may have information the 
                        <PRTPAGE P="1950"/>
                        OIG seeks to obtain in connection with an investigation or inquiry.
                    </P>
                    <P>2. To qualified individuals or organizations in connection with the performance of a peer review or other study of the OIG's audit or investigative functions.</P>
                    <P>3. To a Federal agency responsible for considering debarment or suspension action if the record would be relevant to such action.</P>
                    <P>4. To the Department of Justice for the purpose of obtaining its advice on Freedom of Information Act matters.</P>
                    <P>5. To the Office of Government Ethics (OGE) to comply with agency reporting requirements established by OGE in 5 CFR 2638.604.</P>
                    <P>6. To the Council of the Inspectors General on Integrity and Efficiency, another Federal Office of Inspector General, or other Federal law enforcement office in connection with an allegation of wrongdoing by the Inspector General or staff members of the OIG.</P>
                    <P>7. To a grand jury agent pursuant to a federal or state grand jury subpoena or in response to a prosecution request that such record or information is released for the purpose of its introduction to a grand jury.</P>
                    <HD SOURCE="HD2">POLICIES AND PRACTICES FOR STORAGE OF RECORDS:</HD>
                    <P>Investigative Records are maintained in electronic and paper format. Electronic records are stored in computerized databases. Paper records and other media (photographs, audio recording, CDs, etc.) are stored in locked containers in a secured restricted area.</P>
                    <HD SOURCE="HD2">POLICIES AND PRACTICES FOR RETRIEVAL OF RECORDS:</HD>
                    <P>The paper or physical case records are retrieved by case number. Electronic records may be retrieved by case number, case name, subject, cross referenced item key word search, batch retrieval applications, or by any available field or metadata element recorded in the system.</P>
                    <HD SOURCE="HD2">POLICIES AND PRACTICES FOR RETENTION AND DISPOSAL OF RECORDS:</HD>
                    <P>Investigative records are retained, retired and destroyed in accordance with the Peace Corps' published record disposition schedule that is approved by the National Archives and Records Administration.</P>
                    <HD SOURCE="HD2">ADMINISTRATIVE, TECHNICAL, AND PHYSICAL SAFEGUARDS:</HD>
                    <P>The Peace Corps safeguards records in this system in accordance with applicable laws, rules, and policies to protect personally identifiable information against unauthorized access or disclosure. The Peace Corps has imposed strict controls to minimize such risks. Administrative safeguards include but not limited to: access to the information in this system is limited to authorized personnel with official duties requiring access, and whose roles have been authorized with such access permissions. All such individuals receive the appropriate privacy and cybersecurity training on an annual basis.</P>
                    <P>The physical controls in place include the servers storing electronic data are located offsite in a locked facility with access limited to authorized personnel. The servers are maintained in accordance with a government contract that requires adherence to applicable laws, rules, and policies on protecting individual privacy. Computerized records are safeguarded in a secured environment. Security protocols meet the promulgating guidance as established by the National Institute of Standards and Technology (NIST) Security Standards from Access Control to Data Encryption and Security Assessment and Authorization. The paper or other physical records are kept in limited access areas during duty hours and in locked file cabinets and/or locked offices at all other times.</P>
                    <P>The technical controls in place include multiple firewalls, system access, encrypted data at rest, encrypted data in motion, periodic vulnerability scans to ensure security compliance, and security access logs. Security complies with applicable Federal Information Processing Standards (FIPS) issued by NIST. Access is restricted to specific authorized Peace Corps individuals who have internet access through work computers using a Personally Identity Verification (PIV). Individual users can only access records with the proper pre-approved accreditation.</P>
                    <HD SOURCE="HD2">RECORD ACCESS PROCEDURES:</HD>
                    <P>
                        Records in this system are exempt from the provisions of the Privacy Act of 1974 that permit access, correction, and notification to the extent permitted under the Privacy Act of 1974, 5 U.S.C. 552a(j)(2), (k)(2), and 22 CFR 308.14. At the Inspector General's discretion, individual requests for access and correction may be granted if it is determined that the exercise of these rights will not interfere with an interest that the exemption is intended to protect. The exemption from access is limited in some instances by law to information that would reveal the identity of a confidential source. Individuals seeking access to their records should follow the procedures in 22 CFR part 308. Individuals should address written inquiries to the OIG FOIA Officer at 
                        <E T="03">foia@peacecorpsoig.gov.</E>
                         Complete Peace Corps Privacy Act procedures are set out in 22 CFR part 308. Requesters will be required to provide adequate identification. Additional identification may be required in some instances. Requests for correction or amendment must identify the record to be changed and the corrective action sought.
                    </P>
                    <HD SOURCE="HD2">CONTESTING RECORD PROCEDURES:</HD>
                    <P>Requests must follow the “Records Access Procedures,” above. Clearly and concisely state what information is being contested, the reasons for contesting it, and the proposed amendment to the information sought.</P>
                    <HD SOURCE="HD2">NOTIFICATION PROCEDURES:</HD>
                    <P>See “Record Access Procedures.”</P>
                    <HD SOURCE="HD2">EXEMPTIONS PROMULGATED FOR THE SYSTEM:</HD>
                    <P>Pursuant to 5 U.S.C. 552a(j)(2), this system is exempt from the following provisions of the Privacy Act of 1974, subject to the limitations set forth in that subsection: 5 U.S.C. 552a(c)(3)-(4); (d); (e)(1), (e)(2), (e)(3), (e)(4)(G), (e)(4)(H), (e)(5), and (e)(8); (f); and (g). Pursuant to 5 U.S.C. 552a(k)(2), this system is exempt from the following provisions of the Privacy Act of 1974, subject to the limitations set forth in that subsection: 5 U.S.C. 552a(c)(3), (d), (e)(1), (e)(4)(G), (e)(4)(H), and (f).</P>
                    <HD SOURCE="HD2">HISTORY:</HD>
                    <P>58 FR 39839; 65 FR 53772; 72 FR 44878.</P>
                </PRIACT>
                <SIG>
                    <DATED>Dated: January 5, 2024.</DATED>
                    <NAME>James Olin,</NAME>
                    <TITLE>FOIA/Privacy Act Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00371 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6051-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">POSTAL REGULATORY COMMISSION</AGENCY>
                <DEPDOC>[Docket Nos. MC2024-160 and CP2024-166]</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>
                         January 16, 2024.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit comments electronically via the Commission's 
                        <PRTPAGE P="1951"/>
                        Filing Online system at 
                        <E T="03">http://www.prc.gov.</E>
                         Those who cannot submit comments electronically should contact the person identified in the 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section by telephone for advice on filing alternatives.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>David A. Trissell, General Counsel, at 202-789-6820.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Table of Contents</HD>
                <EXTRACT>
                    <FP SOURCE="FP-1">I. Introduction</FP>
                    <FP SOURCE="FP-1">II. Docketed Proceeding(s)</FP>
                </EXTRACT>
                <HD SOURCE="HD1">I. Introduction</HD>
                <P>The Commission gives notice that the Postal Service filed request(s) for the Commission to consider matters related to negotiated service agreement(s). The request(s) may propose the addition or removal of a negotiated service agreement from the Market Dominant or the Competitive product list, or the modification of an existing product currently appearing on the Market Dominant or the Competitive product list.</P>
                <P>Section II identifies the docket number(s) associated with each Postal Service request, the title of each Postal Service request, the request's acceptance date, and the authority cited by the Postal Service for each request. For each request, the Commission appoints an officer of the Commission to represent the interests of the general public in the proceeding, pursuant to 39 U.S.C. 505 (Public Representative). Section II also establishes comment deadline(s) pertaining to each request.</P>
                <P>
                    The public portions of the Postal Service's request(s) can be accessed via the Commission's website (
                    <E T="03">http://www.prc.gov</E>
                    ). Non-public portions of the Postal Service's request(s), if any, can be accessed through compliance with the requirements of 39 CFR 3011.301.
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See</E>
                         Docket No. RM2018-3, Order Adopting Final Rules Relating to Non-Public Information, June 27, 2018, Attachment A at 19-22 (Order No. 4679).
                    </P>
                </FTNT>
                <P>The Commission invites comments on whether the Postal Service's request(s) in the captioned docket(s) are consistent with the policies of title 39. For request(s) that the Postal Service states concern Market Dominant product(s), applicable statutory and regulatory requirements include 39 U.S.C. 3622, 39 U.S.C. 3642, 39 CFR part 3030, and 39 CFR part 3040, subpart B. For request(s) that the Postal Service states concern Competitive product(s), applicable statutory and regulatory requirements include 39 U.S.C. 3632, 39 U.S.C. 3633, 39 U.S.C. 3642, 39 CFR part 3035, and 39 CFR part 3040, subpart B. Comment deadline(s) for each request appear in section II.</P>
                <HD SOURCE="HD1">II. Docketed Proceeding(s)</HD>
                <P>
                    1. 
                    <E T="03">Docket No(s).:</E>
                     MC2024-160 and CP2024-166; 
                    <E T="03">Filing Title:</E>
                     USPS Request to Add Priority Mail &amp; USPS Ground Advantage Contract 170 to Competitive Product List and Notice of Filing Materials Under Seal; 
                    <E T="03">Filing Acceptance Date:</E>
                     January 5, 2024; 
                    <E T="03">Filing Authority:</E>
                     39 U.S.C. 3642, 39 CFR 3040.130 through 3040.135, and 39 CFR 3035.105; 
                    <E T="03">Public Representative:</E>
                     Alireza Motameni; 
                    <E T="03">Comments Due:</E>
                     January 16, 2024.
                </P>
                <P>
                    This Notice will be published in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <SIG>
                    <NAME>Erica A. Barker,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00423 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7710-FW-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">POSTAL SERVICE</AGENCY>
                <SUBJECT>Product Change—Priority Mail and USPS Ground Advantage® Negotiated Service Agreement</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>
                        Postal Service
                        <E T="51">TM</E>
                        .
                    </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Postal Service gives notice of filing a request with the Postal Regulatory Commission to add a domestic shipping services contract to the list of Negotiated Service Agreements in the Mail Classification Schedule's Competitive Products List.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Date of required notice:</E>
                         January 11, 2024.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Sean Robinson, 202-268-8405.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The United States Postal Service® hereby gives notice that, pursuant to 39 U.S.C. 3642 and 3632(b)(3), on January 4, 2024, it filed with the Postal Regulatory Commission a 
                    <E T="03">USPS Request to Add Priority Mail &amp; USPS Ground Advantage® Contract 169 to Competitive Product List.</E>
                     Documents are available at 
                    <E T="03">www.prc.gov,</E>
                     Docket Nos. MC2024-158, CP2024-164.
                </P>
                <SIG>
                    <NAME>Sean Robinson,</NAME>
                    <TITLE>Attorney, Corporate and Postal Business Law.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00381 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7710-12-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">POSTAL SERVICE</AGENCY>
                <SUBJECT>Product Change—Priority Mail Express, Priority Mail, and USPS Ground Advantage® Negotiated Service Agreement</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>
                        Postal Service
                        <E T="51">TM</E>
                        .
                    </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Postal Service gives notice of filing a request with the Postal Regulatory Commission to add a domestic shipping services contract to the list of Negotiated Service Agreements in the Mail Classification Schedule's Competitive Products List.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Date of required notice:</E>
                         January 11, 2024.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Sean C. Robinson, 202-268-8405.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The United States Postal Service® hereby gives notice that, pursuant to 39 U.S.C. 3642 and 3632(b)(3), on January 4, 2024, it filed with the Postal Regulatory Commission a 
                    <E T="03">USPS Request to Add Priority Mail Express, Priority Mail &amp; USPS Ground Advantage® Contract 42 to Competitive Product List.</E>
                     Documents are available at 
                    <E T="03">www.prc.gov,</E>
                     Docket Nos. MC2024-159, CP2024-165.
                </P>
                <SIG>
                    <NAME>Sean C. Robinson,</NAME>
                    <TITLE>Attorney, Corporate and Postal Business Law.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00387 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7710-12-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">POSTAL SERVICE</AGENCY>
                <SUBJECT>Product Change—Priority Mail and USPS Ground Advantage® Negotiated Service Agreement</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>
                        Postal Service
                        <E T="51">TM</E>
                        .
                    </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Postal Service gives notice of filing a request with the Postal Regulatory Commission to add a domestic shipping services contract to the list of Negotiated Service Agreements in the Mail Classification Schedule's Competitive Products List.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Date of required notice:</E>
                         January 11, 2024.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Sean Robinson, 202-268-8405.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The United States Postal Service® hereby gives notice that, pursuant to 39 U.S.C. 3642 and 3632(b)(3), on January 5, 2024, it filed with the Postal Regulatory Commission a 
                    <E T="03">USPS Request to Add Priority Mail &amp; USPS Ground Advantage® Contract 170 to Competitive Product List.</E>
                     Documents 
                    <PRTPAGE P="1952"/>
                    are available at 
                    <E T="03">www.prc.gov,</E>
                     Docket Nos. MC2024-160, CP2024-166.
                </P>
                <SIG>
                    <NAME>Sean Robinson,</NAME>
                    <TITLE>Attorney, Corporate and Postal Business Law.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00380 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7710-12-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release No. 34-99277; File No. SR-LCH SA-2023-007]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; LCH SA; Notice of Filing of Proposed Rule Change Relating to Liquidity Risk Modelling Framework</SUBJECT>
                <DATE>January 5, 2024.</DATE>
                <P>
                    Pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (“Act”),
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     notice is hereby given that on December 22, 2023, Banque Centrale de Compensation, which conducts business under the name LCH SA (“LCH SA”), filed with the Securities and Exchange Commission (“Commission”) the proposed rule change described in Items I, II and III below, which Items have been primarily prepared by LCH SA. The Commission is publishing this notice to solicit comments on the Proposed Rule Change from interested persons.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Clearing Agency's Statement of the Terms of Substance of the Proposed Rule Change</HD>
                <P>
                    LCH SA is proposing to amend its Liquidity Risk Modelling Framework (the “Framework”), which describes the Liquidity Stress Testing framework by which the Collateral and Liquidity Risk Management department (“CaLRM”) of LCH SA assures that LCH SA has enough cash available to meet any financial obligations, both expected and unexpected, that may arise over the liquidation period for each of the clearing services that LCH SA offers (the “Proposed Rule Change”).
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         LCH SA, a subsidiary of LCH Group and an indirect subsidiary of the London Stock Exchange Group plc (“LSEG”), manages its liquidity risk pursuant to, among other policies and procedures, the Group Liquidity Risk Policy and the Group Liquidity Plan applicable to each entity within LCH Group. In addition to its CDSClear service, LCH SA provides clearing services in connection with cash equities and derivatives listed for trading on Euronext (EquityClear), commodity derivatives listed for trading on Euronext (CommodityClear), and tri-party Repo transactions (RepoClear). LCH SA also maintains an interoperability link with Euronext Clearing, formerly Cassa di Compensazione e Garanzia, in Milan, Italy.
                    </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, LCH SA 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. LCH SA has prepared summaries, set forth in sections A, B, and C below, of the most significant aspects of such statements.</P>
                <HD SOURCE="HD2">A. Clearing Agency's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <HD SOURCE="HD3">1. Purpose</HD>
                <P>
                    The Proposed Rule Change is being adopted primarily to enhance the manner in which the Liquidity Coverage Ratio (“LCR”) is calculated, thereby increasing the robustness of LCH SA's liquidity profile.
                    <SU>4</SU>
                    <FTREF/>
                     The changes implement recommendations made by LCH SA's Model Validation Team following validation exercises in 2020 and 2021.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         LCH SA uses a Cover 2 approach for conducting stress tests and assessing its liquidity resources on a daily basis. This approach assumes that the two Clearing Member groups with the largest liquidity exposure will default on the same day. Cover 2 is computed by taking into account the liquidity risks related to clearing members within the same group across all services of the CCP that are then aggregated.
                    </P>
                </FTNT>
                <P>
                    In particular, the Proposed Rule Change will: (a) revise the manner in which the settlement obligation liquidity requirements are calculated by aligning it to the actual process used by the Operations Team during a default management event and ensuring that no netting is allowed between Members of the same Group; (b) revise the manner in which securities pledged to the Banque de France (“BdF”) are calculated by providing that such securities be valued at the stressed mark-to-market price rather than the contract price; 
                    <SU>5</SU>
                    <FTREF/>
                     (c) extend from five (5) days to seven (7) days the length of time for which LCH SA must maintain liquidity resources sufficient to meet its liquidity requirements; 
                    <SU>6</SU>
                    <FTREF/>
                     (d) include the liquidity needs generated by the expiration of physically settled stock futures in the liquidity monitoring; and (e) require LCH SA, in calculating its required liquidity resources, to take into account that Clearing Members may switch from depositing non-cash collateral in a Full Title Transfer Account, which may be pledged at the BdF to obtain a liquidity line of credit, to depositing non-cash collateral instead in a Pledge Account, which permits no re-hypothecation rights.
                    <SU>7</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         See, Framework, § 4.2.5.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         See, 
                        <E T="03">e.g.,</E>
                         Framework, §§ 4.2.1, 5.1, 5.3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         See, Framework, § 4.2.5.2.4.
                    </P>
                </FTNT>
                <P>
                    The proposed revisions to the Framework are set out in four of the Framework's six sections: Section 1, 
                    <E T="03">Model Scope, Purpose and Use;</E>
                     Section 4, 
                    <E T="03">Model Specifications;</E>
                     Section 5, 
                    <E T="03">Model Performance Testing and Ongoing Monitoring</E>
                     and Section 6, Appendix.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         No revisions are being proposed to Section 2, Limitations and Compensating Controls, or Section 3, Justification of Modeling Approach. The Framework also has a number of appendices, set out in Section 6, that supplement the matters discussed elsewhere in the Framework.
                    </P>
                </FTNT>
                <P>Section 1 of the Framework will be amended as follows:</P>
                <P>
                    Section 1.1, 
                    <E T="03">Model Objective, Business Scope and Intended Use,</E>
                     will be revised to specify that the review of the Framework will be performed at least on an annual basis rather than quarterly to align the frequency of the review with the frequency defined for the regular update of the Liquidity Risk Policy.
                </P>
                <P>
                    Section 1.1.1, 
                    <E T="03">Reminder of SA's activities,</E>
                     will be revised to specify that the Default Funds are calibrated on the assumption of default of the two most exposed Member Groups (Cover 2). In particular, LCH SA's Framework ensures that the liquid resources are sufficient to cover the simultaneous default of the two most exposed Member Groups in term of liquidity that are identified by taking into consideration all of the possible liquidity needs, including the settlement obligation. This is approach incorporates the Cover 1 Clearing Member Group plus the next most exposed Clearing Member Group.
                    <SU>9</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         Per SEC Rule 17Ad-22(e)(7)(i), LCH SA is required to maintain sufficient liquid resources at the minimum in all relevant currencies to effect same-day and, where appropriate, intraday and multiday settlement of payment obligations with a high degree of confidence under a wide range of foreseeable stress scenarios that includes, but is not limited to, the default of the participant family that would generate the largest aggregate payment obligation for the covered clearing agency in extreme but plausible market conditions.
                    </P>
                </FTNT>
                <P>
                    Section 1.1.2, 
                    <E T="03">Investment activities,</E>
                     will be revised to clarify the responsibilities of the Collateral and Liquidity Management (“CaLM”) Front Office team. Specifically, the sentence: “Three main tasks have been assigned to the team: liquidity management, non-cash collateral 
                    <E T="03">settlement</E>
                     in case of a clearing member's default and investment management” has been revised to read: “Three main tasks have been assigned to the team: liquidity management, non-cash collateral
                    <E T="03"> liquidation</E>
                     
                    <SU>10</SU>
                    <FTREF/>
                     in case of a clearing 
                    <PRTPAGE P="1953"/>
                    member's default and investment management”. The purpose of this change is to provide a more accurate description on the actual responsibilities of the CaLM Front Office team which is in charge of performing all the relevant activities necessary to 
                    <E T="03">liquidate</E>
                     a member's non-cash collateral in case of defaults.
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         Such liquidation includes the possible liquidation of securities underlying reverse 
                        <PRTPAGE/>
                        repurchase activities of a defaulting clearing member.
                    </P>
                </FTNT>
                <P>
                    Section 1.3, 
                    <E T="03">Model dependency and interconnectivity,</E>
                     will be revised to describe more fully the purpose of the various policies and procedures that LCH SA employs to manage its liquidity risk in a manner that is consistent with defined risk appetites, as well as with regulatory and internal requirements. These policies and procedures include:
                </P>
                <P>
                    • 
                    <E T="03">LCH SA Liquidity Plan,</E>
                     which sets out the principles and procedures for liquidity management within LCH SA. Its main objectives are to:
                </P>
                <P>○ Ensure that LCH SA maintains sufficient liquidity at all times in accordance with policies set by the appropriate governance authority and monitored and reported by Risk Management;</P>
                <P>○ Ensure that liquidity management and resources are aligned with LCH SA's operational requirements to meet payment obligations as they fall due under business as usual and stressed liquidity conditions; and</P>
                <P>○ Ensure effective liquidity risk identification and escalation within CaLM service and other relevant LCH SA departments.</P>
                <P>
                    • 
                    <E T="03">Group Liquidity Risk Policy,</E>
                     which ensures that each central counterparty (“CCP”) of LCH Group has enough liquid resources on hand to meet all the expected and unexpected financial obligations that arise during the course of the day. The policy lays out how a CCP will measure whether there are enough available liquid resources.
                </P>
                <P>
                    • 
                    <E T="03">Group Financial Resource Adequacy Policy,</E>
                     which describes the standards by which financial resources should be assessed against Clearing Member exposures, including variation margins, initial margins, margin add-ons for liquidity risk, concentration risk, wrong-way risk, where appropriate, as well as the sizing and re-sizing of the default funds across the LCH Group CCPs.
                </P>
                <P>
                    • 
                    <E T="03">Group Collateral Risk Policy,</E>
                     which sets out the standards for managing collateral risk across the LCH Group CCPs and ensures that CCPs must have a robust mechanism in place to process and control the collateral posted by Members.
                </P>
                <P>
                    • 
                    <E T="03">Group Investment Risk Policy,</E>
                     which sets out the standards for the management of investment risk across the LCH Group CCPs.
                </P>
                <P>
                    • 
                    <E T="03">LCH SA Collateral Control Framework,</E>
                     which describes the actions undertaken by the CaLRM team to implement the collateral limits laid out in the Group Collateral Risk Policy and to ensure that the prices integrated on a daily basis by the Margin Team are accurate and fairly priced.
                </P>
                <P>
                    • 
                    <E T="03">Group Risk Policy: Default Management,</E>
                     which describes the minimum standards that each CCP within the LCH Group must meet in dealing with the default of a Member.
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         The CaLM Risk Procedures: Investment Risk Monitoring, and Default Management Guidelines, which currently are included among these policies and procedures, have been removed.
                    </P>
                </FTNT>
                <P>
                    • Section 1.4, 
                    <E T="03">Model Governance,</E>
                     will be revised by adding a footnote specifying that core liquidity reverse stress tests 
                    <SU>12</SU>
                    <FTREF/>
                     are performed monthly in line with that stated in the Liquidity Risk Policy. In particular LCH SA performs two set of reverse stress test:
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">See,</E>
                         Framework, § 5.3.
                    </P>
                </FTNT>
                <P>○ On a monthly basis, in line with the methodology applied to perform any reverse stress tests in LCH SA, risk factors (defined in section 5.3.1) are independently stressed (one single factor at time) to assess extreme market conditions necessary to observe a breach of the LCR limit.</P>
                <P>
                    ○ In addition, combined reverse stress test scenarios (defined in section 5.3.2) are also performed on at least a quarterly basis. These combined scenarios are considered as “non-core reverse stress tests” with combined stress shocks applied on risks factors to determine the joint market conditions necessary to breach the LCR limit and assess their plausibility. This change to the Framework is being proposed to align it with the updated Liquidity Risk Policy text approved during the 2022 review and in compliance with the SEC rule 17Ad-22(e)(7)(vi)(B).
                    <SU>13</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         17 CFR 240.17Ad-22(e)(7)(vi)(B).
                    </P>
                </FTNT>
                <P>
                    ○ Finally, Section 1.6.1, 
                    <E T="03">Liquidity Sources,</E>
                     will be revised to expand the tools available to CaLM to meet LCH SA's non-Euro liquidity requirements in the event of a default. This proposed change aims to align the Framework with the updated Liquidity Plan text approved during the 2022 review.
                </P>
                <P>Specifically, these tools include:</P>
                <P>
                    • Non-Euro cash deposited as collateral in accordance with SEC Rule 17Ad-22(a)(14)(i) 
                    <SU>14</SU>
                    <FTREF/>
                     as being cash held at creditworthy commercial banks;
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         17 CFR 240.17Ad-22(a)(14)(i).
                    </P>
                </FTNT>
                <P>
                    • Sale of non-Euro securities of the defaulting member in accordance with SEC Rule 17Ad-22(a)(14)(ii) 
                    <SU>15</SU>
                    <FTREF/>
                    :
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         17 CFR 240.17Ad-22(a)(14)(ii).
                    </P>
                </FTNT>
                <P>○ These highly liquid and available securities would be converted into cash via an outright sale in the open market; or</P>
                <P>○ in the intermediary period between the default of the member and the auction settlement, these securities might be converted into cash via the repo arrangement in place at CaLM Front Office.</P>
                <P>• Repo transactions, including: (a) bilateral repo transactions (non-Euro cash taker and non-Euro collateral giver); (b) cross-currency bilateral repo (non-Euro cash taker and Euro collateral giver); (c) cross-currency triparty repo (non-Euro cash taker and Euro collateral giver). LCH SA considers these transactions to be classified as prearranged funding arrangements determined to be highly reliable even in extreme but plausible market conditions due to (a) their contractual nature; and (b) the highly liquid and overall resilience of the repo markets for the major currencies cleared by LCH SA.</P>
                <P>
                    • Use of the multicurrency overdraft facility. In accordance with SEC Rule 17Ad-22(a)(14),
                    <SU>16</SU>
                    <FTREF/>
                     LCH SA considers this facility to be classified as a prearranged funding arrangement determined to be highly reliable even in extreme but plausible market conditions due to (a) its contractual nature; and (b) the high credit quality, based on the conservative internal credit score required of the bank providing the facility.
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         17 CFR 240.17Ad-22(a)(14).
                    </P>
                </FTNT>
                <P>
                    • Use of the FX spot market transactions. In accordance with SEC Rule 17Ad-22(a)(14),
                    <SU>17</SU>
                    <FTREF/>
                     LCH SA considers this facility to be classified as a prearranged funding arrangement determined to be highly reliable even in extreme but plausible market conditions as (a) numerous counterparties are already onboarded on the FX platform; and (b) the highly liquid and overall resilience of the FX markets observed for the major currencies cleared by LCH SA.
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    • ECB weekly tender in U.S. Dollars (“USD”).
                    <SU>18</SU>
                    <FTREF/>
                     In accordance with SEC Rule 17Ad-22(a)(14) 
                    <SU>19</SU>
                    <FTREF/>
                     LCH SA considers this facility to be a prearranged funding arrangement determined to be highly reliable even in extreme but plausible market conditions given LCA SA's banking license and the central bank 
                    <PRTPAGE P="1954"/>
                    status of the institution providing such resource.
                </P>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         As a credit institution, LCH SA has access to the ECB Open Market Operations in USD. LCH SA considers this resource as a last resort.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         17 CFR 240.17Ad-22(a)(14).
                    </P>
                </FTNT>
                <P>
                    • Replace LCH SA's liabilities in non-Euro by Euro, as permitted by LCH SA's Rule Book (Article 4.2.3.2 of CDSClear Rulebook).
                    <SU>20</SU>
                    <FTREF/>
                     In accordance with SEC Rule 17Ad-22(a)(14) 
                    <SU>21</SU>
                    <FTREF/>
                     Euros used to cover liabilities would be cash held at central bank.
                </P>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         See Article 4.2.3.2., 
                        <E T="03">https://www.lch.com/system/files/media_root/Supplementary%20Materials%20-%20LCH%20SA%20-%20CDSClear%20SA%20Rule%20Book_1.pdf.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         17 CFR 240.17Ad-22(a)(14).
                    </P>
                </FTNT>
                <P>Furthermore, the committed liquidity line previously noted is being removed as LCH SA has replaced the committed liquidity line with a multicurrency overdraft facility at a major international bank.</P>
                <P>
                    In summary, LCH SA classifies the different liquidity tools pursuant to SEC Rule 17Ad-22(a)(14),
                    <SU>22</SU>
                    <FTREF/>
                     as follows:
                </P>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    • 
                    <E T="03">Cash</E>
                    —Euros cash held at central bank/non euros cash held at creditworthy commercial banks; replacement of LCH SA's liabilities in non euros by euros
                </P>
                <P>
                    • 
                    <E T="03">Uncommitted prearranged</E>
                    —readily available assets convertible to cash through prearranged funding arrangements, that are determined to be highly reliable even in extreme but plausible market conditions by the BoD following a review to be conducted not less than annually:
                </P>
                <P>a. Sale of non-Euro securities of the defaulting members;</P>
                <P>b. Repo transactions (bilateral repo, cross currency bilateral repo, and cross currency triparty repo);</P>
                <P>c. Multicurrency overdraft facility;</P>
                <P>d. FX spot market transactions; and</P>
                <P>e. ECB weekly tender in U.S. dollars</P>
                <P>Additionally, a footnote (8) has been removed as the relevant report has been taken out from the appendix in the context of the reorganisation of the appendix 5 as described below in the relevant section in the present 19b4.</P>
                <P>
                    Section 1.6.1.1, 
                    <E T="03">Collateral transfer,</E>
                     will be revised to recognize that a Clearing Member may deposit non-cash collateral either (a) by Full Title Transfer Accounts that LCH SA maintains at various central securities depositories or (b) by a Single Pledged Account, without the right of re-hypothecation, that LCH SA maintains at Euroclear Bank.
                    <SU>23</SU>
                    <FTREF/>
                     This section will be further revised to clarify that non-cash collateral deposited in Full Title Transfer Accounts may be pledged at the BdF to obtain a liquidity line of credit that can be drawn on intraday or overnight, if needed. Additionnaly, precisions have been added regarding:
                </P>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         Currently, non-cash collateral may be pledged without limits only with regard to the CDSClear service. Moreover, there are limits on the amount of pledge collateral that may be deposited for RepoClear, €GC (Tri-Party Repo) and EquityClear. The majority of the collateral that LCH SA currently collects is by Full Title Transfer.
                    </P>
                </FTNT>
                <FP SOURCE="FP-1">—the existing limits applied on Repoclear SA/€GC Plus and EquityClear SA for pledge</FP>
                <FP SOURCE="FP-1">—the fact that FFTA is used in majority by Clearing Members</FP>
                <FP>Finally, to enhance the wording, a precision has been added to precise that only resources received in FFTA can be pledged to 3G pool.</FP>
                <P>The change aims to improve the clarity of the document as there is no change applied on the actual offer of collateral account.</P>
                <P>
                    Section 1.6.1.2, 
                    <E T="03">Assessment of assets' liquidity,</E>
                     will be revised to provide that Tier 1 assets, 
                    <E T="03">i.e.,</E>
                     securities that are deemed to be of sufficient quality and demand to generate liquidity in the event of a default or a major market stress at little or no loss, will include, in addition to all European Central Bank (“ECB”) eligible collateral, UK Gilts and U.S. Treasury Bills, along with Dutch and Belgian central bank guarantees (but only for the defaulting Clearing Member). In addition, recognized Tier 3 assets, 
                    <E T="03">i.e.,</E>
                     assets that are deemed to have little or no liquidity value in the event of a default or major market stress, or are deemed to be too illiquid to be converted in the timeframe that LCH SA would need the liquidity, will be revised to include non-cash collateral denominated Danish Krone, Norwegian Krone, Swedish Krona, Japanese Yen, Swiss Francs, Canadian Dollars and Australian Dollars.
                </P>
                <P>
                    Section 1.6.1.3, 
                    <E T="03">Synthesis,</E>
                     will be revised to clarify that LCH SA does not retain the right of collateral re-hypothecation for collateral deposited under the pledge regime unless the Clearing Member is in default. The reference specific to CDS has been removed as now the pledge is offered for all LCH SA services. It will confirm that CaLM demonstrated in 2021 and 2022 the ability to raise Euro liquidity from non-Euro non cash collateral in USD and GBP. Moreover, it will clarify that when considering non-Euro non cash collateral as a liquidity source, a conservative buffer of ten percent (10%) is applied to absorb market stress that may occur beyond the volatility already captured by the all-in haircut. In addition, it will confirm that Central Bank guarantees can be considered for liquidity purposes only if the relevant Member posting them is in default because only in that situation the CCP would acquire full ownership of the guarantee provided by the Central Bank.
                </P>
                <P>
                    Section 1.6.2.1, 
                    <E T="03">Liquidity needs arising from members' defaults,</E>
                     will be revised to clarify the description of the liquidity needs that may arise from settlement. The following sentence: “Cash outflows are generated when SA has to step in on behalf of the defaulted member to post cash to non-defaulting member(s) and take in the underlying 
                    <E T="03">collateral”</E>
                     has been revised to read: “Cash outflows are generated when SA has to step in on behalf of the defaulted member to post cash to non-defaulting member(s) and take in the underlying 
                    <E T="03">securities”.</E>
                     This change is being made to increase the accuracy of the document and does not represent a change in the methodology or procedure of LCH SA.
                </P>
                <P>
                    Moreover, LCH SA will also specify that the value of the bonds pledged at the ECB to raise liquidity takes into account stress market conditions.
                    <SU>24</SU>
                    <FTREF/>
                     The addition of the “stress market conditions” is thus performed for clarity in line with adjustments performed in the LCR model assumptions.
                </P>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         A detailed presentation of the model enhancement is reflected in Section 4.2.5.1.1.2 of the Framework.
                    </P>
                </FTNT>
                <P>
                    Section 4 of the Framework, which explains the modelling Framework in detail, will be amended, as noted above, to enhance the manner in which the LCR is calculated, thereby increasing the robustness of LCH SA's liquidity profile. This section discusses first, the calculation of the Operational Target, 
                    <E T="03">i.e.,</E>
                     the amount of liquidity required to be held to satisfy LCH SA's liquidity needs related to the operational management of LCH SA in a stressed environment, but one that does not lead to a Clearing Member's default. The Operational Target ensures that LCH SA's liquidity resources are always greater than its operational liquidity requirements.
                </P>
                <P>
                    Section 4.1.2, 
                    <E T="03">Model inputs and Variable selection,</E>
                     will be revised to clarify that the repayment of excess cash as well as excess ECB eligible securities deposited to cover margin requirements are considered in the liquidity requirement of the Operational Target. Two footnotes will be updated to specify that Portuguese and Finnish government bonds posted via the triparty solution are excluded from the liquid assets (repayment of excess cash and stressed margin reduction) because these securities are not transferrable to the BdF due to operational constraints. These changes will increase the accuracy of the document and does not represent a change in the methodology or procedure of LCH SA. Finally, the change of branding from CC&amp;G to 
                    <PRTPAGE P="1955"/>
                    Euronext Clearing has been performed in line with the change of branding performed in the whole documentation and described below in the present 19b4.
                </P>
                <P>
                    Section 4.1.4, 
                    <E T="03">Mathematical formula, derivation and algorithm, and numerical approximation,</E>
                     will be revised to clarify that the Operational Target is calculated as the sum of the liquidity requirements described in Section 4.1.2 and that the liquidity requirements must always be lower than the resources available. This change will increase the accuracy of the Framework and does not represent a change in the methodology or procedure of LCH SA.
                </P>
                <P>
                    Section 4.1.5, 
                    <E T="03">Model assumptions,</E>
                     will be revised to provide that liquidity resources must be sufficient to meet LCH SA's liquidity requirements for the next seven (7) days in stressed situations. This section currently provides that liquidity resources must be sufficient to meet LCH SA's liquidity requirements for the next five (5) days.
                    <SU>25</SU>
                    <FTREF/>
                     The change incorporates a model validation recommendation to extend the LCR and consequently also the Operational Target to a 7 day period in order to align the liquidity monitoring time horizon to the RepoClear service new maximum holding period to manage a default (changed from a 3-day to 5-day holding period since the end of June 2022, to which LCH SA added 2 days of settlement convention). Additionally, to enhance the clarity, details related to the management of the former horizon have been removed in order to clearly state that the horizon is 7 days and results will be displayed without any aggregation.
                </P>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         Consistent with this change, LCH SA will take into account the maximum daily switches from cash and ECB eligible cash securities to non-Euro denominated securities observed over seven (7) days rather than five (5) days, as currently provided.
                    </P>
                </FTNT>
                <P>In addition (4.1.5.d), the provisions of this section describing the liquidity requirements drivers, which assume, in part, that 100 percent (100%) of the excess cash and excess ECB eligible securities will be withdrawn over the 3-day period will be revised. Specifically, the assumptions that the two largest individual Clearing Members will withdraw their excess on day one (T) and that the third and fourth largest Clearing Members will withdraw their excess on day two (T+1) will be revised to provide instead that (a) the two Clearing Member Groups that have the largest amount of excess collateral will withdraw their excess on T, and (b) the third and fourth Clearing Member Groups that have the next largest amount of excess collateral will withdraw their excess on T+1. In each case, the remaining Clearing Members will withdraw their excess on the third day (T+2). Precision on the footnote to specify that Portuguese and Finnish government bonds posted via the triparty solution are excluded from the liquid assets as these securities are not transferrable to the BdF due to operational constraints.</P>
                <P>For the liquidity requirement that aims to quantify the potential substitution of cash collateral/ECB eligible securities (4.1.5.e), LCH SA will take into account the maximum daily switches from cash and ECB eligible cash securities to non-Euro denominated securities observed over seven (7) days rather than five (5) days as currently provided to incoroporate the model valitation recommendation. In order to be consistent with this change from five to seven days in the time horizon, two additional definition of amount of switch corresponding to T+5 and T+6 have been added. Moreover, it will be clarified that on Q3 2022 CaLM Front Office demonstrated the ability to transfer ECB eligible securities to BdF within 30 minutes for all eligible countries. The list of specific countries will be removed from the Framework as it is dynamic and depends on the collateral eligible at the CCP that can be found on the LCH SA website (a footnote will be added to point towards website). With respect to the amount of equity lodged, as LCH SA takes the maximum amount of switched observed, the reference to 100 million will be removed as the amount is a dynamic figure. It will also be precised that the amount of equity deposited over the past 3 years which is also a dynamic figure remains negligible. These changes will improve the accuracy of the Framework and do not represent a change in the methodology or procedure of LCH SA.</P>
                <P>For Section 4.1.5.f which describes the potential intraday additional liquidity injection that may generate securities carried overnight it will be specified that the amount is calibrated as the maximum EOD securities carried over night over the whole time series available. This change will increase the accuracy and clarity of the Framework and does not represent a change in the methodology or procedure of LCH SA.</P>
                <P>
                    Moreover, Section 4.1.5.g will be revised to modify the targeted estimated margin reduction of non-defaulting Clearing Members. Currently, estimated margin reduction is calculated over a three-day period. As revised, targeted estimated margin reduction will be calculated over seven (7) consecutive days to address model validation recommendation.
                    <SU>26</SU>
                    <FTREF/>
                     To reflect this change, a detailed table has been added describing the margin reduction rate per day of the horizon period in line with the above In order to enhance the wording, two bullet points have been revised to state that (a) margin reduction applied is greater than the biggest one observed in the historical window considered for the calibration (b) for each day, the reduction is over the 99,7% percentile on the available set of data. In order to precise the size of the lookback period of observation, a footnote will be added detailing the current start date and end date. One footnote will be also updated to provide that Portuguese and Finnish government bonds posted via the triparty solution are excluded from the liquid assets because such securities are not transferrable to the BdF due to operational constraints.
                </P>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         The overall compounded margin reduction will be above the maximum historical 7-day margin reduction observed.
                    </P>
                </FTNT>
                <P>These additional changes will increase the accuracy and clarity of the document and does not represent a change in the methodology or procedure of LCH SA.</P>
                <P>Finally, Section 4.1.5.h will be reworded to specify that the liquidity requirements stemming from estimated Variation Margin payment to be processed towards the interoperable CCP is calculated on the basis of the Initial Margin actually posted at LCH SA to cover a 5-days holding period to be spread out over a 5-days period according to a simulated market stress based on historical yield shifts (third bullet point). The rewording of the introduction of 4.1.5.h aims to clarify the computation of the theoretical allocation of IM (leading to the removal of one footnote that was duplicated) as well as to reflect the change of branding. These changes will increase the accuracy and clarity of the document and does not represent a change in the methodology or procedure of the LCH SA.</P>
                <P>As mentioned, Please also note that reference to the depth of time series (4.1.5.e and 4.1.5.f) are proposed to be removed as available set of data are wider and every points are considered. This would avoid LCH to periodically review the depth in the wording.</P>
                <P>Finally, the notion “DF” has been added in 4.1.5.i to reflect the usual acronym of the default fund. The review was the opportunity also to correct a typo in the third bullet point of this section.</P>
                <P>
                    Section 4.2 of the Framework, 
                    <E T="03">LCR,</E>
                     which describes the manner in which 
                    <PRTPAGE P="1956"/>
                    the LCR is calculated, will be revised as follows:
                </P>
                <P>
                    Section 4.2.1, 
                    <E T="03">Model overview,</E>
                     will be revised to provide that the purpose of the LCR Cover 2 scenario is to allow LCH SA to ensure that it has enough liquidity in the case of default of the two largest Members Groups during the seven (7) days following the default, rather than five (5) days, as is currently provided. Moreover the sentence: “
                    <E T="03">3</E>
                     days holding period of margin 
                    <E T="03">collateral, i.e.,</E>
                     SA ensures it has sufficient liquidity to meet non-defaulting member's cash requests even if SA is waiting for the defaulter's 
                    <E T="03">margin collateral</E>
                     to be liquidated” will be revised to read: “
                    <E T="03">5</E>
                     days holding period of margin 
                    <E T="03">requirement, i.e.,</E>
                     SA ensures it has sufficient liquidity to meet non-defaulting member's cash requests even if SA is waiting for the defaulter's 
                    <E T="03">position</E>
                     to be liquidated”. These changes will enhance the accuracy and clarity of the document and do not represent a change in the methodology or procedure of LCH SA (
                    <E T="03">i.e.,</E>
                     “requirement” is an enhanced wording as the objective is to cover the clean risk (collateral might include excess). Similarly, “positions” better clarifies the liquidity needs that are present until the final liquidation of the complete position of the Defaulted Members.
                </P>
                <P>
                    Further, the sentence: “The ERCO has approved the 
                    <E T="03">5</E>
                     days liquidity horizon as per 
                    <E T="03">the article 22 of</E>
                     the Group liquidity risk policy” will be revised to read: “The ERCO has approved the 
                    <E T="03">7</E>
                     days liquidity horizon as per the Group liquidity risk policy”. The change will remove a dependency between the two documents as the number of articles may change when the Group Liquidity Policy is updated on an annual basis, while ensuring that the policy content is referred in the Framework.
                </P>
                <P>
                    Finally, the sentence: “The cover 2 is computed by taking into account the liquidity risks related to clearing members within the same group across all services 
                    <E T="03">within</E>
                     the CCP that are aggregated” will be revised to read: “The cover 2 is computed by taking into account the liquidity risks related to clearing members within the same group across all services 
                    <E T="03">of</E>
                     the CCP that are 
                    <E T="03">then</E>
                     aggregated”. These last changes do not trigger any methodology changes but have been amended to enhance the clarity. The reference to footnote (24) is proposed to be removed as it refers to a non existing footnote (typo).
                </P>
                <P>
                    Section 4.2.2, 
                    <E T="03">Model inputs and Variable selection,</E>
                     and Section 4.2.4, 
                    <E T="03">Mathematical formula derivation and algorithm and numerical approximation,</E>
                     will be revised to provide that securities pledged at the BdF and included among Total Available Assets will be valued at stressed market prices and include the ECB haircut effect on the resulting figures. The notion of “for each market” is proposed to be removed to preserve clarity. At the same time for the computation of VM erosion, the market risk impact arising from the contractual settlement of RepoClear will be excluded from the computation of the component as treated on the asset side as previously described (
                    <E T="03">i.e.,</E>
                     the component that was previously considered in liabilities will be incorporated in the assets as a reduction of the amount of liquidity sourced from the clearing securities pledged to BdF, cf 4.2.4.c). For this purpose, the sentence “on top of which is added the market stress risk impact on the contractual settlement for repoClear” will be removed. These changes have the purpose of adressing a model validation recommendation to enhance the treatment of market stress in the computation of liquidity sourced by the Central Bank.
                </P>
                <P>Moreover an update of wording will be done to consider the Total Default Liabilities and Total Available Assets as plural rather than singular as currently the case. It will be specified that in the VM Erosion calulation all LCH SA services are considered that is Cash &amp; Derivatives, Repoclear, EGC, and CDS markets. Two footnotes will be updated to specify that Portuguese and Finnish government bonds posted via the triparty solution are excluded from the liquid assets because not transferrable to the BdF due to operational constraints (4.2.2/4.2.4). These changes have will increase the accuracy and clarity of the document and do not represent a change in the methodology or procedure of LCH SA.</P>
                <P>Finally, additional clarifications will be made regarding the treatment of FCM/BD client resources in the LCR. In particular, LCH SA will further specify that in a context of default (and purpose of the LCR monitoring) LCH SA will only treat FCM/BD client collateral as available liquidity resources if and only if this FCM/BD client defaults and generates some liquidity needs. Its resources will not be considered as available liquidity assets for any other FCM/BD clients and/or the FCM/BD clearing member or any other clearing member of the CCP. In particular, in case of one FCM/BD client defaulting, other FCM/BD clients assets will not be considered to cover the liquidity needs of the defaulting FCM/BD client. These changes are also replacing “clearing member” with client where relevant to increase clarity.</P>
                <P>The changes will enhance the accuracy and clarity of the document and does not represent a change in the methodology or procedure of LCH SA.</P>
                <P>
                    Section 4.2.5, 
                    <E T="03">Model Assumptions,</E>
                     describes the various risks that each business line must consider in determining liquidity requirements as well as other liquidity requirements that LCH SA must meet.
                    <SU>27</SU>
                    <FTREF/>
                     Title of Section 4.2.5.1 will be changed to `Description of risks per Business line' to reflect that different risks are tackled in different sub section.
                </P>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         As noted earlier, in addition to its CDSClear service, LCH SA provides clearing services in connection with cash equities and derivatives listed for trading on Euronext (EquityClear), commodity derivatives listed for trading on Euronext (CommodityClear), and tri-party Repo transactions (RepoClear). LCH SA also maintains an interoperability link with Euronext Clearing.
                    </P>
                </FTNT>
                <P>
                    Section 4.2.5.1.1, 
                    <E T="03">RepoClear,</E>
                     will be revised to provide that settlement cash outflows will be calculated over a period of 7 days and on a gross basis, aggregated by ISIN, settlement date and Clearing Member level. The final settlement outflows are then aggregated at the Clearing Member Group level without allowing any netting across members of the same Clearing Member Group. The objective of these changes is to address two model validation recommendations: to align the LCR liquidity monitoring period to the RepoClear new maximum holding period to manage a default (5 days holding period of margin +2 of settlement convention); and to not allow any netting between entity of the same Group. Moreover, a table summarizing the liquidity requirements according to the direction of the repo transactions as well as a paragraph describing the specific treatment of forward starting repo in the calculation of the settlement obligation outflows have been removed because a new enhanced algorithm was designed and described in the new sections 4.2.5.1.1.1 and 4.2.5.1.1.2 as described later in the present form. One bullet point is proposed to be removed as well as the sentence “Note that the post default date forward start leg of cash borrower transaction are excluded for the LCR calculation (
                    <E T="03">e.g.,</E>
                     starts date: Default date + 1 day and returns legs: Default date +2). The transactions are performed through DVP so LCH SA will fail to deliver the securities leading no liquidity requirements related to the returns legs to factor in the LCR to keep consistency with the new algorithm.
                </P>
                <P>
                    Section 4.2.5.1.1.1, 
                    <E T="03">Liabilities contractual obligations on physical delivery,</E>
                     will describe the methodology 
                    <PRTPAGE P="1957"/>
                    to compute liabilities due to settlement obligations. In particular, in case of default, LCH SA shall assume and honour the obligations of the defaulted Members. In case of securities with physical settlement, this may represent substantial liquidity needs for LCH SA. The enhanced methodology presented in this section leverages on the actual management of settlement instructions performed by the Fixed Income Operations department during an event of default to fully take into account in the calculation of the liquidity needs the specific settlement dynamics over the time horizon of the LCR with the objective to more closely align the computation of the LCR with the actual default management process.
                </P>
                <P>To model the settlement obligation, the DCO would start by constructing the contractual balance of net buyer/seller position by Clearing Member, ISIN and date within the LCR time horizon:</P>
                <P>1. Identify transactions (each leg independently for repos) that settles within the time horizon of the LCR and allocate, to the settlement date, the contractual cash amount to be settled and the corresponding nominal of securities to be delivered; and</P>
                <P>2. Aggregate cash amounts and nominals by member, ISIN and date.</P>
                <P>This contractual view of cash and security flows is then adjusted to take into account the eventual effect of carrying forward the liquidity position (the effect of one day fails on the contractual flows of the following dates). In fact, in case of a net seller position on date t, LCH SA would fail to deliver securities if they are not already sourced and/or pledged at the BdF and would continue to fail until the date t' on which the balance is net buyer (or until the end of the time horizon when the portfolio would be perfectly matched again). In that case, LCH SA would receive no cash on date t for the securities in which it fails to deliver and would need to inject less cash into the settlement system on date t' because of the netting effect of carrying forward. The real cash injection flows obtained are aligned with the Operations Team view of the settlement obligation in case of default.</P>
                <P>When the real cashflow injections are obtained as described above for each member they are then aggregated at group level.</P>
                <P>A simplified numerical example is provided to demonstrate the sequence of steps used to calculate the liquidity needs deriving from settlement obbligation.</P>
                <P>The changes described in this section will improve the liquidity monitoring of LCH SA and address two model validation recommendations: to improve the liquidity needs estimation related to Settlement Risk and to not allow any netting between entity of the same Group.</P>
                <P>
                    Section 4.2.5.1.1.2, 
                    <E T="03">Assets: settlement securities pledged at Central Bank,</E>
                     will describe the methodology to compute the liquidity raised through the pledge at a Central Bank of the settlement securities withdrawn from the settlement system on behalf of the defaulter. In particular, when LCH SA pledges eligible securities at the Central Bank in exchange of liquidity, two important factors need to be considered:
                </P>
                <FP SOURCE="FP-1">—the market price of the securities that may be decreased by unfavorable market conditions therefore reducting the value of the collateral and consequently the amount of liquidity that can be sourced out of it; and</FP>
                <FP SOURCE="FP-1">—the haircut applied by the Central Bank when lending cash to LCH SA in exchange of securities.</FP>
                <P>The changes described in the following paragraph provide a summary of the calculation performed by the DCO when modelling the liquidity that it would be able to source from the Central Bank.</P>
                <P>The amount raised is the sum of the unstressed assets value after taking into account the ECB haircut and a stress price market impact applied to the value of the securities. In order to calculate the amount of liquidity raised from the BdF, LCH SA will consider the real security flows calculated in Section 4.2.5.1.1.1 which are equivalent to securities pledged at/retrieved from the BdF (with an opposite direction with respect to settlement). The securities are then valued at current market price at the moment of default with the application of an ECB haircut. To quantify the market impact, a preliminary screening is applied in order to identify correctly only the subset of transactions to which the market impact applies because they are not covered by offsetting inflow. In particular for long cash transactions or Cash Borrower Repo—Return Leg:</P>
                <P>
                    • 
                    <E T="03">Before the settlement date:</E>
                     an eventual bond price decrease would result in a margin decrease of the non-defaulting member due to Variation Margin credit which is accounted for in the LCR liabilities in a separate entry.
                </P>
                <P>
                    • 
                    <E T="03">On the settlement date:</E>
                     LCH SA would get the securities from the non-defaulting member, pledge them at the BdF and receive an amount of cash equal to the stressed price of the bond minus the haircut. The additional liquidity impact, with regards to the unstressed assets described previously, rises from the bond price move from the default date until the settlement date. Hereunder, we will refer to this component by “Settlement Market Price Impact”.
                </P>
                <P>
                    • 
                    <E T="03">After the settlement date:</E>
                     once the bond is pledged overnight, the price decrease afterwards would trigger an additional liquidity impact to cover the cash that needs to be returned to the BdF because of the lower amount of the collateral deposited, 
                    <E T="03">i.e.,</E>
                     the price move from the settlement date until the date on which LCH SA will have a settlement obligation to deliver the bond (or until the book is perfectly matched again after the settlement of the auction). Hereunder, we will refer to this component by “Pledge Market Price Impact”.
                </P>
                <P>The total market impact is calculated as the sum of Settlement Market Price Impact and Pledge Market Price Impact. The bond prices moves generating the market impact is calculated in accordance with RepoClear stress test scenarios. The final amount of liquidity retrieved from the BdF resulting from the pledge of securities retrieved from settlement on behalf of the defaulted members will be:</P>
                <FP SOURCE="FP-2">Liquidity retrieved from the BdF (t) = Real Security Flow * Market Price at moment of default * (1−ECB Haircut)−Settlement Market Price Impact−Pledge Market Price Impact.</FP>
                <FP>A simplified numerical example is added to the Framework to demonstrate the sequence of steps used to calculate the liquidity amount retrieved from the BdF.</FP>
                <P>The change will improve the liquidity monitoring of LCH SA and address a model validation recommendation to improve the liquidity needs estimation related to Market Risk.</P>
                <P>To remain consistent with the calculation of settlement obligations, after calculating the Liquidity retrieved from the BdF for all dates in the LCR period at Member level, the amounts are aggregated at the Clearing Member Group level. This change address a model validation recommendation.</P>
                <P>
                    Section 4.2.5.1.1.3, 
                    <E T="03">Market Risk,</E>
                     will be revised to provide that, in addition to the settlement obligations driven flows, the position of the defaulter may generate a liquidity drain for LCH SA in the form of negative mark to market to be paid to non-defaulting members. The formula to estimate this amount is changed and will consider the worst stress loss of the defaulter position according to the relevant RepoClear stress test scenario and add additional margin to model any concentration, 
                    <PRTPAGE P="1958"/>
                    market liquidity issues. The purpose of this change is to address a model validation recommendation by improving the liquidity needs estimation related to Market Risk in the LCR. Additionally, a footnote will be added to disclose that a list of stress scenario is reported in appendix 6.7.
                </P>
                <P>
                    Section 4.2.5.1.2, 
                    <E T="03">€GCPlus,</E>
                     will be revised to provide that, when calculating the settlement driven cash outflows, the aggregation is based on data provided by the triparty agent and that only positions in which the defaulter is a cash borrower (collateral giver) in the first leg of the repo and, therefore, collateral taker when the repo closes, generate a liquidity need. Therefore, in case of default of a Member collateral giver in the first leg, LCH SA has to inject cash and withdraw securities when the repo closes (cf new footnotes).
                </P>
                <P>Finally a repetition of words have been cancelled to remove redundancy in the text. The changes will enhance the accuracy and clarity of the Framework and do not represent a change in the methodology or procedure of LCH SA.</P>
                <P>
                    Section 4.2.5.1.2.1, 
                    <E T="03">Market risk,</E>
                     will be revised to provide that for €GCPlus the additional liquidity needs generated by negative mark to market payments to non-defaulting members is estimated in line with what is done for RepoClear 
                    <SU>28</SU>
                    <FTREF/>
                     as the worst stress loss of the defaulter position according to the relevant €GCPlus stress test scenario and adding additional margins. The change will incorporate a model validation recommendation by improving the liquidity needs estimation related to Market Risk in the LCR.
                </P>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         Please refer to changes to section 4.2.5.1.1.3 described in the present document.
                    </P>
                </FTNT>
                <P>Moreover, a numerical example has been added to the Framework to demonstrate that the eventual BdF haircut will always be covered by the collateral posted by the collateral giver as requested by the current margin methodology (corresponding to “Example”). The change will increase the accuracy and clarity of the document and does not represent a change in the methodology or procedure of LCH SA.</P>
                <P>
                    Section 4.2.5.1.3.1, 
                    <E T="03">Cash Equity,</E>
                     will be revised to provide that the settlement cash outflows will be calculated on a gross basis at the Clearing Member level and then aggregated at the Clearing Member Group level without allowing any netting across the Clearing Members of the same Group. The objective of the change is to enhance the accuracy and clarity of the document and does not represent a change in the methodology or procedure of LCH SA.
                </P>
                <P>
                    Moreover, the methodology to consider among the liquidity requirements the equity settlement arising from the expiration of 
                    <E T="03">physically</E>
                     settled futures is detailed. In particular, in case the defaulting member is long futures which expire during the LCR horizon, LCH SA will have to pay the future price to the non-defaulting counterparty in order to settle the physical underlying. Therefore the enhanced algorithm daily identifies all the potential maturing long futures positions on the day of the computation and on the upcoming business day as well, identifies the positions of the Cover 2 Members Group and finally, given the potential physical settlement, adds the relevant liquidity needs to the computation of the LCR. A numerical example is included to provide a sample of the calculation.This change has the purpose of addressing a model validation recommendation by including the liquidity needs related to the expiry of physical delivery single stock futures in the LCR.
                </P>
                <P>
                    In addition, this section will provide that the liquidity needs generated by negative mark to market payments to be made to non-defaulting members is changed in line with what is done for the other LCH SA services 
                    <SU>29</SU>
                    <FTREF/>
                     (RepoClear, €GCPlus, CDSClear) and will be calculated as the worst stress loss of the defaulter position according to the relevant EquityClear stress test scenario with the addition of additional margins.
                </P>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         Please refer to changes for Sections 4.2.5.1.1.3, 4.2.5.1.2.1 and 4.2.5.1.4 described in the present document.
                    </P>
                </FTNT>
                <P>The objective of the change is to incoporate a model validation recommendation by improving the liquidity needs estimation related to Market Risk in the LCR.</P>
                <P>A footnote has been added to improve the accuracy of the document to specify that the full list of stress scenarios used is presented in a dedicated Appendix.</P>
                <P>Finally, this section will explain that because equities are not eligible at the BdF they will not be considered as liquidity sources in the assets of the LCR. The change will increase the accuracy and clarity of the document and does not represent a change in the methodology or procedure of LCH SA.</P>
                <P>
                    Section 4.2.5.1.3.2, 
                    <E T="03">Listed derivatives,</E>
                     will be revised to clarify that futures on equity index contracts are included among the listed derivatives instruments considered in the calculation of the LCR and that derivatives expirations occur on a monthly basis rather than the previously stated quarterly basis. These changes will improve the accuracy and clarity of the document and does not represent a change in the methodology or procedure of LCH SA (
                    <E T="03">i.e.,</E>
                     monthly expiry is already efficiently implemented in the computation of the LCR).
                </P>
                <P>
                    The calculation of the liquidity needs generated by negative mark to market payments to be done to non-defaulting members is changed in line with what is done for the other LCH SA services 
                    <SU>30</SU>
                    <FTREF/>
                     (RepoClear, €GCPlus, CDSClear) and will be calculated as the worst stress loss of the defaulter position according to the relevant EquityClear stress test scenario with the addition of Additional margins. The change will address a model validation recommendation by improving the liquidity needs estimation related to Market Risk in the LCR. Finally, please note scenario is now stated in plural to reflect that several scenarios (disclosed in appendix 6.7) are used to model stressed VM.
                </P>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    Section 4.2.5.1.4, 
                    <E T="03">Credit Default Swaps,</E>
                     will be revised to clarify that the calculation of the liquidity needs generated by negative mark to market payments to be done to non-defaulting members is changed in line with what is done for the other LCH SA services 
                    <SU>31</SU>
                    <FTREF/>
                     (RepoClear, €GCPlus, EquityClear) and will be calculated as the worst stress loss of the defaulter position according to the relevant CDSClear stress test scenario with the addition of additional margins. The change adresses a model validation recommendation by improving the liquidity needs estimation related to Market Risk in the LCR. Finally, please note scenario is now stated in plural to reflect that several scenarios (disclosed in appendix 6.7) are used to model stressed VM.
                </P>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         Please refer to changes for Sections 4.2.5.1.1.3, 4.2.5.1.2.1, 4.2.5.1.3.1 and 4.2.5.1.3.2 described in the present document.
                    </P>
                </FTNT>
                <P>A footnote have been added to improve the accuracy of the document to specify that the full list of stress scenarios is disclosed in a dedicated Appendix.</P>
                <P>Section 4.2.5.2 will be revised to modify those provisions of the Framework relating to the other liquidity requirements to be taken into account in calculating the LCR.</P>
                <P>
                    Section 4.2.5.2.1 will be revised to provide that the Operational Target to be included in the calculation of the LCR will be restated by removing margin outflows calculated in the Operational Target and related to Cover 2 for LCR. This is because LCH SA has the right to fully use the collateral of the 
                    <PRTPAGE P="1959"/>
                    defaulters including excess. The changes enhance the accuracy and clarity of the document and do not represent a change in the methodology or procedure of LCH SA.
                </P>
                <P>
                    Section 4.2.5.2.2, 
                    <E T="03">Margin non-cash collateral,</E>
                     will be revised to provide that LCH SA will compute the pure stress loss of such collateral rather than the stress loss over haircut (less conservative) as currently stated, by applying a set of stress scenarios used by RepoClear in the calibration of the Default Fund and choosing the one that generates the biggest liquidity exposure in terms of Cover 2. The choice of application of Repoclear scenarios is driven by the fact that only bonds deposited as collateral can be used to raise liquidity while equities are completely excluded from the calculation of liquid assets. The change aims to improve the liquidity monitoring by leveraging on the same coherent scenarios for all bonds position included in the LCR computation. A list of scenarios is disclosed in appendix of the LRMF.
                </P>
                <P>
                    Section 4.2.5.2.3, 
                    <E T="03">CaLM investments,</E>
                     will be revised to specify that when calculating the liquidation losses related to the collateral posted by the defaulting Member through the reverse repo activity and the potential outright purchases losses deriving from the CCP portfolio, LCH SA will apply the driving stress scenario chosen among the set of scenarios from RepoClear consistent with the determination of the Cover 2 described in section 4.2.5.4. “Potential” has been added because the loss on the outright portfolio will be only realized if the DCO is forced to sell the portfolio because of liquidity needs and does not wait until maturity. The changes will increase the accuracy and clarity of the document and do not represent a change in the methodology or procedure of LCH SA.
                </P>
                <P>
                    Section 4.2.5.2.4, 
                    <E T="03">Collateral pledge modelling,</E>
                     is added to describe in details how pledged collateral has to be modelled when calculating the asset of the LCR. In particular LCH SA assumes that Clearing Members will utilize their ability to pledge collateral near the maximum allowed on each LCH SA service and, therefore, this amount will be subtracted from the amount of non-cash collateral included in the LCR assets.
                </P>
                <P>The expected additional pledge will be calculated as the difference between the Maximum pledge capacity scaled by a parameter that can capture Clearing Members behaviour and the actual pledge capacity used currently by the Clearing Members.</P>
                <P>
                    The Maximum pledge capacity amount will take into consideration eventual concentration limits in places for specific LCH SA services (
                    <E T="03">i.e.,</E>
                     Repoclear, €GCPlus and EquityClear).
                </P>
                <P>In contrast, for the Members not having a pledge account active, CDSClear non-cash collateral deposited under Full Title Transfer with the exclusion of securities in DKK, NOK, SEK, JPY, CHF, CAD and AUD is considered to be eligible to raise liquidity and, therefore, is included among liquidity resources. This section has been added to address a model validation recommendation by disclosing more details in the modelling of the collateral pledge.</P>
                <P>
                    Section 4.2.5.3, 
                    <E T="03">Stress scenario selection,</E>
                     will be revised to clarify that the stress tests scenarios selected for each LCH SA service will be consistent with a market state resulting from the default of the Cover 2 as assumed by the LCR. The scenarios selected are taken from the set of scenarios used to calibrate the Default Fund amount on the different services and in particular include scenarios that simulate an increase in interest rates and credit spreads and a decrease of equity indexes. The change has the purpose of increasing the accuracy and clarity of the document and ensure that the stress scenarios chosen are coherent with the LCR assumption of Cover 2 default and the consequent increased volatility on the market. In other terms, additions of wording aim to highlight the consistency of stressed scenarios applied on different market to define the Cover 2 (
                    <E T="03">i.e.,</E>
                     rate up (iii), index and equities down (ii) and CDSClear widening (i)).
                </P>
                <P>A full list of the selected stress test scenarios for each service is set out in an Appendix to the Framework. The driving scenario is then selected as the one that produces the largest stress loss on a Cover 2 basis as described in Section 4.2.5.4.</P>
                <P>The list of scenarios has been updated to select, among the available scenarios used by the LCH SA services, only the most relevant ones given the LCR assumptions. The purpose is to improve the liquidity monitoring of LCH SA.</P>
                <P>
                    In addition, when describing the additional stress scenario where a downgrade of sovereign ratings results in an increase of ECB haircuts applied when the securities are pledged at the BdF to raise liquidity, the table reporting the values of the ECB haircuts applicable will be updated. The new values are the official values applied by the ECB 
                    <SU>32</SU>
                    <FTREF/>
                     on each eligible collateral posted to raise liquidity as a function of the collateral category and maturity.
                </P>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         Please refer to 
                        <E T="03">https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32023O0832.</E>
                    </P>
                </FTNT>
                <P>
                    Section 4.2.5.4, 
                    <E T="03">Cover 2 selection,</E>
                     provide the description of the methodology used by the DCO to identify the two Member Groups most exposed in term of liquidity (Cover 2) which are assumed to be simultaneously in default in the LCR. Liquidity needs deriving from Settlement risk, Market risk and Investment risk are aggregated to rank the Member Group and identify the most exposed ones. The section will be revised to specify that the Cover 2 will be identified by calculating the following liquidity requirements at the Clearing Member Member level, aggregating the total requirement at the Clearing Member Group level and then choosing the two most exposed Clearing Member Groups:
                </P>
                <P>• Stress Variation Margin: for all the services the variation margins are modelled by applying the most punitive scenario among the chosen sets and consistent with the LCR assumptions;</P>
                <P>• Settlement liquidity requirements due to RepoClear and Cash equity settlement obligations. In case of securities pledged at the BdF their value would be stressed according to the scenario that would generate the highest loss;</P>
                <P>• Non-cash Collateral stress losses are estimated by stressing the non-cash collateral eligible for BdF liquidity with the set of scenarios consistent with the LCR assumptions;</P>
                <P>• Investment stress losses over haircut are estimated by applying the stress scenarios to the collateral received from the reverse repo activity with each specific counterpart; and</P>
                <P>• ECB Haircut impact is quantified by applying the relevant haircut to all the securities received from a specific member that are eligible for Central Bank liquidity.</P>
                <P>Between the set of scenarios used from the RepoClear Stress Test framework, the set of scenarios used from the CDSClear Stress Test framework and the set of scenarios used from the EquityClear stress test framework, only the one jointly generating the maximum loss of the sum of all the above elements for the two most exposed Clearing Member Groups will be used to determine the Cover 2 and calculate the final LCR.</P>
                <P>
                    The changes have the objective to coherently include in the computation of the Cover 2 the changes related to the update of the stress test scenarios considered in the LCR (described in 
                    <PRTPAGE P="1960"/>
                    Section 4.2.5.3), the changes related to the impact of market risk on the securities pledged at Central Bank (described in Section 4.2.5.1.1.2) and the changes related to the estimation of the Variation Margin Outflows (described in Sections 4.2.5.1.1.3, 4.2.5.1.2.1, 4.2.5.1.3.1, 4.2.5.1.3.2 and 4.2.5.1.4).
                </P>
                <FP SOURCE="FP-1">—Section 4.3: All the changes reflect the new branding of CC&amp;G (Euronext Clearing). No change in the methodology or procedure applied by LCH.</FP>
                <P>
                    Section 5, 
                    <E T="03">Model Performance Testing and Ongoing Monitoring,</E>
                     will be revised to provide throughout that the length of time for which LCH SA must maintain liquidity resources sufficient to meet its liquidity requirements for each service will be extended from five (5) days to seven (7) days.
                    <SU>33</SU>
                    <FTREF/>
                     In addition, Section 5.1, 
                    <E T="03">Ongoing Monitoring,</E>
                     will be revised to provide that cash or non-cash collateral available for pledge to the BdF should represent at least 25 percent (25%) of LCH SA's available liquid resources after the default of its most significant Clearing Member. This section currently provides that cash alone should represent at least 25 percent (25%) of LCH SA's available liquid resources after the default of its most significant Clearing Member. This change will align the text of the Framework to the updated text of the Liquidity Policy approved in 2022.
                </P>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         See, Section 5.1, 
                        <E T="03">Ongoing Monitoring,</E>
                         Section 5.3, 
                        <E T="03">Reverse Stress Test,</E>
                         and Section 5.3.1, 
                        <E T="03">Independent stress of various risk factors.</E>
                    </P>
                </FTNT>
                <P>
                    Section 5.3 on Reverse Stress Tests will be modified to include a paragraph providing the regulatory requirements pursuant to SEC Rule 17Ad-22(e)(7)(vi)(B) 
                    <SU>34</SU>
                    <FTREF/>
                     and SEC Rule 17Ad-22(e)(7)(vi)(C).
                    <SU>35</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         17 CFR 240.17Ad-22(e)(7)(vi)(B).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         17 CFR 240.17Ad-22(e)(7)(vi)(C).
                    </P>
                </FTNT>
                <P>
                    Consistent with this change, Section 5.3.1, 
                    <E T="03">Independent stress of various risk factors,</E>
                     which describes the single factor reverse stress test (or `core' reverse stress test), which examines the stress on liquidity outflows caused by different risk factors that are independently stressed (one signle factor at time) to assess extreme market conditions necessary to observe a breach of the LCR limit will be revised as follow:
                </P>
                <HD SOURCE="HD3">• Risk Factor 1: Liquid Assets Reduction</HD>
                <P>It will be stated that non-cash collateral deposited by Clearing Members and eligible for pledge at the BdF represents another primary source of liquidity for LCH SA.</P>
                <P>
                    The sentence `A primary source of liquidity for a CCP is from investments maturing management by the CaLM team at the opening of the day' will be revised to `A primary source of liquidity for a CCP is from investments maturing management 
                    <E T="03">performed</E>
                     by the CaLM team at the opening of the day'.
                </P>
                <P>
                    The sentence `The overall liquid 
                    <E T="03">asset is</E>
                     reduced to obtain the stress required to reduce the LCR below 100%' will be revised to `The overall liquid 
                    <E T="03">assets are</E>
                     reduced to obtain the stress required to reduce the LCR below 100%'.
                </P>
                <P>The changes described will improve the accuracy and clarity of the document and do not represent a change in the methodology or procedure of LCH SA.</P>
                <P>Moreover it will be stated that the reduction in assets necessary to breach the LCR will be compared against the 7 days historical data in order to assess the plausibility of the scenario rather than the 5 days historical data currently reported. The change has the purpose of aligning the time horizon of the reverse stress with the time horizon of the LCR (described in Section 4.2.1).</P>
                <HD SOURCE="HD3">• Risk Factor 2: Switches to Non ECB Eligible Assets</HD>
                <P>It will provide that when calculating the single factor reverse stress test that simulates a switch of collateral from ECB eligible assets to non-ECB eligible assets such that a liquidity breach occurs, the non-ECB eligible assets includes GILT or US bonds, Central Bank guarantee, equities, non-Euro non cash collateral, and pledge collateral. The addition of pledge collateral to the list will improve the accuracy and clarity of the document and does not represent a change in the methodology or procedure of LCH SA.</P>
                <P>The required amount of switches necessary to produce a liquidity breach will be compared against the 7 days historical data rather than the 5 days historical data currently reported in the Framework. The change has the purpose of aligning the time horizon of the reverse stress to the tme horizon of the LCR.</P>
                <HD SOURCE="HD3">• Risk Factor 3: Rating Downgrade of the Euro Zone Peripheral and Core Countries</HD>
                <P>
                    The sentence `This reverse stress test aims at modelling the downgrade of the relevant countries and estimate the theoretical ECB haircuts 
                    <E T="03">generating</E>
                     a liquidity shortfall' will be revised to `This reverse stress test aims at modelling the downgrade of the relevant countries and estimate the theoretical ECB haircuts 
                    <E T="03">needed to generate</E>
                     a liquidity shortfall'.
                </P>
                <P>The change described will improve the accuracy and clarity of the document and does not represent a change in the methodology or procedure of LCH SA.</P>
                <HD SOURCE="HD3">• Risk Factor 6: CC&amp;G VM</HD>
                <P>The subparagraph will be renamed Risk Factor 6: CC&amp;GEuronext Clearing VM to reflect the updated name of the interoperable CCP.</P>
                <P>The sentence `The direction of the position' will be revised to `The direction of the positions'.</P>
                <P>The change described will improve the accuracy and clarity of the document and does not represent a change in the methodology or procedure of LCH SA.</P>
                <P>Moreover it will be stated that this specific reverse stress test aims to asses the amount of VM fails by the interoperable CCP during 7 days that could generate a liquidity shortfall rather than 5 days as currently reported in the Framework. The change has the purpose of aligning the time horizon of the reverse stress to the tme horizon of the LCR.</P>
                <HD SOURCE="HD3">• Risk Factor 7: Multiple Defaults</HD>
                <P>
                    The sentence `Given that liquidity requirements are sized to a cover 2 standard, is it plausible that more than 2 
                    <E T="03">members</E>
                     defaults who could lead to a liquidity deficit' will be revised to `Given that liquidity requirements are sized to a cover 2 standard, is it plausible that more than 2 
                    <E T="03">member Groups</E>
                     defaults who could lead to a liquidity deficit'.
                </P>
                <P>
                    In addition, the sentence: “In order to answer this question, LCH SA ranks order Members Groups based on their ICS and starting from the ones with the worst ICS (and hence highest probabilities of default)” will be revised to read: “In order to answer this question, LCH SA ranks Members Groups based on their ICS and 
                    <E T="03">starts considering</E>
                     the ones with the worst ICS (and hence highest probabilities of default)”.
                </P>
                <P>Finally it will be added that all Clearing Member Groups with a credit score of 6 or higher will be considered in the reverse stress test. The changes described will improve the accuracy and clarity of the document and does not represent a change in the methodology or procedure of LCH SA.</P>
                <P>
                    Section 5.3.2.1, 
                    <E T="03">Context &amp; Objective,</E>
                     will be revised to provide that the combined reverse stress test scenarios 
                    <SU>36</SU>
                    <FTREF/>
                     that include multiple risk factors will be 
                    <PRTPAGE P="1961"/>
                    performed at least quarterly. The purpose of the change is to align the frequency of combined reverse stress stress described in the framework to the one state in the Liquidity Risk Policy.
                </P>
                <FTNT>
                    <P>
                        <SU>36</SU>
                         Combined reverse stress test scenario are known as “non core”. Please refer to change to Section 1.4 described previously herein.
                    </P>
                </FTNT>
                <P>
                    Section 5.3.2.2, 
                    <E T="03">Behavioural scenario,</E>
                     will be revised to provide a more updated example of report layout. The change will increase the accuracy and clarity of the document and does not represent a change in the methodology or procedure of LCH SA.
                </P>
                <P>
                    Section 5.3.2.3, 
                    <E T="03">Macro-economic scenario,</E>
                     describes the reverse stress test, which examines the stress on liquidity outflows caused by a set of macro-economic scenarios that combine market, credit and concentration risk to determine the number of defaults that LCH SA can sustain in a shocked macro-economic environment until it suffers a liquidity shortfall. This section will be revised, in part, to clarify that the market risk driving scenarios will be selected from the scenarios used to calculate LCR in accordance with the logic described in Section 4.2.5.4. The current Framework considers only 2 macroeconomic scenarios that will be replaced by the new set of scenarios dscribed in Appendix 6.7. Additional external rating downgrade will be considered on top of the selected market risk scenario as it is the case of the current Framework.
                </P>
                <P>Moreover, the Operational outflow considered in the scenario will be aligned to the calculation of the Operational Target and therefore assuming a margin reduction of 24.7% over 7 days.</P>
                <P>The changes will improve the liquidity monitoring of LCH SA by aligning the reverse stress test calculation to the changes proposed for the LCR and described in Sections 4.1.5g, 4.2.5.3, 4.2.5.4, and Appendix 6.7.</P>
                <P>This Section will also be revised to provide that LCH SA will consider Clearing Member Groups, rather than individual Clearing Members, when simulating the multiple defaults driven by credit quality criteria, concentration criteria or total liquidity exposure criteria as this Section currently provides. The changes will improve the accuracy and clarity of the document and does not represent a change in the methodology or procedure of LCH SA.</P>
                <HD SOURCE="HD3">• Multiple Defaults Based on the Credit Quality of the Member Groups</HD>
                <P>
                    The sentence `By expanding the analysis presented on the individual risk factor 
                    <E T="03">8</E>
                     this case highlights the evolution of the LCR 
                    <E T="03">for each</E>
                     macro-economic scenario' will be revised to `By expanding the analysis presented on the individual risk factor 
                    <E T="03">7</E>
                     this case highlights the evolution of the LCR 
                    <E T="03">under the driving</E>
                     macro-economic 
                    <E T="03">shock</E>
                     scenario'. The change has the purpose of correcting a typo and alignin the description to the new computation of the driving macroeconomic scenario described above.
                </P>
                <P>Moreover, the example table that reports a sample of member Groups and their respective liquidity needs will be updated to anonymize the name of each Group.</P>
                <HD SOURCE="HD3">• Multiple Defaults of the Most Concentrated Countries (FR &amp; US Member Groups)</HD>
                <P>
                    The sentence `More specifically, we assume that the 
                    <E T="03">Macro-Eco 2</E>
                     scenario 
                    <E T="03">(Peripheral shock accompanied with a contagion on core countries)</E>
                     affects French and the European entities of the US members (two different simulations)' will be revised to `More specifically, we assume that the 
                    <E T="03">Driving macro economic</E>
                     scenario affects French and the European entities of the US members (two different simulations)'. The change will align the description to the new computation of the driving macroeconomic scenario described above.
                </P>
                <P>
                    Moreover, the various report examples reported in this section displaying the multiple defaults of member Groups from most concentrated countries will be updated 
                    <SU>37</SU>
                    <FTREF/>
                     to provide a more recent example of report layout. The change will increase the accuracy and clarity of the document and does not represent a change in the methodology or procedure of LCH SA.
                </P>
                <FTNT>
                    <P>
                        <SU>37</SU>
                         Figures as of October 2022.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">• Default of the Biggest Member Groups in Terms of Liquidity (Cover N)</HD>
                <P>
                    The report example reported in this section displaying the default of the biggest Member Groups in terms of liquidity will be updated 
                    <SU>38</SU>
                    <FTREF/>
                     to provide a more recent example of report layout. The change will increase the accuracy and clarity of the document and does not represent a change in the methodology or procedure of LCH SA.
                </P>
                <FTNT>
                    <P>
                        <SU>38</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>Section 5.3.3 is being added to the Framework in order to include provisions governing frequency and reporting. This section specifies that LCH SA performs core reverse stress tests at least on a monthly basis and that the results of the analysis are shared with the CRO on a monthly basis and quarterly to LCH SA Risk Committee.</P>
                <P>LCH SA also performs an ad-hoc analysis of the existing stress testing scenarios, models, and underlying parameters and assumptions used in evaluating liquidity needs and resources through the core reverse stress tests exercise (i) when the products cleared or markets served display high volatility or become less liquid, (ii) when the size or concentration of positions held by the clearing agency's participants increases significantly, or (iii) in any other appropriate circumstances that would lead to a liquidity coverage ratio falling below the alert threshold of 107%. The ad-hoc analysis triggered by a liquidity coverage ratio falling below 107% are reported to LCH SA CRO, the Head of LCH SA Collateral and Liquidity Management division and to the LCH SA Risk Committee.</P>
                <P>
                    Section 5.5, 
                    <E T="03">Testing Summary and Model Limitation,</E>
                     will be revised to add a footnote to provide that single factor reverse stress tests are performed monthly. Single and combined reverse stress tests are performed quarterly. These requirements come from the LCH Liquidity Risk Policy.
                </P>
                <P>
                    Appendix 6.2, 
                    <E T="03">Members behavior analysis,</E>
                     that analyses the assumptions used in calculation the Operational Target and the LCR will be revised to provide that the volume of the non-ECB eligible non cash collateral (mainly Gilts, U.S. Treasury securities, securities denominated in Danish Krone, Norwegian Krone, Swedish Krona, Japanese Yen, Swiss Francs, Canadian Dollars and Australian Dollars and Central Bank Guarantee) will remain at a level that does not downgrade LCH SA liquidity profile (
                    <E T="03">i.e.,</E>
                     quarterly reverse stress test) and that LCH SA imposes concentration limits on non-Euro non cash collateral. The change will enhance the accuracy and clarity of the document and does not represent a change in the methodology or procedure of LCH SA.
                </P>
                <P>Moreover, this Appendix will be revised to specify that the margin reduction is estimated at 24.7% over 7 days assuming that the daily margin reductions are independent (sum of the daily margin reduction vs. 7 days margin reduction). This level is bigger than the historical margin reduction over 7 days observed over a 10-year lookback period. This change has the purpose of updating the Appendix to be coherent with the changes described is Section 4.1.5 and driven by the necessity to address a model validation recommendation. Finally the graph reporting the LCH SA total margin is updated to provide a more recent orverview of the data.</P>
                <P>
                    Appendix 6.3, 
                    <E T="03">Reminder of SA's sources of liquidity and related risk drivers,</E>
                     will be revised to update the table to include as a risk driver the 
                    <PRTPAGE P="1962"/>
                    pledge collateral. In particular it will provide that because of higher concern toward LCH SA, the Clearing Members may increase their use of the pledge collateral capacity. This behavior is modelled in the LCR. Moreover, LCH SA may adjust the maximum limit allowed in pledge.
                </P>
                <P>The change will align the Appendix with what presented in Section 4.2.5.2.4 and highlighted above.</P>
                <P>In addition, when reporting the cash settlement option in case of Euronext Clearing default, the following footnote will be updated to read: “There is a residual risk (uncertainty—delay/amount—with regards SA's margins return by Euronext Clearing administrator)”. The footnote is amended following the completion by LCH SA of its review of risk drivers and related mitigation measures for cash received from Euronext Clearing.</P>
                <P>
                    Appendix 6.4, 
                    <E T="03">Liquidity risk drivers synthesis by reports,</E>
                     will be revised to update the table summarizing the components of each liquidity indicator (Operational Target, LCR Cover 2 and LCR Euronext Clearing) to reflect the fact that the liquidity monitoring period will be extended from 5 days to 7 days and that the overall margin reduction considered is 24.7%. Moreover, for LCR Cover 2, the Appendix will provide that when calculating the settlement obligation and the resulting BdF liquidity, the securities pledge will take into account ECB haircut and market stress, and when estimating excess reduction LCH SA will consider only non-defaulting Clearing Members as LCH SA has the right to use for liquidity purposes any amounts left in excess from a defaulting Clearing Member.
                </P>
                <P>
                    Appendix 6.5, 
                    <E T="03">Liquidity risk monitoring report,</E>
                     will be updated by including the more recent layout versions of liquidity reports used by the DCO to monitor liquidity. The change will improve the accuracy and clarity of the document and does not represent a change in the methodology or procedure of LCH sA.
                </P>
                <P>
                    Appendix 6.7, 
                    <E T="03">Stress scenarios list,</E>
                     will be added to report the specific list of stress scenarios used for each service.
                </P>
                <P>
                    Appendix 6.8, 
                    <E T="03">Pseudo-code of settlement and market risk calculation,</E>
                     will be added to provide the details on the algorithm used to calculate the settlement obligation driven liquidity requirements in the monitoring of the LCR and the resulting BdF liquidity raised by pledging the securities withdrawn from the settlement systems. This appendix translate into a pseudo code the algorithm described in detail in sections 4.2.5.1.1.1 (liabilities contractual obligations on physical delivery) and 4.2.5.1.1.2 (settlement securities pledged at Central Bank). Different steps of computation are described covering both liabilities and assets and the resulting aggegations to get the finale outputs. The Appendix has the purpose of providing a technical overview of the implementation of the algorithm described in the referred sections and duly commented in the present 19b4. Please refer to such sections for a theorical decription of the methodology.
                </P>
                <P>Finally in the whole Framework the name of the interoperable CCP have been updated from “Cassa di Compensazione e Garanzia (CC&amp;G)” into “Euronext Clearing”.</P>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    LCH SA has determined that the Proposed Rule Change is consistent with the requirements of Section 17A of the Act 
                    <SU>39</SU>
                    <FTREF/>
                     and regulations thereunder applicable to it. In particular, Section 17A(b)(3)(F) of the Act requires, 
                    <E T="03">inter alia,</E>
                     that the rules of a clearing agency should be designed to “promote the prompt and accurate clearance and settlement of securities transactions . . . and, 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[.]” 
                    <SU>40</SU>
                    <FTREF/>
                     In addition, Regulation 17Ad-22(e)(7)(ii) 
                    <SU>41</SU>
                    <FTREF/>
                     requires a covered clearing agency to establish, implement, maintain and enforce written policies and procedures reasonably designed to assure that it holds qualifying liquid resources sufficient to meet the minimum liquidity resource requirement in each relevant currency for which the covered clearing agency has payment obligations owed to clearing members.
                </P>
                <FTNT>
                    <P>
                        <SU>39</SU>
                         15 U.S.C. 78q-1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>40</SU>
                         15 U.S.C. 78q-1(b)(3)(F).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>41</SU>
                         17 CFR 240.17Ad-22(e)(7)(ii).
                    </P>
                </FTNT>
                <P>As discussed above, the Framework is being amended primarily to enhance the manner in which the LCR is calculated, thereby increasing the robustness of LCH SA's liquidity profile. In particular, the amendments will: (a) revise the manner in which the settlement obligation is calculated by aligning it to the actual process used by the Operations Team during a default management and ensuring that no netting is allowed between Members of the same Group; (b) revise the manner in which securities pledged to the Banque de France are valued by providing that such securities be valued at the stressed mark-to-market price rather than the contract price; (c) extend from five (5) days to seven (7) days the length of time for which LCH SA must maintain liquidity resources sufficient to meet its liquidity requirements; (d) include the liquidity needs generated by the expiration of physically settled stock futures in the liquidity monitoring; and (e) require LCH SA, in calculating its required liquidity resources, to take into account that Clearing Members may switch from depositing non-cash collateral in a Full Title Transfer Account, which may be pledged at the BdF to obtain a liquidity line of credit, to depositing non-cash collateral instead in a Pledge Account.</P>
                <P>
                    By enhancing the manner in which the LCR is calculated, thereby increasing the robustness of LCH SA's liquidity profile, the policies and procedures set out in the amended Framework are designed to promote the prompt and accurate clearance and settlement of securities transactions and continue to assure the safeguarding of securities and funds that are in LCH SA's custody or control or for which it is responsible to be consistent with the requirements of Section 17A(b)(3)(F) of the Act.
                    <SU>42</SU>
                    <FTREF/>
                     Specifically, the Proposed Rule will revise the manner in which the settlement obligation liquidity requirements are calculated, revise the manner in which securities pledged at the BdF are valued, extend the length of time LCH SA must maintain its liquidity resources, include the liquidity needs from the expiration of physically settled stock futures and account for in the way LCH SA calculates its liquidity resources, the process by which Clearing Members pledge non-cash collateral. Further, the amended Framework continues to assure that LCH SA holds qualifying liquid resources sufficient to meet the minimum liquidity resource requirement in each relevant currency for which the covered clearing agency has payment obligations owed to Clearing Members, as required by Regulation 17Ad-22(e)(7)(ii).
                    <SU>43</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>42</SU>
                         15 U.S.C. 78q-1(b)(3)(F).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>43</SU>
                         17 CFR 240.17Ad-22(e)(7)(ii).
                    </P>
                </FTNT>
                <P>
                    LCH SA also believes that the Proposed Rule Change is consistent with Exchange Act Rule 17Ad-22(e)(1) 
                    <SU>44</SU>
                    <FTREF/>
                     that requires a covered clearing agency to establish, implement, maintain and enforce written policies and procedures reasonably designed to provide for a well-founded, clear, transparent, and enforceable legal basis for each aspect of its activities in all relevant jurisdictions. As described above, the Proposed Rule Change will ensure that the Framework complies with the provisions of SEC Rule 17Ad-
                    <PRTPAGE P="1963"/>
                    22(e)(7) 
                    <SU>45</SU>
                    <FTREF/>
                     with respect to liquidity risk, including with respect to its requirement to determine the amount and regularly test the sufficiency of the liquid resources held for purposes of meeting the minimum liquid resource requirement.
                    <SU>46</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>44</SU>
                         17 CFR 240.17Ad-22(e)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>45</SU>
                         17 CFR 240.17Ad-22(e)(7).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>46</SU>
                         17 CFR 240.17Ad-22(e)(7)(vi).
                    </P>
                </FTNT>
                <P>
                    Finally, LCH SA believes that the Proposed Rule Change is consistent with Exchange Act Rule 17Ad-22(e)(7)(vi)(B) 
                    <SU>47</SU>
                    <FTREF/>
                     and Rule17Ad-22(e)(7)(vi)(C).
                    <SU>48</SU>
                    <FTREF/>
                     Rule 17Ad-22(e)(7)(vi)(B) requires a covered clearing agency to establish, implement, maintain and enforce written policies and procedures reasonably designed to effectively measure, monitor, and manage the liquidity risk that arises in or is borne by the covered clearing agency, including measuring, monitoring, and managing its settlement and funding flows on an ongoing and timely basis, and its use of intraday liquidity by . . . [d]etermining the amount and regularly testing the sufficiency of the liquid resources held for purposes of meeting the minimum liquid resource requirement [as required by SEC Rule 17Ad-22(e)(7)(i)] by establishing requirements for conducting monthly comprehensive analyses of stress testing scenarios, models, parameters and assumptiosn with respect to liquidity needs.
                    <SU>49</SU>
                    <FTREF/>
                     Rule 17Ad-22(e)(7)(vi)(C) further provides that LCH SA conduct such analyses more frequently than monthly, “the products cleared or markets served display high volatility or become less liquid, when the size or concentration of positions held by [LCH SA's] participants increases significantly.” 
                    <SU>50</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>47</SU>
                         17 CFR 240.17Ad-22(e)(7)(vi)(B).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>48</SU>
                         17 CFR 240.17Ad-22(e)(7)(vi)(C).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>49</SU>
                         17 CFR 240.17Ad-22(e)(7)(vi)(B).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>50</SU>
                         17 CFR 240.17Ad-22(e)(7)(vi)(C).
                    </P>
                </FTNT>
                <P>
                    LCH SA is proposing to amend the Framework to reflect its current practice of conducting monthly analysis of its existing stress testing scenarios, models, and underlying parameters and assumptions used in evaluating liquidity needs and resources for purposes of ensuring they are appropriate for determining the LCH SA's identified liquidity needs and resources in light of current and evolving market conditions. LCH SA is also proposing to amend the Framework to include the additional requirement that it conduct more frequent analysis when the products cleared or markets served display high volatility or become less liquid, when the size or concentration of positions held by LCH SA's participants increases significantly, or in other appropriate circumstances. By revising the Framework to reflect its current practice of conducting monthly analysis and including the requirement to conduct more frequent analysis, subject to certain conditions, LCH SA believes that the Proposed Rule Change is therefore consistent with Exchange Act Rule 17Ad-22(e)(7)(vi)(B) 
                    <SU>51</SU>
                    <FTREF/>
                     and Rule 17Ad-22(e)(7)(vi)(C).
                    <SU>52</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>51</SU>
                         17 CFR 240.17Ad-22(e)(7)(vi)(B).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>52</SU>
                         17 CFR 240.17Ad-22(e)(7)(vi)(C).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Clearing Agency's Statement on Burden on Competition</HD>
                <P>
                    Section 17A(b)(3)(I) of the Act requires that the rules of a clearing agency not impose any burden on competition not necessary or appropriate in furtherance of the purposes of the Act.
                    <SU>53</SU>
                    <FTREF/>
                     LCH SA does not believe the Proposed Rule Change would have any impact, or impose any burden, on competition. The Proposed Rule Change does not address any competitive issue or have any impact on the competition among central counterparties. LCH SA operates an open access model, and the Proposed Rule Change will have no effect on this model.
                </P>
                <FTNT>
                    <P>
                        <SU>53</SU>
                         15 U.S.C. 78q-1(b)(3)(I).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">C. Clearing Agency's Statement on Comments on the Proposed Rule Change Received From Members, Participants or Others</HD>
                <P>Written comments relating to the Proposed Rule Change have not been solicited or received. LCH SA will notify the Commission of any written comments received by LCH SA.</P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change 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: (A) by order approve or disapprove such proposed rule change, or (B) institute proceedings to determine whether the proposed rule change should be disapproved.
                </P>
                <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
                <P>Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act.</P>
                <HD SOURCE="HD2">Comments May Be Submitted by Any of the Following Methods</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-LCH SA-2023-007 on the subject line.
                </P>
                <HD SOURCE="HD2">Paper Comments</HD>
                <P>• Send paper comments in triplicate to Secretary, Securities and Exchange Commission, 100 F Street NE, Washington, DC 20549-1090.</P>
                <FP>
                    All submissions should refer to file number SR-LCH SA-2023-007. This file number should be included on the subject line if email is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's internet website (
                    <E T="03">https://www.sec.gov/rules/sro.shtml</E>
                    ). Copies of the submission, all subsequent amendments, all written statements with respect to the proposed rule change that are filed with the Commission, and all written communications relating to the proposed rule change between the Commission and any person, other than those that may be withheld from the public in accordance with the provisions of 5 U.S.C. 552, will be available for website viewing and printing in the Commission's Public Reference Room, 100 F Street NE, Washington, DC 20549, on official business days between the hours of 10 a.m. and 3 p.m. Copies of such filings will also be available for inspection and copying at the principal office of LCH SA and on LCH SA's website at 
                    <E T="03">https://www.lch.com/resources/rulebooks/proposed-rule-changes.</E>
                </FP>
                <P>Do not include personal identifiable information in submissions; you should submit only information that you wish to make available publicly. We may redact in part or withhold entirely from publication submitted material that is obscene or subject to copyright protection. All submissions should refer to File Number SR-LCH SA-2023-007 and should be submitted on or before February 1, 2024.</P>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>54</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>54</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Christina Z. Milnor,</NAME>
                    <TITLE>Assistant Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-00383 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="1964"/>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Investment Company Act Release No. IC-35086; 812-15522]</DEPDOC>
                <SUBJECT>Octagon XAI CLO Income Fund and XA Investments LLC</SUBJECT>
                <DATE>January 8, 2024.</DATE>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Securities and Exchange Commission (“Commission” or “SEC”).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <P>Notice of an application under section 6(c) of the Investment Company Act of 1940 (the “Act”) for an exemption from sections 18(a)(2), 18(c) and 18(i) of the Act, under sections 6(c) and 23(c) of the Act for an exemption from rule 23c-3 under the Act, and for an order pursuant to section 17(d) of the Act and rule 17d-1 under the Act.</P>
                <PREAMHD>
                    <HD SOURCE="HED">Summary of Application:</HD>
                    <P>Applicants request an order to permit certain registered closed-end investment companies to issue multiple classes of shares and to impose asset-based distribution and/or service fees and early withdrawal charges.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">Applicants:</HD>
                    <P>Octagon XAI CLO Income Fund and XA Investments LLC</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">Filing Date:</HD>
                    <P>The application was filed on November 17, 2023.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">Hearing or Notification of Hearing:</HD>
                    <P>
                        An order granting the requested relief will be issued unless the Commission orders a hearing. Interested persons may request a hearing on any application by emailing the SEC's Secretary at 
                        <E T="03">Secretarys-Office@sec.gov</E>
                         and serving the Applicants with a copy of the request by email, if an email address is listed for the relevant Applicant below, or personally or by mail, if a physical address is listed for the relevant Applicant below. Hearing requests should be received by the Commission by 5:30 p.m. on February 2, 2024, and should be accompanied by proof of service on the Applicants, in the form of an affidavit, or, for lawyers, a certificate of service. Pursuant to rule 0-5 under the Act, hearing requests should state the nature of the writer's interest, any facts bearing upon the desirability of a hearing on the matter, the reason for the request, and the issues contested. Persons who wish to be notified of a hearing may request notification by emailing the Commission's Secretary.
                    </P>
                </PREAMHD>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The Commission: 
                        <E T="03">Secretarys-Office@sec.gov</E>
                        . Applicants: Kevin T. Hardy, Esq., Skadden, Arps, Slate, Meagher &amp; Flom LLP, 155 North Wacker Drive, Chicago, Illinois 60606; with a copy to Benjamin McCulloch, Esq., XA Investments LLC, 
                        <E T="03">bmcculloch@xainvestments.com</E>
                        .
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Trace W. Rakestraw, Senior Special 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' application, dated November 17, 2023, 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/legacy/companysearch.html</E>
                    . You may also call the SEC's Public Reference Room 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. 2024-00472 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[SEC File No. 270-399, OMB Control No. 3235-0456]</DEPDOC>
                <SUBJECT>Proposed Collection; Comment Request; Extension: Form 24F-2</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-3520), the Securities and Exchange Commission (the “Commission”) is soliciting comments on the collection of information summarized below. The Commission plans to submit this existing collection of information to the Office of Management and Budget for extension and approval.</P>
                <P>Rule 24f-2 (17 CFR 270.24f-2) under the Investment Company Act of 1940 (15 U.S.C. 80a) requires any open-end investment companies, unit investment trusts (“UITs”), registered closed-end investment companies that make periodic repurchase offers under rule 23c-3 under the Investment Company Act [17 CFR 270.23c-3] (“interval funds”), and face-amount certificate companies (collectively, “funds”) deemed to have registered an indefinite amount of securities to file, not later than 90 days after the end of any fiscal year in which it has publicly offered such securities, Form 24F-2 (17 CFR 274.24) with the Commission. Form 24F-2 is the annual notice of securities sold by funds that accompanies the payment of registration fees with respect to the securities sold during the fiscal year.</P>
                <P>The Commission estimates that 5,116 funds file Form 24F-2 on the required annual basis. The average annual burden per respondent for Form 24F-2 is estimated to be four hours. The total annual burden for all respondents to Form 24F-2 is estimated to be 20,464 hours. The estimate of average burden hours is made solely for the purposes of the Paperwork Reduction Act and is not derived from a comprehensive or even a representative survey or study of the costs of Commission rules.</P>
                <P>Compliance with the collection of information required by Form 24F-2 is mandatory. The Form 24F-2 filing that must be made to the Commission is available to the public. 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 control number.</P>
                <P>Written comments are invited on: (a) whether the proposed collection of information is necessary for the proper performance of the functions of the Commission, including whether the information shall have practical utility; (b) the accuracy of the Commission's estimate of the burden of the collection of information; (c) ways to enhance the quality, utility, and clarity of the information collected; and (d) ways to minimize the burden of the collection of information on respondents, including through the use of automated collection techniques or other forms of information technology. Consideration will be given to comments and suggestions submitted by March 11, 2024.</P>
                <P>An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information under the PRA unless it displays a currently valid OMB control number.</P>
                <P>
                    Please direct your written comments to: David Bottom, Director/Chief Information Officer, Securities and Exchange Commission, c/o John Pezzullo, 100 F Street NE, Washington, DC 20549 or send an email to: 
                    <E T="03">PRA_Mailbox@sec.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: January 8, 2024.</DATED>
                    <NAME>Sherry R. Haywood,</NAME>
                    <TITLE>Assistant Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-00402 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="1965"/>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release No. 34-99281; File No. SR-NYSE-2023-51]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; New York Stock Exchange LLC; Notice of Filing and Immediate Effectiveness of Proposed Rule Change To Amend Its Price List</SUBJECT>
                <DATE>January 5, 2024.</DATE>
                <P>
                    Pursuant to Section 19(b)(1) 
                    <SU>1</SU>
                    <FTREF/>
                     of the Securities Exchange Act of 1934 (“Act”) 
                    <SU>2</SU>
                    <FTREF/>
                     and Rule 19b 4 thereunder,
                    <SU>3</SU>
                    <FTREF/>
                     notice is hereby given that on December 29, 2023, New York Stock Exchange LLC (“NYSE” or the “Exchange”) filed with the Securities and Exchange Commission (the “Commission”) the proposed rule change as described in Items I, II, and III below, which Items have been prepared by the self-regulatory organization. The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         15 U.S.C. 78a.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         17 CFR 240.19b 4.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>
                <P>
                    The Exchange proposes to amend its Price List (the “Price List”) with respect to the system processing fee for use of the Central Registration Depository (“CRD” or “CRD system”) collected by the Financial Industry Regulatory Authority, Inc. (“FINRA”). The Exchange proposes to implement the fee change on January 2, 2024. The proposed rule change is available on the Exchange's website at 
                    <E T="03">www.nyse.com,</E>
                     at the principal office of the Exchange, and at the Commission's Public Reference Room.
                </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <P>In its filing with the Commission, the self-regulatory organization included statements concerning the purpose of, and basis for, the proposed rule change and discussed any comments it received on the proposed rule change. The text of those statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in sections A, B, and C below, of the most significant parts of such statements.</P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and the Statutory Basis for, the Proposed Rule Change</HD>
                <HD SOURCE="HD3">1.  Purpose </HD>
                <P>
                    The Exchange proposes to amend the Price List with respect to the system processing fee for use of CRD collected by FINRA.
                    <SU>4</SU>
                    <FTREF/>
                     The Exchange proposes to implement the fee change effective January 2, 2024.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         CRD is the central licensing and registration system for the U.S. securities industry. The CRD system enables individuals and firms seeking registration with multiple states and self-regulatory organizations to do so by submitting a single form, fingerprint card, and a combined payment of fees to FINRA. Through the CRD system, FINRA maintains the qualification, employment, and disciplinary histories of registered associated persons of broker-dealers.
                    </P>
                </FTNT>
                <P>
                    FINRA collects and retains certain regulatory fees via CRD for the registration of associated persons of Exchange member organizations that are not FINRA members (“Non-FINRA Member Organizations”).
                    <SU>5</SU>
                    <FTREF/>
                     CRD fees are user-based, and there is no distinction in the cost incurred by FINRA if the user is a FINRA member or a Non-FINRA Member Organization.
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         The Exchange originally adopted fees for use of the CRD system in 2001 and amended those fees in 2013, 2022 and 2023. 
                        <E T="03">See</E>
                         Securities Exchange Act Release Nos. 45112 (November 28, 2001), 66 FR 63086 (December 4, 2001) (SR-NYSE-2001-47); 68587 (January 4, 2013), 78 FR 2467 (January 11, 2013) (SR-NYSE-2012-77); 93904 (January 5, 2022), 87 FR 1463 (January 11, 2022) (SR-NYSE-2021-77); and 96636 (January 11, 2023), 88 FR 2985 (January 18, 2023) (NYSE-2023-02). While the Exchange lists these fees in its Price List, it does not collect or retain these fees.
                    </P>
                </FTNT>
                <P>
                    In 2020, FINRA amended certain fees assessed for use of the CRD system for implementation between 2022 and 2024.
                    <SU>6</SU>
                    <FTREF/>
                     The Exchange accordingly proposes to amend the Price List to mirror the system processing fee assessed by FINRA, which will be implemented concurrently with the amended FINRA fee as of January 2024.
                    <SU>7</SU>
                    <FTREF/>
                     Specifically, the Exchange proposes to amend the Price List to modify the system processing fee charged to Non-FINRA Member Organizations for each registered representative and principal from $45 to $70.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 90176 (October 14, 2020), 85 FR 66592 (October 20, 2020) (SR-FINRA-2020-032).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         The Exchange notes that it has only adopted the CRD system fees charged by FINRA to Non-FINRA Member Organizations when such fees are applicable. In this regard, certain FINRA CRD system fees and requirements are specific to FINRA members, but do not apply to NYSE-only member organizations. Non-FINRA Member Organizations have been charged CRD system fees since 2001. 
                        <E T="03">See</E>
                         note 5, 
                        <E T="03">supra.</E>
                         Member organizations that are also FINRA members are charged CRD system fees according to Section 4 of Schedule A to the FINRA By-Laws.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         Section (4)(b)(7) of Schedule A to the FINRA By-laws.
                    </P>
                </FTNT>
                <P>The Exchange notes that the proposed change is not otherwise intended to address any other issues surrounding regulatory fees, and the Exchange is not aware of any problems that member organizations 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>9</SU>
                    <FTREF/>
                     in general, and furthers the objectives of Section 6(b)(4) 
                    <SU>10</SU>
                    <FTREF/>
                     of the Act, in particular, in that it is designed to provide for the equitable allocation of reasonable dues, fees, and other charges. The Exchange also believes that the proposed rule change is consistent with Section 6(b)(5) of the Act,
                    <SU>11</SU>
                    <FTREF/>
                     in that it is designed 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 is not designed to permit unfair discrimination between customers, issuers, brokers, or dealers.
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         15 U.S.C. 78f(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         15 U.S.C. 78f(b)(4).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <P>
                    The Exchange believes that the proposed fee change is reasonable because the fee will be identical to that adopted by FINRA as of January 2024 for use of the CRD system for each of the member's registered representatives and principals for system processing. The costs of operating and improving the CRD system are similarly borne by FINRA when a Non-FINRA Member Organization uses the CRD system; accordingly, the fees collected for such use should, as proposed by the Exchange, mirror the fees assessed to FINRA members. In addition, as FINRA noted in amending its fees, it believes that its proposed pricing structure is reasonable and correlates fees with the components that drive its regulatory costs to the extent feasible. The Exchange further believes that the change is reasonable because it will provide greater specificity regarding the CRD system fees that are applicable to Non-FINRA Member Organizations. All similarly situated member organizations are subject to the same fee structure, and every member organization must use the 
                    <PRTPAGE P="1966"/>
                    CRD system for registration and disclosure. Accordingly, the Exchange believes that the fees collected for such use should likewise increase in lockstep with the fees assessed to FINRA members, as proposed by the Exchange.
                </P>
                <P>The Exchange further believes that the proposed fee change provides for the equitable allocation of reasonable fees and other charges, and does not unfairly discriminate between customers, issuers, brokers, and dealers. The fee applies equally to all individuals and firms required to report information the CRD system, and the proposed change will result in the same regulatory fees being charged to all member organizations required to report information to CRD and for services performed by FINRA regardless of whether such member organizations are FINRA members. Accordingly, the Exchange believes that the fee collected for such use should increase in lockstep with the fee adopted by FINRA as of January 2024, as proposed by the Exchange.</P>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition</HD>
                <P>
                    In accordance with Section 6(b)(8) of the Act,
                    <SU>12</SU>
                    <FTREF/>
                     the Exchange believes that the proposed rule change would not impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. Specifically, the Exchange believes that the proposed change will reflect a fee that will be assessed by FINRA as of January 2024 and will thus result in the same regulatory fee being charged to all member organizations required to report information to the CRD system and for services performed by FINRA, regardless of whether or not such member organizations are FINRA members.
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">See</E>
                         15 U.S.C. 78f(b)(8).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants, or Others</HD>
                <P>No written comments were solicited or received with respect to the proposed rule change.</P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
                <P>
                    The foregoing rule change has become effective upon filing pursuant to Section 19(b)(3)(A) 
                    <SU>13</SU>
                    <FTREF/>
                     of the Act and paragraph (f) thereunder. At any time within 60 days of the filing of the proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act.
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         15 U.S.C. 78s(b)(3)(A).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
                <P>Interested persons are invited to submit written data, views and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:</P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's internet comment form (
                    <E T="03">https://www.sec.gov/rules/sro.shtml</E>
                    ); or
                </P>
                <P>
                    • Send an email to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include file number SR-NYSE-2023-51 on the subject line.
                </P>
                <HD SOURCE="HD2">Paper Comments</HD>
                <P>• Send paper comments in triplicate to Secretary, Securities and Exchange Commission, 100 F Street NE, Washington, DC 20549-1090.</P>
                <FP>
                    All submissions should refer to file number SR-NYSE-2023-51. This file number should be included on the subject line if email is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's internet website (
                    <E T="03">https://www.sec.gov/rules/sro.shtml</E>
                    ). Copies of the submission, all subsequent amendments, all written statements with respect to the proposed rule change that are filed with the Commission, and all written communications relating to the proposed rule change between the Commission and any person, other than those that may be withheld from the public in accordance with the provisions of 5 U.S.C. 552, will be available for website viewing and printing in the Commission's Public Reference Room, 100 F Street NE, Washington, DC 20549, on official business days between the hours of 10 a.m. and 3 p.m. Copies of the filing also will be available for inspection and copying at the principal office of the Exchange. Do not include personal identifiable information in submissions; you should submit only information that you wish to make available publicly. We may redact in part or withhold entirely from publication submitted material that is obscene or subject to copyright protection. All submissions should refer to file number SR-NYSE-2023-51 and should be submitted on or before February 1, 2024.
                    <FTREF/>
                </FP>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         17 CFR 200.30-3(a)(12).
                    </P>
                </FTNT>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>14</SU>
                    </P>
                    <NAME>Christina Z. Milnor,</NAME>
                    <TITLE>Assistant Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-00386 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release No. 34-99280; File No. SR-CboeEDGX-2024-002]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; Cboe EDGX Exchange, Inc.; Notice of Filing and Immediate Effectiveness of a Proposed Rule Change To Amend Its Fee Schedule</SUBJECT>
                <DATE>January 5, 2024.</DATE>
                <P>
                    Pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (“Act”),
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     notice is hereby given that on January 2, 2024, Cboe EDGX Exchange, Inc. (“Exchange” or “EDGX”) filed with the Securities and Exchange Commission (“Commission”) the proposed rule change as described in Items I, II, and III below, which Items have been prepared by the Exchange. The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>
                <P>Cboe EDGX Exchange, Inc. (the “Exchange” or “EDGX”) proposes to amend its Fee Schedule. The text of the proposed rule change is provided in Exhibit 5.</P>
                <P>
                    The text of the proposed rule change is also available on the Exchange's website (
                    <E T="03">http://markets.cboe.com/us/options/regulation/rule_filings/edgx/</E>
                    ), at the Exchange's Office of the Secretary, and at the Commission's Public Reference Room.
                </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <P>
                    In its filing with the Commission, the Exchange included statements concerning the purpose of and basis for the proposed rule change and discussed any comments it received on the proposed rule change. The text of these statements may be examined at the 
                    <PRTPAGE P="1967"/>
                    places specified in Item IV below. The Exchange has prepared summaries, set forth in sections A, B, and C below, of the most significant aspects of such statements.
                </P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <HD SOURCE="HD3">1. Purpose</HD>
                <P>The Exchange proposes to amend its Fee Schedule applicable to its equities trading platform (“EDGX Equities”) as follows: (1) by modifying the standard rate associated with certain fee codes; (2) by discontinuing Remove Volume Tier 1; and (3) by modifying Remove Volume Tier 3. The Exchange proposes to implement these changes effective January 2, 2024.</P>
                <P>
                    The Exchange first notes that it operates in a highly competitive market in which market participants can readily direct order flow to competing venues if they deem fee levels at a particular venue to be excessive or incentives to be insufficient. More specifically, the Exchange is only one of 16 registered equities exchanges, as well as a number of alternative trading systems and other off-exchange venues that do not have similar self-regulatory responsibilities under the Securities Exchange Act of 1934 (the “Act”), to which market participants may direct their order flow. Based on publicly available information,
                    <SU>3</SU>
                    <FTREF/>
                     no single registered equities exchange has more than 13% of the market share. Thus, in such a low-concentrated and highly competitive market, no single equities exchange possesses significant pricing power in the execution of order flow. The Exchange in particular operates a “Maker-Taker” model whereby it pays rebates to members that add liquidity and assesses fees to those that remove liquidity. The Exchange's Fee Schedule sets forth the standard rebates and rates applied per share for orders that provide and remove liquidity, respectively. Currently, for orders in securities priced at or above $1.00, the Exchange provides a standard rebate of $0.00160 per share for orders that add liquidity and assesses a fee of $0.0030 per share for orders that remove liquidity.
                    <SU>4</SU>
                    <FTREF/>
                     For orders in securities priced below $1.00, the Exchange provides a standard rebate of $0.00009 per share for orders that add liquidity and assesses a fee of 0.30% of the total dollar value for orders that remove liquidity.
                    <SU>5</SU>
                    <FTREF/>
                     Additionally, in response to the competitive environment, the Exchange also offers tiered pricing which provides Members opportunities to qualify for higher rebates or reduced fees where certain volume criteria and thresholds are met. Tiered pricing provides an incremental incentive for Members to strive for higher tier levels, which provides increasingly higher benefits or discounts for satisfying increasingly more stringent criteria.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         Cboe Global Markets, U.S. Equities Market Volume Summary, Month-to-Date (December 20, 2023), available at 
                        <E T="03">https://www.cboe.com/us/equities/market_statistics/.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See</E>
                         EDGX Equities Fee Schedule, Standard Rates.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Standard Rates</HD>
                <P>
                    Currently, the Exchange offers standard rates to add liquidity for orders appended with fee codes 3,
                    <SU>6</SU>
                    <FTREF/>
                     4,
                    <SU>7</SU>
                    <FTREF/>
                     B,
                    <SU>8</SU>
                    <FTREF/>
                     V,
                    <SU>9</SU>
                    <FTREF/>
                     and Y.
                    <SU>10</SU>
                    <FTREF/>
                     The Exchange now proposes to revise the standard rebate associated with securities priced below $1.00 from $0.00009 per share to $0.00003 per share for orders appended with fee codes 3, 4, B, V, or Y. The purpose of reducing the standard rebate associated with securities priced below $1.00 is for business and competitive reasons, as the Exchange believes that reducing such rebate as proposed would decrease the Exchange's expenditures with respect to transaction pricing in a manner that is still consistent with the Exchange's overall pricing philosophy of encouraging added liquidity. The Exchange notes that despite the decrease in the standard rebate associated with securities priced below $1.00, the standard rebate remains competitive and continues to be more favorable for Members than the standard rate provided by competing exchanges.
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         Fee code 3 is appended to orders adding liquidity to EDGX in the pre and post market in Tapes A or C securities.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         Fee code 4 is appended to orders adding liquidity to EDGX in the pre and post market in Tape B securities.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         Fee code B is appended to orders adding liquidity to EDGX in Tape B securities.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         Fee code V is appended to orders adding liquidity to EDGX in Tape A securities.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         Fee code Y is appended to orders adding liquidity to EDGX in Tape C securities.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See, e.g.,</E>
                         NYSE Arca Fee Equities Fees and Charges; Standard Rates, available at 
                        <E T="03">https://www.nyse.com/publicdocs/nyse/markets/nyse-arca/NYSE_Arca_Marketplace_Fees.pdf; see also</E>
                         Nasdaq Price List; Add and Remove Rates; Rebates and Fees, Shares Executed Below $1.00, available at 
                        <E T="03">https://www.nasdaqtrader.com/Trader.aspx?id=PriceListTrading2.</E>
                         NYSE Arca provides a rebate to add liquidity equal to 0.0% of Dollar Value for securities priced below $1.00 and Nasdaq provides rebates of $0.00 to add liquidity in securities priced below $1.00.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Remove Volume Tiers</HD>
                <P>
                    Under footnote 1 of the Fee Schedule, the Exchange currently offers various Add/Remove Volume Tiers. In particular, the Exchange offers three Remove Volume Tiers that each assess a reduced fee for Members' qualifying orders yielding fee codes BB,
                    <SU>12</SU>
                    <FTREF/>
                     N,
                    <SU>13</SU>
                    <FTREF/>
                     and W 
                    <SU>14</SU>
                    <FTREF/>
                     where a Member reaches certain add volume-based criteria. The Exchange now proposes to discontinue Remove Volume Tier 1 as the Exchange no longer wishes to, nor is required to, maintain such tier. More specifically, the proposed change removes this tier as the Exchange would rather redirect future resources and funding into other programs and tiers intended to incentivize increased order flow. In conjunction with discontinuing Remove Volume Tier 1, the Exchange proposes to renumber Remove Volume Tiers 2 and 3 as Remove Volume Tiers 1 and 2, respectively, following the deletion of current Remove Volume Tier 1.
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         Fee code BB is appended to orders that remove liquidity from EDGX in Tape B securities.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         Fee code N is appended to orders that remove liquidity from EDGX in Tape C securities.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         Fee code W is appended to orders that remove liquidity from EDGX in Tape A securities.
                    </P>
                </FTNT>
                <P>In addition to the proposed deletion of Remove Tier 1, the Exchange proposes to amend the criteria of proposed Remove Volume Tier 2 (current Remove Volume Tier 3). Currently, the criteria for proposed Remove Volume Tier 2 is as follows:</P>
                <P>
                    • Proposed Remove Volume Tier 2 (current Remove Volume Tier 3) provides a reduced fee of $0.00275 per share for securities priced at or above $1.00 to qualifying orders (
                    <E T="03">i.e.,</E>
                     orders yielding fee codes BB, N, or W) and a reduced fee of 0.28% of total dollar value for securities priced below $1.00 where: (1) Member has an ADAV 
                    <SU>15</SU>
                    <FTREF/>
                     ≥0.30% of the TCV; 
                    <SU>16</SU>
                    <FTREF/>
                     and (2) Member has a total remove ADV 
                    <SU>17</SU>
                    <FTREF/>
                     ≥0.40% of the TCV; or Member has a total remove ADV ≥40,000,000; and (3) Member adds Retail Pre Market Order ADV (
                    <E T="03">i.e.,</E>
                     yielding fee code ZO) ≥3,000,000.
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         ADAV means average daily added volume calculated as the number of shares added per day, calculated on a monthly basis.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         TCV means total consolidated volume calculated as the volume reported by all exchanges and trade reporting facilities to a consolidated transaction reporting plan for the month for which the fees apply.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         ADV means average daily volume calculated as the number of shares added to, removed from, or routed by, the Exchange, or any combination or subset thereof, per day. ADV is calculated on a monthly basis.
                    </P>
                </FTNT>
                <P>Now, the Exchange proposes to amend the second prong of criteria in proposed Remove Volume Tier 2 by removing the total remove ADV share requirement. The proposed criteria is as follows:</P>
                <P>
                    • Proposed Remove Volume Tier 2 provides a reduced fee of $0.00275 per 
                    <PRTPAGE P="1968"/>
                    share for securities priced at or above $1.00 to qualifying orders (
                    <E T="03">i.e.,</E>
                     orders yielding fee codes BB, N, or W) and a reduced fee of 0.28% of total dollar value for securities priced below $1.00 where: (1) Member has an ADAV ≥0.30% of the TCV; and (2) Member has a total remove ADV ≥040% of the TCV; and (3) Member adds Retail Pre Market Order ADV (
                    <E T="03">i.e.,</E>
                     yielding fee code ZO) ≥3,000,000.
                </P>
                <P>The proposed amendment to proposed Remove Volume Tier 2 is intended to slightly increase the difficulty of achieving an existing opportunity to earn an enhanced rebate by providing a single alternative for Members to increase their order flow to the Exchange. Submitting increased order flow to the Exchange will further contribute to a deeper, more liquid market and provide even more execution opportunities for active market participants. Incentivizing an increase in liquidity adding volume, through enhanced rebate opportunities, encourages liquidity adding Members on the Exchange to contribute to a deeper, more liquid market, and liquidity executing Members on the Exchange to increase transactions and take execution opportunities provided by such increased liquidity, together providing for overall enhanced price discovery and price improvement opportunities on the Exchange. As such, increased overall order flow benefits all Members by contributing towards a robust and well-balanced market ecosystem.</P>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    The Exchange believes the proposed rule change is consistent with the Act and the rules and regulations thereunder applicable to the Exchange and, in particular, the requirements of Section 6(b) of the Act.
                    <SU>18</SU>
                    <FTREF/>
                     Specifically, the Exchange believes the proposed rule change is consistent with the Section 6(b)(5) 
                    <SU>19</SU>
                    <FTREF/>
                     requirements that the rules of an exchange be designed to prevent fraudulent and manipulative acts and practices, to promote just and equitable principles of trade, to foster cooperation and coordination with persons engaged in regulating, clearing, settling, processing information with respect to, and facilitating transactions in securities, to remove impediments to and perfect the mechanism of a free and open market and a national market system, and, in general, to protect investors and the public interest. Additionally, the Exchange believes the proposed rule change is consistent with the Section 6(b)(5) 
                    <SU>20</SU>
                    <FTREF/>
                     requirement that the rules of an exchange not be designed to permit unfair discrimination between customers, issuers, brokers, or dealers as well as Section 6(b)(4) 
                    <SU>21</SU>
                    <FTREF/>
                     as it is designed to provide for the equitable allocation of reasonable dues, fees and other charges among its Members and other persons using its facilities.
                </P>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         15 U.S.C. 78f(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         15 U.S.C. 78f(b)(4).
                    </P>
                </FTNT>
                <P>As described above, the Exchange operates in a highly competitive market in which market participants can readily direct order flow to competing venues if they deem fee levels at a particular venue to be excessive or incentives to be insufficient. The Exchange believes that its proposal to: (1) modify the standard rebates associated with securities priced below $1.00 and (2) modify proposed Retail Volume Tier 2 reflects a competitive pricing structure designed to incentivize market participants to direct their order flow to the Exchange, which the Exchange believes would enhance market quality to the benefit of all Members.</P>
                <P>
                    Specifically, the Exchange's proposed criteria for proposed Remove Volume Tier 2 is not a significant departure from existing criteria, continues to be reasonably correlated to the enhanced rebate offered by the Exchange and other competing exchanges,
                    <SU>22</SU>
                    <FTREF/>
                     and will continue to incentivize Members to submit order flow to the Exchange. Additionally, the Exchange notes that relative volume-based incentives and discounts have been widely adopted by exchanges,
                    <SU>23</SU>
                    <FTREF/>
                     including the Exchange,
                    <SU>24</SU>
                    <FTREF/>
                     and are reasonable, equitable and non-discriminatory because they are open to all Members on an equal basis and provide additional benefits or discounts that are reasonably related to (i) the value to an exchange's market quality and (ii) associated higher levels of market activity, such as higher levels of liquidity provision and/or growth patterns. Competing equity exchanges offer similar tiered pricing structures, including schedules of rebates and fees that apply based upon members achieving certain volume and/or growth thresholds, as well as assess similar fees or rebates for similar types of orders, to that of the Exchange.
                </P>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         
                        <E T="03">See, e.g.,</E>
                         MIAX Pearl Equities Exchange Fee Schedule, Remove Volume Tier, available at 
                        <E T="03">https://www.miaxglobal.com/sites/default/files/fee_schedule-files/MIAX_Pearl_Equities_Fee_Schedule_12012023.pdf;</E>
                         and MEMX Equities Fee Schedule, Liquidity Removal Tier, available at 
                        <E T="03">https://info.memxtrading.com/equities-trading-resources/us-equities-fee-schedule/.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         
                        <E T="03">See, e.g.,</E>
                         BZX Equities Fee Schedule, Footnote 1, Add/Remove Volume Tiers.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         
                        <E T="03">See, e.g.,</E>
                         EDGX Equities Fee Schedule, Footnote 1, Add/Remove Volume Tiers.
                    </P>
                </FTNT>
                <P>In particular, the Exchange believes its proposal to modify proposed Retail Volume Tier 2 is reasonable because the revised tier will be available to all Members and provide all Members with an opportunity to receive an enhanced rebate. The Exchange further believes the proposed modification to proposed Remove Volume Tier 2 will provide a reasonable means to encourage liquidity adding displayed orders in Members' order flow to the Exchange and to incentivize Members to continue to provide liquidity adding volume to the Exchange by offering them an opportunity to receive an enhanced rebate on qualifying orders. While the proposed criteria in proposed Remove Volume Tier 2 is slightly more difficult than the current criteria found in that tier, the proposed criteria is not a significant departure from existing criteria, is reasonably correlated to the enhanced rebate offered by the Exchange, and will continue to incentivize Members to submit order flow to the Exchange. An overall increase in activity would deepen the Exchange's liquidity pool, offers additional cost savings, support the quality of price discovery, promote market transparency and improve market quality, for all investors.</P>
                <P>
                    Further, the Exchange believes that its proposal to modify the standard rebate associated with securities priced below $1.00 is reasonable, equitable, and consistent with the Act because such change is designed to decrease the Exchange's expenditures with respect to transaction pricing in order to offset some of the costs associated with the Exchange's current pricing structure, which provides various rebates for liquidity-adding orders, and the Exchange's operations generally, in a manner that is consistent with the Exchange's overall pricing philosophy of encouraging added liquidity. The proposed decreased standard rebate of $0.00003 per share is reasonable and appropriate because it remains competitive with the standard rebate offered by other exchanges.
                    <SU>25</SU>
                    <FTREF/>
                     The Exchange further believes that the proposed decrease to the standard rebate associated with securities priced below $1.00 is not unfairly discriminatory because it applies to all Members equally, in that all Members will received the lower standard rebate upon submitting orders appended with fee codes B, V, Y, 3, or 4.
                </P>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         
                        <E T="03">Supra</E>
                         note 11.
                    </P>
                </FTNT>
                <P>
                    The Exchange believes that its proposal to eliminate current Remove 
                    <PRTPAGE P="1969"/>
                    Volume Tier 1 is reasonable because the Exchange is not required to maintain this tier nor is it required to provide Members an opportunity to receive enhanced rebates. The Exchange believes its proposal to eliminate this tier is also equitable and not unfairly discriminatory because it applies to all Members (
                    <E T="03">i.e.,</E>
                     the tier will not be available for any Member). The Exchange also notes that the proposed rule change to remove this tier merely results in Members not receiving an enhanced rebate, which, as noted above, the Exchange is not required to offer or maintain. Furthermore, the proposed rule change to eliminate current Remove Volume Tier 1 enables the Exchange to redirect resources and funding into other programs and tiers intended to incentivize increased order flow.
                </P>
                <P>The Exchange believes that the proposed changes to its standard rebate associated with securities priced below $1.00 and Remove Volume Tiers are reasonable as they do not represent a significant departure from the criteria or rebates currently offered in the Fee Schedule. The Exchange also believes that the proposal represents an equitable allocation of fees and rebates and is not unfairly discriminatory because all Members will be eligible for the proposed standard rebate and revised tier and have the opportunity to meet the revised tier's criteria and receive the corresponding enhanced rebate if such criteria is met. Without having a view of activity on other markets and off-exchange venues, the Exchange has no way of knowing whether this proposed rule change would definitely result in any Members qualifying the new proposed tiers. While the Exchange has no way of predicting with certainty how the proposed changes will impact Member activity, based on the prior months volume, the Exchange anticipates that at least one Member will be able to satisfy proposed Remove Volume Tier 2. The Exchange also notes that proposed changes will not adversely impact any Member's ability to qualify for enhanced rebates offered under other tiers. Should a Member not meet the proposed new criteria, the Member will merely not receive that corresponding enhanced rebate.</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. Rather, as discussed above, the Exchange believes that the proposed changes would encourage the submission of additional order flow to a public exchange, thereby promoting market depth, execution incentives and enhanced execution opportunities, as well as price discovery and transparency for all Members. As a result, the Exchange believes that the proposed changes further the Commission's goal in adopting Regulation NMS of fostering competition among orders, which promotes “more efficient pricing of individual stocks for all types of orders, large and small.”</P>
                <P>The Exchange believes the proposed rule changes do not impose any burden on intramarket competition that is not necessary or appropriate in furtherance of the purposes of the Act. Particularly, the proposed changes to the Exchange's standard rebate associated with securities priced below $1.00 and the proposed changes to proposed Remove Volume Tier 2 will apply to all Members equally in that all Members are eligible for the standard rebate and the proposed revised tier, have a reasonable opportunity to meet the proposed tier's criteria and will receive the enhanced rebate on their qualifying orders if such criteria is met. The Exchange does not believe the proposed changes burden competition, but rather, enhances competition as it is intended to increase the competitiveness of EDGX by amending an existing pricing incentive and adopting pricing incentives in order to attract order flow and incentivize participants to increase their participation on the Exchange, providing for additional execution opportunities for market participants and improved price transparency. Greater overall order flow, trading opportunities, and pricing transparency benefits all market participants on the Exchange by enhancing market quality and continuing to encourage Members to send orders, thereby contributing towards a robust and well-balanced market ecosystem.</P>
                <P>The Exchange believes the proposed elimination of Remove Volume Tier 1 does not impose any burden on intramarket competition that is not necessary or appropriate in furtherance of the purposes of the Act. Particularly, the proposed change to eliminate the Remove Volume Tier 1 will not impose any burden on intramarket competition because the changes apply to all Members uniformly, as in, the tier will no longer be available to any Member.</P>
                <P>
                    Next, the Exchange believes the proposed rule changes does not impose any burden on intermarket competition that is not necessary or appropriate in furtherance of the purposes of the Act. As previously discussed, the Exchange operates in a highly competitive market. Members have numerous alternative venues that they may participate on and direct their order flow, including other equities exchanges, off-exchange venues, and alternative trading systems. Additionally, the Exchange represents a small percentage of the overall market. Based on publicly available information, no single equities exchange has more than 13% of the market share.
                    <SU>26</SU>
                    <FTREF/>
                     Therefore, no exchange possesses significant pricing power in the execution of order flow. Indeed, participants can readily choose to send their orders to other exchange and off-exchange venues if they deem fee levels at those other venues to be more favorable. Moreover, 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>27</SU>
                    <FTREF/>
                     The fact that this market is competitive has also long been recognized by the courts. In 
                    <E T="03">NetCoalition</E>
                     v. 
                    <E T="03">Securities and Exchange Commission,</E>
                     the D.C. Circuit stated as follows: “[n]o one disputes that competition for order flow is `fierce.' . . . As the SEC explained, `[i]n the U.S. national market system, buyers and sellers of securities, and the broker-dealers that act as their order-routing agents, have a wide range of choices of where to route orders for execution'; [and] `no exchange can afford to take its market share percentages for granted' because `no exchange possesses a monopoly, regulatory or otherwise, in the execution of order flow from broker dealers'. . . .”.
                    <SU>28</SU>
                    <FTREF/>
                     Accordingly, the Exchange does not believe its proposed fee change imposes any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act.
                </P>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         
                        <E T="03">Supra</E>
                         note 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 51808 (June 9, 2005), 70 FR 37496, 37499 (June 29, 2005).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         
                        <E T="03">NetCoalition</E>
                         v. 
                        <E T="03">SEC,</E>
                         615 F.3d 525, 539 (D.C. Cir. 2010) (quoting Securities Exchange Act Release No. 59039 (December 2, 2008), 73 FR 74770, 74782-83 (December 9, 2008) (SR-NYSEArca-2006-21)).
                    </P>
                </FTNT>
                <PRTPAGE P="1970"/>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants, or Others</HD>
                <P>The Exchange neither solicited nor received comments on the proposed rule change.</P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
                <P>
                    The foregoing rule change has become effective pursuant to Section 19(b)(3)(A) of the Act 
                    <SU>29</SU>
                    <FTREF/>
                     and paragraph (f) of Rule 19b-4 
                    <SU>30</SU>
                    <FTREF/>
                     thereunder. At any time within 60 days of the filing of the proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act. If the Commission takes such action, the Commission will institute proceedings to determine whether the proposed rule change should be approved or disapproved.
                </P>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         15 U.S.C. 78s(b)(3)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         17 CFR 240.19b-4(f).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
                <P>Interested persons are invited to submit written data, views and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:</P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's internet comment form (
                    <E T="03">https://www.sec.gov/rules/sro.shtml</E>
                    ); or
                </P>
                <P>
                    • Send an email to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include file number SR-CboeEDGX-2024-002 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-CboeEDGX-2024-002. This file number should be included on the subject line if email is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's internet website (
                    <E T="03">https://www.sec.gov/rules/sro.shtml</E>
                    ). Copies of the submission, all subsequent amendments, all written statements with respect to the proposed rule change that are filed with the Commission, and all written communications relating to the proposed rule change between the Commission and any person, other than those that may be withheld from the public in accordance with the provisions of 5 U.S.C. 552, will be available for website viewing and printing in the Commission's Public Reference Room, 100 F Street NE, Washington, DC 20549, on official business days between the hours of 10 a.m. and 3 p.m. Copies of the filing also will be available for inspection and copying at the principal office of the Exchange. Do not include personal identifiable information in submissions; you should submit only information that you wish to make available publicly. We may redact in part or withhold entirely from publication submitted material that is obscene or subject to copyright protection. All submissions should refer to file number SR-CboeEDGX-2024-002 and should be submitted on or before February 1, 2024.
                </FP>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>31</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>31</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Christina Z. Milnor,</NAME>
                    <TITLE>Assistant Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-00385 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release Nos. 33-11263; 34-99276; IA-6521; IC-35085]</DEPDOC>
                <SUBJECT>Adjustments to Civil Monetary Penalty Amounts</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Securities and Exchange Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of annual inflation adjustment of civil monetary penalties.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Securities and Exchange Commission (“Commission”) is publishing this notice (“Notice”) pursuant to the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015 (“2015 Act”). This Act requires all agencies to annually adjust for inflation the civil monetary penalties that can be imposed under the statutes administered by the agency and publish the adjusted amounts in the 
                        <E T="04">Federal Register</E>
                        . This Notice sets forth the annual inflation adjustment of the maximum amount of civil monetary penalties (“CMPs”) administered by the Commission under the Securities Act of 1933, the Securities Exchange Act of 1934 (“Exchange Act”), the Investment Company Act of 1940, the Investment Advisers Act of 1940, and certain penalties under the Sarbanes-Oxley Act of 2002. These amounts are effective beginning on January 15, 2024, and will apply to all penalties imposed after that date for violations of the aforementioned statutes that occurred after November 2, 2015.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Stephen M. Ng, Senior Special Counsel, Office of the General Counsel, at (202) 551-7957, or Hannah W. Riedel, Senior Counsel, Office of the General Counsel, at (202) 551-7918.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    This Notice is being published pursuant to the 2015 Act,
                    <SU>1</SU>
                    <FTREF/>
                     which amended the Federal Civil Penalties Inflation Adjustment Act of 1990 (“Inflation Adjustment Act”).
                    <SU>2</SU>
                    <FTREF/>
                     The Inflation Adjustment Act previously had been amended by the Debt Collection Improvement Act of 1996 (“DCIA”) 
                    <SU>3</SU>
                    <FTREF/>
                     to require that each Federal agency adopt regulations at least once every four years that adjust for inflation the CMPs that can be imposed under the statutes administered by the agency. Pursuant to this requirement, the Commission previously adopted regulations in 1996, 2001, 2005, 2009, and 2013 to adjust the maximum amount of the CMPs that could be imposed under the statutes the Commission administers.
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Public Law 114-74 Sec. 701, 129 Stat. 599-601 (Nov. 2, 2015), codified at 28 U.S.C. 2461 note.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Public Law 101-410, 104 Stat. 890-892 (1990), codified at 28 U.S.C. 2461 note.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         Public Law. 104-134, title III, section 31001(s)(1), 110 Stat. 1321-373 (1996), codified at 28 U.S.C. 2461 note.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See</E>
                         Release Nos. 33-7361, 34-37912, IA-1596, IC-22310, dated Nov. 1, 1996 (effective Dec. 9, 1996), previously found at 17 CFR 201.1001 and Table I to Subpart E of Part 201; Release Nos. 33-7946, 34-43897, IA-1921, IC-24846, dated Jan. 31, 2001 (effective Feb. 2, 2001), previously found at 17 CFR 201.1002 and Table II to Subpart E of Part 201; Release Nos. 33-8530, 34-51136, IA-2348, IC-26748, dated Feb. 9, 2005 (effective Feb. 14, 2005), previously found at 17 CFR 201.1003 and Table III to Subpart E of Part 201; Release Nos. 33-9009, 34-59449, IA-2845, IC-28635, dated Feb. 25, 2009 (effective Mar. 3, 2009), previously found at 17 CFR 201.1004 and Table IV to Subpart E of Part 201; and Release Nos. 33-9387, 34-68994, IA-3557, IC-30408, dated Feb. 27, 2013 (effective Mar. 5, 2013), previously found at 17 CFR 201.1005 and Table V to Subpart E of Part 201. The penalty amounts contained in these releases have now been consolidated into Table I to 17 CFR 201.1001.
                    </P>
                </FTNT>
                <P>
                    The 2015 Act replaces the inflation adjustment formula prescribed in the DCIA with a new formula for calculating the inflation-adjusted amount of CMPs. The 2015 Act requires that agencies use this new formula to re-calculate the inflation-adjusted amounts of the penalties they administer on an annual basis and publish these new amounts in 
                    <PRTPAGE P="1971"/>
                    the 
                    <E T="04">Federal Register</E>
                     by January 15 of each year.
                    <SU>5</SU>
                    <FTREF/>
                     The Commission previously published the first annual adjustment required by the 2015 Act on January 6, 2017 (“2017 Adjustment”).
                    <SU>6</SU>
                    <FTREF/>
                     As part of the 2017 Adjustment, the Commission promulgated 17 CFR 201.1001(a) and Table I to § 201.1001, which lists the penalty amounts for all violations that occurred on or before November 2, 2015. For violations occurring after November 2, 2015, § 201.1001(b) provides that the applicable penalty amounts will be adjusted annually based on the formula set forth in the 2015 Act. Section 201.1001(b) further provides that these adjusted amounts will be published in the 
                    <E T="04">Federal Register</E>
                     and on the Commission's website. The Commission published the two most recent annual adjustments on January 6, 2022 (“2022 Adjustment”),
                    <SU>7</SU>
                    <FTREF/>
                     and January 6, 2023 (“2023 Adjustment”).
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         28 U.S.C. 2461 note Sec. 4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         Release Nos. 33-10276; 34-79749; IA-4599; IC-32414 (effective Jan. 18, 2017).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         Release Nos. 33-11021; 34-93925; IA-5938; IC-34466 (effective Jan. 15, 2022).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         Release Nos. 33-11143; 34-96605; IA-6212; IC-34797) (effective Jan. 15, 2023).
                    </P>
                </FTNT>
                <P>
                    A CMP is defined in relevant part as any penalty, fine, or other sanction that: (1) is for a specific amount, or has a maximum amount, as provided by Federal law; and (2) is assessed or enforced by an agency in an administrative proceeding or by a Federal court pursuant to Federal law.
                    <SU>9</SU>
                    <FTREF/>
                     This definition applies to the monetary penalty provisions contained in four statutes administered by the Commission: the Securities Act, the Exchange Act, the Investment Company Act, and the Investment Advisers Act. In addition, the Sarbanes-Oxley Act provides the Public Company Accounting Oversight Board (“PCAOB”) authority to levy civil monetary penalties in its disciplinary proceedings pursuant to 15 U.S.C. 7215(c)(4)(D).
                    <SU>10</SU>
                    <FTREF/>
                     The definition of a CMP in the Inflation Adjustment Act encompasses such civil monetary penalties.
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         28 U.S.C. 2461 note Sec. 3(2).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         15 U.S.C. 7215(c)(4)(D).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         The Commission may by order affirm, modify, remand, or set aside sanctions, including civil monetary penalties, imposed by the PCAOB. 
                        <E T="03">See</E>
                         section 107(c) of the Sarbanes-Oxley Act of 2002, 15 U.S.C. 7217. The Commission may enforce such orders in Federal district court pursuant to section 21(e) of the Exchange Act. As a result, penalties assessed by the PCAOB in its disciplinary proceedings are penalties “enforced” by the Commission for purposes of the Inflation Adjustment Act. 
                        <E T="03">See Adjustments to Civil Monetary Penalty Amounts,</E>
                         Release No. 33-8530 (Feb. 4, 2005) [70 FR 7606 (Feb. 14, 2005)].
                    </P>
                </FTNT>
                <HD SOURCE="HD1">II. Adjusting the Commission's Penalty Amounts for Inflation</HD>
                <P>This Notice sets forth the annual inflation adjustment required by the 2015 Act for all CMPs under the Securities Act, the Exchange Act, the Investment Company Act, and the Investment Advisers Act, and certain civil monetary penalties under the Sarbanes-Oxley Act.</P>
                <P>
                    Pursuant to the 2015 Act, the penalty amounts in the 2024 Adjustment are adjusted for inflation by increasing them by the percentage change between the Consumer Price Index for all Urban Consumers (“CPI-U”) for October 2022 and the October 2023 CPI-U.
                    <SU>12</SU>
                    <FTREF/>
                     OMB has provided its calculation of this multiplier (“CPI-U Multiplier”) to agencies.
                    <SU>13</SU>
                    <FTREF/>
                     The new penalty amounts are determined by multiplying the amounts in the 2024 Adjustment by the CPI-U Multiplier and then rounding to the nearest dollar.
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         28 U.S.C. 2461 note Sec. 5.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         Office of Management and Budget, 
                        <E T="03">Implementation of Penalty Inflation Adjustments for 2024, Pursuant to the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015</E>
                         (Dec. 19, 2023), available at 
                        <E T="03">https://www.whitehouse.gov/wp-content/uploads/2023/12/M-24-07-Implementation-of-Penalty-Inflation-Adjustments-for-2024.pdf.</E>
                         This multiplier represents the percentage increase between the Oct. 2022 CPI-U and the Oct. 2023 CPI-U, plus 1.
                    </P>
                </FTNT>
                <P>
                    For example, the CMP for certain insider trading violations by controlling persons under Exchange Act section 21A(a)(3) 
                    <SU>14</SU>
                    <FTREF/>
                     was readjusted for inflation as part of the 2023 Adjustment to $2,479,282. To determine the new CMP under this provision, the Commission multiplies this amount by the CPI-U Multiplier of 1.03241, and rounds to the nearest dollar. Thus, the new CMP for Exchange Act section 21A(a)(3) is $2,559,636.
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         15 U.S.C. 78u-1(a)(3).
                    </P>
                </FTNT>
                <P>Below is the Commission's calculation of the new penalty amounts for the penalties it administers:</P>
                <GPOTABLE COLS="5" OPTS="L2,tp0,p7,7/8,i1" CDEF="s50,r50,10,10,10">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">U.S. Code citation</CHED>
                        <CHED H="1">Civil monetary penalty description</CHED>
                        <CHED H="1">
                            2023
                            <LI>Adjustment</LI>
                            <LI>penalty amounts</LI>
                        </CHED>
                        <CHED H="1">
                            CPI-U
                            <LI>Multiplier</LI>
                        </CHED>
                        <CHED H="1">
                            2024
                            <LI>Adjusted</LI>
                            <LI>penalty</LI>
                            <LI>amounts</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">15 U.S.C. 77h-1(g) (Securities Act Sec. 8A(g))</ENT>
                        <ENT>
                            For natural person
                            <LI>For any other person</LI>
                        </ENT>
                        <ENT>
                            $10,219
                            <LI>102,193</LI>
                        </ENT>
                        <ENT>
                            1.03241
                            <LI>1.03241</LI>
                        </ENT>
                        <ENT>
                            $10,550
                            <LI>105,505</LI>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>For natural person/fraud</ENT>
                        <ENT>102,193</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>105,505</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>For any other person/fraud</ENT>
                        <ENT>510,962</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>527,522</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>For natural person/fraud/substantial losses or risk of losses to others or gains to self</ENT>
                        <ENT>204,385</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>211,009</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>For any other person/fraud/substantial losses or risk of losses to others or gain to self</ENT>
                        <ENT>987,860</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>1,019,877</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">15 U.S.C. 77t(d) (Securities Act Sec. 20(d))</ENT>
                        <ENT>For natural person</ENT>
                        <ENT>11,162</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>11,524</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>For any other person</ENT>
                        <ENT>111,614</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>115,231</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>For natural person/fraud</ENT>
                        <ENT>111,614</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>115,231</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>For any other person/fraud</ENT>
                        <ENT>558,071</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>576,158</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>
                            For natural person/fraud/substantial losses or risk of losses to others
                            <LI>For any other person/fraud/substantial losses or risk of losses to others</LI>
                        </ENT>
                        <ENT>
                            223,229
                            <LI>1,116,140</LI>
                        </ENT>
                        <ENT>
                            1.03241
                            <LI>1.03241</LI>
                        </ENT>
                        <ENT>
                            230,464
                            <LI>1,152,314</LI>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">15 U.S.C. 78u(d)(3) (Exchange Act Sec. 21(d)(3))</ENT>
                        <ENT>
                            For natural person
                            <LI>For any other person</LI>
                        </ENT>
                        <ENT>
                            11,162
                            <LI>111,614</LI>
                        </ENT>
                        <ENT>
                            1.03241
                            <LI>1.03241</LI>
                        </ENT>
                        <ENT>
                            11,524
                            <LI>115,231</LI>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>For natural person/fraud</ENT>
                        <ENT>111,614</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>115,231</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>For any other person/fraud</ENT>
                        <ENT>558,071</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>576,158</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>For natural person/fraud/substantial losses or risk of losses to others or gains to self</ENT>
                        <ENT>223,229</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>230,464</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>For any other person/fraud/substantial losses or risk of losses to others or gain to self</ENT>
                        <ENT>1,116,140</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>1,152,314</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">15 U.S.C. 78u-1(a)(3) (Exchange Act Sec. 21A(a)(3))</ENT>
                        <ENT>Insider Trading—controlling person</ENT>
                        <ENT>2,479,282</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>2,559,636</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">15 U.S.C. 78u-2 (Exchange Act Sec. 21B)</ENT>
                        <ENT>
                            For natural person
                            <LI>For any other person</LI>
                        </ENT>
                        <ENT>
                            11,162
                            <LI>111,614</LI>
                        </ENT>
                        <ENT>
                            1.03241
                            <LI>1.03241</LI>
                        </ENT>
                        <ENT>
                            11,524
                            <LI>115,231</LI>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>For natural person/fraud</ENT>
                        <ENT>111,614</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>115,231</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>For any other person/fraud</ENT>
                        <ENT>558,071</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>576,158</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="1972"/>
                        <ENT I="22"> </ENT>
                        <ENT>For natural person/fraud/substantial losses or risk of losses to others</ENT>
                        <ENT>223,229</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>230,464</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>For any other person/fraud/substantial losses or risk of losses to others</ENT>
                        <ENT>1,116,140</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>1,152,314</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">15 U.S.C. 78ff(b) (Exchange Act Sec. 32(b))</ENT>
                        <ENT>Exchange Act/failure to file information documents, reports</ENT>
                        <ENT>659</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>680</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">15 U.S.C. 78ff(c)(1)(B) (Exchange Act Sec. 32(c)(1)(B))</ENT>
                        <ENT>Foreign Corrupt Practices—any issuer</ENT>
                        <ENT>24,793</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>25,597</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">15 U.S.C. 78ff(c)(2)(B) (Exchange Act Sec. 32(c)(2)(B))</ENT>
                        <ENT>Foreign Corrupt Practices—any agent or stockholder acting on behalf of issuer</ENT>
                        <ENT>24,793</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>25,597</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">15 U.S.C. 80a-9(d) (Investment Company Act Sec. 9(d))</ENT>
                        <ENT>
                            For natural person
                            <LI>For any other person</LI>
                        </ENT>
                        <ENT>
                            11,162
                            <LI>111,614</LI>
                        </ENT>
                        <ENT>
                            1.03241
                            <LI>1.03241</LI>
                        </ENT>
                        <ENT>
                            11,524
                            <LI>115,231</LI>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>For natural person/fraud</ENT>
                        <ENT>111,614</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>115,231</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>For any other person/fraud</ENT>
                        <ENT>558,071</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>576,158</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>For natural person/fraud/substantial losses or risk of losses to others or gains to self</ENT>
                        <ENT>223,229</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>230,464</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>For any other person/fraud/substantial losses or risk of losses to others or gain to self</ENT>
                        <ENT>1,116,140</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>1,152,314</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">15 U.S.C. 80a-41(e) (Investment Company Act Sec. 42(e))</ENT>
                        <ENT>
                            For natural person
                            <LI>For any other person</LI>
                        </ENT>
                        <ENT>
                            11,162
                            <LI>111,614</LI>
                        </ENT>
                        <ENT>
                            1.03241
                            <LI>1.03241</LI>
                        </ENT>
                        <ENT>
                            11,524
                            <LI>115,231</LI>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>For natural person/fraud</ENT>
                        <ENT>111,614</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>115,231</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>For any other person/fraud</ENT>
                        <ENT>558,071</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>576,158</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>For natural person/fraud/substantial losses or risk of losses to others</ENT>
                        <ENT>223,229</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>230,464</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>For any other person/fraud/substantial losses or risk of losses to others</ENT>
                        <ENT>1,116,140</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>1,152,314</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">15 U.S.C. 80b-3(i) (Investment Advisers Act Sec. 203(i))</ENT>
                        <ENT>
                            For natural person
                            <LI>For any other person</LI>
                        </ENT>
                        <ENT>
                            11,162
                            <LI>111,614</LI>
                        </ENT>
                        <ENT>
                            1.03241
                            <LI>1.03241</LI>
                        </ENT>
                        <ENT>
                            11,524
                            <LI>115,231</LI>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>For natural person/fraud</ENT>
                        <ENT>111,614</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>115,231</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>For any other person/fraud</ENT>
                        <ENT>558,071</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>576,158</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>For natural person/fraud/substantial losses or risk of losses to others or gains to self</ENT>
                        <ENT>223,229</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>230,464</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>For any other person/fraud/substantial losses or risk of losses to others or gain to self</ENT>
                        <ENT>1,116,140</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>1,152,314</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">15 U.S.C. 80b-9(e) (Investment Advisers Act Sec. 209(e))</ENT>
                        <ENT>
                            For natural person
                            <LI>For any other person</LI>
                        </ENT>
                        <ENT>
                            11,162
                            <LI>111,614</LI>
                        </ENT>
                        <ENT>
                            1.03241
                            <LI>1.03241</LI>
                        </ENT>
                        <ENT>
                            11,524
                            <LI>115,231</LI>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>For natural person/fraud</ENT>
                        <ENT>111,614</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>115,231</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>For any other person/fraud</ENT>
                        <ENT>558,071</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>576,158</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>For natural person/fraud/substantial losses or risk of losses to others</ENT>
                        <ENT>223,229</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>230,464</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>For any other person/fraud/substantial losses or risk of losses to others</ENT>
                        <ENT>1,116,140</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>1,152,314</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">15 U.S.C. 7215(c)(4)(D)(i) (Sarbanes-Oxley Act Sec. 105(c)(4)(D)(i))</ENT>
                        <ENT>
                            For natural person
                            <LI>For any other person</LI>
                        </ENT>
                        <ENT>
                            164,373
                            <LI>3,287,477</LI>
                        </ENT>
                        <ENT>
                            1.03241
                            <LI>1.03241</LI>
                        </ENT>
                        <ENT>
                            169,700
                            <LI>3,394,024</LI>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">15 U.S.C. 7215(c)(4)(D)(ii) (Sarbanes-Oxley Act Sec. 105(c)(4)(D)(ii))</ENT>
                        <ENT>
                            For natural person
                            <LI>For any other person</LI>
                        </ENT>
                        <ENT>
                            1,232,803
                            <LI>24,656,067</LI>
                        </ENT>
                        <ENT>
                            1.03241
                            <LI>1.03241</LI>
                        </ENT>
                        <ENT>
                            1,272,758
                            <LI>25,455,170</LI>
                        </ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    Pursuant to the 2015 Act and 17 CFR 201.1001, the adjusted penalty amounts in this Notice (and all penalty adjustments performed pursuant to the 2015 Act) apply to penalties imposed after the date the adjustment is effective for violations that occurred after November 2, 2015, the 2015 Act's enactment date. These penalty amounts supersede the amounts in the 2023 Adjustment.
                    <SU>15</SU>
                    <FTREF/>
                     For violations that occurred on or before November 2, 2015, the penalty amounts in Table I to 17 CFR 201.1001 continue to apply.
                    <SU>16</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         The penalty amounts in this Notice are being published in the 
                        <E T="04">Federal Register</E>
                         and will not be added to the Code of Federal Regulations in accordance with the 2015 Act and 17 CFR 201.1001(b). 
                        <E T="03">See</E>
                         28 U.S.C. 2461 note Sec. 4(a)(2); 17 CFR 201.1001(b). In addition to being published in the 
                        <E T="04">Federal Register</E>
                        <E T="03">,</E>
                         the penalty amounts in this Notice will be made available on the Commission's website at 
                        <E T="03">https://www.sec.gov/enforce/civil-penalties-inflation-adjustments.htm,</E>
                         as detailed in 17 CFR 201.1001(b). This website also lists the penalty amounts for violations that occurred on or before Nov. 2, 2015.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         17 CFR 201.1001(a).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">III. Small Business Regulatory Enforcement Fairness Act Status</HD>
                <P>
                    The Office of Management and Budget (“OMB”) has concurred in our recommendation that this Notice is not a “major rule” as defined by section 251 of the Small Business Regulatory Enforcement Fairness Act (“SBREFA”), 5 U.S.C. 804(2), because (1) it will not have an annual effect of $100 million dollars or more on the economy, (2) it does not present a major increase in prices for consumers or individual industries, and (3) it does not have significant adverse effects on competition, investment, or innovation.
                    <SU>17</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         
                        <E T="03">See generally</E>
                         SBREFA, Public Law 104-121 (1996).
                    </P>
                </FTNT>
                <SIG>
                    <P>By the Commission.</P>
                    <DATED>Dated: January 5, 2024.</DATED>
                    <NAME>Vanessa A. Countryman,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00378 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release No. 34-99279; File No. SR-NYSEARCA-2023-37]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; NYSE Arca, Inc.; Notice of Withdrawal of a Proposed Rule Change To List and Trade Shares of the COtwo Advisors Physical European Carbon Allowance Trust Under NYSE Arca Rule 8.201-E</SUBJECT>
                <DATE>January 5, 2024.</DATE>
                <P>
                    On May 23, 2023, NYSE Arca, Inc. (“NYSE Arca” or “Exchange”) filed with the Securities and Exchange Commission (“Commission”), pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (“Act”) 
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     a proposed rule change to list and trade shares of the COtwo Advisors Physical European Carbon Allowance Trust under NYSE Arca Rule 8.201-E (Commodity-Based 
                    <PRTPAGE P="1973"/>
                    Trust Shares). The proposed rule change was published for comment in the 
                    <E T="04">Federal Register</E>
                     on June 12, 2023.
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 97653 (June 6, 2023), 88 FR 38110.
                    </P>
                </FTNT>
                <P>
                    On July 25, 2023, pursuant to Section 19(b)(2) of the Act,
                    <SU>4</SU>
                    <FTREF/>
                     the Commission designated a longer period within which to approve the proposed rule change, disapprove the proposed rule change, or institute proceedings to determine whether to disapprove the proposed rule change.
                    <SU>5</SU>
                    <FTREF/>
                     On September 6, 2023, the Commission instituted proceedings pursuant to Section 19(b)(2)(B) of the Act 
                    <SU>6</SU>
                    <FTREF/>
                     to determine whether to approve or disapprove the proposed rule change.
                    <SU>7</SU>
                    <FTREF/>
                     On September 29, 2023, the Exchange submitted Amendment No. 1 to the proposed rule change, and on October 20, 2023, the Exchange withdrew Amendment No. 1. On November 27, the Commission designated a longer period for Commission action on the proposed rule change.
                    <SU>8</SU>
                    <FTREF/>
                     The Commission has not received any comment letters on the proposal. On December 26, 2023, the Exchange withdrew the proposed rule change (SR-NYSEARCA-2023-37).
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         15 U.S.C. 78s(b)(2).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 97972, 88 FR 49508 (July 31, 2023).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         15 U.S.C. 78s(b)(2)(B).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 98302, 88 FR 62608 (September 12, 2023).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 99019, 88 FR 84007 (December 1, 2023).
                    </P>
                </FTNT>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>9</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>9</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Christina Z. Milnor,</NAME>
                    <TITLE>Assistant Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-00384 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">SOCIAL SECURITY ADMINISTRATION</AGENCY>
                <DEPDOC>[Docket No. SSA-2023-0044]</DEPDOC>
                <SUBJECT>Notice on Penalty Inflation Adjustments for Civil Monetary Penalties</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Social Security Administration.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice announcing updated penalty inflation adjustments for civil monetary penalties for 2024.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Social Security Administration is giving notice of its updated maximum civil monetary penalties. These amounts are effective from January 15, 2024 through January 14, 2025. These figures represent an annual adjustment for inflation. The updated figures and notification are required by the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Jessica Stubbs Platt, Deputy Counsel to the Inspector General, Room 3-ME-1, 6401 Security Boulevard, Baltimore, MD 21235-6401, (410) 816-4054. For information on eligibility or filing for benefits, call the Social Security Administration's national toll-free number, 1-800-772-1213 or TTY 1-800-325-0778, or visit the Social Security Administration's internet site, Social Security Online, at 
                        <E T="03">http://www.socialsecurity.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    On June 27, 2016, pursuant to the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015 (the 2015 Act),
                    <SU>1</SU>
                    <FTREF/>
                     we published an interim final rule to adjust the level of civil monetary penalties (CMPs) under Sections 1129 and 1140 of the Social Security Act, 42 U.S.C. 1320a-8 and 1320b-10, respectively, with an initial “catch-up” adjustment effective August 1, 2016.
                    <SU>2</SU>
                    <FTREF/>
                     We announced in the interim final rule that for any future adjustments, we would publish a notice in the 
                    <E T="04">Federal Register</E>
                     to announce the new amounts. The annual inflation adjustment in subsequent years must be a cost-of-living adjustment based on any increases in the October Consumer Price Index for All Urban Consumers (CPI-U) (not seasonally adjusted) each year.
                    <SU>3</SU>
                    <FTREF/>
                     Inflation adjustment increases must be rounded to the nearest multiple of $1.
                    <SU>4</SU>
                    <FTREF/>
                     We last updated the maximum penalty amounts effective January 15, 2023.
                    <SU>5</SU>
                    <FTREF/>
                     Based on Office of Management and Budget (OMB) guidance,
                    <SU>6</SU>
                    <FTREF/>
                     the information below serves as public notice of the new maximum penalty amounts for 2024. The adjustment results in the following new maximum penalties, which will be effective as of January 15, 2024.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See https://www.congress.gov/bill/114th-congress/house-bill/1314/text.</E>
                          
                        <E T="03">See also</E>
                         81 FR 41438, 
                        <E T="03">https://www.federalregister.gov/documents/2016/06/27/2016-13241/penalty-inflation-adjustments-for-civil-money-penalties.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See</E>
                         81 FR 41438, 
                        <E T="03">https://www.federalregister.gov/documents/2016/06/27/2016-13241/penalty-inflation-adjustments-for-civil-money-penalties.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         OMB Memorandum, Implementation of the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015, M-16-06, p. 1 (February 24, 2016), 
                        <E T="03">https://www.whitehouse.gov/wp-content/uploads/legacy_drupal_files/omb/memoranda/2016/m-16-06.pdf. See also</E>
                         81 FR 41438, 
                        <E T="03">https://www.federalregister.gov/documents/2016/06/27/2016-13241/penalty-inflation-adjustments-for-civil-money-penalties.</E>
                          
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         OMB Memorandum, Implementation of the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015, M-16-06, p. 3 (February 24, 2016), 
                        <E T="03">https://www.whitehouse.gov/wp-content/uploads/legacy_drupal_files/omb/memoranda/2016/m-16-06.pdf. See also</E>
                         81 FR 41438, 
                        <E T="03">https://www.federalregister.gov/documents/2016/06/27/2016-13241/penalty-inflation-adjustments-for-civil-money-penalties.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         87 FR 80245, 
                        <E T="03">https://www.federalregister.gov/documents/2022/12/29/2022-28284/notice-on-penalty-inflation-adjustments-for-civil-monetary-penalties.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         OMB Memorandum, Implementation of Penalty Inflation Adjustments for 2024, Pursuant to the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015, M-24-07, p. 1 (December 19, 2023), 
                        <E T="03">https://www.whitehouse.gov/wp-content/uploads/2023/12/M-24-07-Implementation-of-Penalty-Inflation-Adjustments-for-2024.pdf.</E>
                    </P>
                </FTNT>
                <P>Section 1129 CMPs (42 U.S.C. 1320a-8):</P>
                <EXTRACT>
                    <P>$9,399.00 (current maximum per violation for fraud facilitators in a position of trust) × 1.03241 (OMB-issued inflationary adjustment multiplier) = $9,703.62. When rounded to the nearest dollar, the new maximum penalty is $9,704.</P>
                    <P>$9,966.00 (current maximum per violation for all other violators) × 1.03241 (OMB-issued inflationary adjustment multiplier) = $10,289.00. When rounded to the nearest dollar, the new maximum penalty is $10,289.</P>
                </EXTRACT>
                <P>Section 1140 CMPs (42 U.S.C. 1320b-10):</P>
                <EXTRACT>
                    <P>$12,397.00 (current maximum per violation for all violations other than broadcast or telecasts) × 1.03241 (OMB-issued inflationary adjustment multiplier) = $12,798.79. When rounded to the nearest dollar, the new maximum penalty is $12,799.</P>
                    <P>$61,982.00 (current maximum per violative broadcast or telecast) × 1.03241 (OMB-issued inflationary adjustment multiplier) = $63,990.84. When rounded to the nearest dollar, the new maximum penalty is $63,991.</P>
                </EXTRACT>
                <SIG>
                    <NAME>Michelle Murray,</NAME>
                    <TITLE>Chief Counsel, Office of the Inspector General, Social Security Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00408 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4191-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SOCIAL SECURITY ADMINISTRATION</AGENCY>
                <DEPDOC>[Docket No. SSA-2023-0005]</DEPDOC>
                <SUBJECT>Finding Regarding Foreign Social Insurance or Pension System of Cambodia</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Social Security Administration.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of finding regarding foreign social insurance or pension system of Cambodia.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        We find that, under the Alien Nonpayment Provision of the Social Security Act (Act), citizens of Cambodia may continue to receive Social Security benefits under title II, after 6 consecutive months of absence from the United States, without regard to length of absence, if they meet certain conditions. This finding is based on our analysis of information and data we 
                        <PRTPAGE P="1974"/>
                        received about the social insurance system of Cambodia and its laws. The Commissioner of Social Security delegated the authority to make this finding to the Deputy Commissioner for Retirement and Disability Policy.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>We will implement this finding on January 11, 2024.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Icie K. Allen, Office of Income Security Programs, 2500 Robert Ball Building, 6401 Security Boulevard, Baltimore, MD 21235-6401, (410) 965-8945. For more information on eligibility or filing for benefits, call our national toll-free number, 1-800-772-1213 or TTY 1-800-325-0778, or visit our internet site, Social Security Online, at 
                        <E T="03">https://www.socialsecurity.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    We are prohibited, by law, from paying benefits under title II of the Act to non-U.S. citizens who remain outside the United States for more than 6 consecutive calendar months, unless they meet an exception provided in the law. We refer to this portion of the law as the Alien Nonpayment Provision (ANP).
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Section 202(t) of the Act, 42 U.S.C. 402(t).
                    </P>
                </FTNT>
                <P>We recently reviewed the Cambodian social insurance system to determine if it meets the criteria for an ANP exception. This is a new finding about the social insurance system of Cambodia under the ANP. As a result of this finding, citizens of Cambodia may continue receiving benefits under title II of the Act after 6 consecutive calendar months outside the United States if they meet one of the following conditions:</P>
                <P>1. Their benefits are based on the earnings of an individual who earned at least 40 quarters of coverage, or</P>
                <P>2. Their benefits are based on the earnings of an individual who had periods of U.S. residency that add up to at least 10 years.</P>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    The ANP, section 202(t) of the Act, prohibits payment of title II benefits to individuals who are not U.S. citizens or nationals for any month after they have been outside the United States for more than 6 consecutive calendar months. Beneficiaries who meet one of the exceptions described in the ANP may continue to receive benefits under title II without regard to absence from the United States. Some of these exceptions require that dependents and survivors meet a 5-year U.S. residency requirement for benefits to continue after 6 consecutive calendar months of absence from the United States.
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Section 202(t)(2), (4), (11) of the Act, 42 U.S.C. 402(t)(2), (4), (11).
                    </P>
                </FTNT>
                <P>
                    To determine whether the social insurance or pension system meets the criteria for an exception under section 202(t)(2) of the Act, we review the foreign country's laws. In addition, we review information and data that we receive from the administrators of the social insurance or pension system of that country. The Commissioner of the Social Security Administration publishes these findings in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <P>
                    On July 26, 1958, we published a list of countries that did not meet the requirements of section 202(t)(2), which included Cambodia.
                    <SU>3</SU>
                    <FTREF/>
                     Cambodia did not meet 202(t)(2) because it did not operate a social insurance or pension system of general application. However, the exceptions provided under section 202(t)(4)(A) and (B) did apply to qualified citizens of Cambodia.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         23 FR 5673 (July 26, 1958).
                    </P>
                </FTNT>
                <P>
                    The exceptions under section 202(t)(4)(A) and (B) no longer applied to citizens of Cambodia from April 1975 through November 2001, because the U.S. Department of the Treasury imposed payment restrictions for Cambodia.
                    <SU>4</SU>
                    <FTREF/>
                     The U.S. Department of the Treasury lifted those payment restrictions effective December 10, 2001 
                    <SU>5</SU>
                    <FTREF/>
                     and we updated our regulation in September 2009 
                    <SU>6</SU>
                    <FTREF/>
                     accordingly.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         40 FR 19202 (May 2, 1975).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         66 FR 63623 (Dec. 10, 2001).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         74 FR 48855 (Sept. 25, 2009).
                    </P>
                </FTNT>
                <P>
                    We requested information from Cambodia to make an updated finding of Cambodia's status under section 202(t)(2) of the Act. In June 2014, we received a completed Form SSA-142, 
                    <E T="03">Report of Social Insurance or Pension System,</E>
                     from Cambodia. We initiated an analysis to reach the finding we describe here.
                </P>
                <P>On September 25, 2002, Cambodia enacted the Law on Social Security Schemes for Persons Defined by the Provisions of the Labour Law. This law contains provisions for the earned right to benefits based on contributions from employment covered under Cambodia's social security scheme. However, our review indicates that Cambodia's social insurance system is not in effect because Cambodia does not currently collect contributions or pay pension benefits as of the date of this Finding.</P>
                <HD SOURCE="HD1">Finding</HD>
                <HD SOURCE="HD2">Section 202(t)(2) Exception</HD>
                <P>Section 202(t)(2) of the Act provides that the prohibition against payment shall not apply to individuals who are citizens of a foreign country that the Commissioner of Social Security finds has a social insurance or pension system that is in effect and of general application in such country, and that:</P>
                <P>(A) pays periodic benefits, or the actuarial equivalent thereof, on account of old age, retirement, or death; and</P>
                <P>(B) permits individuals who are U.S. citizens but not citizens of that country and who qualify for benefits to receive those benefits, or the actuarial equivalent thereof, while outside the foreign country regardless of the duration of the absence.</P>
                <P>We find that Cambodia does not meet the conditions in section 202(t)(2) of the Act because the social insurance system of Cambodia is not in effect. This finding is effective January 1, 2002, the first month after the U.S. Treasury restriction was lifted. This finding under section 202(t)(2) does not preclude consideration of section 202(t)(4)(A) and (B).</P>
                <HD SOURCE="HD2">Section 202(t)(4) Exception</HD>
                <P>We find that the ANP exceptions in 202(t)(4)(A) and (B) below apply to citizens of Cambodia in specific instances, as discussed in the next two paragraphs.</P>
                <P>Section 202(t)(4)(A) of the Act provides that the prohibition against payment shall not apply to the benefits payable on the earnings record of an individual who has at least 40 quarters of coverage under Social Security.</P>
                <P>Section 202(t)(4)(B) of the Act provides that the prohibition against payment shall not apply to the benefits payable on the earnings record of an individual who has resided in the United States for a period or periods aggregating 10 years or more.</P>
                <P>Both exceptions are subject to residency requirements: Section 202(t)(11) requires that dependent and survivor beneficiaries must have resided in the United States for 5 years or more while in a qualifying relationship with the individual on whose earnings the benefits are based.</P>
                <P>Moreover, the exceptions in section 202(t)(4)(A) and (B) will not apply if:</P>
                <P>• The individual is a citizen of a foreign country that has in effect a social insurance or pension system that is of general application and that pays periodic benefits (or the actuarial equivalent) on account of old age, retirement, or death; but the social insurance or pension system does not pay benefits to qualifying U.S. citizens without regard to the duration of the absence from the foreign country; or,</P>
                <P>
                    • The individual is a citizen of a foreign country that has no social insurance or pension system of general application and at any time within 5 years before January 1968 (or the first month after December 1967 in which 
                    <PRTPAGE P="1975"/>
                    benefits are subject to ANP suspension), the individual was residing in a country to which payments were withheld by Treasury under 31 U.S.C. 3329(a) and 3330(a).
                </P>
                <P>We apply this finding from January 1, 2002, the first month after the U.S. Department of Treasury lifted the statutory restriction on foreign payments.</P>
                <P>Our finding that section 202(t)(4)(A) and (B) apply to citizens of Cambodia is subject to section 202(t)(11). Section 202(t)(11) requires that dependent and survivor title II beneficiaries must also have resided in the United States for a total period of 5 years or more while in a qualifying relationship with the individual on whose earnings the benefits are based.</P>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance Program Nos. 96.001, Social Security—Disability Insurance; 96.002, Social Security—Retirement Insurance; and 96.004, Social Security—Survivors Insurance)</FP>
                </EXTRACT>
                <P>
                    The Commissioner of the Social Security Administration, Martin O'Malley, having reviewed and approved this document, is delegating the authority to electronically sign this document to Faye I. Lipsky, who is the primary 
                    <E T="04">Federal Register</E>
                     Liaison for SSA, for purposes of publication in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <SIG>
                    <NAME>Faye I. Lipsky,</NAME>
                    <TITLE>Federal Register Liaison, Office of Legislation and Congressional Affairs, Social Security Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00404 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4191-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF STATE</AGENCY>
                <DEPDOC>[Public Notice: 12303]</DEPDOC>
                <SUBJECT>Notice of Determinations; Culturally Significant Objects Being Imported for Exhibition—Determinations: “Hidden Faces: Covered Portraits of the Renaissance” Exhibition</SUBJECT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        Notice is hereby given of the following determinations: I hereby determine that certain objects being imported from abroad pursuant to agreements with their foreign owners or custodians for temporary display in the exhibition “Hidden Faces: Covered Portraits of the Renaissance” at The Metropolitan Museum of Art, New York, New York, and at possible additional exhibitions or venues yet to be determined, are of cultural significance, and, further, that their 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>Nicole L. Elkon,</NAME>
                    <TITLE>Deputy Assistant Secretary for Professional and Cultural Exchanges, Bureau of Educational and Cultural Affairs, Department of State.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-00388 Filed 1-10-24; 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-2024-0001]</DEPDOC>
                <SUBJECT>Coastwise-Qualified Launch Barges: 46 CFR 389.3(a) Notification</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Maritime Administration (MARAD), 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>To maximize the use of coastwise-qualified vessels, in January of each calendar year, MARAD requests owners and operators of coastwise-qualified launch barges or other interested parties to notify the Agency of their interest in, and provide certain information relating to, the transportation, installation, or launching of platform jackets. MARAD publishes the notifications as a resource to companies contemplating these operations on the outer continental shelf. The notifications should include information set forth in the Supplementary Information section below.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit comments on or before February 12, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments identified by DOT Docket Number MARAD-2024-0001 by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">http://www.regulations.gov.</E>
                         Search “MARAD-2024-0001” and follow the instructions for submitting comments on the electronic docket site.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail or Hand Delivery:</E>
                         Docket Management Facility, 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>
                        All submissions must include the agency name and docket number for this notice. All comments received will be posted without change to 
                        <E T="03">http://www.regulations.gov</E>
                         including any personal information provided.
                    </P>
                </NOTE>
                <P>
                    <E T="03">Docket:</E>
                     For access to the docket to read comments received, go to 
                    <E T="03">http://www.regulations.gov</E>
                     and search using “MARAD-2024-0001.”
                </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, Room W23-461, Washington, DC 20590. Telephone: (202) 366-0903. Email: 
                        <E T="03">patricia.hagerty@dot.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Pursuant to 46 U.S.C. 55108, the Secretary of Transportation has the authority to adopt procedures that timely provide information that would maximize the use of coastwise-qualified vessels for the transportation of platform jackets between U.S. coastwise points and the U.S. Outer Continental Shelf. This authority has been delegated to MARAD. The regulation promulgated under the authority of 46 U.S.C. 55108, 46 CFR 389.3(a), requires that MARAD publish a notice in the 
                    <E T="04">Federal Register</E>
                     requesting notification from owners, operators, or potential operators of coastwise-qualified launch barges, or other interested parties, of: (1) their interest in participating in the transportation and, if needed, the launching or installation of offshore platform jackets; (2) the contact information for their company; and, (3) the specifications of any currently owned or operated coastwise-qualified launch barges or plans to construct such a vessel. The notification should indicate that the vessel's certificate of documentation has a coastwise endorsement. The information provided in the notifications will be published at 
                    <E T="03">http://MARAD.regulations.gov.</E>
                     46 CFR 389.3(e).
                    <PRTPAGE P="1976"/>
                </P>
                <HD SOURCE="HD1">Privacy Act</HD>
                <P>
                    In accordance with 5 U.S.C. 553(c), MARAD solicits comments from owners and operators of coastwise-qualified launch barges to compile a list of vessels that could potentially be available to transport, and if necessary, launch or install platform jackets. All timely comments will be considered; however, to facilitate comment tracking, commenters should provide their name or the name of their organization. If comments contain proprietary or confidential information, commenters may contact the Agency for alternate submission instructions. The electronic form of all comments received into MARAD dockets may be searched 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. 55108, 49 CFR 1.93(a), 46 CFR 389.)</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. 2024-00443 Filed 1-10-24; 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-0099; Notice 1]</DEPDOC>
                <SUBJECT>Ford Motor Company, Receipt 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>Receipt of petition.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        Ford Motor Company (Ford), has determined that certain model year (MY) 2018-2020 Ford F-150 motor vehicles do not fully comply with Federal Motor Vehicle Safety Standard (FMVSS) No. 108, 
                        <E T="03">Lamps, Reflective Devices, and Associated Equipment.</E>
                         Ford filed a noncompliance report dated July 22, 2022, and subsequently petitioned NHTSA on August 12, 2022, for a decision that the subject noncompliance is inconsequential as it relates to motor vehicle safety. This document announces receipt of Ford's petition.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Send comments on or before February 12, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Interested persons are invited to submit written data, views, and arguments on this petition. Comments must refer to the docket and notice number cited in the title of this notice and may be submitted by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Send comments by mail addressed to the 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 comments by hand to the U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE, Washington, DC 20590. The Docket Section is open on weekdays from 10 a.m. to 5 p.m. except for Federal holidays.
                    </P>
                    <P>
                        • 
                        <E T="03">Electronically:</E>
                         Submit comments electronically by logging onto the Federal Docket Management System (FDMS) website at 
                        <E T="03">https://www.regulations.gov/.</E>
                         Follow the online instructions for submitting comments.
                    </P>
                    <P>• Comments may also be faxed to (202) 493-2251.</P>
                    <P>
                        Comments must be written in the English language, and be no greater than 15 pages in length, although there is no limit to the length of necessary attachments to the comments. If comments are submitted in hard copy form, please ensure that two copies are provided. If you wish to receive confirmation that comments you have submitted by mail were received, please enclose a stamped, self-addressed postcard with the comments. Note that all comments received will be posted without change to 
                        <E T="03">https://www.regulations.gov,</E>
                         including any personal information provided.
                    </P>
                    <P>All comments and supporting materials received before the close of business on the closing date indicated above will be filed in the docket and will be considered. All comments and supporting materials received after the closing date will also be filed and will be considered to the fullest extent possible.</P>
                    <P>
                        When the petition is granted or denied, notice of the decision will also be published in the 
                        <E T="04">Federal Register</E>
                         pursuant to the authority indicated at the end of this notice.
                    </P>
                    <P>
                        All comments, background documentation, and supporting materials submitted to the docket may be viewed by anyone at the address and times given above. The documents may also be viewed on the internet at 
                        <E T="03">https://www.regulations.gov</E>
                         by following the online instructions for accessing the dockets. The docket ID number for this petition is shown in the heading of this notice.
                    </P>
                    <P>
                        DOT's complete Privacy Act Statement is available for review in a 
                        <E T="04">Federal Register</E>
                         notice published on April 11, 2000 (65 FR 19477-78).
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Leroy Angeles, General Engineer, NHTSA, Office of Vehicle Safety Compliance, (202) 366-5304.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Overview</HD>
                <P>
                    Ford determined that certain MY 2018-2020 Ford F-150 motor vehicles equipped with combination lamps do not fully comply with paragraph S7.6.13 of FMVSS No. 108, 
                    <E T="03">Lamps, Reflective Devices, and Associated Equipment</E>
                     (49 CFR 571.108).
                </P>
                <P>
                    Ford filed an original noncompliance report dated July 22, 2022, pursuant to 49 CFR part 573, 
                    <E T="03">Defect and Noncompliance Responsibility and Reports.</E>
                     Ford petitioned NHTSA on August 12, 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>This notice of receipt of Ford's petition is published under 49 U.S.C. 30118 and 30120 and does not represent any agency decision or another exercise of judgment concerning the merits of the petition.</P>
                <HD SOURCE="HD1">II. Vehicles Involved</HD>
                <P>Approximately 1,271,854 MY 2018-2020 Ford F-150 motor vehicles, manufactured between January 10, 2017, and October 22, 2020, are potentially involved.</P>
                <HD SOURCE="HD1">III. Noncompliance</HD>
                <P>Ford explains that the rear combination lamps installed on the subject vehicles may exceed the maximum backup lamp photometry requirements as required by paragraph S7.6.13 and Table XII of FMVSS No. 108. Specifically, when the subject rear combination lamps were tested in accordance with S7.6.13, 7 of the 8 samples exceeded the maximum candela (cd) rating of 300 at the H-V test point, and 1 of the 8 samples also exceeded the maximum at the H-10L test point.</P>
                <HD SOURCE="HD1">IV. Rule Requirements</HD>
                <P>
                    Paragraph S7.6.13 and Table XII of FMVSS No. 108 include the requirements relevant to this petition. S7.6.13 provides that each backup lamp 
                    <PRTPAGE P="1977"/>
                    must be designed to conform to the photometry requirements of Table XII, when tested according to the procedure of S14.2.1, as specified by this section. Table XII provides the minimum and maximum candela values for photometric intensity. Specifically at the H-10L test point, any single lamp in a multiple lamp system must have a minimum photometric intensity of 15 cd and a maximum photometric intensity of 300 cd; at the H-V test point, any single lamp in a multiple lamp system must have a minimum photometric intensity of 15 cd and a maximum photometric intensity of 300 cd.
                </P>
                <HD SOURCE="HD1">V. Background Information</HD>
                <P>Ford received an information request from NHTSA on May 13, 2022, Ford says NHTSA reported a preliminary test failure was observed in the backup lamp function in the rear combination lamps of a 2018 F-150 base series motor vehicle.</P>
                <P>Ford says that NHTSA provided a FMVSS No. 108 test report dated May 9, 2022, in which Calcoast tested lighting functions of the rear combination lamps on behalf of NHTSA. Ford states that according to the test report, Calcoast tested 8 samples at each of the 15 test points, all of which exceeded the maximum candela rating of 300 that is required at the H-V test point, and one of the samples also exceeded the maximum candela rating at the H-10L test point. Based on the test results of the 7 backup lamps that only exceeded the requirement at the H-V test point, Ford believes that the sample that also exceeded the maximum requirement at the H-10L test point was influenced by the H-V test point “and is not indicative of an additional root cause.”</P>
                <P>Ford states that it reviewed the supplier's lamp certification data as well as their historical and ongoing product audit testing records and found that the lamps tested at values that were “consistently below the 300-cd maximum requirement for backup lamps.” Upon further review, Ford discovered that “the initial certification test data provided to Ford by the supplier pertained to a test that was conducted with a bulb socket that did not represent the final design.” According to Ford, they were informed by the supplier that they retested the lamp with the correct focal length socket and certified the measurement for the backup lamp at H-V as 253.4 cd, which was below the required 300 cd limit. Ford later discovered that the supplier's ongoing audit testing was being conducted using a “production” bulb, rather than the “rated” bulb that is required for certification. The supplier conducted additional testing using 30 sample assemblies each for the left-hand and right-designs. The additional testing showed values exceeding 300 cd at test point H-V. Ford states that on July 15, 2022, its Field Review Committee reviewed the concern and determined that the subject rear combination lamps were not compliant with the backup lamp illumination requirements provided in FMVSS No. 108. Based on its analysis of existing and new test data, Ford believes that the subject noncompliance is inconsequential to motor vehicle safety.</P>
                <HD SOURCE="HD2">Design of the Lamp</HD>
                <P>Ford details the design of the subject backup lamps and states that the subject vehicles are equipped with the “low series” variation of the rear combination lamp. MY 2018 Ford-F-150 vehicles were available in two variations of taillamps: (1) the “BLIS series” lamp that incorporates Blind Spot Information System (BLIS) sensors, and (2) the “low series” lamp that does not incorporate BLIS sensors.</P>
                <HD SOURCE="HD2">Regulatory Framework</HD>
                <P>Ford states the purpose of FMVSS No. 108, and the definition of backup lamps provided in paragraphs S2 and S4 of the standard. According to Ford, in order to determine whether the subject noncompliance impacts motor vehicle safety, it should be evaluated from the perspective of a pedestrian or other drivers. Ford says it has used this perspective in its analysis.</P>
                <P>Ford explains that the backup lamps at issue are required to have a luminosity greater than 15 and less than 300 cd, according to Table XII of FMVSS No. 108. Ford says that the following requirements are important when considering the subject noncompliance: (1) testing is conducted at a series of 22 points 100 feet away from the test apparatus, and (2) bulb certification testing is to be conducted with a “rated” bulb.</P>
                <HD SOURCE="HD1">VI. Summary of Ford's Petition</HD>
                <P>The following views and arguments presented in this section, “VI. Summary of Ford's Petition,” are the views and arguments provided by Ford. They have not been evaluated by the Agency and do not reflect the views of the Agency. Ford describes the subject noncompliance and contends that the noncompliance is inconsequential as it relates to motor vehicle safety.</P>
                <P>Ford believes that the subject noncompliance is inconsequential to motor vehicle safety because the backup lamp only illuminates while the vehicle is backing up or is beginning to back up, therefore, normal operation on roads and highways would be unaffected and the noncompliance does not impact the conspicuity of motor vehicles on public roads, so that their presence is perceived, and their signals are understood during the day and at night or in low visibility conditions.</P>
                <P>Ford claims that the applicable testing procedures do not correlate “to what another driver or pedestrian would experience if they were viewing one of the subject vehicles.” Ford states that (1) vehicles in the field would be equipped with production bulbs, not rated bulbs, and (2) “the voltage used on the NHTSA test report is higher than what could be on the vehicle.”</P>
                <P>
                    Ford states that “[f]or the subject vehicles, the theoretical maximum voltage that could be applied to the backup lamps is 13.3 v,” and Ford designed the lamp to operate at 12.8v. Based on Ford's design, the supplier predicted that the left-hand backup lamps would test at 236 Cd at the H-V test point, and the right-hand back up lamp would test at 234 Cd at the same test point which is about 22 percent less than the 300 Cd limit that is required. However, Ford says it decided to verify the design assumptions because “[t]he voltage for the compliance test sometimes does not match the voltage supplied by the vehicles, and a change in voltage results in a change in brightness.” 
                    <SU>1</SU>
                    <FTREF/>
                     Ford found that of 14 vehicles, the maximum output was 12.85 volts, which it says is more aligned with the design. Ford found that with the 12.85 volts, “a statistical worst case of 327 candelas at the HV point (9% exceedance) is predicted.”
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See, e.g., Grant of Petition for Determination of Inconsequential Noncompliance; Hella, Inc.;</E>
                         55 FR 37601. September 12, 1990.
                    </P>
                </FTNT>
                <P>
                    Upon review of NHTSA's test report that showed the subject noncompliance, Ford says it tested 30 lamps, comparing the use of production bulbs at 12.9 volts and the theoretical maximum at 13.3 volts. Ford found that at 12.9 volts, the H-V test point values “ranged from 197.8 cd to 306 cd (the latter representing 2 [percent] exceedance).” At 13.3 volts, Ford recorded values for the H-V test point that “ranged from 221.32 cd to 337.41 cd (the latter representing 12.5 [percent] exceedance).” Ford adds that, in order to “achieve a value of 460 Lm for the rated bulb, those tests were run at a voltage of 14.25 volts and amperage of 1.961 amps.”
                    <PRTPAGE P="1978"/>
                </P>
                <P>
                    Ford notes that it is not aware of any reports, complaints, accidents, or injuries related the subject noncompliance. Ford says it “recognizes that this fact is not dispositive” but believes that it is “illustrative of the field performance.” 
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See North American Subaru, Inc., Denial of Petition for Decision of Inconsequential Noncompliance;</E>
                         87 FR 46764 (August 10, 2022).
                    </P>
                </FTNT>
                <P>In its petition, Ford relies on studies done by the University of Michigan Transportation Research Institute (UMTRI), its own additional testing, including a “jury evaluation,” and NHTSA precedent to support its claims.</P>
                <HD SOURCE="HD2">UMTRI Reports</HD>
                <P>
                    Ford states that past NHTSA decisions for inconsequential noncompliance referred to UMTRI's, 1994 report titled, “
                    <E T="03">Driver Perception of Just Noticeable Differences of Automotive Signal Lamp Intensities</E>
                    ” 
                    <SU>3</SU>
                    <FTREF/>
                     and its 1997 report that extended the study to low beam automotive headlamps.
                    <SU>4</SU>
                    <FTREF/>
                     Ford argues that NHTSA has granted past petitions in cases where luminosity exceeds the requirement based on the reports finding that “the human eye is unable to detect a 25 [percent] change in illumination.” Ford says the 1994 study indicated that the results were relevant for evaluating inconsequential noncompliance petitions pertaining to vehicle lamp intensities that exceed the performance requirements given in FMVSS No. 108.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         DOT report, 
                        <E T="03">Driver Perception of Just Noticeable Differences of Automotive Signal Lamp Intensities,</E>
                         DOT HS 808 209, September 1994. 
                        <E T="03">https://ntrl.ntis.gov/NTRL/dashboard/searchResults/titleDetail/PB95206306.xhtml.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See Just Noticeable Differences for Low-Beam Headlamp Intensities</E>
                         (Sayer, Flannagan, Sivak, Kojima, and Flannagan), Report No. UMTRI-97-4, February 1997. 
                        <E T="03">https://ntrl.ntis.gov/NTRL/dashboard/searchResults/titleDetail/PB97147300.xhtml.</E>
                    </P>
                </FTNT>
                <P>For vehicles in the field, Ford's prediction is that the maximum candela value will be 327 cd, or a 9 percent exceedance, at point H-V due to the maximum voltage in the subject vehicle. Ford believes that the extent of the subject noncompliance “is such that the human eye is unable to distinguish the worst- case rear backup lamp from a compliant rear backup lamp.”</P>
                <P>Ford says it then conducted a jury evaluation to confirm the results of the UMTRI studies in relation to the subject noncompliance and its impact on drivers of trailing vehicles and pedestrians.</P>
                <HD SOURCE="HD2">Jury Evaluation</HD>
                <P>
                    Ford's jury evaluation 
                    <SU>5</SU>
                    <FTREF/>
                     involved six participants observing “the lamps with voltage modulated to represent the candela values measured in the Agency's testing, under a variety of conditions (light, dark, tail lamps illuminated, brake lamps illuminated).”
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         More details of Ford's jury evaluation can be found in their petition available on the docket.
                    </P>
                </FTNT>
                <P>The observers were unable to consistently distinguish the differences between the light outputs when given seven seconds. When given approximately 5 minutes to evaluate the light outputs, all of the observers could identify which lamps were at 240 cd which were at 350 cd. However, after 5 minutes, none of the observers could distinguish between lamps that were set at 300 cd and lamps set at 350 cd. Additionally, the observers did not identify any conditions that caused “unusual brightness or glare that could potentially affect operators of a trailing vehicle or a pedestrian.” Ford first asked the observers to evaluate the light output with just the backup lamps illuminated in the taillamp, then asked the observers to evaluate the light output with the backup lamps at 350 cd, and the taillamp brake lamps illuminated. Ford says the observers found that the “illumination of the stop lamps took the focus away from the backup lamps,” because of the color difference and the similarities in brightness between the lighting functions. Ford says that the backup lamps being illuminated with the brake lamps also being illuminated is very unlikely because a driver would typically depress the brake pedal when shifting to reverse the vehicle and while backing up. Ford contends that these results validated the UMTRI reports.</P>
                <HD SOURCE="HD2">NHTSA Precedent</HD>
                <P>Ford states that, historically, NHTSA has granted petitions involving noncompliances similar to the subject noncompliance. Ford cites the following NHTSA decisions:</P>
                <P>1. Chrysler Corp.; Grant of Petition for Decision of Inconsequential Noncompliance; 52 FR 17499 (May 8, 1987). This petition concerned backup lamps installed on vehicles that were 68 candela below the required minimum at test point H-V, and therefore, did not meet the photometric requirements of FMVSS No. 108. Ford says, “NHTSA concluded that the 20 [percent] reduction on 800 vehicles would be statistically unlikely to produce even one injury.”</P>
                <P>2. Grant of Petition for Decision of Inconsequential Noncompliance; Hella Inc., 55 FR 37601 (September 12, 1990). Ford says Hella's petition for inconsequential noncompliance involved taillamps that exceeded the requirement by 20 percent in the worst case. Ford states that Hella's petition included the argument that the human eye cannot identify a change in luminescence unless increases or decreases by more than a 25 percent. Hella added that the lamps were designed to conform to FMVSS No. 108, and the voltage of production lamps would be less than the voltage tested in the laboratory. In granting Hella's petition, Ford says, “NHTSA agreed with Hella's statements and referenced other instances where NHTSA granted petitions for inconsequentiality regarding the light output requirements of FMVSS No. 108.”</P>
                <P>3. Subaru of America; Grant of Petition for Determination of Inconsequential Noncompliance, 56 FR 59971, November 26, 1991. In this case, Ford says the noncompliance at issue concerned “failures of luminous intensity on the side reflex reflector” where the lamps tested at 20 percent less than what is required by FMVSS No. 108. Additionally, Ford says Subaru's petition included details of a “study where observers could not differentiate between the reflected light of complying and noncomplying reflectors at distances of 30 m, 60 m, and 100 m.” Ford states that NHTSA granted Subaru's petition based on the same reasoning used in Hella's petition.</P>
                <P>4. Toyota Motor North America, Inc, Grant of Petition for Decision of Inconsequential Noncompliance; 85 FR 39679 (July 1, 2020). Ford describes a petition submitted by Toyota in which the noncompliance involved vehicles that were equipped with reflex reflectors that had a luminous intensity that were 18 percent less than the required minimum. Ford says NHTSA agreed with Toyota “that a change of luminous intensity of 18 percent is imperceptible to the human eye” and based its decision in this case on an evaluation provided by NHTSA and the prior Hella and Subaru decisions.</P>
                <P>
                    5. North America Subaru, Inc., Denial of Petition for Decision of Inconsequential Noncompliance; 87 FR 48764, August 10, 2022. The noncompliance in this petition involved front combination lamp side reflex reflectors with a luminous intensity that measured below the minimum requirement by more than 25 percent. While NHTSA denied Subaru's petition for inconsequential noncompliance in that case, Ford believes that its current petition differs from Subaru's because Ford conducted a jury evaluation and 
                    <PRTPAGE P="1979"/>
                    relied on camera measurements to support its petition. Second, Ford quotes NHTSA's decision as stating, “the performance requirements for reflex reflectors are measured in (cd/incident ft-c) or (mcd/lux), whereas the performance requirements for signal lighting assessed in the [UMTRI] study are measured in candela (cd).”
                </P>
                <P>Ford 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>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, any decision on this petition only applies to the subject vehicles that Ford no longer controlled at the time it determined that the noncompliance existed. However, any decision on this petition does not relieve vehicle 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 Ford 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. 2024-00392 Filed 1-10-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-59-P</BILCOD>
        </NOTICE>
    </NOTICES>
    <VOL>89</VOL>
    <NO>8</NO>
    <DATE>Thursday, January 11, 2024</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="1981"/>
            <PARTNO>Part II</PARTNO>
            <AGENCY TYPE="P">Department of Education</AGENCY>
            <CFR>34 CFR Parts 75, 76, 77, et al.</CFR>
            <TITLE>Education Department General Administrative Regulations and Related Regulatory Provisions; Proposed Rule</TITLE>
        </PTITLE>
        <PRORULES>
            <PRORULE>
                <PREAMB>
                    <PRTPAGE P="1982"/>
                    <AGENCY TYPE="S">DEPARTMENT OF EDUCATION</AGENCY>
                    <CFR>34 CFR Parts 75, 76, 77, 79, and 299</CFR>
                    <RIN>RIN 1875-AA14</RIN>
                    <DEPDOC>[Docket ID ED-2023-OPEPD-0110]</DEPDOC>
                    <SUBJECT>Education Department General Administrative Regulations and Related Regulatory Provisions</SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Office of Planning, Evaluation and Policy Development, Department of Education.</P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Notice of proposed rulemaking.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>
                            The Secretary of Education proposes to amend the Education Department General Administrative Regulations (EDGAR) and associated regulatory provisions to update the regulations and better align them with other U.S. Department of Education (Department) regulations and procedures. A brief summary of the proposed rule is available on 
                            <E T="03">Regulations.gov</E>
                             in the docket for the rulemaking.
                        </P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>We must receive your comments on or before February 26, 2024.</P>
                    </EFFDATE>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P>
                            Comments must be submitted electronically via the Federal eRulemaking Portal at 
                            <E T="03">www.regulations.gov.</E>
                             However, if you require an accommodation or cannot otherwise submit your comments via 
                            <E T="03">http://www.regulations.gov,</E>
                             please contact the program contact person listed under 
                            <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                            . The Department will not accept comments submitted after the comment period closes. To ensure that we do not receive duplicate copies, please submit your comments only once. In addition, please include the Docket ID at the top of your comments.
                        </P>
                        <P>
                            Information on using 
                            <E T="03">Regulations.gov</E>
                            , including instructions for accessing agency documents, submitting comments, and viewing the docket, is available on the site under “FAQ.”
                        </P>
                        <P>
                            <E T="03">Note:</E>
                             The Department's policy is generally to make comments received from members of the public available for public viewing in their entirety at 
                            <E T="03">www.regulations.gov.</E>
                             Therefore, commenters should be careful to include in their comments only information that they wish to make publicly available. Commenters should not include in their comments any information that identifies other individuals or that permits readers to identify other individuals. The Department will not make comments that contain personally identifiable information about someone other than the commenter publicly available on 
                            <E T="03">www.regulations.gov</E>
                             for privacy reasons. Therefore, commenters should be careful to include in their comments only information that they wish to make publicly available.
                        </P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>
                            Kelly Terpak, U.S. Department of Education, 400 Maryland Avenue SW, Room 4C212, Washington, DC 20202. Telephone: (202) 245-6776. Email: 
                            <E T="03">EDGAR@ed.gov.</E>
                        </P>
                        <P>If you are deaf, hard of hearing, or have a speech disability and wish to access telecommunications relay services, please dial 7-1-1.</P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P/>
                    <HD SOURCE="HD1">Executive Summary</HD>
                    <P>
                        <E T="03">Purpose of this Regulatory Action:</E>
                         The last major update to EDGAR was in 2013. Given that EDGAR serves as the foundational set of regulations for the Department, we have reviewed EDGAR, evaluated it for provisions that, over time, have become outdated, unnecessary, or inconsistent with other Department regulations, and identified ways in which EDGAR could be updated, streamlined, and otherwise improved. Specifically, we propose to amend parts 75, 76, 77, 79, and 299 of title 34 of the Code of Federal Regulations. These changes are detailed in the Summary of Major Provisions of this Regulatory Action and the Significant Proposed Regulations section of this document.
                    </P>
                    <P>
                        <E T="03">Summary of Major Provisions of this Regulatory Action:</E>
                         As discussed in greater detail in the 
                        <E T="03">Significant Proposed Regulations</E>
                         section of this document, the proposed regulations would:
                    </P>
                    <P>• Make technical updates to refer to up-to-date statutory authorities, remove outdated terminology, use consistent references, and eliminate obsolete cross-references.</P>
                    <P>• Align EDGAR with updates in the most recent reauthorization of the Elementary and Secondary Education Act of 1965 (ESEA). For example, updates to EDGAR would revise the tiers of evidence to incorporate and parallel those in the ESEA and would specify the procedures used to give special consideration to an application supported by evidence in § 75.226.</P>
                    <P>• Clarify, streamline, and expand the selection criteria the Secretary may use to make discretionary awards under § 75.210.</P>
                    <P>• Clarify procedural approaches, such as those related to making continuation awards under § 75.253, and exceptions to the typical process for new awards under § 75.219, such as if a grant application had been mishandled.</P>
                    <P>• Improve public access to research and evaluation related to Department-funded projects by requiring, under §§ 75.590 and 75.623, that each grantee that prepares an evaluation or a peer-reviewed scholarly publication as part of the grant award or on the basis of grant-funded research make the final evaluation report or peer-reviewed scholarly publication available through the Education Resource Information Center (ERIC), which is current practice of the Department's Institute of Education Sciences (IES).</P>
                    <P>• Expand and clarify flexibility for the Department in administering its grants programs, including by—</P>
                    <P>○ Providing the Department the option to require applicants under grant programs to include a logic model supporting their proposed project under § 75.112;</P>
                    <P>○ Replacing the definition in § 75.225 of “novice applicant” with a broader definition of “new potential grantee,” to allow additional flexibility to give special consideration to such grantees and increase equity in the applicant pool and recipients of Department funds;</P>
                    <P>○ Allowing the Department to require a grantee to conduct an independent evaluation of their project and make the results of such an evaluation public under § 75.590;</P>
                    <P>○ Defining “independent evaluation” under § 77.1(c);</P>
                    <P>○ Clarifying under § 76.50 that, where not prohibited by law, regulation, or the terms and conditions of the grant award, States have subgranting authority;</P>
                    <P>○ Allowing States flexibility under § 76.140 to adopt a process for amending a State plan that is distinct from the process used for initial approval; and</P>
                    <P>○ Clarifying the hearing and appeal process under § 76.401 for subgrants of State-administered formula grant programs, including by clarifying that aggrieved applicants must allege that a specific Federal or State statute or regulation has been violated.</P>
                    <P>• Consolidating and clarifying regulations about participation of private school children, teachers, and other educational personnel in part 299.</P>
                    <P>
                        <E T="03">Costs and Benefits:</E>
                         The Department believes that the benefits of this regulatory action would outweigh any associated costs to States, local educational agencies (LEAs), and other Department applicants and grantees. The proposed regulations would, in part, update terminology to align with applicable statutes and regulations. Many of the adjustments would support the Department, its grantees, or both, in selecting high-quality grantees and to support those grantees in ensuring the effectiveness and continuous 
                        <PRTPAGE P="1983"/>
                        improvement of their projects. These changes include, for example, adding potential selection criteria that apply only to programs that elect to use them, as announced in a notice inviting applications (NIA), and clarifying the language in selection criteria for applicants and peer reviewers. Please refer to the 
                        <E T="03">Regulatory Impact Analysis</E>
                         section of this document for a more detailed discussion of costs and benefits. Consistent with Executive Order 12866, as amended most recently by Executive Order 14094, the Secretary has determined that this action is significant and, thus, is subject to review by the Office of Management and Budget.
                    </P>
                    <P>
                        <E T="03">Incorporation by Reference:</E>
                         Proposed § 75.616 incorporates by reference the American Society of Heating, Refrigerating, and Air Conditioning Engineers (ASHRAE) Standard 90.1. ASHRAE is included in the construction section focused on energy conservation and has been included in EDGAR for over 30 years. The ASHRAE standards are the industry leading standards and are relevant to the construction regulations in this section of EDGAR because grantees need to know the current standard with which they must comply. Standard 90.1 has been a benchmark for commercial building energy codes in the United States, and a key basis for codes and standards around the world, for almost half a century. This standard provides the minimum requirements for energy-efficient design of most sites and buildings, except low-rise residential buildings. It offers, in detail, the minimum energy efficiency requirements for design and construction of new sites and buildings and their systems, new portions of buildings and their systems, and new systems and equipment in existing buildings, as well as criteria for determining compliance with these requirements. It is an indispensable reference for engineers and other professionals involved in design of buildings, sites, and building systems. This standard is available to the public at 
                        <E T="03">www.ashrae.org/technical-resources/bookstore/standard-90-1.</E>
                    </P>
                    <P>
                        Proposed § 77.1 incorporates by reference the What Works Clearinghouse (WWC) Procedures and Standards Handbook, Version 5.0. The purpose of the What Works Clearinghouse is to review and summarize the quality of existing research in educational programs, products, practices, and policies. We incorporate the Handbook, which provides a detailed description of the standards and procedures of the WWC, by reference. The Handbook is available to interested parties at 
                        <E T="03">https://ies.ed.gov/ncee/wwc/Handbooks.</E>
                         The Version 5.0 Handbook includes a new Chapter I, Overview of the What Works Clearinghouse and Its Procedures and Standards and aligns the flow of content with the study review process. Additionally, it no longer allows for topic-specific customization of the standards, aligns its effectiveness ratings with the evidence definitions in § 77.1(c), and describes other protocols for specific study designs. More details are available at 
                        <E T="03">https://ies.ed.gov/ncee/WWC/Docs/referenceresources/Final_HandbookSummary-v5-0-508.pdf.</E>
                    </P>
                    <P>The WWC is an initiative of the Department's National Center for Education Evaluation and Regional Assistance, within IES, which was established under the Education Sciences Reform Act of 2002 (Title I of Pub. L. 107-279). The WWC is an important part of the Department's strategy to use rigorous and relevant research, evaluation, and statistics to inform decisions in the field of education. The WWC provides critical assessments of scientific evidence on the effectiveness of education programs, policies, products, and practices (referred to as “interventions”) and a range of publications and tools summarizing this evidence. The WWC meets the need for credible, succinct information by reviewing research studies, assessing the quality of the research, summarizing the evidence of the effectiveness of interventions on student outcomes and other outcomes related to education, and disseminating its findings broadly.</P>
                    <P>
                        This handbook is available to the public at 
                        <E T="03">https://ies.ed.gov/ncee/wwc/handbooks#procedures.</E>
                    </P>
                    <P>
                        <E T="03">Invitation to Comment:</E>
                         We invite you to submit comments regarding these proposed regulations.
                    </P>
                    <P>The following standards appear in the amendatory text of the document and have already been approved for the locations in which they appear: What Works Clearinghouse Standards Handbook, Versions 4.0 and 4.1; What Works Clearinghouse Procedures Handbook, Versions 4.0 and 4.1; and the What Works Clearinghouse Procedures and Standards Handbook, Versions 2.1 and 3.0.</P>
                    <P>To ensure that your comments have maximum effect in developing the final regulations, we urge you to clearly identify the specific section or sections of the proposed regulations that each of your comments addresses, and to provide relevant information and data whenever possible, even if there is no specific solicitation of data and other supporting materials in the request for comment. We also urge you to arrange your comments in the same order as the proposed regulations.</P>
                    <P>We invite you to assist us in complying with the specific requirements of Executive Orders 12866, 13563, and 14094 and their overall goal of reducing the regulatory burden that might result from the proposed regulations. Please let us know of any further ways that we may reduce potential costs or increase potential benefits, while preserving the effective and efficient administration of the Department's programs and activities. We also welcome comments on any alternative approaches to the subjects addressed by the proposed regulations.</P>
                    <P>
                        During and after the comment period, you may inspect all public comments about the proposed regulations by accessing 
                        <E T="03">Regulations.gov.</E>
                         You may also inspect the comments in person. Please contact the person listed under 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         to make arrangements to inspect the comments in person.
                    </P>
                    <P>
                        <E T="03">Directed Questions:</E>
                         One of the Department's goals in these proposed regulations, in addition to helping strengthen and streamline implementation and monitoring of Department grants, is to better support continuous improvement—encouraging grantees to use research, data, community and other engagement, and other feedback to periodically review and improve their project plans to best advance their programmatic objectives. We particularly welcome comments on how these proposed regulations could best advance this goal of continuous improvement.
                    </P>
                    <P>We also specifically seek input on the proposed changes to § 75.210, which outlines the Department's general selection criteria. We carefully examined usage of these selection criteria over the years to inform the proposed changes. We also looked at how the selection criteria align with the components of a logic model, to allow peer reviewers to assess the logic model more directly, including how the pieces of the proposed project align with the intended outcomes. We seek public input on whether the proposed changes to § 75.210 would add clarity for applicants and peer reviewers and help ensure that the Department funds the highest-quality grant applications that are most likely to lead to successful projects.</P>
                    <P>
                        <E T="03">Assistance to Individuals with Disabilities in Reviewing the Rulemaking Record:</E>
                         On request, we will provide an appropriate accommodation 
                        <PRTPAGE P="1984"/>
                        or auxiliary aid to an individual with a disability who needs assistance to review the comments or other documents in the public rulemaking record for the proposed regulations. To schedule an appointment for this type of accommodation or auxiliary aid, please contact the person listed under 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                        .
                    </P>
                    <HD SOURCE="HD2">Background</HD>
                    <P>
                        In this notice of proposed rulemaking (NPRM), we propose various updates to EDGAR and related regulatory provisions. The proposed changes range from technical updates (such as removing references to the Trust Territory of the Pacific Islands, which no longer exists) to streamlining regulations (such as consolidating those concerning State plans under State-administered formula grant programs) to adding new options for grant competition requirements (such as providing the Department the option to require a logic model in any competitive grant program or to require a grantee to conduct an independent evaluation). Except for minor or technical revisions, such as updates to citations, cross-references, references to outdated programs, links, or general terminology, the proposed changes and reasons for them are explained in detail in the 
                        <E T="03">Significant Proposed Regulations</E>
                         section of this NPRM. The applicable authority for this regulatory package is section 410 of the General Education Provisions Act (GEPA) and section 414 of the Department of Education Organization Act (20 U.S.C. 1221e-3 and 3474, respectively), unless otherwise noted.
                    </P>
                    <HD SOURCE="HD1">Significant Proposed Regulations</HD>
                    <HD SOURCE="HD2">34 CFR Part 75—Direct Grant Programs</HD>
                    <HD SOURCE="HD3">Sections 75.1 and 75.200 Programs to Which Part 75 Applies and How Applications for New Grants and Cooperative Agreements Are Selected for Funding; Standards for Use of Cooperative Agreements</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.1 establishes that part 75 applies to direct grant programs of the Department. Section 75.200 further defines “direct grant programs” as either discretionary grant or formula grant programs.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         Proposed § 75.1 would combine § 75.1, and the note that follows that section, with § 75.200(a), (b)(1), and (c). Proposed § 75.1(c)(3) would specify what regulations in part 75 apply to direct grant programs, which the proposed regulation clarifies are either a discretionary grant program or a formula grant program other than a State-administered formula grant program covered by part 76. We also propose in § 75.1 to change “authorizing statute” to “applicable statutes and regulations.” We also propose deleting current § 75.200(b)(3)(ii).
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         We propose these changes to consolidate all information relevant to which programs are covered by part 75 into one regulatory provision. The changes are not substantive. We propose to change “authorizing statute” because we think the term is too narrow, as it does not include other applicable statutes, such as annual appropriations laws, that may override, modify, or supplement the “authorizing statute” without amending them. Although not reiterated throughout this preamble, we propose to make this conforming change in each applicable instance throughout the proposed regulations. Likewise, we propose to make this change in relevant instances where the term “program statute” is used. We propose deleting current § 75.200(b)(3)(ii) to remove redundancy with § 75.200(b)(3)(i).
                    </P>
                    <HD SOURCE="HD3">Section 75.4 Department Contracts</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.4 describes what regulations apply to Federal contracts and in what circumstances part 75 applies to a contract of the Department.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to remove and reserve § 75.4.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         Section 75.4 discusses contractual arrangements of the Department and when part 75 may apply to a Department contract. However, part 75 concerns the administration of the Department's direct grant programs, not contracts entered into by the Department. Additionally, § 75.4 describes requirements found in Chapters 1 and 34 of title 48 of the Code of Federal Regulations. These requirements apply to Department procurements, not Department grant programs or procurements undertaken by Department grantees. Therefore, to promote clarity and accessibility of the Department's regulations, we propose to remove § 75.4 as unnecessary and redundant given the focus on direct grants in part 75. This provision concerns the regulations that govern Federal agency contracting, not grantee contracting. We do not propose to remove any provision relevant to a grantee's contracting, and removing § 75.4 would not modify any provision related to contractual arrangements of the Department.
                    </P>
                    <HD SOURCE="HD3">Section 75.60 Individuals Ineligible To Receive Assistance</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.60 prohibits certain individuals from receiving a fellowship, scholarship, or loan from the Department if they are in default, as that term is used in 34 CFR part 668. The current section lists specific Department programs that are fellowship, scholarship, or loan programs.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         The proposed revisions to § 75.60 would delete the outdated list of programs and instead define Department programs that provide a fellowship, scholarship, or loan as being a program that offers a fellowship, scholarship, or loan “administered by the Department.”
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         Current § 75.60 lists numerous programs that no longer exist. Rather than update the list with specific references to programs that may become outdated later, we believe that reliance on a description of those programs ensures that, over the long term, the text does not become outdated. The change is not intended to be substantive.
                    </P>
                    <HD SOURCE="HD3">Section 75.101 Information in the Application Notice That Helps an Applicant Apply</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.101 describes what information the Secretary may include in an application notice, including information about the program and the application forms. Current § 75.101(a)(1) includes a description of what information an application package contains.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to revise § 75.101(a)(1) to refer more generally to the application package.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         The information described in current § 75.101(a)(1)(i) and (ii) is now included in the application notice itself and not in the application package. Therefore, we believe that removing § 75.101(a)(1)(i) and (ii) would improve the clarity of the regulations.
                    </P>
                    <HD SOURCE="HD3">Sections 75.102 and 75.104 Deadline Date for Applications and Applicants Must Meet Procedural Rules</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.102(b) provides that, if an applicant wants a new grant, the applicant must submit an application in accordance with the requirements in the application notice.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to move paragraph (b) of § 75.102 to § 75.104, where it would be added as a new paragraph (c). We also propose to revise the heading of § 75.104 to better reflect the topics covered by the regulation.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         Moving this paragraph, which concerns the requirements in application notices, from § 75.102 to § 75.104, would improve the clarity of the regulations because § 75.102 pertains to deadlines for submitting applications and § 75.104 concerns 
                        <PRTPAGE P="1985"/>
                        applicants' compliance with additional application provisions.
                    </P>
                    <HD SOURCE="HD3">Section 75.105 Annual Priorities</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.105 describes the process by which the Secretary may use annual absolute and competitive preference priorities. Current § 75.105(b)(2) describes the exceptions to publishing the annual priorities for public comment. Paragraph (b)(2)(i) describes the Department's use of invitational priorities and paragraph (b)(2)(iii) refers to the exceptions to the requirement for notice-and-comment rulemaking in section 553 of the Administrative Procedure Act (APA) (5 U.S.C. 553).
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         The proposed revisions would update the term “annual priorities” in the section title to “annual absolute, competitive preference, and invitational priorities,” and add existing exceptions to the public comment requirement in a new paragraph (b)(2)(vi). These include the exception authorized by section 437(d)(1) of GEPA (20 U.S.C. 1232(d)(1)) for the first grant competition under a new or substantially revised program authority, as well as rulemaking exceptions under specific statutes.
                    </P>
                    <P>We also propose updates to paragraphs (b)(2)(i), (iii), and (b)(2)(iv) to properly describe the exceptions to the Department's normal practice of publishing proposed priorities for notice and comment.</P>
                    <P>
                        <E T="03">Reasons:</E>
                         The Department has statutory authority to use and has used the GEPA exception for many years, and adding this exception would clarify that the regulation supplements the statutory exemption in GEPA section 437(d)(1). The exception to notice and comment rulemaking for the first grant competition under a new or substantially revised program authority is established by GEPA section 437(d)(1); therefore, this change is not substantive. In addition, we propose to add references to section 681(d) of the Individuals with Disabilities Education Act (20 U.S.C. 1481(d)), and section 191 of the Education Sciences Reform Act (20 U.S.C. 9581), both of which provide longstanding exemptions to the generally applicable requirement for the Department to conduct notice and comment rulemaking with respect to its discretionary grants.
                    </P>
                    <HD SOURCE="HD3">Section 75.109 Changes to Application; Number of Copies</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.109(a) requires each applicant that submits a paper copy of an application to submit an original and two copies to the Department.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to remove paragraph (a) of this section and revise the section heading accordingly.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         We propose to remove this paragraph because it is no longer needed. The majority of applications are now submitted electronically.
                    </P>
                    <HD SOURCE="HD3">Section 75.110 Information Regarding Performance Measurement</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.110 sets out information regarding the Secretary's authority to establish performance measurement requirements in an application notice.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         The proposed revisions would clearly differentiate between program performance measures and project-specific performance measures as well as establish requirements, to which grantees must agree, related to the quality of data and use of performance measures for continuous improvement.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         As a general matter, the Department's programs have program-level performance measures against which all grantees must report. Further, some programs also encourage or require grantees to establish project-specific performance measures. Both sets of measures are important sources of information about program and grantee performance. The current regulations do not clearly differentiate between these two types of performance measures, and these proposed revisions would make that differentiation. Additionally, it is important to ensure that applicants propose to collect and report quality data and that grantees use their performance measures to inform continuous improvement of their projects. Therefore, we propose to require assurances for quality data as part of the applications, and that the data will be used to inform the continuous improvement plan for the project.
                    </P>
                    <HD SOURCE="HD3">Section 75.112 Include a Proposed Project Period and a Timeline</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.112 requires that applications include project periods and timelines of how the applicants plan to meet each project objective.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to revise § 75.112 to allow the Secretary to include a requirement for a logic model in a particular competition, in addition to requiring a project period and a timeline.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         This change would support the development of high-quality applications, given that logic models describe the need for a project, its inputs and outputs, and the intended outcomes. Logic models are helpful tools for applicants to use when establishing timelines and resource needs. They also are helpful to the Department and reviewers in understanding the applicant's rationale for how its proposed project will achieve the project outcomes. Accordingly, adding the flexibility for programs to establish a requirement for logic models would support project planning as well as project implementation if the project is selected for funding.
                    </P>
                    <HD SOURCE="HD3">Section 75.127 Eligible Parties May Apply as a Group</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.127(b) lists some of the terms used to identify a group of eligible parties that may apply as a group for a grant. The list includes: (1) a combination of institutions of higher education; (2) a consortium; (3) joint applicants; and (4) cooperative arrangements.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose revising § 75.127(b) to include the term “partnerships.” We also propose adding a paragraph (c) stating that, in the case of a group application submitted in accordance with §§ 75.127-75.129, all parties in the group must be eligible applicants under the competition. This change would not alter the ability of applicants to form partnerships with entities that are not eligible to be recipients under a program.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         We propose this change solely for clarity. In the case of an application submitted by a group of eligible applicants, a partnership is similar to a consortium, but in some programs the former term is used instead of the latter. Also, in the context of these regulations, the term “eligible applicant” is synonymous with “eligible party,” although § 75.127(a) and (b) refer to both as “eligible parties.”
                    </P>
                    <HD SOURCE="HD3">Sections 75.190-192 Development of Curricula or Instructional Materials</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Sections 75.190, 75.191, and 75.192 describe assurances and define reasonable consultation costs when grantees develop curricula or instructional materials.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to remove §§ 75.190-75.192.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         These regulations duplicate other assurances and regulations, including the cost principles in 2 CFR part 200, subpart E, that allow consultation costs that are reasonable and necessary. In addition, we think the open licensing requirements in 2 CFR 3474.20 for Department competitive grants awarded in competitions announced after February 21, 2017, promote dissemination of materials developed with Department grant funds. 
                        <PRTPAGE P="1986"/>
                        We propose removing them to avoid unnecessary duplication, which we believe may be confusing to grantees if we duplicate certain assurances and regulations but not others.
                    </P>
                    <HD SOURCE="HD3">Section 75.201 How the Selection Criteria Will Be Used</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.201(b) provides that, if points are assigned to the selection criteria, the Secretary informs applicants in the application package or a notice published in the 
                        <E T="04">Federal Register</E>
                        . Paragraph (c) provides that, if no points or weights are assigned to the selection criteria and selected factors, the Secretary evaluates each criterion equally and, within each criterion, each factor equally.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         In § 75.201(b), we propose adding the words “or factors” after the words “selection criteria.” In paragraph (c), we propose replacing the word “and” between the words “selection criteria” and “selected factors” with the word “or.”
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         The proposed revision to paragraph (b) would clarify that the Secretary may assign specific points, either to selection criteria or to the individual factors that make up an individual selection criterion, where appropriate to guide applicants and reviewers in more effectively preparing and reviewing applications. The revision to paragraph (c) would clarify the meaning of the provision and more accurately inform applicants and reviewers of how points are allocated among selection criteria and the individual factors making up each selection criterion when points are not assigned to the criteria or the selection factors.
                    </P>
                    <HD SOURCE="HD3">Section 75.210 General Selection Criteria</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.210 lists the selection criteria and factors that the Department uses in the peer review process to score applications for discretionary grants.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose changes to paragraphs (a) through (i) of § 75.210. Throughout this section, we also propose to remove parenthetical cross-references to definitions in § 77.1(c), to improve the consistency of how we refer to those definitions throughout our regulations. This global technical change would not affect the applicability of those definitions.
                    </P>
                    <P>Specifically, the proposed regulations would make the following updates:</P>
                    <P>In paragraph (a), Need for project, as further described below, we propose clarifying in the criterion heading that it is need for “the” project. Regarding paragraph (a), Need for project, and paragraph (b), Significance, we propose a number of changes to provide greater clarity to applicants regarding the information they should provide in their applications to demonstrate the need or significance of the proposed project, including how the proposed project focuses on underserved populations, with the intent that the clarity for applicants will also provide better guidance for peer reviewers as they assess the extent to which applicants address these revised selection criteria factors. We also propose consolidation of factors where factors were similar in focus to streamline the menu of factors under the criterion.</P>
                    <P>In paragraph (c), Quality of the project design, we propose revisions to the factors that more explicitly reference and connect to a logic model, emphasizing the importance of considering the components of a logic model in relation to the design of the proposed project. We are also proposing to add three new factors regarding how the proposed project is informed by similar projects implemented by the applicant, the extent to which an applicant will allocate a significant portion of requested funding to the evidence-based components, and the commitment of key decision-makers at implementation sites for the proposed project.</P>
                    <P>In paragraph (d), Quality of project services, we propose clarifying in the criterion heading that it is the quality of “the” project services. We also propose to explicitly tie this factor to section 427 of GEPA (20 U.S.C. 1228(a)), and the related form Equity For Students, Teachers, And Other Program Beneficiaries (OMB Control No. 1894-0005), to connect an applicant's response to this form with the peer review of the application. Like Quality of the project design, proposed changes to Quality of project services reflect input from entities involved in the project, more direct connection to and engagement with the populations served by the proposed project, and the impacts of the services on those populations. We also propose a new factor related to early childhood and family outcomes, given the importance of serving young children and families effectively.</P>
                    <P>In paragraph (e), Quality of project personnel, we propose clarifying in the criterion heading that it is quality of “the” project personnel. We also propose revisions that would address how the personnel of the proposed project are representative of the population to be served by the project, including a new factor that would speak to the project team reflecting the demographics of the community to be served. Revisions also would address the relevance of experience of the project personnel with similar projects. Lastly, we propose a new factor that seeks to ensure that the project team is familiar with the assets, needs, and other contextual considerations of the proposed implementation sites.</P>
                    <P>In paragraph (f), Adequacy of resources, we propose revisions that would combine the adequacy of the resources and how those resources will support the proposed project. We also propose revisions that clarify commitments from partners, long-term sustainability and institutionalization of the project, and a new proposed factor on the reasonableness of the costs related to potential future adoption of the project.</P>
                    <P>In paragraph (g), Quality of the management plan, we propose revisions that focus on the feasibility of the project, how data will be used to inform continuous improvement, and how the management plan includes the perspectives of underserved populations for the proposed project.</P>
                    <P>In paragraph (h), Quality of the project evaluation, we propose revising the criterion heading to “Quality of the project evaluation and evidence-building.” In addition to the changes regarding the term “evidence-building,” which we propose to define in § 77.1(c), we propose revisions that would focus on the relevance of the evaluation, a focus of the evaluation on underserved populations, continuous improvement efforts and data to inform continuous improvement, revising the current factor on “promising evidence” so that it refers to the types of studies instead, differentiation of impacts for project components, and the experiences and independence of the evaluator. Lastly, we propose new factors focused on fidelity of implementation and dissemination of evidence-building learnings from the project.</P>
                    <P>In paragraph (i), Strategy to scale, we propose revisions that would clarify how the scaling work is informed by, and builds on, the project, seeks to serve underserved populations, and addresses previous barriers to impact. The revisions would allow for scaling at either the regional level or the national level and could include dissemination as well as adaptation and replication. We also propose new factors that look at how scaling efforts will target new populations or settings, the efficiencies in the project that will be incorporated into the scaling efforts, and the revenue stream to support scaling.</P>
                    <P>
                        <E T="03">Reasons:</E>
                         The proposed revisions would provide clarity, ensure technical 
                        <PRTPAGE P="1987"/>
                        and grammatical consistency, and make certain substantive changes, further described below. The menu of selection criteria and factors has expanded over the years through the various updates to EDGAR, and we closely reviewed it to determine what changes are needed. We also looked at how the existing factors were used in the various Department discretionary grant competitions to inform which factors are used frequently and which factors have rarely or never been used. For those rarely or never used, we examined whether there were other similar factors that might be used in their place, or if the language of the factor might be confusing. In some instances, we propose consolidating factors for these reasons, and, in some instances, we propose deleting the factors because they have rarely or never been used. We also sought to examine how the selection criteria can advance the Department's objectives of increasing diversity of applicants, ensuring equity in project services, and advancing usage of evidence. Clarity in the selection factors aids grant applicants' understanding and the Department's peer review and selection of grantees. The proposed changes to the selection criteria and factors under each criterion are based on lessons we have learned from using the existing selection criteria, ways to streamline the factors, and improvements to clarity. The proposed revisions seek to broaden the applicability of the factors, focus on data to inform project design and continuous improvement, demonstrate how the project and its personnel reflect the population to be served, and indicate how lessons learned from the project are incorporated into the project and plans for continued implementation and improvement after the grant period.
                    </P>
                    <P>In paragraph (a), Need for project, we propose to revise the factors to further distinguish need, including allowing the Department to request comparison data that help an applicant demonstrate their need for the project and having applicants identify gaps that the proposed project will fill. Furthermore, we propose to focus these factors to further target grant funds to individuals and populations that are underserved and lack access to services.</P>
                    <P>Like the factors under Need for project, the proposed revisions under paragraph (b), Significance, are meant to allow applicants to quantify the significance of the project, including significance beyond the individual grant project and relevance to broader educational challenges. The proposed changes are meant to provide information on contributions to the field, capacity for the project to be adopted by others in the field, and a new proposed factor (xvii) that would focus on innovative approaches to existing evidence-based project components that support efforts under some Department programs to invest and then scale innovative projects. Additional revised factors would require using knowledge from project implementation to identify effective strategies to address educational challenges, as we think it is important for applicants to plan for not just implementing a project but developing ways to share knowledge from the implementation beyond the grant project. Recognizing that the Department is not the only agency or organization that funds and supports educational efforts, we think it is important for applicants to prepare for sharing their contributions to the field, and that the field is broader than just the Department. In addition, proposed factor (iv) would more explicitly reference rehabilitative services, which would be important for grant programs under the Rehabilitation Services Administration of the Department's Office of Special Education and Rehabilitative Services.</P>
                    <P>In paragraph (c), Quality of the project design, we intend to emphasize the importance of ensuring that the project design reflects engagement of the community to be served and other relevant entities, includes a focus on continuous improvement, and relies on relevant high-quality research that informs the proposed project. These revisions are intended to strengthen a proposed project design. We also propose to add new factors: how the proposed project is informed by similar projects implemented by the applicant, the extent to which an applicant will allocate a significant portion of requested funding to the evidence-based project components, the commitment of key decision makers at implementation sites for the proposed project, and the engagement of community members and partners in the design of the proposed project. The intent of these additions is to focus on project designs that consider previous implementations, the evidence base, and the needs of the community by engaging them. Additional revisions propose the development and use of a logic model because we think that logic models establish project designs that connect the intended outcomes with the inputs and activities to support those outcomes. Current factors reference only a conceptual framework or the “demonstrates a rationale” or “promising evidence” evidence levels but do not specifically discuss a logic model, which is defined in part 77. Lastly, we propose a factor about commitments at implementation sites to address issues we have seen in grant projects for which implementation sites were named in an application, but their support was unclear and affected implementation during the project period.</P>
                    <P>In paragraph (d), Quality of project services, we propose to explicitly tie this factor to section 427 of GEPA (20 U.S.C. 1228(a)), and the related form Equity For Students, Teachers, And Other Program Beneficiaries (OMB Control No. 1894-0005), for equitable access to, and participation in, the proposed project. The intent of this alignment is to connect an applicant's responses related to equity considerations on that form to the project services proposed under the project and aligns with the form's instructions, which include a broad list of potential barriers that may impede equitable access and participation. We propose these revisions under Quality of the project service and not under Quality of project personnel, as we think the responses on the form are more relevant to the project services and the activities being carried out under the grant. Other proposed revisions to factors under Quality of project services would align with proposed changes to other selection criteria, focusing on community engagement in project services, ensuring that project services are focused on underserved populations, and the relevance of the services and the data being collected and used to inform the project services. We propose a new factor focused on the outcomes of early childhood and families to align with Department programs that focus on these populations, because these populations are currently not included in this criterion.</P>
                    <P>
                        In paragraph (e), Quality of project personnel, we propose revisions to parallel those under Quality of project services that would align the listed examples of groups that have experienced barriers between the two criteria. We also propose factors that align the qualifications of the personnel with similar projects, factors that focus project personnel on being representative of the target population for project services, and a factor to have personnel who are familiar with the needs of the implementation sites for the proposed project. The proposed revisions and new factors are intended to help ensure that personnel are positioned to meet the needs of the underserved populations to be served and more closely reflect those 
                        <PRTPAGE P="1988"/>
                        populations, including a focus on the training and experiences of the personnel that align with the work to be carried out under the proposed project.
                    </P>
                    <P>Regarding paragraph (f) Adequacy of resources, the proposed changes are intended to clarify the connection between the budget for the proposed project and how those costs are reasonable and significant, including a new factor that looks at the reasonableness of others being able to adopt and implement the project, because we are interested in the anticipated costs of broader implementation. We also propose revisions to the factor that requires applicants to address matching funds and partner commitments, which is significant given the number of program statutes that have matching requirements.</P>
                    <P>In paragraph (g), Quality of the management plan, we propose revisions to the existing factors to focus on the applicant's plan to meet goals and objectives, timelines, and budgets. Separately, we propose a revised factor to involve the use of community and partner input in the management plan, to inform continuous improvement efforts related to project implementation. Lastly, the proposed revisions to criterion (v) are meant to ensure meaningful engagement from the underserved populations to be served by the project to ensure the management plan reflects their needs.</P>
                    <P>In paragraph (h), Quality of the project evaluation, the proposed changes are intended to recognize that rigorous evaluation is not feasible for all projects; however, there are efforts relating to project goals, objectives, and performance measurement that can be used to improve the project, reach intended outcomes, and focus on evidence-building, which would be supported by the proposed definition in § 77.1(c). We also propose revising the current factor on “promising evidence” so that it refers to the types of studies instead, which we think provides greater clarity on what evaluation designs are necessary to meet the requirements of the factor.</P>
                    <P>In paragraph (i), Strategy to scale, the proposed changes focus on underserved populations. We propose two factors that would establish the level of the efforts to scale, having a separate factor for scaling to the regional level because not all projects can scale to the national level. A proposed new factor focuses scaling on new populations or settings, which is meant to get at the broader potential scaling of the proposed project. Multiple factors are meant to focus on how an applicant will address issues to scaling, including identifying and proposing strategies to address barriers to scaling, adaptions and replications to allow for scaling, and the addition of two new factors focused on the financial aspects of scaling, including efficiencies in scaling and revenue sources. All these revisions are meant to encourage applicants to more thoughtfully consider all of the aspects related to successful scaling of a project, to ensure ongoing support and growth for a project after Federal funding ends.</P>
                    <HD SOURCE="HD3">Section 75.216 Applications Not Evaluated for Funding</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.216 provides that the Secretary does not evaluate an application if: (a) The applicant is not eligible; (b) the applicant does not comply with all procedural rules that govern the submission of the application; (c) the application does not contain the information required under the program; or (d) the proposed project cannot be funded under the applicable statute and regulation or implementing regulations for the program.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to revise § 75.216 by removing paragraphs (a) and (d) and revising the section heading to read: Applications that the Secretary may choose not to evaluate for funding.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         We propose to revise this provision because the Department is bound by law to follow applicable statutes and regulations, and this change to § 75.216 would not change the rules that govern the eligible entities and types of projects that can be funded under a particular grant competition. To meet the deadlines for timely review of applications, the Department will often forward applications for evaluation to peer reviewers before making final determinations on compliance with all the requirements in § 75.216, which are often complex and time consuming. The proposed changes to § 75.216 align with current Department practice, allow the peer review process to proceed in a timely fashion, and allow final eligibility determinations to be made prior to an award being made to an applicant. For this reason, paragraphs (a) and (d) are unnecessary. In addition, the revisions to the title would clarify the Department's determinations not to evaluate an application for the reasons set forth in this regulation and codifies Department practice.
                    </P>
                    <HD SOURCE="HD3">Section 75.217 How the Secretary Selects Applications for New Grants</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Paragraph (c) of § 75.217 provides that the Secretary prepares a rank order of the applications based solely on the evaluation of their quality according to the selection criteria.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to revise paragraph (c) of § 75.217 to clarify that we may prepare multiple rank orders where we have a menu of absolute priorities that applicants must meet, as well as clarify that the rank order will also reflect any competitive preference points.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         The proposed change would provide a full description of the information relied on by the Secretary in preparing a rank order of applications under § 75.217 and codifies our current practice in § 75.217.
                    </P>
                    <HD SOURCE="HD3">Section 75.219 Exceptions to the Procedures Under § 75.217</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.219(b) excepts an application from the procedures described under § 75.217 if the application was rated highly enough to be funded but was not funded because it was mishandled.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to revise § 75.219(b)(2) and (3) to provide for situations in which an application was not selected for funding because the application was mishandled or improperly processed by the Department and an application has been rated highly enough to qualify for selection under § 75.217.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         We propose this change to improve the clarity of this provision. There have been instances in which the mishandling or improper processing of applications by the Department resulted in either an applicant not being rated or having its rating not properly recorded due to a clerical or other error. As a result, we propose changes to clarify that § 75.219(b) applies if, in the absence of the mishandling or improper processing, an application either had been rated highly enough to be funded or would have been rated highly enough to be funded had it been reviewed. When the Department discovers an application that was not reviewed due to mishandling or improper processing, it has the application reviewed and, if the score is high enough, makes an award using funds that are available when the review is conducted. This proposed change clarifies the scope of this provision and the procedures the Department follows in practice.
                    </P>
                    <HD SOURCE="HD3">Section 75.220 Procedures the Department Uses Under § 75.219(a)</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.220(b)(2) references an employee of the Office of the Chief Financial Officer (OCFO) with responsibility for grants policy to serve on a board to review an application under the special 
                        <PRTPAGE P="1989"/>
                        circumstances of § 75.219(a) (The objectives of the project cannot be achieved unless the Secretary makes the grant before the date grants can be made under the procedures in § 75.217.)
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose revising paragraph (b)(2) to refer instead to the Office of Finance and Operations (OFO).
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         In the reorganization at the Department that went into effect in January 2019, the OCFO functions were incorporated into the new OFO, and this section would be updated to reference the correct office.
                    </P>
                    <HD SOURCE="HD3">Section 75.221 Procedures the Department Uses Under § 75.219(b)</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.221 provides that, if the special circumstances of § 75.219(b) appear to exist for an application, the Secretary may select the application for funding if: the Secretary has documentary evidence that the special circumstances of § 75.219(b) exist; and (b) the Secretary has a statement that explains the circumstances of the mishandling.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to revise § 75.221 to improve its clarity and eliminate the requirement that the Secretary have a statement that explains the circumstances.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         We propose to revise the provision to improve its clarity and eliminate unnecessary language. The proposed changes would remove the requirement for an explanation of the mishandling separate from documentation of the circumstances of the mishandling. The Department does not believe that further explanation of the reasons the application was mishandled is necessary if the Secretary has documentation of the circumstances, already required under § 75.219(b).
                    </P>
                    <HD SOURCE="HD3">Section 75.522 Procedures the Department Uses Under § 75.219(c)</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.222 describes the procedures for considering an unsolicited application, including the note accompanying § 75.222 references the Application Control Center, which no longer exists.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         Proposed § 75.222 would update the mailing procedures for unsolicited applications to align with the mailing procedures discussed in the Common Instructions for Applicants to Department of Education Discretionary Grant Programs, published in the 
                        <E T="04">Federal Register</E>
                         on December 7, 2022 (87 FR 75045).
                    </P>
                    <HD SOURCE="HD3">Section 75.225 What procedures does the secretary use if the secretary decides to give special consideration to novice applications?</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.225 describes the circumstances in which the Secretary may give an absolute or competitive preference to an applicant that meets the definition of “novice applicant.” To be a “novice applicant” under current § 75.225, an applicant must have, in part: (1) never received a grant or subgrant under the program from which it seeks funds; (2) never been a member of a group application; and (3) not had an active discretionary grant from the Federal government in the last five years.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         Proposed § 75.225 would replace the term “novice applicant” with the term “new potential grantee” and provide a definition of that new term. The proposed definition includes five options from which the Department could choose to apply one or more of the conditions to a specific competition. The options of conditions for defining a new potential grantee would include: (1) an applicant that has never received a grant or cooperative agreement, including membership in a group application submitted in accordance with §§ 75.127-75.129 that received a grant, under the program from which it seeks funds; (2) an applicant that does not, as of the deadline date for submission of applications, have an active grant or cooperative agreement, including membership in a group application submitted in accordance with §§ 75.127-75.129 that received a grant, under the program from which it seeks funds; (3) an applicant that has not had an active discretionary grant or cooperative agreement, including membership in a group application submitted in accordance with §§ 75.127-75.129 that received a grant, under the program from which it seeks funds in a specified number of years before the deadline date for submission of applications under the program; (4) an applicant that has not had an active discretionary grant or cooperative agreement from the Department, including membership in a group application submitted in accordance with §§ 75.127-75.129 that received a grant, in a specified number of years before the deadline date for submission of applications under the program; or (5) an applicant that has not had an active contract from the Department in a specified number of years before the deadline date for submission of applications under the program from which it seeks funds. Based on program needs, a discretionary grant program could choose to define “new potential grantee” using one or any combination of the five options described in proposed § 75.225(a). If used, the Secretary would specify the number of years for definitions (3), (4), and (5) in the NIA by selecting from among the identified options, as described in proposed § 75.225(b). In addition, the proposed regulations would create a corresponding inverse priority for applicants that are not “new potential grantees” to be used when the Secretary creates an absolute priority for “new potential grantees” and plans to create multiple funding slates for applicants that are “new potential grantees” and those that are not. The intent is for this inverse option to be used when the “new potential grantee” priority is used as an absolute priority, and there is a need to be able to create another funding slate for those applicants that do not meet the “new potential grantee” priority.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         Since the enactment of this regulation in 2002, we have discovered that the definition of “novice applicant” is often complex and overly restrictive in practice. For instance, many of the Department's grant programs have very few, if any, eligible entities (such as institutions of higher education) that have not had other discretionary grants from the Federal government in the last five years. Despite § 75.225 being applicable to all the Department's discretionary grant programs, many programs have needed to create program-specific definitions of “novice applicant” that are tailored to their individual contexts because the vast majority of prospective applicants for our programs would not meet the current definition of “novice applicant” in § 75.225. These proposed revisions would provide the Department's programs with increased options to define “new potential grantee.” We think that these proposed revisions would allow this priority to be usable in more discretionary grant programs and more effectively promote the Department's interest in awarding grants to a more diverse and inclusive variety of applicants. Furthermore, these revisions align with the successful implementation of the “Applications from New Potential Grantees” and “Applications from Grantees that are Not New Potential Grantees” priorities from the Administrative Priorities for Discretionary Grant Programs published in the 
                        <E T="04">Federal Register</E>
                         on March 9, 2020 (85 FR 13640) (Administrative Priorities), which have worked well in allowing the Department to prioritize 
                        <PRTPAGE P="1990"/>
                        new potential grantees. We propose to add those priorities to the regulations for clarity and consistency.
                    </P>
                    <P>In the Administrative Priorities and proposed here, option (1) would apply in programs where the Department would intend to focus on applicants that have never received a grant under the program; option (2) would apply in grant competitions for which the Department would intend to prioritize “new potential grantees” without an active grant under the program; option (3) would apply in the event that a program may have multiple cohorts of grantees, and the Department would intend to define “new potential grantees” as those that have not had a grant under the program for the specified number of years; option (4) would apply when the Department would intend to be inclusive of other Department grant programs when determining “new potential grantees;” and option (5) would apply in cases when there are grant programs where an applicant may not have a Department grant but may have Department contracts and is familiar with the work of the Department already. The intent of these options is to take into consideration program specific contexts, such as the different characteristics of programs, including different types of applicants and different frequencies in which grant competitions are run.</P>
                    <HD SOURCE="HD3">Section 75.226 What procedures does the Secretary use if the Secretary decides to give special consideration to applications supported by strong, moderate, or promising evidence?</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.226 describes the Secretary's authority to give special consideration to applications supported by strong, moderate, or promising evidence.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         The proposed revision would also permit the Secretary to give special consideration to an application that “demonstrates a rationale” as defined in § 77.1(c) without disallowing evidence that may meet more than one of the four levels described in that section. We also propose removing cross-references to the definitions of “strong evidence,” “moderate evidence,” and “promising evidence” in § 77.1(c), because we do not include such cross-references elsewhere in part 75, and they are not necessary.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         While we continue to be very interested in grant projects that are supported by rigorous evidence, we recognize that the research base supporting many of our discretionary grant programs is still emerging. In addition, we think it is important to provide incentives for innovative approaches to systemic problems in education wherever possible. Adding the “demonstrates a rationale” level of evidence to § 75.226 would allow the Department to give priority to applications that meet this standard, thereby requiring or encouraging applicants to incorporate research into their project planning, where possible, while still supporting the identification of innovative solutions. This addition is also consistent with the “Applications that Demonstrate a Rationale” priority in the Administrative Priorities, which has been beneficial to achieving these objectives in discretionary grant competitions.
                    </P>
                    <HD SOURCE="HD3">Section 75.227 [Reserved]</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.227 is currently reserved.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to add a new § 75.227 that would allow the Secretary to establish a separate competition for, or provide competitive preference to, applicants that propose to serve rural locations. Specifically, the Secretary could decide to give such special consideration to applicants that can demonstrate one or more of the following: (1) the area the applicant proposes to serve is a rural LEA, (2) the area the applicant proposes to serve is a rural community, (3) the area the applicant proposes to serve is a rural school, or (4) the applicant is a rural institution of higher education. We propose to utilize rural programs authorized under ESEA as well as the locale codes from the National Center for Education Statistics School District search tool, given that there are different Federal definitions for “rural.” The proposed regulation also specifies that, if using an absolute priority related to rural applicants, the Secretary may also include an absolute priority for applicants that do not meet that priority in order to offer separate competitions, resulting in separate rank orders, for each competition.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         Rural communities face unique challenges due to their being remote, and they also have unique opportunities. These factors are reflected in many program statutes' priorities accorded to applicants that serve rural communities in many Department programs, but we believe that it is necessary that every discretionary grant program have the option to give priority to applicants that will serve rural communities. This section would enable the Department to specifically encourage applications that will provide services in rural communities. This addition would also be consistent with “Rural Applicants” and “Non-Rural Applicants” priorities in the Administrative Priorities, which have worked well to achieve these goals in discretionary grant competitions.
                    </P>
                    <HD SOURCE="HD3">Section 75.234 The Conditions of the Grant</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.234 refers to “special conditions” that the Secretary determines prior to making a grant.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         Proposed § 75.234 replaces the term “special” with the term “specific.”
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         “Specific” is the term the Department now uses, consistent with 2 CFR 200.208 to refer to conditions imposed on a grant award. The change is not substantive.
                    </P>
                    <HD SOURCE="HD3">Section 75.250 Maximum Funding Period</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.250(a) provides that the Secretary may approve a project period of up to 60 months to perform the substantive work of the grant.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to revise the heading for § 75.250 to change “funding” to “project” and propose to revise § 75.250(a) to clarify that the Secretary may approve project periods of up to 60 months unless statutory authority provides otherwise. We also propose removing § 75.250(b) because we propose a new § 75.254 to separately address data collection periods.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         We propose the change to the heading to align with the use of the term “project period” in § 75.250(a). We propose the change to § 75.250(a) to clarify that EDGAR does not supersede the applicable statutes and regulations that apply to a given program. We also propose to delete § 75.250(b) as we propose a new § 75.254 to allow for data collection periods separate from the extension of a project period.
                    </P>
                    <HD SOURCE="HD3">Section 75.253 Continuation of a Multiyear Project After the First Budget Period</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.253 describes the process and requirements for making continuation awards.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         The proposed revisions would clarify those procedures and requirements, including addition of verification of the quality data submitted, and explain that, if the Department decides not to make a continuation award, a grantee will be given an opportunity to object under 2 CFR 200.341 through a request for reconsideration. They also would explain existing Department practices that a determination by the Secretary to not make a continuation award, or to reduce the amount of a continuation 
                        <PRTPAGE P="1991"/>
                        award, to a grantee does not constitute a withholding under section 455 of GEPA (20 U.S.C. 1234d).
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         These proposed changes would reflect existing Department practices and provide a clearer description of the relevant requirements and procedural rights of grantees in the continuation awards process. In addition, these revisions would explain that a determination by the Department not to make a continuation award, or to reduce the amount of a continuation award, to a grantee does not constitute a withholding under section 455 of GEPA. That provision of GEPA deals with circumstances in which funds have already been obligated, such as a discretionary grantee that has already received a continuation award or, as is the case with a formula grant program, a grantee that is entitled to receive funds or has already received funds if it meets certain eligibility requirements. Neither of these conditions is present if the Secretary decides to not make, or to reduce, a continuation award.
                    </P>
                    <HD SOURCE="HD3">Section 75.254 [Reserved]</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.254 is currently reserved.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to add a new § 75.254 that would allow the Secretary to award a data collection period of up to 72 months after the end of the project period and provide funds for the data collection period. The proposed regulation would also set forth how the Secretary would inform applicants of this data collection period. It would further state that the Secretary may require applicants to include a budget and description for the data collection period in their applications if the data collection period is announced through the NIA.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         Currently, § 75.250 allows for a data collection period for a grant for a period of up to 72 months after the end of the project period. However, § 75.250 is not an option for those Department programs for which there is a maximum statutory performance period. Flexibility in how and for which programs the Department can allow data collection awards would give us opportunities to learn more about the impacts of our grants. Statutory limitations on project periods inhibit this longer-term data collection that could inform impacts beyond grant project periods. Furthermore, the Department operationalizes the data collection period under § 75.250 as a separate grant award and establishing a separate section in EDGAR gives the Department greater flexibility in how to use data collection awards. This section would also align with a similar priority from the Administrative Priorities, building on lessons learned from that priority, including notifying applicants in the NIA to propose a timeline that includes a data collection period.
                    </P>
                    <HD SOURCE="HD3">Section 75.261 Extension of a Project Period</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.261 describes when grant project periods may be extended and under what conditions a grantee may receive a project period extension.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         Proposed § 75.261 would clarify that there are two types of project period extensions: (1) a one-time extension of up to 12 months without prior approval if the requirements in 2 CFR 200.308(e)(2) are met and there are no applicable statutes, regulations, or grant conditions prohibiting such an extension; and (2) an additional extension beyond the 12 months with prior approval of the Secretary, if certain other conditions are met. The proposed revision also would remove references to specific technical assistance centers in current paragraph (b) that no longer exist, correct citations, and align language to be consistent with the Uniform Administrative Requirements, Cost Principles, and Audit Requirements (the Uniform Guidance) for Federal Awards in 2 CFR part 200, as adopted and amended as regulations of the Department in 2 CFR part 3474.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         The regulation, as currently written, includes numerous revisions made over the years and is now in need of streamlining, and contains outdated references and citation errors. These proposed changes would promote greater clarity and accessibility for the public regarding project period extensions. The proposed changes are not substantive.
                    </P>
                    <HD SOURCE="HD3">Section 75.263 Pre-Award Costs; Waiver of Approval</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.263 describes when pre-award costs may be incurred.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         Proposed § 75.263 would remove the clause “notwithstanding any requirement in 2 CFR part 200.”
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         The language we propose to remove is not necessary to establish that the requirements of 2 CFR part 200 apply; removing it would add clarity to the regulation. The proposed change is not substantive.
                    </P>
                    <HD SOURCE="HD3">Section 75.519 Dual Compensation of Staff</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.519 prohibits paying for project staff who are compensated from another source of funds.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         Proposed § 75.519 would add a reference to the cost principles described in 2 CFR part 200, subpart E—Cost Principles.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         The reference we propose to add provides the source for the prohibition discussed in § 75.519. The change is not substantive.
                    </P>
                    <HD SOURCE="HD3">Sections 75.560-75.564 Indirect Cost Rates</HD>
                    <P>
                        <E T="03">Current Regulations:</E>
                         Sections 75.560-75.564 describe the application of indirect costs under discretionary grant programs, including who approves indirect costs rates and how they are applied.
                    </P>
                    <P>
                        <E T="03">Proposed Regulations:</E>
                         The proposed revisions would align these sections of EDGAR with the Uniform Guidance in 2 CFR part 200, include cost allocation plans along with indirect costs rates, and provide clarity on the application of indirect cost rates.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         The Uniform Guidance sets out requirements that apply to Federal grants and was adopted by the Department in 2 CFR part 3474. The Uniform Guidance, in conjunction with EDGAR, governs Department grants and therefore these provisions should be closely aligned with one another. These sections of EDGAR do not reflect recent updates to the Uniform Guidance, including the addition of the de minimis rate, referencing cost allocation plans as performing a role equivalent to indirect costs rate, and clarifications on restricted rates, and this alignment is necessary to ensure that there is no confusion. Moreover, the proposed changes are intended to add clarity regarding how indirect cost rates are applied, as well as the indirect cost rate options an entity has.
                    </P>
                    <HD SOURCE="HD3">Section 75.590 Evaluation by the Grantee</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.590 describes what grantees must demonstrate or provide to the Department regarding performance reporting and the evaluation of their projects.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         The proposed revision would add a new paragraph (c) that would permit the Department to include a requirement for an independent evaluation in any grant competition, for the results of that evaluation to be made public, including the option to make the data available to third-party researchers, and for the results of that evaluation or a grantee final report to be submitted to ERIC, which is administered by IES.
                        <PRTPAGE P="1992"/>
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         We want to have more tools available to build, use, and disseminate rigorous evidence more effectively. Requiring grantees to conduct independent evaluations, where appropriate, would help increase the credibility of their project evaluations because the entity conducting the evaluation would have no vested interest in the outcome of the evaluation. An independent evaluation to assess the implementation or impact of a project or project component has the potential to build the evidence base through the work of competitive program grantees, and the sharing of data with third-party researchers allows for additional data analysis. Submitting evaluations and the final performance reports under grants to ERIC can help identify emerging evidence and promote further research.
                    </P>
                    <HD SOURCE="HD3">Section 75.591 Federal Evaluation—Cooperation by a Grantee</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.591 requires grantees to cooperate in the Department's efforts to evaluate the program supporting their project.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to clarify the types of activities that grantees could be expected to undertake as part of their participation in a Federal program evaluation.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         Although the current regulation makes it clear that grantees must cooperate with the Secretary's evaluation of the program, it does not provide potential applicants information about what that cooperation might entail. The proposed regulation would provide increased transparency about the types of activities in which a grantee may be required to participate. For example, a grantee may be required to participate in a randomized controlled trial conducted by the Department, and we think that it is important to provide clarity, where possible, on grantee expectations under the regulation.
                    </P>
                    <HD SOURCE="HD3">Section 75.600-75.617 Construction</HD>
                    <P>
                        <E T="03">Current Regulations:</E>
                         Sections 75.600-75.617 cover various regulations related to construction projects and the acquisition of real property.
                    </P>
                    <P>
                        <E T="03">Propose Regulation:</E>
                         We propose to amend certain regulations related to construction projects and real property acquisition in parts 75, 76, and 77. The proposed changes to parts 76 and 77 are addressed in more detail in the applicable sections of this preamble.
                    </P>
                    <P>Specifically, the proposed changes include the following:</P>
                    <P>• A reorganization of §§ 75.600-75.614 for a more logical progression of the statutory and regulatory requirements at each stage of the construction project. The proposed regulations are organized to progress through all the stages of a construction project, through Department approval (§ 75.601), planning the project (§ 75.602), beginning the project (§ 75.603), during the project (§ 75.604), and after the project (§ 75.605).</P>
                    <P>• Clarifying that the Secretary considers a grantee's compliance with specific statutes and regulations related to construction prior to approval of the construction project (proposed § 75.602(c)).</P>
                    <P>• Adding specific provisions regarding real property acquisition that, in part, incorporate requirements from existing governmentwide assurances, including nondiscrimination assurances (proposed § 75.606). These provisions mirror the construction provisions in proposed § 75.601 to clarify that real property projects must also receive Department approval.</P>
                    <P>• Incorporating, and updating, as appropriate, applicable cross references to the Uniform Guidance and other applicable law in the various stages of the construction project in various sections of the regulations.</P>
                    <P>• Moving and consolidating the requirements currently in §§ 75.607-75.608 into proposed § 75.602. We do not propose any substantive changes to the current requirements in § 75.607 or § 75.608.</P>
                    <P>• Decreasing the period for which the grantee must retain title to the site from 50 years to 25 years in proposed § 75.610.</P>
                    <P>• Clarifying the requirements of the National Environmental Policy Act of 1969 (NEPA) (proposed § 75.611). This section would not create a requirement, but rather provide additional guidance that the NEPA requirements apply to “major Federal projects” as defined by NEPA.</P>
                    <P>• Moving the requirements of § 75.611 (Avoidance of flood hazards) and § 75.617 (Compliance with the Coastal Barrier Resources Act) to proposed § 75.612 and § 75.613, respectively. We do not propose any substantive changes to the current requirements in § 75.611 or § 75.617.</P>
                    <P>• Clarifying the process and roles of the Secretary and State reviewing a construction project involving historic preservation (proposed §§ 75.614 and 76.600). We do not propose any substantive changes to the current requirements in § 75.602.</P>
                    <P>• Adding the applicability of the new Build America, Buy America Act to construction projects (proposed § 75.615). This section explains that a grantee must comply with the requirements of the Build America, Buy America Act, Public Law 117-58, § 70901-70927 and implementing regulations in 2 CFR part 184.</P>
                    <P>• Updating the requirements of § 75.616 (Energy conservation) to require compliance with the most current ASHRAE standards. The current regulation requires compliance with standards from 1975, 1977, and 1980, respectively.</P>
                    <P>• Moving the requirements of § 75.610 (Access by the handicapped) to proposed § 75.617 and updating the title to “Access for individuals with disabilities.” We do not propose any substantive changes to the current requirements in § 75.610.</P>
                    <P>• Moving and consolidating the requirements currently in § 75.609 (Comply with safety and health standards) into proposed § 75.618. We do not propose any substantive changes to the current requirements in § 75.609.</P>
                    <P>
                        <E T="03">Reasons:</E>
                         The purpose of these proposed changes is to update the current construction regulations in response to statutory changes and related issues that have arisen over the last thirty years, as many of the regulations for this section have not been updated since 1992; to better align the regulations to the Uniform Guidance that was first promulgated in 2014 and updated in 2020; and to improve clarity and transparency regarding Federal program operations. The Department proposes to decrease the period in proposed § 75.610 because we found that grantees with site leases had difficulty establishing that they had an option to extend their lease for 50 years. Rather, we propose to reduce to 25 years or the useful life of the construction, which we think more closely aligns with the Federal investment. We also propose to update these regulations to include the requirements grantees must follow during construction projects under the Build America, Buy America Act, Pub. L. 117-58, § 70901-70927. The Build America, Buy America Act was enacted as part of the overall Infrastructure Investment and Jobs Act in November 2021. The purpose of the Build America, Buy America Act is to create demand for domestically produced goods, helping to sustain and grow domestic manufacturing.
                    </P>
                    <HD SOURCE="HD3">Section 75.618 Charges for Use of Equipment or Supplies</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.618 states that a grantee may not charge for ordinary use of equipment or supplies.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to repurpose § 75.618 for use under the Construction subheading and move the current § 75.618 to currently unused 
                        <PRTPAGE P="1993"/>
                        § 75.619. We do not propose any changes to the text of this section.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         To create space for an additional section under the Construction heading regarding safety and health standards, we propose to move current § 75.618 to § 75.619.
                    </P>
                    <HD SOURCE="HD3">Section 75.620 General Conditions on Publication</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.620(b) includes the text of a statement that grantees must include in any publication that contains project materials.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         The proposed revision would update the required statement with current and more comprehensive language, including current forms of publication, such as on a website or a web page.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         The statement was last updated in 1980. Since then, Federal Government endorsement disclaimers, including the one in § 75.620(b), have evolved to be more comprehensive. We propose updating the statement to mirror the standard disclaimer used by the Department in other contexts, such as what the Department may require on work products developed by Department contractors. In addition, methods of publication have changed since 1980, to include websites and web pages.
                    </P>
                    <HD SOURCE="HD3">Section 75.623 Public Availability of Grant-Supported Research Articles</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         None.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to add a new § 75.623 to require each grantee that prepares a peer-reviewed scholarly publication as part of its grant award or based on grant-funded research to make the publication available to the public by submitting the final peer-reviewed scholarly publication to ERIC. To support § 75.620, we also propose to add a definition of “peer-reviewed scholarly publication” under § 77.1(c).
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         This section would align the practice of the entire Department with the current practice of IES, which requires all its grantees to make their peer-reviewed publications available to the public in this manner. Currently, these materials are exempt from the open licensing requirements in 2 CFR 3474.20. Applying the requirement in this section to peer-reviewed publications produced under grants made by other offices in the Department is in line with the Department's Plan and Policy Development Guidance for Public Access,
                        <SU>1</SU>
                        <FTREF/>
                         with the Office of Science and Technology Policy's memorandum, Increasing Access to the Results of Federally Funded Research,
                        <SU>2</SU>
                        <FTREF/>
                         and would ensure that the results of grant-funded research are available to a wider array of Department partners and other interested parties than is currently the case.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             The Department's Plan and Policy Development Guidance for Public Access is available at 
                            <E T="03">https://ies.ed.gov/funding/pdf/EDPlanPolicyDevelopmentGuidanceforPublicAccess.pdf.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2</SU>
                             The Office of Science and Technology Policy's memorandum is available at 
                            <E T="03">https://obamawhitehouse.archives.gov/sites/default/files/microsites/ostp/ostp_public_access_memo_2013.pdf.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Section 75.700 Compliance With the U.S. Constitution, Statutes, Regulations, Stated Institutional Policies, and Applications</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.700 states that grantees shall comply with and uses Federal funds in accordance with applicable statutes, regulations, and approved applications.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to revise § 75.700 to include Executive orders in addition to statutes, regulations, and approved applications.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         We propose this revision to align § 75.700 to § 75.708, which includes the requirement for subgrantees to comply with Executive orders.
                    </P>
                    <HD SOURCE="HD3">Section 75.708 Subgrants</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.708(b) states that the Secretary may, through an announcement in the 
                        <E T="04">Federal Register</E>
                        , authorize subgrants when necessary to meet the purposes of a program, and paragraph (e) states that grantees may contract for supplies, equipment, construction, and other services.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to revise paragraph (b) to state that this authorization may take place “through an announcement in the 
                        <E T="04">Federal Register</E>
                         or other reasonable means of notice.” We propose to revise paragraph (e) to clarify that, when subgrants are not allowed, grantees are still authorized to contract, as needed, for supplies, equipment, and other services.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         There may be circumstances in which 
                        <E T="04">Federal Register</E>
                         notification is not the most efficient or effective way for the Secretary to authorize subgrants. To account for these situations, we propose adding more flexibility to the current regulation. We also propose to clarify when and how contracts for supplies, equipment, and other services can be used when subgrants are not allowed.
                    </P>
                    <HD SOURCE="HD3">Section 75.720 Financial and Performance Reports</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.720 sets out the financial and performance reporting requirements that grantees must meet.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to add a new paragraph (d) that would require grantees to publish, on a public-facing website, the reports they submit to the Secretary under § 75.720 upon request of the Secretary. Under this new paragraph, the Secretary could choose which grant competitions would be subject to this requirement. The Department expects that any such publication on a public-facing website would be consistent with applicable accessibility requirements and in accordance with privacy laws.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         This requirement would increase transparency with respect to grantee performance and provide useful information on the effectiveness of projects supported by Department grant funds to grantee participants and beneficiaries as well as the general public.
                    </P>
                    <HD SOURCE="HD3">Section 75.901 Suspension and Termination</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 75.901 indicates that the Secretary may use the Office of Administrative Law Judges (OALJ) to resolve disputes concerning a variety of matters that are not subject to other proceedings.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to revise the introductory language to this regulation by removing the following words: “that are not subject to other procedures.”
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         This proposed change would clarify the authority of the Secretary to use the OALJ to resolve disputes on the matters identified in § 75.901(a)-(f).
                    </P>
                    <HD SOURCE="HD2">Part 76 State-Administered Programs</HD>
                    <HD SOURCE="HD3">Section 76.1 Programs to Which Part 76 Applies</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 76.1 describes the programs to which part 76 applies. Paragraph (a) of § 76.1 references “each State-administered program” while paragraph (b) references “a State formula grant program.”
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to revise the language in both paragraphs to clarify that part 76 applies to “State-administered formula grant programs.” We also propose to make conforming changes, as necessary, throughout this part, including the title for this part.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         Inconsistent use of terms within part 76 could create confusion about its applicability. These updates would clarify that all provisions of part 
                        <PRTPAGE P="1994"/>
                        76 apply only to “State-administered formula grant programs.”
                    </P>
                    <HD SOURCE="HD3">Section 76.50 Statutes Determine Eligibility and Whether Subgrants Are Made</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 76.50 describes the circumstances in which the Secretary makes a grant to a State agency, either as directed by the applicable statute and regulation or as designated by the State consistent with the applicable statute and regulation. The regulation states explicitly that the applicable statute determines the extent to which a State may use grant funds itself or make subgrants. Regarding subgrants, § 76.50(c) states that the regulations in part 76 on subgrants apply to a program only if subgrants are authorized under that program, and paragraph (d) states that the applicable statute determines an applicant's eligibility for a subgrant.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to modify § 76.50 in six general ways. First, we propose to change the heading to read “Basic Requirements for Subgrants.” Second, we propose to add references to a State-administered formula grant program's regulations throughout. Third, we propose to make clear in new paragraph (b) that States may make subgrants using funds from State-administered formula grant programs unless prohibited by their authorizing statutes, implementing regulations, or the terms and conditions of their awards. Fourth, we propose to delete paragraphs (c) on how other requirements in part 76 apply to subgrants and (d), which was a previous statement about entities eligible for subgrants, and to incorporate essential requirements into new paragraph (b). Fifth, we propose to add a new paragraph (c) to explicitly identify grantee responsibility for subgrantee monitoring consistent with 2 CFR 200.332. Finally, we propose to add a new paragraph (d) to clarify that subgranting prohibitions under which Department programs operate should not be construed as prohibiting grantees from entering into contracts for goods or services in accordance with 2 CFR part 200, subpart D—Post Federal Award Requirements (2 CFR 200.317-200.326).
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         We propose to modify this section to ensure that State-administered formula grant programs have maximum flexibility to make subgrants. To that end, we propose to revise the heading to signal to States that subgrants are allowed, unless specifically prohibited by statute, regulation, or the terms and conditions of a grant award. Under the current regulations, some State-administered formula grant programs have interpreted statutory silence as meaning that subgranting is not permissible. We believe that the proposed regulations would address this unintended consequence through the changes proposed to the heading and to new paragraph (b). However, we may prohibit subgranting under the terms and conditions of a grant award, as appropriate, such as when subgranting would be counter to fundamental statutory or regulatory requirements for a program. We also propose to refer to both applicable statutes and regulations throughout the provision, rather than just statutes, in case the applicable regulations provide necessary clarification. We propose to remove current paragraph (b) because it does not provide any guidance that is not already provided in a program's authorizing statute. We propose to incorporate essential requirements from paragraphs (c) and (d) into new paragraph (b). As a result, we propose to delete current paragraphs (c) and (d) as no longer necessary. We propose to add new paragraph (c) to highlight grantee responsibilities for monitoring subgrantees to encourage fiscal responsibility, transparency, and appropriate control of taxpayer funds. We propose to add a new paragraph (d) to clarify that, regardless of the authority to subgrant, a grantee is authorized to contract for supplies, equipment, and other services in accordance with 2 CFR part 200, subpart D—Post Federal Award Requirements (2 CFR 200.317-200.326.
                    </P>
                    <HD SOURCE="HD3">Section 76.101 The General State Application</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 76.101 requires a State that makes subgrants to LEAs under a program subject to this part to have on file with the Secretary a State plan that meets the requirements of section 441 of GEPA (20 U.S.C. 1232d).
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to revise § 76.101 to make clear that the requirements of section 441 of GEPA do not apply to a State plan submitted for a program under the ESEA.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         Section 8304(b) of the ESEA (20 U.S.C. 7844(b)) states that the requirements of section 441 of GEPA do not apply to State plans under the ESEA. The purpose of this change is to align the regulations with that statutory provision.
                    </P>
                    <HD SOURCE="HD3">Section 76.102 Definition of State Plan for Part 76</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 76.102 includes a table specifying applications or other documents required under various State-administered formula grant programs that, for the purpose of part 76, are considered “State plans.”
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to remove the table from § 76.102 and to describe a State plan, as that term is used in part 76, as “any document that the applicable statutes and regulations for a State-administered formula grant program require a State to submit in order to receive funds for the program.” To the extent that any provision of part 76 conflicts with program-specific implementing regulations related to the plan, the program-specific implementing regulations govern.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         Current § 76.102 includes a table intended to list all programs that are covered by the State plan regulations in part 76. However, some of the listed programs no longer exist. Other programs have been renamed under a reauthorized statute. Rather than update the table of programs, given that programs may become outdated in the future, we believe that a definition aligned with governing statutes and regulations would be the best way to convey the intended scope of the provision. In addition, the proposed regulations would make clear that, if any provision of part 76 conflicts with program-specific implementing regulations related to the plan, the program-specific implementing regulations govern.
                    </P>
                    <HD SOURCE="HD3">Section 76.103 Multi-Year State Plans</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 76.103 makes clear that a State plan will be effective for a period of more than one fiscal year, to be determined by the Secretary or by regulations. It authorizes the Secretary to stagger submission of State plans and identifies numerous programs to which the section does not apply.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to simplify § 76.103 by deleting the list of programs to which the provision does not apply. Instead, we would make clear that a State plan may be effective for more than one year unless otherwise specified by statute, regulation, or the Secretary. In addition, we remove the note at the end of this section.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         All the programs listed in § 76.103(c) have been reauthorized or repealed since the provision was promulgated in 1980. Rather than listing other programs that could become outdated, we would add language that affords flexibility for a multiyear State plan unless a statute, regulation, or the Secretary specifies otherwise. We also propose to remove the note at the end of this section because it is outdated and no longer needed.
                        <PRTPAGE P="1995"/>
                    </P>
                    <HD SOURCE="HD3">Sections 76.125-76.137 Consolidated Grant Applications for Insular Areas</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         The Department's consolidated grant authority regulations in part 76, as well as in the definitions of “State” in §§ 77.1(c) and 79.2, refer to the Trust Territory of the Pacific Islands. In addition, § 76.125(c) states that the Secretary may make annual consolidated grants to assist an Insular Area in carrying out a Department State-administered formula grant program. The following sections then refer to programs listed in § 76.125 as being eligible for consolidation.
                    </P>
                    <P>
                        <E T="03">Proposed Regulations:</E>
                         We propose to update the regulations to remove all references to the Trust Territory of the Pacific Islands. In addition, the proposed regulations would revise § 76.125(c) to clarify that grantees may consolidate grants only if not otherwise prohibited from doing so by applicable law. Also, we propose to change all references in the following sections from “programs listed in § 76.125(c)” to “State-administered formula grant programs.” We also propose to revise the examples in §§ 76.128 and 76.129 to update the statutory references, and to make conforming changes to remove the term “Trust Territory of the Pacific Islands,” from the definitions of “State” in §§ 77.1(c) and 79.2.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         The Trust Territory of the Pacific Islands was a United Nations trust territory administered by the United States from 1947 to 1986. During the latter part of that time, it was eligible for Department program funding and services much like the Outlying Areas of American Samoa, the Commonwealth of the Northern Mariana Islands, Guam, and the U.S. Virgin Islands. For that reason, it was included, in EDGAR, in the Department's consolidated grant authority regulations as well as in the EDGAR definitions of “State” in §§ 77.1(c) and 79.2.
                    </P>
                    <P>The trusteeship ended in 1986 and from it emerged the Federated States of Micronesia, the Republic of the Marshall Islands, and the Republic of Palau (collectively, the Freely Associated States). While the Freely Associated States still have a special relationship with the United States and each of them receives certain funds through the Department, as provided in their Compacts of Free Association with the United States, they do not receive funds as part of the Trust Territory of the Pacific Islands, which no longer exists. On this point, as a purely technical matter, we propose to delete the outdated reference to the Trust Territory of the Pacific Islands.</P>
                    <P>The change to § 76.125(c) would clarify that consolidation may take place only in a manner that is consistent with applicable law. For clarity, we propose to update references elsewhere to § 76.125(c) to refer directly to “State-administered formula grant programs.”</P>
                    <HD SOURCE="HD3">Sections 76.140-76.142 State Plan Amendments</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 76.140 requires a State to amend its State plan if the Secretary determines that an amendment is essential or if there is a significant and relevant change regarding the plan. Section 76.141 requires a State to use the same procedures when amending its State plan as it did when submitting the plan to the Secretary. Section 76.142 requires the Secretary to use the same procedures to approve an amendment as the Secretary used when reviewing and approving the initial State plan.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to remove duplicate language in § 76.140(b) regarding when an amendment is needed. New proposed paragraph (c) would incorporate current § 76.141 with revisions that would allow the Secretary to prescribe different procedures for a State to amend its State plan based on the characteristics of a particular State-administered formula grant program. We propose to remove §§ 76.141-76.142.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         The current regulations, in § 76.140(b), go into greater detail than necessary about the kinds of changes that result in an amendment; the proposed regulations would simplify and clarify the regulations by stating that a State must submit an amendment whenever there is a significant and relevant change in information or assurances in the State plan. The language in current § 76.140(b)(2) and (b)(3) could be included in the general “information” in the State plan and thus we propose combining the provisions in proposed § 76.140(b)(1). Current §§ 76.141-76.142 are overly prescriptive in requiring States and the Secretary to use the same process for submitting and approving amendments as they used when submitting and approving an initial State plan. Those processes may be burdensome and may not always be appropriate for an amendment to a State plan. We propose to remove current § 76.141 and add a new paragraph (c) to § 76.140, which seeks to provide flexibility so that the Secretary may prescribe different procedures for States to use based on the specific State-administered formula grant program. The proposed regulations would also remove the requirement in current § 76.142 that the Secretary follow the same procedures when approving an amendment as the Secretary used to approve the initial State plan in order to allow the Secretary discretion to streamline the approval of amendments.
                    </P>
                    <HD SOURCE="HD3">Section 76.301 Local Educational Agency Application in General</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 76.301 requires an LEA that applies for a subgrant under a program subject to part 76 to have on file with the State an application that meets the requirements of section 442 of GEPA (20 U.S.C. 1232e).
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to make clear that the requirements of section 442 of GEPA do not apply to an LEA application for a program under the ESEA.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         Section 8306(b) of the ESEA (20 U.S.C. 7846(b)) states that the requirements of section 442 of GEPA do not apply to LEA plans under the ESEA. We propose this change to align the regulation with the statute.
                    </P>
                    <HD SOURCE="HD3">Section 76.401 Disapproval of an Application—Opportunity for a Hearing</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 76.401 sets forth the requirements that a state educational agency (SEA) must meet when disapproving an application for a subgrant in one of the Department's covered State-administered formula grant programs, which are identified in a table in the regulations. The regulation restates the requirements in section 432 of GEPA (20 U.S.C. 1231b-2), including the due process an SEA must provide to an applicant for a subgrant before (or after, in some cases) the SEA either: (1) disapproves or fails to approve a subgrant application in whole or in part; or (2) fails to provide funds in amounts in accordance with the requirements of laws and regulations. Section 76.401 also reiterates the statutory requirements for the relevant timelines, the right of an applicant to appeal an SEA's final decision disapproving an application or failing to provide funds in the required amount to the Secretary, and the standard of review that the Secretary must apply in considering such an appeal. Section 76.401 is silent regarding the information that must be included in a notice of appeal submitted to the Secretary. Under § 76.401(b), the requirements for providing an opportunity for a hearing before disapproving a subgrant application do not apply to a State agency other than an SEA.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to revise the regulation in current § 76.401 in several respects by:
                        <PRTPAGE P="1996"/>
                    </P>
                    <P>(1) Removing the table of programs and clarifying that the requirements apply to State-administered formula grant programs administered by an SEA in which the SEA makes subgrants.</P>
                    <P>(2) Clarifying that an applicant must include a citation to the alleged violation of a Federal or State statute, rule, regulation, or guideline governing the applicable program and a brief description of the alleged violation when it requests that the SEA hold a hearing on the application disapproval.</P>
                    <P>(3) Requiring a notice of appeal to the Secretary submitted pursuant to section 432(b) of GEPA to include, at a minimum, a citation to the specific Federal statute, rule, regulation, or guideline that an SEA allegedly violated and a brief description of the alleged violation.</P>
                    <P>(4) Deleting an opportunity for a hearing if an SEA fails to provide funds in amounts required by statutes and regulations because § 76.401 applies only to disapproval of an application for a subgrant. Rather, the requirement that an SEA hold a hearing, upon request of a subgrantee, when the SEA fails to provide funds in accordance with applicable statutes and regulations would be added to § 76.783(a)(3), which describes other circumstances in which a subgrantee may request that an SEA hold a hearing that meets the procedural requirements in § 76.401.</P>
                    <P>(5) Making numerous other changes to eliminate duplicate provisions.</P>
                    <P>
                        <E T="03">Reasons:</E>
                         For several reasons, described below, we propose to clarify that a notice of appeal to the Secretary must cite the specific Federal statute, rule, regulation, or guideline the appellant believes the SEA's final decision violates and provide a brief description of the alleged violation. For the same reasons, we are also proposing to clarify that an applicant's request to an SEA for a hearing must provide a brief description of the alleged violation of Federal or State statute, rule, regulation, or guideline governing the applicable program.
                    </P>
                    <P>Section 432 of GEPA affords a subgrantee that is aggrieved by the final action of an SEA in disapproving or failing to approve its application for funds the right to request that the SEA conduct a hearing and, upon receiving an adverse final decision, to appeal the SEA's decision to the Secretary. This section applies only to SEAs. In some programs, the authorizing statute may require that a particular State agency be the sole State agency to administer the approved State plan, such as the Independent Living Services for Older Individuals Who are Blind program in section 752(a)(2) of the Rehabilitation Act of 1973 (29 U.S.C. 796k(a)(2)). This program requires that the sole State agency to administer the approved State plan be the State Vocational Rehabilitation Services agency that provides services to individuals who are blind in the State. Even if that State agency is located within an SEA, if it is the other State agency designated by statute that is the only agency authorized to take the final action in disapproving or failing to approve a subgrantee's application for funds, then it is not the SEA that is taking the final action within the meaning of § 76.401, and this section does not apply to that program.</P>
                    <P>These due process protections contemplate that an SEA has violated a Federal or State statute, rule, regulation, or guideline governing the applicable program. Clarifying that a notice of appeal to the Secretary must cite the specific Federal statute, rule, regulation, or guideline that the SEA allegedly violated will help to ensure that an appeal subject to GEPA and the procedures described in § 76.401 is about a violation of Federal law, consistent with GEPA, and not solely a disagreement with the SEA's substantive decision. The GEPA appeal rights apply only when an SEA allegedly violates Federal law and, so, it follows that a GEPA appeal must, at a minimum, allege such a violation.</P>
                    <P>In the past few years, the Department received numerous GEPA appeals that were without merit; these appeals often came from applicants whose applications were not selected for funding pursuant to a discretionary subgrant competition. In a large portion of these appeals, the primary argument that the appellant made was that it disagreed with the SEA's assessment of its application. This argument is insufficient as a matter of law in a GEPA appeal because it does not allege that the SEA's final decision was contrary to Federal laws, rules, regulations, or guidelines. Even so, currently, when such an appeal is filed, the appeal is fully briefed, reviewed, and adjudicated before the Secretary issues a final decision denying the appeal, thereby tying up SEA and Department resources for an extended period.</P>
                    <P>Under our proposed revisions to § 76.401(d)(3), the Secretary would be able to dismiss an appeal immediately upon receipt of a notice of appeal if it is apparent on the face of the notice that it fails to allege a violation of Federal statutes, rules, regulations, or guidelines governing the applicable program. The Secretary would, as a matter of practice, prior to dismissing a GEPA appeal, first request that the appellant show cause for why the appeal should not be dismissed and permit the appellant to revise its notice of appeal to include the specific Federal statute, rule, regulation, or guideline the appellant alleges the SEA violated. By asking that the appellant show cause prior to dismissing the appeal, the Secretary would not cause undue harm to appellants unrepresented by legal counsel who submit their appeals on their own behalf and might have omitted the specific Federal statute, rule, regulation, or guideline the appellant alleges the SEA violated from the initial version of the appeal. Absent the appellant's ability to show cause, however, the appeal would be dismissed, thereby limiting GEPA appeals to those that fall under the Secretary's authority under section 432 of GEPA: those that allege a violation of Federal law, rule, regulation, or guideline governing the applicable program.</P>
                    <P>The proposed regulations would also make changes to clarify, streamline, and delete duplicative information. For example, current § 76.401 includes a table of programs to which the section applies. Some programs listed no longer exist. Other programs have been renamed under a reauthorized statute. Rather than update the table of programs, which may become outdated, we believe that clarifying that the procedures described in the section apply only to an applicant that is aggrieved by the final action of an SEA with respect to disapproving or failing to approve its application for funds under a State-administered formula grant program ensures that, over the long term, the text does not become outdated. Additionally, we propose to move the requirements with respect to a subgrantee's allegation that an SEA failed to provide funds in amounts in accordance with the requirements of applicable statutes and regulations to § 76.783(a)(3). Section 76.401 is about disapproval of an application, and it is, therefore, more logical to include the “failing to provide funds” provision in § 76.783, which describes other circumstances in section 432 of GEPA in which a subgrantee may request a hearing and, ultimately, appeal to the Secretary. This does not change the procedural requirements that apply when a subgrantee alleges that an SEA failed to provide funds in amounts prescribed by law.</P>
                    <P>
                        The other changes in proposed § 76.401 are for consistency and clarity.
                        <PRTPAGE P="1997"/>
                    </P>
                    <HD SOURCE="HD3">Section 76.560-76.569 Indirect Cost Rates</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Sections 76.560-76.569 describe the application of indirect costs under State-administered formula grant programs, including who approves indirect costs rates and how they are applied.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         The Uniform Guidance, in conjunction with EDGAR, governs Department grants and, therefore, these provisions should be closely aligned with one another. The proposed revisions would align these sections of EDGAR with the Uniform Guidance, include cost allocation plans along with indirect costs rates, and provide clarity on the application of indirect cost rates, as well as the addition of § 76.562, specific to reimbursement of indirect costs.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         These sections of EDGAR currently do not reflect updates to the Uniform Guidance, including the addition of the de minimis rate, referencing cost allocation plans as performing a role equivalent to indirect costs rate, and clarifications on restricted rates and this alignment is necessary to ensure that there is no confusion about these requirements. Moreover, the proposed changes are intended to add clarity to how indirect cost rates are applied, the indirect cost rate options an entity has, and reimbursement of indirect costs.
                    </P>
                    <HD SOURCE="HD3">Section 76.600 Where To Find Construction Regulations</HD>
                    <P>
                        <E T="03">Current Regulations:</E>
                         Section 76.600 provides section references to the EDGAR regulations on construction.
                    </P>
                    <P>
                        <E T="03">Propose Regulation:</E>
                         We propose to amend certain regulations related to construction projects and real property acquisition in parts 75, 76, and 77. Specifically for § 76.600, the proposed regulations would update citations to align with the proposed revision in part 75.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         The purpose of these proposed changes is to update the current regulations in response to statutory changes and related issues that have arisen, as many of the regulations for this section have not been updated since 1992; to better align the regulations to the Uniform Guidance; and to improve clarity and transparency regarding Federal program operations. The proposed changes would also update the citations to the regulations on construction in part 75 and set out the State's responsibilities when approving construction projects.
                    </P>
                    <HD SOURCE="HD3">Section 76.650-76.662 Participation of Students Enrolled in Private Schools</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Sections 76.650-76.662 include general requirements applicable to State-administered formula grant programs that require a grantee or subgrantee to provide for participation by students enrolled in private schools.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to amend section 76.650 and remove §§ 76.651-76.662. As a result, we also propose updates to § 75.119, which cross-references § 76.656, and § 75.650, which cross-references §§ 76.650-76.662. In addition, we propose to delete § 299.6(c), which provides that §§ 76.650-76.662 do not apply to the programs covered under § 299.6(b).
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         Sections 76.650-76.662 are currently unchanged since they were issued in 1980. Since then, applicable statutory requirements have changed, and the Department has issued program-specific regulations regarding the provision of services to private school children, teachers and other educational personnel, and families. These include the following regulations: (1) 34 CFR 200.62-200.68, applicable to the provision of equitable services under part A of Title I of the ESEA; (2) §§ 299.6-299.10, applicable to equitable services for programs subject to the requirements in section 8501 of the ESEA; and (3) 34 CFR 300.130-300.144, applicable to equitable services under part B of the Individuals with Disabilities Education Act (IDEA). Therefore, we propose to remove §§ 76.651-76.662 because they are unnecessary, redundant, and, in some instances, inconsistent with current law. We propose to amend § 76.650 to reference §§ 299.7-299.11 to cover any State-administered formula grant program that requires the provision of services to private school children, teachers and other educational personnel, and families and that is not otherwise governed by applicable regulations. We believe that this approach would ensure greater alignment across programs and reduce the potential for confusion. These proposed changes are for clarity and would not substantively affect the services and assistance available to private school students, educators, or families.
                    </P>
                    <HD SOURCE="HD3">Section 76.665 Providing Equitable Services to Students and Teachers in Non-Public Schools</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 76.665 applies to providing equitable services to children and teachers in non-public schools under the CARES Act. It was necessary because equitable services under the CARES Act were not governed by the provisions in part 299.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to delete § 76.665.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         Section 76.665 is no longer needed because funds under the CARES Act are no longer available for obligation. Moreover, the regulations on determining the proportional share under § 76.665(b) have been invalidated by several United States district courts (see, 
                        <E T="03">e.g., Michigan</E>
                         v. 
                        <E T="03">DeVos,</E>
                         481 F.Supp.3d 984 (N.D. Cal. 2020) and 
                        <E T="03">Washington</E>
                         v. 
                        <E T="03">DeVos,</E>
                         481 F.Supp.3d 1184 (W.D. Wash. 2020)).
                    </P>
                    <HD SOURCE="HD3">Sections 76.670-76.677 Procedures for Bypass</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Sections 76.670-76.677 establish procedural requirements applicable to programs under which the Secretary is authorized to waive requirements for providing services to private school children and implement a bypass under which the Department assumes responsibility for providing those services.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to remove §§ 76.670-76.677 and add §§ 299.18-299.28 in a new subpart G of part 299 and amend the requirements to reflect statutory changes.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         Currently, the Secretary is authorized to implement a bypass only under ESEA State-administered formula grant programs and part B of the IDEA. With respect to part B of the IDEA, the Department has established program-specific regulations applicable to a bypass. Because the current bypass regulations in §§ 76.670-76.677 apply only to applicable ESEA State-administered formula grant programs, it is appropriate to remove these requirements from part 76, which applies to more than the ESEA, and add similar provisions as §§ 299.18-299.28 of part 299, which establishes uniform administrative rules for ESEA programs. We describe §§ 299.18-299.28 elsewhere in this document.
                    </P>
                    <HD SOURCE="HD3">Section 76.783 State Educational Agency Action—Subgrantee's Opportunity for a Hearing</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 76.783 requires an SEA to provide a subgrantee an opportunity for a hearing under certain circumstances. With respect to an SEA, the regulation cross-references § 76.401, which restates the requirements from section 432 of GEPA, including the due process an SEA must provide to subgrantees if the SEA either: (1) orders the repayment of misspent or misapplied Federal funds; or (2) terminates further assistance for an approved project.
                        <PRTPAGE P="1998"/>
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         The proposed regulation would add to § 76.783 the requirement currently in § 76.401 that an SEA hold a hearing, upon request of a subgrantee, when the SEA fails to provide funds in amounts in accordance with the requirements of statutes, rules, regulations, or guidelines.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         The proposed regulation would move the requirements with respect to a subgrantee's allegation that an SEA failed to provide funds in amounts in accordance with the requirements of statutes, rules, regulations, and guidelines from § 76.401 to § 76.783. Section 76.401 is about disapproval of an application, and it is, therefore, more logical to include the “failing to provide funds” provision in § 76.783, which describes other circumstances under section 432 of GEPA in which a subgrantee of an SEA may request a hearing and, ultimately, appeal to the Secretary. This provision does not change the procedural requirements that apply when an SEA is alleged to have failed to provide funds in amounts prescribed by law; rather, it moves the requirement to a more relevant section of this part.
                    </P>
                    <HD SOURCE="HD2">Part 77 Definitions That Apply to Department Regulations</HD>
                    <HD SOURCE="HD3">Section 77.1 Definitions That Apply to All Department Programs</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 77.1 includes a number of definitions, including a definition of “direct grant program,” which is referred to in § 75.1. The regulation also includes definitions of “Director of the Institute of Museum Services,” “Director of the National Institute of Education,” and “State,” definitions related to evidence, and definitions about the scope of a project. The current definition of “evidence-based” applies to both direct grant programs administered under part 75 and State-administered formula grant programs administered under part 76. These definitions support the various sections in EDGAR and are used by the Department in NIAs where relevant to the specific grant competition.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to remove the definitions of “direct grant program” and “Director of the Institute of Museum Services.” In addition, we propose technical updates to the following definitions: “demonstrates a rationale,” “Director of the National Institute of Education,” and “evidence-based.” Specifically, we propose limiting the definition of “evidence-based” to only direct grant programs administered under part 75, to align with the interpretation that underlying authorizing statutes are the source for the definition of “evidence-based” for formula grant programs. We propose technical updates to the cross-references in section 77.1(b) as a result of changes to the Uniform Guidance. We propose additional updates to the definitions of “moderate evidence,” “national level,” “performance period,” “promising evidence,” “regional level”, “strong evidence,” and “What Works Clearinghouse Handbooks.” We propose to add definitions of “construction,” “evaluation,” “evidence-building,” “independent evaluation,” and “minor remodeling,” “peer-reviewed scholarly publication,” and “quality data.”
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                    </P>
                    <HD SOURCE="HD1">Definitions of Direct Grant Program and Director of the National Institute of Education</HD>
                    <P>We propose to remove the definition of “direct grant program,” because it applies only to part 75 and the proposed regulations would define it in § 75.1. Although a technical change, we propose to replace the definition of “Director of the National Institute of Education” with a definition of “Director of the Institute of Education Sciences” due to a statutory change in the name of that position, enacted in 2002.</P>
                    <HD SOURCE="HD1">Definitions of National Level and Regional Level</HD>
                    <P>We propose revising the definitions of “national level” and “regional level” to replace the phrase “process, product, strategy, or practice” in these two definitions with the term “project component” because “project component” is already defined and would provide more clarity.</P>
                    <HD SOURCE="HD1">Definition of Project Period</HD>
                    <P>We propose clarifying, in the definition of “performance period,” that the “period during which funds can be obligated” is specific to grantees and not the Department.</P>
                    <HD SOURCE="HD1">Evidence-Related Definitions</HD>
                    <P>We propose expanding the definitions of “moderate evidence,” “promising evidence,” and “strong evidence,” and the references to evidence levels for practice guides, effectiveness ratings for intervention reports, studies and samples in intervention reports to correspond with the designations on the What Works Clearinghouse website and in Version 5.0 of the What Works Clearinghouse Handbooks. We also propose to update the definition of “What Works Clearinghouse Handbooks” to incorporate by reference these updated standards.</P>
                    <P>
                        Additionally, we propose to modify the definition of “moderate evidence” to allow, for example, high-quality studies of low-incidence populations to meet the standard in the context of a systematic review. The new definition of “construction” would give meaning to a term used in multiple sections in parts 75 and 76, and is meant to add clarity, as well as the proposed definition of “minor remodeling” that is meant to help distinguish it from construction. The new definition of “evaluation,” a term used in various sections and especially in § 75.210, would clarify and provide a shared understanding of what is meant when this term is used. The new definition of “evidence-building,” a term used in § 75.210, would support the Department's efforts to ensure learning from funded grants where rigorous evaluation is not appropriate but feedback and continuous improvement efforts are better suited. The new definition of “quality data,” as referenced in section 515 of the Treasury and General Government Appropriations Act, 2001 (Appendix C of Public Law 106-554) (commonly known as the “Information Quality Act”) and further defined in the Department's Information Quality Act Guidelines (
                        <E T="03">www2.ed.gov/policy/gen/guid/iq/iqg.html</E>
                        ), would support the Department's ongoing effort to improve the data that the Department receives from applicants and grantees by ensuring data encompass utility, objectivity, and integrity of the information. The new definition of “independent evaluation,” a term used in § 75.590, would support the Department's ongoing effort to increase the quality and credibility of the project evaluations supported by competitive grant programs through evaluations conducted independently from project developers and implementers. As discussed in greater detail in the section regarding §§ 76.125-76.137, the revised definition of “State” would remove the reference to the Trust Territory of the Pacific Islands. The revisions to the other definitions listed above would clarify the regulations and align with statutory language.
                    </P>
                    <HD SOURCE="HD1">Definition of Evidence-Based</HD>
                    <P>
                        State-administered formula grant programs administered under part 76 have their own statutory definitions of “evidence-based” and limiting the scope of this definition to part 75 will help ensure that the regulatory and statutory definitions of “evidence-based” do not conflict.
                        <PRTPAGE P="1999"/>
                    </P>
                    <HD SOURCE="HD1">Definitions of Construction and Minor Remodeling</HD>
                    <P>We propose adding a definition of “construction” and revising the definition of “minor remodeling” under § 77.1(c). This proposed definition of “construction” is modeled after the definition of “construction” in the Impact Aid program regulations (34 CFR 222.176(a) “Construction”). The Department has found that it is important to define “construction” to distinguish construction activity from “minor remodeling”, a term already defined in § 77.1(c), as there has been confusion about what activities are considered construction, and which are considered minor remodeling. We propose to revise the term “minor remodeling” to more clearly indicate that minor remodeling is not considered “construction” under the proposed definition.</P>
                    <HD SOURCE="HD1">Definition of Peer-Reviewed Scholarly Publication</HD>
                    <P>We propose adding a definition of “peer-reviewed scholarly publication” to support the use of this term in § 75.620. This definition is intended to clarify that research is made available in a variety of formats, and that research funded by the Department that is submitted for publication in scholarly publications should also be made available for free by submission to ERIC.</P>
                    <HD SOURCE="HD2">34 CFR Part 79—Intergovernmental Review of Department of Education Programs and Activities</HD>
                    <HD SOURCE="HD3">Section 79.1-79.8 Intergovernmental Review</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Part 79 discusses the requirements related to intergovernmental review of Department programs and activities.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to remove from §§ 79.1, 79.3, 79.4, and 79.8 references to Section 401 of the Intergovernmental Cooperation Act of 1968 and Section 204 of the Demonstration Cities and Metropolitan Development Act of 1966, which are outdated.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         Section 401 of the Intergovernmental Cooperation Act of 1968 and Section 204 of the Demonstration Cities and Metropolitan Development Act of 1966 are outdated, and we therefore propose to remove them from these sections.
                    </P>
                    <HD SOURCE="HD2">34 CFR Part 299—General Provisions</HD>
                    <HD SOURCE="HD3">Section 299.7</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         None.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to add a new § 299.7 to incorporate the requirements in ESEA section 8501 for consultation with private school officials for programs that require the provision of equitable services to private school children, teachers, and other educational personnel.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         This section would reflect the requirements for consultation with private school officials for programs that require the provision of equitable services to private school children, teachers, and other educational personnel. The addition of a section on consultation is consistent with the current regulations on Title I equitable services in § 200.63. This section would also clarify the requirements in section 8501(c)(1)(H) of the ESEA, which reference the number of children from low-income families in a participating public school attendance area who attend private schools. This language is the same as a similar provision in section 1117(b)(1)(J) of the ESEA, which applies to equitable services under Title I, part A, but is not applicable to equitable services under other covered programs because participation in equitable services under these other programs is not limited to children from low-income families who live in a Title I participating public school attendance area.
                    </P>
                    <HD SOURCE="HD2">34 CFR Part 299—General Provisions</HD>
                    <HD SOURCE="HD3">Section 299.8</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 76.660, which elsewhere in this document we propose to remove, contains information about the context in which a subgrantee may use program funds to pay for the services of an employee of a private school.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to add a new § 299.8 to incorporate the information articulated in § 76.660, which we propose elsewhere in this document to remove. Proposed § 299.8 would note that, in providing for the participation of students in private schools, a grantee or subgrantee may use program funds to pay a private school employee if the employee performs services outside of his or her regular hours of duty and under public supervision and control. While § 76.660 refers only to subgrantees, the proposed § 299.8 would also clarify that a grantee, in addition to a subgrantee, may pay for services of private school personnel if the relevant conditions are met.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         Incorporating this provision in part 299 would consolidate regulations related to the participation of private school students and teachers in part 299 and clarify that the same approach applies whether a grantee or subgrantee is providing services to students enrolled in private schools.
                    </P>
                    <HD SOURCE="HD3">Section 299.16 What must an SEA include in its written resolution of a complaint?</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         None.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to add a new § 299.16 to require that an SEA's written resolution of a complaint from an organization or individual alleging violation of a Federal statute or regulation that applies to an applicable program include specific elements.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         This section would add clarity regarding the contents of an SEA's written resolution of a complaint to help ensure that the resolution includes relevant information and is clear, concise, and understandable to the parties involved. This would also help facilitate the Department's timely review and resolution of any appeal of an SEA's written resolution of a complaint, particularly within the context of equitable services appeals that require the Department to investigate and resolve an appeal within 90 days of receipt.
                    </P>
                    <HD SOURCE="HD3">Section 299.17 What must a party seeking to appeal an SEA's written resolution of a complaint include in its appeal request?</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         None.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to add a new § 299.17 to require that certain elements be included in a party's appeal of an SEA's written resolution of a complaint.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         This section would clarify what must be included in an appeal in order to facilitate the Department's timely review and resolution of the appeal, particularly within the context of equitable services appeals that require the Department to investigate and resolve an appeal within 90 days of receipt.
                    </P>
                    <HD SOURCE="HD3">Section 299.18 When are bypass provisions applicable?</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         None.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         We propose to add a new § 299.18, which would incorporate part of current § 76.670(a), which elsewhere in this document we propose to remove. Section 299.18 would clarify those applicable ESEA programs under which the Secretary is authorized to waive the requirements for providing equitable services to private school children, teachers, and other educational personnel (hereafter, for ease of reference, “private school children”) and implement a bypass.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         Because current § 76.670(a) applies only to ESEA programs under which the Secretary is authorized to waive the requirements for providing equitable services to private school 
                        <PRTPAGE P="2000"/>
                        children and implement a bypass, we propose to move this section to a new subpart G of part 299, which would contain other requirements regarding the provision of equitable services to private school children. Proposed § 299.18 would delete the list of applicable programs contained in current § 76.670(a) because that list is out of date.
                    </P>
                    <HD SOURCE="HD3">Section 299.19 Bypass—General</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         None.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         Proposed § 299.19 would state the statutory standards that authorize the Secretary to implement a bypass.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         We propose to add § 299.19 to clarify the circumstances in which the Secretary is authorized to waive the requirements for providing equitable services to private school children and implement a bypass.
                    </P>
                    <HD SOURCE="HD3">Section 299.20 How To Request a Bypass</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         None.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         Proposed § 299.20 would clarify the circumstances in which a private school official or an agency, consortium, or entity, as applicable, may request a bypass.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         Sections 1117(b)(6)(C) and 8501(c)(6)(C) of the ESEA contain provisions added by the Every Student Succeeds Act that require an SEA to provide equitable services directly or through a contract with a public or private agency, organization, or institution if an appropriate private school official has requested that the SEA provide those services and demonstrated that an agency, consortium, or entity has not met the requirements of section 1117 or 8501, as applicable. If an SEA determines that it is appropriate to provide equitable services itself, a bypass request to the Secretary would be unnecessary. Accordingly, proposed § 299.20(a) would clarify that an appropriate private school official may request a bypass from the Secretary if an SEA declines to provide equitable services itself following a private school official's request or if the failure to provide equitable services is by an SEA. Proposed § 299.20(b) would clarify that such a request may also be made if an agency, consortium, or entity is prohibited by law from providing equitable services.
                    </P>
                    <HD SOURCE="HD3">Section 299.21 Notice of Intent To Implement a Bypass</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 76.671 contains notice procedures that the Secretary uses prior to implementing a bypass, which elsewhere in this document we propose to remove.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         Proposed § 299.21 contains notice provisions essentially identical to those in current § 76.671, with a few edits to conform language to section 8504 of the ESEA.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         We propose to remove current § 76.671 and include its substance in proposed § 299.21 in new Subpart G of part 299, which contains other provisions regarding the provision of equitable services to private school children.
                    </P>
                    <HD SOURCE="HD3">Section 299.22 Filing Requirements</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Section 76.670(b) contains filing requirements to request that the Secretary implement a bypass, which elsewhere in this document we propose to remove.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         Proposed § 299.22 contains filing requirements similar to those in current § 76.670(b).
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         We propose to remove current § 76.670(b) and include its substance in proposed § 299.22 in new Subpart G of part 299, with changes to replace references to facsimile transmission with references to electronic mail.
                    </P>
                    <HD SOURCE="HD3">Sections 299.23 Through 299.28 Bypass Determination Process</HD>
                    <P>
                        <E T="03">Current Regulation:</E>
                         Sections 76.672-76.677, which elsewhere in this document we propose to remove, contain procedures for implementing a bypass.
                    </P>
                    <P>
                        <E T="03">Proposed Regulation:</E>
                         Proposed §§ 299.23-299.28 are essentially identical to §§ 76.672-76.677, with a few edits to conform to section 8504 of the ESEA.
                    </P>
                    <P>
                        <E T="03">Reasons:</E>
                         We propose to remove current §§ 76.672-76.677 and include their substance, with minor edits, in proposed §§ 299.23-299.28 in new subpart G of part 299, which contains other regulations regarding the provision of equitable services to private school children.
                    </P>
                    <HD SOURCE="HD1">Executive Orders 12866, 13563, and 14094</HD>
                    <HD SOURCE="HD1">Regulatory Impact Analysis</HD>
                    <P>Under Executive Order 12866, the Office of Management and Budget (OMB) must determine whether this regulatory action is “significant” and, therefore, subject to the requirements of the Executive order and subject to review by OMB. Section 3(f) of Executive Order 12866, as amended by Executive Order 14094, defines a “significant regulatory action” as an action likely to result in a rule that may—</P>
                    <P>(1) Have an annual effect on the economy of $200 million or more (as of 2022 but adjusted every 3 years by the Administrator of the Office of Information and Regulatory Affairs (OIRA) of OMB for changes in gross domestic product), 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, territorial, or Tribal governments;</P>
                    <P>(2) Create a serious inconsistency or otherwise interfere with an action taken or planned by another agency;</P>
                    <P>(3) Materially alter the budgetary impacts of entitlements, grants, user fees, or loan programs or the rights and obligations of recipients thereof; or</P>
                    <P>(4) Raise legal or policy issues for which centralized review would meaningfully further the President's priorities, or the principles stated in the Executive order, as specifically authorized in a timely manner by the Administrator of OIRA in each case.</P>
                    <P>This proposed regulatory action is a significant regulatory action subject to review by OMB under section 3(f)(4) of Executive Order 12866, as amended by Executive Order 14094. Notwithstanding this determination, we have assessed the potential costs and benefits, both quantitative and qualitative, of this proposed regulatory action and have determined that the benefits would justify the costs.</P>
                    <P>We have also reviewed these proposed regulations under Executive Order 13563, which supplements and explicitly reaffirms the principles, structures, and definitions governing regulatory review established in Executive Order 12866. To the extent permitted by law, Executive Order 13563 requires that an agency—</P>
                    <P>(1) Propose or adopt regulations only on a reasoned determination that their benefits justify their costs (recognizing that some benefits and costs are difficult to quantify);</P>
                    <P>(2) Tailor its regulations to impose the least burden on society, consistent with obtaining regulatory objectives and taking into account—among other things and to the extent practicable—the costs of cumulative regulations;</P>
                    <P>(3) In choosing among alternative regulatory approaches, select those approaches that maximize net benefits (including potential economic, environmental, public health and safety, and other advantages; distributive impacts; and equity);</P>
                    <P>
                        (4) To the extent feasible, specify performance objectives, rather than the behavior or manner of compliance a regulated entity must adopt; and
                        <PRTPAGE P="2001"/>
                    </P>
                    <P>(5) Identify and assess available alternatives to direct regulation, including economic incentives—such as user fees or marketable permits—to encourage the desired behavior, or provide information that enables the public to make choices.</P>
                    <P>Executive Order 13563 also requires an agency “to use the best available techniques to quantify anticipated present and future benefits and costs as accurately as possible.” OIRA has emphasized that these techniques may include “identifying changing future compliance costs that might result from technological innovation or anticipated behavioral changes.”</P>
                    <P>We are issuing these proposed regulations only on a reasoned determination that their benefits justify their costs. In choosing among alternative regulatory approaches, we selected those approaches that maximize net benefits. Based on an analysis of anticipated costs and benefits, we believe that these proposed regulations are consistent with the principles in Executive Order 13563.</P>
                    <P>We also have determined that this regulatory action would not unduly interfere with State, local, and Tribal governments in the exercise of their governmental functions.</P>
                    <HD SOURCE="HD2">Potential Costs and Benefits</HD>
                    <P>We have reviewed the changes proposed in this NPRM in accordance with Executive Order 12866, as amended by Executive Order 14094, and do not believe that these changes would generate a considerable increase in burden. In total, we estimate that the proposed changes in this NPRM would result in a net decrease in burden of approximately $4,000 with transfers of between $109.7 and $113.8 million. Most of the changes proposed in this NPRM are technical in nature and are unlikely to affect the administration of programs or allocation of benefits in any substantial way. However, given the large number of edits proposed herein, we discuss each provision, other than those for which we are updating citations or cross-references and making other technical edits, and its likely costs and benefits in turn below.</P>
                    <P>Proposed changes to §§ 75.1 and 75.200 would simply combine currently existing text into a single section and clarify terms used. We do not expect that these changes will have any quantifiable cost, and it may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>The proposed deletion of § 75.4 as unnecessary and redundant is unlikely to generate any quantifiable cost and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>Proposed changes to § 75.60, which would delete an outdated table and clarify a definition, are unlikely to generate any quantifiable cost and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>Proposed changes to § 75.101 are unlikely to generate any meaningful cost and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>Proposed changes to §§ 75.102 and 75.104, which would move paragraph (b) of § 75.102 to § 75.104, are unlikely to generate any quantifiable costs and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>Proposed changes to § 75.105, which add reference to an already existing exemption to the public comment period to the regulations, are unlikely to generate any quantifiable costs and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>Proposed changes to § 75.109, which would eliminate the requirement that an applicant submit two copies of any paper applications in addition to the original, may reduce costs for applicants that submit paper applications. However, those savings are likely to be minimal, given the small incremental cost of photocopies and the low number of paper applications the Department receives in any year. At most, we estimate that it would save applicants $7.50 per application, assuming a 75-page application photocopied at a rate of $0.05 per page. Assuming an average of 50 paper applications submitted per year, this change would result in an annual savings of approximately $375.</P>
                    <P>Proposed changes to § 75.110, which would more clearly specify how applicants must report against program measures and project-specific performance measures, are unlikely to generate any quantifiable costs and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>Proposed changes to § 75.112, which would allow the Secretary to require applicants to submit a logic model, are unlikely to generate any quantifiable costs or benefits. Many grant competitions already include this requirement and, to the extent that it is included in additional competitions in the future, we do not believe that it would create a substantial burden for applicants, because we assume that applicants in those programs would likely already have conceptualized an implicit logic model for their applications and, therefore, would experience only minimal paperwork burden associated with memorializing it in their applications.</P>
                    <P>Proposed changes to § 75.127, which would add the term “partnership” and clarify that all members of a group application must be eligible entities, are unlikely to generate any quantifiable costs and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>The proposed deletion of §§ 75.190-75.192 as duplicative is unlikely to generate any quantifiable costs and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>Proposed changes to § 75.201, which refer to selection “factors,” as well as “criteria” are unlikely to generate any quantifiable costs and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>Proposed changes to § 75.210, which would clarify word choice and make updates to language based on past experience in using the current selection criteria and factors, are unlikely to generate any quantifiable costs and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>Proposed changes to § 75.216, which would remove paragraphs (a) and (d) and revise the section heading, are unlikely to generate any quantifiable costs and may benefit the Department and general public by improving the clarity of the regulations and providing the Department additional flexibility in considering applications.</P>
                    <P>Proposed changes to § 75.217, which would remove the word “solely” and add “and any competitive preference points,” are unlikely to generate any quantifiable costs and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>Proposed changes to § 75.219, which would reorganize the section to improve clarity, are unlikely to generate any quantifiable costs and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>Proposed changes to § 75.221, which would revise the section to improve clarity and remove unnecessary language, are unlikely to generate any quantifiable costs and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>
                        Proposed changes to § 75.222, which would update the mailing address for unsolicited applications, are unlikely to generate any quantifiable costs and may benefit the Department and general 
                        <PRTPAGE P="2002"/>
                        public by improving the clarity of the regulations.
                    </P>
                    <P>The proposed change to § 75.225 would change the current term “novice applicant” to “new potential grantee” and revise the definition to provide greater flexibility to the Department in classifying applicants as “new potential grantees.” We believe that this proposed regulation may result in a number of changes in the behavior of both Department staff and applicants. First, we believe that the additional flexibility in the new definition will increase the number of competitions in which § 75.225 is used. Second, we believe that it may result in additional applicants submitting applications for competitions in which § 75.225 is used. Finally, we believe that the additional applicants, in conjunction with any absolute or competitive preference associated with the revised section, may shift at least some of the Department's grants among eligible entities. However, because this revised standard would neither expand nor restrict the universe of eligible entities for any Department grant program, and since application submission and participation in our discretionary grant programs is completely voluntary, we do not think that it would be appropriate to characterize any increased participation in our grant competitions as costs associated with this regulation.</P>
                    <P>Proposed changes to § 75.226, which would provide the Secretary with the authority to give special consideration to an application that demonstrates a rationale, are unlikely to generate any quantifiable costs or benefits. Many grant competitions already ask applicants to discuss the extent to which they can demonstrate a rationale for their proposed projects through a selection factor and, to the extent that it is included in additional competitions in the future, we do not believe that it would create a substantial burden for applicants, because we assume that applicants in those programs would likely already have conceptualized an implicit logic model for their applications and would, therefore, experience only minimal paperwork burden associated with memorializing it in their applications.</P>
                    <P>Proposed changes to § 75.227 would give the Secretary the authority to give special consideration to rural applicants. The proposed language in this section mirrors language adopted by the Department in the Administrative Priorities. As such, these proposed changes will not generate any quantifiable costs and may benefit the Department and general public by improving the clarity and transparency of the Department's authority to provide special consideration to particular applicants.</P>
                    <P>Proposed changes to § 75.234, which would replace the word “special” with the word “specific,” are unlikely to generate any quantifiable costs and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>Proposed changes to § 75.250, which would update the heading and would clarify that an extension of the project period is authorized by EDGAR only if the applicable statutes and regulations permit it, are unlikely to generate any quantifiable costs and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>Proposed changes to § 75.253, which would allow a grantee whose request for a non-competitive continuation award has been denied to request reconsideration, could generate costs to affected grantees and the Department. In general, we do not deny a large number of non-competing continuation awards and, if that does happen, grantees are often aware of the likelihood of the decision well in advance and often cite no concerns if they do not receive a continuation award. Therefore, we do not believe that many grantees would qualify for the redress, and we do not believe that the few who may qualify would exercise the right. However, for the purpose of this analysis, we assume that we would process 10 such requests annually—which we believe is an overestimate of the likely incidence. For each request, we assume a project director earning $106.76 per hour, on average, would spend 24 hours drafting and submitting the request. At the Department, a program officer at the GS-13/1 level ($61.96 per hour) would spend approximately 8 hours reviewing each request, along with 2 hours for their supervisor at the GS-14/1 level ($72.69 per hour) to review. We also assume that a Department attorney ($72.69 per hour) would spend approximately 4 hours reviewing each request. In sum, we estimate that this provision would generate an additional cost of approximately $25,622 for grantees and $9,320 for the Department per year.</P>
                    <P>The proposed addition of a new § 75.254 would give the Secretary the authority to approve data collection periods. The proposed language in this section is aligned with this previous authority under § 75.250(b) as well the Administrative Priorities. As such, these proposed changes will not generate any quantifiable costs and may benefit the Department and general public by allowing for data collection periods that give grantees additional time to collection data to measure project impact.</P>
                    <P>Proposed changes to § 75.261, which would remove references to obsolete programs and make other edits, are unlikely to generate any quantifiable costs and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>Proposed changes to § 75.263, which would remove the clause “notwithstanding any requirement in 2 CFR part 200,” are unlikely to generate any quantifiable costs and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>Proposed changes to §§ 75.560-75.564, which align these sections with the Uniform Guidance and provide additional information on the application of indirect cost rates, are unlikely to generate any quantifiable costs and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>
                        Proposed changes to § 75.590, which would allow the Department to require the use of an independent evaluation in a program, would likely generate transfers for affected grantees. Specifically, we assume that grantees that are required to use an independent evaluator will transfer grant funds from their currently designated purpose (such as to defray the costs of an internal evaluation) to pay for an independent evaluation. We note, however, that we do not believe that these transfers would substantially affect the level of support that beneficiaries of our competitive grant programs receive; the grantees would have spent a certain percentage of their awards on evaluation, whether such evaluation is conducted by an internal or external entity. We believe that the most likely programs in which the Department would require an independent evaluation are those that include an expectation of a rigorous evaluation using selection factors related to What Works Clearinghouse evidence standards in project evaluations. From 2014 through 2022, we included such selection factors in 18 competitions (excluding programs that have their own independent evaluation requirements, such as Education Innovation and Research and its predecessor, Investing in Innovation, because these programs are already included in the baseline), with a combined average of $194.8 million in awards per year. Assuming that evaluation costs in these programs average approximately 15 percent of total project costs, we estimate that the evaluations for these competitions would cost approximately $29,227,000 
                        <PRTPAGE P="2003"/>
                        per year. Assuming equal-sized cohorts of new grants per year, we estimate that this total would increase through Year 5, when it would plateau at $146,135,000 per year. To the extent that grantees already use evaluators that would meet the requirements for an independent evaluation, this would represent an overestimate of the transfers associated with this provision.
                    </P>
                    <P>Proposed changes to § 75.591, which clarify how grantees cooperate with Federal research activities, are unlikely to generate any quantifiable costs and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>Proposed changes to §§ 75.600-75.615 and §§ 75.618-75.619 would restructure the sections on construction to improve the flow of the information, as well as update citations, are unlikely to generate any quantifiable costs and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>Proposed changes to § 75.620, which would update language regarding Federal endorsement, are unlikely to generate any quantifiable costs and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>The proposed addition of § 75.623 would require certain grantees to submit final versions of Department-funded research publications to ERIC so that they are publicly available. Given that submission of the files would be a required grant activity, we do not anticipate that the requirement generating any additional costs for grantees. To the extent that submission did generate additional burdens, they would likely be minimal and would be properly considered transfers from support of other grant-related activities. Such transfers would be de minimis. Further, the addition of this requirement would generate benefits for the general public by increasing the availability of publicly supported research.</P>
                    <P>Proposed changes to § 75.700, which would add Executive orders to the list of authorities with which grantees must comply, are unlikely to generate any quantifiable costs and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>
                        Proposed changes to § 75.708, which would allow the Secretary to provide notice authorizing subgrants through the 
                        <E T="04">Federal Register</E>
                         or another reasonable means, may generate minimal efficiency returns to the Department by reducing burdens and costs associated with preparing a notice for publication in the 
                        <E T="04">Federal Register</E>
                        . However, we estimate that staff time to draft and compile these notices will likely remain unchanged and, therefore, do not estimate any changes in burden associated with this provision.
                    </P>
                    <P>Proposed changes to § 75.720 would allow the Secretary to require grantees to publish their annual performance reports on a public-facing website. Given that this requirement would apply only to a subset of discretionary competitive grant programs and participation in such programs is voluntary, we do not estimate any costs associated with this proposed change. However, we believe that, to the extent that the requirement results in a shift in activities by grantees, it is possible that there would be minimal transfers. We estimate that it would take a web developer approximately 30 minutes to post a copy of the grantee's annual performance report on the website. Assuming that a loaded wage rate is $57.05 per hour for web developers, we estimate that this requirement could generate approximately $29 per year per affected grantee. In FY 2020, the Department made approximately 7,700 grants. Assuming this requirement would be used in 20 percent of those grants, we estimate total transfers of approximately $43,930 per year.</P>
                    <P>Proposed changes to § 76.1, which would ensure consistent reference to State-administered formula grant programs, are unlikely to generate any quantifiable costs and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>Proposed changes to § 76.50 would clarify that, in the absence of a statutory or regulatory prohibition against subgranting, or in the absence of a term and condition in the grant award that would prohibit subgranting, States, consistent with 2 CFR 200.332, determine whether to make subgrants. These proposed changes would likely generate cost savings for States associated with the reduced burden associated with making subgrants as opposed to contracts. However, we do not have sufficient information to quantify this impact and we invite public comment on the cost savings associated with such a shift at the State level.</P>
                    <P>Proposed changes to § 76.101, which would clarify the applicability of section 441 of GEPA, are unlikely to generate any quantifiable costs and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>Proposed changes to § 76.102, which would remove a table and provide a general definition of the term “State plan,” are unlikely to generate any quantifiable costs and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>Proposed changes to § 76.103, which would remove extraneous text and simplify the section, are unlikely to generate any quantifiable costs and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>Proposed changes to §§ 76.125-76.137, which would remove references to the Trust Territory of the Pacific Islands and make other changes, are unlikely to generate any quantifiable costs and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>Proposed changes to §§ 76.140-76.142, which would, among other things, allow the Secretary to prescribe alternative amendment processes on a program-by-program basis, could generate benefits for both States and the Department. The proposed changes would provide the Secretary broad flexibility in prescribing alternative procedures, which makes it difficult to assess precisely the specific cost reductions that would occur. However, we assume that these alternative procedures would result in a net burden reduction of 2 hours for a management analyst at the State level and 0.5 hours for an administrator at the State level for each State plan revision under the ESEA. We further estimate that likely alternative procedures would result in a burden reduction of 5 hours for a management analyst and 0.5 hours for a chief executive at the State level for each State plan revision under the Workforce Innovation and Opportunity Act (WIOA). We further assume an average of 15 State plan amendments under the ESEA and 52 State plan amendments under WIOA each year. In total, we estimate that these alternative procedures would reduce costs for States by approximately $23,733 per year. We also assume that the alternative procedures would reduce burden on Federal staff by approximately 1 hour per State plan amendment for a total Federal savings of approximately $4,150 per year.</P>
                    <P>Proposed changes to § 76.301, which would clarify that section 442 of GEPA does not apply to LEA subgrantees, would not generate any quantifiable costs, and would benefit the Department and the general public by improving the clarity of the regulations.</P>
                    <P>
                        Proposed changes to § 76.401, which would clarify that a notice of appeal must include an allegation of a specific violation of law by the SEA, are likely to generate benefits for the Department by reducing the number of appeals that fail to state a claim that we receive and 
                        <PRTPAGE P="2004"/>
                        process each year. On average, we process approximately 10 appeals each year, with an attorney spending approximately 30 hours reviewing each appeal. We estimate that this provision would reduce the number of appeals the Department receives each year by approximately 20 percent, resulting in a net savings of 60 hours per year or approximately $5,530 per year. We also believe that this provision would generate cost savings at the State level, but do not have sufficient information on the case load at the State level to make a reliable estimate. We invite public comment on the potential savings at the State level associated with this proposed change.
                    </P>
                    <P>Proposed changes to §§ 76.560-76.569, which would align these sections with the Uniform Guidance and provide additional information on the application of indirect cost rates, are unlikely to generate any quantifiable costs and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>Proposed changes to § 76.650 and related sections, which would revise regulatory references, are unlikely to generate any quantifiable costs and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>The proposed deletion of § 76.655 as unnecessary is unlikely to generate any quantifiable cost and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>Proposed changes to § 76.783 indicate that a subgrantee may request a hearing related to a State educational agency's failure to provide funds in amounts in accordance with the requirements of applicable statutes and regulations. These proposed changes would not generate any additional costs, as this circumstance was previously contemplated in § 76.401, which we are proposing to delete.</P>
                    <P>Proposed changes to § 77.1(c), which would update existing definitions, remove unnecessary definitions, and add new definitions, are unlikely to generate any quantifiable costs and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>Proposed changes to part 79, which would remove outdated statutory references, are unlikely to generate any quantifiable costs and may benefit the Department and general public by improving the clarity of the regulations.</P>
                    <P>Proposed changes to part 299, which would reflect statutory changes, are unlikely to generate any quantifiable costs and may benefit the Department and the general public by improving the clarity of the regulations. The proposed additions of §§ 299.16-299.17 would add specificity as to what an SEA's resolution of a complaint must include and what a party's appeal to the Secretary of an SEA decision must include. The specific elements named in these sections are all things that a legal decision or appeal should already include (such as a description of applicable statutory and regulatory requirements, legal analysis and conclusions, supporting documentation). When the Department receives records on appeal that do not include one or more of these elements, we go back to the parties to request the missing element(s). Specifying in these sections what we need to issue a decision would prevent this unnecessary delay; however, we do not think that the specific elements would generate quantifiable costs.</P>
                    <P>Proposed additions of §§ 299.18-299.28 regarding the procedures for a bypass in providing equitable services to eligible private school children, teachers or other educational personnel, and families, as applicable, are unlikely to generate any quantifiable costs and may benefit the Department and the general public by improving the clarity of the regulations. These sections reflect only minor updates to information previously contained in §§ 76.670-76.677, which elsewhere we propose to remove.</P>
                    <P>In total, we estimate that these regulations would result in a net decrease in costs of approximately $4,014 per year with transfers ranging from $109.7 million to $113.8 million per year. Of the net benefit, approximately $3,610 would accrue to grantees. The remaining approximately $400 in net additional benefits would accrue to the Department.</P>
                    <P>As noted above, we do not anticipate any meaningful, quantifiable impact from the majority of proposed regulatory changes. However, for those provisions for which we do estimate impacts, we summarize those impacts below using 3 and 7 percent discount rates, consistent with OMB Circular A-4:</P>
                    <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s100,12,12">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1">Provision</CHED>
                            <CHED H="1">
                                3% discount
                                <LI>rate</LI>
                            </CHED>
                            <CHED H="1">
                                7% discount
                                <LI>rate</LI>
                            </CHED>
                        </BOXHD>
                        <ROW RUL="n,s">
                            <ENT I="22"> </ENT>
                            <ENT A="01">Benefits</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 75.109—Reduce the number of paper copies of an application to be submitted</ENT>
                            <ENT>$375</ENT>
                            <ENT>$375</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 76.140-142—Amendments to State Plan</ENT>
                            <ENT>34,940</ENT>
                            <ENT>34,940</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">§ 76.401—Disapproval of an application</ENT>
                            <ENT>10,655</ENT>
                            <ENT>10,655</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="22"> </ENT>
                            <ENT A="01">Costs</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">§ 75.253—Request for Reconsideration</ENT>
                            <ENT>($27,924)</ENT>
                            <ENT>($27,924)</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="22"> </ENT>
                            <ENT A="01">Transfers</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 75.590—Independent evaluation</ENT>
                            <ENT>$113,824,837</ENT>
                            <ENT>$109,706,758</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 75.720—Financial and Performance Reports</ENT>
                            <ENT>$43,500</ENT>
                            <ENT>$43,500</ENT>
                        </ROW>
                    </GPOTABLE>
                    <HD SOURCE="HD1">Clarity of the Regulations</HD>
                    <P>Executive Order 12866 and the Presidential memorandum “Plain Language in Government Writing” require each agency to write regulations that are easy to understand.</P>
                    <P>The Secretary invites comments on how to make these proposed regulations easier to understand, including answers to questions such as the following:</P>
                    <P>• Are the requirements in the proposed regulations clearly stated?</P>
                    <P>• Do the proposed regulations contain technical terms or other wording that interferes with their clarity?</P>
                    <P>• Does the format of the proposed regulations (grouping and order of sections, use of headings, paragraphing, etc.) aid or reduce their clarity?</P>
                    <P>• Would the proposed regulations be easier to understand if we divided them into more (but shorter) sections?</P>
                    <P>
                        • Could the description of the proposed regulations in the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section of 
                        <PRTPAGE P="2005"/>
                        this preamble be more helpful in making the proposed regulations easier to understand? If so, how?
                    </P>
                    <P>• What else could we do to make the proposed regulations easier to understand?</P>
                    <P>
                        To send any comments that concern how the Department could make the proposed regulations easier to understand, see the instructions in the 
                        <E T="02">ADDRESSES</E>
                         section.
                    </P>
                    <HD SOURCE="HD1">Regulatory Flexibility Act Certification</HD>
                    <P>The Secretary certifies that this proposed regulatory action would not have a significant economic impact on a substantial number of small entities. The U.S. Small Business Administration Size Standards define proprietary institutions as small businesses if they are independently owned and operated, are not dominant in their field of operation, and have total annual revenue below $7,000,000. Nonprofit institutions are defined as small entities if they are independently owned and operated and not dominant in their field of operation. Public institutions are defined as small organizations if they are operated by a government overseeing a population below 50,000.</P>
                    <P>Of the impacts we estimate accruing to grantees or eligible entities, all are voluntary and related mostly to an increase in the number of applications prepared and submitted annually for competitive grant competitions. Therefore, we do not believe that these regulations present any significant impact on small entities beyond the potential for increasing the likelihood of their applying for, and receiving, competitive grants from the Department.</P>
                    <HD SOURCE="HD1">Paperwork Reduction Act</HD>
                    <P>The proposed regulatory action does not contain any information collection requirements. However, we do anticipate that the proposed changes to §§ 76.140-76.142 would reduce State burden under existing information collection requirements by approximately 323.5 hours per year (see the Discussion of Costs, Benefits, and Transfers for more information on this estimate). The valid OMB control number for that information collection is 1810-0576.</P>
                    <HD SOURCE="HD1">Intergovernmental Review</HD>
                    <P>These programs are subject to Executive Order 12372 and the regulations in 34 CFR part 79. One of the objectives of the Executive order is to foster an intergovernmental partnership and a strengthened federalism. The Executive order relies on processes developed by State and local governments for coordination and review of proposed Federal financial assistance.</P>
                    <P>This document provides early notification of our specific plans and actions for these programs.</P>
                    <P>
                        <E T="03">Accessible Format:</E>
                         On request to the program contact person listed under 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                        , individuals with disabilities can obtain this document in an accessible format. The Department will provide the requestor with an accessible format that may include Rich Text Format (RTF) or text format (txt), a thumb drive, an MP3 file, braille, large print, audiotape, or compact disc, or other accessible format.
                    </P>
                    <P>
                        <E T="03">Electronic Access to This Document:</E>
                         The official version of this document is the document published in the 
                        <E T="04">Federal Register</E>
                        . You may access the official edition of the 
                        <E T="04">Federal Register</E>
                         and the Code of Federal Regulations at 
                        <E T="03">www.govinfo.gov.</E>
                         At this site you can view this document, as well as all other documents of this Department published in the 
                        <E T="04">Federal Register</E>
                        , in text or Portable Document Format (PDF). To use PDF you must have Adobe Acrobat Reader, which is available free at the site.
                    </P>
                    <P>
                        You may also access documents of the Department published in the 
                        <E T="04">Federal Register</E>
                         by using the article search feature at 
                        <E T="03">www.federalregister.gov.</E>
                         Specifically, through the advanced search feature at this site, you can limit your search to documents published by the Department.
                    </P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects</HD>
                        <CFR>34 CFR Part 75</CFR>
                        <P>Accounting; Copyright; Education; Grant programs—education; Incorporation by reference; Indemnity payments; Inventions and patents; Private schools; Reporting and recordkeeping requirements; Youth organizations.</P>
                        <CFR>34 CFR Part 76</CFR>
                        <P>Accounting; Administrative practice and procedure; American Samoa; Education; Grant programs—education; Guam; Northern Mariana Islands; Pacific Islands Trust Territory; Prisons; Private schools; Reporting and recordkeeping requirements; Virgin Islands; Youth organizations.</P>
                        <CFR>34 CFR Part 77</CFR>
                        <P>Education; Grant programs—education; Incorporation by reference.</P>
                        <CFR>34 CFR Part 79</CFR>
                        <P>Intergovernmental relations.</P>
                        <CFR>34 CFR Part 299</CFR>
                        <P>Administrative practice and procedure; Elementary and secondary education; Grant programs—education; Private schools; Reporting and recordkeeping requirements.</P>
                    </LSTSUB>
                    <SIG>
                        <NAME>Miguel A. Cardona,</NAME>
                        <TITLE>Secretary of Education.</TITLE>
                    </SIG>
                    <P>For the reasons discussed in the preamble, the Secretary proposes to amend parts 75, 76, 77, 79, and 299 of title 34 of the Code of Federal Regulations as follows:</P>
                    <PART>
                        <HD SOURCE="HED">PART 75—DIRECT GRANT PROGRAMS</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 75 is revised to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P> 20 U.S.C. 1221e-3 and 3474, unless otherwise noted.</P>
                    </AUTH>
                    <EXTRACT>
                        <P>Section 75.263; 2 CFR 200.308(d)(1).</P>
                        <P>Section 75.617, 31 U.S.C. 3504, 3505.</P>
                        <P>Section 75.740 also issued under 20 U.S.C. 1232g and 1232h.</P>
                    </EXTRACT>
                    <AMDPAR>2. Revise § 75.1 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.1</SECTNO>
                        <SUBJECT>Programs to which part 75 applies.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">General.</E>
                             (1) The regulations in this part apply to each direct grant program of the Department of Education, except as specified in these regulations for direct formula grant programs, as referenced in paragraph (c)(3) of this section.
                        </P>
                        <P>(2) The Department administers two kinds of direct grant programs. A direct grant program is either a discretionary grant program or a formula grant program other than a State-administered formula grant program covered by 34 CFR part 76.</P>
                        <P>(3) If a direct grant program does not have implementing regulations, the Secretary implements the program under the applicable statutes and regulations and, to the extent consistent with the applicable statutes and regulations, under the General Education Provisions Act and the regulations in this part. With respect to the Impact Aid Program (Title VII of the Elementary and Secondary Education Act of 1965), see 34 CFR 222.19 for the limited applicable regulations in this part.</P>
                        <P>
                            (b) 
                            <E T="03">Discretionary grant programs.</E>
                             A discretionary grant program is one that permits the Secretary to use discretionary judgment in selecting applications for funding.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Formula grant programs.</E>
                             (1) A formula grant program is one that entitles certain applicants to receive grants if they meet the requirements of the program. Applicants do not compete with each other for the funds, and each grant is either for a set amount or for an amount determined under a formula.
                        </P>
                        <P>
                            (2) The Secretary applies the applicable statutes and regulations to 
                            <PRTPAGE P="2006"/>
                            fund projects under a formula grant program.
                        </P>
                        <P>(3) For specific regulations in this part that apply to the selection procedures and grant-making processes for direct formula grant programs, see §§ 75.215 and 75.230.</P>
                        <NOTE>
                            <HD SOURCE="HED">Note 1 to § 75.1:</HD>
                            <P>See 34 CFR part 76 for the general regulations that apply to programs that allocate funds by formula among eligible States.</P>
                        </NOTE>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 75.4</SECTNO>
                        <SUBJECT>[Removed and Reserved]</SUBJECT>
                    </SECTION>
                    <AMDPAR>3. Remove and reserve § 75.4.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.50</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>4. Amend § 75.50 in paragraph (a) by removing the words “the authorizing statute” and adding in their place the words “applicable statutes and regulations”.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.51</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>
                        5. Amend § 75.51 in paragraph (a) by removing the parenthetical sentence “(See the definition of 
                        <E T="03">nonprofit</E>
                         in 34 CFR 77.1.)”.
                    </AMDPAR>
                    <AMDPAR>6. Revise § 75.60 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.60</SECTNO>
                        <SUBJECT>Individuals ineligible to receive assistance.</SUBJECT>
                        <P>An individual is ineligible to receive a fellowship, scholarship, or discretionary grant funded by the Department if the individual—</P>
                        <P>(a) Is not current in repaying a debt or is in default, as that term is used in 34 CFR part 668, on a debt—</P>
                        <P>(1) Under a program administered by the Department under which an individual received a fellowship, scholarship, or loan that they are obligated to repay; or</P>
                        <P>(2) To the Federal Government under a nonprocurement transaction; and</P>
                        <P>(b) Has not made satisfactory arrangements to repay the debt.</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 75.61</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>7. Amend section 75.61 by:</AMDPAR>
                    <AMDPAR>a. In paragraph (a)(2), removing the words “section 5301 of the Anti-Drug Abuse Act of 1988 (21 U.S.C. 853a)” and adding in their place the words “section 421 of the Controlled Substances Act (21 U.S.C. 862)”; and</AMDPAR>
                    <AMDPAR>b. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.62</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>8. Amend § 75.62 by:</AMDPAR>
                    <AMDPAR>a. In paragraph (a)(2), removing the words “section 5301 of the Anti-Drug Abuse Act of 1988 (21 U.S.C. 853a)” and adding, in their place, the words “section 421 of the Controlled Substances Act (21 U.S.C. 862)”; and</AMDPAR>
                    <AMDPAR>b. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <AMDPAR>9. Amend § 75.101 by:</AMDPAR>
                    <AMDPAR>a. Revising paragraph (a)(1);</AMDPAR>
                    <AMDPAR>b. Adding the period after “assistance?)” in paragraph (a)(7);</AMDPAR>
                    <AMDPAR>c. Removing paragraphs (a)(1)(i) and (ii); and</AMDPAR>
                    <AMDPAR>d. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <P>The revision reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 75.101</SECTNO>
                        <SUBJECT>Information in the application notice that helps an applicant apply.</SUBJECT>
                        <P>(a) * * *</P>
                        <P>(1) How an applicant can obtain an application package.</P>
                        <STARS/>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 75.102</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>10. Amend § 75.102 by removing and reserving paragraph (b) and removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.103</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>11. Amend § 75.103 by:</AMDPAR>
                    <AMDPAR>a. Removing in paragraph (b) the citation “§ 75.102(b) and (d)” and adding in its place the citation “§ 75.102(d)”; and</AMDPAR>
                    <AMDPAR>b. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <AMDPAR>12. Amend § 75.104 by:</AMDPAR>
                    <AMDPAR>a. Revising the section heading;</AMDPAR>
                    <AMDPAR>b. Adding paragraph (c); and</AMDPAR>
                    <AMDPAR>c. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <P>The revision and addition read as follows.</P>
                    <SECTION>
                        <SECTNO>§ 75.104</SECTNO>
                        <SUBJECT>Additional application provisions.</SUBJECT>
                        <STARS/>
                        <P>(c) If an applicant wants a new grant, the applicant must submit an application in accordance with the requirements in the application notice.</P>
                    </SECTION>
                    <AMDPAR>13. Amend § 75.105 by:</AMDPAR>
                    <AMDPAR>a. Revising the section heading;</AMDPAR>
                    <AMDPAR>b. In paragraph (b)(2)(i), removing the words “by inviting applications that meet the priorities” and adding in their place the words “through invitational priorities”;</AMDPAR>
                    <AMDPAR>c. In paragraph (b)(2)(iii), removing the words “seriously interfere with an orderly, responsible grant award process or would otherwise”;</AMDPAR>
                    <AMDPAR>d. In paragraph (b)(2)(iv), removing the word “or” after the semicolon;</AMDPAR>
                    <AMDPAR>e. In paragraph (b)(2)(v), removing the period and adding in its place “; or”;</AMDPAR>
                    <AMDPAR>f. Adding paragraph (b)(2)(vi);</AMDPAR>
                    <AMDPAR>g. Removing the words “high quality” in paragraph (c)(3) and adding in their place the words “high-quality”; and</AMDPAR>
                    <AMDPAR>h. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <P>The revision and addition read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 75.105</SECTNO>
                        <SUBJECT>Annual absolute, competitive preference, and invitational priorities.</SUBJECT>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>(2) * * *</P>
                        <P>(vi) The final annual priorities are developed under the exemption from rulemaking for the first grant competition under a new or substantially revised program authority pursuant to section 437(d)(1) of GEPA, 20 U.S.C. 1232(d)(1), or an exemption from rulemaking under section 681(d) of the Individuals with Disabilities Education Act, 20 U.S.C. 1481(d), section 191 of the Education Sciences Reform Act, 20 U.S.C. 9581, or any other applicable exemption from rulemaking.</P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>14. Revise § 75.109 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.109</SECTNO>
                        <SUBJECT>Changes to applications.</SUBJECT>
                        <P>An applicant may make changes to its application on or before the deadline date for submitting the application under the program.</P>
                    </SECTION>
                    <AMDPAR>15. Amend § 75.110 by:</AMDPAR>
                    <AMDPAR>a. Revising paragraph (a);</AMDPAR>
                    <AMDPAR>b. Redesignating paragraphs (b) and (c) as paragraphs (c) and (b), respectively;</AMDPAR>
                    <AMDPAR>c. In newly redesignated paragraph (b) introductory text, adding the word “program” before the words “performance measurement”;</AMDPAR>
                    <AMDPAR>d. Revising newly redesignated paragraphs (b)(1)(ii) and (b)(2);</AMDPAR>
                    <AMDPAR>e. Revising newly redesignated paragraphs (c)(1) and (c)(2)(i); and</AMDPAR>
                    <AMDPAR>f. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <P>The revisions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 75.110</SECTNO>
                        <SUBJECT>Information regarding performance measurement.</SUBJECT>
                        <P>(a) The Secretary may establish, in an application notice for a competition, one or more program performance measurement requirements, including requirements for performance measures, baseline data, or performance targets, and a requirement that applicants propose in their applications one or more of their own project-specific performance measures, baseline data, or performance targets and ensure that the applicant's project-specific performance measurement plan would, if well implemented, yield quality data.</P>
                        <P>(b) * * *</P>
                        <P>(1) * * *</P>
                        <P>
                            (ii) If the Secretary requires applicants to collect data after the substantive work 
                            <PRTPAGE P="2007"/>
                            of a project is complete in order to measure progress toward attaining certain performance targets, the data-collection and reporting methods the applicant would use during the post-performance period and why those methods are likely to yield quality data.
                        </P>
                        <P>(2) The applicant's capacity to collect and report the quality of the performance data, as evidenced by quality data collection, analysis, and reporting in other projects or research.</P>
                        <P>(c) * * *</P>
                        <P>
                            (1) 
                            <E T="03">Project-specific performance measures.</E>
                             How each proposed project-specific performance measure would: accurately measure the performance of the project; be consistent with the program performance measures established under paragraph (a) of this section; and be used to inform continuous improvement of the project.
                        </P>
                        <P>(2) * * *</P>
                        <P>(i) Why each proposed baseline is valid and reliable, including an assessment of the quality data used to establish the baseline; or</P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>16. Amend § 75.112 by:</AMDPAR>
                    <AMDPAR>a. Revising the section heading;</AMDPAR>
                    <AMDPAR>b. Adding paragraph (c); and</AMDPAR>
                    <AMDPAR>c. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <P>The revision and addition read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 75.112</SECTNO>
                        <SUBJECT>Include a proposed project period, a timeline, and a logic model.</SUBJECT>
                        <STARS/>
                        <P>(c) The Secretary may establish, in an application notice, a requirement to include a logic model.</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 75.117</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>17. Amend § 75.117 in paragraph (a) by adding “and” after the semicolon.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.118</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>18. Amend § 75.118 by:</AMDPAR>
                    <AMDPAR>a. In paragraph (a), removing “2 CFR 200.327 and 200.328” and adding in its place “2 CFR 200.328 and 200.329”; and</AMDPAR>
                    <AMDPAR>b. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <AMDPAR>19. Revise § 75.119 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.119</SECTNO>
                        <SUBJECT>Information needed if private school children participate.</SUBJECT>
                        <P>If a program provides for participation of students enrolled in private schools and, as applicable, their teachers or other educational personnel, and their families, the application must include a description of how the applicant will meet the requirements under §§ 299.7-299.11.</P>
                    </SECTION>
                    <AMDPAR>20. Amend § 75.127 by:</AMDPAR>
                    <AMDPAR>a. Redesignating paragraphs (b)(3) and (4) as paragraphs (b)(4) and (5), respectively;</AMDPAR>
                    <AMDPAR>b. Adding new paragraph (b)(3) and paragraph (c); and</AMDPAR>
                    <AMDPAR>c. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <P>The additions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 75.127</SECTNO>
                        <SUBJECT>Eligible parties may apply as a group.</SUBJECT>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>(3) Partnership.</P>
                        <STARS/>
                        <P>(c) In the case of a group application submitted in accordance with §§ 75.127 through 75.129, all parties in the group must be eligible applicants under the competition.</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 75.135</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>21. Amend § 75.135 by:</AMDPAR>
                    <AMDPAR>a. In paragraph (a) introductory text, removing the citation “2 CFR 200.320(c) and (d)” and adding in its place the citation “2 CFR 200.320(b)”; and</AMDPAR>
                    <AMDPAR>b. In paragraph (b) introductory text, removing the citation “2 CFR 200.320(b)” and adding in its place the citation “2 CFR 200.320(a)”.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.155</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>22. Amend § 75.155 by removing the words “the authorizing statue requires” and adding in their place the words “applicable statutes and regulations require”.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.157</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>23. Amend § 75.157 by removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.158</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>24. Amend § 75.158 by:</AMDPAR>
                    <AMDPAR>a. In paragraph (c), removing the citation “§ 75.102(b) and (d)” and adding in its place the citation “§ 75.102(d)”; and</AMDPAR>
                    <AMDPAR>b. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ § 75.190 through 75.192 </SECTNO>
                        <SUBJECT>[Removed and Reserved]</SUBJECT>
                    </SECTION>
                    <AMDPAR>25. Remove the undesignated section heading before § 75.190, and remove and reserve §§ 75.190 through 75.192.</AMDPAR>
                    <AMDPAR>26-27. Revise the undesignated center heading before § 75.200 and revise § 75.200 to read as follows:</AMDPAR>
                    <HD SOURCE="HD1">
                        <E T="0742">Selection of New Discretionary Grant Projects</E>
                    </HD>
                    <SECTION>
                        <SECTNO>§ 75.200</SECTNO>
                        <SUBJECT>How applications for new discretionary grants and cooperative agreements are selected for funding; standards for use of cooperative agreements.</SUBJECT>
                        <P>(a) The Secretary uses selection criteria to evaluate the applications submitted for new grants under a discretionary grant program.</P>
                        <P>(b) To evaluate the applications for new grants under the program, the Secretary may use—</P>
                        <P>(1) Selection criteria established under § 75.209;</P>
                        <P>(2) Selection criteria in § 75.210; or</P>
                        <P>(3) Any combination of criteria from paragraphs (b)(1) and (b)(2) of this section.</P>
                        <P>(c)(1) The Secretary may award a cooperative agreement instead of a grant if the Secretary determines that substantial involvement between the Department and the recipient is necessary to carry out a collaborative project.</P>
                        <P>(2) The Secretary uses the selection procedures in this subpart to select recipients of cooperative agreements.</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 75.201</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>28. Amend § 75.201 by:</AMDPAR>
                    <AMDPAR>a. In paragraph (b), adding the words “or factors” after the words “selection criteria”;</AMDPAR>
                    <AMDPAR>b. In paragraph (c), removing the word “and” between the words “selection criteria” and “selected factors” and adding in its place the word “or”; and</AMDPAR>
                    <AMDPAR>c. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.209</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>29. Amend § 75.209 by:</AMDPAR>
                    <AMDPAR>a. In the introductory text, adding a comma immediately after “limited to”; and</AMDPAR>
                    <AMDPAR>b. In paragraph (c), removing the words “the program statute or regulations” and adding in their place the words “applicable statutes and regulations”.</AMDPAR>
                    <AMDPAR>30. Revise § 75.210 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.210</SECTNO>
                        <SUBJECT>General selection criteria.</SUBJECT>
                        <P>
                            In determining the selection criteria to evaluate applications submitted in a grant competition, the Secretary may select one or more of the following criteria and may select from among the list of optional factors under each criterion. The Secretary may define a selection criterion by selecting one or more specific factors within a criterion or assigning factors from one criterion to another criterion.
                            <PRTPAGE P="2008"/>
                        </P>
                        <P>
                            (a) 
                            <E T="03">Need for the project.</E>
                             (1) The Secretary considers the need for the proposed project.
                        </P>
                        <P>(2) In determining the need for the proposed project, the Secretary considers one or more of the following factors:</P>
                        <P>(i) The data presented (including a comparison to local, State, regional, national, or international data) that demonstrates the issue, challenge, or opportunity to be addressed by the proposed project.</P>
                        <P>(ii) The extent to which the proposed project demonstrates the magnitude of the need for the services to be provided or the activities to be carried out by the proposed project.</P>
                        <P>(iii) The extent to which the proposed project will provide support, resources, or services; close gaps in educational opportunity; or otherwise address the needs of the targeted population, including addressing the needs of underserved populations most affected by the issue, challenge, or opportunity to be addressed by the proposed project.</P>
                        <P>(iv) The extent to which the proposed project will focus on serving or otherwise addressing the needs of underserved populations.</P>
                        <P>(v) The extent to which the specific nature and magnitude of gaps or challenges are identified and the extent to which these gaps or challenges will be addressed by the services, supports, infrastructure, or opportunities described in the proposed project.</P>
                        <P>(vi) The extent to which the proposed project will prepare individuals from underserved populations for employment in fields and careers in which there are demonstrated shortages.</P>
                        <P>
                            (b) 
                            <E T="03">Significance.</E>
                             (1) The Secretary considers the significance of the proposed project.
                        </P>
                        <P>(2) In determining the significance of the proposed project, the Secretary considers one or more of the following factors:</P>
                        <P>(i) The extent to which the proposed project is relevant at the national level.</P>
                        <P>(ii) The significance of the problem or issue as it affects educational access and opportunity, including the underlying or related challenges for underserved populations.</P>
                        <P>(iii) The extent to which findings from the project's implementation will contribute new knowledge to the field by increasing knowledge or understanding of, including the underlying or related challenges, effective strategies for addressing educational challenges and their effective implementation.</P>
                        <P>(iv) The potential contribution of the proposed project to improve the provision of rehabilitative services, increase the number or quality of rehabilitation counselors, or develop and implement effective strategies for providing vocational rehabilitation services to individuals with disabilities.</P>
                        <P>(v) The likelihood that the proposed project will result in systemic change that supports continuous and sustainable improvement.</P>
                        <P>(vi) The potential contribution of the proposed project to the development and advancement of theory, knowledge, and practices in the field of study, including the extent to which the contributions may be used by other appropriate agencies, organizations, or institutions.</P>
                        <P>(vii) The potential for generalizing from the findings or results of the proposed project.</P>
                        <P>(viii) The extent to which the proposed project is likely to build local, State, or national capacity to provide, improve, sustain, or expand training or services that address the needs of underserved populations.</P>
                        <P>(ix) The extent to which the proposed project involves the development or demonstration of innovative and effective strategies that build on, or are alternatives to, existing strategies.</P>
                        <P>(x) The extent to which the proposed project is innovative and likely to be effective compared to other efforts to address a similar problem.</P>
                        <P>(xi) The likely utility of the resources (such as materials, processes, or techniques) that will result from the proposed project, including the potential for effective use in a variety of conditions, populations, or settings.</P>
                        <P>(xii) The extent to which the resources, tools, and implementation lessons of the proposed project will be disseminated in ways to the targeted population and local community that will enable them and others (including practitioners, researchers, education leaders, and partners) to implement similar strategies.</P>
                        <P>(xiii) The potential effective replicability of the proposed project or strategies, including, as appropriate, the potential for implementation by a variety of populations or settings.</P>
                        <P>(xiv) The importance or magnitude of the results or outcomes likely to be attained by the proposed project, especially contributions toward improving teaching practice and student learning and achievement.</P>
                        <P>(xv) The importance or magnitude of the results or outcomes likely to be attained by the proposed project, especially improvements in employment, independent living services, or both, as appropriate.</P>
                        <P>(xvi) The importance or magnitude of the results or outcomes likely to be attained by the proposed project that demonstrate the impact of the proposed project for the targeted underserved populations in terms of breadth and depth of services.</P>
                        <P>(xvii) The extent to which the proposed project introduces an innovative approach, such as a modification of an evidence-based project component to serve different populations, an extension of an existing evidence-based project component, a unique composition of various project components to explore combined effects, or an emerging project component that needs further testing.</P>
                        <P>
                            (c) 
                            <E T="03">Quality of the project design.</E>
                             (1) The Secretary considers the quality of the design of the proposed project.
                        </P>
                        <P>(2) In determining the quality of the design of the proposed project, the Secretary considers one or more of the following factors:</P>
                        <P>(i) The extent to which the goals, objectives, and outcomes to be achieved by the proposed project are clearly specified, measurable, and ambitious yet achievable within the project period, and aligned with the purposes of the grant program.</P>
                        <P>(ii) The extent to which the design of the proposed project demonstrates community engagement and input to ensure that the project is appropriate to successfully address the needs of the target population or other identified needs and will be used to inform continuous improvement strategies.</P>
                        <P>(iii) The quality of the conceptual framework, such as a logic model, underlying the proposed project, including how inputs are related to outcomes.</P>
                        <P>(iv) The extent to which the proposed project's logic model was developed based on engagement of a broad range of community members and partners.</P>
                        <P>(v) The extent to which the proposed project proposes specific, measurable targets, connected to strategies, activities, resources, outputs, and outcomes.</P>
                        <P>(vi) The extent to which the design of the proposed project includes a thorough, high-quality review of the relevant literature, a high-quality plan for project implementation, and the use of appropriate methodological tools to enable successful achievement of project objectives.</P>
                        <P>(vii) The quality of the proposed demonstration design, such as qualitative and quantitative design, and procedures for documenting project activities and results for underserved populations.</P>
                        <P>
                            (viii) The extent to which the design for implementing and evaluating the proposed project will result in 
                            <PRTPAGE P="2009"/>
                            information to guide possible replication of project activities or strategies, including valid and reliable information about the effectiveness of the approach or strategies employed by the project.
                        </P>
                        <P>(ix) The extent to which the proposed development efforts include adequate quality controls, continuous improvement efforts, and, as appropriate, repeated testing of products.</P>
                        <P>(x) The extent to which the proposed project demonstrates that it is designed to build capacity and yield sustainable results that will extend beyond the project period.</P>
                        <P>(xi) The extent to which the design of the proposed project reflects the most recent and relevant knowledge and practices from research and effective practice.</P>
                        <P>(xii) The extent to which the proposed project represents an exceptional approach for meeting program purposes and requirements and serving the target population.</P>
                        <P>(xiii) The extent to which the proposed project represents an exceptional approach to any absolute priority or absolute priorities established for the competition.</P>
                        <P>(xiv) The extent to which the proposed project will integrate or build on ideas, strategies, and efforts from similar external projects to improve relevant outcomes, using existing funding streams from other programs or policies supported by community, State, and Federal resources.</P>
                        <P>(xv) The extent to which the proposed project is informed by similar past projects implemented by the applicant with demonstrated results.</P>
                        <P>(xvi) The extent to which the proposed project will include coordination with other Federal investments, as well as appropriate agencies and organizations providing similar services to the target population.</P>
                        <P>(xvii) The extent to which the proposed project is part of a comprehensive effort to improve teaching and learning and support rigorous academic standards and increased social, emotional, and educational development for students, including members of underserved populations.</P>
                        <P>(xviii) The extent to which the proposed project encourages explicit plans for authentic, meaningful, and ongoing community member and partner engagement, including their involvement in planning, implementing, and revising project activities for underserved populations.</P>
                        <P>(xix) The extent to which the proposed project encourages consumer involvement.</P>
                        <P>(xx) The extent to which performance feedback and formative data are integral to the design of the proposed project and will be used to inform continuous improvement.</P>
                        <P>(xxi) The extent to which fellowship recipients or other project participants are to be selected on the basis of academic excellence.</P>
                        <P>(xxii) The extent to which the applicant demonstrates that it has the resources to operate the project beyond the project period, including a multiyear financial and operating model and accompanying plan; the demonstrated commitment of any partners; demonstration of broad support from community members and partners (such as State educational agencies, teachers' unions, families, business and industry, community members, and State vocational rehabilitation agencies) that are critical to the project's long-term success; or capacity-building leveraged from more than one of these types of resources.</P>
                        <P>(xxiii) The potential and planning for the incorporation of project purposes, activities, or benefits into the ongoing work of the applicant beyond the end of the project period.</P>
                        <P>(xxiv) The extent to which the proposed project will increase efficiency in the use of time, staff, money, or other resources in order to improve results and increase productivity.</P>
                        <P>(xxv) The extent to which the proposed project will integrate with, or build on, similar or related efforts in order to improve relevant outcomes, using nonpublic funds or resources.</P>
                        <P>(xxvi) The extent to which the proposed project demonstrates a rationale that is aligned with the purposes of the grant program.</P>
                        <P>(xxvii) The extent to which the proposed project represents implementation of the evidence cited in support of the proposed project with fidelity.</P>
                        <P>(xxiii) The extent to which the applicant plans to allocate a significant portion of its requested funding to the evidence-based project components.</P>
                        <P>(xxix) The strength of the commitment from key decision-makers at proposed implementation sites.</P>
                        <P>
                            (d) 
                            <E T="03">Quality of project services.</E>
                             (1) The Secretary considers the quality of the services to be provided by the proposed project.
                        </P>
                        <P>(2) In determining the quality of the services to be provided by the proposed project, the Secretary considers the quality and sufficiency of strategies for ensuring equitable and adequate access and participation for project participants who experience barriers based on one or more of the following: economic disadvantage; gender; race; ethnicity; color; national origin; disability; age; language; migration; living in a rural location; experiencing homelessness or housing insecurity; involvement with the justice system; pregnancy, parenting, or caregiver status; and sexual orientation. This determination includes the steps developed and described in the form Equity For Students, Teachers, And Other Program Beneficiaries (OMB Control No. 1894-0005) (section 427 of the General Education Provisions Act (20 U.S.C. 1228a)).</P>
                        <P>(3) In addition, the Secretary considers one or more of the following factors:</P>
                        <P>(i) The extent to which the services to be provided by the proposed project were determined with input from the community to be served to ensure that they are appropriate to the needs of the intended recipients or beneficiaries, including underserved populations, of those services.</P>
                        <P>(ii) The extent to which the proposed project is supported by entities that it is intended to serve.</P>
                        <P>(iii) The extent to which the services to be provided by the proposed project reflect up-to-date knowledge and an evidence-based project component.</P>
                        <P>(iv) The likely benefit to the intended recipients, as indicated by the logic model, of the services to be provided.</P>
                        <P>(v) The extent to which the training or professional development services to be provided by the proposed project are of sufficient quality, intensity, and duration to build recipient and project capacity in ways that lead to improvements in practice among the recipients of those services.</P>
                        <P>(vi) The extent to which the services to be provided by the proposed project are likely to provide long-term solutions to alleviate the personnel shortages that have been identified or are the focus of the proposed project.</P>
                        <P>(vii) The likelihood that the services to be provided by the proposed project will lead to meaningful improvements in the achievement of students as measured against rigorous and relevant standards.</P>
                        <P>(viii) The likelihood that the services to be provided by the proposed project will lead to meaningful improvements in early childhood and family outcomes.</P>
                        <P>
                            (ix) The likelihood that the services to be provided by the proposed project will lead to meaningful improvements in the skills and competencies necessary to gain employment in high-quality jobs, 
                            <PRTPAGE P="2010"/>
                            careers, and industries or build capacity for independent living.
                        </P>
                        <P>(x) The extent to which the services to be provided by the proposed project involve the collaboration of appropriate partners, including those from underserved populations, for maximizing the effectiveness of project services.</P>
                        <P>(xi) The extent to which the services to be provided by the proposed project involve the use of efficient strategies, including the use of technology, as appropriate, and the leveraging of non-project resources.</P>
                        <P>(xii) The extent to which the services to be provided by the proposed project are focused on recipients, community members, or project participants that are most underserved as demonstrated by the data relevant to the project.</P>
                        <P>
                            (e) 
                            <E T="03">Quality of the project personnel.</E>
                             (1) The Secretary considers the quality of the personnel who will carry out the proposed project.
                        </P>
                        <P>(2) In determining the quality of project personnel, the Secretary considers the extent to which the applicant demonstrates that it has project personnel or a plan for hiring of personnel who are members of groups that have historically encountered barriers, or who have professional or personal experiences with barriers, based on one or more of the following: economic disadvantage; gender; race; ethnicity; color; national origin; disability; age; language; migration; living in a rural location; experiencing homelessness or housing insecurity; involvement with the justice system; pregnancy, parenting, or caregiver status; and sexual orientation.</P>
                        <P>(3) In addition, the Secretary considers one or more of the following factors:</P>
                        <P>(i) The qualifications required of the project director or principal investigator, including formal training or work experience in fields related to the objectives of the project and experience in designing, managing, or implementing similar projects for the target population to be served by the project.</P>
                        <P>(ii) The qualifications required of each of the key personnel in the project, including formal training or work experience in fields related to the objectives of the project and be a representative of the target population.</P>
                        <P>(iii) The qualifications, including relevant training and experience, of project consultants or subcontractors.</P>
                        <P>(iv) The extent to which the proposed project team reflects the demographics of project participants to maximize inclusion of diverse perspectives.</P>
                        <P>(v) The extent to which the proposed planning, implementing, and evaluating project team are familiar with the assets, needs, and other contextual considerations of the proposed implementation sites.</P>
                        <P>
                            (f) 
                            <E T="03">Adequacy of resources.</E>
                             (1) The Secretary considers the adequacy of resources for the proposed project.
                        </P>
                        <P>(2) In determining the adequacy of resources for the proposed project, the Secretary considers one or more of the following factors:</P>
                        <P>(i) The adequacy of support for the project, including facilities, equipment, supplies, and other resources, from the applicant organization or the lead applicant organization.</P>
                        <P>(ii) The relevance and demonstrated commitment of each partner in the proposed project to the implementation and success of the project.</P>
                        <P>(iii) The extent to which the budget is adequate to support the proposed project and the costs are reasonable in relation to the objectives, design, and potential significance of the proposed project.</P>
                        <P>(iv) The extent to which the costs are reasonable in relation to the number of persons to be served, the depth and intensity of services, and the anticipated results and benefits.</P>
                        <P>(v) The extent to which the costs of the program are reasonable for potential entities to adopt.</P>
                        <P>(vi) The level of initial matching funds or other commitment from partners, indicating the likelihood for potential continued support of the project after Federal funding ends.</P>
                        <P>(vii) The potential for the purposes, activities, or benefits of the proposed project to be institutionalized into the ongoing practices and programs of the institution, agency, or organization and continue after the end date of Federal funding.</P>
                        <P>
                            (g) 
                            <E T="03">Quality of the management plan.</E>
                             (1) The Secretary considers the quality of the management plan for the proposed project.
                        </P>
                        <P>(2) In determining the quality of the management plan for the proposed project, the Secretary considers one or more of the following factors:</P>
                        <P>(i) The feasibility of the management plan to achieve project objectives and goals on time and within budget, including clearly defined responsibilities, timelines, and milestones for accomplishing project tasks.</P>
                        <P>(ii) The adequacy of plans for ensuring the use of quantitative and qualitative data, including community member and partner input, to inform continuous improvement in the operation of the proposed project.</P>
                        <P>(iii) The adequacy of mechanisms for ensuring high-quality and accessible products and services from the proposed project for the target population.</P>
                        <P>(iv) The extent to which the time commitments of the project director and principal investigator and other key project personnel are appropriate and adequate to meet the objectives of the proposed project.</P>
                        <P>(v) How the applicant will ensure that a diversity of perspectives, including those from underserved populations, are brought to bear in the design, implementation, operation, evaluation, and improvement of the proposed project, including those of parents, educators, community-based organizations, civil rights organizations, the business community, a variety of disciplinary and professional fields, recipients or beneficiaries of services, or others, as appropriate.</P>
                        <P>
                            (h) 
                            <E T="03">Quality of the project evaluation or other evidence-building.</E>
                             (1) The Secretary considers the quality of the evaluation or other evidence-building of the proposed project.
                        </P>
                        <P>(2) In determining the quality of the evaluation or other evidence-building, the Secretary considers one or more of the following factors:</P>
                        <P>(i) The extent to which the methods of evaluation or other evidence-building are thorough, feasible, relevant, and appropriate to the goals, objectives, and outcomes of the proposed project.</P>
                        <P>(ii) The extent to which the methods of evaluation or other evidence-building are appropriate to the context within which the project operates and the target population of the proposed project.</P>
                        <P>(iii) The extent to which the methods of evaluation or other evidence-building provide for describing the fidelity of implementation of the project.</P>
                        <P>(iv) The extent to which the methods of evaluation or other evidence-building include the use of objective performance measures that are clearly related to the intended outcomes of the project and will produce quality data that are quantitative and qualitative.</P>
                        <P>(v) The extent to which the methods of the evaluation or other evidence-building will provide guidance for quality assurance and continuous improvement.</P>
                        <P>(vi) The extent to which the methods of evaluation or other evidence-building will provide performance feedback and provide formative or interim data that is a periodic assessment of progress toward achieving intended outcomes.</P>
                        <P>
                            (vii) The extent to which the evaluation will provide guidance about effective strategies suitable for 
                            <PRTPAGE P="2011"/>
                            replication or testing and potential implementation in other settings.
                        </P>
                        <P>(viii) The extent to which the methods of evaluation will, if well implemented, produce evidence about the effectiveness of the project on relevant outcomes that would meet the What Works Clearinghouse standards without reservations, as described in the What Works Clearinghouse Handbooks.</P>
                        <P>(ix) The extent to which the methods of evaluation will, if well implemented, produce evidence about the effectiveness of the project on relevant outcomes that would meet the What Works Clearinghouse standards with or without reservations, as described in the What Works Clearinghouse Handbooks.</P>
                        <P>(x) The extent to which the methods of evaluation include an experimental study, a quasi-experimental design study, or a correlational study with statistical controls for selection bias (such as regression methods to account for differences between a treatment group and a comparison group) to assess the effectiveness of the project on relevant outcomes.</P>
                        <P>(xi) The extent to which the evaluation plan employs an appropriate analytic strategy to build evidence about the relationship between key project components, mediators, and outcomes for the purpose of informing specific actions on which elements to continue, revise, or dissolve.</P>
                        <P>(xii) The quality of the evaluation plan for measuring fidelity of implementation, including thresholds for acceptable implementation, to inform how implementation is associated with outcomes.</P>
                        <P>(xiii) The extent to which the evaluation plan includes a dissemination strategy that is likely to promote others' learning from the project.</P>
                        <P>(xiv) The qualifications, including relevant training, experience, and independence, of the evaluator, including experience conducting evaluations of similar methodology as proposed, familiar with evaluations for the proposed population and setting.</P>
                        <P>(xv) The extent to which the proposed project plan includes sufficient resources to conduct the project evaluation effectively.</P>
                        <P>
                            (i) 
                            <E T="03">Strategy to scale.</E>
                             (1) The Secretary considers the applicant's strategy to effectively scale, including to underserved populations, the proposed project.
                        </P>
                        <P>(2) In determining the applicant's capacity to effectively scale the proposed project for recipients and community members and partners, including those from underserved populations, the Secretary considers one or more of the following factors:</P>
                        <P>(i) The quality of the strategies to reach scale by expanding the project to new populations or settings.</P>
                        <P>(ii) The applicant's capacity (such as qualified personnel, financial resources, or management capacity), including project partners, to bring the proposed project effectively to scale on a national or regional level working directly, or through partners, during the grant period.</P>
                        <P>(iii) The applicant's capacity (such as qualified personnel, financial resources, or management capacity) to further develop and bring the proposed project to scale on a regional level working directly, or through partners, during the grant period, based on the findings of the proposed project.</P>
                        <P>(iv) The mechanisms the applicant will use to broadly disseminate information and resources on its project to support further development, adaptation, or replication by other entities to implement project components in additional settings or with other populations.</P>
                        <P>(v) The extent to which there is unmet demand for broader implementation of the project that is aligned with the proposed level of scale.</P>
                        <P>(vi) The extent to which there is a market of potential entities that will commit resources toward implementation.</P>
                        <P>(vii) The quality of the strategies to scale that take into account previous barriers to being able to expand the proposed project.</P>
                        <P>(viii) The quality of the plan to deliver project services more efficiently at scale and maintain effectiveness.</P>
                        <P>(ix) The quality of the plan to develop revenue sources that will make the program self-sustaining.</P>
                    </SECTION>
                    <AMDPAR>31. Revise § 75.215 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.215</SECTNO>
                        <SUBJECT>How the Department selects a new project.</SUBJECT>
                        <P>Sections 75.216 through 75.222 describe the process the Secretary uses to select applications for new grants. All these sections apply to a discretionary grant program. However, only § 75.216 applies also to a formula grant program.(See § 75.1(b) Discretionary grant programs, § 75.1(c) Formula grant programs, and § 75.200, How applications for new discretionary grants and cooperative agreements are selected for funding; standards for use of cooperative agreements.)</P>
                    </SECTION>
                    <AMDPAR>32. Revise § 75.216 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.216</SECTNO>
                        <SUBJECT>Applications that the Secretary may choose not to evaluate for funding.</SUBJECT>
                        <P>The Secretary may choose not to evaluate an application if—</P>
                        <P>(a) The applicant does not comply with all of the procedural rules that govern the submission of the application; or</P>
                        <P>(b) The application does not contain the information required under the program.</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 75.217</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>33. Amend § 75.217 by:</AMDPAR>
                    <AMDPAR>a. In paragraph (a), removing the words “the authorizing statute” and adding in their place the words “applicable statutes and regulations”;</AMDPAR>
                    <AMDPAR>b. In paragraph (c), removing the word “solely” and adding the words “and any competitive preference points” after the words “selection criteria”; and</AMDPAR>
                    <AMDPAR>c. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <AMDPAR>34. Amend § 75.219 by:</AMDPAR>
                    <AMDPAR>a. Revising paragraph (b); and</AMDPAR>
                    <AMDPAR>b. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <P>The revision reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 75.219</SECTNO>
                        <SUBJECT>Exceptions to the procedures under § 75.217.</SUBJECT>
                        <STARS/>
                        <P>(b)(1) The application was submitted under the preceding competition of the program;</P>
                        <P>(2) The application was not selected for funding because the application was mishandled or improperly processed by the Department; and</P>
                        <P>(3) The application has been rated highly enough to deserve selection under § 75.217; or</P>
                        <STARS/>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 75.220</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>35. Amend § 75.220 by:</AMDPAR>
                    <AMDPAR>a. In paragraph (b)(2), removing the words “Office of the Chief Financial Officer (OCFO)” and adding, in their place, the words “Office of Finance and Operations (OFO)”; and</AMDPAR>
                    <AMDPAR>b. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <AMDPAR>36. Revise § 75.221 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.221</SECTNO>
                        <SUBJECT>Procedures the Department uses under § 75.219(b).</SUBJECT>
                        <P>If the special circumstances of § 75.219(b) appear to exist for an application, the Secretary may select the application for funding if the Secretary has documentary evidence that those circumstances exist.</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 75.222</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>37. Amend § 75.222 by:</AMDPAR>
                    <AMDPAR>
                        a. In paragraph (a)(1), removing the word “under” before “which funds” and adding in its place the word “for”;
                        <PRTPAGE P="2012"/>
                    </AMDPAR>
                    <AMDPAR>b. In paragraph (a)(2)(ii)(B), removing the citation “(a)(2)(ii)” and adding in its place the citation “(a)(2)(ii)(A)”;</AMDPAR>
                    <AMDPAR>c. In paragraph (b)(1), removing the word “ED” and adding, it its place, the word “the Department”;</AMDPAR>
                    <AMDPAR>d. Removing, in paragraph (b)(2), the word “codified”;</AMDPAR>
                    <AMDPAR>e. Revising the Note; and</AMDPAR>
                    <AMDPAR>f. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <P>The revision reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 75.222</SECTNO>
                        <SUBJECT>Procedures the Department uses under § 75.219(c).</SUBJECT>
                        <STARS/>
                        <NOTE>
                            <HD SOURCE="HED">Note 1 to § 75.222:</HD>
                            <P> To assure prompt consideration, an applicant submitting an unsolicited application should send the application, marked “Unsolicited Application” on the outside, to U.S. Department of Education, OFO/G5 Functional Application Team, Mail Stop 5C231, 400 Maryland Avenue SW, Washington, DC 20202-4260.</P>
                        </NOTE>
                    </SECTION>
                    <AMDPAR>38. Revise § 75.225 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.225</SECTNO>
                        <SUBJECT>What procedures does the Secretary use when deciding to give special consideration to new potential grantees?</SUBJECT>
                        <P>(a) If the Secretary determines that special consideration of new potential grantees is appropriate, the Secretary may establish a separate competition under the procedures in § 75.105(c)(3), or provide competitive preference under the procedures in § 75.105(c)(2).</P>
                        <P>(b) As used in this section, “new potential grantee” means an applicant that meets one or more of the following conditions—</P>
                        <P>(1) The applicant has never received a grant or cooperative agreement, including through membership in a group application submitted in accordance with §§ 75.127 through 75.129 that received a grant or cooperative agreement, under the program from which it seeks funds;</P>
                        <P>(2) The applicant does not, as of the deadline date for submission of applications, have an active grant or cooperative agreement, including through membership in a group application submitted in accordance with §§ 75.127 through 75.129 that has an active grant or cooperative agreement, under the program from which it seeks funds;</P>
                        <P>(3) The applicant has not had an active discretionary grant or cooperative agreement under the program from which it seeks funds, including through membership in a group application submitted in accordance with §§ 75.127 through 75.129, within one of the following number of years before the deadline date for submission of applications under the program:</P>
                        <P>(i) 1 year;</P>
                        <P>(ii) 2 years;</P>
                        <P>(iii) 3 years;</P>
                        <P>(iv) 4 years;</P>
                        <P>(v) 5 years;</P>
                        <P>(vi) 6 years; or</P>
                        <P>(vii) 7 years;</P>
                        <P>(4) The applicant has not had an active discretionary grant or cooperative agreement from the Department, including through membership in a group application submitted in accordance with §§ 75.127 through 75.129, within one of the following number of years before the deadline date for submission of applications under the program from which it seeks funds:</P>
                        <P>(i) 1 year;</P>
                        <P>(ii) 2 years;</P>
                        <P>(iii) 3 years;</P>
                        <P>(iv) 4 years;</P>
                        <P>(v) 5 years;</P>
                        <P>(vi) 6 years; or</P>
                        <P>(vii) 7 years;</P>
                        <P>(5) The applicant has not had an active contract from the Department within one of the following number of years before the deadline date for submission of applications under the program for which it seeks funds:</P>
                        <P>(i) 1 year;</P>
                        <P>(ii) 2 years;</P>
                        <P>(iii) 3 years;</P>
                        <P>(iv) 4 years;</P>
                        <P>(v) 5 years;</P>
                        <P>(vi) 6 years; or</P>
                        <P>(vii) 7 years; or</P>
                        <P>(6) Any combination of paragraphs (b)(1) through (5) of this section.</P>
                        <P>(c) If the Secretary determines that special consideration of applications from new potential grantees is appropriate and chooses, under the procedures in § 75.105(c)(3), to establish a separate competition for those applicants that meet one or more of the conditions in paragraph (b) of this section, the Secretary may also establish a separate competition for applications that do not meet such priority under the procedures in § 75.105(c)(3) and consider those applications separately.</P>
                        <P>(d) As used in this section, an “application from a grantee that is not a new potential grantee” means an applicant that meets one or more of the following conditions—</P>
                        <P>(1) The applicant has received a grant or cooperative agreement, including through membership in a group application submitted in accordance with §§ 75.127 through 75.129 that received a grant or cooperative agreement, under the program from which it seeks funds;</P>
                        <P>(2) The applicant has, as of the deadline date for submission of applications, an active grant or cooperative agreement, including through membership in a group application submitted in accordance with §§ 75.127 through 75.129 that has an active grant or cooperative agreement, under the program from which it seeks funds;</P>
                        <P>(3) The applicant has had an active discretionary grant or cooperative agreement under the program from which it seeks funds, including through membership in a group application submitted in accordance with §§ 75.127 through 75.129, within one of the following number of years before the deadline date for submission of applications under the program:</P>
                        <P>(i) 1 year;</P>
                        <P>(ii) 2 years;</P>
                        <P>(iii) 3 years;</P>
                        <P>(iv) 4 years;</P>
                        <P>(v) 5 years;</P>
                        <P>(vi) 6 years; or</P>
                        <P>(vii) 7 years;</P>
                        <P>(4) The applicant has had an active discretionary grant or cooperative agreement from the Department, including through membership in a group application submitted in accordance with §§ 75.127 through 75.129, within one of the following number of years before the deadline date for submission of applications under the program from which it seeks funds:</P>
                        <P>(i) 1 year;</P>
                        <P>(ii) 2 years;</P>
                        <P>(iii) 3 years;</P>
                        <P>(iv) 4 years;</P>
                        <P>(v) 5 years;</P>
                        <P>(vi) 6 years; or</P>
                        <P>(vii) 7 years;</P>
                        <P>(5) The applicant has had an active contract from the Department within one of the following number of years before the deadline date for submission of applications under the program from which it seeks funds:</P>
                        <P>(i) 1 year;</P>
                        <P>(ii) 2 years;</P>
                        <P>(iii) 3 years;</P>
                        <P>(iv) 4 years;</P>
                        <P>(v) 5 years;</P>
                        <P>(vi) 6 years; or</P>
                        <P>(vii) 7 years.</P>
                        <P>(e) For the purpose of this section, a grant, cooperative agreement, or contract is active until the end of the grant's, cooperative agreement's, or contract's project or funding period, including any extensions of those periods that extend the grantee's or contractor's authority to obligate funds.</P>
                    </SECTION>
                    <AMDPAR>39. Revise § 75.226 to read as follows:</AMDPAR>
                    <SECTION>
                        <PRTPAGE P="2013"/>
                        <SECTNO>§ 75.226</SECTNO>
                        <SUBJECT>What procedures does the Secretary use if the Secretary decides to give special consideration to an application supported by strong evidence, moderate evidence, or promising evidence, or an application that demonstrates a rationale?</SUBJECT>
                        <P>If the Secretary determines that special consideration of applications supported by strong evidence, moderate evidence, promising evidence, or evidence that demonstrates a rationale is appropriate, the Secretary may establish a separate competition under the procedures in § 75.105(c)(3), or provide competitive preference under the procedures in § 75.105(c)(2), for applications that are supported by—</P>
                        <P>(a) Strong evidence;</P>
                        <P>(b) Moderate evidence;</P>
                        <P>(c) Promising evidence; or</P>
                        <P>(d) Evidence that demonstrates a rationale.</P>
                    </SECTION>
                    <AMDPAR>40. Add § 75.227 before the undesignated center heading “Procedures to Make a Grant” to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.227</SECTNO>
                        <SUBJECT>What procedures does the Secretary use if the Secretary decides to give special consideration to rural applicants?</SUBJECT>
                        <P>(a) If the Secretary determines that special consideration of rural applicants is appropriate, the Secretary may establish a separate competition under the procedures in § 75.105(c)(3), or provide competitive preference under the procedures in § 75.105(c)(2).</P>
                        <P>(b) As used in this section, “rural applicant” means an applicant that meets one or more of the following conditions—</P>
                        <P>(1) The applicant proposes to serve a local educational agency (LEA) that is eligible under the Small Rural School Achievement (SRSA) program or the Rural and Low-Income School (RLIS) program authorized under title V, part B of the Elementary and Secondary Education Act of 1965.</P>
                        <P>(2) The applicant proposes to serve a community that is served by one or more LEAs—</P>
                        <P>(i) With a locale code of 32, 33, 41, 42, or 43; or</P>
                        <P>(ii) With a locale code of 41, 42, or 43.</P>
                        <P>(3) The applicant proposes a project in which a majority of the schools served—</P>
                        <P>(i) Have a locale code of 32, 33, 41, 42, or 43; or</P>
                        <P>(ii) Have a locale code of 41, 42, or 43.</P>
                        <P>(4) The applicant is an institution of higher education (IHE) with a rural campus setting, or the applicant proposes to serve a campus with a rural setting. Rural settings include one or more of the following: Town-Fringe, Town-Distant, Town-Remote, Rural Fringe, Rural-Distant, and Rural-Remote, as defined by the National Center for Education Statistics (NCES) College Navigator search tool.</P>
                        <P>(c) If the Secretary determines that special consideration of rural applicants is appropriate and chooses, under the procedures in § 75.105(c)(3), to establish a separate competition for those applicants that meet one or more of the conditions in paragraph (b) of this section, the Secretary may also establish a separate competition for applications that do not meet that priority under the procedures in § 75.105(c)(3) and consider such applications separately.</P>
                        <P>(d) As used in this section, a “non-rural applicant” means an applicant that meets one or more of the following conditions—</P>
                        <P>(1) The applicant does not propose to serve a local educational agency (LEA) that is eligible under the Small Rural School Achievement (SRSA) program or the Rural and Low-Income School (RLIS) program authorized under title V, part B of the Elementary and Secondary Education Act of 1965.</P>
                        <P>(2) The applicant does not propose to serve a community that is served by one or more LEAs—</P>
                        <P>(i) With a locale code of 32, 33, 41, 42, or 43; or</P>
                        <P>(ii) With a locale code of 41, 42, or 43.</P>
                        <P>(3) The applicant proposes a project in which a majority of the schools served—</P>
                        <P>(i) Have a locale code of 32, 33, 41, 42, or 43; or</P>
                        <P>(ii) Have a locale code of 41, 42, or 43.</P>
                        <P>(4) The applicant is not an institution of higher education (IHE) with a rural campus setting, or the applicant proposes to serve a campus with a rural setting. Rural settings include one or more of the following: Town-Fringe, Town-Distant, Town-Remote, Rural Fringe, Rural-Distant, and Rural-Remote, as defined by the National Center for Education Statistics (NCES) College Navigator search tool.</P>
                    </SECTION>
                    <AMDPAR>41. Revise § 75.230 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.230</SECTNO>
                        <SUBJECT>How the Department makes a grant.</SUBJECT>
                        <P>(a) If the Secretary selects an application under §§ 75.217, 75.220, or 75.222, the Secretary follows the procedures in §§ 75.231 through 75.236 to set the amount and determine the conditions of a grant. Sections 75.235 through 75.236 also apply to grants under formula grant programs. (See § 75.200 for more information.)</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 75.234</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>42. Amend § 75.234 by:</AMDPAR>
                    <AMDPAR>a. In paragraph (a)(2), removing the word “special” and adding in its place the word “specific”; and</AMDPAR>
                    <AMDPAR>b. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <AMDPAR>43. Revise § 75.250 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.250</SECTNO>
                        <SUBJECT>Maximum project period.</SUBJECT>
                        <P>The Secretary may approve a project period of up to 60 months to perform the substantive work of a grant unless an applicable statute provides otherwise.</P>
                    </SECTION>
                    <AMDPAR>44. Revise § 75.253 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.253</SECTNO>
                        <SUBJECT>Continuation of a multiyear project after the first budget period.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Continuation award.</E>
                             A grantee, in order to receive a continuation award from the Secretary for a budget period after the first budget period of an approved multiyear project, must—
                        </P>
                        <P>(1) Either—</P>
                        <P>(i) Demonstrate that it has made substantial progress in achieving—</P>
                        <P>(A) The goals and objectives of the project; and</P>
                        <P>(B) The performance targets in the grantee's approved application, if the Secretary established performance measurement requirements for the grant in the application notice; or</P>
                        <P>(ii) Obtain the Secretary's approval for changes to the project that—</P>
                        <P>(A) Do not increase the amount of funds obligated to the project by the Secretary; and</P>
                        <P>(B) Enable the grantee to achieve the goals and objectives of the project and meet the performance targets of the project, if any, without changing the scope or objectives of the project;</P>
                        <P>(2) Submit all reports as required by § 75.118;</P>
                        <P>(3) Continue to meet all applicable eligibility requirements of the grant program;</P>
                        <P>(4) Maintain financial and administrative management systems that meet the requirements in 2 CFR 200.302 and 200.303; and</P>
                        <P>(5) Receive a determination from the Secretary that continuation of the project is in the best interest of the Federal Government.</P>
                        <P>
                            (b) 
                            <E T="03">Information considered in making a continuation award.</E>
                             In determining whether the grantee has met the requirements described in paragraph (a) of this section, the Secretary may consider any relevant information regarding grantee performance. This includes considering reports required by § 75.118, performance measures established by § 75.110, financial information required by 2 CFR part 200, and any other relevant information.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Funding for continuation awards.</E>
                             Subject to the criteria in paragraphs (a) and (b) of this section, in selecting applications for funding under a 
                            <PRTPAGE P="2014"/>
                            program, the Secretary gives priority to continuation awards over new grants.
                        </P>
                        <P>
                            (d) 
                            <E T="03">Budget period.</E>
                             If the Secretary makes a continuation award under this section—
                        </P>
                        <P>(1) The Secretary makes the award under §§ 75.231 through 75.236; and</P>
                        <P>(2) The new budget period begins on the day after the previous budget period ends.</P>
                        <P>
                            (e) 
                            <E T="03">Amount of continuation award.</E>
                             (1) Within the original project period of the grant and notwithstanding any requirements in 2 CFR part 200, a grantee may expend funds that have not been obligated at the end of a budget period for obligations of subsequent budget periods if—
                        </P>
                        <P>(i) The obligation is for an allowable cost within the approved scope and objectives of the project; and</P>
                        <P>(ii) The obligation is not otherwise prohibited by applicable statutes, regulations, or the conditions of an award.</P>
                        <P>(2) The Secretary may—</P>
                        <P>(i) Require the grantee to submit a written statement describing how the funds made available under paragraph (e)(1) of this section will be used; and</P>
                        <P>(ii) Determine the amount of new funds that the Department will make available for the subsequent budget period after considering the statement the grantee provides under paragraph (e)(2)(i) of this section and any other information available to the Secretary about the use of funds under the grant.</P>
                        <P>(3) In determining the amount of new funds to make available to a grantee under this section, the Secretary considers whether the unobligated funds made available are needed to complete activities that were planned for completion in the prior budget period.</P>
                        <P>(4) A decision to reduce the amount of a continuation award under this paragraph (e) does not entitle a grantee to reconsideration under 2 CFR 200.341.</P>
                        <P>
                            (f) 
                            <E T="03">Decision not to make a continuation award.</E>
                             The Secretary may decide not to make a continuation award if—
                        </P>
                        <P>(1) A grantee fails to meet any of the requirements in paragraph (a) of this section; or</P>
                        <P>(2) A grantee fails to ensure that data submitted to the Department as a condition of the grant meet the definition of “quality data” in 34 CFR 77.1(c) and does not have a plan acceptable to the Secretary for addressing data-quality issues in the next budget period.</P>
                        <P>
                            (g) 
                            <E T="03">Request for reconsideration.</E>
                             If the Secretary decides not to make a continuation award under this section, the Secretary will notify the grantee of that decision, the grounds on which it is based, and, consistent with 2 CFR 200.341, provide the grantee with an opportunity to request reconsideration of the decision.
                        </P>
                        <P>(1) A request for reconsideration must—</P>
                        <P>(i) Be submitted in writing to the Department official identified in the notice denying the continuation award by the date specified in that notice; and</P>
                        <P>(ii) Set forth the grantee's basis for disagreeing with the Secretary's decision not to make a continuation award and include relevant supporting documentation.</P>
                        <P>(2) The Secretary will consider the request for reconsideration.</P>
                        <P>
                            (h) 
                            <E T="03">No-cost extension when a continuation award is not made.</E>
                             If the Secretary decides not to make a continuation award under this section, the Secretary may authorize a no-cost extension of the last budget period of the grant in order to provide for the orderly closeout of the grant.
                        </P>
                        <P>
                            (i) 
                            <E T="03">A decision to reduce or not to make a continuation award does not constitute withholding.</E>
                             A decision by the Secretary to reduce the amount of a continuation award under paragraph (e) of this section or to not make a continuation award under paragraph (f) of this section does not constitute a withholding under section 455 of GEPA (20 U.S.C. 1234d).
                        </P>
                    </SECTION>
                    <AMDPAR>45. Revise § 75.254 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.254</SECTNO>
                        <SUBJECT>Data collection period.</SUBJECT>
                        <P>(a) The Secretary may approve a data collection period for a grant for a period of up to 72 months after the end of the project period and provide funds for the data collection period for the purpose of collecting, analyzing, and reporting performance measurement data on the project.</P>
                        <P>(b) If the Secretary plans to approve a data collection period, the Secretary may inform applicants of the Secretary's intent to approve data collection periods in the application notice published for a competition or may decide to fund data collection periods after grantees have started their project periods.</P>
                        <P>(c) If the Secretary informs applicants of the intent to approve data collection periods in the notice inviting applications, the Secretary may require applicants to include in the application a budget for, and description of, a data collection period for a period of up to 72 months, as specified in the notice inviting applications, after the end of the project period.</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 75.260</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>46. Amend § 75.260 by:</AMDPAR>
                    <AMDPAR>a. In paragraph (b), removing the words “the authorizing statute for that program” and adding in their place the words “applicable statutes and regulations”; and</AMDPAR>
                    <AMDPAR>b. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <AMDPAR>47. Revise § 75.261 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.261</SECTNO>
                        <SUBJECT>Extension of a project period.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">One-time extension of project period without prior approval.</E>
                             A grantee may extend the project period of an award one time, for a period up to 12 months, without the prior approval of the Secretary, if—
                        </P>
                        <P>(1) The grantee meets the requirements for extension in 2 CFR 200.308(e)(2); and</P>
                        <P>(2) The extension is not otherwise prohibited by statute, regulation, or the conditions of an award.</P>
                        <P>
                            (b) 
                            <E T="03">Extension of project period with prior approval.</E>
                             At the conclusion of the project period extension authorized under paragraph (a) of this section, or in any case in which a project period extension is not authorized under paragraph (a) of this section, a grantee, with prior approval of the Secretary, may extend a project for an additional period if—
                        </P>
                        <P>(1) The extension is not otherwise prohibited by statute, regulations, or the conditions of an award;</P>
                        <P>(2) The extension does not involve the obligation of additional Federal funds;</P>
                        <P>(3) The extension is to carry out the approved objectives and scope of the project; and</P>
                        <P>(4)(i) The Secretary determines that, due to special or unusual circumstances applicable to a class of grantees, the project periods for the grantees should be extended; or</P>
                        <P>(ii)(A) The Secretary determines that special or unusual circumstances would delay completion of the project beyond the end of the project period;</P>
                        <P>(B) The grantee requests an extension of the project period at least 45 calendar days before the end of the project period; and</P>
                        <P>(C) The grantee provides a written statement, before the end of the project period, of the reasons the extension is appropriate under paragraph (b)(4)(ii)(A) of this section and the period for which the project extension is requested.</P>
                        <P>
                            (c) 
                            <E T="03">Waiver.</E>
                             The Secretary may waive the requirement in paragraph (b)(4)(ii)(B) of this section if—
                        </P>
                        <P>(1) The grantee could not reasonably have known of the need for the extension on or before the start of the 45-day period; or</P>
                        <P>(2) The failure to give notice on or before the start of the 45-day period was unavoidable.</P>
                    </SECTION>
                    <SECTION>
                        <PRTPAGE P="2015"/>
                        <SECTNO>§ 75.263</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>48. Amend § 75.263 by:</AMDPAR>
                    <AMDPAR>a. Removing “, notwithstanding any requirement in 2 CFR part 200,” from the introductory text.</AMDPAR>
                    <AMDPAR>b. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.264</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>49. Remove the authority citation at the end of the section.</AMDPAR>
                    <AMDPAR>50. Amend § 75.500 by revising paragraph (a) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.500</SECTNO>
                        <SUBJECT>Federal statutes and regulations on nondiscrimination.</SUBJECT>
                        <P>(a) Each grantee must comply with the following statutes and regulations:</P>
                        <GPOTABLE COLS="3" OPTS="L2,nj,i1" CDEF="s100,r105,xs66">
                            <TTITLE>
                                Table 1 to § 75.500
                                <E T="01">(a)</E>
                            </TTITLE>
                            <BOXHD>
                                <CHED H="1">Subject</CHED>
                                <CHED H="1">Statute</CHED>
                                <CHED H="1">Regulations</CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">Discrimination on the basis of race, color, or national origin</ENT>
                                <ENT>
                                    Title VI of the Civil Rights Act of 1964 (42 U.S.C. 2000d 
                                    <E T="03">et seq.</E>
                                    )
                                </ENT>
                                <ENT>34 CFR part 100.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Discrimination on the basis of sex</ENT>
                                <ENT>
                                    Title IX of the Education Amendments of 1972 (20 U.S.C. 1681 
                                    <E T="03">et seq.</E>
                                    )
                                </ENT>
                                <ENT>34 CFR part 106.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Discrimination on the basis of disability</ENT>
                                <ENT>Section 504 of the Rehabilitation Act of 1973 (29 U.S.C. 794)</ENT>
                                <ENT>34 CFR part 104.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Discrimination on the basis of age</ENT>
                                <ENT>
                                    Age Discrimination Act of 1975 (42 U.S.C. 6101 
                                    <E T="03">et seq.</E>
                                    )
                                </ENT>
                                <ENT>34 CFR part 110.</ENT>
                            </ROW>
                        </GPOTABLE>
                        <STARS/>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 75.519</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>51. Amend § 75.519 by:</AMDPAR>
                    <AMDPAR>a. Removing the words “its grantee” and adding in their place the words “its grant”;</AMDPAR>
                    <AMDPAR>b. Adding “, consistent with the cost principles described in 2 CFR part 200” after the word “funds”; and</AMDPAR>
                    <AMDPAR>c. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.531</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>52. Amend § 75.531 by removing the word “insure” and adding in its place the word “ensure”.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.533</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>53. Amend § 75.533 by:</AMDPAR>
                    <AMDPAR>a. Removing the words “authorizing statute or implementing regulations for the program” and adding in their place the words “applicable statutes and regulations”.</AMDPAR>
                    <AMDPAR>b. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.534</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>54. Amend § 75.534 in paragraph (a) by removing the words “the program statute” and adding in their place the words “applicable statutes and regulations”.</AMDPAR>
                    <AMDPAR>55. Revise § 75.560 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.560</SECTNO>
                        <SUBJECT>General indirect cost rates and cost allocation plans; exceptions.</SUBJECT>
                        <P>(a) The differences between direct and indirect costs and the principles for determining the general indirect cost rate that a grantee may use for grants under most programs are specified in the cost principles for—</P>
                        <P>(1) All grantees, other than hospitals and commercial (for-profit) organizations, at 2 CFR part 200, subpart E;</P>
                        <P>(2) Hospitals, at 45 CFR part 75, appendix XI; and</P>
                        <P>(3) Commercial (for-profit) organizations, at 48 CFR part 31.</P>
                        <P>(b) Except as specified in paragraph (c) of this section, a grantee must have obtained a current indirect cost rate agreement or approved cost allocation plan from its cognizant agency, to charge indirect costs to a grant. To obtain a negotiated indirect cost rate agreement or approved cost allocation plan, a grantee must submit an indirect cost rate proposal or cost allocation plan to its cognizant agency within 90 days after the date on which the Department issues the Grant Award Notification (GAN).</P>
                        <P>
                            (c) A grantee that meets the requirements in 2 CFR 200.414(f) may elect to charge the 
                            <E T="03">de minimis</E>
                             rate of modified total direct costs (MTDC) specified in that provision, which may be used indefinitely. The 
                            <E T="03">de minimis</E>
                             rate may not be used on programs that have statutory or regulatory restrictions on the indirect cost rate. No documentation is required to justify the 
                            <E T="03">de minimis</E>
                             rate.
                        </P>
                        <P>(1) If the grantee has established a threshold for equipment that is lower than the amount specified in the Uniform Guidance, the grantee must use that threshold to exclude equipment from the MTDC base.</P>
                        <P>
                            (2) For purposes of the MTDC base and application of the 
                            <E T="03">de minimis</E>
                             rate, MTDC includes up to the amount specified in the definition of MTDC in the Uniform Guidance of each subaward, each year.
                        </P>
                        <P>(d) If a grantee is required to, but does not, have a federally recognized indirect cost rate agreement or approved cost allocation plan, the Secretary may permit the grantee to charge its grant for indirect costs at a temporary rate of 10 percent of budgeted direct salaries and wages.</P>
                        <P>(e)(1) If a grantee fails to submit an indirect cost rate proposal or cost allocation plan to its cognizant agency within the required 90 days, the grantee may not charge indirect costs to its grant from the end of the 90-day period until it obtains a federally recognized indirect cost rate agreement applicable to the grant.</P>
                        <P>(2) If the Secretary determines that exceptional circumstances warrant continuation of a temporary indirect cost rate, the Secretary may authorize the grantee to continue charging indirect costs to its grant at the temporary rate specified in paragraph (d) of this section even though the grantee has not submitted its indirect cost rate proposal within the 90-day period.</P>
                        <P>(3) Once a grantee obtains a federally recognized indirect cost rate that is applicable to the affected grant, the grantee may use that indirect cost rate to claim indirect cost reimbursement for expenditures made on or after the date on which the grantee submitted its indirect cost proposal to its cognizant agency or the start of the project period, whichever is later. However, this authority is subject to the following limitations:</P>
                        <P>(i) The total amount of funds recovered by the grantee under the federally recognized indirect cost rate is reduced by the amount of indirect costs previously recovered under the temporary indirect cost rate specified in paragraph (d) of this section.</P>
                        <P>(ii) The grantee must obtain prior approval from the Secretary to shift direct costs to indirect costs in order to recover indirect costs at a higher negotiated indirect cost rate.</P>
                        <P>(iii) The grantee may not request additional funds to recover indirect costs that it cannot recover by shifting direct costs to indirect costs.</P>
                        <P>
                            (f) The Secretary accepts a current indirect cost rate and cost allocation plan approved by a grantee's cognizant 
                            <PRTPAGE P="2016"/>
                            agency but may establish a restricted indirect cost rate or cost allocation plan compliant with 34 CFR 76.564 through 76.569 to satisfy the statutory requirements of certain programs administered by the Department.
                        </P>
                    </SECTION>
                    <AMDPAR>56. Amend § 75.561 by:</AMDPAR>
                    <AMDPAR>a. Revising the section heading and paragraph (a); and</AMDPAR>
                    <AMDPAR>b. Removing the second sentence of paragraph (b).</AMDPAR>
                    <P>The revisions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 75.561</SECTNO>
                        <SUBJECT>Approval of indirect cost rates and cost allocation plans.</SUBJECT>
                        <P>
                            (a) If the Department of Education is the cognizant agency, the Secretary approves an indirect cost rate or cost allocation plan for a grantee that is eligible and does not elect a 
                            <E T="03">de minimis</E>
                             rate, and is not a local educational agency. For the purposes of this section, the term “local educational agency” does not include a State agency.
                        </P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>57. Revise § 75.562 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.562</SECTNO>
                        <SUBJECT>Indirect cost rates for educational training projects; exceptions.</SUBJECT>
                        <P>(a) Educational training grants provide funds for training or other educational services. Examples of the work supported by training grants are summer institutes, training programs for selected participants, the introduction of new or expanded courses, and similar instructional undertakings that are separately budgeted and accounted for by the sponsoring institution. These grants do not usually support activities involving research, development, and dissemination of new educational materials and methods. Training grants largely implement previously developed materials and methods and require no significant adaptation of techniques or instructional services to fit different circumstances.</P>
                        <P>(b) The Secretary uses the definition in paragraph (a) of this section to determine which grants are educational training grants.</P>
                        <P>(c)(1) Indirect cost reimbursement on a training grant is limited to the lesser of the recipient's approved indirect cost rate, or 8 percent of the modified total direct cost (MTDC) base. MTDC is defined in 2 CFR 200.1.</P>
                        <P>
                            (2) If the grantee does not have a federally recognized indirect cost rate agreement on the date on which the training grant is awarded, the grantee may elect to use the temporary indirect cost rate authorized under § 75.560(d)(3) or a rate of 8 percent of the MTDC base. The 
                            <E T="03">de minimis</E>
                             rate may not be used on educational training programs.
                        </P>
                        <P>(i) If the grantee has established a threshold for equipment that is lower than the amount specified in the Uniform Guidance, the grantee must use that threshold to exclude equipment from the MTDC base.</P>
                        <P>(ii) For purposes of the MTDC base and application of the 8 percent rate, MTDC includes up to the amount specified in the definition of MTDC in the Uniform Guidance of each subaward, each year.</P>
                        <P>(3) The 8 percent indirect cost rate reimbursement limit specified in paragraph (c)(1) of this section also applies when subrecipients issue subawards that fund training, as determined by the Secretary under paragraph (b) of this section.</P>
                        <P>(4) The 8 percent limit does not apply to agencies of Indian tribal governments, local governments, and States as defined in 2 CFR 200.1.</P>
                        <P>(5) Indirect costs in excess of the 8 percent limit may not be charged directly, used to satisfy matching or cost-sharing requirements, or charged to another Federal award.</P>
                        <P>(d) A grantee using the training rate of 8 percent is required to maintain documentation to justify the 8 percent rate.</P>
                    </SECTION>
                    <AMDPAR>58. Revise § 75.563 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.563</SECTNO>
                        <SUBJECT>Restricted indirect cost rate or cost allocation plans—programs covered.</SUBJECT>
                        <P>If a grantee or subgrantee decides to charge indirect costs to a program that is subject to a statutory prohibition on using Federal funds to supplant non-Federal funds, the grantee shall—</P>
                        <P>(a) Use a negotiated restricted indirect cost rate or restricted cost allocation plan compliant with 34 CFR 76.564 through 76.569; or</P>
                        <P>(b) Elect to use an indirect cost rate of 8 percent of the modified total direct costs (MTDC) base if the grantee or subgrantee does not have a negotiated restricted indirect cost rate. MTDC is defined in 2 CFR 200.1. If the Secretary determines that the grantee or subgrantee would have a lower rate under 34 CFR 76.564 through 76.569, the lower rate shall be used on the affected program.</P>
                        <P>(c) If the grantee has established a threshold for equipment that is lower than the amount specified in the Uniform Guidance, the grantee must use that threshold to exclude equipment from the MTDC base.</P>
                        <P>(d) For purposes of the MTDC base and application of the 8 percent rate, MTDC includes up to the amount specified in the definition of MTDC in the Uniform Guidance of each subaward, each year.</P>
                    </SECTION>
                    <AMDPAR>59. Amend § 75.564 by:</AMDPAR>
                    <AMDPAR>a. Revising paragraph (b);</AMDPAR>
                    <AMDPAR>b. Adding the words “and other applicable restrictions” at end of paragraph (d);</AMDPAR>
                    <AMDPAR>c. Removing the word “for” after the phrase “to the direct cost base” and adding in its place the word “of” in paragraph (e)(1);</AMDPAR>
                    <AMDPAR>d. Adding the words “and program requirements” at the end of paragraph (e)(1);</AMDPAR>
                    <AMDPAR>e. Removing the hyphen between “sub” and “awards” in paragraph (e)(2); and</AMDPAR>
                    <AMDPAR>f. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <P>The revision reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 75.564</SECTNO>
                        <SUBJECT>Reimbursement of indirect costs.</SUBJECT>
                        <STARS/>
                        <P>(b) The application of the negotiated indirect cost rate (determination of the direct cost base) or cost allocation plan (charging methodology) must be in accordance with the agreement/plan approved by the grantee's cognizant agency.</P>
                        <STARS/>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 75.580</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>60. Amend § 75.580 is amended by removing the parenthetical authority citation.</AMDPAR>
                    <AMDPAR>61. Amend § 75.590 by:</AMDPAR>
                    <AMDPAR>a. Adding paragraph (c); and</AMDPAR>
                    <AMDPAR>b. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <P>The revision reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 75.590</SECTNO>
                        <SUBJECT>Grantee evaluations and reports.</SUBJECT>
                        <STARS/>
                        <P>(c) An application notice for a competition may require each grantee under that competition to do one or more of the following:</P>
                        <P>(1) Conduct an independent evaluation;</P>
                        <P>(2) Make public the final report, including results of any required independent evaluation;</P>
                        <P>(3) Ensure that the data from the independent evaluation are made available to third-party researchers consistent with applicable privacy requirements;</P>
                        <P>(4) Submit the final evaluation to the Education Resources Information Center (ERIC), which is administered by the Institute of Education Sciences; or</P>
                        <P>(5) Submit the final performance report under the grant to ERIC.</P>
                    </SECTION>
                    <AMDPAR>62. Revise § 75.591 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.591</SECTNO>
                        <SUBJECT>Federal evaluation; cooperation by a grantee.</SUBJECT>
                        <P>
                            A grantee must cooperate in any evaluation of the program by the Secretary, in accordance with program 
                            <PRTPAGE P="2017"/>
                            statute. If requested by the Secretary, a grantee must—
                        </P>
                        <P>(a) Cooperate with the collection of information, including from all or a subset of subgrantees and potential project beneficiaries, including both participants and non-participants, through surveys, observations, administrative records, or other data collection and analysis methods. This information collection may include program characteristics, including uses of program funds, as well as beneficiary characteristics, participation, and outcomes; and</P>
                        <P>(b) If required by the Secretary, pilot its Department-funded activities with a subset of subgrantees, potential project beneficiaries, or eligible participants and allow the Department or its agent to randomly select the subset for the purpose of providing a basis for an experimental evaluation that could meet What Works Clearinghouse standards, with or without reservations.</P>
                    </SECTION>
                    <AMDPAR>63. Revise § 75.600 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.600</SECTNO>
                        <SUBJECT>Applicability of using grant funds for construction or real property.</SUBJECT>
                        <P>(a) As used in this section, the terms “construction” and “minor remodeling” have the meanings given those terms in 34 CFR 77.1(c).</P>
                        <P>(b) Except as provided in paragraph (c) of this section, §§ 75.600 through 75.618 apply to:</P>
                        <P>(1) An applicant that requests funds for construction or real property; and</P>
                        <P>(2) A grantee whose grant includes funds for construction or real property.</P>
                        <P>(c) Sections 75.600 through 75.618 do not apply to grantees in—</P>
                        <P>(1) Programs prohibited from using funds for construction or real property under § 75.533; and</P>
                        <P>(2) Projects determined by the Secretary to be minor remodeling under 34 CFR 77.1(c).</P>
                    </SECTION>
                    <AMDPAR>64. Revise § 75.601 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.601</SECTNO>
                        <SUBJECT>Approval of the construction.</SUBJECT>
                        <P>(a) The Secretary approves a direct grantee construction project—</P>
                        <P>(1) When the initial grant application is approved; or</P>
                        <P>(2) After the grant has been awarded.</P>
                        <P>(b) A grantee may not advertise or place the construction project on the market for bidding until after the Secretary has made a determination on the specifications of the project.</P>
                    </SECTION>
                    <AMDPAR>65. Revise § 75.602 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.602</SECTNO>
                        <SUBJECT>Planning the construction.</SUBJECT>
                        <P>(a) In planning the construction project, a grantee—</P>
                        <P>(1) Must ensure that the design is functional, economical, and not elaborate in design or extravagant in the use of materials compared with facilities of a similar type constructed in the State or other applicable geographic area.</P>
                        <P>(2) May consider excellence of architecture and design and inclusion of works of art. A grantee must not spend more than 1 percent of the cost of the project on works of art.</P>
                        <P>(3) May make reasonable provision, consistent with the other uses to be made of the construction, for areas that are adaptable for artistic and other cultural activities.</P>
                        <P>(b) In developing the proposed budget for the construction project, a grantee—</P>
                        <P>(1) Must ensure that sufficient funds are available to meet any non-Federal share of the cost of the construction project.</P>
                        <P>(2) May budget for reasonable and predictable contingency costs consistent with 2 CFR 200.433.</P>
                        <P>(c) Prior to providing approval of the final working specifications of a construction project under § 75.601, the Secretary considers a grantee's compliance with the following requirements, as applicable—</P>
                        <P>(1) Title to site (§ 75.610).</P>
                        <P>(2) Environmental impact assessment (§ 75.611).</P>
                        <P>(3) Avoidance of flood hazards (§ 75.612).</P>
                        <P>(4) Compliance with the Coastal Barrier Resources Act (§ 75.613).</P>
                        <P>(5) Preservation of historic sites (§ 75.614).</P>
                        <P>(6) Build America, Buy America Act (§ 75.615).</P>
                        <P>(7) Energy conservation (§ 75.616).</P>
                        <P>(8) Access for individuals with disabilities (§ 75.617).</P>
                        <P>(9) Safety and health standards (§ 75.618).</P>
                    </SECTION>
                    <AMDPAR>66. Revise § 75.603 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.603</SECTNO>
                        <SUBJECT>Beginning the construction.</SUBJECT>
                        <P>(a) A grantee must begin work on the construction project within a reasonable time after the Secretary has approved the project under § 75.601.</P>
                        <P>(b) A grantee must follow all applicable procurement standards in 2 CFR part 200, subpart D, when advertising or placing the project on the market for bidding.</P>
                    </SECTION>
                    <AMDPAR>67. Revise § 75.604 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.604</SECTNO>
                        <SUBJECT>During the construction.</SUBJECT>
                        <P>(a) A grantee must maintain competent architectural engineering supervision and inspection at the construction site to ensure that the work conforms to the approved final working specifications.</P>
                        <P>(b) A grantee must complete the construction in accordance with the approved final working specifications unless a revision is approved.</P>
                        <P>(c) If a revision to the timeline, budget, or approved final working specifications is required, the grantee must request prior written approval consistent with 2 CFR 200.308(h).</P>
                        <P>(d) A grantee must comply with Federal laws regarding prevailing wages on construction and minor remodeling projects assisted with Department funding, including, as applicable, subchapter IV of chapter 31 of title 40, United States Code (commonly known as the “Davis-Bacon Act”; as applied through section 439 of GEPA; 20 U.S.C. 1232b) and any tribally determined prevailing wages.</P>
                        <P>(e) A grantee must submit periodic performance reports regarding the construction project containing information specified by the Secretary consistent with 2 CFR 200.329(d).</P>
                    </SECTION>
                    <AMDPAR>68. Revise § 75.605 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.605</SECTNO>
                        <SUBJECT>After the construction.</SUBJECT>
                        <P>(a) A grantee must ensure that sufficient funds will be available for effective operation and maintenance of the facilities after the construction is complete.</P>
                        <P>(b) A grantee must operate and maintain the facilities in accordance with applicable Federal, State, and local requirements.</P>
                        <P>(c) A grantee must maintain all financial records, supporting documents, statistical records, and other non-Federal entity records pertinent to the construction project consistent with 2 CFR 200.334.</P>
                    </SECTION>
                    <AMDPAR>69. Revise § 75.606 is revised to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.606</SECTNO>
                        <SUBJECT>Real property requirements.</SUBJECT>
                        <P>(a) The Secretary approves a direct grantee real property project—</P>
                        <P>(1) When the initial grant application is approved;</P>
                        <P>(2) After the grant has been awarded; or</P>
                        <P>(3) With the approval of a construction project under § 75.601.</P>
                        <P>(b) A grantee using any grant funds for real property acquisition must:</P>
                        <P>(1) Comply with the Real Property Standards of the Uniform Guidance (2 CFR 200.310 through 200.316).</P>
                        <P>(2) Not dispose of, modify the use of, or change the terms of the real property title, or other interest in the site and facilities without written permission and instructions from the Secretary.</P>
                        <P>(3) Record the Federal interest in the title of the real property in the official real property records for the jurisdiction in which the facility is located.</P>
                        <P>(4) Include a covenant in the title of the real property to ensure nondiscrimination.</P>
                        <P>
                            (5) Report at least annually on the status of real property in which the 
                            <PRTPAGE P="2018"/>
                            Federal Government retains an interest consistent with 2 CFR 200.330.
                        </P>
                        <P>(c) A grantee is subject to the regulations on relocation assistance and real property acquisition in 34 CFR part 15 and 49 CFR part 24, as applicable</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 75.607 through 75.609</SECTNO>
                        <SUBJECT>[Removed and Reserved]</SUBJECT>
                    </SECTION>
                    <AMDPAR>70. Remove and reserve §§ 75.607 through 75.609.</AMDPAR>
                    <AMDPAR>71. Revise § 75.610 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.610</SECTNO>
                        <SUBJECT>Title to site.</SUBJECT>
                        <P>A grantee must have or obtain a full title or other interest in the site (such as a long-term lease), including right of access, that is sufficient to ensure the grantee's undisturbed use and possession of the facilities for at least 25 years after completion of the project or for the useful life of the construction, whichever is longer.</P>
                    </SECTION>
                    <AMDPAR>72. Revise § 75.611 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.611</SECTNO>
                        <SUBJECT>Environmental impact assessment.</SUBJECT>
                        <P>(a) When a grantee's construction or real property project is considered a “Major Federal Action,” as defined in 40 CFR 1508.1(q), the grantee must include an assessment of the impact of the proposed construction on the quality of the environment in accordance with section 102(2)(C) of the National Environmental Policy Act of 1969 (NEPA) (42 U.S.C. 4332(2)(C)) and Executive Order 11514 (35 FR 4247).</P>
                        <P>(b) If a grantee's construction or real property project is not considered a “Major Federal Action” under NEPA, a NEPA environmental impact assessment is not required; however—</P>
                        <P>(1) An environmental impact assessment may be required under State or local requirements; and</P>
                        <P>(2) Grantees are encouraged to perform some type of environmental assessment for projects that involve breaking ground, such as projects to expand the size of an existing building or replace an outdated building.</P>
                    </SECTION>
                    <AMDPAR>73. Revise § 75.612 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.612</SECTNO>
                        <SUBJECT>Avoidance of flood hazards.</SUBJECT>
                        <P>In planning the construction or real property project, a grantee must, in accordance with Executive Order 11988 of May 24, 1977 (3 CFR, 1978 Comp., pp. 117-120):</P>
                        <P>(a) Evaluate flood hazards in connection with the construction; and</P>
                        <P>(b) As far as practicable, avoid uneconomic, hazardous, or unnecessary use of flood plains in connection with the construction.</P>
                    </SECTION>
                    <AMDPAR>74. Revise § 75.613 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.613</SECTNO>
                        <SUBJECT>Compliance with the Coastal Barrier Resources Act.</SUBJECT>
                        <P>A grantee may not use, within the Coastal Barrier Resources System, funds made available under a program administered by the Secretary for any purpose prohibited by the Coastal Barrier Resources Act (16 U.S.C. 3501-3510).</P>
                    </SECTION>
                    <AMDPAR>75. Revise § 75.614 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.614</SECTNO>
                        <SUBJECT>Preservation of historic sites.</SUBJECT>
                        <P>(a) A grantee must describe the relationship of the proposed construction to, and probable effect on, any district, site, building, structure, or object that is:</P>
                        <P>(1) Included in the National Register of Historic Places; or</P>
                        <P>(2) Eligible under criteria established by the Secretary of the Interior for inclusion in the National Register of Historic Places.</P>
                        <P>(b) In deciding whether to approve a construction project, the Secretary considers:</P>
                        <P>(1) The information provided by the applicant under paragraph (a) of this section; and</P>
                        <P>(2) Any comments received by the Advisory Council on Historic Preservation (see 36 CFR subpart 800.2).</P>
                    </SECTION>
                    <AMDPAR>76. Revise § 75.615 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.615</SECTNO>
                        <SUBJECT>Build America, Buy America Act.</SUBJECT>
                        <P>A grantee must comply with the requirements of the Build America, Buy America Act, Public Law 117-58, § 70901-70927 and implementing regulations, as applicable.</P>
                    </SECTION>
                    <AMDPAR>77. Revise § 76.616 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.616</SECTNO>
                        <SUBJECT>Energy conservation.</SUBJECT>
                        <P>(a) To the extent practicable, a grantee must design and construct facilities to maximize the efficient use of energy.</P>
                        <P>(b) A grantee must comply with ASHRAE 90.1 in their construction project.</P>
                        <P>
                            (c) ASHRAE 90.1, Energy Standard for Sites and Buildings Except Low-Rise Residential Buildings, 2022 is incorporated by reference into this section with the approval of the Director of the Federal Register under 5 U.S.C. 552(a) and 1 CFR part 51. This material is available for inspection at the Department of Education (the Department) and at the National Archives and Records Administration (NARA). Contact the Department at: Department of Education, 400 Maryland Avenue SW, Room 4C212, Washington, DC 20202-8472; phone: 202-245-6776; email: 
                            <E T="03">EDGAR@ed.gov.</E>
                             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>
                             The material may be obtained from the American Society of Heating, Refrigerating, and Air Conditioning Engineers (ASHRAE) at American Society of Heating, Refrigerating, and Air Conditioning Engineers, Inc., 1791 Tullie Circle NE, Atlanta, Georgia 30329; 
                            <E T="03">www.ashrae.org.</E>
                        </P>
                    </SECTION>
                    <AMDPAR>78. Revise § 75.617 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.617</SECTNO>
                        <SUBJECT>Access for individuals with disabilities.</SUBJECT>
                        <P>A grantee must comply with the following Federal regulations on access by individuals with disabilities that apply to the construction of facilities:</P>
                        <P>(a) For residential facilities: 24 CFR part 40; and</P>
                        <P>(b) For non-residential facilities: 41 CFR 102-76.60 to 102-76.95.</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 75.618</SECTNO>
                        <SUBJECT>[Redesignated as § 75.619]</SUBJECT>
                    </SECTION>
                    <AMDPAR>79. Redesignate § 75.618 as § 75.619.</AMDPAR>
                    <AMDPAR>80. Add new § 75.618 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.618</SECTNO>
                        <SUBJECT>Safety and health standards.</SUBJECT>
                        <P>In planning for and designing a construction project, a grantee must comply with the following:</P>
                        <P>(a) The standards under the Occupational Safety and Health Act of 1970 (See 29 CFR part 1910); and</P>
                        <P>(b) State and local codes, to the extent that they are more stringent.</P>
                    </SECTION>
                    <AMDPAR>81. Revise § 75.620 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.620</SECTNO>
                        <SUBJECT>General conditions on publication.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Content of materials.</E>
                             Subject to any specific requirements that apply to its grant, a grantee may decide the format and content of project materials that it publishes or arranges to have published.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Required statement.</E>
                             The grantee must ensure that any publication that contains project materials also contains the following statement:
                        </P>
                        <P>
                            The contents of this [insert type of publication; such as book, report, film, website, and web page] were developed under a grant from the U.S. Department of Education (Department). The Department does not mandate or prescribe practices, models, or other activities described or discussed in this document. The contents of this [insert type of publication] may contain examples of, adaptations of, and links to resources created and maintained by another public or private organization. The Department does not control or guarantee the accuracy, relevance, timeliness, or completeness of this outside information. The content of this [insert type of publication] does not necessarily represent the policy of the Department. This publication is not intended to represent the views or policy of, or be an endorsement of any 
                            <PRTPAGE P="2019"/>
                            views expressed or materials provided by, any Federal agency.
                        </P>
                    </SECTION>
                    <AMDPAR>82. Revise § 75.622 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.622</SECTNO>
                        <SUBJECT>Definition of “project materials.”</SUBJECT>
                        <P>As used in §§ 75.620 through 75.621, “project materials” means a copyrightable work developed with funds from a grant of the Department. (See 2 CFR 200.307 and 200.315.)</P>
                    </SECTION>
                    <AMDPAR>83. Add § 75.623 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.623</SECTNO>
                        <SUBJECT>Public availability of grant-supported research publications.</SUBJECT>
                        <P>(a) Grantees must make final peer-reviewed scholarly publications resulting from research supported by Department grants available to the Education Resources Information Center (ERIC), which is administered by the Institute of Education Sciences, upon acceptance for publication.</P>
                        <P>(b) A final, peer-reviewed scholarly publication is the final version accepted for publication and includes all edits made as part of the peer review process, as well as all graphics and supplemental materials that are associated with the article.</P>
                        <P>(c) The Department will make the final, peer-reviewed scholarly publication available to the public through ERIC no later than 12 months after the official date of publication.</P>
                        <P>(d) Grantees are responsible for ensuring that any publishing or copyright agreements concerning submitted articles fully comply with this section.</P>
                    </SECTION>
                    <AMDPAR>84. Remove the cross-reference under the heading “Inventions and Patents” before § 75.626.</AMDPAR>
                    <AMDPAR>85. Amend § 75.626 by:</AMDPAR>
                    <AMDPAR>a. Revising the section heading; and</AMDPAR>
                    <AMDPAR>b. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <P>The revision reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 75.626</SECTNO>
                        <SUBJECT>Show Federal support.</SUBJECT>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>86. Revise § 75.650 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.650</SECTNO>
                        <SUBJECT>Participation of students enrolled in private schools.</SUBJECT>
                        <P>If applicable statutes and regulations provide for participation of students enrolled in private schools and, as applicable, their teachers or other educational personnel, and their families, the grantee must provide, as applicable, services in accordance with §§ 299.7 through 299.11.</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 75.682</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>87. Amend § 75.682 by:</AMDPAR>
                    <AMDPAR>a. Removing the word “shall” and adding in its place the word “must”;</AMDPAR>
                    <AMDPAR>b. Removing the words “of 1970” after the words “Animal Welfare Act”; and</AMDPAR>
                    <AMDPAR>c. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <AMDPAR>88. Revise § 75.700 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.700</SECTNO>
                        <SUBJECT>Compliance with the U.S. Constitution, statutes, regulations, stated institutional policies, and applications.</SUBJECT>
                        <P>A grantee must comply with § 75.500, applicable statutes, regulations, Executive orders, stated institutional policies, and applications, and must use Federal funds in accordance with the U.S. Constitution and those statutes, regulations, Executive orders, stated institutional policies, and applications.</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 75.702</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>89. Amend § 75.702 by removing the word “insure” and adding in its place the word “ensure”.</AMDPAR>
                    <AMDPAR>90. Amend § 75.708 by:</AMDPAR>
                    <AMDPAR>a. Revising paragraph (b) introductory text;</AMDPAR>
                    <AMDPAR>b. In paragraph (d)(2), removing the words “Federal statute and executive orders and their implementing regulations” and adding in their place the words “applicable law”;</AMDPAR>
                    <AMDPAR>c. In paragraph (d)(3), removing the word “anti-discrimination” and adding in its place the word “nondiscrimination”;</AMDPAR>
                    <AMDPAR>d. Revising paragraph (e); and</AMDPAR>
                    <AMDPAR>e. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <P>The revisions reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 75.708</SECTNO>
                        <SUBJECT>Subgrants.</SUBJECT>
                        <STARS/>
                        <P>
                            (b) The Secretary may, through an announcement in the 
                            <E T="04">Federal Register</E>
                             or other reasonable means of notice, authorize subgrants when necessary to meet the purposes of a program. In this announcement, the Secretary will—
                        </P>
                        <STARS/>
                        <P>(e) Grantees that are not allowed to make subgrants under paragraph (b) of this section are authorized to contract, as needed, for supplies, equipment, and other services, in accordance with 2 CFR part 200, subpart D (2 CFR 200.317 through 200.326).</P>
                    </SECTION>
                    <AMDPAR>91. Amend § 75.720 by:</AMDPAR>
                    <AMDPAR>a. In paragraph (a)(1), removing the citation “2 CFR 200.327” and adding in its place the citation “2 CFR 200.328”;</AMDPAR>
                    <AMDPAR>b. In paragraph (a)(2), removing the citation “2 CFR 200.328” and adding in its place the citation “2 CFR 200.329”;</AMDPAR>
                    <AMDPAR>c. Adding paragraph (d); and</AMDPAR>
                    <AMDPAR>d. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <P>The addition reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 75.720</SECTNO>
                        <SUBJECT>Financial and performance reports.</SUBJECT>
                        <STARS/>
                        <P>(d) Upon request of the Secretary, a grantee shall, at the time of submission to the Secretary, post any report on performance and financial expenditure required by this section on a public-facing website maintained by the grantee.</P>
                    </SECTION>
                    <AMDPAR>92. Amend § 75.740 by:</AMDPAR>
                    <AMDPAR>a. In paragraph (a), revising the parenthetical sentence at the end;</AMDPAR>
                    <AMDPAR>b. In paragraph (b), adding ” ; 20 U.S.C. 1232h, commonly known as the “Protection of Pupil Rights Amendment” or “PPRA”; and the Common Rule for the protection of Human Subjects and its implementing regulations at 34 CFR part 97, as applicable” ” after the word “GEPA and its implementing regulations at 34 CFR part 98”; and</AMDPAR>
                    <AMDPAR>c. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <P>The revision reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 75.740</SECTNO>
                        <SUBJECT>Protection of and access to student records; student rights in research, experimental programs, and testing.</SUBJECT>
                        <P>* * * (Section 444 of GEPA (20 U.S.C. 1232g) is commonly referred to as the “Family Educational Rights and Privacy Act of 1974” or “FERPA”.)</P>
                        <STARS/>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 75.900</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>93. Amend § 75.900 by removing “ED” in paragraphs (a) and (b) and adding in its place the words “the Department”.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 75.901</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>94. Amend § 75.901 by:</AMDPAR>
                    <AMDPAR>a. In the introductory text, removing the words “that are not subject to other procedures”; and</AMDPAR>
                    <AMDPAR>b. Removing the parenthetical authority citation from the end of the section.</AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 76—STATE-ADMINISTERED FORMULA GRANT PROGRAMS</HD>
                    </PART>
                    <AMDPAR>95. The authority citation for part 76 is revised to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">AUTHORITY:</HD>
                        <P> 20 U.S.C. 1221e-3 and 3474, unless otherwise noted.</P>
                    </AUTH>
                    <EXTRACT>
                        <P>Section 76.101 also issued under 20 U.S.C. 1221e-3, 3474, and 7844(b).</P>
                        <P>Section 76.127 also issued under 48 U.S.C. 1469a.</P>
                        <P>Section 76.128 also issued under 48 U.S.C. 1469a.</P>
                        <P>Section 76.129 also issued under 48 U.S.C. 1469a.</P>
                        <P>Section 76.130 also issued under 48 U.S.C. 1469a.</P>
                        <P>Section 76.131 also issued under 48 U.S.C. 1469a.</P>
                        <P>Section 76.132 also issued under 48 U.S.C. 1469a.</P>
                        <P>
                            Section 76.134 also issued under 48 U.S.C. 1469a.
                            <PRTPAGE P="2020"/>
                        </P>
                        <P>Section 76.136 also issued under 48 U.S.C. 1469a.</P>
                        <P>Section 76.140 also issued under 20 U.S.C. 1221e-3, 1231g(a), and 3474.</P>
                        <P>Section 76.301 also issued under 1221e-3, 3474, and 7846(b).</P>
                        <P>Section 76.401 also issued under 20 U.S.C. 1221e-3, 1231b-2, and 3474.</P>
                        <P>Section 76.709 also issued under 20 U.S.C. 1221e-3, 1225(b), and 3474.</P>
                        <P>Section 76.710 also issued under 20 U.S.C. 1221e-3, 1225(b), and 3474.</P>
                        <P>Section 76.720 also issued under 20 U.S.C. 1221e-3, 1231a, and 3474.</P>
                        <P>Section 76.740 also issued under 20 U.S.C. 1221e-3, 1232g, 1232h, and 3474.</P>
                        <P>Section 76.783 also issued under 20 U.S.C. 1231b-2.</P>
                        <P>Section 76.785 also issued under 20 U.S.C. 7221e.</P>
                        <P>Section 76.786 also issued under 20 U.S.C. 7221e</P>
                        <P>Section 76.787 also issued under 20 U.S.C. 7221e.</P>
                        <P>Section 76.788 also issued under 20 U.S.C. 7221e.</P>
                        <P>Section 76.901 also issued under 20 U.S.C. 1234.</P>
                    </EXTRACT>
                    <AMDPAR>96. The part heading for part 76 is revised to read as set forth above.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.1</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>97. Revise § 76.1 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.1</SECTNO>
                        <SUBJECT>Programs to which this part applies.</SUBJECT>
                        <P>(a) The regulations in this part apply to each State-administered formula grant program of the Department.</P>
                        <P>(b) If a State-administered formula grant program does not have implementing regulations, the Secretary implements the program under the applicable statutes and, to the extent consistent with the authorizing statute, under the GEPA and the regulations in this part. For the purposes of this part, the term State-administered formula grant program means a program whose applicable statutes or implementing regulations provide a formula for allocating program funds among eligible States.</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 76.2</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>98. Amend § 76.2 by removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <AMDPAR>99. Revise § 76.50 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.50</SECTNO>
                        <SUBJECT>Basic requirements for subgrants.</SUBJECT>
                        <P>(a) Under a program covered by this part, the Secretary makes a grant—</P>
                        <P>(1) To the State agency designated by applicable statutes and regulations for the program; or</P>
                        <P>(2) To the State agency designated by the State in accordance with applicable statutes and regulations.</P>
                        <P>(b) Unless prohibited by applicable statutes or regulations or by the terms and conditions of the grant award, a State may use State-administered formula grant funds—</P>
                        <P>(1) Directly;</P>
                        <P>(2) To make subgrants to eligible applicants; or</P>
                        <P>(3) To authorize a subgrantee to make subgrants.</P>
                        <P>(c) Grantees are responsible for monitoring subgrantees consistent with 2 CFR 200.332.</P>
                        <P>(d) Grantees, in cases where subgrants are prohibited by applicable statutes or regulations or the conditions of a grant award, are authorized to contract, as needed, for supplies, equipment, and other services, in accordance with 2 CFR part 200, subpart D (2 CFR 200.317 through 200.326).</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 76.51</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>100. Amend § 76.51 by:</AMDPAR>
                    <AMDPAR>a. In the introductory text, removing the words “a program statute authorizes” and adding in their place “applicable statutes and regulations authorize”; and</AMDPAR>
                    <AMDPAR>b. Removing the parenthetical citation authority at the end of the section.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.52</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>101. Amend § 76.52 by:</AMDPAR>
                    <AMDPAR>a. In paragraphs (a)(3) and (4), (b), (c)(1), and (d)(1) and (2), removing the words “State-Administered Formula Grant” and adding in their place “State-administered formula grant”; and</AMDPAR>
                    <AMDPAR>b. In paragraph (e), adding the word “Federal” between the words “indirect” and “financial assistance”.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.100</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>102. Amend § 76.100 by removing the words “the authorizing statute and implementing regulations” and adding in their place the words “applicable statutes and regulations”.</AMDPAR>
                    <AMDPAR>103. Revise § 76.101 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.101</SECTNO>
                        <SUBJECT>State plans in general.</SUBJECT>
                        <P>(a) Except as provided in paragraph (b) of this section, a State that makes subgrants to local educational agencies under a program subject to this part must have on file with the Secretary a State plan that meets the requirements of section 441 of GEPA (20 U.S.C. 1232d).</P>
                        <P>(b) The requirements of section 441 of GEPA do not apply to a State plan submitted for a program under the Elementary and Secondary Education Act of 1965.</P>
                    </SECTION>
                    <AMDPAR>104. Revise § 76.102 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.102</SECTNO>
                        <SUBJECT>Definition of “State plan” for this part.</SUBJECT>
                        <P>
                            As used in this part, 
                            <E T="03">State plan</E>
                             means any document that applicable statutes and regulations for a State-administered formula grant program require a State to submit in order to receive funds for the program. To the extent that any provision of this part conflicts with program-specific implementing regulations related to the plan, the program-specific implementing regulations govern.
                        </P>
                    </SECTION>
                    <AMDPAR>105. Revise § 76.103 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.103</SECTNO>
                        <SUBJECT>Multiyear State plans.</SUBJECT>
                        <P>Unless otherwise specified by statute, regulations, or the Secretary, each State plan is effective for a period of more than one fiscal year, to be determined by the Secretary or by regulations.</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 76.125</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>106. Amend § 76.125 by:</AMDPAR>
                    <AMDPAR>a. In paragraph (b), removing “the Trust Territory of the Pacific Islands,”;</AMDPAR>
                    <AMDPAR>b. In paragraph (c), adding “, consistent with applicable law” after the word “Department”; and</AMDPAR>
                    <AMDPAR>c. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.127</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>107. Amend § 76.127 by:</AMDPAR>
                    <AMDPAR>a. In the introductory text, removing the words “of the programs listed in § 76.125(c)” and adding in their place the words “State-administered formula grant programs”; and</AMDPAR>
                    <AMDPAR>b. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <AMDPAR>108. Amend § 76.128 by:</AMDPAR>
                    <AMDPAR>a. Removing the words “of the programs listed in § 76.125(c)” and adding in their place the words “State-administered formula grant programs”;</AMDPAR>
                    <AMDPAR>b. Revising the example at the end of the section; and</AMDPAR>
                    <AMDPAR>c. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <P>The revision reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 76.128</SECTNO>
                        <SUBJECT>What is a consolidated grant?</SUBJECT>
                        <STARS/>
                        <P>
                            <E T="03">Example 1 to § 76.128.</E>
                             Assume the Virgin Islands applies for a consolidated grant that includes funds under the Carl D. Perkins Career and Technical Education Act of 2006 and title I, part A; title II, part A; and title IV, part A of the Elementary and Secondary Education Act of 1965. If the Virgin Islands' allocation under the formula for each of these four programs is $150,000, the total consolidated grant to the Virgin Islands would be $600,000.
                        </P>
                    </SECTION>
                    <AMDPAR>109. Amend § 76.129 by:</AMDPAR>
                    <AMDPAR>
                        a. Revising the example after paragraph (a) and the example after paragraph (b).
                        <PRTPAGE P="2021"/>
                    </AMDPAR>
                    <AMDPAR>b. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <P>The revisions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 76.129</SECTNO>
                        <SUBJECT>How does a consolidated grant work?</SUBJECT>
                        <P>(a) * * *</P>
                        <P>
                            <E T="03">Example 1 to paragraph (a).</E>
                             Assume that Guam receives, under the consolidated grant, funds from Carl D. Perkins Career and Technical Education Act of 2006, Title I, part A of the ESEA, and Title IV, part A of the ESEA. The sum of the allocations under these programs is $600,000. Guam may choose to allocate this $600,000 among one, two, or all three of the programs.
                        </P>
                        <P>(b) * * *</P>
                        <P>
                            <E T="03">Example 2 to paragraph (b).</E>
                             Assume that American Samoa uses part of the funds under a consolidated grant to carry out programs and activities under Title IV, part A of the ESEA. American Samoa need not submit to the Secretary a State plan that addresses the program's application requirement that the State educational agency describe how it will use funds for State-level activities. However, in carrying out the program, American Samoa must use the required amount of funds for State-level activities under the program.
                        </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 76.130</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>110. Amend § 76.130 by:</AMDPAR>
                    <AMDPAR>a. Removing in paragraph (d) the words “statute and regulations for that program” and adding in their place the words “statutes and regulations that apply to that program”; and</AMDPAR>
                    <AMDPAR>b. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.131</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>111. Amend § 76.131 by:</AMDPAR>
                    <AMDPAR>a. In paragraph (a), removing the words “programs listed in § 76.125(c)” and adding in their place the words “State-administered formula grant programs”;</AMDPAR>
                    <AMDPAR>b. In paragraph (b), removing the words “the authorizing statutes and regulations” and adding in their place the words “applicable statutes and regulations”;</AMDPAR>
                    <AMDPAR>c. In paragraph (c)(1), removing the words “programs in § 76.125(c)” and adding in their place the words “State-administered formula grant programs”;</AMDPAR>
                    <AMDPAR>c. In paragraph (c)(2), removing the words “program or programs in § 76.125(c)” and adding in their place the words “State-administered formula grant programs”; and</AMDPAR>
                    <AMDPAR>d. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.132</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>112. Amend § 76.132 by:</AMDPAR>
                    <AMDPAR>a. In paragraphs (a)(2),removing the word “authorizing” and adding in its place the word “applicable”;</AMDPAR>
                    <AMDPAR>b. In paragraph (a)(4), removing the word “assure” and adding in its place the word “ensure”;</AMDPAR>
                    <AMDPAR>c. In paragraph (a)(5), removing the phrase “2 CFR 200.327 and 200.328” and adding in its place “2 CFR 200.328 and 200.329”;</AMDPAR>
                    <AMDPAR>d. In paragraph (a)(9),removing the word “authorizing” and adding in its place the word “applicable”; and</AMDPAR>
                    <AMDPAR>e. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <AMDPAR>113. Amend § 76.134 by:</AMDPAR>
                    <AMDPAR>a. Revising paragraph (a);</AMDPAR>
                    <AMDPAR>b. In paragraph (b), removing the words “the program statute” and adding in their place the words “applicable statutes”; and</AMDPAR>
                    <AMDPAR>c. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <P>The revision reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 76.134</SECTNO>
                        <SUBJECT>What is the relationship between consolidated and non-consolidated grants?</SUBJECT>
                        <P>(a) An Insular Area may request that any State-administered formula grant programs be included in its consolidated grant and may apply separately for assistance under any other of those programs for which it is eligible.</P>
                        <STARS/>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 76.136</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>114. Amend § 76.136 by:</AMDPAR>
                    <AMDPAR>a. Removing the words “programs described in § 76.125(c)” and adding in their place the words “State-administered formula grant programs”; and</AMDPAR>
                    <AMDPAR>b. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <AMDPAR>115. Revise § 76.140 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.140</SECTNO>
                        <SUBJECT>Amendments to a State plan.</SUBJECT>
                        <P>(a) If the Secretary determines that an amendment to a State plan is essential during the effective period of the plan, the State must make the amendment.</P>
                        <P>(b) A State must also amend a State plan if there is a significant and relevant change in the information or the assurances in the plan.</P>
                        <P>(c) If a State amends a State plan, to the extent consistent with applicable law, the State must use the same procedures as those it must use to prepare and submit a State plan, unless the Secretary prescribes different procedures based on the characteristics of a particular State-administered formula grant program.</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§§ 76.141 and 76.142</SECTNO>
                        <SUBJECT>[Removed and Reserved]</SUBJECT>
                    </SECTION>
                    <AMDPAR>116. Remove and reserve §§ 76.141 and 76.142.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.260</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>117. Amend § 76.260 by:</AMDPAR>
                    <AMDPAR>a. In the section heading, removing the words “program statute” and adding in their place the words “applicable statutes”.</AMDPAR>
                    <AMDPAR>b. Removing the words “the authorizing statute” wherever they appear and adding in their place the words “applicable statutes”.</AMDPAR>
                    <AMDPAR>118. Revise § 76.301 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.301</SECTNO>
                        <SUBJECT>Local educational agency application in general.</SUBJECT>
                        <P>(a) A local educational agency (LEA) that applies for a subgrant under a program subject to this part must have on file with the State an application that meets the requirements of section 442 of GEPA (20 U.S.C. 1232e).</P>
                        <P>(b) The requirements of section 442 of GEPA do not apply to an LEA's application for a program under the ESEA.</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 76.400</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>119. Amend § 76.400 in paragraphs (b)(2), (c)(2), and (d) by removing the words “Federal statutes” and adding in their place the words “applicable statutes”.</AMDPAR>
                    <AMDPAR>120. Revise § 76.401 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.401</SECTNO>
                        <SUBJECT>Disapproval of an application—opportunity for a hearing.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">State educational agency hearing regarding disapproval of an application.</E>
                             When financial assistance is provided to (or through) a State educational agency (SEA) consistent with an approved State plan and the SEA takes final action by disapproving or failing to approve an application for a subgrant in whole or in part, the SEA must provide the aggrieved applicant with notice and an opportunity for a hearing regarding the SEA's disapproval or failure to approve the application.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Applicant request for SEA hearing.</E>
                             (1) The aggrieved applicant must request a hearing within 30 days of the final action of the SEA.
                        </P>
                        <P>
                            (2) The aggrieved applicant's request for a hearing must include, at a minimum, a citation to the specific State or Federal statute, rule, regulation, or guideline that the SEA allegedly violated when disapproving or failing to approve the application in whole or in part and a brief description of the alleged violation.
                            <PRTPAGE P="2022"/>
                        </P>
                        <P>(3) The SEA must make available, at reasonable times and places to each applicant, all records of the SEA pertaining to the SEA's failure to approve the application in whole or in part that is the subject of the applicant's request for a hearing under this paragraph (b).</P>
                        <P>
                            (c) 
                            <E T="03">SEA hearing procedures.</E>
                             (1) Within 30 days after it receives a request that meets the requirements of paragraphs (b)(1) and (2) of this section, the SEA must hold a hearing on the record to review its action.
                        </P>
                        <P>(2) No later than 10 days after the hearing, the SEA must issue its written ruling, including findings of fact and reasons for the ruling.</P>
                        <P>(3) If the SEA determines that its action was contrary to State or Federal statutes, rules, regulations, or guidelines that govern the applicable program, the SEA must rescind its action in whole or in part.</P>
                        <P>
                            (d) 
                            <E T="03">Procedures for appeal of SEA action to the Secretary.</E>
                             (1) If an SEA does not rescind its final action disapproving or failing to approve an application in whole or in part after the SEA conducts a hearing consistent with paragraph (c) of this section, the applicant may appeal the SEA's final action to the Secretary.
                        </P>
                        <P>(2) The applicant must file a notice of appeal with the Secretary within 20 days after the applicant has received the SEA's written ruling.</P>
                        <P>(3) The applicant's notice of appeal must include, at a minimum, a citation to the specific Federal statute, rule, regulation, or guideline that the SEA allegedly violated and a brief description of the alleged violation.</P>
                        <P>(4) The Secretary may issue interim orders at any time when considering the appeal, including requesting the hearing record and any additional documentation, such as additional documentation regarding the information provided pursuant to paragraph (d)(3) of this section.</P>
                        <P>(5) After considering the appeal, the Secretary issues an order either affirming the final action of the SEA or requiring the SEA to take appropriate action, if the Secretary determines that the final action of the SEA was contrary to a Federal statute, rule, regulation, or guideline that governs the applicable program.</P>
                        <P>
                            (e) 
                            <E T="03">Programs administered by State agencies other than an SEA.</E>
                             Under programs with an approved State plan under which financial assistance is provided to (or through) a State agency that is not the SEA, that State agency is not required to comply with this section unless specifically required to do so by Federal statute or regulation.
                        </P>
                    </SECTION>
                    <AMDPAR>121. Amend § 76.500 by revising paragraph (a) and removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <P>The revision reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 76.500</SECTNO>
                        <SUBJECT>Federal statutes and regulations on nondiscrimination.</SUBJECT>
                        <P>(a) A State and a subgrantee must comply with the following statutes and regulations:</P>
                        <GPOTABLE COLS="3" OPTS="L2,nj,i1" CDEF="s90,r100,xs66">
                            <TTITLE>
                                Table 1 to § 76.500(
                                <E T="01">a</E>
                                )
                            </TTITLE>
                            <BOXHD>
                                <CHED H="1">Subject</CHED>
                                <CHED H="1">Statute</CHED>
                                <CHED H="1">Regulation</CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">Discrimination on the basis of race, color, or national origin</ENT>
                                <ENT>
                                    Title VI of the Civil Rights Act of 1964 (42 U.S.C. 2000d 
                                    <E T="03">et seq.</E>
                                    )
                                </ENT>
                                <ENT>34 CFR part 100.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Discrimination on the basis of sex</ENT>
                                <ENT>
                                    Title IX of the Education Amendments of 1972 (20 U.S.C. 1681 
                                    <E T="03">et seq.</E>
                                    )
                                </ENT>
                                <ENT>34 CFR part 106.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Discrimination on the basis of disability</ENT>
                                <ENT>Section 504 of the Rehabilitation Act of 1973 (29 U.S.C. 794)</ENT>
                                <ENT>34 CFR part 104.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Discrimination on the basis of age</ENT>
                                <ENT>
                                    Age Discrimination Act of 1975 (42 U.S.C. 6101 
                                    <E T="03">et seq.</E>
                                    )
                                </ENT>
                                <ENT>34 CFR part 110.</ENT>
                            </ROW>
                        </GPOTABLE>
                        <STARS/>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 76.532</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>122. Amend § 76.532 by removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.533</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>123. Amend § 76.533 by:</AMDPAR>
                    <AMDPAR>a. Removing the words “the authorizing statute” and adding in their place the words “applicable statutes”; and</AMDPAR>
                    <AMDPAR>b. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <AMDPAR>124. Revise § 76.560 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.560</SECTNO>
                        <SUBJECT>General indirect cost rates and cost allocation plans; exceptions.</SUBJECT>
                        <P>(a) The differences between direct and indirect costs and the principles for determining the general indirect cost rate that a grantee may use for grants under most programs are specified in the cost principles for—</P>
                        <P>(1) All grantees, other than hospitals and commercial (for-profit) organizations, at 2 CFR part 200, subpart E;</P>
                        <P>(2) Hospitals, at 45 CFR part 75, appendix IX; and</P>
                        <P>(3) Commercial (for-profit) organizations, at 48 CFR part 31.</P>
                        <P>(b) Except as specified in paragraph (c) of this section, a grantee must have a current indirect cost rate agreement or approved cost allocation plan to charge indirect costs to a grant. To obtain a negotiated indirect cost rate agreement or approved cost allocation plan, a grantee must submit an indirect cost rate proposal or cost allocation plan to its cognizant agency.</P>
                        <P>
                            (c) A grantee that meets the requirements in 2 CFR 200.414(f) may elect to charge the 
                            <E T="03">de minimis</E>
                             rate of modified total direct costs (MTDC) specified in that provision, which may be used indefinitely. The 
                            <E T="03">de minimis</E>
                             rate may not be used on programs that have statutory or regulatory restrictions on the indirect cost rate. No documentation is required to justify the 
                            <E T="03">de minimis</E>
                             rate.
                        </P>
                        <P>(1) If the grantee has established a threshold for equipment that is lower than the amount specified in the Uniform Guidance, the grantee must use that threshold to exclude equipment from the MTDC base.</P>
                        <P>(2) For purposes of the MTDC base and application of the 10 percent rate, MTDC includes up to the amount specified in the definition of MTDC in the Uniform Guidance of each subaward, each year.</P>
                        <P>(d) If a grantee is required to, but does not, have a federally recognized indirect cost rate or approved cost allocation plan, the Secretary may permit the grantee to charge a temporary indirect cost rate of 10 percent of budgeted direct salaries and wages.</P>
                        <P>(e)(1) If a grantee fails to submit an indirect cost rate proposal or cost allocation plan to its cognizant agency within the required 90 days, the grantee may not charge indirect costs to its grant from the end of the 90-day period until it obtains a federally recognized indirect cost rate agreement applicable to the grant.</P>
                        <P>
                            (2) If the Secretary determines that exceptional circumstances warrant continuation of a temporary indirect cost rate, the Secretary may authorize 
                            <PRTPAGE P="2023"/>
                            the grantee to continue charging indirect costs to its grant at the temporary rate specified in paragraph (d) of this section even though the grantee has not submitted its indirect cost rate proposal within the 90-day period.
                        </P>
                        <P>(3) Once a grantee obtains a federally recognized indirect cost rate that is applicable to the affected grant, the grantee may use that indirect cost rate to claim indirect cost reimbursement for expenditures made on or after the date on which the grantee submitted its indirect cost proposal to its cognizant agency or the start of the project period, whichever is later. However, this authority is subject to the following limitations:</P>
                        <P>(i) The total amount of funds recovered by the grantee under the federally recognized indirect cost rate is reduced by the amount of indirect costs previously recovered under the temporary indirect cost rate specified in paragraph (d) of this section.</P>
                        <P>(ii) The grantee must obtain prior approval from the Secretary to shift direct costs to indirect costs in order to recover indirect costs at a higher negotiated indirect cost rate.</P>
                        <P>(iii) The grantee may not request additional funds to recover indirect costs that it cannot recover by shifting direct costs to indirect costs.</P>
                        <P>(f) The Secretary accepts a negotiated indirect cost rate or approved cost allocation plan but may establish a restricted indirect cost rate or cost allocation plan compliant with §§ 76.564 through 76.569 for a grantee to satisfy the statutory requirements of certain programs administered by the Department.</P>
                    </SECTION>
                    <AMDPAR>125. Revise § 76.561 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.561</SECTNO>
                        <SUBJECT>Approval of indirect cost rates and cost allocation plans.</SUBJECT>
                        <P>(a) If the Department of Education is the cognizant agency, the Secretary approves an indirect cost rate or cost allocation plan for a State agency and for a subgrantee other than a local educational agency. For the purposes of this section, the term “local educational agency” does not include a State agency.</P>
                        <P>(b) Each State educational agency, on the basis of a plan approved by the Secretary, shall approve an indirect cost rate for each local educational agency that requests it to do so.</P>
                        <P>(c) The Secretary generally approves indirect cost rate agreements annually. Indirect cost rate agreements may be approved for periods longer than a year if the Secretary determines that rates will be sufficiently stable to justify a longer rate period.</P>
                    </SECTION>
                    <AMDPAR>126. Add § 76.562 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.562</SECTNO>
                        <SUBJECT>Reimbursement of indirect costs.</SUBJECT>
                        <P>(a) Reimbursement of indirect costs is subject to the availability of funds and statutory or administrative restrictions.</P>
                        <P>(b) The application of the negotiated indirect cost rate (determination of the direct cost base) or cost allocation plan (charging methodology) must be in accordance with the agreement/plan approved by the grantee's cognizant agency.</P>
                        <P>(c) Indirect costs for joint applications and projects (see § 76.303) are limited to the amount derived by applying the rate of the applicant, or a restricted rate when applicable, to the direct cost base for the grant in keeping with the terms of the applicant's federally recognized indirect cost rate agreement and program requirements.</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 76.563</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>127. Amend § 76.563 by:</AMDPAR>
                    <AMDPAR>a. Removing the words “agencies of State and local governments that are grantees under”;</AMDPAR>
                    <AMDPAR>b. Removing the words “their subgrantees” and adding in their place the word “subgrants”; and</AMDPAR>
                    <AMDPAR>c. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <AMDPAR>128. Revise § 76.654 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.564</SECTNO>
                        <SUBJECT>Restricted indirect cost rate formula.</SUBJECT>
                        <P>(a) An indirect cost rate for a grant covered by §§ 76.563 or 75.563 is determined by the following formula:</P>
                        <FP SOURCE="FP-2">Restricted indirect cost rate = (General management costs + Fixed costs) ÷ (Other expenditures).</FP>
                        <P>(b) General management costs, fixed costs, and other expenditures must be determined under §§ 76.565 through 76.567.</P>
                        <P>(c) Under the programs covered by § 76.563, a grantee or subgrantee that is not a State or local government agency—</P>
                        <P>(1) Shall use a negotiated restricted indirect cost rate computed under paragraph (a) of this section or cost allocation plan that complies with the formula in paragraph (a) of this section; or</P>
                        <P>(2) May elect to use an indirect cost rate of 8 percent of the modified total direct costs (MTDC) base if the grantee or subgrantee does not have a negotiated restricted indirect cost rate. MTDC is defined in 2 CFR 200.1. If the Secretary determines that the grantee or subgrantee would have a lower rate as calculated under paragraph (a) of this section, the lower rate shall be used for the affected program.</P>
                        <P>(3) If the grantee has established a threshold for equipment that is lower than the amount specified in the Uniform Guidance, the grantee must use that threshold to exclude equipment from the MTDC base.</P>
                        <P>(4) For purposes of the MTDC base and application of the 8 percent rate, MTDC includes up to the amount specified in the definition of MTDC in the Uniform Guidance of each subaward, each year.</P>
                        <P>(d) Indirect costs that are unrecovered as a result of these restrictions may not be charged directly, used to satisfy matching or cost-sharing requirements, or charged to another Federal award.</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 76.565</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>129. Amend § 76.565 by removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.566</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>130. Amend § 76.566 by:</AMDPAR>
                    <AMDPAR>a. In the introductory text, adding the word “allowable” before the words “indirect costs”; and</AMDPAR>
                    <AMDPAR>b. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <AMDPAR>131. Amend § 76.567 by:</AMDPAR>
                    <AMDPAR>a. Revising paragraph (b)(3);</AMDPAR>
                    <AMDPAR>b. In paragraph (b)(7), removing the punctuation and word “; and”;</AMDPAR>
                    <AMDPAR>c. Redesignating paragraph (b)(8) as paragraph (b)(9);</AMDPAR>
                    <AMDPAR>d. Adding a new paragraph (b)(8); and</AMDPAR>
                    <AMDPAR>e. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <P>The revision and addition read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 76.567</SECTNO>
                        <SUBJECT>Other expenditures—restricted rate.</SUBJECT>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>(3) Subawards exceeding the amount specified in the definition of Modified Total Direct Cost in the Uniform Guidance each, per year;</P>
                        <STARS/>
                        <P>(8) Other distorting items; and</P>
                        <STARS/>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 76.568</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>132. Amend § 76.568 by:</AMDPAR>
                    <AMDPAR>a. In paragraph (c), adding the word “(denominator)” after the word “expenditures”; and</AMDPAR>
                    <AMDPAR>b. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <AMDPAR>133. Amend § 76.569 by:</AMDPAR>
                    <AMDPAR>a. Revising paragraph (a) and removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <P>The revision reads as follows:</P>
                    <SECTION>
                        <PRTPAGE P="2024"/>
                        <SECTNO>§ 76.569</SECTNO>
                        <SUBJECT>Using the restricted indirect cost rate.</SUBJECT>
                        <P>(a) Under the programs referenced in §§ 75.563 and 76.563, the maximum amount of indirect costs recovery under a grant is determined by the following formula:</P>
                        <FP SOURCE="FP-2">Indirect costs = (Restricted indirect cost rate) × (Total direct costs of the grant minus capital outlays, subawards exceeding amount specified in the definition of Modified Total Direct Cost in the Uniform Guidance each, per year, and other distorting or unallowable items as specified in the grantee's indirect cost rate agreement)</FP>
                        <STARS/>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 76.580</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>134. Amend § 76.580 by removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <AMDPAR>135. Revise § 76.600 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.600</SECTNO>
                        <SUBJECT>Where to find the construction regulations.</SUBJECT>
                        <P>(a) A State or a subgrantee that requests program funds for construction, or whose grant or subgrant includes funds for construction, must comply with the rules on construction that apply to applicants and grantees under 34 CFR 75.600 through 75.618.</P>
                        <P>(b) The State must perform the functions of the Secretary for subgrantee requests under 34 CFR 75.601 (Approval of the construction).</P>
                        <P>(c) The State must perform the functions that the Secretary performs under 34 CFR 75.614(b). The State may consult with the State Historic Preservation Officer and Tribal Historic Preservation Officer to identify and evaluate historic properties and assess effects. The Secretary will continue to participate in the consultation process when:</P>
                        <P>(1) The State determines that “Criteria of Adverse Effect” applies to a project;</P>
                        <P>(2) There is a disagreement between the State and the State Historic Preservation Officer or Tribal Historic Preservation Officer regarding identification and evaluation or assessment of effects;</P>
                        <P>(3) There is an objection from consulting parties or the public regarding findings, determinations, the implementation of agreed-upon provisions, or their involvement in a National Historic Preservation Act Section 106 review (see 36 CFR part 800); or</P>
                        <P>(4) There is the potential for a foreclosure situation or anticipatory demolition as specified in Section 110(k) of the National Historic Preservation Act (see 36 CFR part 800).</P>
                        <P>(d) The State must provide to the Secretary the information required under 34 CFR 75.614(a) (Preservation of historic sites).</P>
                        <P>(e) The State must submit periodic reports to the Secretary regarding the State's review and approval of construction or real property projects containing information specified by the Secretary consistent with 2 CFR 200.329(d).</P>
                    </SECTION>
                    <AMDPAR>136-137. Revise the undesignated center heading before § 76.650 and revise § 76.650 to read as follows:</AMDPAR>
                    <HD SOURCE="HD1">Participation of Private School Children, Teachers or Other Educational Personnel, and Families</HD>
                    <SECTION>
                        <SECTNO>§ 76.650</SECTNO>
                        <SUBJECT>Participation of private school children, teachers or other educational personnel, and families.</SUBJECT>
                        <P>If a program provides for participation by private school children, teachers or other educational personnel, and families, and the program is not otherwise governed by applicable regulations, the grantee or subgrantee must provide, as applicable, services in accordance with the requirements under §§ 299.7 through 299.11.</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§§ 76.651 through 76.662</SECTNO>
                        <SUBJECT>[Removed and Reserved]</SUBJECT>
                    </SECTION>
                    <AMDPAR>138. Remove and reserve §§ 76.651 through 76.662.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.665</SECTNO>
                        <SUBJECT>[Removed and Reserved]</SUBJECT>
                    </SECTION>
                    <AMDPAR>139. Remove the undesignated center heading “Equitable Services under the CARES Act” above § 76.665 and remove and reserve § 76.665.</AMDPAR>
                    <SECTION>
                        <SECTNO>§§ 76.670 through 76.677</SECTNO>
                        <SUBJECT>[Removed and Reserved]</SUBJECT>
                    </SECTION>
                    <AMDPAR>140. Remove the undesignated section heading “Procedures for Bypass” above § 76.670 and remove and reserve §§ 76.670 through 76.677.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.682</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>141. Amend § 76.682 by removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.702</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>142. Amend § 76.702 removing the word “insure” and adding in its place the word “ensure”.</AMDPAR>
                    <AMDPAR>143. Amend § 76.707 by revising paragraph (h) and removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <P>The revision reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 76.707</SECTNO>
                        <SUBJECT>When obligations are made.</SUBJECT>
                        <STARS/>
                        <GPOTABLE COLS="2" OPTS="L1,nj,tp0,i1" CDEF="s80,r80">
                            <TTITLE> </TTITLE>
                            <BOXHD>
                                <CHED H="1" O="L">If the obligation is for—</CHED>
                                <CHED H="1" O="L">The obligation is made—</CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(h) A pre-agreement cost that was properly approved by the Secretary under the cost principles in 2 CFR part 200, subpart E</ENT>
                                <ENT>On the first day of the grant or subgrant period of performance.</ENT>
                            </ROW>
                        </GPOTABLE>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 76.708</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>144. Amend § 76.708 by:</AMDPAR>
                    <AMDPAR>a. In paragraph (a) introductory text, removing the words “the authorizing statute” and adding in their place the words “applicable statutes and regulations”, removing the word “requires” and adding in its place the word “require”, and removing the words “(see § 76.5)” and adding, in their place, the words “(see § 76.51(a))”;</AMDPAR>
                    <AMDPAR>b. In paragraph (c), removing the words “the authorizing statute” and adding in their place the words “applicable statutes and regulations” and removing the word “gives” and adding in its place the word “give”; and</AMDPAR>
                    <AMDPAR>c. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.709</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>145. Amend § 76.709 by removing the Note and the parenthetical authority citation at the end of the section.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.710</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>146. Amend § 76.710 by removing the Note and the parenthetical authority citation at the end of the section.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.711</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>147. Amend § 76.711 by:</AMDPAR>
                    <AMDPAR>a. In the section heading, removing the abbreviation “CFDA” and adding in its place the abbreviation “ALN”; and</AMDPAR>
                    <AMDPAR>b. Removing the phrase “Catalog of Federal Domestic Assistance (CFDA)” and adding in its place the phrase “Assistance Listing Number (ALN)”.</AMDPAR>
                    <SECTION>
                        <PRTPAGE P="2025"/>
                        <SECTNO>§ 76.714</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>148. Amend § 76.714 by adding “, as defined in § 76.52(c)(3),” after “Federal financial assistance”.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.720</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>149. Amend § 76.720 by:</AMDPAR>
                    <AMDPAR>a. In paragraph (a), removing the citation “2 CFR 200.327” and adding in its place the citation “2 CFR 200.328”, removing the citation “2 CFR 200.328” and adding, in its place, the citation “2 CFR 200.329”, and removing the words “the Paperwork Reduction Act of 1995, 44 U.S.C. 3501-3520” and adding, in their place, the words “Subchapter 1 of Chapter 35 (sections 3501-3521) of Title 44, U.S. Code, commonly known as the “Paperwork Reduction Act” ”;</AMDPAR>
                    <AMDPAR>b. In paragraph (c)(2), removing the words “the General Education Provisions Act” and adding, in their place, the word “GEPA”; and</AMDPAR>
                    <AMDPAR>c. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <AMDPAR>150. Amend § 76.740 by:</AMDPAR>
                    <AMDPAR>a. In paragraph (a), removing the number “438” and adding in its place the number “444” in the first sentence and revising the parenthetical sentence at the end;</AMDPAR>
                    <AMDPAR>b. In paragraph (b), removing the number “439” and adding in its place the number “445”; and adding the words “(20 U.S.C. 1232h; commonly known as the “Protection of Pupil Rights Amendment” or “PPRA”)” after the words “of GEPA”; and</AMDPAR>
                    <AMDPAR>c. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <P>The revision reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 76.740</SECTNO>
                        <SUBJECT>Protection of and access to student records; student rights in research, experimental programs, and testing.</SUBJECT>
                        <P>(a) * * * (Section 444 of GEPA (20 U.S.C. 1232g) is commonly referred to as the “Family Educational Rights and Privacy Act of 1974” or “FERPA”.)</P>
                        <STARS/>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 76.761</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>151. Amend § 76.761 in paragraph (b) by removing the words “the authorizing statute and implementing regulations for the program” and adding in their place the words “applicable statutes and regulations”.</AMDPAR>
                    <AMDPAR>152. Amend § 76.783 by:</AMDPAR>
                    <AMDPAR>a. In paragraph (a)(1), removing the word “or” '</AMDPAR>
                    <AMDPAR>b. In paragraph (a)(2), removing the period and adding in its place “; or”;</AMDPAR>
                    <AMDPAR>c. Adding paragraph (a)(3);</AMDPAR>
                    <AMDPAR>d. Removing the citation “76.401(d)(2)-(7)” in paragraph (b) and adding in its place the citation “76.401(a) through (d)”; and</AMDPAR>
                    <AMDPAR>e. Removing the Note and parenthetical authority citation at the end of the section.</AMDPAR>
                    <P>The addition reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 76.783</SECTNO>
                        <SUBJECT>State educational agency action—subgrantee's opportunity for a hearing.</SUBJECT>
                        <P>(a) * * *</P>
                        <P>(3) Failing to provide funds in amounts in accordance with the requirements of applicable statutes and regulations.</P>
                        <STARS/>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 76.785</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>153. Amend § 76.785 by:</AMDPAR>
                    <AMDPAR>a. Removing the words “section 10306” and adding in their place the words “section 4306”; and</AMDPAR>
                    <AMDPAR>b. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.786</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>154. Amend § 76.786 by:</AMDPAR>
                    <AMDPAR>a. In paragraph (a), removing the words “Public Charter Schools Program” and adding in their place the words “Charter School State Entity Grant Program”; and</AMDPAR>
                    <AMDPAR>b. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.787</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>155. Amend § 76.787 by:</AMDPAR>
                    <AMDPAR>a. In the definition of “charter school,” removing the words “title X, part C of the ESEA” and adding in their place the words “section 4310(2) of the ESEA (20 U.S.C. 7221i(2))”;</AMDPAR>
                    <AMDPAR>b. In the definition of “covered program,” removing the words “an elementary or secondary education program administered by the Department under which the Secretary allocates funds to States on a formula basis” and adding in their place the words “a State-administered formula grant program”;</AMDPAR>
                    <AMDPAR>c. In the definition of “local educational agency,” removing the words “the authorizing statute” and adding in their place the words “applicable statutes and regulations”; and</AMDPAR>
                    <AMDPAR>d. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <AMDPAR>156. Revise the undesignated center heading before § 76.788 to read “Responsibilities for Notice and Information”.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.788</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>157. Amend § 76.788 by:</AMDPAR>
                    <AMDPAR>a. In paragraph (c), removing the words “the authorizing statute or implementing regulations for the applicable covered program” and adding in their place the words “applicable statutes or regulations”; and</AMDPAR>
                    <AMDPAR>b. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.900</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>158. Amend § 76.900 by removing “ED” in paragraphs (a) and (b) and adding in its place the words “the Department”.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 76.901</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>159. Amend § 76.901 by:</AMDPAR>
                    <AMDPAR>a. In paragraph (a) introductory text, removing the words “Part E” and adding in their place the words “Part D (20 U.S.C. 1234-1234h)”; and</AMDPAR>
                    <AMDPAR>b. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 77—DEFINITIONS THAT APPLY TO DEPARTMENT REGULATIONS</HD>
                    </PART>
                    <AMDPAR>160. The authority citation for part 77 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 20 U.S.C. 1221e-3 and 3474, unless otherwise noted.</P>
                    </AUTH>
                    <AMDPAR>161. Amend § 77.1 by:</AMDPAR>
                    <AMDPAR>a. Revising paragraph (b); and</AMDPAR>
                    <AMDPAR>b. In paragraph (c):</AMDPAR>
                    <AMDPAR>i. In the definition of “Applicant” removing the word “requesting” and adding in its place the words “applying for”;</AMDPAR>
                    <AMDPAR>ii. In the definition of “Award” removing the words “the definition of”;</AMDPAR>
                    <AMDPAR>iii. In the definition of “Budget” removing the words “that recipient's” and adding in their place “a recipient's”;</AMDPAR>
                    <AMDPAR>iv. Adding in alphabetical order a definition for “construction”;</AMDPAR>
                    <AMDPAR>v. Revising the definition of “Demonstrates a rationale”;</AMDPAR>
                    <AMDPAR>vi. Removing the definitions of “Direct grant program” and “Director of the Institute of Museum Services”;</AMDPAR>
                    <AMDPAR>vii. Revising the definition of “Director of the National Institute of Education”;</AMDPAR>
                    <AMDPAR>viii. Adding in alphabetical order a definition for “Evaluation”;</AMDPAR>
                    <AMDPAR>ix. In the definition of “Evidence-based” adding “, for the purposes of 34 CFR part 75,” after the word “Evidence-based”;</AMDPAR>
                    <AMDPAR>x. Adding in alphabetical order a definition for “Evidence-building”;</AMDPAR>
                    <AMDPAR>xi. In the definition of “GEPA” removing the word “The” and adding in its place the word “the”;</AMDPAR>
                    <AMDPAR>xii. Adding in alphabetical order definitions for “independent evaluation”;</AMDPAR>
                    <AMDPAR>
                        xiii. Revising the definitions of “minor remodeling”, “Moderate evidence”, and “National level”;
                        <PRTPAGE P="2026"/>
                    </AMDPAR>
                    <AMDPAR>xiv. Adding in alphabetical order a definition for “peer-reviewed scholarly publication”;</AMDPAR>
                    <AMDPAR>xv. In the definition of “Project period” removing the citation “2 CFR 200.77” and adding in its place the citation “2 CFR 200.1”;</AMDPAR>
                    <AMDPAR>xvi. Revising the definition of “Promising evidence”;</AMDPAR>
                    <AMDPAR>xvii. Adding in alphabetical order a definition for “quality data”;</AMDPAR>
                    <AMDPAR>xviii. Revising the definitions of “Regional level”, “State”, and “Strong evidence”;</AMDPAR>
                    <AMDPAR>xix. In the definition of “Subgrant” removing the words “definition of “grant or award” ” and adding in their place the words “definitions of “Grant” or “Award” ”;</AMDPAR>
                    <AMDPAR>xx. Revising the definition of “What Works Clearinghouse (WWC) Handbooks (WWC Handbooks)”; and</AMDPAR>
                    <AMDPAR>xxi. In the definition of “Work of art” removing the word “facilities” and adding it its place the words “a facility”.</AMDPAR>
                    <P>The revisions and additions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 77.1</SECTNO>
                        <SUBJECT>Definitions that apply to all Department programs.</SUBJECT>
                        <STARS/>
                        <P>(b) Unless a statute or regulation provides otherwise, the following definitions in 2 CFR part 200 apply to the regulations in subtitles A and B of this title. The following terms have the definitions given those terms in 2 CFR part 200.1. Phrasing given in parentheses references the term or terms used in title 34 that are consistent with the term defined in title 2.</P>
                        <P>
                            <E T="03">Contract</E>
                        </P>
                        <P>
                            <E T="03">Equipment</E>
                        </P>
                        <P>
                            <E T="03">Federal award</E>
                             (The terms “award,” “grant,” and “subgrant”, as defined in paragraph (c) of this section, have the same meaning, depending on the context, as “Federal award” in 2 CFR 200.1.).
                        </P>
                        <P>
                            <E T="03">Period of performance</E>
                             (For discretionary grants, ED uses the term “project period,” as defined in paragraph (c) of this section, instead of “period of performance,” to describe the period during which funds can be obligated by the grantee.).
                        </P>
                        <P>
                            <E T="03">Personal property</E>
                        </P>
                        <P>
                            <E T="03">Real property</E>
                        </P>
                        <P>
                            <E T="03">Recipient</E>
                        </P>
                        <P>
                            <E T="03">Subaward</E>
                             (The term “subgrant,” as defined in paragraph (c) of this section, has the same meaning as “subaward” in 2 CFR 200.1).
                        </P>
                        <P>
                            <E T="03">Supplies</E>
                        </P>
                        <P>(c) * * *</P>
                        <P>
                            <E T="03">Construction</E>
                             means
                        </P>
                        <P>(i)(A) the preparation of drawings and specifications for a facilities project;</P>
                        <P>(B) erecting, building, demolishing, acquiring, renovating, major remodeling of, or extending a facilities project; or</P>
                        <P>(C) inspecting and supervising the construction of a facilities project;</P>
                        <P>(ii) Does not include minor remodeling.</P>
                        <STARS/>
                        <P>
                            <E T="03">Demonstrates a rationale</E>
                             means that there is a key project component included in the project's logic model that is supported by citations of high-quality research or evaluation findings that suggest that the project component is likely to significantly improve relevant outcomes.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Director of the Institute of Education Sciences</E>
                             means the Director of the Institute of Education Sciences or an officer or employee of the Institute of Education Sciences acting for the Director under a delegation of authority.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Evaluation</E>
                             means an assessment using systematic data collection and analysis of one or more programs, policies, practices, and organizations intended to assess their implementation, outcomes, effectiveness, or efficiency.
                        </P>
                        <P>
                            <E T="03">Evidence-building</E>
                             means a systematic plan for identifying and answering questions relevant to programs and policies through performance measurement, exploratory studies, or program evaluation.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Independent evaluation</E>
                             means an evaluation of a project component that is designed and carried out independently of, but in coordination with, the entities that develop or implement the project component.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Minor remodeling</E>
                             means minor alterations in a previously completed facilities project. The term also includes the extension of utility lines, such as water and electricity, from points beyond the confines of the space in which the minor remodeling is undertaken but within the confines of the previously completed facility. The term may also include related designs and drawings for these projects. The term does not include construction or renovation, structural alterations to buildings, facilities maintenance, or repairs.
                        </P>
                        <P>
                            <E T="03">Moderate evidence</E>
                             means evidence of effectiveness of a key project component in improving a relevant outcome for a sample that overlaps with the populations or settings proposed to receive that component, based on a relevant finding from one of the following:
                        </P>
                        <P>(i) A practice guide prepared by the WWC using version 2.1, 3.0, 4.0, 4.1, or 5.0 of the WWC Handbooks reporting “strong evidence” or “moderate evidence” for the corresponding practice guide recommendation;</P>
                        <P>(ii) An intervention report prepared by the WWC using version 2.1, 3.0, 4.0, 4.1, or 5.0 of the WWC Handbooks reporting “Tier 1 strong evidence” of effectiveness or “Tier 2 moderate evidence” of effectiveness or a “positive effect” on a relevant outcome based on a sample including at least 20 students or other individuals from more than one site (such as a State, county, city, local educational agency (LEA), school, or postsecondary campus), or a “potentially positive effect” on a relevant outcome based on a sample including at least 350 students or other individuals from more than one site (such as a State, county, city, LEA, school, or postsecondary campus), with no reporting of a “negative effect” or “potentially negative effect” on a relevant outcome; or</P>
                        <P>(iii) A single experimental study or quasi-experimental design study reviewed and reported by the WWC most recently using version 2.1, 3.0, 4.0, 4.1, or 5.0 of the WWC Handbooks, or otherwise assessed by the Department using version 5.0 of the WWC Handbook, as appropriate, and that—</P>
                        <P>(A) Meets WWC standards with or without reservations;</P>
                        <P>
                            (B) Includes at least one statistically significant and positive (
                            <E T="03">i.e.,</E>
                             favorable) effect on a relevant outcome;
                        </P>
                        <P>(C) Includes no overriding statistically significant and negative effects on relevant outcomes reported in the study or in a corresponding WWC intervention report prepared under version 2.1, 3.0, 4.0, 4.1, or 5.0 of the WWC Handbooks; and</P>
                        <P>(D) Is based on a sample from more than one site (such as a State, county, city, LEA, school, or postsecondary campus) and includes at least 350 students or other individuals across sites. Multiple studies of the same project component that each meet the requirements in paragraphs (iii)(A) through (C) of this definition may together satisfy the requirement in this paragraph (iii)(D).</P>
                        <P>
                            <E T="03">National level</E>
                             means the level of scope or effectiveness of a project component that is able to be effective in a wide variety of communities, including rural and urban areas, as well as groups with different characteristics (such as socioeconomic status, race, ethnic, gender, disability, language, and migrant populations), populations, and settings.
                        </P>
                        <STARS/>
                        <PRTPAGE P="2027"/>
                        <P>
                            <E T="03">Peer-reviewed scholarly publication</E>
                             means a final peer-reviewed manuscript accepted for publication, that arises from research funded, either fully or partially, by Federal funds awarded through a Department-managed grant, contract, or other agreement. A final peer-reviewed manuscript is defined as an author's final manuscript of a peer-reviewed scholarly paper accepted for publication, including all modifications resulting from the peer review process. The final peer-reviewed manuscript is not the same as the final published article, which is defined as a publisher's authoritative copy of the paper including all modifications from the publishing peer review process, copyediting, stylistic edits, and formatting changes. However, the content included in both the final peer-reviewed manuscript and the final published article, including all findings, tables, and figures should be identical.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Promising evidence</E>
                             means evidence of the effectiveness of a key project component in improving a relevant outcome, based on a relevant finding from one of the following:
                        </P>
                        <P>(i) A practice guide prepared by the WWC reporting “strong evidence”, “moderate evidence”, or “promising evidence” for the corresponding practice guide recommendation;</P>
                        <P>(ii) An intervention report prepared by the WWC reporting “Tier 1 strong evidence” of effectiveness, or “Tier 2 moderate evidence” of effectiveness, or “Tier 3 promising evidence” of effectiveness, or a “positive effect,” or “potentially positive effect” on a relevant outcome, with no reporting of a “negative effect” or “potentially negative effect” on a relevant outcome; or</P>
                        <P>(iii) A single study assessed by the Department, as appropriate, that—-</P>
                        <P>(A) Is an experimental study, a quasi-experimental design study, or a well-designed and well-implemented correlational study with statistical controls for selection bias (such as a study using regression methods to account for differences between a treatment group and a comparison group);</P>
                        <P>
                            (B) Includes at least one statistically significant and positive (
                            <E T="03">i.e.,</E>
                             favorable) effect on a relevant outcome; and
                        </P>
                        <P>(C) Includes no overriding statistically significant and negative effects on relevant outcomes reported in the study or in a corresponding WWC intervention report.</P>
                        <STARS/>
                        <P>
                            <E T="03">Quality data</E>
                             encompasses utility, objectivity, and integrity of the information. “Utility” refers to how the data will be used, either for its intended use or other uses. “Objectivity” refers to data being accurate, complete, reliable, and unbiased. “Integrity” refers to the protection of data from being manipulated.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Regional level</E>
                             means the level of scope or effectiveness of a project component that is able to serve a variety of communities within a State or multiple States, including rural and urban areas, as well as groups with different characteristics (such as socioeconomic status, race, ethnicity, gender, disability, language, and migrant status). For an LEA-based project, to be considered a regional-level project, a project component must serve students in more than one LEA, unless the project component is implemented in a State in which the State educational agency is the sole educational agency for all schools.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">State</E>
                             means any of the 50 States, the Commonwealth of Puerto Rico, the District of Columbia, Guam, American Samoa, the U.S. Virgin Islands, and the Commonwealth of the Northern Mariana Islands.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Strong evidence</E>
                             means evidence of the effectiveness of a key project component in improving a relevant outcome for a sample that overlaps with the populations and settings proposed to receive that component, based on a relevant finding from one of the following:
                        </P>
                        <P>(i) A practice guide prepared by the WWC using version 2.1, 3.0, 4.0, 4.1, or 5.0 of the WWC Handbooks reporting “strong evidence” for the corresponding practice guide recommendation;</P>
                        <P>(ii) An intervention report prepared by the WWC using version 2.1, 3.0, 4.0, 4.1, or 5.0 of the WWC Handbooks reporting “Tier 1 strong evidence” of effectiveness or a “positive effect” on a relevant outcome based on a sample including at least 350 students or other individuals across more than one site (such as a State, county, city, local educational agency (LEA), school, or postsecondary campus), with no reporting of a “negative effect” or “potentially negative effect” on a relevant outcome; or</P>
                        <P>(iii) A single experimental study reviewed and reported by the WWC most recently using version 2.1, 3.0, 4.0, 4.1, or 5.0 of the WWC Handbooks, or otherwise assessed by the Department using version 5.0 of the WWC Handbook, as appropriate, and that—</P>
                        <P>(A) Meets WWC standards without reservations;</P>
                        <P>
                            (B) Includes at least one statistically significant and positive (
                            <E T="03">i.e.,</E>
                             favorable) effect on a relevant outcome;
                        </P>
                        <P>(C) Includes no overriding statistically significant and negative effects on relevant outcomes reported in the study or in a corresponding WWC intervention report prepared under version 2.1, 3.0, 4.0, 4.1, or 5.0 of the WWC Handbooks; and</P>
                        <P>(D) Is based on a sample from more than one site (such as a State, county, city, LEA, school, or postsecondary campus) and includes at least 350 students or other individuals across sites. Multiple studies of the same project component that each meet the requirements in paragraphs (iii)(A) through (C) of this definition may together satisfy the requirement in this paragraph (iii)(D).</P>
                        <STARS/>
                        <P>
                            <E T="03">What Works Clearinghouse (WWC) Handbooks (WWC Handbooks)</E>
                             means the standards and procedures set forth in the WWC Procedures and Standards Handbook, Version 5.0, or in the WWC Standards Handbook, Version 4.0 or 4.1, or in the WWC Procedures Handbook, Version 4.0 or 4.1, the WWC Procedures and Standards Handbook, Version 3.0 or Version 2.1 (all incorporated by reference, see § 77.2). Study findings eligible for review under WWC standards can meet WWC standards without reservations, meet WWC standards with reservations, or not meet WWC standards. WWC practice guides and intervention reports include findings from systematic reviews of evidence as described in the WWC Handbooks documentation.
                        </P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>162. Revise § 77.2 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 77.2 </SECTNO>
                        <SUBJECT>Incorporation by reference.</SUBJECT>
                        <P>
                            Certain material is incorporated by reference into this part with the approval of the Director of the Federal Register under 5 U.S.C. 552(a) and 1 CFR part 51. All approved incorporation by reference (IBR) material is available for inspection at the Department of Education (the Department) and the National Archives and Records Administration (NARA). Contact the Department at: Institute of Education Sciences, National Center for Education Evaluation and Regional Assistance, 550 12th Street SW, PCP-4158, Washington, DC 20202-5900; phone: (202) 245-6940; email: 
                            <E T="03">Contact.WWC@ed.gov</E>
                            . 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 
                            <PRTPAGE P="2028"/>
                            <E T="03">fr.inspection@nara.gov</E>
                            . The following material may be obtained from Institute of Education Sciences, 550 12th Street SW, Washington, DC 20202; phone: (202) 245-6940; website: 
                            <E T="03">http://ies.ed.gov/ncee/wwc/Handbooks:</E>
                        </P>
                        <P>(b) What Works Clearinghouse Procedures and Standards Handbook, Version 5.0, August 2022 (Revised December 2022); IBR approved for § 77.1.</P>
                        <P>(c) What Works Clearinghouse Standards Handbook, Version 4.1, January 2020, IBR approved for § 77.1.</P>
                        <P>(d) What Works Clearinghouse Procedures Handbook, Version 4.1, January 2020, IBR approved for § 77.1.</P>
                        <P>(e) What Works Clearinghouse Standards Handbook, Version 4.0, October 2017, IBR approved for § 77.1.</P>
                        <P>(f) What Works Clearinghouse Procedures Handbook, Version 4.0, October 2017, IBR approved for § 77.1.</P>
                        <P>(g) What Works Clearinghouse Procedures and Standards Handbook, Version 3.0, March 2014, IBR approved for § 77.1.</P>
                        <P>(h) What Works Clearinghouse Procedures and Standards Handbook, Version 2.1, September 2011, IBR approved for § 77.1.</P>
                    </SECTION>
                    <PART>
                        <HD SOURCE="HED">PART 79—INTERGOVERNMENTAL REVIEW OF DEPARTMENT OF EDUCATION PROGRAMS AND ACTIVITIES</HD>
                    </PART>
                    <AMDPAR>163. The authority citation for part 79 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>31 U.S.C. 6506; 42 U.S.C. 3334; and E.O. 12372, unless otherwise noted.</P>
                    </AUTH>
                    <EXTRACT>
                        <P>Section 79.2 also issued under E.O. 12372.</P>
                    </EXTRACT>
                    <AMDPAR>164. In part 79, remove the word “state” wherever it appears and in its place add the word “State” and remove the word “states” where it appears and in its place add the word “States”.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 79.1 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>165. Amend § 79.1 by removing the second sentence in paragraph (a).</AMDPAR>
                    <AMDPAR>166. Amend § 79.2 by:</AMDPAR>
                    <AMDPAR>a. Removing the definitions of “Department” and “Secretary”.</AMDPAR>
                    <AMDPAR>b. Revising the definition of “State”.</AMDPAR>
                    <AMDPAR>c. Removing the parenthetical authority citation at the end of the section.</AMDPAR>
                    <P>The revision reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 79.2</SECTNO>
                        <SUBJECT>What definitions apply to these regulations?</SUBJECT>
                        <STARS/>
                        <P>
                            <E T="03">State</E>
                             means any of the 50 States, the Commonwealth of Puerto Rico, the District of Columbia, Guam, American Samoa, the U.S. Virgin Islands, and the Commonwealth of the Northern Mariana Islands.
                        </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 79.3</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>167. Amend § 79.3 by:</AMDPAR>
                    <AMDPAR>a. In paragraph (a), removing the words “and identifies which of these are subject to the requirements of section 204 of the Demonstration Cities and Metropolitan Development Act”;</AMDPAR>
                    <AMDPAR>
                        b. In paragraph (c)(6), removing the words “(
                        <E T="03">e.g.,</E>
                         block grants under Chapter 2 of the Education Consolidation and Improvement Act of 1981)”; and
                    </AMDPAR>
                    <P>c. In paragraph (c)(7), removing the words “development national” and adding in their place the words “development that is national”.</P>
                    <SECTION>
                        <SECTNO>§ 79.4</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>168. Amend § 79.4 in paragraph (b)(3) by removing the word “official's” and adding in its place the word “officials' ”.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 79.5</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>169. Amend § 79.5 by removing the word “assure” and adding in its place the word “ensure”.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 79.6</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>170. Amend § 79.6 by removing the word “state's” and adding in its place the word “State's”.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 79.8</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>171. Amend § 79.8 by removing paragraph (d).</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 79.9</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>172. Amend § 79.9 in paragraph (e) by removing the words “of this part”.</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 79.10</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>173. Amend § 79.10 in paragraph (a)(2) by removing the words “a mutually agreeable solution with the state process” and adding in their place the words “an agreement with the State”.</AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 299—GENERAL PROVISIONS</HD>
                    </PART>
                    <AMDPAR>174. The authority citation for part 299 is revised to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>20 U.S.C. 1221e-3 and 3474, unless otherwise noted.</P>
                    </AUTH>
                    <EXTRACT>
                        <P>Section 299.4 also issued under 20 U.S.C. 7821 and 7823.</P>
                        <P>Section 299.5 also issued under 20 U.S.C. 7428(c), 7801(11), 7901.</P>
                        <P>Section 299.6 also issued under 20 U.S.C. 7881.</P>
                        <P>Section 299.7 also issued under 20 U.S.C. 7881.</P>
                        <P>Section 299.8 also issued under 20 U.S.C. 7881.</P>
                        <P>Section 299.9 also issued under 20 U.S.C. 7881.</P>
                        <P>Section 299.10 also issued under 20 U.S.C. 7881.</P>
                        <P>Section 299.11 also issued under 20 U.S.C. 7881.</P>
                        <P>Section 299.12 also issued under 20 U.S.C. 7881(a)(3)(B).</P>
                        <P>Section 299.13 also issued under 20 U.S.C. 7844(a)(3)(C), 7883.</P>
                        <P>Section 299.14 also issued under 20 U.S.C. 7844(a)(3)(C), 7883.</P>
                        <P>Section 299.15 also issued under 20 U.S.C. 7844(a)(3)(C), 7883.</P>
                        <P>Section 299.16 also issued under 20 U.S.C. 7883.</P>
                        <P>Section 299.17 also issued under 20 U.S.C. 7883.</P>
                        <P>Section 299.18 issued under 20 U.S.C. 6320(e), 7882, and 7883.</P>
                        <P>Section 299.19 issued under 20 U.S.C. 6320(e) and 7882(a).</P>
                        <P>Section 299.20 issued under 20 U.S.C. 6320(b)(6) and (e), 7881(c)(6), 7882, and 7883.</P>
                        <P>Section 299.21 issued under 20 U.S.C. 7884(a)(1).</P>
                        <P>Section 299.22 issued under 20 U.S.C. 7884(a)(1).</P>
                        <P>Section 299.23 issued under 20 U.S.C. 7884(a)(1).</P>
                        <P>Section 299.24 issued under 20 U.S.C. 7884(a)(1).</P>
                        <P>Section 299.25 issued under 20 U.S.C. 7884(a)(1).</P>
                        <P>Section 299.26 issued under 20 U.S.C. 7884(a)(1).</P>
                        <P>Section 299.27 issued under 20 U.S.C. 7884(a)(2).</P>
                        <P>Section 299.28 issued under 20 U.S.C. 7884(b).</P>
                    </EXTRACT>
                    <SECTION>
                        <SECTNO>§ 299.6</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>175. Amend § 299.6 by removing paragraph (c).</AMDPAR>
                    <SECTION>
                        <SECTNO>§ § 299.7 through 299.13</SECTNO>
                        <SUBJECT>[Redesignated as §§ 299.9 through 299.15]</SUBJECT>
                    </SECTION>
                    <AMDPAR>176. Redesignate §§ 299.7 through 299.13 as §§ 299.9 through 299.15.</AMDPAR>
                    <AMDPAR>177. Add new §§ 299.7 and 299.8 to subpart E to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 299.7</SECTNO>
                        <SUBJECT>What are the requirements for consultation?</SUBJECT>
                        <P>(a)(1) In order to have timely and meaningful consultation, an agency, consortium, or entity must—</P>
                        <P>(i) Consult with appropriate private school officials during the design and development of the agency, consortium, or entity's program for eligible private school children and their teachers and other educational personnel; and</P>
                        <P>(ii) Consult before the agency, consortium, or entity makes any decision that affects the opportunities of eligible private school children and their teachers and other educational personnel to participate in the applicable program.</P>
                        <P>(2) Such consultation must continue throughout the implementation and assessment of equitable services.</P>
                        <P>
                            (b) Both the agency, consortium, or entity and private school officials must have the goal of reaching agreement on how to provide equitable and effective programs for private school children and their teachers and other educational personnel, including, at a minimum, on issues such as—
                            <PRTPAGE P="2029"/>
                        </P>
                        <P>(1) How the agency, consortium, or entity will identify the needs of eligible private school children and their teachers and other educational personnel;</P>
                        <P>(2) What services the agency, consortium, or entity will offer to eligible private school children and their teachers and other educational personnel;</P>
                        <P>(3) How and when the agency, consortium, or entity will make decisions about the delivery of services;</P>
                        <P>(4) How, where, and by whom the agency, consortium, or entity will provide services to eligible private school children and their teachers and other educational personnel;</P>
                        <P>(5) How the agency, consortium, or entity will assess the services and use the results of the assessment to improve those services;</P>
                        <P>(6) Whether the agency, consortium, or entity will provide services directly or through a separate government agency, consortium, entity, or third-party contractor;</P>
                        <P>(7) The size and scope of the equitable services that the agency, consortium, or entity will provide to eligible private school children and their teachers and other educational personnel, the amount of funds available for those services, and how that amount is determined; and</P>
                        <P>(8) Whether to provide equitable services to eligible private school children and their teachers and other educational personnel—</P>
                        <P>(i) On a school-by-school basis;</P>
                        <P>(ii) By creating a pool or pools of funds with all the funds allocated under the applicable program based on the amount of funding allocated for equitable services to two or more participating private schools served by the same agency, consortium, or entity, provided that all the affected private schools agree to receive services in this way; or</P>
                        <P>(iii) By creating a pool or pools of funds with all the funds allocated under the applicable program based on the amount of funding allocated for equitable services to two or more participating private schools served across multiple agencies, consortia, or entities, provided that all the affected private schools agree to receive services in this way.</P>
                        <P>(c)(1) Consultation must include—</P>
                        <P>(i) A discussion of service delivery mechanisms the agency, consortium, or entity can use to provide equitable services to eligible private school children and their teachers and other educational personnel; and</P>
                        <P>(ii) A thorough consideration and analysis of the views of private school officials on the provision of services through a contract with a third-party provider.</P>
                        <P>(2) If the agency, consortium, or entity disagrees with the views of private school officials on the provision of services through a contract, the agency, consortium, or entity must provide in writing to the private school officials the reasons why the agency, consortium, or entity chooses not to use a contractor.</P>
                        <P>(d)(1) The agency, consortium, or entity must maintain in its records and provide to the SEA a written affirmation, signed by officials of each private school with participating children or appropriate private school representatives, that the required consultation has occurred. The written affirmation shall provide the option for private school officials to indicate such officials' belief that timely and meaningful consultation has not occurred or that the program design is not equitable with respect to eligible private school children.</P>
                        <P>(2) If private school officials do not provide the affirmations within a reasonable period of time, the agency, consortium, or entity must submit to the SEA documentation that the required consultation occurred.</P>
                        <P>(e) A private school official has the right to complain to the SEA that the agency, consortium, or entity did not—</P>
                        <P>(1) Engage in timely and meaningful consultation;</P>
                        <P>(2) Give due consideration to the views of the private school official; or</P>
                        <P>(3) Make a decision that treats the private school or its students equitably as required by this section.</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 299.8</SECTNO>
                        <SUBJECT>Use of Private School Personnel.</SUBJECT>
                        <P>A grantee or subgrantee may use program funds to pay for the services of an employee of a private school if:</P>
                        <P>(a) The employee performs the services outside of his or her regular hours of duty; and</P>
                        <P>(b) The employee performs the services under public supervision and control.</P>
                    </SECTION>
                    <AMDPAR>178. Transfer newly redesignated § 299.12 from subpart F to subpart E and revise it to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 299.12</SECTNO>
                        <SUBJECT>Ombudsman.</SUBJECT>
                        <P>To help ensure equity for eligible private school children, teachers, and other educational personnel, an SEA must direct the ombudsman designated under section 1117 of the ESEA and § 200.68 to monitor and enforce the requirements in §§ 299.6-299.11.</P>
                    </SECTION>
                    <AMDPAR>179. Add §§ 299.16 and 299.17 to subpart F to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 299.16</SECTNO>
                        <SUBJECT>What must an SEA include in its written resolution of a complaint?</SUBJECT>
                        <P>An SEA must include the following in its written resolution of a complaint under an applicable program:</P>
                        <P>(a) A description of applicable statutory and regulatory requirements.</P>
                        <P>(b) A description of the procedural history of the complaint.</P>
                        <P>(c) Findings of fact supported by citation, including page numbers, to supporting documents under paragraph (g) of this section.</P>
                        <P>(d) Legal analysis and conclusions.</P>
                        <P>(e) Corrective actions, if applicable.</P>
                        <P>(f) A statement of applicable appeal rights.</P>
                        <P>(g) A statement regarding the State's determination about whether it will provide services.</P>
                        <P>(h) All documents reviewed by the SEA in reaching its decision, paginated consecutively.</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 299.17</SECTNO>
                        <SUBJECT>What must a party seeking to appeal an SEA's written resolution of a complaint or failure to resolve a complaint in 45 days include in its appeal request?</SUBJECT>
                        <P>(a) A party appealing an SEA's written resolution of a complaint, or failure to resolve a complaint, must include the following in its request within 30 days of either the SEA's resolution or the 45-day time limit:</P>
                        <P>(i) A clear and concise statement of the parts of the SEA's decision being appealed, if applicable.</P>
                        <P>(ii) The legal and factual basis for the appeal.</P>
                        <P>(iii) A copy of the complaint filed with the SEA.</P>
                        <P>(iv) A copy of the SEA's written resolution of the complaint being appealed, if one is available, including all supporting documentation required under § 299.16(h).</P>
                        <P>(v) Any supporting documentation not included as part of the SEA's written resolution of the complaint being appealed.</P>
                        <P>(b) Unless substantiating documentation identified in paragraph (a) of this section is provided to the Department, the appeal is not considered complete. Statutory or regulatory time limits are stayed until the appeal is complete as determined by the Department.</P>
                        <P>(c) In resolving the appeal, if the Department determines that additional information is necessary, all applicable statutory or regulatory time limits are stayed pending receipt of that information.</P>
                    </SECTION>
                    <AMDPAR>180. Add subpart G part 299 to read as follows:</AMDPAR>
                    <CONTENTS>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart G—Procedures for Bypass</HD>
                            <SECHD>Sec.</SECHD>
                            <SECTNO>299.18</SECTNO>
                            <SUBJECT>
                                Applicability.
                                <PRTPAGE P="2030"/>
                            </SUBJECT>
                            <SECTNO>299.19</SECTNO>
                            <SUBJECT>Bypass—general.</SUBJECT>
                            <SECTNO>299.20</SECTNO>
                            <SUBJECT>Requesting a bypass.</SUBJECT>
                            <SECTNO>299.21</SECTNO>
                            <SUBJECT>Notice of intent to implement a bypass.</SUBJECT>
                            <SECTNO>299.22</SECTNO>
                            <SUBJECT>Filing requirements.</SUBJECT>
                            <SECTNO>299.23</SECTNO>
                            <SUBJECT>Bypass procedures.</SUBJECT>
                            <SECTNO>299.24</SECTNO>
                            <SUBJECT>Appointment and functions of a hearing officer.</SUBJECT>
                            <SECTNO>299.25</SECTNO>
                            <SUBJECT>Hearing procedures.</SUBJECT>
                            <SECTNO>299.26</SECTNO>
                            <SUBJECT>Decision.</SUBJECT>
                            <SECTNO>299.27</SECTNO>
                            <SUBJECT>Judicial review.</SUBJECT>
                            <SECTNO>299.28</SECTNO>
                            <SUBJECT>Continuation of a bypass.</SUBJECT>
                        </SUBPART>
                    </CONTENTS>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart G—Procedures for Bypass</HD>
                        <SECTION>
                            <SECTNO>§ 299.18</SECTNO>
                            <SUBJECT>Applicability.</SUBJECT>
                            <P>The regulations in this subpart apply to part A of Title I and applicable programs under section 8501(b)(1) of the ESEA under which the Secretary is authorized to waive the requirements for providing services to private school children, teachers or other educational personnel, and families, as applicable, and to implement a bypass.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 299.19</SECTNO>
                            <SUBJECT>Bypass—general.</SUBJECT>
                            <P>(a) The Secretary arranges for a bypass if—</P>
                            <P>(1) An agency, consortium, or entity is prohibited by law from providing for the participation in programs of children enrolled in, or teachers or other educational personnel from, private elementary and secondary schools, on an equitable basis; or</P>
                            <P>(2) The Secretary determines that the agency, consortium, or entity has substantially failed, or is unwilling, to provide for that participation as required by section 1117 or 8501 of the ESEA, as applicable.</P>
                            <P>(b) If the Secretary determines that a bypass is appropriate after following the requirements in §§ 299.21 through 299.26, the Secretary—</P>
                            <P>(1) Waives the requirements under section 1117 or 8501 of the ESEA, as applicable, for the agency, consortium, or entity; and</P>
                            <P>(2) Arranges for the provision of equitable services to those children, teachers or other educational personnel, and families, as applicable, through arrangements subject to the requirements of section 1117 or 8501 of the ESEA, as applicable, and sections 8503 and 8504 of the ESEA.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 299.20</SECTNO>
                            <SUBJECT>Requesting a bypass.</SUBJECT>
                            <P>(a) A private school official may request a bypass of an agency, consortium, or entity under the following circumstances:</P>
                            <P>(1) The private school official has—</P>
                            <P>(i) Filed a complaint with the State educational agency (SEA) under section 1117(b)(6)(A)-(B) or section 8501(c)(6)(A)-(B) of the ESEA and §§ 299.13 through 299.17 that an agency, consortium, or entity other than the SEA has substantially failed or is unwilling to provide equitable services;</P>
                            <P>(ii) Requested that the SEA provide equitable services on behalf of the agency, consortium, or entity under section 1117(b)(6)(C) or section 8501(c)(6)(C) of the ESEA; and</P>
                            <P>(iii) Submitted an appeal of the SEA's resolution of the complaint filed under this paragraph (a)(1) to the Secretary under section 8503(b) of the ESEA and § 299.17.</P>
                            <P>(2) If an SEA has substantially failed, or is unwilling, to provide equitable services, the private school official has—</P>
                            <P>(i) Filed a complaint with the SEA under section 8503(a) of the ESEA and §§ 299.13 through 299.16; and</P>
                            <P>(ii) Submitted an appeal to the Secretary under section 8503(b) of the ESEA and § 299.17 of the SEA's resolution of the complaint filed under paragraph (a)(1) of this section in which the private school official requests a bypass.</P>
                            <P>(b) An agency, consortium, or entity may request that the Secretary implement a bypass if the agency, consortium, or entity is prohibited by law from providing equitable services under section 1117 or section 8501 of the ESEA.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 299.21</SECTNO>
                            <SUBJECT>Notice of intent to implement a bypass.</SUBJECT>
                            <P>(a) Before taking any final action to implement a bypass, the Secretary provides the affected agency, consortium, or entity with written notice.</P>
                            <P>(b) In the written notice, the Secretary—</P>
                            <P>(1) States the reasons for the proposed bypass in sufficient detail to allow the agency, consortium, or entity to respond;</P>
                            <P>(2) Cites the requirement that is the basis for the alleged failure to comply; and</P>
                            <P>(3) Advises the agency, consortium, or entity that it—</P>
                            <P>(i) Has a deadline (which shall not be fewer than 45 days after receiving the written notice) to submit written objections to the proposed bypass; and</P>
                            <P>(ii) May request in writing the opportunity for a hearing to show cause why the Secretary should not implement the bypass.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 299.22</SECTNO>
                            <SUBJECT>Filing requirements.</SUBJECT>
                            <P>(a) Any written submission under § 299.21 must be filed by hand delivery, mail, or email.</P>
                            <P>(b) The filing date for a written submission is the date on which the document is—</P>
                            <P>(1) Hand delivered;</P>
                            <P>(2) Mailed; or</P>
                            <P>(3) Emailed.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 299.23</SECTNO>
                            <SUBJECT>Bypass procedures.</SUBJECT>
                            <P>Sections 299.24 through 299.26 describe the procedures that the Secretary uses in conducting a show-cause hearing. The hearing officer may modify the procedures for a particular case if all parties agree that the modification is appropriate.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 299.24</SECTNO>
                            <SUBJECT>Appointment and functions of a hearing officer.</SUBJECT>
                            <P>(a) If an agency, consortium, or entity requests a hearing to show cause why the Secretary should not implement a bypass, the Secretary appoints a hearing officer and notifies appropriate representatives of the affected private school children, teachers or other educational personnel, or families that they may participate in the hearing.</P>
                            <P>(b) The hearing officer has no authority to require or conduct discovery or to rule on the validity of any statute or regulation.</P>
                            <P>(c) The hearing officer notifies the agency, consortium, or entity and representatives of the private school children, teachers or other educational personnel, or families of the time and place of the hearing.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 299.25</SECTNO>
                            <SUBJECT>Hearing procedures.</SUBJECT>
                            <P>(a) The following procedures apply to a show-cause hearing regarding implementation of a bypass:</P>
                            <P>(1) The hearing officer arranges for a transcript to be created.</P>
                            <P>(2) The agency, consortium, or entity and representatives of the private school children, teachers or other educational personnel, or families each may—</P>
                            <P>(i) Be represented by legal counsel; and</P>
                            <P>(ii) Submit oral or written evidence and arguments at the hearing.</P>
                            <P>(b) Within 10 days after the hearing, the hearing officer—</P>
                            <P>(1) Indicates that a decision will be issued based on the existing record; or</P>
                            <P>(2) Requests further information from the agency, consortium, or entity, representatives of the private school children, teachers or other educational personnel, or families, or Department officials.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 299.26</SECTNO>
                            <SUBJECT>Decision.</SUBJECT>
                            <P>(a)(1) Within 120 days after the record of a show-cause hearing is closed, the hearing officer issues a written decision on whether the Secretary should implement a bypass.</P>
                            <P>
                                (2) The hearing officer sends copies of the decision to the agency, consortium, or entity; representatives of the private school children, teachers or other 
                                <PRTPAGE P="2031"/>
                                educational personnel, or families; and the Secretary.
                            </P>
                            <P>(b) Within 30 days after receiving the hearing officer's decision, the agency, consortium, or entity, and representatives of the private school children, teachers or other educational personnel, or families may each submit to the Secretary written comments on the decision.</P>
                            <P>(c) The Secretary may adopt, reverse, modify, or remand the hearing officer's decision.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 299.27</SECTNO>
                            <SUBJECT>Judicial review.</SUBJECT>
                            <P>If an agency, consortium, or entity is dissatisfied with the Secretary's final action after a proceeding under §§ 299.13 through 299.26, it may, within 60 days after receiving notice of that action, file a petition for review with the United States Court of Appeals for the circuit in which it is located.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 299.28</SECTNO>
                            <SUBJECT>Continuation of a bypass.</SUBJECT>
                            <P>The Secretary continues a bypass until the Secretary determines, in consultation with the relevant agency, consortium, or entity and representatives of the affected private school children, teachers or other educational personnel, or families, that there will no longer be any failure or inability on the part of the agency, consortium, or entity to meet the requirements for providing services.</P>
                        </SECTION>
                    </SUBPART>
                </SUPLINF>
                <FRDOC>[FR Doc. 2023-27682 Filed 1-10-24; 8:45 am]</FRDOC>
                <BILCOD>BILLING CODE 4000-01-P</BILCOD>
            </PRORULE>
        </PRORULES>
    </NEWPART>
    <VOL>89</VOL>
    <NO>8</NO>
    <DATE>Thursday, January 11, 2024</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="2033"/>
            <PARTNO>Part III</PARTNO>
            <AGENCY TYPE="P">Federal Trade Commission</AGENCY>
            <CFR>16 CFR Part 312</CFR>
            <TITLE>Children's Online Privacy Protection Rule; Proposed Rule</TITLE>
        </PTITLE>
        <PRORULES>
            <PRORULE>
                <PREAMB>
                    <PRTPAGE P="2034"/>
                    <AGENCY TYPE="N">FEDERAL TRADE COMMISSION</AGENCY>
                    <CFR>16 CFR Part 312</CFR>
                    <RIN>RIN 3084-AB20</RIN>
                    <SUBJECT>Children's Online Privacy Protection Rule</SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Federal Trade Commission.</P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Notice of proposed rulemaking.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>The Commission proposes to amend the Children's Online Privacy Protection Rule, consistent with the requirements of the Children's Online Privacy Protection Act. The proposed modifications are intended to respond to changes in technology and online practices, and where appropriate, to clarify and streamline the Rule. The proposed modifications, which are based on the FTC's review of public comments and its enforcement experience, are intended to clarify the scope of the Rule and/or strengthen its protection of personal information collected from children.</P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>Comments must be received by March 11, 2024.</P>
                    </EFFDATE>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P>
                            Interested parties may file a comment online or on paper by following the instructions in the Request for Comment part of the 
                            <E T="02">SUPPLEMENTARY INFORMATION</E>
                             section below. Write “COPPA Rule Review, Project No. P195404” on your comment and file your comment online at 
                            <E T="03">https://www.regulations.gov</E>
                             by following the instructions on the web-based form. If you prefer to file your comment on paper, mail your comment to the following address: Federal Trade Commission, Office of the Secretary, 600 Pennsylvania Avenue NW, Suite CC-5610 (Annex E), Washington, DC 20580.
                        </P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>Manmeet Dhindsa (202-326-2877) or James Trilling (202-326-3497), Division of Privacy and Identity Protection, Bureau of Consumer Protection, Federal Trade Commission.</P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P/>
                    <HD SOURCE="HD1">I. Background</HD>
                    <P>
                        Congress enacted the Children's Online Privacy Protection Act (“COPPA” or “COPPA statute”), 15 U.S.C. 6501 
                        <E T="03">et seq.,</E>
                         in 1998. The COPPA statute directed the Federal Trade Commission (“Commission” or “FTC”) to promulgate regulations implementing COPPA's requirements. On November 3, 1999, the Commission issued its Children's Online Privacy Protection Rule, 16 CFR part 312 (“COPPA Rule” or “Rule”), which became effective on April 21, 2000.
                        <SU>1</SU>
                        <FTREF/>
                         Section 6506 of the COPPA statute and § 312.11 of the initial Rule required that the Commission initiate a review no later than five years after the initial Rule's effective date to evaluate the Rule's implementation. The Commission commenced this mandatory review on April 21, 2005.
                        <SU>2</SU>
                        <FTREF/>
                         After receiving and considering extensive public comment, the Commission determined in March 2006 to retain the COPPA Rule without change.
                        <SU>3</SU>
                        <FTREF/>
                         In 2010, the Commission once again undertook a review of the COPPA Rule to determine whether the Rule was keeping pace with changing technology. After notice and comment, the Commission issued final amendments to the Rule, which became effective on July 1, 2013 (“2013 Amendments”).
                        <SU>4</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             Children's Online Privacy Protection Rule, Statement of Basis and Purpose, 64 FR 59888 (Nov. 3, 1999), available at 
                            <E T="03">https://www.federalregister.gov/documents/1999/11/03/99-27740/childrens-online-privacy-protection-rule.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2</SU>
                             Children's Online Privacy Protection Rule, Request for Public Comment, 70 FR 21107 (Apr. 22, 2005), available at 
                            <E T="03">https://www.federalregister.gov/documents/2005/04/22/05-8160/childrens-online-privacy-protection-rule-request-for-comments.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>3</SU>
                             Children's Online Privacy Protection Rule, Retention of Rule Without Modification, 71 FR 13247 (Mar. 15, 2006), available at 
                            <E T="03">https://www.federalregister.gov/documents/2006/03/15/06-2356/childrens-online-privacy-protection-rule.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>4</SU>
                             
                            <E T="03">See</E>
                             Children's Online Privacy Protection Rule, Statement of Basis and Purpose, 78 FR 3972 (Jan. 17, 2013), available at 
                            <E T="03">https://www.federalregister.gov/documents/2013/01/17/2012-31341/childrens-online-privacy-protection-rule.</E>
                        </P>
                    </FTNT>
                    <P>
                        The COPPA Rule imposes certain requirements on operators of websites 
                        <SU>5</SU>
                        <FTREF/>
                         or online services directed to children under 13 years of age, and on operators of websites or online services that have actual knowledge that they are collecting personal information online from a child under 13 years of age (collectively, “operators”). The Rule requires that operators provide notice to parents and obtain verifiable parental consent before collecting, using, or disclosing personal information from children under 13 years of age.
                        <SU>6</SU>
                        <FTREF/>
                         Additionally, the Rule requires that operators must provide parents the opportunity to review the types or categories of personal information collected from their child, the opportunity to delete the collected information, and the opportunity to prevent further use or future collection of personal information from their child.
                        <SU>7</SU>
                        <FTREF/>
                         The Rule also requires operators to keep personal information they collect from children secure, including by imposing retention and deletion requirements, and prohibits them from conditioning children's participation in activities on the collection of more personal information than is reasonably necessary to participate in such activities.
                        <SU>8</SU>
                        <FTREF/>
                         The Rule contains a “safe harbor” provision enabling industry groups or others to submit to the Commission for approval self-regulatory guidelines that would implement the Rule's protections.
                        <SU>9</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>5</SU>
                             
                            <E T="03">See</E>
                             Part IV for further discussion of the Commission's proposal to change the term “Web site” to “Web site” throughout the Rule. This Notice of Proposed Rulemaking incorporates this proposed change in all instances in which the term “Web site” is used.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>6</SU>
                             16 CFR 312.3, 312.4, and 312.5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>7</SU>
                             16 CFR 312.3 and 312.6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>8</SU>
                             16 CFR 312.3, 312.7, 312.8, and 312.10.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>9</SU>
                             16 CFR 312.11.
                        </P>
                    </FTNT>
                    <P>
                        The 2013 Amendments 
                        <SU>10</SU>
                        <FTREF/>
                         revised the COPPA Rule to address changes in the way children use and access the internet, including through the increased use of mobile devices and social networking. In particular, the 2013 Amendments:
                    </P>
                    <FTNT>
                        <P>
                            <SU>10</SU>
                             78 FR 3972.
                        </P>
                    </FTNT>
                    <P>• Modified the definition of “operator” to make clear that the Rule covers an operator of a child-directed website or online service that integrates outside services—such as plug-ins or advertising networks—that collect personal information from the website's or online service's visitors, and expanded the definition of “website or online service directed to children” to clarify that those outside services are subject to the Rule where they have actual knowledge that they are collecting personal information directly from users of a child-directed website or online service;</P>
                    <P>• Permitted a subset of child-directed websites or online services that do not target children as their primary audience to differentiate among users, requiring them to comply with the Rule's obligations only as to users who identify as under the age of 13;</P>
                    <P>• Expanded the definition of “personal information” to include geolocation information; photos, videos and audio files containing a child's image or voice; and persistent identifiers that can be used to recognize a user over time and across different websites or online services;</P>
                    <P>• Streamlined the direct notice requirements to ensure that key information is presented to parents in a succinct “just-in-time” notice;</P>
                    <P>• Expanded the non-exhaustive list of acceptable methods for obtaining prior verifiable parental consent;</P>
                    <P>
                        • Created three new exceptions to the Rule's notice and consent requirements, including for the use of persistent identifiers for the support for the internal operations of a website or online service;
                        <PRTPAGE P="2035"/>
                    </P>
                    <P>• Strengthened data security protections by requiring operators to take reasonable steps to release children's personal information only to service providers and third parties who are capable of maintaining the confidentiality, security, and integrity of such information, and required reasonable data retention and deletion procedures; and</P>
                    <P>
                        • Strengthened the Commission's oversight of self-regulatory safe harbor programs.
                        <SU>11</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>11</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <P>
                        On July 25, 2019, the FTC announced in the 
                        <E T="04">Federal Register</E>
                         that it was again undertaking a review of the COPPA Rule, noting that questions had arisen about the Rule's application to the educational technology (“ed tech”) sector, voice-enabled connected devices, and general audience platforms that host third-party child-directed content (“2019 Rule Review Initiation”).
                        <SU>12</SU>
                        <FTREF/>
                         The Commission sought public comment on these and other issues in its 2019 Rule Review Initiation. In addition to its standard regulatory review questions to determine whether the Commission should retain, eliminate, or modify the COPPA Rule, the Commission asked whether the 2013 Amendments have resulted in stronger protections for children and whether the revisions have had any negative consequences. The Commission also posed specific questions about the Rule's provisions, including the Rule's definitions, notice and consent requirements, access and deletion rights, security requirements, and safe harbor provisions.
                    </P>
                    <FTNT>
                        <P>
                            <SU>12</SU>
                             
                            <E T="03">See</E>
                             Children's Online Privacy Protection Rule, Request for Public Comment, 84 FR 35842 (July 25, 2019), available at 
                            <E T="03">https://www.federalregister.gov/documents/2019/07/25/2019-15754/request-for-public-comment-on-the-federal-trade-commissions-implementation-of-the-childrens-online.</E>
                        </P>
                    </FTNT>
                    <P>
                        During the comment period, the Commission held a public workshop on October 7, 2019, to discuss in detail several of the areas where it sought public comment (“COPPA Workshop”).
                        <SU>13</SU>
                        <FTREF/>
                         Specific discussion included such topics as application of the COPPA Rule to the ed tech sector, how the development of new technologies and business models have affected children's privacy, and whether the 2013 Amendments have worked as intended.
                    </P>
                    <FTNT>
                        <P>
                            <SU>13</SU>
                             
                            <E T="03">See The Future of the COPPA Rule: An FTC Workshop</E>
                             (Oct. 7, 2019), available at 
                            <E T="03">https://www.ftc.gov/news-events/events/2019/10/future-coppa-rule-ftc-workshop;</E>
                             84 FR 35842.
                        </P>
                    </FTNT>
                    <P>
                        In response to the 2019 Rule Review Initiation, the Commission received more than 175,000 comments from various stakeholders, including industry representatives, video content creators, consumer advocacy groups, academics, technologists, FTC-approved COPPA Safe Harbor programs, members of Congress, and individual members of the public. While many of these comments expressed overall support for COPPA,
                        <SU>14</SU>
                        <FTREF/>
                         the comments identified a number of areas where the Commission could provide additional clarification or guidance about the COPPA Rule's requirements. The comments also proposed a number of potential changes to the Rule.
                    </P>
                    <FTNT>
                        <P>
                            <SU>14</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Joint Comment of the Attorneys General of New Mexico, Connecticut, Delaware, the District of Columbia, Idaho, Illinois, Iowa, Kentucky, Louisiana, Maine, Maryland, Massachusetts, Michigan, Minnesota, Mississippi, Nebraska, Nevada, New York, North Carolina, Oregon, Pennsylvania, Tennessee, Vermont, Virginia, and Washington (“Joint Attorneys General”), at 2 (“As more and more of our lives are lived online, and as digital tools make their way into our schools and into our lives at ever-earlier ages, rules like the COPPA Rule must continue not only to exist, but grow and adapt to ever-changing regulatory landscapes”); SuperAwesome Inc. (“SuperAwesome”), at 8 (“As a result of the rapid evolution of the [I]nternet economy and in particular services that rely on user data, the need for the COPPA Rule has never been greater”); Privacy Vaults Online, Inc. (“PRIVO”), at 2 (“In PRIVO's experience, both children and operators benefit when COPPA-compliant processes are in place to permit operators to offer relevant content to children and permit children to engage with that content in an appropriate and permissioned manner”); The LEGO Group (“Lego”), at 3 (“COPPA has played and continues to play an important role in raising awareness of the importance of protecting children's privacy online. COPPA has been effective because of its future-proof language, which has allowed it to protect against real harms today, that were not clear when the Rule was enacted in 1998”); Internet Association, at 1 (“Nearly 20 years after its adoption, COPPA remains an important mechanism for preserving parental choice with respect to the privacy and security of personal information about children under 13”); Consumer Reports, at 5 (“Due to the increase in connected products generally, and children's products specifically, there is only heightened need for the COPPA rules in the coming years”); and Association of National Advertisers (“ANA”), at 3 (“The current COPPA Rule is protective of children's privacy interests and generally workable for businesses. The FTC has given parents the ability to protect children's privacy and entities clear `rules of the road' regarding how to comply with COPPA”). 
                            <E T="03">But see</E>
                             Committee for Justice, at 2 (“In addition to being ineffective at preventing the personal information of children from being collected without parental consent, [COPPA's] approach has the effect of burdening sites targeted towards children”); International Center for Law &amp; Economics (“ICLE”), at 3 (regarding the aggregate costs and benefits of the Rule, “[t]he benefits are unclear, but the costs—in the form of restricting the ability of family-friendly content creators to monetize their products—are real”); Connected Camps, at 1-3 (stating that COPPA has resulted in a number of unintended consequences based on mistaken assumptions).
                        </P>
                    </FTNT>
                    <P>Following consideration of the submitted public comments, viewpoints expressed during the COPPA Workshop, and the Commission's experience enforcing the Rule, the Commission proposes modifying most provisions of the Rule. Part II of this notice of proposed rulemaking (“NPRM”) discusses commenters' calls to expand the COPPA Rule's coverage by amending the definition of “website or online service directed to children” or by changing the Rule's actual knowledge standard. Part III of this NPRM discusses commenters' viewpoints on whether the Commission should permit general audience platforms that allow third parties to upload content to the platform to rebut the presumption that all users of uploaded child-directed content are children. Part IV addresses the Commission's proposed modifications to the Rule. Parts V-X provide information about requests for comment, the Paperwork Reduction Act, the Regulatory Flexibility Act, communications by outside parties to the Commissioners or their advisors, questions for the proposed revisions to the Rule, a list of subjects in the Rule, and the amended text of the Rule.</P>
                    <HD SOURCE="HD1">II. Comments on Expanding the COPPA Rule's Coverage</HD>
                    <P>As part of its 2019 Rule Review Initiation, the Commission requested comment on questions regarding whether the Commission should revise the definition of “website or online service directed to children.” In response, the Commission received various comments regarding expanding the COPPA Rule's coverage by either amending the definition of “website or online service directed to children” or by changing the Rule's actual knowledge standard. This Part includes discussion of comments advocating for and against such expansions.</P>
                    <HD SOURCE="HD2">A. Amending the Definition of “Website or Online Service Directed to Children”</HD>
                    <P>
                        In its 2019 Rule Review Initiation, the Commission asked for comment on various aspects of the Rule's definition of “website or online service directed to children.” Among other questions, the Commission asked whether it should amend the definition to address websites and online services that do not include traditionally child-oriented activities but still have large numbers of child users.
                        <SU>15</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>15</SU>
                             Other aspects of this definition are discussed in Part IV.A.5.
                        </P>
                    </FTNT>
                    <P>
                        Some commenters argued that the definition of “website or online service directed to children” should be modified to include sites and services with large numbers of children, those with a certain percentage of child users, or those that include child-attractive 
                        <PRTPAGE P="2036"/>
                        content.
                        <SU>16</SU>
                        <FTREF/>
                         For example, FTC-approved COPPA Safe Harbor program PRIVO asserted that general audience services with large numbers of children should be required to comply with COPPA, noting that “[s]ervices not targeted to children that have large numbers of children must be addressed as it can result in online harm to the child due to inherent privacy and safety risks.” 
                        <SU>17</SU>
                        <FTREF/>
                         PRIVO further argued that the Commission should define thresholds for the number of child users at which COPPA's protections must be provided.
                        <SU>18</SU>
                        <FTREF/>
                         Similarly, Common Sense Media encouraged the Commission to interpret the definition of “website or online service directed to children” to include “sites and services that attract, or are likely to be accessed by, disproportionate numbers of children.” 
                        <SU>19</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>16</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Children's Advertising Review Unit (“CARU”), at 6-7; PRIVO, at 7; Common Sense Media, at 12.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>17</SU>
                             PRIVO, at 7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>18</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>19</SU>
                             Common Sense Media, at 12, 15-17.
                        </P>
                    </FTNT>
                    <P>
                        However, other commenters opposed expanding the definition of “website or online service directed to children” in such ways.
                        <SU>20</SU>
                        <FTREF/>
                         For example, The Toy Association opposed the adoption of a numerical or percentage audience threshold as a determinative factor in identifying child-directed websites or online services.
                        <SU>21</SU>
                        <FTREF/>
                         Similarly, panelists during the COPPA Workshop noted that “[a]ttractive to children is very different from targeted to children,” 
                        <SU>22</SU>
                        <FTREF/>
                         and that COPPA's statutory language is “child-directed” and not “child-attractive.” 
                        <SU>23</SU>
                        <FTREF/>
                         Commenters raised additional concerns with expanding the definition to include sites and services that do not include child-oriented activities but have large numbers of children, including because such a change would be inconsistent with the statute,
                        <SU>24</SU>
                        <FTREF/>
                         decrease online offerings for children,
                        <SU>25</SU>
                        <FTREF/>
                         be unduly burdensome to operators of non-child-directed websites or online services,
                        <SU>26</SU>
                        <FTREF/>
                         and lead to regulatory uncertainty.
                        <SU>27</SU>
                        <FTREF/>
                         Some commenters also noted that this amendment would be unnecessary since the definition already includes “competent and reliable empirical evidence regarding audience composition” as a factor to consider in determining whether a site or service is directed to children.
                        <SU>28</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>20</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Computer &amp; Communications Industry Association (“CCIA”), at 6-7; U.S. Chamber of Commerce, at 3-4; ANA, at 6-7; Network Advertising Initiative (“NAI”), at 3-5; ViacomCBS Inc. (“Viacom”), at 5-6; Internet Association, at 9; Entertainment Software Association (“ESA”), at 8-12; TechFreedom, at 18.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>21</SU>
                             The Toy Association, at 9-10 (adding that “[d]oing so is inconsistent with traditional norms for advertising and risks undermining the intent of the statute by elevating a single factor over others. Such an approach is also entirely inconsistent with how the FTC and advertising self-regulatory bodies handle advertising”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>22</SU>
                             P. Aftab, Remarks from the 
                            <E T="03">Scope of the COPPA Rule</E>
                             panel at 
                            <E T="03">The Future of the COPPA Rule: An FTC Workshop</E>
                             52 (Oct. 7, 2019), available at 
                            <E T="03">https://www.ftc.gov/news-events/events/2019/10/future-coppa-rule-ftc-workshop.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>23</SU>
                             
                            <E T="03">See</E>
                             D. McGowan, Remarks from the 
                            <E T="03">Scope of the COPPA Rule</E>
                             panel at 
                            <E T="03">The Future of the COPPA Rule: An FTC Workshop</E>
                             48 (Oct. 7, 2019), available at 
                            <E T="03">https://www.ftc.gov/news-events/events/2019/10/future-coppa-rule-ftc-workshop.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>24</SU>
                             
                            <E T="03">See, e.g.,</E>
                             CCIA, at 6; NAI, at 3; ANA, at 6; Viacom, at 5-6; U.S. Chamber of Commerce, at 3-4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>25</SU>
                             
                            <E T="03">See, e.g.,</E>
                             ANA, at 7 (noting that “[b]roadening the Rule's scope by making it applicable to websites or online services that do not include traditionally child-oriented activities, but that have large numbers of child users, would negatively impact consumers and children because operators would be disincentivized from producing content, products, and online services that, while not directed to them, have the potential to attract child users”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>26</SU>
                             
                            <E T="03">See, e.g.,</E>
                             CCIA, at 7 (noting that “[a]udience metrics alone are a poor basis for determining COPPA applicability because they can shift over time, may be highly responsive to fads, cannot necessarily be predicted by an operator at the outset of (launching a website or online service, and cannot be reliably calculated”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>27</SU>
                             
                            <E T="03">See, e.g.,</E>
                             ESA, at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>28</SU>
                             
                            <E T="03">See, e.g.,</E>
                             CCIA, at 6-7; ANA, at 6-7.
                        </P>
                    </FTNT>
                    <P>
                        During the Rule review that resulted in the 2013 Amendments, the Commission considered amending the definition of “website or online service directed to children” to cover sites or services that “[b]ased on the overall content of the website or online service, [are] likely to attract an audience that includes a disproportionately large percentage of children under age 13 as compared to the percentage of such children in the general population. . . .” 
                        <SU>29</SU>
                        <FTREF/>
                         In response, the Commission received numerous comments raising concerns that such a standard was vague, potentially unconstitutional, and unduly expansive, and could lead to widespread age-screening and more intensive age verification across all websites and online services.
                        <SU>30</SU>
                        <FTREF/>
                         In ultimately declining to adopt this standard, the Commission stated it did not intend to expand the reach of the Rule to include additional sites and services.
                    </P>
                    <FTNT>
                        <P>
                            <SU>29</SU>
                             Children's Online Privacy Protection Rule, Supplemental Notice of Proposed Rulemaking; Request for Comment, 77 FR 46643, 46646 (Aug. 6, 2012), available at 
                            <E T="03">https://www.federalregister.gov/documents/2012/08/06/2012-19115/childrens-online-privacy-protection-rule.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>30</SU>
                             
                            <E T="03">See</E>
                             78 FR 3972 at 3983-3984.
                        </P>
                    </FTNT>
                    <P>The Commission again declines to modify the Rule in this manner. The definition of “website or online service directed to children” includes a number of factors the Commission will consider in determining whether a particular website or online service is child-directed, including consideration of “competent and reliable empirical evidence regarding audience composition.” Because the Commission already considers the demographics of a website's or online service's user base in its determination, the Commission does not believe it is necessary to modify the definition.</P>
                    <P>
                        Similarly, the Commission also previously considered amending the Rule to set forth that websites and online services with a specified percentage of child users would be considered directed to children. As part of the Rule review that led to the 2013 Amendments, the Institute for Public Representation recommended that the Commission amend the Rule so that a website per se should be deemed “directed to children” if audience demographics show that 20% or more of its visitors are children under age 13.
                        <SU>31</SU>
                        <FTREF/>
                         The Commission determined not to adopt this as a per se legal standard, in part because the Commission noted that the definition of “website or online service directed to children” already positions the Commission to consider empirical evidence of the number of child users on a site.
                    </P>
                    <FTNT>
                        <P>
                            <SU>31</SU>
                             Children's Online Privacy Protection Rule, Proposed Rule; Request for Comment, 76 FR 59804, 59814 (Sept. 27, 2011), available at 
                            <E T="03">https://www.federalregister.gov/documents/2011/09/27/2011-24314/childrens-online-privacy-protection-rule.</E>
                        </P>
                    </FTNT>
                    <P>
                        While the Commission continues to believe that there are good reasons not to ground COPPA liability simply on an assessment of the percentage of a site's or service's audience that is under 13, the Commission would like to obtain additional comment on whether it should provide an exemption under which an operator's site or service would not be deemed child-directed if the operator undertakes an analysis of the site's or service's audience composition and determines that no more than a specific percentage of its users are likely to be children under 13. In particular, the Commission seeks comment on (1) whether the Rule should provide an exemption or other incentive to encourage operators to conduct an analysis of their sites' or services' user bases; (2) what the reliable means are by which operators can determine the likely ages of a site's or service's users; (3) whether and how the COPPA Rule should identify such means; (4) what the appropriate percentage of users should be to qualify for this potential exemption; 
                        <SU>32</SU>
                        <FTREF/>
                         and (5) 
                        <PRTPAGE P="2037"/>
                        whether such an exemption would be inconsistent with the COPPA Rule's multi-factor test for determining whether a website or online service, or a portion thereof, is directed to children.
                    </P>
                    <FTNT>
                        <P>
                            <SU>32</SU>
                             Because this exemption would rely on a single factor (
                            <E T="03">i.e.,</E>
                             audience composition) to exempt sites or services from being deemed child-directed, the Commission anticipates that the appropriate 
                            <PRTPAGE/>
                            percentage to qualify for this exemption would be very low.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">B. Changing the COPPA Rule's “Actual Knowledge” Standard</HD>
                    <P>
                        In responding to the Commission's request for comment on the definition of “website or online service directed to children,” a number of commenters recommended that the Commission revise COPPA's actual knowledge standard by moving to a constructive knowledge standard.
                        <SU>33</SU>
                        <FTREF/>
                         Namely, these commenters sought to bring within COPPA's jurisdiction those operators that have reason to know they may be collecting information from a child and those operators that willfully avoid gaining actual knowledge that they are collecting information from a child. Common Sense Media, for example, encouraged the Commission to broaden its view of “actual knowledge” to prevent the “willful disregard that children's personal[ ] information is being collected.” 
                        <SU>34</SU>
                        <FTREF/>
                         Other commenters, referencing the California Consumer Privacy Act, similarly recommended that COPPA's actual knowledge standard should cover operators of general audience sites and services that ignore or willfully disregard the age of their users.
                        <SU>35</SU>
                        <FTREF/>
                         Children's privacy advocate 5Rights Foundation further recommended that the Commission should consider current and historic audience composition evidence of both the specific service and similar services in determining whether an operator has met the actual knowledge standard.
                        <SU>36</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>33</SU>
                             
                            <E T="03">See, e.g.,</E>
                             London School of Economics and Political Science, at 9 (noting that the FTC should re-examine its definition of child-directed websites and online services to include “`constructive knowledge' 
                            <E T="03">i.e.,</E>
                             what an operator ought to know about its users if they have carried their work in due diligence”) (bold typeface omitted); S. Egelman, at 3-4 (asserting that “actual knowledge” should include third-party recipients of data from a mobile app that can be identified as child-directed); Color of Change, at 4-5 (advocating that the FTC should move from an actual knowledge standard to a constructive knowledge standard); SuperAwesome, at 18 (recommending the Commission amend the definition of “website or online service directed to children” to include situations where an operator has, or should be reasonably expected to have, actual knowledge that it is collecting information from children or from users of a child-directed website or online service).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>34</SU>
                             Common Sense Media, at 12.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>35</SU>
                             5Rights Foundation, at 3-4; Consumer Reports, at 8-9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>36</SU>
                             5Rights Foundation, at 4.
                        </P>
                    </FTNT>
                    <P>
                        A number of industry commenters opposed the Commission adopting a constructive knowledge standard. Several of these commenters pointed to the COPPA statute's language 
                        <SU>37</SU>
                        <FTREF/>
                         and argued that the Commission lacks authority to change the actual knowledge standard.
                        <SU>38</SU>
                        <FTREF/>
                         Others asserted that a constructive knowledge standard would result in operators collecting additional data from all users, including children, and might lead to a reduction in available online content because operators may decide to withdraw content intended for teenagers and young adults to avoid the risk of interacting with children.
                        <SU>39</SU>
                        <FTREF/>
                         Additionally, the Association of National Advertisers stated that a constructive knowledge standard would conflict with the Commission's long-established position that operators are not obligated to investigate the age of their users 
                        <SU>40</SU>
                        <FTREF/>
                         and would increase uncertainty about companies' potential COPPA obligations.
                        <SU>41</SU>
                        <FTREF/>
                         Similarly, Engine, a non-profit policy organization, noted that moving from the “bright-line” standard of actual knowledge to a less clear constructive knowledge standard could disproportionately burden small companies and start-ups.
                        <SU>42</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>37</SU>
                             15 U.S.C. 6502(a)(1) (providing that “[i]t is unlawful for an operator of a website or online service directed to children, or any operator that has actual knowledge that it is collecting personal information from a child, to collect personal information from a child in a manner that violates the regulations prescribed under subsection (b)”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>38</SU>
                             
                            <E T="03">See, e.g.,</E>
                             ANA, at 4-5; Interactive Advertising Bureau (“IAB”), at 4-5; internet Association, at 19; Software &amp; Information Industry Association (“SIIA”), at 4; The Toy Association, at 3, 8, 10, 16.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>39</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Family Online Safety Institute (“FOSI”), at 6 (noting that “[i]f a constructive knowledge standard were imposed, it is likely that all general audience sites and services would start treating all users as children, or turn off any services that might benefit minors clearly older than 13. This would have serious implications for free speech, or could lead to an increase in age gating, which is ineffective and often results—paradoxically—in increased collection of data from all users, including children”); Digital Content Next, at 1 (stating that “[w]e believe that expanding the actual knowledge standard might inadvertently harm the privacy of children in two ways. First, if COPPA were expanded to apply in situations where a company has no actual knowledge that the consumer is under 13 years of age or when the company is not providing services directed to children, companies would need to collect significantly more data from children and their parents or guardians to meet the obligations of COPPA including obtaining consent. Second, in order to avoid COPPA compliance, some companies may decide to withdraw content that is intended for teenagers or young adults in order to avoid the risk of interacting with children”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>40</SU>
                             
                            <E T="03">See, e.g.,</E>
                             64 FR 59888 at 59892 (noting that “COPPA does not require operators of general audience sites to investigate the ages of their site's visitors . . .”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>41</SU>
                             
                            <E T="03">See</E>
                             ANA, at 5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>42</SU>
                             Engine, at 5.
                        </P>
                    </FTNT>
                    <P>
                        The Commission declines to change the Rule to bring operators of general audience sites and services under COPPA's jurisdiction based on constructive knowledge. As the Commission noted in 2011, Congress has already rejected a constructive knowledge approach with respect to COPPA. Specifically, the legislative history indicates that Congress originally drafted COPPA to apply to operators that “knowingly” collect personal information from children, a standard which would include actual, implied, or constructive knowledge.
                        <SU>43</SU>
                        <FTREF/>
                         After consideration of witness testimony, however, Congress modified the knowledge standard in the final legislation to require “actual knowledge.” 
                        <SU>44</SU>
                        <FTREF/>
                         This deliberate decision to reject the more expansive approach makes clear that Congress did not intend for the “actual knowledge” standard to be read to include the concept of constructive knowledge. The Commission rejected calls for a move to a lesser knowledge standard for general audience operators while considering the 2013 Amendments,
                        <SU>45</SU>
                        <FTREF/>
                         and the Commission again declines to do so.
                        <SU>46</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>43</SU>
                             
                            <E T="03">See</E>
                             76 FR 59804 at 59806, n. 26 (citing Senate and House bills), noting that “Under federal case law, the term `knowingly' encompasses actual, implied, and constructive knowledge.”
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>44</SU>
                             
                            <E T="03">Id.</E>
                             (citing 
                            <E T="03">internet Privacy Hearing: Hearing on S. 2326 Before the Subcomm. On Commc'ns of the S. Comm. On Commerce, Science, &amp; Transp.,</E>
                             105th Cong. 1069 (1998)).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>45</SU>
                             
                            <E T="03">See</E>
                             76 FR 59804 at 59806.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>46</SU>
                             As noted above, various commenters recommended that the Rule's actual knowledge standard cover operators of general audience sites and services that ignore or willfully disregard the age of their users. 
                            <E T="03">See, e.g.,</E>
                             Common Sense Media, at 12; 5Rights Foundation, at 3-4; Consumer Reports, at 8-9.
                        </P>
                        <P>
                            The concept of actual knowledge includes willful disregard. 
                            <E T="03">See, e.g., Glob.-Tech Appliances, Inc.</E>
                             v. 
                            <E T="03">SEB S.A.,</E>
                             563 U.S. 754, 766 (2011) (noting that “[i]t is also said that persons who know enough to blind themselves to direct proof of critical facts in effect have actual knowledge of those facts”). Therefore, the Rule already applies to instances in which an operator of a general audience site or service willfully disregards the fact that a particular user is a child.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">III. Comments on the Rebuttable Presumption</HD>
                    <P>
                        Operators of websites or online services directed to children that collect personal information from their users must comply with COPPA regardless of whether they have actual knowledge that a particular user is, in fact, a child. Accordingly, as a practical matter, operators of child-directed sites and services must presume that all users are children.
                        <SU>47</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>47</SU>
                             
                            <E T="03">See, e.g.,</E>
                             78 FR 3972 at 3984 (“The Commission retains its longstanding position that child-directed sites or services whose primary target audience is children must continue to presume all users are children and to provide COPPA protections accordingly”).
                        </P>
                    </FTNT>
                    <P>
                        Through the 2013 Amendments, the Commission extended COPPA liability to operators that have actual knowledge 
                        <PRTPAGE P="2038"/>
                        they are collecting personal information directly from the users of another website or online service that is child-directed.
                        <SU>48</SU>
                        <FTREF/>
                         Under the Rule, such an operator “has effectively adopted that child-directed content as its own and that portion of its service may appropriately be deemed to be directed to children.” 
                        <SU>49</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>48</SU>
                             
                            <E T="03">See</E>
                             16 CFR 312.2, definition of “website or online service directed to children,” paragraph 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>49</SU>
                             78 FR 3972 at 3978.
                        </P>
                    </FTNT>
                    <P>
                        The Commission sought comments in its 2019 Rule Review Initiation on whether it should permit general audience platforms that allow third parties to upload content to the platform to rebut the presumption that all users of uploaded child-directed content are in fact children. In seeking comment on this issue, the Commission stated that absent actual knowledge that the uploaded content is child-directed, the platform operator is not responsible for complying with the Rule. Therefore, the FTC noted that the platform operator may have an incentive to avoid gaining knowledge about the nature of the uploaded content.
                        <SU>50</SU>
                        <FTREF/>
                         The Commission asked whether allowing general audience platform operators to rebut this presumption, thereby allowing them to treat users under age 13 differently from older users, would incentivize platform operators to take affirmative steps to identify child-directed content and treat users of that content in accordance with the Rule. The Commission also asked about the types of steps platforms could take to overcome the presumption that all users of child-directed content are children.
                    </P>
                    <FTNT>
                        <P>
                            <SU>50</SU>
                             84 FR 35842 at 35845-35846. In extending liability to operators of general audience sites and services with actual knowledge, the Commission discussed, but expressly rejected, imposing a “reason to know” standard. 78 FR 3972 at 3977-78. Accordingly, the 2013 Amendments do not impose a duty on operators of general audience websites and online services to investigate whether they are collecting personal information from users of child-directed sites or services.
                        </P>
                    </FTNT>
                    <P>
                        Relying on a variety of arguments, many consumer and privacy advocates opposed the notion of modifying the Rule to allow operators of general audience platforms to rebut the presumption that users of child-directed content uploaded to the platform by third parties are children. For example, a coalition of consumer organizations argued against allowing general audience platforms to rebut the presumption, pointing to the fact that families often share devices, accounts, and apps and that, as a result, many children likely access child-directed content while logged into a parent's account. Because of this, they argued that if the FTC modifies the presumption, “it would lead to widespread mislabeling of children as adults and large numbers of under-protected children.” 
                        <SU>51</SU>
                        <FTREF/>
                         Other commenters echoed the concern that because users in a household may share devices that are persistently signed in, operators may incorrectly determine that a user is an adult.
                        <SU>52</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>51</SU>
                             Georgetown University Law Center's Institute for Public Representation submitted a joint comment on behalf of the following nineteen consumer groups: Campaign for a Commercial-Free Childhood; The Center for Digital Democracy; Alana Institute; American Academy of Pediatrics; Badass Teachers Association; Berkeley Media Studies Group; Consumer Action; Consumer Watchdog; Defending the Early Years; Electronic Frontier Foundation; Obligation, Inc.; P.E.A.C.E (Peace Educators Allied for Children Everywhere); Parent Coalition for Student Privacy; Parents Across America; Parents Television Council; Public Citizen; Story of Stuff; TRUCE (Teachers Resisting Unhealthy Childhood Entertainment); and U.S. PIRG (“Joint Consumer Groups”), at iii, 35-36.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>52</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Consumer Reports, at 19 (“[B]rowsers and other connected services are increasingly using always-logged-in features in order to make the browsing experience more seamless across devices . . . Although this allows the company to easily sync data across devices, it means that if a child then uses that device to go to YouTube [K]ids or another service it will appear that an adult is logged on and viewing the content”); SuperAwesome, at 28 (“Given the prevalence of shared devices, the only current method to safely detect whether a child or an adult is viewing particular content is by virtue of the type of content. E.g., preschool content is mostly likely viewed by preschoolers. We are particularly concerned about logged-in parents on kids' content, where there is a presumption that the adult is enjoying the kids' content. In our experience, this is rarely the case. In the vast majority of situations it is a child using an adult's device. For this reason, the only safe approach is to default to considering the user a child based on a subjective assessment of the content”) (bold typeface omitted).
                        </P>
                    </FTNT>
                    <P>
                        Another commenter, while acknowledging the “perverse incentive” operators have to avoid gaining actual knowledge, raised concern about operators' ability to effectively establish which of their users are children.
                        <SU>53</SU>
                        <FTREF/>
                         The commenter argued that, until operators are transparent about methods used to determine which users are children and such methods are deemed effective, permitting operators to rebut the presumption may result in children being treated as adults.
                        <SU>54</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>53</SU>
                             5Rights Foundation, at 4 (also arguing that that the most privacy-protective way of addressing the incentive is to make it more difficult for operators to avoid gaining actual knowledge). 
                            <E T="03">See also</E>
                             Consumer Reports, at 18-19 (raising concern about the lack of transparency as to how general audience services determine the population of children that use the service).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>54</SU>
                             5Rights Foundation, at 4.
                        </P>
                    </FTNT>
                    <P>
                        One commenter argued that, “in the vast majority of cases,” users of child-directed content are, in fact, children.
                        <SU>55</SU>
                        <FTREF/>
                         This commenter further stated that allowing operators to rebut the presumption would prioritize allowing companies to engage in targeted advertising over ensuring that general audience platforms comply with COPPA.
                        <SU>56</SU>
                        <FTREF/>
                         Another commenter noted that, despite the alleged existence of subcultures of adult viewership of kids' content, the adult viewership of such content is likely very small.
                        <SU>57</SU>
                        <FTREF/>
                         The commenter further argued that protecting those adults' right to receive personalized advertising does not outweigh the risk of collecting personal data from children and tracking them online.
                        <SU>58</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>55</SU>
                             Consumer Reports, at 19.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>56</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>57</SU>
                             SuperAwesome, at 27.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>58</SU>
                             
                            <E T="03">Id. See also</E>
                             P. Aftab, at 15 (arguing that the convenience of adults accessing child-directed material should not outweigh children's privacy).
                        </P>
                    </FTNT>
                    <P>
                        A number of State Attorneys General argued that modifying the Rule to allow rebuttal is unlikely to incentivize platforms to identify and police child-directed content.
                        <SU>59</SU>
                        <FTREF/>
                         These commenters claimed that, even with the ability to rebut the presumption, platforms would have a greater incentive not to know about the presence of child-directed content because this would allow them to collect data for targeted ads from all users.
                        <SU>60</SU>
                        <FTREF/>
                         Additionally, an FTC-approved COPPA Safe Harbor program argued that allowing rebuttal would “be complex and unfairly benefit large tech companies who may be the only companies with the wherewithal, rich customer data, and back-end infrastructure to meet the criteria for rebuttal.” 
                        <SU>61</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>59</SU>
                             Joint Attorneys General, at 13-14 (adding that they do not support permitting a rebuttable presumption absent robust measures—beyond logged in status or periodic reauthorization—to confirm a user is 13 or older, stating that such measures can include requiring operators to ask during the account creation process whether a child ever uses the account holder's device).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>60</SU>
                             
                            <E T="03">Id.</E>
                             At 13.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>61</SU>
                             kidSAFE, at 13 (also suggesting that the Rule's existing mixed audience category could potentially serve the underlying purpose of not treating child-directed content audiences as exclusively under 13).
                        </P>
                    </FTNT>
                    <P>
                        On the other hand, a number of industry commenters supported allowing general audience platforms to rebut the presumption that all users of child-directed content are necessarily children. Google argued that rebuttal “with the appropriate safeguards, would allow those users to benefit from social engagement with the content and would allow content creators to benefit from increased monetization options, supporting continued investment in such content.” 
                        <SU>62</SU>
                        <FTREF/>
                         Without the ability to rebut the presumption, Google argued that platforms must degrade adults' user 
                        <PRTPAGE P="2039"/>
                        experience, including by preventing interactivity with other adults. Google also distinguished general audience platforms with third-party content from “static” child-directed websites intended for a single audience, noting that such platforms “have significant adult user bases that engage with traditionally child-directed content.” 
                        <SU>63</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>62</SU>
                             Google, at 7-8, 11-12 (also arguing that allowing rebuttal does not require a Rule modification because the presumption is not codified in the COPPA statute or Rule).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>63</SU>
                             
                            <E T="03">Id.</E>
                             At 8.
                        </P>
                    </FTNT>
                    <P>
                        Other commenters made similar arguments. One trade association stated that some general audience platforms “have significant adult user bases” and feature child-directed content that may appeal to users of varying ages, such as crafting or science education content.
                        <SU>64</SU>
                        <FTREF/>
                         It claimed that the audience presumption harms adult users of child-directed content by denying them the ability “to find community, learn, and discover new content.” 
                        <SU>65</SU>
                        <FTREF/>
                         Another trade association noted that adults might want “to interact with child-directed content for a variety of reasons, including nostalgia or to find content suitable for their children or students.” 
                        <SU>66</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>64</SU>
                             SIIA, at 5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>65</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>66</SU>
                             CCIA, at 13.
                        </P>
                    </FTNT>
                    <P>
                        A majority of the commenters that support modifying the Rule to permit rebuttal also recommended against the Commission proscribing specific means by which a general audience platform could rebut the presumption, calling instead for a flexible, standards-based approach that would allow platforms to employ a variety of measures to overcome the presumption. For example, citing “advancements in technology and age-screening,” one trade association recommended allowing rebuttal through reliance on a neutral age gate combined with additional steps to confirm identity, such as re-entry of a password.
                        <SU>67</SU>
                        <FTREF/>
                         The commenter also suggested that the Commission allow industry to explore alternative methods such as fingerprint, voiceprint, or device PIN.
                        <SU>68</SU>
                        <FTREF/>
                         Other commenters recommended similar flexibility in approach.
                        <SU>69</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>67</SU>
                             internet Association, at 18-19.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>68</SU>
                             
                            <E T="03">Id.</E>
                             At 19.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>69</SU>
                             
                            <E T="03">See</E>
                             Centre for Information Policy Leadership (“CIPL”), at 7 (supporting rebuttal where platforms take reasonable steps such as a neutral age gate plus additional verification, adding that the Commission should permit companies to adopt their own approach as long as they meet certain standards set by FTC); CCIA, at 14 (recommending the FTC adopt an “adaptable standards-based approach” for permitting general audience services to treat adult users interacting with child-directed content as adults, including the use of neutral age screening in conjunction with periodic password reauthorization and “verification methods that may be appropriate in additional contexts, such as submitting a voiceprint or device PIN”); Google, at 10-11 (recommending the FTC adopt a “reasonably calculated” standard similar to the parental consent standard that provides reasonable assurance that the person engaging with the content is an adult, and further suggesting use of a neutral age gate in combination with such mechanisms as password re-authentication, fingerprint, or device PINs); SIIA, at 5 (supporting a “standards-based approach to rebut presumption relying on neutral age gates plus additional steps like password authorization or alternative verification methods”); U.S. Chamber of Commerce, at 7 (supporting an adaptable standards-based approach rather than prescriptive measures); Yoti, at 16 (supporting the various mechanisms suggested in the Commission's 2019 Rule Review Initiation, but adding that because some may not work in certain circumstances, they should be options as opposed to a mandatory list).
                        </P>
                    </FTNT>
                    <P>
                        Many of the comments supporting rebuttal of the presumption also argued against tying rebuttal to a requirement that the platform investigate and identify child-directed content on the platform. These commenters asserted that such a requirement would change the Rule's actual knowledge standard to a constructive knowledge standard, which would “contravene [c]ongressional intent” 
                        <SU>70</SU>
                        <FTREF/>
                         and impose an unreasonable burden on platforms that would chill investment into the production of child-directed content.
                        <SU>71</SU>
                        <FTREF/>
                         One commenter cautioned that requiring the platform operators to identify whether uploaded content is child-directed could raise First Amendment concerns.
                        <SU>72</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>70</SU>
                             CCIA, at 14.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>71</SU>
                             
                            <E T="03">See</E>
                             U.S. Chamber of Commerce, at 7; ANA, at 5-6; Google, at 11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>72</SU>
                             Center for Democracy &amp; Technology (“CDT”), at 9 (further adding that the Commission should not consider costs and benefits unrelated to privacy (
                            <E T="03">e.g.,</E>
                             exposure to age-inappropriate content) as such concerns fall outside COPPA's statutory focus). 
                            <E T="03">But see</E>
                             SuperAwesome, at 29 (recommending the Commission consider costs and benefits unrelated to privacy, noting that allowing a rebuttal “will significantly increase the risk of exposing children to inappropriate content, including inappropriate advertising, and potentially dangerous user-generated content”).
                        </P>
                    </FTNT>
                    <P>After reviewing the submitted comments, the Commission does not propose modifying the Rule to permit general audience platforms to rebut the presumption that all users of child-directed content are children. The Commission finds persuasive the concerns raised in the comments about the practicality of allowing operators of such platforms to rebut this presumption. In particular, the Commission believes that the reality of parents and children sharing devices, along with account holders remaining perpetually logged into their accounts, could make it difficult for an operator to distinguish reliably between those users who are children and those who are not.</P>
                    <P>
                        The Commission recognizes that allowing platforms to rebut the presumption would permit additional forms of monetization and, in some instances, provide additional functionality and convenience for adults interacting with child-directed content. Such benefits, however, simply do not outweigh the important goal of protecting children's privacy. Moreover, as set forth in the Commission's 2019 Rule Review Initiation, the reason for considering whether to allow platforms to rebut the audience presumption was to create an incentive for them to “identify and police child-directed content uploaded by others.” 
                        <SU>73</SU>
                        <FTREF/>
                         Many commenters supporting the addition of this rebuttal expressed strong opposition to such a duty, thereby undercutting the rationale for modifying the Rule.
                    </P>
                    <FTNT>
                        <P>
                            <SU>73</SU>
                             84 FR 35842 at 35846.
                        </P>
                    </FTNT>
                    <P>
                        Finally, through its recognition of the “mixed audience” category of websites and online services, the Commission essentially allows operators to rebut the presumption as to the users of a subset of child-directed sites and services that do not target children as their primary audience. For example, where third-party content on a platform is child-directed under the Rule's multi-factor test but the platform does not target children as its primary audience, the operator can request age information and provide COPPA protections only to those users who are under 13. The Commission believes the mixed audience category affords operators an appropriate degree of flexibility.
                        <SU>74</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>74</SU>
                             While it is possible that the sharing of devices between parents and children can lead to complexities in determining the “mixed audience” nature of a website or online service, the Commission believes on balance that there is value in continuing to allow for a mixed audience designation.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">IV. Proposed Modifications to the Rule</HD>
                    <P>
                        As discussed in Part I, comments reflect overall support for COPPA and a recognition that it is an important and helpful tool for protecting children's online privacy. Additionally, many comments indicate support for the 2013 Amendments.
                        <SU>75</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>75</SU>
                             
                            <E T="03">See, e.g.,</E>
                             SuperAwesome; PRIVO; ESA; Electronic Privacy Information Center (“EPIC”); and Joint Consumer Groups. 
                            <E T="03">But see, e.g.,</E>
                             Skyship Entertainment; J. Johnston (J House Vlogs); H. and S. Jho (Sockeye Media LLC); and ICLE. These commenters, many of whom are content creators on YouTube, opposed the Rule changes and/or the FTC's 2019 enforcement action against Google LLC and its subsidiary YouTube, LLC (“YouTube Case”), 
                            <E T="03">Federal Trade Commission &amp; People of the State of New York</E>
                             v. 
                            <E T="03">Google LLC &amp; YouTube, LLC,</E>
                             Case No. 1:19-cv-2642 (D.D.C. 2019), 
                            <E T="03">available at https://www.ftc.gov/legal-library/browse/cases-proceedings/172-3083-google-llc-youtube-llc.</E>
                             These commenters asserted that the 2013 Amendments and the YouTube Case have affected the availability of children's content on YouTube due to creators' inability to monetize through personalized advertisements. Additional commenters criticized the 2013 Amendments for other reasons, such as 
                            <PRTPAGE/>
                            purported negative consequences to industry or beliefs that the 2013 Amendments strayed from the purpose of the COPPA statute. 
                            <E T="03">See, e.g.,</E>
                             Committee for Justice; TechFreedom; and Competitive Enterprise Institute.
                        </P>
                    </FTNT>
                    <PRTPAGE P="2040"/>
                    <P>Despite this overall support, the Commission believes it is appropriate to modify a number of the Rule's provisions in light of the record developed through the 2019 Rule Review Initiation—including the COPPA Workshop and the large number of public comments received—as well as the FTC's two decades of experience enforcing the Rule. The Commission intends these modifications to update certain aspects of the Rule, taking into account technological and other relevant developments, and to provide additional clarity to operators on the Rule's existing requirements. Specifically, the Commission proposes modifying most provisions of the Rule, namely the following areas: Definitions; Notice; Parental Consent; Parental Right to Review; Confidentiality, Security, and Integrity of Children's Personal Information; Data Retention and Deletion; and Safe Harbor Programs. In addition, the Commission proposes minor modifications to the sections on Scope of Regulations and Voluntary Commission Approval Processes to address technical corrections.</P>
                    <P>Additionally, the Commission proposes some revisions to the Rule to address spelling, grammatical, and punctuation issues. For example, as noted above, the Commission proposes to modify § 312.1 regarding the scope of regulations, specifically to change the location of commas. Similarly, the Commission proposes amending the Rule to change the term “Web site” to “website” throughout the Rule, including in various definitions that use this term. This construction aligns with the COPPA statute's use of the term, as well as how that term is currently used in today's marketplace. This NPRM incorporates this proposed change in all instances in which the term “Web site” is used. The Commission does not intend for these proposed modifications to alter existing obligations or create new obligations under the Rule.</P>
                    <HD SOURCE="HD2">A. Definitions (16 CFR 312.2)</HD>
                    <P>The Commission proposes to modify a number of the Rule's definitions in order to update the Rule's coverage and functionality and, in certain areas, to provide greater clarity regarding the Rule's intended application. The Commission proposes modifications to the definitions of “online contact information” and “personal information.” The Commission also proposes modifications to the definition of “website or online service directed to children,” including by adding a stand-alone definition for “mixed audience website or online service.” Additionally, the Commission proposes adding definitions for “school” and “school-authorized education purpose.” These two new definitions relate to the Rule's proposed new parental consent exception—a codification of longstanding Commission guidance by which operators rely on school authorization to collect personal information in limited circumstances rather than on parental consent. Finally, the Commission proposes modifications to the second paragraph of the definition of “support for the internal operations of the website or online service.”</P>
                    <HD SOURCE="HD3">1. Online Contact Information</HD>
                    <P>Section 312.2 of the Rule defines “online contact information” as “an email address or any other substantially similar identifier that permits direct contact with a person online, including but not limited to, an instant messaging user identifier, a voice over internet protocol (VOIP) identifier, or a video chat user identifier.” Online contact information is considered “personal information” under the Rule. Under certain parental consent exceptions, the Rule permits operators to collect online contact information from a child for certain purposes, such as initiating the process of obtaining verifiable parental consent, without first obtaining verifiable parental consent.</P>
                    <P>To improve the Rule's functionality, the Commission proposes amending this definition by adding “an identifier such as a mobile telephone number provided the operator uses it only to send a text message” to the non-exhaustive list of identifiers that constitute “online contact information.” As discussed later in this Part, this modification would allow operators to collect and use a parent's or child's mobile phone number in certain circumstances, including in connection with obtaining parental consent through a text message.</P>
                    <P>
                        Although the Commission did not raise the issue of adding mobile telephone numbers to the online contact information definition in its 2019 Rule Review Initiation, some commenters supported such a modification in discussing the Rule's parental consent requirement.
                        <SU>76</SU>
                        <FTREF/>
                         One commenter noted that parents increasingly rely on telephone and cloud-based text messaging services,
                        <SU>77</SU>
                        <FTREF/>
                         and another similarly noted that permitting parents to utilize text messages to provide consent would be more in sync with current technology and parental expectations.
                        <SU>78</SU>
                        <FTREF/>
                         Commenters also stated that mobile communication mechanisms are more likely to result in operators reaching parents for the desired purpose of providing notice and obtaining consent, and that sending a text message may be one of the most direct and easily verifiable methods of contacting a parent.
                        <SU>79</SU>
                        <FTREF/>
                         Further, one commenter posited that the chance of a child submitting his or her own mobile number in order to circumvent a valid consent mechanism is no greater than, for instance, a child submitting his or her own email address.
                        <SU>80</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>76</SU>
                             
                            <E T="03">See, e.g.,</E>
                             kidSAFE, at 3-4. More generally, several other commenters recommended modifying the Rule to allow the use of text messaging in connection with obtaining parental consent. 
                            <E T="03">See</E>
                             The Toy Association, at 4; ESA, at 24-26; ANA, at 12; Entertainment Software Rating Board (“ESRB”), at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>77</SU>
                             kidSAFE, at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>78</SU>
                             ESA, at 24-25.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>79</SU>
                             kidSAFE, at 3-4; ANA, at 12.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>80</SU>
                             kidSAFE, at 4.
                        </P>
                    </FTNT>
                    <P>The Commission agrees that permitting parents to provide consent via text message would offer them significant convenience and utility. The Commission also recognizes that consumers are likely accustomed to using mobile telephone numbers for account creation or log-in purposes. For these reasons, the Commission is persuaded that operators should be able to collect parents' mobile telephone numbers as a method to obtain consent from the parent. Therefore, the Commission proposes adding mobile telephone numbers to the definition of “online contact information.”</P>
                    <P>
                        Modifying the definition in this way, however, will also enable operators to collect and use a child's mobile telephone number to communicate with the child, including—under various parental consent exceptions—prior to the operator obtaining parental consent.
                        <SU>81</SU>
                        <FTREF/>
                         The Commission does not seek to allow operators to use children's mobile telephone numbers to call them prior to the operator obtaining parental consent. Therefore, the Commission proposes including the qualifier “provided the operator uses it only to send a text message” to ensure that operators cannot call the child using the mobile telephone number, unless and until the operator seeks and obtains a parent's verifiable parental consent to do so.
                        <SU>82</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>81</SU>
                             16 CFR 312.5(c)(1), (3), (4), (5), and (6).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>82</SU>
                             Because various parental consent exceptions allow operators to collect a child's “online contact information” without first obtaining verifiable parental consent, the Commission proposes limiting operators from using such information to call a child. However, this proposal does not prevent an 
                            <PRTPAGE/>
                            operator from making telephone calls after the operator has obtained consent. Indeed, the definition of “personal information” includes a telephone number under COPPA and the COPPA Rule, and neither the statute nor the Rule includes a prohibition on using that information to make telephone calls.
                        </P>
                    </FTNT>
                    <PRTPAGE P="2041"/>
                    <P>
                        This proposed modification is a departure from the position the Commission previously took when it declined to include mobile telephone numbers within the definition of “online contact information.” In discussing the 2013 Amendments, the Commission stated that the COPPA statute did not contemplate adding mobile telephone numbers as a form of online contact information, and therefore it determined not to include mobile telephone numbers within the definition.
                        <SU>83</SU>
                        <FTREF/>
                         However, the Commission also stated at that time that the list of identifiers constituting online contact information was non-exhaustive and would encompass other substantially similar identifiers that permit direct contact with a person online.
                        <SU>84</SU>
                        <FTREF/>
                         As part of the 2013 Amendments, the Commission revised the definition to include examples of such identifiers, and the Commission now believes that adding mobile telephone numbers to this list is appropriate.
                    </P>
                    <FTNT>
                        <P>
                            <SU>83</SU>
                             
                            <E T="03">See</E>
                             78 FR 3972 at 3975. At that time, the Commission also questioned whether adding mobile telephone numbers would result in greater convenience for parents in providing consent, noting that children might have difficulty distinguishing between a parent's mobile number and a landline number. 
                            <E T="03">See</E>
                             78 FR 3972 at 3975. This concern seems less significant today given that many more consumers now rely exclusively on their mobile phone.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>84</SU>
                             78 FR 3972 at 3975, citing 76 FR 59804 at 59810.
                        </P>
                    </FTNT>
                    <P>
                        Specifically, consumers today widely use over-the-top messaging platforms, which are platforms that utilize the internet instead of a carrier's mobile network to exchange messages. These platforms include Wi-Fi messaging applications, voice over internet protocol applications that have messaging features, and other messaging applications. Because a consumer's mobile telephone number is often used as the unique identifier through which a consumer can exchange messages through these over-the- top platforms, mobile telephone numbers permit direct contact with a person online, thereby meeting the statutory requirements for this definition.
                        <SU>85</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>85</SU>
                             15 U.S.C. 6501(12) (providing that “the term `online contact information' means an email address or 
                            <E T="03">another substantially similar identifier that permits direct contact with a person online”</E>
                             (emphasis added)).
                        </P>
                    </FTNT>
                    <P>When the Commission enacted the 2013 Amendments, the use of over-the-top messaging platforms was more nascent and growing in adoption. Today, the prevalent and widespread adoption of such messaging platforms allows consumers to use these platforms as their primary form of text messaging. Therefore, the Commission finds it appropriate to propose amending the definition of “online contact information” to include “an identifier such as a mobile telephone number provided the operator uses it only to send a text message.” The Commission welcomes comment on this proposed modification. In particular, the Commission is interested in understanding whether allowing operators to contact parents through a text message to obtain verifiable parental consent presents security risks to the recipient of the text message, especially if the parent would need to click on a link provided in the text message.</P>
                    <HD SOURCE="HD3">2. Personal Information</HD>
                    <P>
                        The COPPA statute defines “personal information” as individually identifiable information about an individual collected online, including, for example, a first and last name, an email address, or a Social Security number.
                        <SU>86</SU>
                        <FTREF/>
                         The COPPA statute also includes within the definition “any other identifier that the Commission determines permits the physical or online contacting of a specific individual.” 
                        <SU>87</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>86</SU>
                             
                            <E T="03">See</E>
                             15 U.S.C. 6501(8).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>87</SU>
                             15 U.S.C. 6501(8)(F). As part of the 2013 Amendments, the Commission used this statutory authority to add several new identifiers to the COPPA Rule's definition of “personal information.” 
                            <E T="03">See</E>
                             78 FR 3972 at 3978-83. For example, the Commission added a photograph, video, or audio file containing a child's image or voice, and it also included geolocation information sufficient to identify street name and name of a city or town. Additionally, the Commission added persistent identifiers that can be used to recognize a user over time and across different websites or online services, which the Rule had previously only covered when associated with individually identifiable information. 
                            <E T="03">See</E>
                             64 FR 59888 at 59912.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">a. Biometric Data</HD>
                    <P>
                        The Commission proposes using its statutory authority to expand the Rule's coverage by modifying the Rule's definition of “personal information” to include “[a] biometric identifier that can be used for the automated or semi-automated recognition of an individual, including fingerprints or handprints; retina and iris patterns; genetic data, including a DNA sequence; or data derived from voice data, gait data, or facial data.” 
                        <SU>88</SU>
                        <FTREF/>
                         The Commission believes this proposed modification is necessary to ensure that the Rule is keeping pace with technological developments that facilitate increasingly sophisticated means of identification.
                    </P>
                    <FTNT>
                        <P>
                            <SU>88</SU>
                             Given that the Rule's definition of “personal information” currently includes “a photograph, video, or audio file where such file contains a child's image or voice,” the Commission believes facial features, voice, and gait are already covered under the Rule. 16 CFR 312.2, definition of “personal information,” paragraph 8. However, in light of the inherently personal and sensitive nature of data derived from voice data, gait data, and facial data, the Commission proposes to cover this data within the proposed list of biometric identifiers.
                        </P>
                    </FTNT>
                    <P>
                        The majority of comments addressing the question of whether to expand the Rule's definition of “personal information” supported the addition of biometric data.
                        <SU>89</SU>
                        <FTREF/>
                         These commenters asserted that different types of biometric data can be used to contact specific individuals. For example, a coalition of consumer groups recommended adding biometric data, including genetic data, fingerprints, and retinal patterns, to the Rule's enumerated list of “personal information.” 
                        <SU>90</SU>
                        <FTREF/>
                         These commenters cited consumer products' current use of biometrics to identify and authenticate users through such mechanisms as fingerprints and face scans.
                        <SU>91</SU>
                        <FTREF/>
                         They also noted that while some types of personal information may be altered to protect privacy, biometric data collected today may be used to identify and contact specific children for the rest of their lives.
                        <SU>92</SU>
                        <FTREF/>
                         Several other commenters also argued that the permanent and unalterable nature of biometric data makes it particularly sensitive.
                        <SU>93</SU>
                        <FTREF/>
                         Additional commenters noted that many states have expanded the definition of personally identifiable information to include biometric data as have other federal laws and regulations, such as the Department of Education's Family Educational Rights and Privacy Act (“FERPA”) Regulations, 34 CFR 99.3.
                        <SU>94</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>89</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Attorney General of Arizona, at 2; Joint Attorneys General, at 7; Consumer Reports, at 14; SuperAwesome, at 12; CARU, at 3-5; ESRB, at 5; and kidSAFE, at 6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>90</SU>
                             Joint Consumer Groups, at 52-53.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>91</SU>
                             
                            <E T="03">Id.</E>
                             at 53 (citing Heather Kelly, 
                            <E T="03">Fingerprints and Face Scans Are the Future of Smartphones. These Holdouts Refuse to Use Them,</E>
                             Wash. Post (Nov. 15, 2019)).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>92</SU>
                             Joint Consumer Groups, at 53.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>93</SU>
                             CARU, at 4; H. Adams, at 3; Joint Attorneys General, at 7, 11-12.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>94</SU>
                             Future of Privacy Forum (“FPF”), at 4-5; D. Derigiotis Burns Wilcox, at 1-2.
                        </P>
                    </FTNT>
                    <P>
                        A small number of commenters urged the Commission to proceed cautiously with respect to adding biometric data to the Rule's personal information definition. These commenters suggested that such an expansion could stifle innovation 
                        <SU>95</SU>
                        <FTREF/>
                         or questioned whether biometric data allows the physical or online contacting of a specific individual.
                        <SU>96</SU>
                        <FTREF/>
                         Some commenters also 
                        <PRTPAGE P="2042"/>
                        recommended that, if the Commission does define biometric data as personal information, it should consider appropriate exceptions, for example, where the data enhances the security of a child-directed service 
                        <SU>97</SU>
                        <FTREF/>
                         or the operator promptly deletes the data.
                        <SU>98</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>95</SU>
                             The App Association (“ACT”), at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>96</SU>
                             CCIA, at 4; The Toy Association, at 3, 17.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>97</SU>
                             The Toy Association, at 3, 17.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>98</SU>
                             kidSAFE, at 6.
                        </P>
                    </FTNT>
                    <P>
                        The Commission believes that, as with a photograph, video, or audio file containing a child's image or voice, biometric data is inherently personal in nature. Indeed, the Commission agrees with the many commenters 
                        <SU>99</SU>
                        <FTREF/>
                         who argued that the personal, permanent, and unique nature of biometric data makes it sensitive, and the Commission believes that the privacy interest in protecting such data is a strong one.
                    </P>
                    <FTNT>
                        <P>
                            <SU>99</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Joint Consumer Groups, at 53; CARU, at 3-5; H. Adams, at 3; Joint Attorneys General, at 11-12.
                        </P>
                    </FTNT>
                    <P>And, as with some facial and voice recognition technologies, the Commission believes that biometric recognition systems are sufficiently sophisticated to permit the use of identifiers such as fingerprints and handprints; retina and iris patterns; genetic data, including a DNA sequence; and data derived from voice data, gait data, or facial data to identify and contact a specific individual either physically or online.</P>
                    <P>The Commission notes that the specific biometric identifiers that it proposes adding to the Rule's personal information definition are examples and not an exhaustive list. The Commission welcomes further comment on this proposed modification, including whether it should consider additional biometric identifier examples and whether there are appropriate exceptions to any of the Rule's requirements that it should consider applying to biometric data, such as exceptions for biometric data that has been promptly deleted.</P>
                    <HD SOURCE="HD3">b. Inferred and Other Data</HD>
                    <P>
                        In addition to biometric data, the Commission also asked for comment on whether it should expand the Rule's definition of “personal information” to include data that is inferred about, but not directly collected from, children, or other data that serves as a proxy for “personal information.” Several commenters recommended such an expansion.
                        <SU>100</SU>
                        <FTREF/>
                         For example, one commenter stated that inferred data, including predictive behavior, is often incredibly sensitive and that even when it is supplied in the aggregate, can be easily re-identified.
                        <SU>101</SU>
                        <FTREF/>
                         The commenter also noted that certain State laws include inferred data in their definitions of personally identifiable information.
                        <SU>102</SU>
                        <FTREF/>
                         Another pointed to the ability of analysts to infer personal information that the Rule covers, such as an individual's geolocation, from data that currently falls outside the Rule's scope.
                        <SU>103</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>100</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Joint Consumer Groups, at 53-54 (supporting the inclusion of inferred data); London School of Economics, at 1, 9 (supporting the inclusion of inferred data from profiling and other data analytics); SuperAwesome, at 18 (supporting the inclusion of inferred data, health and activity information derived from fitness trackers, and household viewing data from automated content recognition systems in televisions and video streaming devices); C. Frascella, at 2-3 (supporting the inclusion of personal information collected from children through digital reproduction technology); Parent Coalition for Student Privacy, at 5-8 (supporting, among other things, the inclusion of inferred data and proxy data, such as the language spoken at home and the length of time the child has lived in the United States); UnidosUS (“Unidos”), at 5 (urging the Commission to study the use of “cultural cues” as personal information). 
                            <E T="03">See also, e.g.,</E>
                             National Center on Sexual Exploitation, at 2 (expressing general support for expanding the definition of “personal information” to protect children).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>101</SU>
                             Parent Coalition for Student Privacy, at 5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>102</SU>
                             
                            <E T="03">Id.</E>
                             (citing Colorado's Student Data Transparency and Security Act and California's Consumer Privacy Act).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>103</SU>
                             Joint Consumer Groups, at 54 (“For example, non-geolocation ambient data collected by a mobile device operating system does not constitute an independently enumerated category of personal information under the current iteration of the COPPA Rule. But a savvy analyst could use data collected by a mobile device to infer specific geolocation or other details that clearly 
                            <E T="03">would</E>
                             fall under the COPPA Rule definition of personal information”) (emphasis in original).
                        </P>
                    </FTNT>
                    <P>
                        Commenters opposed to including inferred data stated that such an expansion would not be in accordance with the COPPA statute, which covers data collected “from” a child.
                        <SU>104</SU>
                        <FTREF/>
                         Some commenters opposed to the inclusion of inferred data argued that inferred data does not permit the physical or online contacting of the child.
                        <SU>105</SU>
                        <FTREF/>
                         Some commenters also expressed concern that adding inferred data would create ambiguity and hamper companies' abilities to provide websites and online services to children, would stifle new products and services, and may prohibit the practice of contextual advertising.
                        <SU>106</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>104</SU>
                             
                            <E T="03">See, e.g.,</E>
                             IAB, at 4; NCTA—The internet and Television Association (“NCTA”), at 5-7; U.S. Chamber of Commerce, at 3. 
                            <E T="03">See also</E>
                             CCIA, at 4 (asserting that the COPPA Rule already covers the processing of personal information to derive inferences about a specific user and that the use of aggregated data that does not relate to a specific user is outside the scope of the COPPA statute's definition of “personal information”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>105</SU>
                             
                            <E T="03">See, e.g.,</E>
                             IAB, at 4; The Toy Association, at 16-17.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>106</SU>
                             
                            <E T="03">See</E>
                             CIPL, at 2; U.S. Chamber of Commerce, at 3; IAB, at 4; internet Association, at 5-6; PRIVO, at 8.
                        </P>
                    </FTNT>
                    <P>
                        The Commission has decided not to propose including inferred data or data that may serve as a proxy for “personal information” within the definition. As several commenters correctly note, the COPPA statute expressly pertains to the collection of personal information 
                        <E T="03">from</E>
                         a child.
                        <SU>107</SU>
                        <FTREF/>
                         Therefore, to the extent data is collected from a source other than the child, such information is outside the scope of the COPPA statute and such an expansion would exceed the Commission's authority. Inferred data or data that may serve as a proxy for “personal information” could fall within COPPA's scope, however, if it is combined with additional data that would meet the Rule's current definition of “personal information.” In such a case, the existing “catch-all” provision of that definition would apply.
                        <SU>108</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>107</SU>
                             15 U.S.C. 6502(a)(1).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>108</SU>
                             
                            <E T="03">See</E>
                             16 CFR 312.2, definition of “personal information,” paragraph 10 (defining “personal information” to include “[i]nformation concerning the child or the parents of that child that the operator collects online from the child and combines with an identifier described in this definition”).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Persistent Identifiers</HD>
                    <P>
                        In 2013, the Commission used its authority under 15 U.S.C. 6501(8)(F) to modify the Rule's definition of “personal information” to include persistent identifiers that can be used to recognize a user over time and across different websites or online services. Prior to that change, the Rule covered persistent identifiers only when they were combined with certain types of identifying information.
                        <SU>109</SU>
                        <FTREF/>
                         As part of the 2019 Rule Review Initiation, the Commission asked for comment on whether this modification has resulted in stronger privacy protections for children. The Commission also asked whether the modification has had any negative consequences.
                    </P>
                    <FTNT>
                        <P>
                            <SU>109</SU>
                             
                            <E T="03">See</E>
                             64 FR 59888 at 59912.
                        </P>
                    </FTNT>
                    <P>
                        A number of commenters, citing a variety of reasons, argued that the amendment to include “stand-alone” persistent identifiers as personal information was incorrect or had caused harm. Several commenters claimed that persistent identifiers alone do not allow for the physical or online contacting of a child, and thus should not be included unless linked to other forms of personal information.
                        <SU>110</SU>
                        <FTREF/>
                         Commenters also argued 
                        <PRTPAGE P="2043"/>
                        that the persistent identifier modification harmed both operators and children. Specifically, some commenters pointed to operators' lost revenue from targeted advertising, which requires collection of persistent identifiers, and the resulting reduction of available child-appropriate content online due to operators' inability to monetize such content.
                        <SU>111</SU>
                        <FTREF/>
                         One commenter stated that while the 2013 modification “served the widely held goal of excluding children from interest-based advertising,” it created uncertainty for operators' use of data for internal operations.
                        <SU>112</SU>
                        <FTREF/>
                         The commenter suggested that the Commission consider exempting persistent identifiers used for internal operations from the Rule's deletion requirements.
                        <SU>113</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>110</SU>
                             
                            <E T="03">See, e.g.,</E>
                             TechFreedom, at 8 (“[P]ersistent identifiers on their own can only identify a device, not a `specific person' as the COPPA statute requires”); Competitive Enterprise Institute, at 2 (“[P]ersistent online identifiers do not `permit[] the physical or online contacting of a specific individual' in the sense that Congress contemplated when it enacted COPPA in 1998”); ICLE, at 6 (“Neither IP addresses nor device identifiers alone `permit the physical or online contacting of a specific individual' as required by 15 U.S.C. 6501(8)(F)”); NetChoice, at 3 (“Persistent 
                            <PRTPAGE/>
                            identifiers, like cookies, only identify devices—not a person”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>111</SU>
                             
                            <E T="03">See, e.g.,</E>
                             ICLE, at 7-12. These commenters also included content creators on YouTube. 
                            <E T="03">See, e.g.,</E>
                             Skyship Entertainment; J. Johnston (J House Vlogs); H. and S. Jho (Sockeye Media LLC). 
                            <E T="03">See also</E>
                             CARU, at 1 (noting that “[t]he addition of `persistent identifier' to the definition of `Personal Information' has resulted in improved privacy protections for children but has had negative consequences for industry, specifically the lack of robust and creative child-directed content”); IAB, at 4 (noting that this modification may have had the unintended effect of reducing the availability of children's online content).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>112</SU>
                             CCIA, at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>113</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <P>
                        In contrast, other commenters expressed strong support for the 2013 persistent identifier modification. For example, while acknowledging that it took time for the digital advertising industry to adapt to the new definition, one commenter described the 2013 modification as “wholly positive.” 
                        <SU>114</SU>
                        <FTREF/>
                         The commenter also noted that the change recognized that unique technical identifiers might be just as personal as traditional identifiers such as name or address when used to contact, track, or profile users.
                        <SU>115</SU>
                        <FTREF/>
                         The commenter stated that this change “laid the groundwork for many countries adopting this expanded definition of personal information in their updated privacy laws.” 
                        <SU>116</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>114</SU>
                             SuperAwesome, at 18.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>115</SU>
                             
                            <E T="03">Id. See also</E>
                             Princeton University Center for Information Technology Policy (“Princeton University”), at 4 (“In the most recent COPPA Rule revision, the FTC recognized that `persistent identifiers' are a form of `personal information,' because they enable singling out a specific user through their device for contact. This makes sense; we see no basis in computer science for treating persistent identifiers any differently from other means of directing communications, such as telephone numbers or email addresses. While the technical details differ, the use of the information is the same”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>116</SU>
                             SuperAwesome, at 18. This commenter also recommended that the Commission expand the “personal information” definition's non-exhaustive list of persistent identifiers to include “device ID, [a]dvertising ID or similar” IDs and a “user agent or other device information which, when combined, can be used to create a unique fingerprint of the device.” SuperAwesome, at 17. Because the Rule provides examples of persistent identifiers rather than an exhaustive list, the Commission does not find it necessary to include these elements within the definition.
                        </P>
                    </FTNT>
                    <P>
                        After reviewing the comments relevant to this issue, the Commission has decided to retain the 2013 modification including stand-alone persistent identifiers as “personal information.” The Commission is not persuaded by the argument that persistent identifiers must be associated with other individually identifiable information to permit the physical or online contacting of a specific individual. The Commission specifically addressed, and rejected, this argument during its discussion of the 2013 Amendments. There, the Commission rejected the claim that persistent identifiers only permit contact with a device. Instead, the Commission pointed to the reality that at any given moment a specific individual is using that device, noting that this reality underlies the very premise behind behavioral advertising.
                        <SU>117</SU>
                        <FTREF/>
                         The Commission also reasoned that while multiple people in a single home often use the same phone number, home address, and email address, Congress nevertheless defined these identifiers as “individually identifiable information” in the COPPA statute.
                        <SU>118</SU>
                        <FTREF/>
                         The adoption of similar approaches in other legal regimes enacted since the 2013 Amendments further supports the Commission's position.
                        <SU>119</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>117</SU>
                             78 FR 3972 at 3980.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>118</SU>
                             
                            <E T="03">Id.</E>
                             (citing 15 U.S.C. 6501(8)).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>119</SU>
                             
                            <E T="03">See</E>
                             The European Union's General Data Protection Regulation (“GDPR”), which defines “personal data” as “any information relating to an identified or identifiable natural person . . . [A]n identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as . . . an online identifier.” GDPR, Article 4, 
                            <E T="03">available at https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A02016R0679-20160504&amp;qid=1532348683434.</E>
                             Recital 30 of the GDPR notes that “natural persons may be associated with online identifiers provided by their devices, applications, tools and protocols, such as [I]nternet [P]rotocol addresses, cookie identifiers or other identifiers such as radio frequency identification tags.” Recital 30, 
                            <E T="03">available at https://eur-lex.europa.eu/eli/reg/2016/679.</E>
                             The California Privacy Rights Act similarly defines “personal information” as “information that identifies, relates to, describes, is reasonably capable of being associated with, or could reasonably be linked, directly or indirectly, with a particular consumer or household,” and includes identifiers such as online identifiers. Section 3, Title 1.81.5 of the CCPA, added to Part 4 of Division 3 of the California Civil Code § 1798.140(v). This approach is also consistent with the FTC's own precedent. 
                            <E T="03">See Protecting Consumer Privacy in an Era of Rapid Change,</E>
                             Federal Trade Commission (March 2012), available at 
                            <E T="03">https://www.ftc.gov/sites/default/files/documents/reports/federal-trade-commission-report-protecting-consumer-privacy-era-rapid-change-recommendations/120326bprivacybreport.pdf; FTC Staff Report: Self-Regulatory Principles For Online Behavioral Advertising</E>
                             (February 2009), available at 
                            <E T="03">https://www.ftc.gov/sites/default/files/documents/reports/federal-trade-commission-staff-report-self-regulatory-principles-online-behavioral-advertising/p085400behavadreport.pdf.</E>
                        </P>
                    </FTNT>
                    <P>
                        Nor does the Commission find compelling the argument that the 2013 persistent identifier modification has caused harm by hindering the ability of operators to monetize online content through targeted advertising. One of the stated goals of including persistent identifiers within the definition of “personal information” was to prevent the collection of personal information from children for behavioral advertising without parental consent.
                        <SU>120</SU>
                        <FTREF/>
                         After reviewing the comments, the Commission has determined that the privacy benefits of such an approach outweigh the potential harm, including the purported harm created by requiring operators to provide notice and seek verifiable parental consent in order to contact children through targeted advertising.
                        <SU>121</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>120</SU>
                             78 FR 3972 at 3979-3981.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>121</SU>
                             The Commission received comments from content creators who indicated that the 2013 Amendments resulted in the loss of the ability to monetize content through targeted advertising. 
                            <E T="03">See</E>
                             Skyship Entertainment; J. Johnston (J House Vlogs); H. and S. Jho (Sockeye Media LLC). As discussed in Part IV.A.2.c., the 2013 Amendments permit monetization through other avenues, such as contextual advertising, or through providing notice and seeking parental consent for the use of personal information for targeted advertising.
                        </P>
                    </FTNT>
                    <P>Moreover, it bears noting, as the Commission did in 2013, that the expansion of the personal information definition was coupled with a newly created exception that allows operators to collect persistent identifiers from children to provide support for the internal operations of the website or online service without providing notice or obtaining parental consent. One of these purposes is serving contextual advertising, which provides operators another avenue for monetizing online content. The Commission continues to believe that it struck the proper balance in 2013 when it expanded the personal information definition while also creating a new exception to the Rule's requirements.</P>
                    <HD SOURCE="HD3">3. School and School-Authorized Education Purpose</HD>
                    <P>
                        As discussed in Part IV.C.3.a., the Commission proposes codifying current guidance on ed tech 
                        <SU>122</SU>
                        <FTREF/>
                         by adding an 
                        <PRTPAGE P="2044"/>
                        exception for parental consent in certain, limited situations in which a school authorizes an operator to collect personal information from a child. The Commission also proposes adding definitions for “school” and “school-authorized education purpose,” terms that are incorporated into the functioning of the proposed exception and necessary to cabin its scope. Part IV.C.3.a. provides further discussion about these definitions.
                    </P>
                    <FTNT>
                        <P>
                            <SU>122</SU>
                             
                            <E T="03">Policy Statement of the Federal Trade Commission on Education Technology and the Children's Online Privacy Protection Act,</E>
                             Federal Trade Commission (May 19, 2022), available at 
                            <PRTPAGE/>
                            <E T="03">https://www.ftc.gov/legal-library/browse/policy-statement-federal-trade-commission-education-technology-childrens-online-privacy-protection;ComplyingwithCOPPA:FrequentlyAskedQuestions</E>
                             (“
                            <E T="03">COPPA FAQs”</E>
                            ), 
                            <E T="03">FAQ Section N,</E>
                             available at 
                            <E T="03">https://www.ftc.gov/business-guidance/resources/complying-coppa-frequently-asked-questions.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">4. Support for the Internal Operations of the Website or Online Service</HD>
                    <P>
                        As discussed in Part IV.A.2.c., the 2013 Amendments expanded the definition of “personal information” to include stand-alone persistent identifiers “that can be used to recognize a user over time and across different websites or online services.” 
                        <SU>123</SU>
                        <FTREF/>
                         The 2013 Amendments balanced this expansion by creating an exception to the Rule's notice and consent requirements for operators that collect a persistent identifier for the “sole purpose of providing support for the internal operations of the website or online service.” 
                        <SU>124</SU>
                        <FTREF/>
                         The Rule defines “support for the internal operations of the website or online service” to include a number of specified activities and provides that the information collected to perform those activities cannot be used or disclosed “to contact a specific individual, including through behavioral advertising, to amass a profile on a specific individual, or for any other purpose.” 
                        <SU>125</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>123</SU>
                             16 CFR 312.2, definition of “personal information,” paragraph 7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>124</SU>
                             16 CFR 312.5(c)(7).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>125</SU>
                             16 CFR 312.2, definition of “support for the internal operations of the website or online service.” The definition includes activities such as those necessary to maintain or analyze the functioning of a site or service; personalize content; serve contextual advertising or cap the frequency of advertising; and protect the security or integrity of the user, site, or service.
                        </P>
                    </FTNT>
                    <P>
                        A variety of commenters recommended modifying the definition of “support for the internal operations of the website or online service.” Multiple consumer and privacy advocates, academics, and one advertising platform called for the Commission to define “support for the internal operations” narrowly and thereby restrict the exception's use.
                        <SU>126</SU>
                        <FTREF/>
                         For example, a coalition of consumer groups argued that the current definition is overly broad, too vague, and allows operators to avoid or minimize their COPPA obligations.
                        <SU>127</SU>
                        <FTREF/>
                         These commenters cited the lack of clarity between data collection for permissible content personalization versus collection for impermissible behavioral advertising.
                        <SU>128</SU>
                        <FTREF/>
                         To prevent operators from applying the exception too broadly, the coalition recommended a number of modifications to the definition, including limiting “personalization” to user-driven actions and to exclude methods designed to maximize user engagement.
                        <SU>129</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>126</SU>
                             Joint Consumer Groups, at 48-52; S. Egelman, at 5-6 (stating that, from a technical standpoint, persistent identifiers are not needed to carry out the activities listed in the support for the internal operations of the website or online service definition); Princeton University, at 5-7 (expressing reservations about the scope of the internal operations exception); SuperAwesome, at 5-7 and 19-20 (noting that the industry-standard persistent identifiers are not needed for most internal operations and that the support for the internal operations exception should be significantly narrowed, if not eliminated).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>127</SU>
                             Joint Consumer Groups, at 48-52.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>128</SU>
                             
                            <E T="03">Id.</E>
                             at 48-49.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>129</SU>
                             
                            <E T="03">Id.</E>
                             at 50-52.
                        </P>
                    </FTNT>
                    <P>
                        Several commenters specifically recommended that the Commission exclude the practice of “ad attribution”—which allows the advertiser to associate a consumer's action with a particular ad—from the support for the internal operations definition.
                        <SU>130</SU>
                        <FTREF/>
                         A group of State Attorneys General argued that ad attribution is unrelated to the activities enumerated in the definition and that the practice “necessarily involves `recogniz[ing] a user over time and across different [websites] or online services.' ” 
                        <SU>131</SU>
                        <FTREF/>
                         Another commenter argued that companies should not be able to track children across online services to determine which ads are effective because the harm to privacy outweighs the practice's negligible benefit.
                        <SU>132</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>130</SU>
                             Joint Attorneys General, at 8; Joint Consumer Groups, at 51-52; Consumer Reports, at 14-15.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>131</SU>
                             Joint Attorneys General, at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>132</SU>
                             Consumer Reports, at 14-15 (noting that it is unclear whether companies are following COPPA's existing restraints on operators' use of the support for the internal operations exception).
                        </P>
                    </FTNT>
                    <P>
                        In contrast, many industry commenters recommended that the Commission expand the list of activities that fall under the support for the internal operations definition. With respect to ad attribution, these commenters generally cited the practical need of websites and online services that monetize through advertising to evaluate the effectiveness of ad campaigns or to measure conversion in order to calculate compensation for advertising partners.
                        <SU>133</SU>
                        <FTREF/>
                         Some commenters characterized the practice as common and expected, and they argued that reducing the ability to monetize would result in the development of fewer apps and online experiences for children.
                        <SU>134</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>133</SU>
                             ESA, at 17-18; CARU, at 5; The Toy Association, at 14-15; NCTA, at 10. 
                            <E T="03">See also</E>
                             Committee for Justice, at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>134</SU>
                             
                            <E T="03">See, e.g.,</E>
                             kidSAFE, at 6.
                        </P>
                    </FTNT>
                    <P>
                        Several commenters stated that ad attribution already falls within the definition but supported a Rule modification to make this clear.
                        <SU>135</SU>
                        <FTREF/>
                         One argued that the definition's prohibition on the collection of persistent identifiers for behavioral advertising “serves as a safeguard to assure that [attribution] is appropriately limited.” 
                        <SU>136</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>135</SU>
                             
                            <E T="03">See, e.g.,</E>
                             The Toy Association, at 14-15; NCTA, at 10; ESA, at 18; CARU, at 5. 
                            <E T="03">See also</E>
                             PRIVO, at 8 (noting that “the Commission should make clear whether attribution and remarketing can be claimed to be support for internal operations”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>136</SU>
                             The Toy Association, at 15.
                        </P>
                    </FTNT>
                    <P>
                        Commenters also recommended that a number of other practices should fall within the definition of “support for the internal operations of the website or online service.” These include additional ad measuring techniques,
                        <SU>137</SU>
                        <FTREF/>
                         different types of personalization activities,
                        <SU>138</SU>
                        <FTREF/>
                         product improvement,
                        <SU>139</SU>
                        <FTREF/>
                         and fraud detection.
                        <SU>140</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>137</SU>
                             
                            <E T="03">See, e.g.,</E>
                             ANA, at 11 (recommending including click/conversion tracking, ad modeling, and A/B testing, practices that provide operators with information about the value of their ads, reduce the need for behavioral targeted ads, and allow operators to determine the most “user-friendly” version of a site); Google, at 17 (recommending adding conversion tracking and ad modeling, which allow measuring the relevance and appropriateness of ads); IAB, at 3 (recommending including conversion tracking and advertising modeling because they “are fundamental activities that improve the customer and business experience without creating additional privacy risks to children”); internet Association, at 6-7 (recommending including click/conversion tracking and ad modeling support because they “support child-centered content creation and, in each case, can be undertaken without focusing on a specific child's behavior over time for targeting purposes”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>138</SU>
                             
                            <E T="03">See, e.g.,</E>
                             NCTA, at 9-10 (recommending including user-driven and user-engagement personalization to allow, for example, “activities to tailor users' experiences based on their prior interactions with a site or service (whether derived from predictive analytics, real-time behaviors, or both)”); Viacom, at 3 (requesting the Commission clarify that the definition includes “enhanced personalization techniques based on operator-driven first-party metrics and inferences about user interaction”); CCIA, at 5-6 (recommending including personalization to a user, such as “the recommendation of content based on prior activity on the website or online service”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>139</SU>
                             
                            <E T="03">See, e.g.,</E>
                             ANA, at 11; kidSAFE, at 7; Khan Academy, at 2-3 (noting that it is important to preserve the operator's ability to use data for educational research, product development, and to analyze the functioning of a product).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>140</SU>
                             
                            <E T="03">See, e.g.,</E>
                             SIIA, at 5 (recommending amending (1)(v) of the definition to “[p]rotect the security or 
                            <PRTPAGE/>
                            integrity of the user, [website], or online service of the operator or its service providers”). 
                            <E T="03">See also</E>
                             kidSAFE, at 7 (recommending expanding the definition to include customer or technical support, market research and user surveys, demographic analysis, “or any other function that helps operate internal features and activities offered by a site or app”).
                        </P>
                    </FTNT>
                    <PRTPAGE P="2045"/>
                    <P>
                        By expanding the definition of “personal information” to include stand-alone persistent identifiers, while at the same time creating an exception that allowed operators to collect such identifiers without providing notice and obtaining consent for a set of prescribed internal operations, the Commission struck an important balance between privacy and practicality in the 2013 Amendments.
                        <SU>141</SU>
                        <FTREF/>
                         After careful consideration of the comments that addressed the Rule's support for the internal operations definition, the Commission does not believe that significant modifications to either narrow or expand the definition are necessary.
                    </P>
                    <FTNT>
                        <P>
                            <SU>141</SU>
                             
                            <E T="03">See</E>
                             78 FR 3972 at 3980 (noting that “the Commission recognizes that persistent identifiers are also used for a host of functions that have little or nothing to do with contacting a specific individual, and that these uses are fundamental to the smooth functioning of the internet, the quality of the site or service, and the individual user's experience”).
                        </P>
                    </FTNT>
                    <P>
                        With respect to ad attribution, which generated significant commentary, the Commission believes the practice currently falls within the support for the internal operations definition. When it amended the definition in 2013, the Commission declined to enumerate certain categories of uses, including payment and delivery functions, optimization, and statistical reporting, in the Rule, stating that the definitional language sufficiently covered such functions as activities necessary to “ `maintain or analyze' the functions” of the website or service.
                        <SU>142</SU>
                        <FTREF/>
                         The Commission believes that ad attribution, where a persistent identifier is used to determine whether a particular advertisement led a user to take a particular action, falls within various categories, such as the concept of “payment and delivery functions” and “optimization and statistical reporting.” When used as a tool against click fraud, ad attribution also falls within the category of “protecting against fraud or theft,” an activity that served as a basis for the Commission's creation of the support for the internal operations exception.
                        <SU>143</SU>
                        <FTREF/>
                         That said, as the definition makes clear, the Commission would not treat ad attribution as support for the internal operations of the website or online service if the information collected to perform the activity is used or disclosed “to contact a specific individual, including through behavioral advertising, to amass a profile on a specific individual, or for any other purpose.” 
                        <SU>144</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>142</SU>
                             
                            <E T="03">Id.</E>
                             at 3981.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>143</SU>
                             76 FR 59804 at 59812; 77 FR 46643 at 46647-46648.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>144</SU>
                             16 CFR 312.2, definition of “support for the internal operations of the website or online service,” paragraph 2. This restriction applies to each of the activities enumerated in the definition.
                        </P>
                    </FTNT>
                    <P>
                        The definition's use restriction is an important safeguard to help ensure that operators do not misuse the exception that allows them to collect a persistent identifier in order to provide support for the internal operations without providing notice and obtaining consent.
                        <SU>145</SU>
                        <FTREF/>
                         The Commission appreciates the concerns expressed by some commenters that there is a lack of clarity in how operators implement the support for the internal operations exception and that certain operators may not comply with the use restriction. To increase transparency and to help ensure that operators follow the use restriction, the Commission proposes modifying the online notice requirements in § 312.4(d) to require any operator using the support for the internal operations exception to specifically identify the practices for which the operator has collected a persistent identifier and the means the operator uses to comply with the definition's use restriction.
                        <SU>146</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>145</SU>
                             16 CFR 312.5(c)(7).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>146</SU>
                             
                            <E T="03">See</E>
                             Part IV.B.3. for further discussion of these proposed changes.
                        </P>
                    </FTNT>
                    <P>
                        With respect to the other proposed additions, the Commission does not believe additional enumerated activities are necessary. Other proposed additions—such as personalization, product improvement, and fraud prevention—are already covered.
                        <SU>147</SU>
                        <FTREF/>
                         As the Commission noted in developing the 2013 Amendments, the Commission is cognizant that future technical innovation may result in additional activities that websites or online services find necessary to support their internal operations.
                        <SU>148</SU>
                        <FTREF/>
                         Therefore, the Commission reminds interested parties that they may utilize the process permitted under § 312.12(b) of the Rule, which allows parties to request Commission approval of additional activities to be included within the support for the internal operations definition based on a detailed justification and an analysis of the activities' potential effects on children's online privacy.
                    </P>
                    <FTNT>
                        <P>
                            <SU>147</SU>
                             
                            <E T="03">See, e.g.,</E>
                             77 FR 46643 at 46647 (noting that “[b]y carving out exceptions for support for internal operations, the Commission stated it intended to exempt from COPPA's coverage the collection and use of identifiers for authenticating users, improving site navigation, maintaining user preferences, serving contextual advertisements, protecting against fraud or theft, or otherwise personalizing, improving upon, or securing a [website] or online service”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>148</SU>
                             78 FR 3972 at 3981.
                        </P>
                    </FTNT>
                    <P>
                        Although the Commission does not find it necessary to modify the definition's enumerated activities, it does propose modifications to the definition's use restriction. Currently, the use restriction applies to each of the seven enumerated activities in the definition, and it states that information collected for those enumerated activities may not be used or disclosed to contact a specific individual, including through behavioral advertising, to amass a profile on a specific individual, or for any other purpose.
                        <SU>149</SU>
                        <FTREF/>
                         However, certain of these activities likely necessarily require an operator to contact an individual, for example in order to “[f]ulfill a request of a child as permitted by §§ 312.5(c)(3) and (4).” 
                        <SU>150</SU>
                        <FTREF/>
                         Therefore, the Commission proposes clarifying language to indicate that the information collected for these enumerated activities may be used or disclosed to carry out the activities permitted under the support for the internal operations exception.
                    </P>
                    <FTNT>
                        <P>
                            <SU>149</SU>
                             16 CFR 312.2, definition of “support for the internal operations of the website or online service,” paragraph 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>150</SU>
                             16 CFR 312.2, definition of “support for the internal operations of the website or online service,” paragraph (1)(vii). For example, § 312.5(c)(3) allows an operator to “respond directly on a one-time basis to a specific request from the child.” The Commission notes that the exceptions set forth in §§ 312.5(c)(3) and (4) are limited to responding to a child's specific request. Such a response would not include contacting an individual for another purpose, including through behavioral advertising, amassing a profile on a specific individual, or for any other purpose.
                        </P>
                    </FTNT>
                    <P>In addition, the Commission proposes expanding its non-exhaustive list of use restrictions. The Commission agrees with commenters who argued that the support for the internal operations exception should not be used to allow operators to maximize children's engagement without verifiable parental consent. Therefore, the Commission proposes prohibiting operators that use this exception from using or disclosing personal information in connection with processes, including machine learning processes, that encourage or prompt use of a website or online service. This proposed addition prohibits operators from using or disclosing persistent identifiers to optimize user attention or maximize user engagement with the website or online service, including by sending notifications to prompt the child to engage with the site or service, without verifiable parental consent.</P>
                    <P>
                        The Commission welcomes comment on whether there are other engagement 
                        <PRTPAGE P="2046"/>
                        techniques the Rule should address. The Commission also welcomes comment on whether and how the Rule should differentiate between techniques used solely to promote a child's engagement with the website or online service and those techniques that provide other functions, such as to personalize the child's experience on the website or online service.
                    </P>
                    <HD SOURCE="HD3">5. Website or Online Service Directed to Children</HD>
                    <P>The Commission proposes a number of changes to the definition of “website or online service directed to children.” Overall, the Commission does not intend these proposed changes to alter the definition substantively; rather, the changes will provide additional insight into and clarity regarding how the Commission currently interprets and applies the definition.</P>
                    <HD SOURCE="HD3">a. Multi-Factor Test</HD>
                    <P>
                        The first paragraph of the definition sets forth a list of factors the Commission will consider in determining whether a particular website or online service is child-directed. The Commission received a significant number of comments regarding the Rule's multi-factor test. Several industry commenters encouraged the FTC to continue relying on a multi-factor test to determine whether a site or service is directed to children, balancing both context (
                        <E T="03">e.g.,</E>
                         intent to target children, promoted to children, and empirical evidence of audience) and content (
                        <E T="03">e.g.,</E>
                         subject matter, animation, and child-oriented activities) factors.
                        <SU>151</SU>
                        <FTREF/>
                         These commenters discouraged the FTC from relying on a single factor taken alone, arguing that a multi-factor evaluation allows flexibility and takes into account that some factors may be more or less indicative than others.
                        <SU>152</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>151</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Google, at 15 (“By equally balancing both content and context factors in applying the multi-factor test, operators—including creators, developers and platforms—are less likely to be over- or under-inclusive in making determinations about child-directed services, particularly when decisions are being made at the margins. We are concerned that pulling out a single factor as a litmus test for child-directedness can lead to bad outcomes, resulting in the application of COPPA obligations to general audience content where it doesn't make sense to apply the same protections we'd apply to children's services”); internet Association, at 9 (“The Commission should continue to consider these factors holistically, with no single factor taking precedence over others. Reliance on a comprehensive multi-factor test that includes audience composition as one of many factors balances both content and context inputs and provides the flexibility needed to apply the Rule in the context of new technology and evolving platforms such as interactive media”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>152</SU>
                             
                            <E T="03">See, e.g.,</E>
                             internet Association, at 9; CIPL, at 3-4; Google, at 15-16; Pokémon Company International, Inc. (“Pokémon”), at 1-2; ESA, at 3-8. 
                            <E T="03">See also</E>
                             TechFreedom, at 19 (“The FTC should reinforce its prior decision to apply a `totality of circumstances' test in determining whether content is child-directed”).
                        </P>
                    </FTNT>
                    <P>
                        At the same time, commenters also recommended that the Commission reevaluate the test's existing factors, claiming that some are outdated and no longer seem indicative of child-directed websites or online services. For example, several industry members noted that content styles such as animation are not necessarily determinative of whether a service is child-directed.
                        <SU>153</SU>
                        <FTREF/>
                         In addition, several industry members recommended that the FTC consider giving more weight to particular factors when determining whether a website or online service is directed to children or that it create a sliding scale for existing factors to provide more guidance for operators.
                        <SU>154</SU>
                        <FTREF/>
                         For example, a number of commenters recommended that the Commission weigh more heavily operators' intended audience as opposed to empirical evidence of audience composition.
                        <SU>155</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>153</SU>
                             
                            <E T="03">See, e.g.,</E>
                             ANA, at 8 (noting that animated content is often adult-oriented rather than child-oriented); Pokémon, at 2 (noting that popular adult animated content such as “Family Guy” or “South Park” illustrates that the use of animation is no longer a clear indicator that the use of animated characters is targeted to children); ESA, at 6 (asserting that the use of animated characters should not be given weight in video game and similar media contexts because video games are computer-generated media and therefore inherently utilize animated characters).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>154</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Pokémon, at 2 (suggesting “weighting” the factors); TRUSTe, LLC (“TRUSTe”), at 2 (noting that, while not dispositive, audience composition and target market factors will have a higher likelihood of determining that the service is child-directed); SuperAwesome, at 11 (suggesting the establishment of a roadmap for the Rule's scope to evolve from “content-based” to “user-based” factors, noting that “[t]oday, the best (and highly imperfect) method for determining whether a user is a child is by categori[z]ing the content being accessed, 
                            <E T="03">e.g.</E>
                             is it child-directed or not. In the near future, new technologies will make it possible to identify whether a user is a child on any website or app, and without collecting more personal information to verify age”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>155</SU>
                             
                            <E T="03">See, e.g.,</E>
                             ANA, at 8; J. Johnston (J House Vlogs), at 14; The Toy Association, at 10. 
                            <E T="03">See also generally</E>
                             Screen Actors Guild-American Federation of Television and Radio Artists (“SAG-AFTRA”), at 4-5 (asserting that, when applying the COPPA Rule to content creators who distribute their content on general audience platforms, the Commission should consider the content creators' knowledge and intent).
                        </P>
                    </FTNT>
                    <P>
                        Several FTC-approved COPPA Safe Harbor programs suggested adding new factors to the Rule to help guide operators, including by adding an operator's self-categorization to third parties. One such program, for example, recommended considering marketing materials directed to third-party partners or advertisers, claiming that such materials can provide insights on the operator's target and users.
                        <SU>156</SU>
                        <FTREF/>
                         Another supported consideration of “whether an operator self-categorizes its website or online service as child-directed on third[-]party platforms.” 
                        <SU>157</SU>
                        <FTREF/>
                         A third FTC-approved COPPA Safe Harbor program recommended requiring operators to periodically analyze the demographics of their audience or users and to consider consumer inquiries and complaints.
                        <SU>158</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>156</SU>
                             TRUSTe, at 1-2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>157</SU>
                             kidSAFE, at 7 (also recommending the addition of “video content” to the existing factor of “music or other audio content”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>158</SU>
                             CARU, at 6-7 (suggesting that such factors would be particularly relevant to sites or services that were not originally directed to children, but where the audience has reached a threshold level such that COPPA protections should apply).
                        </P>
                    </FTNT>
                    <P>
                        Some commenters cautioned against relying on an operator's internal rating system or a third party's rating system as a factor.
                        <SU>159</SU>
                        <FTREF/>
                         One such commenter argued that relying on operators' internal rating systems would potentially punish those that engage in good faith, responsible review activities and might violate section 230 of the Communications Decency Act.
                        <SU>160</SU>
                        <FTREF/>
                         The commenter also argued that a third party's ratings do not constitute competent and empirical evidence regarding audience composition or evidence regarding the intended audience, and further argued that relying on such ratings increases an operator's risk of unexpected liability, particularly if the rating system may have been developed for a purpose unrelated to the COPPA Rule's factors.
                        <SU>161</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>159</SU>
                             
                            <E T="03">See, e.g.,</E>
                             ANA, at 8; ESRB, at 7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>160</SU>
                             ANA, at 8 (stating that “Section 230 of the Communications Decency Act explicitly states that no provider of an interactive computer service shall be held liable for `any action voluntarily taken in good faith to restrict access to or availability of material that the provider or user considers to be obscene, lewd, lascivious, filthy, excessively violent, harassing, or otherwise objectionable.' As such, considering content moderation actions taken by companies to oversee content on their platforms as a basis for liability may be impermissible pursuant to the Communications Decency Act”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>161</SU>
                             ANA, at 8-9.
                        </P>
                    </FTNT>
                    <P>
                        The Commission continues to believe that the Rule's multi-factor test, which applies a “totality of the circumstances” standard, is the most practical and effective means for determining whether a website or online service is directed to children. The determination of whether a given site or service is child-directed is necessarily fact-based and requires flexibility as individual factors may be more or less relevant depending on the context. Moreover, a requirement that the Commission, in all cases, weigh more heavily certain factors could unduly hamper the Commission's law enforcement efforts. For example, it is 
                        <PRTPAGE P="2047"/>
                        not hard to envision operators circumventing the Rule by claiming an “intended” adult audience despite the attributes and overall look and feel of the site or service appearing to be directed to children.
                        <SU>162</SU>
                        <FTREF/>
                         Additionally, a rigid approach that prioritizes specific factors is unlikely to be nimble enough to address a site or service that changes its characteristics over time.
                    </P>
                    <FTNT>
                        <P>
                            <SU>162</SU>
                             Indeed, the Commission has previously acknowledged that a website or online service with the attributes, look, and feel of a property targeted to children would be deemed directed to children even if an operator claims that was not the intent. 78 FR 3972 at 3983.
                        </P>
                    </FTNT>
                    <P>
                        The Commission does not propose eliminating any of the existing factors or modifying how it applies the multi-factor test.
                        <SU>163</SU>
                        <FTREF/>
                         However, the Commission proposes modifications to clarify the evidence the Commission will consider regarding audience composition and intended audience.
                    </P>
                    <FTNT>
                        <P>
                            <SU>163</SU>
                             With respect to animation as a factor, the Commission recognizes that a variety of adult content uses animated characters. By the same token, animation can be an important characteristic of child-directed sites and services. Accordingly, as with the other enumerated factors, animation continues to be one of several potentially relevant considerations the Commission will take into account in determining whether a specific site or service is directed to children.
                        </P>
                    </FTNT>
                    <P>Specifically, the Commission proposes adding a non-exhaustive list of examples of evidence the Commission will consider in analyzing audience composition and intended audience. The Commission agrees with those commenters that argued that an operator's marketing materials and own representations about the nature of its site or service are relevant. Such materials and representations can provide insight into the operator's understanding of its intended or actual audience and are thus relevant to the Commission's analysis. Additionally, the Commission believes that other factors can help elucidate the intended or actual audience of a site or service, including user or third-party reviews and the age of users on similar websites or services. Therefore, the Commission proposes adding “marketing or promotional materials or plans, representations to consumers or to third parties, reviews by users or third parties, and the age of users on similar websites or services” as examples of evidence the Commission will consider. Because many of these examples can provide evidence as to both audience composition and intended audience, the Commission also proposes a technical fix to remove the comma between “competent and reliable empirical evidence regarding audience composition” and “evidence regarding the intended audience.”</P>
                    <HD SOURCE="HD3">b. Operators Collecting Personal Information From Other Websites and Online Services Directed to Children</HD>
                    <P>
                        The second paragraph of the definition of “website or online service directed to children” states “[a] website or online service shall be deemed directed to children when it has actual knowledge that it is collecting personal information directly from users of another website or online service directed to children.” 
                        <SU>164</SU>
                        <FTREF/>
                         The Commission added this language in 2013, along with parallel changes to the definition of “operator,” in order “to allocate and clarify the responsibilities under COPPA” of third parties that collect information from users of child-directed sites and services.
                        <SU>165</SU>
                        <FTREF/>
                         The changes clarified that the child-directed content provider is strictly liable when a third party collects personal information through its site or service, while the third party is liable only if it had actual knowledge that the site or service from which it was collecting personal information was child-directed.
                        <SU>166</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>164</SU>
                             16 CFR 312.2, definition of “website or online service directed to children,” paragraph 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>165</SU>
                             78 FR 3972 at 3975. The 2013 Amendments added a proviso to the definition of “operator” discussing the circumstances under which personal information is collected or maintained on behalf of an operator. 
                            <E T="03">See</E>
                             16 CFR 312.2, definition of “operator.”
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>166</SU>
                             The Commission stated that “for purposes of the [COPPA] statute” the third party “has effectively adopted that child-directed content as its own and that portion of its service may appropriately be deemed to be directed to children.” 78 FR 3972 at 3978.
                        </P>
                    </FTNT>
                    <P>Because the second paragraph of this definition specifies that the operator must have actual knowledge that it is collecting personal information “directly” from users of another site or service, the Commission is concerned that entities with actual knowledge that they receive large amounts of children's data from another site or service that is directed to children, without collecting it directly from the users of such site or service, may avoid COPPA's requirements. For example, the online advertising ecosystem involves ad exchanges that receive data from an ad network that has collected information from users of a child-directed site or service. In the same spirit of avoiding a loophole that led the Commission to amend the Rule in 2013, the Commission proposes modifying the current language by deleting the word “directly.” The Commission did not seek comment in the 2019 Rule Review Initiation on this aspect of the Rule's definition of “website or online service directed to children” and therefore welcomes comment on this proposed modification.</P>
                    <HD SOURCE="HD3">c. Mixed Audience</HD>
                    <P>
                        The 2013 Amendments established a distinction between child-directed sites and services that target children as a “primary audience” and those for which children are one of multiple audiences—so called “mixed audience” sites or services. Specifically, the Rule provides that a website or online service that meets the multi-factor test for being child-directed “but that does not target children as its primary audience, shall not be deemed directed to children” so long as the operator first collects age information and then prevents the collection, use, or disclosure of information from users who identify as younger than 13 before providing notice and obtaining verifiable parental consent.
                        <SU>167</SU>
                        <FTREF/>
                         This allows operators of mixed audience sites or services to use an age-screen and apply COPPA protections only to those users who are under 13.
                    </P>
                    <FTNT>
                        <P>
                            <SU>167</SU>
                             16 CFR 312.2, definition of “website or online service directed to children,” paragraph 3.
                        </P>
                    </FTNT>
                    <P>
                        Although there appears to be general support for the mixed audience classification, a number of commenters cited confusion regarding its application and called on the Commission to provide additional clarity on where to draw the line between general audience, primarily child-directed, and mixed audience categories of sites and services.
                        <SU>168</SU>
                        <FTREF/>
                         One commenter noted that the mixed audience definition is confusing and the language “shall not be deemed directed to children” 
                        <PRTPAGE P="2048"/>
                        suggests that such sites or services are not within the definition of child-directed websites or online services.
                        <SU>169</SU>
                        <FTREF/>
                         Others recommended the Commission use a specific threshold for making the determination or provide additional guidance based on the Rule's multi-factor test.
                        <SU>170</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>168</SU>
                             
                            <E T="03">See, e.g.,</E>
                             ANA, at 9 (“Although the ability to age screen users has helped businesses ascertain those users to which COPPA applies, children could benefit from the FTC providing additional guidance on the threshold for determining whether a website or online service is 
                            <E T="03">primarily</E>
                             directed to children”); Google, at 13 (“We support the retention of the mixed audience category, which appropriately recognizes that it is reasonable to treat age screened users as adults when the underlying child-directed content is also directed to adult audiences . . . At the same time, we believe that the definition of mixed audience as currently drafted requires significant clarification, especially with respect to its distinction from primarily child-directed and general audience content”); Lego, at 7 (“[F]urther clarity on how content for mixed audience and adults could be interpreted by regulatory and self-regulatory authorities would increase our ability to provide clearer direction internally on content development”); The Toy Association, at 9 (suggesting the Commission amend the Rule “to establish that a mixed audience site or service, including apps or platforms, is one that offers content directed to children, but whose target audience likely includes a significant number of tweens, teens or adults”) (bold typeface omitted); Internet Association, at 7 (“While it can be fairly straightforward to identify sites and services that are directed primarily to children, the concept of mixed audience sites is not clearly defined and the implications of this concept are unclear and unpredictable”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>169</SU>
                             kidSAFE, at 7-8 (“How can a site or service be `directed to children' for purposes of the factors' test, yet not be `deemed directed to children' for purposes of compliance?”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>170</SU>
                             
                            <E T="03">See, e.g.,</E>
                             The Toy Association, at 9 (“[The Toy Association] suggests that the FTC consider revising the Rule to establish that a mixed audience site or service, including apps or platforms, is one that offers content directed to children, but whose target audience likely includes a significant number of tweens, teens or adults, even if segments other than children do not comprise 50% or more of the audience”) (bold typeface omitted); CIPL, at 3-4 (“In its application of the COPPA Rule, the Commission has increasingly blurred the lines between services that are `primarily directed to children,' services that target children as one but not the primary audience (`mixed audience'), and general audience sites that don't target children as an audience. The FTC should issue guidance based upon the multi-factor test in COPPA to ensure that content creators, app developers and platforms understand how the rules apply to their products and services”); SIIA, at 4 (“As the way people consume content online continues to evolve, additional guidance is needed on the line between child-directed and mixed audience services”); ESRB, at 6-7 (recommending the Commission provide clarity on the “directed to children” analysis through rulemaking or guidance); and J. Johnston (J House Vlogs), at 16 (requesting an “[e]mergency [e]nforcement [s]tatement from the FTC providing . . . [c]larity on the lines between child-directed, mixed-audience, and general audience content”).
                        </P>
                    </FTNT>
                    <P>
                        Commenters also questioned the effectiveness of age screening, with some arguing that children have been conditioned to lie about their age in order to circumvent age gates.
                        <SU>171</SU>
                        <FTREF/>
                         Others expressed support for the current approach,
                        <SU>172</SU>
                        <FTREF/>
                         and some warned against specifying proscriptive methods for age screening, as it could prevent companies from innovating new methods.
                        <SU>173</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>171</SU>
                             
                            <E T="03">See, e.g.,</E>
                             SuperAwesome, at 21; PRIVO, at 7-8; Joint Attorneys General, at 9; CARU, at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>172</SU>
                             
                            <E T="03">See, e.g.,</E>
                             CCIA, at 7-8; U.S. Chamber of Commerce, at 4-5; ANA, at 9; Internet Association, at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>173</SU>
                             
                            <E T="03">See, e.g.,</E>
                             CCIA, at 8; ANA, at 9.
                        </P>
                    </FTNT>
                    <P>
                        Through the 2013 Amendments, the Commission intended mixed audience sites and services to be a subset of the “child-directed” category of websites or online services to which COPPA applies. A website or online service falls under the mixed audience designation if it: (1) meets the Rule's multi-factor test for being child-directed; and (2) does not target children as its primary audience. Unlike other child-directed sites and services, mixed audience sites and services may collect age information and need only apply COPPA's protections to those users who identify as under 13. An operator falling under this mixed audience designation may not collect personal information from any visitor until it collects age information from the visitor. To the extent the visitor identifies themselves as under age 13, the operator must provide notice and obtain verifiable parental consent before collecting, using, and disclosing personal information from the visitor.
                        <SU>174</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>174</SU>
                             16 CFR 312.2, definition of “website or online service directed to children,” paragraph 3.
                        </P>
                    </FTNT>
                    <P>
                        To make its position clearer, the Commission proposes adding to the Rule a separate, stand-alone definition for “mixed audience website or online service.” This definition provides that a mixed audience site or service is one that meets the criteria of the Rule's multi-factor test but does not target children as the primary audience.
                        <SU>175</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>175</SU>
                             Current staff guidance notes that operators should carefully analyze the intended audience, actual audience, and, in many instances, the likely audience for the website or online service in determining whether children are the primary audience or not. 
                            <E T="03">COPPA FAQ</E>
                            s, FAQ D.5.
                        </P>
                    </FTNT>
                    <P>
                        The proposed definition also provides additional clarity on the means by which an operator of a mixed audience site or service can determine whether a user is a child. First, the Commission agrees with the comments that recommend it allow operators flexibility in determining whether a user is a child. To that end, the proposed definition allows operators to collect age information or use “another means that is reasonably calculated, in light of available technology, to determine whether the visitor is a child,” reflecting a standard used elsewhere in the Rule.
                        <SU>176</SU>
                        <FTREF/>
                         Although currently collecting age information may be the most practical means for determining that a user is a child, the proposed definition allows operators to innovate and develop additional mechanisms that do not rely on a user's self-declaration.
                        <SU>177</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>176</SU>
                             
                            <E T="03">Compare</E>
                             proposed definition of “mixed audience website or online service” (as quoted in the text accompanying this footnote) 
                            <E T="03">with</E>
                             16 CFR 312.5(b)(1) (“Any method to obtain verifiable parental consent must be reasonably calculated, in light of available technology, to ensure that the person providing consent is the child's parent.”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>177</SU>
                             Indeed, the Commission supports the development of other means and mechanisms to determine whether the user is a child. Other jurisdictions, such as the United Kingdom, have conducted research that indicates that mechanisms other than self-declaration may be a more effective means of age assurance. Specifically, the research states that parents found the self-declaration method “easy to circumvent,” with many parents “open about themselves and their children lying about their ages.” 
                            <E T="03">Families' attitudes towards age assurance,</E>
                             Research commissioned by the United Kingdom's Information Commissioner's Office and Ofcom (Oct. 11, 2022), at 19, available at 
                            <E T="03">https://www.gov.uk/government/publications/families-attitudes-towards-age-assurance-research-commissioned-by-the-ico-and-ofcom.</E>
                        </P>
                    </FTNT>
                    <P>
                        Additionally, consistent with long-standing staff guidance,
                        <SU>178</SU>
                        <FTREF/>
                         the proposed mixed audience definition specifically requires that the means used for determining whether a visitor is a child “be done in a neutral manner that does not default to a set age or encourage visitors to falsify age information.” This, for instance, would prevent operators from suggesting to users that certain features will not be available for users who identify as younger than 13.
                    </P>
                    <FTNT>
                        <P>
                            <SU>178</SU>
                             
                            <E T="03">COPPA FAQs,</E>
                             FAQ D.7.
                        </P>
                    </FTNT>
                    <P>To further clarify the obligations of an operator of a mixed audience site or service, the Commission also proposes amending paragraph (3) of the definition of “website or online service directed to children” by stating that such operators shall not be deemed directed to children with regard to any visitor not identified as under 13.</P>
                    <HD SOURCE="HD2">B. Notice (16 CFR 312.4)</HD>
                    <P>The Commission proposes a number of modifications to the Rule's direct notice and online notice provisions.</P>
                    <HD SOURCE="HD3">1. Direct Notice to the Parent (Paragraph (b))</HD>
                    <P>
                        Section 312.4(b) requires operators to make reasonable efforts to ensure that parents receive direct notice of an operator's practices with respect to the collection, use, or disclosure of children's information. The Commission proposes adding references to “school” in § 312.4(b) to cover the situation in which an operator relies on authorization from a school to collect information from a child and provides the direct notice to the school rather than to the child's parent. As discussed in Part IV.C.3.a., the Commission is proposing to add an exception to the Rule's parental consent requirement where an operator, in limited contexts, obtains authorization from a school to collect a child's personal information. For purposes of authorization, “school” includes individual schools as well as local educational agencies and State educational agencies, as those terms are defined under Federal law.
                        <SU>179</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>179</SU>
                             
                            <E T="03">See</E>
                             Part IV.C.3.a. for further discussion on the proposed school authorization exception. This proposed definition is intended to preserve the ability of local and State educational agencies to contract on behalf of multiple schools and school districts. This definition aligns with current staff guidance providing that “[a]s a best practice, we recommend that schools or school districts decide whether a particular site's or service's information practices are appropriate, rather than delegating that decision to the teacher.” 
                            <E T="03">COPPA FAQs,</E>
                             FAQ N.3.
                        </P>
                    </FTNT>
                    <P>
                        Just as notice is necessary for a parent to provide informed and meaningful consent, a school must also obtain information about an operator's data 
                        <PRTPAGE P="2049"/>
                        collection and use practices before authorizing collection. Therefore, as part of the proposed school authorization exception, an operator must make reasonable efforts to ensure that the school receives the notice that the operator would otherwise provide to a child's parent.
                    </P>
                    <HD SOURCE="HD3">2. Content of the Direct Notice (Paragraph (c))</HD>
                    <P>Section 312.4(c) details the content of the direct notice required where an operator avails itself of one of the Rule's exceptions to prior parental consent set forth in § 312.5(c)(1)-(8). The Commission proposes several modifications to § 312.4(c). The first is to delete the reference to “parent” in the § 312.4(c) heading. This modification is to accommodate the proposed new § 312.4(c)(5), which specifies the content of the direct notice where an operator relies on school authorization to collect personal information.</P>
                    <P>Next, the Commission proposes modifying language in § 312.4(c)(1) and a number of its paragraphs. As currently drafted, this section sets forth the required content of direct notice when an operator collects personal information in order to initiate parental consent under the parental consent exception listed in § 312.5(c)(1). The Commission proposes revising the heading of § 312.4(c)(1) by adding the phrase “for purposes of obtaining consent, including . . .” after “[c]ontent of the direct notice to the parent” and before “under § 312.5(c)(1).” This change would clarify that this direct notice requirement applies to all instances in which the operator provides direct notice to a parent for the purposes of obtaining consent, including under § 312.5(c)(1).</P>
                    <P>In its current form, § 312.4(c)(1) presumes that an operator has collected a parent's online contact information and, potentially, the name of the child or parent. However, operators are free to use other means to initiate parental consent, including those that do not require collecting online contact information. For example, an operator could use an in-app pop-up message that directs the child to hand a device to the parent and then instructs a parent to call a toll-free number. The modification is intended to clarify that even where the operator does not collect personal information to initiate consent under § 312.5(c)(1), it still must provide the relevant aspects of the § 312.4(c)(1) direct notice to the parent.</P>
                    <P>
                        Because the Commission's proposed changes to § 312.4(c)(1) would expand the scope of when an operator must provide this direct notice, the Commission proposes modifications to indicate that §§ 312.4(c)(1)(i) and newly-numbered 312.4(c)(1)(vii) may not be applicable in all instances.
                        <SU>180</SU>
                        <FTREF/>
                         Additionally, because §§ 312.4(c)(1)(i) and newly-numbered 312.4(c)(1)(vii) apply to scenarios in which an operator is obtaining parental consent under the parental consent exception provided in § 312.5(c)(1), the Commission proposes making minor modifications to those sections to align language with that exception. Specifically, that exception permits operators to collect a child's name or online contact information prior to obtaining parental consent, and the proposed notice would require the operator to indicate when it has collected a child's name or online contact information.
                    </P>
                    <FTNT>
                        <P>
                            <SU>180</SU>
                             As discussed in Part IV.B.2., the Commission proposes expanding § 312.4(c)(1) to include instances in which operators collect information other than online contact information to obtain consent. The modifications to §§ 312.4(c)(1)(i) and newly-numbered 312.4(c)(1)(vii) address those instances in which an operator may not have collected a parent's or child's online contact information to obtain consent.
                        </P>
                    </FTNT>
                    <P>
                        The Commission also proposes adding a new paragraph (iv) to require that operators sharing personal information with third parties identify the third parties as well as the purposes for such sharing, should the parent provide consent. This new paragraph (iv) will also require the operator to state that the parent can consent to the collection and use of the child's information without consenting to the disclosure of such information, except where such disclosure is integral to the nature of the website or online service.
                        <SU>181</SU>
                        <FTREF/>
                         For example, such disclosure could be integral if the website or online service is an online messaging forum through which children necessarily have to disclose their personal information, such as online contact information, to other users on that forum. The Commission believes that this information will enhance parents' ability to make an informed decision about whether to consent to the collection of their child's personal information. In order to minimize the burden on operators, and to maintain the goal of providing parents with a clear and concise direct notice, the proposed modification allows operators to disclose the categories of third parties with which the operator shares data rather than identifying each individual entity. The Commission welcomes further comment on whether information regarding the identities or categories of third parties with which an operator shares information is most appropriately placed in the direct notice to parents required under § 312.4(c) or in the online notice required under § 312.4(d).
                    </P>
                    <FTNT>
                        <P>
                            <SU>181</SU>
                             This proposed modification effectuates current requirements under the Rule, namely § 312.5(a)(2), which states that “[a]n operator must give the parent the option to consent to the collection and use of the child's personal information without consenting to disclosure of his or her personal information to third parties.”
                        </P>
                    </FTNT>
                    <P>
                        Additionally, the Commission proposes a number of clarifying changes. First, the Commission proposes clarifying that the information at issue in the first clause of § 312.4(c)(1)(ii) is “personal information.” 
                        <SU>182</SU>
                        <FTREF/>
                         Second, in § 312.4(c)(1)(iii), the Commission proposes clarifying that the direct notice must include how the operator intends to use the personal information collected from the child. For example, to the extent an operator uses personal information collected from a child to encourage or prompt use of the operator's website or online service such as through a push notification, such use must be explicitly stated in the direct notice. Additionally, the Commission further proposes to change the current use of “or” to “and” to indicate that the operator must provide all information listed in § 312.4(c)(1)(iii). Lastly, the Commission also proposes removing the term “additional” from § 312.4(c)(1)(iii) because this paragraph no longer applies solely to instances in which the operator collects the parent's or child's name or online contact information.
                    </P>
                    <FTNT>
                        <P>
                            <SU>182</SU>
                             This clause currently uses the term “such information.” 16 CFR 312.4(c)(1)(ii).
                        </P>
                    </FTNT>
                    <P>
                        In addition to the proposed modifications to § 312.4(c)(1), the Commission proposes adding § 312.4(c)(5) to identify the content of the direct notice an operator must provide when seeking to obtain school authorization to collect personal information.
                        <SU>183</SU>
                        <FTREF/>
                         While tailored to the school context, the requirements in this new provision generally track the proposed modifications to § 312.4(c)(1).
                        <SU>184</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>183</SU>
                             The Commission is aware that ed tech operators may enter into standard contracts with schools, school districts, and other education organizations across the country. This direct notice requirement is not meant to interfere with such contractual arrangements. Operators may employ various methods to meet the proposed direct notice requirement without interfering with the standard contract, such as by appending the direct notice to the contract. 
                            <E T="03">See</E>
                             Part IV.C.3.a. for further discussion of the direct notice required under this exception.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>184</SU>
                             For instance, proposed § 312.4(c)(5)(iii) requires the operator to provide the information collected from the child, how the operator intends to use such information, and the potential opportunities for disclosure. Similarly, to the extent the operator discloses information to third parties, proposed § 312.4(c)(5)(iv) requires the operator to 
                            <PRTPAGE/>
                            provide the identities or specific categories of such third parties and the purposes for such disclosures.
                        </P>
                    </FTNT>
                    <PRTPAGE P="2050"/>
                    <HD SOURCE="HD3">3. Notice on the Website or Online Service (Paragraph (d))</HD>
                    <P>
                        The Commission proposes two additions to the Rule's online notice requirement. These additions pertain to an operator's use of the exception for prior parental consent set forth in § 312.5(c)(7) and the proposed exception set forth in new proposed § 312.5(c)(9).
                        <SU>185</SU>
                        <FTREF/>
                         The Commission also proposes certain modifications to the Rule's existing online notice requirements.
                    </P>
                    <FTNT>
                        <P>
                            <SU>185</SU>
                             Given that these proposed disclosures may be longer and somewhat technical in nature, the Commission believes their appropriate location is in the operator's online notice rather than the direct notice.
                        </P>
                    </FTNT>
                    <P>
                        First, the Commission proposes adding a new paragraph, § 312.4(d)(3), which would require operators that collect a persistent identifier under the support for the internal operations exception in § 312.5(c)(7) to specify the particular internal operation(s) for which the operator has collected the persistent identifier and describe the means it uses to ensure that it does not use or disclose the persistent identifier to contact a specific individual, including through behavioral advertising, to amass a profile on a specific individual, in connection with processes that encourage or prompt use of a website or online service, or for any other purpose, except as permitted by the support for the internal operations exception.
                        <SU>186</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>186</SU>
                             The Commission also proposes requiring operators to implement a data retention policy as part of the requirements for § 312.10. 
                            <E T="03">See</E>
                             Part IV.G. for a discussion of this proposed change.
                        </P>
                    </FTNT>
                    <P>
                        Currently, an operator that collects a persistent identifier pursuant to § 312.5(c)(7) is not required to provide notice of the collection. The Commission finds merit in the concerns expressed by some commenters about a lack of transparency in how operators implement the support for the internal operations exception and the extent to which they comply with the exception's restrictions.
                        <SU>187</SU>
                        <FTREF/>
                         The Commission believes that the proposed disclosure requirements will provide additional clarity into the use of § 312.5(c)(7), will enhance operator accountability, and will function as an important tool for monitoring COPPA compliance.
                    </P>
                    <FTNT>
                        <P>
                            <SU>187</SU>
                             
                            <E T="03">See</E>
                             Part IV.A.4. for a discussion of these concerns.
                        </P>
                    </FTNT>
                    <P>
                        Second, as discussed in Part IV.C.3.b., the Commission proposes a new parental consent exception, codifying its law enforcement policy statement regarding the collection of audio files.
                        <SU>188</SU>
                        <FTREF/>
                         Consistent with this codification, the Commission also proposes a new § 312.4(d)(4) requiring that an operator that collects audio files pursuant to the new § 312.5(c)(9) exception describe how the operator uses the audio files and to represent that it deletes such files immediately after responding to the request for which the files were collected.
                    </P>
                    <FTNT>
                        <P>
                            <SU>188</SU>
                             
                            <E T="03">See</E>
                             Part IV.C.3.b.
                        </P>
                    </FTNT>
                    <P>
                        The Commission also proposes a number of other modifications to the Rule's online notice requirements. Specifically, the Commission proposes modifying § 312.4(d)(2) to require additional information regarding operators' disclosure practices and operators' retention policies.
                        <SU>189</SU>
                        <FTREF/>
                         As discussed earlier, the Commission believes that this information will enhance parents' ability to make an informed decision about whether to consent to the collection of their child's personal information. The Commission notes that the COPPA Rule's online notice provision requires that operators describe how they use personal information collected from children.
                        <SU>190</SU>
                        <FTREF/>
                         For example, to the extent an operator uses personal information collected from a child to encourage or prompt use of the operator's website or online service such as through a push notification, such use must be explicitly stated in the online notice. The Commission also proposes adding “if applicable” to current § 312.4(d)(3) (which would be redesignated as § 312.4(d)(5)) in order to acknowledge that there may be situations in which a parent cannot review or delete the child's personal information.
                        <SU>191</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>189</SU>
                             The Commission proposes requiring operators to implement a data retention policy as part of the requirements for § 312.10. 
                            <E T="03">See</E>
                             Part IV.G. for a discussion of this proposed change.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>190</SU>
                             16 CFR 312.4(d)(2).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>191</SU>
                             As discussed in Part IV.D., operators utilizing the school authorization exception would not be required to provide parents the rights afforded under § 312.6(a) for information collected under that exception.
                        </P>
                    </FTNT>
                    <P>Lastly, the Commission proposes to delete the reference to “parent” in the § 312.4(d) introductory text. This proposal is to align with the Commission's new proposed direct notice requirement to accommodate the proposed new school authorization exception found in § 312.5(c)(10).</P>
                    <HD SOURCE="HD3">4. Additional Notice on the Website or Online Service Where an Operator Has Collected Personal Information Under § 312.5(c)(10) (New Paragraph § 312.4(e))</HD>
                    <P>
                        The Commission also proposes adding a separate online notice provision applicable to operators that obtain school authorization to collect personal information from children pursuant to the proposed exception set forth in § 312.5(c)(10). These disclosures are in addition to the requirements of § 312.4(d). The Commission believes these proposed disclosures will convey important information to parents regarding the limitations on an operator's use and disclosure of personal information collected under the school authorization exception, and the school's ability to review that information and request the deletion of such information.
                        <SU>192</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>192</SU>
                             The school's ability to review information and request the deletion of such information are addressed in Part IV.D. in connection with the proposed modification to § 312.6.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">C. Parental Consent (16 CFR 312.5)</HD>
                    <P>
                        The verifiable parental consent requirement, in combination with the notice provisions, is a fundamental component of the COPPA Rule's ability to protect children's privacy. The Rule requires operators to obtain verifiable parental consent before they collect, use, or disclose a child's personal information.
                        <SU>193</SU>
                        <FTREF/>
                         Operators must make “reasonable efforts to obtain verifiable parental consent” and any parental consent method “must be reasonably calculated, in light of available technology, to ensure that the person providing consent is the child's parent.” 
                        <SU>194</SU>
                        <FTREF/>
                         Although the Rule sets forth a non-exhaustive list of methods that the Commission has recognized as meeting this standard, the Commission encourages operators to develop their own consent mechanisms provided they meet the “reasonably calculated standard” required by § 312.5(b)(1). In addition to the enumerated consent mechanisms listed in § 312.5(b)(2), § 312.5(c) provides several exceptions pursuant to which an operator may collect limited personal information without first obtaining parental consent and, in some cases, without providing notice.
                    </P>
                    <FTNT>
                        <P>
                            <SU>193</SU>
                             Operators must also obtain such consent for “any material change in the collection, use, or disclosure practices to which the parent has previously consented.” 16 CFR 312.5(a)(1).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>194</SU>
                             16 CFR 312.5(b)(1).
                        </P>
                    </FTNT>
                    <P>
                        The Commission requested comment in its 2019 Rule Review Initiation on the efficacy of the Rule's consent requirements, including whether the Commission should add to the list of approved methods and whether there are ways to encourage the development of new consent methods. The Commission also requested comment on whether the Commission should consider additional exceptions to the consent requirement, including with respect to the collection of audio files 
                        <PRTPAGE P="2051"/>
                        containing a child's voice and in the educational context where a school authorizes the operator to collect personal information.
                    </P>
                    <P>The Commission proposes modifying the Rule's consent requirements in a number of ways. First, the Commission proposes requiring the operator to obtain separate verifiable parental consent before disclosing personal information collected from a child. The Commission also proposes modifying the consent method set forth in § 312.5(b)(2)(ii) and incorporating into the Rule two previously approved consent mechanisms submitted through the § 312.12(a) voluntary process. Lastly, the Commission proposes modifying the parental consent exceptions set forth in § 312.5(c)(4), (6), and (7) and adding exceptions for where an operator relies on school authorization and for the collection of audio files that contain a child's voice.</P>
                    <HD SOURCE="HD3">1. General Requirements (Paragraph (a))</HD>
                    <P>Section 312.5(a)(1) provides that an operator must obtain verifiable parental consent before collecting, using, or disclosing personal information from a child. While the Commission does not propose modifications to this paragraph, it seeks to make a clarification. This requirement applies to any feature on a website or online service through which an operator collects personal information from a child. For example, if an operator institutes a feature that prompts or enables a child to communicate with a chatbot or other similar computer program that simulates conversation, the operator must obtain verifiable parental consent before collecting any personal information from a child through that feature. While the Commission is not proposing modifications to this paragraph, it welcomes comment on it.</P>
                    <P>
                        Section 312.5(a)(2) currently states that “[a]n operator must give the parent the option to consent to the collection and use of the child's information without consenting to disclosure of his or her personal information to third parties.” The Commission proposes bolstering this requirement by adding that operators must obtain separate verifiable parental consent for disclosures of a child's personal information, unless such disclosures are integral to the nature of the website or online service.
                        <SU>195</SU>
                        <FTREF/>
                         Under the proposed language, operators required to obtain separate verifiable parental consent for disclosures may not condition access to the website or online service on such consent.
                    </P>
                    <FTNT>
                        <P>
                            <SU>195</SU>
                             This exception aligns with previous staff guidance, in which FTC staff has stated that operators are not required to provide parents with a separate option to consent to the disclosure of the child's personal information where such disclosures are integral to the site or service. The guidance requires the operators to make clear when such disclosures are integral. 
                            <E T="03">See COPPA FAQs,</E>
                             FAQ A.1. For example, such disclosure could be integral if the website or online service is an online messaging forum through which children necessarily have to disclose their personal information, such as online contact information, to other users on that forum.
                        </P>
                    </FTNT>
                    <P>
                        In the preamble of the 1999 initial COPPA Rule, the Commission noted that “disclosures to third parties are among the most sensitive and potentially risky uses of children's personal information. This is especially true in light of the fact that children lose even the protections of [COPPA] once their information is disclosed to third parties.” 
                        <SU>196</SU>
                        <FTREF/>
                         The Commission remains concerned about the disclosure of personal information collected from children. Indeed, one commenter noted that “[c]hildren today face surveillance unlike any other generation—their every movement online and off can be tracked by potentially dozens of different companies and organizations.” 
                        <SU>197</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>196</SU>
                             64 FR 59888 at 59899.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>197</SU>
                             Common Sense Media, at 3.
                        </P>
                    </FTNT>
                    <P>The Commission believes that information sharing is a pervasive practice. Therefore, the Commission finds it appropriate to provide parents with greater control over the disclosure of their children's information by clarifying that § 312.5(a)(2) requires operators to obtain separate verifiable parental consent for disclosures. This includes disclosure of persistent identifiers for targeted advertising purposes, as well as disclosure of other personal information for marketing or other purposes. The Commission did not seek comment on this particular aspect of the Rule's verifiable parental consent requirements in the 2019 Rule Review Initiation and welcomes comment on this proposed modification.</P>
                    <HD SOURCE="HD3">2. Methods for Verifiable Parental Consent (Paragraph (b))</HD>
                    <P>
                        The Commission received numerous comments related to the methods by which operators can obtain parental consent. Many commenters criticized particular approved parental consent methods. Some characterized the methods as outdated or counterintuitive.
                        <SU>198</SU>
                        <FTREF/>
                         Others complained that the methods failed to serve unbanked or low-income families who may lack access to the means to provide consent, such as a credit card.
                        <SU>199</SU>
                        <FTREF/>
                         Some commenters suggested that the use of credit card data and government-issued IDs are too privacy-invasive,
                        <SU>200</SU>
                        <FTREF/>
                         while one advocate claimed that the current methods are better indicators of adulthood than parenthood.
                        <SU>201</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>198</SU>
                             
                            <E T="03">See, e.g.,</E>
                             FOSI, at 4-5 (describing current method of requiring submission by facsimile as outdated, staffing a toll-free number as expensive, and requiring a credit card number for a service that should be free as counter-intuitive); ESA, at 24 (“For example, the collection of a driver's license or credit card in connection with a transaction may appear particularly cumbersome in the context of a free mobile app that does not require registration and that collects and uses only limited types of information within the app”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>199</SU>
                             
                            <E T="03">See, e.g.,</E>
                             internet Association, at 13; CIPL, at 5; Net Safety Collaborative, at 2; Connected Camps, at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>200</SU>
                             
                            <E T="03">See, e.g.,</E>
                             P. Aftab, at 12-13; 
                            <E T="03">see also</E>
                             ESRB, at 8 (noting that parents may be disinclined to provide credit card information unless the operator is a name the parents know and trust).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>201</SU>
                             P. Aftab, at 13.
                        </P>
                    </FTNT>
                    <P>
                        Commenters also expressed concern that the current methods include too much friction, resulting in significant drop-off during the consent process. Commenters noted that this friction discourages operators from creating services that target children or creates an incentive to limit their collection of personal information to avoid triggering COPPA.
                        <SU>202</SU>
                        <FTREF/>
                         Consistent with this view, the Network Advertising Initiative stated that “[r]ecognizing that verifiable parental consent mechanisms are challenging and expensive to implement, and result in considerable drop-off, the practical reality is that most ad-tech companies simply seek to avoid advertising to children altogether.” 
                        <SU>203</SU>
                        <FTREF/>
                         Other commenters warned that cumbersome consent methods can drive children to general audience sites, which may have fewer digital safety and privacy protections in place.
                        <SU>204</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>202</SU>
                             
                            <E T="03">See, e.g.,</E>
                             ESRB, at 8; CIPL, at 4-5; Internet Association, at 13; Connected Camps, at 2-3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>203</SU>
                             
                            <E T="03">See</E>
                             NAI, at 2; s
                            <E T="03">ee also</E>
                             Attorney General of Arizona, at 2 (noting that “. . . the cost of obtaining verifiable parental consent can be unduly burdensome on small businesses, and the consent process can be frustrating for both businesses and parents alike”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>204</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Lego, at 4-5; Net Safety Collaborative, at 2.
                        </P>
                    </FTNT>
                    <P>
                        Some commenters suggested modifying existing consent methods or adding new ones. For example, several recommended that the Commission eliminate the need for a monetary transaction when an operator obtains consent through a credit or debit card or an online payment system where the system provides notification of transactions that do not involve a charge.
                        <SU>205</SU>
                        <FTREF/>
                         Some recommended 
                        <PRTPAGE P="2052"/>
                        modifying the Rule to allow for the use of text messages to obtain consent. Those commenters noted that text messages are a common alternative to email for verification purposes and argued that text message-based consent is no weaker than consent initiated through the collection of an email address.
                        <SU>206</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>205</SU>
                             
                            <E T="03">See, e.g.,</E>
                             ANA, at 12 (“. . . companies should be able to obtain verifiable parental consent by requesting a valid credit card from a parent even if the consent is not obtained in connection with a monetary transaction”); kidSAFE, at 10 (“The FTC 
                            <PRTPAGE/>
                            should consider eliminating the need for a `monetary' transaction when consent is obtained using a credit card, debit card, or other online payment system that provides notification of each discreet [
                            <E T="03">sic</E>
                            ] transaction”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>206</SU>
                             
                            <E T="03">See</E>
                             ANA, at 12; The Toy Association, at 4; kidSAFE, at 11.
                        </P>
                    </FTNT>
                    <P>
                        Other commenters called for the Commission to add to the list of approved consent methods. They recommended allowing the use of fingerprint or facial recognition technologies that already exist in parents' mobile devices,
                        <SU>207</SU>
                        <FTREF/>
                         voice recognition technology currently used in the online banking context,
                        <SU>208</SU>
                        <FTREF/>
                         and a variety of other technologies and tools.
                        <SU>209</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>207</SU>
                             
                            <E T="03">See</E>
                             ESRB, at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>208</SU>
                             
                            <E T="03">See</E>
                             Net Safety Collaborative, at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>209</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Net Choice, at 12 (recommending the use of a digital certificate that uses public key technology coupled with additional steps to demonstrate that consent is from the parent); Internet Association, at 14 (recommending that the Commission add a mechanism whereby parents log into a preexisting parental account); CTIA, at 2-3 (recommending obtaining consent through the set-up process for services, such as wearables, that collect personal information from children at parents' direction); Yoti, at 12 (recommending the use of age estimation and age verification tools instead of parental consent).
                        </P>
                    </FTNT>
                    <P>
                        Several commenters recommended that the Commission encourage platforms to participate in the parental consent process.
                        <SU>210</SU>
                        <FTREF/>
                         One suggested that platforms could provide notifications to the consenting parent about the intended collection, use, or disclosure of the child's personal information.
                        <SU>211</SU>
                        <FTREF/>
                         Another suggested that parents would be more likely to engage with platforms than to provide consent on a service-by-service basis.
                        <SU>212</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>210</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Princeton University, at 9 (noting that mobile operating systems offer linked parent and child accounts and could provide an interface for child accounts to submit consent permission requests to parent accounts).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>211</SU>
                             
                            <E T="03">See</E>
                             ACT: The App Association, at 4-5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>212</SU>
                             
                            <E T="03">See</E>
                             ESRB, at 8.
                        </P>
                    </FTNT>
                    <P>
                        Commenters also recommended different procedural steps the Commission could undertake. These include such things as the Commission using its authority to conduct studies on the costs and benefits of different consent methods,
                        <SU>213</SU>
                        <FTREF/>
                         streamlining the Rule's current 120-day comment period on applications for new parental consent methods,
                        <SU>214</SU>
                        <FTREF/>
                         and convening stakeholder meetings to explore effective solutions.
                        <SU>215</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>213</SU>
                             
                            <E T="03">See</E>
                             Pokémon, at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>214</SU>
                             
                            <E T="03">See</E>
                             CCIA, at 10; SIIA, at 3-4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>215</SU>
                             
                            <E T="03">See</E>
                             Lego, at 5; The Toy Association, at 20; Yoti, at 13.
                        </P>
                    </FTNT>
                    <P>After reviewing these comments, the Commission continues to believe that the Rule's current approach to verifiable parental consent is appropriate and sound. With respect to the more general concerns that COPPA's consent methods create “friction,” the Commission stresses that COPPA requires a balance between facilitating consent mechanisms that are not prohibitively difficult for operators or parents, while also ensuring that it is a parent granting informed consent, rather than a child circumventing the process. In response to commenters indicating that this friction has discouraged operators from creating services or caused operators to change their practices, the Commission welcomes the development of methods that prove less cumbersome for operators while still meeting COPPA's statutory requirements.</P>
                    <P>
                        As to the more specific criticisms of the approved consent mechanisms set forth in the Rule, the Commission notes that operators are not obligated to use any of those methods.
                        <SU>216</SU>
                        <FTREF/>
                         Rather, operators are free to develop and use any method that meets the standard contained in § 312.5(b)(1) and to tailor their approach to their own individual situation.
                    </P>
                    <FTNT>
                        <P>
                            <SU>216</SU>
                             Indeed, the Commission is aware that many operators will choose not to utilize certain enumerated methods. However, the Commission retains these methods in the Rule in case any operator would like to use these methods.
                        </P>
                    </FTNT>
                    <P>While it is possible that some of the suggested methods could meet the § 312.5(b)(1) requirement, the Commission does not believe the comments contain sufficient detail or context for it to propose adding these additional consent methods at this time. The Commission welcomes further explanation detailing the necessity and practicality of any recommended new consent method, including how it would satisfy the Rule's requirements. This could come in the form of additional comments or through the voluntary approval process provided in § 312.12(a) of the Rule.</P>
                    <P>
                        At the same time, the Commission agrees that platforms could play an important role in the consent process, and the Commission has long recognized the potential of a platform-based common consent mechanism.
                        <SU>217</SU>
                        <FTREF/>
                         The Commission would also welcome further information on the role that platforms could play in facilitating the obtaining of parental consent. In particular, the Commission would be interested in any potential benefits platform-based consent mechanisms would create for operators and parents and what specific steps the Commission could take to encourage development of such mechanisms.
                    </P>
                    <FTNT>
                        <P>
                            <SU>217</SU>
                             78 FR 3972 at 3989-90 (noting that platform-based common consent mechanism could simplify operators' and parents' abilities to protect children's privacy).
                        </P>
                    </FTNT>
                    <P>
                        The Commission also agrees with the recommendation that it modify the Rule to eliminate the monetary transaction requirement when an operator obtains consent through a parent's use of a credit card, debit card, or an online payment system. As one commenter noted, many of these payment mechanisms provide a means for the account holder to receive notification of every transaction, even those that cost no money, such as a free mobile app download.
                        <SU>218</SU>
                        <FTREF/>
                         In addition, many operators offer their apps or other online services at no charge. Requiring such operators to charge the parent a fee when seeking consent undercuts their ability to offer the service at no cost. Further, the Commission understands that some consumers might be hesitant to complete consent processes when they will incur even a nominal monetary charge.
                    </P>
                    <FTNT>
                        <P>
                            <SU>218</SU>
                             kidSAFE, at 10.
                        </P>
                    </FTNT>
                    <P>
                        In proposing this modification, the Commission notes that it had previously determined that a monetary transaction was necessary for this form of consent.
                        <SU>219</SU>
                        <FTREF/>
                         At that time, the Commission reasoned that requiring a monetary transaction would increase the method's reliability because the parent would receive a record of the transaction. This would provide the parent notice of purported consent, which, if improperly given, the parent could then withdraw. Because § 312.5(b)(2)(ii), as proposed to be modified, would still require notice of a discrete transaction, even where there is no monetary charge, the Commission believes this indicia of reliability is preserved. Where a payment system cannot provide notice absent a monetary charge, an operator will not be able to obtain consent through this method.
                    </P>
                    <FTNT>
                        <P>
                            <SU>219</SU>
                             
                            <E T="03">See</E>
                             76 FR 59804 at 59819; 
                            <E T="03">see also</E>
                             78 FR 3972 at 3987.
                        </P>
                    </FTNT>
                    <P>
                        The Commission also agrees with the recommendation to modify the Rule to allow the use of text messages to obtain consent. As discussed in Part IV.A.1., the Commission believes this is achieved through its proposed modification to the “online contact information” definition.
                        <SU>220</SU>
                        <FTREF/>
                         Therefore, the Commission does not propose 
                        <PRTPAGE P="2053"/>
                        modifying § 312.5(b)(2)(ii) to address this recommendation.
                    </P>
                    <FTNT>
                        <P>
                            <SU>220</SU>
                             
                            <E T="03">See</E>
                             Part IV.A.1.
                        </P>
                    </FTNT>
                    <P>
                        In addition to the modification to § 312.5(b)(2)(ii), the Commission also proposes adding two parental consent methods to § 312.5(b). These methods are knowledge-based authentication and the use of facial recognition technology. The Commission approved both methods pursuant to the § 312.12(a) process created from the 2013 Amendments.
                        <SU>221</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>221</SU>
                             
                            <E T="03">See Letter to Imperium, LLC</E>
                             (Dec. 23, 2013) (approval of knowledge-based authentication), available at 
                            <E T="03">https://www.ftc.gov/sites/default/files/attachments/press-releases/ftc-grants-approval-new-coppa-verifiable-parental-consent-method/131223imperiumcoppa-app.pdf; Letter to Jest8 Limited (Trading as Riyo)</E>
                             (Nov. 18, 2015) (approval of facial recognition technology), 
                            <E T="03">available at https://www.ftc.gov/system/files/documents/public_statements/881633/151119riyocoppaletter.pdf.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">3. Exceptions to Prior Parental Consent (Paragraph (c))</HD>
                    <P>The Commission also received numerous comments regarding possible additional exceptions to the Rule's parental consent requirement. The majority of the commenters addressing this issue focused on whether the Commission should allow schools to authorize data collection, use, and disclosure in certain circumstances rather than requiring ed tech operators to obtain parental consent. A smaller number of commenters addressed whether the Commission should codify in the Rule its existing enforcement policy statement regarding the collection of audio files. In addition, several commenters recommended that the Commission expand the Rule's current one-time use exception.</P>
                    <P>
                        The Commission proposes creating exceptions for where an operator relies on school authorization and for the collection of audio files that contain a child's voice. The Commission also proposes a modification to § 312.5(c)(7), which relates to the support for the internal operations exception, to align with proposed new requirements.
                        <SU>222</SU>
                        <FTREF/>
                         Additionally, Commission proposes a modification to § 312.5(c)(4) to exclude from this exception the use of push notifications to encourage or prompt use of a website or online service. Finally, the Commission proposes technical modifications to § 312.5(c)(6). At this time, the Commission does not propose expanding the Rule's current one-time use exception.
                    </P>
                    <FTNT>
                        <P>
                            <SU>222</SU>
                             
                            <E T="03">See</E>
                             Part IV.B.3. for discussion of the Commission's proposed notice requirement under 16 CFR 312.4(d)(3).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">a. School Authorization Exception</HD>
                    <P>
                        In response to the Commission's initial proposed COPPA Rule in 1999, stakeholders expressed concern about how the Rule would apply to the use of websites and online services in schools. Some of these commenters claimed that requiring parental consent to collect students' information could interfere with classroom activities.
                        <SU>223</SU>
                        <FTREF/>
                         In response, the Commission noted in the final Rule's preamble “that the Rule does not preclude schools from acting as intermediaries between operators and parents in the notice and consent process, or from serving as the parents' agent in the process.” 
                        <SU>224</SU>
                        <FTREF/>
                         It further stated, “where an operator is authorized by a school to collect personal information from children, after providing notice to the school of the operator's collection, use, and disclosure practices, the operator can presume that the school's authorization is based on the school's having obtained the parent's consent.” 
                        <SU>225</SU>
                        <FTREF/>
                         Since that time, Commission staff has provided additional guidance on this issue through its “Complying with COPPA: Frequently Asked Questions” document (“COPPA FAQs”), which specifies that an operator may rely on school consent when it collects a child's personal information provided the operator uses the information for an educational purpose and for “no other commercial purpose.” 
                        <SU>226</SU>
                        <FTREF/>
                         The Commission has since issued a policy statement on COPPA's application to ed tech providers, similarly noting that operators of ed tech that collect personal information pursuant to school authorization are prohibited from using such information for any commercial purpose, including marketing, advertising, or other commercial purposes unrelated to the provision of the school-requested online service.
                        <SU>227</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>223</SU>
                             
                            <E T="03">See</E>
                             64 FR 59888 at 59903.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>224</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>225</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>226</SU>
                             
                            <E T="03">COPPA FAQs,</E>
                             FAQ N.1.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>227</SU>
                             
                            <E T="03">Policy Statement of the Federal Trade Commission on Education Technology and the Children's Online Privacy Protection Act,</E>
                             Federal Trade Commission (May 19, 2022), available at 
                            <E T="03">https://www.ftc.gov/legal-library/browse/policy-statement-federal-trade-commission-education-technology-childrens-online-privacy-protection.</E>
                        </P>
                    </FTNT>
                    <P>
                        In recent years there has been a significant expansion of ed tech used in both classrooms and in the home.
                        <SU>228</SU>
                        <FTREF/>
                         This expansion, in the form of students' increased access to school-issued computers and online learning curricula, raised questions about ed tech providers' compliance with the Rule as well as calls for additional guidance on how COPPA applies in the school context. Stakeholders also questioned how COPPA obligations relate to those operators subject to FERPA, the federal law that protects the privacy of “education records,” and its implementing regulations.
                        <SU>229</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>228</SU>
                             The closure of schools and in-person learning due to the global COVID-19 pandemic added to this expansion as students shifted to remote education.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>229</SU>
                             FERPA applies to all schools receiving funds from any applicable program of the Department of Education. 34 CFR 99.1. In general, unless an exception applies, parents (or students over 18 years of age) must provide consent for the disclosure of personal information from an education record. 34 CFR 99.30. FERPA provides an exception to its parental consent requirement for “school officials.” 34 CFR 99.31. Under this exception, schools do not need to obtain consent to disclose personal information where there is a “legitimate educational interest.” In addition, the school must maintain direct control over the information.
                        </P>
                    </FTNT>
                    <P>
                        In 2017, the FTC and the Department of Education hosted a workshop on student privacy and ed tech to explore these questions.
                        <SU>230</SU>
                        <FTREF/>
                         Through the discussions at the workshop, the Commission gathered information that helped inform the questions posed in the 2019 Rule Review Initiation regarding the application of the COPPA Rule to the education context. The Commission asked whether it should modify the Rule to add an exception to the parental consent requirement where the school provides authorization and, if so, whether the exception should mirror the requirements of FERPA's “school official exception.” 
                        <SU>231</SU>
                        <FTREF/>
                         The Commission also asked for comment on various aspects of a school authorization exception, including how student data could be used, who at the school should be able to provide consent, and notice to parents.
                        <SU>232</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>230</SU>
                             
                            <E T="03">Student Privacy and Ed Tech</E>
                             (Dec. 1, 2017), available at 
                            <E T="03">https://www.ftc.gov/news-events/events/2017/12/student-privacy-ed-tech.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>231</SU>
                             The FERPA school official exception allows schools to outsource institutional services or functions that involve the disclosure of education records to contractors, consultants, volunteers, or other third parties, provided that the outside party: “(1) Performs an institutional service or function for which the agency or institution would otherwise use employees; (2) Is under the direct control of the agency or institution with respect to the use and maintenance of education records; (3) Is subject to the requirements in 34 CFR 99.33(a) that the personally identifiable information (PII) from education records may be used only for the purposes for which the disclosure was made, 
                            <E T="03">e.g.,</E>
                             to promote school safety and the physical security of students, and governing the redisclosure of PII from education records; and (4) Meets the criteria specified in the school or local educational agency's (LEA's) annual notification of FERPA rights for being a school official with a legitimate educational interest in the education records.” 
                            <E T="03">Who is a “School Official” Under FERPA?,</E>
                             Department of Education, available at 
                            <E T="03">https://studentprivacy.ed.gov/faq/who-%E2%80%9Cschool-official%E2%80%9D-under-ferpa.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>232</SU>
                             The Commission also asked for comment on deletion rights in the educational context. The issue of the deletion of information collected when a school has provided authorization is discussed in Part IV.D.
                        </P>
                    </FTNT>
                    <PRTPAGE P="2054"/>
                    <HD SOURCE="HD3">i. Whether To Include a School Authorization Exception in the Rule</HD>
                    <P>
                        Numerous commenters representing industry and schools, along with some consumer groups, expressed support for codifying a school authorization exception in the Rule so long as such exception is consistent with FERPA and its implementing regulations. That is, where there is a legitimate educational interest to collect the child's data, the school maintains direct control of the data, and the operator uses the data only as permitted by the school and complies with disclosure limits.
                        <SU>233</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>233</SU>
                             
                            <E T="03">See, e.g.,</E>
                             CIPL, at 6; Net Safety Collaborative, at 3; Illinois Council of School Attorneys, at 1-2; Association of American Publishers, at 5; CCIA, at 11; internet Association, at 14-17; SIIA, at 3; Joint comment of the Consortium for School Networking, Knowledge Alliance, National Association of State Boards of Education, and the State Educational Technology Directors Association (“CoSN”), at 2; National School Boards Association, at 4-5; National Parent Teacher Association, at 2; Joint comment of the AASA, the School Superintendents Association, and the Association of Education Service Agencies, at 1-3; CDT, at 5; Khan Academy, at 2; Google, at 18; Future of Privacy Forum, at 10-12; Lego, at 5-6. Some commenters supported the Commission implementing a school authorization exception within the Rule but did not call for alignment with FERPA's school official exception. 
                            <E T="03">See, e.g.,</E>
                             ANA, at 13-14; Lightspeed, at 1-2; The Toy Association, at 5, 19-20; 5Rights, at 6.
                        </P>
                    </FTNT>
                    <P>
                        In supporting such an exception, several of these commenters raised concerns that requiring schools to obtain consent from parents would be burdensome and costly for schools.
                        <SU>234</SU>
                        <FTREF/>
                         These commenters claimed that the burden would include obtaining parental consent as well as providing curriculum to students whose parents did not consent to the use of the ed tech program.
                        <SU>235</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>234</SU>
                             
                            <E T="03">See</E>
                             CDT, at 4 (noting that “[s]ome schools do not have the resources or the time to ask for consent from parents every time they rely on an educational technology product”); CCIA, at 11 (noting that “[a]s Ed Tech becomes increasingly prevalent in the classroom, requiring parental consent for every online service used in the classroom would quickly become administratively and practically unwieldy for parents and schools alike, with the resulting consent fatigue decreasing the availability of beneficial technologies and services to all students”); Lightspeed, at 2 (“Seeking explicit, written parental approval for every single use of technology by a student at present is impracticable. Requiring parents to affirmatively approve each student's use of every application would lead to an avalanche of paperwork for parents and school administrators, one that would push schools to shy away from utilizing EdTech solutions in the classroom”); National PTA, at 3 (noting that “[w]hen student data is collected in support of core curricular functions, National PTA believes that schools should be able to act as parents' agents and consent on parents' behalf. However, not all student data collection meets that standard. Schools use education technology for a broad range of extracurricular, non-essential or optional activities . . . We ask that the FTC clarify when schools may act on behalf of parents, differentiating between technology used in support of schools' essential academic and administrative needs and other, optional uses”); Net Safety, at 3 (urging the Commission to ensure that schools' burden and cost of obtaining parental consent under COPPA not be increased); Illinois Council of School Attorneys, at 2 (noting that “requiring school districts to obtain verifiable parental consent from all parents/guardians for potentially hundreds of education applications in use in a district would be an enormous and unworkable administrative burden, even for those districts that have more resources available to them”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>235</SU>
                             
                            <E T="03">See, e.g.,</E>
                             National School Boards Association, at 3 (“If school districts are required to get actual parent consent, many districts would be unable to deliver the curriculum to students whose parents have not responded, creating inequities in addition to administrative burdens”); CIPL, at 5 (noting that “[i]t could also result in administrative burden and classroom disruption for teachers to manage different lesson plans for students whose parents have provided consent and those whose parents have not”).
                        </P>
                    </FTNT>
                    <P>
                        Commenters also raised concerns about requiring ed tech providers to obtain verifiable parental consent from parents. For example, commenters expressed concern that requiring operators to obtain parental consent would require operators to collect additional personal information from parents, much of which is not necessary to provide the educational service, which contradicts data minimization principles.
                        <SU>236</SU>
                        <FTREF/>
                         One commenter argued that requiring parents to consent would lead to “consent fatigue,” 
                        <SU>237</SU>
                        <FTREF/>
                         while another commenter explained that operators often do not have a direct touchpoint with parents that could facilitate the consent process.
                        <SU>238</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>236</SU>
                             
                            <E T="03">See</E>
                             CIPL, at 5; ANA, at 14; CCIA, at 11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>237</SU>
                             CCIA, at 11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>238</SU>
                             ANA, at 13.
                        </P>
                    </FTNT>
                    <P>
                        The Illinois Council of School Attorneys argued that schools are often in a better position than parents to evaluate ed tech products.
                        <SU>239</SU>
                        <FTREF/>
                         They also pointed to privacy protections in the FERPA school official exception including the requirement that the school maintain direct control of the data and the operator use the data for only limited, authorized purposes.
                        <SU>240</SU>
                        <FTREF/>
                         Finally, in supporting a school authorization exception, some commenters stated that numerous operators have built up their consent process in reliance on the Commission's existing guidance indicating that COPPA permits schools to provide consent for educational purposes.
                        <SU>241</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>239</SU>
                             Illinois Council of School Attorneys, at 1.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>240</SU>
                             The organization also noted that schools consenting on behalf of parents is consistent with their 
                            <E T="03">in loco parentis</E>
                             role. Illinois Council of School Attorneys, at 1-2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>241</SU>
                             
                            <E T="03">See</E>
                             ANA, at 13; Association of American Publishers, at 3.
                        </P>
                    </FTNT>
                    <P>
                        However, not all commenters supported a school authorization exception, with several consumer groups, parent organizations, and government representatives raising various concerns.
                        <SU>242</SU>
                        <FTREF/>
                         For example, a coalition of consumer groups argued that a COPPA exception aligned with FERPA would not adequately protect children because FERPA fails to provide a clear standard for when a party has a “legitimate educational interest” as required by the school official exception. The coalition also claimed that schools fail to adequately inform parents about the use of FERPA's school official exception and that most schools are ill-equipped to properly vet the privacy and security practices of ed tech services.
                        <SU>243</SU>
                        <FTREF/>
                         Another advocacy organization cited statistics purportedly showing that schools do not comply with the school official exception.
                        <SU>244</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>242</SU>
                             
                            <E T="03">See, e.g.,</E>
                             EPIC, at 8-9 (asserting that “[i]nstead of putting the burden on schools to obtain and provide consent on behalf of parents, which they are unauthorized to do under the Act, the burden should be shifted to operators, who are in a better position to do so given advancements in technology and greater availability of resources, to obtain verifiable parental consent”); Joint Consumer Groups, at 20-30; Unidos, at 6 (noting that “cash-strapped districts could be preyed upon by bad actors targeting these districts by offering free or low-cost programs to gain a foothold in schools and start collecting children's data. Many of these companies have opaque privacy policies. Inadequately funded school administrators and/or teachers will not likely have the resources to advocate for better protections or do a sufficient review to understand policies, especially in an environment where schools are using countless apps and programs”); Illinois Families for Public Schools, at 2 (noting that “[p]arental consent is especially important in the case of extremely sensitive student data regarding children's behavior, biometrics, geolocation, disabilities, or health conditions. As such, we disagree firmly with the idea of amending COPPA rules to have a Family Educational Rights and Privacy Act (FERPA)-type exception for school officials to grant consent for the collection and use of a child's data in an educational setting in place of a parent. The school-official exception in FERPA has weakened its protections for disclosure of student data, and this should not be a precedent for modifying or weakening the COPPA Rule”); Joint Attorneys General, at 10-11; Parent Coalition for Student Privacy, at 8 (noting that “[p]arents' existing rights under COPPA to be informed and provide prior consent to any program collecting data directly from their children under the age of 13 should not be erased or limited simply because their children's use of a commercial operator's service occurs inside the school building or at the direction of a teacher or school administrator”); Senator Markey, et al., at 2 (noting that this type of exception could be “fundamentally inconsistent with the congressional intent behind COPPA”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>243</SU>
                             
                            <E T="03">See</E>
                             Joint Consumer Groups, at 25-29.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>244</SU>
                             
                            <E T="03">See</E>
                             Surveillance Technology Oversight Project (“STOP”), at 3-4.
                        </P>
                    </FTNT>
                    <P>
                        A number of individual parents also opposed the exception. These individuals emphasized that parents should retain the ability afforded to them under COPPA to provide consent to collect, use, and share their children's data.
                        <SU>245</SU>
                        <FTREF/>
                         One parent noted that over 400 ed tech providers had access to her 
                        <PRTPAGE P="2055"/>
                        child's data, and that she is unable to understand what information was shared with each provider.
                        <SU>246</SU>
                        <FTREF/>
                         These parents noted that school districts should not be able to provide consent to ed tech providers on their behalf,
                        <SU>247</SU>
                        <FTREF/>
                         and further noted that including such an exception would weaken COPPA rather than strengthen it.
                        <SU>248</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>245</SU>
                             
                            <E T="03">See, e.g.,</E>
                             A. Segur, at 1; F. Bocquet, at 1; M. Murphy, at 1; N. Williams, at 1.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>246</SU>
                             A. Segur, at 1.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>247</SU>
                             
                            <E T="03">See</E>
                             A. Segur, at 1; F. Bocquet, at 1; M. Murphy, at 1; N. Williams, at 1.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>248</SU>
                             
                            <E T="03">See, e.g.,</E>
                             A. Segur, at 1; F. Bocquet, at 1; N. Williams, at 1.
                        </P>
                    </FTNT>
                    <P>
                        Another concern raised was that such an exception could ultimately swallow the Rule.
                        <SU>249</SU>
                        <FTREF/>
                         For instance, in a joint comment of multiple State Attorneys General, the Attorneys General cited the incredible growth in ed tech and noted the technologies are not cabined to the classroom but are often encouraged to be used by students at home, and sometimes for non-educational purposes. The Attorneys General argued that, because the use of ed tech is often mandatory for students, an exception to COPPA's parental consent requirement would force parents to choose between education and their children's online privacy.
                        <SU>250</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>249</SU>
                             
                            <E T="03">See</E>
                             Senator Markey, et al., at 2 (noting that such an exception “risks opening the door to invasive tracking of children for advertising purposes”); Joint Attorneys General, at 10-11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>250</SU>
                             Joint Attorneys General, at 10-11.
                        </P>
                    </FTNT>
                    <P>
                        While opposing a school authorization exception, the Parent Coalition for Student Privacy argued that if the Commission decides to create one, its applicability should be limited in scope. Specifically, the Coalition argued that schools should not be able to consent to the collection of particularly sensitive data, such as medical or geolocation information.
                        <SU>251</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>251</SU>
                             Parent Coalition for Student Privacy, at 11-12.
                        </P>
                    </FTNT>
                    <P>
                        After careful consideration of the comments, the Commission proposes codifying in the Rule its long-standing guidance that schools, State educational agencies, and local educational agencies may authorize the collection of personal information from students younger than 13 in very limited circumstances; specifically, where the data is used for a school-authorized education purpose and no other commercial purpose.
                        <SU>252</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>252</SU>
                             The definition for “school-authorized education purpose” is discussed in Part IV.A.3. 
                            <E T="03">See</E>
                             Part IV.B.1. for further discussion about the proposed inclusion of State and local educational agencies within the definition of “school.”
                        </P>
                    </FTNT>
                    <P>
                        When a child goes to school, schools have the ability to act 
                        <E T="03">in loco parentis</E>
                         under certain circumstances. This is particularly the case when schools are selecting the means through which the schools and school districts can achieve their educational purposes, such as when deciding which educational technologies to use in their classrooms. The Commission finds compelling the concern that requiring parental consent in the educational context would impose an undue burden on ed tech providers and educators alike. As an initial matter, many ed tech providers have relied upon and structured their consent mechanisms based on the Commission's existing guidance. Requiring providers to reconfigure their systems to obtain parental consent directly from parents would undoubtedly create logistical problems that could increase costs and potentially dissuade some ed tech providers from offering their services to schools.
                        <SU>253</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>253</SU>
                             The Commission also agrees with commenters that noted that obtaining parental consent could require providers to collect additional personal information from parents that they would not collect if the school provides consent.
                        </P>
                    </FTNT>
                    <P>The need for parental consent is also likely to interfere with educators' curriculum decisions. As a practical matter, obtaining consent from the parents of every student in a class often will be challenging, in many cases for reasons unrelated to privacy concerns. In situations where some number of parents in a class decline to consent to their children's use of ed tech, schools would face the prospect of foregoing particular services for the entire class or developing a separate mechanism for those students whose parents do not consent. Because the proposed school authorization exception restricts an operator's use of children's data to a school-authorized education purpose and precludes use for commercial purposes such as targeted advertising, it may ultimately be more privacy-protective than requiring ed tech providers to obtain consent from parents.</P>
                    <P>
                        Finally, the proposed school authorization exception requires that the ed tech provider and the school have in place a written agreement setting forth the exception's requirements.
                        <SU>254</SU>
                        <FTREF/>
                         This includes identifying who from the school may provide consent and attesting that such individual has the authority to provide consent; the limitations on the use and disclosure of student data; the school's control over the use, disclosure, and maintenance of the data; and the operator's data retention policy. Accordingly, the proposed exception incorporates the privacy protections contained in the FERPA school official exception. This exception also builds on FERPA's protections by incorporating the Commission's existing prohibition on the use of student data for non-educational commercial purposes.
                    </P>
                    <FTNT>
                        <P>
                            <SU>254</SU>
                             As noted in Part IV.B.2., the Commission is aware that operators may enter into standard contracts to provide ed tech services. So long as the standard contract meets the elements required under proposed § 312.5(c)(10), operators may continue to utilize such contracts.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">ii. Permitted Use of Data Collected Through the School Authorization Exception</HD>
                    <P>
                        Existing staff guidance indicates that, where the school authorizes data collection, an operator may only use children's data for an educational purpose and for no other commercial purpose.
                        <SU>255</SU>
                        <FTREF/>
                         However, there has been confusion around the parameters of what constitutes an “educational purpose” as opposed to a “commercial purpose.” 
                        <SU>256</SU>
                        <FTREF/>
                         Many of the commenters that support a school authorization exception to parental consent called on the Commission to clarify the permissible uses of data collected under such an exception.
                        <SU>257</SU>
                        <FTREF/>
                         In an effort to seek further clarity, commenters suggested specific uses that the Commission should explicitly allow or exclude under the exception.
                        <SU>258</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>255</SU>
                             
                            <E T="03">See COPPA FAQs,</E>
                             FAQ N.1; 
                            <E T="03">Policy Statement of the Federal Trade Commission on Education Technology and the Children's Online Privacy Protection Act,</E>
                             Federal Trade Commission (May 19, 2022), available at 
                            <E T="03">https://www.ftc.gov/legal-library/browse/policy-statement-federal-trade-commission-education-technology-childrens-online-privacy-protection.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>256</SU>
                             Additionally, FERPA does not define what a “legitimate educational interest” is for purposes of the school official exception. Thus, even if the Commission aligned a COPPA school consent exception with FERPA, the scope of the exception would be unclear.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>257</SU>
                             
                            <E T="03">See, e.g.,</E>
                             CCIA, at 11-12; Joint comment of the AASA, the School Superintendents Association, and the Association of Education Service Agencies, at 3-4; Parent Coalition for Student Privacy, at 4-5; Google, at 18.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>258</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Joint comment of the AASA, the School Superintendents Association, and the Association of Education Service Agencies, at 4 (advocating for the inclusion of product research and development); Parent Coalition for Student Privacy, at 3 (opposing the use of children's information to advertise, improve a service, or develop a new service); Google, at 18 (noting that a “commercial purpose” under COPPA could be aligned with FERPA such that “. . . certain types of processing are impermissible, such as personalized ads or product placements, but other important activities to support educational services are permitted, like the maintenance, development and improvement of the product, analytics, and personalization of content within the service”).
                        </P>
                    </FTNT>
                    <P>
                        Among these commenters, there was general agreement that the exception should not permit ed tech providers to use student data for marketing purposes, such as serving personalized advertisements.
                        <SU>259</SU>
                        <FTREF/>
                         The comments 
                        <PRTPAGE P="2056"/>
                        reflected less consensus on the question of whether to allow operators to engage in product improvement or development. Some commenters favored allowing product improvement or development under limited circumstances. For example, Lego recommended that the exception allow operators to use aggregated or anonymized data to improve existing products or develop new products that would benefit students.
                        <SU>260</SU>
                        <FTREF/>
                         The 5Rights Foundation similarly noted that, if the Commission were to allow operators to use student data to improve products, the student information must be “de-identified and de-identifiable,” cannot be shared with third parties, and must be limited to use for improving educational products only.
                        <SU>261</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>259</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Princeton University, at 10; 5Rights Foundation, at 5 (“FTC could usefully clarify both the definition of `educational purposes' for which consent can be sought, and the scope of purposes that are proscribed (including, but not limited to, 
                            <PRTPAGE/>
                            direct marketing, behavioural advertising, and any profiling not necessary to the functioning of the service in question)”); Consumer Reports, at 18 (noting that “. . . operators seeking consent in the school setting should be prohibited from using the information for marketing”); internet Association, at 16 (“IA strongly supports appropriate limits on online service operators' use of students' personal information and does not believe that online services should be able to rely on school official consent in order to use personal information for marketing purposes”); STOP, at 5 (noting that the Rule “ . . . must also prohibit operators from using students' personal information for marketing or product-improvement purposes”); Google, at 18 (recognizing the need to exclude commercial activities like advertising, including personalized ads and product placement).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>260</SU>
                             Lego, at 6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>261</SU>
                             5Rights Foundation, at 6. 
                            <E T="03">See also</E>
                             Khan Academy, at 3 (noting the distinction between internal use of data for educational product development and disclosure of that data to third parties for commercial purposes); Yoti, at 14 (recommending allowing operators to use student data where the school has provided consent for research and development, broadly defined, so long as protections are in place); Oregon Attorney General, at 3 (if operators are allowed to use data for product improvement, Commission should consider “whether operators are able to de-identify the personal information, and are able to prevent re-identification of the data”).
                        </P>
                    </FTNT>
                    <P>
                        In contrast, some commenters strongly opposed allowing product improvement absent verifiable parental consent. For example, EPIC argued that product improvement would allow ed tech vendors “to create virtual laboratories in schools to study child behavior and further develop commercial products for profit, unbeknownst to parents.” 
                        <SU>262</SU>
                        <FTREF/>
                         Others raised similar objections,
                        <SU>263</SU>
                        <FTREF/>
                         including parents who stated that the Commission should prohibit the use of student data to improve or develop new products or services.
                        <SU>264</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>262</SU>
                             EPIC, at 11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>263</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Parent Coalition for Student Privacy, at 11 (“The Commission should ban operators of education technology from using or processing de-identified or identifiable student information to improve existing or to develop or improve new educational or non-educational products and services”); Illinois Families for Public Schools, at 2 (opposing use of student data “for advertising purposes or to improve or develop new products or services”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>264</SU>
                             
                            <E T="03">See, e.g.,</E>
                             F. Bocquet, at 1; N. Williams, at 1.
                        </P>
                    </FTNT>
                    <P>
                        In discussing the appropriate use of student data, several commenters suggested that the Commission adopt an approach similar to the treatment of activities that fall under the COPPA Rule's definition of “support for the internal operations of the website or online service.” This approach would allow ed tech providers to use student data for “analytics, content personalization, and product development, maintenance, and improvement uses that benefit students and schools” but not for activities such as personalized marketing.
                        <SU>265</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>265</SU>
                             
                            <E T="03">See, e.g.,</E>
                             CCIA, at 12. 
                            <E T="03">See also</E>
                             CIPL, at 3 (suggesting that companies be allowed to engage in profiling in the education context in order to provide “'personalized” curricula); School Superintendents, at 3 (recommending that FTC clarify that “commercial purposes” for purposes of school consent exception does not include activities that would fall under the Rule's support for internal operations exception); Google, at 18 (“. . . certain types of processing are impermissible, such as personalized ads or product placements, but other important activities to support educational services are permitted, like the maintenance, development and improvement of the product, analytics, and personalization of content within the service”).
                        </P>
                    </FTNT>
                    <P>
                        The Commission believes that it should tailor the proposed school exception narrowly while ensuring its practicality for schools and operators. The Commission agrees with the commenters asserting that the use or disclosure of student data for marketing purposes should fall outside the school authorization exception. Indeed, this view is consistent with staff's guidance that schools can consent to the collection of student data for educational purposes but not for other commercial purposes, such as marketing and advertising.
                        <SU>266</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>266</SU>
                             
                            <E T="03">See COPPA FAQs,</E>
                             FAQ N.1; 
                            <E T="03">Policy Statement of the Federal Trade Commission on Education Technology and the Children's Online Privacy Protection Act,</E>
                             Federal Trade Commission (May 19, 2022), available at 
                            <E T="03">https://www.ftc.gov/legal-library/browse/policy-statement-federal-trade-commission-education-technology-childrens-online-privacy-protection.</E>
                        </P>
                    </FTNT>
                    <P>The Commission also agrees with those commenters recommending that the school authorization exception should allow operators to engage in limited product improvement and development, provided certain safeguards are in place. The Commission believes that allowing providers to make ongoing improvements to the educational services the school has authorized benefits students and educators, and that user data may be necessary to identify and remedy a problem or “bug” in a product or service. Therefore, in contrast to general marketing, product improvement and development can be viewed as part of providing an educational purpose rather than engaging in an unrelated commercial practice.</P>
                    <P>That said, the Commission is mindful of the concerns that allowing such uses, particularly product development, could open the door to ed tech providers exploiting the exception. To address these concerns, the Commission proposes that the Rule's definition of a “school-authorized education purpose” include product improvement and development (as well as other uses related to the operation of the product, including maintaining, supporting, or diagnosing the service), provided the use is directly related to the service the school authorized. This would permit operators to improve the service, for example by fixing bugs or adding new features, or develop a new version of the service. An operator may not use the information it collected from one educational service to develop or improve a different service.</P>
                    <P>The Commission believes that limiting product improvement and development in this way will allow ed tech providers to provide better services while helping to safeguard against the use of student data for non-educational purposes. We also believe that this proposed approach is consistent with the requirement under FERPA's school official exception that a school have a “legitimate educational interest” to share personal information without parental consent.</P>
                    <P>
                        The Commission does not agree with the commenters that recommended aligning the permissible uses of data collected under the school authorization exception with the Rule's support for the internal operations exception. The two exceptions serve different purposes, and the activities within the support for the internal operations definition are generally unnecessary for and unrelated to the provision of an educational purpose.
                        <SU>267</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>267</SU>
                             The Commission notes that one potential area of overlap between these exceptions is that the support for the internal operations exception allows an operator to personalize content on a website or online service. The Commission recognizes that some degree of personalization will be inherent in providing the ed tech service for which the student data is collected. For example, this can include personalizing curricula or advancing a student who has completed an assignment to the next level or unit in a lesson plan. While such personalization would be a permissible part of providing the service, personalization could not include the marketing of services even if those services were educational in nature.
                        </P>
                    </FTNT>
                    <P>
                        As an additional protection, the proposed school authorization exception would require operators to 
                        <PRTPAGE P="2057"/>
                        have a written agreement with the school setting forth the exception's requirements. This written agreement must specify that the ed tech provider's use and disclosure of the data collected under the exception is limited to a school-authorized education purpose as defined in the Rule and for no other purpose. As an extra safeguard to help ensure that ed tech providers are using student data appropriately and to align the exception with FERPA, the required written agreement must specify that the school will have direct control over the provider's use, disclosure, and maintenance of the personal information under the exception. The agreement must also include the operator's data retention policy with respect to personal information collected from children under the school authorization exception.
                    </P>
                    <HD SOURCE="HD3">iii. Who at the school should provide authorization?</HD>
                    <P>
                        In response to the question of who should be able to provide authorization for data collection under the school authorization exception, a wide variety of commenters, including industry, FTC-approved COPPA Safe Harbor programs, school personnel, and the Oregon Attorney General, called for flexibility.
                        <SU>268</SU>
                        <FTREF/>
                         For example, while the Illinois Council of School Attorneys recommended against specifying who can provide authorization, it stated that if the Commission decides to do so, it should use general, flexible terminology such as “employees designated by the school's administration or governing board” to describe individuals who may provide authorization.
                        <SU>269</SU>
                        <FTREF/>
                         The Oregon Attorney General called for flexibility and urged the Commission to be mindful that schools and districts obtain and implement ed tech in different ways.
                        <SU>270</SU>
                        <FTREF/>
                         Another commenter, kidSAFE, recommended the Commission permit consent from an adult outside the school environment, including coaches or tutors.
                        <SU>271</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>268</SU>
                             
                            <E T="03">See</E>
                             internet Association, at 15; ANA, at 13; SIIA, at 3; FOSI, at 5; kidSAFE, at 4; Illinois Council of School Attorneys, at 2; Oregon Attorney General, at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>269</SU>
                             Illinois Council of School Attorneys, at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>270</SU>
                             Oregon Attorney General, at 2 (noting that, in Oregon, some schools contract with educational technology companies through an intragovernmental technology alliance while others do so independently).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>271</SU>
                             kidSAFE, at 4.
                        </P>
                    </FTNT>
                    <P>
                        Other commenters supported a more prescriptive approach,
                        <SU>272</SU>
                        <FTREF/>
                         with some recommending that the Rule not allow teachers to provide consent.
                        <SU>273</SU>
                        <FTREF/>
                         One commenter stated that few teachers are in a position to evaluate which ed tech services are trustworthy, adding that allowing individual teachers to make these decisions prevents school administrators from knowing what products are being used in the classroom.
                        <SU>274</SU>
                        <FTREF/>
                         Another recommended requiring that, if schools are allowed to provide consent on behalf of parents, the school or district must have clear and uniform policies for adopting ed tech led by a team of qualified education research, curriculum, and privacy, and technology experts.
                        <SU>275</SU>
                        <FTREF/>
                         Similarly, Lego recommended that only duly authorized individuals, such as IT administrators, data protection officers, or chief IT officers, provide consent through a contract with the ed tech provider.
                        <SU>276</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>272</SU>
                             
                            <E T="03">See</E>
                             P. Aftab, at 8; Common Sense Media, at 8; Parent Coalition for Student Privacy, at 14; Lego, at 6; Privo, at 6; STOP, at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>273</SU>
                             
                            <E T="03">See</E>
                             P. Aftab, at 8; Common Sense Media, at 8; Lego, at 6; Privo, at 6; STOP, at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>274</SU>
                             P. Aftab, at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>275</SU>
                             Parent Coalition for Student Privacy, at 14.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>276</SU>
                             Lego, at 7.
                        </P>
                    </FTNT>
                    <P>
                        Because the Commission believes it is important to accommodate the different ways schools obtain and implement ed tech, the Commission agrees with the commenters that called for flexibility rather than a “one size fits all” approach. At the same time, the Commission recognizes the need for measures to prevent the situation in which a school is unaware of the ed tech services their teachers have consented to on an ad hoc basis. Indeed, staff guidance has previously recommended that consent for ed tech to collect personal information comes from the schools or school districts rather than from individual teachers.
                        <SU>277</SU>
                        <FTREF/>
                         To balance the need for flexibility with the need for oversight and accountability, the Commission proposes that the written agreement between the ed tech provider and the school, which the new § 312.5(c)(10) exception would require, identify the name and title of the person providing consent and specify that the school has authorized the person to provide such consent.
                    </P>
                    <FTNT>
                        <P>
                            <SU>277</SU>
                             
                            <E T="03">COPPA FAQs,</E>
                             FAQ N.3.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">iv. Notice to Parents</HD>
                    <P>
                        Many of the commenters supporting a school consent exception recommended that parents receive notice of the ed tech providers the school authorized to collect children's data.
                        <SU>278</SU>
                        <FTREF/>
                         Some commenters suggested that the notice to parents come from schools, recommending that the notice be similar to the FERPA annual notification requirement 
                        <SU>279</SU>
                        <FTREF/>
                         or that schools make information about ed tech providers' information practices available to parents in a public place such as the school district's website.
                        <SU>280</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>278</SU>
                             
                            <E T="03">See, e.g.,</E>
                             CDT, at 8; Common Sense, at 11; Consumer Reports, at 17; FPF, at 12; The National PTA, at 3; Lego, at 6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>279</SU>
                             CDT, at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>280</SU>
                             FPF, at 12.
                        </P>
                    </FTNT>
                    <P>
                        Other commenters raised concerns about the Commission imposing obligations on schools through the Rule. For example, the Oregon Attorney General expressed concern that allowing an operator to shift notice obligations to schools would potentially shield operators from liability.
                        <SU>281</SU>
                        <FTREF/>
                         Instead, the Oregon Attorney General recommended that the Commission require the operator to “provide notice of its information practices in a manner that is easily accessible to all parents . . . and to inform the school on where parents may find such notice of information practices.” 
                        <SU>282</SU>
                        <FTREF/>
                         Similarly, the Parent Coalition for Student Privacy recommended that, if the Commission creates an exception for school authorization, it require ed tech providers to dedicate space on their website for notices about the exception and explain how the data will be strictly used for educational purposes and state which third parties can access the data.
                        <SU>283</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>281</SU>
                             Oregon Attorney General, at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>282</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>283</SU>
                             Parent Coalition for Student Privacy, at 8-9 (also recommending that schools should also be required to link to and post this information as it applies to the specific education technology services the schools choose to utilize).
                        </P>
                    </FTNT>
                    <P>
                        The Commission agrees that notice is an important aspect of the proposed school authorization exception. At the same time the Commission agrees with commenters who raised concerns about imposing burdens on schools that may not have sufficient resources to undertake an additional administrative responsibility.
                        <SU>284</SU>
                        <FTREF/>
                         To promote transparency without burdening schools, the Commission proposes requiring operators to provide notice. Namely, the Commission's proposed addition of § 312.4(e), discussed earlier in Part IV.B.4., would require an operator that collects personal information from a child under the school authorization exception to include an additional notice on its website or online service noting that: (1) the operator has obtained authorization from a school to collect a child's personal information; (2) that the 
                        <PRTPAGE P="2058"/>
                        operator will use and disclose the information for a school-authorized education purpose and no other purpose; and (3) that the school may review information collected from a child and request deletion of such information.
                        <SU>285</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>284</SU>
                             Moreover, the Commission cannot impose COPPA obligations on schools. COPPA applies to an operator of a website or online service directed to children, or any operator that has actual knowledge that it is collecting personal information from a child. 15 U.S.C 6502(a)(1); 16 CFR 312.3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>285</SU>
                             
                            <E T="03">See</E>
                             Part IV.B.4. for discussion on this proposed change.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Audio File Exception</HD>
                    <P>
                        In 2013, the Commission expanded the Rule's definition of “personal information” to include “[a] photograph, video, or audio file where such file contains a child's image or voice.” 
                        <SU>286</SU>
                        <FTREF/>
                         Since that time there has been a dramatic increase in the popularity of internet-connected “home assistants” and other devices that are voice activated and controlled. This led to inquiries from stakeholders about the Rule's applicability to the collection of audio files containing a child's voice where an operator converts the audio to text and then deletes the audio file. While the Commission determined that the Rule applies to such collection, it recognized the value of using verbal commands to perform search and other functions on internet-connected devices, especially for children who have not yet learned to write or those with disabilities. Accordingly, in 2017, the Commission issued an enforcement policy statement indicating that it would not take action against an operator who, without obtaining parental consent, collects a child's voice recording, provided the operator only uses the audio file as a replacement for written words, such as to effectuate an instruction or request, and the operator retains the recording only for a brief period.
                        <SU>287</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>286</SU>
                             16 CFR 312.2, definition of “personal information.”
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>287</SU>
                             
                            <E T="03">Enforcement Policy Statement Regarding the Applicability of the COPPA Rule to the Collection and Use of Voice Recordings,</E>
                             82 FR 58076 (Dec. 8, 2017), available at 
                            <E T="03">https://www.ftc.gov/system/files/documents/public_statements/1266473/coppa_policy_statement_audiorecordings.pdf.</E>
                             The enforcement statement also specified that the operator must provide the notice required by the COPPA Rule and sets forth a number of important limitations on the policy's application.
                        </P>
                    </FTNT>
                    <P>In the 2019 Rule Review Initiation, the Commission asked whether it should modify the Rule to include a parental consent exception based on the enforcement policy statement. The Commission also asked whether such an exception should allow an operator to use de-identified audio files for product improvement and, if so, how long an operator could retain such data. Additionally, the Commission asked whether de-identification of audio files is effective at preventing re-identification.</P>
                    <P>
                        The vast majority of commenters that addressed the issue recommended the Commission modify the Rule to include a parental consent exception for audio files based on the existing enforcement policy statement.
                        <SU>288</SU>
                        <FTREF/>
                         Some of these commenters supported the narrow confines of the current enforcement statement, which requires the collected audio file to serve solely as a replacement for written words and be maintained only until completion of that purpose.
                        <SU>289</SU>
                        <FTREF/>
                         A number of other commenters, however, recommended that the Commission adopt a more expansive audio exception. For example, Google noted that many voice actions for internet-connected devices are not a replacement for written words. Because of this, Google recommended that the Commission include an expanded exception that “covers voice data used to perform a task or engage with a device, as well as to replace written words.” 
                        <SU>290</SU>
                        <FTREF/>
                         Others made similar recommendations.
                        <SU>291</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>288</SU>
                             
                            <E T="03">See, e.g.,</E>
                             CIPL, at 6; TechFreedom, at 22; ANA, at 14; CCIA, at 13; CTIA, at 5-6; ESA, at 22-23; Google, at 19; internet Association, at 17-18; NCTA, at 11; U.S. Chamber of Commerce, at 5-7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>289</SU>
                             FOSI, at 6; FPF, at 5-6; The Toy Association, at 17.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>290</SU>
                             Google, at 19 (noting that a written command is not typically used to play a video or turn on an appliance and that collection of this type of voice data would pose no additional risk as it would still be briefly retained only to complete the requested action).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>291</SU>
                             
                            <E T="03">Id.; see also, e.g.,</E>
                             CCIA, at 13 (noting that the exception should apply to voice data generally as emerging technologies may not necessarily use verbal commands as a “replacement” for written words); U.S. Chamber of Commerce, at 6 (noting that voice-activated commands may not constitute a replacement for written words).
                        </P>
                    </FTNT>
                    <P>
                        Several commenters argued that where an operator de-identifies the audio file, the exception should allow it to engage in product improvement as well as internal operations such as improving functionality and personalization.
                        <SU>292</SU>
                        <FTREF/>
                         Only a few of these commenters discussed the means by which an operator could effectively de-identify audio files. One suggested using the approach set forth in a White House draft privacy law, which would require the operator to alter the data to prevent it from being linked to a specific individual, to commit not to re-identify the data, and to require third-party recipients to similarly commit not to re-identify the data.
                        <SU>293</SU>
                        <FTREF/>
                         Another commenter suggested the operator could de-link the audio file from a user's account or device identifier.
                        <SU>294</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>292</SU>
                             
                            <E T="03">See</E>
                             internet Association, at 17-18 (asserting that the exception should allow use of audio recordings to train and improve voice recognition and understanding systems); ANA, at 15 (noting that the exception should allow operators to use de-identified audio files to improve current products and future products); TechFreedom, at 23 (noting that the exception should allow de-identified audio files to train automatic speech recognition systems); NCTA, at 11 (recommending the Commission allow product improvement as well as improved functionality, personalization or analytics, and customer service). 
                            <E T="03">See also</E>
                             CTIA, at 6 (recommending that even if data is not de-identified, the exception should allow an operator to retain the data for product improvement, provided it is not combined with other personal information and appropriate safeguards are in place).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>293</SU>
                             See TechFreedom, at 25-26, citing White House, Administration Discussion Draft: Consumer Privacy Bill of Rights Act of 2015 (Feb. 27, 2015), available at 
                            <E T="03">https://obamawhitehouse.archives.gov/sites/default/files/omb/legislative/letters/cpbr-actof-2015-discussion-draft.pdf.</E>
                             This approach is based on the Commission's own data de-identification standard. 
                            <E T="03">See Protecting Consumer Privacy in an Era of Rapid Change,</E>
                             Federal Trade Commission (March 2012), page 22, available at 
                            <E T="03">https://www.ftc.gov/sites/default/files/documents/reports/federal-trade-commission-report-protecting-consumer-privacy-era-rapid-change-recommendations/120326privacyreport.pdf.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>294</SU>
                             NCTA, at 11.
                        </P>
                    </FTNT>
                    <P>
                        The Commission received a small number of comments that opposed adding a consent exception for audio files to the Rule. Arguing against an exception, a group of State Attorneys General characterized recordings of children's voices as biometric data and stated that, as such, they are “individually-identifying and immutable.” 
                        <SU>295</SU>
                        <FTREF/>
                         These commenters also questioned whether operators could effectively and consistently de-identify audio files, pointing to numerous instances in which anonymized data had been re-identified.
                        <SU>296</SU>
                        <FTREF/>
                         A coalition of consumer groups argued that the Commission's existing enforcement statement, as structured, effectively protects children's privacy and there is no need to amend the Rule to add an exception.
                        <SU>297</SU>
                        <FTREF/>
                         The commenters also stated that if the Commission does add an exception to the Rule, the exception should not permit operators to retain or use collected audio files for product improvement even if the files are de-identified.
                        <SU>298</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>295</SU>
                             Joint Attorneys General, at 11-12. 
                            <E T="03">See also</E>
                             A. Wang, at 2-4 (arguing that parental consent should be required for the collection of children's voice recordings because of the risks of an insecure transfer of data and noting that de-identification is not effective at preventing re-identification).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>296</SU>
                             Joint Attorneys General, at 11-12; A. Wang, at 2-4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>297</SU>
                             Joint Consumer Groups, at 36-41.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>298</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <P>
                        Based on the comments overall, the Commission proposes codifying the audio file enforcement statement as an exception to the Rule's parental consent requirement, with one modification. The Commission believes the calls to expand the exception to also include audio files used to perform a task or to 
                        <PRTPAGE P="2059"/>
                        engage with a device have merit. Limiting the proposed exception to circumstances in which the voice data replaces written words would be overly restrictive and unnecessarily prevent its application to a variety of internet-connected services that do not involve written commands. Further, because the proposed exception requires the operator to delete the collected audio file as soon as the command or engagement is completed, this expansion will not create additional risk to children's privacy. Additionally, to the extent an operator collects personal information beyond the audio file—such as a transcript of the audio file in combination with other personal information—the operator could not utilize the audio file exception and would have to afford COPPA's protections to that information.
                    </P>
                    <P>The Commission, however, does not agree that the exception should allow operators to retain the audio files or to use them for other purposes such as product improvement and internal operations, even if the operator has taken steps to de-identify the data. The Commission agrees that a recording of a child's voice is particularly sensitive given that, like other biometric data, it is personal and unique. Consequently, the privacy risk created by such data potentially falling into the wrong hands and being re-identified exceeds the benefit of allowing broader use. This is especially the case where parents are not provided direct notice or provided the opportunity to consent to such practices.</P>
                    <HD SOURCE="HD3">c. Other Exceptions</HD>
                    <P>
                        The Commission also proposes adding language to the support for the internal operations exception, § 312.5(c)(7), to address the new online notice requirement the Commission proposes.
                        <SU>299</SU>
                        <FTREF/>
                         This proposal indicates that an operator that collects information under the support for the internal operations exception must provide information in its online notice regarding its use of the exception. The Commission also proposes technical fixes to § 312.5(c)(6) for clarity purposes. Namely, the Commission proposes changing § 312.5(c)(6)(i) from “protect the security or integrity of its website or online service” to “protect the security or integrity of 
                        <E T="03">the</E>
                         website or online service” (emphasis added). The Commission also proposes removing “be” in § 312.5(c)(6)(iv) to fix a typographical issue.
                    </P>
                    <FTNT>
                        <P>
                            <SU>299</SU>
                             This proposal is discussed in Part IV.B.3.
                        </P>
                    </FTNT>
                    <P>
                        In addition, the Commission proposes to modify § 312.5(c)(4) to prohibit operators from utilizing this exception to encourage or prompt use of a website or online service. This proposed addition prohibits operators from using online contact information to optimize user attention or maximize user engagement with the website or online service, including by sending push notifications, without first obtaining verifiable parental consent.
                        <SU>300</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>300</SU>
                             The Commission acknowledges that the 
                            <E T="03">COPPA FAQs</E>
                             currently indicate that operators may rely on the multiple contact exception to send push notifications to children without first obtaining verifiable parental consent. 
                            <E T="03">COPPA FAQs,</E>
                             FAQ J.9. The Commission is aware of recent media reports indicating that children may be overusing online services due to engagement-enhancing techniques. The Commission is concerned about the potential harm from such overuse and therefore deems it important to ensure parents are notified and provide verifiable parental consent before operators use such techniques to further children's engagement with websites and online services.
                        </P>
                    </FTNT>
                    <P>
                        Additionally, several commenters recommended that the Commission expand the Rule's current one-time use exception, § 312.5(c)(3).
                        <SU>301</SU>
                        <FTREF/>
                         Specifically, multiple commenters noted that the Commission should expand the types of information collected under this exception to include telephone numbers.
                        <SU>302</SU>
                        <FTREF/>
                         A commenter also requested the Commission expand this exception to permit multiple contacts with a child without providing notice and an opportunity to opt out, as required by the multiple contact exception.
                        <SU>303</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>301</SU>
                             
                            <E T="03">See, e.g.,</E>
                             kidSAFE, at 13; Consumer Technology Association (“CTA”), at 6-7; ESA, at 24-25; NCTA, at 17.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>302</SU>
                             kidSAFE, at 13; CTA, at 6-7; ESA, at 24-25; NCTA, at 17.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>303</SU>
                             kidSAFE, at 13.
                        </P>
                    </FTNT>
                    <P>
                        As explained earlier in the discussion regarding the definition of “online contact information,” the Commission proposes modifying this definition to include a mobile telephone number, provided the operator uses it only to send a text message and not for voice communication, unless and until the operator has obtained the parent's verifiable parental consent.
                        <SU>304</SU>
                        <FTREF/>
                         The Commission believes that the proposed revision to the definition of “online contact information” addresses commenters' recommendations to permit the use of mobile telephone numbers to contact children under the one-time use exception. However, the Commission stresses that under the proposed definition of “online contact information,” operators using a child's mobile telephone number under this exception may only text the child and may not call the child.
                    </P>
                    <FTNT>
                        <P>
                            <SU>304</SU>
                             This discussion can be found in Part IV.A.1.
                        </P>
                    </FTNT>
                    <P>
                        Further, the Commission is not persuaded by commenters suggesting that it should expand this exception to permit multiple contacts with a child without offering parents notice and the opportunity to opt out. The COPPA statute envisioned the scenario in which an operator would have to contact a child more than once to respond to a specific request, and Congress included notice and opt-out requirements in association with such scenario.
                        <SU>305</SU>
                        <FTREF/>
                         This scenario was codified in the COPPA Rule under the multiple contact exception, § 312.5(c)(4). Commenters' recommendation essentially asks the Commission to remove the multiple contact exception's notice and consent requirements. However, the Commission believes these elements are required by the COPPA statute, and therefore it does not propose such modifications.
                    </P>
                    <FTNT>
                        <P>
                            <SU>305</SU>
                             15 U.S.C. 6502(b)(2)(C); 64 FR 59888 at 59902.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">D. Right To Review Personal Information Provided by a Child (16 CFR 312.6)</HD>
                    <P>
                        The Commission proposes a new paragraph related to the Commission's proposed school authorization exception.
                        <SU>306</SU>
                        <FTREF/>
                         Specifically, the Commission proposes requiring operators utilizing such exception to provide schools with the rights operators currently provide parents under § 312.6(a), namely the right to review personal information collected from a child, refuse to permit operators' further use or future online collection of personal information, and to direct operators to delete such information. Under this proposal, operators utilizing the school authorization exception would not be required to provide such rights to parents for information collected under the exception.
                    </P>
                    <FTNT>
                        <P>
                            <SU>306</SU>
                             
                            <E T="03">See</E>
                             Part IV.C.3.a. for further discussion of the proposed school authorization exception.
                        </P>
                    </FTNT>
                    <P>Requiring operators to fulfill requests, such as deletion requests, from each parent could result in schools having to provide different services to different children or forego particular services for the entire class based on the request of an individual parent. To reduce this burden, the Commission proposes this modification. The Commission also proposes deleting the reference to “parent” in the § 312.6 heading to account for this modification.</P>
                    <HD SOURCE="HD2">E. Prohibition Against Conditioning a Child's Participation on Collection of Personal Information (16 CFR 312.7)</HD>
                    <P>
                        Section 312.7 of the Rule provides that an operator is prohibited from conditioning a child's participation in a game, the offering of a prize, or another activity on the child's disclosing more 
                        <PRTPAGE P="2060"/>
                        personal information than is reasonably necessary to participate in such activity.
                    </P>
                    <P>The Commission notes that this provision serves as an outright prohibition on collecting more personal information than is reasonably necessary for a child to participate in a game, offering of a prize, or another activity. Therefore, operators may not collect more information than is reasonably necessary for such participation, even if the operator obtains consent for the collection of information that goes beyond what is reasonably necessary.</P>
                    <P>With respect to the scope of § 312.7, the Commission is considering adding new language to address the meaning of “activity,” as that term is used in § 312.7. Specifically, the Commission is considering including language in § 312.7 to provide that an “activity” means “any activity offered by a website or online service, whether that activity is a subset or component of the website or online service or is the entirety of the website or online service.” It welcomes comment on whether this language is consistent with the COPPA statute's text and purpose, and it also welcomes comment on whether this change is necessary given the breadth of the plain meaning of the term “activity.”</P>
                    <HD SOURCE="HD2">F. Confidentiality, Security, and Integrity of Personal Information Collected From Children (16 CFR 312.8)</HD>
                    <P>Section 312.8 of the Rule provides:</P>
                    <P>The operator must establish and maintain reasonable procedures to protect the confidentiality, security, and integrity of personal information from children. The operator must also take reasonable steps to release children's personal information only to service providers and third parties who are capable of maintaining the confidentiality, security, and integrity of such information, and who provide assurances that they will maintain the information in such a manner.</P>
                    <P>In the 2019 Rule Review Initiation, the Commission asked whether operators have implemented sufficient safeguards to protect the personal information they collect from children. The Commission also asked whether the requirements of § 312.8 are adequate and whether the Rule should include more specific data security requirements.</P>
                    <P>
                        Many commenters asked the Commission to clarify or strengthen operators' obligations under this section. For example, a coalition of consumer groups criticized the Commission for not promulgating clear data security regulations as directed by the COPPA statute.
                        <SU>307</SU>
                        <FTREF/>
                         These commenters recommended that the Commission elaborate on the meaning of “reasonable procedures to protect the confidentiality, security, and integrity” of children's information.
                        <SU>308</SU>
                        <FTREF/>
                         Similarly, an FTC-approved COPPA Safe Harbor program recommended that the Commission provide detailed guidance about minimum standards for what constitutes “reasonable procedures,” to help guide operators and FTC-approved COPPA Safe Harbor programs tasked with ensuring that companies are compliant with the Rule.
                        <SU>309</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>307</SU>
                             
                            <E T="03">See</E>
                             Joint Consumer Groups, at 54-56 (criticizing the Commission for neglecting to promulgate regulations that “require the operator of such a website or online service to establish and maintain reasonable procedures to protect the confidentiality, security, and integrity of personal information collected from children,” but only adding “small sections” about releasing data to third parties in § 312.8 and about data retention and deletion in § 312.10).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>308</SU>
                             
                            <E T="03">Id.</E>
                             at 56 (requesting the Commission, in particular, clarify operators' obligations to protect the “confidentiality” of children's personal information).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>309</SU>
                             CARU, at 10 (noting that, in its experience, companies make good-faith efforts to establish and maintain reasonable procedures but could use additional guidance about “minimum standards,” such as encryption).
                        </P>
                    </FTNT>
                    <P>
                        Some commenters argued that recent data breaches in all industries demonstrate the need for stricter data security requirements for children's personal information.
                        <SU>310</SU>
                        <FTREF/>
                         Other commenters expressed a more narrow concern that the evolving online landscape in schools, combined with an increase in data breaches and ransomware attacks, suggests the need for stricter data security requirements for children's personal information generally.
                        <SU>311</SU>
                        <FTREF/>
                         In contrast, a small number of commenters opined that operators are adequately protecting children's personal information. For example, the Internet Association stated that the increase in well-publicized breaches has heightened operators' awareness of their obligations and encouraged them to safeguard personal data.
                        <SU>312</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>310</SU>
                             
                            <E T="03">See e.g.,</E>
                             Consumer Reports, at 24 (listing examples of data breaches and suggesting that the Commission provide “sufficient enforcement” to incentivize companies to better steward children's personal information).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>311</SU>
                             Parent Coalition for Student Privacy, at 4 (recommending that the Commission strengthen the Rule's data security requirements generally, in light of the increase in data breaches of schools, school districts, and their vendors); 
                            <E T="03">see also</E>
                             CoSN, at 2, 4-5 (asking the Commission to strengthen the Rule's security requirements generally, considering the increase of cyberattacks on school districts and citing CoSN's 2019 leadership survey report identifying cybersecurity as the first priority for school system technology administrators).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>312</SU>
                             Internet Association, at 20 (“With the emergence of other privacy and security requirements and fall-out from well-publicized breaches, operators are increasingly aware of their obligations to safeguard personal data about users of any age by maintaining physical, technical, and administrative security procedures that are reasonable and appropriate in light of the nature of the data to be protected”) (footnote omitted). 
                            <E T="03">See also</E>
                             P. Aftab, at 10 (stating that the “over-arching principles” of COPPA's data security guidelines are “working well,” although they may require updating and closer examination).
                        </P>
                    </FTNT>
                    <P>
                        Commenters on both sides—those who believe operators are adequately protecting children's personal information and those who believe operators need to do more—recommended against adding prescriptive data security requirements or risk management controls in the Rule. These commenters expressed concern that such measures could become quickly outdated. For example, the Internet Association and The Toy Association expressed concerns that specific, detailed security requirements and risk management controls might prevent operators from keeping pace with evolving technology and security threats.
                        <SU>313</SU>
                        <FTREF/>
                         The internet Association opined that the Rule's flexibility permits operators to develop privacy and security risk management frameworks that are tailored to their activities and users, and that also keep pace with technology, evolving security threats, and varying security risks.
                        <SU>314</SU>
                        <FTREF/>
                         FTC-approved COPPA Safe Harbor program kidSAFE and a technology trade association recommended that the Commission keep the “broad and flexible” standard in § 312.8 for similar reasons.
                        <SU>315</SU>
                        <FTREF/>
                         A group of State Attorneys General also supported a flexible approach.
                        <SU>316</SU>
                        <FTREF/>
                         These commenters urged the Commission to proceed cautiously and make clear that any additional data security requirements within the Rule are simply illustrative examples of what constitutes “reasonable procedures” rather than an exhaustive list.
                        <SU>317</SU>
                        <FTREF/>
                         Such an approach, they argued, would encourage operators to consistently monitor and update security protocols that evolve with “rapid advances in technology and the enterprising nature of cybercriminals.” 
                        <SU>318</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>313</SU>
                             Internet Association, at 20; The Toy Association, at 22 (expressing concerns that specific data security requirements could become quickly outdated and might add costs to operators who must also comply with security requirements in other laws, such as the GDPR and State data security laws).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>314</SU>
                             Internet Association, at 20.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>315</SU>
                             kidSAFE, at 16; 
                            <E T="03">see also</E>
                             Consumer Technology Association, at 19 (opining that “[f]lexible, dynamic approaches to security are the best answer to solving the security challenges of both today and tomorrow”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>316</SU>
                             Joint Attorneys General, at 14-15.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>317</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>318</SU>
                             
                            <E T="03">Id.</E>
                             at 14.
                        </P>
                    </FTNT>
                    <P>
                        kidSAFE also encouraged the Commission to consider the varying 
                        <PRTPAGE P="2061"/>
                        levels of resources and bargaining power that different operators hold. kidSAFE claimed that smaller companies often lack the resources to invest in their own data security measures or the bargaining power to obtain security assurances from the third-party service providers they use.
                        <SU>319</SU>
                        <FTREF/>
                         An individual commenter expressed similar concerns that additional data security requirements might further burden small businesses, which already may not be in a position to determine whether service providers are capable of the Rule's existing security requirements.
                        <SU>320</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>319</SU>
                             kidSAFE, at 15 (opining that it believes operators are implementing sufficient security safeguards considering their varying sizes).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>320</SU>
                             K. O'Connell, at 2.
                        </P>
                    </FTNT>
                    <P>
                        In enacting COPPA, Congress recognized the need for heightened protections for children's personal information, and the Commission has long recognized a similar need.
                        <SU>321</SU>
                        <FTREF/>
                         The Commission agrees that the proliferation of data breaches in all industries, including schools, supports strong and effective data security requirements, especially for particularly sensitive information like children's data. The Commission also agrees that operators would benefit from additional clarity and detail regarding the Rule's security requirements set forth in § 312.8.
                    </P>
                    <FTNT>
                        <P>
                            <SU>321</SU>
                             
                            <E T="03">See, e.g.,</E>
                             then-FTC Chairman Robert Pitofsky, FTC Testimony before Senate Committee on Commerce, Science &amp; Transportation, U.S. Senate “Protection of Children's Privacy on the World Wide Web,” Sept. 23, 1998, at 4 (testifying in support of enacting COPPA and describing safety concerns that the disclosure of children's personal information may lead to, as pedophiles and other sexual predators use online services to identify and contact children), 
                            <E T="03">available at https://www.ftc.gov/public-statements/1998/09/prepared-statement-federal-trade-commission-protection-childrens-privacy; see also</E>
                             then-FTC Chairman Jon Leibowitz, “Updated FTC COPPA Rule,” Dec. 19, 2012, at 6 (explaining that while COPPA covers only “a small sliver of the internet” it is “an important sliver, a small, Congressionally-mandated oasis sheltering personal privacy, one in which websites must respect the privacy of the most vulnerable and precious among us”), 
                            <E T="03">available at https://www.ftc.gov/public-statements/2012/12/statement-ftc-chairman-jon-leibowitz-updated-coppa-rule-prepared-delivery.</E>
                        </P>
                    </FTNT>
                    <P>For these reasons, the Commission proposes modifications to the Rule's security requirements. Specifically, the Commission proposes to split the operator's requirements in § 312.8 into discrete paragraphs and provide further guidance as to steps operators can take to comply with each requirement. The second paragraph will provide more guidance on the “reasonable procedures” that an operator must establish and maintain under newly-numbered § 312.8(a) to protect the confidentiality, security, and integrity of personal information from children. The third paragraph will address the “reasonable steps” an operator should take to release children's personal information only to those capable of protecting such and who provide written assurances to protect the information.</P>
                    <P>
                        First, the Commission proposes modifying § 312.8 to specify that operators must, at minimum, establish, implement, and maintain a written comprehensive security program that contains safeguards that are appropriate to the sensitivity of children's information and to the operator's size, complexity, and nature and scope of activities. This requirement is modeled on the Commission's original Safeguards Rule implemented under the Gramm-Leach-Bliley Act (“GLBA”), which provides heightened protections for financial institutions' customer data.
                        <SU>322</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>322</SU>
                             Safeguards Rule, Final Rule, 67 FR 36484 (May 23, 2002), 
                            <E T="03">available at https://www.ftc.gov/sites/default/files/documents/federal_register_notices/standards-safeguarding-customer-information-16-cfr-part-314/020523standardsforsafeguardingcustomerinformation.pdf.</E>
                        </P>
                    </FTNT>
                    <P>To provide additional guidance, the proposed § 312.8 security program must contain a number of specific elements including designating an employee to coordinate the information security program; identifying and, at least annually, performing additional assessments to identify risks to the confidentiality, security, and integrity of personal information collected from children; designing, implementing, and maintaining safeguards to control any identified risks, as well as testing and monitoring the effectiveness of such safeguards; and, at least annually, evaluating and modifying the information security program.</P>
                    <P>
                        The Commission believes that these modifications are appropriate for several reasons. First, this approach provides additional guidance to operators and FTC-approved COPPA Safe Harbor programs, while also maintaining the Rule's flexibility by allowing for technological advancements and taking into account an operator's size, complexity, and the nature and scope of its activities. It is also consistent with prior Commission COPPA and data security decisions and guidance.
                        <SU>323</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>323</SU>
                             
                            <E T="03">See, e.g., In re Retina-X Studios, LLC,</E>
                             File No. 172 3118 (2020), 
                            <E T="03">available at https://www.ftc.gov/legal-library/browse/cases-proceedings/172-3118-retina-x-studios-llc-matter; United States</E>
                             vs. 
                            <E T="03">Unixiz, Inc., et al.,</E>
                             No. 5:19-cv-2222 (N.D. Cal. 2019), 
                            <E T="03">available at https://www.ftc.gov/legal-library/browse/cases-proceedings/172-3002-unixiz-inc-doing-business-i-dressupcom.</E>
                        </P>
                    </FTNT>
                    <P>
                        In addition to the proposed written data security program, the Commission also proposes adding language to § 312.8 to clarify that operators that release personal information to third parties or other operators must obtain written assurances that the recipients will employ reasonable measures to maintain the confidentiality, security, and integrity of the information. In 2013, when the Commission amended § 312.8 to require operators to “take reasonable steps to release children's personal information only to service providers and third parties who are capable of maintaining the confidentiality, security and integrity of such information, and who provide assurances that they will maintain the information in such a manner,” the Commission envisioned that operators would obtain assurances “by contract or otherwise.” 
                        <SU>324</SU>
                        <FTREF/>
                         The Commission based this requirement on a similar obligation of financial institutions under the GLBA, which requires entities to “requir[e] your service providers 
                        <E T="03">by contract</E>
                         to implement and maintain such safeguards” (emphasis added).
                        <SU>325</SU>
                        <FTREF/>
                         While the Commission expanded on the GLBA's provision to allow operators to obtain assurances by contract “or otherwise,” the Commission did not intend to allow operators to rely on verbal assurances alone. Rather, the Commission envisioned other written assurances for which there is tangible evidence, such as a written email or a service provider's written terms and conditions.
                    </P>
                    <FTNT>
                        <P>
                            <SU>324</SU>
                             78 FR 3972 at 3995.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>325</SU>
                             16 CFR 314.4(f)(2) (requiring financial institutions to obtain contracts with service providers to implement and maintain safeguards).
                        </P>
                    </FTNT>
                    <P>
                        Accordingly, the Commission proposes inserting “written” to clarify that the assurances operators must obtain from other operators, service providers, and third parties to whom the operator releases children's personal information, or who collect such on the operator's behalf, must be in writing. As similarly noted in the Rule review that led to the 2013 Amendments,
                        <SU>326</SU>
                        <FTREF/>
                         this provision is intended to address security issues surrounding business-to-business releases of data. The Commission did not seek specific comment on this aspect of the Rule's security requirements and therefore welcomes comment on this proposed modification.
                    </P>
                    <FTNT>
                        <P>
                            <SU>326</SU>
                             76 FR 59804 at 59821.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">G. Data Retention and Deletion Requirements (16 CFR 312.10)</HD>
                    <P>
                        Section 312.10 of the Rule currently states that “an operator of a website or online service shall retain personal information collected online from a child for only as long as is reasonably 
                        <PRTPAGE P="2062"/>
                        necessary to fulfill the purpose for which the information was collected.” This section further states that “the operator must delete such information using reasonable measures to protect against unauthorized access to, or use of, the information in connection with its deletion.”
                    </P>
                    <P>
                        In 2013, the Commission amended the Rule to add the data retention and deletion requirements of § 312.10 pursuant to its 15 U.S.C. 6502(b)(1)(D) authority to establish regulations requiring operators to establish and maintain reasonable procedures to protect the confidentiality, security, and integrity of personal information collected from children. At that time, the Commission explained that timely deletion of data is an integral part of a reasonable data security strategy, referencing the Institute for Public Representation's comment that without such “operators have no incentive to eliminate children's personal information and may retain it indefinitely.” 
                        <SU>327</SU>
                        <FTREF/>
                         The Commission, however, rejected requests to specify a finite timeframe in which companies must delete data, instead deciding to choose “the phrases `for only as long as is reasonably necessary' and `reasonable measures' to avoid the very rigidity about which commenters opposing this provision complain.” 
                        <SU>328</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>327</SU>
                             78 FR 3972 at 3995.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>328</SU>
                             78 FR 3972 at 3995, note 302 (rejecting the Institute for Public Representation's request to require companies to delete children's personal information within three months).
                        </P>
                    </FTNT>
                    <P>
                        Although the Commission did not specifically seek comment on data deletion in its 2019 Rule Review Initiation, many of the commenters that recommended the Commission provide more guidance on the § 312.8 requirements also suggested that the Commission clarify operators' obligations under § 312.10. These commenters expressed concern that, without specific time limits on data retention, operators could read the Rule to allow indefinite retention of children's personal information. For example, a group of State Attorneys General asked the Commission to modify the Rule to require operators or others maintaining children's data to serve contextual ads to delete such information immediately at the end of a user's session.
                        <SU>329</SU>
                        <FTREF/>
                         Many consumer groups and individual commenters also opined that an increase in school data breaches and ransomware attacks indicates a need for stronger data deletion requirements within the Rule generally.
                        <SU>330</SU>
                        <FTREF/>
                         A few commenters asked specifically for data retention limits for personal information stored within the education system or by ed tech providers.
                        <SU>331</SU>
                        <FTREF/>
                         Similarly, a non-profit privacy organization requested that the Commission make it clear that operators cannot retain student data indefinitely.
                        <SU>332</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>329</SU>
                             Joint Attorneys General, at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>330</SU>
                             Parent Coalition for Student Privacy, at 4 (recommending that the Commission incorporate stronger security standards in the Rule generally, considering the increase in data breaches of schools, school districts, and their vendors, including strengthening COPPA's requirements for data minimization and deletion); CoSN, at 4-5 (recommending that, in light of the growing number of cyberattacks on school districts, the Commission strengthen the Rule's security requirements generally and citing CoSN's 2019 leadership survey report identifying cybersecurity as the first priority for school system technology administrators, including “efforts to promote transparency, and strengthen data retention and deletion policies”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>331</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Illinois Families for Public Schools, at 2 (asking the Commission to have COPPA adopt Illinois' State law approach that retention of student data must be purpose driven and minimized); D. Derigiotis Burns Wilcox, at 2 (requesting the Commission adopt mandatory limits on the period for retaining personal information stored within the educational system and affiliated vendors).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>332</SU>
                             FPF, at 12.
                        </P>
                    </FTNT>
                    <P>Section 312.10 prohibits operators from retaining children's personal information indefinitely. The Commission framed the prohibition on data retention to permit enough flexibility to allow operators to retain data only for specified, necessary business needs.</P>
                    <P>
                        Given the misunderstanding identified by the consumer groups, the Commission now proposes to modify this section to state more explicitly operators' duties with regard to the retention of personal information collected from children. Specifically, the Commission proposes clarifying that operators may retain personal information for only as long as is reasonably necessary for the specific purpose for which it was collected, and not for any secondary purpose. For example, if an operator collects an email address from a child for account creation purposes, the operator could not then use that email address for marketing purposes without first obtaining verifiable parental consent to use that information for that specific purpose. Additionally, the operator must delete the information when such information is no longer reasonably necessary for the purpose for which it was collected.
                        <SU>333</SU>
                        <FTREF/>
                         In any event, personal information collected from a child may not be retained indefinitely.
                    </P>
                    <FTNT>
                        <P>
                            <SU>333</SU>
                             
                            <E T="03">See</E>
                             Compl., 
                            <E T="03">United States</E>
                             v. 
                            <E T="03">Amazon.com, Inc., et al.,</E>
                             Case No. 2:23-cv-00811 (W.D. Wash. May 31. 2023), 
                            <E T="03">available at https://www.ftc.gov/system/files/ftc_gov/pdf/Amazon-Complaint-%28Dkt.1%29.pdf</E>
                             (alleging that Amazon.com. Inc. and Amazon.com Services LLC violated § 312.10 by retaining children's personal information longer than was reasonably necessary to fulfill the purposes for collecting the information).
                        </P>
                    </FTNT>
                    <P>The Commission also proposes requiring an operator to, at least, establish and maintain a written data retention policy specifying its business need for retaining children's personal information and its timeframe for deleting it, precluding indefinite retention.</P>
                    <P>
                        These proposed modifications are intended to reinforce section 312.7's data minimization requirements, which prohibit an operator from conditioning a child's participation in a game, the offering of a prize, or another activity on the child's disclosing more personal information than is reasonably necessary to participate in such activity.
                        <SU>334</SU>
                        <FTREF/>
                         Namely, these proposed modifications require that an operator must have a specific business need for retaining information collected from children, and may retain such information for only so long as is reasonably necessary for the specific purpose for which it was collected, and not for any secondary purpose. The modifications also preclude operators from retaining such information indefinitely. The Commission welcomes comment on its proposed modification to this section.
                    </P>
                    <FTNT>
                        <P>
                            <SU>334</SU>
                             16 CFR 312.7.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">H. Safe Harbor (16 CFR 312.11)</HD>
                    <P>The 2019 Rule Review Initiation posed a number of questions related to the Rule's safe harbor program provision, including: whether it has been effective in enhancing compliance with the Rule; whether the Commission should modify the criteria currently enumerated in § 312.11(b) for approval of FTC-approved COPPA Safe Harbor programs; whether the Commission should clarify or modify § 312.11(g) with respect to the Commission's discretion to initiate an investigation or bring an enforcement action against an operator participating in an FTC-approved COPPA Safe Harbor program; whether the Commission should consider changes to the safe harbor monitoring process, including to promote greater transparency; and whether the Rule should include factors for the Commission to consider in revoking approval for an FTC-approved COPPA Safe Harbor program.</P>
                    <P>
                        A number of commenters expressed support for the Rule's safe harbor program.
                        <SU>335</SU>
                        <FTREF/>
                         At the same time, however, 
                        <PRTPAGE P="2063"/>
                        multiple commenters recommended that the Commission enhance oversight of, and transparency regarding, the safe harbor program by modifying the criteria for the Commission's approval of FTC-approved COPPA Safe Harbor programs' guidelines and the Rule's requirements for FTC-approved COPPA Safe Harbor programs to submit reports to the Commission and retain records.
                        <SU>336</SU>
                        <FTREF/>
                         While the Commission continues to believe that FTC-approved COPPA Safe Harbor programs serve an important function in helping companies comply with COPPA, it finds merit in the recommendations for enhanced oversight and transparency. Accordingly, the Commission proposes revisions to § 312.11 of the Rule as set forth in this part of the preamble, which it believes will further strengthen the COPPA Rule's safe harbor program.
                    </P>
                    <FTNT>
                        <P>
                            <SU>335</SU>
                             
                            <E T="03">See, e.g.,</E>
                             CARU, at 11; SuperAwesome, at 31; PRIVO, at 8; FOSI, at 6; CIPL, at 7. 
                            <E T="03">But see, e.g.,</E>
                             S. Egelman, at 4-5 (stating the belief that FTC-approved COPPA Safe Harbor programs certify 
                            <PRTPAGE/>
                            online services that do not comply with the Rule and that, if the COPPA statute permitted the Commission to do so, it would be better for the Commission to eliminate the safe harbor program); Joint Consumer Groups, at 15-20 (arguing that the safe harbor program does not effectively protect children's privacy because of online services' low participation rates, a lack of sufficiently strict requirements for approval of safe harbor programs, and a lack of safe harbor programs' enforcement of their guidelines).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>336</SU>
                             
                            <E T="03">See, e.g.,</E>
                             CARU, at 11; SuperAwesome, at 31; CIPL, at 7.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">1. Criteria for Approval of Self-Regulatory Program Guidelines (§ 312.11(b))</HD>
                    <P>Paragraph 312.11(b) of the Rule requires that FTC-approved COPPA Safe Harbor programs demonstrate that they meet certain performance standards, specifically: (1) requirements to ensure operators subject to the self-regulatory program guidelines (“subject operators”) provide substantially the same or greater protections for children as those contained in §§ 312.2 through 312.8 and 312.10; (2) an effective, mandatory mechanism for the independent assessment of subject operators' compliance with the FTC-approved COPPA Safe Harbor program's guidelines; and (3) disciplinary actions for subject operators' non-compliance with self-regulatory program guidelines.</P>
                    <P>
                        Several commenters recommended that the Commission provide additional clarity regarding the criteria the Commission applies when determining whether to approve an FTC-approved COPPA Safe Harbor program's self-regulatory guidelines. One FTC-approved COPPA Safe Harbor program suggested that the Commission consider publishing a standard set of program requirements, assessment questionnaires, and technical tests for all FTC-approved COPPA Safe Harbor programs to utilize with their subject operators.
                        <SU>337</SU>
                        <FTREF/>
                         Another recommended that the FTC consider enumerating minimum operating standards for FTC-approved COPPA Safe Harbor programs, including how often they monitor subject operators' sites and communicate with subject operators.
                        <SU>338</SU>
                        <FTREF/>
                         Another commenter recommended that the Commission should require FTC-approved COPPA Safe Harbor programs to apply a duty of care to promote principles behind COPPA when they conduct safe harbor program audits and certifications.
                        <SU>339</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>337</SU>
                             TRUSTe, at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>338</SU>
                             CARU, at 11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>339</SU>
                             SuperAwesome, at 31.
                        </P>
                    </FTNT>
                    <P>
                        The Commission finds merit in the overall call for additional clarity regarding its criteria for approving FTC-approved COPPA Safe Harbor programs' self-regulatory guidelines. As discussed previously, the Commission proposes changes to the Rule's security requirements.
                        <SU>340</SU>
                        <FTREF/>
                         These proposed modifications provide additional guidance on the “reasonable procedures” that an operator must establish and maintain to protect the confidentiality, security, and integrity of personal information from children. FTC-approved COPPA Safe Harbor programs can utilize that guidance in determining whether subject operators meet the Rule's § 312.8 requirements.
                    </P>
                    <FTNT>
                        <P>
                            <SU>340</SU>
                             
                            <E T="03">See</E>
                             Part IV.F.
                        </P>
                    </FTNT>
                    <P>
                        Further, in parallel with the proposed changes to § 312.8 discussed in Part IV.F., the Commission proposes to revise § 312.11(b)(2) to state explicitly that an FTC-approved COPPA Safe Harbor program's assessments of subject operators must include comprehensive reviews of both the subject operators' 
                        <E T="03">privacy and security</E>
                         policies, practices, and representations. The Commission does not propose any revisions to § 312.11(b)(1).
                    </P>
                    <HD SOURCE="HD3">2. Reporting and Recordkeeping Requirements (§ 312.11(d) and § 312.11(f))</HD>
                    <P>Section 312.11(d) of the Rule sets forth requirements for FTC-approved COPPA Safe Harbor programs to, among other things, submit annual reports to the Commission and maintain for not less than three years, and make available to the Commission upon request, consumer complaints alleging that subject operators violated an FTC-approved COPPA Safe Harbor program's guidelines, records of disciplinary actions taken against subject operators, and results of the FTC-approved COPPA Safe Harbor program's § 312.11(b)(2) assessments.</P>
                    <P>
                        Several commenters recommended that the Commission modify the reporting and recordkeeping requirements in order to strengthen the Commission's oversight of FTC-approved COPPA Safe Harbor programs and to make that oversight more transparent. One commenter recommended that the Commission require FTC-approved COPPA Safe Harbor programs to submit more detailed and frequent reports.
                        <SU>341</SU>
                        <FTREF/>
                         Another suggested that the Rule should require such programs to demonstrate on a periodic basis that they are regularly assessing and updating their programs to comply with COPPA.
                        <SU>342</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>341</SU>
                             SuperAwesome, at 31.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>342</SU>
                             CIPL, at 7.
                        </P>
                    </FTNT>
                    <P>The Commission agrees with commenters' general recommendation to enhance FTC-approved COPPA Safe Harbor programs' reporting requirements in order to strengthen oversight. Accordingly, the Commission proposes revising § 312.11(d)(1) to require the following additions to the FTC-approved COPPA Safe Harbor programs' annual reports.</P>
                    <P>
                        First, the Commission proposes requiring FTC-approved COPPA Safe Harbor programs to identify each subject operator and all approved websites or online services in the program, as well as all subject operators that have left the program.
                        <SU>343</SU>
                        <FTREF/>
                         The proposed revision further requires an FTC-approved COPPA Safe Harbor program to provide: a narrative description of the program's business model, including whether it provides additional services to subject operators, such as training; copies of each consumer complaint related to each subject operator's violation of an FTC-approved COPPA Safe Harbor program's guidelines; and a description of the process for determining whether a subject operator is subject to discipline (in addition to the existing requirement to describe any disciplinary action that the FTC-approved COPPA Safe Harbor program took against any 
                        <PRTPAGE P="2064"/>
                        subject operator). These proposed changes will enhance the Commission's ability to oversee FTC-approved COPPA Safe Harbor programs.
                    </P>
                    <FTNT>
                        <P>
                            <SU>343</SU>
                             This requirement will additionally allow the Commission to monitor whether subject operators are switching FTC-approved COPPA Safe Harbor programs for forum shopping purposes as one commenter noted. 
                            <E T="03">See</E>
                             Representative Kathy Castor, at 2. This concern was also raised during the COPPA Workshop, in which an employee of an FTC-approved COPPA Safe Harbor program noted that “one of the issues that we have with safe harbor right now is the shopping around . . . we've lost a few, actually, where we've refused to allow standards that we don't think are meeting the requirements of COPPA and our program and they've gone elsewhere.” 
                            <E T="03">See</E>
                             C. Quinn, Remarks from the 
                            <E T="03">State of the World in Children's Privacy Panel</E>
                             at 
                            <E T="03">The Future of the COPPA Rule: An FTC Workshop</E>
                             37-38 (Oct. 7, 2019), 
                            <E T="03">available at https://www.ftc.gov/system/files/documents/public_events/1535372/transcript_of_coppa_workshop_part_1_1.pdf.</E>
                        </P>
                    </FTNT>
                    <P>
                        Additionally, one FTC-approved COPPA Safe Harbor program recommended that the Commission consider conducting audits of each FTC-approved COPPA Safe Harbor program and publishing an audit checklist after completing each audit.
                        <SU>344</SU>
                        <FTREF/>
                         Relatedly, another commenter suggested that the Rule should require FTC-approved COPPA Safe Harbor programs to demonstrate on a periodic basis that they are regularly assessing and updating their programs to comply with COPPA.
                        <SU>345</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>344</SU>
                             ESRB, at 5. This commenter suggested biennial audits, however on balance, the Commission believes that conducting such reviews every three years is appropriate.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>345</SU>
                             CIPL, at 7.
                        </P>
                    </FTNT>
                    <P>
                        The Commission agrees that, in addition to its current oversight of FTC-approved COPPA Safe Harbor programs, including review of the FTC-approved COPPA Safe Harbor programs' annual reports discussed in this part of the preamble, regular audits of FTC-approved COPPA Safe Harbor programs' technological capabilities and mechanisms for assessing subject operators' fitness for maintaining membership could further strengthen oversight. To that end, the Commission proposes to add a new § 312.11(f) requiring FTC-approved COPPA Safe Harbor programs to submit triennial reports that provide details about those issues.
                        <SU>346</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>346</SU>
                             Because the Commission proposes to add a new § 312.11(f), the Commission also proposes to renumber existing §§ 312.11(f) and 312.11(g) as 312.11(g) and 312.11(h), respectively.
                        </P>
                    </FTNT>
                    <P>
                        In terms of transparency, several commenters recommended that the Commission require programs to publish lists of their certified members.
                        <SU>347</SU>
                        <FTREF/>
                         One FTC-approved COPPA Safe Harbor program, however, posited that public disclosure of membership lists would lead to the “poaching” of safe harbor members and recommended that the Rule require safe harbors instead to provide service-level certification information to the FTC confidentially.
                        <SU>348</SU>
                        <FTREF/>
                         Another disagreed that public disclosure of membership lists would lead to the stealing of members, stating that it has always publicly disclosed the products it has certified.
                        <SU>349</SU>
                        <FTREF/>
                         A coalition of consumer groups supported greater transparency and argued that FTC-approved COPPA Safe Harbor programs' current practices with respect to whether and where subject operators display membership seals makes it difficult for parents and others to determine whether websites or online services are participants of an FTC-approved COPPA Safe Harbor program.
                        <SU>350</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>347</SU>
                             SuperAwesome, at 31; S. Egelman, at 5; kidSAFE, at 17.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>348</SU>
                             ESRB, at 5 (also asserting that there is a lack of evidence showing that consumers want access to such lists).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>349</SU>
                             kidSAFE, at 17.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>350</SU>
                             Joint Consumer Groups, at 19-20.
                        </P>
                    </FTNT>
                    <P>The Commission proposes requiring that FTC-approved COPPA Safe Harbor programs publish lists of their subject operators. While the Commission understands certain commenters' concerns that the publication of such a list could result in the loss of subject operators to other FTC-approved COPPA Safe Harbor programs, the Commission believes that such concerns are outweighed by the benefits created by increasing transparency around FTC-approved COPPA Safe Harbor programs. Therefore, the Commission proposes adding this requirement as new paragraph § 312.11(d)(4).</P>
                    <HD SOURCE="HD3">3. Revocation of Approval of Self-Regulatory Program Guidelines (Current § 312.11(f), Proposed To Be Renumbered as § 312.11(g))</HD>
                    <P>Current § 312.11(f), which the Commission proposes to renumber as § 312.11(g) in light of the new proposed § 312.11(f), reserves the Commission's right to revoke the approval of any FTC-approved COPPA Safe Harbor program whose guidelines or implementation of guidelines do not meet the requirements set forth in the Rule. In addition, current § 312.11(f) requires FTC-approved COPPA Safe Harbor programs that the Commission had approved before the Commission amended the Rule in 2013 to submit by March 1, 2013 proposed modifications to bring their guidelines into compliance with the 2013 Rule amendments.</P>
                    <P>Because the March 1, 2013 deadline has passed and is no longer relevant, the Commission proposes to strike from renumbered § 312.11(g) the requirement that FTC-approved COPPA Safe Harbor programs submit proposed modifications to their guidelines. If the Commission proceeds to modify the Rule as discussed in this notice, the Commission will provide an appropriate deadline for safe harbor programs to submit proposed modifications to bring their guidelines into compliance with such amendments.</P>
                    <HD SOURCE="HD2">I. Voluntary Commission Approval Processes (16 CFR 312.12)</HD>
                    <P>
                        The Commission also proposes making a few technical edits in § 312.12(b) to ensure that each reference to the support for the internal operations of the website or online service is consistent with the COPPA statute's use of the phrase “support for the internal operations of the [website] or online service.” 
                        <SU>351</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>351</SU>
                             15 U.S.C. 6501(4).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">V. Request for Comment</HD>
                    <P>
                        You can file a comment online or on paper. For the Commission to consider your comment, we must receive it on or before March 11, 2024. Write “COPPA Rule Review, Project No. P195404” on your comment. Your comment—including your name and your State—will be placed on the public record of this proceeding, including the 
                        <E T="03">https://www.regulations.gov</E>
                         website.
                    </P>
                    <P>
                        Postal mail addressed to the Commission is subject to delay due to heightened security screening. As a result, we encourage you to submit your comments online. To make sure that the Commission considers your online comment, you must file it at 
                        <E T="03">https://www.regulations.gov,</E>
                         by following the instructions on the web-based form.
                    </P>
                    <P>If you file your comment on paper, write “COPPA Rule Review, Project No. P195404” on your comment and on the envelope, and mail your comment to the following address: Federal Trade Commission, Office of the Secretary, 600 Pennsylvania Avenue NW, Suite CC-5610 (Annex E), Washington, DC 20580. If possible, please submit your paper comment to the Commission by overnight service.</P>
                    <P>
                        Because your comment will be placed on the publicly accessible website at 
                        <E T="03">https://www.regulations.gov,</E>
                         you are solely responsible for making sure that your comment does not include any sensitive or confidential information. In particular, your comment should not include any sensitive personal information, such as your or anyone else's Social Security number; date of birth; driver's license number or other State identification number, or foreign country equivalent; passport number; financial account number; or credit or debit card number. You are also solely responsible for making sure that your comment does not include any sensitive health information, such as medical records or other individually identifiable health information. In addition, your comment should not include any “trade secret or any commercial or financial information which . . . is privileged or confidential”—as provided by section 6(f) of the FTC Act, 15 U.S.C. 46(f), and FTC Rule 4.10(a)(2), 16 CFR 4.10(a)(2)—including in particular competitively sensitive information such as costs, 
                        <PRTPAGE P="2065"/>
                        sales statistics, inventories, formulas, patterns, devices, manufacturing processes, or customer names.
                    </P>
                    <P>
                        Comments containing material for which confidential treatment is requested must be filed in paper form, must be clearly labeled “Confidential,” and must comply with FTC Rule 4.9(c). In particular, the written request for confidential treatment that accompanies the comment must include the factual and legal basis for the request, and must identify the specific portions of the comment to be withheld from the public record. 
                        <E T="03">See</E>
                         FTC Rule 4.9(c). Your comment will be kept confidential only if the General Counsel grants your request in accordance with the law and the public interest. Once your comment has been posted publicly at 
                        <E T="03">https://www.regulations.gov</E>
                        —as legally required by FTC Rule 4.9(b)—we cannot redact or remove your comment, unless you submit a confidentiality request that meets the requirements for such treatment under FTC Rule 4.9(c), and the General Counsel grants that request.
                    </P>
                    <P>
                        Visit the FTC website to read this publication and the news release describing it, and visit 
                        <E T="03">https://www.regulations.gov/docket/FTC-2023-0076</E>
                         to read a plain-language summary of the proposed Rule. The FTC Act and other laws that the Commission administers permit the collection of public comments to consider and use in this proceeding as appropriate. The Commission will consider all timely and responsive public comments that it receives on or before March 11, 2024. For information on the Commission's privacy policy, including routine uses permitted by the Privacy Act, see 
                        <E T="03">https://www.ftc.gov/site-information/privacy-policy.</E>
                    </P>
                    <HD SOURCE="HD1">VI. Paperwork Reduction Act</HD>
                    <P>
                        The Paperwork Reduction Act (“PRA”), 44 U.S.C. chapter 35, requires federal agencies to seek and obtain approval from the Office of Management and Budget (“OMB”) before undertaking a collection of information directed to ten or more persons.
                        <SU>352</SU>
                        <FTREF/>
                         Under the PRA, a rule creates a “collection of information” when ten or more persons are asked to report, provide, disclose, or record information in response to “identical questions.” 
                        <SU>353</SU>
                        <FTREF/>
                         The existing COPPA Rule contains recordkeeping, disclosure, and reporting requirements that constitute “information collection requirements” as defined by 5 CFR 1320.3(c) under the OMB regulations that implement the PRA. OMB has approved the Rule's existing information collection requirements through March 31, 2025 (OMB Control No. 3084-0117).
                    </P>
                    <FTNT>
                        <P>
                            <SU>352</SU>
                             44 U.S.C. 3502(3)(A)(i).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>353</SU>
                             
                            <E T="03">See</E>
                             44 U.S.C. 3502(3)(A).
                        </P>
                    </FTNT>
                    <P>The proposed amendments to the COPPA Rule would amend the definition of “website or online service directed to children,” potentially increasing the number of operators subject to the Rule, albeit likely not to a significant degree. The proposed Rule would also increase disclosure obligations for operators and FTC-approved COPPA Safe Harbor programs, and FTC-approved COPPA Safe Harbor programs would also face additional reporting obligations under the proposed Rule. Commission staff does not believe that the proposed Rule would increase operators' recordkeeping obligations.</P>
                    <P>
                        The Commission invites comments on: (1) whether the proposed collection of information is necessary for the proper performance of the functions of the FTC, including whether the information will have practical utility; (2) the accuracy of the FTC's estimate of the burden of the proposed collection of information; (3) ways to enhance the quality, utility, and clarity of the information to be collected; and (4) ways to minimize the burden of collecting information on those who respond. Written comments and recommendations for the proposed information collection should also be sent within 30 days of publication of this document 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 
                        <E T="03">reginfo.gov</E>
                         web link is a United States Government website produced by OMB and the General Services Administration. Under PRA requirements, OMB's Office of Information and Regulatory Affairs reviews federal information collections.
                    </P>
                    <HD SOURCE="HD2">Estimated Additional Annual Hours Burden</HD>
                    <HD SOURCE="HD2">A. Number of Respondents</HD>
                    <P>
                        As noted in the Regulatory Flexibility section of this NPRM, Commission staff estimates that there are currently approximately 5,710 operators subject to the Rule. Commission staff believes that the changes that are most likely to affect the number of operators subject to the Rule are the Commission's proposed changes to the Rule's definition of “website or online service directed to children.” Of most relevance to this discussion, the Commission proposes to modify paragraph 2 of this definition to account for third parties with actual knowledge that they collect children's information from users of a child-directed site or service, even if such third parties do not collect the information 
                        <E T="03">directly</E>
                         from such users. While Commission staff contemplates that this modification could increase the number of operators subject to the Rule's requirements, staff does not have sufficient evidence to estimate the amount of increase, and therefore the Commission welcomes comment on this issue. Commission staff does not expect that the other proposed modifications to this definition, such as the additional exemplar factors the Commission will consider in determining whether a site or service is child-directed, will alter the number of operators subject to the Rule.
                    </P>
                    <P>Commission staff does not believe that other proposed modifications to the Rule's definitions will affect the number of operators subject to the Rule. For example, Commission staff does not expect that the Commission's proposed addition of “biometric identifiers” to the Rule's definition of “personal information” will significantly alter the number of operators subject to the Rule. Commission staff believes that all or nearly all operators of websites or online services that collect “biometric identifiers” from children are already subject to the Rule.</P>
                    <P>In total, to the extent that any of the Commission's proposed revisions to the Rule's definitions might result in minor additional numbers of operators being subject to the Rule, Commission staff believes that any such increase will be offset by other operators of websites or online services adjusting their information collection practices so that they will not be subject to the Rule.</P>
                    <P>
                        For this burden analysis, Commission staff retains its recently published estimate of 280 new operators per year.
                        <SU>354</SU>
                        <FTREF/>
                         Commission staff also retains its estimate that no more than one additional FTC-approved COPPA Safe Harbor program applicant is likely to submit a request within the next three years of PRA clearance.
                    </P>
                    <FTNT>
                        <P>
                            <SU>354</SU>
                             
                            <E T="03">See</E>
                             2022 COPPA PRA Supporting Statement, available at 
                            <E T="03">https://omb.report/icr/202112-3084-002/doc/119087900</E>
                             (hereinafter, “2022 COPPA PRA Supporting Statement”).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">B. Recordkeeping Hours</HD>
                    <P>
                        While the proposed Rule requires operators to establish, implement, and maintain a written comprehensive security program and data retention policy, such requirements do not constitute a “collection of information” under the PRA. Namely, under the proposed Rule, each operator's security 
                        <PRTPAGE P="2066"/>
                        program and the safeguards instituted under such program will vary according to the operator's size and complexity, the nature and scope of its activities, and the sensitivity of the information involved. Similarly, the instituted data retention policy will differ depending on the operator's business practices. Thus, although each operator must summarize its compliance efforts in one or more written documents, the discretionary balancing of factors and circumstances that the proposed Rule allows does not require entities to answer “identical questions” and therefore does not trigger the PRA's requirements.
                    </P>
                    <P>
                        Separately, the proposed Rule imposes minimal recordkeeping requirements for FTC-approved COPPA Safe Harbor programs. However, FTC staff understands that most of the records listed in the COPPA Rule's safe harbor recordkeeping provisions consist of documentation that covered entities retain in the ordinary course of business irrespective of the COPPA Rule. OMB excludes from the definition of PRA burden, among other things, recordkeeping requirements that customarily would be undertaken independently in the normal course of business.
                        <SU>355</SU>
                        <FTREF/>
                         In staff's view, any incremental burden posed by the proposed Rule—such as that to include additional content in annual reports, submit a report to the Commission every three years detailing technological capabilities and mechanisms, and publicly post membership lists—would be marginal.
                    </P>
                    <FTNT>
                        <P>
                            <SU>355</SU>
                             
                            <E T="03">See</E>
                             5 CFR 1320.3(b)(2).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">C. Disclosure Hours</HD>
                    <HD SOURCE="HD3">1. New Operators' Disclosure Burden</HD>
                    <P>
                        FTC staff estimates that the Rule affects approximately 280 new operators per year.
                        <SU>356</SU>
                        <FTREF/>
                         Staff maintains its longstanding estimate that new operators of websites and online services will require, on average, approximately 60 hours to draft a privacy policy, design mechanisms to provide the required online privacy notice and, where applicable, the direct notice to parents.
                        <SU>357</SU>
                        <FTREF/>
                         In addition, the proposed Rule includes a new requirement that operators establish, implement, maintain, and disclose a data retention policy. Staff estimates it will require, on average, approximately 10 hours to meet the data retention policy requirement. In combining these figures, Commission staff estimates that these disclosure requirements will require 70 hours of burden per operator. This yields an estimated annual hours burden of 19,600 hours (280 respondents × 70 hours).
                    </P>
                    <FTNT>
                        <P>
                            <SU>356</SU>
                             This consists of certain traditional website operators, mobile app developers, plug-in developers, and advertising networks.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>357</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Children's Online Privacy Protection Rule, Notice, 86 FR 55609 (Oct. 6, 2021), available at 
                            <E T="03">https://www.govinfo.gov/content/pkg/FR-2021-10-06/pdf/2021-21753.pdf;</E>
                             2022 COPPA PRA Supporting Statement.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2. Existing Operators' Disclosure Burden</HD>
                    <P>The proposed Rule imposes various new disclosure requirements on operators. Specifically, the proposed amendments require operators to update existing disclosures, namely to update the direct and online notices with additional information about the operators' information practices. Additionally, some operators may have to provide disclosures that were not previously required under the Rule. For operators utilizing the support for the internal operations exception, 16 CFR 312.5(c)(7), the proposed Rule will now require such operators to provide an online notice. Similarly, the proposed Rule will require operators utilizing the proposed school authorization exception, which is newly numbered as 16 CFR 312.5(c)(10), to provide an online notice, a direct notice to the school, and enter into a written agreement with the school. Additionally, the proposed Rule requires operators to disclose a data retention policy.</P>
                    <P>
                        Commission staff believes that an existing operator's time to make these changes to its online and direct notices would be no more than that estimated for a new entrant to craft an online notice and direct notice for the first time, 
                        <E T="03">i.e.,</E>
                         60 hours. Regarding the written agreement, FTC staff understands that many ed tech operators enter into standard contracts with schools, school districts, and other education organizations across the country, and this requirement is not intended to interfere with such contractual arrangements. Therefore, this agreement likely consists of documentation that covered entities retain in the ordinary course of business irrespective of the COPPA Rule. As noted above, OMB excludes from the definition of PRA burden, among other things, recordkeeping requirements that customarily would be undertaken independently in the normal course of business.
                        <SU>358</SU>
                        <FTREF/>
                         Additionally, as discussed previously, Commission staff believes the time necessary to develop, draft, and publish a data retention policy is approximately 10 hours. Therefore, these disclosure requirements will amount to approximately 70 hours of burden. Annualized over three years of PRA clearance, this amounts to approximately 23 hours (70 hours ÷ 3 years) per operator each year. Aggregated for the 5,710 existing operators, the annualized disclosure burden for these requirements would be approximately 131,330 hours per year (5,710 respondents × 23 hours).
                    </P>
                    <FTNT>
                        <P>
                            <SU>358</SU>
                             
                            <E T="03">See</E>
                             5 CFR 1320.3(b)(2).
                        </P>
                    </FTNT>
                    <P>The proposed Rule will also require each FTC-approved COPPA Safe Harbor program to provide a list of all current subject operators on each of the FTC-approved COPPA Safe Harbor program's websites and online services, and the proposed Rule further requires that such list be updated every six months thereafter. Because FTC-approved COPPA Safe Harbor programs likely already keep up-to-date lists of their subject operators, Commission staff does not anticipate this requirement will significantly burden FTC-approved COPPA Safe Harbor programs. To account for time necessary to prepare the list for publication and to ensure that the list is updated every 6 months, Commission staff estimates 10 hours per year. Aggregated for one new FTC-approved COPPA Safe Harbor program and six existing FTC-approved COPPA Safe Harbor programs, this amounts to an estimated cumulative disclosure burden of 70 hours per year (7 respondents × 10 hours).</P>
                    <HD SOURCE="HD2">D. Reporting Hours</HD>
                    <P>The proposed amendments will require FTC-approved COPPA Safe Harbor programs to include additional content in their annual reports. The proposed amendments will also require each FTC-approved COPPA Safe Harbor program to submit a report to the Commission every three years detailing the program's technological capabilities and mechanisms for assessing subject operators' fitness for membership in the program.</P>
                    <P>The burden of conducting subject operator audits and preparing the annual reports likely varies by FTC-approved COPPA Safe Harbor program, depending on the number of subject operators. Commission staff estimates that the additional reporting requirements for the annual report will require approximately 50 hours per program per year. Aggregated for one new FTC-approved COPPA Safe Harbor program (50 hours) and six existing (300 hours) FTC-approved COPPA Safe Harbor programs, this amounts to an estimated cumulative reporting burden of 350 hours per year (7 respondents × 50 hours).</P>
                    <P>
                        Regarding the reports that the proposed Rule will require FTC-approved Safe Harbor programs to 
                        <PRTPAGE P="2067"/>
                        submit to the Commission every three years, § 312.11(c)(1) of the Rule already requires FTC-approved COPPA Safe Harbor programs to include similar information in their initial application to the Commission. Specifically, § 312.11(c)(1) requires that the application address FTC-approved COPPA Safe Harbor programs' business models and the technological capabilities and mechanisms they will use for initial and continuing assessment of operators' fitness for membership in their programs. Consequently, the three-year reports should merely require reviewing and potentially updating an already-existing report. Staff estimates that reviewing and updating existing information to comply with proposed § 312.11(f) will require approximately 10 hours per FTC-approved COPPA Safe Harbor program. Divided over the three-year period, FTC staff estimates that annualized burden attributable to this requirement would be approximately 3.33 hours per year (10 hours ÷ 3 years) per FTC-approved COPPA Safe Harbor program, which staff will round up to 4 hours per year per FTC-approved COPPA Safe Harbor program. Given that several FTC-approved COPPA Safe Harbor programs are already available to website and online service operators, FTC staff anticipates that no more than one additional FTC-approved COPPA Safe Harbor program applicant is likely to submit a request within the next three years of PRA clearance. Aggregated for one new FTC-approved COPPA Safe Harbor program and six existing FTC-approved COPPA Safe Harbor programs, this amounts to an estimated cumulative reporting burden of 28 hours per year (7 respondents × 4 hours).
                    </P>
                    <HD SOURCE="HD2">E. Labor Costs</HD>
                    <HD SOURCE="HD3">1. Disclosure</HD>
                    <HD SOURCE="HD3">a. New Operators</HD>
                    <P>
                        As previously noted, Commission staff estimates a total annual burden of 19,600 hours (280 respondents × 70 hours). Consistent with its past estimates and based on its 2013 rulemaking record,
                        <SU>359</SU>
                        <FTREF/>
                         FTC staff estimates that the time spent on compliance for new operators covered by the COPPA Rule would be apportioned five to one between legal (outside counsel lawyers or similar professionals) and technical (
                        <E T="03">e.g.,</E>
                         computer programmers, software developers, and information security analysts) personnel. Therefore, Commission staff estimates that approximately 16,333 of the estimated 19,600 hours required will be completed by legal staff.
                    </P>
                    <FTNT>
                        <P>
                            <SU>359</SU>
                             
                            <E T="03">See, e.g.,</E>
                             78 FR 3972 at 4007; 2022 COPPA PRA Supporting Statement.
                        </P>
                    </FTNT>
                    <P>
                        Regarding legal personnel, Commission staff anticipates that the workload among law firm partners and associates for assisting with COPPA compliance would be distributed among attorneys at varying levels of seniority. Assuming two-thirds of such work is done by junior associates at a rate of approximately $300 per hour, and one-third by senior partners at approximately $600 per hour, the weighted average of outside counsel costs would be approximately $400 per hour.
                        <SU>360</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>360</SU>
                             These estimates are drawn from the “Laffey Matrix.” The Laffey Matrix is a fee schedule used by many United States courts for determining the reasonable hourly rates in the District of Columbia for attorneys' fee awards under federal fee-shifting statutes. It is used here as a proxy for market rates for litigation counsel in the Washington, DC area. For 2020-2021, rates in the table range from $333 per hour for most junior associates to $665 per hour for the most senior partners. 
                            <E T="03">See</E>
                             Laffey Matrix, Civil Division of the United States Attorney's Office for the District of Columbia, United States Attorney's Office, District of Columbia, Laffey Matrix B 2015-2021, 
                            <E T="03">available at https://www.justice.gov/usao-dc/page/file/1305941/download.</E>
                        </P>
                    </FTNT>
                    <P>
                        FTC staff anticipates that computer programmers responsible for posting privacy policies and implementing direct notices and parental consent mechanisms would account for the remaining approximately 3,267 hours. FTC staff estimates an hourly wage of $57 (rounded to the nearest dollar) for technical assistance, based on Bureau of Labor Statistics (“BLS”) data.
                        <SU>361</SU>
                        <FTREF/>
                         Accordingly, associated annual labor costs would be $6,719,419 [(16,333 hours × $400/hour) + (3,267 hours × $57/hour)] for the estimated 280 new operators.
                    </P>
                    <FTNT>
                        <P>
                            <SU>361</SU>
                             The estimated mean hourly wage for technical labor support ($57) is based on an average of the mean hourly wage for computer programmers, software developers, and information security analysts as reported by the Bureau of Labor Statistics. 
                            <E T="03">See Occupational Employment and Wages—May 2022,</E>
                             Table 1 (National employment and wage data from the Occupational Employment and Wage Statistics survey by occupation, May 2022), 
                            <E T="03">available at https://www.bls.gov/news.release/ocwage.t01.htm</E>
                             (hereinafter, “BLS Table 1”).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Existing Operators</HD>
                    <P>As previously discussed, Commission staff estimates that the annualized disclosure burden for these requirements for the 5,710 existing operators would be 131,330 hours per year. Thus, apportioned five to one, this amounts to 109,442 hours of legal and 21,888 hours of technical assistance. Applying hourly rates of $400 and $57, respectively, for these personnel categories, associated labor costs would total approximately $45,024,416 ($43,776,800 + $1,247,616).</P>
                    <P>As noted, Commission staff estimates a cumulative disclosure burden of 10 hours per year for FTC-approved COPPA Safe Harbor programs. Aggregated for one new FTC-approved COPPA Safe Harbor program and six existing FTC-approved COPPA Safe Harbor programs, this amounts to an estimated cumulative reporting burden of 70 hours per year (7 respondents × 10 hours).</P>
                    <P>
                        Industry sources have advised that the labor to comply with requirements from FTC-approved COPPA Safe Harbor programs would be attributable to the efforts of in-house lawyers. To determine in-house legal costs, FTC staff applied an approximate average between the BLS reported mean hourly wage for lawyers ($78.74),
                        <SU>362</SU>
                        <FTREF/>
                         and estimated in-house hourly attorney rates ($300) that are likely to reflect the costs associated with the proposed Rule's safe harbor requirements. This yields an approximate hourly rate of $190. Applying this hourly labor cost estimate to the hours burden associated with the cumulative disclosure burden for FTC-approved COPPA Safe Harbor programs yields an estimated annual burden of $13,300 (70 hours × $190).
                    </P>
                    <FTNT>
                        <P>
                            <SU>362</SU>
                             
                            <E T="03">See</E>
                             BLS Table 1 (lawyers).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2. Reporting</HD>
                    <P>As previously noted, Commission staff estimates an estimated cumulative reporting burden of 378 hours per year for FTC-approved COPPA Safe Harbor programs. The approximate hourly rate for labor to comply with requirements from FTC-approved COPPA Safe Harbor programs is $190, as previously calculated. Applying this hourly labor cost estimate to the hours burden associated with the cumulative reporting burden for FTC-approved COPPA Safe Harbor programs yields an estimated annual labor cost burden of $71,820 (378 hours × $190).</P>
                    <HD SOURCE="HD2">F. Non-Labor/Capital Costs</HD>
                    <P>Because both operators and FTC-approved COPPA Safe Harbor programs will already be equipped with the computer equipment and software necessary to comply with the Rule's notice requirements, the proposed Rule should not impose any additional capital or other non-labor costs.</P>
                    <HD SOURCE="HD1">VII. Regulatory Flexibility Act</HD>
                    <P>
                        The Regulatory Flexibility Act (“RFA”), as amended by the Small Business Regulatory Enforcement Fairness Act of 1996, requires an agency to either provide an Initial Regulatory 
                        <PRTPAGE P="2068"/>
                        Flexibility Analysis (“IRFA”) with a proposed rule, or certify that the proposed Rule will not have a significant impact on a substantial number of small entities.
                        <SU>363</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>363</SU>
                             5 U.S.C. 603-605.
                        </P>
                    </FTNT>
                    <P>The Commission does not expect that the proposed Rule, if adopted, would have a significant impact on a substantial number of small entities. Among other things, as discussed further below, many of the proposed amendments reflect modest changes to the Rule, including to clarify definitions, increase content requirements for existing notices, increase specificity for existing security requirements, increase clarity on existing retention and deletion requirements, and increase specificity on certain reporting requirements. While the proposed amendments may require some entities to implement notices they were not required to provide before, obtain consent they previously were not required to obtain, and implement new retention policies, the Commission does not anticipate this will require significant additional costs to entities covered by the Rule. Instead, some of the proposed amendments, such as amendments to create exceptions for the Rule's verifiable parental consent requirements, may even reduce costs for many entities covered by the Rule.</P>
                    <P>Although the Commission certifies under the RFA that the proposed rule will not have a significant impact on a substantial number of small entities, and hereby provides notice of that certification to the Small Business Administration, the Commission has determined that it is appropriate to publish an IRFA in order to inquire into the impact of the proposed Rule on small entities. The Commission invites comment on the burden on any small entities that would be covered and has prepared the following analysis.</P>
                    <HD SOURCE="HD2">A. Reasons for the Proposed Rule</HD>
                    <P>As discussed in Part I, the Commission commenced a review of the COPPA Rule on July 25, 2019, noting that questions had arisen about the Rule's application to the ed tech sector, voice-enabled connected devices, and general audience platforms that host third-party child-directed content. After review of the comments received, the Commission concludes that there is a need to update certain Rule provisions to account for changes in technology and online practices, and where appropriate, to clarify and streamline the Rule. Accordingly, the Commission proposes modifications to the Rule in the following areas: Scope of Regulations; Definitions; Notice; Parental Consent; Parental Right to Review; Confidentiality and Security of Children's Personal Information; Data Retention and Deletion; Safe Harbor Programs; and Voluntary Commission Approval Processes.</P>
                    <HD SOURCE="HD2">B. Statement of Objectives and Legal Basis</HD>
                    <P>
                        The objectives of the Proposed Rule are to update the Rule to ensure that children's online privacy continues to be protected, as directed by Congress, even as new online technologies emerge and existing online technologies evolve, and to clarify existing obligations for operators under the Rule. The legal basis for the proposed Rule is the Children's Online Privacy Protection Act, 15 U.S.C. 6501 
                        <E T="03">et seq.</E>
                    </P>
                    <HD SOURCE="HD2">C. Description and Estimated Number of Small Entities to Which the Rule Will Apply</HD>
                    <P>The COPPA Rule applies to operators of commercial websites or online services directed to children that collect personal information through such websites or online services, and operators of any commercial website or online service with actual knowledge that it is collecting personal information from children. The Rule also applies to operators of websites or online services that have actual knowledge that they are collecting personal information directly from users of another website or online service directed to children.</P>
                    <P>
                        The Commission staff is unaware of any empirical evidence concerning the number of operators subject to the Rule. However, based on the previous estimates 
                        <SU>364</SU>
                        <FTREF/>
                         and the Commission's compliance monitoring efforts in the areas of children's privacy, Commission staff estimates that approximately 5,710 operators may be subject to the Rule's requirements, with approximately 280 new operators per year.
                    </P>
                    <FTNT>
                        <P>
                            <SU>364</SU>
                             
                            <E T="03">See, e.g.,</E>
                             78 FR 3972 at 4000.
                        </P>
                    </FTNT>
                    <P>
                        Under the Small Business Size Standards issued by the Small Business Administration, “web search portals and all other information services” qualify as small businesses if they have 1,000 or fewer employees.
                        <SU>365</SU>
                        <FTREF/>
                         Commission staff estimates that approximately 80% of operators potentially subject to the Rule qualify as small entities. The Commission staff bases this estimate on its experience in this area, which includes its law enforcement activities, oversight of FTC-approved COPPA Safe Harbor programs, conducting relevant workshops, and discussions with industry and privacy professionals. The Commission seeks comment and information with regard to the estimated number or nature of small business entities on which the proposed Rule would have a significant economic impact.
                    </P>
                    <FTNT>
                        <P>
                            <SU>365</SU>
                             
                            <E T="03">See</E>
                             U.S. Small Business Administration Table of Small Business Size Standards Matched to North American Industry Classification System Codes, available at 
                            <E T="03">https://www.sba.gov/sites/sbagov/files/2023-03/Table%20of%20Size%20Standards_Effective%20March%2017%2C%202023%20%281%29%20%281%29_0.pdf.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">D. Projected Reporting, Recordkeeping, and Other Compliance Requirements</HD>
                    <P>The proposed amended Rule would impose reporting, recordkeeping, and other compliance requirements within the meaning of the PRA, as set forth in Part VI of this NPRM. Therefore, the Commission is submitting the proposed requirements to OMB for review before issuing a final rule.</P>
                    <P>For example, while not constituting a “collection of information” under the PRA, the proposed Rule would require operators to establish, implement, and maintain a written comprehensive security program. The proposed Rule would also likely increase the disclosure requirements for covered operators, and it would likely increase the disclosure and reporting requirements for FTC-approved COPPA Safe Harbor programs. Specifically, the proposed amendments require operators to update existing disclosures with additional content requirements, namely to update the direct and online notices with additional information about the operators' information practices. Some operators may have to provide disclosures that were not previously required under the Rule. Additionally, the proposed Rule requires operators to disclose a data retention policy.</P>
                    <P>The proposed Rule will also require each FTC-approved COPPA Safe Harbor program to provide a list of all current subject operators on each of the FTC-approved COPPA Safe Harbor program's websites and online services, and the proposed Rule further requires that such list be updated every six months thereafter. The proposed amendments will also require FTC-approved COPPA Safe Harbor programs to include additional content in their annual reports, and submit a new report to the Commission every three years detailing the program's technological capabilities and mechanisms for assessing subject operators' fitness for membership in the program.</P>
                    <P>
                        The estimated burden imposed by these proposed amendments is discussed in the PRA section of this document, and there should be no 
                        <PRTPAGE P="2069"/>
                        difference in that burden as applied to small businesses. While the Rule's compliance obligations apply equally to all entities subject to the Rule, it is unclear whether the economic burden on small entities will be the same as or greater than the burden on other entities. That determination would depend upon a particular entity's compliance costs, some of which may be largely fixed for all entities (
                        <E T="03">e.g.,</E>
                         website programming) and others variable (
                        <E T="03">e.g.,</E>
                         participation in an FTC-approved COPPA Safe Harbor program), and the entity's income or profit from operation of the website or online service itself (
                        <E T="03">e.g.,</E>
                         membership fees) or related sources. As explained in the PRA section, in order to comply with the proposed Rule's requirements, website or online service operators will require the professional skills of legal (lawyers or similar professionals) and technical (
                        <E T="03">e.g.,</E>
                         computer programmers, software developers, and information security analysts) personnel.
                    </P>
                    <P>As explained in the PRA section, Commission staff estimates that there are approximately 5,710 websites or online services that qualify as operators under the proposed Rule, and that approximately 80% of such operators qualify as small entities under the SBA's Small Business Size standards. The Commission invites comment and information on these issues.</P>
                    <HD SOURCE="HD2">E. Identification of Duplicative, Overlapping, or Conflicting Federal Rules</HD>
                    <P>The Commission has not identified any other federal statutes, rules, or policies that would duplicate, overlap, or conflict with the proposed Rule. While the proposed Rule includes amendments related to schools, the Commission believes it has drafted the proposed Rule to ensure it does not duplicate, overlap, or conflict with the Family Educational Rights and Privacy Act. The Commission invites comment and information on this issue.</P>
                    <HD SOURCE="HD2">F. Discussion of Significant Alternatives</HD>
                    <P>In drafting the proposed Rule, the Commission has made every effort to avoid unduly burdensome requirements for entities. The Commission believes that the proposed amendments are necessary to continue to protect children's online privacy in accordance with the purposes of COPPA. For each of the proposed amendments, the Commission has attempted to tailor the provision to any concerns evidenced by the record to date. On balance, the Commission believes that the benefits to children and their parents outweigh any potential increased costs of implementation to industry.</P>
                    <P>For example, some commenters called for the Commission to implement specific time limits on data retention, noting that operators could read the Rule as currently written to allow indefinite retention of personal information. Rather than impose specific limitations that would apply to operators that collect different types of personal information for varying types of activities, the Commission alternatively proposes to require operators to establish a written data retention policy that sets forth a timeframe for deletion and explicitly prohibits indefinite retention.</P>
                    <P>Additionally, the Commission has taken care in developing the proposed amendments to set performance standards that will establish the objective results that must be achieved by regulated entities, but do not mandate a particular technology that must be employed in achieving these objectives. For example, the proposed Rule does not mandate the technology that must be used to establish, implement, and maintain the children's written information security program and related safeguards required under newly-numbered § 312.8(b).</P>
                    <P>The Commission seeks comments on ways in which the proposed Rule could be modified to reduce any costs or benefits for small entities.</P>
                    <HD SOURCE="HD1">VIII. Communications by Outside Parties to the Commissioners or Their Advisors</HD>
                    <P>
                        Written communications and summaries or transcripts of oral communications respecting the merits of this proceeding, from any outside party to any Commissioner or Commissioner's advisor, will be placed on the public record. 
                        <E T="03">See</E>
                         16 CFR 1.26(b)(5).
                    </P>
                    <HD SOURCE="HD1">IX. Questions for the Proposed Revisions to the Rule</HD>
                    <P>The Commission is seeking comment on various aspects of the proposed Rule and is particularly interested in receiving comment on the questions that follow. These questions are designed to assist the public and should not be construed as a limitation on the issues on which public comment may be submitted. Responses to these questions should cite the numbers and subsections of the questions being answered. For all comments submitted, please submit any relevant data, statistics, or any other evidence, upon which those comments are based.</P>
                    <HD SOURCE="HD2">General Question</HD>
                    <P>1. Please provide comment on any or all of the provisions in the proposed Rule. For each provision commented on, please describe: (1) the impact of the provision(s) (including any benefits and costs), if any; and (2) what alternatives, if any, the Commission should consider, as well as the costs and benefits of those alternatives.</P>
                    <HD SOURCE="HD2">Definitions</HD>
                    <P>
                        2. As part of the Rule review that led to the 2013 Amendments, the Commission determined that an operator will not be deemed to have “collected” (as that term is defined in the Rule) personal information from a child when it employs technologies reasonably designed to delete all or virtually all personal information input by children before making information publicly available.
                        <SU>366</SU>
                        <FTREF/>
                         The Commission is concerned that, if automatic moderation or filtering technologies can be circumvented, reliance on such technologies may not be appropriate in a context where a child is communicating one to one with another person privately, as opposed to posting information online publicly. Should the Commission retain its position that an operator will not be deemed to have “collected” personal information, and therefore does not have to comply with the Rule's requirements, if it employs automated means to delete all or virtually all personal information from one-to-one communications?
                    </P>
                    <FTNT>
                        <P>
                            <SU>366</SU>
                             76 FR 59804 at 59808.
                        </P>
                    </FTNT>
                    <P>3. The Commission proposes to include mobile telephone numbers within the definition of “online contact information” so long as such information is used only to send text messages. This proposed modification would permit operators to send text messages to parents to initiate obtaining verifiable parental consent. Does allowing operators to contact parents through a text message to obtain verifiable parental consent present security risks to the recipient of the text message, particularly if the parent would need to click on a link provided in the text message?</P>
                    <P>
                        4. In conjunction with the 2013 Amendments, the Commission acknowledged that screen and user names have increasingly become portable across multiple websites or online services, and that such identifiers permit the direct contact of a specific individual online.
                        <SU>367</SU>
                        <FTREF/>
                         Through the 2013 Amendments, the Commission defined personal information to include screen or user names only to the extent these 
                        <PRTPAGE P="2070"/>
                        identifiers function in the same way as “online contact information” as the Rule defines that term. Since 2013, the use of screen and user names has proliferated across websites and online services, including on online gaming platforms that allow users to directly engage with each other. The Commission is concerned that children may use the same screen or user name on different sites and services, potentially allowing other users to contact and engage in direct communications with children on another online service.
                    </P>
                    <FTNT>
                        <P>
                            <SU>367</SU>
                             76 FR 59804 at 59810.
                        </P>
                    </FTNT>
                    <P>a. Should screen or user names be treated as online contact information, even if the screen or user name does not allow one user to contact another user through the operator's website or online service, when the screen or user name could enable one user to contact another by assuming that the user to be contacted is using the same screen or user name on another website or online service that does allow such contact?</P>
                    <P>b. Are there measures an operator can take to ensure that a screen or user name cannot be used to permit the direct contact of a person online?</P>
                    <P>5. The Commission proposes adding biometric identifiers such as fingerprints, retina and iris patterns, a DNA sequence, and data derived from voice data, gait data, or facial data to the definition of “personal information.” Should the Commission consider including any additional biometric identifier examples to this definition? Are there exceptions to the Rule's requirements that the Commission should consider applying to biometric data, such as exceptions for biometric data that has been promptly deleted?</P>
                    <P>6. The use of avatars generated from a child's image has become popular in online services, such as video games. Should an avatar generated from a child's image constitute “personal information” under the COPPA Rule even if the photograph of the child is not itself uploaded to the site or service and no other personal information is collected from the child? If so, are these avatars sufficiently covered under the current COPPA Rule, or are further modifications to the definition required to cover avatars generated from a child's image?</P>
                    <P>7. The definition of “personal information” includes a Social Security number. Should the Commission revise this definition to list other government-issued identifiers specifically? If so, what type of identifiers should be included?</P>
                    <P>8. The definition of “personal information” includes “information concerning the child or the parents of that child that the operator collects online from the child and combines with an identifier described in [the Rule's definition of `personal information'].” Does the phrase “concerning the child or parents of that child” require further clarification?</P>
                    <P>9. Certain commenters recommended modifications to the “support for the internal operations of the website or online service” definition, including to limit personalization to “user-driven” actions and to exclude methods designed to maximize user engagement. Under what circumstances would personalization be considered “user-driven” versus personalization driven by an operator? How do operators use persistent identifiers, as defined by the COPPA Rule, to maximize user engagement with a website or online service?</P>
                    <P>10. Operators can collect persistent identifiers for contextual advertising purposes without parental consent so long as they do not also collect other personal information. Given the sophistication of contextual advertising today, including that personal information collected from users may be used to enable companies to target even contextual advertising to some extent, should the Commission consider changes to the Rule's treatment of contextual advertising?</P>
                    <P>11. With regard to the definition of “website or online service directed to children,” the Commission would like to obtain additional comment on whether it should provide an exemption for operators from being deemed a child-directed website or online service if such operators undertake an analysis of their audience composition and determine no more than a specific percentage of its users are likely to be children under 13.</P>
                    <P>a. Should the COPPA Rule offer an exemption or other incentive to encourage operators to conduct an analysis of their user bases?</P>
                    <P>b. If the COPPA Rule should include such an exemption or other incentive, what are the reliable means by which operators can determine the likely ages of their sites' or services' users?</P>
                    <P>c. As part of this exemption or incentive, should the COPPA Rule identify which means operators must utilize to determine the likely ages of their users? If so, how should the COPPA Rule identify such means?</P>
                    <P>d. If the COPPA Rule should include such an exemption or other incentive, what should be the appropriate percentage of users to qualify for this exemption or incentive?</P>
                    <P>e. Would such an exemption be inconsistent with the COPPA Rule's multi-factor test for determining whether a website or online service, or a portion thereof, is directed to children?</P>
                    <HD SOURCE="HD2">Notice</HD>
                    <P>12. The Commission proposes requiring operators that share personal information with third parties to identify those third parties or specific categories of those third parties in the direct notice to the parent. Is this information better positioned in the direct notice required under § 312.4(c), or should it be placed in the online notice required under § 312.4(d)?</P>
                    <HD SOURCE="HD2">Parental Consent</HD>
                    <P>13. Can platforms play a role in establishing consent mechanisms to enable app developers or other websites or online services to obtain verifiable parental consent? If so, what benefits would a platform-based common consent mechanism offer operators and parents? What steps can the Commission take to encourage the development of platform-based consent mechanisms?</P>
                    <P>14. To effectuate § 312.5(a)(2), which requires operators to give the parent the option to consent to the collection and use of the child's personal information without consenting to disclosure of the child's personal information to third parties, the Commission proposes requiring operators to obtain separate verifiable parental consent prior to disclosing a child's personal information, unless such disclosure is integral to the nature of the website or online service. Should the Commission implement such a requirement? Should the consent mechanism for disclosure be offered at a different time and/or place than the mechanism for the underlying collection and use? Is the exception for disclosures that are integral to the nature of the website or online service clear, or should the Commission clarify which disclosures are integral? Should the Rule require operators to state which disclosures are integral to the nature of website or online service?</P>
                    <P>
                        15. As noted in Part IV.C.3.c., the Commission proposes to modify § 312.5(c)(4) to prohibit operators from utilizing this exception to encourage or prompt use of a website or online service. Are there other engagement techniques the Rule should address? If so, what section of the Rule should address them? What types of personal information do operators use when utilizing engagement techniques? Additionally, should the Rule differentiate between techniques used solely to promote a child's engagement 
                        <PRTPAGE P="2071"/>
                        with the website or online service and those techniques that provide other functions, such as to personalize the child's experience on the website or online service? If so, how should the Rule differentiate between those techniques?
                    </P>
                    <P>16. The Commission proposes to include a parental consent exception to permit schools, State educational agencies, and local educational agencies to authorize the collection, use, and disclosure of personal information from students younger than 13 where the data is used for a school-authorized education purpose and no other commercial purpose. What types of services should be covered under a “school-authorized education purpose”? For example, should this include services used to conduct activities not directly related to teaching, such as services used to ensure the safety of students or schools?</P>
                    <HD SOURCE="HD2">Prohibition Against Conditioning a Child's Participation on Collection of Personal Information</HD>
                    <P>17. COPPA and § 312.7 of the Rule prohibit operators from conditioning a child's participation in an activity on disclosing more personal information than is reasonably necessary to participate in such activity.</P>
                    <P>a. What efforts are operators taking to comply with § 312.7? Are these efforts taken on a website-wide or online service-wide basis, or are operators imposing efforts on a more granular level?</P>
                    <P>b. Should the Commission specify whether disclosures for particular purposes are reasonably necessary or not reasonably necessary in a particular context? If so, for which purposes and in which contexts?</P>
                    <P>c. Given that operators must provide notice and seek verifiable parental consent before collecting personal information, to what extent should the Commission consider the information practices disclosed to the parent in assessing whether information collection is reasonably necessary?</P>
                    <P>18. The Commission is considering adding new language to address the meaning of “activity,” as that term is used in § 312.7. Specifically, the Commission is considering including language in § 312.7 to provide that an “activity” means “any activity offered by a website or online service, whether that activity is a subset or component of the website or online service or is the entirety of the website or online service.” Should the Commission make this modification to the Rule? Is this modification necessary in light of the breadth of the plain meaning of the term “activity”?</P>
                    <HD SOURCE="HD2">Safe Harbor</HD>
                    <P>19. What types of conflicts would affect an FTC-approved COPPA Safe Harbor program from effectively assessing a subject operator's fitness for membership in the FTC-approved COPPA Safe Harbor program? What policies do FTC-approved COPPA Safe Harbor programs have in place to prevent such conflicts?</P>
                    <HD SOURCE="HD2">Effective Date</HD>
                    <P>
                        20. As part of the issuance of the initial Rule and the 2013 Amendments, the Commission stated that the Rule and amended Rule, respectively, would become effective approximately six months after issuance of the Commission's final rule in the 
                        <E T="04">Federal Register</E>
                        . The Commission requests comment on whether such timeframe is appropriate for the modifications set forth during this Rule review that do not specify an effective date.
                    </P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects in 16 CFR Part 312</HD>
                        <P>Communications, Computer technology, Consumer protection, Infants and children, internet, Privacy, Reporting and recordkeeping requirements, Safety, Science and technology, Trade practices, Youth.</P>
                    </LSTSUB>
                    <P>Accordingly, the Federal Trade Commission proposes to amend 16 CFR 312 as follows:</P>
                    <PART>
                        <HD SOURCE="HED">PART 312—CHILDREN'S ONLINE PRIVACY PROTECTION RULE</HD>
                    </PART>
                    <AMDPAR>1. The authority for part 312 continues to read:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 15 U.S.C. 6501 through 6508.</P>
                    </AUTH>
                    <AMDPAR>2. Revise § 312.1 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 312.1</SECTNO>
                        <SUBJECT>Scope of regulations in this part.</SUBJECT>
                        <P>
                            This part implements the Children's Online Privacy Protection Act of 1998 (15 U.S.C. 6501, 
                            <E T="03">et seq.</E>
                            ), which prohibits unfair or deceptive acts or practices in connection with the collection, use, and/or disclosure of personal information from and about children on the internet.
                        </P>
                    </SECTION>
                    <AMDPAR>3. In § 312.2:</AMDPAR>
                    <AMDPAR>
                        a. Revise the definition of 
                        <E T="03">Disclose or disclosure;</E>
                    </AMDPAR>
                    <AMDPAR>
                        b. Add in alphabetical order a definition for 
                        <E T="03">Mixed audience website or online service;</E>
                    </AMDPAR>
                    <AMDPAR>
                        c. Revise the definition of 
                        <E T="03">Online contact information;</E>
                    </AMDPAR>
                    <AMDPAR>
                        d. Revise the introductory text and paragraph (2) of the definition of 
                        <E T="03">Operator;</E>
                    </AMDPAR>
                    <AMDPAR>
                        e. Republish the introductory text, revise paragraphs (7) and (9), redesignate paragraph (10) as paragraph (11), and add a new paragraph (10) to the definition of 
                        <E T="03">Personal information;</E>
                    </AMDPAR>
                    <AMDPAR>
                        f. Add in alphabetical order definitions for 
                        <E T="03">School</E>
                         and 
                        <E T="03">School-authorized education purpose;</E>
                    </AMDPAR>
                    <AMDPAR>
                        g. Remove the words “Web Site” and add in their place the word “Web site” in the term 
                        <E T="03">Support for the internal operations of the website or online service</E>
                         and in the definition, republish paragraph (1) introductory text and revise paragraphs (1)(i), (iii), (iv), (v), and (vii) and (2);
                    </AMDPAR>
                    <AMDPAR>
                        h. Revise the definition of 
                        <E T="03">Third party; and</E>
                    </AMDPAR>
                    <AMDPAR>
                        i. Remove the definition of 
                        <E T="03">Web site or online service directed to children</E>
                         and add inits place in alphabetical order a definition for 
                        <E T="03">Website or online service directed to children.</E>
                    </AMDPAR>
                    <P>The additions, republications, and revisions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 312.2</SECTNO>
                        <SUBJECT>Definitions.</SUBJECT>
                        <STARS/>
                        <P>
                            <E T="03">Disclose or disclosure</E>
                             means, with respect to personal information:
                        </P>
                        <P>(1) The release of personal information collected by an operator from a child in identifiable form for any purpose, except where an operator provides such information to a person who provides support for the internal operations of the website or online service; and</P>
                        <P>(2) Making personal information collected by an operator from a child publicly available in identifiable form by any means, including but not limited to a public posting through the internet, or through a personal home page or screen posted on a website or online service; a pen pal service; an electronic mail service; a message board; or a chat room.</P>
                        <STARS/>
                        <P>
                            <E T="03">Mixed audience website or online service</E>
                             means a website or online service that is directed to children under the criteria set forth in paragraph (1) of the definition of website or online service directed to children, but that does not target children as its primary audience, and does not collect personal information from any visitor prior to collecting age information or using another means that is reasonably calculated, in light of available technology, to determine whether the visitor is a child. Any collection of age information, or other means of determining whether a visitor is a child, must be done in a neutral manner that does not default to a set age or encourage visitors to falsify age information.
                        </P>
                        <STARS/>
                        <PRTPAGE P="2072"/>
                        <P>
                            <E T="03">Online contact information</E>
                             means an email address or any other substantially similar identifier that permits direct contact with a person online, including but not limited to, an instant messaging user identifier, a voice over internet protocol (VOIP) identifier, a video chat user identifier, or an identifier such as a mobile telephone number provided the operator uses it only to send a text message.
                        </P>
                        <P>
                            <E T="03">Operator</E>
                             means any person who operates a website located on the internet or an online service and who collects or maintains personal information from or about the users of or visitors to such website or online service, or on whose behalf such information is collected or maintained, or offers products or services for sale through that website or online service, where such website or online service is operated for commercial purposes involving commerce among the several States or with one or more foreign nations; in any territory of the United States or in the District of Columbia, or between any such territory and another such territory or any State or foreign nation; or between the District of Columbia and any State, territory, or foreign nation. This definition does not include any nonprofit entity that would otherwise be exempt from coverage under section 5 of the Federal Trade Commission Act (15 U.S.C. 45). Personal information is collected or maintained on behalf of an operator when:
                        </P>
                        <STARS/>
                        <P>(2) The operator benefits by allowing another person to collect personal information directly from users of such website or online service.</P>
                        <STARS/>
                        <P>
                            <E T="03">Personal information</E>
                             means individually identifiable information about an individual collected online, including:
                        </P>
                        <STARS/>
                        <P>(7) A persistent identifier that can be used to recognize a user over time and across different websites or online services. Such persistent identifier includes, but is not limited to, a customer number held in a cookie, an internet Protocol (IP) address, a processor or device serial number, or unique device identifier;</P>
                        <STARS/>
                        <P>(9) Geolocation information sufficient to identify street name and name of a city or town;</P>
                        <P>(10) A biometric identifier that can be used for the automated or semi-automated recognition of an individual, including fingerprints or handprints; retina and iris patterns; genetic data, including a DNA sequence; or data derived from voice data, gait data, or facial data; or</P>
                        <P>(11) Information concerning the child or the parents of that child that the operator collects online from the child and combines with an identifier described in this definition.</P>
                        <STARS/>
                        <P>
                            <E T="03">School</E>
                             means a State educational agency or local educational agency as defined under Federal law, as well as an institutional day or residential school, including a public school, charter school, or private school, that provides elementary or secondary education, as determined under State law.
                        </P>
                        <P>
                            <E T="03">School-authorized education purpose</E>
                             means any school-authorized use related to a child's education. Such use shall be limited to operating the specific educational service that the school has authorized, including maintaining, developing, supporting, improving, or diagnosing the service, provided such uses are directly related to the service the school authorized. School-authorized education purpose does not include commercial purposes unrelated to a child's education, such as advertising.
                        </P>
                        <P>
                            <E T="03">Support for the internal operations of the website or online service</E>
                             means:
                        </P>
                        <P>(1) Those activities necessary to:</P>
                        <P>(i) Maintain or analyze the functioning of the website or online service;</P>
                        <STARS/>
                        <P>(iii) Authenticate users of, or personalize the content on, the website or online service;</P>
                        <P>(iv) Serve contextual advertising on the website or online service or cap the frequency of advertising;</P>
                        <P>(v) Protect the security or integrity of the user, website, or online service;</P>
                        <STARS/>
                        <P>(vii) Fulfill a request of a child as permitted by § 312.5(c)(3) and (4).</P>
                        <P>(2) Provided, however, that, except as specifically permitted by paragraphs 1(i) through(vii) of this definition, the information collected for the activities listed in paragraphs (1)(i) through (vii) of this definition cannot be used or disclosed to contact a specific individual, including through behavioral advertising, to amass a profile on a specific individual, in connection with processes that encourage or prompt use of a website or online service, or for any other purpose.</P>
                        <P>
                            <E T="03">Third party</E>
                             means any person who is not:
                        </P>
                        <P>(1) An operator with respect to the collection or maintenance of personal information on the website or online service; or</P>
                        <P>(2) A person who provides support for the internal operations of the website or online service and who does not use or disclose information protected under this part for any other purpose.</P>
                        <P>
                            <E T="03">Website or online service directed to children</E>
                             means a commercial website or online service, or portion thereof, that is targeted to children.
                        </P>
                        <P>(1) In determining whether a website or online service, or a portion thereof, is directed to children, the Commission will consider its subject matter, visual content, use of animated characters or child-oriented activities and incentives, music or other audio content, age of models, presence of child celebrities or celebrities who appeal to children, language or other characteristics of the website or online service, as well as whether advertising promoting or appearing on the website or online service is directed to children. The Commission will also consider competent and reliable empirical evidence regarding audience composition and evidence regarding the intended audience, including marketing or promotional materials or plans, representations to consumers or to third parties, reviews by users or third parties, and the age of users on similar websites or services.</P>
                        <P>(2) A website or online service shall be deemed directed to children when it has actual knowledge that it is collecting personal information from users of another website or online service directed to children.</P>
                        <P>(3) A mixed audience website or online service shall not be deemed directed to children with regard to any visitor not identified as under 13.</P>
                        <P>(4) A website or online service shall not be deemed directed to children solely because it refers or links to a commercial website or online service directed to children by using information location tools, including a directory, index, reference, pointer, or hypertext link.</P>
                    </SECTION>
                    <AMDPAR>4. Revise § 312.3 introductory text and paragraph (a) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 312.3</SECTNO>
                        <SUBJECT> Regulation of unfair or deceptive acts or practices in connection with the collection, use, and/or disclosure of personal information from and about children on the Internet.</SUBJECT>
                        <P>
                            <E T="03">General requirements.</E>
                             It shall be unlawful for any operator of a website or online service directed to children, or any operator that has actual knowledge that it is collecting or maintaining personal information from a child, to collect personal information from a child in a manner that violates the regulations prescribed under this part. 
                            <PRTPAGE P="2073"/>
                            Generally, under this part, an operator must:
                        </P>
                        <P>(a) Provide notice on the website or online service of what information it collects from children, how it uses such information, and its disclosure practices for such information (§ 312.4(b));</P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>5. In § 312.4:</AMDPAR>
                    <AMDPAR>a. Revise paragraphs (b), (c) introductory text, (c)(1), (c)(2) introductory text, and (c)(2)(i) and (iii);</AMDPAR>
                    <AMDPAR>b. Add paragraph (c)(5);</AMDPAR>
                    <AMDPAR>c. Revise paragraph (d); and</AMDPAR>
                    <AMDPAR>d. Add paragraph (e);</AMDPAR>
                    <P>The revisions and additions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 312.4</SECTNO>
                        <SUBJECT>Notice.</SUBJECT>
                        <STARS/>
                        <P>
                            (b) 
                            <E T="03">Direct notice to the parent or school.</E>
                             An operator must make reasonable efforts, taking into account available technology, to ensure that a parent of a child or, if applicable, the child's school receives direct notice of the operator's practices with regard to the collection, use, or disclosure of personal information from children, including notice of any material change in the collection, use, or disclosure practices to which the parent has previously consented or the school has previously authorized.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Content of the direct notice</E>
                            —(1) 
                            <E T="03">Content of the direct notice to the parent for purposes of obtaining consent, including under § 312.5(c)(1) (Notice to Obtain Parent's Affirmative Consent to the Collection, Use, or Disclosure of a Child's Personal Information).</E>
                             This direct notice shall set forth:
                        </P>
                        <P>(i) If applicable, that the operator has collected the parent's or child's online contact information from the child, and, if such is the case, the name of the child or the parent, in order to obtain the parent's consent;</P>
                        <P>(ii) That the parent's consent is required for the collection, use, or disclosure of personal information, and that the operator will not collect, use, or disclose any personal information from the child if the parent does not provide such consent;</P>
                        <P>(iii) The items of personal information the operator intends to collect from the child, how the operator intends to use such information, and the potential opportunities for the disclosure of personal information, should the parent provide consent;</P>
                        <P>(iv) Where the operator discloses personal information to one or more third parties, the identities or specific categories of such third parties (including the public if making it publicly available) and the purposes for such disclosure, should the parent provide consent, and that the parent can consent to the collection and use of the child's personal information without consenting to the disclosure of such personal information to third parties except to the extent such disclosure is integral to the nature of the website or online service;</P>
                        <P>(v) A hyperlink to the operator's online notice of its information practices required under paragraph (d) of this section;</P>
                        <P>(vi) The means by which the parent can provide verifiable consent to the collection, use, and disclosure of the information; and</P>
                        <P>(vii) If the operator has collected the name or online contact information of the parent or child to provide notice and obtain parental consent, that if the parent does not provide consent within a reasonable time from the date the direct notice was sent, the operator will delete the parent's or child's online contact information and the parent's or child's name from its records.</P>
                        <P>
                            (2) 
                            <E T="03">Content of the direct notice to the parent under § 312.5(c)(2) (Voluntary Notice to Parent of a Child's Online Activities Not Involving the Collection, Use or Disclosure of Personal Information).</E>
                             Where an operator chooses to notify a parent of a child's participation in a website or online service, and where such site or service does not collect any personal information other than the parent's online contact information, the direct notice shall set forth:
                        </P>
                        <P>(i) That the operator has collected the parent's online contact information from the child in order to provide notice to, and subsequently update the parent about, a child's participation in a website or online service that does not otherwise collect, use, or disclose children's personal information;</P>
                        <STARS/>
                        <P>(iii) That the parent may refuse to permit the child's participation in the website or online service and may require the deletion of the parent's online contact information, and how the parent can do so; and</P>
                        <STARS/>
                        <P>
                            (5) 
                            <E T="03">Content of the direct notice to the school under § 312.5(c)(10) (Notice to a School for Educational Services).</E>
                             This direct notice shall set forth:
                        </P>
                        <P>(i) That a school's authorization is required for the collection, use, or disclosure of personal information, and that the operator will not collect, use, or disclose any personal information from the child if the school does not provide such authorization;</P>
                        <P>(ii) That the operator's use and disclosure of personal information collected from the child is limited to a school-authorized education purpose;</P>
                        <P>(iii) The items of personal information the operator intends to collect from the child, how the operator intends to use such information, and the potential opportunities for the disclosure of personal information, should the school provide authorization;</P>
                        <P>(iv) Where the operator discloses the personal information to third parties, the identities or specific categories of such third parties and the specific school-authorized education purposes for such disclosure, should the school provide authorization;</P>
                        <P>(v) A hyperlink to the operator's online notice of its information practices required under paragraphs (d) and (e) of this section; and</P>
                        <P>(vi) The means by which the school can authorize the collection, use, and disclosure of the information.</P>
                        <P>
                            (d) 
                            <E T="03">Notice on the website or online service.</E>
                             In addition to the direct notice, an operator must post a prominent and clearly labeled link to an online notice of its information practices with regard to children on the home or landing page or screen of its website or online service, 
                            <E T="03">and,</E>
                             at each area of the website or online service where personal information is collected from children. The link must be in close proximity to the requests for information in each such area. An operator of a general audience website or online service that has a separate children's area must post a link to a notice of its information practices with regard to children on the home or landing page or screen of the children's area. To be complete, the online notice of the website or online service's information practices must state the following:
                        </P>
                        <P>
                            (1) The name, address, telephone number, and email address of all operators collecting or maintaining personal information from children through the website or online service. 
                            <E T="03">Provided that:</E>
                             The operators of a website or online service may list the name, address, phone number, and email address of one operator who will respond to all inquiries from parents concerning the operators' privacy policies and use of children's information, as long as the names of all the operators collecting or maintaining personal information from children through the website or online service are also listed in the notice;
                        </P>
                        <P>
                            (2) A description of what information the operator collects from children, including whether the website or online service enables a child to make personal information publicly available; how the operator uses such information; the operator's disclosure practices for such 
                            <PRTPAGE P="2074"/>
                            information, including the identities or specific categories of any third parties to which the operator discloses personal information and the purposes for such disclosures; and the operator's data retention policy as required under § 312.10;
                        </P>
                        <P>(3) If applicable, the specific internal operations for which the operator has collected a persistent identifier pursuant to § 312.5(c)(7); and the means the operator uses to ensure that such identifier is not used or disclosed to contact a specific individual, including through behavioral advertising, to amass a profile on a specific individual, in connection with processes that encourage or prompt use of a website or online service, or for any other purpose (except as specifically permitted to provide support for the internal operations of the website or online service);</P>
                        <P>(4) Where the operator collects audio files containing a child's voice pursuant to § 312.5(c)(9), a description of how the operator uses such audio files and that the operator deletes such audio files immediately after responding to the request for which they were collected; and</P>
                        <P>(5) If applicable, that the parent can review or have deleted the child's personal information, and refuse to permit further collection or use of the child's information, and state the procedures for doing so.</P>
                        <P>
                            (e) 
                            <E T="03">Additional notice on the website or online service where an operator has collected personal information under § 312.5(c)(10).</E>
                             In addition to the applicable requirements in paragraph (d) of this section, where an operator has collected personal information under § 312.5(c)(10), an operator's online notice of its information practices with regard to children must state that the operator has obtained authorization from a school to collect a child's personal information; that the operator will use and disclose the information for a school-authorized education purpose and no other purpose; that the school may review the information; and that the school may request deletion of the child's personal information, and the procedures for doing so.
                        </P>
                    </SECTION>
                    <AMDPAR>6. In § 312.5:</AMDPAR>
                    <AMDPAR>a. Revise paragraph (a)(2) and paragraph (b)(2)(ii);</AMDPAR>
                    <AMDPAR>b. Redesignate paragraph (b)(2)(vi) as (b)(2)(viii);</AMDPAR>
                    <AMDPAR>c. Republish newly designated paragraphs (b)(2)(viii);</AMDPAR>
                    <AMDPAR>d. Add new paragraphs (b)(2)(vi) and (vii);</AMDPAR>
                    <AMDPAR>e. Revise paragraphs (c)(2) and (4), (c)(6)(i) and (iv), (c)(7) and (8); and</AMDPAR>
                    <AMDPAR>f. Add paragraphs (c)(9) and (10);</AMDPAR>
                    <P>The revisions, republication, and additions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 312.5</SECTNO>
                        <SUBJECT>Parental consent.</SUBJECT>
                        <P>(a) * * *</P>
                        <P>(2) An operator must give the parent the option to consent to the collection and use of the child's personal information without consenting to disclosure of his or her personal information to third parties, unless such disclosure is integral to the nature of the website or online service. An operator required to give the parent this option must obtain separate verifiable parental consent to such disclosure, and the operator may not condition access to the website or online service on such consent.</P>
                        <P>(b) * * *</P>
                        <P>(2) * * *</P>
                        <P>(ii) Requiring a parent, in connection with a transaction, to use a credit card, debit card, or other online payment system that provides notification of each discrete transaction to the primary account holder;</P>
                        <STARS/>
                        <P>(vi) Verifying a parent's identity using knowledge-based authentication, provided:</P>
                        <P>(A) the verification process uses dynamic, multiple-choice questions, where there are a reasonable number of questions with an adequate number of possible answers such that the probability of correctly guessing the answers is low; and</P>
                        <P>(B) the questions are of sufficient difficulty that a child age 12 or younger in the parent's household could not reasonably ascertain the answers;</P>
                        <P>(vii) Having a parent submit a government-issued photographic identification that is verified to be authentic and is compared against an image of the parent's face taken with a phone camera or webcam using facial recognition technology and confirmed by personnel trained to confirm that the photos match; provided that the parent's identification and images are deleted by the operator from its records after the match is confirmed; or</P>
                        <P>(viii) Provided that an operator that does not “disclose” (as defined by § 312.2) children's personal information, may use an email coupled with additional steps to provide assurances that the person providing the consent is the parent. Such additional steps include: Sending a confirmatory email to the parent following receipt of consent, or obtaining a postal address or telephone number from the parent and confirming the parent's consent by letter or telephone call. An operator that uses this method must provide notice that the parent can revoke any consent given in response to the earlier email.</P>
                        <STARS/>
                        <P>(c) * * *</P>
                        <P>(2) Where the purpose of collecting a parent's online contact information is to provide voluntary notice to, and subsequently update the parent about, the child's participation in a website or online service that does not otherwise collect, use, or disclose children's personal information. In such cases, the parent's online contact information may not be used or disclosed for any other purpose. In such cases, the operator must make reasonable efforts, taking into consideration available technology, to ensure that the parent receives notice as described in § 312.4(c)(2);</P>
                        <STARS/>
                        <P>(4) Where the purpose of collecting a child's and a parent's online contact information is to respond directly more than once to the child's specific request, and where such information is not used for any other purpose, disclosed, or combined with any other information collected from the child. Provided, however, that an operator may not utilize this exception to encourage or prompt use of a website or online service. An operator utilizing this exception for permissible purposes must make reasonable efforts, taking into consideration available technology, to ensure that the parent receives notice as described in § 312.4(c)(3). An operator will not be deemed to have made reasonable efforts to ensure that a parent receives notice where the notice to the parent was unable to be delivered;</P>
                        <STARS/>
                        <P>(6) * * *</P>
                        <P>(i) Protect the security or integrity of the website or online service;</P>
                        <STARS/>
                        <P>(iv) To the extent permitted under other provisions of law, to provide information to law enforcement agencies or for an investigation on a matter related to public safety; and where such information is not used for any other purpose;</P>
                        <STARS/>
                        <P>(7) Where an operator collects a persistent identifier and no other personal information and such identifier is used for the sole purpose of providing support for the internal operations of the website or online service. In such case, the operator shall provide notice under § 312.4(d)(3);</P>
                        <P>
                            (8) Where an operator covered under paragraph (2) of the definition of website or online service directed to children in § 312.2 collects a persistent identifier and no other personal information from a user who 
                            <PRTPAGE P="2075"/>
                            affirmatively interacts with the operator and whose previous registration with that operator indicates that such user is not a child. In such case, there also shall be no obligation to provide notice under § 312.4;
                        </P>
                        <P>(9) Where an operator collects an audio file containing a child's voice, and no other personal information, for use in responding to a child's specific request and where the operator does not use such information for any other purpose, does not disclose it, and deletes it immediately after responding to the child's request. In such case, there also shall be no obligation to provide a direct notice, but notice shall be required under § 312.4(d); or</P>
                        <P>(10) Where the operator obtains school authorization for the collection of the child's personal information for a school-authorized education purpose. In such a case, the operator must ensure that the school receives notice as described in § 312.4(c)(5) and must have a written agreement with the school that:</P>
                        <P>(i) Indicates the name and title of the person providing authorization and attests that the person has the authority to do so;</P>
                        <P>(ii) Limits the operator's use and disclosure of the personal information to a school-authorized education purpose only and no other purpose;</P>
                        <P>(iii) Provides that the operator is under the school's direct control with regard to the use, disclosure, and maintenance of the personal information collected from the child pursuant to school authorization; and</P>
                        <P>(iv) Sets forth the operator's data retention policy with respect to such information in accordance with § 312.10.</P>
                    </SECTION>
                    <AMDPAR>7. In § 312.6:</AMDPAR>
                    <AMDPAR>a. Revise the section heading and paragraph (a) introductory text;</AMDPAR>
                    <AMDPAR>b. Redesignate paragraphs (b) and (c) as paragraphs (c) and (d);</AMDPAR>
                    <AMDPAR>c. Add new paragraph (b); and</AMDPAR>
                    <AMDPAR>d. Republish newly redesignated paragraphs (c) and (d).</AMDPAR>
                    <P>The revisions, addition, and republications read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 312.6</SECTNO>
                        <SUBJECT>Right to review personal information provided by a child.</SUBJECT>
                        <P>(a) Upon request of a parent whose child has provided personal information to a website or online service, the operator of that website or online service is required to provide to that parent the following:</P>
                        <STARS/>
                        <P>(b) Where personal information is collected from the child pursuant to § 312.5(c)(10), the operator of the website or online service is required to provide the rights under paragraph (a) of this section to the school and is not required to provide such rights to a parent whose child has provided personal information to the website or online service.</P>
                        <P>(c) Neither an operator nor the operator's agent shall be held liable under any Federal or State law for any disclosure made in good faith and following reasonable procedures in responding to a request for disclosure of personal information under this section.</P>
                        <P>(d) Subject to the limitations set forth in § 312.7, an operator may terminate any service provided to a child whose parent has refused, under paragraph (a)(2) of this section, to permit the operator's further use or collection of personal information from his or her child or has directed the operator to delete the child's personal information.</P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>8. Revise § 312.8 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 312.8</SECTNO>
                        <SUBJECT>Confidentiality, security, and integrity of personal information collected from children.</SUBJECT>
                        <P>(a) The operator must establish and maintain reasonable procedures to protect the confidentiality, security, and integrity of personal information collected from children.</P>
                        <P>(b) At a minimum, the operator must establish, implement, and maintain a written children's personal information security program that contains safeguards that are appropriate to the sensitivity of the personal information collected from children and the operator's size, complexity, and nature and scope of activities. To establish, implement, and maintain a children's personal information security program, the operator must:</P>
                        <P>(1) Designate one or more employees to coordinate the operator's children's personal information security program;</P>
                        <P>(2) Identify and, at least annually, perform additional assessments to identify internal and external risks to the confidentiality, security, and integrity of personal information collected from children and the sufficiency of any safeguards in place to control such risks;</P>
                        <P>(3) Design, implement, and maintain safeguards to control risks identified through the risk assessments required under paragraph (b)(2) of this section. Each safeguard must be based on the volume and sensitivity of the children's personal information that is at risk, and the likelihood that the risk could result in the unauthorized disclosure, misuse, alteration, destruction or other compromise of such information;</P>
                        <P>(4) Regularly test and monitor the effectiveness of the safeguards in place to control risks identified through the risk assessments required under paragraph (b)(2) of this section; and</P>
                        <P>(5) At least annually, evaluate and modify the children's personal information security program to address identified risks, results of required testing and monitoring, new or more efficient technological or operational methods to control for identified risks, or any other circumstances that an operator knows or has reason to know may have a material impact on its children's personal information security program or any safeguards in place.</P>
                        <P>(c) Before allowing other operators, service providers, or third parties to collect or maintain personal information from children on the operator's behalf, or before releasing children's personal information to such entities, the operator must take reasonable steps to determine that such entities are capable of maintaining the confidentiality, security, and integrity of the information and must obtain written assurances that such entities will employ reasonable measures to maintain the confidentiality, security, and integrity of the information.</P>
                    </SECTION>
                    <AMDPAR>9. Revise § 312.10 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 312.10</SECTNO>
                        <SUBJECT>Data retention and deletion requirements.</SUBJECT>
                        <P>An operator of a website or online service shall retain personal information collected online from a child for only as long as is reasonably necessary to fulfill the specific purpose(s) for which the information was collected and not for a secondary purpose. When such information is no longer reasonably necessary for the purpose for which it was collected, the operator must delete the information using reasonable measures to protect against unauthorized access to, or use of, the information in connection with its deletion. Personal information collected online from a child may not be retained indefinitely. At a minimum, the operator must establish, implement, and maintain a written children's data retention policy that sets forth the purposes for which children's personal information is collected, the business need for retaining such information, and a timeframe for deletion of such information that precludes indefinite retention. The operator must provide its written children's data retention policy in the notice on the website or online service provided in accordance with § 312.4(d).</P>
                    </SECTION>
                    <AMDPAR>10. In § 312.11:</AMDPAR>
                    <AMDPAR>a. Republish (b) introductory text;</AMDPAR>
                    <AMDPAR>b. Revise paragraphs (b)(2), (d)(1) and (2), and (d)(3)(iii);</AMDPAR>
                    <AMDPAR>
                        c. Add paragraph (d)(4);
                        <PRTPAGE P="2076"/>
                    </AMDPAR>
                    <AMDPAR>d. Redesignate paragraphs (f) and (g) as paragraphs (g) and (h);</AMDPAR>
                    <AMDPAR>e. Add paragraph (f);</AMDPAR>
                    <AMDPAR>f. Revise newly redesignated paragraph (g); and</AMDPAR>
                    <AMDPAR>g. Republish newly redesignated paragraph (h).</AMDPAR>
                    <P>The republications, revisions, and additions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 312.11</SECTNO>
                        <SUBJECT>Safe harbor programs.</SUBJECT>
                        <STARS/>
                        <P>
                            (b) 
                            <E T="03">Criteria for approval of self-regulatory program guidelines.</E>
                             Proposed safe harbor programs must demonstrate that they meet the following performance standards:
                        </P>
                        <STARS/>
                        <P>(2) An effective, mandatory mechanism for the independent assessment of subject operators' compliance with the self-regulatory program guidelines. At a minimum, this mechanism must include a comprehensive review by the safe harbor program, to be conducted not less than annually, of each subject operator's information privacy and security policies, practices, and representations.</P>
                        <STARS/>
                        <P>
                            (d) 
                            <E T="03">* * *</E>
                        </P>
                        <P>
                            (1) By [DATE SIX MONTHS AFTER PUBLICATION OF THE FINAL RULE IN THE 
                            <E T="04">FEDERAL REGISTER</E>
                            ], and annually thereafter, submit a report to the Commission that identifies each subject operator and all approved websites or online services, as well as any subject operators that have left the safe harbor program. The report must also contain, at a minimum:
                        </P>
                        <P>(i) A narrative description of the safe harbor program's business model, including whether it provides additional services such as training to subject operators;</P>
                        <P>(ii) Copies of each consumer complaint related to each subject operator's violation of a safe harbor program's guidelines;</P>
                        <P>(iii) An aggregated summary of the results of the independent assessments conducted under paragraph (b)(2) of this section;</P>
                        <P>(iv) A description of each disciplinary action taken against any subject operator under paragraph (b)(3) of this section, as well as a description of the process for determining whether a subject operator is subject to discipline; and</P>
                        <P>(v) A description of any approvals of member operators' use of a parental consent mechanism, pursuant to § 312.5(b)(4);</P>
                        <P>(2) Promptly respond to Commission requests for additional information; and</P>
                        <P>(3) * * *</P>
                        <P>(iii) Results of the independent assessments of subject operators' compliance required under paragraph (b)(2) of this section; and</P>
                        <P>
                            (4) No later than [DATE 90 DAYS AFTER PUBLICATION OF THE FINAL RULE IN THE 
                            <E T="04">FEDERAL REGISTER</E>
                            ], publicly post a list of all current subject operators on each of the approved safe harbor program's websites and online services. Approved safe harbor programs shall update this list every six months thereafter to reflect any changes to the approved safe harbor programs' subject operators or their applicable websites and online services.
                        </P>
                        <STARS/>
                        <P>
                            (f) 
                            <E T="03">Review of self-regulatory program guidelines.</E>
                             Every three years approved safe harbor programs shall submit to the Commission a report detailing the safe harbor program's technological capabilities and mechanisms for assessing subject operators' fitness for membership in the safe harbor program.
                        </P>
                        <P>
                            (g) 
                            <E T="03">Revocation of approval of self-regulatory program guidelines.</E>
                             The Commission reserves the right to revoke any approval granted under this section if at any time it determines that the approved self-regulatory program guidelines or their implementation do not meet the requirements of this part.
                        </P>
                        <P>
                            (h) 
                            <E T="03">Operators' participation in a safe harbor program.</E>
                             An operator will be deemed to be in compliance with the requirements of §§ 312.2 through 312.8 and 312.10 if that operator complies with Commission-approved safe harbor program guidelines. In considering whether to initiate an investigation or bring an enforcement action against a subject operator for violations of this part, the Commission will take into account the history of the subject operator's participation in the safe harbor program, whether the subject operator has taken action to remedy such non-compliance, and whether the operator's non-compliance resulted in any one of the disciplinary actions set forth in paragraph (b)(3) of this section.
                        </P>
                    </SECTION>
                    <AMDPAR>11. In § 312.12, revise paragraph (b) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 312.12</SECTNO>
                        <SUBJECT>Voluntary Commission approval processes.</SUBJECT>
                        <STARS/>
                        <P>
                            (b) 
                            <E T="03">Support for the internal operations of the website or online service.</E>
                             An interested party may file a written request for Commission approval of additional activities to be included within the definition of support for the internal operations of the website or online service. To be considered for approval, a party must provide a detailed justification why such activities should be deemed support for the internal operations of the website or online service, and an analysis of their potential effects on children's online privacy. The request shall be filed with the Commission's Office of the Secretary. The Commission will publish in the 
                            <E T="04">Federal Register</E>
                             a document seeking public comment on the request. The Commission shall issue a written determination within 120 days of the filing of the request.
                        </P>
                    </SECTION>
                    <SIG>
                        <P>By direction of the Commission.</P>
                        <NAME>Joel Christie,</NAME>
                        <TITLE>Acting Secretary.</TITLE>
                    </SIG>
                </SUPLINF>
                <FRDOC>[FR Doc. 2023-28569 Filed 1-10-24; 8:45 am]</FRDOC>
                <BILCOD>BILLING CODE 6750-01-P</BILCOD>
            </PRORULE>
        </PRORULES>
    </NEWPART>
    <VOL>89</VOL>
    <NO>8</NO>
    <DATE>Thursday, January 11, 2024</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="2077"/>
            <PARTNO>Part IV</PARTNO>
            <AGENCY TYPE="P">Department of Health and Human Services</AGENCY>
            <CFR>45 CFR Part 88</CFR>
            <HRULE/>
            <TITLE>Safeguarding the Rights of Conscience as Protected by Federal Statutes; Final Rule</TITLE>
        </PTITLE>
        <RULES>
            <RULE>
                <PREAMB>
                    <PRTPAGE P="2078"/>
                    <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                    <SUBAGY>Office of the Secretary</SUBAGY>
                    <CFR>45 CFR Part 88</CFR>
                    <RIN>RIN 0945-AA18</RIN>
                    <SUBJECT>Safeguarding the Rights of Conscience as Protected by Federal Statutes</SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Office for Civil Rights (OCR), Office of the Secretary, HHS.</P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Final rule</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>The Department of Health and Human Services (HHS or the Department) is issuing this final rule to partially rescind the May 21, 2019, final rule entitled, “Protecting Statutory Conscience Rights in Health Care; Delegations of Authority” (“2019 Final Rule”), while leaving in effect the framework created by the February 23, 2011, final rule entitled, “Regulation for the Enforcement of Federal Health Care Provider Conscience Protection Laws” (“2011 Final Rule”), which has been in effect continuously since March 25, 2011. Though the 2019 Final Rule never took effect, the Department also retains, with some modifications, certain provisions of the 2019 Final Rule regarding federal conscience protections, but eliminates others that are redundant or confusing, that undermine the clarity of the statutes Congress enacted to both safeguard conscience rights and protect access to health care, or because significant questions have been raised as to their legality.</P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>This rule is effective March 11, 2024.</P>
                    </EFFDATE>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P/>
                        <P>
                            <E T="03">Office for Civil Rights:</E>
                             David Christensen, Supervisory Policy Advisor, and Gabriela Weigel, Policy Advisor, HHS Office for Civil Rights, (202) 795-7830 or (800) 537-7697 (TDD), or via email at 
                            <E T="03">consciencerule@hhs.gov.</E>
                        </P>
                        <P>
                            <E T="03">Assistance to Individuals with Disabilities in Reviewing the Rulemaking Record:</E>
                             Upon request, the Department will provide an accommodation or auxiliary aid to an individual with a disability who needs assistance to review the comments or other documents in the public rulemaking record for the final rule. To schedule an appointment for this type of accommodation or auxiliary aid, please call (202) 795-7830 or (800) 537-7697 (TDD) for assistance or email 
                            <E T="03">consciencerule@hhs.gov.</E>
                        </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P/>
                    <HD SOURCE="HD1">Electronic Access</HD>
                    <P>
                        This 
                        <E T="04">Federal Register</E>
                         document is also available from the 
                        <E T="04">Federal Register</E>
                         online database through 
                        <E T="03">http://www.govinfo.gov,</E>
                         a service of the U.S. Government Publishing Office.
                    </P>
                    <HD SOURCE="HD1">Table of Contents</HD>
                    <EXTRACT>
                        <GPOTABLE COLS="2" OPTS="L0,tp0,p0,8/9,g1,t1,i1" CDEF="s200,4">
                            <TTITLE> </TTITLE>
                            <BOXHD>
                                <CHED H="1"> </CHED>
                                <CHED H="1"> </CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="22">Contents</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">I. Background</ENT>
                                <ENT>900</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">A. Statutory Background</ENT>
                                <ENT>900</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">B. Regulatory Background</ENT>
                                <ENT>907</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">C. Litigation</ENT>
                                <ENT>910</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">D. The Proposed Rule</ENT>
                                <ENT>911</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">II. Comments on the Proposed Rule </ENT>
                                <ENT>913</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">A. General Comments </ENT>
                                <ENT>914</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">B. Comments Addressing Sections 88.1-88.4 of the Proposed Rule </ENT>
                                <ENT>916</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">C. Comments Addressing the Proposed Rule's Requests for Comment </ENT>
                                <ENT>941</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">III. Statutory Authority </ENT>
                                <ENT>971</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">IV. Overview and Section-by-Section Description of the Final Rule</ENT>
                                <ENT>972</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">V. Regulatory Impact Analysis </ENT>
                                <ENT>975</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">A. Introduction</ENT>
                                <ENT>975</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">B. Requests for Comment</ENT>
                                <ENT>976</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">C. Detailed Economic Analysis </ENT>
                                <ENT>981</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">D. Summary of Impacts</ENT>
                                <ENT>989</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">E. Regulatory Flexibility Analysis </ENT>
                                <ENT>990</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Rule Text </ENT>
                                <ENT>993</ENT>
                            </ROW>
                        </GPOTABLE>
                    </EXTRACT>
                    <HD SOURCE="HD1">I. Background</HD>
                    <HD SOURCE="HD2">A. Statutory Background</HD>
                    <P>Several provisions of Federal law protect the conscience rights of certain federally funded health care entities and prohibit recipients of certain Federal funds from requiring individuals and entities to participate in actions they find religiously or morally objectionable. They include the following provisions:</P>
                    <HD SOURCE="HD3">The Church Amendments [42 U.S.C. 300a-7]</HD>
                    <P>The conscience provisions contained in 42 U.S.C. 300a-7 (collectively known as the “Church Amendments”) were enacted in the 1970s in response to debates over whether receipt of Federal funds required those recipients to perform abortion or sterilization procedures. The Church Amendments consist of five conscience provisions. The first provision, 42 U.S.C. 300a-7(b), provides that “[t]he receipt of any grant, contract, loan, or loan guarantee under [certain statutes implemented by the Department of Health and Human Services] by any individual or entity does not authorize any court or any public official or other public authority to require” (1) the individual to perform or assist in a sterilization procedure or an abortion, if it would be contrary to their religious beliefs or moral convictions; (2) the entity to make its facilities available for sterilization procedures or abortions, if the performance of sterilization procedures or abortions in the facilities is prohibited by the entity on the basis of religious beliefs or moral convictions; or (3) the entity to provide personnel for the performance or assistance in the performance of sterilization procedures or abortions, if it would be contrary to the religious beliefs or moral convictions of such personnel.</P>
                    <P>
                        The second provision, 42 U.S.C. 300a-7(c)(1), prohibits any entity that receives a grant, contract, loan, or loan guarantee under certain Department-implemented statutes from discriminating against any physician or other health care personnel in employment, promotion, termination of employment, or the extension of staff or other privileges because the individual “performed or assisted in the performance of a lawful sterilization procedure or abortion, because he refused to perform or assist in the performance of such a procedure or abortion on the grounds that his performance or assistance in the performance of the procedure or abortion would be contrary to his 
                        <PRTPAGE P="2079"/>
                        religious beliefs or moral convictions, or because of his religious beliefs or moral convictions respecting sterilization procedures or abortions.”
                    </P>
                    <P>The third provision, 42 U.S.C. 300a-7(c)(2), prohibits any entity that receives a grant or contract for biomedical or behavioral research under any program administered by the Department from discriminating against any physician or other health care personnel in employment, promotion, termination of employment, or extension of staff or other privileges “because he performed or assisted in the performance of any lawful health service or research activity, because he refused to perform or assist in the performance of any such service or activity on the grounds that his performance or assistance in the performance of such service or activity would be contrary to his religious beliefs or moral convictions, or because of his religious beliefs or moral convictions respecting any such service or activity.”</P>
                    <P>The fourth provision, 42 U.S.C. 300a-7(d), provides that “[n]o individual shall be required to perform or assist in the performance of any part of a health service program or research activity funded in whole or in part under a program administered by [the Department] if his performance or assistance in the performance of such part of such program or activity would be contrary to his religious beliefs or moral convictions.”</P>
                    <P>The fifth provision, 42 U.S.C. 300a-7(e), prohibits any entity that receives a grant, contract, loan, loan guarantee, or interest subsidy under certain Departmentally implemented statutes from denying admission to, or otherwise discriminating against “any applicant (including applicants for internships and residencies) for training or study because of the applicant's reluctance, or willingness, to counsel, suggest, recommend, assist, or in any way participate in the performance of abortions or sterilizations contrary to or consistent with the applicant's religious beliefs or moral convictions.”</P>
                    <HD SOURCE="HD3">Public Health Service Act Sec. 245, The Coats-Snowe Amendment [42 U.S.C. 238n]</HD>
                    <P>Enacted in 1996, section 245 of the Public Health Service Act (PHS Act) prohibits the Federal Government and any State or local governments receiving Federal financial assistance from discriminating against any health care entity on the basis that the entity (1) “refuses to undergo training in the performance of induced abortions, to require or provide such training, to perform such abortions, or to provide referrals for such training or such abortions;” (2) refuses to make arrangements for such activities; or (3) “attends (or attended) a post-graduate physician training program, or any other program of training in the health professions, that does not (or did not) perform induced abortions or require, provide, or refer for training in the performance of induced abortions, or make arrangements for the provision of such training.” For the purposes of this protection, the statute defines “financial assistance” as including “with respect to a government program,” “governmental payments provided as reimbursement for carrying out health-related activities.” In addition, PHS Act Sec. 245 requires that, in determining whether to grant legal status to a health care entity (including a State's determination of whether to issue a license or certificate), the federal government and any State or local governments receiving Federal financial assistance shall deem accredited any post-graduate physician training program that would be accredited, but for the reliance on an accrediting standard that, regardless of whether such standard provides exceptions or exemptions, requires an entity: (1) to perform induced abortions; or (2) to require, provide, or refer for training in the performance of induced abortions, or make arrangements for such training.</P>
                    <HD SOURCE="HD3">Medicaid and Medicare</HD>
                    <P>
                        The Medicaid and Medicare statutes also include certain conscience provisions. The Balanced Budget Act of 1997, Public Law 105-33, 111 Stat. 251 (1997), provides that Medicaid managed care-managed organizations and Medicare Advantage plans are not required to provide, reimburse for, or cover a counseling or referral service if the organization or plan objects to the service on moral or religious grounds. 
                        <E T="03">See id.</E>
                         40011852(j)(3)(B), 111 Stat. at 295 (codified at 42 U.S.C. 1395w-22(j)(3)(B)) (Medicare Advantage); 
                        <E T="03">id.</E>
                         § 4704(b)(3)(B), 111 Stat. at 496-97 (codified at 42 U.S.C. 1396u-2(b)(3)(B)) (Medicaid). The organization or plan must, however, provide sufficient notice of its moral or religious objections to prospective enrollees. 42 U.S.C. 1395w-22(j)(3)(B)(ii) (Medicare Advantage), 1396u-2(b)(3)(B)(ii) (Medicaid managed care).
                    </P>
                    <P>
                        These Medicare and Medicaid statutes also contain conscience provisions related to the performance of advanced directives. 
                        <E T="03">See</E>
                         42 U.S.C. 1395cc(f), 1396a(w)(3), and 14406(2). Additionally, they contain provisions related to religious nonmedical health care providers and their patients. 
                        <E T="03">See</E>
                         42 U.S.C. 1320a-1(h), 1320c-11, 1395i-5, 1395x(e), 1395x(y)(1), 1396a(a) and 1397j-1(b). For example, Congress prohibited States from excluding Religious Nonmedical Health Care Institutions (RNHCIs) from licensure through implementation of State definitions of “nursing home” and “nursing home administrator,” 42 U.S.C. 1396g(e), and Congress exempted RNHCIs from certain Medicaid requirements for medical criteria and standards. 42 U.S.C. 1396a(a) (exempting RNHCIs from 42 U.S.C. 1396a(a)(9)(A), 1396a(a)(31), 1396a(a)(33), and 1396b(i)(4)). Additionally, section 6703(a) of the Elder Justice Act of 2009 (Pub. L. 111-148, 124 Stat. 119) provides that Elder Justice and Social Services Block Grant programs may not interfere with or abridge an elder person's “right to practice his or her religion through reliance on prayer alone for healing,” when the preference for such reliance is contemporaneously expressed, previously set forth in a living will or similar document, or unambiguously deduced from such person's life history. 42 U.S.C. 1397j-1(b).
                    </P>
                    <HD SOURCE="HD3">The Weldon Amendment</HD>
                    <P>
                        The Weldon Amendment, originally adopted as section 508(d) of the Labor-HHS Division (Division F) of the 2005 Consolidated Appropriations Act, Public Law 108-447, 118 Stat. 2809, 3163 (Dec. 8, 2004), has been readopted (or incorporated) in each subsequent legislative measure appropriating funds to HHS. 
                        <E T="03">See, e.g.,</E>
                         Consolidated Appropriations Act, 2023, Public Law 117-328, div. H, title V General Provisions, section 507(d)(1) (Dec 29, 2022).
                    </P>
                    <P>
                        The Weldon Amendment provides that “[n]one of the funds made available in this Act [making appropriations for the Departments of Labor, Health and Human Services, and Education] may be made available to a Federal agency or program, or to a State or local government, if such agency, program, or government subjects any institutional or individual health care entity to discrimination on the basis that the health care entity does not provide, pay for, provide coverage of, or refer for abortions.” It also defines “health care entity” to include “an individual physician or other health care professional, a hospital, a provider-sponsored organization, a health maintenance organization, a health insurance plan, or any other kind of health care facility, organization, or plan.”
                        <PRTPAGE P="2080"/>
                    </P>
                    <HD SOURCE="HD3">The Affordable Care Act</HD>
                    <P>
                        Passed in 2010, the Patient Protection and Affordable Care Act (ACA), Public Law 111-148, 124 Stat. 119 (2010) (codified at 42 U.S.C. 18001, 
                        <E T="03">et seq.</E>
                        ), includes certain conscience provisions in sections 1553, 1303(b)(1)(A), (b)(4), and (c)(2)(A), and 1411(b)(5)(A).
                    </P>
                    <P>
                        Section 1553 prohibits the Federal government, any state or local government, and any health care provider that receives Federal funding under the ACA, or any health plan created under the ACA, from subjecting an individual or health care entity to discrimination on the ground that the individual or entity does not provide services for the purpose of causing or assisting in the death of any individual, including through assisted suicide, euthanasia, and mercy killing. 
                        <E T="03">See</E>
                         42 U.S.C. 18113(a). Section 1553 provides that the Department's Office for Civil Rights (“OCR”) will receive complaints of discrimination related to that section. 
                        <E T="03">Id.</E>
                         18113(d).
                    </P>
                    <P>
                        Section 1303(b)(1)(A) provides that issuers of qualified health plans shall determine whether or not the plan provides coverage of abortion services. 
                        <E T="03">Id.</E>
                         18023(b)(1)(A)(ii). Additionally, Section 1303(b)(4) states that “[n]o qualified health plan offered through an Exchange may discriminate against any health care provider or health care facility because of its unwillingness to provide, pay for, provide coverage of, or refer for abortions.” 
                        <E T="03">Id.</E>
                         18023(b)(4). Additionally, Section 1303(c) states that nothing in the ACA will be understood to preempt or otherwise effect State laws “regarding the prohibition of (or requirement of) coverage, funding, or procedural requirements on abortions, including parental notification or consent for the performance of an abortion on a minor,” 42 U.S.C. 18023(c)(1). Section 1303(c) also states that nothing in the ACA will be understood to have any effect on Federal laws that protect conscience; that regard the willingness or refusal to provide abortion; and that regard “discrimination on the basis of the willingness or refusal to provide, pay for, cover, or refer for abortion or to provide or participate in training to provide abortion.” 
                        <E T="03">Id.</E>
                         18023(c)(2). Section 1303(d) further states that “Nothing in this Act shall be construed to relieve any health care provider from providing emergency services as required by State or Federal law,” including the Emergency Medical Treatment and Labor Act. 
                        <E T="03">Id.</E>
                         18023(d).
                    </P>
                    <P>
                        Section 1411(b)(5)(A) addresses exemptions to the ACA's “individual responsibility requirement.” 42 U.S.C. 18081(b)(5)(A).
                        <SU>1</SU>
                        <FTREF/>
                         Under this section, the Department may grant exemptions based on hardship (which the Department has stated includes an individual's inability to secure affordable coverage that does not provide for abortions (84 FR 23172), membership in a particular religious organization, or membership in a “health care sharing ministry”).
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             In 2017 Congress effectively eliminated the penalty for noncompliance by reducing it to zero. 
                            <E T="03">See</E>
                             Tax Cuts and Jobs Act of 2017, Public Law 115-97, 11081, 131 Stat. 2092 (codified in 26 U.S.C. 5000A(c)).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Federal Conscience and Anti-Discrimination Protections Applying to Global Health Programs</HD>
                    <P>The Department administers certain programs under the President's Emergency Plan for AIDS Relief (PEPFAR), to which additional conscience protections apply. Specifically, recipients of foreign assistance funds for HIV/AIDS prevention, treatment, or care authorized by section 104A of the Foreign Assistance Act of 1961 (22 U.S.C. 2151b-2), 22 U.S.C. 7601-7682, or under any amendment made by the Tom Lantos and Henry J. Hyde United States Global Leadership Against HIV/AIDS, Tuberculosis, and Malaria Reauthorization Act of 2008 (Pub. L. 110-293), cannot be required, as a condition of receiving such funds, (1) to “endorse or utilize a multisectoral or comprehensive approach to combating HIV/AIDS,” or (2) to “endorse, utilize, make a referral to, become integrated with, or otherwise participate in any program or activity to which the organization has a religious or moral objection.” 22 U.S.C. 7631(d)(1)(B). The government cannot discriminate against such recipients in the solicitation or issuance of grants, contracts, or cooperative agreements for the recipients' refusal to do any such actions. 22 U.S.C. 7631(d)(2). In addition, recipients of foreign assistance funds under the Foreign Assistance Act of 1961 are prohibited from using those funds for performance or research respecting abortions or involuntary sterilization or to motivate or coerce any person to practice abortions or to coerce or provide any financial incentive to any person to undergo sterilization. 22 U.S.C. 2151b(f).</P>
                    <HD SOURCE="HD3">Exemptions From Compulsory Medical Screening, Examination, Diagnosis, or Treatment</HD>
                    <P>
                        Additional provisions relating to conscience have also been the subject of previous HHS rulemaking. These include provisions related to mental health treatment, hearing screening programs, vaccination programs, occupational illness testing, and compulsory health care services generally. First, under the Public Health Service Act, certain suicide prevention programs are not to be construed to require “suicide assessment, early intervention, or treatment services for youth” if their parents or legal guardians have religious or moral objections to such services. 42 U.S.C. 290bb-36(f); section 3(c) of the Garrett Lee Smith Memorial Act (Pub. L. 108-355, 118 Stat. 1404, reauthorized by Pub. L. 114-255 at sec. 9008). Second, authority to issue certain grants through the Health Resources and Services Administration (HRSA), Centers for Disease Control and Prevention (CDC), and the National Institutes of Health (NIH) may not be construed to preempt or prohibit State laws which do not require hearing loss screening for newborn, infants or young children whose parents object to such screening based on religious beliefs. 42 U.S.C. 280g-1(d). Third, in providing pediatric vaccines funded by Federal medical assistance programs, providers must comply with any State laws relating to any religious or other exemptions. 42 U.S.C. 1396s(c)(2)(B)(ii). Fourth, the provisions of the Occupational Safety and Health Act of 1970 are not to be construed to “authorize or require medical examination, immunization, or treatment for those who object thereto on religious grounds, except where such is necessary for the protection of the health or safety of others.” 29 U.S.C. 669(a)(5). Fifth, certain State and local child abuse prevention and treatment programs funded by HHS are not to be construed as creating a Federal requirement that a parent or legal guardian provide a child any medical service or treatment against the religious beliefs of that parent or legal guardian, 42 U.S.C. 5106i(a), and Medicaid and CHIP programs are not to be construed to require a State to compel a person to undergo medical screenings, examination, diagnosis, treatment, health care or services if a person objects on religious grounds, with limited exceptions, 42 U.S.C. 1396(f). Additionally, the Child Abuse Prevention and Treatment Act (CAPTA) specifies that it does not require (though it also does not prevent) a State finding of child abuse or neglect in cases in which a parent or legal guardian relies solely or partially upon spiritual means rather than medical treatment, in accordance with religious beliefs. 42 U.S.C. 5106i(a)(2).
                        <PRTPAGE P="2081"/>
                    </P>
                    <HD SOURCE="HD2">B. Regulatory Background</HD>
                    <P>No statute requires the promulgation of rules to implement the conscience provisions outlined above. On August 26, 2008, however, the Department exercised its discretion and issued a proposed rule entitled “Ensuring that Department of Health and Human Services Funds Do Not Support Coercive or Discriminatory Policies or Practices in Violation of Federal Law” (73 FR 50274) (2008 Final Rule) to address the conscience provisions in effect at that time. In the preamble to the 2008 Final Rule, the Department concluded that regulations were necessary in order to:</P>
                    <EXTRACT>
                        <P>1. Educate the public and health care providers on the obligations imposed, and protections afforded, by Federal law;</P>
                        <P>2. Work with state and local governments and other recipients of funds from the Department to ensure compliance with the nondiscrimination requirements embodied in the Federal health care provider conscience protection statutes;</P>
                        <P>3. When such compliance efforts prove unsuccessful, enforce these nondiscrimination laws through the various Department mechanisms, to ensure that Department funds do not support coercive or discriminatory practices, or policies in violation of Federal law; and</P>
                        <P>4. Otherwise take an active role in promoting open communication within the health care industry, and between providers and patients, fostering a more inclusive, tolerant environment in the health care industry than may currently exist.</P>
                    </EXTRACT>
                    <FP>“Ensuring That Department of Health and Human Services Funds Do Not Support Coercive or Discriminatory Policies or Practices in Violation of Federal Law,” 73 FR 78072, 78074.</FP>
                    <P>The rule went into effect on January 20, 2009, except for a certification requirement that never took effect, as it was subject to the information collection approval process under the Paperwork Reduction Act, which was never completed.</P>
                    <P>On March 10, 2009, the Department proposed rescinding, in its entirety, the 2008 Final Rule, and sought public comment to determine whether or not to rescind the 2008 Final Rule in part or in its entirety (74 FR 10207). On February 23, 2011, the Department issued a final rule entitled “Regulation for the Enforcement of Federal Health Care Provider Conscience Protection Laws” (2011 Final Rule) (76 FR 9968). Concluding that parts of the 2008 Final Rule were unclear and potentially overbroad in scope, the 2011 Final Rule rescinded much of the 2008 Final Rule, including provisions defining certain terms used in one or more of the conscience provisions and requiring entities that received Department funds, both as recipients and subrecipients, to provide a written certificate of compliance with the 2008 Final Rule. The 2011 Final Rule retained a provision designating OCR to receive and coordinate the handling of complaints of violations of the three conscience provisions that were the subject of the 2008 Final Rule: the Church Amendments, the Weldon Amendment, and the Coats-Snowe Amendment.</P>
                    <P>On January 26, 2018, the Department issued a new proposed rule entitled “Protecting Statutory Conscience Rights in Health Care; Delegations of Authority” (83 FR 3880) (2018 proposed rule). Citing a desire to “enhance the awareness and enforcement of Federal health care conscience and associated nondiscrimination laws, to further conscience and religious freedom, and to protect the rights of individuals and entities to abstain from certain activities related to health care services without discrimination or retaliation,” the 2018 proposed rule proposed reinstating several rescinded provisions of the 2008 Final Rule, while also expanding upon that rule in a number of respects. Among other things, the 2018 proposed rule added a number of additional statutes and a detailed provision that would apply to alleged violations of any of the statutes covered by the rule.</P>
                    <P>In response to the 2018 proposed rule, the Department received over 242,000 comments from a wide variety of individuals and organizations, health care providers, faith-based organizations, patient advocacy groups, professional organizations, universities and research institutions, consumer organizations, and State and Federal agencies and representatives. Comments dealt with a range of issues surrounding the proposed rule, including the Department's authority to issue the rule, the need for the rule, what kinds of workers would be protected by the proposed rule, the rule's relationship to Title VII of the Civil Rights Act and other statutes and protections, what services are covered by the rule, whether the regulation might be used to discriminate against patients, how the rule would affect access to care, legal arguments, and the cost impacts and public health consequences of the rule.</P>
                    <P>On May 21, 2019, the Department issued a final rule (84 FR 23170) (2019 Final Rule). The Department concluded that the withdrawal of the 2008 Final Rule had created confusion about the various conscience provisions, citing what the Department determined was a significant increase in complaints alleging violations of a conscience provision that it had received since November 2016. The Department consequently reinstated the 2008 Final Rule while revising and expanding on its provisions, including by (1) adding additional statutory provisions to the rule's enforcement scheme; (2) adopting definitions of various statutory terms; (3) imposing assurance and certification requirements; (4) reaffirming OCR's enforcement authority; (5) imposing record-keeping and cooperation requirements; (6) establishing enforcement provisions and penalties; and (7) adopting a voluntary notice provision.</P>
                    <HD SOURCE="HD2">C. Litigation</HD>
                    <P>
                        Following issuance of the 2019 Final Rule, a number of States, localities, and non-governmental parties filed lawsuits challenging the rule in the Southern District of New York, the Northern District of California, the Eastern District of Washington, and the District of Maryland. Before the rule took effect, the New York, California, and Washington district courts granted summary judgment to the respective plaintiffs and vacated the rule in its entirety nationwide. 
                        <E T="03">See Washington</E>
                         v. 
                        <E T="03">Azar,</E>
                         426 F. Supp. 3d 704 (E.D. Wash. 2019), 
                        <E T="03">appeal pending,</E>
                         No. 20-35044 (9th Cir.); 
                        <E T="03">San Francisco</E>
                         v. 
                        <E T="03">Azar,</E>
                         411 F. Supp. 3d 1001 (N.D. Cal. 2019), 
                        <E T="03">appeal pending,</E>
                         Nos. 20-15398 et al. (9th Cir.); 
                        <E T="03">New York</E>
                         v. 
                        <E T="03">HHS,</E>
                         414 F. Supp. 3d 475 (S.D.N.Y. 2019), 
                        <E T="03">appeal dismissed without prejudice,</E>
                         Nos. 19-4254 et al. (2d Cir.).
                    </P>
                    <P>The courts' rationales for vacating the 2019 Final Rule were not identical, but each concluded that the rule was defective in a number of respects. One or more courts held that the 2019 Final Rule: (i) exceeded the Department's authority; (ii) was inconsistent in certain respects with the conscience statutes or other statutes, including the Emergency Medical Treatment &amp; Labor Act (EMTALA) and Title VII of the Civil Rights Act; (iii) was arbitrary and capricious in its evaluation of the record, its treatment of the Department's conclusions underlying the 2011 Final Rule and reliance interests of funding recipients, and its consideration of certain issues relating to access to care and medical ethics raised by commenters; (iv) contained a particular definitional provision that was not promulgated in compliance with the notice-and-comment requirements of the Administrative Procedure Act (APA); and (v) had penalties for non-compliance with conscience provisions that violated the separation of powers and the Spending Clause.</P>
                    <P>
                        Because the 2019 Final Rule never took effect: (1) HHS has been 
                        <PRTPAGE P="2082"/>
                        continuously operating under the 2011 Final Rule; (2) HHS currently accepts, investigates, and processes complaints under the framework created by the 2011 Final Rule; (3) There are no significant reliance interests stemming from the 2019 Final Rule; (4) No person or entity could have therefore reasonably relied on the 2019 Final Rule's provisions; and (5) Health care providers or individuals have continuously and reasonably relied on the 2011 Final Rule because it has remained operational throughout.
                    </P>
                    <HD SOURCE="HD2">D. The Proposed Rule</HD>
                    <P>On January 5, 2023, the Department issued a notice of proposed rulemaking entitled, “Safeguarding the Rights of Conscience as Protected by Federal Statutes.” 88 FR 820 (2023 proposed rule). The Department proposed to partially rescind the 2019 Final Rule entitled “Protecting Statutory Conscience Rights in Health Care; Delegations of Authority,” 84 FR 23170 (May 21, 2019) by: (1) leaving in effect the framework created by the 2011 Final Rule (76 FR 9968) and (2) retaining, with some modifications, certain provisions of the 2019 Final Rule. The Department solicited public comment to aid in its proposed rulemaking, specifically seeking comments addressing the following:</P>
                    <P>1. Information, including specific examples where feasible, addressing the scope and nature of the problems giving rise to the need for rulemaking, and whether those problems could be addressed by different regulations than those adopted in 2019 or by sub-regulatory guidance;</P>
                    <P>2. Information, including specific examples where feasible, supporting or refuting allegations that the 2019 Final Rule hindered, or would hinder, access to information and health care services, particularly sexual and reproductive health care and other preventive services;</P>
                    <P>3. Information, including specific examples where feasible, regarding complaints of discrimination on the basis that an individual or health care entity did not provide services for the purpose of causing or assisting in the death of any individual, including through assisted suicide, euthanasia, and mercy killing, as described in section 1553 of the ACA, and comments on whether additional regulations under this authority are necessary;</P>
                    <P>4. Information, including specific examples where feasible, regarding complaints of discrimination by a qualified health plan under the ACA on the basis that a health care provider or facility refused to provide, pay for, cover, or refer for abortions, as described in section 1303 of the ACA and comments on whether additional regulations under this authority are necessary;</P>
                    <P>5. Information, including specific examples where feasible, from health care providers regarding alleged violations of the conscience provisions provided for in the Medicaid and Medicare statutes, including the provisions codified at 42 U.S.C. 1320a-1(h), 1320c-11, 1395i-5, 1395w-22(j)(3), 1395x(e), 1395x(y)(1), 1395cc(f), 1396a(a), 1396a(w)(3), 1396u-2(b)(3), 1397j-1(b), and 14406(2) and comments on whether additional regulations under these authorities are necessary;</P>
                    <P>6. Information, including specific examples where feasible, regarding alleged violations of any of the other authorities that appeared in the 2019 Final Rule but not the 2011 Final Rule;</P>
                    <P>7. Comment on whether the 2019 Final Rule provided sufficient clarity to minimize the potential for harm resulting from any ambiguity and confusion that may exist because of the rule, and whether any statutory terms require additional clarification;</P>
                    <P>8. Comment on whether the provisions added by the 2019 Final Rule are necessary, collectively or with respect to individual provisions, to serve the statutes' or the rule's objectives, including with regard to whether the Department accurately evaluated the need for additional regulation in the 2019 Final Rule, and whether those provisions should be modified, or whether the rule's objectives may also be accomplished through alternative means, such as outreach and education;</P>
                    <P>9. Comment on the proposal to retain a voluntary notice provision, including comments on whether such notice should be mandatory, and what a model notice should include; and</P>
                    <P>10. Comment on the proposal to retain portions of the 2019 Final Rule's enforcement provisions in the proposed § 88.2.</P>
                    <HD SOURCE="HD1">II. Comments on the Proposed Rule</HD>
                    <P>The Department received more than 48,000 comments addressing the 2023 proposed rule. A wide range of individuals and organizations submitted comments, including private citizens, health care workers and institutions, faith-based organizations, patient advocacy groups, civil rights organizations, professional associations, state and local government and elected officials, and members of Congress. These comments covered a variety of issues and points of view responding to the Department's requests for comments, and the Department reviewed and analyzed all of the comments. Most commenters supported the Department's proposed rule. The overwhelming majority of comments were individual comments associated with form letter campaigns from various groups and individuals.</P>
                    <P>Numerous commenters, including civil rights organizations, health organizations, legal associations, and individual commenters, supported the proposed rule as written, while some commenters, including some faith-based organizations, supported the proposed rule as an improvement over the 2011 Final Rule. Some others supportive of the proposed rule, including certain legal associations, faith-based organizations, and individual commenters, requested the Department incorporate additional provisions from the 2019 Final Rule that were not at issue in the litigation over that rule. Still other commenters said they generally supported the proposal to rescind the 2019 Final Rule.</P>
                    <P>Commenters also expressed opposition to the proposed rule for a variety of reasons. Numerous commenters, including some non-profits, legal organizations, faith-based organizations, and individuals opposed this rule because they would like the Department to retain the 2019 Final Rule. Other commenters, including a professional health care organization, a legal organization, and a local Department of Health, opposed the proposed rule on the grounds that they would like the Department to return to the 2011 Final Rule completely. Numerous commenters said they believed that the proposed rule would remove conscience protections, undermine the diversity of views in health care, and cause health care professionals to exit the profession.</P>
                    <P>The Department thanks commenters for sharing their views on the proposed rule. Because the 2019 Final Rule never went into effect, the 2011 Final Rule has been in effect since its enactment. This final rule builds on the 2011 Final Rule and does not remove provisions from it. The Department therefore disagrees that employees would decide to leave the workforce in response to this final rule. The Department responds in greater detail in the following sections to comments requesting additions to the proposed rule text and other comments raising specific points of support for or opposition to this rule.</P>
                    <P>
                        This final rule responds to comments as follows. Subpart A addresses comments expressing concern over access to care; Subpart B addresses comments received on specific sections 
                        <PRTPAGE P="2083"/>
                        of the proposed rule; and Subpart C addresses comments in response to the Department's requests for comments in the proposed rule.
                    </P>
                    <HD SOURCE="HD2">A. General Comments</HD>
                    <HD SOURCE="HD3">Concerns Over Access to Care</HD>
                    <P>
                        <E T="03">Comment:</E>
                         The Department received numerous comments that raised concerns over access to health care generally. For example, commenters, including reproductive health organizations and major professional health care associations, discussed the negative impact that refusals of care have on people of certain genders, sexes, ages, or races, and individuals with disabilities. The commenters further explained that these refusals exist against the backdrop of barriers many patients already face, especially among Black, Indigenous, and other people of color. These disparities are heightened for individuals living in rural areas, religious minorities, and people with disabilities. Some commenters said that conscience-based refusals to provide certain forms of health care block access to such care and endanger patient's lives. Many reproductive health organizations, individuals and other commenters, discussed the impact on reproductive health care after 
                        <E T="03">Dobbs vs. Jackson Women's Health Organization,</E>
                         142 S. Ct. 2228 (2022), and the confusion for providers and patients that they contended that decision caused, especially in states that have banned, or attempted to ban, abortion. Commenters gave various examples of pregnant women being denied medical treatment for miscarriage management and sterilization procedures. Others were denied, or delayed in obtaining, medications, including emergency contraception. Many commenters, including reproductive health groups, reported that women were forced to wait extended periods or travel across state lines to obtain health care.
                    </P>
                    <P>Others said conscience-based refusals to provide certain kinds of care have negatively impacted the LGBTQI+ community, especially older LGBTQI+ adults. Many of these commenters also cited what they said were specific examples of such denials of care that constituted discrimination against LGBTQI+ individuals, including patients being shamed by doctors for taking pre-exposure prophylaxis (PrEP) medication; denials of gender-affirming care at hospitals; denials of emergency room care; refusals to provide prescription refills for gender dysphoria medication by pharmacists; and refusals of requests from persons with HIV to process lab specimens. Also, a professional health care organization urged the Department to ensure that its efforts to protect conscience not further reduce availability of abortion care, especially in areas where providers retain the ability under state law to provide those services. The organization recommended that while HHS permits individual providers to abide by their conscience, providers should do so in a way that is consistent with patients' immediate needs.</P>
                    <P>
                        <E T="03">Response:</E>
                         The Department thanks commenters for sharing this information. The Department is committed to protecting access to health care and protecting conscience rights as set forth in Federal statutes.
                        <SU>2</SU>
                        <FTREF/>
                         OCR works to advance access to health care by enforcing federal civil rights laws, the Health Insurance Portability and Accountability Act (HIPAA) Privacy, Security, and Breach Notification Rules, the Patient Safety Act and Rule, and Federal health care conscience statutes, which together protect fundamental rights of nondiscrimination, health information privacy, and conscience. The Federal health care conscience protection statutes represent Congress' attempt to strike a careful balance between maintaining access to health care on the one hand and honoring religious beliefs and moral convictions on the other.
                        <SU>3</SU>
                        <FTREF/>
                         Some doctors, nurses, and hospitals, for example, object for religious or moral reasons to providing or referring for abortions or assisted suicide, among other procedures. Respecting such objections honors liberty and human dignity. Patients also have rights and health needs, sometimes urgent ones. The Department will continue to respect the balance Congress struck, work to ensure individuals understand their conscience rights, and enforce the law.
                    </P>
                    <FTNT>
                        <P>
                            <SU>2</SU>
                             
                            <E T="03">See</E>
                             “Nondiscrimination in Health Programs and Activities,” 87 FR 47824 (Aug. 4, 2022).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>3</SU>
                             See lengthier discussion of this principle on pages 40-41, below.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">B. Comments Addressing §§ 88.1-88.4 of the Proposed Rule</HD>
                    <HD SOURCE="HD3">1. Comments Addressing § 88.1</HD>
                    <HD SOURCE="HD3">General Support and Opposition</HD>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters including some non-profit, legal, and faith-based organizations, supported the inclusion of the statutory authorities contained in § 88.1 of the 2019 Final Rule, and that are maintained in the proposed rule, because their inclusion provides clarity and awareness of the various conscience protections and ensures all federal conscience protections follow one clear and transparent process.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department appreciates the commenters' views. We will finalize and include in this final rule all the authorities providing for conscience protections that were contained in the 2019 Final Rule.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Two reproductive health groups stated that the proposed rule properly relies on HHS's Housekeeping Authority under 5 U.S.C. 301 to create internal processes and guidelines “rather than impose substantial burdens on those regulated by the Church, Coats-Snowe, and Weldon Amendments, which HHS lacks the authority to do.” Another commenter argued that the Department's interpretation of the Federal conscience statutes is not entitled to deference given that “nothing in the Church, Coats-Snowe, and Weldon Amendments suggest that HHS is `charged with administering' them.” Other individual commenters noted that the 2019 Final Rule was justified under the Housekeeping Authority. Two commenters suggested that, in order to be consistent in noting the limited nature of the Housekeeping Authority for this rule, the Department must rescind other rules that exceed the bounds of that authority.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department thanks the commenters for their views on the scope of the Department's authority, including under the Housekeeping Authority. The Department agrees that it is authorized under its Housekeeping Authority, 5 U.S.C. 301, to establish internal processes for handling complaints raised under the conscience statutes. HHS is obligated to ensure compliance with these statutes because they apply to certain HHS programs and specific funding streams that HHS is expressly charged with administering.
                        <SU>4</SU>
                        <FTREF/>
                         Finally, whether any HHS rules outside of the context of the rulemakings for the Federal conscience statutes should be rescinded as beyond the Housekeeping Authority is beyond the scope of this rulemaking.
                    </P>
                    <FTNT>
                        <P>
                            <SU>4</SU>
                             For example, 42 U.S.C. 300a-7(b) regards the receipt of Public Health Service Act funds which are administered by HHS agencies such as the Substance Abuse and Mental Health Services Administration (SAMHSA), the Agency for Healthcare Research and Quality (AHRQ), and the National Institutes of Health (NIH)); 42 U.S.C. 280g-1(d) regards funds for hearing screening which are awarded through the Health Resources and Services Administration (HRSA); 42 U.S.C. 1395w-22(j)(3)(B) and 1396u-2(b)(3)(B) are rules of construction expressly applying to Medicare Advantage and Medicaid Managed Care Organizations which the Department oversees through the Centers for Medicare and Medicaid Services (CMS).
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters, including professional health care 
                        <PRTPAGE P="2084"/>
                        organizations and a local governmental entity, expressed opposition to the inclusion of statutes in the 2019 Final Rule that were not in the 2011 Final Rule.
                        <SU>5</SU>
                        <FTREF/>
                         The commenters argued: (1) HHS does not adequately justify why it is necessary to reference these statutes; (2) including these statutes will have negative consequences, such as undermining patients' access to medical care and information, imposing barriers to physicians' and health care institutions' ability to provide treatment, legitimizing discrimination against underserved and vulnerable patients, especially as regards abortion and gender-affirming care, and creating confusion and uncertainty among physicians, other health care professionals, and health care institutions about their legal and ethical obligations to treat patients; (3) HHS has not demonstrated that the public lacks awareness about these statutes; and (4) no influx of relevant complaints justifies the inclusion of the statutes. Another commenter noted that many of the conscience provisions have not been traditionally overseen by OCR, meaning they do not share the well-developed body of legal guidance applicable to civil rights complaints and it is therefore unclear which, if any, of the traditional safeguards for civil rights complainants, such as anti-retaliation protection, are available to complainants that refuse to engage in certain activities due to their religious or moral beliefs. Another commenter suggested HHS should not frame the statutes as conscience statutes and instead “accurately describe the scope of possible exemptions, including both religious and secular exemptions” or remove certain provisions from the rule. For example, 42 U.S.C. 18081 covers individuals seeking an exemption “as an Indian, or as an individual eligible for a hardship exemption”; 22 U.S.C. 7631 prevents aid from being provided with a condition that the recipient “endorse or utilize a multisectoral or comprehensive approach to combating HIV/AIDS”; 29 U.S.C. 669 prevents that chapter from being “deemed to authorize or require medical examination.”
                    </P>
                    <FTNT>
                        <P>
                            <SU>5</SU>
                             The statutes added by the 2019 Final Rule and retained in this final rule are: 42 U.S.C. 18113; 42 U.S.C. 14406(1)) 26 U.S.C. 5000A; 42 U.S.C. 18081; 42 U.S.C. 18023(b)(1)(A) and (b)(4); 42 U.S.C. 1395w-22(j)(3)(B) and 1396u-2(b)(3)(B); 42 U.S.C. 1395cc(f), 1396a(w)(3), and 14406(2); 22 U.S.C. 7631(d); 22 U.S.C. 2151b(f), see, 
                            <E T="03">e.g.,</E>
                             the Consolidated Appropriations Act, 2019, Public  Law 116-6, Div. F, sec. 7018 (the “Helms, Biden, 1978, and 1985 Amendments”); 42 U.S.C. 1396f and 5106i(a); 42 U.S.C. 280g-1(d); 29 U.S.C. 669(a)(5); 42 U.S.C. 1396s(c)(2)(B)(ii); 42 U.S.C. 290bb-36(f); 42 U.S.C. 1320a-1(h), 1320c-11, 1395i-5, 1395x(e), 1395x(y)(1), 1396a(a), and 1397j-1(b)). 84 FR 23170, 23170 (May 2019).
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Response:</E>
                         The Department appreciates the concerns raised by commenters. First, the Department notes that this rule clarifies the Department's processes for handling the Federal health care conscience statutes. Second, the Department agrees that access to health care is a significant concern, especially for patients with urgent health care needs or marginalized populations whose care is facing restrictions across the country. As stated in the proposed rule, the Federal health care conscience protection statutes represent Congress' attempt to strike a careful balance. The Department is obligated to ensure compliance with the Federal conscience statutes set forth in this rule and is committed to doing so. At the same time, the Department, through OCR, also enforces civil rights laws that prohibit recipients of HHS federal financial assistance from discriminating on the basis of race, color, national origin, disability, age, sex, and religion in the provision of health care services. In addition to exhibiting the Department's commitment to patient access to care, this guidance is an example of OCR's role in coordinating compliance across various authorities. As explained in the proposed rule, retaining these provisions as part of the rule, and maintaining OCR as the centralized HHS office tasked with receiving and investigating complaints under these provisions, is consistent with OCR's existing role and delegations and will aid the public by: (1) increasing awareness of the rights protected by the various statutes, and (2) providing clear direction on where to file complaints alleging violations of those rights, even where the public is already aware of these authorities. Rather than requiring an affected party to determine which HHS component was responsible for the stream of funding connected to a potential problem, and how to raise their concerns, the rule creates a single intake point for anyone who believes their federally protected conscience rights may have been violated in the context of HHS programs. The Department disagrees that it should not retain the additional conscience statutes from the 2019 Final Rule in this final rule.
                    </P>
                    <P>
                        In addition, the Department disagrees that 42 U.S.C. 18081, 22 U.S.C. 7631(d), and 29 U.S.C. 669(a)(5) are unrelated to conscience and do not belong in this rule. As with each of the other Federal health care conscience statutes, each of the provisions referenced by the commenter provides exemptions for or prohibits discrimination based on an individual or entity's religious or moral (or other) objection to a health care method or service. First, as noted in the proposed rule, 42 U.S.C. 18081(b)(5)(A) addresses exemptions to the ACA's “individual responsibility requirement.” 
                        <SU>6</SU>
                        <FTREF/>
                         Under this section, the Department may grant exemptions based on hardship, which the Department has stated includes an individual's inability to secure affordable coverage that does not provide for abortions (84 FR 23172), membership in a particular religious organization, or membership in a “health care sharing ministry.” Second, the provisions at 22 U.S.C. 7631(d) state that a faith-based organization or other organization is not required in order to receive such assistance to “endorse or utilize a multisectoral or comprehensive approach to combating HIV/AIDS;” or “endorse, utilize, make a referral to, become integrated with, or otherwise participate in any program or activity to which the organization has a religious or moral objection.” Finally, the relevant provision at 29 U.S.C. 669(a)(5) clarifies that nothing in that chapter will be deemed to “authorize or require medical examination, immunization, or treatment for those who object thereto on religious grounds.” The text of these statutes makes it clear that these provisions relate to protections for conscience, and so the Department declines to remove them from this rule.
                    </P>
                    <FTNT>
                        <P>
                            <SU>6</SU>
                             In 2017 Congress effectively eliminated the penalty for noncompliance by being reducing it to zero. 
                            <E T="03">See</E>
                             Tax Cuts and Jobs Act of 2017, Public  Law 115-97, 11081, 131 Stat. 2092 (codified in 26 U.S.C. 5000A(c)).
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters, including a health care organization, requested that the Department ensure the conscience statutes are properly enforced even in the context of enforcing other recent proposed HHS regulations, such as the Section 1557 notice of proposed rulemaking, 87 FR 47824, so that there is not an increase in instances where religious adherents are required to engage in conduct that violates their religious beliefs. These commenters suggested that the Department clarify how they planned to enforce the conscience statutes in light of these other regulations.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The final rule will maintain the general framework that OCR has been employing since 2011—enforcing the listed conscience statutes on a case-by-case basis, which respects the balance Congress sought to achieve through these statutes. The Section 1557 proposed rule is beyond the scope of this rulemaking. We note, however, that the proposed rule for Section 1557, for 
                        <PRTPAGE P="2085"/>
                        example, contains its own religious and conscience exemption process at proposed § 92.302 for how to raise such claims in the context of that rulemaking, 87 FR 47885-47886.
                    </P>
                    <HD SOURCE="HD3">Requests for Technical Changes</HD>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters, including members of Congress, stated § 88.1's list of citations is incomplete without additional context like that provided in the 2019 Final Rule, making it harder for covered entities to have a full understanding of the implications of the law and how they will be applied and enforced. These commenters suggest that the rule “should include the full list of laws with their applicability, requirements, and prohibitions explained, as included in the 2019 rule at 88.3.” A commenter argued it would be unlawful for HHS not to retain language from § 88.1 of the 2019 Final Rule, given this rule's purpose of protecting conscience rights and preventing non-discrimination.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department thanks the commenters for their views. We have added explanatory text to the preamble of this final rule to elaborate on the full list of the laws included in this final rule. However, we are finalizing this rule without the additional information drawn from § 88.3 of the 2019 Final Rule because, in the Department's view, that explanatory language is not necessary to accomplish the goal of this section, namely clarifying which conscience statutes OCR enforces. We have added the full list of the laws covered by this final rule in the model notice. Additionally, the Department maintains information about the Federal conscience statutes on OCR's website, and has included a link to this web page in the model notice text in Appendix A of this final rule.
                        <SU>7</SU>
                        <FTREF/>
                         Moreover, a purpose provision similar to § 88.1 of the 2019 Final Rule is unnecessary given the procedural nature of this final rule. We note in this regard that the court in 
                        <E T="03">New York</E>
                         v. 
                        <E T="03">U.S. Dep't of Health &amp; Human Servs.,</E>
                         414 F. Supp. 3d 475, 513-14, 523 (S.D.N.Y. 2019), cited language used in the purpose provision of § 88.1 of the 2019 Final Rule in support of its view that that rule was substantive.
                    </P>
                    <FTNT>
                        <P>
                            <SU>7</SU>
                             
                            <E T="03">See</E>
                             U.S. Dep't of Health and Human Servs., Off. for Civil Rights, 
                            <E T="03">Conscience and Religious Nondiscrimination, https://www.hhs.gov/conscience/conscience-protections/index.html.</E>
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Comment:</E>
                         Two commenters requested that the Department correct an error in the preamble of the proposed rule that improperly paraphrased a provision of Section 1303 of the ACA, 42 U.S.C. 18023. The commenters pointed out that, when paraphrasing one provision of Section 1303 of the ACA, 42 U.S.C. 18023(c)(1), the language in the proposed rule did not mirror the language of the statute because the NPRM stated the provision discussed preemption of state laws about conscience, rather than lack of preemption of certain state laws about abortion.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         OCR has made the noted corrections. Section 1303(c)(1) states that “Nothing in this Act shall be construed to preempt or otherwise have any effect on State laws regarding the prohibition of (or requirement of) coverage, funding, or procedural requirements on abortions, including parental notification or consent for the performance of an abortion on a minor.” 42 U.S.C. 18203(c)(1). The preamble of the final rule uses that language.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter suggested that § 88.1 should explicitly state that the Department's goal is to balance the interests of providers and patients. Another commenter argued that the freedom of conscience and religion should not be extended to facilities or institutions, such as hospital systems or universities, but only to individual providers.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department maintains that Congress sought to balance provider and patient rights through a variety of statutes and, as we noted in the proposed rule, the Department respects that balance. The Department declines to make changes to the final rule recommended by the commenter but discusses the issue of balancing these rights in greater detail in response to other comments 
                        <E T="03">infra</E>
                         at pages 42-43. Finally, regarding facilities or institutions, the Department will refer to each individual conscience statute in determining whether a particular statute applies to a particular entity.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Noting that some of the statutory provisions do not apply to only health care providers, a commenter suggested changing the collective reference to the statutory authorities in § 88.1 and throughout the rule from “health care provider conscience protection statutes” to “health care conscience statutory protections.”
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department agrees with the commenter's concern. For example, 42 U.S.C. 280g-1(d) protects parents of newborns, infants, and young children who object to hearing screenings based on religious beliefs. Likewise, 29 U.S.C. 669(a)(5) protects employees who object to “medical examination, immunization, or treatment . . . on religious grounds.” The Department will revise this provision in the final rule to refer to the statutes as the “Federal health care conscience protection statutes.”
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter requested that reference be made to 42 U.S.C. 1395x(ss) within the reference to “certain Medicare and Medicaid provisions” in the list of statutory authorities in § 88.1.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         OCR has been delegated multiple authorities that relate to protecting Religious Nonmedical Health Care Institutions (RNHCIs), five of which reference 42 U.S.C. 1395x(ss)(1), which defines RNHCIs. Section 1395x(ss)(1) contains the definition of RNHCIs, Section 1395x(ss)(2) covers accreditation of RNHCIs, and Section 1395x(ss)(3) contains a conscience provision that restricts the Secretary from requiring patients of RNHCIs to undergo certain medical services, such as medical screenings and treatment, against their religious beliefs, or from requiring RNHCIs and their personnel from undergoing medical supervision, regulation, or control, against their religious beliefs. Section 1395x(ss) was not delegated to OCR in the 2018 proposed rule's Delegations of Authority.
                        <SU>8</SU>
                        <FTREF/>
                         The Department declines to include 1395x(ss) in this final rule but is taking this comment under consideration outside this rulemaking process.
                    </P>
                    <FTNT>
                        <P>
                            <SU>8</SU>
                             “Protecting Statutory Conscience Rights in Health Care; Delegations of Authority,” 83 FR 3880, 3901 (Jan. 26, 2018)
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2. Comments Addressing § 88.2</HD>
                    <HD SOURCE="HD3">Requests for Clarification</HD>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters, including legal organizations and reproductive health groups, asked OCR to clarify that its enforcement authority is limited to existing provisions—such as those in the proposed rule and HHS's Uniform Administrative Requirements (UAR)—and clarify that it is not creating new mechanisms under this provision. Many commenters asked for clarification regarding the terms “relevant funding” and “appropriate action,” as well as the scope of the terms regarding violations of the proposed rule. Specifically, some commenters urged HHS to clarify that “appropriate action” relates to the enforcement tools of existing regulations (such as the UAR) and suggested establishing a limiting principle for “relevant funding” so that it cannot include all the funds available to an entity.
                    </P>
                    <P>
                        One commenter expressed support for the proposed rule because they believed it removed the authority to initiate compliance reviews, make enforcement referrals to the Department of Justice, 
                        <PRTPAGE P="2086"/>
                        and claw back relevant funding. The commenter argued that these enforcement tools went beyond the existing regulations for enforcement that should be used when handling and investigating complaints. Another commenter indicated that in their view, proposed § 88.2(a)(4) in conjunction with proposed § 88.2(d) removes OCR's ability to undertake involuntary enforcement measures. The commenter approved of this perceived change and what they understood in the proposed rule to be a clarification that enforcement will be a voluntary process with flexibility for recipients to work with OCR to correct any findings of violations of the proposed rule. Other commenters asked the Department to modify the proposed rule to clarify that the scope of OCR's authority is limited to seeking voluntary resolution of complaints. Other commenters stated that the Department should not wait for a complaint in order to ensure compliance with the conscience statutes, and so should include the authority to initiate compliance reviews.
                    </P>
                    <P>Additional commenters argued that OCR should release formal findings of fact in any investigation before reconciliation is attempted and that the rule should state that complainants should be informed of other possible avenues for seeking relief when their complaint is resolved.</P>
                    <P>
                        <E T="03">Response:</E>
                         The Department thanks commenters for their views. As noted in the proposed rule, 45 FR 820, 825, the Department decided to retain certain provisions of the 2019 Final Rule with modifications and not to retain others in order to address various concerns, including concerns raised in litigation regarding the lawfulness of certain provisions of the 2019 Final Rule. The Department clarifies, however, that, where authorized by the funding at issue, OCR may initiate compliance reviews when it determines to do so in its enforcement discretion and may refer items to the Department of Justice for appropriate proceedings. Additionally, the provisions included under this rule maintain the authority to seek voluntary compliance. Specifically, the rule provides that matters of noncompliance will, when possible, be resolved using informal means. This does not preclude the Department from using relevant enforcement regulations, including, when necessary, formal means of achieving compliance. These existing enforcement regulations could include, for example, the Department's authority under the Uniform Administrative Requirements, Cost Principles, and Audit Requirements For HHS Awards (UAR; 45 CFR part 75). We also note that “relevant funding” as referenced in § 88.2(c) of the proposed rule is defined by the terms of the Federal conscience statutes. The Department makes several changes to the rule text to clarify its authority. The Department is adding reference to OCR's authority to initiate compliance reviews in § 88.2(a)(2) and a new § 88.2(c). The Department also notes OCR's authority in § 88.2(a)(7) to coordinate additional remedial action as the Department determines to be both necessary and allowed by applicable law and regulation. Additionally, the Department is adding a new paragraph (3) to proposed § 88.2(d), now § 88.2(g) in this final rule, to specify that where a matter is not able to be resolved by informal means, OCR will coordinate with the relevant Departmental component to (1) utilize enforcement regulations, such as those existing applicable to grants, contracts, or other programs and services, or (2) withhold funding as authorized and relevant under the statutes listed in § 88.1. Finally, the Department is also adding in § 88.2(a)(8) a reference to, and a new paragraph in § 88.2(g)(4) regarding, OCR's ability to refer enforcement items to the Department of Justice.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters, including some non-profits, elected officials, and legal organizations, suggested that the provisions in proposed § 88.2 are not strong enough. Specifically, commenters were concerned that this rule does not include certain enforcement provisions from the 2019 Final Rule and were concerned with the statement that matters “will be resolved by informal means whenever possible.” Some asked the Department to define “informal means” and explain how that will deter future violations of the conscience statutes or prevent retaliation. One commenter stated that HHS should incorporate a formal resolution process in the rule in order to ensure conscience rights are not treated differently than other civil rights. Two commenters stated that the proposed rule was at risk of being unlawful because the Department failed to explain its rationale for not maintaining a formal resolution process similar to the 2019 Final Rule or because the rule was removing additional protections for conscience rights. Another commenter stated that the lack of effective and reasonable enforcement mechanisms would be an obstacle to ensuring compliance with the law.
                    </P>
                    <P>Several commenters stated that the proposed rule's removal of enforcement provisions from the 2019 Final Rule, including the requirement that HHS respond to and resolve conscience complaints, demonstrates clear anti-religious and anti-conscience bias and treats conscience rights as “less-than” or demonstrates “overt hostility on the part of the administration to both conscience rights and to religious liberty of health care professionals.” Many commenters raised the Department's investigation of the University of Vermont Medical Center, the California Department of Managed Health Care, and other recent decisions by the Department as examples of the need for additional provisions to ensure the final rule is adequate for consistently enforcing the Federal health care conscience statutes. Another commenter argued that the enforcement provisions retained in the proposed rule lacked an articulable standard against which any investigation will be conducted. The commenter stated that providers will be uncertain with respect to complaint investigations in this area, but that such uncertainty is preferable to over-regulating in the form of attempting to define violations without sufficiently stated guidance. Other commenters also claimed that the proposed rule will make it harder for any further discrimination claims to be filed, investigated, and remedied.</P>
                    <P>Commenters made various additional requests, including for the rule to contain more rigorous enforcement protections, the explanatory provisions and enforcement mechanisms from the 2019 Final Rule, and clear protections against retaliation.</P>
                    <P>
                        <E T="03">Response:</E>
                         OCR works to achieve voluntary compliance with all the authorities it is delegated to enforce and has found this to be an effective means of ensuring compliance. This includes OCR's approach to enforcement of the HIPAA Privacy, Security, Breach Notification, and Enforcement Rules, to the extent practicable and consistent with law,
                        <SU>9</SU>
                        <FTREF/>
                         and Title VI.
                        <SU>10</SU>
                        <FTREF/>
                         The Department's approach to the Federal conscience statutes is consistent with this approach. OCR further notes that applying a single “articulable standard,” as requested by a commenter, may not be appropriate given the breadth and variety of conscience statutes OCR is delegated to enforce. Rather than provide a one-size-fits-all standard, OCR will investigate complaints based on the relevant statute at issue. This rule 
                        <PRTPAGE P="2087"/>
                        clarifies that OCR is the central office to receive and handle complaints related to the conscience statutes and will coordinate complaints with partner agencies as appropriate on a case-by-case basis. This approach creates a more efficient and powerful method for ensuring compliance with the various statutes.
                    </P>
                    <FTNT>
                        <P>
                            <SU>9</SU>
                             
                            <E T="03">See</E>
                             45 CFR 160.304.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>10</SU>
                             
                            <E T="03">See</E>
                             28 CFR 42.411 (“Effective enforcement of title VI requires that agencies take prompt action to achieve 
                            <E T="03">voluntary</E>
                             compliance in all instances in which noncompliance is found.” (emphasis added)). Many of the other authorities OCR enforces, such as Title IX, Section 1557, Section 504, and the Age Discrimination Act, contain identical requirements.
                        </P>
                    </FTNT>
                    <P>Further, the Department is making several additions to the rule text, similar to procedures contained in the 2019 Final Rule, in response to comments. As discussed in response to other comments, the Department is adding reference to OCR's authority to initiate compliance reviews in § 88.2(a) and a new § 88.2(c). The Department also notes OCR's authority in § 88.2(a)(7) to coordinate other remedial action as the Department deems appropriate and necessary and as allowed by law and applicable regulation. The Department is adding a new paragraph (3) to proposed § 88.2(d), now § 88.2(g) in this final rule, to specify that where a matter is not able to be resolved by informal means, OCR will coordinate and consult with the relevant Departmental component to either utilize enforcement regulations, such as those that existing applicable to grants, contracts, or other programs and services, or withhold funding as authorized and relevant under the statutes listed under § 88.1. Finally, the Department notes its authority in § 88.2(a)(8) to make enforcement referrals to the Department of Justice, and is adding a new paragraph (4) to proposed § 88.2(d), now § 88.2(g) in this final rule, to specify that OCR may, in coordination with the Office of the General Counsel, refer a matter that cannot be resolved informally to the Department of Justice to enforce the Federal health care conscience protection statutes as authorized by law.</P>
                    <P>
                        The Department takes seriously its obligations to comply with the Federal health care conscience protection statutes and has taken numerous actions to defend religious freedom rights, including by supporting the right to exercise faith freely. For example, the Department is participating in the National Strategy to Counter Anti-Semitism, including by providing ongoing OCR trainings on antidiscrimination laws, including the Federal health care conscience statutes, to medical students nationwide and holding listening sessions with chaplains on religious discrimination in healthcare settings.
                        <SU>11</SU>
                        <FTREF/>
                         As part of this same initiative, OCR recently released a bulletin on countering antisemitism which explains that, depending on the factual context, Title VI of the Civil Rights Act of 1964 and Section 1557 of the Affordable Care Act may prohibit discrimination against individuals who are or are perceived to be Jewish, Christian, Muslim, Sikh, Hindu, Buddhist, or of another religion, if the discrimination is based on their ancestry or ethnic characteristics.
                        <SU>12</SU>
                        <FTREF/>
                         Also, the Department, through the longstanding operation of the HHS Center for Faith-Based and Neighborhood Partnerships, continues efforts to build and support partnerships with faith-based and community organizations in order to better serve individuals, families and communities in need.
                        <SU>13</SU>
                        <FTREF/>
                         The Department's regulations state that faith-based organizations are eligible, on the same basis as any other organization, to participate in agency programs and services.
                        <SU>14</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>11</SU>
                             
                            <E T="03">See</E>
                             Press Release, The White House, Fact Sheet: Biden-Harris Administration Releases First-Ever U.S. National Strategy to Counter Antisemitism (May 25, 2023), 
                            <E T="03">https://www.whitehouse.gov/briefing-room/statements-releases/2023/05/25/fact-sheet-biden-harris-administration-releases-first-ever-u-s-national-strategy-to-counter-antisemitism/.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>12</SU>
                             
                            <E T="03">See</E>
                             Bulletin, U.S. Dep't of Health and Human Servs., Off. for Civil Rights, Fact Sheet: Protecting Patients and Recipients of Human Services from Discrimination Based on Actual or Perceived Shared Ancestry or Ethnic Characteristics (Sept. 28, 2023), 
                            <E T="03">https://www.hhs.gov/civil-rights/for-individuals/special-topics/shared-ancestry-or-ethnic-characteristics-discrimination/index.html.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>13</SU>
                             
                            <E T="03">See</E>
                             Off. of Intergovernmental and External Affairs, Ctr. for Faith-based and Neighborhood Partnerships (Partnership Center) Homepage, (updated as of September 21, 2023), 
                            <E T="03">https://www.hhs.gov/about/agencies/iea/partnerships/index.html.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>14</SU>
                             45 CFR part 87.
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter requested that the Department specifically clarify OCR's process for handling complaints and the potential involvement of state health agencies as mentioned in proposed § 88.2(b). Other commenters requested OCR limit the extent to which OCR is permitted to rely on state agencies due to concerns about state laws and policies related to abortion and gender-affirming care potentially interfering with an accurate evaluation of the complaint under applicable federal law, especially where the state health departments involved have a record of hostility towards those seeking reproductive health care and gender-affirming care. They requested that OCR implement protections for the information gathered in the investigative process and clarify which state agencies may provide assistance, whether these agencies will make recommendations regarding resolution of the investigation, and when OCR will engage in independent fact finding. Another commenter suggested that HHS work to implement privacy protections ensuring state agencies cannot weaponize any collected information against any patients.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Where appropriate, OCR may coordinate the handling of complaints related to the Federal conscience statutes with State agencies. However, authority for making determinations about the Department's or another entity's compliance with the Federal conscience statutes as it relates to HHS programs and funding ultimately rests with the Department, which will consider all relevant facts and use its independent judgment in making its determination.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters noted that the proposed rule does not obligate OCR to evaluate every complaint or assure the public of the prompt, transparent, thorough, and reasonable handling of complaints, which undercuts the effectiveness of the proposed rule. In addition, some commenters said the rule should be modified to “permit OCR to adopt a negative inference against an investigated entity for any factual question to which the entity fails to respond.” A couple of commenters questioned whether OCR was truly an independent factfinder without conflicts of interests and argued that more enforcement or compliance tools are needed to demonstrate independence.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department agrees with the commenters' recommendation on the prompt handling of complaints and has determined to retain, at proposed § 88.2(b), now § 88.2(d) of this final rule, text from § 88.7(d) of the 2019 Final Rule stating that “OCR shall make a prompt investigation” of conscience complaints. Additionally, OCR reviews all complaints it receives and takes into consideration a covered entity's response to questions and data requests to assess if a violation has taken place, or technical assistance can help the entity comply with the law. To clarify this, the Department is finalizing this final rule with the addition of a new § 88.2(e) that notes that, OCR may adopt a negative inference if, absent good cause, an entity that is subject to the Federal health care conscience protection statutes fails to respond to a request for information or to a data or document request within a reasonable timeframe. As noted in the proposed rule, the Department remains committed to educating patients, providers, and other covered entities about their rights and obligations under the conscience statutes and using its independent judgment to ensure compliance.
                        <PRTPAGE P="2088"/>
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter recommended that to reduce confusion, the Department should use different forms to collect information on violations of the proposed rule than those used to collect civil rights complaints because conscience claims are legally distinct from civil rights complaints and will likely require different data and information during intake.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department thanks the commenter for their suggestion. However, OCR's intake forms are beyond the scope of this rulemaking.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters requested that the rule state that complainants may be represented by legal counsel.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         OCR's website states that a complaint may be filed on behalf of someone else.
                        <SU>15</SU>
                        <FTREF/>
                         We agree that legal counsel may file a complaint on behalf of their client and represent their client throughout the complaint investigation process. The Department is finalizing this final rule with the addition of a new § 88.2(b) which explains that any entity or individual may file a complaint with OCR alleging a potential violation of Federal health care conscience protection statutes, and the entity or individual filing does not have to be the entity or individual whose rights have been violated.
                    </P>
                    <FTNT>
                        <P>
                            <SU>15</SU>
                             
                            <E T="03">See, e.g.,</E>
                             U.S. Dep't of Health and Human Servs., Off. for Civil Rights, 
                            <E T="03">Complaint Portal Assistant, https://ocrportal.hhs.gov/ocr/smartscreen/main.jsf.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Interpretation of Federal Health Care Conscience Statutes</HD>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters provided their views on the proper interpretation of the Federal health care conscience statutes with many requesting substantive guidance in the final rule on how OCR will interpret and apply the various statutes included in § 88.1. Two commenters stated that even if the Department lacks authority to issue substantive regulations interpreting any or all of the Federal health care conscience statutes, it cannot pretend that it will not engage in some interpretation of the meaning of those statutes in the course of its enforcement efforts. The commenters argued that therefore, the proposed rule should set out, for internal administrative purposes, and in at least general terms, principles governing how the Department will interpret the federal health care conscience statutes in relation to other laws. In the absence of definitions, the commenters argued that such a provision would provide some guidance to covered entities about how the Department understands the statutes subject to the proposed rule.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate these comments. The Department is committed to applying the relevant conscience statutes on a case-by-case basis, which respects the balance Congress sought to achieve through these statutes.
                        <SU>16</SU>
                        <FTREF/>
                         The Department appreciates the recommendation to issue additional guidance outside of this rulemaking and takes these comments under advisement, but it does not agree that there is a need for additional language as to the Department's interpretation of the statutes in this rule at this time given the Department's intended case-by-case approach to enforcing the conscience statutes. The Department consequently declines to add language interpreting the provisions of the conscience statutes to the rule text as it is unnecessary to include such information to clarify OCR's processes by which it enforces these statutes or to enforce the conscience statutes on a case-by-case basis. Additionally, this final rule encompasses a variety of statutes such that certain “general principles,” may not apply to all the statutes contained in this rulemaking.
                    </P>
                    <FTNT>
                        <P>
                            <SU>16</SU>
                             See lengthier discussion of this principle on pages 40-41, below.
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters, including some faith-based organizations, legal organizations, and non-profits, stated the federal conscience rights should not be balanced against other competing interests and that HHS was not delegated authority to balance these interests, especially as against access to abortion. These commenters also expressed concern that a balancing test could result in different levels of protection for different providers based on factors like their geographic location or otherwise result in the arbitrary handling of conscience complaints. Another commenter said it was confusing to speak about a balance between the federal health care conscience statutes and other interests, as the proposed rule did, noting that the conscience statutes set forth absolute protections. The commenter went on to say that the courts that vacated the 2019 rule incorrectly held that the rule's broad construction of the federal health care statutes unlawfully displaced Title VII's application to employment-related religious exercise claims in the health care setting.
                    </P>
                    <P>Another commenter also emphasized that conscience statutes “are themselves a subset of nondiscrimination law.” At the same time, this commenter stressed that it agreed “that patients' autonomy and religious moral convictions must be respected” too.</P>
                    <P>
                        <E T="03">Response:</E>
                         As noted in the proposed rule, the Federal health care conscience protection statutes represent Congress' attempt to strike a careful balance between the rights of both providers and patients, and the Department intends to respect that balance. This statement reflects the balance 
                        <E T="03">Congress</E>
                         struck, not the legal requirements specific to each conscience statute set forth in this rule. Each of those conscience statutes contain particular legal requirements that must be met in order for them to apply to any given set of facts, and any determination regarding their application will be made based upon each statute.
                    </P>
                    <P>
                        The Department wishes to affirm that conscience statutes are a subset of nondiscrimination law and to clarify that it understands that the text of the conscience statutes themselves generally does not contain balancing tests. At the same time, these statutes co-exist with others protecting rights of access to health care. As it did in the preamble to the 2011 final rule, the Department continues to affirm that health care entities must comply with the long-established requirements of statutes governing Departmental programs. These statutes strike a careful balance between the rights of patients to access needed health care, and the conscience rights of health care providers. Many of the conscience laws in this rule and the other federal statues have operated side by side, often for many decades. As the 2011 Final Rule stated, “repeals by implication are disfavored and laws are meant to be read in harmony.” The Department will continue to enforce all the laws it has been charged with administering. At the same time, entities must continue to comply with their Title X, Section 330, EMTALA, Medicaid obligations and the federal health care provider conscience protection statutes.
                        <SU>17</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>17</SU>
                             76 FR 9968, 9973-74 (2011).
                        </P>
                    </FTNT>
                    <P>The Department will bear these points in mind in its investigation of any complaints it may receive.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters, including professional health care associations and reproductive health groups, stated that the government should ensure that patients' access to care is a top priority and should be appropriately balanced with the needs of health care providers. Another commenter stated that it is important to ensure an exhaustive good faith effort is made to connect patients with care.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department thanks commenters for raising these concerns 
                        <PRTPAGE P="2089"/>
                        and agrees that patients' access to care is a top priority. Protecting the rights of conscience, as directed by Congress in federal statutes, is also a top priority, which the Department is committed to safeguarding as well. As noted elsewhere, the Department will handle complaints related to conscience on a case-by-case basis which respects the balance Congress sought to achieve through these statutes.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter requested that HHS focus its resources on civil rights complaints rather than conscience complaints because, compared to civil rights complaints, violations of conscience rights occur less frequently and rarely result in adverse medical outcomes for the provider. The commenter said that patients who encounter denial of care may be unable to find a suitable provider if they face a denial of care and may suffer adverse health consequences or death due to the denial. On the other hand, the commenter said providers seeking to deny care or that were prevented from denying care are unlikely to face the medical complications or death that can result from denial of care.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         OCR reviews all the complaints it receives and will continue to do so for each of the authorities it is delegated to enforce.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter recommended that HHS include a provision that states no one served by HHS programs will be denied medically indicated care and impose a penalty for institutions and providers that deny necessary services under the “pretext” of religious freedom. The commenter noted, however, that HHS should restore the enforcement provisions from the 2019 Final Rule to avoid making providers feel they must choose between their religion and livelihood and facing retaliation.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department thanks the commenter for sharing its views. As discussed in response to other comments, the Department is adding provisions to this final rule similar to some of the enforcement provisions of the 2019 Final Rule. These include: reference to OCR's authority to initiate compliance reviews in § 88.2(a) and a new § 88.2(c); noting OCR's authority in § 88.2(a)(7) to “coordinate other appropriate remedial action as the Department deems necessary and as allowed by law and applicable regulation”; new paragraphs (3) and (4) to proposed § 88.2(d), now § 88.2(g) in this final rule, to specify formal means of enforcement, which may include the withholding of funds and referrals to the Department of Justice.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter recommended requiring that providers, grantees, and other entities subject to the proposed rule ensure patients are able to obtain care, including by being made aware of the treatments and procedures a provider refuses to provide, informed of alternative providers, and referred to alternative providers when failing to do so would harm the patient.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department agrees that patients should be able to make informed choices about which providers to seek care from, access care broadly, and receive the best care possible. This final rule clarifies OCR's existing authority and process for handling complaints under the conscience statutes. Adding a substantive provision in line with the commenter's request is beyond the scope of this rulemaking. The Department notes, however, that patients will also benefit from awareness of the Federal conscience statutes generated by entities posting a voluntary notice as outlined in this final rule.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters, including professional health care organizations and a think tank, addressed the importance of having sufficient enforcement provisions in the proposed rule because courts have held that conscience statutes do not contain or imply a private right of action, meaning the government has the central role in enforcing Federal conscience laws and protecting providers from discrimination.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department agrees with commenters regarding the importance of the Department's role with respect to the Federal conscience statutes. As stated in the proposed rule, 45 FR 820, 826, the Department remains committed to educating patients, providers, and other covered entities about their rights and obligations under the conscience statutes and remains committed to ensuring compliance. As mentioned in response to other comments, this rule is being finalized with additional provisions from the 2019 Final Rule as well as all the authorities that the proposed rule previously incorporated from the 2019 Final Rule to allow for consistent and effective enforcement of the Federal conscience statutes. We believe that this rule simplifies, and therefore strengthens, the Department's approach to ensuring compliance with the underlying statutes. It provides clarity to providers and patients about where and how they may register their concerns. And it provides the Department the ability to apply the specific legal standards and enforcement mechanisms that correspond to the statute at issue. This, in turn, allows the Department to better achieve outcomes consistent with the statutory protections Congress enacted. We also note that in the proposed rule for Section 1557, the Department provided an additional process at proposed § 92.302 for individuals to raise requests for a conscience or religious freedom exemption, 87 FR 47885-47886.
                    </P>
                    <HD SOURCE="HD3">3. Comments Addressing § 88.3</HD>
                    <HD SOURCE="HD3">General Support</HD>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters, including a national association of faith-based medical and dental providers and a national hospital association of faith-based providers, expressed support for the voluntary nature of the rule's notice provision. Additionally, a couple of commenters supported the proposed rule for allowing entities to tailor the voluntary notice to “particular circumstances and communities” and combine the notice with other notices. A couple of commenters also supported the proposed rule's inclusion of a recognition that some entities will have a conscience-based objection to posting details about alternative providers that offer services that the posting entity objects to providing. Commenters stated the proposed voluntary notice provision appropriately promotes compliance without undue burden.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department appreciates the commenters' support. The Department includes the voluntary notice provision, including the provision recognizing that some entities will have a conscience-based objection to posting details about alternative providers in the final rule.
                    </P>
                    <HD SOURCE="HD3">Requests for Changes to Rule Text</HD>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter argued that the proposed rule does not incentivize entities to post a voluntary notice. This commenter suggested that certain compliance requirements from § 88.6 of the 2019 Final Rule and the provision from §  88.5 of the 2019 Final Rule, which noted that posting the voluntary notice would constitute “non-dispositive evidence of compliance” and support the Department's goal of clarifying what an entity must do to comply with the federal conscience statutes.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As noted in the proposed rule, while the Department considers posting a notice to be a best practice and encourages covered entities to post the model notice included in this regulation, this alone does not satisfy the substantive obligations imposed on 
                        <PRTPAGE P="2090"/>
                        a covered entity by the underlying statutes. The proposed rule and this final rule modify §  88.5 of the 2019 Final Rule to avoid implying that covered entities can substantively comply with the underlying statute by simply posting a notice because such an implication could undermine the conscience protections provided by the underlying statutes themselves, and therefore the goal of this rule. While the Department does not adopt §  88.5 of the 2019 Final Rule, the Department is finalizing § 88.3 with additional statements that the Department considers posting a notice to be a best practice “towards achieving compliance with and educating the public about the Federal health care conscience statutes” and that “OCR will consider posting a notice as a factor in any investigation or compliance review” to emphasize the importance of posting the voluntary notice.
                    </P>
                    <P>The Department declines, however, to maintain all the compliance requirements from § 88.6 of the 2019 Final Rule. Some commenters raised concerns in response to both the 2018 Proposed Rule and the proposed rule for this rulemaking that the compliance requirements at § 88.6 were overly burdensome on covered entities, especially the record keeping requirements, and not authorized by the conscience statutes. In the Department's view, these concerns raised by commenters warrant additional consideration. Even though the Department declines to maintain the duty to cooperate as specified in § 88.6(c) of the 2019 Final Rule, however, this final rule includes a notice to covered entities in § 88.2(e) that OCR will adopt a negative inference if, absent good cause, an entity that is subject to the Federal health care conscience protection statutes fails to respond to a request for information or to a data or document request within a reasonable timeframe. In the Department's view, this requirement will encourage compliance without creating additional regulatory burden.</P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter requested that HHS require that notices related to conscience exceptions also be required to comply with the Section 1557 language access and auxiliary aids and services requirements.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department appreciates this comment. Covered entities are required to comply fully with all applicable language access requirements found in statute or regulation, regardless of whether the requirements overlap with the topics of this regulation.
                    </P>
                    <HD SOURCE="HD3">Language of the Notice</HD>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters stated that the model notice should be the same as the model notice proposed in the 2019 Final Rule because it provided more clarity. Other commenters recommended more specific and clear language generally. A commenter said that, while they supported aspects of the proposed notice, such as listing the relevant statutes and dropping the implication that posting the notice would be some evidence of substantive compliance with the underlying statute, the commenter urged HHS to include in the notice a general description of the types of protections these statutes provide.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department appreciates the commenters' recommendations and has included the following text in the model notice text in response to commenter requests for more clarity: “You may have rights as a provider, patient, or other individual under these Federal statutes, which prohibit coercion or other discrimination on the basis of conscience in certain circumstances.” The Department also notes that § 88.3(d) states that an entity “may tailor its notice to address its particular circumstances and to more specifically address the conscience laws covered by this rule that apply to it.” Finally, the Department has included in the model notice a list of the federal health care conscience protection statutes and a link to the HHS web page where additional resources can be accessed for covered entities and the public to better understand their obligations and rights under the Federal health care conscience statutes.
                        <SU>18</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>18</SU>
                             
                            <E T="03">See</E>
                             U.S. Dep't of Health and Human Servs., Off. for Civil Rights, 
                            <E T="03">Conscience and Religious Nondiscrimination, https://www.hhs.gov/conscience/conscience-protections/index.html.</E>
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter argued that the following language in proposed § 88.3(d) was improper: “where possible, and where the recipient does not have a conscience-based objection to doing so, the notice should include information about alternative providers that may offer patients services the recipient does not provide for reasons of conscience.” This commenter maintained that the language is improper because the Coats-Snowe Amendment prohibits a covered entity from requiring a physician or certain other individuals to refer patients, which may be the case where a covered employer does not object to the inclusion of information about alternative providers, but their employee physician does. Another commenter argued that this language was “a prudent observance of the Supreme Court's decision in NIFLA v. Becerra.”
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department disagrees that the challenged language is improper. The provision identified by the commenter does not require recipients to provide information about alternative providers in any notice, nor does it suggest that any recipient may require a health care provider (
                        <E T="03">e.g.,</E>
                         a doctor) to post this information in violation of their rights under applicable health care conscience protection statutes or the Constitution.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters requested additional language in the voluntary notice that would focus on protecting patients from negative impacts caused by a denial of care under the conscience statutes. These commenters suggested that the voluntary notice provision has two target audiences: employees of providers and members of the public, and so there should be two separate notice provisions for each group, and they should be posted on the health care provider's website.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department agrees that patients should also be the focus of the voluntary notice and notes that the text of § 88.3 addresses this concern. Section 88.3(d) states that “[w]here possible, and where the recipient does not have a conscience-based objection to doing so, the notice should include information about alternative providers that may offer patients services the recipient does not provide for reasons of conscience,” which gives entities the opportunity to include additional information for the consideration of patients about access to certain health care services. Additionally, the Department in § 88.3(d) states that an entity “may tailor its notice to address its particular circumstances and to more specifically address the conscience laws covered by this rule that apply to it.” The Department is also adding text to the voluntary notice to make clear that the Federal health care conscience statutes also provide certain conscience protections for patients. Finally, the Department notes that § 88.3(b)(1) of both the proposed rule and this final rule recommends the model notice be posted on provider's websites, where both patients and providers may view it.
                    </P>
                    <HD SOURCE="HD3">4. Comments Addressing Section 88.4</HD>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter noted that the preamble to the proposed rule stated that it was repealing the severability provision, but that the provision is retained in the regulation text at § 88.4.
                        <PRTPAGE P="2091"/>
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department thanks the commenter. The statement that OCR was removing the severability provision was a typographical error at 88 FR 820, 825. The error is corrected in this final rule. This rule provides meaningful tools for OCR to enforce the Federal health care conscience protection statutes. Section 88.4 ensures that portions of this rule not found to be unlawful would remain in effect even if a court were to strike down some provision of this final rule. The various complaint handling and investigating provisions at § 88.2, for instance, operate independently of each other. Likewise, the notice provision at § 88.3 can operate independently of the rest of the rule.
                    </P>
                    <HD SOURCE="HD2">C. Comments Addressing the Proposed Rule's Requests for Comment</HD>
                    <HD SOURCE="HD3">1. Information, Including Specific Examples Where Feasible, Addressing the Scope and Nature of the Problems Giving Rise to the Need for Rulemaking, and Whether Those Problems Could Be Addressed by Different Regulations Than Those Adopted in 2019 or by Sub-Regulatory Guidance</HD>
                    <HD SOURCE="HD3">Comments Addressing the Scope and Nature of the Problems Giving Rise to the Need for Rulemaking</HD>
                    <P>
                        <E T="03">Comment:</E>
                         In support of the need for rulemaking, one legal organization provided court cases related to the Religious Freedom Restoration Act. Another individual commenter cited her own published work which suggests that nurses and nursing students are under the impression that they must set aside their conscientious views to be a nurse. Other commenters highlighted that their religious beliefs and moral convictions are what motivate them to be in the health care field and help them to relate to the spiritual needs of patients who desire a religious perspective.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department appreciates the concerns raised by the commenters regarding the need for this rulemaking. While the Department does not opine here on any of the cases raised by the commenters, the comments help illustrate that finalizing this rule will provide further clarity about OCR's enforcement authority and processes related to the Federal health care conscience statutes. The Department is committed to applying the text of the relevant conscience statutes on a case-by-case basis, which respects the balance Congress sought to achieve through these statutes, and that commitment is evidenced in part through this new rulemaking. The Department has also taken steps to ensure that the public is aware of the protections under the conscience statutes beyond this rulemaking, including by issuing guidance on the Church Amendments.
                        <SU>19</SU>
                        <FTREF/>
                         The Department encourages anyone who believes the Federal health care conscience statutes have been violated to file a complaint with OCR. For detailed instructions on how to file a complaint or to download a complaint form, please visit OCR's website at 
                        <E T="03">www.hhs.gov/ocr/complaints.</E>
                    </P>
                    <FTNT>
                        <P>
                            <SU>19</SU>
                             U.S. Dep't of Health and Human Servs., Off. for Civil Rights, “Guidance on Nondiscrimination Protections under the Church Amendments” (Content last reviewed Feb. 3, 2023), 
                            <E T="03">https://www.hhs.gov/conscience/conscience-protections/guidance-church-amendments-protections/index.html.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Whether the Problems Giving Rise to Rulemaking Could Be Addressed by Different Regulations or by Sub-Regulatory Guidance</HD>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter proposed a new framework for evaluating conscience complaints, revolving around requiring objections to be stated in advance, increasing staffing to accommodate objections, and requiring health care entities that object to providing procedures to either (1) facilitate and pay for transferring patients to hospitals that provide procedures or (2) limit their services to patients who share their beliefs and divest facilities where there is no similar sized health care entity within a 30 minute drive that provides all needed services. Another commenter similarly commented that any exceptions based on the Church Amendments should not apply if the provider's refusal to provide care results in serious harm to the patient, and the patient could not schedule another in-network provider.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department thanks the commenters. We decline to implement the commenters' recommendations in this final rule as they are beyond the scope of this rulemaking. The Department will adhere to the Federal health care conscience statutes and apply them on a case-by-case basis.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Given the lack of explicit enforcement mechanisms in the existing statutes, one commenter urged the Department to consider what additional regulatory language or subsequent guidance it can provide consistent with its authority to ensure that the conscience laws are fully and effectively enforced when violations of conscience rights are found.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department thanks the commenter for recommending that the Department consider additional regulatory language and subsequent guidance. As discussed in response to other comments, the Department is adding regulatory language to clarify the Department's and OCR's authority to enforce the Federal health care conscience statutes, including through compliance reviews (§ 88.2(a) and a new § 88.2(c)), coordinating other appropriate remedial action (§ 88.2(a)), and OCR's authority to utilize existing enforcement regulations or withhold relevant funding to the extent authorized under the Federal health care conscience statutes where a matter cannot be resolved by informal means (§ 88.2(g)(3)). The commenter did not provide any recommendations on what that guidance should include, but the Department will continue to consider whether additional guidance under the conscience statutes is warranted.
                    </P>
                    <HD SOURCE="HD3">2. Information, Including Specific Examples Where Feasible, Supporting or Refuting Allegations That the 2019 Final Rule Hindered, or Would Hinder, Access to Information and Health Care Services, Particularly Sexual and Reproductive Health Care and Other Preventive Services</HD>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters, including reproductive health groups, claimed that the 2019 Final Rule generally would have had a negative effect on patients by restricting access to care and increasing denials of care. Commenters stated that barriers to health care are compounded in health systems that refuse to provide certain types of care due to religious or moral objections. These commenters said patients do not necessarily know about such limits on care. The commenters further said this occurs more often in rural areas where there are often no alternative providers, impacts those with lower incomes, and impacts pregnant women of color who disproportionately give birth at hospitals that object to abortion and contraception.
                    </P>
                    <P>
                        Numerous commenters, including reproductive health groups and LGBTQI+ rights groups discussed the 2019 Final Rule's potential impact on services and access to care for groups of marginalized or underserved populations, including but not limited to women, older Americans, LGBTQI+ people, people with disabilities, people living in rural areas, Black, Indigenous, and people of color, immigrants, low-income communities, people with HIV, and people with substance use disorder. Numerous commenters discussed general health disparities and heightened discrimination against LGBTQI+ individuals, including access 
                        <PRTPAGE P="2092"/>
                        to reproductive health care and technology, that they claimed would have occurred because of the 2019 Final Rule. One commenter tied the fact that LGBTQI+ individuals already experience significant health inequities due to refusals to provide certain forms of care and stated LGBTQI+ individuals often suffer from “health care avoidance” due to facing discrimination in a number of services, including reproductive services, adoption and foster care services, childcare, homeless shelters, and transportation services—as well as physical and mental health care services. A commenter stated the 2019 Final Rule would have allowed providers to object to providing care, especially emergency services, which would disproportionately affect transgender people because of their struggle to access care. Another commenter argued the 2019 Final Rule would have harmed older adults by authorizing discrimination and increasing disparities in Medicare and Medicaid, especially for transgender older adults that would be at the mercy of Medicare Advantage plans hoping the plan contracts with providers who will not refuse them treatment. Additionally, a commenter discussed refusals to provide care that are based on religious or moral objections as particularly impactful to transgender individuals.
                    </P>
                    <P>Numerous commenters described the types of services that they believed the 2019 Final Rule would have negatively impacted, such as contraception, end-of-life care, vaccination, pregnancy and reproductive services, counseling and behavioral health, infertility treatment, pre-exposure prophylaxis (PrEP) and HIV treatment, among others. One commenter said the 2019 Final Rule could have allowed providers to refuse cancer treatment or reproductive services for pregnant individuals. Another commenter discussed the importance of family planning under the Title X program, stating that they believed the 2019 Final Rule would have reduced access to such “sexuality education” and family planning care and would have made it difficult for Title X facilities to hire employees willing to perform core job functions. Other commenters said that by further restricting access, the 2019 Final Rule would have exacerbated existing racial and socio-economic health disparities.</P>
                    <P>
                        A few commenters, including reproductive health organizations, noted that immigrants, ethnic minorities, and LGBTQI+ individuals faced disproportionate barriers accessing reproductive health care before the 
                        <E T="03">Dobbs</E>
                         v. 
                        <E T="03">Jackson Women's Health Organization,</E>
                         142 S. Ct. 2228 (2022), decision and the 2019 Final Rule would have increased those barriers. One commenter stated that the 2019 Final Rule targeted people seeking reproductive health care, but even before the 2019 Final Rule, people cited religious beliefs to deny access to services such as abortion, sterilization, certain infertility treatments, and miscarriage management. A commenter stated there are serious physical and socioeconomical impacts on patients who experience discrimination when seeking abortion care, and refusals to provide such care can have profound health consequences for women. Two commenters stated that this partial recission of the 2019 Final Rule comes at an important time in the wake of the 
                        <E T="03">Dobbs</E>
                         decision, as abortion services are harder to obtain.
                    </P>
                    <P>Several commenters, including a reproductive health group, stated that the 2019 Final Rule upset the careful balance in Federal laws between patient needs and conscience rights, and that the proposed rule appropriately resets that balance. A professional health care association stated that in the balance between conscience rights and patients' rights, patients' rights must come first as the patient is in the more vulnerable position, meaning there is a duty to refer on the part of the objecting provider. A few commenters argued that the proposed rule is needed to ensure LGBTQI+ patients have access to care, free from discrimination. Two commenters stated that the proposed rule would minimize the frequency of refusals to provide abortions, which especially burden the most vulnerable in our society. The commenter also stated that physicians should have some discretion if they truly believe performing an abortion in certain cases would violate their duties as medical professionals, but those who would be unwilling to perform abortion under any circumstance are not well suited for reproductive health care.</P>
                    <P>Numerous commenters, including a reproductive health organization, urged the Department to eliminate the 2019 Final Rule because it would have allowed almost any worker in a health care facility, insurance plan, or hospital to delay or block patients from getting care because of who they are or the kind of care they seek, including individuals indirectly involved in the provision of health care. One commenter stated that the 2019 Final Rule would have caused massive disruptions to large provider networks because costs of compliance with the 2019 Final Rule would have been astronomical, since losing federal funding for failure to comply would have led to the discontinuation of essential services and even closures.</P>
                    <P>One commenter stated that the 2019 Final Rule failed to account for health care providers who have moral beliefs that motivate them to treat and provide health care, especially abortion, end-of-life care, and gender-affirming care, to patients.</P>
                    <P>
                        <E T="03">Response:</E>
                         The Department thanks commenters for sharing their views. The Department appreciates the concern that patients have full access to health care and as the proposed rule stated, 88 FR 820, 826, the Department maintains that our health care systems must effectively deliver services to all who need them in order to protect patients' health and dignity. The Department is engaging in this rulemaking in part to address the concerns raised by commenters about the impact of the 2019 Final Rule. The Department reiterates its commitment to ensuring that patients are not discriminated against, including by being denied health care on the various bases protected under civil rights laws. In addition, the Department is committed to ensuring compliance with the conscience statutes, including those provisions under the Church Amendments that offer protections for physicians or certain other individuals in certain federally funded health, training, or research programs who have performed or assisted in the performance of, or who are willing to perform or assist in the performance of, a lawful sterilization procedure or abortion.
                    </P>
                    <HD SOURCE="HD3">3. Information, Including Specific Examples Where Feasible, Regarding Complaints of Discrimination on the Basis That an Individual or Health Care Entity Did Not Provide Services for the Purpose of Causing or Assisting in the Death of Any Individual, Including Through Assisted Suicide, Euthanasia, and Mercy Killing, as Described in Section 1553 of the ACA, and Comments on Whether Additional Regulations Under This Authority Are Necessary</HD>
                    <HD SOURCE="HD3">General Support for Conscience Protections</HD>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters requested that conscience protections for assisted suicide be strengthened due to a recent rise in conscience objections. Some commenters referenced various examples, including cases and state laws from Vermont, Maine, California, and New Mexico and stated that since state laws protect conscience rights to a lesser degree than Section 1553, the Department must ensure compliance with Section 1553 to protect the 
                        <PRTPAGE P="2093"/>
                        conscience rights of those providers who object to taking human life.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department appreciates commenters providing their views regarding conscience rights related to assisted suicide. The Department remains committed to educating patients, providers, and other covered entities about their rights and obligations under the conscience statutes and remains committed to ensuring compliance, including with Section 1553 of the Affordable Care Act.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter noted that assisted suicide or medical aid in dying is not necessary, life-preserving, or lifesaving, so there should be no issue with permitting health care entities to refuse to perform such services for moral or religious objections. A commenter stated that conscientious objections are from the perspective of the objector, meaning it is immaterial how a state defines the “practice” of assisted suicide or whether it disagrees that abortion is a procedure that takes the life of a separate, unique, human being.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Each of the conscience statutes contains particular requirements that must be met in order for them to apply to a given set of facts. The Department remains committed to faithfully applying each statute as drafted by Congress on a case-by-case basis.
                    </P>
                    <HD SOURCE="HD3">Requests for Technical Changes</HD>
                    <P>
                        <E T="03">Comment:</E>
                         One end-of-life patient advocacy group raised concerns about the proposed rule using the term “assisted suicide” as opposed to “medical aid in dying,” arguing that using that term in conjunction with citing Section 1553 of the Affordable Care Act would create barriers preventing terminally ill patients from accessing their right to “medical aid in dying” in states that authorize it and consider it as distinct from assisted suicide. The commenter argued that medical aid in dying is a medical procedure in which a physician writes a prescription for medication for a mentally capable, terminally ill adult who can then decide if they want to self-administer the medication if their suffering becomes too great. The commenter contrasted that with assisted suicide, which it defined as a criminal act in which someone encourages and facilitates the self-inflicted death of an individual irrespective of their life expectancy. The commenter recommended the Department use the term “medical aid in dying” to ensure that patients are informed of the option, and to distinguish between the duty to share information about medical options at the end of life from the act of participating in a medical procedure to which a provider objects.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department appreciates this comment. The Department notes that the final rule includes reference to Section 1553 of the Affordable Care Act, which uses the terms “assisted suicide,” “euthanasia,” and “mercy killing.” 
                        <SU>20</SU>
                        <FTREF/>
                         The Department declines, however, to incorporate additional language in the rule text regarding the definition of “assisted suicide” or the other terms in the statute as it is unnecessary to include such language to clarify OCR's processes by which it enforces this statute or to enforce it on a case-by-case basis.
                    </P>
                    <FTNT>
                        <P>
                            <SU>20</SU>
                             “The Federal Government, and any State or local government or health care provider that receives Federal financial assistance under this Act (or under an amendment made by this Act) or any health plan created under this Act (or under an amendment made by this Act), may not subject an individual or institutional health care entity to discrimination on the basis that the entity does not provide any health care item or service furnished for the purpose of causing, or for the purpose of assisting in causing, the death of any individual, such as by assisted suicide, euthanasia, or mercy killing.” 42 U.S.C. 18113(a).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">4. Information, Including Specific Examples Where Feasible, Regarding Complaints of Discrimination by a Qualified Health Plan Under the ACA on the Basis That a Health Care Provider or Facility Refused To Provide, Pay for, Cover, or Refer for Abortions, as Described in Section 1303 of the ACA and Comments on Whether Additional Regulations Under This Authority Are Necessary</HD>
                    <P>
                        <E T="03">Comment:</E>
                         The Department received a comment in response to this question, but did not receive information regarding complaints of discrimination by a qualified health plan. The commenter expressed concern that patients can either choose their employer's insurance plan or an Affordable Care Act plan but stated that neither type of insurance plan should be allowed to deny care under the federal conscience statutes. The commenter stated that health insurance plans, and hospitals as well, are not people with rights that can be infringed.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department thanks the commenters for sharing their views, but notes that each of the conscience statutes contains particular requirements and prohibitions that were put in place by Congress. Any determination regarding their application will be made based upon the specifics of each statute.
                    </P>
                    <HD SOURCE="HD3">5. Information, Including Specific Examples Where Feasible, From Health Care Providers Regarding Alleged Violations of the Conscience Provisions Provided for in the Medicaid and Medicare Statutes, Including the Provisions Codified at 42 U.S.C. 1320a-1(h), 1320c-11, 1395i-5, 1395w-22(j)(3), 1395x(e), 1395x(y)(1), 1395cc(f), 1396a(a), 1396a(w)(3), 1396u-2(b)(3), 1397j-1(b), and 14406(2) and Comments on Whether Additional Regulations Under These Authorities Are Necessary</HD>
                    <P>
                        <E T="03">Comment:</E>
                         A patient advocacy group generally discussed the importance of advance directives as a health care planning tool for end-of-life medical care. The commenter stated that the Medicare and Medicaid provisions regarding advanced directives should not be construed to allow entities and providers to fail to provide complete information to patients about end-of-life care and advance directives, pointing out that under many state laws providers may refuse to follow advance directives for religious or moral beliefs so long as the physician informs the patient and in many cases assists in the transfer to another provider who will honor the patient's wishes.
                    </P>
                    <P>Another commenter stated that the Department failed to articulate a sufficient reason for expanding the proposed rule to include these Medicare and Medicaid provisions. The commenter stated the proposed rule invalidates the inherent authority of advance directives by allowing providers to ignore these documents if they disagree. The commenter asserted that Section 1395cc(f) and CMS implementing regulations (See 42 CFR 489.102(a)(1)(ii) (2018); 42 CFR 418.52(a)(2) (2018)) require facilities to inform patients and residents of their rights to have completed advance directives, and that facilities should provide their patients and residents with written information about whether or not the provider objects on conscience grounds to honoring the directive. The commenter recommended that the Department require health care entities to provide accessible and prominent notice about all information the health care entity or provider refuses to offer and urged the Department to ensure patients are still timely transferred if a health care provider objects to honoring an advance directive.</P>
                    <P>
                        <E T="03">Response:</E>
                         As the proposed rule stated, retaining the Federal conscience provisions as a part of the rule and maintaining OCR as the centralized HHS office tasked with receiving and investigating complaints under these 
                        <PRTPAGE P="2094"/>
                        provisions will aid the public by increasing awareness of the rights protected by these statutes and where to file complaints alleging violations of those rights. The Department declines to include provisions beyond the text of the conscience statutes in this procedural rule as recommended by the commenter or to require entities to post information about services to which they have a conscience objection. The Department notes, however, that the voluntary notice provision of this final rule states that, where possible, and where the recipient does not have a conscience-based objection to doing so, the notice should include information about alternative providers that may offer patients services the recipient does not provide for reasons of conscience.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter referenced the Department's request for comment for examples from providers about discrimination in violation of conscience provisions in the Medicaid and Medicare statutes without directly providing such examples. The commenter stated that public and private insurance should safeguard existing benefits for children and should include reproductive health and related services. The commenter urged HHS to ensure no individuals receiving care through public health insurance are denied access to care or willing providers.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department thanks the commenter for sharing their concern. Providing such substantive provisions, however, is beyond the scope of this rulemaking.
                    </P>
                    <HD SOURCE="HD3">6. Information, Including Specific Examples Where Feasible, Regarding Alleged Violations of Any of the Other Authorities That Appeared in the 2019 Final Rule But Not the 2011 Final Rule</HD>
                    <P>
                        <E T="03">Comment:</E>
                         The Department only identified one comment in response to this question. A commenter offered suggestions on “other relevant authorities” (without citation) in reference to this request for comment and urged HHS to support only organizations that advocate in favor of childhood vaccination and not to make policy changes to weaken measures to immunize health care personnel.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department thanks the commenter for their response. This final rule clarifies OCR's existing authorities over the Federal conscience statutes in § 88.1, which includes a provision regarding pediatric vaccines (42 U.S.C. 1396s(c)(2)(B)(ii)).
                    </P>
                    <HD SOURCE="HD3">7. Comment on Whether the 2019 Final Rule Provided Sufficient Clarity To Minimize the Potential for Harm Resulting From Any Ambiguity and Confusion That May Exist Because of the Rule, and Whether Any Statutory Terms Require Additional Clarification</HD>
                    <HD SOURCE="HD3">Whether the 2019 Final Rule Provided Sufficient Clarity To Minimize the Potential for Harm</HD>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters, including reproductive health organizations and legal organizations, generally expressed support for the rescission of 2019 Final Rule provisions, stating that the 2019 Final Rule was confusing and redundant, unlawful, overbroad, discriminatory, and ripe for abuse. Many of these commenters also stated that rescinding the 2019 Final Rule would restore OCR's appropriate scope of enforcement. One commenter stated that the proposed rule reflected the appropriate balance between providing reasonable accommodations for providers who cannot perform certain services in good conscience and obligations to patients and providing the care they need—a balance that hospitals already have vast experience in addressing.
                    </P>
                    <P>Two commenters stated that for many major medical providers, including their own, the threat of loss of federal funding is a threat to the facilities' existence, meaning the 2019 Final Rule would have skewed health systems against patient care and in favor of refusals to provide certain services based on religious or moral objections. Three commenters stated that the 2019 Final Rule would have aggravated health disparities, contrary to the mission of HHS and OCR. One commenter expressed their support for the proposed rule because it declined to retain the provisions in the 2019 Final Rule that appeared to give OCR the authority to withhold federal financial assistance and suspend award activities based on “threatened violations” alone, without first allowing for the completion of an informal resolution process. A couple of commenters stated that they support the proposed rule for removing onerous reporting requirements that the 2019 Final Rule would have imposed.</P>
                    <P>Other commenters discussed physicians' duties to patients, with one commenter asking that the Department clarify that the Federal government's stance is that providers cannot refuse to serve patients due to personal beliefs. Another commenter supported the proposed rule out of concern that the 2019 Final Rule would have negatively impacted the field of pediatrics and the care and well-being of children in particular.</P>
                    <P>
                        Many commenters, including legal organizations and reproductive health organizations, argued that the sweeping language of the 2019 Final Rule definitions exceeded statutory and constitutional authority by abandoning the long-standing balancing framework under Title VII of the Civil Rights Act of 1964 or violating the Establishment Clause, especially the definitions of “referral/refer” and “assist in the performance.” Many of these commenters said the 2019 Final Rule definitions would have allowed providers to violate principles of medical ethics and informed consent by refraining from informing patients about treatment options that they find objectionable and referring the patient to another provider, even in an emergency. These commenters said that this would have weakened the integrity of key HHS programs and the quality of U.S. health care by disregarding evidence-based standards of care. One legal organization asserted that the 2019 Rule's definition of “discrimination” contrasted with prior case law regarding the Weldon and Coats-Snowe Amendments and the reasonableness of accommodations. Several commenters, including state attorneys general, a legal organization, and a reproductive health organization, argued that the definition of “health care entity” in the 2019 Rule would have exceeded the reach of the Weldon and Coats-Snowe Amendments by including dozens of new entities under their protection, such as employers that provide health benefits, pharmacists, and medical laboratories. One of these commenters elaborated that in the Coats-Snowe Amendment, Congress chose to focus on a select group of individuals involved in the abortion training context in its definition of “health care entity,” and cited to contemporary statements by Senator Coats that the statute was meant to “simply address the question of training for induced abortions.” 
                        <SU>21</SU>
                        <FTREF/>
                         The commenter likewise cited floor statements by Representative Weldon to show that the Weldon Amendment was meant to apply to a limited group of entities. Additional commenters argued the 2019 Final Rule would have made it exceedingly difficult for health care providers to interview, hire, or respond to accommodation requests, and to continue to provide essential services to their patients since the rule would have, in their view, impermissibly broadened the right to object based on conscience 
                        <PRTPAGE P="2095"/>
                        to virtually any other person in the health care setting.
                    </P>
                    <FTNT>
                        <P>
                            <SU>21</SU>
                             142 Cong. Rec. 5,158 (1996) (statement of Sen. Coats).
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Response:</E>
                         The Department thanks the commenters for sharing their views on the 2019 Rule. As stated in the proposed rule, the Federal health care conscience protection statutes represent Congress' attempt to strike a careful balance, which the Department will respect. Some doctors, nurses, and hospitals, for example, object for religious or moral reasons to providing or referring for abortions or assisted suicide, among other procedures. Respecting such objections honors liberty and human dignity. It also redounds to the benefit of the medical profession. Patients also have autonomy, rights, and moral and religious convictions. And they have health needs, sometimes urgent ones. Our health care systems must effectively deliver services to all who need them in order to protect patients' health and dignity. The Department maintains that this final rule appropriately addresses the concerns raised by commenters and three separate district courts about the 2019 Final Rule, and in particular, its definitions, and allows the Department to faithfully apply each statute on a case-by-case basis.
                    </P>
                    <HD SOURCE="HD3">Whether Any Statutory Terms Require Additional Clarification</HD>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters, including local governments, legal organizations, and others, generally expressed opposition to the rescission of the definitions that appeared at § 88.2 of the 2019 Final Rule on the grounds that those definitions provide more clarity regarding conscience protection statutes, that some of the definitions were not redundant, unlawful, or unnecessary, and that the definitions would ensure adequate enforcement and prevent arbitrary determinations by OCR. One commenter stated that the Department has failed to provide an adequate justification for why the removal of all definitions improves the application or interpretation of laws regarding conscience protections, while another commenter requested that the Department replace the allegedly confusing definitions of the rule with new definitions. A few commenters said that the 2019 Final Rule's definitions upheld the balance between conscience protection and patient rights and appropriately reflected the breadth of the underlying statutes.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department thanks the commenters for sharing their concerns regarding the 2019 Final Rule's definitions and clarifying certain statutory terms. The Department is declining to include certain portions of the 2019 Final Rule, including the definitions mentioned by commenters, because questions have been raised as to their clarity and legality, including whether they undermine the balance Congress struck between safeguarding conscience rights and protecting access to health care. In response to the 2018 Proposed Rule, the Department received numerous comments about the clarity and scope of the proposed definitions. 
                        <E T="03">See,</E>
                         84 FR 23170, 23186-23204 (May 21, 2019). While the Department finalized the definitions in the 2019 Final Rule with changes to address these concerns, the district court for the Southern District of New York found that the 2019 Final Rule's definitions of “discrimination,” “assist in the performance,” “referral,” and “health care entity,” in the court's view, impermissibly broaden the conscience statutes beyond the balance struck by Congress. 
                        <E T="03">New York,</E>
                         414 F. Supp. 3d at 523. The district court for the Northern District of California similarly found that the 2019 Final Rule, including the definitions and enforcement provisions, were not “mere housekeeping.” 
                        <E T="03">San Francisco,</E>
                         411 F. Supp. 3d at 1023. In the court's view, the “expansive definitions,” which departed from the federal statutes, coupled with the termination of all HHS funding as a consequence of noncompliance, rendered the rule “undoubtedly substantive.” 
                        <E T="03">Id.</E>
                         In response to the proposed rule, the Department received comments again raising concerns about the clarity and scope of the 2019 Final Rule's definitions. Taken together, the Department determined that the questions raised about the definitions in the 2019 Final Rule by commenters and the courts warrant additional careful consideration. Finally, as noted elsewhere, the Department declines to add language interpreting the provisions of the conscience statutes to the rule text as it is unnecessary to include such language to clarify OCR's processes by which it enforces these statutes or to enforce them on a case-by-case basis.
                        <SU>22</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>22</SU>
                             The Department notes that the model notice text includes a link to the HHS web page where additional resources can be accessed for covered entities and the public to better understand their obligations and rights under the Federal health care conscience statutes. 
                            <E T="03">See</E>
                             U.S. Dep't of Health and Human Servs., Off. for Civil Rights, 
                            <E T="03">Conscience and Religious Nondiscrimination, https://www.hhs.gov/conscience/conscience-protections/index.html.</E>
                             As noted elsewhere in this preamble, the Department agrees it is important to ensure the public is aware of the Federal conscience statutes and remains committed to educating patients, providers, and other covered entities about their rights and obligations under the conscience statutes, including through education and outreach efforts.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">8. Comment on Whether the Provisions Added by the 2019 Final Rule Are Necessary, Collectively or With Respect to Individual Provisions, To Serve the Statutes' or the Rule's Objectives, Including With Regard to Whether the Department Accurately Evaluated the Need for Additional Regulation in the 2019 Final Rule, and Whether Those Provisions Should Be Modified, or Whether the Rule's Objectives May Also Be Accomplished Through Alternative Means, Such as Outreach and Education</HD>
                    <HD SOURCE="HD3">Whether the Provisions Added by the 2019 Final Rule Are Necessary and Whether the Department Accurately Evaluated the Need for Additional Regulation in the 2019 Final Rule</HD>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters, including a reproductive health group, stated that the Department did not accurately evaluate the need for additional regulation in its promulgation of the 2019 Final Rule, stating that the paucity of data on conscience complaints or allegations of conscience statute violations, and the decision by three federal district courts to vacate the 2019 Final Rule, illustrates that the provisions of the 2019 Final rule were not actually necessary. One legal organization agreed that the 2019 Final Rule made significant changes to the conscience statutes and argued the Department did not need to engage in rulemaking given that there were less than a dozen conscience complaints filed with OCR between 2011 and 2017 and instances in which providers are required to violate their conscience are rare. Some commenters noted that, as the Southern District of New York found, the number of conscience complaints received by OCR was significantly less than the 2019 Final Rule stated, which undermined one key argument for it. These commenters said that this lack of data means HHS has no justification for the assertion in the 2019 Final Rule that HHS otherwise lacks the capacity to enforce the provisions of the Federal conscience statutes. These commenters stated that the provisions of the 2019 Final Rule are not necessary because (1) Congress did not delegate to HHS rulemaking authority to promulgate the substantive components of the 2019 Final Rule and (2) Congress did not delegate to OCR the ultimate enforcement power to cut off all of a recipient's funding for the breach of a conscience provision.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department acknowledges that the litigation surrounding the 2019 Final Rule raised questions regarding the complaints of statutory violations that served as a predicate for the 2019 Final Rule, and 
                        <PRTPAGE P="2096"/>
                        thanks the commenters for sharing their other thoughts regarding this issue. The Department notes that OCR's overall caseload has multiplied in recent years, increasing to over 51,000 complaints in 2022—an increase of 69 percent between 2017 and 2022—with 27 percent of those complaints alleging violations of civil rights, 66 percent alleging violations of health information privacy and security laws, and 7 percent alleging violations of conscience/religious freedom laws.
                        <SU>23</SU>
                        <FTREF/>
                         The Department has concluded that this final rule will enable OCR to effectively process and resolve complaints related to the Federal health care conscience statutes.
                    </P>
                    <FTNT>
                        <P>
                            <SU>23</SU>
                             
                            <E T="03">See</E>
                             Press Release, U.S. Dep't of Health and Human Servs., Off. for Civil Rights, HHS Announces New Divisions Within the Office for Civil Rights to Better Address Growing Need of Enforcement in Recent Years (Feb. 27, 2023), 
                            <E T="03">https://www.hhs.gov/about/news/2023/02/27/hhs-announces-new-divisions-within-office-civil-rights-better-address-growing-need-enforcement-recent-years.html.</E>
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter stated that the 300 complaints filed with OCR within a month of the announcement of the new Conscience and Religious Freedom Division within OCR are evidence of the need for broader conscience protections, and another commenter defended the 2019 Final Rule in part due to an increase in complaints filed with OCR.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Among other things, the litigation over the 2019 Final Rule raised significant questions regarding the complaints of statutory violations that served as a predicate for the 2019 Final Rule. As noted above, OCR's caseload has increased,
                        <SU>24</SU>
                        <FTREF/>
                         but the Department has concluded that this final rule will enable OCR to effectively process and resolve complaints related to the Federal health care conscience statutes.
                    </P>
                    <FTNT>
                        <P>
                            <SU>24</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters, including a faith-based organization, expressed opposition to the removal of the compliance requirements at § 88.6 of the 2019 Final Rule, stating that removal of these requirements is contradictory to the stated goal of protecting conscience rights and will hinder the Department's ability to prevent discrimination. Commenters explained that compliance requirements would provide clarity on how conscience rights are expected to be enforced, would aid in the fact-intensive investigations conscience complaints can require, and would fit in with the general practices for other for civil rights laws. One commenter elaborated that in the absence of these requirements, recipients may under- or over-record, incurring laborious administrative costs and enormous legal fees. Additionally, some commenters expressed opposition to the rescission of the applicable requirements and prohibitions that appeared at § 88.3 in the 2019 Final Rule because this rescission creates issues with enforcement. Without this provision's language, several commenters said that the rule fails to provide information to covered entities about which statutes apply to them, removes helpful context, and imposes increased costs on covered entities who now have to research over two dozen separate statutes instead of having one place to learn about them.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department thanks the commenters for their recommendations. The Department declines to retain, among other provisions, the applicable requirements and prohibitions that appeared at § 88.3 and the compliance requirements at § 88.6. Specifically, the applicable requirements and prohibitions that appeared at § 88.3 were unnecessary because they simply repeated the language of the underlying statutes.
                        <SU>25</SU>
                        <FTREF/>
                         Some commenters also raised concerns in response to both the 2018 Proposed Rule 
                        <SU>26</SU>
                        <FTREF/>
                         and the proposed rule for this rulemaking that the compliance requirements at § 88.6 were overly burdensome on covered entities and not authorized by the conscience statutes. The concerns raised by commenters highlight significant questions that warrant additional consideration, and in the Department's view, these provisions are not necessary to clarify OCR's processes by which it enforces these statutes. This final rule specifies the Department's procedures for handling conscience complaints in a manner that allows the Department to address conscience complaints on a case-by-case basis to ensure the balance struck by Congress is respected. Finally, the Department notes, as it has already elsewhere, that in response to comments received on the proposed rule, this rule is being finalized with additional enforcement provisions similar to provisions in the 2019 Final Rule that did not raise the same issues as were raised by the other provisions noted above.
                    </P>
                    <FTNT>
                        <P>
                            <SU>25</SU>
                             The Department notes that the model notice text includes a link to the HHS web page where additional resources can be accessed for covered entities and the public to better understand their obligations and rights under the Federal health care conscience statutes. 
                            <E T="03">See</E>
                             U.S. Dep't of Health and Human Servs., Off. for Civil Rights, 
                            <E T="03">Conscience and Religious Nondiscrimination, https://www.hhs.gov/conscience/conscience-protections/index.html.</E>
                             As noted elsewhere in this preamble, the Department agrees it is important to ensure the public is aware of the Federal conscience statutes and remains committed to educating patients, providers, and other covered entities about their rights and obligations under the conscience statutes, including through education and outreach efforts.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>26</SU>
                             
                            <E T="03">See</E>
                             84 FR 23170, 23219 (May 21, 2019).
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter stated that the potential withdrawal of federal funds or the potential for a lawsuit needs to remain in the rule to ensure that there is effective enforcement; and that requirements for reporting incidents of discrimination from § 88.6 of the 2019 Final Rule need to be left in place. One commenter said, “The courts that vacated the 2019 Final Rule did not find that the use of such formal means was impermissible per se, but only that the 2019 rule's text deviated from those existing frameworks in specific ways.” The commenter also said that the final rule should therefore retain OCR's authority to pursue formal as well as informal means of enforcing the conscience statutes.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As discussed in response to other comments, the Department is adding regulatory language to clarify the Department's and OCR's authority to enforce the Federal health care conscience statutes, including through compliance reviews (§ 88.2(a) and a new § 88.2(c)), coordinating other appropriate remedial action (§ 88.2(a)), and OCR's authority to utilize existing enforcement regulations, such as those that apply to grants, contracts, or other programs and services, or withhold relevant funding to the extent authorized under the Federal health care conscience statutes where a matter cannot be resolved by informal means (§ 88.2(g)(3)).
                    </P>
                    <P>As the Department has already noted in response to other comments, the Department determined not to retain, among other provisions, compliance requirements at § 88.6. In the Department's view, this provision is not necessary to clarify OCR's processes by which it enforces these statutes. The Department has concluded that the final rule's enforcement provisions, which set out procedures for the Department to handle conscience complaints on a case-by-case basis as they arise, appropriately permit the Department to ensure compliance with the conscience statutes without raising certain potential concerns commenters identified in connection with compliance provisions included in the 2019 final rule.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters, including several faith-based organizations and a couple non-profits, expressed concern regarding the rescission of the rule of construction and severability provisions at § 88.9 and § 88.10 of the 2019 Final Rule, arguing that they provided much needed clarity as to the Department's interpretation and enforcement of the conscience 
                        <PRTPAGE P="2097"/>
                        protection laws. Three commenters cited caselaw to elaborate that courts and administrative agencies have long recognized that non-discrimination laws should be construed broadly to give full effect to their remedial purposes, and so it would be entirely appropriate for HHS to announce a rule of broad construction in the final rule.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department notes that the language from the severability provision from § 88.10 of the 2019 Final Rule is retained at § 88.4 of the proposed rule and in this final rule. Additionally, as noted in the proposed rule, the enactment of the Federal health care conscience protection statutes represents Congress' attempt to strike a careful balance, and the Department will respect that balance. The conscience statutes each contain particular requirements that must be met in order for them to apply. The Department is committed to meeting its obligations and ensuring compliance with all relevant federal law, including under the Federal conscience statutes.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter stated that the proposed rule does not provide any justification for rescinding the 2019 Final Rule other than by citing 
                        <E T="03">New York</E>
                         v. 
                        <E T="03">U.S. Dep't of Health &amp; Human Servs.,</E>
                         414 F. Supp. 3d 475, 513-14, 535 (S.D.N.Y. 2019), without explaining why HHS is deferring to the court's decision. Many other commenters argued that the Department should not rely on the 
                        <E T="03">New York</E>
                         decision because the district court's ruling was based on an incomplete and incorrect understanding of the underlying legislation. Other commenters maintained that, because only certain provisions of the 2019 Final Rule were held unlawful, the proposed rule over-relied on the finding of the court as to the other provisions in the 2019 Final Rule and did not clearly articulate the reasoning for rescissions in general to specific rescinded provisions.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department respectfully disagrees with commenters that the sole proffered justification for rescinding the 2019 Final Rule was the 
                        <E T="03">New York</E>
                         decision. As the Department noted in the proposed rule, 88 FR 820, 825-26, “[t]he Department proposes to rescind the other portions of the 2019 Final Rule because those portions are 
                        <E T="03">redundant, unlawful, confusing or undermine the balance Congress struck</E>
                         between safeguarding conscience rights and protecting access to health care, or because significant questions have been raised as to their legal authorization.” (Emphasis added). For example, the applicable requirements and prohibitions that appeared at § 88.3 were unnecessary because they simply repeated the language of the underlying statute.
                        <SU>27</SU>
                        <FTREF/>
                         Additionally, the Department received comments in response to the 2018 Proposed Rule and the proposed rule for this final rule that stated that many of the definitions at § 88.2 were confusing or undermined the balance struck by Congress between safeguarding conscience rights and protecting access to care. Likewise, commenters in response to the 2018 Proposed Rule and the proposed rule for this final rule stated that the assurance and certification requirements that appeared at § 88.4 were overly burdensome. The Department also determined that the requirements at § 88.4 are not necessary as the Department has updated the HHS Form 690 Assurance of Compliance (which OCR maintains) independent of the 2019 Final Rule and this rulemaking to include reference to the Federal conscience statutes.
                        <SU>28</SU>
                        <FTREF/>
                         Further, the compliance requirements at § 88.6, the relationship to other laws provision at § 88.8, and rule of construction at § 88.9 (which was echoed in § 88.1) were flagged by commenters to both the 2018 Proposed Rule and the proposed rule for this final rule as, in their view, unlawful or having created confusion or risk of harm by undermining the balance struck by Congress. Finally, as noted in the proposed rule, in the view of the court in the 
                        <E T="03">New York</E>
                         decision, the purpose provision at § 88.1, several of the definitions at § 88.2, and the assurance and certification requirements at § 88.4 were found to be unlawful since the court understood them to impose new substantive duties on regulated entities in the health care sector, beyond the Department's Housekeeping Authority. The district court decisions overlapped with concerns raised by commenters regarding the provisions at § 88.1, several of the definitions at § 88.2, and the assurance and certification requirements at § 88.4, and so the Department determined these concerns warrant additional consideration. In the current instance, however, the Department does not view these provisions as necessary to clarify OCR's processes by which it enforces these statutes. This final rule specifies the Department's procedures for handling conscience complaints in a manner that allows the Department to address conscience complaints on a case-by-case basis to ensure the balance struck by Congress is respected.
                    </P>
                    <FTNT>
                        <P>
                            <SU>27</SU>
                             The Department notes that the model notice text includes a link to the HHS web page where additional resources can be accessed for covered entities and the public to better understand their obligations and rights under the Federal health care conscience statutes. 
                            <E T="03">See</E>
                             U.S. Dep't of Health and Human Servs., Off. for Civil Rights, 
                            <E T="03">Conscience and Religious Nondiscrimination, https://www.hhs.gov/conscience/conscience-protections/index.html.</E>
                             As noted elsewhere in this preamble, the Department agrees it is important to ensure the public is aware of the Federal conscience statutes and remains committed to educating patients, providers, and other covered entities about their rights and obligations under the conscience statutes, including through education and outreach efforts.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>28</SU>
                             
                            <E T="03">See</E>
                             U.S. Dep't of Health and Human Servs., Off. for Civil Rights, “Assurance of Compliance,” HHS Form 690, OMB Control Number 0945-0008 (Last updated Nov. 2019), 
                            <E T="03">https://www.hhs.gov/sites/default/files/form-hhs690.pdf.</E>
                        </P>
                    </FTNT>
                    <P>The Department notes as well, as it has already elsewhere, that in response to comments received on the proposed rule, this rule is being finalized with additional enforcement provisions similar to provisions in the 2019 Final Rule that did not raise the same issues as were raised by the other provisions noted above.</P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter argued that the specified reasons for the removal of § 88.4 are not rational and weaken the argument proffered by the Department that the proposed rule strengthens conscience rights. Some commenters requested that the Department maintain assurance and certification requirements in the final rule as it is a common mechanism for preventing discrimination used in civil rights regulations. Another commenter argued that HHS, at a minimum, must replace the assurance and certification requirements with a requirement that the names of all conscience statutes that a grantee may be subject to be included in the terms of any grant agreements. One commenter argued that the purpose provision of the 2019 Final Rule was necessary evidence of the Department's commitment to ensuring that conscience rights are respected and protected to the furthest extent of the law, and that the rule in general was a vital expression of the need to protect conscience rights in health care, where, in the commenter's view, discrimination against “pro-life” persons is evident.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department believes the final rule clearly demonstrates the Department's commitment to ensuring that the federal conscience statutes are given full effect. The Department determined that the requirements at § 88.4 are not necessary as the Department has updated the HHS Form 690 Assurance of Certification (which OCR maintains) independent of the 2019 Final Rule and this rulemaking to include reference to the Federal conscience statutes. The purpose provision from § 88.1 of the 2019 Final Rule similarly is not necessary for this rule as this rule is not intended to “implement” the conscience statutes. The final rule is the result of the Department's careful efforts to design an 
                        <PRTPAGE P="2098"/>
                        effective system of enforcement that is fully supported by the authority Congress has granted the Department, and these determinations likewise avoid potential concerns raised by the court decisions and commenters regarding §§ 88.4 and 88.1 of the 2019 rule. As noted in the proposed rule, the district court for the Southern District of New York found that, in its view, the 2019 Final Rule's purpose and assurance and certification requirements, among others, “impose[d] new substantive duties on regulated entities in the health care sector” and did not fall within the agency's Housekeeping Authority. 
                        <E T="03">New York,</E>
                         414 F. Supp. 3d at 523.The court's decision raised similar concerns as those raised by commenters in response to both the 2018 Proposed Rule and the proposed rule for this final rule, who stated concerns that those provisions were overly burdensome or overly broad.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Two commenters noted that HHS has explicit rulemaking authority to engage in substantive rulemaking on the conscience protections set out in Sections 1303, 1411, and 1553 of the Affordable Care Act, 42 U.S.C. 18023, 18081, and 18113; and certain Medicare and Medicaid provisions, 42 U.S.C. 1320a-1(h), 1320c-11, 1395i-5, 1395w-22(j)(3)(B), 1395x(e), 1395x(y)(1), 1395cc(f), 1396a(a), 1396a(w)(3), 1396u-2(b)(3)(B), 1397j-1(b), and 14406. The commenters argued that the Department should retain as applicable to those statutes the provisions of the 2019 Final Rule requiring assurances and certifications of compliance, establishing compliance requirements comparable to those applicable to other civil rights laws, and defining terms.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department has carefully considered these comments but declines to make these substantive changes in this final rule at this time. This rule addresses statutes beyond those mentioned by the commenters, and none of the statutes mentioned by the commenters requires the Department to enact regulations for the respective statute's implementation. The Department maintains that addressing all of the statutes listed in § 88.1 uniformly under this rule outweighs the benefits of including piecemeal provisions for certain statutes but not others. The Department will consider, however, whether further rulemaking on the statutes recommended by commenters is needed.
                    </P>
                    <HD SOURCE="HD3">Whether the Rule's Objectives May Also Be Accomplished Through Alternative Means, Such as Outreach and Education</HD>
                    <P>
                        <E T="03">Comment:</E>
                         One professional health care organization stated that they believe physicians are aware of their legal obligations under the conscience statutes, and so the proposed rule is not necessary to enforce the conscience provisions under existing law. A few commenters urged HHS to pursue education and outreach to entities and individuals instead, with some commenters requesting the Department do so as an alternative to rulemaking and others requesting that the Department do so in addition to rulemaking. Commenters stated that such efforts would ensure that physicians and other providers and health care entities are fully aware of their rights and responsibilities under the numerous federal conscience protection laws, especially in light of the proposal to remove the assurance of compliance requirement and to only require voluntary notice.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department thanks the commenters for their recommendations. The Department agrees it is important to ensure the public is aware of the Federal conscience statutes and remains committed to educating patients, providers, and other covered entities about their rights and obligations under the conscience statutes, including through education and outreach efforts. The Department looks forward to working with covered entities and stakeholders to increase outreach activities and ensure awareness. The Department notes as well that it has updated the HHS Form 690 Assurance of Certification (which OCR maintains) to include reference to the Federal conscience statutes as another means of increasing awareness. The Department maintains that that this rule is also an important component of educating the public about these statutes.
                    </P>
                    <HD SOURCE="HD3">9. Comment on the Proposal To Retain a Voluntary Notice Provision, Including Comments on Whether Such Notice Should Be Mandatory, and What a Model Notice Should Include</HD>
                    <HD SOURCE="HD3">Opposition To Retention of Voluntary Notice</HD>
                    <P>
                        <E T="03">Comment:</E>
                         One local government agency argued that having a voluntary notice provision was inconsistent with the scope of the Housekeeping Authority as explained in 
                        <E T="03">City and County of San Francisco</E>
                         v. 
                        <E T="03">Azar,</E>
                         411 F. Supp. 3d 1001 (N.D. Cal. 2019), and argued in favor of returning to the 2011 Final Rule in full. A commenter that provides Skilled Nursing &amp; Assisted Living services opposed the rule's inclusion of a voluntary notice, arguing that there is already overregulation, and adding additional notices would only add confusion and increase anxiety.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         While the court in 
                        <E T="03">San Francisco</E>
                         v. 
                        <E T="03">Azar</E>
                         determined that some provisions in the 2019 Final Rule were “substantive” provisions that were not authorized by the Department's Housekeeping Authority, it did not address that rule's voluntary notice provision. 411 F. Supp. 3d at 1023. This rule lacks the provisions that the 
                        <E T="03">San Francisco</E>
                         v. 
                        <E T="03">Azar</E>
                         court identified as substantive, and, as the notice is voluntary, the rule does not impose new responsibilities on health care providers. The Department maintains that providing notice is an important way for covered entities to promote compliance and ensure the public, patients, and workforce, which may include students or applicants for employment or training, are aware of their rights under the health care conscience protection statutes. The Department declines to remove the voluntary notice provision on the bases cited by the commenters and encourages all covered entities to provide the voluntary notice. As stated in this final rule, the Department will consider posting a notice as a factor in an investigation or compliance review.
                    </P>
                    <HD SOURCE="HD3">Whether the Notice Should Be Mandatory</HD>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters, including some faith-based organizations, elected officials, and professional health care organizations, argued that the voluntary notice provision should be mandatory instead, citing a variety of reasons. A couple of commenters argued that making the notice mandatory would increase awareness of the conscience statutes. Another commenter relied on the concept of notice in many other areas of law to argue that a mandatory notice provision should be applied here. Other commenters, including a professional health care organization, argued that a mandatory notice would increase access to services that providers might object to and supported changes that would ensure that the notice offered information about access to such services. A commenter proposed the notice should include the words “religious and moral beliefs” along with “conscience.”
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department declines to make the notice mandatory, and notes that the 2019 Final Rule notice was also voluntary. The Department also notes that the wide variety of entities subject to the Federal health care conscience 
                        <PRTPAGE P="2099"/>
                        protection statutes would make it difficult to mandate a notice with text that would be relevant to each of those entities. In the Department's view, a voluntary notice with recommended text does a better job of giving covered entities the flexibility to post a notice that is relevant to their obligations without increasing regulatory burden on the Department and covered entities. The Department nonetheless is clarifying in the rule text that posting a notice will be considered as a factor in any relevant OCR investigation or compliance review. Lastly, in response to the commenter's request, the Department has added “religious beliefs or moral convictions” in the model notice.
                    </P>
                    <HD SOURCE="HD3">10. Comment on the Proposal To Retain Portions of the 2019 Final Rule's Enforcement Provisions in the Proposed § 88.2</HD>
                    <HD SOURCE="HD3">General Support</HD>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters, including some faith-based organizations, expressed general support for retaining the complaint handling and investigation provisions in § 88.2 on the grounds that it is an improvement over the 2011 Final Rule, noting that OCR is best equipped to be the central HHS office for receiving and investigating complaints.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department thanks the commenters for sharing their views and agrees that maintaining OCR as the centralized HHS office tasked with receiving and investigating complaints under these provisions will aid the public by increasing awareness of the rights protected by the various statutes and where to file complaints alleging violations of those rights.
                    </P>
                    <HD SOURCE="HD3">Requests for Clarification</HD>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters, including reproductive health organizations and legal organizations, expressed support for the rescission of several portions of the 2019 Final Rule, especially what they characterized as overly broad enforcement provisions, but urged HHS to provide more clarity on the limits of the retained enforcement provisions and on OCR's enforcement authority generally. Some commenters recommended that the Department provide a more detailed justification for the proposal to retain procedural elements from the 2019 Final Rule's § 88.7, which includes the authority to conduct interviews and issue “written data or discovery requests.” 88 FR at 829-30.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department thanks the commenters for sharing their views. Section 88.2(a)(5) makes clear that OCR's authority is to “[c]onsult and coordinate with the relevant Departmental funding component, and 
                        <E T="03">utilize existing enforcement regulations.</E>
                        ” 
                        <SU>29</SU>
                        <FTREF/>
                         These existing enforcement regulations could include, for example, the Department's authority under the Uniform Administrative Requirements, Cost Principles, And Audit Requirements for HHS Awards (UAR; 45 CFR part 75). Second, the ability to conduct interviews and issue written data requests are standard components of OCR's function as an enforcement agency. The Department considers these elements to be part and parcel of the Department's compliance powers, and, as the commenter notes, procedural elements that fall within the Department's Housekeeping Authority. As with its other authorities, OCR may also use the provision of technical assistance or voluntary resolution agreements in an effort to achieve voluntary compliance. The Department's approach to enforcing the Federal health care conscience statutes will continue to rely on the Department's existing compliance and enforcement authority. Finally, the Department notes that, as discussed in response to other comments, the Department is adding regulatory language to clarify the Department's and OCR's authority to enforce the Federal health care conscience statutes, including through compliance reviews (§ 88.2(a) and a new § 88.2(c)), coordinating other appropriate remedial action (§ 88.2(a)), and OCR's authority to utilize existing enforcement regulations or withhold relevant funding to the extent authorized under the Federal health care conscience statutes (§ 88.2(g)(3)) or to refer to the Attorney General (§ 88.2(g)(4)) where a matter cannot be resolved by informal means.
                    </P>
                    <FTNT>
                        <P>
                            <SU>29</SU>
                             Section 88.2(a)(5) of the proposed rule stated, “Consult and coordinate with the relevant Departmental funding component, and utilize existing 
                            <E T="03">regulations enforcement.</E>
                            ” (emphasis added). 88 FR 820, 829. This typo has been corrected in this final rule to “enforcement regulations” instead.
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters expressed concern that the modifications to § 88.7 of the 2019 Final Rule (§ 88.2 of the proposed rule) remove assurances that OCR will conduct a prompt investigation of complaints and investigate complaints involving a potential or threatened failure to comply with the conscience statutes. One individual commenter specifically pointed to the change of verb from “should” to “may” with regard to the investigatory and fact-finding methods the proposed rule stated OCR would employ, which the commenter felt left the Department with too much discretion in the complaint handling process. The commenter stated that the proposed rule fails to clarify which, if any, complaints are accepted, and fails to clarify how complaints are to be handled by OCR, making it uncertain who is allowed to file a complaint.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         OCR reviews all complaints received as a matter of course in its normal business operations and may use some or all of the investigatory tools outlined in § 88.2 in evaluating and investigating a complaint. As noted in the proposed rule, the Department remains committed to educating patients, providers, and other covered entities about their rights and obligations under the conscience statutes and remains committed to ensuring compliance. In addition, the Department is finalizing proposed § 88.2(b) as § 88.2(d) with a revision to state that OCR shall make a 
                        <E T="03">prompt</E>
                         investigation of a complaint alleging failure to comply with the Federal health care conscience protection statutes, and adding a new § 88.2(b) explaining that any entity or individual may file a complaint with OCR alleging a potential violation of Federal health care conscience protection statutes, and that the entity filing does not have to be the entity whose rights have been violated. The Department declines to modify the language of § 88.2(d) to mandate the use of certain investigation methods as not all the investigatory and fact-finding methods available to OCR are appropriate or necessary to be used in all cases. Any relevant complaints filed with the Department will be routed to OCR if they are not initially filed directly with OCR, and OCR will review all received complaints and make a determination regarding the allegations raised.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters criticized the proposed rule and HHS for rescinding portions of the 2019 Final Rule's enforcement provisions and only retaining some, stating it would make it difficult for HHS to protect conscience rights and would lead to discrimination against health care entities and individual providers. Many commenters, including a professional health care organization and a think tank, requested the Department include explicit authority for OCR to pursue formal rather than just informal enforcement and a clear statement on how the Department will interpret the conscience laws in relation to other laws, similar to the language provided in §§ 88.7 and 88.8 of the 2019 Final Rule.
                        <PRTPAGE P="2100"/>
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         OCR works to achieve voluntary compliance with all of its authorities, including HIPAA Privacy, Security, Breach Notification, and Enforcement Rules 
                        <SU>30</SU>
                        <FTREF/>
                         and Title VI.
                        <SU>31</SU>
                        <FTREF/>
                         As finalized in this rule, the Department states that matters of noncompliance will “be resolved by informal means 
                        <E T="03">whenever possible.”</E>
                         (Emphasis added). This is consistent with OCR's approach to enforcement across the authorities it has been delegated and does not preclude the Department from using appropriate formal means at its disposal to achieve compliance whenever it is not possible to resolve a matter through informal means. As well, as discussed in response to other comments, the Department is adding regulatory language to clarify the Department's and OCR's processes and authority to enforce the Federal health care conscience statutes, including through compliance reviews (§ 88.2(a) and a new § 88.2(c)), coordinating other appropriate remedial action (§ 88.2(a)), and OCR's authority to utilize existing enforcement regulations or withhold relevant funding to the extent authorized under the Federal health care conscience statutes where a matter cannot be resolved by informal means (§ 88.2(g)(3)). The Department declines, however, to add § 88.8 from the 2019 Final Rule into this rule as this is a procedural rule that does not address the scope of any substantive right, and thus there is no need to clarify how the rule interacts with laws that do establish protections for religious freedom or moral convictions. Moreover, in the Department's view, it is appropriate to proceed with case-by-case enforcement of the conscience statutes. The Department has determined therefore that additional guidance is not necessary at this point.
                    </P>
                    <FTNT>
                        <P>
                            <SU>30</SU>
                             
                            <E T="03">See</E>
                             45 CFR 160.304.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>31</SU>
                             
                            <E T="03">See</E>
                             28 CFR 42.411 (“Effective enforcement of title VI requires that agencies take prompt action to achieve 
                            <E T="03">voluntary</E>
                             compliance in all instances in which noncompliance is found.” (emphasis added)).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">III. Statutory Authority</HD>
                    <P>The Secretary is partially rescinding the May 21, 2019, Final Rule entitled “Protecting Statutory Conscience Rights in Health Care; Delegations of Authority.” As discussed above, the Church Amendments, section 245 of the PHS Act, the Weldon Amendment, and the Affordable Care Act require, among other things, that the Department and recipients of Department funds (including State and local governments) refrain from discriminating against institutional and individual health care entities for their participation in, abstention from, or objection to certain medical procedures or services, including certain health services, or research activities funded in whole or in part by the federal government. No statutory provision, however, requires promulgation of regulations for their interpretation or implementation. This rule is being issued pursuant to the authority of 5 U.S.C. 301, which empowers the head of an Executive department to prescribe regulations “for the government of his department, the conduct of its employees, the distribution and performance of its business, and the custody, use, and preservation of its records, papers, and property.”</P>
                    <HD SOURCE="HD1">IV. Overview and Section-by-Section Description of the Final Rule</HD>
                    <P>
                        Section 88.1 describes the purpose of the Final Rule. The language is revised from the 2019 Final Rule, and states that the purpose of this Part 88 is to provide for the enforcement of the Church Amendments, 42 U.S.C. 300a-7; the Coats-Snowe Amendment, section 245 of the Public Health Service Act, 42 U.S.C. 238n; the Weldon Amendment, 
                        <E T="03">e.g.,</E>
                         Consolidated Appropriations Act, 2023, Public Law 117-328, div. H, title V General Provisions, section 507(d)(1) (Dec. 29, 2022); Sections 1303(b)(1)(A), (b)(4), and (c)(2)(A), and 1411(b)(5)(A), and 1553 of the ACA, 42 U.S.C. 18023(b)(1)(A), (b)(4), and (c)(2)(A), 18081(b)(5)(A), and 18113; certain Medicare and Medicaid provisions, 42 U.S.C. 1320a-1(h), 1320c-11, 1395i-5, 1395w-22(j)(3)(B), 1395x(e) 1395x(y)(1), 1395cc(f), 1396a(a), 1396a(w)(3), 1396u-2(b)(3)(B), 1397j-1(b), and 14406; the Helms, Biden, 1978, and 1985 Amendments, 22 U.S.C. 2151b(f); 
                        <E T="03">accord., e.g.,</E>
                         Consolidated Appropriations Act, 2023, Public Law 117-328, div. H, section 209, div. K, title VII, section 7018 (Dec. 29, 2022); 22 U.S.C. 7631(d42 U.S.C. 280g-1(d), 290bb-36(f), 1396f, 1396s(c)(2)(B)(ii); 5106i(a); and 29 U.S.C. 669(a)(5), referred to collectively as the “Federal health care conscience protection statutes.” The Department is finalizing this provision with two changes. First, in response to a comment, the Department is removing the word “provider” from the proposed rule's collective reference of the “federal health care conscience protection statutes.” Second, the Department identified and corrected an error in the citations to the Medicare and Medicaid statutes. The proposed rule cites 42 U.S.C. 1395w-22(j)(3)(A) and 1396u-2(b)(3)(A) as conscience provisions when 42 U.S.C. 1395w-22(j)(3)(B) and 1396u-2(b)(3)(B) are the relevant conscience provisions.
                    </P>
                    <P>
                        Sections 88.2 through 88.4 of the 2019 Final Rule have been removed. The language of § 88.7 of the 2019 Final Rule has been revised and redesignated as § 88.2 in this final rule. Section 88.2 in this final rule states under paragraph (a) that OCR has been delegated the authority to facilitate and coordinate the Department's enforcement of the Federal health care provider conscience protection statutes and includes a list of related authorities. This includes three authorities that did not appear in the proposed rule, but which the Department is finalizing at § 88.2(a)(2), (7), and (8) addressing OCR's authority to initiate compliance reviews, “coordinate other appropriate remedial action as the Department deems necessary and as allowed by law and applicable regulation,” and “make enforcement referrals to the Department of Justice.” In response to comments, the Department is finalizing this rule with a new § 88.2(b) and (c) to clarify OCR's authority to conduct compliance reviews and to clarify who may file a complaint with OCR regarding the Federal health care conscience protection statutes. Section 88.2(b) of the proposed rule has been redesignated in this final rule as § 88.2(d) and describes OCR's investigation process. In response to comments, the Department is finalizing § 88.2(d) with a revision to state that OCR shall make a 
                        <E T="03">prompt</E>
                         investigation of a complaint alleging failure to comply with the Federal health care conscience protection statutes. The Department is also making a technical edit to remove the term “discovery” from § 88.2(d) as that term is generally used in litigation, but is keeping the term “data request.” The Department is also finalizing this rule with a new § 88.2(e) that did not appear in the proposed rule, but which now notes that, “OCR may adopt a negative inference if, absent good cause, an entity that is subject to the Federal health care conscience protection statutes fails to respond to a request for information or to a data or document request within a reasonable timeframe.” Proposed § 88.2(c) has been redesignated as § 88.2(f) and describes OCR's role in providing supervision and coordination of compliance where OCR makes a determination as a result of an investigation that an entity is not compliant with their responsibilities under the Federal health care conscience protection statutes. Proposed § 88.2(d) has been redesignated as § 88.2(g) and describes OCR's process for achieving resolution of matters. In 
                        <PRTPAGE P="2101"/>
                        response to comments, the Department is finalizing § 88.2(g) with a new paragraph (3) that describes OCR's authority to “coordinate with the relevant Departmental component to (1) utilize existing enforcement regulations, such as those that apply to grants, contracts, or other programs and services, or (2) withhold relevant funding to the extent authorized under the statutes listed under § 88.1” where informal means of achieving compliance have failed to resolve a given matter. In response to comments, the Department is also finalizing § 88.2(g) with a new paragraph (4) that describes OCR's authority to “in coordination with the Office of the General Counsel, refer the matter to the Department of Justice for proceedings to enforce the statutes listed under § 88.1” where informal means of achieving compliance have failed to resolve a given matter.
                    </P>
                    <P>Section 88.5 of the 2019 Final Rule has been revised and redesignated as § 88.3 of this final rule. In response to comments, section 88.3(a) in this final rule now states that OCR considers the posting of a notice consistent with this part “as a best practice towards achieving compliance with and educating the public about the Federal health care conscience protection statutes, and encourages all entities subject to the Federal health care conscience protection statutes to post the model notice provided in Appendix A.” In addition, we have also added to section 88.3(a) language to explain that “OCR will consider posting a notice as a factor in any investigation or compliance review under this rule.” Section 88.3(b) describes places where the model notice in Appendix A should be posted. Section 88.3(c) describes the format of the notice. Section 88.3(d) describes the content of the notice text. Section 88.3(e) provides that the Department and each recipient may post the notice text along with the content of other notices (such as other nondiscrimination notices). The language from Appendix A to Part 88 in the 2019 Final Rule has been revised but is still designated as Appendix A to Part 88 in this final rule. The Department is finalizing the text of Appendix A with one change in response to commenters to include a statement for clarity that “You may have rights as a provider, patient, or other individual under these Federal statutes, which prohibit coercion or other discrimination on the basis of conscience in certain circumstances.”</P>
                    <HD SOURCE="HD1">V. Regulatory Impact Analysis</HD>
                    <HD SOURCE="HD2">A. Introduction</HD>
                    <P>The Department has examined the impacts of this Final Rule under Executive Order 12866, Executive Order 13563, the Regulatory Flexibility Act (5 U.S.C. 601-612), and the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4). Executive Orders 12866 and 13563 direct agencies to assess all costs and benefits of available regulatory alternatives and, when regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety, and other advantages; distributive impacts; and equity). The Office of Information and Regulatory Affairs has designated this final rule significant under Section 3(f)(1) of Executive Order 12866, as amended by Executive Order 14094. The Department addresses the Regulatory Flexibility Act below.</P>
                    <P>The Unfunded Mandates Reform Act of 1995 (section 202(a)) requires agencies to prepare a written statement, which includes an assessment of anticipated costs and benefits, before proposing “any rule that includes any Federal mandate that may result in the expenditure by State, local, and tribal governments, in the aggregate, or by the private sector, of $100,000,000 or more (adjusted annually for inflation) in any 1 year.” The current threshold after adjustment for inflation is approximately $177 million, using the most current (2022) Implicit Price Deflator for the Gross Domestic Product. This proposed rule would not create an unfunded mandate under the Unfunded Mandates Reform Act because it does not impose any new requirements resulting in unfunded expenditures by state, local, and tribal governments, or by the private sector.</P>
                    <P>
                        Congress enacted the Paperwork Reduction Act of 1995 to “maximize the utility of information created, collected, maintained, used, shared and disseminated by or for the Federal government” and to minimize the burden of this collection. 44 U.S.C. 3501(2). This final rule does not require new collections of information under the Paperwork Reduction Act of 1995. 
                        <E T="03">See generally</E>
                         44 U.S.C. 3501-3520.
                    </P>
                    <P>The Department made several changes to this Regulatory Impact Analysis (RIA) in response to public comment to the RIA that was published with the proposed rule in January 2023. In response to multiple comments regarding potential cost savings against a baseline of the 2019 Final Rule, the Department reviewed all RIA cost categories from the 2019 Final Rule to determine if they will be potentially recoverable by virtue of the recission of the 2019 Final Rule. The Department concluded that regulatory familiarization costs likely happened immediately following the publication of the 2019 Final Rule and would not be recoverable as a result of this final rule. The Department determined that all other cost categories might be considered as potential savings in a rescission scenario. We also added regulatory familiarization costs in response to concerns about the need of various stakeholders to review the provisions of this rule. Finally, the Department addressed comments about the impacts to small businesses by including a separate regulatory flexibility analysis section.</P>
                    <HD SOURCE="HD2">B. Requests for Comment</HD>
                    <P>The Department solicited comments on the proposed rule's RIA, including whether the non-quantified impacts identified in the 2019 Final Rule's RIA would likely be realized, absent any further regulatory action. The Department responds to those comments here.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter said that the 2019 Final Rule would have been burdensome because providers would have had to: obtain legal counsel to determine whether and how policies must be altered; revise employment manuals and training programs; maintain the records the Rule requires; and provide the mandated assurances and certifications.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department thanks the commenter for insight into potential burdens.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that HHS did not “adequately or accurately” consider the costs of the proposed rulemaking. The commenter elaborated that the RIA did not show that the proposed rule is justified “when evaluated reasonably,” stating that the primary baseline used is “irrational and self-contradictory.” The commenter disagreed that the Department's explanation of the proposed rescissions of the 2019 Final Rule could be considered a savings, since the rule was not put into effect. The commenter stated that HHS should use its alternative baseline scenario, which assumes the 2019 Final Rule to be unimplemented, instead of the primary baseline to avoid arbitrariness. The commenter also said that the Department underestimates the impact of the proposed rule because the calculations under the alternative baseline in the RIA leave out the familiarization costs included with the 2019 Final Rule's RIA.
                        <PRTPAGE P="2102"/>
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department acknowledges the commenter's concern. The two baselines in question—the primary baseline that the 2019 Final Rule would go into effect and the alternative baseline that it would never go into effect—involve different ways of looking at the economic impact of the rule, not the justification for the rule. The Department continues to use the primary baseline but presents the alternative baseline as well.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that the RIA published with the proposed rule excludes the impact of the rulemaking on voluntary remedial efforts. The commenter cited the 2019 Final Rule's RIA statement that “some recipients will institute a grievance or similar process to handle internal complaints raised to the recipient's or sub-recipient's attention,” and concluded that “an additional undiscounted 5-year cost of $36 million at minimum must be added to the total cost of the proposed rule.” The commenter stated that there is no reason to suggest that the proposed rule will not cause adoption of the same number of grievance processes as the 2019 Final Rule would have.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department has reviewed this comment and disagrees. The commenter did not provide any new data to support the argument that the Department should adopt a particular view regarding how many entities will adopt a grievance or other remedial process. The Department does have reason to disagree with the remedial costs being identical, as significant provisions from the 2019 Final Rule that would likely have incentivized entities to voluntarily adopt grievance processes are removed. The rule rescinds significant portions of the 2019 Final Rule including required assurance and compliance provisions. Absent new data, the Department continues to believe that the recissions in this final rule will generate $8.3 million per year in savings through less grievance costs.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter claimed that if the assurance and certification requirements of the 2019 Final Rule were “redundant and unnecessary” as HHS described them in the proposed rule, then “there would likely not be any costs within the first five years of publication” since “entities were already fully taking steps to be educated on, and comply with, all the laws that are the subject of this rule,” as stated in the 2019 Final Rule's RIA. Given this assumption, the commenter continued, then the impact of the 2019 Final Rule should be reduced by the $255.3 million in assurance and certification impact, bringing the total undiscounted cost of the 2019 Final Rule to $769.7 million. The commenter argued that this “overall lack of consideration of cost itself” constitutes a failure to meet the demands of 
                        <E T="03">Michigan</E>
                         v. 
                        <E T="03">EPA.</E>
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The commenter quotes from the 2019 Final Rule's RIA's statement that there would likely not be “any costs within the first five years of publication” for 
                        <E T="03">remedial efforts</E>
                         taken by a recipient to meet the assurance and certification requirements in §  88.4 if “entities were already fully taking steps to be educated on, and comply with, all the laws that are the subject of this rule[.]” In other words, the costs of these remedial efforts would be zero if entities were taking these steps. But this conclusion cannot be extrapolated to the assurance and compliance requirements more generally. Section 88.4(b)(6) of the 2019 Final Rule required annual assurance and certification to OCR. These assurance and certification costs were projected to occur regardless of whether entities were already educated about the health care conscience protection statutes.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters suggested that, because a pandemic has occurred since the 2019 Final Rule, various estimates in the RIA are unreliable because of the strain on the health care community, including from loss of staffing.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department agrees with the commenter that the impact estimates of the final rule are subject to several sources of uncertainty, including any impacts of the COVID-19 pandemic on covered entities. However, the comment did not provide any new data to explain which numbers in the 2019 RIA should be changed because of the noted strain due to the pandemic. The comment also did not provide a recommended approach for projecting these impacts over the 5-year time horizon of the analysis of the final rule. The Department notes that, while the analysis does not modify its estimates based on impacts related to the COVID-19 pandemic, it does address uncertainty, including by assessing a secondary baseline scenario.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters urged HHS to consider additional costs in the calculation of the final rule. These included: the impact of turnover, increased agency costs, increased litigation, and risk management costs; the costs of potential increased conscience and religious freedom complaints; the Federalism implications associated with impacts on state hospitals, medical facilities, and insurance plans, as well as the interaction with state and local laws regarding conscience and religious freedom; specific costs, such as: the stresses placed on the nation's infrastructure of health care as a whole, and the public health consequences of “conscientious providers” leaving the workforce; the loss of access to certain providers; the costs that may result from companies that choose to ignore conscience protections, and thus lose employees and patients as a result; the compound effect of the rule's impact on existing labor shortages, among others.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department is unable to quantify most of these costs, as the necessary data are not provided by the commenter and are not available in any data sources that the Department has reviewed. This approach is consistent with the 2019 Final Rule, in which these potential effects were discussed qualitatively but were also not quantified.
                    </P>
                    <P>In response to the concerns about federalism, some of the Federal laws that this rule implements and enforces, such as the Weldon and Coats-Snowe Amendments, directly regulate States and local governments that receive Federal funding by conditioning the receipt of such funding on the governments' commitments to refrain from discrimination on certain bases or by imposing certain requirements on States and local governments that receive Federal funding. This impact, however, is a result of the statutory prohibitions and requirements themselves and are not due to the mechanisms provided by this rule.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter pointed out that a premise of the 2019 Final Rule was that the 2019 Final Rule would expand access to health care, specifically by reducing barriers to the entry of certain health professionals and delaying the exit of certain health professionals from the field, by reducing discrimination or coercion that health professionals anticipate or experience. The commenter suggested that the proposed rule's disagreement with this conclusion means the Department (which continues to rely on the 2019 RIA) now underestimates the effects of reversing the 2019 Final Rule, as the commenter agrees with the 2019 Final Rule's assessment of its effects.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department has reviewed this comment and found that it does not provide any new data or other actionable information relevant to the economic analysis. Consistent with numerous comments received on the 2018 proposed rule, the Department has no reason to conclude that the 2019 Rule would have resulted in more providers entering the workforce or 
                        <PRTPAGE P="2103"/>
                        would have resulted in greater patient access to care.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Commenters had varying views regarding what percent of providers would post the voluntary notice. One commenter, who suspected the percent of covered entities posting voluntary notices would be minimal, requested that OCR better estimate the percentage of entities that will comply with the proposed posting notice on a voluntary basis. Another commenter suggested it would be reasonable for the Department to assume that all entities will provide voluntary notices, and, therefore, the overall cost to covered entities from posting the voluntary notices will be higher than the RIA states.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Department has reviewed this issue but disagrees that nearly all entities will post a voluntary notice. No commenter provided data to support their assertion that all covered entities or else a minimal number of covered entities will post the voluntary notice. After consideration, the Department in this final rule maintains the 2019 Final Rule RIA's estimate that half of all entities would post a voluntary notice in this final rule. If all entities posted a voluntary notice, the costs associated would be equivalent to the costs of a mandatory notice summarized in Policy Option 3 (this final rule, modified to include a mandatory notice). This final rule adopts a voluntary notice provision, and the cost is the same as the cost of the 2019 Final Rule's voluntary notice provision summarized in Policy Option 2 (this final rule).
                    </P>
                    <HD SOURCE="HD2">C. Detailed Economic Analysis</HD>
                    <P>HHS considered several policy alternatives, in addition to the approach of this final rule. This economic analysis considers the likely impacts associated with the following three policy options: (1) rescinding the 2019 Final Rule without exceptions; (2) adopting the approach of this final rule, which partially rescinds the 2019 Final Rule, and modifies other provisions; and (3) adopting the approach of this final rule, except further modifying the notice provision to require mandatory notices instead of voluntary notices. To simplify the narrative of this RIA, we present the impacts of rescinding the 2019 Final Rule in its entirety first, and then present the impacts of a partial rescission with modifications. These modifications correspond to the policy option of the final rule, and the policy option of mandatory notices. This RIA then summarizes the impacts of each policy option against common assumptions about the baseline scenario of no further regulatory action.</P>
                    <HD SOURCE="HD3">Policy Option 1: Rescinding the 2019 Final Rule</HD>
                    <P>
                        Rescinding the final rule entitled “Protecting Statutory Conscience Rights in Health Care; Delegations of Authority,” published in the 
                        <E T="04">Federal Register</E>
                         on May 21, 2019 (84 FR 23170, 45 CFR part 88) (hereafter, “2019 Final Rule”) would prevent the realization of many of the anticipated impacts of the 2019 Final Rule. For the purposes of this economic analysis, we provisionally adopt the characterization and quantification of these impacts that were presented in the regulatory impact analysis (RIA) of the 2019 Final Rule. The potential impacts identified and estimated in the RIA covered a five-year time horizon following the effective date of the 2019 Final Rule. However, because the 2019 Final Rule has been vacated by three federal district courts, these impacts have mostly not occurred and are not likely to occur. The litigation status of the 2019 Final Rule introduces substantial analytic uncertainty into any characterization of the baseline scenario of no further regulatory action. We address this uncertainty directly by analyzing the potential impacts of Policy Option 1 under two discrete baseline scenarios. First, for the purposes of this economic analysis, we adopt a primary baseline scenario that the 2019 Final Rule would take effect. Second, we adopt an alternative baseline scenario that the 2019 Final Rule would never take effect, even without any subsequent regulatory action.
                    </P>
                    <P>Under our primary baseline scenario, Policy Option 1 would entirely reverse the impacts of the 2019 Final Rule. To analyze the impacts of Policy Option 1 under this scenario, we provisionally adopt the estimates of the likely impacts of the 2019 Final Rule in its RIA, although we understand that commenters raised questions whether, for example, certain of the non-quantified benefits that the 2019 Final Rule anticipated would in fact be realized. The RIA identified five categories of quantified costs: (1) familiarization; (2) assurance and certification; (3) voluntary actions to provide notices of rights; (4) voluntary remedial efforts; and (5) OCR enforcement and associated costs. The narrative of the RIA described an approach for estimating each of these costs, and Table 6 of the RIA summarized the timing and magnitude of these quantified costs (84 FR 23240). In addition to identifying quantified costs, the RIA identified non-quantified costs associated with compliance procedures and non-quantified costs associated with seeking alternative providers of certain objected to medical services or procedures.</P>
                    <P>
                        The 2019 Final Rule's RIA did not identify any quantified benefits, but identified non-quantified benefits associated with compliance with the law; protection of conscience rights, the free exercise of religion and moral convictions; more diverse and inclusive providers and health care professionals; improved provider-patient relationships that facilitate improved quality of care; equity, fairness, nondiscrimination; and increased access to care. The District Court in 
                        <E T="03">New York,</E>
                         however, also identified some non-quantified costs of the 2019 Final Rule, including: “that the Rule could potentially impose liability on an employer . . . for insisting that an ambulance driver complete a mission of transporting a patient to a hospital for an emergency procedure,” that the Rule “would authorize individuals [to leave] the operating theater or medical procedure [and] withhold their services,” and other instances of failing to provide care in life-threatening situations. 414 F.Supp.3d at 539, 519, 514 (citing 
                        <E T="03">Shelton</E>
                         v. 
                        <E T="03">Univ. of Med. &amp; Dentistry of N.J.,</E>
                         223 F.3d 220, 222-23, 224-28 (3d Cir. 2000)). The Department has no reason to conclude that, consistent with numerous comments received on the 2018 proposed rule, the 2019 Rule would have resulted in more providers entering the workforce or would have resulted in greater patient access to care, and acknowledges the potential harms raised by the 
                        <E T="03">New York</E>
                         decision. In addition, the Department notes that there are non-quantifiable benefits of this revised rule, including respecting Congress' attempt to strike a careful balance between patient and provider rights, ensuring patient access to health care, notifying the public of OCR's existing authorities on conscience laws, and clarifying to the public what OCR's process is for handling complaints under these authorities.
                    </P>
                    <P>
                        Table 1 of the 2019 Final Rule's RIA reported the present value and annualized value of the quantified costs and summarized the non-quantified costs and benefits of the 2019 Final Rule (84 FR 23227). That RIA reported estimates of the present value of the total costs over a 5-year time horizon of $900.7 million using a 3-percent discount rate and $731.5 million using a 7-percent discount rate. That RIA also reported annualized estimates of the costs of $214.9 million under a 3-percent discount rate and $218.5 million using a 7-percent discount rate. 
                        <PRTPAGE P="2104"/>
                        Both sets of these cost estimates were reported in year 2016 dollars. We updated these estimates to year 2022 dollars using the Implicit Price Deflator for the Gross Domestic Product. We removed the regulatory familiarization costs for the 2019 Final Rule from the potential costs savings, as we believe these were incurred in full upon publication of the rule and will therefore be non-recoverable despite the partial recission of the 2019 Final Rule. Likewise, we added regulatory familiarization costs for this final rule following the general methodology of the 2019 Final Rule updated with the most recent available data. We estimate that 513,627 entities will spend 2 hours of legal professional time to review the document. To determine the cost of legal professional time, we use the average wage for Lawyers (OES 23-1011) and load it with the factor for all civilian workers.
                        <SU>32</SU>
                        <FTREF/>
                         As Table 1 notes below, the present value of these familiarization costs add up to $114 million using a 3-percent discount rate, or $106 million using a 7-percent discount rate; they will also partially offset any cost savings in the first year of this current rule. The annualized costs are $24.8 million, and $23.2 million, respectively.
                    </P>
                    <FTNT>
                        <P>
                            <SU>32</SU>
                             U.S. Dep't of Labor, Bureau of Labor Statistics, 
                            <E T="03">May 2022 State Occupational Employment and Wage Estimates</E>
                             (Last visited October 30, 2023), 
                            <E T="03">https://www.bls.gov/oes/current/oessrcst.htm;</E>
                             U.S. Dep't of Labor, Bureau of Labor Statistics, 
                            <E T="03">Employer Costs for Employee Compensation,</E>
                             Quarter 1, 2023 (Last visited October 30, 2023), 
                            <E T="03">https://www.bls.gov/ecec/data.htm.</E>
                        </P>
                    </FTNT>
                    <P>HHS next estimated the Policy Option 1 cost savings by calculating the total potentially recoverable costs from fully rescinding the 2019 Final Rule and adjusting them with the new regulatory familiarization costs. The present value of potentially recoverable costs from fully rescinding the 2019 Final Rule is $1,026.0 million using a 3-percent discount rate and $856.8 million using a 7-percent discount rate; these cover assurance and certification, voluntary notice and remedial efforts, and OCR enforcement costs (see Table 1 below for detailed breakdown of individual costs), and annualized costs of $224.0 million using a 3-percent discount rate and $187.1 million using a 7-percent discount rate. Under our primary baseline scenario, the cost savings of Policy Option 1 would be approximately the inverse of the impacts contained in the 2019 potentially recoverable costs from the 2019 Final Rule's RIA plus the newly incurred regulatory familiarization cost. These cost savings sum up to a total discounted value of $912.3 million at a 3-percent discount rate, or $750.5 million using a 7-percent discount rate; the annualized values are, $199.2 million, and $163.9 million, respectively. Table A in the Summary of Impacts section of this preliminary regulatory impact analysis reports the summary impacts of the Policy Option 1 under this baseline scenario in millions of 2022 dollars, covering a 5-year time horizon, including annualized values, and Table 1 reports the detailed impacts in this primary baseline scenario, by cost category.</P>
                    <GPOTABLE COLS="7" OPTS="L2,i1" CDEF="s50,8,8,8,8,8,8">
                        <TTITLE>Table 1—Costs and Cost Savings—Option 1 (Primary Baseline)</TTITLE>
                        <TDESC>[Discounted 3% and 7% in millions]</TDESC>
                        <BOXHD>
                            <CHED H="1"> </CHED>
                            <CHED H="1">Year 1</CHED>
                            <CHED H="1">Year 2</CHED>
                            <CHED H="1">Year 3</CHED>
                            <CHED H="1">Year 4</CHED>
                            <CHED H="1">Year 5</CHED>
                            <CHED H="1">Total</CHED>
                        </BOXHD>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">Costs and Cost Savings—Option 1</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Familiarization (undiscounted)</ENT>
                            <ENT>$117.2</ENT>
                            <ENT>$0.0</ENT>
                            <ENT>$0.0</ENT>
                            <ENT>$0.0</ENT>
                            <ENT>$0.0</ENT>
                            <ENT>$117.1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Familiarization (3%)</ENT>
                            <ENT>113.8</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>113.7</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Familiarization (7%)</ENT>
                            <ENT>106.3</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>106.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Assurance and Certification (undiscounted)</ENT>
                            <ENT>−187.2</ENT>
                            <ENT>−171.1</ENT>
                            <ENT>−171.1</ENT>
                            <ENT>−171.1</ENT>
                            <ENT>−171.1</ENT>
                            <ENT>−871.5</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Assurance and Certification (3%)</ENT>
                            <ENT>−181.7</ENT>
                            <ENT>−161.3</ENT>
                            <ENT>−156.6</ENT>
                            <ENT>−152.0</ENT>
                            <ENT>−147.6</ENT>
                            <ENT>−799.1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Assurance and Certification (7%)</ENT>
                            <ENT>−169.8</ENT>
                            <ENT>−140.8</ENT>
                            <ENT>−127.8</ENT>
                            <ENT>−116.0</ENT>
                            <ENT>−105.2</ENT>
                            <ENT>−659.6</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Voluntary Notice (undiscounted)</ENT>
                            <ENT>−112.3</ENT>
                            <ENT>−17.0</ENT>
                            <ENT>−17.0</ENT>
                            <ENT>−17.0</ENT>
                            <ENT>−17.0</ENT>
                            <ENT>−180.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Voluntary Notice (3%)</ENT>
                            <ENT>−109.1</ENT>
                            <ENT>−16.0</ENT>
                            <ENT>−15.5</ENT>
                            <ENT>−15.1</ENT>
                            <ENT>−14.6</ENT>
                            <ENT>−170.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Voluntary Notice (7%)</ENT>
                            <ENT>−101.9</ENT>
                            <ENT>−14.0</ENT>
                            <ENT>−12.7</ENT>
                            <ENT>−11.5</ENT>
                            <ENT>−10.4</ENT>
                            <ENT>−150.6</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Voluntary Remedial Efforts (undiscounted)</ENT>
                            <ENT>−8.8</ENT>
                            <ENT>−8.8</ENT>
                            <ENT>−8.8</ENT>
                            <ENT>−8.8</ENT>
                            <ENT>−8.8</ENT>
                            <ENT>−43.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Voluntary Remedial Efforts (3%)</ENT>
                            <ENT>−8.5</ENT>
                            <ENT>−8.3</ENT>
                            <ENT>−8.0</ENT>
                            <ENT>−7.8</ENT>
                            <ENT>−7.6</ENT>
                            <ENT>−40.2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Voluntary Remedial Efforts (7%)</ENT>
                            <ENT>−8.0</ENT>
                            <ENT>−7.2</ENT>
                            <ENT>−6.6</ENT>
                            <ENT>−5.9</ENT>
                            <ENT>−5.4</ENT>
                            <ENT>−33.1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">OCR Enforcement Costs (undiscounted)</ENT>
                            <ENT>−3.6</ENT>
                            <ENT>−3.6</ENT>
                            <ENT>−3.6</ENT>
                            <ENT>−3.6</ENT>
                            <ENT>−3.6</ENT>
                            <ENT>−17.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">OCR Enforcement Costs (3%)</ENT>
                            <ENT>−3.5</ENT>
                            <ENT>−3.4</ENT>
                            <ENT>−3.3</ENT>
                            <ENT>−3.2</ENT>
                            <ENT>−3.1</ENT>
                            <ENT>−16.4</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">OCR Enforcement Costs (7%)</ENT>
                            <ENT>−3.3</ENT>
                            <ENT>−3.0</ENT>
                            <ENT>−2.7</ENT>
                            <ENT>−2.4</ENT>
                            <ENT>−2.2</ENT>
                            <ENT>−13.5</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="03">Total Costs (undiscounted)</ENT>
                            <ENT>−194.6</ENT>
                            <ENT>−200.4</ENT>
                            <ENT>−200.4</ENT>
                            <ENT>−200.4</ENT>
                            <ENT>−200.4</ENT>
                            <ENT>−996.4</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="03">Total Costs (3%)</ENT>
                            <ENT>−189.0</ENT>
                            <ENT>−188.9</ENT>
                            <ENT>−183.4</ENT>
                            <ENT>−178.1</ENT>
                            <ENT>−172.9</ENT>
                            <ENT>−912.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total Costs (7%)</ENT>
                            <ENT>−176.6</ENT>
                            <ENT>−165.0</ENT>
                            <ENT>−149.7</ENT>
                            <ENT>−135.8</ENT>
                            <ENT>−123.3</ENT>
                            <ENT>−750.5</ENT>
                        </ROW>
                        <TNOTE>
                            <E T="02">Notes:</E>
                             Negative costs indicate the Policy Option, if finalized would result in cost savings.
                        </TNOTE>
                    </GPOTABLE>
                    <P>
                        Under our alternative baseline scenario, we assume that the 2019 Final Rule would never take effect, even without any additional regulatory action. Under this baseline scenario, Policy Option 1 would maintain the current status quo, which is characterized by the 2011 Final Rule (76 FR 9968). Thus, for this baseline scenario, we conclude that adopting Policy Option 1 would result in the new regulatory familiarization costs (discussed above) plus other 
                        <E T="03">de minimis</E>
                         impacts that we do not quantify, such as resolving any regulatory uncertainty associated with the 2019 Final Rule, which has been vacated by three federal courts but not rescinded. We report the summary impacts of Policy Option 1 under this alternative baseline scenario in Table A in the Impacts Summary section.
                    </P>
                    <HD SOURCE="HD3">Policy Option 2: The Final Rule</HD>
                    <P>
                        The final rule partially rescinds the 2019 Final Rule, with certain exceptions. Specifically, this final rule retains three aspects of the 2019 Final Rule: (1) the addition to part 88 of statutes included in the 2019 Final Rule; 
                        <PRTPAGE P="2105"/>
                        (2) several enforcement provisions; and (3) a voluntary notice provision.
                        <SU>33</SU>
                        <FTREF/>
                         However, as described in greater detail in the Preamble, the Department is also modifying each of these provisions of the 2019 Final Rule. For example, the voluntary notice provision in the proposed rule would clarify that providing these voluntary notices would not satisfy an entity's substantive obligations imposed upon covered entities by the underlying statutes.
                    </P>
                    <FTNT>
                        <P>
                            <SU>33</SU>
                             The Department also keeps the severability clause from the 2019 Final Rule.
                        </P>
                    </FTNT>
                    <P>We considered the likely impacts of each of the three retained aspects of the 2019 Final Rule. The Department estimates that maintaining the statutes from the 2019 Final Rule will not impact costs. For the remaining two aspects of the 2019 Final Rule, we identify quantifiable impacts associated with retaining the aspects of the 2019 Final Rule related to the enforcement provisions and quantifiable impacts related to the voluntary notice provision. We adopt the analytic approach contained in the 2019 Final Rule's RIA to quantify these impacts, including an assumption in that RIA that about half of covered entities would provide notices voluntarily. For the provisions related to enforcement, the 2019 RIA estimated an annual impact of about $3 million in costs to the Department and $15 million in total costs over five years. For the provisions related to voluntary notices, that RIA estimated an impact of about $93.4 million in costs in the first year of the analysis, and about $14.1 million in costs in subsequent years, or about $150 million over five years. Combined, the 2019 RIA estimated 5-year costs for these two provisions of $165 million; in present value terms, these estimates are $142 million using a 3-percent discount rate and $118 million using a 7-percent discount rate. The 2019 RIA reported these costs in 2016 dollars.</P>
                    <P>To quantify the net impact of this rule, we fully remove the costs associated with enforcement and voluntary notice provisions from our earlier estimates of the total cost savings of rescinding the 2019 Final Rule. Since the voluntary notice requirement will not be rescinded, and some enforcement provisions will be retained, we anticipate that there will be no cost savings against the 2019 Final Rule under these cost categories. As an intermediate step, we converted the 2016 dollar estimates from the previous paragraph to 2022 dollars using the Implicit Price Deflator for the Gross Domestic Product. Compared to our primary baseline, we estimate that over the first five years of this rule, this rule will result in total cost savings in 2022 dollars of $725.5 million using a 3-percent discount rate and $586.4 million using a 7-percent discount rate (as shown in Table 2); the corresponding annualized cost savings are $158.4 million using a 3-percent discount rate and $128.0 million using a 7-percent discount rate. We report these estimates in Table A in the Summary of Impacts section, which also reports comparable estimates corresponding to our alternative baseline scenario, and include a detailed breakdown of primary baseline costs in Table 2 below.</P>
                    <GPOTABLE COLS="7" OPTS="L2,i1" CDEF="s50,8,8,8,8,8,8">
                        <TTITLE>Table 2—Costs and Cost Savings—Option 2 (Primary Baseline)</TTITLE>
                        <TDESC>[Discounted 3% and 7% in millions]</TDESC>
                        <BOXHD>
                            <CHED H="1"> </CHED>
                            <CHED H="1">Year 1</CHED>
                            <CHED H="1">Year 2</CHED>
                            <CHED H="1">Year 3</CHED>
                            <CHED H="1">Year 4</CHED>
                            <CHED H="1">Year 5</CHED>
                            <CHED H="1">Total</CHED>
                        </BOXHD>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">Costs and Cost Savings—Option 2</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Familiarization (undiscounted)</ENT>
                            <ENT>$117.2</ENT>
                            <ENT>$0.0</ENT>
                            <ENT>$0.0</ENT>
                            <ENT>$0.0</ENT>
                            <ENT>$0.0</ENT>
                            <ENT>$117.1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Familiarization (3%)</ENT>
                            <ENT>113.8</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>113.7</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Familiarization (7%)</ENT>
                            <ENT>106.3</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>106.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Assurance and Certification (undiscounted)</ENT>
                            <ENT>−187.2</ENT>
                            <ENT>−171.1</ENT>
                            <ENT>−171.1</ENT>
                            <ENT>−171.1</ENT>
                            <ENT>−171.1</ENT>
                            <ENT>−871.5</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Assurance and Certification (3%)</ENT>
                            <ENT>−181.7</ENT>
                            <ENT>−161.3</ENT>
                            <ENT>−156.6</ENT>
                            <ENT>−152.0</ENT>
                            <ENT>−147.6</ENT>
                            <ENT>−799.1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Assurance and Certification (7%)</ENT>
                            <ENT>−169.8</ENT>
                            <ENT>−140.8</ENT>
                            <ENT>−127.8</ENT>
                            <ENT>−116.0</ENT>
                            <ENT>−105.2</ENT>
                            <ENT>−659.6</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Voluntary Notice (undiscounted)</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Voluntary Notice (3%)</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Voluntary Notice (7%)</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Voluntary Remedial Efforts (undiscounted)</ENT>
                            <ENT>−8.8</ENT>
                            <ENT>−8.8</ENT>
                            <ENT>−8.8</ENT>
                            <ENT>−8.8</ENT>
                            <ENT>−8.8</ENT>
                            <ENT>−43.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Voluntary Remedial Efforts (3%)</ENT>
                            <ENT>−8.5</ENT>
                            <ENT>−8.3</ENT>
                            <ENT>−8.0</ENT>
                            <ENT>−7.8</ENT>
                            <ENT>−7.6</ENT>
                            <ENT>−40.2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Voluntary Remedial Efforts (7%)</ENT>
                            <ENT>−8.0</ENT>
                            <ENT>−7.2</ENT>
                            <ENT>−6.6</ENT>
                            <ENT>−5.9</ENT>
                            <ENT>−5.4</ENT>
                            <ENT>−33.1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">OCR Enforcement Costs (undiscounted)</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">OCR Enforcement Costs (3%)</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">OCR Enforcement Costs (7%)</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="03">Total Costs (undiscounted)</ENT>
                            <ENT>−78.7</ENT>
                            <ENT>−179.8</ENT>
                            <ENT>−179.8</ENT>
                            <ENT>−179.8</ENT>
                            <ENT>−179.8</ENT>
                            <ENT>−798.2</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="03">Total Costs (3%)</ENT>
                            <ENT>−76.4</ENT>
                            <ENT>−169.5</ENT>
                            <ENT>−164.6</ENT>
                            <ENT>−159.8</ENT>
                            <ENT>−155.1</ENT>
                            <ENT>−725.5</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total Costs (7%)</ENT>
                            <ENT>−71.4</ENT>
                            <ENT>−148.1</ENT>
                            <ENT>−134.4</ENT>
                            <ENT>−121.9</ENT>
                            <ENT>−110.6</ENT>
                            <ENT>−586.4</ENT>
                        </ROW>
                        <TNOTE>Negative costs indicate the Policy Option, if finalized would result in cost savings.</TNOTE>
                    </GPOTABLE>
                    <HD SOURCE="HD3">Policy Option 3: The Final Rule With an Alternative Notice Provision</HD>
                    <P>The Department analyzed a third policy option, which is similar to the final rule, but would further modify the notice provision by requiring covered entities to post these notices in designated places. The 2019 Final Rule's RIA assumes that about half of covered entities would provide these notices on a voluntary basis, and we carried this assumption through in this analysis, including in our analysis of the costs of the proposed rule. Under Policy Option 3, we anticipate that all covered entities would provide notices, and therefore estimate that the costs of mandatory notices would be double that of our estimates of the costs of voluntary notices.</P>
                    <P>
                        To quantify the net impact of Policy Option 3, we subtract the costs associated with enforcement and mandatory notice provisions from our 
                        <PRTPAGE P="2106"/>
                        earlier estimates of the total cost savings of rescinding the 2019 Final Rule. Compared to our primary baseline, we estimate that Policy Option 3 would result in annualized cost savings in 2022 dollars of $121.2 million using a 3-percent discount rate and $95.2 million using a 7-percent discount rate. We report these estimates in Table A in the Summary of Impacts section, which also includes comparable estimates corresponding to our alternative baseline scenario; a detailed breakdown of primary baseline impacts is included in Table 3 below.
                    </P>
                    <GPOTABLE COLS="7" OPTS="L2,i1" CDEF="s50,8,8,8,8,8,8">
                        <TTITLE>Table 3—Costs and Cost Savings—Option 3 (Primary Baseline)</TTITLE>
                        <TDESC>[Discounted 3% and 7% in millions]</TDESC>
                        <BOXHD>
                            <CHED H="1"> </CHED>
                            <CHED H="1">Year 1</CHED>
                            <CHED H="1">Year 2</CHED>
                            <CHED H="1">Year 3</CHED>
                            <CHED H="1">Year 4</CHED>
                            <CHED H="1">Year 5</CHED>
                            <CHED H="1">Total</CHED>
                        </BOXHD>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">Costs and Cost Savings—Option 3</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Familiarization (undiscounted)</ENT>
                            <ENT>$117.2</ENT>
                            <ENT>$0.0</ENT>
                            <ENT>$0.0</ENT>
                            <ENT>$0.0</ENT>
                            <ENT>$0.0</ENT>
                            <ENT>$117.1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Familiarization (3%)</ENT>
                            <ENT>113.8</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>113.7</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Familiarization (7%)</ENT>
                            <ENT>106.3</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>106.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Assurance and Certification (undiscounted)</ENT>
                            <ENT>−187.2</ENT>
                            <ENT>−171.1</ENT>
                            <ENT>−171.1</ENT>
                            <ENT>−171.1</ENT>
                            <ENT>−171.1</ENT>
                            <ENT>−871.5</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Assurance and Certification (3%)</ENT>
                            <ENT>−181.7</ENT>
                            <ENT>−161.3</ENT>
                            <ENT>−156.6</ENT>
                            <ENT>−152.0</ENT>
                            <ENT>−147.6</ENT>
                            <ENT>−799.1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Assurance and Certification (7%)</ENT>
                            <ENT>−169.8</ENT>
                            <ENT>−140.8</ENT>
                            <ENT>−127.8</ENT>
                            <ENT>−116.0</ENT>
                            <ENT>−105.2</ENT>
                            <ENT>−659.6</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Mandatory Notice (undiscounted)</ENT>
                            <ENT>112.3</ENT>
                            <ENT>17.0</ENT>
                            <ENT>17.0</ENT>
                            <ENT>17.0</ENT>
                            <ENT>17.0</ENT>
                            <ENT>180.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Mandatory Notice (3%)</ENT>
                            <ENT>109.1</ENT>
                            <ENT>16.0</ENT>
                            <ENT>15.5</ENT>
                            <ENT>15.1</ENT>
                            <ENT>14.6</ENT>
                            <ENT>170.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Mandatory Notice (7%)</ENT>
                            <ENT>101.9</ENT>
                            <ENT>14.0</ENT>
                            <ENT>12.7</ENT>
                            <ENT>11.5</ENT>
                            <ENT>10.4</ENT>
                            <ENT>150.6</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Voluntary Remedial Efforts (undiscounted)</ENT>
                            <ENT>−8.8</ENT>
                            <ENT>−8.8</ENT>
                            <ENT>−8.8</ENT>
                            <ENT>−8.8</ENT>
                            <ENT>−8.8</ENT>
                            <ENT>−43.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Voluntary Remedial Efforts (3%)</ENT>
                            <ENT>−8.5</ENT>
                            <ENT>−8.3</ENT>
                            <ENT>−8.0</ENT>
                            <ENT>−7.8</ENT>
                            <ENT>−7.6</ENT>
                            <ENT>−40.2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Voluntary Remedial Efforts (7%)</ENT>
                            <ENT>−8.0</ENT>
                            <ENT>−7.2</ENT>
                            <ENT>−6.6</ENT>
                            <ENT>−5.9</ENT>
                            <ENT>−5.4</ENT>
                            <ENT>−33.1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">OCR Enforcement Costs (undiscounted)</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">OCR Enforcement Costs (3%)</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">OCR Enforcement Costs (7%)</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                            <ENT>0.0</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="03">Total Costs (undiscounted)</ENT>
                            <ENT>$33.6</ENT>
                            <ENT>−162.9</ENT>
                            <ENT>−162.9</ENT>
                            <ENT>−162.9</ENT>
                            <ENT>−162.9</ENT>
                            <ENT>−617.9</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="03">Total Costs (3%)</ENT>
                            <ENT>$32.6</ENT>
                            <ENT>−153.5</ENT>
                            <ENT>−149.0</ENT>
                            <ENT>−144.7</ENT>
                            <ENT>−140.5</ENT>
                            <ENT>−555.2</ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="03">Total Costs (7%)</ENT>
                            <ENT>$30.5</ENT>
                            <ENT>−134.1</ENT>
                            <ENT>−121.7</ENT>
                            <ENT>−110.4</ENT>
                            <ENT>−100.2</ENT>
                            <ENT>−435.9</ENT>
                        </ROW>
                        <TNOTE>
                            <E T="02">Notes:</E>
                             Negative costs indicate the Policy Option, if finalized would result in cost savings.
                        </TNOTE>
                    </GPOTABLE>
                    <HD SOURCE="HD2">D. Summary of Impacts</HD>
                    <P>This analysis estimates the costs associated with the final rule and for two policy alternatives. For the final rule, we estimate the present value of the costs of −$725.5 million using a 3-percent discount rate and −$586.4 million using a 7-percent discount rate. Alternatively stated, we estimate that the final rule would generate cost savings of $725.5 million using a 3-percent discount rate and $586.4 million using a 7-percent discount rate. Table A reports cost estimates for the Final Rule and for the two policy alternatives. These estimates are reported in millions of 2022 dollars over a 5-year time horizon. Table A presents these cost estimates in present value terms and as annualized values for both a 3-percent and a 7-percent discount rate. Table A reports these estimates for our primary baseline scenario that the 2019 Final Rule would take effect, and for an alternative baseline scenario that the 2019 Final Rule would never take effect, even without any subsequent regulatory action. We do not identify any quantified benefits for the Final Rule or for the two policy alternatives.</P>
                    <P>The Department has selected Policy Option 2 despite Policy Option 1 generating the most savings because Policy Option 2 both rescinds the 2019 Final Rule and maintains several of its provisions. This approach better clarifies OCR's existing authorities and processes for enforcing the conscience statutes, as explained above.</P>
                    <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s50,10,10,10,10">
                        <TTITLE>Table A—Accounting Table of Costs</TTITLE>
                        <TDESC>[Millions of 2022 dollars over a 5-year time horizon]</TDESC>
                        <BOXHD>
                            <CHED H="1">Baseline scenario and policy option</CHED>
                            <CHED H="1">
                                Present value by
                                <LI>discount rate</LI>
                            </CHED>
                            <CHED H="2">3 Percent</CHED>
                            <CHED H="2">7 Percent</CHED>
                            <CHED H="1">
                                Annualized value by
                                <LI>discount rate</LI>
                            </CHED>
                            <CHED H="2">3 Percent</CHED>
                            <CHED H="2">7 Percent</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="22">Primary Baseline:</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Option 1 (Rescinding the 2019 Final Rule)</ENT>
                            <ENT>−$912.3</ENT>
                            <ENT>−$750.5</ENT>
                            <ENT>−$199.2</ENT>
                            <ENT>−$163.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Option 2 (The Final Rule)</ENT>
                            <ENT>−725.5</ENT>
                            <ENT>−586.4</ENT>
                            <ENT>−158.4</ENT>
                            <ENT>−128.0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Option 3 (The Final Rule with an Alternative Notice Provision)</ENT>
                            <ENT>−555.2</ENT>
                            <ENT>−435.9</ENT>
                            <ENT>−121.2</ENT>
                            <ENT>−95.2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Alternative Baseline:</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Option 1 (Rescinding the 2019 Final Rule)</ENT>
                            <ENT>113.7</ENT>
                            <ENT>106.3</ENT>
                            <ENT>24.8</ENT>
                            <ENT>23.2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Option 2 (The Final Rule)</ENT>
                            <ENT>300.5</ENT>
                            <ENT>270.4</ENT>
                            <ENT>65.6</ENT>
                            <ENT>59.0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Option 3 (The Final Rule with an Alternative Notice Provision)</ENT>
                            <ENT>470.8</ENT>
                            <ENT>420.9</ENT>
                            <ENT>102.8</ENT>
                            <ENT>91.9</ENT>
                        </ROW>
                        <TNOTE>
                            <E T="02">Notes:</E>
                             Negative costs indicate the Policy Option, if finalized would result in cost savings.
                        </TNOTE>
                    </GPOTABLE>
                    <PRTPAGE P="2107"/>
                    <HD SOURCE="HD2">E. Regulatory Flexibility Analysis</HD>
                    <P>The Regulatory Flexibility Act (RFA) (5 U.S.C. 601-612) requires us to analyze regulatory options that would minimize any significant impact of a rule on small entities. HHS has examined the economic implications of this final rule as required by the RFA. The RFA requires an agency to describe the impact of a rulemaking on small entities by providing an initial regulatory flexibility analysis unless the agency expects that the rule will not have a significant impact on a substantial number of small entities, provides a factual basis for this determination, and to certify the statement. 5 U.S.C. 603(a), 605(b). If an agency must provide an initial regulatory flexibility analysis, this analysis must address the consideration of regulatory options that would lessen the economic effect of the rule on small entities. For purposes of the RFA, small entities include small businesses, nonprofit organizations, and small governmental jurisdictions. HHS considers a rule to have a significant impact on a substantial number of small entities if it has at least a three percent impact of revenue on at least five percent of small entities.</P>
                    <P>One commenter said that HHS also needs to assess and certify the impact on small businesses and all non-profits under the RFA, using the above analysis on costs and explaining its reasoning. The commenter pointed to non-profit organizations, including many religiously affiliated hospitals and health-care facilities, and small health-care practitioners as entities and individuals affected by this rule.</P>
                    <P>Based on its examination, the Department has concluded that this rule does not have a significant economic impact on a substantial number of small entities. The entities that would be affected by this final rule, in industries described in detail in the RIA, are considered small by virtue of either nonprofit status or having revenues of less than between $7.5 million and $38.5 million in average annual revenue, with the threshold varying by industry. Persons and States are not included in the definition of a small entity. The Department assumes that most of the entities affected meet the threshold of a small entity.</P>
                    <P>Although this final rule will apply to and affect small entities, this rule's per-entity effects are relatively small. The Department estimates that this rule would result in average cost savings of $307 per entity in the primary baseline scenario, or an average cost of $129 per entity in the alternative baseline scenario, over the first five years of compliance (both annualized with a 3-percent discount rate). Furthermore, any costs would generally be proportional to the size of an entity, so that the smallest affected entities will face lower average costs. Given the thresholds discussed in the preceding paragraphs, the average costs are below the Department's default threshold for significance.</P>
                    <P>Because this final rule would result in either a small reduction in costs to small entities or minimal to no impact on costs to small entities, this analysis concludes, and the Secretary certifies that the rule will not have a significant economic impact on a substantial number of small entities. This finding and certification is consistent with the regulatory flexibility analysis of the 2019 Final Rule that would be partially rescinded by this regulatory action, which “concluded that this rule does not have a significant economic impact on a substantial number of small entities” (84 FR 23255).</P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects in 45 CFR Part 88</HD>
                        <P>Adult education, Authority delegations (Government agencies), Civil rights, Colleges and universities, Community facilities, Conflicts of interest, Educational facilities, Employment, Family planning, Freedom of information, Government contracts, Government employees, Grant programs—health, Grants administration, Health care, Health facilities, Health insurance, Health professions, Hospitals, Immunization, Indians—Tribal government, Insurance, Insurance companies, Intergovernmental relations, Laboratories, Maternal and child health, Medicaid, Medical and dental schools, Medical research, Medicare, Mental health programs, Nursing homes, Occupational safety and health, Prescription drugs, Public assistance programs, Public health, Religious discrimination, Reporting and recordkeeping requirements, Research, Scholarships and fellowships, Schools, Scientists.</P>
                    </LSTSUB>
                    <SIG>
                        <NAME>Xavier Becerra,</NAME>
                        <TITLE>Secretary, Department of Health and Human Services.</TITLE>
                    </SIG>
                    <REGTEXT TITLE="45" PART="88">
                        <AMDPAR>For the reasons set forth in the preamble, the Department revises 45 CFR part 88 to read as follows:</AMDPAR>
                        <PART>
                            <HD SOURCE="HED">PART 88—ENSURING THAT DEPARTMENT OF HEALTH AND HUMAN SERVICES FUNDS DO NOT SUPPORT COERCIVE OR DISCIMINATORY POLICIES OR PRACTICES IN VIOLATION OF FEDERAL LAW</HD>
                            <CONTENTS>
                                <SECHD>Sec.</SECHD>
                                <SECTNO>88.1</SECTNO>
                                <SUBJECT>Purpose</SUBJECT>
                                <SECTNO>88.2</SECTNO>
                                <SUBJECT>Complaint handling and investigating.</SUBJECT>
                                <SECTNO>88.3</SECTNO>
                                <SUBJECT>Notice of Federal conscience and nondiscrimination laws.</SUBJECT>
                                <SECTNO>88.4</SECTNO>
                                <SUBJECT>Severability.</SUBJECT>
                                <FP SOURCE="FP-2">Appendix A to Part 88—Model Text: Notice of Rights Under Federal Conscience and Nondiscrimination Laws</FP>
                            </CONTENTS>
                            <AUTH>
                                <HD SOURCE="HED">Authority:</HD>
                                <P> 5 U.S.C. 301.</P>
                            </AUTH>
                            <SECTION>
                                <SECTNO>§ 88.1</SECTNO>
                                <SUBJECT>Purpose.</SUBJECT>
                                <P>
                                    The purpose of this part is to provide for the enforcement of the Church Amendments, 42 U.S.C. 300a-7; the Coats-Snowe Amendment, section 245 of the Public Health Service Act, 42 U.S.C. 238n; the Weldon Amendment, 
                                    <E T="03">e.g.,</E>
                                     Consolidated Appropriations Act, 2023, Public Law 117-328, div. H, title V General Provisions, section 507(d)(1) (Dec. 29, 2022); Sections 1303(b)(1)(A), (b)(4), and (c)(2)(A), and 1411(b)(5)(A), and 1553 of the ACA, 42 U.S.C. 18023(b)(1)(A), (b)(4), and (c)(2)(A), 18081(b)(5)(A), and 18113; certain Medicare and Medicaid provisions, 42 U.S.C. 1320a-1(h), 1320c-11, 1395i-5, 1395w-22(j)(3)(B), 1395x(e), 1395x(y)(1), 1395cc(f), 1396a(a), 1396a(w)(3), 1396u-2(b)(3)(B), 1397j-1(b), and 14406; the Helms, Biden, 1978, and 1985 Amendments, 22 U.S.C. 2151b(f), 
                                    <E T="03">accord, e.g.,</E>
                                     Consolidated Appropriations Act, 2023, Public Law 117-328, div. K, title VII, section 7018 (Dec. 29, 2022); 22 U.S.C. 7631(d); 42 U.S.C. 280g-1(d), 290bb-36(f), 1396f, 1396s(c)(2)(B)(ii); 5106i(a)); and 29 U.S.C. 669(a)(5), referred to collectively as the “Federal health care conscience protection statutes.”
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 88.2</SECTNO>
                                <SUBJECT>Complaint handling and investigating.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Delegated authority.</E>
                                     The Office for Civil Rights (OCR) has been delegated the authority to facilitate and coordinate the Department's enforcement of the Federal health care conscience protection statutes, which includes the authority to:
                                </P>
                                <P>(1) Receive and handle complaints;</P>
                                <P>(2) Initiate compliance reviews;</P>
                                <P>(3) Conduct investigations;</P>
                                <P>(4) Consult on compliance within the Department;</P>
                                <P>(5) Seek voluntary resolutions of complaints;</P>
                                <P>
                                    (6) Consult and coordinate with the relevant Departmental funding component, and utilize existing 
                                    <PRTPAGE P="2108"/>
                                    enforcement regulations, such as those that apply to grants, contracts, or other programs and services;
                                </P>
                                <P>(7) In coordination with the relevant component or components of the Department, coordinate other appropriate remedial action as the Department deems necessary and as allowed by law and applicable regulation; and</P>
                                <P>(8) In coordination with the relevant component or components of the Department, make enforcement referrals to the Department of Justice.</P>
                                <P>
                                    (b) 
                                    <E T="03">Complaints.</E>
                                     Any entity or individual may file a complaint with OCR alleging a potential violation of Federal health care conscience protection statutes. OCR shall coordinate handling of complaints with the relevant Department component(s). The complaint filer is not required to be the entity whose rights under the Federal health care conscience protection statutes have been potentially violated.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Compliance reviews.</E>
                                     OCR may conduct compliance reviews of an entity subject to the Federal health care conscience protection statutes, where authorized for the funding at issue, to determine whether they are complying with Federal health care conscience protection statutes. OCR may initiate a compliance review of an entity subject to the Federal health care conscience protection statutes based on information from a complaint or other source that causes OCR to suspect non-compliance by such entity with the Federal health care conscience protection statutes.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Investigations.</E>
                                     OCR shall make a prompt investigation of a complaint alleging failure to comply with the Federal health care conscience protection statutes. This investigation may include a review of the pertinent practices, policies, communications, documents, compliance history, circumstances under which the possible noncompliance occurred, and other factors relevant to determining whether the Department, Department components, recipient, or sub-recipient has failed to comply. OCR may use fact-finding methods including site visits; interviews with the complainants, Department components, recipients, sub-recipients, or third parties; and written data requests. OCR may seek the assistance of any State agency.
                                </P>
                                <P>
                                    (e) 
                                    <E T="03">Failure to respond.</E>
                                     OCR will adopt a negative inference if, absent good cause, an entity that is subject to the Federal health care conscience protection statutes fails to respond to a request for information or to a data or document request within a reasonable timeframe.
                                </P>
                                <P>
                                    (f) 
                                    <E T="03">Supervision and coordination.</E>
                                     If, as a result of an investigation, OCR makes a determination of noncompliance with responsibilities under the Federal health care conscience protection statutes, OCR will coordinate and consult with the Departmental component responsible for the relevant funding to undertake appropriate action with the component to assure compliance.
                                </P>
                                <P>
                                    (g) 
                                    <E T="03">Resolution of matters.</E>
                                     (1) If an investigation reveals that no action is warranted, OCR will in writing so inform any party who has been notified by OCR of the existence of the investigation.
                                </P>
                                <P>(2) If an investigation indicates a failure to comply with the Federal health care conscience protection statutes, OCR will so inform the relevant parties and the matter will be resolved by informal means whenever possible.</P>
                                <P>(3) If a matter cannot be resolved by informal means, OCR will coordinate with the relevant Departmental component to:</P>
                                <P>(i) Utilize existing enforcement regulations, such as those that apply to grants, contracts, or other programs and services, or</P>
                                <P>(ii) Withhold relevant funding to the extent authorized under the statutes listed under § 88.1.</P>
                                <P>(4) If a matter cannot be resolved by informal means, OCR may, in coordination with the Office of the General Counsel, refer the matter to the Department of Justice to the extent permitted by law for proceedings to enforce the statutes listed under § 88.1.</P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 88.3</SECTNO>
                                <SUBJECT>Notice of Federal conscience and nondiscrimination laws.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">In general.</E>
                                     OCR considers the posting of a notice consistent with this part as a best practice towards achieving compliance with and educating the public about the Federal health care conscience protection statutes, and encourages all entities subject to the Federal health care conscience protection statutes to post the model notice provided in Appendix A to this part. OCR will consider posting a notice as a factor in any investigation or compliance review under this rule.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Placement of the notice text.</E>
                                     The model notice in Appendix A to this part should be posted in the following places, where relevant:
                                </P>
                                <P>(1) On the Department or recipient's website(s);</P>
                                <P>(2) In a prominent and conspicuous physical location in the Department's or covered entity's establishments where notices to the public and notices to its workforce are customarily posted to permit ready observation;</P>
                                <P>(3) In a personnel manual, handbook, orientation materials, trainings, or other substantially similar document likely to be reviewed by members of the covered entity's workforce;</P>
                                <P>(4) In employment applications to the Department or covered entity, or in applications for participation in a service, benefit, or other program, including for training or study; and</P>
                                <P>(5) In any student handbook, orientation materials, or other substantially similar document for students participating in a program of training or study, including for postgraduate interns, residents, and fellows.</P>
                                <P>
                                    (c) 
                                    <E T="03">Format of the notice.</E>
                                     The text of the notice should be large and conspicuous enough to be read easily and be presented in a format, location, and manner that impedes or prevents the notice being altered, defaced, removed, or covered by other material.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Content of the notice text.</E>
                                     A recipient or the Department should consider using the model text provided in Appendix A to this part for the notice but may tailor its notice to address its particular circumstances and to more specifically address the Federal health care conscience protection statutes covered by this rule that apply to it. Where possible, and where the recipient does not have a conscience-based objection to doing so, the notice should include information about alternative providers that may offer patients services the recipient does not provide for reasons of conscience.
                                </P>
                                <P>
                                    (e) 
                                    <E T="03">Combined nondiscrimination notices.</E>
                                     The Department and each recipient may post the notice text provided in Appendix A of this part, or a notice it drafts itself, along with the content of other notices (such as other nondiscrimination notices).
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 88.4</SECTNO>
                                <SUBJECT>Severability.</SUBJECT>
                                <P>Any provision of this part held to be invalid or unenforceable either by its terms or as applied to any entity or circumstance shall be construed so as to continue to give the maximum effect to the provision permitted by law, unless such holding shall be one of utter invalidity or unenforceability, in which event such provision shall be severable from this part, which shall remain in full force and effect to the maximum extent permitted by law. A severed provision shall not affect the remainder of this part or the application of the provision to other persons or entities not similarly situated or to other, dissimilar circumstances.</P>
                                <APPENDIX>
                                    <PRTPAGE P="2109"/>
                                    <HD SOURCE="HED">Appendix A to Part 88—Model Text: Notice of Rights Under Federal Conscience and Nondiscrimination Laws</HD>
                                    <P>
                                        [Name of entity] complies with applicable Federal health care conscience protection statutes, including the Church Amendments, 42 U.S.C. 300a-7; the Coats-Snowe Amendment, section 245 of the Public Health Service Act, 42 U.S.C. 238n; the Weldon Amendment, 
                                        <E T="03">e.g.,</E>
                                         Consolidated Appropriations Act, 2023, Public Law 117-328, div. H, title V General Provisions, section 507(d)(1) (Dec. 29, 2022); Sections 1303(b)(1)(A), (b)(4), and (c)(2)(A), and 1411(b)(5)(A), and 1553 of the ACA, 42 U.S.C. 18023(b)(1)(A), (b)(4), and (c)(2)(A), 18081(b)(5)(A), and 18113; certain Medicare and Medicaid provisions, 42 U.S.C. 1320a-1(h), 1320c-11, 1395i-5, 1395w-22(j)(3)(B), 1395x(e), 1395x(y)(1), 1395cc(f), 1396a(a), 1396a(w)(3), 1396u-2(b)(3)(B), 1397j-1(b), and 14406; the Helms, Biden, 1978, and 1985 Amendments, 22 U.S.C. 2151b(f), 
                                        <E T="03">accord, e.g.,</E>
                                         Consolidated Appropriations Act, 2023, Public Law 117-328, div. K, title VII, section 7018 (Dec. 29, 2022); 22 U.S.C. 7631(d); 42 U.S.C. 280g-1(d), 290bb-36(f), 1396f, 1396s(c)(2)(B)(ii); 5106i(a)); and 29 U.S.C. 669(a)(5). More information to help entities determine which statutes are applicable to them is available at 
                                        <E T="03">https://www.hhs.gov/conscience/conscience-protections/index.html.</E>
                                         You may have rights as a provider, patient, or other individual under these Federal statutes, which prohibit coercion or other discrimination on the basis of conscience, whether based on religious beliefs or moral convictions, in certain circumstances. If you believe that [Name of entity] has violated any of these provisions, you may file a complaint with the U.S. Department of Health and Human Services, Office for Civil Rights, electronically through the Office for Civil Rights Complaint Portal, available at 
                                        <E T="03">https://www.hhs.gov/ocr/complaints/index.html</E>
                                         or by mail or phone at: U.S. Department of Health and Human Services, 200 Independence Avenue SW, Room 509F, HHH Building, Washington, DC 20201, 1-800-368-1019, 800-537-7697 (TDD) or by email at 
                                        <E T="03">ocrmail@hhs.gov.</E>
                                         Complaint forms and more information about Federal conscience protection laws are available at 
                                        <E T="03">https://www.hhs.gov/conscience.</E>
                                    </P>
                                </APPENDIX>
                            </SECTION>
                        </PART>
                    </REGTEXT>
                </SUPLINF>
                <FRDOC>[FR Doc. 2024-00091 Filed 1-9-24; 8:45 am]</FRDOC>
                <BILCOD>BILLING CODE 4153-01-P</BILCOD>
            </RULE>
        </RULES>
    </NEWPART>
</FEDREG>
